UE to network relay support for N3IWF access

Abstract

Aspects relate to relaying data between a PC5 remote UE and a network entity via an interworking function through a sidelink UE-to-NW relay access. For example, a relay UE establishes a connection with the network entity and determines whether relay access to the network entity via an interworking function device is supported at the relay UE. The relay UE then indicates to the remote UE that relay access to the network entity via the interworking function device is supported. The relay UE receives a request from the remote UE to relay data between the remote UE and the network entity via the interworking function device, and thereafter relays data between the remote UE and the network entity via the interworking function device based on the request.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to and the benefit of non-provisional application serial number 17 / 146,293 filed in the U.S. Patent and Trademark Office on January 11, 2021, and provisional application serial number 62 / 960,591 filed in the U.S. Patent and Trademark Office on January 13, 2020, the entire contents of which are incorporated herein by reference as if fully set forth below and for all applicable purposes. Technical Field

[0003] The techniques discussed below relate generally to wireless communication systems, and more specifically to relaying data between a PC5 remote UE and a network entity (e.g., a 5G core network entity) via an interworking function (e.g., N3IWF) via sidelink UE-to-network relay access. Background Art

[0004] The non-3GPP access network can be connected to the 5G core network via the non-3GPP interworking function (N3IWF). The N3IWF is connected to the 5G core network control plane function and user plane function via the N2 interface and the N3 interface respectively.

[0005] Proximity Services (ProSe) PC5 with UE to Network (NW) Relay Access A remote user equipment (UE) may be connected to a 5G core network (5GC) via an interworking function (e.g., N3IWF). Specifically, layer 3 (L3) UE to NW relay may be implemented to support relaying of remote UEs as part of system enhancements for Proximity Based Services (ProSe) in a 5G System (5GS). In such a system, a ProSe 5G UE to NW relay UE may provide functionality to support connection of a remote UE to the network by relaying the user plane (UP) traffic of the remote UE to the gNB / 5GC.

[0006] In one implementation, the remote UE may configure a non-access stratum (NAS) connection with the 5GC via the N3IWF. The UE-to-NW relay on PC5 may be another access type connected to the N3IWF. On the other hand, access traffic steering, switching and splitting (ATSSS) may be implemented at the remote UE. For example, the remote UE NAS may send a message to the 5GC supported by ASSS carried by the N3IWF.

[0007] In one implementation, the remote UE may discover the interworking function while connected to the relay UE via the side link interface. The remote UE may also establish a non-access stratum (NAS) connection with the network entity using a signaling IPsec security association (via an Internet Key Exchange (IKE) Security Association (SA) process) established using the interworking function, similar to untrusted non-3GPP access via N3IWF. The remote UE may also communicate with the network entity via the relay UE by sending data on an IPsec sub-SA established using the interworking function for a corresponding protocol data unit (PDU) session.

[0008] In another implementation, the relay UE may receive at least one relay discovery parameter from the network entity. The relay UE may also discover the interworking function based on at least one relay discovery parameter while being connected to the remote UE via the side link interface. The relay UE may also be a remote UE that establishes a single relay PDU session or a dual relay PDU session corresponding to two PDU sessions for each relay service based on at least the address of the interworking function.

[0009] In another implementation, the remote UE may determine satisfaction of the service continuity condition through a radio interface or a side link interface while being connected to the network entity via the relay UE. The remote UE may also establish a multiple access protocol data unit (MA-PDU) session via at least one of the radio interface or the IWF. The remote UE may also communicate data with the network entity via the relay UE via the radio interface or the interworking function. Summary of the invention

[0010] An overview of one or more aspects of the present disclosure is given below in order to provide a basic understanding of these aspects. This overview is not a broad overview of all expected features of the present disclosure, and is neither intended to identify the key or important elements of all aspects of the present disclosure, nor is it intended to describe the scope of any or all aspects of the present disclosure. Its sole purpose is to give some ideas of one or more aspects of the present disclosure in the form of a preface to a more detailed description given later.

[0011] Aspects of the present disclosure relate to relaying data between a remote UE and a network entity via a non-3GPP interworking function (N3IWF). In one example, a method of relaying wireless communications at a user equipment (UE) is disclosed. The method includes: establishing a connection with a network entity; determining whether sidelink relay access to a network entity via an interworking function device is supported at a relay UE; indicating to a remote UE that sidelink relay access to a network entity via an interworking function device is supported; receiving a request from a remote UE to relay data between the remote UE and the network entity via an interworking function device; and relaying data between the remote UE and the network entity via the interworking function device based on the request.

[0012] In another example, a relay user equipment (UE) for wireless communication is disclosed. The relay UE includes at least one processor, a transceiver communicatively coupled to the at least one processor, and a memory communicatively coupled to the at least one processor. The at least one processor is configured to: establish a connection with a network entity; determine whether a sidelink relay access to the network entity via an interworking function device is supported at the relay UE; indicate to a remote UE that a sidelink relay access to the network entity via an interworking function device is supported; receive a request from the remote UE to relay data between the remote UE and the network entity via the interworking function device; and relay the data between the remote UE and the network entity via the interworking function device based on the request.

[0013] In one example, a method of wireless communication at a remote user equipment (UE) is disclosed. The method includes: receiving an indication from a relay UE that a sidelink relay access to a network entity via an interworking function device is supported at the relay UE; determining that data is to be transmitted between the remote UE and the network entity via the interworking function device; sending a request to the relay UE to relay data between the remote UE and the network entity via the interworking function device; receiving a response from the relay UE indicating that the sidelink relay access to the network entity via the interworking function device is available; and when the sidelink relay access via the interworking function device is available, transmitting data between the remote UE and the network entity via the interworking function device by the relay UE.

[0014] In another example, a remote user equipment (UE) for wireless communication is disclosed. The remote UE includes at least one processor, a transceiver communicatively coupled to the at least one processor, and a memory communicatively coupled to the at least one processor. The at least one processor is configured to receive an indication from a relay UE that a sidelink relay access to a network entity via an interworking function device is supported at the relay UE; determine that data is to be transmitted between the remote UE and the network entity via the interworking function device; send a request to the relay UE to relay data between the remote UE and the network entity via the interworking function device; receive a response from the relay UE indicating that the sidelink relay access to the network entity via the interworking function device is available; and when the sidelink relay access via the interworking function device is available, transmit data between the remote UE and the network entity via the interworking function device through the relay UE.

[0015] By reading the following detailed description, these and other aspects of the present invention will be more fully understood. When reading the following description of the specific exemplary examples of the present invention in conjunction with the accompanying drawings, other aspects, features and examples of the present invention will become apparent to those of ordinary skill in the art. Although the features of the present invention can be discussed relative to some of the following examples and the accompanying drawings, all examples of the present invention can include one or more advantageous features in the advantageous features discussed herein. In other words, although one or more examples can be discussed as having certain advantageous features, one or more of these features can also be used according to the various examples of the present invention discussed herein. In a similar manner, although the exemplary examples can be discussed as equipment, system or method examples below, it should be understood that such exemplary examples can be implemented in various equipment, systems and methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1 is a schematic diagram of a wireless communication system.

[0017] Figure 2 is a conceptual illustration of an example of a radio access network.

[0018] Figure 3 An example of a wireless communication network configured to support D2D or sidelink communications is shown.

[0019] Figure 4 is a schematic diagram of the organization of radio resources in an air interface using orthogonal frequency division multiplexing (OFDM).

[0020] Figure 5 is a diagram of an OFDM air interface utilizing scalable numerologies in accordance with some aspects of the present disclosure.

[0021] Figure 6 is a diagram illustrating an exemplary wireless communication network employing D2D relay.

[0022] Figure 7 is an example architecture of a 5G core network with non-3GPP access.

[0023] Figure 8 is an example message flow for establishing 5G core network access via a non-3GPP interworking function (N3IWF) according to some aspects of the present disclosure.

[0024] Fig. 9 is a block diagram illustrating an example of a hardware implementation of an exemplary relay UE employing a processing system according to some aspects of the present disclosure.

[0025] Fig.10is a flow chart illustrating an exemplary process for relaying data between a remote UE and a network entity via an N3IWF according to some aspects of the present disclosure.

[0026] Fig.11 is a block diagram illustrating an example of a hardware implementation of an exemplary remote UE employing a processing system according to some aspects of the present disclosure.

[0027] Fig.12 is a flow chart illustrating an exemplary process for relaying data between a remote UE and a network entity via an N3IWF according to some aspects of the present disclosure. DETAILED DESCRIPTION

[0028] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configuration in which the concepts described herein can be practiced. For the purpose of providing a thorough understanding of the various concepts, the detailed description includes specific details. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid blurring these concepts.

[0029] Although various aspects and examples are described in this application by the description of some examples, it will be understood by those skilled in the art that additional implementations and use cases may occur in many different arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, various aspects and / or uses can be implemented via integrated chip examples and other devices based on non-module components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchase equipment, medical equipment, AI-enabled devices, etc.). Although some examples may or may not be specifically targeted at use cases or applications, a variety of applicability of the described innovations may occur. The range of implementations can range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or OEM devices or systems containing one or more aspects of the described innovations. In some actual settings, the devices containing the various aspects and features described may also necessarily include additional components and features for implementing and practicing the claimed and described examples. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.) The innovations described herein are intended to be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, end-user devices, etc., of various sizes, shapes, and configurations.

[0030] The various concepts presented throughout this disclosure may be implemented across a wide variety of telecommunication systems, network architectures and communication standards. Figure 1 , various aspects of the present disclosure are illustrated with reference to a wireless communication system 100, by way of illustrative example and not limitation. The wireless communication system 100 includes three interacting domains: a core network 102, a radio access network (RAN) 104, and a user equipment (UE) 106. By means of the wireless communication system 100, the UE 106 may be able to perform data communications with an external data network 110, such as (but not limited to) the Internet.

[0031] The RAN 104 may implement any suitable one or more wireless communication technologies to provide radio access to the UE 106. As an example, the RAN 104 may operate in accordance with the 3rd Generation Partnership Project (3GPP) New Radio (NR) specification (commonly referred to as 5G). As another example, the RAN 104 may operate under a mix of 5G NR and Evolved Universal Terrestrial Radio Access Network (eUTRAN) standards (commonly referred to as LTE). 3GPP refers to this hybrid RAN as the Next Generation RAN or NG-RAN. Of course, many other examples may be utilized within the scope of the present disclosure.

[0032] As shown, RAN 104 includes multiple base stations 108. Broadly speaking, a base station is a network element in a radio access network that is responsible for radio transmission and reception to or from a UE in one or more cells. In different technologies, standards, or contexts, those skilled in the art may refer to a base station as a base transceiver station (BTS), a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), an access point (AP), a node B (NB), an evolved node B (eNB), a g node B (gNB), a transmission and reception point (TRP), or some other appropriate term. In some examples, a base station may include two or more TRPs that may be co-located or non-co-located. Each TRP may communicate on the same or different carrier frequencies in the same or different frequency bands.

