Sidelink relay adaptation protocol (SRAP) enhancements for usage in flexible topology networks

Description

Client Ref. No. P65096WO1SIDELINK RELAY ADAPTATION PROTOCOL (SRAP) ENHANCEMENTS FOR USAGE IN FLEXIBLE TOPOLOGY NETWORKSFIELD

[0001] Embodiments of the invention relate to wireless communications, including apparatuses, systems, and methods for enhancing sidelink relay adaptation protocol (SRAP) for usage in flexible topology networks in a cellular communications network.DESCRIPTION OF THE RELATED ART

[0002] Wireless communication systems are rapidly growing in usage. In recent years, wireless devices such as smart phones and tablet computers have become increasingly sophisticated. In addition to supporting telephone calls, many mobile devices now provide access to the internet, email, text messaging, and navigation using the global positioning system (GPS) and are capable of operating sophisticated applications that utilize these functionalities.

[0003] Long Term Evolution (LTE) has been the technology of choice for the majority of wireless network operators worldwide, providing mobile broadband data and high-speed Internet access to their subscriber base. LTE was first proposed in 2004 and was first standardized in 2008. Since then, as usage of wireless communication systems has expanded exponentially, demand has risen for wireless network operators to support a higher capacity for a higher density of mobile broadband users. In 2015, a study of a new radio access technology began and, in 2017, a first release of Fifth Generation New Radio (5G NR) was standardized.

[0004] 5G-NR, also simply referred to as NR, provides, as compared to LTE, a higher capacity for a higher density of mobile broadband users, while also supporting device-to-device, ultra-reliable, and massive machine type communications with lower latency and / or lower battery consumption. Further, NRClient Ref. No. P65096WO1 may allow for more flexible UE scheduling as compared to current LTE. Consequently, efforts are being made in ongoing developments of 5G-NR to take advantage of higher throughputs possible at higher frequencies.SUMMARY

[0005] Embodiments relate to wireless communications, and more particularly to apparatuses, systems, and methods for an apparatus of a user equipment (UE), the method comprising one or more processors, coupled to a memory, configured to: process a Sidelink Relay Adaptation Protocol (SRAP) protocol data unit (PDU) for a relay operation between the UE and one or more target entities, wherein the UE communicates with the one or more target entities via a first sidelink and the SRAP PDU includes an SRAP header having control information for multi-link communication; and transmitting the SRAP PDU to the one or more target entities from the UE via the first link, wherein the one or more target entities are at least one or more of a UE or a base station.

[0006] Other embodiments relate to apparatuses, systems, and methods for an apparatus of a user equipment (UE), the method comprising one or more processors, including a baseband processor, coupled to a memory, configured to: establish a relay operation with one or more source entities via a first link and one or more target entities via a second link, wherein the one or more source entities and the one or more target entities are at least one or more of a UE and a base station; decode, with the baseband processor, a Sidelink Relay Adaptation Protocol (SRAP) protocol data unit (PDU) received from a source entity from the one or more source entities via the first link; select a target entity from the one or more target entities based on the SRAP PDU; update the SRAP header of SRAP PDU based on the target entity, wherein the SRAP header is an enhanced SRAP header; and encode, with the baseband processor, the SRAP PDU having the enhanced SRAP header for transmission to the target entity via the second link.

[0007] Other embodiments relate to apparatuses, systems, and methods for an apparatus of a user equipment (UE), the method comprising one or moreClient Ref. No. P65096WO1 processors, coupled to a memory, configured to: establish two or more PC5 interfaces for communication with one or more of Remote-UEs, Relay-UEs, and alternative Intermediate-UEs; receive a Sidelink Relay Adaptation Protocol (SRAP) protocol data unit (PDU) from a source entity via a first PC5 interface of the two or more PC5 interfaces; determine a target entity based on information in an enhanced SRAP PDU header of the SRAP PDU; and forward the SRAP PDU to the target entity via a second PC5 interface of the two or more PC5 interfaces without modifying the enhanced SRAP PDU header.

[0008] Other embodiments relate to apparatus of a base station (e.g., gNB)), the apparatus comprising one or more processors including a baseband processor, coupled to a memory, configured to: assist a UE to establish a relay operation with one or more source entities via a first link and one or more target entities via a second link, wherein the one or more source entities and the one or more target entities are at least one or more of a UE and a base station; assist a UE to decode, using the baseband processor, a Sidelink Relay Adaptation Protocol (SRAP) protocol data unit (PDU) received from a source entity from the one or more source entities via the first link; assist a UE to select a target entity from the one or more target entities based on the SRAP PDU; assist a UE to update the SRAP header of SRAP PDU based on the target entity, wherein the SRAP header is an enhanced SRAP header; and assist a UE to encode, using the baseband processor, the SRAP PDU having the enhanced SRAP header for transmission to the target entity via the second link.

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

[0010] This Summary is intended to provide a brief overview of some of the subject matter described in this document. Accordingly, it will be appreciated that the above-described features are merely examples and should not be construed to narrow the scope or spirit of the subject matter described herein in any way. OtherClient Ref. No. P65096WO1 features, aspects, and advantages of the subject matter described herein will become apparent from the following Detailed Description, Figures, and Claims.BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

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

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

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

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

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

[0020] FIG. 8A illustrates an example of an exemplary network arrangement in accordance with some embodiments.Client Ref. No. P65096WO1

[0021] FIG. 8B illustrates an example of an exemplary UE in accordance with some embodiments.

[0022] FIG. 9A illustrates an example SRAP header usage in different UE types within a flexible topology network in accordance with some embodiments.

[0023] FIG. 9B illustrates an example of a legacy SRAP header in accordance with some embodiments.

[0024] FIG. 9C illustrates an example of an enhanced or modified SRAP header in accordance with some embodiments.

[0025] FIG. 9D illustrates an example of mapping tables using a modified SRAP header usage and legacy SRAP header format in different UE types within a flexible topology network in accordance with some embodiments.

[0026] FIG. 10A illustrates example diagram of an SRAP sublayer at the PC5 interface in a layer 2 (L2) UE-to-network (U2N) relay operation in accordance with some embodiments.

[0027] FIG. 10B illustrates example diagram of an SRAP sublayer at the Uu interface in the L2 U2N relay operation in accordance with some embodiments.

[0028] FIG. 10C illustrates example diagram of an enhanced SRAP sublayer at the PC5 interface in the L2 U2N relay operation in accordance with some embodiments.

[0029] FIG. 10D illustrates example diagram of the enhanced SRAP sublayer at the Uu interface in the L2 U2N relay operation in accordance with some embodiments.

[0030] FIG. 1 1 A illustrates an example diagram including protocol layers for remote UE, a relay UE, and a network (e.g., base station / Next Generation Node B “gNB”) of a user equipment UE for a relay operation.

[0031] FIG. 1 1 B illustrates an example diagram including protocol layers for remote UE, an intermediate UE, a relay UE, and a gNB of a user equipment UE for an extended relay operation.Client Ref. No. P65096WO1

[0032] FIG. 1 1 C illustrates an example diagram including protocol layers for source UE, one or mor intermediate UEs, and a destination UE for UE-to-UE operation without a network.

[0033] FIG. 12A illustrates an example illustration of mapping tables for a remote UE, a network (e.g., gNB), and an intermediate UE in accordance with some embodiments.

[0034] FIG. 12B illustrates an example illustration of mapping tables for a relay UE in accordance with some embodiments.

[0035] FIG. 13 illustrates an example of alternative SRAP header formats and combined header format within a flexible topology network in accordance with some embodiments.

[0036] FIG. 14 illustrates an example flow chart of a method of facilitating relay communication in a user equipment (UE) using SRAP in a flexible topology network in a wireless communication system, according to some embodiments.

[0037] FIG. 15 illustrates an example flow chart of a method of facilitating relay communication using an intermediate user equipment (UE) using SRAP in a flexible topology network in a wireless communication system, according to some embodiments.

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

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

[0040] 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 random-access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; a non-volatile memory such as a Flash, magnetic media, e.g., a hard drive, or optical storage; registers, or other similar types of memory elements, etc. The memory medium may include other types of non- transitory memory as well or combinations thereof. In addition, the memory medium may be located in a first computer system in which the programs are executed or may be located in a second different computer system which connects to the first computer system over a network, such as the Internet. In the latter instance, the second computer system may provide program instructions to the first computer for execution. The term “memory medium” may include two or more memory mediums which may reside in different locations, e.g., in different computer systems that are connected over a network. The memory medium may store program instructions (e.g., embodied as computer programs) that may be executed by one or more processors.

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

[0042] 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”.Client Ref. No. P65096WO1

[0043] 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 any device (or combination of devices) having at least one processor that executes instructions from a memory medium.

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

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

[0046] 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 hardwareClient Ref. No. P65096WO1 elements such as a field programmable gate array (FPGA), as well any of various combinations of the above.

[0047] 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 channels for different uses such as data, control information, etc.

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

[0049] 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 fieldClient Ref. No. P65096WO1 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.

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

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

