Method and apparatus for providing user equipment route selection policy information for proximity-based services in 5G systems

Abstract

1. A network node of a wireless communication system supporting device-to-device (D2D) communication, the network node comprising: at least one processor; and at least one memory containing computer program code that, when executed by the at least one processor, causes the network node to provide, to at least a user equipment (UE) of the wireless communication system, a UE route selection policy including a traffic descriptor to be used by the UE for D2D communication, the traffic descriptor including information indicating use for D2D communication.

Description

[Technical Field]

[0001] The subject matter described herein relates generally to wireless communication systems, and more particularly to wireless communication systems supporting device-to-device (D2D) communication. More particularly, the subject matter described herein relates to providing and using user equipment (UE) route selection policy information for proximity-based services in 5G systems. [Background technology]

[0002] In a 5G system, device-to-device (D2D) communication can be implemented to directly communicate between devices using wireless communication. Because D2D communication is based on the proximity between user equipments (UEs) or devices, the D2D communication service can be called a proximity-based service (ProSe). ProSe is a proximity-based service using D2D communication proposed by the 3rd Generation Partnership Project (3GPP). In D2D communication, services can be used through direct communication between UEs.

[0003] To support ProSe, architectural enhancements to 5G systems are necessary. 5G systems support, among other things, direct discovery of ProSe-enabled UEs by other ProSe-enabled UEs within the same or different public land mobile network (PLMN), including in-coverage and out-of-coverage, ProSe communication and seamless service continuity when switching user traffic between a ProSe-enabled UE's Uu and PC5 paths, including in-coverage and out-of-coverage, route selection between a PC5 path and a Uu path, or route selection / switching between two PC5 paths, such as UE-to-network relay or UE-to-UE relay, service authorization and provisioning for ProSe-enabled UEs, UE-to-network relay function, and UE-to-UE relay function. For 5G system architectural enhancements and 3GPP discussions regarding ProSe, see TR 23.752 (January 2020 edition), which is incorporated herein by reference in its entirety. Summary of the Invention [Problem to be solved by the invention]

[0004] In the UE-to-network relay function, a UE that can connect to a 5G system based on a network relays traffic to / from the 5G system on behalf of a remote UE that cannot access the 5G system itself because it is outside the radio coverage of the NGRAN / base station of the 5G system network. Such a UE-to-network relay is particularly useful for using the 5G system for public safety devices. However, the architectural enhancements of the 5G system pose problems for the configuration of the UE-to-network relay. [Means for solving the problem]

[0005] According to an aspect, there can be provided a network node of a wireless communication system supporting device-to-device (D2D) communication, the network node comprising at least one processor and at least one memory containing computer program code that, when executed by the at least one processor, causes the network node to provide, to at least a user equipment (UE) of the wireless communication system, a UE route selection policy including a traffic descriptor to be used by the UE for D2D communication, the traffic descriptor including information indicating use for D2D communication.

[0006] In some embodiments of the network node, the traffic descriptor may include connection capability information indicating a capability of the connection to be used. The connection capability information may include a value representing information indicating use for D2D communication. In some embodiments, the value indicates proximity-based services of the wireless communication system as a capability of the connection to be used.

[0007] In some embodiments of the network node, the traffic descriptor may include tethering capability information representing information indicative of use for D2D communication. The tethering capability information may include one or more values ​​each indicative of a tethering method to use for D2D communication. In some embodiments, the one or more values ​​may include a value indicative of proximity-based services of the wireless communication system as the tethering method and a value indicative of Bluetooth as the tethering method.

[0008] In some embodiments of the network node, the UE route selection policy may further include one or more route selection descriptors associated with the traffic descriptor including information indicating use for relaying D2D communications. Each route selection descriptor may define parameters for setting up a connection used by the UE to relay D2D communications. In some embodiments, the parameters may include one or more of a Single Network Slice Selection Assistance Information (S-NSSAI), a Data Network Name (DNN), a path selection rule between direct and indirect proximity-based service communications over a PC5 connection, security credentials, and parameters for a PC5 connection for proximity-based services of the wireless communication system.

[0009] In some embodiments of the network node, the computer program code, when executed by at least one processor, causes the network node to provide a UE route selection policy in response to determining one of: a UE registering with a wireless communication system; a UE roaming to another public land mobile network (PLMN); a UE route selection policy for the UE has changed; a UE requesting that a UE route selection policy be provided; and a time period having elapsed.

[0010] In some embodiments of the network node, the UE may function as a UE-to-network relay that connects the UE to the wireless communication system and relays traffic to / from the wireless communication system on behalf of remote UEs, or the UE may perform tethering for remote UEs that can connect to the UE but cannot access the wireless communication system.

[0011] In some embodiments of the network node, the wireless communication system may be a 5G system and the D2D communication may be a proximity-based service.

[0012] According to another aspect, there can be provided a user equipment (UE) of a wireless communication system supporting device-to-device (D2D) communication, the user equipment comprising: at least one processor; and at least one memory including computer program code that, when executed by the at least one processor, causes the UE to receive from a network node of the wireless communication system or store in the at least one memory a UE route selection policy including at least a traffic descriptor to be used by the UE for D2D communication, the traffic descriptor including information indicating use for D2D communication.

[0013] In some embodiments of the UE, the traffic descriptor may include connection capability information indicating a capability of the connection to be used. The connection capability information may include a value representing information indicating use for D2D communication. In some embodiments, the value may indicate proximity-based services of the wireless communication system as a capability of the connection to be used.

[0014] In some embodiments of the UE, the traffic descriptor may include tethering capability information representing information indicating use for D2D communication. The tethering capability information may include one or more values ​​each indicating a tethering method to use for D2D communication. In some embodiments, the one or more values ​​may include a value indicating a proximity-based service of the wireless communication system as the tethering method and a value indicating Bluetooth as the tethering method.