[0033] The wireless access network 104 is also shown to support wireless communications for multiple mobile devices. A mobile device may be referred to as a user equipment (UE) in the 3GPP standard, but may also be referred to as a mobile station (MS), a user station, a mobile unit, a user unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile user station, an access terminal (AT), a mobile terminal, a wireless terminal, a remote terminal, a handset, a terminal, a user agent, a mobile client, a client, or some other appropriate terminology by those skilled in the art. A UE may be a device that provides a user with access to network services.

[0034] Within this document, a "mobile" device does not necessarily need to have the ability to move, and can be stationary. The term mobile device or mobile device refers broadly to a wide variety of devices and technologies. A UE may include a plurality of hardware structural components of a size, shape, and arrangement to facilitate communication; such components can include antennas, antenna arrays, RF chains, amplifiers, one or more processors, etc. electrically coupled to each other. For example, some non-limiting examples of mobile devices include mobile devices, cellular (cell) phones, smart phones, session initiation protocol (SIP) phones, laptops, personal computers (PCs), notebooks, netbooks, smartbooks, tablet devices, personal digital assistants (PDAs), and a wide range of embedded systems (e.g., corresponding to the "Internet of Things" (IoT)). A mobile device may additionally be a car or other transportation vehicle, a remote sensor or actuator, a robot or robotic device, a satellite radio, a global positioning system (GPS) device, an object tracking device, a drone, a multi-axis aircraft, a quadcopter, a remote control device, a consumer and / or wearable device (such as glasses), a wearable camera, a virtual reality device, a smart watch, a health or fitness tracker, a digital audio player (e.g., an MP3 player), a camera, a game console, etc. The mobile device may also be a digital home or smart home device, such as home audio, video and / or multimedia equipment, appliances, vending machines, smart lighting, home security systems, smart meters, etc. The mobile device may also be a smart energy device, a security device, a solar panel or solar array, municipal infrastructure equipment that controls power (e.g., smart grid), lighting, water, etc., industrial automation and enterprise equipment, logistics controllers, agricultural equipment, etc. Further, the mobile device may provide connected medical or telemedicine support, such as remote health care. Telemedicine devices may include telemedicine monitoring devices and telemedicine management devices, whose communications may be given priority treatment or priority access over other types of information, for example, in terms of priority access for transmitting critical service data and / or associated QoS for transmitting critical service data.

[0035] Wireless communication between RAN 104 and UE 106 can be described as utilizing an air interface. Transmissions from a base station (e.g., base station 108) to one or more UEs (e.g., UE 106) over an air interface can be referred to as downlink (DL) transmissions. According to certain aspects of the present disclosure, the term downlink can refer to point-to-multipoint transmissions originating from a scheduling entity (further described below, e.g., base station 108). Another way to describe the scheme can be to use the term broadcast channel multiplexing. Transmissions from a UE (e.g., UE 106) to a base station (e.g., base station 108) can be referred to as uplink (UL) transmissions. According to further aspects of the present disclosure, the term uplink can refer to point-to-point transmissions initiated at a scheduled entity (further described below, e.g., UE 106).

[0036] In some examples, access to the air interface may be scheduled, wherein a scheduling entity (e.g., a base station 108) allocates resources for communication between some or all devices and apparatuses within its service area or cell. Within the present disclosure, as discussed further below, a scheduling entity may be responsible for scheduling, allocating, reconfiguring, and releasing resources for one or more scheduled entities. That is, for scheduled communications, a UE 106, which may be a scheduled entity, may utilize resources allocated by the base station / scheduling entity 108.

[0037] Base station 108 is not the only entity that can function as a scheduling entity. That is, in some examples, a UE can function as a scheduling entity that schedules resources for one or more scheduled entities (eg, one or more other UEs).

[0038] like Figure 1 As shown, a base station 108 may broadcast downlink traffic 112 to one or more UEs 106. Broadly speaking, a base station 108 is a node or device responsible for scheduling traffic in a wireless communication network, including downlink traffic 112 and, in some examples, uplink traffic 116 from one or more UEs 106 to the base station 108. On the other hand, a UE 106 is a node or device that receives downlink control information 114 from another entity in the wireless communication network, such as a base station 108, including but not limited to scheduling information (e.g., grants), synchronization or timing information, or other control information.

[0039] Typically, the base stations 108 may include a backhaul interface for communicating with a backhaul portion 120 of the wireless communication system. The backhaul 120 may provide a link between the base stations 108 and the core network 102. Additionally, in some examples, the backhaul network may provide interconnections between the various base stations 108. Various types of backhaul interfaces may be employed, such as a direct physical connection, a virtual network, or the like using any suitable transport network.

[0040] The core network 102 may be part of the wireless communication system 100 and may be independent of the radio access technology used in the RAN 104. In some examples, the core network 102 may be configured according to a 5G standard (e.g., 5GC). In other examples, the core network 102 may be configured according to a 4G Evolved Packet Core (EPC) or any other suitable standard or configuration.

[0041] Reference now Figure 2 , a schematic diagram of a RAN 200 is provided as an example and not a limitation. In some examples, the RAN 200 may be similar to that described above and in Figure 1The geographic area covered by the RAN 200 may be divided into cellular areas (cells) that can be uniquely identified by a user equipment (UE) based on an identity broadcast from an access point or base station. Figure 2 Macro cells 202, 204, and 206 and small cells 208 are shown, each of which may include one or more sectors (not shown). A sector is a sub-area of ​​a cell. All sectors within a cell are served by the same base station. A radio link within a sector can be identified by a single logical identifier belonging to the sector. In a cell divided into sectors, multiple sectors within a cell can be formed by antenna groups, where each antenna is responsible for communication with a UE in a portion of the cell.

[0042] exist Figure 2 , two base stations 210 and 212 are shown in cells 202 and 204; and a third base station 214 is shown as controlling a remote radio head (RRH) 216 in cell 206. That is, the base station can have an integrated antenna, or can be connected to an antenna or RRH via a feeder cable. In the example shown, cells 202, 204, and 126 can be referred to as macro cells because base stations 210, 212, and 214 support cells with large sizes. In addition, base station 218 is shown in a small cell 208 (e.g., a micro cell, a micro cell, a femto cell, a home base station, a home node B, a home eNode B node, etc.), which can overlap with one or more macro cells. In this example, cell 208 can be referred to as a small cell because base station 218 supports a cell with a relatively small size. Cell sizing can be accomplished based on system design and component constraints.

[0043] It should be understood that the radio access network 200 may include any number of wireless base stations and cells. In addition, relay nodes may be deployed to extend the size or coverage area of ​​a given cell. Base stations 210, 212, 214, 218 provide wireless access points to a core network (or core network entity) for any number of mobile devices. In some examples, base stations 210, 212, 214, and / or 218 may be similar to those described above and described in Figure 1 The base station / scheduling entity 108 shown in FIG.

[0044] Figure 2 Also included is a quadcopter or drone 220 that can be configured to function as a base station. That is, in some examples, a cell may not necessarily be stationary, and the geographic area of ​​a cell may move based on the location of a mobile base station such as a quadcopter 220.

[0045] Within the RAN 200, cells may include UEs that may be in communication with one or more sectors of each cell. In addition, each base station 210, 212, 214, 218, and 220 may be configured to provide access to the core network 102 (see FIG. 1 ) for all UEs in the corresponding cell. Figure 1 ) access point. For example, UEs 222 and 224 may communicate with base station 210; UEs 226 and 228 may communicate with base station 212; UEs 230 and 232 may communicate with base station 214 via RRH 216; UE 234 may communicate with base station 218; and UE 236 may communicate with mobile base station 220. In some examples, UEs 222, 224, 226, 228, 230, 232, 234, 236, 238, 240, and / or 242 may communicate with the base stations described above and described in detail in the accompanying drawings. Figure 1 The UE / scheduled entity 106 shown in FIG. 1 is the same as that shown in FIG.

[0046] In some examples, a mobile network node (e.g., quadcopter 220) can be configured to function as a UE. For example, quadcopter 220 can operate within cell 202 by communicating with base station 210.