[0052] Legacy - The 3rd Generation Partnership Project (3GPP) produces specifications that define 3GPP technologies. 3GPP specifications cover cellular telecommunications technologies, including radio access, core network and service capabilities, which provide a complete system description for mobile telecommunications. 3GPP uses a system of parallel “Releases” that providesClient Ref. No. P65096WO1 developers with a stable platform for the implementation of features at a given point and then allows for the addition of new functionality in subsequent releases. Release 17 was released in 2022. Release 18 (Rel-18), at the time of this disclosure, is nearing release on June 22, 2024, as its specifications have been largely defined. Accordingly, implementations and concepts compatible with Rel- 18, or previous Releases, are sometimes referred to herein as “Legacy Releases.” One or more embodiments of the present disclosure may be adopted in future Releases, e.g., Release 19.

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

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

[0055] The example embodiments may be further understood with reference to the following description and the related appended drawings, wherein like elements are provided with the same reference numerals. The example embodiments relate to enhancing Secondary Cell (SCell) activation with Early Measurement Report (EMR).Client Ref. No. P65096WO1

[0056] The example embodiments are described with regard to communication between a network (e.g., a 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 to support enhancing SCell activation with EMR. Therefore, the base station or UE as described herein is used to represent any appropriate type of electronic component.

[0057] The example embodiments are also described with regard to a fifth generation (5G) New Radio (NR) network that may configure a UE to control the UE side for enhancing Secondary Cell (SCell) activation with Early Measurement Report (EMR). However, reference to a 5G NR network is merely provided for illustrative purposes. The example embodiments may be utilized with any appropriate type of network.

[0058] 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.FIGs. 1 A and 1 B: Communication Systems

[0059] FIG. 1 A 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.

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

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

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

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

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

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

[0066] In some embodiments, UEs 102A to N may be configured for UE to UE communication using the 3GPP Sidelink standard. The UEs can be configured as one of a remote UE, an intermediate UE, or a relay UE. For example, UE 102A may be a remote UE that can communicate with relay UE 102N and / or base station 102A via intermediate UE 102B. This will be more fully described in the proceeding paragraphs.

[0067] In some embodiments, base station 102A may be a next generation base station, e.g., a 5G New Radio (5G NR) base station, or “base station”. In some embodiments, a base station may be connected to a legacy evolved packet core (EPC) network and / or to a NR core (NRC) network. In addition, a base station 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 base stations.

[0068] 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.) inClient Ref. No. P65096WO1 addition to at least one cellular communication protocol (e.g., GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE, LTE-A, 5G NR, HSPA, 3GPP2 CDMA2000 (e.g., 1 xRTT, 1xEV-DO, HRPD, eHRPD), etc.). The UE 106 may also or alternatively be configured to communicate using one or more global navigational satellite systems (GNSS, e.g., GPS or GLONASS), one or more mobile television broadcasting standards (e.g., ATSC-M / H or DVB-H), and / or any other wireless communication protocol, if desired. Other combinations of wireless communication standards (including more than two wireless communication standards) are also possible.

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

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

[0071] The UE 106 may include one or more antennas for communicating using one or more wireless communication protocols or technologies. In some embodiments, the UE 106 may be configured to communicate using, for example, CDMA2000 (1 xRTT 1 1 xEV-DO / HRPD I eHRPD), LTE / LTE- Advanced, or 5G NR using a single shared radio and / or GSM, LTE, LTE-Advanced, or 5G NR using the single shared radio. The shared radio may couple to a single antenna, or may couple to multiple antennas (e.g., for MIMO) for performing wireless communications. In general, a radio may include any combination of a basebandClient Ref. No. P65096WO1 processor, analog RF signal processing circuitry (e.g., including filters, mixers, oscillators, amplifiers, etc.), ordigital 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.

[0072] 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 LTE or 5G NR (or LTE or IxRTTor LTE or GSM), and separate radios for communicating using each of Wi-Fi and Bluetooth. Other configurations are also possible.FIG. 2: Block Diagram of a Base Station

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

[0074] 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 UE devices 106, access to the telephone network as described above in FIGs. 1 a, 1 b and 2.Client Ref. No. P65096WO1

[0075] 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 UE devices 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).

[0076] In some embodiments, base station 102 may be a next generation base station, e.g., a 5G New Radio (5G NR) base station, or “base station”. 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 base stations.

[0077] 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 UE devices 106 via radio 230. The antenna 234 communicates with the radio 230 via communication chain 232. Communication chain 232 may be a receive chain, a transmit chain or both. The radio 230 may be configured to communicate via various wireless communication standards, including, but not limited to, 5G NR, LTE, LTE-A, GSM, UMTS, CDMA2000, Wi-Fi, etc.

[0078] The base station 102 may be configured to communicate wirelessly using multiple wireless communication standards. In some instances, the base station 102 may include multiple radios, which may enable the base station 102 to communicate according to multiple wireless communication technologies. For example, as one possibility, the base station 102 may include an LTE radio for performing communication according to LTE as well as a 5G NR radio for performing communication according to 5G NR. In such a case, the base station 102 may be capable of operating as both an LTE base station and a 5G NR baseClient Ref. No. P65096WO1 station. As another possibility, the base station 102 may include a multi-mode radio which is capable of performing communications according to any of multiple wireless communication technologies (e.g., 5G NR and Wi-Fi, LTE and Wi-Fi, LTE and UMTS, LTE and CDMA2000, UMTS and GSM, etc.).

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

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

[0081] 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.Client Ref. No. P65096WO1FIG. 3: Block Diagram of a Server

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

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

[0084] 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 (NRG) network.

[0085] 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.Client Ref. No. P65096WO1

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

[0087] FIG. 4 illustrates an example simplified block diagram of a communication device 106, 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 106 may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet, an unmanned aerial vehicle (UAV), a UAV controller (UAC) and / or a combination of devices, among other devices. As shown, the communication device 106 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 106.

[0088] For example, the communication device 106 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 toClient Ref. No. P65096WO1 the communication device 106, and cellular communication circuitry 430 such as for 5G NR, LTE, GSM, etc., and short to medium range wireless communication circuitry 429 (e.g., Bluetooth™ and WLAN circuitry). In some embodiments, communication device 106 may include wired communication circuitry (not shown), such as a network interface card, e.g., for Ethernet.

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

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

[0091] The communication device 106 may also include and / or be configured for use with one or more user interface elements. The user interface elements mayClient Ref. No. P65096WO1 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.

[0092] The communication device 106 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 410 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 410 may be one or more embedded cards (such as embedded UICCs (eUlCCs), which are sometimes referred to as “eSIMs” or “eSIM cards”). In some embodiments (such as when the SIM(s) include an eUlCC), one or more of the SIM(s) may implement embedded SIM (eSIM) functionality; in such an embodiment, a single one of the SIM(s) may execute multiple SIM applications. Each of the SIMs may include components such as a processor and / or a memory; instructions for performing SIM / eSIM functionality may be stored in the memory and executed by the processor. In some embodiments, the UE 106 may include a combination of removable smart cards and fixed / non-removable smart cards (such as one or more eUlCC cards that implement eSIM functionality), as desired. For example, the UE 106 may comprise two embedded SIMs, two removable SIMs, or a combination of one embedded SIMs and one removable SIMs. Various other SIM configurations are also contemplated.Client Ref. No. P65096WO1

[0093] 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 410 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.

[0094] As shown, the SOC 400 may include processor(s) 402, which may execute program instructions for the communication device 106 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 rangeClient Ref. No. P65096WO1 wireless communication circuitry 429, cellular communication circuitry 430, connector l / F 420, and / or display 460. The MMU 440 may be configured to perform memory protection and page table translation or set up. In some embodiments, the MMU 440 may be included as a portion of the processor(s) 402.

[0095] As described herein, the communication device 106 may include hardware and software components for implementing the above features for a communication device 106 to communicate a scheduling profile for power savings to a network. The processor 402 of the communication device 106 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 106, 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.

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

[0097] 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 circuitClient Ref. No. P65096WO1 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.FIG. 5: Block Diagram of Cellular Communication Circuitry

[0098] 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 106 described above. As noted above, communication device 106 may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet and / or a combination of devices, among other devices.

[0099] 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 asClient Ref. No. P65096WO1LTE or LTE-A, and modem 520 may be configured for communications according to a second RAT, e.g., such as 5G NR.

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

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

[0102] 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).Client Ref. No. P65096WO1

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

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

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

[0106] 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 processorsClient Ref. No. P65096WO1522. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processors 522.FIG. 6: Block Diagram of a Baseband Processor Architecture for a UE

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

[0108] 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 102A. 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).

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

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

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

[0112] 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 (WRAN). 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.

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

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

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

[0116] 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.Client Ref. No. P65096WO1

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

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

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

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

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

[0122] 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 phaseClient Ref. No. P65096WO1 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.

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

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

[0125] 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 receiveClient Ref. No. P65096WO1 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).

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

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

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

[0129] 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 thenClient Ref. No. P65096WO1 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.

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

[0131] 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 in a UE can be used to encode a message for transmission from a UE to a base station, or decode a message received from a base station at a UE. Similarly, baseband circuitry 604 in a base station can be used to encode and decode messages communicate with the UE 106.FIG. 7: Block Diagram of an Interface of Baseband Circuitry

[0132] 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.Client Ref. No. P65096WO1

[0133] 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 the processors 604A-604E may include a memory interface, 704A-704E, respectively, to send / receive data to / from the memory 604G.

[0134] 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. 8A: Network Arrangement