[0015] In some embodiments of the UE, the UE route selection policy may further include one or more route selection descriptors associated with the traffic descriptor including information indicating use for relaying D2D communications. Each route selection descriptor may define parameters for setting up a connection used by the UE to relay D2D communications. In some embodiments, the parameters may include one or more of a Single Network Slice Selection Assistance Information (S-NSSAI), a Data Network Name (DNN), a path selection rule between direct and indirect proximity-based service communications over a PC5 connection, security credentials, and parameters for a PC5 connection for proximity-based services of the wireless communication system.

[0016] In some embodiments of the UE, the computer program code, when executed by the at least one processor, causes the UE to further match the D2D or tethering request with information indicating use for D2D communication to determine whether to select a UE route selection policy.

[0017] In some embodiments of the UE, the UE can function as a UE-to-network relay that connects the UE to the wireless communication system and relays traffic to / from the wireless communication system on behalf of a remote UE, or the UE can perform tethering for a remote UE that can connect to the UE but cannot access the wireless communication system.

[0018] In some embodiments of the UE, the wireless communication system may be a 5G system and the D2D communication may be a proximity-based service.

[0019] According to another aspect, there can be provided a method in a network node of a wireless communication system supporting device-to-device (D2D) communication, the method including providing, to a user equipment (UE) of the wireless communication system, a UE route selection policy including a traffic descriptor to be used by the UE for D2D communication, the traffic descriptor including information indicating use for the D2D communication.

[0020] According to another aspect, a method in a user equipment (UE) of a wireless communication system supporting device-to-device (D2D) communication can be provided, the method including receiving, from a network node of the wireless communication system or storing in at least one memory of the UE, a UE route selection policy including a traffic descriptor to be used by the UE for D2D communication, the traffic descriptor including information indicating use for the D2D communication.

[0021] In some embodiments of the method in the network node, the UE route selection policy is provided in response to determining one of: the UE registering with the wireless communication system; the UE roaming to another public land mobile network (PLMN); the UE route selection policy of the UE has changed; the UE requesting that the UE route selection policy be provided; and a time period having elapsed.

[0022] In some embodiments of the method in the UE, the method may further include matching the D2D or tethering request with information indicating a use for D2D communication to determine whether to select a UE route selection policy.

[0023] In some embodiments of the method, the traffic descriptor may include connection capability information indicating a capability of the connection to be used, the connection capability information including a value representing information indicating use for D2D communication. In some embodiments, the value may indicate proximity-based services of the wireless communication system as a capability of the connection to be used.

[0024] In some embodiments of the method, the traffic descriptor may include tethering capability information representing information indicating use for D2D communication. The tethering capability information may include one or more values ​​each indicating a tethering method to use for D2D communication. In some embodiments, the one or more values ​​may include a value indicating a proximity-based service of the wireless communication system as the tethering method and a value indicating Bluetooth as the tethering method.

[0025] In some embodiments of the method, the UE route selection policy may further include one or more route selection descriptors associated with the traffic descriptor that includes information indicating use for relaying D2D communications, each route selection descriptor may define parameters for setting up a connection used by the UE to relay D2D communications.

[0026] In some embodiments of the method, the parameters may include one or more of a single network slice selection assistance information (S-NSSAI), a data network name (DNN), a routing rule between direct proximity-based service communication and indirect proximity-based service communication over a PC5 connection, a security certificate, and parameters for a PC5 connection of the proximity-based service of the wireless communication system.

[0027] In some embodiments of the method, the UE can function as a UE-to-network relay that connects the UE to the wireless communication system and relays traffic to / from the wireless communication system on behalf of a remote UE, or the UE can perform tethering for a remote UE that can connect to the UE but cannot access the wireless communication system.

[0028] In some embodiments of the method, the wireless communication system may be a 5G system and the D2D communication may be a proximity-based service.

[0029] According to a further aspect, a computer program product comprises program instructions stored on a computer readable medium for performing the steps according to any one of the above method embodiments when the program is run on a computer.

[0030] The above aspects and features may be implemented in a system, an apparatus, a method, an article, and / or a non-transitory computer-readable medium, depending on the desired configuration. The subject matter described herein may be implemented in and / or used in conjunction with several different types of devices, including, but not limited to, mobile phones, tablet computers, wearable computing devices, portable media players, and any of a variety of other computing devices.

[0031] This summary is intended to provide a brief overview of some of the aspects and features of the subject matter described herein. Accordingly, it should be understood that the above features are examples only and should not be construed as narrowing the scope of the subject matter described herein in any way. Other features, aspects, and advantages of the subject matter described herein will become apparent from the following detailed description, drawings, and claims.

[0032] The subject matter described herein can be better understood when considered in conjunction with the following detailed description of various embodiments and the following drawings. [Brief explanation of the drawings]

[0033] [Figure 1] FIG. 1 illustrates a simplified wireless communication system according to some embodiments. [Figure 2] FIG. 1 illustrates an example 5G network that supports user equipment route selection policies, according to some embodiments. [Figure 3] FIG. 1 illustrates a simplified block diagram of a UE according to some embodiments. [Figure 4] FIG. 1 illustrates a simplified block diagram of a network node according to some embodiments. [Figure 5] FIG. 1 illustrates an exemplary 5G system architecture enhancement that supports ProSe, according to some embodiments. [Figure 6] FIG. 1 illustrates a simplified sequence flow between a UE and a network node for providing or updating a UE route selection policy, according to some embodiments. [Figure 7A] 1 is a flowchart of a method for providing a UE route selection policy according to some embodiments. [Figure 7B] 1 is a flowchart of a method for providing a UE route selection policy according to some embodiments. DETAILED DESCRIPTION OF THE INVENTION

[0034] Figure 1 illustrates a simplified wireless communication system 100 according to some embodiments. It should be noted that the system of Figure 1 is only one example of a possible system, and that features of the subject matter described herein may be implemented in any of a variety of systems, as desired.

[0035] As shown, the wireless communication system 100 includes a base station 110-1 that communicates with one or more user devices 120 over a transmission medium. In FIG. 1, only three user devices 120-1, 120-2, and 120-3 are shown, but are not limited to these. Each of the user devices 120-1, 120-2, and 120-3 may be referred to herein as a "user equipment" (UE). Accordingly, the user devices 120 are referred to as UEs or UE devices.