[0047] In the radio access network 200, the ability of a UE to communicate independently of its location while moving is called mobility. Typically, in an access and mobility management function (AMF, not shown, Figure 1 Under the control of the core network 102 in the UE, various physical channels between the UE and the radio access network are established, maintained and released, wherein the access and mobility management functions may include a security context management function (SCMF) for managing security contexts for both control plane and user plane functions, and a security anchor function (SEAF) for performing authentication.

[0048] In various aspects of the present disclosure, the radio access network 200 can utilize DL-based mobility or UL-based mobility to implement mobility and handover (i.e., the transfer of a UE's connection from one radio channel to another). In a network configured for DL-based mobility, during a call with a scheduling entity, or at any other time, the UE can monitor various parameters of the signal from its serving cell and various parameters of neighboring cells. Depending on the quality of these parameters, the UE can maintain communication with one or more of the neighboring cells. During this time, if the UE moves from one cell to another, or if the signal quality from the neighboring cell exceeds the signal quality from the serving cell for a given amount of time, the UE can perform a handover or handover from the serving cell to the neighboring (target) cell. For example, a UE 224 (shown as a vehicle, but any suitable form of UE can be used) can move from a geographic area corresponding to its serving cell 202 to a geographic area corresponding to a neighboring cell 206. When the signal strength or quality from the neighboring cell 206 exceeds the signal strength or quality of its serving cell 202 for a given amount of time, the UE 224 can transmit a report message indicating the condition to its serving base station 210. In response, UE 224 may receive a handover command, and the UE may undergo a handover to cell 206 .

[0049] In a network configured for UL-based mobility, the UL reference signal from each UE can be used by the network to select a serving cell for each UE. In some examples, base stations 210, 212, and 214 / 216 can broadcast a unified synchronization signal (e.g., a unified primary synchronization signal (PSS), a unified secondary synchronization signal (SSS), and a unified physical broadcast channel (PBCH)). UE222, 224, 226, 228, 230, and 232 can receive the unified synchronization signal, derive the carrier frequency and slot timing from the synchronization signal, and send an uplink pilot or reference signal in response to the derived timing. The uplink pilot signal sent by a UE (e.g., UE 224) can be received concurrently by two or more cells (e.g., base stations 210 and 214 / 216) within the radio access network 200. Each of these cells can measure the strength of the pilot signal, and the radio access network (e.g., one or more of base stations 210 and 214 / 216 and / or a central node within the core network) can determine the serving cell for UE 224. As UE 224 moves through radio access network 200, the network may continue to monitor uplink pilot signals sent by UE 224. When the signal strength or quality of the pilot signal measured by a neighboring cell exceeds the signal strength or quality measured by a serving cell, network 200 may handover UE 224 from the serving cell to a neighboring cell with or without notifying UE 224.

[0050] Although the synchronization signals transmitted by base stations 210, 212 and 214 / 216 may be uniform, the synchronization signals may not identify a specific cell, but may identify a zone of multiple cells operating on the same frequency and / or having the same timing. The use of zones in 5G networks or other next generation communication networks implements an uplink-based mobility framework and improves the efficiency of both the UE and the network because the number of mobility messages that need to be exchanged between the UE and the network can be reduced.

[0051] In various implementations, the air interface in the radio access network 200 can utilize licensed spectrum, unlicensed spectrum, or shared spectrum. Licensed spectrum generally provides exclusive use of a portion of the spectrum with the help of a mobile network operator purchasing a license from a government regulator. Unlicensed spectrum provides shared use of a portion of the spectrum without the need for a government-granted authorization. Although it is still generally necessary to comply with some technical rules to access the unlicensed spectrum, generally, any operator or device can obtain access. Shared spectrum can fall between licensed spectrum and unlicensed spectrum, where technical rules or restrictions may be required to access the spectrum, but the spectrum can still be shared by multiple operators and / or multiple RATs. For example, the holder of a license for a portion of the licensed spectrum can provide licensed shared access (LSA) to share the spectrum with other parties, for example, with conditions determined by the appropriate licensee to obtain access.

[0052] The air interface in the radio access network 200 may utilize one or more duplex algorithms. Duplex refers to a point-to-point communication link in which two endpoints can communicate with each other in two directions. Full-duplex means that two endpoints can communicate with each other at the same time. Half-duplex means that only one endpoint can send information to the other endpoint at a time. Half-duplex emulation is often implemented for wireless links that utilize time division duplex (TDD). In TDD, transmissions in different directions on a given channel are separated from each other using time division multiplexing. That is, at some times, the channel is dedicated to transmissions in one direction, and at other times, the channel is dedicated to transmissions in another direction, where the direction can change very quickly, for example, several times per time slot. In wireless links, full-duplex channels typically rely on physical isolation of the transmitter and receiver and suitable interference cancellation techniques. Full-duplex emulation is often implemented for wireless links by utilizing frequency division duplex (FDD) or space division duplex (SDD). In FDD, transmissions in different directions can operate at different carrier frequencies (e.g., within a paired spectrum). In SDD, transmissions in different directions on a given channel are separated from each other using spatial division multiplexing (SDM). In other examples, full-duplex communication may be implemented within an unpaired spectrum (e.g., within a single carrier bandwidth), where transmissions in different directions occur within different sub-bands of the carrier bandwidth. This type of full-duplex communication may be referred to herein as sub-band full-duplex (SBFD), also known as flexible duplex.

[0053] In order to obtain a low block error rate (BLER) for transmission over the radio access network 200 while still achieving very high data rates, channel coding can be used. That is, wireless communications can typically utilize suitable error-correcting block codes. In a typical block code, an information message or sequence is split into code blocks (CBs), and an encoder (e.g., a codec) at the transmitting device then mathematically adds redundancy to the information message. Utilizing this redundancy in the encoded information message can improve the reliability of the message, enabling correction of any bit errors that may occur due to noise.

[0054] In early 5G NR specifications, user data is encoded using quasi-cyclic low-density parity check (LDPC) with two different basemaps: one basemap is used for large code blocks and / or high code rates, and the other basemap is used for other cases. Control information and the physical broadcast channel (PBCH) are encoded using polarization coding based on nested sequences. For these channels, puncturing, shortening, and repetition are used for rate matching.

[0055] However, it will be appreciated by those skilled in the art that aspects of the present disclosure may be implemented using any suitable channel code. Various implementations of the base station (e.g., scheduling entity) 108 and the UE (e.g., scheduled entity) 106 may include suitable hardware and capabilities (e.g., encoders, decoders, and / or codecs) to utilize one or more of these channel codes for wireless communication.

[0056] The air interface in the radio access network 200 may utilize one or more multiplexing and multiple access algorithms to enable simultaneous communication of various devices. For example, the 5G NR specification utilizes orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) to provide multiple access for UL transmissions from UE 222 and 224 to base station 210, and provides multiplexing for DL ​​transmissions from base station 210 to one or more UEs 222 and 224. In addition, for UL transmissions, the 5G NR specification provides support for discrete Fourier transform spread OFDM (DFT-s-OFDM) with CP (also known as single carrier FDMA (SC-FDMA)). However, within the scope of the present disclosure, multiplexing and multiple access are not limited to the above schemes, and may be provided using time division multiple access (TDMA), code division multiple access (CDMA), frequency division multiple access (FDMA), sparse code multiple access (SCMA), resource extension multiple access (RSMA), or other appropriate multiple access schemes. In addition, multiplexing of DL transmissions from base station 210 to UEs 222 and 224 may be provided using time division multiplexing (TDM), code division multiplexing (CDM), frequency division multiplexing (FDM), orthogonal frequency division multiplexing (OFDM), sparse code multiplexing (SCM), or other suitable multiplexing schemes.

[0057] In another aspect of RAN 200, sidelink signals can be used between UEs without having to rely on scheduling or control information from a base station. For example, two or more UEs (e.g., UEs 238, 240, and 242) can use peer-to-peer (P2P) or sidelink signals 237 to communicate with each other without relaying the communication through a base station. In some examples, each of UEs 238, 240, and 242 can be used as a scheduling entity or a transmitting sidelink device and / or a scheduled entity or a receiving sidelink device to schedule resources and communicate sidelink signals 237 therebetween without relying on scheduling or control information from a base station. In other examples, two or more UEs (e.g., UEs 226 and 228) within the coverage area of ​​a base station (e.g., base station 212) can also transmit sidelink signals 227 on a direct link (sidelink) without transmitting the communication through base station 212. In this example, base station 212 can allocate resources for sidelink communication to UEs 226 and 228. In either case, such sidelink signaling 227 and 237 may be implemented in a P2P network, a device-to-device (D2D) network, a vehicle-to-vehicle (V2V) network, a vehicle-to-everything (V2X), a mesh network, or other suitable direct link network.

[0058] In some examples, a D2D relay framework may be included within a cellular network to facilitate relaying of communications to / from base station 212 via a D2D link (e.g., side link 227 or 237). For example, one or more UEs (e.g., UE 228) within the coverage area of ​​base station 212 may operate as relay UEs to extend the coverage of base station 212, improve transmission reliability to one or more UEs (e.g., UE 226), and / or allow the base station to recover from a failed UE link due to, for example, congestion or fading.

[0059] Two major technologies that may be used by V2X networks include dedicated short range communications (DSRC) based on the IEEE 802.11p standard and cellular V2X based on LTE and / or 5G (New Radio) standards. Various aspects of the present disclosure may relate to New Radio (NR) cellular V2X networks, which for simplicity are referred to herein as V2X networks. However, it should be understood that the concepts disclosed herein may not be limited to a particular V2X standard, or may relate to sidelink networks other than V2X networks.

[0060] Figure 3An example of a wireless communication network 300 configured to support D2D or sidelink communications is shown. In some examples, the sidelink communications may include V2X communications. V2X communications involve the direct wireless exchange of information not only between the vehicles (e.g., vehicles 302 and 304) themselves, but also between vehicles 302 / 304 and infrastructure (e.g., roadside units (RSUs) 306) (such as streetlights, buildings, traffic cameras, toll booths, or other stationary objects), vehicles 302 / 304 and pedestrians 308, and vehicles 302 / 304 and wireless communication networks (e.g., base stations 310). In some examples, V2X communications may be implemented in accordance with the New Radio (NR) cellular V2X standard defined by 3GPP Release 16 or other suitable standards.

[0061] V2X communications enable vehicles 302 and 304 to obtain information about weather, nearby accidents, road conditions, activities of nearby vehicles and pedestrians, objects near the vehicle, and other relevant information that can be used to improve the vehicle driving experience and increase vehicle safety. For example, such V2X data can enable autonomous driving and improve road safety and traffic efficiency. For example, V2X connected vehicles 302 and 304 can use the exchanged V2X data to provide in-vehicle collision warnings, road hazard warnings, approaching emergency vehicle warnings, pre-collision / post-collision warnings and information, emergency braking warnings, forward traffic jam warnings, lane change warnings, smart navigation services, and other similar information. In addition, in the event of an impending danger, the V2X data received by the V2X-connected mobile device of the pedestrian / cyclist 308 can be used to trigger warning sounds, vibrations, flashing lights, etc.

[0062] Sidelink communications between vehicle-UEs (V-UEs) 302 and 304 or between a V-UE 302 or 304 and an RSU 306 or a pedestrian-UE (P-UE) 308 may occur over the sidelink 312 using a Proximity Services (ProSe) PC5 interface. In various aspects of the present disclosure, the PC5 interface may also be used to support D3D sidelink 312 communications in other proximity use cases. Examples of other proximity use cases may include proximity services based on public safety or business (e.g., entertainment, education, office, medical, and / or interactive). Figure 3 In the example shown, ProSe communication may also occur between UEs 314 and 316 .

[0063] ProSe communication can support different operation scenarios, such as in-coverage, out-of-coverage, and partial coverage. Out-of-coverage refers to a scenario in which UEs (e.g., V-UEs 302 and 304 and P-UE 308) are outside the coverage area of ​​a base station (e.g., base station 310), but each UE is still configured for ProSe communication. Partial coverage refers to a scenario in which some of the UEs (e.g., V-UE 304) are outside the coverage area of ​​the base station 310, while other UEs (e.g., V-UE 302 and P-UE 308) communicate with the base station 310. In-coverage refers to a scenario in which UEs (e.g., UEs 314 and 316) communicate with the base station 310 (e.g., gNB) via a Uu (e.g., cellular interface) connection to receive ProSe service authorization and provisioning information to support ProSe operation.

[0064] To facilitate D3D side link communication on side link 312, for example, between UE 314 and 316, UE 314 and 316 may send discovery signals between them. In some examples, each discovery signal may include a synchronization signal, such as a primary synchronization signal (PSS) and / or a secondary synchronization signal (SSS), which facilitates device discovery and synchronization of communications on side link 312. For example, UE 316 may utilize the discovery signal to measure the signal strength and channel state of a potential side link (e.g., side link 312) with another UE (e.g., UE 314). UE 316 may utilize the measurement results to select a UE (e.g., UE 314) for side link communication or relay communication.

[0065] In a 5G NR sidelink, the sidelink communication may utilize a transmit or receive resource pool. For example, the minimum resource allocation unit in frequency may be a subchannel (e.g., which may include, for example, 10, 15, 30, 35, 50, 75, or 100 consecutive resource blocks), and the minimum resource allocation unit in time may be a time slot. The radio resource control (RRC) configuration of the resource pool may be pre-configured (e.g., a factory setting on the UE determined by a sidelink standard or specification) or configured by a base station (e.g., base station 310).

[0066] In addition, for sidelink (e.g., PC5) communications, there may be two main resource allocation operating modes. In the first mode (mode 1), the base station (e.g., gNB) 310 may allocate resources for sidelink communications between sidelink devices to sidelink devices (e.g., V2X devices or other sidelink devices) in various ways. For example, the base station 310 may dynamically allocate sidelink resources (e.g., dynamic grants) to the sidelink devices in response to requests for sidelink resources from the sidelink devices. The base station 310 may also activate pre-configured sidelink grants (e.g., configured grants) for sidelink communications between sidelink devices. In mode 1, sidelink feedback may be reported back to the base station 310 by the sending sidelink device.

[0067] In the second mode (Mode 2), the sidelink devices can autonomously select sidelink resources for sidelink communications between them. In some examples, the transmitting sidelink device can perform resource / channel sensing to select unoccupied resources (e.g., subchannels) on the sidelink channel. The signaling on the sidelink 312 is the same between the two modes. Therefore, from the receiver's perspective, there is no difference between the modes.

[0068] Reference will be made to Figure 4 Various aspects of the present disclosure are described using the OFDM waveform schematically shown in FIG. It should be understood by those skilled in the art that various aspects of the present disclosure can be applied to DFT-s-OFDMA waveforms in substantially the same manner as described below. That is, although some examples of the present disclosure may focus on OFDM links for clarity, it should be understood that the same principles can also be applied to DFT-s-OFDMA waveforms.

[0069] In this disclosure, a frame refers to a duration of 10 ms used for wireless transmission, where each frame includes 10 subframes, each subframe is 1 ms. On a given carrier, there may be one set of frames in the UL and another set of frames in the DL. Now refer to Figure 4 , shows an expanded view of an exemplary DL subframe 402, which shows an OFDM resource grid 404. However, as will be readily appreciated by those skilled in the art, the PHY transmission structure for any particular application may differ from the examples described herein depending on any number of factors. Here, time is the horizontal direction in units of OFDM symbols; and frequency is the vertical direction in units of subcarriers or tones.

[0070] Resource grid 404 can be used to schematically represent the time-frequency resources of a given antenna port. That is, in a MIMO implementation with multiple antenna ports available, corresponding multiple resource grids 404 can be used for communication. Resource grid 404 is divided into multiple resource elements (REs) 406. RE, which is 1 subcarrier × 1 symbol, is the smallest discrete part of the time-frequency grid and contains a single complex value representing data from a physical channel or signal. Depending on the modulation used in a specific implementation, each RE can represent one or more information bits. In some examples, RE blocks can be referred to as physical resource blocks (PRBs) or more simply as resource blocks (RBs) 408, which contain any suitable number of consecutive subcarriers in the frequency domain. In one example, an RB can include 12 subcarriers, the number of which is independent of the parameter set used. In some examples, depending on the parameter set, an RB can include any suitable number of consecutive OFDM symbols in the time domain. In the present disclosure, it is assumed that a single RB such as RB 408 corresponds entirely to a single communication direction (transmission or reception for a given device).

[0071] Scheduling a UE or sidelink device (hereinafter collectively referred to as a UE) for downlink, uplink, or sidelink transmission typically involves scheduling one or more resource elements 406 within one or more subbands or bandwidth parts (BWPs). Thus, the UE typically utilizes only a subset of the resource grid 404. In some examples, an RB may be the smallest unit of resources that can be allocated to a UE. Thus, the more RBs scheduled for a UE and the higher the modulation scheme selected for the air interface, the higher the data rate for the UE. The RBs may be scheduled by a base station (e.g., a gNB, eNB, etc.) or may be self-scheduled by a UE / sidelink device implementing D2D sidelink communication.

[0072] In this illustration, RB 408 is shown as occupying less than the entire bandwidth of subframe 402, with some subcarriers shown above and below RB 408. In a given implementation, subframe 402 may have a bandwidth corresponding to any number of one or more RBs 408. Also, in this illustration, RB 408 is shown as occupying less than the entire duration of subframe 402, but this is merely one possible example.

[0073] Each 1 ms subframe 402 may consist of one or more adjacent time slots. Figure 4In the example shown in , as an illustrative example, a subframe 402 includes four time slots 410. In some examples, time slots can be defined according to a specified number of OFDM symbols with a given cyclic prefix (CP) length. For example, a time slot can include 7 or 14 OFDM symbols with a nominal CP. Other examples may include micro-slots with shorter durations (e.g., one to three OFDM symbols), sometimes referred to as shortened transmission time intervals (TTIs). In some cases, these micro-slots or shortened transmission time intervals (TTIs) can be sent, occupying resources scheduled for ongoing time slot transmissions for the same or different UEs. Any number of resource blocks can be utilized within a subframe or time slot.

[0074] An expanded view of one of the time slots 410 shows that the time slot 410 includes a control region 412 and a data region 414. In general, the control region 412 may carry control channels, and the data region 414 may carry data channels. Of course, a time slot may contain all DL, all UL, or at least one DL portion and at least one UL portion. Figure 4 The simple structure shown in is merely exemplary in nature, and different slot structures may be utilized and may include one or more of each of the control region and the data region.

[0075] Although not in Figure 4 408, but each RE 406 within RB 408 may be scheduled to carry one or more physical channels, including control channels, shared channels, data channels, etc. Other REs 406 within RB 408 may also carry pilot or reference signals. These pilot or reference signals may be used by a receiving device to perform channel estimation of the corresponding channel, which may enable coherent demodulation / detection of control and / or data channels within RB 408.

[0076] In some examples, time slot 410 may be used for broadcast, multicast, groupcast, or unicast communications. For example, broadcast, multicast, or groupcast communications may refer to point-to-multipoint transmissions from one device (e.g., a base station, UE, or other similar device) to other devices. Here, broadcast communications are delivered to all devices, while multicast or groupcast communications are delivered to multiple intended receiving devices. Unicast communications may refer to point-to-point transmissions from one device to a single other device.

[0077] In an example of cellular communication on a cellular carrier via a Uu interface, for DL ​​transmission, a scheduling entity (e.g., a base station) may allocate one or more REs 406 (e.g., within a control region 412) to one or more scheduled entities (e.g., UEs) to carry DL control information including one or more DL control channels (such as a physical downlink control channel (PDCCH)). The PDCCH carries downlink control information (DCI), including but not limited to power control commands (e.g., one or more open-loop power control parameters and / or one or more closed-loop power control parameters), scheduling information, grants, and / or allocations of REs for DL ​​and UL transmissions. The PDCCH may further carry HARQ feedback transmissions, such as an acknowledgement (ACK) or a negative acknowledgement (NACK). HARQ is a technique well known to those of ordinary skill in the art, in which the integrity of a packet transmission may be checked for accuracy at the receiving side, for example, using any suitable integrity checking mechanism, such as a checksum or a cyclic redundancy check (CRC). If the integrity of the transmission is acknowledged, an ACK may be sent, and if it is not acknowledged, a NACK may be sent. In response to the NACK, the transmitting device may send a HARQ retransmission, which may implement chase combining, incremental redundancy, and the like.

[0078] The base station may further allocate one or more REs 406 (e.g., in the control region 412 or the data region 414) to carry other DL signals, such as a demodulation reference signal (DMRS), a phase tracking reference signal (PT-RS), a channel state information (CSI) reference signal (CSI-RS), and a synchronization signal block (SSB). The SSB may be broadcast at regular intervals based on a periodicity (e.g., 5ms, 10ms, 20ms, 40ms, 80ms, or 140ms). The SSB includes a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast control channel (PBCH). The UE may utilize the PSS and SSS to achieve radio frame, subframe, time slot, and symbol synchronization in the time domain, identify the center of the channel (system) bandwidth in the frequency domain, and identify the physical cell identity (PCI) of the cell.

[0079] The PBCH in the SSB may further include a master information block (MIB), which includes various system information and parameters for decoding a system information block (SIB). The SIB may be, for example, SystemInformationType1 (SIB1), which may include various additional system information. Examples of system information sent in the MIB may include, but are not limited to, subcarrier spacing, system frame number, configuration of a PDCCH control resource set (CORESET) (e.g., PDCCH CORESET0), and search space of SIB1. Examples of additional system information sent in SIB1 may include, but are not limited to, random access search space, downlink configuration information, and uplink configuration information. The MIB and SIB1 together provide minimum system information (SI) for initial access.

[0080] In UL transmission, the scheduled entity (e.g., UE) may utilize one or more REs 406 to carry UL control information (UCI) including one or more UL control channels (such as a physical uplink control channel (PUCCH)) to the scheduling entity. UCI may include various packet types and categories, including pilots, reference signals, and information configured to enable or assist in decoding uplink data transmissions. Examples of uplink reference signals may include sounding reference signals (SRS) and uplink DMRS. In some examples, UCI may include a scheduling request (SR), i.e., a request to the scheduling entity to schedule an uplink transmission. Here, in response to the SR sent on the UCI, the scheduling entity may send downlink control information (DCI) that may schedule resources for uplink packet transmission. UCI may also include HARQ feedback, channel state feedback (CSF) (such as a CSI report), or any other suitable UCI.

[0081] In addition to control information, one or more REs 406 may be allocated for data traffic (e.g., within data region 414). Such data traffic may be carried on one or more traffic channels, such as, for DL ​​transmissions, a physical downlink shared channel (PDSCH); or for UL transmissions, a physical uplink shared channel (PUSCH). In some examples, one or more REs 406 within data region 414 may be configured to carry other signals, such as one or more SIBs and DMRS.

[0082] In an example of sidelink communication on a sidelink carrier via a PC5 interface, a control region 412 of a time slot 410 may include a physical sidelink control channel (PSCCH) including sidelink control information (SCI) sent by an initiating (transmitting) sidelink device (e.g., a Tx V2X device or other Tx UE) to a set of one or more other receiving sidelink devices (e.g., an Rx V2X device or other Rx UE). A data region 414 of the time slot 410 may include a physical sidelink shared channel (PSSCH) including sidelink data traffic sent by the initiating (transmitting) sidelink device in resources reserved by the transmitting sidelink device on the sidelink carrier via the SCI. Other information may also be sent on each RE 406 within the time slot 410. For example, HARQ feedback information may be sent from a receiving sidelink device to a transmitting sidelink device in a physical sidelink feedback channel (PSFCH) within the time slot 410.

[0083] The above description and Figure 1 and Figure 4 The channels or carriers shown in are not necessarily all channels or carriers that may be utilized between the base station 108 and the UE 106, and one of ordinary skill in the art will recognize that other channels or carriers may be utilized in addition to those shown, such as other traffic, control, and feedback channels.

[0084] These physical channels are typically multiplexed and mapped to transport channels for processing at the medium access control (MAC) layer. Transport channels carry blocks of information called transport blocks (TBs). The transport block size (TBS), which may correspond to the number of bits of information, may be a controlled parameter based on the modulation and coding scheme (MCS) and the number of RBs in a given transmission.

[0085] In OFDM, in order to maintain the orthogonality of the subcarriers or tones, the subcarrier spacing can be equal to the inverse of the symbol period. The parameter set (numerology) of the OFDM waveform refers to its specific subcarrier spacing and cyclic prefix (CP) overhead. The scalable parameter set refers to the ability of the network to select different subcarrier spacings, and therefore, for each interval, the ability to select the corresponding symbol duration (including the CP length). With the scalable parameter set, the nominal subcarrier spacing (SCS) can be scaled up or down by integer multiples. In this way, regardless of the CP overhead and the selected SC, the symbol boundaries can be aligned at certain common multiples of the symbol (for example, aligned at the boundaries of each 1ms subframe). The range of SCS can include any suitable SCS. For example, the scalable parameter set can support SCS ranging from 15kHz to 480kHz.

[0086] To illustrate this concept of scalable parameter sets, Figure 5 A first RB 502 having a nominal parameter set and a second RB 504 having a scaling parameter set are shown. As an example, the first RB 502 may have a "nominal" subcarrier spacing (SCS) of 30 kHz. n ) and a "nominal" symbol duration of 333 μs n Here, in the second RB 504, the scaling parameter set includes a scaled SCS of twice the nominal SCS, or 2×SCS n =60kHz. Since this provides twice the bandwidth per symbol, it results in a shortened symbol duration for carrying the same information. Thus, in the second RB 504, the scaling parameter set includes a scaled symbol duration of half the nominal symbol duration, or (symbol duration n )÷2=167μs.

