Uplink (UL) timing acquisition for support of UL and downlink (DL) carrier aggregation (CA) decoupling

The implementation of UL timing acquisition methods for decoupling UL and DL carrier aggregation addresses inefficiencies in wireless communication systems by synchronizing UL transmissions with DL timing references, enhancing network performance and resource utilization.

WO2026235896A1PCT designated stage Publication Date: 2026-11-12APPLE INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/US2026/024224
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-05
Filing Date
2026-04-17
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

Existing wireless communication systems face challenges in efficiently managing uplink (UL) and downlink (DL) carrier aggregation (CA) due to the lack of effective timing acquisition mechanisms, particularly in scenarios where UL and DL CCs are not co-located, leading to inefficiencies in resource allocation and communication performance.

Method used

Implementing methods and apparatuses for UL timing acquisition that enable decoupling of UL and DL carrier aggregation by utilizing signaling mechanisms to synchronize UL transmissions with DL timing references, even when CCs are non-co-located, through techniques such as cross-CC contention-free and contention-based Random Access Channel (RACH) processes.

Benefits of technology

Enhances communication efficiency and resource utilization by enabling precise UL timing synchronization, even in non-co-located scenarios, thereby improving overall system performance and reducing latency in wireless networks.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure US2026024224_12112026_PF_FP_ABST
    Figure US2026024224_12112026_PF_FP_ABST
Patent Text Reader

Abstract

A user equipment (UE) comprises processors coupled to memory and configured to receive, at the UE from a network (NW) via a base station (BS), an uplink (UL) timing advance (TA) command to enable the UE to obtain UL timing information for two or more component carriers (CCs) aggregated together in a carrier aggregation (CA) configuration. The two or more CCs comprise a first component carrier (CC A), which is a UL only CC without a corresponding DL CC, co-located with a second component carrier (CC B) which is comprised of both a UL CC and a DL CC, and receives the TA command in the DL CC from the BS. The processors are conjured to send, at the UE to the NW via the base station, UL transmissions on the first component carrier (CC A) using UL timing information based on the TA command from the second component carrier.
Need to check novelty before this filing date? Find Prior Art

Description

Client Ref. No. P71093WO1UPLINK (UL) TIMING ACQUISITION FOR SUPPORT OF UL AND DOWNLINK (DL) CARRIER AGGREGATION (CA) DECOUPLING

[0001] Embodiments of the invention relate to wireless communications, including apparatuses, systems, and methods for an uplink (UL) timing acquisition for support of UL and downlink (DL) carrier aggregation (CA) decoupling in wireless communication systems.DESCRIPTION OF THE RELATED ART

[0002] Wireless communication systems are used to provide various communication services such as telephone, video, data and messaging. The wireless communication systems can support communication with multiple users by sharing available system resources such as bandwidth and transmit power.

[0003] The wireless communication system may include a number of base stations (BSs) that can support communication for a number of user equipment (UEs). A BS may be referred to as a Node B, a gNB, an access point (AP), a radio head, a transmit receive point (TRP), a New Radio (NR) BS, a 5G Node B, or the like. A UE may be referred to as a wireless mobile device or cellular phone.

[0004] Telecommunication standards have been adopted to provide a common protocol to enable different UEs and BSs to communicate on a municipal, national, regional, and even global level. Wireless communication system standards and protocols can include the 3rd Generation Partnership Project (3GPP) long term evolution (LTE) (e.g., 4G) or new radio (NR) (e.g., 5G). In 3GPP radio access networks (RANs) in LTE systems, the base station can include a RAN Node such as an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly denoted as evolved Node B, enhanced Node B, eNodeB, or eNB) and / or Radio Network Controller (RNC) in an E-UTRAN, which communicate with the UE. In fifth generation (5G) wireless RANs, RAN Nodes can include a 5G Node, or NR node (also referred to as a next generation Node B or g Node B (gNB)).Client Ref. No. P71093WO1BRIEF DESCRIPTION OF THE DRAWINGS

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

[0006] FIG. 1A illustrates an example wireless communication system according to some embodiments.

[0007] FIG. 1 B illustrates an example of a base station and an access point in communication with a user equipment (UE) device, according to some embodiments.

[0008] FIG. 2 illustrates an example block diagram of a base station, according to some embodiments.

[0009] FIG. 3 illustrates an example block diagram of a server according to some embodiments.

[0010] FIG. 4 illustrates an example block diagram of a UE according to some embodiments.

[0011] FIG. 5 illustrates an example block diagram of cellular communication circuitry, according to some embodiments.

[0012] FIG. 6 illustrates an example of a baseband processor architecture for a UE, according to some embodiments.

[0013] FIG. 7 illustrates an example block diagram of an interface of baseband circuitry according to some embodiments.

[0014] FIG. 8 illustrates example components of a core network in accordance with some embodiments.

[0015] FIGS. 9 and 10 illustrate a simplified example carrier aggregation system, according to some embodiments.

[0016] FIG. 11 illustrates an example carrier aggregation system with a UL only CC (CC A) co-located with another UL CC (CC B) with a corresponding DL CC, according to some embodiments.Client Ref. No. P71093WO1

[0017] FIG. 12 illustrates a flowchart of an example method of UL timing acquisition for UL and DL decoupling, according to some embodiments.

[0018] FIG. 13 illustrates a flowchart of an example method of UL timing acquisition for UL and DL decoupling, according to some embodiments.

[0019] FIG. 14 illustrates an example carrier aggregation system with a UL only CC (CCA) non-co-located with another UL CC (CC B) with a corresponding DL CC, according to some embodiments.

[0020] FIG. 15 illustrates an example signaling for a cross-CC contention-free Random Access Channel (RACH) process, according to some embodiments.

[0021] FIG. 16 illustrates a flowchart of an example method of UL timing acquisition for UL and DL decoupling, according to some embodiments.

[0022] FIG. 17 illustrates an example signaling for a cross-CC contention-based Random Access Channel (RACH) process, according to some embodiments.

[0023] FIG. 18 illustrates a flowchart of an example method of UL timing acquisition for UL and DL decoupling, according to some embodiments.

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

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

[0026] Memory Medium or Memory - Any of various types of non-transitory memory devices or storage devices. The term “memory medium” is intended toClient Ref. No. P71093WO1include an installation medium, e.g., a CD-ROM, floppy disks, or tape device; a computer system memory or random-access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; a non-volatile memory such as a Flash, magnetic media, e.g., a hard drive, or optical storage; registers, or other similar types of memory elements, etc. The memory medium may include other types of non-transitory memory as well or combinations thereof. In addition, the memory medium may be located in a first computer system in which the programs are executed, or may be located in a second different computer system which connects to the first computer system over a network, such as the Internet. In the latter instance, the second computer system may provide program instructions to the first computer for execution. The term “memory medium” may include two or more memory mediums which may reside in different locations, e.g., in different computer systems that are connected over a network. The memory medium may store program instructions (e.g., embodied as computer programs) that may be executed by one or more processors.

[0027] Carrier Medium - a memory medium as described above, as well as a physical transmission medium, such as a bus, network, and / or other physical transmission medium that conveys signals such as electrical, electromagnetic, or digital signals.

[0028] Programmable Hardware Element includes various hardware devices comprising multiple programmable function blocks connected via a programmable interconnect. Examples include FPGAs (Field Programmable Gate Arrays), PLDs (Programmable Logic Devices), FPOAs (Field Programmable Object Arrays), and CPLDs (Complex PLDs). The programmable function blocks may range from fine grained (combinatorial logic or look up tables) to coarse grained (arithmetic logic units or processor cores). A programmable hardware element may also be referred to as "reconfigurable logic”.

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

[0030] User Equipment (UE) (or “UE Device”) - any of various types of computer systems devices which are mobile or portable and which performs wireless communications. Examples of UE devices include mobile telephones or smart phones (e.g., iPhone™, Android™-based phones), portable gaming devices (e.g., Nintendo DS™, PlayStation Portable™, Gameboy Advance™, iPhone™), laptops, wearable devices (e.g., smart watch, smart glasses), PDAs, portable Internet devices, Internet of Things, music players, data storage devices, other handheld devices, unmanned aerial vehicles (UAVs) (e.g., drones), UAV controllers (UACs), and so forth. In general, the term “UE” or “UE device” can be broadly defined to encompass any electronic, computing, and / or telecommunications device (or combination of devices) which is easily transported by a user and capable of wireless communication.

[0031] Base Station - The term “Base Station” has the full breadth of its ordinary meaning, and at least includes a wireless communication station installed at a fixed location and used to communicate with UEs as part of a wireless telephone system or radio system, including but not limited Next Generation Node-Bs (gNB or gNodeB) in NR and NG-RAN nodes.

[0032] Processing Element (or Processor) - refers to various elements or combinations of elements that are capable of performing a function in a device, such as a user equipment or a cellular network device. 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 an ASIC (Application Specific Integrated Circuit), programmable hardware elements such as a field programmable gate array (FPGA), as well any of various combinations of the above.

[0033] Channel - a medium used to convey information from a sender (transmitter) to a receiver. It should be noted that since characteristics of the termClient Ref. No. P71093WO1“channel” may differ according to different wireless protocols, the term “channel” as used herein may be considered as being used in a manner that is consistent with the standard of the type of device with reference to which the term is used. In some standards, channel widths may be variable (e.g., depending on device capability, band conditions, etc.). For example, LTE may support scalable channel bandwidths from 1.4 MHz to 20MHz. 5G NR can support scalable channel bandwidths from 5 MHz to 100 MHz in Frequency Range 1 (FR1) and up to 400 MHz in FR2. In other radio access technologies, WLAN channels may be 22 MHz wide while Bluetooth channels may 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, e.g., different channels for uplink or downlink and / or different channels for different uses such as data, control information, etc.

[0034] Band - The term "band" has the full breadth of its ordinary meaning, and at least includes a section of spectrum (e.g., radio frequency spectrum) in which channels are used or set aside for the same purpose.

[0035] Automatically - refers to an action or operation performed by a computer system (e.g., software executed by the computer system) or device (e.g., circuitry, programmable hardware elements, ASICs, etc.), without user input directly specifying or performing the action or operation. Thus, the term "automatically" is in contrast to an operation being manually performed or specified by the user, where the user provides input to directly perform the operation. An automatic procedure may be initiated by input provided by the user, but the subsequent actions that are performed “automatically” are not specified by the user, i.e., are not performed “manually”, where the user specifies each action to perform. For example, a user filling out an electronic form by selecting each field and providing input specifying information (e.g., by typing information, selecting check boxes, radio selections, etc.) is filling out the form manually, even though the computer system will update the form in response to the user actions. The form may be automatically filled out by the computer system where the computer system (e.g., software executing on the computer system) analyzes the fields of the form andClient Ref. No. P71093WO1fills in the form without any user input specifying the answers to the fields. As indicated above, the user may invoke the automatic filling of the form, but is not involved in the actual filling of the form (e.g., the user is not manually specifying answers to fields but rather they are being automatically completed). The present specification provides various examples of operations being automatically performed in response to actions the user has taken.

[0036] Approximately - refers to a value that is almost correct or exact. For example, approximately may refer to a value that is within 1 to 10 percent of the exact (or desired) value. It should be noted, however, that the actual threshold value (or tolerance) may be application dependent. For example, in some embodiments, “approximately” may mean within 0.1% of some specified or desired value, while in various other embodiments, the threshold may be, for example, 2%, 3%, 5%, and so forth, as desired or as set by the particular application.

[0037] Concurrent - refers to parallel execution or performance, where tasks, processes, or programs are performed in an at least partially overlapping manner. For example, concurrency may be implemented using “strong” or strict parallelism, where tasks are performed (at least partially) in parallel on respective computational elements, or using “weak parallelism”, where the tasks are performed in an interleaved manner, e.g., by time multiplexing of execution threads.

[0038] Various components may be described as “configured to” perform a task or tasks. In such contexts, “configured to” is a broad recitation generally meaning “having structure that” performs the task or tasks during operation. As such, the component can be configured to perform the task even when the component is not currently performing that task (e.g., a set of electrical conductors may be configured to electrically connect a module to another module, even when the two modules are not connected). In some contexts, “configured to” may be a broad recitation of structure generally meaning “having circuitry that” performs the task or tasks during operation. As such, the component can be configured to perform the task even when the component is not currently on. In general, the circuitry that forms the structure corresponding to “configured to” may include hardware circuits.Client Ref. No. P71093WO1

[0039] Various components may be described as performing a task or tasks, for convenience in the description. Such descriptions should be interpreted as including the phrase “configured to.” Reciting a component that is configured to perform one or more tasks is expressly intended not to invoke 35 U.S.C. § 112(f) interpretation for that component.

[0040] The example embodiments may be further understood with reference to the following description and the related appended drawings, wherein like elements are provided with the same reference numerals. The example embodiments relate to apparatuses, systems and methods for signaling and procedure of an artificial intelligence / machine learning (AI / ML) dataset and / or model parameter transfer between a network (NW) entity and a user equipment (UE) server for two-sided model including establishment of a tunnel between a NW training entity and a UE-side training server to enable non-over-the air (non-OTA) signaling and intervendor training collaboration.

