Power efficiency by UE centric and network coordinated dynamic TX-RX operation

Abstract

A method of selecting an active transmit-receive operation (TRO) at a user equipment is disclosed. The method comprises receiving, from a network, a scheduling priority for a plurality of N TROs, where N is a positive number, and identifying, at the UE, a selected TRO from the plurality of N TROs. The UE can determine a start time for the selected TRO and send the start time to the network. The UE can switch to the selected TRO at the start time and communicate with the network over the selected TRO.

Description

Client Ref. No. P70047W01POWER EFFICIENCY BY UE CENTRIC ANDNETWORK COORIDINATED DYNAMIC TX-RX OPERATIONFIELDEmbodiments of the invention relate to wireless communications, including apparatuses, systems, and methods for performing user equipment (UE) centric and network coordinated dynamic transmit-receive operations in a cellular communications network.DESCRIPTION OF THE RELATED ART

[0001] 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.

[0002] 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.

[0003] 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)). In sixth generation (6G) wireless RANS, RAN nodes can include a 6G Node.BRIEF DESCRIPTION OF THE DRAWINGSClient Ref. No. P70047W01

[0004] 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:

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

[0006] 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.

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

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

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

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

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

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

[0013] FIG. 8 illustrates an example block diagram of a control plane protocol stack according to some embodiments.

[0014] FIG. 9 illustrates an example block diagram of a user plane protocol stack in accordance with some embodiments.

[0015] FIG. 10 illustrates an example architecture of a system including a core network (GN) in accordance with various embodiments.

[0016] FIG. 1 1 illustrates an example block diagram showing three different bandwidth parts, in accordance with some embodiments.

[0017] FIG. 12 illustrates an example diagram of transmit-receive operations (TRO) used for 5G and 6G communication, in accordance with some embodiments.

[0018] FIG. 13 is an example illustration of TRO switching for UL data communication to provide high throughput and low latency traffic that is prioritized by a UE 106, in accordanceClient Ref. No. P70047W01 with some embodiments.

[0019] FIG. 14 is an example illustration of UE TRO switching for UL data communication to reduce physical downlink control channel monitoring and switching delay, in accordance with some embodiments.

[0020] FIG. 15 is an example illustration of a process for power efficiency by a UE centric dynamic TRO, in accordance with some embodiments.

[0021] FIG. 16 is an example illustration of an artificial intelligence / machine learning (AI / ML) model 1600 for classification and regression of a TRO selection (classification) and a TRO switch time (regression), in accordance with some embodiments.

[0022] FIG. 17 is an example illustration of a flow chart for a method 1700 of selecting an active transmit-receive operation (TRO) at a user equipment (UE), according to some embodiments.

[0023] FIG. 18 is an example illustration of a communication 1800 between a UE and a serving cell (e.g. base station) for a UE centric adaptive TRO configuration selection, in accordance with some embodiments.

[0024] FIG. 19 is an example flow chart of a method 1900 for selecting a transmit-receive operation (TRO) configuration at a UE, in accordance with some embodiments.

[0025] FIG. 20 illustrates an example of a UE assisted NW centric dynamic Transmit- Receive operation (TRO) adaptation procedure 2000, in accordance with some embodiments.

[0026] FIG. 21 illustrates a flow chart of a method 2100 of network centric dynamic Tx- Rx operation (TRO) adaptation, in accordance with some embodiments.

[0027] 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.Client Ref. No. P70047W01DETAILED DESCRIPTIONTerms

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

[0029] Memory Medium - Any of various types of non-transitory memory devices or storage devices. The term “memory medium” is intended to include an installation medium, e.g., a CD-ROM, floppy disks, or tape device; a computer system memory or randomaccess memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; a nonvolatile 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.

[0030] 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.

[0031] 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”.

[0032] 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 device or combinations of devices. In general, the term "computer system" can be broadly defined to encompass anyClient Ref. No. P70047W01 device (or combination of devices) having at least one processor that executes instructions from a memory medium.

[0033] 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, 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.

[0034] 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 as part of a wireless telephone system or radio system.

[0035] 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.

[0036] Channel - a medium used to convey information from a sender (transmitter) to a receiver. It should be noted that since characteristics of the term “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 channelsClient Ref. No. P70047W01 for different uses such as data, control information, etc.

[0037] 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.

[0038] 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 and fills 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.

[0039] 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.

[0040] 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, orClient Ref. No. P70047W01 using “weak parallelism”, where the tasks are performed in an interleaved manner, e.g., by time multiplexing of execution threads.

[0041] 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.

[0042] 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.

[0043] The example embodiments are described with regard to communication between a base station (or a network through the base station) and a user equipment (UE). However, reference to a base station 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. Therefore, the base station or the UE as described herein is used to represent any appropriate type of electronic component.

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

[0045] Throughout this description various information elements (lEs) are referred to by specific names. It should be understood that these names are only examples and the lEs carrying the information referred to throughout this description may be referred to by other names by various entities.Client Ref. No. P70047W01

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

[0047] 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 devices. Each of the user devices may be referred to herein as a “user equipment” (LIE). Thus, the user equipment 106 devices are referred to as UEs or LIE devices.

[0048] 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.

[0049] 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 l o n g te rm evo l uti o n ( LTE), LTE-Advanced (LTE-A), 5G new radio (5G NR), 5G advance (5G-A), 6G, 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’.

[0050] As shown, the base station 102A may also be equipped to communicate with a network 100 (e.g., a core network of a cellular service provider, a telecommunication 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.

[0051] 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 orClient Ref. No. P70047W01 nearly continuous overlapping service to UEs 106A-N and similar devices over a geographic area via one or more cellular communication standards.

[0052] Thus, while base station 102A may act as a “serving cell” for UEs 106A-N as illustrated in FIG. 1 A, 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.

[0053] 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 transition 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.

[0054] 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., LTE, LTE-A, 5G NR, 5G-A, 6G, 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.

[0055] 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 1 12, 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.Client Ref. No. P70047W01

[0056] 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 of the method embodiments described herein.

[0057] 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, LTE / LTE-Advanced, or 5G NR / 5G-Advanced or 6G using a single shared radio and / or LTE, LTE-Advanced, 5G NR, 5G-A, or 6G 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 RF 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.

[0058] 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, 5G-A, or 6G, and separate radios for communicating using each of Wi-Fi and Bluetooth. The UE may also include separate receive chains that are each coupled to a separate baseband processor. Other configurations are also possible.FIG. 2: Block Diagram of a Base Station

[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 aClient Ref. No. P70047W01 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 Figures 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, the 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 transition 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, 6G, 5G NR, 5G-A LTE, LTE-A, 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 asClient Ref. No. P70047W01 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., 6G, 5G-A, 5G NR and Wi-Fi, LTE etc.).

[0065] As described further subsequently herein, the BS 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 BS 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, the base station 102 and / or processors 204 thereof can be capable of and configured to receive UL data in a transmit receive operation (TRO) configured by the UE 106.FIG. 3: Blockof a ServerClient Ref. No. P70047W01

[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 of one 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 deviceClient Ref. No. P70047W01405, 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 (LIE) 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 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 such as for 6G, 5G-A, 5G NR, LTE, 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 communicationClient Ref. No. P70047W01 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 implemented as 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 (UICC) 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 (UICCs) 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 combinationClient Ref. No. P70047W01 of removable smart cards and fixed / non-removable smart cards (such as one or more elllCC 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 to communicate on corresponding two or more respective networks. For example, a first SIM may support a first RAT such as LTE, and a second SIM (UICC) supports 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 protectionClient Ref. No. P70047W01 and page table translation or set up. In some embodiments, the MMU 440 may be included as a portion of the processor(s) 402.

[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 include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of short to medium range wireless communication circuitry 429.

[0085] In some embodiments, the UE 106 and / or the processors 402 thereof can includeClient Ref. No. P70047W01 configure a transmit-receive operation (TRO) and a start time for the TRO and communicate the TRO configuration information and start time to a network via a base station.FIG. 5: Block Diagram of Cellular Communication Circuitry

[0086] 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.

[0087] 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.

[0088] 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 front end 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.

[0089] 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 anClient Ref. No. P70047W01RF 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.

[0090] 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).

[0091] 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 Gate Array), 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, 550, 570, 572, 335a, 335b, and 336 may be configured to implement part or all of the features described herein.

[0092] 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.

[0093] 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),Client Ref. No. P70047W01 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.

[0094] 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 Diaaram of a Baseband Processor Architecture for a UE

[0095] 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.

[0096] In some embodiments, the device 600 may include application circuitry 602, 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 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).