[0087] Figure 6 is a diagram showing an exemplary wireless communication network 600 employing D2D relay. The wireless communication network 600 may correspond to, for example Figure 2 RAN 200 is shown in FIG. The wireless communication network 600 may include a fifth generation base station (eg, gNB) 604 for wireless communication with one or more UEs 602a, 602b, 602c, 602d, and 602e. Figure 6 In the example shown, base station 604 can communicate with each of UEs 602a, 602b, 602c, 602d, and 602e via respective wireless communication links 606a, 606b, 606c, 606d, and 606e. Each of wireless communication links 606a, 606b, 606c, 606d, and 606e can utilize a carrier frequency below 6 GHz or a millimeter wave carrier frequency.

[0088] In addition, a D2D relay link (side link) 608a may be established between UE 602a and another UE 602f to enable information relay between the base station 604 and the UE 602f. In this example, due to the distance or signal blocking between the base station 604 and the UE 602f, the weak reception capability of the UE 602f, the low transmission power of the UE 602f, and / or the limited battery capacity of the UE 602f, a relay link (side link) 608a may be established between the UE 602a and the UE 602f. The relay link 608a between the UE 602a and 602f may enable the communication between the base station 604 and the UE 602f to be relayed via the UE 602a through the wireless communication link (e.g., Uu interface) 606a and the relay link (e.g., side link) 608a.