[0041] The example embodiments are described with regard to communication between a network (NW) via a Radio Access Networks (RAN), e.g. a base station or a Next Generation Node B (gNB), and a user equipment (UE). However, reference to a base station (gNB) or a UE is merely provided for illustrative purposes. The example embodiments may be utilized with any electronic component that may establish a connection to a network and is configured with the hardware, software, and / or firmware to support establishing a tunnel for non-OTA signaling between a NW training entity and a UE-side training server. Therefore, the gNB or UE as described herein is used to represent any appropriate type of electronic component.

[0042] The example embodiments are also described with regard to a fifth generation (5G) New Radio (NR). However, reference to a 5G NR network is merely provided for illustrative purposes. The example embodiments may be utilized with any appropriate type of network.

[0043] Throughout this description various information elements (lEs) are referred to by specific names. It should be understood that these names are onlyClient Ref. No. P71093WO1examples and the lEs carrying the information referred to throughout this description may be referred to by other names by various entities.FIGs. 1A and 1B: Communication Systems

[0044] FIG. 1 A illustrates a simplified example wireless communication system, according to some embodiments. It is noted that the system of FIG. 1A is merely one example of a possible system, and that features of this disclosure may be implemented in any of various systems, as desired.

[0045] As shown, the example wireless communication system includes a base station 102A which communicates over a transmission medium with one or more user equipment 106A, 106B, etc., through 106N. Each of the user devices may be referred to herein as a “user equipment” (UE). Thus, the user equipment 106 are referred to as UEs or UE devices.

[0046] The base station (BS) 102A may be a base transceiver station (BTS) or cell site (a “cellular base station”) and may include hardware that enables wireless communication with the UEs 106A through 106N.

[0047] The communication area (or coverage area) of the base station may be referred to as a “cell.” The base station 102A and the UEs 106 may be configured to communicate over the transmission medium using any of various radio access technologies (RATs), also referred to as wireless communication technologies, or telecommunication standards, such as GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE, LTE-Advanced (LTE-A), 5G new radio (5G NR), HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), etc. Note that if the base station 102A is implemented in the context of LTE, also referred to as the Evolved Universal Terrestrial Radio Access Network (E-UTRAN, it may alternately be referred to as an 'eNodeB' or ‘eNB’. Note that if the base station 102A is implemented in the context of 5G NR, it may alternately be referred to as ‘gNodeB’ or ‘gNB’.

[0048] As shown, the base station 102A may also be equipped to communicate with a network 100 (e.g., a core network 820 of a cellular service provider, aClient Ref. No. P71093WO1telecommunication network such as a public switched telephone network (PSTN), and / or the Internet, among various possibilities). Thus, the base station 102A may facilitate communication between the user devices and / or between the user devices and the network 100. In particular, the cellular base station 102A may provide UEs 106 with various telecommunication capabilities, such as voice, SMS and / or data services.

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

[0050] Thus, while base station 102A may act as a “serving cell” for UEs 106A-N as illustrated in FIG. 1A, each UE 106 may also be capable of receiving signals from (and possibly within communication range of) one or more other cells (which might be provided by base stations 102B-N and / or any other base stations), which may be referred to as “neighboring cells”. Such cells may also be capable of facilitating communication between user devices and / or between user devices and the network 100. Such cells may include “macro” cells, “micro” cells, “pico” cells, and / or cells which provide any of various other granularities of service area size. For example, base stations 102A-B illustrated in FIG. 1A might be macro cells, while base station 102N might be a micro cell. Other configurations are also possible.

[0051] In some embodiments, base station 102A may be a next generation base station, e.g., a 5G New Radio (5G NR) base station, or “gNB”. In some embodiments, a gNB may be connected to a legacy evolved packet core (EPC) network and / or to a NR core (NRC) network. In addition, a gNB cell may include one or more transmission and reception points (TRPs). In addition, a UE capable of operating according to 5G NR may be connected to one or more TRPs within one or more gNBs.Client Ref. No. P71093WO1

[0052] Note that a UE 106 may be capable of communicating using multiple wireless communication standards. For example, the UE 106 may be configured to communicate using a wireless networking (e.g., Wi-Fi) and / or peer-to-peer wireless communication protocol (e.g., Bluetooth, Wi-Fi peer-to-peer, etc.) in addition to at least one cellular communication protocol (e.g., GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE, LTE-A, 5G NR, HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), etc.). The UE 106 may also or alternatively be configured to communicate using one or more global navigational satellite systems (GNSS, e.g., 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, if desired. Other combinations of wireless communication standards (including more than two wireless communication standards) are also possible.

[0053] In some embodiments, the base station 102A may select a paging configuration and a PEI configuration for UEs 106. The base station 102A may encode and transmit the paging configuration and the PEI configuration to UEs 106 as part of a registration process. Using the paging configuration, UEs 106 can determine which PO and PF to monitor in a paging cycle. Using the PEI configuration, UEs 106 can determine the radio frame that carries relevant PEI.

[0054] FIG. 1 B illustrates user equipment 106 (e.g., one of the UEs 106A through 106N) in communication with a base station 102 and an access point 112, according to some embodiments. The UE 106 may be a device with both cellular communication capability and non-cellular communication capability (e.g., Bluetooth, Wi-Fi, and so forth) such as a mobile phone, a hand-held device, a computer or a tablet, or virtually any type of wireless device.

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

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

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

[0058] As described herein, messages can be signaled between a UE 106 and the NW 100 via the base station 102, such as a Radio Access Network (RAN) or the gNB. The signaling can enable the UE 106 to receive an uplink (UL) timing information to enable UL transmission on a UL only component carrier (CC), i.e. a CC decoupled from or without a corresponding downlink (DL) CC. The UL timingClient Ref. No. P71093WO1information can be obtained from another CC which is both a UL CC and a DL CC with the timing information. The signaling may be different for CCs that are colocated or non-co-located. For co-located CCs, the signaling can comprise the UE 106 receiving a UL timing advance (TA) command (TA_CC_B) from the NW 100 via the base station 102. Also, for co-located CCs, the NW 100 can form a UL timing reference group (RRG) comprising at least two UL CCs wherein at least one of the UL CCs has a corresponding DL CC. The UE can receive a TA command on the corresponding DL CC. The UE 106 can send UL transmissions on a first CC which can be a UL only CC. For non-co-located CCs, the UE 106 can receive DL timing from the NW 100 on a first base station (BS1) 102 on a DL transmission on a second CC (CC B) with both a UL CC and a DL CC. The UE 106 can send UL transmissions on a first CC (CC A) using UL timing based on the DL timing.FIG. 2: Block Diaqram of a Base Station (cjNB)

[0059] FIG. 2 illustrates an example block diagram of a base station 102, according to some embodiments. It is noted that the base station of FIG. 2 is merely one example of a possible base station. As shown, the base station 102 may include processor(s) 204 which may execute program instructions for the base station 102. The processor(s) 204 may also be coupled to memory management unit (MMU) 240, which may be configured to receive addresses from the processor(s) 204 and translate those addresses to locations in memory (e.g., memory 260 and read only memory (ROM) 250) or to other circuits or devices.

[0060] The base station 102 may include at least one network port 270. The network port 270 may be configured to couple to a telephone network and provide a plurality of devices, such as UEs 106, access to the telephone network as described above in FIGs. 1 and 2.

[0061] The network port 270 (or an additional network port) may also or alternatively be configured to couple to a cellular network, e.g., a core network of a cellular service provider. The core network may provide mobility related services and / or other services to a plurality of devices, such as UEs 106. In some cases,Client Ref. No. P71093WO1the network port 270 may couple to a telephone network via the core network, and / or the core network may provide a telephone network (e.g., among other UE devices serviced by the cellular service provider).

[0062] In some embodiments, base station 102 may be a next generation base station, e.g., a 5G New Radio (5G NR) base station, or “gNB”. In such embodiments, base station 102 may be connected to a legacy evolved packet core (EPC) network and / or to a NR core (NRC) network. In addition, base station 102 may be considered a 5G NR cell and may include one or more transmission and reception points (TRPs). In addition, a UE capable of operating according to 5G NR may be connected to one or more TRPs within one or more gNBs.

[0063] The base station 102 may include at least one antenna 234, and possibly multiple antennas. The at least one antenna 234 may be configured to operate as a wireless transceiver and may be further configured to communicate with UEs 106 via radio 230. The antenna 234 communicates with the radio 230 via communication chain 232. Communication chain 232 may be a receive chain, a transmit chain or both. The radio 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.

[0064] The base station 102 may be configured to communicate wirelessly using multiple wireless communication standards. In some instances, the base station 102 may include multiple radios, which may enable the base station 102 to communicate according to multiple wireless communication technologies. For example, as one possibility, the base station 102 may include an LTE radio for performing communication according to LTE as well as a 5G NR radio for performing communication according to 5G NR. In such a case, the base station 102 may be capable of operating as both an LTE base station and a 5G NR base station. As another possibility, the base station 102 may include a multi-mode radio which is capable of performing communications 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.).Client Ref. No. P71093WO1

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

[0066] In addition, as described herein, processor(s) 204 may be comprised of one or more processing elements. In other words, one or more processing elements may be included in processor(s) 204. Thus, processor(s) 204 may include one or more integrated circuits (ICs) that are configured to perform the functions of processor(s) 204. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processor(s) 204.

[0067] Further, as described herein, radio 230 may be comprised of one or more processing elements. In other words, one or more processing elements may be included in radio 230. Thus, radio 230 may include one or more integrated circuits (ICs) that are configured to perform the functions of radio 230. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of radio 230.

[0068] In some embodiments, base station 102, and / or processors 204 thereof, can be capable of and configured to transmit (or encode for transmission) to the UE 106: an uplink (UL) timing advance (TA) command (TA_CC_B); an uplink (LIL) timing reference group (TRG); and to receive (or decode) from the UE 106 UL transmissions on a first component carrier (CC A).Client Ref. No. P71093WO1FIG. 3: Block Diagram of a Server

[0069] FIG. 3 illustrates an example block diagram of a server 104, according to some embodiments. It is noted that the server of FIG. 3 is merely one example of a possible server. As shown, the server 104 may include processor(s) 344 which may execute program instructions for the server 104. The processor(s) 344 may also be coupled to memory management unit (MMU) 374, which may be configured to receive addresses from the processor(s) 344 and translate those addresses to locations in memory (e.g., memory 364 and read only memory (ROM) 354) or to other circuits or devices.

[0070] The server 104 may be configured to provide a plurality of devices, such as base station 102, and UEs 106 access to network functions, e.g., as further described herein.

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

[0072] As described herein, the server 104 may include hardware and software components for implementing or supporting implementation of features described herein. The processor 344 of the server 104 may be configured to implement or support implementation of part or all of the methods described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively, the processor 344 may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit), or a combination thereof. Alternatively (or in addition) the processor 344 of the server 104, in conjunction with one or more of the other components 354, 364, and / or 374 may be configured to implement or support implementation of part or all of the features described herein.

[0073] In addition, as described herein, processor(s) 344 may be comprised ofClient Ref. No. P71093WO1one or more processing elements. In other words, one or more processing elements may be included in processor(s) 344. Thus, processor(s) 344 may include one or more integrated circuits (ICs) that are configured to perform the functions of processor(s) 344. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processor(s) 344.FIG. 4: Block Diagram of a User Equipment (UE)

[0074] FIG. 4 illustrates an example simplified block diagram of a communication device 405, according to some embodiments. It is noted that the block diagram of the communication device of FIG. 4 is only one example of a possible communication device. According to embodiments, communication device 405 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, an unmanned aerial vehicle (UAV), a UAV controller (UAC) and / or a combination of devices, among other devices. As shown, the communication device 405 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 chip (SOC), which may include portions for various purposes. Alternatively, this set of components 400 may be implemented as separate components or groups of components for the various purposes. The set of components 400 may be coupled (e.g., communicatively; directly or indirectly) to various other circuits of the communication device 405.

[0075] For example, the communication device 405 may include various types of memory (e.g., including NAND flash memory 410), an input / output interface such as connector l / F 420 (e.g., for connecting to a computer system; dock; charging station; input devices, such as a microphone, camera, keyboard; output devices, such as speakers; etc.), the display 460, which may be integrated with or external to the communication device 405, and cellular communication circuitry 430 suchClient Ref. No. P71093WO1as for 5G NR, LTE, GSM, etc., and short to medium range wireless communication circuitry 429 (e.g., Bluetooth™ and WLAN circuitry). In some embodiments, communication device 405 may include wired communication circuitry (not shown), such as a network interface card, e.g., for Ethernet.

