Apparatus and method for eas discovery and ue-to-ue relay operation in 5gs

Abstract

The present disclosure provides apparatuses and methods for EAS discovery and UE-to-UE relay operation in 5GS. An apparatus for configuring UE-to-UE relay operation in 5GS includes interface circuitry; and processing circuitry coupled with the interface circuitry, the processing circuitry to: process a registration request message of a UE received via the interface circuitry, the registration request message including information indicating 5G ProSe UE-to-UE relay capability and / or 5G ProSe UE-to-UE relay access capability of the UE; select a PCF supporting 5G ProSe information provisioning for the UE; and establish a UE policy association with the PCF for 5G ProSe UE-to-UE relay information provisioning delivery and / or 5G ProSe UE-to-UE relay access information provisioning delivery. Other embodiments are also disclosed and claimed.

Description

[0001] Priority Statement

[0002] This application claims priority to International Application No. PCT / CN2020 / 070411, filed on January 6, 2020, and International Application No. PCT / CN2020 / 070413, filed on January 6, 2020, the entire contents of which are incorporated herein by reference. Technical Field

[0003] Embodiments of this disclosure generally relate to the field of wireless communication, and more specifically, to apparatus and methods for edge application server (EAS) discovery and user equipment-to-user equipment (UE-to-UE, UE-to-UE) relay operations in fifth-generation (5G) systems (i.e., 5GS). Background Technology

[0004] For 5GS, various enablers to support edge computing have been defined in the 3GPP technical specifications, such as EAS discovery. 5GS can also support UE-to-UE relay services.

[0005] More questions are being raised and are yet to be addressed regarding edge computing and UE-to-UE relay operations. Summary of the Invention

[0006] One aspect of this disclosure provides an apparatus for configuring UE-to-UE relay operation in a fifth-generation system (5GS). The apparatus includes: an interface circuit; and a processing circuit coupled to the interface circuit, the processing circuit being configured to: process a registration request message received via the interface circuit from a user equipment (UE), the registration request message including information indicating the UE's fifth-generation (5G) proximity-based service (ProSe) UE-to-UE relay capability and / or 5G ProSe UE-to-UE relay access capability; select a policy control function (PCF) supporting 5G ProSe information configuration for the UE; and establish a UE policy association with the PCF for 5G ProSe UE-to-UE relay information configuration delivery and / or 5G ProSe UE-to-UE relay access information configuration delivery.

[0007] Another aspect of this disclosure provides an apparatus for configuring UE-to-UE relay operations in a fifth-generation system (5GS). The apparatus includes: an interface circuit; and a processing circuit coupled to the interface circuit, the processing circuit being configured to: process messages received via the interface circuit from an Access and Mobility Management Function (AMF), the messages including information indicating a user equipment (UE)'s fifth-generation (5G) proximity-based service (ProSe) UE-to-UE relay capability and / or 5G ProSe UE-to-UE relay access capability; and determine 5G ProSe UE-to-UE relay information and / or 5G ProSe UE-to-UE relay access information for the UE based on the UE's 5G ProSe UE-to-UE relay capability and / or 5G ProSe UE-to-UE relay access capability, respectively.

[0008] Another aspect of this disclosure provides a computer-readable storage medium having instructions stored thereon. When executed by processing circuitry of a user equipment (UE) in a fifth-generation system (5GS), these instructions cause the UE to: encode a registration request message including information indicating the UE's fifth-generation (5G) proximity-based service (ProSe) UE-to-UE relay capability and / or 5G ProSe UE-to-UE relay access capability; and send the registration request message to the Access and Mobility Management Function (AMF).

[0009] Another aspect of this disclosure provides an apparatus for edge application server (EAS) discovery based on a directory name system (DNS) checker. The apparatus includes: interface circuitry; and processing circuitry coupled to the interface circuitry, the processing circuitry being configured to: modify the uplink classifier / branch point (UL) from the user plane function (UPF) in a manner that... The CL / BP receives a DNS request from a User Equipment (UE): modifies the destination Internet Protocol (IP) address of the DNS request to the IP address of the local DNS (L-DNS) and stores the destination IP address of the DNS request for subsequent processing; and modifies the source IP address of the DNS request to the IP address of the DNS checker and stores the source IP address of the DNS request for subsequent processing. The destination IP address of the DNS request corresponds to the default DNS server, and the source IP address of the DNS request corresponds to the UE's IP address. The modified DNS request is forwarded to the L-DNS via the interface circuit. Based on the DNS response from the L-DNS, it is determined whether the fully qualified domain name (FQDN) of the EAS specified in the DNS request has been resolved. When the FQDN is determined to be resolved to the IP address of the EAS: the source IP address and destination IP address of the DNS response are replaced with the stored destination IP address and source IP address of the DNS request, respectively, and the DNS response is forwarded to the UPF's UL CL / BP. And when the FQDN is determined to be unresolved, the DNS request initially received from the UPF's UL CL / BP is forwarded back to the UPF's UL CL / BP. CL / BP.

[0010] Another aspect of this disclosure provides an apparatus for a fifth-generation system (5GS). The apparatus includes: an interface circuit; and processing circuitry coupled to the interface circuitry, the processing circuitry being configured to: forward a Directory Name System (DNS) request from a User Equipment (UE) to a DNS checker via the interface circuitry; and process a DNS response or DNS request received from the DNS checker via the interface circuitry.

[0011] Another aspect of this disclosure provides an apparatus for a fifth-generation system (5GS). The apparatus includes: an interface circuit; and processing circuitry coupled to the interface circuitry, the processing circuitry being configured to: process a DNS request received from a directory name system (DNS) checker via the interface circuitry from a user equipment (UE); determine whether a local DNS (L-DNS) can resolve the fully qualified domain name (FQDN) of an edge application server (EAS) specified in the DNS request; if the L-DNS can resolve the FQDN of the EAS, respond to the DNS checker with a DNS response including the expected Internet Protocol (IP) address of the local EAS (L-EAS); if the L-DNS cannot resolve the EAS... If the FQDN of EAS is not connected to the Cloud DNS (C-DNS), then the L-DNS is determined to be connected to the C-DNS: When the L-DNS is not connected to the C-DNS, it responds to the DNS checker with the following DNS response: the DNS response does not include the IP address of EAS or the DNS response has an indication that the L-DNS cannot resolve the FQDN of EAS; or when the L-DNS is connected to the C-DNS, it communicates with the C-DNS to recursively resolve the FQDN of EAS, receives the IP address of the cloud EAS from the C-DNS, and responds to the DNS checker with the following DNS response: the DNS response includes the IP address of the cloud EAS. Attached Figure Description

[0012] In the accompanying drawings, embodiments of the present disclosure will be illustrated by way of example rather than limitation, wherein like reference numerals refer to similar elements.

[0013] Figure 1 An example architecture of a system according to some embodiments of this disclosure is shown.

[0014] Figure 2 An example architecture of a system including a 5G core (5GC) according to some embodiments of this disclosure is shown.

[0015] Figure 3 An example architecture of 5GS including a Directory Name System (DNS) Inspector for EAS discovery is shown according to some embodiments of this disclosure.

[0016] Figure 4 An example EAS discovery process using a DNS checker is shown according to some embodiments of this disclosure.

[0017] Figure 5 This is a flowchart illustrating the process for EAS discovery based on a DNS checker in 5GS according to some embodiments of the present disclosure.

[0018] Figure 6A flowchart is shown for another process for EAS discovery using a DNS checker in 5GS, according to some embodiments of this disclosure.

[0019] Figure 7 The flowchart of another process for EAS discovery based on a DNS checker in 5GS is shown according to some embodiments of this disclosure.

[0020] Figure 8 A simplified registration process for a UE according to some embodiments of this disclosure is illustrated.

[0021] Figure 9 Another simplified registration process for a UE according to some embodiments of this disclosure is shown.

[0022] Figure 10 A flowchart illustrating the configuration process for UE-to-UE relay operation in 5GS according to some embodiments of the present disclosure is shown.

[0023] Figure 11 A flowchart illustrating the configuration process for UE-to-UE relay operation in 5GS according to some embodiments of the present disclosure is shown.

[0024] Figure 12 A flowchart illustrating the configuration process for UE-to-UE relay operation in 5GS according to some embodiments of the present disclosure is shown.

[0025] Figure 13 A flowchart illustrating the configuration process for UE-to-UE relay operation in 5GS according to some embodiments of the present disclosure is shown.

[0026] Figure 14 A flowchart illustrating the configuration process for UE-to-UE relay operation in 5GS according to some embodiments of the present disclosure is shown.

[0027] Figure 15 Example components of a device according to some embodiments of this disclosure are shown.

[0028] Figure 16 Examples of infrastructure devices according to various embodiments are shown.

[0029] Figure 17 This is a block diagram illustrating a component capable of reading instructions from a machine-readable or computer-readable medium and performing any one or more methods discussed herein, according to some example embodiments. Detailed Implementation

[0030] Various aspects of the illustrative embodiments will be described using terminology commonly employed by those skilled in the art to convey the essence of this disclosure to others skilled in the art. However, it will be readily understood by those skilled in the art that many alternative embodiments can be practiced using portions of the described aspects. Specific figures, materials, and configurations are set forth for illustrative purposes to provide a thorough understanding of the illustrative embodiments. However, it will be readily understood by those skilled in the art that alternative embodiments can be practiced without these specific details. In other instances, well-known features may be omitted or simplified to avoid obscuring the illustrative embodiments.

[0031] Furthermore, the various operations will be described as multiple discrete operations in a manner most conducive to understanding the illustrative embodiments; however, the order of description should not be construed as implying that these operations must depend on the order. In particular, these operations do not need to be performed in the order presented.

[0032] The phrases “in an embodiment,” “in one embodiment,” and “in some embodiments” are used repeatedly throughout this document. These phrases do not typically refer to the same embodiment; however, they may refer to the same embodiment. Unless the context otherwise specifies, the terms “comprising,” “having,” and “including” are synonyms. The phrases “A or B” and “A / B” mean “(A), (B), or (A and B).”

[0033] Figure 1 An example architecture of a system 100 according to some embodiments of this disclosure is shown. The following description is provided for an example system 100 operating in combination with the Long Term Evolution (LTE) system standard provided by the 3GPP Technical Specification (TS) and the 5G or New Radio (NR) system standard. However, the example embodiments are not limited in this respect, and the described embodiments can be applied to other networks that benefit from the principles described herein, such as future 3GPP systems (e.g., sixth generation (6G)) systems, IEEE 802.16 protocols (e.g., Wireless Metropolitan Area Network (MAN), Global Microwave Access Interoperability (WiMAX), etc.).

[0034] like Figure 1As shown, system 100 may include UE 101a and UE 101b (collectively referred to as "(one or more) UE 101"). As used herein, the term "user equipment" or "UE" may refer to a device with radio communication capabilities and may describe a remote user of network resources in a communication network. The term "user equipment" or "UE" may be considered synonymous and may refer to a client, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Furthermore, the term "user equipment" or "UE" may include any type of wireless / wired device or any computing device including a wireless communication interface. In this example, UE 101 is shown as a smartphone (e.g., a handheld touchscreen mobile computing device that can connect to one or more cellular networks), but may also include any mobile or non-mobile computing device, such as consumer electronics, cellular phones, smartphones, feature phones, tablets, wearable computing devices, personal digital assistants (PDAs), pagers, wireless handheld devices, desktop computers, laptops, in-vehicle infotainment systems (IVI), in-vehicle entertainment (ICE) devices, instrument clusters (ICs), head-up displays (HUDs), on-board diagnostics (OBD) devices, dashboard mobile devices (DMEs), mobile data terminals (MDTs), electronic engine management systems (EEMS), electronic / engine control units (ECUs), electronic / engine control modules (ECMs), embedded systems, microcontrollers, control modules, engine management systems (EMS), networked or “smart” devices, machine-type communication (MTC) devices, machine-to-machine (M2M) devices, Internet of Things (IoT) devices, and / or the like.

[0035] In some embodiments, any of UEs 101 may include an IoT UE, which may include a network access layer designed for low-power IoT applications utilizing short-lived UE connections. The IoT UE may utilize technologies such as M2M or MTC to exchange data with an MTC server or device via a PLMN, Proximity-Based Service (ProSe) or Device-to-Device (D2D) communication, sensor networks, or IoT networks. M2M or MTC data exchange may be machine-initiated. The IoT network describes interconnected IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure) with short-lived connections. The IoT UE may execute background applications (e.g., keeping messages active, state updates, etc.) to facilitate connectivity within the IoT network.

[0036] UE 101 can be configured to connect to (e.g., communicatively coupled to) RAN 110. In embodiments, RAN 110 can be a next-generation (NG) RAN or a 5G RAN, an evolved Universal Mobile Telecommunications System (UMTS) terrestrial radio access network (E-UTRAN), or a legacy RAN, such as UTRAN (UMTS terrestrial radio access network) or GERAN (GSM (Global System for Mobile Communications or Groupe Spécial Mobile) EDGE (GSM evolution) radio access network). As used herein, the term "NGRAN," etc., can refer to RAN 110 operating in NR or 5G system 100, and the term "E-UTRAN," etc., can refer to RAN 110 operating in LTE or 4G system 100. UE 101 utilizes connections (or channels) 103 and 104, respectively, each connection including a physical communication interface or layer (discussed in further detail below). As used herein, the term "channel" can refer to any tangible or intangible transmission medium used to transmit data or data streams. The term "channel" may be synonymous and / or equivalent with "communication channel," "data communication channel," "transmission channel," "data transmission channel," "access channel," "data access channel," "link," "data link," "carrier," "radio frequency carrier," and / or any other similar term that indicates a path or medium through which data is transmitted. Additionally, the term "link" may refer to a connection between two devices for the purpose of sending and receiving information via radio access technology (RAT).

[0037] In this example, connections 103 and 104 are shown as air interfaces for communication coupling and can be consistent with cellular communication protocols such as the Global System for Mobile Communications (GSM) protocol, Code Division Multiple Access (CDMA) network protocol, Push-to-Talk (PTT) protocol, Cellular PTT (POC) protocol, Universal Mobile Telecommunications System (UMTS) protocol, 3GPP Long Term Evolution (LTE) protocol, 5G protocol, New Radio (NR) protocol, and / or any other communication protocols discussed herein. In this embodiment, UE 101 can directly exchange communication data via ProSe interface 105. ProSe interface 105 can alternatively be referred to as sidelink (SL) interface 105 and may include one or more logical channels, including but not limited to the Physical Sidelink Control Channel (PSCCH), Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Discovery Channel (PSDCH), and Physical Sidelink Broadcast Channel (PSBCH).

[0038] UE 101b is shown configured to access access point (AP) 106 (also referred to as "WLAN node 106", "WLAN 106", "WLAN terminal 106", or "WT 106", etc.) via connection 107. Connection 107 may include a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, where AP 106 will include a Wi-Fi router. In this example, AP 106 is shown connected to the Internet but not to the core network of the wireless system (described in further detail below). In various embodiments, UE 101b, RAN 110, and AP 106 may be configured to utilize LTE-WLAN aggregation (LWA) operation and / or WLAN LTE / WLAN radio-grade integration (LWIP) operation with IPsec tunneling. LWA operation may involve UE 101b in RRC_CONNECTED being configured by RAN node 111 to utilize LTE and WLAN radio resources. LWIP operation may involve UE 101b using WLAN radio resources (e.g., connection 107) via an Internet Protocol Security (IPsec) protocol tunnel to authenticate and encrypt packets (e.g., Internet Protocol (IP) packets) sent through connection 107. The IPsec tunnel may include encapsulating the entire original IP packet and adding a new packet header, thereby protecting the original header of the IP packet.

[0039] RAN 110 may include one or more RAN nodes 111a and 111b (collectively referred to as "(one or more) RAN nodes 111") that enable connections to 103 and 104. As used herein, the terms "access node (AN)," "access point," "RAN node," etc., may describe equipment that provides radio baseband functionality for data and / or voice connections between the network and one or more users. These access nodes may be referred to as base stations (BS), next-generation node B (gNB), RAN nodes, evolved Node B (eNB), Node B, roadside unit (RSU), transmit receiver point (TRxP or TRP), etc., and may include ground stations (e.g., ground access points) or satellite stations that provide coverage within a geographic area (e.g., cell). As used herein, the terms "NGRAN node," etc., may refer to RAN node 111 (e.g., gNB) operating in NR or 5G system 100, and the terms "E-UTRAN node," etc., may refer to RAN node 111 (e.g., eNB) operating in LTE or 4G system 100. According to various embodiments, RAN node 111 may be implemented as one or more dedicated physical devices such as a macro cell base station and / or a low-power (LP) base station for providing smaller coverage areas, smaller user capacity, or higher bandwidth compared to a macro cell.

[0040] In some embodiments, all or part of RAN node 111 can be implemented as one or more software entities running on a server computer as part of a virtual network, which may be referred to as Cloud Radio Access Network (CRAN) and / or Virtual Baseband Unit Pool (vBBUP). In these embodiments, CRAN or vBBUP can implement RAN function partitioning, such as: Packet Data Convergence Protocol (PDCP) partitioning, where the RRC and PDCP layers are operated by CRAN / vBBUP, while other Layer 2 (L2) protocol entities are operated by individual RAN node 111; MAC / PHY partitioning, where the RRC, PDCP, RLC, and MAC layers are operated by CRAN / vBBUP, and the PHY layer is operated by individual RAN node 111; or "lower PHY" partitioning, where the upper part of the RRC, PDCP, RLC, MAC, and PHY layers is operated by CRAN / vBBUP, and the lower part of the PHY layer is operated by individual RAN node 111. This virtualization framework allows the processor cores of RAN node 111 to be freed up to execute other virtualized applications. In some implementations, individual RAN node 111 may represent a virtualized application running via an individual F1 interface (…). Figure 1 (Not shown) Individual gNB-DUs connected to the gNB-CU. In these implementations, the gNB-DU may include one or more remote radio heads or radio front-end modules (RFEMs), and the gNB-CU may be operated by a server (not shown) located in RAN110 or by a server pool in a manner similar to CRAN / vBBUP. Additionally or alternatively, one or more RAN nodes 111 may be next-generation eNBs (ng-eNBs), which are RAN nodes that provide E-UTRA user plane and control plane protocol termination to UE 101, and are connected to 5GC via the ng interface.

[0041] In a V2X scenario, one or more RAN nodes 111 can be or act as RSUs. The terms "roadside unit" or "RSU" can refer to any transport infrastructure entity used for V2X communication. An RSU can be implemented in or by a suitable RAN node or a stationary (or relatively static) UE, where an RSU implemented in or by a UE can be referred to as a "UE-type RSU," an RSU implemented in or by an eNB can be referred to as an "eNB-type RSU," an RSU implemented in or by a gNB can be referred to as a "gNB-type RSU," and so on. In one example, an RSU is a computing device coupled to radio frequency circuitry located on the roadside, providing connectivity support for a passing vehicle UE 101 (vUE 101). An RSU may also include internal data storage circuitry for storing intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling ongoing vehicle and pedestrian traffic. The RSU can operate on the 5.9 GHz Direct Short Range Communication (DSRC) band to provide very low-latency communication required for high-speed events, such as collision avoidance and traffic warnings. Alternatively or additionally, the RSU can operate on the cellular V2X band to provide the aforementioned low-latency communication as well as other cellular communication services. Alternatively or additionally, the RSU can operate as a WiFi hotspot (2.4 GHz band) and / or provide connectivity to one or more cellular networks to provide uplink and downlink communication. One or more computing devices and some or all of the RF circuitry of the RSU can be encapsulated in a weatherproof enclosure suitable for outdoor installation and may include a network interface controller to provide wired (e.g., Ethernet) connectivity to traffic signal controllers and / or backhaul networks.

[0042] Any RAN node 111 can terminate the air interface protocol and can be the first point of contact for UE 101. In some embodiments, any RAN node 111 can fulfill various logical functions of RAN 110, including but not limited to radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

[0043] In an embodiment, UE 101 may be configured to communicate with each other or with any RAN node 111 via a multi-carrier communication channel using various communication technologies, such as, but not limited to, Orthogonal Frequency Division Multiple Access (OFDM) communication technology (e.g., for downlink communication) or Single Carrier Frequency Division Multiple Access (SC-FDMA) communication technology (e.g., for uplink and ProSe or sidelink communication), although the scope of the embodiment is not limited to this aspect. The OFDM signal may include multiple orthogonal subcarriers.

[0044] In some embodiments, the downlink resource grid can be used for downlink transmissions from any RAN node 111 to UE 101, while uplink transmissions can use a similar technique. The grid can be a time-frequency grid, referred to as a resource grid or time-frequency resource grid, which is the physical resource in the downlink for each time slot. This time-frequency plane representation is common practice in OFDM systems, making radio resource allocation intuitive. Each column and row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to one time slot in a radio frame. The smallest time-frequency unit in the resource grid is represented as a resource element. Each resource grid comprises multiple resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block comprises a set of resource elements; in the frequency domain, this can represent the minimum amount of resources that can currently be allocated. Several different physical downlink channels exist that are transmitted using such resource blocks.

[0045] According to various embodiments, UE 101 and RAN node 111 transmit (e.g., send and receive) data through licensed media (also referred to as “licensed spectrum” and / or “licensed band”) and unlicensed shared media (also referred to as “unlicensed spectrum” and / or “unlicensed band”). Licensed spectrum may include channels operating in a frequency range of approximately 400 MHz to approximately 3.8 GHz, while unlicensed spectrum may include a 5 GHz band.

[0046] To operate in unlicensed spectrum, UE 101 and RAN node 111 can use Licensed Assisted Access (LAA), Enhanced LAA (eLAA), and / or other eLAA (feLAA) mechanisms. In these implementations, UE 101 and RAN node 111 can perform one or more known media sensing and / or carrier sensing operations to determine whether one or more channels in the unlicensed spectrum are unavailable or otherwise occupied before transmitting in the unlicensed spectrum. Media / carrier sensing operations can be performed according to a Listen-After-Talk (LBT) protocol.

[0047] LBT is a mechanism in which a device (e.g., UE 101, RAN nodes 111, 112, etc.) senses the medium (e.g., a channel or carrier frequency) and transmits data when the medium is sensed to be idle (or when a specific channel in the medium is sensed to be unoccupied). The medium sensing operation may include a Free Channel Assessment (CCA), which utilizes at least Energy Detection (ED) to determine the presence of other signals on the channel to determine whether the channel is occupied or idle. This LBT mechanism allows cellular / LAA networks to coexist with incumbent systems in unlicensed spectrum and with other LAA networks. ED may include sensing radio frequency (RF) energy in the intended transmission band for a period of time and comparing the sensed RF energy with a predetermined or configured threshold.