[0097] 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 mayClient Ref. No. P70047W01 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.

[0098] 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 processor 604A, 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.

[0099] 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 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 inClient Ref. No. P70047W01 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).

[0100] 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 wireless metropolitan 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.

[0101] 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.

[0102] 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 receiveClient Ref. No. P70047W01 signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.

[0103] 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.

[0104] 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.

[0105] 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.

[0106] 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.

[0107] In some embodiments, the synthesizer circuitry 606d may be a fractional-N synthesizer or a fractional N / N+1 synthesizer, although the scope of the 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.

[0108] The synthesizer circuitry 606d may be configured to synthesize an outputClient Ref. No. P70047W01 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.

[0109] 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 applications processor 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 applications processor 602.

[0110] 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.

[0111] 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 with quadrature 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.

[0112] 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 variousClient Ref. No. P70047W01 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.

[0113] 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).

[0114] 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.

[0115] 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.

[0116] 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.

[0117] 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 again. The device 600 may not receive data in this state, in order to receive data, it will transition back to RRC_Connected state.Client Ref. No. P70047W01

[0118] 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.

[0119] Processors of the application circuitry 602 and processors of the baseband circuitry 604 may be used to execute elements of one or more instances of a protocol stack. For example, processors of the baseband circuitry 604, alone or in combination, may be used execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the application circuitry 604 may utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., transmission communication protocol (TCP) and user datagram protocol (UDP) layers). As referred to herein, Layer 3 (L3) may comprise a radio resource control (RRC) layer, described in further detail below. As referred to herein, Layer 2 (L2) may comprise a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, described in further detail below. As referred to herein, Layer 1 (L1 ) may comprise a physical (PHY) layer of a UE / RAN node, described in further detail below. Accordingly, the baseband circuitry 604 can be used to encode a message for transmission between a UE and a gNB, or decode a message received between a UE and a gNB.

[0120] For example, the baseband circuitry 604 can be used to encode and transmit, at the base station 102, an LC-RS to a UE 106. In addition, baseband circuitry at the base station 102 can be configured to encode and transmit data in a transmit-receive operation (TRO) configured by a UE for uplink communication with the base station 102.

[0121] As another example, the baseband circuitry 604 can be used to receive and decode, at the UE 106, data on the TRO.FIG. 7: Block Diagram of an Interface of Baseband Circuitry

[0122] 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.

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

[0124] 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: Control Plane Protocol Stack

[0125] FIG. 8 is an illustration of a control plane protocol stack in accordance with some embodiments. In this embodiment, a control plane 800 is shown as a communications protocol stack between the UE 106a (or alternatively, the UE 106b), the RAN node with base station 102A (or alternatively, the RAN node with base station 102B), and the mobility management entity (MME) 621 .

[0126] The PHY layer 801 may transmit or receive information used by the MAC layer 802 over one or more air interfaces. The PHY layer 801 may further perform link adaptation or adaptive modulation and coding (AMC), power control, cell search (e.g., for initial synchronization and handover purposes), and other measurements used by higher layers, such as the RRC layer 805. The PHY layer 801 may still further perform error detection on the transport channels, forward error correction (FEC) coding / decoding of the transport channels, modulation / demodulation of physical channels, interleaving, rate matching, mapping onto physical channels, and Multiple Input Multiple Output (MIMO) antenna processing.

[0127] The MAC layer 802 may perform mapping between logical channels and transport channels, multiplexing of MAC service data units (SDUs) from one or more logical channels onto transport blocks (TB) to be delivered to PHY via transport channels, de-multiplexing MAC SDUs to one or more logical channels from transport blocks (TB) delivered from the PHY via transport channels, multiplexing MAC SDUs onto TBs, scheduling informationClient Ref. No. P70047W01 reporting, error correction through hybrid automatic repeat request (HARQ), and logical channel prioritization.

[0128] The RLC layer 803 may operate in a plurality of modes of operation, including: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). The RLC layer 803 may execute transfer of upper layer protocol data units (PDUs), error correction through automatic repeat request (ARQ) for AM data transfers, and concatenation, segmentation and reassembly of RLC SDUs for UM and AM data transfers. The RLC layer 803 may also execute re-segmentation of RLC data PDUs for AM data transfers, reorder RLC data PDUs for UM and AM data transfers, detect duplicate data for UM and AM data transfers, discard RLC SDUs for UM and AM data transfers, detect protocol errors for AM data transfers, and perform RLC re-establishment.

[0129] The PDCP layer 804 may execute header compression and decompression of IP data, maintain PDCP Sequence Numbers (SNs), perform in-sequence delivery of upper layer PDUs at re-establishment of lower layers, eliminate duplicates of lower layer SDUs at re-establishment of lower layers for radio bearers mapped on RLC AM, cipher and decipher control plane data, perform integrity protection and integrity verification of control plane data, control timer-based discard of data, and perform security operations (e.g., ciphering, deciphering, integrity protection, integrity verification, etc.).

[0130] The main services and functions of the RRC layer 805 may include broadcast of system information (e.g., included in Master Information Blocks (MIBs) or System Information Blocks (SIBs) related to the non-access stratum (NAS)), broadcast of system information related to the access stratum (AS), paging, establishment, maintenance and release of an RRC connection between the UE and E-UTRAN (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), establishment, configuration, maintenance and release of point to point Radio Bearers, security functions including key management, inter radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting. Said MIBs and SIBs may comprise one or more information elements (lEs), which may each comprise individual data fields or data structures.

[0131] The UE 106 and the RAN node with base stationl 02A may utilize a Uu interface (e.g., an LTE-Uu interface) to exchange control plane data via a protocol stack comprising the PHY layer 801 , the MAC layer 802, the RLC layer 803, the PDCP layer 804, and the RRC layer 805.Client Ref. No. P70047W01

[0132] The non-access stratum (NAS) protocols 806 form the highest stratum of the control plane between the LIE 601 and the MME 621 . The NAS protocols 806 support the mobility of the LIE 601 and the session management procedures to establish and maintain IP connectivity between the UE 601 and the P-GW 623.

[0133] The S1 Application Protocol (S1 -AP) layer 815 may support the functions of the S1 interface and comprise Elementary Procedures (EPs). An EP is a unit of interaction between the RAN node with base station 102A and the CN 1020. The S1 -AP layer services may comprise two groups: UE-associated services and non UE-associated services. These services perform functions including, but not limited to: E-UTRAN Radio Access Bearer (E- RAB) management, UE capability indication, mobility, NAS signaling transport, RAN Information Management (RIM), and configuration transfer.

[0134] The Stream Control Transmission Protocol (SCTP) layer (alternatively referred to as the SCTP / IP layer) 814 may ensure reliable delivery of signaling messages between the RAN node with base station 102A and the MME 621 based, in part, on the IP protocol, supported by the IP layer 813. The L2 layer 812 and the L1 layer 811 may refer to communication links (e.g., wired or wireless) used by the RAN node and the MME to exchange information.

[0135] The RAN node with base station 102A and the MME 621 may utilize an S1 -MME interface to exchange control plane data via a protocol stack comprising the L1 layer 81 1 , the L2 layer 812, the IP layer 813, the SCTP layer 814, and the S1 -AP layer 815.FIG. 9: User Plane Protocol Stack

[0136] FIG. 9 is an illustration of an example of a user plane protocol stack in accordance with some embodiments. In this embodiment, a user plane 900 is shown as a communications protocol stack between the UE 106A (or alternatively, the UE 106B or 106N), the RAN node with base station 102A (or alternatively, the RAN node with base station 102B), the S-GW 622, and the P-GW 623. The user plane 900 may utilize at least some of the same protocol layers as the control plane 800. For example, the UE 601 and the RAN node with base station 102A may utilize a Uu interface (e.g., an LTE-Uu interface) to exchange user plane data via a protocol stack comprising the PHY layer 801 , the MAC layer 802, the RLC layer 803, the PDCP layer 804.