[0076] The cellular communication circuitry 430 may couple (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas 435 and 436 as shown. The short to medium range wireless communication circuitry 429 may also couple (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas 437 and 438 as shown. Alternatively, the short to medium range wireless communication circuitry 429 may couple (e.g., communicatively; directly or indirectly) to the antennas 435 and 436 in addition to, or instead of, coupling (e.g., communicatively; directly or indirectly) to the antennas 437 and 438. The short to medium range wireless communication circuitry 429 and / or cellular communication circuitry 430 may include multiple receive chains and / or multiple transmit chains for receiving and / or transmitting multiple spatial streams, such as in a multiple-input multiple output (MIMO) configuration.

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

[0078] The communication device 405 may also include and / or be configured for use with one or more user interface elements. The user interface elements may include any of various elements, such as display 460 (which may be a touchscreen display), a keyboard (which may be a discrete keyboard or may be implementedClient Ref. No. P71093WO1as part of a touchscreen display), a mouse, a microphone and / or speakers, one or more cameras, one or more buttons, and / or any of various other elements capable of providing information to a user and / or receiving or interpreting user input.

[0079] The communication device 405 may further include one or more smart cards 445 that include SIM (Subscriber Identity Module) functionality, such as one or more UICC(s) (Universal Integrated Circuit Card(s)) cards 445. Note that the term “SIM” or “SIM entity” is intended to include any of various types of SIM implementations or SIM functionality, such as the one or more UICC(s) cards 445, one or more eUlCCs, one or more eSIMs, either removable or embedded, etc. In some embodiments, the UE 106 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 may be embedded, e.g., may be soldered onto a circuit board in the UE 106, or each SIM may be implemented as a removable smart card. Thus, the SIM(s) may be one or more removable smart cards (such as UICC cards, which are sometimes referred to as “SIM cards”), and / or the SIMs may be one or more embedded cards (such as embedded UICCs (eUlCCs), which are sometimes referred to as “eSIMs” or “eSIM cards”). In some embodiments (such as when the SIM(s) include an eUlCC), one or more of the SIM(s) may implement embedded SIM (eSIM) functionality; in such an embodiment, a single one of the SIM(s) may execute multiple SIM applications. Each of the SIMs may include components such as a processor and / or a memory; instructions for performing SIM / eSIM functionality may be stored in the memory and executed by the processor. In some embodiments, the UE 106 may include a combination of removable smart cards and fixed / non-removable smart cards (such as one or more eUlCC cards that implement eSIM functionality), as desired. For example, the UE 106 may comprise two embedded SIMs, two removable SIMs, or a combination of one embedded SIMs and one removable SIMs. Various other SIM configurations are also contemplated.

[0080] As noted above, in some embodiments, the UE 106 may include two or more SIMs. The inclusion of two or more SIMs in the UE 106 may allow the UE 106 to support two different telephone numbers and may allow the UE 106 toClient Ref. No. P71093WO1communicate on corresponding two or more respective networks. For example, a first SIM may support a first RAT such as LTE, and a second SIM support a second RAT such as 5G NR. Other implementations and RATs are of course possible. In some embodiments, when the UE 106 comprises two SIMs, the UE 106 may support Dual SIM Dual Active (DSDA) functionality. The DSDA functionality may allow the UE 106 to be simultaneously connected to two networks (and use two different RATs) at the same time, or to simultaneously maintain two connections supported by two different SIMs using the same or different RATs on the same or different networks. The DSDA functionality may also allow the UE 106 to simultaneously receive voice calls or data traffic on either phone number. In certain embodiments the voice call may be a packet switched communication. In other words, the voice call may be received using voice over LTE (VoLTE) technology and / or voice over NR (VoNR) technology. In some embodiments, the UE 106 may support Dual SIM Dual Standby (DSDS) functionality. The DSDS functionality may allow either of the two SIMs in the UE 106 to be on standby waiting for a voice call and / or data connection. In DSDS, when a call / data is established on one SIM, the other SIM is no longer active. In some embodiments, DSDx functionality (either DSDA or DSDS functionality) may be implemented with a single SIM (e.g., a eUlCC) that executes multiple SIM applications for different carriers and / or RATs.

[0081] As shown, the SOC 400 may include processor(s) 402, which may execute program instructions for the communication device 405 and display circuitry 404, which may perform graphics processing and provide display signals to the display 460. The processor(s) 402 may also be coupled to memory management unit (MMU) 440, which may be configured to receive addresses from the processor(s) 402 and translate those addresses to locations in memory (e.g., memory 406, read only memory (ROM) 450, NAND flash memory 410) and / or to other circuits or devices, such as the display circuitry 404, short to medium range wireless communication circuitry 429, cellular communication circuitry 430, connector l / F 420, and / or display 460. The MMU 440 may be configured to perform memory protection and page table translation or set up. In some embodiments, the MMU 440 may be included as a portion of the processor(s) 402.Client Ref. No. P71093WO1

[0082] As described herein, the communication device 405 may include hardware and software components for implementing the above features for a communication device 405 to communicate a scheduling profile for power savings to a network. The processor 402 of the communication device 405 may be configured to implement part or all of the features described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), processor 402 may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit). Alternatively (or in addition) the processor 402 of the communication device 405, in conjunction with one or more of the other components 400, 404, 406, 410, 420, 429, 430, 440, 445, 450, 460 may be configured to implement part or all of the features described herein.

[0083] In addition, as described herein, processor 402 may include one or more processing elements. Thus, processor 402 may include one or more integrated circuits (ICs) that are configured to perform the functions of processor 402. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processor(s) 402.

[0084] Further, as described herein, cellular communication circuitry 430 and short to medium range wireless communication circuitry 429 may each include one or more processing elements. In other words, one or more processing elements may be included in cellular communication circuitry 430 and, similarly, one or more processing elements may be included in short to medium range wireless communication circuitry 429. Thus, cellular communication circuitry 430 may include one or more integrated circuits (ICs) that are configured to perform the functions of cellular communication circuitry 430. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of cellular communication circuitry 430. Similarly, the short to medium range wireless communication circuitry 429 may include one or more ICs that are configured to perform the functions of short to medium range wireless communication circuitry 429. In addition, each integrated circuit may includeClient Ref. No. P71093WO1circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of short to medium range wireless communication circuitry 429.FIG. 5: Block Diagram of Cellular Communication Circuitry

[0085] FIG. 5 illustrates an example simplified block diagram of cellular communication circuitry, according to some embodiments. It is noted that the block diagram of the cellular communication circuitry of FIG. 5 is only one example of a possible cellular communication circuit. According to embodiments, cellular communication circuitry 530, which may be cellular communication circuitry 430, may be included in a communication device, such as communication device 405 described above. As noted above, communication device 405 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 and / or a combination of devices, among other devices.

[0086] The cellular communication circuitry 530 may couple (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas 435a-b and 436 as shown (in FIG. 4). In some embodiments, cellular communication circuitry 530 may include dedicated receive chains (including and / or coupled to, e.g., communicatively; directly or indirectly, dedicated processors and / or radios) for multiple RATs (e.g., a first receive chain for LTE and a second receive chain for 5G NR). For example, as shown in FIG. 5, cellular communication circuitry 530 may include a modem 510 and a modem 520. Modem 510 may be configured for communications according to a first RAT, e.g., such as LTE or LTE-A, and modem 520 may be configured for communications according to a second RAT, e.g., such as 5G NR.

[0087] As shown, modem 510 may include one or more processors 512 and a memory 516 in communication with processors 512. Modem 510 may be in communication with a radio frequency (RF) front end 535. RF front end 535 may include circuitry for transmitting and receiving radio signals. For example, RF frontClient Ref. No. P71093WO1end 535 may include receive circuitry (RX) 532 and transmit circuitry (TX) 534. In some embodiments, receive circuitry 532 may be in communication with downlink (DL) front end 550, which may include circuitry for receiving radio signals via antenna 335a.

[0088] Similarly, modem 520 may include one or more processors 522 and a memory 526 in communication with processors 522. Modem 520 may be in communication with an 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 receive circuitry 542 and transmit circuitry 544. In some embodiments, receive circuitry 542 may be in communication with DL front end 560, which may include circuitry for receiving radio signals via antenna 335b.

[0089] In some embodiments, a switch 570 may couple transmit circuitry 534 to uplink (UL) front end 572. In addition, switch 570 may couple transmit circuitry 544 to UL front end 572. UL front end 572 may include circuitry for transmitting radio signals via antenna 336. Thus, when cellular communication circuitry 530 receives instructions to transmit according to the first RAT (e.g., as supported via modem 510), switch 570 may be switched to a first state that allows modem 510 to transmit signals according to the first RAT (e.g., via a transmit chain that includes transmit circuitry 534 and UL front end 572). Similarly, when cellular communication circuitry 530 receives instructions to transmit according to the second RAT (e.g., as supported via modem 520), switch 570 may be switched to a second state that allows modem 520 to transmit signals according to the second RAT (e.g., via a transmit chain that includes transmit circuitry 544 and UL front end 572).

[0090] As described herein, the modem 510 may include hardware and software components for implementing the above features or for time division multiplexing UL data for NSA NR operations, as well as the various other techniques described herein. The processors 512 may be configured to implement part or all of the features described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), processor 512 may be configured as a programmable hardware element, such as an FPGA (Field Programmable GateClient Ref. No. P71093WO1Array), or as an ASIC (Application Specific Integrated Circuit). Alternatively (or in addition) the processor 512, in conjunction with one or more of the other components 530, 532, 534, 535, 550, 570, 572, 335a, 335b, and 336 may be configured to implement part or all of the features described herein.

[0091] In addition, as described herein, processors 512 may include one or more processing elements. Thus, processors 512 may include one or more integrated circuits (ICs) that are configured to perform the functions of processors 512. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processors 512.

[0092] The processors 522 may be configured to implement part or all of the features described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), processor 522 may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit). Alternatively (or in addition) the processor 522, in conjunction with one or more of the other components 540, 542, 544, 550, 570, 572, 335a, 335b, and 336 may be configured to implement part or all of the features described herein.

[0093] In addition, as described herein, processors 522 may include one or more processing elements. Thus, processors 522 may include one or more integrated circuits (ICs) that are configured to perform the functions of processors 522. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processors 522.FIG. 6: Block Diagram of a Baseband Processor Architecture for a LIE

[0094] FIG. 6 illustrates example components of a device 600 in accordance with some embodiments. It is noted that the device of FIG. 6 is merely one example of a possible system, and that features of this disclosure may be implemented in any of various UEs, as desired.

[0095] In some embodiments, the device 600 may include application circuitryClient Ref. No. P71093WO1602, baseband circuitry 604, Radio Frequency (RF) circuitry 606, front-end module (FEM) circuitry 608, one or more antennas 610, and power management circuitry (PMC) 612 coupled together at least as shown. The components of the illustrated device 600 may be included in a UE 106 or a BS 102A in a RAN node. In some embodiments, the device 600 may include less elements (e.g., a RAN node may not utilize application circuitry 602, and instead include a processor / controller to process IP data received from an EPC). In some embodiments, the device 600 may include additional elements such as, for example, memory / storage, display, camera, sensor, or input / output (I / O) interface. In other embodiments, the components described below may be included in more than one device (e.g., said circuitries may be separately included in more than one device for Cloud-RAN (C-RAN) implementations).

[0096] The application circuitry 602 may include one or more application processors. For example, the application circuitry 602 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor(s) may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.). The processors may be coupled with or may include memory / storage and may be configured to execute instructions stored in the memory / storage to enable various applications or operating systems to run on the device 600. In some embodiments, processors of application circuitry 602 may process IP data packets received from an EPC.

[0097] The baseband circuitry 604 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 604 may include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry 606 and to generate baseband signals for a transmit signal path of the RF circuitry 606. Baseband processing circuity 604 may interface with the application circuitry 602 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 606. For example, in some embodiments, the baseband circuitry 604 may include a third generation (3G) baseband processorClient Ref. No. P71093WO1604A, a fourth generation (4G) baseband processor 604B, a fifth generation (5G) baseband processor 604C, or other baseband processor(s) 604D for other existing generations, generations in development or to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.). The baseband circuitry 604 (e.g., one or more of baseband processors 604A-D) may handle various radio control functions that enable communication with one or more radio networks via the RF circuitry 606. In other embodiments, some or all of the functionality of baseband processors 604A-D may be included in modules stored in the memory 604G and executed via a Central Processing Unit (CPU) 604E. The radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. In some embodiments, modulation / demodulation circuitry of the baseband circuitry 604 may include Fast-Fourier Transform (FFT), precoding, or constellation mapping / demapping functionality. In some embodiments, encoding / decoding circuitry of the baseband circuitry 604 may include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder / decoder functionality. Embodiments of modulation / demodulation and encoder / decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments.

[0098] In some embodiments, the baseband circuitry 604 may include one or more audio digital signal processor(s) (DSP) 604F. The audio DSP(s) 604F may be include elements for compression / decompression and echo cancellation and may include other suitable processing elements in other embodiments. Components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments. In some embodiments, some or all of the constituent components of the baseband circuitry 604 and the application circuitry 602 may be implemented together such as, for example, on a system on a chip (SOC).

[0099] In some embodiments, the baseband circuitry 604 may provide for communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry 604 may support communication with an evolved universal terrestrial radio access network (EUTRAN) or other wirelessClient Ref. No. P71093WO1metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN). Embodiments in which the baseband circuitry 604 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

[0100] RF circuitry 606 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry 606 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. RF circuitry 606 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 608 and provide baseband signals to the baseband circuitry 604. RF circuitry 606 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 604 and provide RF output signals to the FEM circuitry 608 for transmission.