[0048] Typically, current systems in the 5GHz band are WLANs based on IEEE 802.11 technology. WLANs employ a contention-based channel access mechanism called Carrier Sense Multiple Access with Collision Avoidance (CSMA / CA). Here, when a WLAN node (e.g., a mobile station (MS) such as UE 101 or AP 106) intends to transmit, the WLAN node can first perform CCA before transmitting. Additionally, a backoff mechanism is used to avoid collisions when more than one WLAN node senses the channel as idle and transmits simultaneously. The backoff mechanism can be a counter randomly drawn within the contention window size (CWS), which increases exponentially when a collision occurs and is reset to a minimum upon successful transmission. The LBT mechanism designed for LAA is somewhat similar to CSMA / CA for WLANs. In some implementations, the LBT process for DL ​​or UL transmission bursts that respectively include PDSCH or PUSCH transmissions can have an LAA contention window of variable length between X and Y extended CCA (ECCA) slots, where X and Y are the minimum and maximum values ​​of the CWS for LAA. In one example, the minimum CWS for LAA transmission can be 9 microseconds (μs); however, the size of the CWS and the maximum channel occupancy time (MCOT) (e.g., transmission burst) can be based on government regulatory requirements.

[0049] The LAA mechanism is based on the carrier aggregation (CA) technology of LTE-Advanced systems. In CA, each aggregated carrier is called a component carrier (CC). A CC can have a bandwidth of 1.4, 3, 5, 10, 15, or 20 MHz, and up to five CCs can be aggregated, thus the maximum aggregated bandwidth is 100 MHz. In Frequency Division Duplex (FDD) systems, the number of aggregated carriers can differ for DL ​​and UL, where the number of UL CCs is equal to or less than the number of DL component carriers. In some cases, an individual CC can have a different bandwidth than the other CCs. In Time Division Duplex (TDD) systems, the number of CCs and the bandwidth of each CC are typically the same for DL ​​and UL.

[0050] CA also includes separate serving cells to provide separate CCs. The coverage of serving cells may differ, for example, because CCs on different frequency bands will experience different path losses. The primary serving cell, or primary cell (PCell), can provide the primary CC (PCC) for both UL and DL, and can handle Radio Resource Control (RRC) and Non-Access Stratum (NAS) related activities. Other serving cells are called secondary cells (SCells), and each SCell can provide a separate secondary CC (SCC) for both UL and DL. SCCs can be added and removed as needed, and changing the PCC may require UE 101 to undergo a handover. In LAA, eLAA, and feLAA, some or all SCells can operate in unlicensed spectrum (referred to as "LAA SCells"), and LAA SCells are assisted by PCells operating in licensed spectrum. When a UE is configured with more than one LAA SCell, the UE can receive a UL grant on the configured LAASCell, which indicates the start position of different Physical Uplink Shared Channels (PUSCHs) within the same subframe.

[0051] The Physical Downlink Shared Channel (PDSCH) carries user data and higher-layer signaling to UE 101. The Physical Downlink Control Channel (PDCCH) carries information such as the transmission format and resource allocation related to the PDSCH channel. It can also inform UE 101 of the transmission format, resource allocation, and H-ARQ (Hybrid Automatic Repeat Request) information related to the uplink shared channel. Typically, downlink scheduling (allocating control and shared channel resource blocks to UE 101b within the cell) can be performed at any RAN node 111 based on channel quality information fed back from any UE 101. Downlink resource allocation information can be transmitted on the PDCCH used (e.g., allocated to) each UE 101.

[0052] PDCCH can use Control Channel Elements (CCEs) to convey control information. Before mapping to resource elements, PDCCH complex-valued symbols are first organized into quadruplets, which are then permuted using a sub-block interleaver for rate matching. Each PDCCH can be transmitted using one or more of these CCEs, where each CCE can correspond to nine groups of four physical resource elements called Resource Element Groups (REGs). Four Quadrature Phase Shift Keying (QPSK) symbols can be mapped to each REG. The number of CCEs used to transmit PDCCH depends on the size of the Downlink Control Information (DCI) and channel conditions. In LTE, four or more different PDCCH formats (e.g., aggregation levels, L = 1, 2, 4, or 8) with different numbers of CCEs can be defined.

[0053] Some embodiments may use the concept of resource allocation for control channel information, which is an extension of the concepts described above. For example, some embodiments may use an Enhanced Physical Downlink Control Channel (EPDCCH) that uses PDSCH resources for control information transmission. The EPDCCH may be transmitted using one or more Enhanced Control Channel Elements (ECCEs). Similar to the above, each ECCE may correspond to nine groups of four physical resource elements, referred to as Enhanced Resource Element Groups (EREGs). In some cases, there may be an additional number of EREGs for the ECCE.

[0054] RAN nodes 111 can be configured to communicate with each other via interface 112. In embodiments where system 100 is an LTE system, interface 112 can be an X2 interface 112. The X2 interface can be defined between two or more RAN nodes 111 connected to EPC 120 (e.g., two or more eNBs, etc.) and / or two eNBs connected to EPC 120. In some implementations, the X2 interface may include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C). X2-U can provide flow control mechanisms for user data packets transmitted via the X2 interface and can be used to transmit information about user data transfers between eNBs. For example, X2-U can provide specific sequence number information for user data transmitted from the primary eNB (MeNB) to the secondary eNB (SeNB); information about successful sequential transmission of PDCP protocol data units (PDUs) from the SeNB to UE 101 for user data; information about PDCP PDUs not delivered to UE 101; information about the current minimum required buffer size at the SeNB for sending user data to the UE; and so on. X2-C can provide LTE intra-eNB access mobility functions, including context transmission from the source eNB to the destination eNB, user plane transmission control, load management functions, and inter-cell interference coordination functions.

[0055] In embodiments where system 100 is a 5G or NR system, interface 112 may be an Xn interface 112. The Xn interface is defined between two or more RAN nodes 111 (e.g., two or more gNBs, etc.) connected to 5GC 120, between a RAN node 111 (e.g., a gNB) connected to 5GC 120 and an eNB, and / or between two eNBs connected to 5GC 120. In some implementations, the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. Xn-U can provide unguaranteed delivery of user plane PDUs and supports / provides data forwarding and flow control functions. Xn-C can provide: management and error handling functions; functions for managing the Xn-C interface; and mobility support for UE 101 in connected modes (e.g., CM-CONNECTED), including functions for managing UE mobility in connected modes between one or more RAN nodes 111. Mobility support may include context delivery from the old (source) serving RAN node 111 to the new (destination) serving RAN node 111; and control of the user plane tunnel between the old (source) serving RAN node 111 and the new (destination) serving RAN node 111. The Xn-U protocol stack may include a transport network layer built on the Internet Protocol (IP) transport layer, and a GTP-U layer built on top of one or more UDP and / or IP layers for carrying user plane PDUs. The Xn-C protocol stack may include an application layer signaling protocol (referred to as the Xn Application Protocol (Xn-AP)) and a transport network layer built on SCTP. SCTP may reside above the IP layer and may provide guaranteed delivery of application layer messages. In the transport IP layer, point-to-point transmission is used to deliver signaling PDUs. In other implementations, the Xn-U protocol stack and / or the Xn-C protocol stack may be the same as or similar to one or more user plane and / or control plane protocol stacks shown and described herein.

[0056] RAN 110 is shown communicatively coupled to the core network—in this embodiment, the core network (CN) 120. CN 120 may include a plurality of network elements 122 configured to provide various data and telecommunications services to customers / subscribers (e.g., users of UE 101) connected to CN 120 via RAN 110. The term “network element” can describe a physical or virtualized device used to provide wired or wireless communication network services. The term “network element” can be considered synonymous with and / or referred to as: networked computer, network hardware, network device, router, switch, hub, bridge, radio network controller, radio access network device, gateway, server, virtualized network function (VNF), network function virtualization infrastructure (NFVI), and / or the like. Components of CN 120 may be implemented in a single physical node or separate physical nodes, including components that read and execute instructions from machine-readable or computer-readable media (e.g., non-transitory machine-readable storage media). In some embodiments, Network Functions Virtualization (NFV) can be used to virtualize any or all of the aforementioned network node functions (described in further detail below) via executable instructions stored in one or more computer-readable storage media. A logical instantiation of the CN120 may be referred to as a network slice, and a logical instantiation of a portion of the CN120 may be referred to as a network subslice. NFV architectures and infrastructures can be used to virtualize one or more network functions, or to execute them by dedicated hardware onto physical resources including a combination of industry-standard server hardware, storage hardware, or switches. In other words, an NFV system can be used to execute a virtual or reconfigurable implementation of one or more EPC components / functions.

[0057] Typically, application server 130 may be an element that provides applications that use IP bearer resources with the core network (e.g., UMTS Packet Service (PS) domain, LTE PS data service, etc.). Application server 130 may also be configured to support one or more communication services (e.g., Voice over Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for UE 101 via EPC 120.

[0058] In this embodiment, CN 120 may be a 5GC (referred to as "5GC 120", etc.), and RAN 110 may be connected to CN 120 via NG interface 113. In this embodiment, NG interface 113 may be divided into two parts: NG User Plane (NG-U) interface 114, which carries service data between RAN node 111 and User Plane Function (UPF); and S1 Control Plane (NG-C) interface 115, which is the signaling interface between RAN node 111 and AMF.

[0059] In one embodiment, CN 120 may be a 5G CN (referred to as "5GC 120", etc.), while in other embodiments, CN 120 may be an evolved packet core (EPC). When CN 120 is an EPC (referred to as "EPC 120", etc.), RAN 110 may connect to CN 120 via S1 interface 113. In one embodiment, S1 interface 13 may be divided into two parts: an S1 user plane (S1-U) interface 114, which carries service data between RAN node 111 and the serving gateway (S-GW); and an S1 mobility management entity (MME) interface 115, which is the signaling interface between RAN node 111 and the MME.

[0060] Figure 2 An example architecture of a system 200 including a 5GC 220 according to some embodiments of the present disclosure is shown.

[0061] System 200 is shown to include: UE 201, which may be the same as or similar to UE 101 previously discussed; (R)AN 210, which may be the same as or similar to RAN 110 previously discussed, and may include RAN node 111 previously discussed; and data network (DN) 203, which may be, for example, operator service, Internet access or third-party service; and 5G core network (5GC or CN) 220.

[0062] 5GC 220 may include Authentication Server Function (AUSF) 222; Access and Mobility Management Function (AMF) 221; Session Management Function (SMF) 224; Network Exposure Function (NEF) 223; Policy Control Function (PCF) 226; Network Function (NF) Repository Function (NRF) 225; Unified Data Management (UDM) 227; Application Function (AF) 228; User Plane Function (UPF) 202; and Network Slice Selection Function (NSSF) 229.

[0063] UPF 202 can act as an anchor point for mobility within and between RATs, an external PDU session interconnection point to DN 203, and a branch point supporting multihomed PDU sessions. UPF 202 can also perform packet routing and forwarding, packet inspection, enforcement of policy rules for the user plane portion, lawful packet interception (UP sets), traffic usage reporting, QoS processing on the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), uplink traffic authentication (e.g., SDF-to-QoS traffic mapping), transport level packet marking in uplink and downlink, and downlink packet buffering and downlink data notification triggering. UPF 202 may include an uplink classifier (UL CL) to support routing traffic flows to the data network. DN 203 can represent various network operator services, Internet access, or third-party services. DN 203 may include or resemble the previously discussed application server 130. UPF 202 can interact with SMF 224 via the N4 reference point between SMF 224 and UPF 202.

[0064] AUSF 222 can store data for UE 201 authentication and handle authentication-related functions. AUSF 222 facilitates a common authentication framework for various access types. AUSF 222 can communicate with AMF 221 via the N12 reference point between AMF 221 and AUSF 222; and can communicate with UDM 227 via the N13 reference point between UDM 227 and AUSF 222. Additionally, AUSF 222 can expose interfaces based on Nausf services.

[0065] AMF 221 can be responsible for registration management (e.g., for registering UE 201, etc.), connection management, reachability management, mobility management, and lawful interception of AMF-related events, as well as access authentication and authorization. AMF 221 can be the termination point of the N11 reference point between AMF 221 and SMF 224. AMF 221 can provide transmission of Session Management (SM) messages between UE 201 and SMF 224 and act as a transparent proxy for routing SM messages. AMF 221 can also be used in conjunction with the SMS Function (SMSF) between UE 201 and SMF 224. Figure 2AMF 221 provides transmission of Short Message Service (SMS) messages between (not shown). AMF 221 can act as a Security Anchor (SEA) function, which may include interaction with AUSF 222 and UE 201, receiving an intermediate key established as a result of the UE 201 authentication process. In the case of USIM-based authentication, AMF 221 can obtain security materials from AUSF 222. AMF 221 may also include a Security Context Management (SCM) function, which receives a key from the SEA for deriving a key specific to the access network. Furthermore, AMF 221 can be the termination point of the RAN CP interface, which may include or be an N2 reference point between (R)AN 211 and AMF 221; AMF 221 can be the termination point of NAS (N1) signaling and perform NAS encryption and integrity protection.

[0066] AMF 221 can also support NAS signaling with UE 201 via the N3 Interoperability Function (IWF) interface. The N3IWF can be used to provide access to untrusted entities. The N3IWF can be the termination point of the N2 interface between (R)AN 210 and AMF 221 for the control plane, and can be the termination point of the N3 reference point between (R)AN 210 and UPF 202 for the user plane. Thus, AMF 221 can process N2 signaling from SMF 224 and AMF 221 for PDU sessions and QoS, encapsulate / decapsulate packets for IPSec and N3 tunneling, mark N3 user plane packets in the uplink, and perform QoS corresponding to the N3 packet marking, taking into account the QoS requirements associated with such marking received via N2. The N3IWF can also relay uplink and downlink control plane NAS signaling between UE 201 and AMF 221 via the N1 reference point between UE 201 and AMF 221, and relay uplink and downlink user plane packets between UE 201 and UPF 202. The N3IWF also provides a mechanism for establishing an IPsec tunnel with UE 201. AMF 221 can expose an interface based on Namf services and can be the N14 reference point between two AMF 221s, as well as the interface between AMF 221 and the 5G Device Identifier Register (5G-EIR). Figure 2 The endpoint of the N17 reference point (not shown).

[0067] UE 201 may need to register with AMF 221 to receive network services. Registration Management (RM) is used to register or deregister UE 201 with the network (e.g., AMF 221) and establish a UE context within the network (e.g., AMF 221). UE 201 can operate in either RM registration or RM deregistration states. In RM deregistration state, UE 201 is not registered with the network, and the UE context in AMF 221 does not maintain valid location or routing information for UE 201; therefore, AMF 221 cannot reach UE 201. In RM registration state, UE 201 registers with the network, and the UE context in AMF 221 can maintain valid location or routing information for UE 201, allowing UE 201 to be reached by AMF 221. In the RM registration state, UE 201 can perform a mobility registration update process, a periodic registration update process triggered by the expiration of a periodic update timer (e.g., to notify the network that UE 201 is still active), and a registration update process to update UE capability information or renegotiate protocol parameters with the network, etc.

[0068] AMF 221 may store one or more RM contexts for UE 201, where each RM context is associated with a specific access to the network. The RM context may be a data structure, database object, etc., indicating or storing registration status and periodic update timers for each access type. AMF 221 may also store a 5GC MM context, which may be the same as or similar to the previously discussed (E)MM context. In various embodiments, AMF 221 may store CE Mode B limitation parameters of UE 201 in the associated MM or RM context. When needed, AMF 221 may also derive this value from UE usage setting parameters already stored in the UE context (and / or MM / RM context).

[0069] Connection Management (CM) can be used to establish and release signaling connections between UE 201 and AMF 221 via the N1 interface. This signaling connection enables NAS signaling exchange between UE 201 and CN 120, and includes AN signaling connections (e.g., RRC connections or UE-N3IWF connections for non-3GPP networks) between the UE and the Access Network (AN), and N2 connections between the AN (e.g., RAN 210) and AMF 221 for UE 201. UE 201 can operate in one of two CM states: CM-IDLE mode or CM-CONNECTED mode. When UE 201 operates in CM-IDLE state / mode, UE 201 may not have a NAS signaling connection established with AMF 221 via the N1 interface, and (R)AN210 signaling connections (e.g., N2 and / or N3 connections) may exist for UE 201. When UE 201 operates in CM-CONNECTED state / mode, UE 201 may have a NAS signaling connection established with AMF 221 via the N1 interface, and may have (R)AN 210 signaling connections (e.g., N2 and / or N3 connections) for UE 201. Establishing an N2 connection between (R)AN 210 and AMF 221 allows UE 201 to transition from CM-IDLE mode to CM-CONNECTED mode, and when the N2 signaling between (R)AN 210 and AMF 221 is released, UE 201 can transition from CM-CONNECTED mode to CM-IDLE mode.

[0070] SMF 224 can be responsible for: Session Management (SM) (e.g., session establishment, modification, and release, including tunnel maintenance between UPF and AN nodes); UE IP address allocation and management (including optional authorization); selecting and controlling UP functions; configuring traffic routing at the UPF to route traffic to the correct destination; terminating the interface to policy control functions; controlling policy enforcement and a portion of QoS; lawful interception (for SM events and the interface with the LI system); terminating NAS messages for the SM portion; downlink data notification; initiating AN-specific SM information, sent to the AN via N2 through the AMF; and determining the SSC mode of the session. SM can refer to the management of PDU sessions, and a PDU session or "session" can refer to the PDU connection service that provides or enables PDU exchange between UE 201 and the data network (DN) 203 identified by the data network name (DNN). A PDU session can be established upon request from UE 201, modified upon request from both UE 201 and 5GC 220, and released upon request from both UE 201 and 5GC 220 using NAS SM signaling exchanged at the N1 reference point between UE 201 and SMF 224. Based on a request from the application server, 5GC 220 can trigger a specific application in UE 201. In response to receiving a trigger message, UE 201 can pass the trigger message (or relevant portions / information of the trigger message) to one or more identified applications in UE 201. One or more identified applications in UE 201 can establish a PDU session to a specific DNN. SMF 224 can check whether a UE 201 request matches the user subscription information associated with UE 201. In this regard, SMF 224 can retrieve and / or request updates from UDM 227 regarding SMF 224-level subscription data.

[0071] The SMF 224 can include the following roaming functions: handling local implementation to apply QoS SLAs (VPLMN); charging data collection and charging interface (VPLMN); lawful interception (in the interface between the VPLMN and LI systems for SM events); and support for interaction with external DNs to transmit PDU session authorization / authentication signaling over the external DN. An N16 reference point between two SMF 224s can be included in system 200, which can be between another SMF 224 in the access network and an SMF 224 in the home network in a roaming scenario. Additionally, the SMF 224 can expose an interface based on NSMF services.

[0072] NEF 223 can provide means for securely exposing services and capabilities provided by 3GPP network functions to third parties, internal exposure / re-exposure, application functions (e.g., AF 228), edge computing, or fog computing systems. In such embodiments, NEF 223 can authenticate, authorize, and / or restrict AFs. NEF 223 can also translate information exchanged with AF 228 and information exchanged with internal network functions. For example, NEF 223 can translate between AF service identifiers and internal 5GC information. NEF 223 can also receive information from other network functions (NFs) based on their exposure capabilities. This information can be stored as structured data in NEF 223 or stored in a data storage device NF using a standardized interface. The stored information can then be re-exposed by NEF 223 to other NFs and AFs, and / or used for other purposes, such as analysis. Additionally, NEF 223 can expose interfaces based on Nnef services.

[0073] NRF 225 can support service discovery, receiving NF discovery requests from NF instances and providing information about discovered NF instances to those instances. NRF 225 also maintains information about available NF instances and the services they support. As used herein, terms such as "instantiation" can refer to the creation of an instance, and "instance" can refer to the concrete occurrence of an object, which can happen, for example, during the execution of program code. Additionally, NRF 225 can demonstrate interfaces based on NRF services.

[0074] PCF 226 can provide policy rules to control one or more plane functions to implement them, and can also support a unified policy framework to manage network behavior. PCF 226 can also implement a front-end (FE) to access subscription information related to policy decisions in the UDR of UDM 227. PCF 226 can communicate with AMF 221 via the N15 reference point between PCF 226 and AMF 221, which can include PCF 226 in the access network and AMF 221 in roaming scenarios. PCF 226 can communicate with AF 228 via the N5 reference point between PCF 226 and AF 228; and with SMF 224 via the N7 reference point between PCF 226 and SMF 224. System 200 and / or CN 120 may also include the N24 reference point between PCF 226 (in the home network) and PCF 226 in the access network. Additionally, PCF 226 can expose an interface based on NPCF services.

[0075] UDM 227 can process subscription-related information to support network entities in handling communication sessions, and can store UE 201's subscription data. For example, subscription data can be exchanged between UDM 227 and AMF 221 via the N8 reference point between UDM 227 and AMF 221. Figure 2 Transmission is performed (not shown). The UDM 227 may include two parts: the application FE and the user data repository (UDR). Figure 2 (FE and UDR are not shown). The UDR can store subscription and policy data for UDM 227 and PCF 226, and / or structured and application data for exposure (including Packet Flow Descriptions (PFDs) for application detection and application request information for multiple UEs 201) for NEF 223. The UDR 221 can expose a Nudr-based service interface to allow UDM 227, PCF 226, and NEF 223 to access a specific set of stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notifications of related data changes in the UDR. The UDM may include a UDM FE, which is responsible for credential processing, location management, subscription management, etc. Several different front-ends can serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing; user identification processing; access authorization; registration / mobility management; and subscription management. The UDR can interact with SMF 224 via the N10 reference point between UDM 227 and SMF 224. The UDM 227 also supports SMS management, with SMS-FE implementing similar application logic as described above. Additionally, the UDM 227 can display interfaces based on Nudm services.

[0076] AF 228 can influence traffic routing, provide access to Network Capability Exposure (NCE), and interact with the policy framework for policy control. NCE can be a mechanism allowing 5GC 220 and AF 228 to provide information to each other via NEF 223, which can be used for edge computing implementations. In such implementations, network operators and third-party services can be hosted close to the UE 201 access connection point to achieve efficient service delivery by reducing end-to-end latency and load on the transport network. For edge computing implementations, 5GC can select a UPF 202 close to UE 201 and perform service routing from UPF 202 to DN 203 via the N6 interface. This can be based on UE subscription data, UE location, and information provided by AF 228. In this way, AF 228 can influence UPF (re)selection and service routing. Based on operator deployment, when AF 228 is considered a trusted entity, network operators can allow AF 228 to interact directly with the relevant NF. Additionally, AF 228 can expose interfaces based on Naf services.