[0089] exist Figure 6 In the illustrated example, UE 602a may be referred to as a source relay UE, UEs 602b-602e may be referred to as neighboring relay UEs, and UE 602f may be referred to as a remote UE. When source relay UE 602A initiates a relay node handover of remote UE 602F from source relay UE 602A to one of neighboring relay UEs 602b-602e (e.g., due to movement of UE 602a or 602f, channel change of a channel between UE 602a and 602f, battery status change of UE 602a or 602f, and / or load status change associated with UE 602a), source relay UE 602a may instruct remote UE 602f to perform a relay node handover.

[0090] In some examples, the remote UE 602f can perform relay node switching operations without assistance from the source relay UE 602a. For example, the remote UE 602f can detect one or more neighboring relay UEs 602b-602e, wake up one or more of the neighboring relay UEs 602b-602e, and receive and process discovery signals from one or more neighboring relay UEs 602b-602e. In other examples, the source relay UE 602a can assist the remote UE 602f in discovering and activating the neighboring relay UEs 602b-602e for relay node switching. For example, the source relay UE 602a may monitor a range of possible spectrum to identify the device bandwidth of each neighboring relay UE 602b-602e, exchange messages with each neighboring relay UE 602b-602e to determine the availability of each neighboring relay UE 602b-602e to relay to the remote UE 602f, and then instruct the available neighboring relay UEs 602b-602e to send a discovery signal to the remote UE 602f.

[0091] In one aspect of the present disclosure, a non-3GPP access network may be connected to a 5G core network (5GC) via a non-3GPP interworking function (N3IWF). The N3IWF is connected to the 5G core network control plane function and user plane function via the N2 interface and the N3 interface, respectively.

[0092] Figure 7It is a block diagram of a non-roaming architecture of a 5GC system (5GS) 700 with UE-to-NW relay access. In a non-roaming architecture, the 5GS can extend non-access stratum (NAS) registration and connection management on untrusted non-3GPP access using N3IWF 702 for the UE-to-NW relay path. That is, N3IWF 702 can be reached by a remote UE 704 through a UE-to-NW relay access path. The remote UE 704 can support independent 5G registration and connection management processes through the Uu interface, and support UE-to-NW relay with the 5G core network through the PC5 interface. Therefore, the 5G core network can authorize and authenticate the operation of the remote UE 704 on the UE-to-NW relay path. In addition, the remote UE 704 can discover the N3IWF 702 and use the IPSec security association with the N3IWF 702 to establish a NAS connection with the network entity. Additionally, the relay UE 706 may establish a relay PDU session (eg, shared across other remote UEs) and relay both NAS and user plane (UP) traffic to the N3IWF 702 .

[0093] In one aspect of the present disclosure, the relay service code may be used to identify whether the relay UE supports access of the remote UE to the 5G core network (or network entity) via the N3IWF. In a first example, some relay service codes (within a certain range of values) may be reserved for operation via the N3IWF.

[0094] In a second example, within each relay service code (e.g., having a length of 24 bits), a first number of bits (e.g., the first 2 or 3 bits) may be reserved to indicate the type of UE-to-network (UE-to-NW) relay access supported. For example, if the first number of bits in the relay service code is [0 0], only conventional UE-to-NW relay access is supported. If the first number of bits in the relay service code is [0 1], UE-to-NW relay access via N3IWF is supported. If the first number of bits in the relay service code is [1 0], UE-to-NW relay access via N3IWF and access service steering, switching, and sharing (ATSSS) is supported. If the first number of bits is [1 1], only UE-to-NW relay access utilizing ATSSS is supported. In some implementations, the first number of bits in the relay service code for indicating the type of UE-to-NW relay access may be extended to the first 3 or more bits to indicate other types of relay support.

[0095] In a third example, the relay UE may indicate whether each relay service code supports N3IWF access via a specific field or flag value. The specific field or flag value may be received during relay parameter provision by the ProSe function over the PC3 interface or during discovery between the relay UE and the remote UE over the PC5 interface.

[0096] As described in some of the examples above, the relay UE dynamically announces its support for 5G core network access via N3IWF. Therefore, it would be beneficial for the remote UE to indicate a request for 5G core network access to the relay UE via N3IWF. As such, various aspects of the present disclosure relate to extending the relay UE design to support dynamic control of N3IWF access.

[0097] Figure 8 800 is an example message flow for establishing 5G core network access via N3IWF. The message flow 800 may involve a remote UE 802, a UE to NW relay UE 804, a next generation radio access network (NG-RAN) 806, an access and mobility management function (AMF) 808, a session management function (SMF) 810, and a user plane function (UPF) 812.

[0098] At step 814, the UE-to-NW relay UE 804 performs a 5G system (5GS) registration process and / or attempts to establish a PDU session connection. Similarly, at step 826, the remote UE 802 performs a 5GS registration process and / or attempts to establish a PDU session connection.

[0099] In step 818, the UE to NW relay UE 804 establishes a relay PDU session with the 5G core network (or network entity). Here, the UE to NW relay UE 804 establishes a relay PDU session without accessing the N3IWF.

[0100] At step 820, the UE-to-NW relay UE 804 performs a relay discovery procedure with the remote UE 802. The relay discovery procedure may involve transmitting discovery messages (e.g., discovery advertisement messages in model A and discovery response messages in model B) between the UE-to-NW relay UE 804 and the remote UE 802. In one aspect, the UE-to-NW relay UE 804 may indicate support for accessing the 5G core network (or network entity) via N3IWF (N3IWF access) via a discovery advertisement message or a discovery response message.

[0101] For example, the UE to NW relay UE 804 can use a bit field (e.g., the first 2 or 3 bits) in one or more relay service codes to indicate whether N3IWF access is supported. One or more relay service codes may be included in the discovery message. Therefore, when the UE to NW relay UE 804 broadcasts a discovery message to the remote UE 802 during the relay discovery process, the UE to NW relay UE 804 announces its support for N3IWF access via a specific bit set in the utilized bit field of one or more relay service codes included in the discovery message. In this way, the remote UE 802 can know that the UE to NW relay UE 804 supports access to the 5G core network via N3IWF.

[0102] In another example, the UE to NW relay UE 804 may use a specific field or flag value within the discovery message to indicate whether N3IWF access is supported. The specific field or flag value may be separated from the relay service code in the discovery message. Therefore, when the UE to NW relay UE 804 broadcasts a discovery message to the remote UE 802 during the relay discovery process, the UE to NW relay UE 804 announces its support for N3IWF access via a specific field or flag value in the discovery message, without using a bit field in the relay service code. In this way, the remote UE 802 can know that the UE to NW relay UE 804 supports access to the 5G core network via N3IWF.

[0103] At step 822, if the UE-to-NW relay UE 804 advertises support for N3IWF access, the remote UE 802 may send a direct UE communication request to the UE-to-NW relay UE 804 to indicate that access to the 5G core network via N3IWF is needed / required (e.g., for a specific relay service code). That is, the remote UE 802 may send a request for UE-to-NW relay via N3IWF to the UE-to-NW relay UE 804. For example, the request may be performed by setting a field in a unicast link establishment message sent from the remote UE 802 to the UE-to-NW relay UE 804 via the PC5 interface.

[0104] In step 824, based on the indication from the remote UE 802 that access to the 5G core network is required via the N3IWF, the UE-to-NW relay UE 804 may establish a new PDU session with the 5G core network that provides relay access via the N3IWF.

[0105] At step 826, the UE-to-NW relay UE 804 may indicate the successful establishment of the PDU session with the N3IWF access by sending a direct UE communication accept message to the remote UE 802. The direct UE communication accept message may be a unicast link establishment response message including an N3IWF access available field and an N3IWF IP address (optional).

[0106] At step 828, the remote UE 802 and the UE-to-NW relay UE 804 may communicate IP address / prefix allocation information. Thereafter, at step 830, the remote UE 802 begins communicating traffic with the UE-to-NW relay UE 804, which traffic will be relayed to the 5G core network via the N3IWF. At step 832, the UE-to-NW relay UE 804 relays traffic associated with the remote UE 802 to the 5G core network via the N3IWF. Additionally or alternatively, the UE-to-NW relay UE 804 may also begin receiving data to be relayed to the remote UE 802 from the 5G core network via the N3IWF.

[0107] In one aspect, for remote UEs that do not indicate that N3IWF access is required (e.g., for a specific relay service code), the UE to NW relay UE 804 can establish a separate PDU session without N3IWF access, or the existing PDU session can be modified by setting appropriate packet filters so that the traffic of the remote UE is not routed to the N3IWF. Therefore, the traffic of the remote UE is sent directly to the data network.

[0108] Fig. 9 9 is a block diagram illustrating an example of a hardware implementation of an exemplary relay UE 900 employing a processing system 914. For example, the relay UE 900 may be Figure 1 , Figure 2 , Figure 7 and / or Figure 8 A user equipment (UE) shown in any one or more of .