[0101] In some embodiments, the receive signal path of the RF circuitry 606 may include mixer circuitry 606a, amplifier circuitry 606b and filter circuitry 606c. In some embodiments, the transmit signal path of the RF circuitry 606 may include filter circuitry 606c and mixer circuitry 606a. RF circuitry 606 may also include synthesizer circuitry 606d for synthesizing a frequency for use by the mixer circuitry 606a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuitry 606a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 608 based on the synthesized frequency provided by synthesizer circuitry 606d. The amplifier circuitry 606b may be configured to amplify the down-converted signals and the filter circuitry 606c may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals. Output baseband signals may be provided to the baseband circuitry 604 for further processing. In some embodiments, the output baseband signals may be zero-frequency baseband signals, although this is not a necessity. In some embodiments, mixer circuitry 606a of the receive signal path may comprise passive mixers, although the scope of the embodiments is notClient Ref. No. P71093WO1limited in this respect.

[0102] In some embodiments, the mixer circuitry 606a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 606d to generate RF output signals for the FEM circuitry 608. The baseband signals may be provided by the baseband circuitry 604 and may be filtered by filter circuitry 606c.

[0103] In some embodiments, the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively. In some embodiments, the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a may be arranged for direct downconversion and direct upconversion, respectively. In some embodiments, the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a of the transmit signal path may be configured for super-heterodyne operation.

[0104] In some embodiments, the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternate embodiments, the output baseband signals and the input baseband signals may be digital baseband signals. In these alternate embodiments, the RF circuitry 606 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 604 may include a digital baseband interface to communicate with the RF circuitry 606.

[0105] In some dual-mode embodiments, a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.

[0106] In some embodiments, the synthesizer circuitry 606d may be a fractional-N synthesizer or a fractional N / N+1 synthesizer, although the scope ofClient Ref. No. P71093WO1the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable. For example, synthesizer circuitry 606d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.

[0107] The synthesizer circuitry 606d may be configured to synthesize an output frequency for use by the mixer circuitry 606a of the RF circuitry 606 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 606d may be a fractional N / N+1 synthesizer.

[0108] In some embodiments, frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a necessity. Divider control input may be provided by either the baseband circuitry 604 or the application circuitry 602 depending on the desired output frequency. In some embodiments, a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the application circuitry 602.

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

[0110] In some embodiments, synthesizer circuitry 606d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction withClient Ref. No. P71093WO1quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other. In some embodiments, the output frequency may be a LO frequency (fLO). In some embodiments, the RF circuitry 606 may include an IQ / polar converter.

[0111] FEM circuitry 608 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 610, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 606 for further processing. FEM circuitry 608 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 606 for transmission by one or more of the one or more antennas 610. In various embodiments, the amplification through the transmit or receive signal paths may be done solely in the RF circuitry 606, solely in the FEM 608, or in both the RF circuitry 606 and the FEM 608.

[0112] In some embodiments, the FEM circuitry 608 may include a TX / RX switch to switch between transmit mode and receive mode operation. The FEM circuitry may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry may include an LNA to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 606). The transmit signal path of the FEM circuitry 608 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 606), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 610).

[0113] In some embodiments, the PMC 612 may manage power provided to the baseband circuitry 604. In particular, the PMC 612 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion. The PMC 612 may often be included when the device 600 is capable of being powered by a battery, for example, when the device is included in a UE. The PMC 612 may increase the power conversion efficiency while providing desirable implementation size and heat dissipation characteristics.Client Ref. No. P71093WO1

[0114] While FIG. 6 shows the PMC 612 coupled only with the baseband circuitry 604, in other embodiments the PMC 612 may be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, application circuitry 602, RF circuitry 606, or FEM 608.

[0115] In some embodiments, the PMC 612 may control, or otherwise be part of, various power saving mechanisms of the device 600. For example, if the device 600 is in a radio resource control_Connected (RRC_Connected) state, where it is still connected to the RAN node as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the device 600 may power down for brief intervals of time and thus save power.

[0116] If there is no data traffic activity for an extended period of time, then the device 600 may transition off to an RRCJdle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. The device 600 goes into a very low power state and it performs paging where, again, it periodically wakes up to listen to the network and then powers down at least portions of the device again. The device 600 may not receive data in this state. In order to receive data, it will transition back to an RRC Connected state.

[0117] An additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device is totally unreachable to the network and may power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable.

[0118] In some embodiments, the UE 106 and / or the baseband circuitry 604 of the one or more processors thereof can send (encode for transmission): UL transmissions on the first component carrier (CC A) using UL timing information based on the TA command (T _CC_B) from the second component carrier; UL transmissions on the two or more UL CCs using UL timing information based onClient Ref. No. P71093WO1the TA; a first message (Message 1) comprising a Physical Random Access Channel (PRACH) preamble on a first component carrier (CC A) using UL timing based on the DL timing for the second component carrier (CC B); UL transmissions on the first component carrier (CC A) using UL timing based on the DL timing for the second component carrier (CC B); and a third message (Message 3) comprising a Physical Uplink Shared Channel (PUSCH) via the BS2 on the first component carrier (CC A) with timing information based on a timing advance (TA) based on DL timing of the second component carrier (CC B) or via the BS1 on the second component carrier (CC B).

[0119] In addition, the UE 106 and / or the baseband circuitry 604 of the one or more processors thereof can receive (decode): an uplink (UL) timing advance (TA) command (TA_CC_B) to enable the UE to obtain UL timing information for two or more component carriers (CCs) aggregated together in a carrier aggregation (CA) configuration; an uplink (UL) timing reference group (TRG) for two or more colocated UL component carriers (CCs) in a carrier aggregation (CA) configuration; a timing advance (TA) command on the corresponding DL CC; a downlink (DL) transmission on a second component carrier (CC B) comprising a DL timing for the second component carrier (CC B), the second component carrier (CC B) comprising both a DL CC and an uplink (UL) CC; a second message (Message 2) comprising a Random Access Channel (RACH) response on the second component carrier (CC B); and a fourth message (Message 4) comprising a Physical Downlink Control Channel (PDCCH) on the second component carrier (CC B).FIG. 7: Block Diagram of an Interface of Baseband Circuitry

[0120] FIG. 7 illustrates example interfaces of baseband circuitry in accordance with some embodiments. It is noted that the baseband circuitry of FIG. 7 is merely one example of a possible circuitry, and that features of this disclosure may be implemented in any of various systems, as desired.

[0121] As discussed above, the baseband circuitry 604 of FIG. 6 may compriseClient Ref. No. P71093WO1processors 604A-604E and a memory 604G utilized by said processors. Each of the processors 604A-604E may include a memory interface, 704A-704E, respectively, to send / receive data to / from the memory 604G.

[0122] The baseband circuitry 604 may further include one or more interfaces to communicatively couple to other circuitries / devices, such as a memory interface 712 (e.g., an interface to send / receive data to / from memory external to the baseband circuitry 604), an application circuitry interface 714 (e.g., an interface to send / receive data to / from the application circuitry 602 of FIG. 6), an RF circuitry interface 716 (e.g., an interface to send / receive data to / from RF circuitry 606 of FIG. 6), a wireless hardware connectivity interface 718 (e.g., an interface to send / receive data to / from Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components), and a power management interface 720 (e.g., an interface to send / receive power or control signals to / from the PMC 612.FIG. 8: Core Network

[0123] FIG. 8 illustrates an example architecture of a system 800 including a core network (CN) 820 in accordance with various embodiments. The CN 820 may be a core network for a 5G System (which may be referred to as a 5GC). The system 800 is shown to include a UE 801 , which may be the same or similar to the UEs 106A, 106B, or 106N discussed previously; a (R)AN 810, which may be the same or similar to the BSs 102A or 102N discussed previously; and a data network (DN) 803, which may be, for example, operator services, Internet access, or 3rd party services; and a CN 820. The CN 820 may include a number of network functions including an Authentication Server Function (AUSF) 822; an Access and Mobility Management Function (AMF) 821 ; a Session Management Function (SMF) 824; a Network Exposure Function (NEF) 823; a Policy Control Function (PCF) 826; a Network Repository Function (NRF) 825; a Unified Data Management (UDM) 827; an Application Function (AF) 828; a User Plane Function (UPF) 802; and a Network Slice Selection Function (NSSF) 829. These networkClient Ref. No. P71093WO1functions may be implemented, in some cases, as virtualized software-based functions / services.

[0124] The UPF 802 may act as an anchor point for intra-RAT and inter-RAT mobility, an external packet data unit (PDU) session point of interconnect to DN 803, and a branching point to support mufti-homed PDU session. A PDU session is a logical connection between the UE and the DN. The UPF 802 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane part of policy rules, lawfully intercept packets (user plane (UP) collection), perform traffic usage reporting, perform quality of service (QoS) handling for a user plane (e.g., packet filtering, gating, UL / DL rate enforcement), perform Uplink Traffic verification (e.g., Service Data Flows (SDF) to QoS flow mapping), transport level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. UPF 802 may include an uplink classifier to support routing traffic flows to a data network, The DN 803 may represent various network operator services, Internet access, or third-party services. DN 803 may include, or be similar to, server 104 discussed previously. The UPF 802 may interact with the SMF 824 via an N4 reference point between the SMF 824 and the UPF 802.

[0125] The AUSF 822 may store data for authentication of UE 801 and handle authentication-related functionality, The AUSF 822 may facilitate a common authentication framework for various access types. The AUSF 822 may communicate with the AMF 821 via an N12 reference point between the AMF 821 and the AUSF 822; and may communicate with the UDM 827 via an N13 reference point between the UDM 827 and the AUSF 822. Additionally, the AUSF 822 may exhibit an Nausf service-based interface.

[0126] The AMF 821 may be responsible for registration management (e.g., for registering UE 801 , etc.), connection management, reachability management, mobility management, and lawful interception of AMF-related events, and access authentication and authorization. The AMF 821 may be a termination point for the an N11 reference point between the AMF 821 and the SMF 824. The AMF 821 may provide transport for SM messages between the UE 801 and the SMF 824,Client Ref. No. P71093WO1and act as a transparent proxy for routing SM messages. AMF 821 may also provide transport for Short Message Service (SMS) messages between UE 801 and an SMSF (not shown by FIG. 8). AMF 821 may act as a security anchor function (SEAF), which may include interaction with the ALISF 822 and the UE 801 , receipt of an intermediate key that was established as a result of the UE 801 authentication process. Where Universal Subscriber Identity Module (USIM) based authentication is used, the AMF 821 may retrieve the security material from the AUSF 822. AMF 821 may also include a Security Context Management (SCM) function, which receives a key from the SEAF that it uses to derive access-network specific keys. Furthermore, AMF 821 may be a termination point of a RAN control plane (CP) interface, which may include or be an N2 reference point between the (R)AN 810 and the AMF 821 ; and the AMF 821 may be a termination point of NAS (Nl) signaling, and perform NAS ciphering and integrity protection.

[0127] AMF 821 may also support NAS signaling with a UE 801 over a non-3GPP Inter-Working Function (N3IWF) interface. The N3IWF may be used to provide access to untrusted entities. N3IWF may be a termination point for the N2 interface between the (R)AN 810 and the AMF 821 for the control plane, and may be a termination point for the N3 reference point between the (R)AN 810 and the UPF 802 for the user plane. As such, the AMF 821 may handle N2 signaling from the SMF 824 and the AMF 821 for PDU sessions and encapsulate / de- encapsulate packets for IPSec and N3 tunneling, mark N3 user-plane packets in the uplink, and enforce QoS corresponding to N3 packet marking while considering QoS requirements associated with such marking received over N2. N3IWF may also relay uplink and downlink control plane non-access stratum (NAS) signaling between the UE 801 and AMF 821 via an N1 reference point between the UE 801 and the AMF 821, and relay uplink and downlink user-plane packets between the UE 801 and UPF 802. The N3IWF also provides mechanisms for internet protocol security (IPsec) tunnel establishment with the UE 801. The AMF 821 may exhibit an Namf service based interface, and may be a termination point for an N14 reference point between two AMFs 821 and an N17 reference point between the AMF 821 and a 5G Equipment Identity Register (5G-EIR) (not shown by FIG. 8).Client Ref. No. P71093WO1

[0128] The UE 801 may need to register with the AMF 821 in order to receive network services. Registration Management (RM) is used to register or deregister the UE 801 with the network (e.g., AMF 821), and establish a UE context in the network (e.g., AMF 821 ). The UE 801 may operate in an RM-REGISTERED state or an RM-DEREGISTERED state. In the RM-DEREGISTERED state, the UE 801 is not registered with the network, and the UE context in AMF 821 holds no valid location or routing information for the UE 801 so the UE 801 is not reachable by the AMF 821. In the RM REGISTERED state, the UE 801 is registered with the network, and the UE context in AMF 821 may hold a valid location or routing information for the UE 801 so the UE 801 is reachable by the AMF 821 . In the RM-REGISTERED state, the UE 801 may perform mobility registration update procedures, perform periodic registration update procedures triggered by expiration of the periodic update timer (e.g., to notify the network that the UE 801 is still active), and perform a Registration Update procedure to update UE capability information or to re-negotiate protocol parameters with the network, among others.

[0129] The AMF 821 may store one or more RM contexts for the UE 801 , where each RM context is associated with a specific access to the network. The RM context may be a data structure, database object, etc. that indicates or stores, inter glia, a registration state per access type and the periodic update timer. The AMF 821 may also store a 5GC mobility management (MM) context that may be the same or similar to the evolved packet services (EPS) Mobility Management (E)MM context discussed previously. In various embodiments, the AMF 821 may store a GE mode B Restriction parameter of the UE 801 in an associated MM context or registration management (RM) context. The AMF 821 may also derive the value, when needed, from the UE's usage setting parameter already stored in the UE context (and / or MM / RM context).

[0130] Connection Management (CM) may be used to establish and release a signaling connection between the UE 801 and the AMF 821 over the N1 interface. The signaling connection is used to enable NAS signaling exchange between the UE 801 and the CN 820, and comprises both the signaling connection between the UE and the AN (e.g., RRC connection or UE-N3IWF connection for non-3GPPClient Ref. No. P71093WO1access) and the N2 connection for the UE 801 between the AN (e.g., AN 810) and the AMF 821 . The UE 801 may operate in one of two CM states, CM-IDLE mode or CM-CONNECTED mode. When the UE 801 is operating in the CM-IDLE state / mode, the UE 801 may have no NAS signaling connection established with the AMF 821 over the N1 interface, and there may be (R)AN 810 signaling connection (e.g., N2 and / or N3 connections) for the UE 801 . When the UE 801 is operating in the CM-CONNECTED state / mode, the UE 801 may have an established NAS signaling connection with the AMF 821 over the Nl interface, and there may be a (R)AN 810 signaling connection (e.g., N2 and / or N3 connections) for the UE 801. Establishment of an N2 connection between the (R)AN 810 and the AMF 821 may cause the UE 801 to transition from CM-IDLE mode to CM-CONNECTED mode, and the UE 801 may transition from the CM-CONNECTED mode to the CM-IDLE mode when N2 signaling between the (R)AN 810 and the AMF 821 is released.

[0131] The SMF 824 may be responsible for session management (SM) session establishment, modify and release, including tunnel maintain between UPF and AN node); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF to route traffic to proper destination; termination of interfaces toward policy control functions; controlling part of policy enforcement and QoS; lawful intercept (for SM events and interface to LI system); termination of SM parts of NAS messages; downlink data notification; initiating AN specific SM information, sent via AMF over N2 to AN; and determining SSC mode of a session. SM may refer to management of a PDU session, and a PDU session or "session" may refer to a PDU connectivity service that provides or enables the exchange of PDUs between a UE 801 and a data network (DN) 803 identified by a Data Network Name (DNN). PDU sessions may be established upon UE 801 request, modified upon UE 801 and CN 820 request, and released upon UE 801 and CN 820 request using NAS SM signaling exchanged over the N1 reference point between the UE 801 and the SMF 824. Upon request from an application server, the CN 820 may trigger a specific application in the UE 801 . In response to receipt of the trigger message,Client Ref. No. P71093WO1the UE 801 may pass the trigger message (or relevant parts / information of the trigger message) to one or more identified applications in the UE 801 . The identified application(s) in the UE 801 may establish a PDU session to a specific data network name (DNN). The SMF 824 may check whether the UE 801 requests are compliant with user subscription information associated with the UE 801. In this regard, the SMF 824 may retrieve and / or request to receive update notifications on SMF 824 level subscription data from the UDM 827.