[0137] The General Packet Radio Service (GPRS) Tunneling Protocol for the user plane (GTP-U) layer 904 may be used for carrying user data within the GPRS core network andClient Ref. No. P70047W01 between the radio access network and the core network. The user data transported can be packets in any of IPv4, IPv6, or PPP formats, for example. The UDP and IP security (LIDP / IP) layer 903 may provide checksums for data integrity, port numbers for addressing different functions at the source and destination, and encryption and authentication on the selected data flows. The RAN node with base station 102A and the S-GW 622 may utilize an S1 -U interface to exchange user plane data via a protocol stack comprising the L1 layer 81 1 , the L2 layer 812, the UDP / IP layer 903, and the GTP-U layer 904. The S-GW 622 and the P-GW 623 may utilize an S5 / S8a interface to exchange user plane data via a protocol stack comprising the L1 layer 81 1 , the L2 layer 812, the UDP / IP layer 903, and the GTP-U layer 904. As discussed above with respect to FIG. 8, NAS protocols support the mobility of the UE 106 and the session management procedures to establish and maintain IP 813 connectivity between the UE 106 and the P-GW 623.FIG. 10: Core Network

[0138] FIG. 10 illustrates an example architecture of a system 1000 including a core network (CN) 1020 in accordance with various embodiments. The CN 1020 may be a core network for a 5G System (which may be referred to as a 5GC) or 6G system. The system 1000 is shown to include a UE 1001 , which may be the same or similar to the UEs 106A, 106B, or 106N discussed previously; a (R)AN 1010, which may be the same or similar to the BSs 102A or 102N discussed previously; and a data network (DN) 1003, which may be, for example, operator services, Internet access, or 3rd party services; and a CN 1020. The CN 1020 can be the network 100 as discussed previously. The CN 1020 may include a number of network functions including an Authentication Server Function (AUSF) 1022; an Access and Mobility Management Function (AMF) 1021 ; a Session Management Function (SMF) 1024; a Network Exposure Function (NEF) 1023; a Policy Control Function (PCF) 1026; a Network Repository Function (NRF) 1025; a Unified Data Management (UDM) 1027; an Application Function (AF) 1028; a User Plane Function (UPF) 1002; and a Network Slice Selection Function (NSSF) 1029. These network functions may be implemented, in some cases, as virtualized software-based functions / services.

[0139] The UPF 1002 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 1003, 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 1002 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane part of policy rules,Client Ref. No. P70047W01 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 1002 may include an uplink classifier to support routing traffic flows to a data network, The DN 1003 may represent various network operator services, Internet access, or third-party services. DN 1003 may include, or be similar to, application server 104 discussed previously. The UPF 1002 may interact with the SMF 1024 via an N4 reference point between the SMF 1024 and the UPF 1002.

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

[0141] The AMF 1021 may be responsible for registration management (e.g., for registering UE 1001 , etc.), connection management, reachability management, mobility management, and lawful interception of AMF-related events, and access authentication and authorization. The AMF 1021 may be a termination point for an N11 reference point between the AMF 1021 and the SMF 1024. The AMF 1021 may provide transport for SM messages between the UE 1001 and the SMF 1024, and act as a transparent proxy for routing SM messages. AMF 1021 may also provide transport for Short Message Service (SMS) messages between UE 1001 and an SMSF (not shown by FIG. 10). AMF 1021 may act as a security anchor function (SEAF), which may include interaction with the AUSF 1022 and the UE 1001 , receipt of an intermediate key that was established as a result of the UE 1001 authentication process. Where Universal Subscriber Identity Module (USIM) based authentication is used, the AMF 1021 may retrieve the security material from the AUSF 1022. AMF 1021 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 1021 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 1010 and the AMF 1021 ; and the AMF 1021 may be a termination point of NAS (Nl) signaling and perform NAS ciphering and integrity protection.Client Ref. No. P70047W01

[0142] AMF 1021 may also support NAS signaling with a LIE 1001 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 1010 and the AMF 1021 for the control plane and may be a termination point for the N3 reference point between the (R)AN 1010 and the UPF 1002 for the user plane. As such, the AMF 1021 may handle N2 signaling from the SMF 1024 and the AMF 1021 for PDll 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 1001 and AMF 1021 via an N1 reference point between the UE 1001 and the AMF 1021 , and relay uplink and downlink user-plane packets between the UE 1001 and UPF 1002. The N3IWF also provides mechanisms for internet protocol security (IPsec) tunnel establishment with the UE 1001 . The AMF 1021 may exhibit an Namf service based interface and may be a termination point for an N14 reference point between two AMFs 1021 and an N17 reference point between the AMF 1021 and a 5G Equipment Identity Register (5G-EIR) (not shown by FIG. 10).

[0143] The UE 1001 may need to register with the AMF 1021 in order to receive network services. Registration Management (RM) is used to register or deregister the UE 1001 with the network (e.g., AMF 1021 ), and establish a UE context in the network (e.g., AMF 1021 ). The UE 1001 may operate in an RM-REGISTERED state or an RM-DEREGISTERED state. In the RM-DEREGISTERED state, the UE 1001 is not registered with the network, and the UE context in AMF 1021 holds no valid location or routing information for the UE 1001 so the UE 1001 is not reachable by the AMF 1021. In the RM REGISTERED state, the UE 1001 is registered with the network, and the UE context in AMF 1021 may hold a valid location or routing information for the UE 1001 so the UE 1001 is reachable by the AMF 1021 . In the RM-REGISTERED state, the UE 1001 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 1001 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.

[0144] The AMF 1021 may store one or more RM contexts for the UE 1001 , 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 stateClient Ref. No. P70047W01 per access type and the periodic update timer. The AMF 1021 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 1021 may store a CE mode B Restriction parameter of the UE 1001 in an associated MM context or registration management (RM) context. The AMF 1021 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).

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

[0146] The SMF 1024 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 UEClient Ref. No. P70047W011001 and a data network (DN) 1003 identified by a Data Network Name (DNN). PDU sessions may be established upon UE 1001 request, modified upon UE 1001 and CN 1020 request, and released upon UE 1001 and CN 1020 request using NAS SM signaling exchanged over the N1 reference point between the UE 1001 and the SMF 1024. Upon request from an application server, the CN 1020 may trigger a specific application in the UE 1001. In response to receipt of the trigger message, the UE 1001 may pass the trigger message (or relevant parts / information of the trigger message) to one or more identified applications in the UE 1001 . The identified application(s) in the UE 1001 may establish a PDU session to a specific data network name (DNN). The SMF 1024 may check whether the UE 1001 requests are compliant with user subscription information associated with the UE 1001. In this regard, the SMF 1024 may retrieve and / or request to receive update notifications on SMF 1024 level subscription data from the UDM 1027.

[0147] The SMF 1024 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 1024 may be included in the system 1000, which may be between another SMF 1024 in a visited network and the SMF 1024 in the home network in roaming scenarios. Additionally, the SMF 1024 may exhibit the Nsmf service-based interface.

[0148] The NEF 1023 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 1028), edge computing or fog computing systems, etc. In such embodiments, the NEF 1023 may authenticate, authorize, and / or throttle the AFS. NEF 1023 may also translate information exchanged with the AF 1028 and information exchanged with internal network functions. For example, the NEF 1023 may translate between an AF-Service-ldentifier and an internal SCC information. NEF 1023 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 1023 as structured data, or at a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF 1023 to other NFs and AFs, and / or used for other purposes such as analytics. Additionally, the NEF 1023 may exhibit an Nnef service-based interface.

[0149] The NRF 1025 may support service discovery functions, receive NF discovery requests from NF instances, and provide the information of the discovered NF instances toClient Ref. No. P70047W01 the NF instances. NRF 1025 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 1025 may exhibit the Nnrf service-based interface.