[0109] The relay UE 900 may be implemented with a processing system 914 including one or more processors 904. Examples of the processor 904 include a microprocessor, a microcontroller, a digital signal processor (DSP), a field programmable gate array (FPGA), a programmable logic device (PLD), a state machine, a gated logic, a discrete hardware circuit, and other suitable hardware configured to perform various functions described throughout the present disclosure. In various examples, the relay UE 900 may be configured to perform any one or more of the functions described herein. That is, the processor 904 as utilized in the relay UE 900 may be used to implement the functions described below and described in Fig.10 Any one or more of the processes and procedures shown in .

[0110] In this example, the processing system 914 can be implemented with a bus architecture generally represented by the bus 902. Depending on the specific application of the processing system 914 and the overall design constraints, the bus 902 may include any number of interconnecting buses and bridges. The bus 902 communicatively couples various circuits including one or more processors (generally represented by the processor 904), a memory 905, and a computer-readable medium (generally represented by the computer-readable medium 906). The bus 902 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and will not be described further. The bus interface 908 provides an interface between the bus 902 and the transceiver 910. The transceiver 910 provides a communication interface or device for communicating with various other devices via a transmission medium. Depending on the nature of the device, a user interface 912 (e.g., a keyboard, a display, a speaker, a microphone, a joystick) may also be provided. Of course, such a user interface 912 is optional and may be omitted in some examples (such as a base station).

[0111] In some aspects of the present disclosure, the processor 904 may include a network connection establishment circuit 940 configured for various functions, including, for example, establishing a connection with a network entity. For example, the network connection establishment circuit 940 may be configured to implement the following Fig.10 One or more functions described herein, including, for example, block 1002. Processor 904 may also include a relay access determination circuit 942 configured for various functions, including, for example, determining whether a sidelink relay access to a network entity via an interworking function device is supported at a relay UE. For example, the relay access determination circuit 942 may be configured to implement the following regarding Fig.10 One or more functions described herein include, for example, block 1004. The processor 904 may also include a relay access indication circuit 944 configured to perform various functions, including, for example, indicating to a remote UE that a sidelink relay access to a network entity via an interworking function device is supported. For example, the relay access indication circuit 944 may be configured to implement the following regarding Fig.10One or more functions described, including, for example, block 1006. The processor 904 may also include a data relay circuit 946, which is configured for various functions, including, for example, receiving a request from a remote UE to relay data between the remote UE and the network entity via an interworking function device, relaying data between the remote UE and the network entity via the interworking function device based on the request, and for one or more remote UEs that do not indicate a request to relay data via the interworking function device, establishing a separate data session without accessing through the interworking function device, and routing data of the one or more remote UEs directly to the network entity via the separate data session, and / or modifying an existing data session by configuring an appropriate packet filter so that the data of the one or more remote UEs is not routed to the interworking function device, and routing the data of the one or more remote UEs directly to the network entity via the modified data session. For example, the data relay circuit 946 may be configured to implement the following with respect to Fig.10 One or more functions described, including, for example, blocks 1008, 1010, and 1012.

[0112] The processor 904 is responsible for managing the bus 902 and general processing, including executing software stored on the computer-readable medium 906. The software, when executed by the processor 904, causes the processing system 914 to perform the various functions described below for any particular device. The computer-readable medium 906 and memory 905 may also be used to store data manipulated by the processor 904 when executing the software.

[0113] One or more processors 904 in the processing system can execute software. Whether it is referred to as software, firmware, middleware, microcode, hardware description language or other terms, software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, processes, functions, etc. The software can reside on a computer-readable medium 906. The computer-readable medium 906 can be a non-transitory computer-readable medium. As an example, a non-transitory computer-readable medium includes a magnetic storage device (e.g., a hard disk, a floppy disk, a magnetic strip), an optical disk (e.g., a compact disk (CD) or a digital versatile disk (DVD)), a smart card, a flash memory device (e.g., a card, a stick, or a key drive), a random access memory (RAM), a read-only memory (ROM), a programmable ROM (PROM), an erasable PROM (EPROM), an electrically erasable PROM (EEPROM), a register, a removable disk, and any other suitable medium for storing software and / or instructions that can be accessed and read by a computer. The computer readable medium 906 may reside in the processing system 914, be external to the processing system 914, or be distributed across multiple entities including the processing system 914. The computer readable medium 906 may be embodied in a computer program product. For example, a computer program product may include a computer readable medium in packaging materials. Those skilled in the art will recognize how to best implement the described functionality presented throughout this disclosure depending on the specific application and the overall design constraints imposed on the entire system.

[0114] In one or more examples, the computer-readable storage medium 906 may include network connection establishment instructions 950 configured for various functions, including, for example, establishing a connection with a network entity. For example, the network connection establishment instructions 950 may be configured to implement the following regarding Fig.10 One or more functions described herein, including, for example, block 1002. The computer-readable storage medium 906 may also include relay access determination instructions 952 configured to be used for various functions, including, for example, determining whether sidelink relay access to a network entity via an interworking function device is supported at a relay UE. For example, the relay access determination instructions 952 may be configured to implement the following regarding Fig.10 One or more of the functions described herein, including, for example, block 1004. The computer-readable storage medium 906 may also include a relay access indication instruction 954, which is configured to be used for various functions, including, for example, indicating to a remote UE that a sidelink relay access to a network entity via an interworking function device is supported. For example, the relay access indication instruction 954 may be configured to implement the following about Fig.10One or more functions described, including, for example, block 1006. The computer-readable storage medium 906 may also include data relay instructions 956 configured for various functions, including, for example, receiving a request from a remote UE to relay data between the remote UE and a network entity via an interworking function device, relaying data between the remote UE and the network entity via the interworking function device based on the request, and for one or more remote UEs that do not indicate a request to relay data via the interworking function device, establishing a separate data session without access through the interworking function device, and routing data of the one or more remote UEs directly to the network entity via the separate data session, and / or modifying an existing data session by configuring appropriate packet filters so that data of the one or more remote UEs is not routed to the interworking function device, and routing data of the one or more remote UEs directly to the network entity via the modified data session. For example, the data relay instructions 956 may be configured to implement the following with respect to Fig.10 One or more of the described functions, including, for example, blocks 1008 , 1010 , and 1012 .

[0115] Fig.10 1 is a flow chart illustrating an exemplary process 1000 for relaying data between a remote UE and a network entity via a non-3GPP interworking function (N3IWF). As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and some of the illustrated features may not be required to implement all examples. In some examples, process 1000 may be performed by Fig. 9 In some examples, process 1000 may be performed by any suitable device or apparatus for performing the functions or algorithms described below.

[0116] At block 1002, the relay UE establishes a connection with a network entity (e.g., a 5G core network entity). At block 1004, the relay determines whether sidelink relay access to the network entity via an interworking function device is supported at the relay UE. The interworking function device may be a non-3GPP interworking function (N3IWF) device.

[0117] At block 1006, the relay UE indicates to the remote UE that it supports sidelink relay access to the network entity via the interworking function device. In one aspect, the relay UE indicates support by setting the value of at least one bit in the discovery message to indicate support and sending the discovery message to the remote UE (e.g., during the discovery process). For example, the at least one bit may be part of a bit field of a relay service code included in the discovery message (e.g., the first 2 or 3 bits). In another example, the at least one bit may be a specific field or flag value separate from the relay service code within the discovery message.

[0118] At block 1008, the relay UE receives a request from the remote UE to relay data between the remote UE and the network entity via the interworking function device. The request may be a sidelink unicast link establishment request message. At block 1010, the relay UE relays data between the remote UE and the network entity via the interworking function device based on the request.

[0119] On the one hand, in order to relay data, the relay UE first establishes a data session for side link relay access with the network entity via an interworking function device based on a request. After the data session is established, the relay UE sends a response to the remote UE indicating that relay access via the interworking function device is available. The response may be a side link unicast link establishment response message. The relay UE then relays data between the remote UE and the network entity via the interworking function device based on the established data session. On the one hand, the response includes a bit field having at least one bit, the at least one bit being set to indicate the availability of side link relay access via the interworking function device and / or a value of an Internet Protocol (IP) address of the interworking function device.

[0120] At block 1012, for one or more remote UEs that do not indicate a request to relay data via the interworking function device, the relay UE may optionally establish a separate data session without access through the interworking function device, and route the data of the one or more remote UEs directly to the network entity via the separate data session. Alternatively, the relay UE may optionally modify an existing data session by configuring an appropriate packet filter so as not to route the data of the one or more remote UEs to the interworking function device, and route the data of the one or more remote UEs directly to the network entity via the modified data session.

[0121] In one configuration, the relay UE 900 includes: a component for establishing a connection with a network entity (e.g., a network connection establishment circuit system 940 and / or a transceiver 910), a component for determining whether relay access to the network entity via an interworking function device is supported at the relay UE (e.g., a relay access determination circuit 942), a component for indicating support for relay access to the network entity via the interworking function device to a remote UE (e.g., a relay access indication circuit 944 and / or the transceiver 910), a component for receiving a request from the remote UE to relay data between the remote UE and the network entity via the interworking function device (e.g., a data relay circuit 946 and / or the transceiver 910), a component for relaying data between the remote UE and the network entity via the interworking function device based on the request (e.g., a data relay circuit 946 and / or the transceiver 910), and for one or more remote UEs that do not indicate a request to relay data via the interworking function device, the relay UE 900 includes a component (e.g., data relay circuit 946 and / or transceiver 910) for establishing a separate data session without accessing through an interworking function device and routing data of one or more remote UEs directly to a network entity via the separate data session, and a component (e.g., data relay circuit 946 and / or transceiver 910) for modifying an existing data session by configuring an appropriate packet filter so as not to route data of one or more remote UEs to the interworking function device and routing data of one or more remote UEs directly to the network entity via the modified data session. In one aspect, the aforementioned apparatus may be Fig. 9 The processor 904 shown in FIG. 1 is configured to perform the functions recited by the aforementioned means. On the other hand, the aforementioned means may be a circuit or any device configured to perform the functions recited by the aforementioned means.

[0122] Of course, in the above examples, the circuits included in the processor 904 are provided only as examples, and other means for performing the described functions may be included in various aspects of the present disclosure, including but not limited to instructions stored in the computer-readable storage medium 906, or in Figure 1 , Figure 2 , Figure 7 and / or Figure 8 Any of the foregoing and utilizing, for example, Fig.10 Any other suitable apparatus or device for implementing the described processes and / or algorithms.

[0123] Fig.111 is a conceptual diagram showing an example of a hardware implementation of an exemplary remote UE 1100 employing a processing system 1114. According to various aspects of the present disclosure, an element, or any portion of an element, or any combination of elements may be implemented with a processing system 1114 including one or more processors 1104. For example, the remote UE 1100 may be such as Figure 1 , Figure 2 , Figure 7 and / or Figure 8 Any one or more of the user equipments (UEs) shown in .