[0036] As used herein, the term "user equipment" can refer to any of various types of computer system devices that are mobile or portable and that communicate wirelessly. Examples of UE include mobile phones or smartphones, portable gaming devices, laptops, wearable devices (e.g., smart watches, smart glasses), personal digital assistants (PDAs), portable Internet devices, music players, data storage devices, or other handheld devices. In general, the term "UE" or "UE device" can be broadly defined to encompass any electronic, computing, and / or telecommunications device (or combination of devices) that is easily carried by a user and capable of wireless communication.

[0037] Base station (BS) 110-1 may be a Base Transceiver Station (BTS) or cell site (“cellular base station”) and may include hardware that enables wireless communication with UE 120.

[0038] As used herein, the term "base station" has the full scope of its ordinary meaning and includes at least a wireless communication station that is installed at a fixed location and used for communication as part of a wireless telephone or wireless system.

[0039] A communication area (or coverage area) of the base station 110 may be referred to as a “cell.” The base station 110 and the UE 120 may be configured to communicate over a transmission medium using any of a variety of radio access technologies (RATs), also referred to as wireless communication technologies or telecommunications standards, such as GSM, UMTS (e.g., associated with a WCDMA or TD-SCDMA air interface), LTE, LTE-Advanced (LTE-A), 5G New Radio (5GNR), HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), etc. If the base station 110-1 is implemented in the context of LTE, the base station 110-1 may alternatively be referred to as an “eNodeB” or “eNB.” If the base station 110-1 is implemented in the context of 5G NR, the base station 110-1 may alternatively be referred to as a “gNodeB” or “gNB.”

[0040] As shown, base station 110-1 may be equipped to communicate with network 130 (e.g., a cellular service provider's core network, a telecommunications network such as the Public Switched Telephone Network (PSTN), and / or the Internet, among other possibilities). Thus, base station 110-1 may facilitate communications between user devices 120 and / or between user devices 120 and network 130. In particular, cellular base station 110-1 may provide various telecommunications capabilities to UEs 120, such as voice, SMS, and / or data services.

[0041] Thus, base station 110-1 and other similar base stations (e.g., base stations 110-2, 110-3) operating according to the same or different cellular communication standards may be provided as a network of cells that can provide continuous or near-continuous overlapping service to UE 120 and similar devices over a geographic area via one or more cellular communication standards.

[0042] Thus, as shown in FIG. 1, base station 110-1 may function as a “serving cell” for UE 120, while each UE 120 may also receive signals from (and possibly be within communication range of) one or more other cells (which may be provided by base station 110 and / or any other base station), which may be referred to as “neighbor cells.” Such cells may be capable of facilitating communication between user devices 120 and / or between user devices 120 and network 130. Such cells may include “macro” cells, “micro” cells, “pico” cells, and / or cells providing any of various other granularity of coverage area sizes. For example, base stations 110-1 and 110-2 shown in FIG. 1 may be macro cells, and base station 110-3 may be a micro cell. Other configurations are possible.

[0043] In some embodiments, the base station 110-1 may be a next-generation base station, e.g., a 5G New Radio (5G NR) base station or "gNB." In some embodiments, the gNB may be connected to a legacy evolved packet core (EPC) network and / or an NR core (NRC) network. In addition, a gNB cell may include one or more transition and reception points (TRPs). In addition, a UE capable of operating according to 5G NR may be connected to one or more TRPs in one or more gNBs.

[0044] UE 120 may be capable of communicating using multiple wireless communication standards. For example, UE 120 may be configured to communicate using at least one cellular communication protocol (e.g., GSM, UMTS (e.g., associated with a WCDMA or TD-SCDMA air interface), LTE, LTE-A, 5G NR, HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), etc.), in addition to a wireless network protocol (e.g., Wi-Fi) and / or a peer-to-peer wireless communication protocol (e.g., Bluetooth, Wi-Fi peer-to-peer, etc.). UE 120 may also, or instead, be configured to communicate using one or more global navigation satellite systems (GNSS, e.g., GPS or GLONASS), one or more mobile television broadcast standards (e.g., ATSC-M / H or DVB-H), and / or any other wireless communication protocol, as desired. Other combinations of wireless communication standards (including three or more wireless communication standards) are possible.

[0045] Figure 2 illustrates an example 5G network 200 supporting a User Equipment Route Selection Policy (URSP), according to some embodiments. The 5G New Radio (NR) network 200 includes a user equipment (UE) 201, a base station (gNB) 202, an access and mobility management function (AMF) 203, a session management function (SMF) 204, a policy control function (PCF) 205, and a unified data management (UDM) 206. In the example of Figure 2, the UE 201 and its serving base station (gNB) 202 belong to a part of a radio access network (RAN) 220. At the access stratum (AS), the RAN 220 provides radio access to the UE 201 via a radio access technology (RAT). At the non-access stratum (NAS), the AMF 203 communicates with the gNB 202 and the 5G Global Control (5GC) 204 for access and mobility management of radio access devices in the 5G network 200. The UE 201 may be equipped with a radio frequency (RF) transceiver or multiple RF transceivers for different application services over different RATs / CNs.

[0046] The 5G network 200 may be a packet-switched (PS) Internet Protocol (IP) network. This means that the network delivers all data traffic in IP packets, providing users with always-on IP connectivity. When the UE 201 subscribes to the 5G network 200, a packet data network (PDN) address (i.e., an address usable in the PDN) is assigned to the UE 201 for connection to the PDN. In 4G, EPS defined a default EPS bearer to provide always-on IP connectivity. In 5G, the Protocol Data Unit (PDU) Session Establishment procedure is a parallel procedure to the 4G PDN connection procedure. A PDU session (e.g., 130) defines the association between the UE 201 and the data network that provides the PDU connection service. Each PDU session 130 is identified by a PDU session ID and can include multiple QoS flows and QoS rules.