[0135] FIG. 8A shows an exemplary network arrangement 800 according to various exemplary embodiments. The exemplary network arrangement 800 include UEs 106A, 106B. Those skilled in the art will understand that the UEs 106A, 106B may be any type of electronic component that is configured to communicate via a network, e.g., mobile phones, tablet computers, desktop computers, smartphones, phablets, embedded devices, wearables (e.g., HMD, AR glasses, etc. ) , Internet of Things (loT) devices, etc. It should also be understood that an actual network arrangement may include any number of UEs being used by any number of users. Thus, the example of two UEs 106A, 106B is merely provided for illustrative purposes.

[0136] The UEs 106A, 106B may communicate directly with one or more networks. In the example of the network arrangement 800 configuration, the networks with which the UEs 106A, 106B may wirelessly communicate are a 5GClient Ref. No. P65096WO1NR radio access network (5G NR-RAN) 820, an LTE radio access network (LTE- RAN) 822 and a wireless local access network (WLAN) 824. These types of networks support sidelink (SL) communication. In the exemplary network arrangement 800, the UEs 106A and 106B may be connected via a SL. However, the UEs 106A, 106B may also communicate with other types of networks and the UEs 106A, 106B may also communicate with networks over a wired connection. Therefore, the UEs 106A, 106B may include a 5G NR chipset to communicate with the 5G NR-RAN 820, an LTE chipset to communicate with the LTE-RAN 822 and an ISM chipset to communicate with the WLAN 824.

[0137] The 5G NR-RAN 820 and the LTE-RAN 822 may be portions of cellular networks that may be deployed by a network carrier (e.g., Verizon, AT&T, T- Mobile, etc. ) . These networks 820, 822 may include, for example, cells or base stations (Node Bs, eNodeBs, HeNBs, eNBS, gNBs, gNodeBs, macrocells, microcells, small cells, femtocells, etc. ) that are configured to send and receive traffic from UEs that are equipped with the appropriate cellular chip set. The WLAN 824 may include any type of wireless local area network (WiFi, Hot Spot, IEEE 802.1 1 x networks, etc. ) .

[0138] The UEs 106A, 106B may connect to the 5G NR-RAN via the gNB 820A or the gNB 820B. Reference to two gNBs 820A, 820B is merely for illustrative purposes. The exemplary embodiments may apply to any appropriate number of gNBs. The UEs 106A, 106B may also connect to the LTE-RAN 822 via the eNBs 822A, 822B. Those skilled in the art will understand that any association procedure may be performed for the UEs 106A, 106B to connect to the 5G NR-RAN 820 and the LTE-RAN 822. For example, as discussed above, the 5G NR-RAN 820 and the LTE-RAN 822 may be associated with a particular cellular provider where the UEs 106A, 106B and / or the user thereof has a contract and credential information (e.g., stored on a SIM card) . Upon detecting the presence of the 5G NR-RAN 820, the UEs 106A, 106B may transmit the corresponding credential information to associate with the 5G NR-RAN 820. More specifically, the UEs 106A, 106B may associate with a specific base station (e.g., the gNB 820A of the 5G NR-RAN 820, the eNB 822A of theClient Ref. No. P65096WO1

[0139] The UEs 106A, 106B may also communicate with one another directly using a SL. The SL is a direct device-to-device (D2D) communication link. Thus, the information and / or data transmitted directly to the other endpoint (e.g., the UE 106A or the UE 106B) does not go through a cell (e.g., gNB 820A, eNB 822A) . In some embodiments the UEs 106A, 106B may receive information from a cell regarding how the SL is to be established, maintained and / or utilized. Thus, a network (e.g., the 5G NR-RAN 820, LTE-RAN 822) may control the SL. In other embodiments, the UEs 106A, 106B may control the SL. Regardless of how the SL is controlled, the UEs 106A, 106B may maintain a downlink / uplink to a currently camped cell (e.g., gNB 820A, eNB 822A) and a SL to the other UE simultaneously.

[0140] While examples are provided herein for 4G (LTE) and 5G communication with a 5G NR-RAN 820 and an LTE-RAN 822, this is not intended to be limiting. RANs of other configurations, including 6G RANs may also be used to assist in performing the SL communication described herein.

[0141] In some scenarios, a UE, e.g., the UE 106A, may not have a direct connection with a cell and may use a further UE, e.g., the UE 106B, as a relay UE to forward data / signals to / from the UE 106A and / or the 5G NR-RAN 820. The SL may be used for relay assistance to forward data / signals between the 5G NR-RAN 820 and the remote UE 106A that is out of range of the network and / or has poor network coverage. A Layer 2 (L2) UE to network (U2N) relay amplifies received signals to the destination after successful decoding / encoding and demodulation / modulation of the signals.

[0142] In some other scenarios, a UE, e.g., the UE 106A, may use a relay UE to forward data / signals to / from another remote UE in a L2 U2U relay.

[0143] In addition to the networks 820 (e.g., the 5G NR-RAN 820), 822 (e.g., LTE-RAN 822) and 824 the network arrangement 800 also includes a cellular core network 830, the Internet 840, an IP Multimedia Subsystem (IMS) 850, and a network services backbone 860. The cellular core network 830 may be considered to be the interconnected set of components that manages the operation and trafficClient Ref. No. P65096WO1 of the cellular network. The cellular core network 830 also manages the traffic that flows between the cellular network and the Internet 840. The IMS 850 may be generally described as an architecture for delivering multimedia services to the UEs 106A, 106B using the I P protocol. The IMS 850 may communicate with the cellular core network 830 and the Internet 840 to provide the multimedia services to the UEs 106A, 106B. The network services backbone 860 is in communication either directly or indirectly with the Internet 840 and the cellular core network 830. The network services backbone 860 may be generally described as a set of components (e.g., servers, network storage arrangements, etc. ) that implement a suite of services that may be used to extend the functionalities of the UEs 106A, 106B in communication with the various networks.FIG. 8B: Exemplary UE

[0144] FIG. 8B shows an exemplary UE 106 according to various exemplary embodiments. The UE 106 will be described with regard to the network arrangement 800 of FIG. 8A. The UE 106 may include a processor 905, a memory arrangement 910, a display device 915, an input / output (I / O) device 920, a transceiver 925 and other components 930. The other components 930 may include, for example, an audio input device, an audio output device, a power supply, a data acquisition device, ports to electrically connect the UE 106A to other electronic devices, etc.

[0145] The processor 905 may be configured to execute a plurality of engines of the UE 106A. For example, the engines may include an L2 U2U relay engine 935 for performing various operations related to establishing the L2 U2U relay and transmitting / receiving SRAP data PDUs and / or SRAP control PDUs for a source remote UE, a relay UE, or a target remote UE, as described above.

[0146] The above referenced engine 935 being an application (e.g., a program) executed by the processor 905 is provided merely for illustrative purposes. The functionality associated with the engine 935 may also be represented as a separate incorporated component of the UE 106A or may be a modular component coupledClient Ref. No. P65096WO1 to the UE 106A, e.g., an integrated circuit with or without firmware. For example, the integrated circuit may include input circuitry to receive signals and processing circuitry to process the signals and other information. The engines may also be embodied as one application or separate applications. In addition, in some UEs, the functionality described for the processor 905 is split among two or more processors such as a baseband processor and an applications processor. The exemplary embodiments may be implemented in any of these or other configurations of a UE.

[0147] The memory arrangement 910 may be a hardware component configured to store data related to operations performed by the UE 106A. The display device 915 may be a hardware component configured to show data to a user while the I / O device 920 may be a hardware component that enables the user to enter inputs. The display device 915 and the I / O device 920 may be separate components or integrated together such as a touchscreen. The transceiver 925 may be a hardware component configured to establish a connection with the 5G NR-RAN 620 and / or any other appropriate type of network. Accordingly, the transceiver 925 may operate on a variety of different frequencies or channels (e.g., set of consecutive frequencies).

[0148] As shown in FIG. 9A, UEs configured for UE to UE sidelink (SL) communication may communicate via a PC5 interface. A UE configured to communicate with a base station, such as a gNB, can communicate with a Uu interface. UE’s configured for UE to UE communication are commonly referred to as a remote UE, or a relay UE. A new type of configuration, referred to as an intermediate UE, is disclosed in embodiments herein.

[0149] As used herein, a remote UE has a PC5 interface to one or several Relay UEs or intermediate UEs. The remote UE has no (active) Uu interface to a base station, such as a gNB. The remote UE performs end to end (E2E) communication towards a base station, such as a gNB, on a Packet Data Convergence Protocol / Service Data Adaptation Protocol (PDCP / SDAP) layer. The remote UE can create and / or remove an SRAP header for SL communication with other UEs.Client Ref. No. P65096WO1

[0150] A relay UE has a Uu interface for communication with a base station, such as a gNB. The relay UE also has one or several PC5 interfaces to other relay UEs and / or intermediate UEs, and / or other remote UEs. Communication that includes intermediate UEs uses an enhanced SRAP. An example of an enhanced SRAP header is illustrated in FIG. 14. The relay UE can perform mapping between a legacy SRAP and enhanced SRAP header format. This will be discussed more fully in the proceeding paragraphs.

[0151] An intermediate UE (new), which is a new type of UE used in SL communication, has no (active) Uu interface with a gNB. The intermediate UE has two or more PC5 interfaces for communication with remote UEs, relay UEs, and / or other intermediate UEs. An intermediate UE is configured to forward packets without changing an SRAP (or enhanced SRAP) header.

[0152] A base station that is configured for SL communication with an SRAP header and an enhanced SRAP header has a Uu interface to a relay-UE. The base station has no PC5 interface to any UE. The base station does not perform E2E communication towards remote-UEs on the PDCP / SDAP level. The base station can create and remove SRAP and enhanced SRAP headers.

[0153] FIG. 9B illustrates an example of a legacy SRAP header 960. The structure of the modified or enhanced SRAP header, which includes a D / C (e.g., Data / Control) bit, an R (Reserved) bit, an additional R (Reserved) bit, a BEARER- ID field, a UE-ID field, and a DATA field.

[0154] As used herein, a remote-UE-ID is assigned to a UE which is the source UE or the destination UE of an end to end (E2E) communication. A Bearer-ID is a data radio bearer (DRB) ID that is used on the PDCP level. The remote-UE-ID and the Bearer-ID can be included in a legacy SRAP header.

[0155] FIG. 9C illustrates an example of an enhanced or modified SRAP header 970. One of the reserved bits (R) in the legacy SRAP header 960 in FIG. 9B can be modified to include a direction (DIR) bit. The direction bit can be used to designate the direction of an SRAP PDU, such as an uplink direction or a downlink direction. In one example, the DIR bit in the modified or enhanced SRAP headerClient Ref. No. P65096WO1 indicates the traffic direction, with 0 representing Uplink and 1 representing Downlink, or vice versa.

[0156] Returning to FIG. 9A, an example SRAP header usage is illustrated in different UE types within a flexible topology network in accordance with some embodiments. A network configuration with multiple User Equipment (UE) devices, including a Remote UE (UE 1 ), Intermediate UEs (UE 2 and UE 3), a Relay UE (UE 4), and a next generation Node B (gNB) are illustrated in this example. The UEs are interconnected via PC5 interfaces, while the Relay UE connects to the gNB via a Uu interface.

[0157] That is, FIG. 9A depicts potential interconnections of a network configuration used for sidelink (SL) communication with multiple User Equipment (UE) devices, including: a Remote UE (UE 1 ), Intermediate UEs (UE 2 and UE 3), a Relay UE (UE 4), and a base station, such as a next generation Node B (gNB). The UEs are interconnected via PC5 interfaces, while the Relay UE connects to the gNB via a Uu interface. Three routing options are shown, illustrating potential paths for data transmission.

[0158] FIG. 9A illustrates mapping tables for different UEs: UE 1 , UE 3, and UE4. A UE 1 (Remote UE) table shows Data Radio Bearer (DRB) to next UE-ID mappings. For example, DRB a maps to UE-ID 1 , and DRB b maps to UE-ID 2. A UE 3 (Intermediate UE) table demonstrates more complex routing with columns for UE-ID, DRB, Next UE, and Direction. The mapping table shows how UE 3 may route traffic based on the source / destination UE, the DRB, and the traffic direction (UL / DL). The UE 4 (Relay UE) table presents mappings for both UL and DL traffic. For UL, it maps Remote UE (UE 1 ) DRBs to Next UE-IDs. For DL, it shows DRB a mapped to UE-ID 4, with other DRBs mapped for UL or DL directions.

[0159] For routing decisions, the UE Identifier (UE-ID) and Bearer Identifier (BEARER-ID), also known as Data Radio Bearer Identifier (DRB-ID), from the SRAP header may be used. Additionally, within Intermediate UEs, it's necessary to know the traffic direction (Uplink / Downlink).Client Ref. No. P65096WO1

[0160] The direction bit in the modified or enhanced SRAP header is only used between UEs (e.g., Remote / Relay / lntermediate), but not between the Relay UE and the gNB. This ensures backward compatibility with the current 3rd Generation Partnership Project (3GPP) standards. In data transfer between a UE and gNB, the direction is inherently clear: 1 ) all packets sent towards the gNB are Uplink (UL) packets, and 2) all packets sent by the gNB are Downlink (DL) packets.