[0150] The PCF 1026 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 1026 may also implement a front end (FE) to access subscription information relevant for policy decisions in a UDR of the UDM 1027. The PCF 1026 may communicate with the AMF 1021 via an N15 reference point between the PCF 1026 and the AMF 1021 , which may include a PCF 1026 in a visited network and the AMF 1021 in case of roaming scenarios. The PCF 1026 may communicate with the AF 1028 via an NS reference point between the PCF 1026 and the AF 1028; and with the SMF 1024 via an N7 reference point between the PCF 1026 and the SMF 1024, The system 1000 and / or CN 1020 may also include an N24 reference point between the PCF 1026 (in the home network) and a PCF 1026 in a visited network, Additionally, the PCF 1026 may exhibit an Npcf service-based interface.

[0151] The UDM 1027 may handle subscription-related information to support the network entities' handling of communication sessions and may store subscription data of UE 1001 . For example, subscription data may be communicated between the UDM 1027 and the AMF 1021 via an NS reference point between the UDM 1027 and the AMF. The UDM 1027 may include two parts, an application FE and a UDR (the FE and UDR are not shown by FIG. 10). The UDR may store subscription data and policy data for the UDM 1027 and the PCF 1026, and / or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 1001 ) for the NEF 1023. The Nadr service-based interface may be exhibited by the UDR to allow the UDM 1027, PCF 1026, and NEF 1023 to access a particular set of the stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notification of relevant data changes in the UDR. The UDM may include a UDM-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 UDM-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 1024 via an NI0 reference point between the UDM 1027 and the SMF 1024. UDM 1027 may alsoClient Ref. No. P70047W01 support SMS management, wherein an SMS-FE implements the similar application logic as discussed previously. Additionally, the UDM 1027 may exhibit the Nudm service based interface.

[0152] The AF 1028 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 1020 and AF 1028 to provide information to each other via NEF 1023, 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 1001 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 1002 close to the UE 1001 and execute traffic steering from the UPF 1002 to DN 1003 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 1028. In this way, the AF 1028 may influence UPF (re)selection and traffic routing. Based on operator deployment, when AF 1028 is considered to be a trusted entity, the network operator may permit AF 1028 to interact directly with relevant NFs. Additionally, the AF 1028 may exhibit an Naf service-based interface.

[0153] The NSSF 1029 may select a set of network slice instances serving the UE 1001 . The NSSF 1029 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 1029 may also determine the AMF set to be used to serve the UE 1001 , or a list of candidate AMF(s) 1021 based on a suitable configuration and possibly by querying the NRF 1025. The selection of a set of network slice instances for the UE 1001 may be triggered by the AMF 1021 with which the UE 1001 is registered by interacting with the NSSF 1029, which may lead to a change of AMF 1021. The NSSF 1029 may interact with the AMF 1021 via an N22 reference point between AMF 1021 and NSSF 1029; and may communicate with another NSSF 1029 in a visited network via an N31 reference point (not shown by FIG. 10). Additionally, the NSSF 1029 may exhibit an Nnssf service-based interface.

[0154] As discussed previously, the CN 1020 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 1001 to / from other entities, such as an SMS- GMSC / IWMSC / SMS-router. The SMS may also interact with AMF 1021 and UDM 1027 for a notification procedure that the UE 1001 is available for SMS transfer (e.g., set a UE notClient Ref. No. P70047W01 reachable flag, and notifying UDM 1027 when UE 1001 is available for SMS).

[0155] The CN 1020 may also include other elements that are not shown by FIG. 10, 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. 10), 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. 10). 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, message filtering, and policing on inter-PLMN control plane interfaces.

[0156] Additionally, there may be many more reference points and / or service-based interfaces between the NF services in the NFs; however, these interfaces and reference points have been omitted from FIG. 10 for clarity. In one example, the CN 1020 may include an Nx interface, which is an inter-CN interface between a mobility management entity (MME) and the AMF 1021 in order to enable interworking between CN 1020 and a CN in a 4G system and 6G 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.FIG. 1 1 : Bandwidth Parts in 5G-NR

[0157] With each new generation of wireless communication, more bandwidth has been provided to enable faster communication. 5G-NR was no exception. In 3GPP 4G, the maximum available bandwidth of a signal was 20 megahertz (MHz). With the introduction of 3GPP 5G NR, the broadest bandwidth was increased to 400 MHz per carrier. This allows the transmission of very high data rates to allow large files to be communicated with 5G in short periods of time.

[0158] However, the use of broad bandwidth does not come without a cost. As bandwidth increases, the amount of power and signal processing at a UE also increases.Client Ref. No. P70047W01With the advent of very broad bandwidth in 5G-NR, it could result in could result in power drain and processing levels at a LIE that would rapidly drain a typical UE’s battery.

[0159] To reduce the amount of power and processing in a UE configured to support 3GPP 5G NR, the specification was designed to allow a UE to use less than the available bandwidth in a channel. The term “bandwidth part”, with the acronym BWP was coined in the 3GPP 5G NR specification to refer to a selected portion of the available bandwidth that a UE can use to communicate when the amount of data for transmission or reception does not need the entire available bandwidth.

[0160] A Bandwidth Part (BWP) in the 3GPP NR release 15 specification, and the following releases 16-19, is a contiguous set of physical resource blocks (PRBs) on a given carrier. These PRBs are selected from a contiguous subset of the common resource blocks for a given numerology (u). Each BWP defined for a numerology can have the following three parameters: subcarrier spacing, symbol duration, and cyclic prefix (CP) length.

[0161] FIG. 1 1 illustrates an example block diagram showing three different bandwidth parts, in accordance with some embodiments. In this example, each bandwidth part has a different subcarrier spacing (SCS). BWP#1 has an SCS (Af) of 30 kHz. BWP#2 has an SCS of 15 kHz. And BWP#3, in frequency range 2 (FR2), has an SCS of 60 kHz. Each of the BWPs include 14 symbols per slot. Each RB has 12 subcarriers.

[0162] In 3GPP 5G NR, a UE can be configured up to 4 uplink (UL) and 4 downlink (DL) BWPs on a serving cell. Only one UL and one DL BWP can be active at a given time. UEs are expected to receive and transmit only within the frequency range configured for the active UL and DL BWPs with the associated numerologies. Some exceptions for this include the UE performing Radio Resource Management (RRM) measurements or transmitting a sounding reference signal (SRS) outside of its active BWP during a measurement gap, when data is not transmitted or received at the UE.FIG. 12: Transmit-Receive Operation in 5G and 6G

[0163] As used herein, the term “Tx-Rx operation”, or “TRO” is used in place of the term “bandwidth part”, or “BWP”, as coined for 3GPP 5G. A TRO can be considered synonymous with a BWP. However, a TRO can be configured for 6G communications in ways that are not currently specified for 3GPP 5G communications in 3GPP Release 19 and earlier releases.Client Ref. No. P70047W01

[0164] FIG. 12 provides an example illustration of transmit-receive operations (TRO) used for 5G and 6G communication, in accordance with some embodiments. There are four types of Tx-Rx operations (TROs): an initial TRO (for initial access), a first active TRO, a default TRO, and a dedicated TRO. The initial TRO for a UE occurs during the initial access until the UE is explicitly configured with a TRO during or after a radio resource control (RRC) connection establishment. The initial active TRO is the default TRO, unless configured otherwise.

[0165] TRO switching involves activating a TRO and deactivating a current active TRO. TRO switching can be activated using downlink control information (DCI) or RRC signaling. TRO switching can also be based on an inactivity timer (2-150ms), shown at operation (1 ) in FIG. 12 which triggers if there is no active data transmission. At operation (2), the TRO inactivity timer expires, and the TRO switch timer starts at operation (3). The TRO switch timer expires at operation (4) and the TRO switch is executed to a different TRO at operation (5).

[0166] There is also TRO switching delay to allow a device to switch configuration from one TRO to another during which there is no UL / DL transmission.

[0167] In time division duplex (TDD) systems, TROs are paired for UL and DL transmission. A decision on UL Tx-Rx operation impacts DL Tx-Rx operations. In frequency division duplex (FDD) systems, Tx-Rx operations for UL and DL can be switched independently. It is assumed that the same requirement will be maintained in 6G communications.

[0168] There is a trade-off between power efficiency, throughput and latency when using TROs. In a policy dependent TRO optimization, a power efficiency with throughput maximizing policy can be achieved if a device is operating in TRO which has larger bandwidth in a short period of time to transmit a given amount of data.