[0124] Processing system 1114 can be used with Fig. 9 The processing system 1014 shown in FIG. 1 is substantially the same as that shown in FIG. 1 , including a bus interface 1108, a bus 1102, a memory 1105, a processor 1104, and a computer-readable medium 1106. In addition, the remote UE 1100 may include a processor 1104 substantially similar to that described above. Fig. 9 That is, the processor 1104 as utilized in the remote UE 1100 may be used to implement the following description and in Fig.12 Any one or more of the processes shown in .

[0125] In some aspects of the present disclosure, the processor 1104 may include an indication processing circuit 1140 configured for various functions, including, for example, receiving an indication from a relay UE regarding supporting sidelink relay access to a network entity via an interworking function device at the relay UE. For example, the indication processing circuit 1140 may be configured to implement the following regarding Fig.12 The processor 1104 may also include a relay data determination circuit 1142 configured for various functions, including, for example, determining that data is to be transmitted between a remote UE and a network entity via an interworking function device. For example, the relay data determination circuit 1142 may be configured to implement the following regarding Fig.12 The processor 1104 may also include a relay access processing circuit 1144 configured for various functions, including, for example, sending a request to a relay UE to relay data between a remote UE and a network entity via an interworking function device, and receiving a response from the relay UE indicating that a sidelink relay access to the network entity via the interworking function device is available. For example, the relay access processing circuit 1144 may be configured to implement the following with respect to Fig.12The processor 1104 may also include a data communication circuit 1146 configured for various functions, including, for example, when sidelink relay access via the interworking function device is available, transmitting data between the remote UE and the network entity via the interworking function device through the relay UE. For example, the data communication circuit 1146 may be configured to implement the following with respect to Fig.12 One or more functions described, including, for example, block 1210.

[0126] In one or more examples, the computer-readable storage medium 1106 may include an indication processing instruction 1150 configured for various functions, including, for example, receiving an indication from a relay UE regarding supporting sidelink relay access to a network entity via an interworking function device at the relay UE. For example, the indication processing instruction 1150 may be configured to implement the following regarding Fig.12 The computer readable storage medium 1106 may also include relay data determination instructions 1152 configured for various functions, including, for example, determining that data is to be transmitted between a remote UE and a network entity via an interworking function device. For example, the relay data determination instructions 1152 may be configured to implement the following regarding Fig.12 One or more functions described herein, including, for example, block 1204. The computer-readable storage medium 1106 may also include relay access processing instructions 1154 configured for various functions, including, for example, sending a request to a relay UE to relay data between a remote UE and a network entity via an interworking function device, and receiving a response from the relay UE indicating that sidelink relay access to the network entity via the interworking function device is available. For example, the relay access processing instructions 1154 may be configured to implement the following regarding Fig.12 The computer-readable storage medium 1106 may also include data communication instructions 1156 configured for various functions, including, for example, transmitting data between a remote UE and a network entity via an interworking function device through a relay UE when sidelink relay access via the interworking function device is available. For example, the data communication instructions 1156 may be configured to implement the following regarding Fig.12 One or more functions described, including, for example, block 1210.

[0127] Fig.12 1 is a flow chart illustrating an exemplary process 1200 for relaying data between a remote UE and a network entity via a non-3GPP interworking function (N3IWF). As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and some of the illustrated features may not be required to implement all examples. In some examples, process 1200 may be performed by Fig.11 The process 1200 is performed by the remote UE 1100 shown in FIG. In some examples, the process 1200 can be performed by any suitable device or apparatus for performing the functions or algorithms described below.

[0128] At block 1202, the remote UE receives an indication from the relay UE that sidelink relay access to a network entity (e.g., a 5G core network entity) via an interworking function device is supported at the relay UE. The interworking function device may be a non-3GPP interworking function (N3IWF) device.

[0129] In one aspect, the indication may be included in a discovery message received from the relay UE (e.g., during a discovery process). The indication may be the value of at least one bit in the discovery message. For example, the at least one bit is a portion of a bit field of a relay service code included in the discovery message (e.g., the first 2 or 3 bits). In another example, the at least one bit may be a specific field or flag value separate from the relay service code within the discovery message.

[0130] At block 1204, the remote UE determines to transmit data between the remote UE and the network entity via the interworking function device. At block 1206, the remote UE sends a request to the relay UE to relay data between the remote UE and the network entity via the interworking function device. The request may be a sidelink unicast link establishment request message.

[0131] At block 1208, the remote UE receives a response from the relay UE indicating that sidelink relay access to the network entity via the interworking function device is available. The response may be a sidelink unicast link setup response message. In one aspect, the response includes a bit field having at least one bit set to a value indicating the availability of relay access via the interworking function device and / or an Internet Protocol (IP) address of the interworking function device.

[0132] At block 1210, when sidelink relay access via the interworking function device is available, the remote UE transmits data between the remote UE and the network entity through the relay UE via the interworking function device.

[0133] In one configuration, the remote UE 1100 includes: a component for receiving an indication from the relay UE that relay access to a network entity via an interworking function device is supported at the relay UE (e.g., an indication processing circuit 1140 and / or a transceiver 1110); a component for determining that data will be transmitted between the remote UE and the network entity via the interworking function device (e.g., a relay data determination circuit 1142); a component for sending a request to the relay UE to relay data between the remote UE and the network entity via the interworking function device (e.g., a relay data processing circuit 1144 and / or a transceiver 1110), a component for receiving a response from the relay UE indicating that relay access to the network entity via the interworking function device is available (e.g., a relay access processing circuit 1144 and / or a transceiver 1110); and a component for transmitting data between the remote UE and the network entity via the interworking function device through the relay UE when relay access via the interworking function device is available (e.g., a data communication circuit 1146). In one aspect, the aforementioned apparatus may be Fig.11 The processor 1104 shown in FIG. 1 is configured to perform the functions recited by the aforementioned means. In another aspect, the aforementioned means may be a circuit or any device configured to perform the functions recited by the aforementioned means.

[0134] Of course, in the above examples, the circuits included in the processor 1104 are provided only as examples, and other means for performing the described functions may be included in various aspects of the present disclosure, including but not limited to instructions stored in the computer-readable storage medium 1106, or in Figure 1 , Figure 2 , Figure 7 and / or Figure 8 Any of the foregoing and utilizing, for example, Fig.12 Any other suitable apparatus or device for implementing the described processes and / or algorithms.

[0135] Several aspects of wireless communication networks have been presented with reference to exemplary implementations. Those skilled in the art will appreciate that various aspects described throughout this document may be extended to other telecommunication systems, network architectures, and communication standards.

[0136] As an example, various aspects may be implemented within other systems defined by 3GPP, such as Long Term Evolution (LTE), Evolved Packet System (EPS), Universal Mobile Telecommunications System (UMTS), and / or Global System for Mobile (GSM). Various aspects may also be extended to systems defined by the Third Generation Partnership Project 2 (3GPP2), such as CDMA2000 and / or Evolution Data Optimized (EV-DO). Other examples may be implemented within systems employing IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE802.20, Ultra Wideband (UWB), Bluetooth, and / or other suitable systems. The actual telecommunication standard, network architecture, and / or communication standard employed will depend on the specific application and the overall design constraints imposed on the system.

[0137] In the present disclosure, the word "exemplary" is used to mean "serving as an example, instance, or illustration". Any implementation or aspect described herein as "exemplary" is not necessarily to be construed as being preferred or advantageous over other aspects of the present disclosure. Likewise, the term "aspect" does not require that all aspects of the present disclosure include the discussed features, advantages, or modes of operation. The term "coupled" is used herein to refer to a direct or indirect coupling between two objects. For example, if object A physically contacts object B, and object B contacts object C, objects A and C may still be considered to be coupled to each other - even if they are not directly physically in contact with each other. For example, a first object may be coupled to a second object even if the first object has never been in direct physical contact with the second object. The terms "circuit" and "circuitry" are used broadly and are intended to include both hardware implementations of electrical devices and conductors that, when connected and configured, enable the functions described in the present disclosure to be performed, without limitation to the type of electronic circuits, and software implementations of information and instructions that, when executed by a processor, enable the functions described in the present disclosure to be performed.

[0138] Figure 1-12 One or more of the components, steps, features, and / or functions shown in the drawings may be rearranged and / or combined into a single component, step, feature, or function, or implemented in several components, steps, or functions. Additional elements, components, steps, and / or functions may also be added without departing from the novel features disclosed herein. Figure 1-12 The apparatus, devices and / or components shown in the can be configured to perform one or more of the methods, features or steps described herein. The novel algorithms described herein can also be efficiently implemented in software and / or embedded in hardware.

[0139] It should be understood that the specific order or hierarchy of steps in the disclosed methods is an illustration of exemplary processes. It should be understood that the specific order or hierarchy of steps in the methods may be rearranged based on design preferences. The accompanying method claims present elements of the various steps in a sample order, and are not meant to be limited to the specific order or hierarchy presented unless specifically recited therein.

[0140] The following provides an overview of various aspects of the present disclosure:

[0141] Aspect 1: A method for relaying wireless communications at a user equipment (UE), comprising: establishing a connection with a network entity; determining whether sidelink relay access to the network entity via an interworking function device is supported at the relay UE; indicating to a remote UE that sidelink relay access to the network entity via an interworking function device is supported; receiving a request from the remote UE to relay data between the remote UE and the network entity via the interworking function device; and relaying data between the remote UE and the network entity via the interworking function device based on the request.

[0142] Aspect 2: The method according to aspect 1, wherein indicating support for sidelink relay access via an interworking function device comprises: setting a value of at least one bit in a discovery message to indicate the support; and sending a discovery message to a remote UE.

[0143] Aspect 3: The method according to aspect 1 or 2, wherein the at least one bit is part of a bit field of a relay service code included in a discovery message.

[0144] Aspect 4: The method according to any one of Aspects 1 to 3, wherein the request is a sidelink unicast link establishment request message.

[0145] Aspect 5: A method according to any one of Aspects 1 to 4, wherein the relayed data includes: establishing a data session with a network entity for side link relay access via an interworking function device based on a side link unicast link establishment request message; after establishing the data session, sending a side link unicast link establishment response message to a remote UE, wherein the side link unicast link establishment response message indicates that side link relay access via the interworking function device is available; and relaying data between the remote UE and the network entity via the interworking function device based on the established data session.

[0146] Aspect 6: A method according to any one of Aspects 1 to 5, wherein the side link unicast link establishment response message includes at least one of the following: a bit field having at least one bit set to a value for indicating the availability of side link relay access via an interworking functional device; or an Internet Protocol (IP) address of an interworking functional device.

[0147] Aspect 7: A method according to any one of Aspects 1 to 5, wherein, for one or more remote UEs that do not indicate a request to relay data via an interworking function device, the method also includes at least one of the following: establishing a separate data session without accessing through the interworking function device, and routing the data of the one or more remote UEs directly to the network entity via the separate data session; or modifying an existing data session by configuring appropriate packet filters so as not to route the data of one or more remote UEs to the interworking function device, and routing the data of the one or more remote UEs directly to the network entity via the modified data session.

[0148] Aspect 8: The method according to any one of Aspects 1 to 7, wherein the interworking function device is a non-3GPP interworking function (N3IWF) device, and the network entity is a 5G core network entity.