[0047] User equipment policies for 5G networks include a user equipment route selection policy (URSP) and an access network discovery and selection policy (ANDSP). User equipment policies can be delivered to the UE 201 from the PCF 205. The PCF 205 processes network policies for managing network behavior. The PCF 205 obtains subscription information from the UDM 206. The PCF 205 interfaces with both the AMF 203 for managing mobility context and the SMF 204 for managing session context. The PCF 205 also plays an important role in providing schemes for network slicing and roaming. The PCF 205 triggers URSPs to enable the UE 201 to determine how to handle certain applications in the context of an existing or new protocol data unit (PDU) session. User equipment policies may be preconfigured in the UE 201. A preconfigured policy should be applied by the UE 201 only when the UE 201 has not received a policy of the same type from the PCF 205.

[0048] 3 is a simplified block diagram of a UE 120 according to some embodiments. Note that the block diagram of the UE 120 in FIG. 3 is only one example of a possible user device. According to embodiments, the UE 120 may be, among other devices, a user device, a mobile device or station, a wireless device or station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or handheld computing device), a tablet, and / or a combination of devices.

[0049] As shown, the UE 120 may include a set of components configured to perform core functions. For example, the set of components may be implemented as a system on a chip (SOC) and may include portions for various purposes. Alternatively, the set of components may be implemented as separate components or groups of components for various purposes. The set of components may be communicatively connected (e.g., communicatively, directly or indirectly) to various other circuits of the UE 120.

[0050] The UE 120 may include at least one antenna 312 in communication with a transmitter 314 and a receiver 316. Alternatively, the transmit and receive antennas may be separate. The UE 120 may also include a processor 320 configured to provide signals to and receive signals from the transmitter 314 and receiver 316 and to control functionality of the UE 120. The processor 320 may be configured to control functionality of the transmitter 314 and receiver 316 by providing control signal transmissions via electrical leads to the transmitter 314 and receiver 316. Similarly, the processor 320 may be configured to control other elements of the UE 120 by providing control signal transmissions via electrical leads connecting the processor 320 to other elements, such as a display or memory. Processor 320 may be embodied in a variety of ways, including, for example, as a circuit, at least one processing core, one or more microprocessors with an associated digital signal processor, one or more processors without an associated digital signal processor, one or more coprocessors, one or more multi-core processors, one or more controllers, processing circuitry, one or more computers, various other processing elements including integrated circuits (e.g., application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), etc.), or combinations thereof. Thus, although shown as a single processor in FIG. 3, in some example embodiments, processor 320 may include multiple processors or processing cores.

[0051] UE 120 may be capable of operating according to one or more air interface standards, communication protocols, modulation types, access types, etc. Signals transmitted and received by processor 320 may include signaling information according to applicable cellular system air interface standards and / or any number of different wired or wireless network technologies, including, but not limited to, Wi-Fi, Wireless Local Access Network (WLAN) technologies such as Institute of Electrical and Electronics Engineers (IEEE) 802.11, 802.16, 802.3, ADSL, DOCSIS, etc. Additionally, these signals may include voice data, user-generated data, user-requested data, etc.

[0052] For example, UE 120 and / or a cellular modem within UE 120 may be capable of operating according to various first-generation (1G) communication protocols, second-generation (2G or 2.5G) communication protocols, third-generation (3G) communication protocols, fourth-generation (4G) communication protocols, fifth-generation (5G) communication protocols, Internet Protocol Multimedia Subsystem (IMS) communication protocols (e.g., Session Initiation Protocol (SIP)), etc. For example, UE 120 may be capable of operating according to 2G wireless communication protocols IS-136, Time Division Multiple Access (TDMA), Global System for Mobile Communications, GSM, IS-95, Code Division Multiple Access (CDMA), etc. Additionally, for example, UE 120 may be capable of operating according to 2.5G wireless communication protocols General Packet Radio Service (GPRS), Enhanced Data GSM Environment (EDGE), etc. Further, for example, the UE 120 may be capable of operating according to a 3G wireless communication protocol, such as Universal Mobile Telecommunications System (UMTS), Code Division Multiple Access 2000 (CDMA2000), Wideband Code Division Multiple Access (WCDMA), Time Division-Synchronous Code Division Multiple Access (TD-SCDMA), etc. The UE 120 may also be capable of operating according to a 3.9G wireless communication protocol, such as Long Term Evolution (LTE), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), etc. Further, for example, the UE 120 may be capable of operating according to a 4G wireless communication protocol, such as LTE Advanced, 5G, etc., and similar wireless communication protocols that may be developed in the future.

[0053] It should be understood that the processor 320 may include circuits for implementing the audio / visual and logic functions of the UE 120. For example, the processor 320 may include a digital signal processor device, a microprocessor device, an analog-to-digital converter, a digital-to-analog converter, etc. The control and signal processing functions of the UE 120 may be allocated among these devices according to their respective capabilities. The processor 320 may further include an internal voice coder (VC) 320a, an internal data modem (DM) 320b, etc. Furthermore, the processor 320 may include functionality for operating one or more software programs, which may be stored in memory. Generally, the processor 320 and the stored software instructions may be configured to cause the UE 120 to perform actions. For example, the processor 320 may be capable of operating a connectivity program, such as a web browser. The connectivity program may enable the UE 120 to send and receive web content, such as location-based content, according to protocols such as Wireless Application Protocol (WAP), Hypertext Transfer Protocol (HTTP), etc.

[0054] The UE 120 may also include a user interface that may be operatively connected to the processor 320, including, for example, an earpiece or speaker 324, a ringer 322, a microphone 326, a display 328, a user input interface, etc. The display 328, as described above, may include a touch-sensitive display that a user can touch and / or gesture to make selections, input values, etc. The processor 320 may also include user interface circuitry configured to control at least some functions of one or more elements of the user interface, such as the speaker 324, the ringer 322, the microphone 326, and the display 328. The processor 320 and / or user interface circuitry that includes the processor 320 may be configured to control one or more functions of one or more elements of the user interface through computer program instructions, e.g., software and / or firmware, stored in a memory accessible to the processor 320, e.g., a volatile memory 340, a non-volatile memory 342, etc. The UE 120 may include a battery for powering various circuitry associated with the mobile terminal, e.g., a circuit that provides mechanical vibrations as a detectable output. The user input interface may include devices from which the UE 120 can receive data, such as a keypad 330 (which may be a virtual keyboard shown on the display 328 or an externally connected keyboard) and / or other input devices.