[0132] The SMF 824 may include the following roaming functionality: handling local enforcement to apply QoS SLAB virtual Public Land Mobile Network (VPLMN); charging data collection and charging interface (VPLMN); lawful intercept (in VPLMN for SM events and interface to LI system); and support for interaction with external DN for transport of signaling for PDU session authorization / authentication by external DN. An N16 reference point between two SMFs 824 may be included in the system 800, which may be between another SMF 824 in a visited network and the SMF 824 in the home network in roaming scenarios. Additionally, the SMF 824 may exhibit the Nsmf service-based interface.

[0133] The NEF 823 may provide means for securely exposing the services and capabilities provided by 3GPP network functions for third party, internal exposure / re-exposure, Application Functions (e.g., AF 828), edge computing or fog computing systems, etc. In such embodiments, the NEF 823 may authenticate, authorize, and / or throttle the AFS. NEF 823 may also translate information exchanged with the AF 828 and information exchanged with internal network functions. For example, the NEF 823 may translate between an AF-Service-Identifier and an internal SCC information. NEF 823 may also receive information from other network functions (NFs) based on exposed capabilities of other network functions. This information may be stored at the NEF 823 as structured data, or at a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF 823 to other NFs and AFs, and / or used for other purposes such as analytics. Additionally, the NEF 823 may exhibit an Nnef servicebased interface.

[0134] The NRF 825 may support service discovery functions, receive NFClient Ref. No. P71093WO1discovery requests from NF instances, and provide the information of the discovered NF instances to the NF instances. NRF 825 also maintains information of available NF instances and their supported services. As used herein, the terms "instantiate," "instantiation," and the like may refer to the creation of an instance, and an "instance" may refer to a concrete occurrence of an object, which may occur, for example, during execution of program code. Additionally, the NRF 825 may exhibit the Nnrf service-based interface.

[0135] The PCF 826 may provide policy rules to control plane function(s) to enforce them, and may also support unified policy framework to govern network behavior, The PCF 826 may also implement a front end (FE) to access subscription information relevant for policy decisions in a UDR of the UDM 827. The PCF 826 may communicate with the AMF 821 via an N15 reference point between the PCF 826 and the AMF 821 , which may include a PCF 826 in a visited network and the AMF 821 in case of roaming scenarios. The PCF 826 may communicate with the AF 828 via an NS reference point between the PCF 826 and the AF 828; and with the SMF 824 via an N7 reference point between the PCF 826 and the SMF 824, The system 800 and / or CN 820 may also include an N24 reference point between the PCF 826 (in the home network) and a PCF 826 in a visited network, Additionally, the PCF 826 may exhibit an Npcf service-based interface.

[0136] The UDM 827 may handle subscription-related information to support the network entities' handling of communication sessions, and may store subscription data of UE 801 . For example, subscription data may be communicated between the UDM 827 and the AMF 821 via an NS reference point between the UDM 827 and the AMF. The UDM 827 may include two parts, an application FE and a UDR (the FE and UDR are not shown by FIG. 8). The UDR may store subscription data and policy data for the UDM 827 and the PCF 826, and / or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 801) for the NEF 823. The Nadr service-based interface may be exhibited by the UDR to allow the UDM 827, PCF 826, and NEF 823 to access a particular set of the stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notification ofClient Ref. No. P71093WO1relevant data changes in the UDR. The UDM may include a LIDM-FE, which is in charge of processing credentials, location management, subscription management and so on. Several different front ends may serve the same user in different transactions. The LIDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification handling, access authorization, registration / mobility management, and subscription management. The UDR may interact with the SMF 824 via an NIO reference point between the UDM 827 and the SMF 824. UDM 827 may also support SMS management, wherein an SMS-FE implements the similar application logic as discussed previously. Additionally, the UDM 827 may exhibit the Nudm servicebased interface.

[0137] The AF 828 may provide application influence on traffic routing, provide access to the NCE, and interact with the policy framework for policy control. The NCE may be a mechanism that allows the CN 820 and AF 828 to provide information to each other via NEF 823, which may be used for edge computing implementations. In such implementations, the network operator and third-party services may be hosted close to the UE 801 access point of attachment to achieve an efficient service delivery through the reduced end-to-end latency and load on the transport network. For edge computing implementations, the 5GC may select a UPF 802 close to the UE 801 and execute traffic steering from the UPF 802 to DN 803 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 828. In this way, the AF 828 may influence UPF (re)selection and traffic routing. Based on operator deployment, when AF 828 is considered to be a trusted entity, the network operator may permit AF 828 to interact directly with relevant NFs. Additionally, the AF 828 may exhibit an Naf service-based interface.

[0138] The NSSF 829 may select a set of network slice instances serving the UE 801. The NSSF 829 may also determine allowed Network Slice Selection Assistance Information (NSSAI) and the mapping to the subscribed single NSSAI (S-NSSAI) is, if needed. The NSSF 829 may also determine the AMF set to be used to serve the UE 801, or a list of candidate AMF(s) 821 based on a suitableClient Ref. No. P71093WO1configuration and possibly by querying the NRF 825. The selection of a set of network slice instances for the UE 801 may be triggered by the AMF 821 with which the UE 801 is registered by interacting with the NSSF 829, which may lead to a change of AMF 821 . The NSSF 829 may interact with the AMF 821 via an N22 reference point between AMF 821 and NSSF 829; and may communicate with another NSSF 829 in a visited network via an N31 reference point (not shown by FIG. 8). Additionally, the NSSF 829 may exhibit an Nnssf service-based interface.

[0139] As discussed previously, the CN 820 may include a short message service function (SMSF), which may be responsible for SMS subscription checking and verification, and relaying SM messages to / from the UE 801 to / from other entities, such as an SMS-GMSC / IWMSC / SMS-router. The SMS may also interact with AMF 821 and UDM 827 for a notification procedure that the UE 801 is available for SMS transfer (e.g., set a UE not reachable flag, and notifying UDM 827 when UE 801 is available for SMS).

[0140] The CN 820 may further include a location management function (LMF) 830. The LMF 830 receives measurements and assistance information from the base station 102A and the UE 106 via the AMF 821 over the NLs interface to compute the position of the UE 106.

[0141] The CN 820 may also include other elements that are not shown by FIG.8, such as a Data Storage system / architecture, a 5G-EIR, a Security Edge Protection Proxy (SEPP), and the like. The Data Storage system may include a Structured Data Storage Network Function (SDSF), air Unstructured Data Storage Function (UDSF), and / or the like. Any network function (NF) may store and retrieve unstructured data into / from the UDSF (e.g., UE contexts), via N18 reference point between any NF and the UDSF (not shown by FIG. 8), Individual NFs may share a UDSF for storing their respective unstructured data or individual NFs may each have their own UDSF located at or near the individual NFs. Addition- ally, the UDSF may exhibit an Nudsf service-based interface (not shown by FIG. 8). The 5G-EIR may be an NF that checks the status of permanent equipment identifier (PEI) for determining whether particular equipment / entities are blacklisted from the network; and the SEPP may be a non-transparent proxy that performs topology hiding,Client Ref. No. P71093WO1message filtering, and policing on inter-PLMN control plane interfaces.

[0142] Additionally, there may be many more reference points and / or servicebased interfaces between the NF services in the NFs; however, these interfaces and reference points have been omitted from FIG. 8 for clarity. In one example, the CN 820 may include an Nx interface, which is an inter-CN interface between a mobility management entity (MME) and the AMF 821 in order to enable interworking between CN 820 and a CN in a 4G system. Other example interfaces / reference points may include an N5G-EIR service-based interface exhibited by a 5G-EIR, an N27 reference point between the NRF in the visited network and the NRF in the home network; and an N31 reference point between the NSSF in the visited network and the NSSF in the home network.

[0143] The CN 820 can be or can be part of the NW 100. As described herein, the NW 100 and / or the CN 820 can transmit and receive messages with the LIE 106 via the base station 102.FIGS. 9 and 10: Carrier Aggregation

[0144] FIGS. 9 and 10 illustrate a simplified example carrier aggregation system, according to some embodiments. It is noted that the system 900 and 1000 of FIGS. 9 and 10 is merely one example of a possible system, and that features of this disclosure may be implemented in any of various systems, as desired. Carrier aggregation is used to increase the data rate per user where multiple frequency blocks (called component carriers (CC)) are assigned to the same user. Three types of carrier aggregation can be defined, including: intra-band contiguous, intra-band non-contiguous, and inter-band. In intra-band contiguous carrier aggregation, component carriers are contiguous in the same frequency band. In intra-band non-contiguous carrier aggregation, the component carriers are in the same frequency band but are separated by a gap. In inter-band carrier aggregation, the component carriers are in different frequency bands.

[0145] FIG. 9 illustrates multiple different CA possibilities. In one example, the UE 106 can be in communication with a primary cell (PCell) 902A. The PCell 902AClient Ref. No. P71093WO1can be designated as the active serving cell for the UE 106. The UE 106 can also be in communication, using CA, with a secondary cell (SCell) 902B that can be colocated with the PCell 902A. The component carriers (CC) for the SCell can be intra-band contiguous with the component carriers of the PCell, as shown in 1004 of FIG. 10. FIG. 10 shows the component carriers associated with the SCells of Figure 9. In this case, the SCell can be an intra-band SCell.

[0146] In another embodiment, the cells 902A-N in FIG. 9 can be configured for CA communication with the UE 106 using inter-band. In this example, the UE 106 can be configured for CA to communicate with the PCell 902A and an SCell 902N. The component carriers assigned for the UE to communicate with the SCell 902N can be in a different band (i.e. band B) than the band of the component carriers assigned for the UE to communicate with the PCell 902A (i.e. band A). Since the component carriers of the PCell 902A and the SCell 902N are in different bands, they are, by definition, not contiguous, as shown in 1008 of Figure 10.

[0147] In a 3GPP new radio (NR), e.g. a fifth generation (5G), carrier aggregation (CA) can have a tight coupling between uplink (UL) and downlink (DL). An UL component carrier (CC) can be tied to a DL CC, except for the case of supplemental downlink (SDL). Thus, the number of DL CCs can be equal to or more than the number of UL CCs.