[0169] For TDD and FDD systems, a device may wait a little longer to activate a TRO with a large bandwidth to utilize Tx-Rx operation more efficiently.

[0170] For a TDD system, a device (e.g. UE) may switch to a default TRO later if there is large uncertainty in data arrival or the device may switch to a default TRO earlier if a probability of large data arrival is low, or it is expected that a default TRO is sufficient for the remaining data transmission.

[0171] A device may switch to a medium size TRO (average data rate) if there is large variation in data arrival profile to better utilize the available BW.Client Ref. No. P70047W01

[0172] In contrast to the throughput maximizing policy, a power efficiency with latency minimizing policy can be achieved if a device is operating in a Tx-Rx operation which satisfies packet delay budget.

[0173] For TDD and FDD systems, the device may accumulate data in the buffer until packet delay budget and send the UL packets in an appropriate Tx-Rx operation. The device may switch to a TRO with a higher numerology to reduce data transmission scheduling while buffering enhanced mobile broadband (eMBB) traffic.

[0174] For a TDD system, a device may activate a TRO periodically to match with a data arrival profile. The device may switch to a default TRO later in time under the given packet arrival uncertainty.

[0175] For a power saving policy only, for a TDD system, a device may proactively send an optimized inactivity timer to the network (NW). The device may request for early termination of a current TRO or an extension of a current TRO.FIG. 13, 14: TRO switching for high throughout and low latency communication

[0176] FIG. 13 is an example illustration of TRO switching for UL data communication to provide high throughput and low latency traffic that is prioritized by a UE 106, in accordance with some embodiments. In this example, different TRO are used with different bandwidth and potentially different subcarrier spacing. One TRO may have a larger bandwidth and a selected subcarrier spacing to provide high throughput. The UE can prioritize the high throughput by selecting the TRO with the larger bandwidth and SOS when there is a large amount of uplink data to transmit. When the amount of UL data is less, but the latency requirements are low, the UE can prioritize a TRO with a smaller bandwidth that can provide lower latency UL communication. Selecting an SOS with a higher numerology can be used by the UE to provide power savings. The power savings policy can be due to the bandwidth size quantization via delaying data traffic to fit to an expected data rate and improve resource utilization, as shown in FIG. 13.

[0177] FIG. 14 is an example illustration of UE TRO switching in UL data communication to reduce physical downlink control channel monitoring and switching delay, in accordance with some embodiments. As shown in FIG. 14, a default TRO with a relatively low bandwidth (BW1 ), and a second TRO with a high bandwidth (BW) relative to BW1 , and be used to decrease switching delay, which can have an impact on latency and throughput. The predicted operation bandwidth selection and predicted time can be used to reduce switchingClient Ref. No. P70047W01 time. By reducing inactivity time, unnecessary PDCCH monitoring in the large bandwidth is reduced.

[0178] There is strong interest in NW-LIE coordinated energy saving in 3GPP. In some embodiments, A UE can send a preferred TRO to the NW and the NW can configure a TRO for a UE while considering the UE’s preference.

[0179] However, TRO switching can impact latency, throughput and device power consumption. This is true in particular at a low traffic load and when there is frequent TRO switching.

[0180] Existing solutions focus on NW centric solutions which configure all UEs with a fixed TRO configuration. The optimization over TRO adaptation and switching is done with only NW side information.

[0181] The existing solutions don’t utilize UE preference over power, latency, throughput, key performance indicators (KPIs), and an UL data traffic profile that is available at the UE side. Without UE side information, TRO adaptation and switching can be sub-optimal.

[0182] Fixed data traffic independent TRO adaptation can have an impact on one or many of the above metrics. Communicating and / or monitoring a physical downlink control channel (PDCCH) over a large bandwidth in DL for longer than necessary increases power consumption at the UE. Communicating over a smaller bandwidth may be beneficial for power saving but may have an impact on latency and throughput due to limited resource availability. Communicating over a large subcarrier spacing (SCS) can be beneficial for low latency traffic, but it increases power consumption due to higher clock speeds and other factors.

[0183] To provide NW-UE coordinated energy savings while optimizing TRO switching, the system can be configured to focus on either variable bandwidth size and / or the SCS aspect of the TRO configuration as simplification is expected in TRO operation in 6G.

[0184] All configurations regarding TRO (bandwidth size / SCS) are currently performed by the NW. The UE is given multiple TRO and selects one option and the time of switching of Tx-Rx operation.

[0185] Two cases are considered: paired UL / DL TROs and asymmetric UL / DL traffic, and unpaired UL / DL TROs.

[0186] In some embodiments, based on the UL data volume, traffic type, data arrival profile, the NW can prioritize some UEs for scheduling proactively and the NW can indicateClient Ref. No. P70047W01 the priority to the UE, either dynamically or semi-statically. The NW can configure a subset of M out of the N TROs that a UE is allowed to select and a switching time, where M and N are positive integers and M < N. The UE can send a preferred BW / SCS (TRO) and related configurations proactively according to the UE’s UL data traffic profile.

[0187] The UE can send an optimal TRO index, the UE's best activation / deactivation time of the TRO, and optimized bandwidth / SCS choice predictions. The UE and NW can communicate over the TRO selected by the UE for the time and duration that the UE had decided.

[0188] In 3GPP Technical Report (TR) 38.840, a study was performed for a to UE send a preferred TRO to the NW. The NW can then configure a TRO considering the UE’s preference as outlined:1 . When a UE knows the total size of a file to download I upload, it can estimate power efficient TRO sizes.2. The UE can indicate its preferred TRO configuration to a next generation Node B (gNB).3. The gNB can configure the UE with the TRO which was determined based on the UE’s recommendation.4. The file transfer can occur with the configured TRO.5. TRO switching and DRX operation are enabled.

[0189] However, there are several issues with the above proposal. It is a reactive solution which limits the procedure when the UE knows the total size of the file to download / upload. The use case is limited to very slow time scale, large file uploads and downloads. The UE only indicates a preferred TRO index which still has issues regarding a TRO inactive timer, and a switching time of the TRO.FIGs. 15-17: Power Efficiency by UE centric TRO

[0190] To overcome the limitations disclosed in the preceding paragraphs, in one example, Artificial Intelligence / Machine Learning can be used to predict finer granularity packet sizes and indicate a TRO proactively to the NW 100 for latency sensitive applications. A UE can indicate a TRO switching time to the NW. This improves inefficiencies due to the inactive timer and the TRO switching time. The inactivity timer andClient Ref. No. P70047W01 default TRO concepts in 5G can be removed in some cases. The UE can know its priority of scheduling in a TRO. In some cases, the UE may have dedicated resources per TRO per scheduling. The UE is more informed about radio resources than the NW, which enables the UE to make a more informed decision.

[0191] FIG. 15 illustrates an example process 1500 for power efficiency by a UE centric dynamic TRO, in accordance with some embodiments. In a first operation 1510, the UE 106 can receive a dynamic scheduling priority indication from the network via a base station 102 configured as a serving cell for the UE. For latency sensitive applications, there can be concerns regarding resource availability in which case even if a UE can switch to a new TRO quickly, it makes no difference in terms of traffic latency if the base station does not schedule any resource on the new TRO anyway. The NW 100 can prioritize UEs proactively for scheduling so that when the UE 102 requests for TRO switching, the resources are available for data transmission within some delay constraints. Resource prioritization can be either over dedicated resources for the UE or over shared resources for the UE with priority indications.

[0192] In a second operation 1520, the UE can receive an RRC reconfiguration message in which the NW 100 configures the UE with two or more TRO configurations. In one embodiment, there are N TROs in total. The NW can configure a subset of M out of the N TROs that the UE is allowed to switch to. For the other N-M TROs, they can still be under NW control and the UE cannot switch to them by itself. Accordingly, out of the N total TRO configurations, there are M TRO configurations that the UE can switch to, and N-M additional TROs that the network can instruct the UE to switch to. In one embodiment, the UE can receive information from the NW with available radio resources per TRO. Tx-Rx operation can be configured with a subset of options, such as periodicity of selection, in advance reporting options by the UE, and other additional options. TRO Configurations may include traffic types, conditions for activation of this feature, models, run-time, activation / deactivation cases, and other desired configurations. In one embodiment, a UE may learn provisioned KPIs through exploration of various Tx-Rx operation (e.g., contextual bandwidth, etc.), by requesting on-demand Tx-Rx operation provisioning from the NW and historical Tx-Rx operation KPIs.