[0055] As shown in FIG. 3 , the UE 120 may also include one or more mechanisms for sharing and / or obtaining data. For example, the UE 120 may include a short-range radio frequency (RF) transceiver and / or interrogator 364 so that data can be shared with and / or obtained from electronic devices according to RF technology. The UE 120 may include an infrared (IR) transceiver 366, a Bluetooth™ transceiver 368 operating using Bluetooth™ (BT) wireless technology, a wireless universal serial bus (USB) transceiver 370, other short-range transceivers such as a Bluetooth™ low energy transceiver, a ZigBee transceiver, an ANT transceiver, a cellular device-to-device transceiver, a wireless local area link transceiver, and / or any other short-range wireless technology. The UE 120, and in particular the short-range transceiver, may be capable of transmitting data to and / or receiving data from the electronic device within proximity of the device, such as within 10 meters. The UE 120, which includes a Wi-Fi or wireless local area network modem, may be capable of transmitting data to and / or receiving data from electronic devices according to various wireless network technologies, including WLAN technologies such as 6LoWpan, Wi-Fi, low power Wi-Fi, IEEE 802.11 technology, IEEE 802.15 technology, IEEE 802.16 technology, and the like.

[0056] The UE 120 may include memory, such as a subscriber identity module (SIM) 338, a removable user identity module (R-UIM), an eUICC, or a UICC, capable of storing information elements associated with a mobile subscriber. In addition to the SIM, the UE 120 may include other removable and / or fixed memory. The UE 120 may include volatile memory 340 and / or nonvolatile memory 342. For example, the volatile memory 340 may include random access memory (RAM), including dynamic and / or static RAM, on-chip or off-chip cache memory, etc. The non-volatile memory 342, which may be embedded and / or removable, may include, for example, read-only memory, flash memory, magnetic storage devices, such as hard disks, floppy disk drives, magnetic tape, optical disk drives and / or media, non-volatile random access memory (NVRAM), etc. Like the volatile memory 340, the non-volatile memory 342 may include a cache area for temporary storage of data. At least a portion of the volatile and / or non-volatile memory may be incorporated into the processor 320. The memory may store one or more software programs, instructions, information, data, etc. that may be used by the device to perform the operations disclosed herein.

[0057] The memory may include an identifier, such as an International Mobile Equipment Identity (IMEI) code or a PEI (Permanent Equipment Identifier as defined in 3GPP TS 23.501), that can uniquely identify the mobile device of UE 120. In an exemplary embodiment, processor 320 may be configured to use computer code stored in memory 340 and / or 342 to cause processor 320 to perform the operations disclosed herein.

[0058] Some of the embodiments disclosed herein may be implemented in software, hardware, application logic, or a combination of software, hardware, and application logic. The software, application logic, and / or hardware may reside, for example, in memory 340, processor 320, or other electronic components. In some exemplary embodiments, the application logic, software, or instruction set is maintained on any one of a variety of conventional computer-readable media. In the context of this specification, a "computer-readable medium" may be any non-transitory medium that can contain, store, communicate, propagate, or transmit instructions used by or associated with an instruction execution system, apparatus, or device, such as a computer or data processor circuit; in the example shown in FIG. 3, the computer-readable medium may include a non-transitory computer-readable storage medium, which may be any medium that can contain or store instructions used by or associated with an instruction execution system, apparatus, or device, such as a computer.

[0059] FIG. 4 is a simplified block diagram of a network node 411 according to some embodiments. The network node 411 may be a base station combined with an MME or an AMF. The network node 411 has an antenna 415 for transmitting and receiving radio signals. A radio frequency (RF) transceiver module 414 connected to the antenna receives RF signals from the antenna 415, converts the RF signals to baseband signals, and transmits them to a processor 413. The RF transceiver 414 also converts the baseband signals received from the processor 413, converts the baseband signals to RF signals, and transmits them to the antenna 415. The processor 413 processes the received baseband signals and invokes different function modules to perform functions in the network node 411. A memory 412 stores program instructions and data 420 for controlling the operation of the network node 411. In the example of FIG. 4, the network node 411 also includes a protocol stack 480 and a set of control function modules and circuits 490. A PDU session processing circuit 431 processes PDU session establishment and modification procedures. The policy control module 432 configures policy rules for the UE. The configuration and control circuitry 433 provides different parameters for configuring and controlling the UE for related functions, including mobility management and session management. Suitable processors include, by way of example, dedicated processors, digital signal processors (DSPs), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) circuit, and other types of integrated circuits (ICs), and / or state machines.

[0060] FIG. 5 illustrates an example 5G system architecture enhancement that supports ProSe, according to some embodiments.

[0061] A remote UE 510 that does not have access to the 5G core network 540 is connected to a UE 520 acting as a UE-to-network relay via an NR PC5 connection 515. The UE 520 is connected to a base station (gNB) 530 via an NR Uu connection 525 and can access the 5G core network 540. The UE 520 acting as a UE-to-network relay relays traffic to / from the 5G core network 540 and / or data network (DN) 550 on behalf of the remote UE 510. In some embodiments, the UE 520 can perform tethering for the remote UE 510.

[0062] Figure 6 illustrates a simplified sequence flow between a UE and a network node for providing or updating a UE route selection policy, according to some embodiments. The UE may be the UE 120 shown in Figure 1 or a UE acting as a UE-to-network relay 520 shown in Figure 5. The network node may be the base station 110 shown in Figure 1, the gNB 530 shown in Figure 5, or any entity implementing a PCF (such as the PCF 205 shown in Figure 2).

[0063] Optionally or additionally, in step 610, the UE may store in its memory a UE route selection policy including a traffic descriptor used by the UE for D2D communication. In step 620, the UE may register, roam to another PLMN, or request that a UE route selection policy be provided. More specifically, the network node may determine whether to provide the UE route selection policy to the UE in response to, but not limited to, these examples of step 620 (not shown in FIG. 6). The network node may also determine that the UE route selection policy of the UE has changed and / or that a time period for providing / updating the UE route selection policy has elapsed.