[0077] NSSF 229 can select a set of network slice instances to serve UE 201. NSSF 229 can also determine the allowed network slice selection assistance information (NSSAI) and the mapping to the subscribed single NSSAI (S-NSSAI), if needed. NSSF 229 can also determine the set of AMFs or a list of candidate AMFs 221 for serving UE 201 based on appropriate configuration and possibly by querying NRF 225. The selection of a set of network slice instances for UE 201 can be triggered by AMF 221 (which registers UE 201 by interacting with NSSF 229), which can result in a change to AMF 221. NSSF 229 can interact with AMF 221 via the N22 reference point between AMF 221 and NSSF 229; and via the N31 reference point ( Figure 2 (Not shown) communicates with another NSSF 229 in the access network. Additionally, the NSSF 229 can display an interface based on the Nnssf service.

[0078] As previously mentioned, 5GC 220 may include an SMSF, which can be responsible for SMS subscription checks and authentication, as well as relaying SM messages from other entities to UE 201 and from UE 201 to other entities, such as SMS-GMSC / IWMSC / SMS routers. SMS can also interact with AMF 221 and UDM 227 for notification procedures when UE 201 is available for SMS delivery (e.g., setting a UE unreachable flag and notifying UDM 227 when UE 201 is available for SMS).

[0079] 5GC 220 may also include Figure 2 Other components not shown include the data storage system / architecture, the 5G Device Identity Register (5G-EIR), the Secure Edge Protection Agent (SEPP), and so on. The data storage system may include Structured Data Storage Network Function (SDSF), Unstructured Data Storage Network Function (UDSF), and so on. Any NF can be connected via an N18 reference point between any NF and the UDSF. Figure 2 Unstructured data (e.g., UE context) is stored in or retrieved from the UDSF (not shown). Individual NFs can share a UDSF for storing their respective unstructured data, or each NF can have its own UDSF located at or near the respective NF. Additionally, the UDSF can expose an interface based on Nudsf services (…). Figure 2 (Not shown). 5G-EIR can be an NF that checks the status of a Permanent Device Identifier (PEI) to determine whether a specific device / entity is blacklisted from the network; SEPP can be a non-transparent agent that performs topology hiding, message filtering, and policing on the control plane interface between PLMNs.

[0080] Additionally, there may be more reference points and / or service-based interfaces between NF services within an NF; however, for clarity, Figure 2 These interfaces and reference points are omitted. In one example, the 5GC 220 may include an Nx interface, which is the CN-to-CN interface between the MME and AMF 221 to enable interoperability between the EPC and the 5GC 220. Other example interfaces / reference points may include the interface based on the N5g-eir service demonstrated by 5G-EIR, the N27 reference point between the NRF in the access network and the NRF in the home network; and the N31 reference point between the NSSF in the access network and the NSSF in the home network.

[0081] As mentioned, UPF 202 may include an uplink classifier / branch point (UL CL / BP), in Figure 2 Not shown in the diagram. This UL CL / BP is a function that forces selected traffic to enter local DN 203 via a local PDU session stream.

[0082] 3GPP is working on further system enhancements to support edge computing. One of the issues being investigated, as defined in Technical Implementation (TR) 23.748, is “Edge Application Server Discovery.” In edge computing deployments, an application service may be served by multiple Edge Application Servers (EASs), typically deployed in different locations. These multiple EAS instances carrying the same content or service can use a single IP address (anycast address) or different IP addresses. Before an application / UE begins connecting to a service, it is crucial for the application / UE to discover the IP address of a suitable EAS (e.g., the nearest EAS) so that traffic can be locally routed to the EAS via UL CL / BP mechanisms, optimizing service latency, traffic routing paths, and user service experience. Furthermore, once the discovered EAS becomes no longer optimal (e.g., after the UE is moved), a new EAS can be used to replace the old one and continue serving the application / UE.

[0083] Edge computing deployments are used for a select group of applications that can benefit from the geographical proximity between the UE and the application server, primarily due to reduced latency. In contrast, latency-insensitive applications typically continue to be served by application servers located remotely (also known as the “cloud”).

[0084] This assumes that edge computing deployments in a given operator network may not be ubiquitous, meaning there may be geographical areas that support edge computing for specific applications and other areas that do not. In the latter case, it is assumed that applications can be served from application servers in the cloud, although performance will be reduced. It is also assumed that the UE has an established PDU session with a remote PDU session anchor (PSA) (e.g., a PSA in a remote UPF), which is also equipped with a UL CL / BP.

[0085] This disclosure provides a solution for handling Directory Name System (DNS) requests. Embodiments may propose a method for resolving an Internet Protocol (IP) address (e.g., a destination IP address) included in a DNS request to the IP address of an Application Server (EAS) located in a local Domain Name (DN) or a Cloud Domain Name (ND) (hereinafter also referred to as a "cloud DN"), depending on whether the application server is deployed in the local DN. For example, if the fully qualified domain name (FQDN) included in the DNS request corresponds to an application for which an EAS is deployed in the local DN, the method described herein can resolve the FQDN to the IP address of the EAS; otherwise, if the FQDN corresponds to an application for which no EAS is deployed in the local DN, the method described herein can resolve the FQDN to the IP address of the cloud EAS.

[0086] Figure 3 An example architecture of a 5G system (5GS) 300 including a DNS checker for EAS discovery is shown according to some embodiments of the present disclosure.

[0087] 5GS 300 is shown to include UE 301, which can be used in conjunction with previously... Figure 1 and Figure 2 The UE 101 and UE 201 discussed are the same or similar; AN 310, which may be consistent with the previous provisions. Figure 1 and Figure 2 The RAN 110 and AN 210 discussed are the same or similar; and DN 303, which may be the same as previously discussed. Figure 2 The DN 203 discussed is the same as or similar to DN 203. DN 303 can be accessed using a Local Directory Name System (L-DNS) 308 or Cloud DNS (C-DNS) 309. DN 303 may include multiple Edge Application Servers (EAS) 307 to provide services such as network operator services, internet access, or third-party services. EAS 307 can be deployed in different locations, such as locally on UE 301 or remotely on UE 301 (i.e., in the cloud). Multiple instances of EAS 307 can host the same content or services, and therefore can use a single IP address (anycast address) or different IP addresses. Before UE 301 begins connecting to a service, it is important for UE 301 to discover the IP address of a suitable EAS 307 (e.g., the nearest EAS 307) so that traffic can be locally routed to EAS 307 via the UL CL / BP mechanism (described in detail below), and service latency, traffic routing paths, and user service experience can be optimized.

[0088] The 5GS 300 may also include a UPF 302. (And...) Figure 2 Similar to UPF 202, UPF 302 can serve as an anchor point for mobility within and between RATs, an external PDU session point for interconnection to DNs, and a branch point (BP) supporting multi-homed PDU sessions. UPF 302 can also perform packet routing and forwarding, packet inspection, enforcement of policy rules in the user plane portion, lawful packet interception (UP sets), traffic usage reporting, QoS processing on the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), uplink traffic authentication (e.g., SDF to QoS traffic mapping), transport level packet marking in uplink and downlink, and downlink packet buffering and downlink data notification triggering. UPF 302 may include ULCL / BP 305 to force selected traffic to flow through the local PSA ( Figure 3The PSA2)304 in the UPF 302 enters DN 303. The UPF 302 may also include a UL CL / BP (not shown) to force selected flow through a remote PSA (…). Figure 3 PSA1)311 enters DN 303. UPF302 can interact with SMF 324 via the N4 reference point between SMF 324 and UPF 302.

[0089] The 5GS 300 can also include SMF 324, AMF 321, NEF 323, PCF 326, and AF 328. Figure 2 All descriptions of SMF224, AMF 221, NEF 223, PCF 226, and AF 228 are equally applicable to SMF 324, AMF 321, NEF323, PCF 326, and AF 328, and will not be repeated here.

[0090] Additionally, the 5GS 300 may include a DNS checker 306. The DNS checker 306 may be a logical function located in any of the UPF 302, SMF324, and local DN 303, or it may be a separate entity.

[0091] In this embodiment, UL CL / BP 305, for example, uses the UL CL rule for destination port number 53 to forward all DNS requests from the N3 interface to DNS checker 306. Packets do not pause here, nor is there any state to maintain.

[0092] Figure 4 An example EAS discovery process 400 using DNS checker 306 is shown according to some embodiments of this disclosure.

[0093] The EAS discovery process 400 can involve Figure 3 The UE 301, AN 310 (which may be NG-RAN 310), UL CL / BP 305 of UPF 302, DNS checker 306, local PSA (PSA2) 304, L-DNS 308, remote PSA (PSA1) 311, and C-DNS 309 are shown and discussed.

[0094] In step 1, UE 301 sends a DNS request to UPF 302 via NG-RAN 310. The DNS request may include a source IP address corresponding to UE 301's own IP address (hereinafter referred to as "UE-IP") and a destination IP address corresponding to the default DNS server (hereinafter referred to as "default DNS-IP").

[0095] In step 2, UPF 302 forwards the DNS request to DNS checker 306 using UL CL / BP 305. The packet proceeds without pause or state maintenance.

[0096] In step 3, DNS checker 306 modifies the destination IP address of the DNS request (i.e., the default DNS-IP) to the IP address of L-DNS 308 and stores the default DNS-IP for subsequent processing; and modifies the source IP address of the DNS request (i.e., the UE-IP) to the IP address of DNS checker 306 and stores the UE-IP for subsequent processing.

[0097] In step 4, DNS checker 306 forwards the modified DNS request to L-DNS 308 via PSA2, and performs the following processing:

[0098] If L-DNS 308 can resolve the IP address of the FQDN of the EAS specified in the DNS request, then step 5 is skipped, and L-DNS 308 can respond to DNS checker 306 with the expected IP address of the local EAS.

[0099] - If L-DNS 308 cannot resolve the IP address of the FQDN of EAS specified in the DNS request, and L-DNS 308 is not connected to C-DNS 309, skip step 5, and L-DNS 308 can respond to DNSInspector 306 with a DNS response that does not include the IP address of EAS or includes information indicating that it cannot resolve the FQDN.

[0100] If L-DNS 308 is unable to resolve the IP address of the EAS's FQDN specified in the DNS request, but is connected to C-DNS 309, L-DNS 308 may communicate with C-DNS 309 to recursively resolve the EAS's IP address, as described in step 5.

[0101] In step 5, L-DNS 308 recursively forwards DNS requests to C-DNS 309, and C-DNS 309 responds to L-DNS 308 with DNS that includes the IP address of the cloud / remote ESA.

[0102] In step 6, L-DNS 308 sends a DNS response to DNS checker 306, which includes the resolved IP address of the local EAS or cloud / remote EAS or a null value indicating that L-DNS 308 cannot resolve the FQDN.

[0103] For option A: If DNS checker 306 receives a DNS response including the resolved IP address of the EAS's FQDN specified in the DNS request (whether it's the expected local EAS IP address or the resolved cloud / remote EAS IP address), then in step 7a, DNS checker 306 may replace the source IP address and destination IP address of the DNS response with the stored default DNS-IP and UE-IP, respectively, and then forward the DNS response to UL CL / BP 305 of UPF 302. In step 8a, UL CL / BP 305 of UPF 302 forwards the DNS response arriving from DNS checker 306 to UE 301 via the N3 interface.

[0104] Alternatively, for option B: If DNS checker 306 receives a DNS response including a null value indicating that L-DNS 308 cannot resolve the FQDN, then in step 7b, DNS checker 306 may forward the original DNS request (i.e., the DNS request that initially arrived from UL CL / BP 305 of UPF 302) back to UL CL / BP 305 of UPF 302. In step 8b, UL CL / BP 305 of UPF 302 forwards the original DNS request from DNS checker 306 to PSA1 311 via the N9 interface. In step 9b, C-DNS 309 responds to UE 301 with a DNS response including the IP address of the cloud / remote ESA.

[0105] After UE 301 receives a DNS response containing the IP address of the EAS, subsequent application traffic from UE 301 will be automatically routed by UL CL / BP 305 of UPF 302 to the desired EAS in the local DN or the EAS in the cloud, depending on the destination IP address.

[0106] Alternatively, in some embodiments, if DNS checker 306 determines after step 2 that the FQDN of the EAS specified in the DNS request cannot be resolved by L-DNS 308 (e.g., because the FQDN corresponds to a server in the cloud and DNS checker 306 is configured to know that L-DNS 308 is not connected to C-DNS 309), then DNS checker 306 can directly skip to step 7b above, that is, return the original unmodified DNS request to UL CL / BP 305 of UPF 302.

[0107] As described above, DNS checker 306 can be a logical function residing in any of UPF 302, SMF 324, or local DN 303, or it can be a standalone entity in 5GC. If DNS checker 306 resides in SMF 324 or is a standalone entity in 5GC, the DNS response in step 6 is forwarded via UL CL / BP 305 of UPF 302 using DL classifier rules that detect the DNS checker address as the destination IP address. If DNS checker 306 resides in SMF 224, DNS requests and responses are exchanged between UL CL / BP 305 of UPF 302 and SMF 224 in an N4 signaling message. If DNS checker 306 is located in local DN 303, DNS requests and responses can be carried in the UE-specific N9 tunnel between UL CL / BP 305 of UPF 302 and PSA2 308, and in the pre-configured non-UE-specific N6 tunnel between PSA2 308 of UPF 302 and DNS checker 306. UE-specific N9 tunnels from multiple UEs can be mapped to a single non-UE-specific N6 tunnel. For a specific DNS response arriving at the non-UE-specific N6 tunnel, PSA2 308 selects the UE-specific N9 tunnel that matches the UE's IP address.

[0108] Figure 5 This is a flowchart illustrating a process 500 for EAS discovery in 5GS based on a DNS checker, according to some embodiments of the present disclosure. Process 500 can be performed by a DNS checker, such as those described above. Figure 3 and Figure 4 The DNS checker 306 is discussed.

[0109] Processing 500 may include, in block 510, modifying the DNS request of the UE received from the UPF's UL CL / BP by: modifying the destination Internet Protocol (IP) address of the DNS request to the IP address of the L-DNS and storing the destination IP address of the DNS request for subsequent processing, and modifying the source IP address of the DNS request to the IP address of the DNS checker and storing the source IP address of the DNS request for subsequent processing, wherein the destination IP address of the DNS request corresponds to the default DNS server and the source IP address of the DNS request corresponds to the IP address of the UE.

[0110] Processing 500 may include, in box 520, forwarding the modified DNS request to L-DNS.

[0111] Processing 500 may include, in box 530, determining, based on the DNS response from the L-DNS, whether the FQDN of the EAS specified in the DNS request has been resolved.

[0112] If it is determined in box 530 that the FQDN has been resolved to the IP address of the EAS, then process 500 may include, in box 540, replacing the source IP address and destination IP address of the DNS response with the destination IP address and source IP address of the stored DNS request, respectively; and, in box 550, forwarding the DNS response to the UPF's UL CL / BP.

[0113] If it is determined in box 530 that the FQDN is not resolved, then process 500 may include, in box 560, forwarding the DNS request initially received from the UPF's ULCL / BP back to the UPF's ULCL / BP.

[0114] Figure 6 This is a flowchart illustrating another process 600 for EAS discovery using a DNS-based checker in 5GS according to some embodiments of this disclosure. Process 600 can be performed by a UPF, for example, as described above. Figure 3 and Figure 4 UPF 302 under discussion.

[0115] Processing 600 may include, in box 610, forwarding a DNS request from the UE to a DNS checker. Processing 600 may also include, in box 620, receiving either a DNS response or the DNS request itself from the DNS checker. Whether a DNS response or a DNS request is received depends on whether the FQDN of the EAS specified in the DNS request can be resolved to the IP address of the EAS.

[0116] Figure 7 This is a flowchart illustrating another process 700 for EAS discovery using a DNS-based checker in 5GS according to some embodiments of this disclosure. Process 700 can be performed by L-DNS, such as those described above. Figure 3 and Figure 4 The L-DNS308 is under discussion.

[0117] Processing 700 may include, in box 710, receiving a DNS request from the UE forwarded by the DNS checker.

[0118] Process 700 may include, at box 720, determining whether the L-DNS can resolve the FQDN of the EAS specified in the DNS request. If it is determined at box 720 that the L-DNS can resolve the FQDN of the EAS, then process 700 may include, at box 730, responding to the DNS checker with a DNS response including the expected IP address of the L-EAS. If it is determined at box 720 that the L-DNS cannot resolve the FQDN of the EAS, then process 700 proceeds to box 740 to determine whether the L-DNS is connected to the C-DNS.

[0119] If it is determined in box 740 that the L-DNS is not connected to the C-DNS, then processing 700 may include, in box 750, responding to the DNS checker with a DNS response that does not include the IP address of the EAS or has information indicating that the L-DNS cannot resolve the DNS request.

[0120] If it is determined in box 740 that the L-DNS is connected to the C-DNS, then process 700 proceeds to box 760 to communicate with the C-DNS to recursively resolve the FQDN. Process 700 may include, in box 770, receiving the IP address of the cloud EAS from the C-DNS. Process 700 may also include, in box 780, responding to the DNS checker with a DNS response including the IP address of the cloud EAS.

[0121] More specifically, Figure 5 Processing 500 Figure 6 Processing 600, and Figure 7 The processing 700 can be implemented in one or more modules as a set of logic instructions stored in a machine or computer-readable storage medium such as random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), firmware, flash memory; in configurable logic such as programmable logic array (PLA), field-programmable gate array (FPGA), complex programmable logic device (CPLD); in fixed-function logic hardware using circuit technologies such as application-specific integrated circuit (ASIC), complementary metal-oxide-semiconductor (CMOS) or transistor-transistor logic (TTL); or in any combination thereof.

[0122] For example, used to execute Figure 5 Processing 500 Figure 6 Processing 600, and Figure 7The computer program code for processing the operations shown in 700 can be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as JAVA, SMALLTALK, C++, etc., and conventional procedural programming languages ​​such as the "C" programming language or similar programming languages. Additionally, the logic instructions can include assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, state setting data, integrated circuit configuration data, and state information that personalizes hardware-local electronic circuits and / or other structural components (e.g., main processor, central processing unit / CPU, microcontroller, etc.).