[0148] In some applications, a UE may need more UL bandwidth and less DL bandwidth, such as for video surveillance or artificial intelligence (Al). Some mid / low-end UEs supporting UL transmission (TX) switching may have reduced DL CA capability. By way of example, there can be four radio frequency bands (A, B, C and D), including a low band group (A and B) and a high band group (C and D). In the UL, the UE can transmit uplink signals on bands A or B from the low band group, and C or D from the high band group (i.e., UL switching). In the DL, the UE may not need to support all four bands in CA. In addition, enabling a single cell multiple carrier framework may be beneficial. To support maximum flexibility, it may be useful to pair UL carriers and DL carriers in different bands.

[0149] For example, in low frequency bands, signals can travel farther than highClient Ref. No. P71093WO1frequency bands due to greater signal absorption in the atmosphere at higher frequencies. A UE that is limited to transmitting at a relatively low power level can transmit an UL signal in a low frequency band, such as lower than 1 gigahertz (GHz) much farther than an UL transmission in a high frequency signal, such as frequency bands greater than 2 GHz. However, a base station can transmit at much higher power levels. The base station may still be able to transmit a DL signal in higher frequency bands using a higher transmission power than a UE can achieve. Accordingly, a UE located near a cell edge may receive DL signals in higher frequency bands from the BS, and transmit UL signals in lower frequency bands to the BS.

[0150] In order to provide more flexibility, cells can be configured in which the UL and DL component carriers are not coupled. Decoupling the UL CA and DL CA can achieve: the number of UL CCs can be greater than the number of DL CCs; flexible UL CO and DL CO pairing; and more flexible network scheduling and UE implementation. For an UL CO without the paired / corresponding DL CC, the UE may not be able to obtain the UL timing information. Thus, for UL timing acquisition for co-located CA deployment, the network (NW) may form a reference group. For UL timing acquisition for non-collocated CA, the UE may use a cross CC Random Access Channel (RACH) process. In addition, a blind CA configuration / deconfiguration can be used.FIGS. 11-13: UL Timing Co-Located

[0151] FIG. 11 illustrates an example carrier aggregation system 1100 with a UL only CC (CC A) co-located with another UL CC (CC B) paired with a corresponding DL CC, according to some embodiments. DL timing information for a UE is typically obtained by measurement of the synchronization signal / physical broadcast channel (SSB) received in a DL from the BS. UL transmission timing for each UL CC is typically obtained from the corresponding DL CC in a random access channel (RACH) procedure.

[0152] For the UL only CCs (CC A), i.e. without a corresponding DL CC, the ULClient Ref. No. P71093WO1timing can be obtained using a network timing advance (TA) from another, colocated (Case 1) UL CC (CC B) which has a corresponding DL CC.

[0153] According to some embodiments, the network can send a timing advance (TA) command (TA_cc_B) to the UE for the CC A UL transmission, if the CC B is in sync with the network (as the network has full information on colocation). The UE can use the TA command from the network. The DL reference timing can be indicated to the UE together with the TA command. The DL reference timing can be indicated to the UE when the UL CC A is configured through a Radio Resource Control (RRC) configuration. A DL reference signal from the CC B can be indicated to the UE for deriving the DL reference timing. The UL only CC A can be configured with the UL CC B in the same timing advance group (TAG) and can share the same UL TA.

[0154] In one aspect, an apparatus of a user equipment (UE) 106 can comprise one or more processors 402 and / or 604A-D coupled to a memory 406 and / or 604G. The processors 604A-D can be configured to receive, at the UE 106 from a network (NW) 100 via a base station (BS) 102, an uplink (UL) timing advance (TA) command to enable the UE 106 to obtain UL timing information for two or more component carriers (CCs) aggregated together in a carrier aggregation (CA) configuration. The two or more CCs can comprise a first component carrier (CC A), which is a UL only CC without a corresponding DL CC, co-located with a second component carrier (CC B) which is comprised of both a UL CC and a DL CC, and receives the TA command in the DL CC from the BS. The processors 604A-D can be configured to send, at the UE 106 to the NW 100 via the base station 102, UL transmissions on the first component carrier (CC A) using UL timing information based on the TA command from the second component carrier. The UL transmissions can be only UL transmissions.

[0155] In another aspect, the processors 604A-D can be further configured to receive, at the UE from the NW via the base station, one or more of: an indication comprising a DL reference timing along with the TA command; a Radio Resource Configuration (RRC) for the UL only CC comprising a DL reference timing; or a DL reference signal from the second component carrier (CC B) with an indication forClient Ref. No. P71093WO1the UE to derive a DL reference timing.

[0156] In another aspect, the processors 604A-D can be further configured to receive, at the UE from the NW via the base station, a DL transmission on the DL CC of the second component carrier (CC B) comprising an UL timing reference group (TRG) comprising the UL only CC of the first component carrier (CC A) and the UL CC of the second component carrier (CC B). The UL TRG can share the UL TA.

[0157] FIG. 12 illustrates a flowchart of an example method 1200 of UL timing acquisition for UL and DL decoupling, according to some embodiments. The method 1200 shown in FIG. 12 may be used in conjunction with any of the systems, methods, or devices illustrated in the Figures, among other devices. In various embodiments, some of the method elements shown may be performed concurrently, in a different order than shown, or may be omitted. Additional method elements may also be performed as desired.

[0158] The method 1200 can comprise receiving 1210, at the UE 106 from a network (NW) 100 via a base station 102, an uplink (UL) timing advance (TA) command to enable the UE 106 to obtain UL timing information for two or more component carriers (CCs) aggregated together in a carrier aggregation (CA) configuration. The two or more CCs can comprise a first component carrier (CC A), which is a UL only CC without a corresponding DL CC, co-located with a second component carrier (CC B) which is comprised of both a UL CC and a DL CC, and receives the TA command in the DL CC from the BS. The method 1200 can comprise sending 1220, at the UE 106 to the NW 100 via the base station 102, UL transmissions on the first component carrier (CC A) using UL timing information based on the TA command from the second component carrier. The UL transmissions can be only UL transmissions.

[0159] According to some embodiments, the network can form a UL CC timing reference group (TRG), that can be similar to the TAG, that can include both the CC A and the CC B (as the network has the full information on co-location). The UE can automatically apply the timing advance for the CC B to the CC A. The CCClient Ref. No. P71093WO1group can be explicitly configured through an RRC configuration for CCs in the same band or different bands. The CC group can be only explicitly configured through the RRC configuration for CCs in different bands. For CCs in the same band, the UE can assume they are co-located unless they receive separate signaling. The DL reference timing can be obtained by the UE using any of the DL CCs in the group. The network may update the CCs in the UL timing reference group when it changes CA configuration for the UE. The network can ensure there is always a CC with both UL and DL that is in sync with the network.

[0160] In one aspect, apparatus of a user equipment (UE) 106 can comprise one or more processors 402 and / or 604A-D coupled to a memory 406 and / or 604G . The processors 402 and / or 604A-D can be configured to identify, at the UE 106, an uplink (UL) timing reference group (TRG) for two or more co-located UL component carriers (CCs) in a carrier aggregation (CA) configuration. At least one of the two or more UL CCs can comprise a corresponding downlink (DL) CC. The processors 604A-D can be configured to receive, at the UE 106, a timing advance (TA) command on the corresponding DL CC. The processors 604A-D can be configured to send, at the UE 106 to a network (NW) 100 via a base station 102, UL transmissions on the two or more UL CCs using UL timing information based on the TA.

[0161] In another aspect, the processors 604A-D can be further configured to receive, at the UE from a network (NW) via a base station, a DL transmission on the corresponding DL CC which is part of a second component carrier (CC B). The UL TRG can comprise a first component carrier (CC A) that is co-located with the second component carrier (CC B) and the second component carrier (CC B) has both an UL CC and a corresponding DL CC. The first component carrier (CC A) can be a UL only CC without a corresponding DL CC. The processors 604A-D can be further configured to send, at the UE to the NW via the base station, UL transmissions on the first component carrier (CC A) using UL timing information based on the TA for the second component carrier (CC B). The UL transmissions can be only UL transmissions.

[0162] In another aspect, the processors 604A-D can be further configured toClient Ref. No. P71093WO1receive, at the UE from a network (NW) via a base station, a Radio Resource Control (RRC) configuration comprising a TRG configuration, wherein: the CCs in the TRG are in the same band or different bands; or the CCs in the TRG are in different bands and the one or more processors are configured to determine that CCs are in the same band when the CCs are co-located unless the CCs receive separate signaling.

[0163] In another aspect, the processors 402 and / or 604A-D can be further configured to obtain, at the UE, a DL reference timing from a DL CC in the TRG.

[0164] FIG. 13 illustrates a flowchart of an example method 1300 of UL timing acquisition for UL and DL decoupling, according to some embodiments. The method 1300 shown in FIG. 13 may be used in conjunction with any of the systems, methods, or devices illustrated in the Figures, among other devices. In various embodiments, some of the method elements shown may be performed concurrently, in a different order than shown, or may be omitted. Additional method elements may also be performed as desired.

[0165] The method 1300 can comprise identifying 1310, at the UE 106, an uplink (UL) timing reference group (TRG) for two or more co-located UL component carriers (CCs) in a carrier aggregation (CA) configuration. At least one of the two or more UL CCs can comprise a corresponding downlink (DL) CC. The method 1300 can comprise receiving 1320, at the UE 106, a timing advance (TA) command on the corresponding DL CC. The method 1300 can comprise sending 1330, at the UE 106 to a network (NW) 100 via a base station 102, UL transmissions on the two or more UL CCs using UL timing information based on the TA.FIGS. 14-16: UL Timing Non-Co-Located Cross-CC Contention-Free RACH Process

[0166] FIG. 14 illustrates an example carrier aggregation system 1400 with a UL only CC (CCA) non-co-located with another UL CC (CC B) with a corresponding DL CC, according to some embodiments.

[0167] FIG. 15 illustrates an example signaling 1500 for a cross-CC contention-Client Ref. No. P71093WO1free Random Access Channel (RACH) process, according to some embodiments.

[0168] For UL only CCs, i.e. without a corresponding DL CC, and non-co-located (Case 2), i.e. the UL only CC (CC A) is not co-located with any another UL CC which has a corresponding DL CC, the UL timing can be obtained using a cross-CC Random Access Channel (RACH) process.

[0169] For a contention-free RACH process, a first message (Message 1) comprising a Physical Random Access Channel (PRACH) preamble can be sent by the UE to the network (NW) via a base station, e.g. a gNB, over the UL only CC (CC A) using the DL timing from another UL CC (CC B) which has a corresponding DL CC. A second message (Message 2) comprising a RACH response can be sent by the NW via the base station to the UE over the CC B DL.

[0170] In one aspect, an apparatus of a user equipment (UE) 106 can comprise one or more processors 402 and / or 604A-D coupled to a memory 406 and / or 604G. The processors 604A-D can be configured to receive, at the UE 106 from a network (NW) 100 via a first base station (BS1) 102, a downlink (DL) transmission on a second component carrier (CC B) comprising a DL timing for the second component carrier (CC B), the second component carrier (CC B) comprising both a DL CC and an uplink (UL) CC. The processors 604A-D can be configured to send, at the UE 106 to the NW 100 via a second base station (BS2) 102, a first message (Message 1) comprising a Physical Random Access Channel (PRACH) preamble on a first component carrier (CC A) using UL timing based on the DL timing for the second component carrier (CC B). The first component carrier (CC A) can be a UL only CC without a corresponding DL CC. The processors 604A-D can be configured to receive, at the UE 106 from the NW 100 via the BS1 102, a second message (Message 2) comprising a Random Access Channel (RACH) response on the second component carrier (CC B). The processors 604A-D can be configured to send, at the UE 106 to the NW 100 via the BS2 102, UL transmissions on the first component carrier (CC A) using UL timing based on the DL timing for the second component carrier (CC B). The UL transmissions can be only UL transmissions.Client Ref. No. P71093WO1

[0171] In another aspect, the processors 604A-D can be further configured to receive, at the UE from the BS1 , a Radio Resource Control (RRC) reconfiguration message comprising frequency information for a cross-CC RACH procedure and a CC indication indicating which DL CC and LIL CC to use. The processors 402 and / or 604A-D can be further configured to initiate, at the UE, the cross-CC RACH procedure for the UL only CC.

[0172] In another aspect, the RRC reconfiguration message can further comprise an indication indicating which DL CC to receive a Random Access Response (RAR).

[0173] In another aspect, the processors 604A-D can be further configured to receive, at the UE from the BS1 , a Medium Access Control-Control Element (MAC-CE) comprising information for a cross-CC RACH procedure and a CC indication indicating which DL CC and UL CC to use. The processors 402 and / or 604A-D can be further configured to initiate, at the UE, the cross-CC RACH procedure for the UL only CC.

[0174] In another aspect, the MAC-CE can further comprise an indication indicating which DL CC to receive a Random Access Response (RAR).