[0064] In step 630, the network (e.g., PCF via AMF and gNB) provides the UE with a UE route selection policy including a traffic descriptor to be used by the UE for D2D communication. The traffic descriptor includes information indicating use for D2D communication. Examples of the UE route selection policy and the traffic descriptor to be used by the UE for D2D communication will be described later. The UE receives the UE route selection policy and stores the received UE route selection policy as a default setting or updates a previously received or pre-stored UE route selection policy.

[0065] In step 640, the UE checks the D2D or tethering request against the URSP information (received in step 630) indicating use for D2D communication to determine whether to select a UE route selection policy. Step 640 may be performed in response to a request to act as a network relay received by the UE 520 from a remote UE 510 or in response to initiation of a tethering process.

[0066] In step 650, the UE configures connections that the UE uses to support D2D and tethering communications. For example, the UE can configure an NR PC5 connection 515 with a remote UE 510 and / or an NR Uu connection 525 with a gNB 530 to relay traffic between the PC5 and the 5G core. The UE can use parameters defined by a route selection descriptor associated with a traffic descriptor that includes information related to D2D and / or tethering. Example parameters include, but are not limited to, S-NSSAI, DNN, SSC mode, PDU session type, route selection rules between direct and indirect ProSe communications over the NR PC5 connection, security certificates, and parameters for the NR PC5 connection.

[0067] 7A is a flowchart of a method for providing a UE route selection policy according to some embodiments. The method may be performed by a network node (such as the base station 110 shown in FIG. 1 or the PCF 205 shown in FIG. 2) of a wireless communication system (such as the wireless communication system 100 shown in FIG. 1 or the 5G system 200 shown in FIG. 2) that supports device-to-device (D2D) communication (e.g., ProSe or UE-to-network relay).

[0068] In step 710, the network node 110 determines whether to provide a UE route selection policy to the UE 120. In some examples, the network node may determine that the UE 120 has registered with the wireless communication system 100 or that the UE 120 roams to another PLMN. In other examples, the network node 110 may determine that the UE route selection policy of the UE 120 has changed or that a period of time has elapsed. In other words, the network node may update the UE route selection policy at a given period of time. Also, the UE 120 may request the network node 110 to provide the UE route selection policy.

[0069] In step 720, in response to the determination in step 710, the network node 110 provides the UE 120 with a UE route selection policy including a traffic descriptor to be used by the UE for D2D communication. The traffic descriptor includes information indicating use for D2D communication. Examples of the UE route selection policy and the traffic descriptor to be used by the UE for D2D communication will be described later.

[0070] 7B is a flowchart of a method for receiving a UE route selection policy according to some embodiments. The method may be performed by a UE (such as the UE 120 shown in FIG. 1 or the UE 201 shown in FIG. 2) of a wireless communication system (such as the wireless communication system 100 shown in FIG. 1 or the 5G system 200 shown in FIG. 2) that supports device-to-device (D2D) communication (e.g., ProSe or UE-to-network relay).

[0071] In step 730, the UE 120 receives from the network node 110 a UE route selection policy including a traffic descriptor that the UE 120 uses for D2D communication. In another example, additionally or optionally, the UE 120 can pre-store the UE route selection policy in memory. The traffic descriptor includes information indicating use for D2D communication. Examples of the UE route selection policy and the traffic descriptor that the UE uses for D2D communication are described below.

[0072] The UE 120 may receive the UE route selection policy from the wireless communication system 100 via the network node 110 when the UE 120 registers with the wireless communication system 100, when the UE 120 roams to another PLMN, and / or when the UE 120 requests the network node 110 to provide the UE route selection policy. The UE 120 may also receive the UE route selection policy from the network node 110 when the UE route selection policy changes and / or when a time period has elapsed.

[0073] In step 740, the UE matches the D2D or tethering request with the URSP information (received in step 730) indicating use for D2D communication to determine whether to select a UE route selection policy. Step 740 may be performed in response to a request to act as a network relay received by the UE 520 from the remote UE 510 or in response to initiation of a tethering process. Upon selecting a UE route selection policy or traffic descriptor, the UE 120 can set up an NR PC5 connection 515 with the remote UE 510 and / or an NR Uu connection 525 with the gNB 530 to relay traffic between the PC5 and the 5G core using parameters included in the UE route selection policy or traffic descriptor.

[0074] In this manner, the UE 120 can function as a UE-to-network relay connecting the UE 120 to the wireless communication system 100, relaying traffic to / from the wireless communication system 100 on behalf of a remote UE 510 that is connected to the UE 120 but does not have access to the wireless communication system 100. In another embodiment, the UE 120 performs tethering for the remote UE 510.

[0075] In some embodiments, as will be described in more detail below, the traffic descriptor includes connection capability information indicating the capabilities of the connection to be used. The connection capability information may include a value representing information indicating use for D2D communication (e.g., "ProSe", tethering, etc.). Thus, the value indicates ProSe (or tethering) as the capability of the connection to be used. In other embodiments, the traffic descriptor includes tethering capability information representing information indicating use for D2D communication. The tethering capability information includes one or more values ​​each indicating a tethering method to be used for D2D communication (e.g., ProSe, Bluetooth™, etc.).

[0076] In some embodiments, the UE route selection policy includes one or more route selection descriptors associated with a traffic descriptor that includes information indicating use for relaying D2D communications. The route selection descriptor defines parameters for setting up a connection that the UE uses to relay D2D communications. Example parameters include S-NSSAI, DNN, SSC mode, PDU session type, path selection rules between direct and indirect proximity-based service communications over a PC5 connection, security certificates, and parameters for the ProSe PC5 connection.

[0077] With regard to UE route selection policy information, reference is made to TR 23.503, which is incorporated herein by reference in its entirety. Section 6.6.2 of TS 23.503 defines UE route selection policy information. This UE route selection policy information is a data element maintained by a PCF in a wireless communication network (e.g., a 5G system network) and delivered to a UE to guide the UE's decisions regarding, among other things, the parameters of the PDU session the UE requests from the network. When necessary, i.e., when a new UE first registers, when the UE roams to another PLMN, or when the policy for a particular UE is changed to specify only a portion of the possibilities, the PCF updates the UE with the latest applicable policy for the current UE location.