[0161] FIG. 9A also illustrates a scenario where an Intermediate UE receives a packet from another Intermediate UE (e.g., between UE 2 and UE 3). In this case, it is unclear whether the packet originally came from a Remote UE (e.g., UE 1 ) or from the gNB (DL). Therefore, a direction bit can be added to an enhanced or modified SRAP header to clarify the packet's direction.

[0162] The UL direction in the SRAP header may be set by the Remote UE (e.g., UE 1 ) when receiving a packet from upper layers. The remote UE may add the UL direction to the SRAP header for an SRAP PDU. Conversely, the DL direction in the SRAP header may be added to the SRAP header by the Relay UE (e.g., UE 4) when receiving an SRAP PDU packet via the Uu interface from the gNB. In addition, the relay UE can remove the direction bit from the enhanced or modified SRAP header prior to sending an SRAP PDU to the gNB to enable the PDU to be backwards compatible.

[0163] As an alternative option, it may be possible to avoid the direction bit entirely. Since it may be unlikely that a Radio Link Control (RLC) channel between two UEs would be used for both directions (UE1 <-> UE2), a UE may be able to identify the packet direction based on the RLC channel used. This approach could simplify the SRAP header while still maintaining the necessary routing information in the flexible topology network.

[0164] FIG. 9D illustrates an example flow of SRAP Protocol Data Units (PDUs) between different UE types and a base station, such as a gNB, depicting how the SRAP header format changes in E2E communication.

[0165] In the example of FIG. 9D, three types of SRAP header usage are depicted. Between the gNB and Relay-UE, a legacy SRAP header format is used.Client Ref. No. P65096WO1Between Relay-UE and Intermediate-UE, a modified or enhanced SRAP header format is used. Between Intermediate-UE and Remote-UE, a modified or enhanced SRAP header format may also be used.

[0166] The Relay-UE may be used in mapping between the legacy SRAP header formats (e.g., legacy SRAP header format 960) and modified SRAP header format (e.g., enhanced or modified SRAP header 970). When a Relay-UE receives a packet from the gNB via the Uu interface, the Relay-UE can replace the legacy header format with the modified SRAP header format and set the DIR-bit to Downlink, such as (1 ). The packet is then forwarded to the next UE (Intermediate or Remote UE) via the PC5 interface.

[0167] Conversely, when a Relay-UE receives a packet from another UE via the PC5 interface, the Relay-UE may replace the modified or enhanced SRAP header with the legacy SRAP header format before sending the packet to the gNB via the Uu interface. An Intermediate-UE may receive SRAP packets in the modified SRAP format and forward them in the same format without modification.

[0168] When a Remote-UE is creating a packet, such as an SRAP PDU packet, the remote-UE can add an SRAP header in the modified format 970. This approach ensures backward compatibility with existing systems while enabling enhanced functionality within the local area network formed by the UEs, allowing for efficient routing and direction indication in the flexible topology network without affecting the communication between the Relay-UE and the gNB.

[0169] FIG. 10A illustrates an example diagram 1000 of an SRAP sublayer at a PC5 interface in a layer 2 (L2) UE-to-network (U2N) relay operation in accordance with some embodiments.

[0170] FIG. 10A shows a diagram 1000 of the SRAP sublayer at the PC5 interface in the L2 U2N relay operation according to one example. The diagram 1000 includes a transmitting entity 1012 (e.g., transmitting SRAP entity) of the PC5 interface (e.g., in the remote UE or the relay UE) and a receiving entity 1014 (e.g., receiving PC5 SRAP entity) (e.g., in the remote UE or the relay UE).Client Ref. No. P65096WO1

[0171] If the transmitting entity 1012 is the relay UE, the receiving entity 1014 receives an SRAP PDU from the receiving part of the relay UE SRAP entity at the Uu interface. The transmitting entity 1012 (e.g., transmitting PC5 SRAP entity) (in the relay UE) determines an egress link and maps the SRAP PDU to an egress RLC channel (PC5). If the transmitting entity 1012 is the remote UE, the transmitting entity 1012 receives a SRAP service data unit (SDU) from the upper layers (e.g., PDCP). A service data unit is a unit of data that has been passed down from a higher layer or sublayer to a lower layer. This unit of data (SDU) has not yet been encapsulated into a protocol data unit (PDU) by the lower layer.

[0172] The transmitting entity 1012 (remote UE) determines the UE ID and bearer ID, adds the SRAP header including the UE ID and the bearer ID to the SRAP SDU (e.g., generates a SRAP PDU), and maps the SRAP PDU to the egress RLC channel (PC5).

[0173] The transmitting entity 1012 of the PC5 SRAP transmits the SRAP PDU via the egress RLC interface, e.g., PC5. The receiving entity 1014 of the PC5 SRAP receives the SRAP PDU via the ingress RLC interface, e.g., PC5. If the receiving entity 1014 is the remote UE, the receiving entity 1014 processes and removes the SRAP header (generates a SRAP SDU) and transmits the SRAP SDU to the upper layers (e.g., PDCP). If the receiving entity 1014 is the relay UE, the receiving entity 1014 transmits the SRAP PDU to the transmitting part of the relay UE SRAP entity at the Uu interface.

[0174] FIG. 10B illustrates example diagram 1010 of an SRAP sublayer at the Uu interface in the L2 U2N relay operation in accordance with some embodiments. That is, FIG. 10B shows a diagram 1010 of the SRAP sublayer at the Uu interface in the L2 U2N relay operation according to one example. The diagram 1010 includes a transmitting entity 1022 (e.g., Uu SRAP entity such as, for example the RAN / gNB or the relay UE) and a receiving entity 1024 (e.g., a receiving SRAP entity or the RAN / gNB or the relay UE). If the transmitting entity 1022 is the relay UE, the transmitting entity 1022 receives a SRAP PDU from the receiving part of the relay UE SRAP entity at the PC5 interface.Client Ref. No. P65096WO1