[0123] As proposed by Working Group 2 on Services and Systems (SA WG2), in 5G systems (5GS) (e.g., Figure 1 System 100 and Figure 2 The 5G system (System 200) will support user equipment to user equipment (UE to UE) operations. Several issues regarding UE to UE relay operations in 5G have been identified. One of these issues concerns whether and how the 5G network controls UE to UE relay operations, such as how to authorize a UE to become a UE to UE relay or how to provide the source / destination UE and the visibility of the UE to the network for purposes such as billing.

[0124] This disclosure provides a solution for configuring UE-to-UE relay operation in 5GS. Embodiments may propose methods to authorize a UE to act as a UE-to-UE relay for 5G Proximity-Based Service (ProSe) and configure 5G ProSe UE-to-UE relay information for the UE, and enable the UE to access 5G ProSe UE-to-UE relays and configure 5G ProSe UE-to-UE relay access information for the UE.

[0125] refer to Figure 1 and Figure 2 Each of UE 101a, UE 101b and UE 201 can be authorized and configured by a core network such as 5GC 220 to act as a 5G ProSe UE to UE relay based on the UE's 5G ProSe UE to UE relay capability.

[0126] Figure 8 A simplified registration process 800 for a UE according to some embodiments of this disclosure is illustrated. Note that, for the sake of simplicity and clarity of this disclosure, in... Figure 8 Some steps have been omitted. The entire registration process is defined in Section 4.2.2.2 of Technical Specification (TS) 23.502, which is incorporated herein by reference.

[0127] exist Figure 8In the middle, UE 801 can be with Figure 1 and Figure 2 UE 101a, UE 101b and UE 201 are the same as or similar; (R)AN810 can be with Figure 1 and Figure 2 RAN 110 and (R)AN 210 are the same or similar; AMF 821 can be with Figure 2 The AMF 221 is the same as or similar to it; and PCF 826 can be the same as... Figure 2 The same as or similar to PCF 226.

[0128] In step 1, UE 801 sends a registration request message to (R)AN 810. This registration request message may include information indicating UE 801's 5G ProSe UE-to-UE relay capability.

[0129] (R)AN 810 selects AMF 821 for UE 801 in step 2, and sends a registration request message including information indicating UE 801's 5G ProSe UE-to-UE relay capability to the selected AMF 821 in step 3.

[0130] In step 4, AMF 821 selects PCF 826 that supports 5G ProSe information configuration for the UE, and in step 5, notifies the UE 801 that the registration request has been accepted.

[0131] In step 6, AMF 821 then communicates with PCF 826 to establish a UE policy association for 5G ProSe UE-to-UE relay information configuration delivery.

[0132] Section 4.2.2.2 of TS 23.502 has defined the details of the UE policy association establishment process, which is incorporated herein by reference and will not be literally repeated. During the UE policy association establishment process, AMF 821 may report UE 801's 5G ProSe UE-to-UE relay capability to PCF 826.

[0133] PCF 826 can then determine 5G ProSe UE-to-UE relay information for the UE based on the UE's 5G ProSe UE-to-UE relay capability.

[0134] In some embodiments, UE 801 supports 5G ProSe UE-to-UE relay capability but lacks valid 5G ProSe UE-to-UE relay information. In this case, UE 801 may send a UE policy container during registration procedure 800, which includes information indicating a 5G ProSe UE-to-UE relay information configuration request. If UE 801 indicates a 5G ProSe UE-to-UE relay information configuration request in the UE policy container, PCF 826 may determine during the UE policy association establishment procedure whether to configure 5G ProSe UE-to-UE relay information to the UE, as specified in Section 6.1.2.2.2 of TS 23.503. If PCF 826 determines to configure 5G ProSe UE-to-UE relay information to the UE, PCF 826 may provide the 5G ProSe UE-to-UE relay information to the UE using the “UE Configuration Update procedure for transparent UE Policy Delivery” as defined in Section 4.2.4.3 of TS 23.502. Both TS 23.503 and TS 23.502 are incorporated herein by reference.

[0135] The 5G ProSe UE-to-UE relay information of UE 801 may need to be updated if at least one of the following conditions occurs:

[0136] - UE mobility, for example, a UE moving from one Public Land Mobile Network (PLMN) to another. This is achieved using a UE policy association modification procedure initiated by the AMF (as defined in Section 4.16.12.1 of TS 23.502).

[0137] - There are subscription changes in the list of PLMNs, and the UE is authorized to perform 5G ProSe UE-to-UE relay operations in these PLMNs. This is achieved using a UE policy association modification procedure initiated by the PCF (as defined in Section 4.16.12.2 of TS 23.502).

[0138] - As described in Section 4.15.6.7 of TS 23.502, there are variations in service-specific parameters.

[0139] For example, if a PLMN that is providing services is removed from the PLMN list in the service authorization parameters, the service authorization will be revoked from UE 801.

[0140] For example, when UE 801 is roaming, subscription changes that cause service authorization parameter updates can be transmitted to the UE by H-PCF via V-PCF.

[0141] When a UE determines that the 5G ProSe UE-to-UE relay information is invalid (e.g., the policy / parameters are outdated, lost, or invalid), it may initiate a UE-triggered policy configuration procedure to the PCF in accordance with the provisions of Section 6.2.4 of TS 23.287, the contents of which are incorporated herein by reference.

[0142] The 5G ProSe UE-to-UE relay information configured by PCF 826 to support UE 801 acting as a 5G ProSe UE-to-UE relay may include any of the following: an authorization policy for acting as a 5G ProSe UE-to-UE relay when "served by NG-RAN"; a 5G ProSe relay discovery policy / parameters for 5G ProSe UE-to-UE relay; radio parameters for 5G ProSe relay discovery; radio parameters for 5G ProSe relay communication; a mapping rule between 5G ProSe PC5 5QI (PQI) and Uu 5QI values; and / or a mapping rule between 5G ProSe PC5 5QI and Uu QCI values. "PC5" refers to the interface used for vehicle-to-everything (V2X) communication. "Uu" refers to the radio interface between the UTRAN and the UE. "5QI" is an abbreviation for 5G QoS identifier. "QCI" is an abbreviation for QoS class identifier.

[0143] When “served by NG-RAN”, the authorization policy for acting as a 5G ProSe UE-to-UE relay may include PLMNs in which the UE is authorized to access other UE relay traffic of that UE-to-UE relay.

[0144] The 5G ProSe relay discovery policy / parameters for 5G ProSe UE-to-UE relays may include the following parameters: these parameters, when configured from the PCF to the mobile device (ME) or configured in a Universal Integrated Circuit Card (UICC), enable the UE to perform 5G ProSe relay discovery as a UE-to-UE relay. These parameters may include indications regarding the UE-to-UE relay role and 5G ProSe UE-to-UE relay discovery parameters (e.g., User Info ID and one or more relay service codes). For Layer 3 relays, these parameters may also include PDU session parameters (e.g., PDU session type, Data Network Name (DNN), Session and Service Continuity (SSC) mode, Single Network Slice Selection Assistance Information (S-NSSAI), Access Type Preference, etc.) to be used for relay traffic for each ProSe relay service code. These parameters may also include security-related content for 5G ProSe relay discovery for each 5G ProSe relay service code.

[0145] Radio parameters for 5G ProSe relay discovery may include radio parameters with one or more geographical regions. These radio parameters need to be configured in the UE to enable the 5G ProSe direct discovery process when acting as a 5G ProSe UE-to-UE relay. These radio parameters (e.g., frequency bands) are defined in TS 38.331 and are common to all types of 5G ProSe direct discovery, including group membership discovery, 5G ProSe UE-to-UE relay discovery, or 5G ProSe UE-to-UE relay discovery with additional information. A UE can only use these radio parameters if it can locate itself in the appropriate geographical region. Otherwise, the UE is not authorized to transmit these radio parameters.

[0146] Radio parameters for 5G ProSe relay communication may include radio parameters with one or more geographical areas. These radio parameters need to be configured in the UE to enable 5G ProSe direct communication procedures when acting as a 5G ProSe UE-to-UE relay. These radio parameters (e.g., frequency bands) are defined in TS 38.331 and are common to all types of 5G ProSe direct communication, including one-to-one, one-to-many, or ProSe UE-to-UE relay. A UE can only use radio parameters if it can locate itself in the appropriate geographical area. Otherwise, the UE is not authorized to transmit these radio parameters.

[0147] The mapping rules between 5G ProSe PQI and Uu 5QI values ​​can include rules that determine how 5G ProSe UE-to-UE relays map between the 5QI of the QoS flow on NR Uu and the 5G ProSe PQI value on NR PC5.

[0148] The mapping rules between 5G ProSe PC5 5QI (PQI) and Uu QCI values ​​can include rules that determine how 5G ProSe UE-to-UE relays are mapped between the QCI carried by the Evolved Packet System (EPS) on E-UTRA Uu and the 5G ProSe PQI value on NR PC5.

[0149] In order to access 5G ProSe UE-to-UE relay, the UE may indicate its ability to access 5G ProSe UE-to-UE relay during the registration process as defined in Section 4.2.2.2 of TS 23.502.

[0150] Figure 8 Another simplified registration process 900 for a UE according to some embodiments of this disclosure is shown. Note that, for the sake of simplicity and clarity of this disclosure, in... Figure 9 Some steps have been omitted.

[0151] exist Figure 9 In the middle, UE 901 can be with Figure 1 and Figure 2 UE 101a, UE 101b and UE 201 are the same as or similar; (R)AN910 can be with Figure 1 and Figure 2 RAN 110 and (R)AN 210 are the same or similar; AMF 921 can be with Figure 2 The AMF 221 is the same as or similar to it; and PCF 926 can be the same as... Figure 2 The same as or similar to PCF 226.

[0152] In step 1, UE 901 sends a registration request message to (R)AN 910. The registration request message may include information indicating UE 901's 5G ProSe UE-to-UE relay access capability (i.e., the ability to access 5G ProSe UE-to-UE relay).

[0153] (R)AN 910 selects AMF 921 for UE 901 in step 2, and sends a registration request message including information indicating UE 901's 5G ProSe UE-to-UE relay access capability to the selected AMF 921 in step 3.

[0154] In step 4, AMF 921 selects PCF 926 for the UE to support 5G ProSe information configuration, and in step 5, notifies the UE 901 that the registration request has been accepted.

[0155] In step 6, AMF 921 then communicates with PCF 926 to establish a UE policy association for 5G ProSe UE-to-UE relay access information configuration delivery.

[0156] During the UE policy association establishment process, AMF 921 can report UE 901's 5G ProSe UE-to-UE relay access capability to PCF 926.

[0157] PCF 926 can then determine 5G ProSe UE-to-UE relay access information for the UE based on the UE's 5G ProSe UE-to-UE relay access capability.

[0158] In some embodiments, UE 901 supports 5G ProSe UE-to-UE relay access capability but lacks valid 5G ProSe UE-to-UE relay access information. In this case, UE 901 may send a UE policy container during the registration process 900, which includes information indicating a 5G ProSe UE-to-UE relay access information configuration request. If UE 901 indicates a 5G ProSe UE-to-UE relay access information configuration request in the UE policy container, PCF 926 may determine during the UE policy association establishment process whether to configure 5G ProSe UE-to-UE relay access information to the UE, as specified in Section 6.1.2.2.2 of TS 23.503. If PCF 926 determines to configure 5G ProSe UE-to-UE relay access information to the UE, PCF 926 may use the “UE Configuration Update procedure for transparent UE Policy Delivery” as defined in Section 4.2.4.3 of TS 23.502 to provide 5G ProSe UE-to-UE relay access information to the UE.

[0159] The 5G ProSe UE-to-UE relay access information of UE 901 may need to be updated if at least one of the following conditions occurs:

[0160] - UE mobility, for example, a UE moving from one PLMN to another. This is achieved using a UE policy association modification procedure initiated by the AMF (as defined in Section 4.16.12.1 of TS 23.502).

[0161] - There are subscription changes in the list of PLMNs, and the UE is authorized to perform 5G ProSe UE-to-UE relay operations in these PLMNs. This is achieved using a UE policy association modification procedure initiated by the PCF (as defined in Section 4.16.12.2 of TS 23.502).

[0162] - As described in Section 4.15.6.7 of TS 23.502, there are variations in service-specific parameters.

[0163] For example, if a PLMN that is providing services is removed from the PLMN list in the service authorization parameters, the service authorization will be revoked from UE 901.

[0164] For example, when UE 901 is roaming, subscription changes that cause service authorization parameter updates can be transmitted to the UE by H-PCF via V-PCF.

[0165] When a UE determines that the 5G ProSe UE-to-UE relay information is invalid (e.g., the policy / parameters are outdated, lost, or invalid), it can initiate a UE-triggered policy configuration procedure to the PCF in accordance with the provisions of Section 6.2.4 of TS 23.297.

[0166] The 5G ProSe UE-to-UE Relay access information configured by PCF 926 to support UE 901 access to 5G ProSe UE-to-UE Relay may include any of the following: an authorization policy for using 5G ProSe UE-to-UE Relay, a policy / parameter for 5G ProSe UE-to-UE Relay discovery and enabling connection to 5G ProSe UE-to-UE Relay after discovery is performed, and / or radio parameters when the UE is not "served by NG-RAN".

[0167] The licensing policy for using 5G ProSe UE-to-UE relay can indicate whether a UE is authorized to use UE-to-UE relay.

[0168] Policies / parameters for 5G ProSe UE-to-UE relay discovery and enabling connection to 5G ProSe UE-to-UE relay after discovery can include parameters for 5G ProSe UE-to-UE relay discovery. These parameters, when configured to the ME from the PCF or configured in the UICC, also enable the UE to connect to the 5G ProSe UE-to-UE relay after discovery. These parameters may include indications about using UE-to-UE relay, 5G ProSe UE-to-UE relay discovery parameters (e.g., User Info ID and one or more relay service codes), or one or more IP versions that can be used for relay traffic for each ProSe relay service code. For Layer 2 relay, these parameters may also include PDU session parameters (e.g., PDU session type, DNN, SSC mode, S-NSSAI, access type preference, etc.) that will be used for relay traffic for each ProSe relay service code. These parameters may also include security-related content for 5G ProSe relay discovery for each 5G ProSe relay service code.

[0169] Radio parameters when the UE is not "served by NG-RAN" may include radio parameters with one or more geographical regions. These radio parameters need to be configured in the UE to perform the 5G ProSe direct discovery procedure as a UE accessing 5G ProSe UE-to-UE relay when not "served by NG-RAN". These radio parameters (e.g., frequency bands) are defined in TS 39.331 and are common to all types of 5G ProSe direct discovery (including group membership discovery, 5G ProSe UE-to-UE relay discovery, or 5G ProSe UE-to-UE relay discovery additional information). The UE can only use these radio parameters if it can locate itself in the appropriate geographical region. Otherwise, the UE is not authorized to send these radio parameters. Radio parameters when the UE is not "served by NG-RAN" may also include radio parameters with one or more geographical regions. These radio parameters need to be configured in the UE to perform the 5G ProSe direct communication procedure as a UE accessing 5G ProSe UE-to-UE relay when not "served by NG-RAN". These radio parameters (e.g., frequency bands) are defined in TS39.331 and are common to all types of 5G ProSe direct communication (including one-to-one, one-to-many, or ProSe UE-to-UE relay). A UE may use these radio parameters only if it can locate itself in the appropriate geographic area. Otherwise, the UE is not authorized to transmit these radio parameters.

[0170] As mentioned above, both the 5G ProSe UE-to-UE relay discovery policy / parameters included in the 5G ProSe UE-to-UE relay information and the 5G ProSe UE-to-UE relay access information, which includes policies / parameters for 5G ProSe UE-to-UE relay discovery and enable connection to the 5G ProSe UE-to-UE relay after discovery, can include 5G ProSe UE-to-UE relay discovery parameters, such as a user information ID and one or more relay service codes. In embodiments, when configured from the PCF in the ME or in the UICC, the 5G ProSe UE-to-UE relay discovery parameters can include parameters that enable the UE to perform 5G ProSe UE-to-UE relay discovery. These parameters can include the user information ID. For Model A, when the UE is announcing UE, the user information ID corresponds to the announcing information parameter. For Model B, when the UE acts as a discovering UE or a found UE, the user information ID corresponds to the discovering information in the request message or the discovering information in the response message. These parameters may include one or more relay service codes. One of the relay service codes may identify the connectivity services that the 5G ProSe UE-to-UE relay will provide to the application. One or more relay service codes may be configured in the 5G ProSe UE-to-UE relay that provides connectivity services to the application. One or more relay service codes may be configured in the UE accessing the UE-to-UE relay and interested in the relevant connectivity services.

[0171] Figure 10 This is a flowchart illustrating a process 1000 for configuring UE-to-UE relay operation in a 5GS according to some embodiments of the present disclosure. Process 1000 can be executed by an AMF, such as those described above. Figure 2 , Figure 8 and Figure 9 The AMF 221, AMF821 and AMF 921 are discussed.

[0172] Processing 1000 may include, in block 1010, receiving a registration request message from a UE, the registration request message including information indicating the UE's 5G ProSe UE-to-UE relay capability (i.e., the capability to act as a 5G ProSe UE-to-UE relay for other UEs) and / or 5G ProSe UE-to-UE relay access capability (i.e., the capability to access a 5G ProSe UE-to-UE relay implemented by other UEs).

[0173] Processing 1000 may include, in box 1020, selecting a PCF that supports 5G ProSe information configuration for the UE.

[0174] Processing 1000 may further include, in block 1030, establishing a UE policy association with the PCF for 5G ProSe UE-to-UE relay information configuration delivery and / or 5G ProSe UE-to-UE relay access information configuration delivery. When the registration request message includes indications of the UE's 5G ProSe UE-to-UE relay capabilities, the UE policy association with the PCF can be used for 5G ProSe UE-to-UE relay information configuration delivery; when the registration request message includes indications of the UE's 5G ProSe UE-to-UE relay access capabilities, the UE policy association with the PCF can be used for 5G ProSe UE-to-UE relay access information configuration delivery; and when the registration request message includes both, the UE policy association with the PCF can be used for both 5G ProSe UE-to-UE relay information configuration delivery and 5G ProSe UE-to-UE relay access information configuration delivery.

[0175] Figure 11 This is a flowchart illustrating a process 1100 for configuring UE-to-UE relay operation in a 5GS according to some embodiments of the present disclosure. Process 1100 can be performed by a PCF, such as those described above. Figure 2 , Figure 8 and Figure 9 The PCF 226, PCF826 and PCF 926 are discussed.

[0176] Processing 1100 may include, in block 1110, receiving a message from the AMF, the message including information indicating the UE's 5GProSe UE-to-UE relay capability (i.e., the capability to act as a 5G ProSe UE-to-UE relay for other UEs) and / or 5GProSe UE-to-UE relay access capability (i.e., the capability to access a 5G ProSe UE-to-UE relay implemented by other UEs).

[0177] Processing 1100 may further include, in block 1120, determining 5G ProSe UE-to-UE relay information for the UE based on the UE's 5G ProSe UE-to-UE relay capability and / or determining 5G ProSe UE-to-UE relay access information for the UE based on the UE's 5G ProSe UE-to-UE relay access capability.

[0178] Figure 12 This is a flowchart illustrating a process 1200 for configuring a UE to UE relay operation in a 5GS according to some embodiments of the present disclosure. Process 1200 can be performed by the UE, for example, as described above. Figure 1 , Figure 2 , Figure 8 and Figure 9 The UEs discussed are UE 101a, UE 101b, UE 201, UE 801 and UE 901.

[0179] Processing 1200 may include, in block 1210, encoding a registration request message that includes information indicating the UE’s 5G ProSe UE-to-UE relay capability (i.e., the capability to act as a 5G ProSe UE-to-UE relay for other UEs) and / or 5G ProSe UE-to-UE relay access capability (i.e., the capability to access a 5G ProSe UE-to-UE relay implemented by other UEs).

[0180] Processing 1200 may also include, in box 1220, sending the registration request message to the AN.

[0181] Figure 13 This is a flowchart illustrating a process 1300 for configuring UE-to-UE relay operation in a 5GS according to some embodiments of the present disclosure. Process 1300 can be performed by an AMF, such as those described above. Figure 2 , Figure 8 and Figure 9 The AMF 221, AMF821 and AMF 921 are discussed.

[0182] Processing 1300 may include, in block 1310, receiving a UE policy container from the UE, the UE policy container including information for instructing the UE to make a 5G ProSe UE-to-UE relay information configuration request and / or a 5G ProSe UE-to-UE relay access information configuration request.

[0183] Processing 1300 may include, in block 1320, reporting information of the UE's 5G ProSe UE-to-UE relay information configuration request and / or 5G ProSe UE-to-UE relay access information configuration request to the PCF selected for the UE, so that the PCF can determine whether to configure 5G ProSe UE-to-UE relay information and / or 5G ProSe UE-to-UE relay access information for the UE.

[0184] Figure 14 This is a flowchart illustrating a process 1400 for configuring UE-to-UE relay operation in a 5GS according to some embodiments of the present disclosure. Process 1400 can be performed by a PCF, such as those described above. Figure 2 , Figure 8 and Figure 9 The PCF 226, PCF826 and PCF 926 are discussed.

[0185] Processing 1400 may include, in block 1410, receiving a message from the AMF, the message including a 5G ProSe UE-to-UE relay information configuration request and / or a 5G ProSe UE-to-UE relay access information configuration request for instructing the UE.

[0186] Processing 1400 may include, in block 1420, determining whether to provide 5G ProSe UE-to-UE relay information and / or 5G ProSe UE-to-UE relay access information to the UE based on the UE's 5G ProSe UE-to-UE relay information configuration request and / or 5G ProSe UE-to-UE relay access information configuration request.

[0187] More specifically, Figure 10 Processing 1000 Figure 11 Processing 1100 Figure 12 Processing 1200 Figure 13 Processing 1300, and Figure 14 The processor 1400 can be implemented in one or more modules as a set of logic instructions stored in a machine or computer-readable storage medium such as random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), firmware, flash memory; in configurable logic such as programmable logic array (PLA), field-programmable gate array (FPGA), complex programmable logic device (CPLD); in fixed-function logic hardware using circuit technologies such as application-specific integrated circuit (ASIC), complementary metal-oxide-semiconductor (CMOS) or transistor-transistor logic (TTL); or in any combination thereof.

[0188] For example, used to execute Figure 10 Processing 1000 Figure 11 Processing 1100 Figure 12 Processing 1200 Figure 13 Processing 1300, and Figure 14 The computer program code for processing the operations shown in 1400 can be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as JAVA, SMALLTALK, C++, etc., and conventional procedural programming languages ​​such as the "C" programming language or similar programming languages. Additionally, the logic instructions can include assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, state setting data, integrated circuit configuration data, and state information that personalizes hardware-local electronic circuits and / or other structural components (e.g., main processor, central processing unit / CPU, microcontroller, etc.).

[0189] Figure 15Example components of a device 1500 according to some embodiments are shown. In some embodiments, device 1500 may include at least application circuitry 1502, baseband circuitry 1504, radio frequency (RF) circuitry 1506, front-end module (FEM) circuitry 1508, one or more antennas 1510, and power management circuitry (PMC) 1512 coupled together as shown. Components of the illustrated device 1500 may be included in a UE or AN. In some embodiments, device 1500 may include fewer components (e.g., the AN may not use application circuitry 1502, but instead include a processor / controller to process IP data received from the EPC). In some embodiments, device 1500 may include additional components such as memory / storage devices, displays, cameras, sensors, or input / output (I / O) interfaces. In other embodiments, the components described below may be included in more than one device (e.g., for a Cloud-RAN (C-RAN) implementation, the circuitry may be separately included in more than one device).

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

[0191] Baseband circuit 1504 may include circuitry, such as, but not limited to, one or more single-core or multi-core processors. Baseband circuit 1504 may include one or more baseband processors or control logic to process baseband signals received from the receive signal path of RF circuit 1506 and generate baseband signals for the transmit signal path of RF circuit 1506. Baseband processing circuitry 1504 may interface with application circuitry 1502 to generate and process baseband signals and control the operation of RF circuit 1506. For example, in some embodiments, baseband circuitry 1504 may include a third-generation (3G) baseband processor 1504A, a fourth-generation (4G) baseband processor 1504B, a fifth-generation (5G) baseband processor 1504C, or one or more other baseband processors 1504D for other existing generations, generations under development, or future generations (e.g., sixth generation (6G), etc.). Baseband circuitry 1504 (e.g., one or more of baseband processors 1504A-D) can handle various radio control functions supporting communication with one or more radio networks via RF circuitry 1506. In other embodiments, some or all of the functions of baseband processors 1504A-D may be included in modules stored in memory 1504G and these functions may be executed via central processing unit (CPU) 1504E. Radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. In some embodiments, the modulation / demodulation circuitry of baseband circuitry 1504 may include Fast Fourier Transform (FFT), precoding, and / or constellation mapping / demapping functions. In some embodiments, the encoding / decoding circuitry of baseband circuitry 1504 may include convolution, tail-biting convolution, turbo, Viterbi, and / or low-density parity-check (LDPC) encoder / decoder functions. Embodiments of modulation / demodulation and encoder / decoder functions are not limited to these examples, and other suitable functions may be included in other embodiments.

[0192] In some embodiments, the baseband circuitry 1504 may include one or more audio digital signal processors (DSPs) 1504F. The audio DSP(s) 1504F may include elements for compression / decompression and echo cancellation, and in other embodiments may include other suitable processing elements. In some embodiments, components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or arranged on the same circuit board. In some embodiments, some or all components of the baseband circuitry 1504 and the application circuitry 1502 may be implemented together, for example, on a system-on-a-chip (SoC).

[0193] In some embodiments, baseband circuitry 1504 can provide communications compatible with one or more radio technologies. For example, in some embodiments, baseband circuitry 1504 can support communications with the Evolved Universal Terrestrial Radio Access Network (EUTRAN) or other Wireless Metropolitan Area Networks (WMAN), Wireless Local Area Networks (WLAN), or Wireless Personal Area Networks (WPAN). Embodiments in which baseband circuitry 1504 is configured to support radio communications with more than one radio protocol may be referred to as multimode baseband circuitry.

[0194] RF circuit 1506 can support communication with wireless networks using modulated electromagnetic radiation via non-solid-state media. In various embodiments, RF circuit 1506 may include switches, filters, amplifiers, etc., to facilitate communication with the wireless network. RF circuit 1506 may include a receive signal path that includes circuitry for down-converting the RF signal received from FEM circuit 1508 and providing a baseband signal to baseband circuit 1504. RF circuit 1506 may also include a transmit signal path that includes circuitry for up-converting the baseband signal provided by baseband circuit 1504 and providing an RF output signal to FEM circuit 1508 for transmission.

[0195] In some embodiments, the receive signal path of the RF circuit 1506 may include a mixer circuit 1506a, an amplifier circuit 1506b, and a filter circuit 1506c. In some embodiments, the transmit signal path of the RF circuit 1506 may include a filter circuit 1506c and a mixer circuit 1506a. The RF circuit 1506 may also include a synthesizer circuit 1506d for synthesizing frequencies used by the mixer circuit 1506a in both the receive and transmit signal paths. In some embodiments, the mixer circuit 1506a in the receive signal path may be configured to down-convert the RF signal received from the FEM circuit 1508 based on the synthesized frequency provided by the synthesizer circuit 1506d. The amplifier circuit 1506b may be configured to amplify the down-converted signal, and the filter circuit 1506c may be a low-pass filter (LPF) or a band-pass filter (BPF) configured to remove unwanted signals from the down-converted signal to generate an output baseband signal. The output baseband signal can be provided to the baseband circuit 1504 for further processing. In some embodiments, the output baseband signal may be a zero-frequency baseband signal, but this is not required. In some embodiments, the mixer circuit 1506a receiving the signal path may include a passive mixer, but the scope of the embodiments is not limited in this respect.

[0196] In some embodiments, the mixer circuit 1506a of the transmit signal path can be configured to up-convert the input baseband signal based on the synthesis frequency provided by the synthesizer circuit 1506d to generate an RF output signal for the FEM circuit 1508. The baseband signal can be provided by the baseband circuit 1504 and can be filtered by the filter circuit 1506c.

[0197] In some embodiments, the mixer circuit 1506a for the receiving signal path and the mixer circuit 1506a for the transmitting signal path may include two or more mixers and may be arranged for quadrature downconversion and / or upconversion, respectively.