[0149] Aspect 9: A relay UE comprises at least one processor and a memory coupled to the at least one processor, wherein the at least one processor and the memory are configured to execute the method of any one of aspects 1 to 8.

[0150] Aspect 10: A relay UE, comprising at least one component for performing the method according to any one of aspects 1 to 8.

[0151] Aspect 11: A non-transitory computer-readable medium storing code at a relay UE, the code comprising instructions executable by a processor to perform the method of any one of aspects 1 to 8.

[0152] Aspect 12: A method for wireless communication at a remote user equipment (UE), comprising: receiving an indication from a relay UE that sidelink relay access to a network entity via an interworking function device is supported at the relay UE; determining that data is to be transmitted between the remote UE and the network entity via the interworking function device; sending a request to the relay UE to relay data between the remote UE and the network entity via the interworking function device; receiving a response from the relay UE indicating that sidelink relay access to the network entity via the interworking function device is available; and when sidelink relay access via the interworking function device is available, transmitting data between the remote UE and the network entity via the interworking function device through the relay UE.

[0153] Aspect 13: The method according to aspect 12, wherein the indication is included in a discovery message received from the relay UE.

[0154] Aspect 14: The method according to aspect 12 or 13, wherein the indication comprises a value of at least one bit in the discovery message.

[0155] Aspect 15: The method according to any one of aspects 12 to 14, wherein the at least one bit is part of a bit field of a relay service code included in a discovery message.

[0156] Aspect 16: The method according to any one of Aspects 12 to 15, wherein the request is a sidelink unicast link establishment request message.

[0157] Aspect 17: A method according to any one of Aspects 12 to 16, wherein the response is a sidelink unicast link establishment response message, and the sidelink unicast link establishment response message includes at least one of the following: a bit field having at least one bit set to a value for indicating the availability of sidelink relay access via an interworking functional device; or an Internet Protocol (IP) address of an interworking functional device.

[0158] Aspect 18: The method according to any one of Aspects 12 to 17, wherein the interworking function device is a non-3GPP interworking function (N3IWF) device, and the network entity is a 5G core network entity.

[0159] Aspect 19: A remote UE comprising at least one processor and a memory coupled to the at least one processor, wherein the at least one processor and the memory are configured to perform the method according to any one of aspects 1 to 18.

[0160] Aspect 20: A remote UE comprising at least one component for performing the method of any one of aspects 1 to 18.

[0161] Aspect 21: A non-transitory computer-readable medium storing code at a remote UE, the code comprising instructions executable by a processor to perform the method of any one of aspects 1 to 18.

[0162] To enable any person skilled in the art to practice the various aspects described herein, a previous description is provided. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but to the full range consistent with the language of the claims, wherein, unless otherwise specified, references to elements in the singular form are not intended to mean "one and only one", but to mean "one or more". Unless otherwise specifically specified, the term "some" refers to one or more. The phrase "at least one" mentioned in the list of items refers to any combination of these items, including a single member. As an example, "at least one of a, b or c" is intended to cover: a, b, c, a and b, a and c, b and c, and a, b and c. All structural and functional equivalents of elements throughout the various aspects described in this disclosure that are known or will be known to those of ordinary skill in the art are expressly incorporated herein by reference, and are intended to be covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly recorded in the claims.

Claims

1. A method for relaying wireless communications at a user equipment (UE), comprising: Establishing a connection with a network entity; determining whether sidelink relay access to a network entity via a non-3GPP interworking function (N3IWF) device is supported at a relay UE, wherein the sidelink relay access to the network entity flows at least from the relay UE to a radio access network (RAN), from the RAN to the N3IWF device, and from the N3IWF device to the network entity; Indicating to the remote UE that sidelink relay access to the network entity via the N3IWF device is supported; receiving a request from a remote UE to relay data between the remote UE and a network entity via the N3IWF device; and Based on the request, data is relayed between the remote UE and the network entity via the N3IWF device.

2. The method according to claim 1, wherein: Indication of support for sidelink relay access via N3IWF device includes: setting a value of at least one bit in a discovery message to indicate said support; and Send a discovery message to the remote UE.

3. The method according to claim 2, wherein: The at least one bit is part of a bit field of a relay service code included in the discovery message.

4. The method according to claim 1, wherein: The request is a sidelink unicast link establishment request message.

5. The method according to claim 4, wherein: The relay data includes: Establishing, with the network entity, a data session for sidelink relay access via the N3IWF device based on the sidelink unicast link establishment request message; After establishing the data session, sending a sidelink unicast link setup response message to the remote UE, the sidelink unicast link setup response message indicating that sidelink relay access via the N3IWF device is available; and Based on the established data session, data is relayed between the remote UE and the network entity via the N3IWF device.

6. The method according to claim 5, wherein: The sidelink unicast link establishment response message includes at least one of the following: a bit field having at least one bit set to a value indicating the availability of sidelink relay access via the N3IWF device; or The Internet Protocol (IP) address of the N3IWF device.

7. The method according to claim 5, wherein: For one or more remote UEs that do not indicate a request to relay data via the N3IWF device, the method further includes at least one of: Establishing a separate data session without access through the N3IWF device and routing data of one or more remote UEs directly to the network entity via the separate data session; or An existing data session is modified by configuring appropriate packet filters so as not to route data of one or more remote UEs to the N3IWF device, and the data of the one or more remote UEs is routed directly to the network entity via the modified data session.

8. The method according to claim 1, wherein: The network entity is a 5G core network entity.

9. A relay user equipment (UE) for wireless communication, comprising: at least one processor; a transceiver communicatively coupled to the at least one processor; as well as a memory communicatively coupled to the at least one processor, wherein the at least one processor is configured to: Establish a connection with a network entity, determining whether sidelink relay access to a network entity via a non-3GPP interworking function (N3IWF) device is supported at a relay UE, wherein the sidelink relay access to the network entity flows at least from the relay UE to a radio access network (RAN), from the RAN to the N3IWF device, and from the N3IWF device to the network entity, Indicate to the remote UE that sidelink relay access to the network entity via the N3IWF device is supported, receiving a request from a remote UE to relay data between the remote UE and a network entity via the N3IWF device, and Based on the request, data is relayed between the remote UE and the network entity via the N3IWF device.

10. The relay UE according to claim 9, wherein: The at least one processor configured to indicate support for sidelink relay access via an N3IWF device is configured to: setting a value of at least one bit in a discovery message to indicate said support; as well as Send a discovery message to the remote UE.

11. The relay UE according to claim 10, wherein: The at least one bit is part of a bit field of a relay service code included in the discovery message.

12. The relay UE according to claim 9, wherein: The request is a sidelink unicast link establishment request message.

13. The relay UE according to claim 12, wherein: The at least one processor configured to relay data is configured to: Establishing, with the network entity, a data session for sidelink relay access via the N3IWF device based on the sidelink unicast link establishment request message; After establishing the data session, sending a sidelink unicast link setup response message to the remote UE, the sidelink unicast link setup response message indicating that sidelink relay access via the N3IWF device is available; as well as Based on the established data session, data is relayed between the remote UE and the network entity via the N3IWF device.

14. The relay UE according to claim 13, wherein: The sidelink unicast link establishment response message includes at least one of the following: a bit field having at least one bit set to a value indicating the availability of sidelink relay access via the N3IWF device; or The Internet Protocol (IP) address of the N3IWF device.

15. The relay UE according to claim 13, wherein: For one or more remote UEs that do not indicate a request to relay data via the N3IWF device, the at least one processor is further configured to at least one of: Establishing a separate data session without access through the N3IWF device and routing data of one or more remote UEs directly to the network entity via the separate data session; or An existing data session is modified by configuring appropriate packet filters so as not to route data of one or more remote UEs to the N3IWF device, and the data of the one or more remote UEs is routed directly to the network entity via the modified data session.

16. The relay UE according to claim 9, wherein: The network entity is a 5G core network entity.

17. A method of wireless communication at a remote user equipment (UE), comprising: receiving, from a relay UE, an indication that sidelink relay access to a network entity via a non-3GPP interworking function (N3IWF) device is supported at the relay UE, wherein the sidelink relay access to the network entity flows at least from the relay UE to a radio access network (RAN), from the RAN to the N3IWF device, and from the N3IWF device to the network entity; Determining that data is to be transmitted between the remote UE and the network entity via the N3IWF device; sending a request to the relay UE to relay data between the remote UE and the network entity via the N3IWF device; receiving a response from the relay UE indicating that sidelink relay access to the network entity via the N3IWF device is available; and When sidelink relay access via the N3IWF device is available, data is transmitted between the remote UE and the network entity via the N3IWF device through the relay UE.

18. The method according to claim 17, wherein: The indication is included in a discovery message received from the relay UE.

19. The method according to claim 18, wherein: The indication comprises a value of at least one bit in the discovery message.

20. The method according to claim 19, wherein: The at least one bit is part of a bit field of a relay service code included in the discovery message.

21. The method according to claim 17, wherein: The request is a sidelink unicast link establishment request message.

22. The method according to claim 21, wherein: The response is a sidelink unicast link setup response message, and the sidelink unicast link setup response message includes at least one of the following: a bit field having at least one bit set to a value indicating the availability of sidelink relay access via the N3IWF device; or The Internet Protocol (IP) address of the N3IWF device.

23. The method according to claim 17, wherein: The network entity is a 5G core network entity.

24. A remote user equipment (UE) for wireless communication, comprising: at least one processor; a transceiver communicatively coupled to the at least one processor; as well as a memory communicatively coupled to the at least one processor, wherein the at least one processor is configured to: receiving, from a relay UE, an indication that sidelink relay access to a network entity via a non-3GPP interworking function (N3IWF) device is supported at the relay UE, wherein the sidelink relay access to the network entity flows at least from the relay UE to a radio access network (RAN), from the RAN to the N3IWF device, and from the N3IWF device to the network entity, determining that data is to be transmitted between the remote UE and the network entity via the N3IWF device, sending a request to the relay UE to relay data between the remote UE and the network entity via the N3IWF device, receiving a response from the relay UE indicating that sidelink relay access to the network entity via the N3IWF device is available, and When sidelink relay access via the N3IWF device is available, data is transmitted between the remote UE and the network entity via the N3IWF device through the relay UE.

25. The remote UE according to claim 24, wherein: The indication is included in a discovery message received from the relay UE.

26. The remote UE according to claim 25, wherein: The indication comprises a value of at least one bit in the discovery message.

27. The remote UE according to claim 26, wherein: The at least one bit is part of a bit field of a relay service code included in the discovery message.

28. The remote UE of claim 24, wherein: The request is a sidelink unicast link establishment request message.

29. The remote UE according to claim 28, wherein: The response is a sidelink unicast link setup response message, and the sidelink unicast link setup response message includes at least one of the following: a bit field having at least one bit set to a value indicating the availability of sidelink relay access via the N3IWF device; or The Internet Protocol (IP) address of the N3IWF device.

30. The remote UE of claim 24, wherein: The network entity is a 5G core network entity.

Images