[0078] The UE route selection policy allows the PCF to configure a preferred route selection policy to apply based on certain traffic descriptors, as exemplified in Table 6.6.2.1-2 of TS 23.503, including parameters such as operating system and application descriptors, target addresses, target DNNs, and IP and non-IP descriptors that identify connection capabilities, among others.

[0079] When establishing a connection via 3GPP or non-3GPP, the UE matches the intended connection request with the traffic descriptor and identifies a top-priority UE route selection policy rule if the traffic descriptor matches the intended communication parameters. Once a valid top-priority UE route selection policy rule is identified, the UE uses the protocol parameters in the associated list of the route selection descriptor to establish the desired connection. Route selection descriptor parameters are exemplified in Table 6.6.2.1-3 of TS 23.503 and include the SSC mode, the network slice identified by the S-NSSAI, the PDU session type, the non-seamless offload indication, and the access type preference between 3GPP and non-3GPP.

[0080] For example, the UE route selection policy defined in TS23.503, section 6.6.2 may be extended as described below. The UE route selection policy may be extended to define specific policies when the UE acts as a UE-network relay or when the UE performs tethering. As described above, the UE route selection policy may include a traffic descriptor to be used by the UE for D2D communication, and the traffic descriptor may be extended to include information indicating use for D2D communication.

[0081] In some examples, the traffic descriptor portion (also referred to as a traffic descriptor) may be extended to identify a traffic descriptor that the UE should use for the ProSe connection, for example, but not limited to, when acting as a UE-to-network relay or supporting other forms of traffic tethering (such as when the UE relays traffic on behalf of another device, such as a PC connected to a WiFi / WLAN AP (access point) hosted by the UE). The traffic descriptor portion is applied by the UE when determining which traffic descriptor to use for determining route selection descriptor parameters to apply for the ProSe connection.

[0082] In some examples, the route selection descriptor part (also called the route selection descriptor) may be extended to include additional parameters required for a ProSe connection. The route selection descriptor part serves as an extension of the route selection descriptor when the list of route selection descriptors described in TS23.503 does not cover all the required ProSe communication parameters (such as authentication information required to set up a ProSe UE-network connection over a PC5 interface).

[0083] An example of the traffic descriptor part is shown in Table 1. As shown in Table 1, the connection capability descriptor can have a new value indicating use for D2D communication. By way of a non-limiting example, "ProSe" can be used as the new value (see Note 4 in Table 1).

[0084] [Table 1] TIFF0007757305000002.tif83137

[0085] Another example of a traffic descriptor portion is shown in Table 2. As shown in Table 2, the UE route selection policy rules may be extended with a new traffic descriptor (specified tethering capability) that can be used for any type of tethering connection. The new traffic descriptor may be matched by the UE with information related to the intended tethering method, including but not limited to ProSe and Bluetooth™.

[0086] [Table 2] TIFF0007757305000004.tif119145

[0087] The traffic descriptor used by the UE for D2D communication can be coded in two alternative ways, as shown in Table 1 or Table 2. Regardless of which way the UE codes the traffic descriptor used for D2D communication, the UE also evaluates this new information when identifying a matching rule. The associated list of route selection description parameters includes parameters for ProSe or tethering connection establishment (e.g., route selection rules between direct and indirect ProSe communication via S-NSSAI, DNN, PC5, etc.).

[0088] An example of a route selection descriptor portion is shown in Table 3. As shown in Table 3, the list of route selection descriptor portions may be extended to include tethering parameters that indicate tethering-specific route selection description parameters, for example, via ProSePC5. The route selection description parameters may include security certificates, path selection preferences, etc. Once the UE identifies the list of route selection descriptions associated with the applicable traffic descriptor, it sets up the connection using the parameters in that list of route selection descriptions, and the UE also uses ProSe-related parameters such as DNN and S-NSSAI used for ProSe (which may be different from those used for the same application via a direct 3GPP or non-3GPP connection), and tethering parameters specific to the ProSe (and other) tethering case.

[0089] [Table 3] TIFF0007757305000006.tif171150

[0090] The subject matter described herein may be embodied in systems, apparatus, methods, and / or articles, depending on the desired configuration. For example, the user equipment (or one or more components therein) and / or processes described herein may be implemented using one or more of a processor executing program code, an application-specific integrated circuit (ASIC), a digital signal processor (DSP), an embedded processor, a field-programmable gate array (FPGA), and / or combinations thereof. These various implementations may include implementations in one or more computer programs, which are executable and / or interpretable by a programmable system including at least one programmable processor, which may be special-purpose or general-purpose and may be connected to receive data and instructions from and transmit data and instructions to a storage system, at least one input device, and at least one output device. These computer programs (also known as programs, software, software applications, applications, components, program code, or code) include machine instructions for the programmable processor and may be implemented in a high-level procedural language and / or an object-oriented programming language, and / or in an assembly / machine language. As used herein, the term "computer-readable medium" refers to any computer program product, machine-readable medium, computer-readable storage medium, apparatus, and / or device (e.g., magnetic disk, optical disk, memory, programmable logic device (PLD)) used to provide machine instructions and / or data to a programmable processor, including the machine-readable medium for receiving the machine instructions. Similarly, systems that can include a processor and memory connected to the processor are also described herein. The memory can contain one or more programs that cause the processor to perform one or more of the operations described herein.

[0091] While several variations have been described in detail above, other modifications or additions are possible. In particular, further features and / or variations may be provided in addition to those described herein. Furthermore, the above implementations may be directed to various combinations and subcombinations of the disclosed features and / or combinations and subcombinations of certain additional features disclosed above. Other embodiments may be within the scope of the following claims.