[0175] If the transmitting entity 1022 is the RAN / gNB, the transmitting entity 1022 receives a SRAP SDU from the upper layers (e.g., PDCP) . The transmitting entity 1022 (in the RAN / gNB) determines the UE ID and bearer ID, adds the SRAP header including the UE ID and the bearer ID to the SRAP SDU (e.g., generates an SRAP PDU) , and maps the SRAP PDU to the egress RLC channel (Uu) using an SRAP header .

[0176] The transmitting entity 1022 (e.g., transmitting Uu SRAP entity) transmits the SRAP PDU via the egress RLC interface, e.g., Uu. The receiving entity 1024 (e.g., receiving Uu SRAP entity) receives the SRAP PDU via the ingress RLC interface, e.g., Uu. If the receiving entity 1024 is the RAN / gNB, the receiving entity 1024 processes and removes the SRAP header (generates a SRAP SDU) and transmits the SRAP SDU to the upper layers (e.g., PDCP).

[0177] If the receiving entity 1024 is in the relay UE, the receiving entity 1024 transmits the SRAP PDU to the transmitting part of the relay UE SRAP entity at the PC5 interface.

[0178] The L2 UE-to-UE (U2U) relay was introduced in 3GPP Rel-18, wherein a relay UE provides relay services between two remote UEs, e.g., a source remote UE and a target remote UE. In the L2 U2U, it is assumed the SRAP is to be used above the RLC layer, similar to the L2 U2N relay.

[0179] FIG. 10C illustrates example diagram 1030 of an enhanced SRAP sublayer at the PC5 interface in the L2 U2N relay operation in accordance with some embodiments. The diagram 1030 includes a transmitting entity 1032 (e.g., a transmitting SRAP entity) of the PC5 interface (e.g., in the remote UE or the relay UE) and a receiving entity 1034 (e.g., a receiving PC5 SRAP entity in the remote UE or the relay UE, or the intermediate UE).

[0180] If the transmitting entity 1032 is the relay UE or intermediate UE, the transmitting entity 1032 receives an SRAP PDU from the receiving part of the relay UE SRAP entity at the Uu interface or from another PC5 interface. The transmitting entity 1032 (in the relay UE or intermediate UE) selects a remote UE orClient Ref. No. P65096WO1Intermediate UE, determines an egress link, and maps the SRAP PDU to an egress RLC channel (PC5).

[0181] If the transmitting entity 1032 is the remote UE, the transmitting entity 1032 receives an SRAP SDU from the upper layers (e.g., PDCP). The transmitting entity 1032 (remote UE) determines the UE ID and bearer ID, adds the enhanced SRAP header including the UE ID, the bearer ID, and the direction (e.g. UL (bit 0)) to the SRAP SDU (e.g., generates an enhanced SRAP PDU), selects a next Relay UE or Intermediate UE, and maps the SRAP PDU to the egress RLC channel (PC5). The next relay UE may be selected based on one more of a number of hops to the end point, a signal quality to a next hop, a distance to a next hop, a signal quality to a next hop or a multiple hop route to the end point, a data throughput to a next hop or a multiple hop route, or other desired parameters. The criteria here is provided as an example and is not intended to be limiting. A broad array of choices may be made to select a next hop in a network.

[0182] The transmitting entity 1032 of the PC5 SRAP transmits the enhanced SRAP PDU via the egress RLC interface, e.g., PC5. The receiving entity 1034 of the PC5 SRAP receives the enhanced SRAP PDU via the ingress RLC interface, e.g., PC5. If the receiving entity 1034 is the remote UE, the receiving entity 1034 processes and removes the SRAP header or enhanced SRAP header (generates a SRAP SDU) and transmits the SRAP SDU to the upper layers (e.g., PDCP). If the receiving entity 1034 is the relay UE or intermediate UE, the receiving entity 1034 selects an intermediate UE or Remote UE and transmits the SRAP PDU to the transmitting part of the selected UE's SRAP entity at the appropriate interface (e.g., transmits the SRAP PDU to the transmitting part of the relay UE SRAP entity at the Uu interface or the transmitting part of the intermediate UE SRAP entity at PC5 interface).

[0183] FIG. 10D illustrates example diagram 1040 of the enhanced SRAP sublayer at the Uu interface in the L2 U2N relay operation in accordance with some embodiments. That is, FIG. 10D includes a transmitting entity 1042 (e.g., a transmitting Uu SRAP entity or the RAN / gNB or the relay UE and hereafter referredClient Ref. No. P65096WO1 to as “transmitting entity 1042”) and a receiving entity 1044 (e.g., a receiving SRAP entity or the RAN / gNB or the relay UE and hereafter referred to as “receiving entity 1044”).

[0184] If the transmitting entity 1042 is the relay UE, the transmitting entity 1042 receives an SRAP PDU from the receiving part of the relay UE SRAP entity at the PC5 interface. The transmitting entity 1042 then determines an egress link and maps the SRAP PDU to an egress RLC channel (Uu).

[0185] If the transmitting entity 1042 is the RAN / gNB, the transmitting entity 1042 receives a SRAP SDU from the upper layers (e.g., PDCP). The transmitting entity 1042 (in the RAN / gNB) determines the UE ID and bearer ID, adds the SRAP header including the UE ID and the bearer ID to the SRAP SDU (e.g., generates a SRAP PDU), and maps the SRAP PDU to the egress RLC channel (Uu).

[0186] The transmitting entity 1042 (e.g., the transmitting Uu SRAP entity) transmits the SRAP PDU via the egress RLC interface, e.g., Uu. The receiving entity 1044 (e.g., the receiving Uu SRAP entity) receives the SRAP PDU via the ingress RLC interface, e.g., Uu.

[0187] If the receiving entity 1044 is the RAN / gNB, the receiving entity 1044 processes and removes the SRAP header (generates a SRAP SDU) and transmits the SRAP SDU to the upper layers (e.g., PDCP).

[0188] If the receiving entity 1044 is in the relay UE, the receiving entity 1044 selects an intermediate UE or Remote UE, and transmits the SRAP PDU to the transmitting part of the selected UE's SRAP entity at the PC5 interface.

[0189] This enhanced SRAP sublayer at the Uu interface allows for more flexible routing decisions, supporting the concept of a flexible topology network with multiple possible paths for data transmission between the RAN / gNB and the UEs in the network.

[0190] FIG. 1 1 A illustrates an example diagram 1 1 10 including protocol layers for a remote UE, a relay UE, and a network (e.g., base station / Next Generation Node B “gNB”) of a user equipment UE for a relay operation (e.g., relay use case).Client Ref. No. P65096WO1

[0191] The diagram 1 1 10 shows the protocol stack for a layer 2 (L2) UE-to- network (U2N) relay operation in a flexible topology network. On the remote UE, the protocol stack includes SDAP, PDCP, PC5-SRAP, PC5-Radio Link Control (RLC), PC5-Medim Access Control (MAC), and PC5-Physical (PHY) layers. The SRAP sublayer on the remote UE may contain only one SRAP entity at the PC5 interface.

[0192] Both Relay UE 1 and Relay UE 2 have identical protocol stacks, each including two sets of protocol layers: one for the PC5 interface and another for the Uu interface. The PC5 side includes PC5-SRAP, PC5-RLC, PC5-MAC, and PC5- PHY layers, while the Uu side includes Uu-SRAP, Uu-RLC, Uu-MAC, and Uu-PHY layers. In each relay UE, the SRAP sublayer contains two separate SRAP entities: one for the PC5 interface and another for the Uu interface.

[0193] On the gNB side, the protocol stack includes Uu-SDAP, Uu-PDCP, Uu- SRAP, Uu-RLC, Uu-MAC, and Uu-PHY layers. The SRAP sublayer on the gNB contains only one SRAP entity at the Uu interface.

[0194] The SRAP sublayer is positioned above the RLC layer and below the PDCP layer in all cases. The PDCP layer performs security and ciphering functions. Notably, the packets received at the relay UE are opaque to the relay UE, ensuring end-to-end security between the remote UE and the gNB.

[0195] Each SRAP entity has both transmitting and receiving parts. Across the PC5 interface, the transmitting part of the SRAP entity in the remote UE corresponds to the receiving part of the SRAP entity in the relay UE, and vice versa. Similarly, across the Uu interface, the transmitting part of the SRAP entity in the relay UE corresponds to the receiving part of the SRAP entity in the gNB, and vice versa. This bidirectional communication capability allows for efficient data transfer in both uplink and downlink directions.

[0196] This architecture enables end-to-end (E2E) communication between the remote UE and the gNB through the relay UE, with the SRAP layer managing the relay adaptation process.Client Ref. No. P65096WO1

[0197] FIG. 1 1 B illustrates an example diagram 1 120 including protocol layers for remote UE, an intermediate UE, a relay UE, and a gNB of a user equipment UE for an extended relay operation (e.g., Extended relay use case).