[0198] In some embodiments, the mixer circuit 1506a for the receive signal path and the mixer circuit 1506a for the transmit signal path may include two or more mixers and may be arranged for image suppression (e.g., Hartley image suppression). In some embodiments, the mixer circuit 1506a for the receive signal path and the mixer circuit 1506a for the transmit signal path may be arranged for direct downconversion and / or direct upconversion, respectively. In some embodiments, the mixer circuit 1506a for the receive signal path and the mixer circuit 1506a for the transmit signal path may be configured for superheterodyne operation.

[0199] In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, but the scope of the embodiments is not limited in this respect. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, the RF circuit 1506 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry, and the baseband circuit 1504 may include a digital baseband interface for communicating with the RF circuit 1506.

[0200] In some dual-mode embodiments, separate radio IC circuitry may be provided to process signals for each spectrum, but the scope of the embodiments is not limited in this respect.

[0201] In some embodiments, synthesizer circuit 1506d may be a fractional N-type synthesizer or a fractional N / N+1-type synthesizer, but the scope of the embodiments is not limited in this respect, as other types of frequency synthesizers may be suitable. For example, synthesizer circuit 1506d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

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

[0203] In some embodiments, the frequency input may be provided by a voltage-controlled oscillator (VCO), but this is not required. The divider control input may be provided by the baseband circuit 1504 or the application processor 1502 according to the desired output frequency. In some embodiments, the divider control input (e.g., N) may be determined from a lookup table based on the channel indicated by the application processor 1502.

[0204] The synthesizer circuit 1506d of the RF circuit 1506 may include a frequency divider, a delay-locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the frequency divider may be a dual-mode divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by N or N+1 (e.g., based on carry output) to provide a fractional division ratio. In some example embodiments, the DLL may include a set of cascaded tunable delay elements, a phase detector, a charge pump, and a D-type flip-flop. In these embodiments, the delay elements may be configured to decompose the VCO cycle into at most Nd equal phase groups, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[0205] In some embodiments, synthesizer circuitry 1506d may be configured to generate a carrier frequency as an output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and frequency divider circuitry to generate multiple signals having multiple phases of each other at the carrier frequency. In some embodiments, the output frequency may be the LO frequency (fLO). In some embodiments, RF circuitry 1506 may include an IQ / polarity converter.

[0206] FEM circuit 1508 may include a receive signal path, which may include circuitry configured to operate RF signals received from one or more antennas 1510, amplify the received signals, and provide an amplified version of the received signals to RF circuit 1506 for further processing. FEM circuit 1508 may also include a transmit signal path, which may include circuitry configured to amplify signals provided by RF circuit 1506 for transmission by one or more antennas of the one or more antennas 1510. In various embodiments, amplification via the transmit or receive signal path may be performed only in RF circuit 1506, only in FEM 1508, or both in RF circuit 1506 and FEM 1508.

[0207] In some embodiments, FEM circuit 1508 may include a TX / RX switch to switch between transmit and receive mode operation. The FEM circuit may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit may include a low-noise amplifier (LNA) to amplify the received RF signal and provide the amplified received RF signal as an output (e.g., to RF circuit 1506). The transmit signal path of FEM circuit 1508 may include a power amplifier (PA) for amplifying (e.g., provided by RF circuit 1506) the input RF signal and one or more filters for generating RF signals for subsequent transmission (e.g., via one or more antennas in one or more antennas 1510).

[0208] In some embodiments, the PMC 1512 can manage the power supplied to the baseband circuitry 1504. Specifically, the PMC 1512 can control power selection, voltage scaling, battery charging, or DC-DC conversion. The PMC 1512 is typically included when the device 1500 can be powered by a battery, for example, when the device is included in a UE. The PMC 1512 can improve power conversion efficiency while providing the desired implementation size and thermal characteristics.

[0209] Although Figure 15 The diagram shows that the PMC 1512 is coupled only to the baseband circuit 1504. However, in other embodiments, the PMC 1512 may additionally or alternatively be coupled to other components and perform similar power management operations on other components, such as, but not limited to, the application circuit 1502, the RF circuit 1506, or the FEM 1508.

[0210] In some embodiments, PMC 1512 can control various power-saving mechanisms of device 1500, or otherwise become part of various power-saving mechanisms of device 1500. For example, if device 1500 is in the RRC_Connected state, in which device 1500 remains connected to the RAN node when it anticipates receiving traffic soon, it may then enter a state known as Discontinuous Receive Mode (DRX) after a period of inactivity. During this state, device 1500 can power down for short intervals to save power.

[0211] If there is no data service activity during the extended period, device 1500 can transition to the RRC_Idle state. In this state, device 1500 disconnects from the network and does not perform operations such as channel quality feedback or handover. Device 1500 enters a very low-power state and performs paging, during which it periodically wakes up again to listen to the network and then powers off again. Device 1500 can not receive data in this state; to receive data, it can transition back to the RRC_Connected state.

[0212] An additional power-saving mode allows the device to be unavailable to the network for periods longer than the paging interval (ranging from seconds to hours). During this time, the device has no network access whatsoever and may lose power completely. Any data sent during this period will incur significant latency, and this is assumed to be acceptable.

[0213] The processors of application circuit 1502 and baseband circuit 1504 can be used to execute elements of one or more instances of the protocol stack. For example, the processor of baseband circuit 1504 (alone or in combination) can be used to execute layer 3, layer 2, or layer 1 functions, while the processor of application circuit 1504 can utilize data received from these layers (e.g., packet data) and further execute layer 4 functions (e.g., Transport Communication Protocol (TCP) and User Datagram Protocol (UDP) layers). As mentioned herein, layer 3 may include the RRC layer. As mentioned herein, layer 2 may include the Media Access Control (MAC) layer, the Radio Link Control (RLC) layer, and the Packet Data Convergence Protocol (PDCP) layer. As mentioned herein, layer 1 may include the physical (PHY) layer of the UE / RAN node.

[0214] Figure 16Examples of infrastructure device 1600 according to various embodiments are shown. Infrastructure device 1600 (or “system 1600”) may be implemented as a base station, radio headend, RAN node, etc., such as RAN nodes 111 and 112 and / or AP 106 previously shown and described. In other examples, system 1600 may be implemented in or by a UE, one or more application servers 130 and / or any other element / device discussed herein. System 1600 may include one or more of the following: application circuitry 1605, baseband circuitry 1610, one or more radio headend modules 1615, memory 1620, power management integrated circuit (PMIC) 1625, power tee circuitry 1630, network controller 1635, network interface connector 1640, satellite positioning circuitry 1645, and user interface 1650. In some embodiments, device 1600 may include additional elements such as memory / storage devices, displays, cameras, sensors, or input / output (I / O) interface elements. In other embodiments, the components described below may be included in more than one device (e.g., for a cloud RAN (C-RAN) implementation, the circuitry may be separately included in more than one device).

[0215] For the purposes of this document, the term "circuit" can refer to, be part of, or include hardware components configured to provide the described functions, such as: electronic circuitry, logic circuitry, processors (shared, dedicated, or grouped) and / or memories (shared, dedicated, or grouped), application-specific integrated circuits (ASICs), field-programmable devices (fFPDs) (e.g., field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), structured ASICs, or programmable system-on-chips (SoCs)), digital signal processors (DSPs), and the like. In some embodiments, a circuit may execute one or more software or firmware programs to provide at least some of the described functions. Furthermore, the term "circuit" can also refer to a combination of one or more hardware elements (or circuitry used in an electrical or electronic system) and program code for performing the functions of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuit.

[0216] The terms “application circuit” and / or “baseband circuit” may be considered synonymous with “processor circuit” and may be referred to as “processor circuit”. For the purposes of this document, the term “processor circuit” may refer to, be part of, or include circuits capable of sequentially and automatically performing a sequence of arithmetic or logical operations; and recording, storing, and / or transmitting digital data. The term “processor circuit” may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and / or any other device capable of executing or otherwise operating computer-executable instructions such as program code, software modules, and / or functional processes.

[0217] Furthermore, various components of the core network 120 (or CN 120 as previously discussed) may be referred to as “network elements”. The term “network element” can describe physical or virtualized devices used to provide wired or wireless communication network services. The term “network element” may be considered synonymous with and / or referred to as the following terms: networked computer, network hardware, network device, network node, router, switch, hub, bridge, radio network controller, radio access network device, gateway, server, virtualized network function (VNF), network function virtualization infrastructure (NFVI), etc.

[0218] Application circuitry 1605 may include one or more central processing unit (CPU) cores and one or more of the following: cache memory, low-dropout (LDO) regulator, interrupt controller, serial interface such as SPI, I2C, or a general-purpose programmable serial interface module, real-time clock (RTC), timer-counter including interval and watchdog timers, general-purpose input / output (I / O or IO), memory card controller such as a secure digital card (SD) / multimedia card (MMC), universal serial bus (USB) interface, mobile industrial processor interface (MIPI) interface, and Joint Test Access Group (JTAG) test access port. As an example, application circuitry 1605 may include one or more Intel... or Processor; Advanced Micro Devices (AMD) Processor, Accelerated Processing Unit (APU) or Processor; etc. In some embodiments, system 1600 may not utilize application circuitry 1605, but may instead include, for example, a dedicated processor / controller to process IP data received from EPC or 5GC.

[0219] Additionally or alternatively, application circuitry 1605 may include circuitry such as, but not limited to, the following: one or more field-programmable devices (FPDs), such as field-programmable gate arrays (FPGAs); programmable logic devices (PLDs), such as complex PLDs (CPLDs), high-capacity PLDs (HCPLDs); ASICs, such as structured ASICs; programmable SoCs (PSoCs); and so on. In this embodiment, the circuitry of application circuitry 1605 may include logic blocks or logic architectures, including other interconnected resources, which may be programmed to perform various functions, such as the processes, methods, functions, etc., of the various embodiments discussed herein. In this embodiment, the circuitry of application circuitry 1605 may include memory cells (e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), antifuse, etc.) for storing logic blocks, logic architectures, data, etc., in lookup tables (LUTs), and so on.

[0220] The baseband circuit 1610 may be implemented, for example, as a soldered substrate including one or more integrated circuits, a single-package integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more integrated circuits. Although not shown, the baseband circuit 1610 may include one or more digital baseband systems that may be coupled to a CPU subsystem, an audio subsystem, and an interface subsystem via interconnect subsystems. The digital baseband subsystems may also be coupled to a digital baseband interface and a mixed-signal baseband subsystem via additional interconnect subsystems. Each interconnect subsystem may include a bus system, a point-to-point connection, a network-on-chip (NOC) architecture, and / or some other suitable bus or interconnect technology, such as those discussed herein. The audio subsystem may include digital signal processing circuitry, buffer memory, program memory, voice processing accelerator circuitry, data converter circuitry such as analog-to-digital and digital-to-analog converter circuitry, analog circuitry including one or more amplifiers and filters, and / or other similar components. In one aspect of this disclosure, the baseband circuit 1610 may include protocol processing circuitry having one or more instances of control circuitry (not shown) to provide control functions for the digital baseband circuitry and / or radio frequency circuitry (e.g., radio front-end module 1615).

[0221] User interface circuitry 1650 may include one or more user interfaces designed to enable interaction with a user of system 1600, or peripheral component interfaces designed to enable interaction with peripheral components of system 1600. User interfaces may include, but are not limited to, one or more physical or virtual buttons (e.g., a reset button), one or more indicators (e.g., light-emitting diodes (LEDs)), a physical keyboard or keypad, a mouse, a touchpad, a touchscreen, a speaker or other audio emitting device, a microphone, a printer, a scanner, headphones, a display screen or display device, and so on. Peripheral component interfaces may include, but are not limited to, non-volatile memory ports, universal serial bus (USB) ports, audio jacks, power supply interfaces, and so on.

[0222] The Radio Front-End Module (RFEM) 1615 may include a millimeter-wave RFEM and one or more submillimeter-wave radio frequency integrated circuits (RFICs). In some implementations, the one or more submillimeter-wave RFICs may be physically separated from the millimeter-wave RFEM. The RFIC may include connections to one or more antennas or antenna arrays, and the RFEM may be connected to multiple antennas. In alternative implementations, both millimeter-wave and submillimeter-wave radio functions may be implemented in the same physical Radio Front-End Module 1615. The RFEM 1615 may contain both millimeter-wave and submillimeter-wave antennas.

[0223] The memory circuitry 1620 may include one or more of the following: volatile memory, including dynamic random access memory (DRAM) and / or synchronous dynamic random access memory (SDRAM); and non-volatile memory (NVM), including high-speed electrically erasable memory (commonly referred to as flash memory), phase-change random access memory (PRAM), magnetoresistive random access memory (MRAM), etc., and may contain information from… and A three-dimensional (3D) XPOINT memory. The memory circuit 1620 can be implemented as one or more of a solder-in packaged integrated circuit, a socket-type memory module, and an insertable memory card.

[0224] The PMIC 1625 may include a voltage regulator, surge protector, power alarm detection circuitry, and one or more backup power sources such as batteries or capacitors. The power alarm detection circuitry can detect one or more of a power outage (undervoltage) and a power surge (overvoltage) condition. The power tee circuit 1630 can provide power drawn from the network cable to supply both power and data connectivity to the infrastructure equipment 1600 via a single cable.

[0225] Network controller circuitry 1635 can provide connectivity to a network using standard network interface protocols such as Ethernet, GRE-tunneled Ethernet, Multiprotocol Label Switching (MPLS)-based Ethernet, or some other suitable protocol. Network connectivity to / from infrastructure device 1600 can be provided via a physical connection through network interface connector 1640, which can be electrical (typically referred to as a "copper interconnect"), optical, or wireless. Network controller circuitry 1635 may include one or more dedicated processors and / or FPGAs to communicate using one or more of the aforementioned protocols. In some implementations, network controller circuitry 1635 may include multiple controllers to provide connectivity to other networks using the same or different protocols.

[0226] Positioning circuit 1645 may include circuitry for receiving and decoding signals transmitted by one or more navigation satellite constellations of a Global Navigation Satellite System (GNSS). Examples of navigation satellite constellations (or GNSS) may include the U.S. Global Positioning System (GPS), Russia's GLONASS, the European Union's Galileo system, China's BeiDou Navigation Satellite System, regional navigation systems, or GNSS augmentation systems (e.g., India's NAVIC, Japan's QZSS, France's DORIS, etc.), and so on. Positioning circuit 1645 may include various hardware components (e.g., hardware devices such as switches, filters, amplifiers, antenna elements, etc., to facilitate communication over-the-air (OTA) communication) to communicate with components of the positioning network (e.g., navigation satellite constellation nodes).

[0227] Nodes or satellites of one or more navigation satellite constellations (“GNSS nodes”) provide positioning services by continuously transmitting or broadcasting GNSS signals along the line of sight. These GNSS signals can be used by GNSS receivers (e.g., positioning circuitry 1645 and / or positioning circuitry implemented by UEs 101, 102, etc.) to determine their GNSS positions. GNSS signals may include pseudo-random codes (e.g., sequences of ones and zeros) known to the GNSS receiver and a message including the transmission time (ToT) of the code epoch (e.g., a defined point in the pseudo-random code sequence) and the GNSS node position at the ToT. The GNSS receiver can monitor / measure GNSS signals transmitted / broadcast by multiple GNSS nodes (e.g., four or more satellites) and solve various equations to determine the corresponding GNSS positions (e.g., spatial coordinates). The GNSS receiver also implements a clock that is typically not as stable and accurate as the atomic clocks of the GNSS nodes, and can use the measured GNSS signals to determine the GNSS receiver's deviation from real time (e.g., the deviation of the GNSS receiver clock from the GNSS node time). In some embodiments, the positioning circuit 1645 may include a micro-PNT IC for positioning, navigation, and timing, which uses a master timing clock to perform position tracking / estimation without GNSS assistance.

[0228] A GNSS receiver can measure the time of arrival (ToA) of GNSS signals from multiple GNSS nodes according to its own clock. The GNSS receiver can determine the time of flight (ToF) value for each received GNSS signal based on the ToA and ToT, and then determine the three-dimensional (3D) position and clock offset based on the ToF. The 3D position can then be converted into latitude, longitude, and altitude. Positioning circuitry 1645 can provide data to application circuitry 1605, which may include one or more of position data or time data. Application circuitry 1605 can use the time data to synchronize its operation with other radio base stations (e.g., RAN nodes 111, 112, etc.).

[0229] Figure 16The components shown can communicate with each other using interface circuitry. For the purposes of this document, the term "interface circuitry" can refer to, be part of, or include circuitry that enables the exchange of information between two or more components or devices. The term "interface circuitry" can refer to one or more hardware interfaces, such as a bus, input / output (I / O) interface, peripheral component interface, network interface card, etc. Any suitable bus technology can be used in various implementations, including any number of technologies such as Industry Standard Architecture (ISA), Extended ISA (EISA), Peripheral Component Interconnect (PCI), Extended Peripheral Component Interconnect (PCIx), Fast PCI (PCI express, PCIe), or any number of other technologies. The bus can be, for example, a proprietary bus used in a SoC-based system. Other bus systems can be included, such as I2C interfaces, SPI interfaces, point-to-point interfaces, and power buses, etc.

[0230] Figure 17 This is a block diagram illustrating components capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more methods discussed herein, according to some example embodiments. Specifically, Figure 17 A schematic representation of hardware resource 1700 is shown, which includes one or more processors (or processor cores) 1710, one or more memory / storage devices 1720, and one or more communication resources 1730, each of which can be communicatively coupled via bus 1740. Hardware resource 1700 may be part of a UE, AN, or LMF. For embodiments utilizing node virtualization (e.g., NFV), a hypervisor 1702 may be executed to provide an execution environment for one or more network slices / subslices to utilize hardware resource 1700.

[0231] Processor 1710 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP) such as a baseband processor, an application-specific integrated circuit (ASIC), a radio frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, processor 1712 and processor 1714.

[0232] The memory / storage device 1720 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 1720 may include, but is not limited to, any type of volatile or non-volatile memory, such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state storage devices, etc.

[0233] Communication resource 1730 may include interconnect or network interface components or other suitable devices for communicating with one or more peripheral devices 1704 or one or more databases 1706 via network 1708. For example, communication resource 1730 may include wired communication components (e.g., for coupling via Universal Serial Bus (USB)), cellular communication components, NFC components, Bluetooth components (e.g., Bluetooth Low Energy), Wi-Fi components, and other communication components.