[0175] In another aspect, the processors 604A-D can be further configured to receive, at the UE from the BS1 , a Physical Downlink Control Channel (PDCCH) order comprising information for a cross-CC RACH procedure and a CC indication indicating which DL CC and UL CC to use. The processors 402 and / or 604A-D can be further configured to initiate, at the UE, the cross-CC RACH procedure for the UL only CC.

[0176] In another aspect, the PDCCH order can further comprise an indication indicating which DL CC to receive a Random Access Response (RAR).

[0177] In another aspect, a carrier aggregation (CA) configuration can comprise one or two UL only CCs. The processors 604A-D can be further configured to receive, at the UE from the BS1, a System Information Block Type 1 (SIB1) comprising frequency information for a cross-CC RACH procedure and a CC indication indicating which DL CC and UL CC to use. The processors 402 and / orClient Ref. No. P71093WO164 can be further configured to initiate, at the UE, the cross-CC RACH procedure for the UL only CCs.

[0178] In another aspect, a carrier aggregation (CA) configuration can comprise only one DL CC. The processors 604A-D can be further configured to receive, at the UE from the BS1 , an indication indicating the DL CC to be used for a DL timing reference. The processors 604A-D can be further configured to receive, at the UE from the BS1 , the second message (Message 2) comprising the RACH using the DL timing reference.

[0179] In another aspect, a carrier aggregation (CA) configuration can comprise two or more DL CCs. The processors 604A-D can be further configured to receive, at the UE from the BS1 , an indication indicating which of the DL CCs to be used for a DL timing reference. The processors 604A-D can be further configured to receive, at the UE from the BS1 , the second message (Message 2) comprising the RACH using the DL timing reference.

[0180] FIG. 16 illustrates a flowchart of an example method 1600 of UL timing acquisition for UL and DL decoupling, according to some embodiments. The method 1600 shown in FIG. 16 may be used in conjunction with any of the systems, methods, or devices illustrated in the Figures, among other devices. In various embodiments, some of the method elements shown may be performed concurrently, in a different order than shown, or may be omitted. Additional method elements may also be performed as desired.

[0181] The method 1600 can comprise receiving 1610, at the UE from a network (NW) via a first base station (BS1), a downlink (DL) transmission on a second component carrier (CC B) comprising a DL timing for the second component carrier (CC B), the second component carrier (CC B) comprising both a DL CC and an uplink (UL) CC. The method 1600 can comprise sending 1620, at the UE to the NW via a second base station (BS2), a first message (Message 1) comprising a Physical Random Access Channel (PRACH) preamble on a first component carrier (CC A) using UL timing based on the DL timing for the second component carrier (CC B). The first component carrier (CC A) can be a UL onlyClient Ref. No. P71093WO1CC without a corresponding DL CC. The method 1600 can comprise receiving 1630, at the UE from the NW via the BS1, a second message (Message 2) comprising a Random Access Channel (RACH) response on the second component carrier (CC B). The method 1600 can comprise sending 1640, at the UE to the NW via the BS2, UL transmissions on the first component carrier (CC A) using UL timing based on the DL timing for the second component carrier (CC B).FIGS. 17-18: UL Timing Non-Co- Located Cross-CC Contention-Based RACH Process

[0182] FIG. 17 illustrates an example signaling 1700 for a cross-CC contentionbased Random Access Channel (RACH) process, according to some embodiments.

[0183] For a contention-based RACH process, a first message (Message 1) comprising a Physical Random Access Channel (PRACH) preamble can be sent by the UE to the network (NW) via a base station, e.g. a gNB, over the UL only CC (CC A) using the DL timing from CC B. A second message (Message 2) comprising a RACH response can be sent by the NW via the base station to the UE over the CC B DL. A third message (Message 3) comprising a Physical Uplink Shared Channel (PUSCH) can be sent by the UE to the NW over the CC A with timing advance (TA) based on the CC B DL timing, or over the CC B UL. A fourth message (Message 4) comprising a Physical Downlink Control Channel (PDCCH) can be send by the UE to the NW over the CC B DL.

[0184] The cross-CC RACH and an indication of which DL / UL CC to use can be triggered. According to some embodiments, frequency information can be provided in a Radio Resource Control (RRC) reconfiguration. Once configured by the RRC, the UE can start a cross-CC RACH for each UL only CC. The DL to receive a Random Access Response (RAR) can be indicated by the network in the RRC reconfiguration or the UE can monitor all DLs. Once the second message (Message 2) is received on a DL CC, the UE can use the same DL for receiving the fourth message (Message 4) in case of a contention-based RACH.Client Ref. No. P71093WO1

[0185] According to some embodiments, the UE RACH can be triggered by Medium Access Control-Control Element (MAC CE). Which DL to receive the RAR can be indicated by the network in the MAC-CE.

[0186] According to some embodiments, the UE RACH can be triggered by a PDCCH order once the RRC reconfiguration is done. Which DL to receive the RAR can be indicated by the network in the PDCCH.

[0187] If there is only 1 or 2 UL only CCs, the frequency information of such UL CCs can be provided in System Information Block Type 1 (SIB1 ). If there is only one DL CC, the CC can be indicated by the network, which is used for DL timing reference and for RACH Message 2 and / or Message 4 transmission. If there are more than one DL CC, the network can configure one DL for the timing reference and the RACH Message 2 and / or Message 4 transmission. Such DL CC can be configured by network.

[0188] In one aspect, an apparatus of a user equipment (UE) 106 can comprise one or more processors 402 and / or 604A-D coupled to a memory 406 and / or 604G. The processors 604A-D can be configured to receive, at the UE 106 from a network (NW) 100 via a first base station (BS1) 102, a downlink (DL) transmission on a second component carrier (CC B) comprising a DL timing for the second component carrier (CC B), the second component carrier (CC B) comprising both a DL CC and an uplink (UL) CC. The processors 604A-D can be configured to send, at the UE 106 to the NW 100 via a second base station (BS2) 102, a first message (Message 1) comprising a Physical Random Access Channel (PRACH) preamble on a first component carrier (CC A) using UL timing based on the DL timing for the second component carrier (CC B). The first component carrier (CC A) can be a UL only CC without a corresponding DL CC. The processors 604A-D can be configured to receive, at the UE 106 from the NW 100 via the BS1 102, a second message (Message 2) comprising a Random Access Channel (RACH) response on the second component carrier (CC B). The processors 604A-D can be configured to send, at the UE 106 to the NW 100, a third message (Message 3) comprising a Physical Uplink Shared Channel (PUSCH) via the BS2 on the first component carrier (CC A) with timing information based on a timing advance (TA)Client Ref. No. P71093WO1based on DL timing of the second component carrier (CC B) or via the BS1 on the second component carrier (CC B). The processors 604A-D can be configured to receive, at the UE 106 from the NW via BS1 , a fourth message (Message 4) comprising a Physical Downlink Control Channel (PDCCH) on the second component carrier (CC B). The processors 604A-D can be configured to send, at the UE 106 to the NW 100 via the BS2 102, UL transmissions on the first component carrier (CC A) UL timing based on the DL timing for the second component carrier (CC B). The UL transmissions can be only UL transmissions.

[0189] In another aspect, the processors 604A-D can be further configured to receive, at the UE from the BS1 , a Radio Resource Control (RRC) reconfiguration message comprising frequency information for a cross-CC RACH procedure and a CC indication indicating which DL CC and UL CC to use. The processors 402 and / or 604A-D can be further configured to initiate, at the UE, the cross-CC RACH procedure for the UL only CC.

[0190] In another aspect, the RRC reconfiguration message can further comprise an indication indicating which DL CC to receive a Random Access Response (RAR).

[0191] In another aspect, the processors 604A-D can be further configured to receive, at the UE from the BS1 , a Medium Access Control-Control Element (MAC-CE) comprising information for a cross-CC RACH procedure and a CC indication indicating which DL CC and UL CC to use. The processors 402 and / or 604A-D can be further configured to initiate, at the UE, the cross-CC RACH procedure for the UL only CC.

[0192] In another aspect, the MAC-CE can further comprise an indication indicating which DL CC to receive a Random Access Response (RAR).

[0193] In another aspect, the processors 604A-D can be further configured to receive, at the UE from the BS1 , a Physical Downlink Control Channel (PDCCH) order comprising information for a cross-CC RACH procedure and a CC indication indicating which DL CC and UL CC to use. The processors 402 and / or 604A-D can be further configured to initiate, at the UE, the cross-CC RACH procedure for theClient Ref. No. P71093WO1UL only CC.

[0194] In another aspect, the PDCCH order can further comprise an indication indicating which DL CC to receive a Random Access Response (RAR).

[0195] In another aspect, a carrier aggregation (CA) configuration can comprise one or two UL only CCs. The processors 604A-D can be further configured to receive, at the LIE from the BS1, a System Information Block Type 1 (SIB1) comprising frequency information for a cross-CC RACH procedure and a CC indication indicating which DL CC and UL CC to use. The processors 402 and / or 604A-D can be further configured to initiate, at the UE, the cross-CC RACH procedure for the UL only CCs.

[0196] In another aspect, a carrier aggregation (CA) configuration can comprise only one DL CC. The processors 604A-D can be further configured to receive, at the UE from the BS1 , an indication indicating the DL CC to be used for a DL timing reference. The processors 604A-D can be further configured to receive, at the UE from the BS1 , the second message (Message 2) comprising the RACH using the DL timing reference.

[0197] In another aspect, a carrier aggregation (CA) configuration can comprise two or more DL CCs. The processors 604A-D can be further configured to receive, at the UE from the BS1 , an indication indicating which of the DL CCs to be used for a DL timing reference. The processors can be further configured to receive, at the UE from the BS1 , the second message (Message 2) comprising the RACH using the DL timing reference.

[0198] FIG. 18 illustrates a flowchart of an example method 1800 of UL timing acquisition for UL and DL decoupling, according to some embodiments. The method 1800 shown in FIG. 18 may be used in conjunction with any of the systems, methods, or devices illustrated in the Figures, among other devices. In various embodiments, some of the method elements shown may be performed concurrently, in a different order than shown, or may be omitted. Additional method elements may also be performed as desired.

[0199] The method 1800 can comprise receiving 1810, at the UE from aClient Ref. No. P71093WO1network (NW) via a first base station (BS1), a downlink (DL) transmission on a second component carrier (CC B) comprising a DL timing for the second component carrier (CC B), the second component carrier (CC B) comprising both a DL CC and an uplink (UL) CC. The method 1800 can comprise sending 1820, at the UE to the NW via a second base station (BS2), a first message (Message 1) comprising a Physical Random Access Channel (PRACH) preamble on a first component carrier (CC A) using UL timing based on the DL timing for the second component carrier (CC B). The first component carrier (CC A) can be a UL only CC without a corresponding DL CC. The method 1800 can comprise receiving 1830, at the UE from the NW via the BS1 , a second message (Message 2) comprising a Random Access Channel (RACH) response on the second component carrier (CC B). The method 1800 can comprise sending 1840, at the UE to the NW, a third message (Message 3) comprising a Physical Uplink Shared Channel (PUSCH) via the BS2 on the first component carrier (CC A) with timing information based on a timing advance (TA) based on DL timing of the second component carrier (CC B) or via the BS1 on the second component carrier (CC B). The method can comprise receiving 1850, at the UE from the NW via BS1 , a fourth message (Message 4) comprising a Physical Downlink Control Channel (PDCCH) on the second component carrier (CC B). The method 1800 can comprise sending 1860, at the UE to the NW via the BS2, UL transmissions on the first component carrier (CC A) using UL timing based on the DL timing for the second component carrier (CC B). The UL transmissions can be only UL transmissions.CA

[0200] With respect to CA configuration, during initial access, the UE can connect to the network via a normal CC, i.e. with both UL and DL. According to some embodiments, the network can configure the UL only CC through blind configuration, i.e. without prior UE measurements. According to some embodiments, the UL only CCs can be configured with a normal CC (with both UL and DL) and then the DL can be released, e.g. when the DL traffic is light.Client Ref. No. P71093WO1

[0201] In another aspect, the processors 604A-D can be further configured to receive, at the UE from the NW via the base station, a UL only CC configuration without prior UE measurements.

[0202] In another aspect, the processors 604A-D can be further configured to receive, at the UE from the NW via the base station, a CC configuration which is both an UL CC and a DL CC. The DL CC can be later released.