[0198] The diagram 1 120 shows the protocol stack for an extended layer 2 (L2) UE-to-network (U2N) relay operation. On the remote UE, the protocol stack includes SDAP, PDCP, PC5-SRAP, PC5-RLC, PC5-MAC, and PC5-PHY layers. The SRAP sublayer on the remote UE may contain only one SRAP entity at the PC5 interface.

[0199] The intermediate UE’s protocol stack includes only PC5 interface layers: PC5-SRAP, PC5-RLC, PC5-MAC, and PC5-PHY. The SRAP sublayer on the intermediate UE contains two SRAP entities, both at PC5 interfaces, allowing it to receive from one UE and forward to another UE.

[0200] The relay UE's protocol stack includes two sets of protocol layers: one for the PC5 interface (towards the intermediate UE) and another for the Uu interface (towards the gNB). The PC5 side includes PC5-SRAP, PC5-RLC, PC5- MAC, and PC5-PHY layers, while the Uu side includes Uu-SRAP, Uu-RLC, Uu- MAC, and Uu-PHY layers. The relay UE's SRAP sublayer contains two separate SRAP entities: one for the PC5 interface and another for the Uu interface.

[0201] On the gNB side, the protocol stack includes Uu-SDAP, Uu-PDCP, Uu- SRAP, Uu-RLC, Uu-MAC, and Uu-PHY layers. The SRAP sublayer on the gNB contains only one SRAP entity at the Uu interface.

[0202] The SRAP sublayer is positioned above the RLC layer and below the PDCP layer where applicable. The PDCP layer, present in the remote UE, relay UE (Uu side), and gNB, performs security and ciphering functions. The packets are end-to-end encrypted between the remote UE and the gNB, remaining opaque to the intermediate and relay UEs.

[0203] Each SRAP entity has both transmitting and receiving parts. The communication chain extends from the remote UE through the intermediate UE and relay UE to the gNB, with each hop using the appropriate interface (PC5 or Uu).Client Ref. No. P65096WO1

[0204] FIG. 110 illustrates an example diagram 1 130 including protocol layers for UE to UE communication using sidelink. A source UE is a UE that transmits a communication. A destination UE is a UE that receives the communication from the source UE, through one or more additional UEs. In FIG. 11 C, the source UE, one or more intermediate UEs, and a destination UE are configured for UE-to-UE operation using sidelink without a network (e.g., UE-to-UE use case (without gNB) use case).

[0205] The diagram 1130 shows the protocol stack for a UE-to-UE communication scenario that does not involve a base station (gNB).

[0206] On both the source UE and destination UE, the protocol stack includes SDAP, PDCP, PC5-SRAP, PC5-RLC, PC5-MAC, and PC5-PHY layers. The SRAP sublayer on these end-point UEs contains only one SRAP entity at the PC5 interface.

[0207] The diagram 1 130 shows multiple intermediate UEs (labeled as Intermediate UE 1 , Intermediate UE 2, and Intermediate UE 3), illustrating the potential for extended range communication through a chain of UEs using sidelink (SL) connections. This setup allows messages to be relayed through several UEs via SL interfaces, effectively extending the communication range beyond what would be possible with a direct SL connection between the source and destination UEs.

[0208] Each intermediate UE's protocol stack includes only PC5 interface layers: PC5-SRAP, PC5-RLC, PC5-MAC, and PC5-PHY. The SRAP sublayer on each intermediate UE contains two SRAP entities, both at PC5 interfaces, allowing it to receive from one UE and forward to another UE.

[0209] The SRAP sublayer is positioned above the RLC layer and below the PDCP layer in all UEs. The PDCP layer, present in the source and destination UEs, performs security and ciphering functions.

[0210] Each SRAP entity has both transmitting and receiving parts. The communication path extends from the source UE through one or more intermediate UEs to the destination UE, with each link in the chain using the PC5 interface forClient Ref. No. P65096WO1 sidelink (SL) communication. This sidelink relay chain enables messages to traverse multiple UEs, significantly extending the effective range of device-to- device communication.

[0211] FIG. 12A illustrates an example illustration of mapping tables for a remote UE, a network (e.g., gNB), and an intermediate UE in accordance with some embodiments.

[0212] That is, FIG. 12A depicts three mapping tables (mapping tables 1210, 1220, and 1230) used in the flexible topology network for routing decisions and packet forwarding.

[0213] The Remote-UE mapping table 1210 (e.g., mapping table 1210 or “Remote-UE mapping table 1210”) includes columns for Bearer-ID and UE-ID used in a PC5 interface.

[0214] The Remote-UE mapping table 1210 may be used for uplink traffic only, as no mapping is needed for downlink (DL) traffic since the Remote-UE is the endpoint. The UE-ID identifies either a neighboring Relay-UE or an Intermediate- UE for an SRAP PDU to be sent. For example, DRB1 is mapped to UE-ID X, and DRB2 can be mapped to UE-ID Y. For selecting the next UE, criteria can be identified to choose the best next UE, as previously discussed.

[0215] The gNB mapping table 1220 (e.g., mapping table 1220 or “gNB mapping table 1220”) contains columns for Remote-UE ID, Bearer-ID, and Relay- UE-ID of a used Uu interface. The gNB mapping table 1220 may be used for downlink traffic, always mapping to a Relay-UE. For instance, Remote-UE ID 1 with DRB1 is mapped to Relay-UE-ID X, while the same Remote-UE ID 1 with DRB2 is mapped to Relay-UE-ID Y.

[0216] As previously discussed, the legacy SRAP header can be modified or enhanced to include a direction bit, identifying whether an SRAP PDU sent to an intermediate-UE is an uplink packet or a downlink packet. The Intermediate-UE mapping table (e.g., mapping table 1230 or “Intermediate-UE mapping table 1230”) may include columns for Remote-UE, Bearer-ID, Traffic direction (UL / DL), and a Next UE-ID of used PC5 interface. The Intermediate-UE mapping table 1230 mayClient Ref. No. P65096WO1 consider both uplink and downlink directions for routing in the flexible topology. For example, for Remote-UE 1 and DRB1 , uplink traffic is mapped to UE-ID X, while downlink traffic for the same Remote-UE and DRB is mapped to UE-ID Y.

[0217] These mapping tables enable efficient routing decisions in the flexible topology network and allow each entity to determine the next appropriate UE for forwarding traffic, considering factors such as the bearer, the direction of traffic, and the specific remote UE involved in the communication.

[0218] FIG. 12B illustrates an example illustration of mapping tables for a relay UE in accordance with some embodiments. That is, FIG. 12B depicts two mapping tables (mapping tables 1240 and 1250) used by the Relay-UE for routing decisions in a flexible topology network.

[0219] The Relay-UE mapping table 1240 (e.g., mapping table 1240 or “Relay- UE mapping table 1240”), labeled "UL Data received from other UE via PC5," is used for uplink (UL) traffic. The Relay-UE mapping table 1240 includes columns for Remote-UE, Bearer-ID, Traffic Direction (UL / DL), and Next UE-ID. For example, Relay-UE mapping table 1240 shows that for Remote-UE 1 , both Data Radio Bearer 1 (DRB1 ) and DRB2 are mapped for UL traffic. The Next UE-ID column may contain the identifier of the next node in the network to which the Relay-UE should forward the traffic.

[0220] The Relay-UE mapping table 1250 (e.g., mapping table 1250 or “Relay- UE mapping table 1250”), labeled "DL Data received from gNB," is used for downlink (DL) traffic. The Relay-UE mapping table 1250 also includes columns for Remote-UE, Bearer-ID, Traffic direction (UL / DL), and Next UE-ID of used PC5 interface. The Relay-UE mapping table 1250 shows an example where for Remote- UE 1 , DRB1 and DRB2 are mapped for DL traffic. For DRB2, the Next UE-ID is specified as UE-IDx, indicating the specific UE to which this downlink traffic should be forwarded via the PC5 interface.

[0221] These mapping tables enable the Relay-UE to make efficient routing decisions for both uplink and downlink traffic in the flexible topology network. They allow the Relay-UE to determine the appropriate next hop for each packet basedClient Ref. No. P65096WO1 on factors such as the source or destination Remote-UE, the Bearer-ID, and the traffic direction.

[0222] FIG. 13 illustrates an example of alternative SRAP header formats and combined header format within a flexible topology network in accordance with some embodiments.

[0223] In one example, FIG. 13 depicts two different SRAP header formats (e.g., SRAP header 1310, 1320 or formats for SRAP header 1310, 1320). The first is an alternative header format for traffic between UEs, designed for UE-to-UE communication. The SRAP header 1310 is designed for UE-to-UE communication. For relay communication, end-to-end traffic occurs only between the network and a Remote-UE, so a single BEARER-ID / UE-ID in the header would be sufficient. However, for UE-to-UE use cases, information about both UEs is required in the SRAP header 1310, allowing intermediate UEs to make routing decisions for the packets. Thus, the SRAP header includes four octets with fields for source and destination BEARER-ID and UE-ID, allowing intermediate UEs to make routing decisions for the packets.

[0224] The second is a combined header format (e.g., SRAP header 1320) designed to support both UE-to / from-RAN and UE-to-UE transmissions in a single structure.