[0193] In a third operation 1530, the UE 106 can select an appropriate TRO according to UL data traffic and based on the UE’s preference. The information regarding the selected TRO can be sent to the network, via the serving cell, using a MAC-CE, RRC communication, or uplink control information (UCI). In this example, the UE can inform the NW 100Client Ref. No. P70047W01 proactively of the UE’s selected Tx-Rx operation. Upon reception of selected TRO, the NW can evaluate the selected Tx-Rx operation. It should be noted that proactive signaling (10- 20ms early) is essential to allow the NW to have enough time to process input from the UE and send acknowledgement / non-acknowledgement (ACK / NACK) messages to the UE before a TRO switching event.

[0194] In a fourth operation 1540, the UE can send a TRO selection switching time to the NW 100. The UE may send an ordered list of TRO selection in terms of a preference. In a fifth operation 1550, the UE may then receive ACK / NACK from the NW or a new TRO configuration. The NW may send an ACK with the following options: (1 ) the NW may configure another TRO for the UE in response to the UE selected Tx-Rx operation; (2) the NW may send updated configuration information or conditions for a UE centric TRO selection; or (3) the NW may send an updated time of TRO switching. The NW may send a NACK message, if resources are not available for the TRO suggested by the UE, due to resource constraints. In a sixth operation 1560, the UE can switch to the selected TRO at the switching time. The base station 1021 network 100 can also switch to the selected TRO at the switching time. In a seventh operation 1570, the UE and base station can communicate data over the selected TRO. The UE and base station may also communicate control information over the selected TRO.

[0195] FIG. 16 provides an example illustration of an artificial intelligence / machine learning (AI / ML) model 1600 for classification and regression of a TRO selection (classification) and a TRO switch time (regression), in accordance with some embodiments. In some embodiments, the UE 106 can be configured to operate the AI / ML model 1600 at the UE. Various inputs can be used to train the AI / ML model 1600 to output an inference of a TRO selection, and a TRO switch time for the UE 106 and NW 100 to switch to the new TRO. Example inputs include, but are not limited to: historical NACK information for a TRO, packet arrival time, packet length, flow (source, destination IP and Port number, logical channel group), traffic type, embedded preference vector (latency, throughput, power saving), quality of service (QoS) flow requirement, historical KPIs per TRO, and a base station allowed TRO list and constraints. The AI / ML model 1600 may be trained at the UE based on UE centric information. Alternatively, the AI / ML model 1600 may be trained at the network or at a server 104, such as an edge server. Information from the UE 106 can be sent to the network or the server 104 for use in training the AI / ML model 1600.

[0196] The behavior of UE centric TRO selection based on the AI / ML model 1600 may be dynamically activated or de-activated by the NW 100. When the NW sends a dynamicClient Ref. No. P70047W01 signal to the UE to deactivate the AI / ML model based TRO setting selection, the UE 106 may: fallback to the default TRO settings; or continue with settings before such a command is received. The UE can send a UE capability message to the NW regarding the UE’s AI / ML capability for UE centric dynamic TRO selection. The UE can be configured for this feature for a particular logical channel. The NW and UE can monitor the AI / ML prediction accuracy or beam failure. If the NW observes that there is another TRO with a better KPI, the NW can reconfigure the UE with the new TRO. If the UE observes that predicted traffic volume or KPIs are less than expected, the UE can terminate this procedure and fall back to a default setup.

[0197] The UE centric TRO selection based on the AI / ML model 1600 can be trained to output a TRO selection for the UE and a TRO switch time. As previously discussed, the UE 106 can send the TRO selection and TRO switch time from the AI / ML model to the NW 100.

[0198] FIG. 17 provides an example illustration of a flow chart for a method 1700 of selecting an active transmit-receive operation (TRO) at a user equipment (UE), according to some embodiments. In a first operation 1710 the UE 106 can receive, from a network (100), a scheduling priority for a plurality of TRO. A selected TRO from the plurality of TROs can be identified at the UE, as shown in block 1720. A start time for the selected TRO can be determined at the UE, as shown in block 1730. The start time for the TRO can be sent from the UE to the network, as shown in block 1740. The UE can switch to the selected TRO at the start time, as shown in block 1750. The UE can communicate with the network over the selected TRO until a new TRO is triggered, as shown in block 1760.

[0199] In some embodiments, a method of selecting an active transmit-receive operation (TRO) at a user equipment (UE) 106 is disclosed. The method comprises receiving, from a network, a scheduling priority for a plurality of N TROs, where N is a positive integer. The UE can identify a selected TRO from the plurality of N TROs. The UE can determine a start time for the selected TRO. The start time can be sent from the UE to the network 100, via a base station 102. The UE can switch to the selected TRO at the start time. The network can switch to the selected TRO at approximately the same time as the UE. The UE can then communicate with the network over the selected TRO.

[0200] In some embodiments, the UE 106 can receive, from the network 100, configuration information for a subset of M of the plurality of N TROs that the UE is allowed to switch to, where M is a positive integer and M < N. The UE can identify the selected TRO from the M TROs. In one embodiment, the UE is not able to switch to N-M TROs and the UE is configured to receive switching instructions from the network for the N-M TROs.Client Ref. No. P70047W01

[0201] In some embodiments, the UE can identify the selected TRO from the plurality of TROs based on one or more of: a packet arrival time in uplink data traffic; a packet length in the uplink data traffic; a source destination internet protocol address and port number in the uplink data traffic; a traffic type in the uplink data traffic; or an embedded preference vector comprising weighted values denoting an importance of latency, throughput, and power savings for the selected TRO.

[0202] In some embodiments, the UE can identify the selected TRO from the plurality of N TROs based on an inference from an inference of an artificial intelligence I machine learning (AI / ML) model. The AI / ML model can be trained with one or more inputs comprising: historical non-acknowledgement (NACK) information; a packet arrival time; a packet length; data flow comprising one or more of a source, a destination internet protocol address and a port number, or a logical channel group; a traffic type; an embedded preference vector comprising weighted values denoting an importance of latency, throughput, and power savings for the selected TRO; a quality of service (QoS) flow requirement; historical key performance indicators (KPIs) per TRO; or base station allowed TRO list and constraints.

[0203] In some embodiments, the UE can communicate with the network over the selected TRO until a new TRO is triggered. The UE can receive configuration information from the network for two or more TRO configurations via radio resource control (RRC) communications.FIGs. 18-19: UE Centric Adaptive Tx-Rx Configuration Selection

[0204] FIG. 18 provides an example illustration of a communication 1800 between a UE and a serving cell (e.g. base station) for a UE centric adaptive TRO configuration selection, in accordance with some embodiments. In a first operation 1810, a network can send two or more TRO configurations to a UE. In one embodiment, the TRO configurations can be sent from the network to the UE via an RRC reconfiguration message sent from the serving cell to the UE. The network can preconfigure at least an inactive timer, a default TRO, a subcarrier spacing (SCS), and a bandwidth. The network can configure a pool of configuration options, including an inactivity timer, a default TRO, an SCS, or a bandwidth size. The UE can be configured with a subset of configuration options, such as a periodicity of a TRO, and advance reporting options.

[0205] In a second operation 1820 of the communication 1800, the UE can identify aClient Ref. No. P70047W01TRO configuration at the UE. The TRO configuration can be based on UL data traffic and UE preference. In a third operation 1830, the UE can send the TRO configuration selected by the UE to the network. The TRO configuration selection may be sent from the UE to the network using a layer 1 or layer 2 communication, such as a MAC-CE communication. In various options, the UE may send to the network: an optimized TRO inactivity timer duration; and parameters of TRO adaptation, such as a preferred SCS and bandwidth size. The UE may request from the network one or more of: a new default TRO; a periodic TRO switching pattern depending on a data traffic profile; a request for extension of a current TRO, or a request for an early termination of a current TRO.