[0203] In one aspect, a baseband processor (e.g. 604A-D), or functionally similar component(s) whose function may include supporting baseband layer operations (e.g., to facilitate wireless communication between the UE 106 and other wireless devices) in the UE 106, can be configured to cause the UE 106 to perform any of the methods described herein. In another aspect, the UE 106 can have one or more processors (e.g. processors 402 and / or 604A-D) coupled to a memory 406 or 604G to cause the user equipment 106 to perform any of the methods described herein. In another aspect, a baseband processor (e.g. baseband processor 604A-D can be configured to cause a base station 102 to perform one or more of the methods described herein. In another aspect, the base station 102 can have one or more processors 204 and / or 604A-D coupled to memory 260 or 604G configured to cause the base station 102 to perform any of the methods described herein. In another aspect, a computer program product, comprising computer instructions which, when executed by one or more processors, can perform any of the operations described herein.

[0204] Embodiments of the present disclosure may be realized in any of various forms. For example, some embodiments may be realized as a computer-implemented method, a computer readable memory medium, or a computer system. Other embodiments may be realized using one or more custom-designed hardware devices such as ASICs. Still other embodiments may be realized using one or more programmable hardware elements such as FPGAs.

[0205] In some embodiments, a non-transitory computer-readable memory medium may be configured so that it stores program instructions and / or data,Client Ref. No. P71093WO1where the program instructions, if executed by a computer system, cause the computer system to perform a method, e.g., any of the method embodiments described herein, or, any combination of the method embodiments described herein, or, any subset of any of the method embodiments described herein, or, any combination of such subsets.

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

[0207] Any of the methods described herein for operating a user equipment (UE) may be the basis of a corresponding method for operating a base station, by interpreting each message / signal X received by the UE in the downlink as message / signal X transmitted by the base station, and each message / signal Y transmitted in the uplink by the UE as a message / signal Y received by the base station.

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

Claims

Client Ref. No. P71093WO1CLAIMSWhat is claimed is:1 . An apparatus of a user equipment (UE) comprising:one or more processors, coupled to a memory, configured to:receive, at the UE from a network (NW) via a base station (BS), an uplink (UL) timing advance (TA) command to enable the UE to obtain UL timing information for two or more component carriers (CCs) aggregated together in a carrier aggregation (CA) configuration;wherein the two or more CCs comprise a first component carrier (CC A), which is a UL only CC without a corresponding DL CC, co-located with a second component carrier (CC B) which is comprised of both a UL CC and a DL CC, and receives the TA command in the DL CC from the BS; andsend, at the UE to the NW via the base station, UL transmissions on the first component carrier (CC A) using UL timing information based on the TA command from the second component carrier.

2. The apparatus of claim 1 , wherein the one or more processors are further configured to:receive, at the UE from the NW via the base station, one or more of:an indication comprising a DL reference timing along with the TA command;a Radio Resource Configuration (RRC) for the UL only CC comprising a DL reference timing; ora DL reference signal from the second component carrier (CC B) with an indication for the UE to derive a DL reference timing.Client Ref. No. P71093WO13. The apparatus of claim 1 , wherein the one or more processors are further configured to:receive, at the UE from the NW via the base station, a DL transmission on the DL CC of the second component carrier (CC B) comprising an UL timing reference group (TRG) comprising the UL only CC of the first component carrier (CC A) and the UL CC of the second component carrier (CC B);wherein the UL TRG shares the UL TA.

4. The apparatus of claim 1 , wherein the one or more processors are further configured to:receive, at the UE from the NW via the base station, a UL only CC configuration without prior UE measurements.

5. The apparatus of claim 1 , wherein the one or more processors are further configured to:receive, at the UE from the NW via the base station, a CC configuration which is both an UL CC and a DL CC;wherein the DL CC is later released.

6. An apparatus of a user equipment (UE) comprising:one or more processors, coupled to a memory, configured to:identify, at the UE, an uplink (UL) timing reference group (TRG) for two or more co-located UL component carriers (CCs) in a carrier aggregation (CA) configuration;wherein at least one of the two or more UL CCs comprises a corresponding downlink (DL) CC;receive, at the UE, a timing advance (TA) command on the corresponding DL CC; andsend, at the UE to a network (NW) via a base station, UL transmissions on the two or more UL CCs using UL timing information based on the TA.Client Ref. No. P71093WO17. The apparatus of claim 6, wherein the one or more processors are further configured to:receive, at the UE from a network (NW) via a base station, a DL transmission on the corresponding DL CC which is part of a second component carrier (CC B);wherein the UL TRG comprises a first component carrier (CC A) that is co-located with the second component carrier (CC B) and the second component carrier (CC B) has both an UL CC and a corresponding DL CC;wherein the first component carrier (CC A) is a UL only CC without a corresponding DL CC; andsend, at the UE to the NW via the base station, UL transmissions on the first component carrier (CC A) using UL timing information based on the TA for the second component carrier (CC B).

8. The apparatus of claim 6, wherein the one or more processors are further configured to:receive, at the UE from a network (NW) via a base station, a Radio Resource Control (RRC) configuration comprising a TRG configuration, wherein:the CCs in the TRG are in a same band or different bands; or the CCs in the TRG are in different bands and the one or more processors are configured to determine that CCs are in the same band when the CCs are co-located unless the CCs receive separate signaling.

9. The apparatus of claim 6, wherein the one or more processors are further configured to:obtain, at the UE, a DL reference timing from a DL CC in the TRG.Client Ref. No. P71093WO110. The apparatus of claim 6, wherein the one or more processors are further configured to:receive, at the UE from the NW via the base station, a UL only CC configuration without prior UE measurements.11 .The apparatus of claim 6, wherein the one or more processors are further configured to:receive, at the UE from the NW via the base station, a CC configuration which is both an UL CC and a DL CC;wherein the DL CC is later released.

12. An apparatus of a user equipment (UE) comprising:one or more processors, coupled to a memory, configured to:receive, at the UE from a network (NW) via a first base station (BS1), a downlink (DL) transmission on a second component carrier (CC B) comprising a DL timing for the second component carrier (CC B), the second component carrier (CC B) comprising both a DL CC and an uplink (UL) CC;send, at the UE to the NW via a second base station (BS2), a first message (Message 1) comprising a Physical Random Access Channel (PRACH) preamble on a first component carrier (CC A) using UL timing based on the DL timing for the second component carrier (CC B);wherein the first component carrier (CC A) is a UL only CC without a corresponding DL CC;receive, at the UE from the NW via the BS1, a second message (Message 2) comprising a Random Access Channel (RACH) response on the second component carrier (CC B); and send, at the UE to the NW via the BS2, UL transmissions on the first component carrier (CC A) using UL timing based on the DL timing for the second component carrier (CC B).Client Ref. No. P71093WO113. The apparatus of claim 12, wherein the one or more processors are further configured to:receive, at the UE from the BS1 , a Radio Resource Control (RRC) reconfiguration message comprising frequency information for a cross-CC RACH procedure and a CC indication indicating which DL CC and UL CC to use; andinitiate, at the UE, the cross-CC RACH procedure for the UL only CC.

14. The apparatus of claim 13, wherein the RRC reconfiguration message further comprises an indication indicating which DL CC to receive a Random Access Response (RAR).

15. The apparatus of claim 12, wherein the one or more processors are further configured to:receive, at the UE from the BS1 , a Medium Access Control- Control Element (MAC-CE) comprising information for a cross-CC RACH procedure and a CC indication indicating which DL CC and UL CC to use; andinitiate, at the UE, the cross-CC RACH procedure for the UL only CC.

16. The apparatus of claim 15, wherein the MAC-CE further comprises an indication indicating which DL CC to receive a Random Access Response (RAR).

17. The apparatus of claim 12, wherein the one or more processors are further configured to:receive, at the UE from the BS1 , a Physical Downlink Control Channel (PDCCH) order comprising information for a cross-CCClient Ref. No. P71093WO1RACH procedure and a CC indication indicating which DL CC and UL CC to use; andinitiate, at the UE, the cross-CC RACH procedure for the UL only CC.

18. The apparatus of claim 17, wherein the PDCCH order further comprises an indication indicating which DL CC to receive a Random Access Response (RAR).

19. The apparatus of claim 12, wherein in a carrier aggregation (CA) configuration comprises one or two UL only CCs; and wherein the one or more processors are further configured to:receive, at the UE from the BS1 , a System Information Block Type 1 (SIB1 ) comprising frequency information for a cross-CC RACH procedure and a CC indication indicating which DL CC and UL CC to use; andinitiate, at the UE, the cross-CC RACH procedure for the UL only CCs.

20. The apparatus of claim 12, wherein in a carrier aggregation (CA) configuration comprises only one DL CC; and wherein the one or more processors are further configured to:receive, at the UE from the BS1 , an indication indicating the DL CC to be used for a DL timing reference; andreceive, at the UE from the BS1 , the second message (Message 2) comprising the RACH using the DL timing reference.21.The apparatus of claim 12, wherein in a carrier aggregation (CA) configuration comprises two or more DL CCs; and wherein the one or more processors are further configured to:receive, at the UE from the BS1 , an indication indicating which of the DL CCs to be used for a DL timing reference; andClient Ref. No. P71093WO1receive, at the UE from the BS1 , the second message (Message 2) comprising the RACH using the DL timing reference.

22. The apparatus of claim 12, wherein the one or more processors are further configured to:receive, at the UE from the NW via the base station, a UL only CC configuration without prior UE measurements.

23. The apparatus of claim 12, wherein the one or more processors are further configured to:receive, at the UE from the NW via the base station, a CC configuration which is both an UL CC and a DL CC;wherein the DL CC is later released.

24. An apparatus of a user equipment (UE) comprising:one or more processors, coupled to a memory, configured to:receive, at the UE from a network (NW) via a first base station (BS1), a downlink (DL) transmission on a second component carrier (CC B) comprising a DL timing for the second component carrier (CC B), the second component carrier (CC B) comprising both a DL CC and an uplink (UL) CC;send, at the UE to the NW via a second base station (BS2), a first message (Message 1) comprising a Physical Random Access Channel (PRACH) preamble on a first component carrier (CC A) using UL timing based on the DL timing for the second component carrier (CC B);wherein the first component carrier (CC A) is a UL only CC without a corresponding DL CC;receive, at the UE from the NW via the BS1, a second message (Message 2) comprising a Random Access Channel (RACH) response on the second component carrier (CC B); send, at the UE to the NW, a third message (Message 3)Client Ref. No. P71093WO1comprising a Physical Uplink Shared Channel (PUSCH) via the BS2 on the first component carrier (CC A) with timing information based on a timing advance (TA) based on DL timing of the second component carrier (CC B) or via the BS1 on the second component carrier (CC B);receive, at the UE from the NW via BS1, a fourth message (Message 4) comprising a Physical Downlink Control Channel (PDCCH) on the second component carrier (CC B); andsend, at the UE to the NW via the BS2, UL transmissions on the first component carrier (CC A) using UL timing based on the DL timing for the second component carrier (CC B).

25. The apparatus of claim 24, wherein the one or more processors are further configured to:receive, at the UE from the BS1 , a Radio Resource Control (RRC) reconfiguration message comprising frequency information for a cross-CC RACH procedure and a CC indication indicating which DL CC and UL CC to use; andinitiate, at the UE, the cross-CC RACH procedure for the UL only CC.

26. The apparatus of claim 25, wherein the RRC reconfiguration message further comprises an indication indicating which DL CC to receive a Random Access Response (RAR).

27. The apparatus of claim 24, wherein the one or more processors are further configured to:receive, at the UE from the BS1 , a Medium Access Control- Control Element (MAC-CE) comprising information for a cross-CC RACH procedure and a CC indication indicating which DL CC and UL CC to use; andClient Ref. No. P71093WO1initiate, at the UE, the cross-CC RACH procedure for the UL only CC.

28. The apparatus of claim 27, wherein the MAC-CE further comprises an indication indicating which DL CC to receive a Random Access Response (RAR).

29. The apparatus of claim 24, wherein the one or more processors are further configured to:receive, at the UE from the BS1 , a Physical Downlink Control Channel (PDCCH) order comprising information for a cross-CC RACH procedure and a CC indication indicating which DL CC and UL CC to use; andinitiate, at the UE, the cross-CC RACH procedure for the UL only CC.

30. The apparatus of claim 29, wherein the PDCCH order further comprises an indication indicating which DL CC to receive a Random Access Response (RAR).31.The apparatus of claim 24, wherein a carrier aggregation (CA) configuration comprises one or two UL only CCs; and wherein the one or more processors are further configured to:receive, at the UE from the BS1 , a System Information Block Type 1 (SIB1) comprising frequency information for a cross-CC RACH procedure and a CC indication indicating which DL CC and UL CC to use; andinitiate, at the UE, the cross-CC RACH procedure for the UL only CCs.Client Ref. No. P71093WO132. The apparatus of claim 24, wherein a carrier aggregation (CA) configuration comprises only one DL CC; and wherein the one or more processors are further configured to:receive, at the UE from the BS1 , an indication indicating the DL CC to be used for a DL timing reference; andreceive, at the UE from the BS1 , the second message (Message 2) comprising the RACH using the DL timing reference.

33. The apparatus of claim 24, wherein a carrier aggregation (CA) configuration comprises two or more DL CCs; and wherein the one or more processors are further configured to:receive, at the UE from the BS1 , an indication indicating which of the DL CCs to be used for a DL timing reference; and receive, at the UE from the BS1 , the second message (Message 2) comprising the RACH using the DL timing reference.

34. The apparatus of claim 24, wherein the one or more processors are further configured to:receive, at the UE from the NW via the base station, a UL only CC configuration without prior UE measurements.

35. The apparatus of claim 24, wherein the one or more processors are further configured to:receive, at the UE from the NW via the base station, a CC configuration which is both an UL CC and a DL CC;wherein the DL CC is later released.

36. A user equipment (UE) configured to perform any of the operations described herein.

37. A next generation node B (gNB) configured to perform any of the operations described herein.Client Ref. No. P71093WO138. A computer program product, comprising computer instructions which, when executed by one or more processors, perform any of the operations described herein.