[0225] The SRAP header 1320 includes a UE-to-UE bit that determines the packet type. When this bit is set to 0, the SRAP header 1320 indicates a UE-to- gNB packet with a valid DIR bit and only two octets. When set to 1 , the SRAP header 1320 indicates a UE-to-UE packet with four octets and an invalid DIR bit. This combined format provides flexibility to support different communication scenarios within the same network, allowing for efficient header usage depending on the type of communication. It should be noted that if the direction bit is not needed (as direction can be derived using a Radio Link Control (RLC) channel information), the direction it can be replaced with a reserved (R) bit. This approach enables a unified header structure that can accommodate various communication needs in the flexible topology network.Client Ref. No. P65096WO1

[0226] FIG. 14 illustrates an example flow chart of a method of facilitating relay communication in a user equipment (UE) using SRAP in a flexible topology network in a wireless communication system, according to some embodiments.

[0227] The method shown in FIG. 14 may be used in conjunction with any of the systems, methods, or devices illustrated in the Figures, among other devices. In various embodiments, some of the method elements shown may be performed concurrently, in a different order than shown, or may be omitted. Additional method elements may also be performed as desired.

[0228] In accordance with an embodiment, a method 1400, for facilitating relay communication by a user equipment (UE), comprises processing a Sidelink Relay Adaptation Protocol (SRAP) protocol data unit (PDU) for a relay operation between the UE and one or more target entities, wherein the UE communicates with the one or more target entities via a first sidelink and the SRAP PDU includes an SRAP header having control information for multi-link communication, as in block 1410.

[0229] The method 1400 further comprises transmitting the SRAP PDU to the one or more target entities from the UE via the first link, wherein the one or more target entities are at least one or more of a UE or a base station, as in block 1420.

[0230] In some embodiments, the UE is a Remote-UE. In some embodiments, the UE is a Relay-UE. In some embodiments, the UE is an Intermediate-UE, wherein processing the SRAP PDU comprises receiving the SRAP PDU from a source UE.

[0231] In some embodiments, the Remote-UE has one or more PC5 interfaces communicating with at least one or more Relay-UEs and one or more Intermediate- UEs. In some embodiments, the Remote-UE is absent a Uu interface with a base station. In some embodiments, the Remote-UE performs end-to-end (E2E) communication with a base station on Packet Data Convergence Protocol (PDCP) and Service Data Adaptation Protocol (SDAP) levels. In some embodiments, the Remote-UE performs one or more of adding and removing an SRAP header from one or more SRAP PDUs.Client Ref. No. P65096WO1

[0232] In some embodiments, the Relay-UE has a Uu interface with a base station. In some embodiments, the Relay-UE has one or more PC5 interfaces communicating with at least one or more Relay-UEs, one or more Intermediate- UEs, and one or more Remote-UEs. In some embodiments, the Relay-UE performs mapping between a standard SRAP header format and enhanced SRAP header format in the SRAP PDU.

[0233] In some embodiments, the Intermediate-UE does not include a Uu interface with a base station. In some embodiments, the Intermediate-UE has two or more PC5 interfaces communicating with at least one or more Relay-UEs, one or more Intermediate-UEs, or one or more Remote-UEs. In some embodiments, the Intermediate-UE forwards the SRAP PDU without modifying the SRAP header.

[0234] In some embodiments, the SRAP header in the SRAP PDU includes a Remote-UE-ID assigned to a UE which is one of the one or more source entities or the one or more target entities of an end-to-end (E2E) communication. In some embodiments, the SRAP header in the SRAP PDU includes a BEARER-ID which is a Data Radio Bearer (DRB) identifier (ID) used at a packet data convergence protocol (PDCP) level.

[0235] In some embodiments, the method further includes updating the SRAP header by adding a direction bit to indicate whether the SRAP PDU is for uplink or downlink communication. In some embodiments, the SRAP header includes a direction bit indicating uplink traffic or downlink traffic. In some embodiments, the direction bit is set to uplink by a Remote-UE upon receiving the SRAP PDU from one or more upper layers. In some embodiments, the direction bit is set to downlink by a Relay-UE upon receiving the SRAP PDU via Uu interface.

[0236] In some embodiments, the Relay-UE maps between a legacy SRAP header format used with a base station and a modified SRAP format used within a local area network between UEs.

[0237] In some embodiments, for UE-to-UE communication, the SRAP header includes information of both source and destination UEs. In some embodiments, when the Relay-UE receives the SRAP PDU from a base station via the first link,Client Ref. No. P65096WO1 the Relay-UE replaces a standard SRAP header format with the enhanced SRAP header format and sets a direction bit to indicate downlink communication prior to forwarding the SRAP PDU to the one or more target entities via the first link. In some embodiments, when the Relay-UE receives the SRAP PDU from a source entity via the first link, the Relay-UE replaces the enhanced SRAP header with a legacy SRAP header format before sending the SRAP PDU to the base station via the first sidelink.

[0238] In some embodiments, the Intermediate-UE receives the SRAP PDU with the enhanced SRAP header, the Intermediate-UE forwards the SRAP PDU without modifying the enhanced SRAP header. In some embodiments, when the Remote-UE is a source UE, the Remote-UE creates the SRAP PDU by adding the enhanced SRAP header. In some embodiments, the direction of communication for the SRAP PDU is determined by identifying which a Radio Link Control (RLC) channel is used between the UE and the one or more target entities without using a direction bit in the enhanced SRAP header.

[0239] In some embodiments, the Relay-UE maps between a standard SRAP header format used with the base station and the enhanced SRAP header format used within a local area network between the one or more UEs.

[0240] In some embodiments, for UE-to-UE communication, the enhanced SRAP header includes information of both the UE and the one or more target entities, including a source UE ID, a source bearer ID, a destination UE ID, and a destination bearer ID. In some embodiments, the enhanced SRAP header includes a UE-to-UE field that determines whether the SRAP PDU is for UE-to-base station or UE-to-UE communication.

[0241] In some embodiments, when the UE-to-UE field is set to 0, the SRAP PDU is for UE-to-base station communication and a direction bit in the enhanced SRAP header is valid. In some embodiments, when the UE-to-UE field is set to 1 , the SRAP PDU is for UE-to-UE communication and the direction bit in the enhanced SRAP header is not valid.Client Ref. No. P65096WO1

[0242] In some embodiments, method further includes selecting the one or more target entities based on a plurality of criteria, wherein the plurality of criteria includes one or more of enhanced SRAP header information, User Equipment Identifier (UE-ID), Data Radio Bearer Identifier (DRB-ID), direction of communication, PC5 link quality and throughput, and Quality of Service (QoS) requirements.

[0243] In some embodiments, the Remote-UE selects the first sidelink based on local Quality of Service (QoS) to Data Radio Bearer (DRB) mapping and configured priority of the DRB.

[0244] In some embodiments, tracking received SRAP PDUs to determine which sidelink the SRAP PDUs were received from, and using this information for transmitting subsequent SRAP PDUs

[0245] In some embodiments, an apparatus, having one or more processors, coupled to a memory, is disclosed that is configured to cause a base station to perform any of the operations of the method 1400.

[0246] In some embodiments, an apparatus, having one or more processors, coupled to a memory, is disclosed that is configured to cause a user equipment (UE) to assist with performing any of the operations of the method 1400.

[0247] FIG. 15 illustrates an example flow chart of a method of facilitating relay communication using an intermediate UE in a flexible topology network in a wireless communication system, according to some embodiments.

[0248] The method shown in FIG. 15 may be used in conjunction with any of the systems, methods, or devices illustrated in the Figures, among other devices. In various embodiments, some of the method elements shown may be performed concurrently, in a different order than shown, or may be omitted. Additional method elements may also be performed as desired.

[0249] In accordance with an embodiment, a method 1500, for facilitating relay communication using an intermediate UE, comprises establishing two or more PC5Client Ref. No. P65096WO1 interfaces for communication with one or more of Remote-UEs, Relay-UEs, and alternative Intermediate-UEs, as in block 1510.

[0250] The method 1500 further comprises processing a Sidelink Relay Adaptation Protocol (SRAP) protocol data unit (PDU) from a tar via a first PC5 interface of the two or more PC5 interfaces, as in block 1520. The method 1500 further comprises determining a target entity based on information in an enhanced SRAP PDU header of the SRAP PDU, as in block 1530. The method 1500 further comprises forwarding the SRAP PDU to the target entity via a second PC5 interface of the two or more PC5 interfaces without modifying the enhanced SRAP PDU header, as in block 1540.

[0251] In some embodiments, the UE is an Intermediate-UE absent a Uu interface with a base station. In some embodiments, the enhanced SRAP PDU header includes a Remote-UE-ID assigned to one or more of the source entity or target entity of an end-to-end (E2E) communication. In some embodiments, the enhanced SRAP PDU header includes a BEARER-ID, wherein the BEARER-ID is a Data Radio Bearer (DRB) identifier (ID) used on Packet Data Convergence Protocol (PDCP) level. In some embodiments, the enhanced SRAP PDU header includes a direction bit indicating uplink or downlink traffic.

[0252] In some embodiments, determining the target entity is based on the direction bit in the enhanced SRAP PDU header.

[0253] In some embodiments, the method further comprises deriving traffic direction from a Radio Link Control (RLC) channel used between two UEs. In some embodiments, determining the target entity is based on criteria including SRAP PDU header information, PC5 link quality and throughput, and Quality of Service (QoS) requirements.

[0254] In some embodiments, the method further comprises tracking the SRAP PDU to determine from which PC5 interface of the two or more PC5 interfaces the SRAP PDU was received; and using tracking information to select a PC5 interface for transmitting subsequent SRAP PDUs in the opposite direction.Client Ref. No. P65096WO1