[0234] Instruction 1750 may include software, a program, application, applet, app, or other executable code for causing at least any processor 1710 to perform any one or more of the methods discussed herein. Instruction 1750 may reside wholly or partially within processor 1710 (e.g., within the processor's cache memory), memory / storage device 1720, or any suitable combination thereof. Furthermore, any portion of instruction 1750 may be transferred from any combination of peripheral device 1704 or database 1706 to hardware resource 1700. Therefore, the memory of processor 1710, memory / storage device 1720, peripheral device 1704, and database 1706 are examples of computer-readable and machine-readable media.

[0235] The following paragraphs describe examples of various embodiments.

[0236] Example I-1 includes an apparatus for edge application server (EAS) discovery based on a directory name system (DNS) checker, comprising: interface circuitry; and processing circuitry coupled to the interface circuitry, the processing circuitry being configured to: modify the uplink classifier / branch point (UL) from the user plane function (UPF) in such a way as... The CL / BP receives a DNS request from a User Equipment (UE): modifies the destination Internet Protocol (IP) address of the DNS request to the IP address of the Local DNS (L-DNS) and stores the destination IP address of the DNS request for subsequent processing; modifies the source IP address of the DNS request to the IP address of the DNS checker and stores the source IP address of the DNS request for subsequent processing, wherein the destination IP address of the DNS request corresponds to the default DNS server, and the source IP address of the DNS request corresponds to the IP address of the UE; forwards the modified DNS request to the L-DNS via the interface circuit; based on the DNS response from the L-DNS, determines whether the fully qualified domain name (FQDN) of the EAS specified in the DNS request has been resolved; when the FQDN is determined to be resolved to the IP address of the EAS: replaces the source IP address and destination IP address of the DNS response with the stored destination IP address and source IP address of the DNS request, respectively, and forwards the DNS response to the UL of the UPF. CL / BP; and when the FQDN is determined to be unresolved, the DNS request initially received from the UL CL / BP of the UPF is forwarded back to the UL CL / BP of the UPF.

[0237] Example I-2 includes the apparatus of Example I-1, wherein the IP address of the EAS includes the IP address of a local EAS or the IP address of a cloud EAS.

[0238] Example I-3 includes the apparatus of Example I-1 or I-2, wherein, before modifying the DNS request, the processing circuitry is configured to determine that the FQDN of the EAS specified in the DNS request is related to an application in which the EAS is not deployed in the local data network (DN), and return the DNS request to the UPF.

[0239] Example I-4 includes the apparatus of any one of Examples I-1 to I-3, wherein the DNS checker is a logical function located in the UPF.

[0240] Example I-5 includes an apparatus of any of Examples I-1 to I-3, wherein the DNS checker is a logical function located in a Session Management Function (SMF) or a Local Data Network (DN).

[0241] Example I-6 includes the apparatus of any of Examples I-1 to I-3, wherein the DNS checker is a standalone entity.

[0242] Example I-7 includes an apparatus for a fifth-generation system (5GS), comprising: an interface circuit; and a processing circuit coupled to the interface circuit, the processing circuit being configured to: forward a Directory Name System (DNS) request from a user equipment (UE) to a DNS checker via the interface circuit; and process a DNS response or the DNS request received from the DNS checker via the interface circuit.

[0243] Example I-8 includes the apparatus of Example I-7, wherein the DNS response includes the IP address of the local edge application server (EAS) or the IP address of the cloud EAS.

[0244] Example I-9 includes the apparatus of Example I-7, wherein the processing circuitry, after receiving the DNS response from the DNS checker, forwards the DNS response to the UE via the N3 interface.

[0245] Example I-10 includes the apparatus of Example I-7, wherein the processing circuitry forwards the DNS request from the DNS checker to the Protocol Data Unit Session Anchor (PSA) via the N9 interface.

[0246] Example I-11 includes the apparatus of Example I-7, wherein the processing circuitry forwards the DNS request based on an uplink classifier (UL CL) rule that detects the destination port number 53.

[0247] Example I-12 includes the means of any one of Examples I-7 to I-11, wherein the means is part of the User Plane Function (UPF).

[0248] Example I-13 includes an apparatus for a fifth-generation system (5GS), comprising: an interface circuit; and a processing circuit coupled to the interface circuit, the processing circuit being configured to: process a DNS request received from a user equipment (UE) via the interface circuit from a directory name system (DNS) checker; determine whether a local DNS (L-DNS) can resolve the fully qualified domain name (FQDN) of an edge application server (EAS) specified in the DNS request; if the L-DNS can resolve the FQDN of the EAS, respond to the DNS checker with a DNS response including the expected Internet Protocol (IP) address of the local EAS (L-EAS); if the L-DNS cannot resolve the FQDN... To resolve the FQDN of the EAS, determine whether the L-DNS is connected to the Cloud DNS (C-DNS): If the L-DNS is not connected to the C-DNS, respond to the DNS checker with a DNS response that does not include the IP address of the EAS or has an indication that the L-DNS cannot resolve the FQDN of the EAS; or if the L-DNS is connected to the C-DNS, communicate with the C-DNS to recursively resolve the FQDN of the EAS, receive the IP address of the cloud EAS from the C-DNS, and respond to the DNS checker with a DNS response that includes the IP address of the cloud EAS.

[0249] Example I-14 includes the apparatus of Example I-13, wherein, if the DNS checker resides in the Session Management Function (SMF) or a separate entity in the 5G Core (5GC), the processing circuitry is configured to forward the DNS response via the uplink classifier / branch point (UL CL / BP) of the User Plane Function (UPF) using downlink (DL) classifier rules, the DL classifier rules detecting the address of the DNS checker as the destination IP address.

[0250] Example I-15 includes the apparatus of Example I-13 or I-14, wherein the apparatus is part of the L-DNS.

[0251] Example I-16 includes a non-transitory computer-readable storage medium storing instructions that, when executed by the processing circuitry of a device, cause the device to perform operations for edge application server (EAS) discovery based on a directory name system (DNS) checker, the operations including: modifying the uplink classifier / branch point (UL) from the user plane function (UPF) in such a way as... The CL / BP receives a DNS request from a User Equipment (UE): modifies the destination Internet Protocol (IP) address of the DNS request to the IP address of the local DNS (L-DNS) and stores the destination IP address of the DNS request for subsequent processing; modifies the source IP address of the DNS request to the IP address of the DNS checker and stores the source IP address of the DNS request for subsequent processing, wherein the destination IP address of the DNS request corresponds to the default DNS server, and the source IP address of the DNS request corresponds to the IP address of the UE; forwards the modified DNS request to the L-DNS; based on the DNS response from the L-DNS, determines whether the fully qualified domain name (FQDN) of the EAS specified in the DNS request has been resolved; when the FQDN is determined to be resolved to the IP address of the EAS: replaces the source IP address and destination IP address of the DNS response with the stored destination IP address and source IP address of the DNS request, respectively, and forwards the DNS response to the UL of the UPF. CL / BP; and when the FQDN is determined to be unresolved, the DNS request initially received from the UL CL / BP of the UPF is forwarded back to the UL CL / BP of the UPF.

[0252] Example I-17 includes the non-transitory computer-readable storage medium of Example I-16, wherein the IP address of the EAS includes the IP address of a local EAS or the IP address of a cloud EAS.

[0253] Example I-18 includes the non-transitory computer-readable storage medium of Example I-16 or I-17, wherein the operation includes: determining, before modifying the DNS request, that the FQDN of the EAS specified in the DNS request relates to an application in which the EAS is not deployed in the local data network (DN), and returning the DNS request to the UPF.

[0254] Example I-19 includes a nontransitory computer-readable storage medium of any of Examples I-16 to I-18, wherein the DNS checker is a logical function located in the UPF.

[0255] Example I-20 includes a nontransitory computer-readable storage medium of any of Examples I-16 to I-18, wherein the DNS checker is a logical function located in a Session Management Function (SMF) or a Local Data Network (DN).

[0256] Example I-21 includes a nontransitory computer-readable storage medium of any of Examples I-16 to I-18, wherein the DNS checker is a standalone entity.

[0257] Example I-22 includes a non-transitory computer-readable storage medium storing instructions that, when executed by processing circuitry of a User Plane Function (UPF) in a fifth-generation system (5GS), cause the UPF to perform operations for discovery by an Edge Application Server (EAS) based on a Directory Name System (DNS) checker, the operations including: forwarding a Directory Name System (DNS) request from a User Equipment (UE) to the DNS checker; and processing a DNS response or the DNS request received from the DNS checker.

[0258] Example I-23 includes the non-transitory computer-readable storage medium of Example I-22, wherein the DNS response includes the IP address of a local edge application server (EAS) or a cloud EAS.

[0259] Example I-24 includes the non-transitory computer-readable storage medium of Example I-22, wherein the operation further includes: after receiving the DNS response from the DNS checker, forwarding the DNS response to the UE via the N3 interface.

[0260] Example I-25 includes the non-transitory computer-readable storage medium of Example I-22, wherein the operation further includes: forwarding the DNS request from the DNS checker to the Protocol Data Unit Session Anchor (PSA) via the N9 interface.

[0261] Example I-26 includes the non-transitory computer-readable storage medium of Example I-22, wherein the operation further includes: forwarding the DNS request based on an uplink classifier (UL CL) rule, the UL CL rule detecting the destination port number 53.

[0262] Example I-27 includes a non-transitory computer-readable storage medium storing instructions that, when executed by processing circuitry of a Local Directory Name System (L-DNS) in a fifth-generation system (5GS), cause the L-DNS to perform operations for Edge Application Server (EAS) discovery based on a Directory Name System (DNS) checker. The operations include: processing a DNS request from a User Equipment (UE) received from the Directory Name System (DNS) checker; determining whether the Local DNS (L-DNS) can resolve the fully qualified domain name (FQDN) of the Edge Application Server (EAS) specified in the DNS request; and, if the L-DNS can resolve the FQDN of the EAS, responding to the DNS checker with a DNS response including the expected Local EAS (L-DNS) domain name. The L-DNS retrieves the Internet Protocol (IP) address of the EAS; if the L-DNS cannot resolve the FQDN of the EAS, it determines whether the L-DNS is connected to the Cloud DNS (C-DNS): when the L-DNS is not connected to the C-DNS, it responds to the DNS checker with a DNS response that does not include the IP address of the EAS or has an indication that the L-DNS cannot resolve the FQDN of the EAS; or when the L-DNS is connected to the C-DNS, it communicates with the C-DNS to recursively resolve the FQDN of the EAS, receives the IP address of the cloud EAS from the C-DNS, and responds to the DNS checker with a DNS response that includes the IP address of the cloud EAS.

[0263] Example I-28 includes the non-transitory computer-readable storage medium of Example I-27, wherein, if the DNS checker resides in a Session Management Function (SMF) or a standalone entity in the 5G Core (5GC), the operation further includes: forwarding the DNS response via an uplink classifier / branch point (UL CL / BP) of the User Plane Function (UPF) using downlink (DL) classifier rules, the DL classifier rules detecting the address of the DNS checker as the destination IP address.

[0264] Example I-29 includes a method for edge application server (EAS) discovery based on a directory name system (DNS) checker, comprising: modifying a DNS request received from a user equipment (UE) at an uplink classifier / branch point (ULCL / BP) of a user plane function (UPF) by: modifying the destination Internet Protocol (IP) address of the DNS request to the IP address of a local DNS (L-DNS) and storing the destination IP address of the DNS request for subsequent processing; and modifying the source IP address of the DNS request to the IP address of the DNS checker and storing the source IP address of the DNS request for subsequent processing. Wherein, the destination IP address of the DNS request corresponds to the default DNS server, and the source IP address of the DNS request corresponds to the IP address of the UE; the modified DNS request is forwarded to the L-DNS; based on the DNS response from the L-DNS, it is determined whether the fully qualified domain name (FQDN) of the EAS specified in the DNS request has been resolved; when the FQDN is determined to be resolved to the IP address of the EAS: the source IP address and destination IP address of the DNS response are replaced with the stored destination IP address and source IP address of the DNS request, respectively, and the DNS response is forwarded to the UL CL / BP of the UPF; and when the FQDN is determined to be unresolved, the DNS request initially received from the UL CL / BP of the UPF is forwarded back to the UL CL / BP of the UPF.

[0265] Example I-30 includes the method of Example I-29, wherein the IP address of the EAS includes the IP address of a local EAS or the IP address of a cloud EAS.

[0266] Example I-31 includes the method of Example I-29 or I-30, further comprising: determining, before modifying the DNS request, that the FQDN of the EAS specified in the DNS request is related to an application in which the EAS is not deployed in the local data network (DN), and returning the DNS request to the UPF.

[0267] Example I-32 includes the method of any one of Examples I-29 to I-31, wherein the DNS checker is a logical function located in the UPF.

[0268] Example I-33 includes the method of any of Examples I-29 to I-31, wherein the DNS checker is a logical function located in a Session Management Function (SMF) or a Local Data Network (DN).

[0269] Example I-34 includes the method of any of Examples I-29 to I-31, wherein the DNS checker is a standalone entity.

[0270] Example I-35 includes a device for edge application server (EAS) discovery based on a directory name system (DNS) checker, including means for performing the method of any of Examples I-29 to I-34.

[0271] Example I-36 includes a method performed by a User Plane Function (UPF) in a fifth-generation system (5GS), comprising: forwarding a Directory Name System (DNS) request from a User Equipment (UE) to a DNS checker; and processing a DNS response or the DNS request received from the DNS checker.

[0272] Example I-37 includes the method of Example I-36, wherein the DNS response includes the IP address of the local edge application server (EAS) or the IP address of the cloud EAS.

[0273] Example I-38 includes the method of Example I-36, and further includes: after receiving the DNS response from the DNS checker, forwarding the DNS response to the UE via the N3 interface.

[0274] Example I-39 includes the method of Example I-36, and further includes: forwarding the DNS request from the DNS checker to a Protocol Data Unit Session Anchor (PSA) via the N9 interface.

[0275] Example I-40 includes the method of Example I-36, and further includes: forwarding the DNS request based on an uplink classifier (UL CL) rule, the UL CL rule detecting the destination port number 53.

[0276] Example I-41 includes an apparatus for edge application server (EAS) discovery based on a directory name system (DNS) checker, including means for performing the method of any of Examples I-36 to I-40.

[0277] Example I-42 includes a method performed by a local directory name system (L-DNS) in a fifth-generation system (5GS), comprising: processing a DNS request from a user equipment (UE) received from a directory name system (DNS) checker; determining whether the local DNS (L-DNS) can resolve a fully qualified domain name (FQDN) of an edge application server (EAS) specified in the DNS request; if the L-DNS can resolve the FQDN of the EAS, responding to the DNS checker with a DNS response including an expected Internet Protocol (IP) address of the local EAS (L-EAS); if the L-DNS cannot resolve the FQDN of the EAS... If the FQDN is not connected to the C-DNS, the L-DNS is then used to determine whether it is connected to the C-DNS: when the L-DNS is not connected to the C-DNS, it responds to the DNS checker with a DNS response that does not include the IP address of the EAS or has an indication that the L-DNS cannot resolve the FQDN of the EAS; or when the L-DNS is connected to the C-DNS, it communicates with the C-DNS to recursively resolve the FQDN of the EAS, receives the IP address of the cloud EAS from the C-DNS, and responds to the DNS checker with a DNS response that includes the IP address of the cloud EAS.

[0278] Example I-43 includes the method of Example I-42, wherein if the DNS checker resides in the Session Management Function (SMF) or a separate entity in the 5G Core (5GC), the method further includes: forwarding the DNS response via an uplink classifier / branch point (UL CL / BP) of the User Plane Function (UPF) using downlink (DL) classifier rules, the DL classifier rules detecting the address of the DNS checker as the destination IP address.

[0279] Example I-44 includes a device for edge application server (EAS) discovery based on a directory name system (DNS) checker, including means for performing the methods of Example I-42 or I-43.

[0280] Example I-45 includes a communication system comprising: means of any one of Examples I-1 to I-6, means of any one of Examples I-7 to I-12, and means of any one of Examples I-13 to I-15.

[0281] Example II-1 includes an apparatus for configuring UE-UE relay operation in a fifth-generation system (5GS), comprising: an interface circuit; and a processing circuit coupled to the interface circuit, the processing circuit being configured to: process a registration request message received via the interface circuit from a user equipment (UE), the registration request message including information indicating the UE's fifth-generation (5G) proximity-based service (ProSe) UE-UE relay capability and / or 5G ProSe UE-UE relay access capability; select a policy control function (PCF) supporting 5G ProSe information configuration for the UE; and establish a UE policy association with the PCF for 5G ProSe UE-UE relay information configuration delivery and / or 5G ProSe UE-UE relay access information configuration delivery.

[0282] Example II-2 includes the apparatus of Example II-1, wherein the processing circuitry is further configured to report the UE's 5G ProSe UE-to-UE relay capability and / or 5G ProSe UE-to-UE relay access capability to the selected PCF, such that the selected PCF can determine 5G ProSe UE-to-UE relay information for the UE based on the UE's 5G ProSe UE-to-UE relay capability and / or determine 5G ProSe UE-to-UE relay access information for the UE based on the UE's 5G ProSe UE-to-UE relay access capability.

[0283] Example II-3 includes the apparatus of Example II-1, wherein the processing circuitry is further configured to process a UE policy container received via the interface circuitry, the UE policy container including information for instructing the UE to make a 5G ProSe UE-to-UE relay information configuration request and / or a 5G ProSe UE-to-UE relay access information configuration request.

[0284] Example II-4 includes the apparatus of Example II-3, wherein the processing circuitry is further configured to report the UE's 5G ProSe UE-to-UE relay information configuration request and / or 5G ProSe UE-to-UE relay access information configuration request to the selected PCF, so that the selected PCF can determine whether to configure the 5G ProSe UE-to-UE relay information and / or the 5G ProSe UE-to-UE relay access information to the UE.

[0285] Example II-5 includes the apparatus of Example II-4, wherein the processing circuitry is further configured to: process a message received from the selected PCF, the message instructing the selected PCF to determine to configure the 5G ProSe UE-to-UE relay information and / or the 5G ProSe UE-to-UE relay access information to the UE; and deliver the 5G ProSe UE-to-UE relay information and / or the 5G ProSe UE-to-UE relay access information to the UE.

[0286] Example II-6 includes the apparatus of Example II-5, wherein the 5G ProSe UE-to-UE relay information and / or the 5G ProSe UE-to-UE relay access information of the UE will be updated when at least one of the following conditions occurs: the UE moves from one Public Land Mobile Network (PLMN) to another PLMN; there is a subscription change in the list of PLMNs in which the UE is authorized to perform 5G ProSe UE-to-UE relay operations; or there is a change in service-specific parameters.

[0287] Example II-7 includes the apparatus of Example II-6, wherein when a PLMN that is providing services is removed from the list of PLMNs in the service authorization parameters, the processing circuitry is further configured to: revoke the service authorization from the UE.

[0288] Example II-8 includes the apparatus of Example II-6, wherein the 5G ProSe UE-to-UE relay information and / or the 5G ProSe UE-to-UE relay access information of the UE are updated when the UE's roaming causes a subscription change.

[0289] Example II-9 includes the apparatus of Example II-5, wherein the processing circuitry is further configured to process a UE policy configuration request received from the UE when the UE determines that either the 5GProSe UE-to-UE relay information and / or the 5G ProSe UE-to-UE relay access information is invalid.

[0290] Example II-10 includes the apparatus of Example II-5, wherein the 5G ProSe UE-to-UE relay information includes one or more of the following: an authorization policy for acting as a 5G ProSe UE-to-UE relay; a 5G ProSe relay discovery policy / parameters for the 5G ProSe UE-to-UE relay; radio parameters for 5G ProSe relay discovery; radio parameters for 5G ProSe relay communication; a mapping rule between 5G ProSe PC5 5QI and Uu 5QI values; and / or a mapping rule between 5G ProSe PC5 5QI and Uu QCI values.

[0291] Example II-11 includes the apparatus of Example II-10, wherein the 5G ProSe relay discovery policy / parameters for 5G ProSe UE-to-UE relays include one or more of the following: an indication for UE-to-UE relays; 5G ProSe UE-to-UE relay discovery parameters, including a user information ID and one or more relay service codes; for Layer 3 relays, protocol data unit (PDU) session parameters for relay traffic for each ProSe relay service code, including PDU session type, data network name (DNN), session and service continuity (SSC) mode, single network slice selection assistance information (S-NSSAI), and access type preference; and security-related content for 5G ProSe relay discovery for each 5G ProSe relay service code.

[0292] Example II-12 includes the apparatus of Example II-15, wherein the 5G ProSe UE-to-UE relay access information includes one or more of the following: an authorization policy for using 5G ProSe UE-to-UE relay; a policy / parameter for 5G ProSe UE-to-UE relay discovery and enabling connection to the 5G ProSe UE-to-UE relay after discovery is performed; and / or radio parameters when the UE is not served by a Next Generation Radio Access Network (NG-RAN).

[0293] Example II-13 includes the apparatus of Example II-12, wherein the policy / parameters for 5G ProSe UE-to-UE relay discovery and enabling connection to the 5G ProSe UE-to-UE relay after discovery is performed include one or more of the following: an indication to use UE-to-UE relay; 5G ProSe UE-to-UE relay discovery parameters, including user information ID and one or more relay service codes; one or more IP versions that can be used for relay traffic for each ProSe relay service code; for Layer 2 relays, Protocol Data Unit (PDU) session parameters that will be used for relay traffic for each ProSe relay service code, including PDU session type, Data Network Name (DNN), Session and Service Continuity (SSC) mode, Single Network Slice Selection Assistance Information (S-NSSAI), and Access Type Preference; and security-related content for 5G ProSe relay discovery for each 5G ProSe relay service code.

[0294] Example II-14 includes the apparatus of Example II-11 or II-13, wherein, for Model A, when the UE is announcing UE, the user information ID corresponds to the announcing party information parameter; and for Model B, when the UE is acting as a discovering UE or a discovered UE, the user information ID corresponds to the discovering party information in the request message or the discovering party information in the response message.

[0295] Example II-15 includes the apparatus of Example II-11 or II-13, wherein the one or more relay service codes include relay service codes for identifying the connectivity services that the 5G ProSe UE-to-UE relay will provide to the application.

[0296] Example II-16 includes an apparatus of any one of Examples II-1 to II-15, wherein the apparatus is part of the Access and Mobility Management Function (AMF).

[0297] Example II-17 includes an apparatus for configuring UE-UE relay operations in a fifth-generation system (5GS), comprising: an interface circuit; and a processing circuit coupled to the interface circuit, the processing circuit being configured to: process a message received via the interface circuit from an Access and Mobility Management Function (AMF), the message including information indicating a user equipment (UE)'s fifth-generation (5G) proximity-based service (ProSe) UE-UE relay capability and / or 5G ProSe UE-UE relay access capability; and determine 5G ProSe UE-UE relay information and / or 5G ProSe UE-UE relay access information for the UE based on the UE's 5G ProSe UE-UE relay capability and / or the 5G ProSe UE-UE relay access capability, respectively.

[0298] Example II-18 includes the apparatus of Example II-17, wherein the processing circuitry is further configured to determine whether to configure the 5G ProSe UE-to-UE relay information and / or the 5G ProSe UE-to-UE relay access information for the UE in response to a 5G ProSe UE-to-UE relay information configuration request and / or a 5G ProSe UE-to-UE relay access information configuration request from the UE.

[0299] Example II-19 includes the apparatus of Example II-17, wherein the processing circuitry is further configured to update the 5G ProSe UE-to-UE relay information and / or the 5G ProSe UE-to-UE relay access information of the UE when at least one of the following conditions occurs: the UE moves from one Public Land Mobile Network (PLMN) to another PLMN; there is a subscription change in the PLMN's list, and the UE is authorized to perform 5G ProSe UE-to-UE relay operations in the PLMN; or there is a change in service-specific parameters.

[0300] Example II-20 includes the apparatus of Example II-19, wherein when a PLMN that is providing services is removed from the list of PLMNs in the service authorization parameters, the processing circuitry is further configured to: revoke the service authorization from the UE.

[0301] Example II-21 includes the apparatus of Example II-19, wherein when the roaming of the UE causes a subscription change, the processing circuitry is further configured to: update the 5G ProSe UE-to-UE relay information and / or the 5G ProSe UE-to-UE relay access information of the UE.

[0302] Example II-22 includes the apparatus of Example II-17, wherein when the UE determines that either the 5G ProSe UE-to-UE relay information and / or the 5G ProSe UE-to-UE relay access information is invalid, the processing circuitry is further configured to: process a message received from the AMF via the interface circuitry, the message indicating that the UE has triggered a policy configuration process.

[0303] Example II-23 includes the apparatus of Example II-17, wherein the 5G ProSe UE-to-UE relay information includes one or more of the following: an authorization policy for acting as a 5G ProSe UE-to-UE relay; a 5G ProSe relay discovery policy / parameters for the 5G ProSe UE-to-UE relay; radio parameters for 5G ProSe relay discovery; radio parameters for 5G ProSe relay communication; a mapping rule between 5G ProSe PC5 5QI and Uu 5QI values; and / or a mapping rule between 5G ProSe PC5 5QI and Uu QCI values.

[0304] Example II-24 includes the apparatus of Example II-23, wherein the 5G ProSe relay discovery policy / parameters for 5G ProSe UE-to-UE relays include one or more of the following: an indication for UE-to-UE relays; 5G ProSe UE-to-UE relay discovery parameters, including a user information ID and one or more relay service codes; for Layer 3 relays, protocol data unit (PDU) session parameters for relay traffic for each ProSe relay service code, including PDU session type, data network name (DNN), session and service continuity (SSC) mode, single network slice selection assistance information (S-NSSAI), and access type preference; and security-related content for 5G ProSe relay discovery for each 5G ProSe relay service code.

[0305] Example II-25 includes the apparatus of Example II-17, wherein the 5G ProSe UE-to-UE relay access information includes one or more of the following: an authorization policy for using 5G ProSe UE-to-UE relay; a policy / parameter for 5G ProSe UE-to-UE relay discovery and enabling connection to the 5G ProSe UE-to-UE relay after discovery is performed; and / or radio parameters when the UE is not served by a Next Generation Radio Access Network (NG-RAN).

[0306] Example II-26 includes the apparatus of Example II-25, wherein the policy / parameters for 5G ProSe UE-to-UE relay discovery and enabling connection to the 5G ProSe UE-to-UE relay after discovery is performed include one or more of the following: an indication to use UE-to-UE relay; 5G ProSe UE-to-UE relay discovery parameters, including user information ID and one or more relay service codes; one or more IP versions that can be used for relay traffic for each ProSe relay service code; for Layer 2 relays, Protocol Data Unit (PDU) session parameters that will be used for relay traffic for each ProSe relay service code, including PDU session type, Data Network Name (DNN), Session and Service Continuity (SSC) mode, Single Network Slice Selection Assistance Information (S-NSSAI), and Access Type Preference; and security-related content for 5G ProSe relay discovery for each 5G ProSe relay service code.

[0307] Example II-27 includes the apparatus of Example II-24 or II-26, wherein, for Model A, when the UE is announcing UE, the user information ID corresponds to the announcing party information parameter; and for Model B, when the UE is acting as a discovering party UE or a discovered party UE, the user information ID corresponds to the discovering party information in the request message or the discovering party information in the response message.

[0308] Example II-28 includes the apparatus of Example II-24 or II-26, wherein the one or more relay service codes include relay service codes for identifying the connectivity services that the 5G ProSe UE-to-UE relay will provide to the application.

[0309] Example II-29 includes an apparatus of any one of Examples II-17 to II-28, wherein the apparatus is part of a policy control function (PCF).

[0310] Example II-30 includes an apparatus for a user equipment (UE) in a fifth-generation system (5GS), comprising: an interface circuit; and a processing circuit coupled to the interface circuit, the processing circuit being configured to: encode a registration request message including information indicating the UE's fifth-generation (5G) proximity-based service (ProSe) UE-to-UE relay capability and / or 5G ProSe UE-to-UE relay access capability; and provide the registration request message to the interface circuit for transmission to the Access and Mobility Management Function (AMF).

[0311] Example II-31 includes the apparatus of Example II-30, wherein the processing circuitry is further configured to: encode a UE policy container, the UE policy container including information for indicating a 5G ProSe UE-to-UE relay information configuration request and / or a 5G ProSe UE-to-UE relay access information configuration request for the UE; and provide the UE policy container to the interface circuitry for transmission to the AMF.

[0312] Example II-32 includes the apparatus of Example II-31, wherein the processing circuitry is further configured to: process 5G ProSe UE-to-UE relay information and / or 5G ProSe UE-to-UE relay access information configured by a policy control function (PCF) selected by the AMF for the UE, wherein the PCF supports 5G ProSe information configuration.

[0313] Example II-33 includes the apparatus of Example II-32, wherein the 5G ProSe UE-to-UE relay information and / or the 5G ProSe UE-to-UE relay access information of the UE will be updated when at least one of the following conditions occurs: the UE moves from one Public Land Mobile Network (PLMN) to another PLMN; there is a subscription change in the list of PLMNs in which the UE is authorized to perform 5G ProSe UE-to-UE relay operations; or there is a change in service-specific parameters.

[0314] Example II-34 includes the apparatus of Example II-32, wherein the processing circuitry is further configured to determine whether any one of the 5G ProSe UE-to-UE relay information and / or the 5G ProSe UE-to-UE relay access information is valid; and to trigger a policy configuration process when any one of the 5G ProSe UE-to-UE relay information and / or the 5G ProSe UE-to-UE relay access information is determined to be invalid.

[0315] Example II-35 includes the apparatus of Example II-32, wherein the 5G ProSe UE-to-UE relay information includes one or more of the following: an authorization policy for acting as a 5G ProSe UE-to-UE relay; a 5G ProSe relay discovery policy / parameters for the 5G ProSe UE-to-UE relay; radio parameters for 5G ProSe relay discovery; radio parameters for 5G ProSe relay communication; a mapping rule between 5G ProSe PC5 5QI and Uu 5QI values; and / or a mapping rule between 5G ProSe PC5 5QI and Uu QCI values.

[0316] Example II-36 includes the apparatus of Example II-35, wherein the 5G ProSe relay discovery policy / parameters for 5G ProSe UE-to-UE relays include one or more of the following: an indication for UE-to-UE relays; 5G ProSe UE-to-UE relay discovery parameters, including a user information ID and one or more relay service codes; for Layer 3 relays, protocol data unit (PDU) session parameters for relay traffic for each ProSe relay service code, including PDU session type, data network name (DNN), session and service continuity (SSC) mode, single network slice selection assistance information (S-NSSAI), and access type preference; and security-related content for 5G ProSe relay discovery for each 5G ProSe relay service code.

[0317] Example II-37 includes the apparatus of Example II-32, wherein the 5G ProSe UE-to-UE relay access information includes one or more of the following: an authorization policy for using 5G ProSe UE-to-UE relay; a policy / parameter for 5G ProSe UE-to-UE relay discovery and enabling connection to the 5G ProSe UE-to-UE relay after discovery is performed; and / or radio parameters when the UE is not served by a Next Generation Radio Access Network (NG-RAN).

[0318] Example II-38 includes the apparatus of Example II-37, wherein the policy / parameters for 5G ProSe UE-to-UE relay discovery and enabling connection to the 5G ProSe UE-to-UE relay after discovery is performed include one or more of the following: an indication to use UE-to-UE relay; 5G ProSe UE-to-UE relay discovery parameters, including user information ID and one or more relay service codes; one or more IP versions that can be used for relay traffic for each ProSe relay service code; for Layer 2 relays, Protocol Data Unit (PDU) session parameters that will be used for relay traffic for each ProSe relay service code, including PDU session type, Data Network Name (DNN), Session and Service Continuity (SSC) mode, Single Network Slice Selection Assistance Information (S-NSSAI), and Access Type Preference; and security-related content for 5G ProSe relay discovery for each 5G ProSe relay service code.

[0319] Example II-39 includes the apparatus of Example II-36 or II-38, wherein, for Model A, when the UE is announcing UE, the user information ID corresponds to the announcing party information parameter; and for Model B, when the UE is acting as a discovering party UE or a discovered party UE, the user information ID corresponds to the discovering party information in the request message or the discovering party information in the response message.

[0320] Example II-40 includes the apparatus of Example II-36 or II-38, wherein the one or more relay service codes include relay service codes for identifying the connectivity services that the 5G ProSe UE-to-UE relay will provide to the application.

[0321] Example II-41 includes a non-transitory computer-readable storage medium storing instructions that, when executed by processing circuitry of an access and mobility management function (AMF) device in a fifth-generation system (5GS), cause the device to perform operations for configuring UE-to-UE relay operations, the operations including: processing a user equipment (UE) registration request message, the registration request message including information indicating the UE's fifth-generation (5G) proximity-based service (ProSe) UE-to-UE relay capability and / or 5G ProSe UE-to-UE relay access capability; selecting a policy control function (PCF) supporting 5G ProSe information configuration for the UE; and establishing a UE policy association with the PCF for 5G ProSe UE-to-UE relay information configuration delivery and / or 5G ProSe UE-to-UE relay access information configuration delivery.

[0322] Example II-42 includes the non-transitory computer-readable storage medium of Example II-41, wherein the operation further includes reporting the UE's 5G ProSe UE-to-UE relay capability and / or 5G ProSe UE-to-UE relay access capability to the selected PCF, such that the selected PCF can determine 5G ProSe UE-to-UE relay information for the UE based on the UE's 5G ProSe UE-to-UE relay capability and / or determine 5G ProSe UE-to-UE relay access information for the UE based on the UE's 5G ProSe UE-to-UE relay access capability.

[0323] Example II-43 includes the non-transitory computer-readable storage medium of Example II-41, wherein the operation further includes processing a UE policy container, the UE policy container including information for instructing the UE to make a 5G ProSe UE-to-UE relay information configuration request and / or a 5G ProSe UE-to-UE relay access information configuration request.

[0324] Example II-44 includes the non-transitory computer-readable storage medium of Example II-43, wherein the operation further includes reporting the UE's 5G ProSe UE-to-UE relay information configuration request and / or 5G ProSe UE-to-UE relay access information configuration request to the selected PCF, such that the selected PCF determines whether to configure the 5G ProSe UE-to-UE relay information and / or the 5G ProSe UE-to-UE relay access information to the UE.

[0325] Example II-45 includes the non-transitory computer-readable storage medium of Example II-44, wherein the operation further includes: processing a message received from the selected PCF, the message instructing the selected PCF to determine to configure the 5G ProSe UE-to-UE relay information and / or the 5G ProSe UE-to-UE relay access information to the UE; and delivering the 5G ProSe UE-to-UE relay information and / or the 5G ProSe UE-to-UE relay access information to the UE.

[0326] Example II-46 includes the non-transitory computer-readable storage medium of Example II-45, wherein the 5G ProSe UE-to-UE relay information and / or the 5G ProSe UE-to-UE relay access information of the UE will be updated when at least one of the following conditions occurs: the UE moves from one Public Land Mobile Network (PLMN) to another PLMN; there is a subscription change in the list of PLMNs in which the UE is authorized to perform 5G ProSe UE-to-UE relay operations; or there is a change in service-specific parameters.

[0327] Example II-47 includes the non-transitory computer-readable storage medium of Example II-46, wherein the operation further includes: revoking service authorization from the UE when a PLMN that is providing services is removed from the list of PLMNs in the service authorization parameters.

[0328] Example II-48 includes the non-transitory computer-readable storage medium of Example II-46, wherein the 5GProSe UE-to-UE relay information and / or the 5G ProSe UE-to-UE relay access information of the UE will be updated when the UE's roaming causes a subscription change.

[0329] Example II-49 includes the non-transitory computer-readable storage medium of Example II-45, wherein the operation further includes processing a UE policy configuration request received from the UE when the UE determines that either the 5G ProSe UE-to-UE relay information and / or the 5G ProSe UE-to-UE relay access information is invalid.

[0330] Example II-50 includes the non-transitory computer-readable storage medium of Example II-45, wherein the 5G ProSe UE-to-UE relay information includes one or more of the following: an authorization policy for acting as a 5G ProSe UE-to-UE relay; a 5G ProSe relay discovery policy / parameters for the 5G ProSe UE-to-UE relay; radio parameters for 5G ProSe relay discovery; radio parameters for 5G ProSe relay communication; a mapping rule between 5G ProSe PC5 5QI and Uu 5QI values; and / or a mapping rule between 5G ProSe PC5 5QI and Uu QCI values.

[0331] Example II-51 includes the non-transitory computer-readable storage medium of Example II-50, wherein the 5G ProSe relay discovery policy / parameters for 5GProSe UE-to-UE relays include one or more of the following: an indication for UE-to-UE relays; 5G ProSe UE-to-UE relay discovery parameters, including a user information ID and one or more relay service codes; for Layer 3 relays, protocol data unit (PDU) session parameters for relay traffic for each ProSe relay service code, including PDU session type, data network name (DNN), session and service continuity (SSC) mode, single network slice selection assistance information (S-NSSAI), and access type preference; and security-related content for 5G ProSe relay discovery for each 5G ProSe relay service code.

[0332] Example II-52 includes the non-transitory computer-readable storage medium of Example II-45, wherein the 5G ProSe UE-to-UE relay access information includes one or more of the following: an authorization policy for using 5G ProSe UE-to-UE relay; a policy / parameter for 5G ProSe UE-to-UE relay discovery and enabling connection to the 5G ProSe UE-to-UE relay after discovery is performed; and / or radio parameters when the UE is not served by a next-generation radio access network (NG-RAN).

[0333] Example II-53 includes the non-transitory computer-readable storage medium of Example II-52, wherein the policy / parameters for 5G ProSe UE-to-UE relay discovery and enabling connection to the 5G ProSe UE-to-UE relay after discovery is performed include one or more of the following: an indication to use UE-to-UE relay; 5G ProSe UE-to-UE relay discovery parameters, including user information ID and one or more relay service codes; one or more IP versions that can be used for relay traffic for each ProSe relay service code; for Layer 2 relays, Protocol Data Unit (PDU) session parameters that will be used for relay traffic for each ProSe relay service code, including PDU session type, Data Network Name (DNN), Session and Service Continuity (SSC) mode, Single Network Slice Selection Assistance Information (S-NSSAI), and Access Type Preference; and security-related content for 5G ProSe relay discovery for each 5G ProSe relay service code.

[0334] Example II-54 includes a non-transitory computer-readable storage medium of Example II-51 or II-53, wherein, for Model A, when the UE is announcing UE, the user information ID corresponds to the announcing party information parameter; and for Model B, when the UE is acting as a discovering UE or a discovered UE, the user information ID corresponds to the discovering party information in a request message or the discovering party information in a response message.

[0335] Example II-55 includes a non-transitory computer-readable storage medium of Example II-51 or II-53, wherein the one or more relay service codes include relay service codes for identifying the connectivity services that the 5G ProSe UE-to-UE relay will provide to the application.

[0336] Example II-56 includes a non-transitory computer-readable storage medium storing instructions that, when executed by processing circuitry of a device of a policy control function (PCF) in a fifth-generation system (5GS), cause the device to perform operations for configuring UE-to-UE relay operations. The operations include: processing a message received from an access and mobility management function (AMF) including information indicating a user equipment (UE)'s fifth-generation (5G) proximity-based service (ProSe) UE-to-UE relay capability and / or 5G ProSe UE-to-UE relay access capability; and determining 5G ProSe UE-to-UE relay information and / or 5G ProSe UE-to-UE relay access information for the UE based on the UE's 5G ProSe UE-to-UE relay capability and / or the 5G ProSe UE-to-UE relay access capability, respectively.

[0337] Example II-57 includes the non-transitory computer-readable storage medium of Example II-56, wherein the operation further includes determining whether to configure the 5G ProSe UE-to-UE relay information and / or the 5G ProSe UE-to-UE relay access information for the UE in response to a 5G ProSe UE-to-UE relay information configuration request and / or a 5G ProSe UE-to-UE relay access information configuration request from the UE.

[0338] Example II-58 includes the non-transitory computer-readable storage medium of Example II-56, wherein the operation further includes updating the 5G ProSe UE-to-UE relay information and / or the 5G ProSe UE-to-UE relay access information of the UE when at least one of the following conditions occurs: the UE moves from one Public Land Mobile Network (PLMN) to another PLMN; there is a subscription change in the list of PLMNs, and the UE is authorized to perform 5G ProSe UE-to-UE relay operations in the PLMN; or there is a change in service-specific parameters.

[0339] Example II-59 includes the non-transitory computer-readable storage medium of Example II-58, wherein the operation further includes: revoking service authorization from the UE when a PLMN that is providing services is removed from the list of PLMNs in the service authorization parameters.

[0340] Example II-60 includes the non-transitory computer-readable storage medium of Example II-58, wherein the operation further includes: updating the 5G ProSe UE-to-UE relay information and / or the 5G ProSe UE-to-UE relay access information of the UE when roaming of the UE causes a subscription change.

[0341] Example II-61 includes the non-transitory computer-readable storage medium of Example II-58, wherein the operation further includes: when the UE determines that either the 5G ProSe UE-to-UE relay information and / or the 5G ProSe UE-to-UE relay access information is invalid, processing a message received from the AMF indicating that the UE has triggered a policy configuration procedure.

[0342] Example II-62 includes the non-transitory computer-readable storage medium of Example II-58, wherein the 5G ProSe UE-to-UE relay information includes one or more of the following: an authorization policy for acting as a 5G ProSe UE-to-UE relay; a 5G ProSe relay discovery policy / parameters for the 5G ProSe UE-to-UE relay; radio parameters for 5G ProSe relay discovery; radio parameters for 5G ProSe relay communication; a mapping rule between 5G ProSe PC5 5QI and Uu 5QI values; and / or a mapping rule between 5G ProSe PC5 5QI and Uu QCI values.

[0343] Example II-63 includes the non-transitory computer-readable storage medium of Example II-62, wherein the 5G ProSe relay discovery policy / parameters for 5GProSe UE-to-UE relays include one or more of the following: an indication for UE-to-UE relays; 5G ProSe UE-to-UE relay discovery parameters, including a user information ID and one or more relay service codes; for Layer 3 relays, protocol data unit (PDU) session parameters for relay traffic for each ProSe relay service code, including PDU session type, data network name (DNN), session and service continuity (SSC) mode, single network slice selection assistance information (S-NSSAI), and access type preference; and security-related content for 5G ProSe relay discovery for each 5G ProSe relay service code.

[0344] Example II-64 includes the non-transitory computer-readable storage medium of Example II-58, wherein the 5G ProSe UE-to-UE relay access information includes one or more of the following: an authorization policy for using 5G ProSe UE-to-UE relay; a policy / parameter for 5G ProSe UE-to-UE relay discovery and enabling connection to the 5G ProSe UE-to-UE relay after discovery is performed; and / or radio parameters when the UE is not served by a next-generation radio access network (NG-RAN).

[0345] Example II-65 includes the non-transitory computer-readable storage medium of Example II-64, wherein the policy / parameters for 5G ProSe UE-to-UE relay discovery and enabling connection to the 5G ProSe UE-to-UE relay after discovery is performed include one or more of the following: an indication to use UE-to-UE relay; 5G ProSe UE-to-UE relay discovery parameters, including user information ID and one or more relay service codes; one or more IP versions that can be used for relay traffic for each ProSe relay service code; for Layer 2 relays, Protocol Data Unit (PDU) session parameters that will be used for relay traffic for each ProSe relay service code, including PDU session type, Data Network Name (DNN), Session and Service Continuity (SSC) mode, Single Network Slice Selection Assistance Information (S-NSSAI), and Access Type Preference; and security-related content for 5G ProSe relay discovery for each 5G ProSe relay service code.

[0346] Example II-66 includes a non-transitory computer-readable storage medium of Example II-63 or II-65, wherein, for Model A, when the UE is announcing UE, the user information ID corresponds to the announcing party information parameter; and for Model B, when the UE is acting as a discovering UE or a discovered UE, the user information ID corresponds to the discovering party information in a request message or the discovering party information in a response message.

[0347] Example II-67 includes a non-transitory computer-readable storage medium of Example II-63 or II-65, wherein the one or more relay service codes include relay service codes for identifying the connectivity services that the 5G ProSe UE-to-UE relay will provide to the application.

[0348] Example II-68 includes a non-transitory computer-readable storage medium storing instructions that, when executed by processing circuitry of a user equipment (UE) in a fifth-generation system (5GS), cause the UE to: encode a registration request message including information indicating the UE's fifth-generation (5G) proximity-based service (ProSe) UE-to-UE relay capability and / or 5G ProSe UE-to-UE relay access capability; and send the registration request message to the Access and Mobility Management Function (AMF).

[0349] Example II-69 includes the non-transitory computer-readable storage medium of Example II-68, wherein the instructions further cause the UE to: encode a UE policy container, the UE policy container including information for instructing the UE to make a 5G ProSe UE-to-UE relay information configuration request and / or a 5G ProSe UE-to-UE relay access information configuration request; and send the UE policy container to the AMF.

[0350] Example II-70 includes the non-transitory computer-readable storage medium of Example II-69, wherein the instructions further cause the UE to: process 5G ProSe UE-to-UE relay information and / or 5G ProSe UE-to-UE relay access information configured by a policy control function (PCF) selected by the AMF for the UE, the PCF supporting 5G ProSe information configuration.

[0351] Example II-71 includes the non-transitory computer-readable storage medium of Example II-70, wherein the 5G ProSe UE-to-UE relay information and / or the 5G ProSe UE-to-UE relay access information of the UE will be updated when at least one of the following conditions occurs: the UE moves from one Public Land Mobile Network (PLMN) to another PLMN; there is a subscription change in the list of PLMNs in which the UE is authorized to perform 5G ProSe UE-to-UE relay operations; or there is a change in service-specific parameters.

[0352] Example II-72 includes the non-transitory computer-readable storage medium of Example II-70, wherein the instructions further cause the UE to determine whether any one of the 5G ProSe UE-to-UE relay information and / or the 5G ProSe UE-to-UE relay access information is valid; and if any one of the 5G ProSe UE-to-UE relay information and / or the 5G ProSe UE-to-UE relay access information is determined to be invalid, trigger a policy configuration process.

[0353] Example II-73 includes the non-transitory computer-readable storage medium of Example II-70, wherein the 5G ProSe UE-to-UE relay information includes one or more of the following: an authorization policy for acting as a 5G ProSe UE-to-UE relay; a 5G ProSe relay discovery policy / parameters for the 5G ProSe UE-to-UE relay; radio parameters for 5G ProSe relay discovery; radio parameters for 5G ProSe relay communication; a mapping rule between 5G ProSe PC5 5QI and Uu 5QI values; and / or a mapping rule between 5G ProSe PC5 5QI and Uu QCI values.

[0354] Example II-74 includes the non-transitory computer-readable storage medium of Example II-73, wherein the 5G ProSe relay discovery policy / parameters for 5GProSe UE-to-UE relays include one or more of the following: an indication for UE-to-UE relays; 5G ProSe UE-to-UE relay discovery parameters, including a user information ID and one or more relay service codes; for Layer 3 relays, protocol data unit (PDU) session parameters for relay traffic for each ProSe relay service code, including PDU session type, data network name (DNN), session and service continuity (SSC) mode, single network slice selection assistance information (S-NSSAI), and access type preference; and security-related content for 5G ProSe relay discovery for each 5G ProSe relay service code.

[0355] Example II-75 includes the non-transitory computer-readable storage medium of Example II-70, wherein the 5G ProSe UE-to-UE relay access information includes one or more of the following: an authorization policy for using 5G ProSe UE-to-UE relay; a policy / parameter for 5G ProSe UE-to-UE relay discovery and enabling connection to the 5G ProSe UE-to-UE relay after discovery is performed; and / or radio parameters when the UE is not served by a next-generation radio access network (NG-RAN).

[0356] Example II-76 includes the non-transitory computer-readable storage medium of Example II-75, wherein the policy / parameters for 5G ProSe UE-to-UE relay discovery and enabling connection to the 5G ProSe UE-to-UE relay after discovery is performed include one or more of the following: an indication to use UE-to-UE relay; 5G ProSe UE-to-UE relay discovery parameters, including user information ID and one or more relay service codes; one or more IP versions that can be used for relay traffic for each ProSe relay service code; for Layer 2 relays, Protocol Data Unit (PDU) session parameters for relay traffic for each ProSe relay service code, including PDU session type, Data Network Name (DNN), Session and Service Continuity (SSC) mode, Single Network Slice Selection Assistance Information (S-NSSAI), and access type preference; and security-related content for 5G ProSe relay discovery for each 5G ProSe relay service code.

[0357] Example II-77 includes the non-transitory computer-readable storage medium of Example II-74 or II-76, wherein, for Model A, when the UE is announcing UE, the user information ID corresponds to the announcing party information parameter; and for Model B, when the UE is acting as a discovering UE or a discovered UE, the user information ID corresponds to the discovering party information in the request message or the discovering party information in the response message.

[0358] Example II-78 includes the non-transitory computer-readable storage medium of Example II-74 or II-76, wherein the one or more relay service codes include relay service codes for identifying the connectivity services that the 5G ProSe UE-to-UE relay will provide to the application.

[0359] Example II-79 includes a method performed by an Access and Mobility Management Function (AMF) in a fifth-generation system (5GS), comprising: processing a registration request message for a user equipment (UE), the registration request message including information indicating the UE's fifth-generation (5G) proximity-based service (ProSe) UE-to-UE relay capability and / or 5G ProSe UE-to-UE relay access capability; selecting a policy control function (PCF) supporting 5G ProSe information configuration for the UE; and establishing a UE policy association with the PCF for 5G ProSe UE-to-UE relay information configuration delivery and / or 5G ProSe UE-to-UE relay access information configuration delivery.

[0360] Example II-80 includes the method of Example II-79, further comprising: reporting the 5G ProSe UE-to-UE relay capability and / or the 5G ProSe UE-to-UE relay access capability of the UE to the selected PCF, such that the selected PCF can determine 5G ProSe UE-to-UE relay information for the UE based on the UE's 5G ProSe UE-to-UE relay capability and / or determine 5G ProSe UE-to-UE relay access information for the UE based on the UE's 5G ProSe UE-to-UE relay access capability.

[0361] Example II-81 includes the method of Example II-79, and further includes: processing a UE policy container, the UE policy container including information for instructing the UE to make a 5G ProSe UE-to-UE relay information configuration request and / or a 5G ProSe UE-to-UE relay access information configuration request.

[0362] Example II-82 includes the method of Example II-81, further comprising: reporting the 5G ProSe UE-to-UE relay information configuration request and / or the 5G ProSe UE-to-UE relay access information configuration request of the UE to the selected PCF, such that the selected PCF determines whether to configure the 5G ProSe UE-to-UE relay information and / or the 5G ProSe UE-to-UE relay access information to the UE.

[0363] Example II-83 includes the method of Example II-82, further comprising: processing a message received from a selected PCF, the message instructing the selected PCF to determine to configure the 5G ProSe UE-to-UE relay information and / or the 5G ProSe UE-to-UE relay access information to the UE; and delivering the 5G ProSe UE-to-UE relay information and / or the 5G ProSe UE-to-UE relay access information to the UE.

[0364] Example II-84 includes the method of Example II-83, wherein the 5G ProSe UE-to-UE relay information and / or the 5G ProSe UE-to-UE relay access information of the UE will be updated when at least one of the following conditions occurs: the UE moves from one Public Land Mobile Network (PLMN) to another PLMN; there is a subscription change in the list of PLMNs in which the UE is authorized to perform 5G ProSe UE-to-UE relay operations; or there is a change in service-specific parameters.

[0365] Example II-85 includes the method of Example II-84, and further includes: revoking the service authorization from the UE when the PLMN that is providing the service is removed from the list of PLMNs in the service authorization parameters.

[0366] Example II-86 includes the method of Example II-84, wherein the 5G ProSe UE-to-UE relay information and / or the 5G ProSe UE-to-UE relay access information of the UE are updated when the UE's roaming causes a subscription change.

[0367] Example II-87 includes the method of Example II-83, and further includes: processing a UE policy configuration request received from the UE when the UE determines that either the 5G ProSe UE-to-UE relay information and / or the 5G ProSe UE-to-UE relay access information is invalid.

[0368] Example II-88 includes the method of Example II-83, wherein the 5G ProSe UE-to-UE relay information includes one or more of the following: an authorization policy for acting as a 5G ProSe UE-to-UE relay; a 5G ProSe relay discovery policy / parameters for the 5G ProSe UE-to-UE relay; radio parameters for 5G ProSe relay discovery; radio parameters for 5G ProSe relay communication; a mapping rule between 5G ProSe PC5 5QI and Uu 5QI values; and / or a mapping rule between 5G ProSe PC5 5QI and Uu QCI values.

[0369] Example II-89 includes the method of Example II-88, wherein the 5G ProSe relay discovery policy / parameters for 5G ProSe UE-to-UE relays include one or more of the following: 5G ProSe UE-to-UE relays as an indication; 5G ProSe UE-to-UE relay discovery parameters, including user information ID and one or more relay service codes; for Layer 3 relays, Protocol Data Unit (PDU) session parameters for relay traffic for each ProSe relay service code, including PDU session type, Data Network Name (DNN), Session and Service Continuity (SSC) mode, Single Network Slice Selection Assistance Information (S-NSSAI), and Access Type Preference; and security-related content for 5G ProSe relay discovery for each 5G ProSe relay service code.

[0370] Example II-90 includes the method of Example II-83, wherein the 5G ProSe UE-to-UE relay access information includes one or more of the following: an authorization policy for using 5G ProSe UE-to-UE relay; a policy / parameter for 5G ProSe UE-to-UE relay discovery and enabling connection to the 5G ProSe UE-to-UE relay after discovery is performed; and / or radio parameters when the UE is not served by a next-generation radio access network (NG-RAN).

[0371] Example II-91 includes the method of Example II-90, wherein the policy / parameters for 5G ProSe UE-to-UE relay discovery and enabling connection to the 5G ProSe UE-to-UE relay after discovery is performed include one or more of the following: an indication to use UE-to-UE relay; 5G ProSe UE-to-UE relay discovery parameters, including user information ID and one or more relay service codes; one or more IP versions that can be used for relay traffic for each ProSe relay service code; for Layer 2 relays, Protocol Data Unit (PDU) session parameters that will be used for relay traffic for each ProSe relay service code, including PDU session type, Data Network Name (DNN), Session and Service Continuity (SSC) mode, Single Network Slice Selection Assistance Information (S-NSSAI), and Access Type Preference; and security-related content for 5G ProSe relay discovery for each 5G ProSe relay service code.

[0372] Example II-92 includes the methods of Example II-89 or II-91, wherein, for model A, when the UE is announcing UE, the user information ID corresponds to the announcing party information parameter; and for model B, when the UE is acting as a discovering UE or a discovered UE, the user information ID corresponds to the discovering party information in the request message or the discovering party information in the response message.

[0373] Example II-93 includes the method of Example II-89 or II-91, wherein the one or more relay service codes include a relay service code for identifying the connectivity service that the 5G ProSe UE-to-UE relay will provide to the application.

[0374] Example II-94 includes a device in a fifth-generation system (5GS) including means for performing the method of any one of Examples II-79 to II-93.

[0375] Example II-95 includes a method performed by a policy control function (PCF) in a fifth-generation system (5GS), comprising: processing a message received from an access and mobility management function (AMF), the message including information for indicating a user equipment (UE)'s fifth-generation (5G) proximity-based service (ProSe) UE-to-UE relay capability and / or 5G ProSe UE-to-UE relay access capability; and determining 5G ProSe UE-to-UE relay information and / or 5G ProSe UE-to-UE relay access information for the UE based on the UE's 5G ProSe UE-to-UE relay capability and / or the 5G ProSe UE-to-UE relay access capability, respectively.

[0376] Example II-96 includes the method of Example II-95, further comprising: determining whether to configure the 5G ProSe UE-to-UE relay information and / or the 5G ProSe UE-to-UE relay access information for the UE in response to a 5G ProSe UE-to-UE relay information configuration request and / or a 5G ProSe UE-to-UE relay access information configuration request from the UE.

[0377] Example II-97 includes the method of Example II-95, further comprising: updating the 5G ProSe UE-to-UE relay information and / or the 5G ProSe UE-to-UE relay access information of the UE when at least one of the following conditions occurs: the UE moves from one Public Land Mobile Network (PLMN) to another PLMN; there is a subscription change in the list of PLMNs, and the UE is authorized to perform 5G ProSe UE-to-UE relay operations in the PLMN; or there is a change in service-specific parameters.

[0378] Example II-98 includes the method of Example II-97, and further includes: revoking the service authorization from the UE when the PLMN that is providing the service is removed from the list of PLMNs in the service authorization parameters.

[0379] Example II-99 includes the method of Example II-97, and further includes: updating the 5G ProSe UE-to-UE relay information and / or the 5G ProSe UE-to-UE relay access information of the UE when the roaming of the UE causes a subscription change.

[0380] Example II-100 includes the method of Example II-97, further comprising: when the UE determines that either the 5G ProSe UE-to-UE relay information and / or the 5G ProSe UE-to-UE relay access information is invalid, processing a message received from the AMF indicating that the UE has triggered a policy configuration procedure.

[0381] Example II-101 includes the method of Example II-95, wherein the 5G ProSe UE-to-UE relay information includes one or more of the following: an authorization policy for acting as a 5G ProSe UE-to-UE relay; a 5G ProSe relay discovery policy / parameters for the 5G ProSe UE-to-UE relay; radio parameters for 5G ProSe relay discovery; radio parameters for 5G ProSe relay communication; a mapping rule between 5G ProSe PC5 5QI and Uu 5QI values; and / or a mapping rule between 5G ProSe PC5 5QI and Uu QCI values.

[0382] Example II-102 includes the method of Example II-101, wherein the 5G ProSe relay discovery policy / parameters for 5G ProSe UE-to-UE relays include one or more of the following: UE-to-UE relay indications; 5G ProSe UE-to-UE relay discovery parameters, including user information ID and one or more relay service codes; for Layer 3 relays, Protocol Data Unit (PDU) session parameters for relay traffic for each ProSe relay service code, including PDU session type, Data Network Name (DNN), Session and Service Continuity (SSC) mode, Single Network Slice Selection Assistance Information (S-NSSAI), and Access Type Preference; and security-related content for 5G ProSe relay discovery for each 5G ProSe relay service code.

[0383] Example II-103 includes the method of Example II-95, wherein the 5G ProSe UE-to-UE relay access information includes one or more of the following: an authorization policy for using 5G ProSe UE-to-UE relay; a policy / parameter for 5G ProSe UE-to-UE relay discovery and enabling connection to the 5G ProSe UE-to-UE relay after discovery is performed; and / or radio parameters when the UE is not served by a next-generation radio access network (NG-RAN).

[0384] Example II-104 includes the method of Example II-103, wherein the policy / parameters for 5G ProSe UE-to-UE relay discovery and enabling connection to the 5G ProSe UE-to-UE relay after discovery is performed include one or more of the following: an indication to use UE-to-UE relay; 5G ProSe UE-to-UE relay discovery parameters, including user information ID and one or more relay service codes; one or more IP versions that can be used for relay traffic for each ProSe relay service code; for Layer 2 relays, Protocol Data Unit (PDU) session parameters that will be used for relay traffic for each ProSe relay service code, including PDU session type, Data Network Name (DNN), Session and Service Continuity (SSC) mode, Single Network Slice Selection Assistance Information (S-NSSAI), and Access Type Preference; and security-related content for 5G ProSe relay discovery for each 5G ProSe relay service code.

[0385] Example II-105 includes the methods of Example II-102 or II-104, wherein, for model A, when the UE is announcing UE, the user information ID corresponds to the announcing party information parameter; and for model B, when the UE is acting as a discovering party UE or a discovered party UE, the user information ID corresponds to the discovering party information in the request message or the discovering party information in the response message.

[0386] Example II-106 includes the methods of Example II-102 or II-104, wherein the one or more relay service codes include relay service codes for identifying the connectivity services that the 5G ProSe UE-to-UE relay will provide to the application.

[0387] Example II-107 includes a device in a fifth-generation system (5GS) including means for performing the method of any one of Examples II-95 to II-106.

[0388] Example II-108 includes a method performed by a user equipment (UE) in a fifth-generation system (5GS), comprising: encoding a registration request message, the registration request message including information indicating the UE's fifth-generation (5G) proximity-based service (ProSe) UE-to-UE relay capability and / or 5G ProSe UE-to-UE relay access capability; and sending the registration request message to the Access and Mobility Management Function (AMF).

[0389] Example II-109 includes the method of Example II-108, further comprising: encoding a UE policy container, the UE policy container including information for instructing the UE to make a 5G ProSe UE-to-UE Relay Information Configuration Request and / or a 5G ProSe UE-to-UE Relay Access Information Configuration Request; and sending the UE policy container to the AMF.

[0390] Example II-110 includes the method of Example II-109, further comprising: processing 5G ProSe UE-to-UE relay information and / or 5G ProSe UE-to-UE relay access information configured by a policy control function (PCF) selected by the AMF for the UE, wherein the PCF supports 5G ProSe information configuration.

[0391] Example II-111 includes the method of Example II-10, wherein the 5G ProSe UE-to-UE relay information and / or the 5G ProSe UE-to-UE relay access information of the UE will be updated when at least one of the following conditions occurs: the UE moves from one Public Land Mobile Network (PLMN) to another PLMN; there is a subscription change in the list of PLMNs, and the UE is authorized to perform 5G ProSe UE-to-UE relay operations in the PLMN; or there is a change in service-specific parameters.

[0392] Example II-112 includes the method of Example II-110, further comprising: determining whether any one of the 5G ProSe UE-to-UE relay information and / or the 5G ProSe UE-to-UE relay access information is valid; and triggering a policy configuration process when any one of the 5G ProSe UE-to-UE relay information and / or the 5G ProSe UE-to-UE relay access information is determined to be invalid.

[0393] Example II-113 includes the method of Example II-110, wherein the 5G ProSe UE-to-UE relay information includes one or more of the following: an authorization policy for acting as a 5G ProSe UE-to-UE relay; a 5G ProSe relay discovery policy / parameters for the 5G ProSe UE-to-UE relay; radio parameters for 5G ProSe relay discovery; radio parameters for 5G ProSe relay communication; a mapping rule between 5G ProSe PC5 5QI and Uu 5QI values; and / or a mapping rule between 5G ProSe PC5 5QI and Uu QCI values.

[0394] Example II-114 includes the method of Example II-113, wherein the 5G ProSe relay discovery policy / parameters for 5G ProSe UE-to-UE relays include one or more of the following: 5G ProSe UE-to-UE relays as an indication; 5G ProSe UE-to-UE relay discovery parameters, including user information ID and one or more relay service codes; for Layer 3 relays, Protocol Data Unit (PDU) session parameters for relay traffic for each ProSe relay service code, including PDU session type, Data Network Name (DNN), Session and Service Continuity (SSC) mode, Single Network Slice Selection Assistance Information (S-NSSAI), and Access Type Preference; and security-related content for 5G ProSe relay discovery for each 5G ProSe relay service code.

[0395] Example II-115 includes the method of Example II-110, wherein the 5G ProSe UE-to-UE relay access information includes one or more of the following: an authorization policy for using 5G ProSe UE-to-UE relay; a policy / parameter for 5G ProSe UE-to-UE relay discovery and enabling connection to the 5G ProSe UE-to-UE relay after discovery is performed; and / or radio parameters when the UE is not served by a next-generation radio access network (NG-RAN).

[0396] Example II-116 includes the method of Example II-115, wherein the policy / parameters for 5G ProSe UE-to-UE relay discovery and enabling connection to the 5G ProSe UE-to-UE relay after discovery is performed include one or more of the following: an indication to use UE-to-UE relay; 5G ProSe UE-to-UE relay discovery parameters, including user information ID and one or more relay service codes; one or more IP versions that can be used for relay traffic for each ProSe relay service code; for Layer 2 relays, Protocol Data Unit (PDU) session parameters that will be used for relay traffic for each ProSe relay service code, including PDU session type, Data Network Name (DNN), Session and Service Continuity (SSC) mode, Single Network Slice Selection Assistance Information (S-NSSAI), and Access Type Preference; and security-related content for 5G ProSe relay discovery for each 5G ProSe relay service code.

[0397] Example II-117 includes the methods of Example II-114 or II-116, wherein, for model A, when the UE is announcing UE, the user information ID corresponds to the announcing party information parameter; and for model B, when the UE is acting as a discovering UE or a discovered UE, the user information ID corresponds to the discovering party information in the request message or the discovering party information in the response message.

[0398] Example II-118 includes the methods of Example II-114 or II-116, wherein the one or more relay service codes include relay service codes for identifying the connectivity services that the 5G ProSe UE-to-UE relay will provide to the application.

[0399] Example II-119 includes a device in a fifth-generation system (5GS) including means for performing the method of any one of Examples II-108 to II-118.

[0400] Example II-120 includes a communication system comprising means for performing any of Examples II-1 to II-16, means for performing any of Examples II-17 to II-29, and means for performing any of Examples II-30 to II-40.

[0401] While certain embodiments have been illustrated and described herein for purposes of description, various alternative and / or equivalent embodiments or implementations devised to achieve the same purpose may replace the illustrated and described embodiments without departing from the scope of this disclosure. This application is intended to cover any adaptations or variations of the embodiments discussed herein. Therefore, it is readily understood that the embodiments described herein are limited only by the appended claims and their equivalents.

Claims

1. An apparatus for configuring UE-to-UE relay operation in a 5G system, comprising: Interface circuit; as well as A processing circuit coupled to the interface circuit, the processing circuit being used for: Process a registration request message of a user equipment (UE) received via the interface circuit, the registration request message including information indicating the UE's fifth-generation proximity-based 5G ProSe UE-to-UE relay capability and / or 5G ProSe UE-to-UE relay access capability; Based on the UE's 5G ProSe UE-to-UE relay capability and / or 5G ProSe UE-to-UE relay access capability, select the policy control function (PCF) that supports 5G ProSe information configuration for the UE. Establish UE policy association with the PCF for 5G ProSe UE-to-UE relay information configuration delivery and / or 5G ProSe UE-to-UE relay access information configuration delivery, and When the UE determines that the 5G ProSe UE-to-UE relay information and / or the 5G ProSe UE-to-UE relay access information is invalid, the UE initiates a policy configuration process to the PCF.

2. The apparatus of claim 1, wherein, The processing circuit is further configured to report the UE's 5G ProSe UE-to-UE relay capability and / or 5G ProSe UE-to-UE relay access capability to the selected PCF, so that the selected PCF can determine 5G ProSe UE-to-UE relay information for the UE based on the UE's 5G ProSe UE-to-UE relay capability and / or determine 5G ProSe UE-to-UE relay access information for the UE based on the UE's 5G ProSe UE-to-UE relay access capability.

3. The apparatus of claim 1, wherein, The processing circuit is also configured to process a UE policy container received via the interface circuit, the UE policy container including information for instructing the UE to make a 5G ProSe UE-to-UE relay information configuration request and / or a 5G ProSe UE-to-UE relay access information configuration request.

4. The apparatus of claim 3, wherein, The processing circuit is further configured to report the UE's 5G ProSe UE-to-UE relay information configuration request and / or 5G ProSe UE-to-UE relay access information configuration request to the selected PCF, so that the selected PCF can determine whether to configure the 5G ProSe UE-to-UE relay information and / or the 5G ProSe UE-to-UE relay access information to the UE.

5. The apparatus of claim 4, wherein, The processing circuit is also used for: Process the message received from the selected PCF, the message instructing the selected PCF to determine to configure the 5G ProSe UE-to-UE relay information and / or the 5G ProSe UE-to-UE relay access information to the UE; and The 5G ProSe UE-to-UE relay information and / or the 5G ProSe UE-to-UE relay access information are delivered to the UE.

6. The apparatus of claim 5, wherein, The 5GProSe UE-to-UE relay information and / or the 5GProSe UE-to-UE relay access information of the UE will be updated when at least one of the following conditions occurs: The UE moves from one public land mobile network (PLMN) to another PLMN. There are subscription changes in the PLMN list, and the UE is authorized to perform 5G ProSe UE-to-UE relay operation in the PLMN; or Service-specific parameters may change.

7. The apparatus of claim 5, wherein, The 5G ProSe UE-to-UE relay information includes one or more of the following: Licensing policies for 5G ProSe UE-to-UE relays; 5G ProSe relay discovery strategy / parameters for 5G ProSe UE-to-UE relay; Radio parameters discovered for 5G ProSe relays; Radio parameters for 5G ProSe relay communication; Mapping rules between 5G ProSe PC5 5QI and Uu 5QI values; and / or Mapping rules between 5G ProSe PC5 5QI and Uu QCI values.

8. The apparatus of claim 7, wherein, The 5G ProSe relay discovery strategy / parameters for 5G ProSe UE-to-UE relays include one or more of the following: This will serve as an indication for UE-to-UE relay; 5G ProSe UE-to-UE relay discovery parameters include user information ID and one or more relay service codes; For Layer 3 trunks, the Protocol Data Unit (PDU) session parameters used for trunk traffic for each ProSe trunk service code will include PDU session type, Data Network Name (DNN), Session and Service Continuity (SSC) mode, Single Network Slice Selection Auxiliary Information (S-NSSAI), and Access Type Preference. as well as Security-related content for 5G ProSe relay discovery used for each 5G ProSe relay service code.

9. The apparatus of claim 5, wherein, The 5G ProSe UE-to-UE relay access information includes one or more of the following: Licensing policies for using 5G ProSe UE-to-UE relay; Policies / parameters for 5G ProSe UE-to-UE relay discovery and enabling connection to the 5G ProSe UE-to-UE relay after discovery is performed; and / or Radio parameters when the UE is not served by the Next Generation Radio Access Network (NG-RAN).

10. The apparatus of claim 9, wherein, The policy / parameters for 5G ProSe UE-to-UE relay discovery and enabling connection to the 5G ProSe UE-to-UE relay after discovery is performed include one or more of the following: Instructions for UE-to-UE relay will be used; 5G ProSe UE-to-UE relay discovery parameters include user information ID and one or more relay service codes; One or more IP versions can be used for relay traffic for each ProSe relay service code; For Layer 2 trunks, the Protocol Data Unit (PDU) session parameters used for trunk traffic for each ProSe trunk service code will include PDU session type, Data Network Name (DNN), Session and Service Continuity (SSC) mode, Single Network Slice Selection Auxiliary Information (S-NSSAI), and Access Type Preference. as well as Security-related content for 5G ProSe relay discovery used for each 5G ProSe relay service code.

11. The apparatus of claim 8 or 10, wherein, For Model A, when the UE acts as the declaring UE, the user information ID corresponds to the declaring party information parameter; and for Model B, when the UE acts as the discovering UE or the discovered party UE respectively, the user information ID corresponds to the discovering party information in the request message or the discovering party information in the response message.

12. The apparatus of claim 8 or 10, wherein, The one or more relay service codes include relay service codes used to identify the connectivity services that the 5G ProSe UE-to-UE relay will provide to the application.

13. The apparatus according to any one of claims 1 to 10, wherein, The device is part of the Access and Mobility Management Function (AMF).

14. An apparatus for configuring UE-to-UE relay operation in a fifth-generation system (5GS), comprising: Interface circuit; as well as A processing circuit coupled to the interface circuit, the processing circuit being used for: Process messages received from the Access and Mobility Management Function (AMF) via the interface circuitry, the messages including information indicating the 5G ProSe UE-to-UE relay capability and / or 5G ProSe UE-to-UE relay access capability of the User Equipment (UE). and Based on the UE's 5G ProSe UE-to-UE relay capability and / or 5G ProSe UE-to-UE relay access capability, 5G ProSe UE-to-UE relay information and / or 5G ProSe UE-to-UE relay access information are determined for the UE. The process of configuring a policy initiated by the UE when the UE determines that the 5G ProSe UE-to-UE relay information and / or the 5G ProSe UE-to-UE relay access information is invalid.

15. The apparatus of claim 14, wherein, The processing circuit is further configured to determine whether to configure the 5G ProSe UE-to-UE relay information and / or the 5G ProSe UE-to-UE relay access information for the UE in response to a 5G ProSe UE-to-UE relay information configuration request and / or a 5G ProSe UE-to-UE relay access information configuration request from the UE.

16. A computer-readable storage medium storing instructions thereon, said instructions, when executed by processing circuitry of a user equipment (UE) in a fifth-generation system (5GS), causing the UE to: The coded registration request message includes information indicating the UE's fifth-generation proximity-based 5G ProSe UE-to-UE relay capability and / or 5G ProSe UE-to-UE relay access capability; The registration request message is sent to the Access and Mobility Management Function (AMF); Receive 5G ProSe UE-to-UE relay information and / or 5G ProSe UE-to-UE relay access information from the PCF, wherein the PCF is selected by the AMF for the UE based on the information used to indicate the UE's 5G ProSe UE-to-UE relay capability and / or 5G ProSe UE-to-UE relay access capability; and When the UE determines that the 5G ProSe UE-to-UE relay information and / or the 5G ProSe UE-to-UE relay access information is invalid, it initiates a policy configuration process to the PCF.

17. The computer-readable storage medium of claim 16, wherein the instructions further cause the UE to: An encoded UE policy container, the UE policy container including information for instructing the UE to make a 5G ProSe UE-to-UE relay information configuration request and / or a 5G ProSe UE-to-UE relay access information configuration request; and The UE policy container is sent to the AMF.

Images