[0092] Where appropriate, various functions described herein may be performed in different orders and / or concurrently with one another. Furthermore, where appropriate, one or more of the aforementioned functions may be optional or combined. While various aspects of some embodiments are set forth in independent claims, other aspects of some embodiments include other combinations of features of the described embodiments and / or dependent claims with features of the independent claims, as well as combinations explicitly set forth in the claims. It should also be noted that while the above describes exemplary embodiments, these descriptions should not be considered in a limiting sense. Rather, several variations and modifications can be made without departing from the scope of some embodiments, as defined in the appended claims. Other embodiments may be included within the scope of the following claims. The term "based on" includes "based at least on." The use of the phrase "such as" means "for example, such as" unless otherwise indicated.

Claims

1. A network node of a wireless communication system supporting device-to-device (D2D) communication, at least one processor; at least one memory containing computer program code; The computer program code, when executed by the at least one processor, causes the network node to A network node that causes a user equipment (UE) of the wireless communication system to provide a UE route selection policy including a traffic descriptor used by the UE to relay D2D communication, the traffic descriptor including parameters used by the UE to set up a PC5 connection or a Uu connection.

2. The network node of claim 1 , wherein the traffic descriptor includes connection capability information indicating a capability of a connection to be used, the connection capability information including a value representing the information indicating use for D2D communication.

3. The network node of claim 2 , wherein the value indicates a proximity-based service of the wireless communication system as a capability of the connection to be used.

4. 2. The network node of claim 1, wherein the traffic descriptor includes tethering capability information representing the information indicating use for D2D communication, the tethering capability information including one or more values ​​each indicating a tethering method to use for D2D communication.

5. The network node of claim 4 , wherein the one or more values ​​include a value indicating proximity-based services of the wireless communication system as the tethering method and a value indicating Bluetooth as the tethering method.

6. 6. The network node according to claim 1, wherein the UE route selection policy further comprises one or more route selection descriptors associated with the traffic descriptor containing information indicating use for relaying D2D communication, each route selection descriptor defining parameters for setting up a connection to be used by the UE for relaying D2D communication.

7. 7. The network node of claim 6, wherein the parameters include one or more of a single network slice selection assistance information (S-NSSAI), a data network name (DNN), a route selection rule between direct and indirect proximity-based service communications over a PC5 connection, a security certificate, and parameters for the PC5 connection of proximity-based services of the wireless communication system.

8. 8. The network node of claim 1, wherein the computer program code, when executed by the at least one processor, causes the network node to provide the UE route selection policy in response to determining one of: the UE registering with the wireless communication system; the UE roaming to another public land mobile network (PLMN); the UE route selection policy of the UE has changed; the UE requesting that the UE route selection policy be provided; and a time period having elapsed.

9. 9. The network node according to claim 1, wherein the UE acts as a UE-to-network relay that connects the UE to the wireless communication system and relays traffic to / from the wireless communication system on behalf of a remote UE, or the UE performs tethering for the remote UE, which is connected to the UE but cannot access the wireless communication system.

10. The network node according to any one of claims 1 to 8, wherein the wireless communication system is a 5G system and the D2D communication is a proximity-based service.

11. A user equipment (UE) of a wireless communication system supporting device-to-device (D2D) communication, comprising: at least one processor; at least one memory containing computer program code; The computer program code, when executed by the at least one processor, causes the UE to perform at least: a user equipment configured to receive from a network node of the wireless communication system or to store in the at least one memory a UE route selection policy including a traffic descriptor used by the UE to relay D2D communication, the traffic descriptor including parameters used by the UE to set up a PC5 connection or a Uu connection.

12. The UE of claim 11 , wherein the traffic descriptor includes connection capability information indicating a capability of a connection to be used, and the connection capability information includes a value representing the information indicating use for D2D communication.

13. The UE of claim 12 , wherein the value indicates a proximity-based service of the wireless communication system as a capability of the connection to be used.

14. 12. The UE of claim 11, wherein the traffic descriptor includes tethering capability information representing the information indicating use for D2D communication, the tethering capability information including one or more values ​​each indicating a tethering method to use for D2D communication.

15. The UE of claim 14 , wherein the one or more values ​​include a value indicating a proximity-based service of the wireless communication system as the tethering method and a value indicating Bluetooth as the tethering method.

16. 16. The UE according to claim 11, wherein the UE route selection policy further comprises one or more route selection descriptors associated with the traffic descriptor containing information indicating use for relaying D2D communication, each route selection descriptor defining parameters for setting up a connection used by the UE to relay D2D communication.

17. 17. The UE of claim 16, wherein the parameters include one or more of a single network slice selection assistance information (S-NSSAI), a data network name (DNN), a route selection rule between direct proximity-based service communication and indirect proximity-based service communication via a PC5 connection, a security certificate, and parameters for the PC5 connection of the proximity-based service of the wireless communication system.

18. 18. The UE of claim 11, wherein the computer program code, when executed by the at least one processor, further causes the UE to match a D2D or tethering request with the information indicating a use for D2D communication to determine whether to select the UE route selection policy.

19. The UE of any one of claims 11 to 18, wherein the UE acts as a UE-to-network relay that connects the UE to the wireless communication system and relays traffic to / from the wireless communication system on behalf of a remote UE, or the UE performs tethering of the remote UE, which is connected to the UE but cannot access the wireless communication system.

20. The UE according to any one of claims 11 to 18, wherein the wireless communication system is a 5G system and the D2D communication is a proximity-based service.

21. 1. A method in a network node of a wireless communication system supporting device-to-device (D2D) communication, comprising:

1. A method comprising: providing, to a user equipment (UE) of the wireless communication system, a UE route selection policy comprising a traffic descriptor for use by the UE to relay D2D communication, the traffic descriptor comprising parameters for use by the UE to set up a PC5 connection or a Uu connection.

22. 1. A method in a user equipment (UE) of a wireless communication system supporting device-to-device (D2D) communication, comprising: receiving from a network node of the wireless communication system or storing in at least one memory of the UE a UE route selection policy including a traffic descriptor used by the UE to relay D2D communication, the traffic descriptor including parameters used by the UE to set up a PC5 connection or a Uu connection.

23. 22. A computer program comprising program instructions stored on a computer readable medium for performing the method of claim 21 when the computer program is run on a computer.

24. A computer program comprising program instructions stored on a computer-readable medium for performing the method of claim 22 when executed on a computer.

Images