[0255] In some embodiments, for UE-to-UE communication, the enhanced SRAP PDU header includes information of both the source entity and the target entity. In some embodiments, the enhanced SRAP PDU header includes a UE-to- UE field determining when the SRAP PDU is for UE-to-RAN or UE-to-UE communication. In some embodiments, when the UE-to-UE field is set to 0, the SRAP PDU is a UE-to-base station PDU and a direction bit is valid. In some embodiments, when the UE-to-UE field is set to 1 , the SRAP PDU is a UE-to-UE PDU and a direction bit is not valid.

[0256] In some embodiments, an apparatus is disclosed that is configured to cause a base station to perform any of the operations of the method 1500.

[0257] In some embodiments, an apparatus is disclosed that is configured to cause a user equipment (UE) to assist with performing any of the operations of the method 1500.

[0258] In some embodiments, a computer program product is disclosed, comprising computer instructions which, when executed by one or more processors, perform any of the operations described with respect to the method 1500.

[0259] In some embodiments, a computer program product is disclosed, comprising computer instructions which, when executed by one or more processors, perform any of the operations described with respect to the method 1500.

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

[0261] 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 theClient Ref. No. P65096WO1 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.

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

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

[0264] 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. P65096WO1CLAIMSWhat is claimed is:1 . A method of facilitating relay communication in a user equipment (UE), the method comprising: processing a Sidelink Relay Adaptation Protocol (SRAP) protocol data unit (PDU) for a relay operation between the UE and one or more target entities, wherein the UE communicates with the one or more target entities via a first sidelink and the SRAP PDU includes an SRAP header having control information for multi-link communication; and transmitting the SRAP PDU to the one or more target entities from the UE via the first sidelink, wherein the one or more target entities are at least one or more of a UE or a base station.

2. The method of claim 1 , wherein the UE is a Remote-UE.

3. The method of claim 1 , wherein the UE is a Relay-UE.

4. The method of claim 1 , wherein the UE is an Intermediate-UE, wherein processing the SRAP PDU comprises receiving the SRAP PDU from a source UE.

5. The method of claim 2, wherein the Remote-UE has one or more PC5 interfaces communicating with at least one or more Relay-UEs and one or more Intermediate-UEs.

6. The method of claim 2, wherein the Remote-UE is absent a Uu interface with a base station.

7. The method of claim 2, wherein the Remote-UE performs end-to-endClient Ref. No. P65096WO1(E2E) communication with a base station on Packet Data Convergence Protocol (PDCP) and Service Data Adaptation Protocol (SDAP) levels.

8. The method of claim 2, wherein the Remote-UE performs one or more of adding and removing an SRAP header from one or more SRAP PDUs.

9. The method of claim 3, wherein the Relay-UE has a Uu interface with a base station.

10. The method of claim 3, wherein the Relay-UE has one or more PC5 interfaces communicating with at least one or more Relay-UEs, one or more Intermediate-UEs, and one or more Remote-UEs.

11. The method of claim 3, wherein the Relay-UE performs mapping between a standard SRAP header format and enhanced SRAP header format in the SRAP PDU.

12. The method of claim 4, wherein the Intermediate-UE does not include a Uu interface with a base station.

13. The method of claim 4, wherein the Intermediate-UE has two or more PC5 interfaces communicating with at least one or more Relay-UEs, one or more Intermediate-UEs, or one or more Remote-UEs.

14. The method of claim 4, wherein the Intermediate-UE forwards the SRAP PDU without modifying the SRAP header.

15. The method of claim 1 , wherein the SRAP header in the SRAP PDU includes a Remote-UE-ID assigned to a UE which is one or more source entities or the one or more target entities of an end-to-end (E2E)Client Ref. No. P65096WO1 communication.

16. The method of claim 1 , wherein the SRAP header in the SRAP PDU includes a BEARER-ID which is a Data Radio Bearer (DRB) identifier (ID) used at a packet data convergence protocol (PDCP) level.

17. The method of claim 3, wherein the Relay-UE performs mapping between a legacy SRAP header format used with a base station and a modified SRAP format used within a local area network between UEs.

18. The method of claim 1 , wherein for UE-to-UE communication, the SRAP header includes information of both source and destination UEs.

19. The method of claim 3, wherein, when the Relay-UE receives the SRAP PDU from a base station via the first sidelink, the Relay-UE replaces a standard SRAP header format with an enhanced SRAP header format and sets a direction bit to indicate downlink communication prior to forwarding the SRAP PDU to the one or more target entities via the first sidelink.

20. The method of claim 3, wherein, when the Relay-UE receives the SRAP PDU from a source entity via the first sidelink, the Relay-UE replaces an legacy SRAP header format with an enhanced SRAP header before transmitting the SRAP PDU to the base station via the first sidelink.

21. The method of claim 4, wherein the Intermediate-UE receives the SRAP PDU with an enhanced SRAP header, the Intermediate-UE forwards the SRAP PDU without modifying the enhanced SRAP header.Client Ref. No. P65096WO122. The method of claim 2, wherein when the Remote-UE is a source UE, the Remote-UE creates the SRAP PDU by adding an enhanced SRAP header.

23. The method of claim 1 , further comprising determining a direction of communication for the SRAP PDU by identifying which a Radio Link Control (RLC) channel is used between the UE and the one or more target entities without using a direction bit in an enhanced SRAP header.

24. The method of claim 3, wherein the Relay-UE performs mapping between a standard SRAP header format used with the base station and an enhanced SRAP header format used within a local area network between one or more UEs.

25. The method of claim 1 , wherein for UE-to-UE communication, an enhanced SRAP header is used and includes information of both the UE and the one or more target entities, including a source UE ID, a source bearer ID, a destination UE ID, and a destination bearer ID.

26. The method of claim 1 , wherein the SRAP header includes a UE-to- UE field that determines whether the SRAP PDU is for UE-to-base station or UE-to-UE communication.

27. The method of claim 1 , further comprising selecting the one or more target entities based on a plurality of criteria, wherein the plurality of criteria include one or more of enhanced SRAP header information, User Equipment Identifier (UE-ID), Data Radio Bearer Identifier (DRBID), direction of communication, PC5 link quality and throughput, and Quality of Service (QoS) requirements.Client Ref. No. P65096WO128. The method of claim 2, wherein the Remote-UE selects the first sidelink based on local Quality of Service (QoS) to Data Radio Bearer (DRB) mapping and configured priority of the DRB.

29. The method of claim 1 , further comprising tracking received SRAP PDUs to determine which sidelink the SRAP PDUs were received from, and using tracking information for transmitting subsequent SRAP PDUs.

30. A method of facilitating relay communication in an user equipment (UE), the method comprising: establishing two or more PC5 interfaces for communication with one or more of Remote-UEs, Relay-UEs, or alternative Intermediate-UEs; processing a Sidelink Relay Adaptation Protocol (SRAP) protocol data unit (PDU) from a tar via a first PC5 interface of the two or more PC5 interfaces; determining a target entity based on information in an enhanced SRAP PDU header of the SRAP PDU; and forwarding the SRAP PDU to the target entity via a second PC5 interface of the two or more PC5 interfaces without modifying the enhanced SRAP PDU header.

31. The method of claim 30, wherein the UE is an Intermediate-UE absent a Uu interface with a base station.

32. The method of claim 30, wherein the enhanced SRAP PDU header includes a Remote-UE-ID assigned to one or more of source entities or target entity of an end-to-end (E2E) communication.Client Ref. No. P65096WO133. The method of claim 30, wherein the enhanced SRAP PDU header includes a BEARER-ID, wherein the BEARER-ID is a Data Radio Bearer (DRB) identifier (ID) used on Packet Data Convergence Protocol (PDCP) level.

34. The method of claim 30, wherein the enhanced SRAP PDU header includes a direction bit indicating uplink or downlink traffic.

35. The method of claim 34, wherein determining the target entity is based on the direction bit in the enhanced SRAP PDU header.

36. The method of claim 30, further comprising deriving traffic direction from a Radio Link Control (RLC) channel used between two UEs.

37. The method of claim 30, wherein determining the target entity is based on criteria including SRAP PDU header information, PC5 link quality and throughput, and Quality of Service (QoS) requirements.

38. The method of claim 30, wherein for UE-to-UE communication, the enhanced SRAP PDU header includes information of both a source entity and the target entity.

39. The method of claim 30, wherein the enhanced SRAP PDU header includes a UE-to-UE field determining when the SRAP PDU is for UE- to-RAN or UE-to-UE communication.

40. An apparatus of a user equipment (UE) comprising: one or more processors including a baseband processor, coupled to a memory, configured to: establish a relay operation with one or more source entities via a first link and one or more target entities via a second link,Client Ref. No. P65096WO1 wherein the one or more source entities and the one or more target entities are at least one or more of a UE and a base station; decode, at the baseband processor, a Sidelink Relay Adaptation Protocol (SRAP) protocol data unit (PDU) received from a source entity from the one or more source entities via the first link; select a target entity from the one or more target entities based on the SRAP PDU; update an SRAP header of SRAP PDU based on the target entity, wherein the SRAP header is an enhanced SRAP header; and encode, with the baseband processor, the SRAP PDU having the enhanced SRAP header for transmission to the target entity via the second link.

Images