[0206] In a fourth operation 1840, the UE can receive an ACK / NACK from the network. If the network accepts the TRO configuration received from the UE, the network can send an ACK to the UE. If the network does not accept the TRO configuration from the UE, the network can send a NACK to the UE. When a NACK is sent, the network may configure another TRO in response to the UE selected TRO configuration selection. The NW may also configure the UE with another TRO configuration based on NW information. The NW may send a time duration in which the UE is allowed to send another TRO configuration selection.

[0207] In a fifth and sixth operation, the UE can switch 1850 and the network can switch 1860 to the TRO configuration received from the UE. In a seventh operation, the UE and network can communicate over the TRO configuration received from the UE 1870.

[0208] A behavior of a UE centric TRO configuration selection based on an AI / ML, such as AI / ML model 1600, may be dynamically activated or deactivated by the network 100. When the network sends a dynamic signal to deactivate an AI / ML based TRO configuration selection, the UE can: fallback to default settings; or continue with settings before such a command is received. The UE can indicate capability to the NW regarding the UE’s ability to make an AI / ML based TRO configuration selection. The UE can indicate its preference on whether the AI / ML based TRO configuration selection should be enabled using UE assistance information (UAI).

[0209] FIG. 19 provides an example flow chart of a method 1900 for selecting a transmitreceive operation (TRO) configuration at a UE, in accordance with some embodiments. The method comprises the operation 1910 receiving, at the UE, a plurality of configuration options for a TRO. A new TRO configuration is identified 1920 at the UE. The TRO configuration can be identified based on uplink data traffic information, including but not limited to one or more of: packet arrival time packet length, flow (source, destination IP, andClient Ref. No. P70047W01 port number), traffic type, or embedded preference vector (latency, throughput, and power savings). The UE can send 1930 the TRO configuration information selected by the UE to the network. The TRO configuration information sent by the network can include one or more of an inactivity timer, a default TRO, an SOS, or a bandwidth size. The UE can receive an ACK from the network. The UE can then switch 1940 to the selected TRO configuration based on the UE TRO configuration selection. The UE, via the serving cell, can then transmit data to the network on the selected TRO.

[0210] In some embodiments, a method of user equipment (UE) centric adaptive transmit-receive operation (TRO) configuration selection is disclosed. The method comprises: receiving, from a network, a pool of configuration options for one or more TROs; identifying a selected TRO configuration that is configured with one or more configurations from the pool of configuration options; sending the TRO configuration to the network; and switching to a selected TRO with the selected TRO configuration.

[0211] In some embodiments, the method further comprises receiving, from the network, the pool of configuration options for the one or more TROs comprising: an inactivity timer value; a default TRO configuration; a subcarrier spacing; a bandwidth size; or a carrier frequency.

[0212] In some embodiments, the method can further comprise identifying the selected TRO configuration from the pool of TRO configurations based on one or more of: a packet arrival time in uplink data traffic; a packet length in the uplink data traffic; a source destination internet protocol address and port number in the uplink data traffic; a traffic type in the uplink data traffic; or an embedded preference vector comprising weighted values denoting an importance of latency, throughput, and power savings for the selected TRO.

[0213] In some embodiments, the method can further comprise sending the TRO configuration to the network, wherein the TRO configuration comprises one or more of: an inactivity timer duration; or a default TRO configuration; or a preferred subcarrier spacing of the selected TRO; or a preferred bandwidth of the selected TRO; or a preferred carrier frequency of the selected TRO.

[0214] In some embodiments, the method can further comprise sending a request to the network for the selected TRO, the request comprising one or more of: a new default TRO configuration; a periodic TRO switching pattern; an extension of a current TRO; or an early termination of a current TRO.

[0215] In some embodiments, the method can further comprise receiving anClient Ref. No. P70047W01 acknowledgement / non-acknowledgement (ACK / NACK) from the network for the TRO configuration. The method can further comprise: receiving the ACK from the network to switch to the selected TRO with the selected TRO configuration; or receiving the NACK from the network when the network configures another TRO in response to the TRO configuration identified by the UE; or receiving the NACK from the network when the network configures the UE with another TRO configuration based on information at the network; or receiving the NACK from the network; and receiving a time duration from the network in which the UE is allowed to send another TRO configuration selection.

[0216] The method can further comprise identifying, at the UE, the selected TRO configuration from an inference of an artificial intelligence I machine learning (AI / ML) model. The AI / ML model can be trained with one or more inputs comprising: historical nonacknowledgement (NACK) information; a packet arrival time; a packet length; data flow comprising one or more of a source, a destination internet protocol address and a port number, or a logical channel group; a traffic type; an embedded preference vector comprising weighted values denoting an importance of latency, throughput, and power savings for the selected TRO; a quality of service (QoS) flow requirement; historical key performance indicators (KPIs) per TRO; or base station allowed TRO list and constraints.FIGS. 20-23: UE assisted NW Centric Dynamic TRO Adaptation

[0217] FIG. 20 illustrates an example of a UE assisted NW centric dynamic Transmit- Receive operation (TRO) adaptation procedure 2000, in accordance with some embodiments. In this example, the network 100 configures 2010 the UE with two or more TRO configurations.

[0218] The network 100 can then request for the UE to send preference options regarding the configured TROs. The UE can send 2020 a network preference vector in terms of throughput, latency, and power metrics. One TRO configuration can be a default configuration. The default configuration can be selected based on UE preferred optimization criteria such as power optimization first, latency minimization first, or throughput first. The vector may be weights between 0 and 1 showing which criteria should be emphasized relative to the others. For example, a vector [0.3, 0.5, 0.2] can be communicated to show an embedded or meta preference for latency, throughput, and power savings. This may be communicated using layer-1 or layer-2 communication, such as a MAC-CE.Client Ref. No. P70047W01

[0219] The UE 106 can send additional features such as expected traffic volume, and parameters such as power / latency / rate preference to the network for a network centric optimized TRO selection. The UE may send a more structured data arrival profile such as periodic / aperiodic information. The UE may send prioritized data traffic information. The UE may send a weight of UE and NW centric preference.

[0220] The UE 106 may send a modified buffer status report (BSR) or a BSR report with additional attributes to the network 100 to inform the network 100 about the TRO selection. When the UE has TRO X activated and the reported BSR is larger than a threshold then, TRO Y may be automatically activated by the UE and base station. The BSR report may include estimated future traffic volume from the UE.

[0221] The network can then select 2030 a TRO and its configurations for the UE based on the network preference vector using Layer 1 or Layer 2 signaling, such as a MAC-CE. The network can send 2040 a TRO configuration to the UE based on the network preference vector. The UE can switch 2050 and the network can switch 2060 to the selected TRO configuration. The UE can send 2070 data and control information to the network, via the serving cell, over a TRO based on the selected TRO configuration.

[0222] In some embodiments, the UE may deactivate a TRO adaptation received from the NW. For example, the UE may detect that an AI / ML model operating at the NW has a prediction accuracy is not good enough (e.g. below a threshold level). The UE can indicate a capability to the NW about this feature. The UE may indicate its preference on whether this feature should be enabled using UAL The UE can be configured for this feature for a particular logical channel.

[0223] FIG. 21 illustrates a flow chart of a method 2100 of network centric dynamic Tx- Rx operation (TRO) adaptation, in accordance with some embodiments. The method comprises sending 21 10, to a user equipment (UE) 106, one or more TRO configurations, and requesting UE preference information for the TROs. The network can receive TRO preference information from the UE. The TRO preference information comprises one or more of UL data traffic information (packet arrival time, a packet length), a flow (source, destination IP and Port number), a traffic type, or an embedded preference vector (latency, throughput, power saving)

[0224] The network 100 can identify 2120 a preference option from the UE preference information. The network can receive 2130 a preference vector from the UE. The network vector can comprise weighted values representing information such as latency, throughput,Client Ref. No. P70047W01 and power savings, e.g. [0.3, 0.5, 0.2], The method 2100 further comprises switching 2140 to the selected TRO at the network 100.

[0225] In some embodiments, a method of user equipment assisted network centric dynamic transmit-receive operation (TRO) adaptation is disclosed. The method comprises: sending, from the network, two or more TRO configurations to a user equipment (UE); sending, from the network, a request for TRO preference options from the UE; receiving, from the UE, the TRO preference options; identifying, at the network, a selected TRO configuration based on one or more of the TRO preference options received from the UE; sending a selected TRO configuration to the UE; switching to the selected TRO configuration; and receiving data from the UE on the selected TRO configuration.

[0226] In some embodiments, at least one of the two or more TRO configurations are a default TRO configuration for the UE.

[0227] In some embodiments, the network can receive the TRO preference options from the UE, comprising one or more of: an embedded preference vector comprising weighted values denoting an importance of latency, throughput, and power savings for the selected TRO; a preferred optimization criteria selecting one of power optimization or latency minimization as a most important criterion; a periodic data arrival period; an aperiodic data arrival timing; prioritized data traffic information; a weight of a UE and a network centric preference; a modified buffer status report (BSR) or a BSR report with additional attributes to inform the network about TRO selection; an estimated future traffic volume in the BSR; or a UE capability.

[0228] In one aspect, a baseband processor (e.g. device 600 or baseband circuitry 604), 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 600 or 604) 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. device 600 or baseband circuitry 604 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 600 or 604 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, canClient Ref. No. P70047W01 perform any of the operations described herein.

[0229] 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.

[0230] In some embodiments, a non-transitory computer-readable memory medium may be configured so that it stores program instructions and / or data, where 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.

[0231] 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.

[0232] 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.

[0233] 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. P70047W01CLAIMSWhat is claimed is:1 . A method of selecting an active transmit-receive operation (TRO) at a user equipment (UE), comprising: receiving, from a network, a scheduling priority for a plurality of N TROs, where N is a positive integer; identifying, at the UE, a selected TRO from the plurality of N TROs; determining, at the UE, a start time for the selected TRO; sending the start time to the network; switching, at the UE, to the selected TRO at the start time; and communicating with the network over the selected TRO.

2. The method of claim 1 , further comprising receiving, from the network, configuration information for a subset of M of the plurality of N TROs that the UE is allowed to switch to, where M is a positive integer and M < N.

3. The method of claim 2, further comprising identifying, at the UE, the selected TRO from the M TROs.

4. The method of claim 2, wherein the UE is not able to switch to N-M TROs and the UE is configured to receive switching instructions from the network for the N-M TROs.

5. The method of claim 1 , further comprising identifying the selected TRO from the plurality of TROs based on one or more of: a packet arrival time in uplink data traffic; a packet length in the uplink data traffic; a source destination internet protocol address and port number in the uplink data traffic; a traffic type in the uplink data traffic; or an embedded preference vector comprising weighted values denoting an importance of latency, throughput, and power savings for the selected TRO.Client Ref. No. P70047W016. The method of claim 1 , further comprising identifying, at the UE, the selected TRO from the plurality of N TROs based on an inference from an inference of an artificial intelligence I machine learning (AI / ML) model.

7. The method of claim 6, further comprising training the AI / ML model with one or more inputs comprising: historical non-acknowledgement (NACK) information; a packet arrival time; a packet length; data flow comprising one or more of a source, a destination internet protocol address and a port number, or a logical channel group; a traffic type; an embedded preference vector comprising weighted values denoting an importance of latency, throughput, and power savings for the selected TRO; a quality of service (QoS) flow requirement; historical key performance indicators (KPIs) per TRO; or base station allowed TRO list and constraints.

8. The method of claim 1 , further comprising communicating with the network over the selected TRO until a new TRO is triggered.

9. The method of claim 1 , further comprising receiving configuration information from the network for two or more TRO configurations via radio resource control (RRC) communications.

10. A method of user equipment (UE) centric adaptive transmit-receive operation (TRO) configuration selection, comprising: receiving, from a network, a pool of configuration options for one or more TROs; identifying a selected TRO configuration that is configured with one or more configurations from the pool of configuration options; sending the TRO configuration to the network; and switching to a selected TRO with the selected TRO configuration.Client Ref. No. P70047W011 1 . The method of claim 10, further comprising receiving, from the network, the pool of configuration options for the one or more TROs comprising: an inactivity timer value; a default TRO configuration; a subcarrier spacing; a bandwidth size; or a carrier frequency.

12. The method of claim 10, further comprising identifying the selected TRO configuration from the pool of TRO configurations based on one or more of: a packet arrival time in uplink data traffic; a packet length in the uplink data traffic; a source destination internet protocol address and port number in the uplink data traffic; a traffic type in the uplink data traffic; or an embedded preference vector comprising weighted values denoting an importance of latency, throughput, and power savings for the selected TRO.

13. The method of claim 10, further comprising sending the TRO configuration to the network, wherein the TRO configuration comprises one or more of: an inactivity timer duration; or a default TRO configuration; or a preferred subcarrier spacing of the selected TRO; or a preferred bandwidth of the selected TRO; or a preferred carrier frequency of the selected TRO.

14. The method of claim 10, further comprising sending a request to the network for the selected TRO, the request comprising one or more of: a new default TRO configuration; a periodic TRO switching pattern; an extension of a current TRO; or an early termination of a current TRO.Client Ref. No. P70047W0115. The method of claim 10, further comprising receiving an acknowledgement I non-acknowledgement (ACK / NACK) from the network for the TRO configuration.

16. The method of claim 15, further comprising: receiving the ACK from the network to switch to the selected TRO with the selected TRO configuration; or receiving the NACK from the network when the network configures another TRO in response to the TRO configuration identified by the UE; or receiving the NACK from the network when the network configures the UE with another TRO configuration based on information at the network; or receiving the NACK from the network; and receiving a time duration from the network in which the UE is allowed to send another TRO configuration selection.

17. The method of claim 10, further comprising identifying, at the UE, the selected TRO configuration from an inference of an artificial intelligence I machine learning (AI / ML) model.

18. The method of claim 17, further comprising training the AI / ML model with one or more inputs comprising: historical non-acknowledgement (NACK) information; a packet arrival time; a packet length; data flow comprising one or more of a source, a destination internet protocol address and a port number, or a logical channel group; a traffic type; an embedded preference vector comprising weighted values denoting an importance of latency, throughput, and power savings for the selected TRO; a quality of service (QoS) flow requirement; historical key performance indicators (KPIs) per TRO; or base station allowed TRO list and constraints.

19. A method of user equipment assisted network centric dynamic transmit-Client Ref. No. P70047W01 receive operation (TRO) adaptation, comprising: sending, from the network, two or more TRO configurations to a user equipment (UE); sending, from the network, a request for TRO preference options from the UE; receiving, from the UE, the TRO preference options; identifying, at the network, a selected TRO configuration based on one or more of the TRO preference options received from the UE; sending a selected TRO configuration to the UE; switching to the selected TRO configuration; and receiving data from the UE on the selected TRO configuration.

20. The method of claim 19, wherein at least one of the two or more TRO configurations are a default TRO configuration for the UE.21 . The method of claim 19, further comprising receiving the TRO preference options from the UE, comprising one or more of: an embedded preference vector comprising weighted values denoting an importance of latency, throughput, and power savings for the selected TRO; a preferred optimization criteria selecting one of power optimization or latency minimization as a most important criterion; a periodic data arrival period; an aperiodic data arrival timing; prioritized data traffic information; a weight of a UE and a network centric preference; a modified buffer status report (BSR) or a BSR report with additional attributes to inform the network about TRO selection; an estimated future traffic volume in the BSR; or a UE capability.

22. An apparatus of a device configured for communicating in a wireless communication network, comprising: one or more processors, coupled to a memory, configured to perform any of the methods of claims 1 -21 .Client Ref. No. P70047W0123. The device of claim 22, wherein the device includes a user equipment (UE).

24. The device of claim 22, wherein the device includes a base station (BS).

25. The device of claim 22, wherein the device includes a network entity.

26. A non-transitory computer program product, comprising computer instructions which, when executed by one or more processors, perform any of the methods of claims 1 -22.

27. A baseband processor configured to cause a user equipment (UE) to perform any of the methods of claims 1 -22.

28. A baseband processor configured to cause a base station to perform one or more of the methods of claims 1 -22.

Images