Method and apparatus for proximity service authorization and provisioning

Abstract

Various aspects of the present disclosure relate to mechanisms for proximity service (ProSe) authorization and provisioning. A user equipment (UE) may be configured to support ProSe communications and may indicate this capability to a radio access network (RAN) and a core network during registration of the UE. Based on the ProSe indication, the RAN may select an access and mobility management function (AMF) that supports ProSe authorization and policy provisioning, and forward a registration request indicating that the UE supports ProSe communications to the selected AMF. Upon authorizing the UE for ProSe operation, the AMF may transmit a registration accept message including a ProSe support indication to the UE. The UE may then initiate a ProSe session with another UE based on the ProSe support indication in the registration accept message.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to and the benefit of pending non-provisional patent application No. 17 / 088,478 filed in the U.S. Patent Office on November 3, 2020, and provisional application No. 62 / 931,131 filed in the U.S. Patent Office on November 5, 2019, both of which are assigned to the assignee of this application and are hereby expressly incorporated herein by reference as if fully set forth below and for all applicable purposes. Technical Field

[0003] The techniques discussed below relate generally to wireless communication networks, and more particularly to proximity service (ProSe) wireless communications.

[0004] introduction

[0005] Wireless communication between devices can be facilitated through various network configurations. In one configuration, a cellular network can enable user equipment (UE) to communicate with each other through signaling with a nearby base station or cellular cell. Another wireless communication network configuration is a device-to-device (D2D) network, in which UEs can directly signal each other, rather than via an intermediate base station or cellular cell. For example, a D2D communication network can utilize sidelink signaling to facilitate direct communication between UEs. In some sidelink network configurations, the UE can further communicate in a cellular network (usually under the control of a base station). Therefore, the UE can be configured for uplink and downlink signaling via a base station, and further for sidelink signaling directly between UEs without transmission through a base station.

[0006] An example of a sidelink wireless communication network is a vehicle-to-everything (V2X) communication network. V2X communication involves information exchange not only between vehicles themselves, but also between vehicles and external systems such as street lights, buildings, pedestrians, and cellular communication networks. In some examples, V2X and other D2D networks can utilize Proximity Services (ProSe) signaling to achieve sidelink communications. Compared to traditional D2D technologies, ProSe can provide improved scalability, manageability, privacy, security, and battery efficiency.

[0007] A brief overview of some examples

[0008] An overview of one or more aspects of the present disclosure is given below to provide a basic understanding of these aspects. This overview is not an exhaustive overview of all conceived features of the present disclosure, and is neither intended to identify the key or decisive elements of all aspects of the present disclosure nor to attempt to define the scope of any or all aspects of the present disclosure. Its sole purpose is to present some concepts of one or more aspects of the present disclosure in a form as a preface to a more detailed description given later.

[0009] In one example, a method for wireless communication at a user equipment is disclosed. The method may include transmitting a message to a radio access network. The message includes a registration request and a proximity service (ProSe) indication. The ProSe indication indicates to the radio access network and a core network serving the radio access network that the user equipment is configured to support ProSe communication. The method may further include: receiving a registration accept message including a ProSe support indication from the core network via the radio access network; and initiating a ProSe session between the user equipment and another user equipment based on the ProSe support indication in the registration accept message.

[0010] Another example provides a user equipment (UE) in a wireless communication network. The UE includes a transceiver configured to communicate with a radio access network, a memory, and a processor coupled to the transceiver and the memory. The transceiver and the memory may be configured to transmit a message to the radio access network. The message includes a registration request and a proximity service (ProSe) indication. The ProSe indication indicates to the radio access network and a core network serving the radio access network that the user equipment is configured to support ProSe communication. The processor and the memory may be further configured to: receive a registration acceptance message including a ProSe support indication from the core network via the radio access network; and initiate a ProSe session between the user equipment and another user equipment based on the ProSe support indication in the registration acceptance message.

[0011] Another example provides a method for wireless communication at a base station. The method may include receiving a message from a user equipment. The message includes a registration request and a proximity service (ProSe) indication. The ProSe indication indicates to the base station that the user equipment is configured to support ProSe communication. The method may further include: selecting a core network service node within a core network that supports ProSe authorization and policy provisioning; forwarding the registration request to the core network service node; and forwarding a registration acceptance message from the core network service node to the user equipment. The registration acceptance message includes a ProSe support indication.

[0012] Another example provides a method for facilitating wireless communication at a core network service node within a core network. The method may include: receiving a registration request for a user equipment from a base station; and obtaining subscription information and context information for the user equipment. The subscription information includes proximity service (ProSe) subscription data indicating that the user equipment is configured to support ProSe communication. The method may further include transmitting a registration acceptance message to the user equipment. The registration acceptance message includes a ProSe support indication when the user equipment is authorized for ProSe operation.

[0013] These and other aspects of the present invention will be more fully understood after reading the following detailed description. After reading the following description of specific exemplary embodiments of the present invention in conjunction with the accompanying drawings, other aspects, features and embodiments of the present invention will be apparent to those of ordinary skill in the art. Although features of the present invention may be discussed below with respect to certain embodiments and drawings, all embodiments of the present invention may include one or more advantageous features discussed herein. In other words, although one or more embodiments may be discussed as having certain advantageous features, one or more such features may also be used according to the various embodiments of the present invention discussed herein. In a similar manner, although exemplary embodiments may be discussed below as device, system or method embodiments, it should be appreciated that such exemplary embodiments may be implemented in various devices, systems, and methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 is a diagram illustrating an example of a wireless communication system in accordance with some aspects.

[0016] Figure 2 is a block diagram illustrating an example of a 5G wireless communication system (5GS) according to some aspects.

[0017] Figure 3 is a conceptual illustration of an example of a radio access network in accordance with some aspects.

[0018] Figure 4 is a diagram illustrating an example in which a 5GS is configured to support sidelink and proximity service (ProSe) communications according to some aspects.

[0019] Figure 5 is a signaling diagram illustrating an example flow for supporting UE registration for ProSe services in accordance with some aspects.

[0020] Figure 6 is a diagram illustrating an example of a hardware implementation for user equipment employing a processing system in accordance with some aspects.

[0021] Figure 7is a diagram illustrating an example of a hardware implementation for a base station employing a processing system in accordance with some aspects.

[0022] Figure 8 is a diagram illustrating an example of a hardware implementation for a core network service node employing a processing system in accordance with some aspects.

[0023] Fig. 9 is a flow chart of an exemplary method for facilitating ProSe authorization and provisioning at a user equipment in accordance with some aspects.

[0024] Fig.10 is a flow chart of an example method for facilitating ProSe authorization and provisioning at a base station according to some aspects.

[0025] Fig.11 is a flow chart of another exemplary method for facilitating ProSe authorization and provisioning at a base station in accordance with some aspects.

[0026] Fig.12 is a flow chart of an example method for facilitating ProSe authorization provisioning at a core network serving node in accordance with some aspects.

[0027] Fig.13 is a flow chart of another exemplary method for facilitating ProSe authorization and provisioning at a core network serving node in accordance with some aspects.

[0028] Fig.14 is a flow chart of another exemplary method for facilitating ProSe authorization and provisioning at a core network serving node in accordance with some aspects.

[0029] Detailed Description

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

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

[0032] Various aspects of the present disclosure relate to mechanisms for proximity service (ProSe) authorization and provisioning in a fifth generation (5G) new radio (NR) system. In some examples, a user equipment (UE) may be configured to support ProSe communications and may provide a ProSe indication indicating the capability to a radio access network (RAN) and a core network during UE registration. For example, the UE may include the ProSe indication in a registration request message sent to the core network via the RAN. As another example, the UE may include a ProSe slice identifier indicating ProSe network slice selection assistance information (PS-NSSAI) in an access network (AN) message containing a registration request message sent to the RAN. As yet another example, the UE may include a ProSe capability indication in an AN message sent to the RAN.

[0033] In some examples, upon receiving an AN message including a registration request and a ProSe indication (e.g., within the registration request or as an AN parameter of the AN message), the RAN (e.g., a base station) may be configured to select a core network service node that supports ProSe services. In some examples, the core network service node may be a standard access and mobility management function (AMF) within the core network configured to support ProSe authorization and policy provisioning, or a ProSe-specific AMF within the core network configured to support ProSe registration and ProSe service access authorization functionality. The base station may be further configured to modify the registration request to include a PS-NSSAI and forward the modified registration request including the PS-NSSAI to the selected AMF or ProSe AMF.

[0034] When authorizing the UE for ProSe operation, the core network service node (e.g., AMF or ProSe AMF) may be configured to transmit a registration accept message including a ProSe support indication to the UE. For example, the core network service node may be configured to obtain ProSe subscription data and context information (e.g., UE context) from a unified data management (UDM) in the core network. The core network service node may be further configured to determine whether the UE is authorized for ProSe operation and is therefore allowed to use ProSe services based on the ProSe subscription data and the UE context. The core network service node may be further configured to retrieve ProSe policy information from a policy control function (PCF) in the core network and include the ProSe policy information in the registration accept message. The UE may utilize the ProSe support indication and the ProSe policy information when initiating and establishing a ProSe session with another UE over the ProSe PC5 interface.

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

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

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

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

[0039] Within this document, a "mobile" device does not necessarily need to have mobile capabilities, and may be stationary. The term mobile device or mobile equipment refers broadly to a wide variety of devices and technologies. A UE may include several hardware structural components sized, shaped, and arranged to facilitate communication; such components may include antennas, antenna arrays, RF chains, amplifiers, one or more processors, and the like electrically coupled to each other. For example, some non-limiting examples of mobile devices include mobile devices, cellular (cell) phones, smart phones, Session Initiation Protocol (SIP) phones, laptops, personal computers (PCs), notebooks, netbooks, smartbooks, tablet devices, personal digital assistants (PDAs), and a wide variety of embedded systems, for example, corresponding to the "Internet of Things" (IoT). Additionally, the mobile device may be a car or other transportation vehicle, a remote sensor or actuator, a robot or robotic device, a satellite radio, a global positioning system (GPS) device, an object tracking device, a drone, a multicopter, a quadcopter, a remote control device, a consumer and / or wearable device (such as glasses), a wearable camera, a virtual reality device, a smart watch, a health or fitness tracker, a digital audio player (e.g., an MP3 player), a camera, a game console, etc. The mobile device may additionally be a digital home or smart home device, such as home audio, video, and / or multimedia equipment, an appliance, a vending machine, a smart lighting device, a home security system, a smart meter, etc. The mobile device may additionally be a smart energy device, a security device, a solar panel or solar array, a municipal infrastructure device that controls power, lighting, water, etc. (e.g., a smart grid), an industrial automation and enterprise device, a logistics controller, agricultural equipment, etc. Still further, the mobile device may provide connected medical or telemedicine support, i.e., health care at a distance. Telehealth devices may include telehealth monitoring devices and telehealth supervisory devices, whose communications may be given priority or prioritized access over other types of information, for example, in the form of prioritized access for critical service data transmission and / or associated QoS for critical service data transmission.

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

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

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

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

[0044] In addition, uplink and / or downlink control information and / or traffic information may be divided into frames, subframes, time slots, and / or symbols in time. As used herein, a symbol may refer to a time unit in which each subcarrier carries one resource element (RE) in an orthogonal frequency division multiplexing (OFDM) waveform. A time slot may carry 7 or 14 OFDM symbols. A subframe may refer to a duration of 1 ms. Multiple subframes or time slots may be grouped together to form a single frame or radio frame. Of course, these definitions are not required, and any appropriate scheme may be utilized to organize the waveform, and the various time divisions of the waveform may have any appropriate duration.

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

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

[0047] Now refer to Figure 2 , by way of example and not limitation, a block diagram illustrating an example of various components of a 5G wireless communication system (5GS) 200 is provided. In some examples, the 5GS 200 may be used in conjunction with the 5G wireless communication system described above and in Figure 1 . 5GS 200 includes a user equipment (UE) 202, an NR-RAN 204, and a core network 206. By means of the wireless communication system 200, the UE 202 can perform data communication with an external data network 214 (such as but not limited to the Internet or an Ethernet network).

[0048] For example, the core network 206 may include an access and mobility management function (AMF) 208, a session management function (SMF) 210, and a user plane function (UPF) 212. The AMF 208 and the SMF 210 employ control plane (e.g., non-access stratum (NAS)) signaling to perform various functions related to mobility management and session management for the UE 202. For example, the AMF 208 provides connectivity, mobility management, and authentication for the UE 202, while the SMF 210 provides session management for the UE 202 (e.g., handling signaling related to a protocol data unit (PDU) session between the UE 202 and the external DN 214). The UPF 212 provides user plane connectivity to route 5G (NR) packets to / from the UE 202 via the NR-RAN 204.

[0049] The core network 206 may further include other functions such as a policy control function (PCF) 216, an authentication server function (AUSF) 218, a unified data management (UDM) 220, a network slice selection function (NSSF) 222, and other functions (not illustrated for simplicity). PCF 216 provides policy information (e.g., rules) for control plane functions such as network slicing, roaming, and mobility management. In addition, PCF 216 supports 5G quality of service (QoS) policies, network slicing policies, and other types of policies. AUSF 218 performs authentication of UE 202. UDM 220 facilitates the generation of authentication and key agreement (AKA) credentials, performs user identification, and manages subscription information and UE context. NSSF 222 redirects traffic to network slices. For example, network slices may be defined for different categories of subscribers or use cases, such as smart homes, the Internet of Things (IoT), connected cars, smart energy grids, etc.

[0050] Each use case may receive a unique set of optimized resources and network topology (e.g., network slice) to meet the connectivity, speed, power, and capacity requirements of the use case.

[0051] In order to establish a connection to the 5G core network 206 via the NR-RAN 204, the UE 202 may transmit a registration request and a PDU session establishment request to the 5G core network 206 via the NR-RAN 204. The AMF 208 and the SMF 210 may process the registration request and the PDU session establishment request and establish a data network session (DNS) between the UE 202 and the external DN 214 via the UPF 212. The DNS may include one or more sessions (e.g., data sessions or data flows) and may be served by multiple UPFs 212 (only one of which is shown for convenience). Examples of data flows include, but are not limited to, IP flows, Ethernet flows, and unstructured data flows.

[0052] Now refer to Figure 3 , a schematic illustration of RAN 300 is provided as an example and not as a limitation. In some examples, RAN 300 may be similar to that described above and in Figure 1 RAN 104 illustrated in and / or described above and in Figure 2 The geographic area covered by the RAN 300 may be divided into cellular areas (cells) that may be uniquely identified by user equipment (UE) based on an identity broadcasted from an access point or base station. Figure 3 Macro cells 302, 304, and 306 and small cells 308 are illustrated, each of which may include one or more sectors (not shown). A sector is a sub-area of ​​a cell. All sectors within one cell are served by the same base station. A radio link within a sector may be identified by a single logical identification belonging to the sector. In a cell divided into sectors, multiple sectors within a cell may be formed by antenna groups, where each antenna is responsible for communication with UEs in a portion of the cell.

[0053] Various base station arrangements can be used. Figure 3 , two base stations 310 and 312 are shown in the cellular cells 302 and 304, and the third base station 314 is shown as controlling the remote radio head (RRH) 316 in the cellular cell 306. That is, the base station may have an integrated antenna, or may be connected to the antenna or RRH by a feeder cable. In the illustrated example, the cellular cells 302, 304, and 306 may be referred to as macro cells because the base stations 310, 312, and 314 support cells with large sizes. In addition, the base station 318 is shown in a small cell 308 (e.g., a micro cell, a micro cell, a femto cell, a home base station, a home node B, a home evolved node B, etc.), which may overlap with one or more macro cells. In this example, the cellular cell 308 may be referred to as a small cell because the base station 318 supports a cell with a relatively small size. The cell size setting may be completed according to the system design and component constraints.

[0054] It is to be understood that the radio access network 300 may include any number of wireless base stations and cellular cells. In addition, relay nodes may be deployed to extend the size or coverage area of ​​a given cellular cell. Base stations 310, 312, 314, 318 provide wireless access points to the core network for any number of mobile devices. In some examples, base stations 310, 312, 314, and / or 318 may be similar to those described above and in Figure 1 The same as the base station / scheduling entity 108 illustrated in FIG.

[0055] Within the RAN 300, cells may include UEs that may be in communication with one or more sectors of each cell. Further, each base station 310, 312, 314, and 318 may be configured to provide a core network (e.g., such as a core network) for all UEs in the corresponding cell. Figure 1 2). For example, UEs 322 and 324 may be in communication with base station 310; UEs 326 and 328 may be in communication with base station 312; UEs 330 and 332 may be in communication with base station 314 via RRH 316; and UE 334 may be in communication with base station 318. In some examples, UEs 322, 324, 326, 328, 330, 332, 334, 338, 340, and / or 342 may be in communication with base station 310 as described above and in Figure 1 The UE / scheduled entity 106 illustrated in FIG. 1 is the same as and / or the same as described above and in Figure 2 The various physical channels between the UE and the RAN are usually established, maintained, and released under the control of the AMF 208, such as Figure 2 As explained in .

[0056] In some examples, an unmanned aerial vehicle (UAV) 320 (which may be a drone or a quadcopter) may be a mobile network node and may be configured to function as a UE. For example, UAV 320 may operate within cell 302 by communicating with base station 310.

[0057] In the RAN 300, the ability of a UE to communicate independently of its location while moving is referred to as mobility. The RAN 300 can achieve the mobility of the UE by facilitating handovers between cells (i.e., transferring the UE's connection from one radio channel to another radio channel). For example, during a call with a scheduling entity, or at any other time, the UE may monitor various parameters of the signal from its serving cell and various parameters of neighboring cells. Depending on the quality of these parameters, the UE may maintain communication with one or more neighboring cells. During this time, if the UE moves from one cell to another, or if the signal quality from a neighboring cell exceeds the signal quality from the serving cell for a given amount of time, the UE may perform a handover or handover from the serving cell to the neighboring (target) cell. For example, a UE 324 (illustrated as a vehicle, but any suitable form of UE may be used) may move from a geographic area corresponding to its serving cell 302 to a geographic area corresponding to a neighboring cell 306. When the signal strength or quality from a neighbor cell 306 exceeds the signal strength or quality of its serving cell 302 for a given amount of time, the UE 324 may transmit a report message indicating this condition to its serving base station 310. In response, the UE 324 may receive a handover command, and the UE may undergo a handover to the cell 306.

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

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

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

[0061] In a further aspect of the RAN 300, sidelink or device-to-device (D2D) signals 327 may be communicated directly between UEs on resources allocated by the base station 312 for sidelink or D2D communications. In some examples, the sidelink or D2D signals 327 include one or more of sidelink / D2D traffic and sidelink / D2D control. For example, two or more UEs (e.g., UEs 326 and 328) may communicate with each other using D2D or sidelink signals 327 without relaying the communication through a base station (e.g., base station 312). In this example, the UE may act as a scheduling entity to schedule the D2D or sidelink signals 327 on network allocated resources in a D2D, vehicle-to-vehicle (V2V), or vehicle-to-everything (V2X) network. Thus, in a wireless communication system with scheduled access to time-frequency resources and having a cellular configuration, a scheduling entity (e.g., UE 326) and one or more scheduled entities (e.g., one or more other UEs 328) can communicate directly with each other using resources allocated by a cellular network (e.g., base station 312) for D2D or sidelink communication.

[0062] Figure 4 An example of a 5GS 400 configured to support D2D or sidelink communication is illustrated. In some examples, sidelink communication may include V2X communication. V2X communication not only involves wireless information exchange directly between vehicle UEs (e.g., vehicle UEs 402 and 404) themselves, but also involves wireless information exchange directly between vehicle UEs 402 / 404 and infrastructure (e.g., roadside units (RSU) UEs (R-UEs) 406) (such as street lights, buildings, traffic cameras, toll booths or other stationary objects), wireless information exchange directly between vehicle UEs 402 / 404 and pedestrian UEs 408, and wireless information exchange directly between vehicle UEs 402 / 404 and radio access networks (e.g., base stations 410). In some examples, V2X communication can be implemented according to the new radio (NR) cellular V2X standard defined by 3GPP (Release 15) or other suitable standards.

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

[0064] Sidelink communications between vehicle UEs 402 and 404 or between vehicle UEs 402 or 404 and R-UE 406 or P-UE 408 may occur over a proximity service (ProSe) PC5 interface 412. In various aspects of the present disclosure, the PC5 interface 412 may be further used to support D2D communications in other proximity use cases. Examples of other proximity use cases may include public safety or business-based (e.g., entertainment, education, office, medical, and / or interactive) proximity services. Figure 4 In the example shown in , ProSe D2D communication may occur between UEs 414 and 416 .

[0065] ProSe communication may support different operation scenarios, such as in-coverage, out-of-coverage, and partial coverage. Out-of-coverage refers to a scenario where a UE (e.g., V-UEs 402 and 404 or UEs 414 and 416) is outside the coverage area of ​​a base station (e.g., base station 410), but each UE is still configured for ProSe communication. Partial coverage refers to a scenario where at least one of these UEs (e.g., V-UE 404) is outside the coverage area of ​​a base station (e.g., base station 410), while one or more other UEs (e.g., V-UE 402 and P-UE 408) are in communication with the base station 410. In-coverage refers to a scenario where a UE (e.g., UEs 414 and 416) is in communication with a base station 410 (e.g., gNB) via a Uu (e.g., air interface) connection to receive ProSe service authorization and provisioning information to support ProSe operation. To facilitate ProSe authorization and policy provisioning in the ProSe use case, each UE 414 and 416 may be configured to indicate to the base station 410 and the core network 418 serving the base station 410 that the UE 414 / 416 supports ProSe communications over the PC5 interface 412 .

[0066] Figure 5 5 is a signaling diagram illustrating an exemplary flow for supporting a UE 502 to register with a core network via a radio access network (RAN) 504 for ProSe services in a proximity use case. For example, the UE 502 may correspond to Figure 1-4 , including any V2X UE (e.g., V-UE, P-UE, R-UE, etc.). In addition, the RAN 504 may include one or more base stations (e.g., eNBs or gNBs), such as Figure 1-4 As shown in Figure 5 In the example shown in FIG, the core network includes AMF 506, PCF 508, AUSF 510, and UDM 512. For example, each of AMF 506, PCF 508, AUSF 510, and UDM 512 may correspond to Figure 2 In some examples, the AMF 506 is a ProSe AMF configured to support registration for ProSe services and provide ProSe service access authorization functionality.

[0067] At 514, the UE 502 transmits an access network (AN) message to the RAN 504. The AN message includes a registration request (RR) and a ProSe indication that the UE 502 supports ProSe communications. In some examples, the ProSe indication may be included in the RR to indicate to the RAN 504 and the core network that the UE 502 is configured to support ProSe communications for proximity usage services. In other examples, the ProSe indication of the ProSe communications supported by the UE 502 may be included in one or more AN parameters of the AN message. For example, the AN parameters may include a ProSe capability indication indicating to the RAN 504 that the UE 502 is configured to support ProSe communications for proximity usage services. In yet other examples, the AN parameters may include a ProSe slice identifier indicating to the RAN 504 that the UE 502 is configured to support ProSe communications for proximity usage services. For example, the ProSe slice identifier may include ProSe Network Slice Selection Assistance Information (PS-NSSAI).

[0068] At 516, the RAN 504 selects an AMF 506 based on the ProSe indication included in the AN message (e.g., within the RR or as an AN parameter of the AN message). In some examples, the RAN 504 may select an AMF 506 that supports ProSe authorization and policy provisioning. In other examples, the RAN 504 may select a specific type of AMF 506 (e.g., ProSe AMF 506) that is configured for ProSe registration and supports ProSe service access authorization functionality.

[0069] At 518, the RAN 504 transmits the RR to the selected AMF 506. In some examples, the RAN 504 may modify the RR to include the PS-NSSAI and transmit the modified RR including the PS-NSSAI to the selected AMF 506. At 520, the AMF 506 transfers the UE context of the UE 502 from the old AMF (not shown) that previously served the UE 502 to the new AMF 506. In some examples, the UE context may include ProSe session management function (SMF) information. For example, when the PS-NSSAI or the ProSe support indication is included in the RR, the AMF 506 may request the transfer of the ProSe SMF information from the old AMF.

[0070] At 522, the AMF 506 may perform authentication of the UE 502. In some examples, the AMF 506 may select the AUSF 510 and request authentication of the UE from the AUSF 510. In some examples, the AUSF 510 may retrieve authentication data for the UE 502 from the UDM 512. Once the UE 502 has been authenticated, the AUSF 510 may provide security information to the AMF 506. The AMF 506 may then indicate to the UE 502 that the UE is verified.

[0071] At 524, the AMF 506 retrieves subscription information (e.g., access and mobility subscription data and / or SMF selection subscription data) and may further retrieve the UE context from the UDM 512. In some examples, the subscription information may include ProSe subscription information. For example, the ProSe subscription data may include whether the UE 502 is authorized for ProSe operation and, therefore, whether it is allowed to utilize ProSe services, such as PS-NSSAI services. At 526, the AMF 506 may retrieve policy information for the UE 502 from the PCF 508. In some examples, the policy information may include ProSe policy information.

[0072] At 528, the AMF 506 transmits a registration accept message to the UE 502 via the RAN 504. In some examples, the AMF 506 may determine whether the UE 502 is authorized for ProSe operation based on the ProSe subscription data and the UE context. When the UE 502 is authorized for ProSe operation, the registration accept message may include a ProSe support indication to indicate to the UE 502 that the UE 502 can utilize ProSe services (e.g., initiate one or more ProSe sessions with other UEs). In addition, the registration accept message may further include ProSe policy information for use by the UE 502 in establishing one or more ProSe sessions.

[0073] Figure 6 614 is a block diagram illustrating an example of a hardware implementation for a user equipment (UE) 600 that employs a processing system 614. For example, the UE 600 may correspond to the above referenced Figure 1-5 Any UE shown and described.

[0074] UE 600 can be implemented with a processing system 614 including one or more processors 604. Examples of processor 604 include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform various functionalities described throughout this disclosure. In various examples, UE 600 can be configured to perform any one or more of the functions described herein. That is, the processor 604 as utilized in UE 600 can be used to implement any one or more of the processes and procedures described below.

[0075] In this example, the processing system 614 may be implemented with a bus architecture generally represented by bus 602. Bus 602 may include any number of interconnecting buses and bridges depending on the specific application and overall design constraints of the processing system 614. Bus 602 links together various circuits including one or more processors (generally represented by processor 604), memory 605, and computer readable media (generally represented by computer readable media 606). Bus 602 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further.

[0076] The bus interface 608 provides an interface between the bus 602 and the transceiver 610. The transceiver 610 provides a means for communicating with various other devices via a transmission medium (e.g., an air interface). Depending on the characteristics of the device, a user interface 612 (e.g., a keypad, a display, a touch screen, a speaker, a microphone, a control knob, etc.) may also be provided. Of course, such a user interface 612 is optional and may be omitted in some examples.

[0077] The processor 604 is responsible for managing the bus 602 and general processing, including the execution of software stored on the computer-readable medium 606. Software should be broadly interpreted to mean instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether described in software, firmware, middleware, microcode, hardware description languages, or other terms. The software, when executed by the processor 604, causes the processing system 614 to perform the various functions described below for any particular equipment. The computer-readable medium 606 and memory 605 can also be used to store data manipulated by the processor 604 when executing the software.

[0078] Computer readable medium 606 may be a non-transient computer readable medium. As an example, non-transient computer readable media include magnetic storage devices (e.g., hard disks, floppy disks, magnetic tapes), optical disks (e.g., compact disks (CDs) or digital versatile disks (DVDs)), smart cards, flash memory devices (e.g., card, stick, or key-type drives), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), registers, removable disks, and any other suitable medium for storing software and / or instructions that can be accessed and read by a computer. Computer readable medium 606 may reside in processor system 614, external to processing system 614, or distributed across multiple entities including processing system 614. Computer readable medium 606 may be implemented in a computer program product. As an example, a computer program product may include a computer readable medium in a packaging material. In some examples, computer readable medium 606 may be part of memory 605. Those skilled in the art will recognize how to best implement the described functionality presented throughout this disclosure depending on the particular application and the overall design constraints imposed on the overall system.

[0079] In some aspects of the present disclosure, the processor 604 may include a circuit system configured for various functions. For example, the processor 604 may include a communication and processing circuit system 642 configured to communicate with a base station (e.g., a scheduling entity) via downlink and uplink signals, and further configured to communicate with one or more other UEs via ProSe signals. For example, the communication and processing circuit system 642 may be configured to exchange ProSe control information and ProSe data with other UEs via the transceiver 610. As another example, the communication and processing circuit system 642 may be configured to generate uplink user data traffic and uplink control channels within one or more subframes, time slots and / or mini-slots and transmit uplink user data traffic and uplink control channels to the base station. In addition, the communication and processing circuit system 642 may be configured to receive downlink user data traffic and downlink control channels from the base station within one or more subframes, time slots and / or mini-slots. The communication and processing circuit system 642 may include one or more hardware components that provide a physical structure for performing processes related to wireless communication (e.g., signal reception and / or signal transmission) and signal processing (e.g., processing received signals and / or processing signals for transmission). The communication and processing circuit system 642 may be further configured to execute communication and processing software 652 stored on the computer-readable medium 606 to implement one or more functions described herein.

[0080] The processor 604 may further include a ProSe registration circuit system 644, which is configured to operate with the communication and processing circuit system 642 to generate a message (e.g., an AN message) and transmit the message to the RAN (e.g., a base station) serving the UE 600 to register with the core network. The AN message includes a registration request and a ProSe indication indicating that the UE 600 supports ProSe communication. In some examples, the ProSe indication is included in the registration request to indicate to the base station and the core network that the UE 600 is configured to support ProSe communication for proximity usage services. In other examples, the ProSe indication may be included in one or more AN parameters of the AN message. For example, the AN parameters may include a ProSe capability indication indicating to the base station that the UE 600 is configured to support ProSe communication for proximity usage services. In yet other examples, the AN parameters may include a ProSe slice identifier indicating to the base station that the UE 600 is configured to support ProSe communication for proximity usage services. For example, the ProSe slice identifier may include ProSe network slice selection assistance information (PS-NSSAI) 615. For example, PS-NSSAI 615 may be maintained in memory 605 for use by ProSe registration circuitry 644 .

[0081] The ProSe registration circuit system 644 may be further configured to operate with the communication and processing circuit system 642 to receive and process the registration accept message. In some examples, the registration accept message includes a ProSe support indication when the core network has authorized the UE 600 for ProSe operation. The registration accept message may further include ProSe policy information (PS policy information 618) for use in initiating one or more ProSe sessions. The ProSe registration circuit system 644 may be further configured to execute ProSe registration software 654 stored on the computer-readable medium 606 to implement one or more functions described herein.

[0082] The processor 604 may further include a ProSe session establishment circuit system 646 configured to establish one or more ProSe sessions with other UEs. In some examples, the ProSe session establishment circuit system 646 may be configured to initiate and establish ProSe with another UE upon receiving a ProSe support indication in a registration accept message from the core network. In some examples, the ProSe session establishment circuit system 646 may be configured to initiate and establish a ProSe session based on the PS policy information 618 included in the registration accept message.

[0083] In some examples, the ProSe session establishment circuit system 646 may be configured to discover another UE (e.g., using a peer discovery procedure) and establish a radio resource control (RRC) connection and a signaling radio bearer (SRB) for a ProSe session with the other UE. SRBs are logical communication channels on L2 and higher layers for transmitting control information for a communication session. For example, SRBs may carry a dedicated control channel (DCCH) including physical (PHY) layer, media access control (MAC) layer, and other access layer control information to initiate a communication session. Using SRBs, the configuration of L2 and higher protocol layers has a semi-static nature that occurs during the establishment of a communication session. PHY layer control is more dynamic in nature based on resource allocation (e.g., time, frequency, space, and / or power), and thus, PHY layer control and adaptation typically occurs when data is being exchanged (e.g., transmitted / received). SRBs may further establish one or more data radio bearers (DRBs) for the communication session. Data radio bearers are logical communications on L2 and higher layers for transmitting data for a communication session. For example, a DRB carries Dedicated Traffic Channel (DTCH) data for a communication session. A DRB may be established on an SRB using a Radio Bearer (RB) setup procedure.

[0084] Once the ProSe session is established by the ProSe session establishment circuitry 646, the communication and processing circuitry 642 may be configured to reserve resources (e.g., time-frequency resources) for transmission of one or more data packets to other UEs (or groups of UEs in a multicast ProSe session). The communication and processing circuitry 642 may then be configured to transmit a physical sidelink control channel (PSSCH) including downlink control information (DCI) indicating resources within the reserved resources scheduled for transmission of data packets within the physical sidelink shared channel (PSSCH). The ProSe session establishment circuitry 646 may be further configured to execute ProSe establishment software 656 stored on the computer-readable medium 606 to implement one or more functions described herein.

[0085] Figure 7 is a conceptual diagram illustrating an example of a hardware implementation for an exemplary base station 700 employing a processing system 714. For example, the base station 700 may be Figure 1-5 A base station as described in any one or more of the .

[0086] According to various aspects of the present disclosure, an element, or any portion of an element, or any combination of elements may be implemented with a processing system 714 including one or more processors 704. That is, the processor 704 as utilized in the base station 700 may be used to implement any one or more of the processes described below. The processing system 714 may be used with Figure 6 The processing system 614 illustrated in FIG. 7 is substantially the same as that in FIG. 7 , including a bus interface 708, a bus 702, a memory 705, a processor 704, and a computer readable medium 706. In addition, the base station 700 may include the same as that in FIG. Figure 6 In addition, base station 700 may include an interface 718 (eg, a network interface) that provides a means for communicating with various other devices within the core network and within one or more radio access networks.

[0087] In some aspects of the present disclosure, the processor 704 may include a resource assignment and scheduling circuit system 742 configured to generate, schedule, and modify resource assignments or grants for time-frequency resources (e.g., a set of one or more resource elements). For example, the resource assignment and scheduling circuit system 742 may schedule time-frequency resources within a plurality of subframes, time slots, and / or mini-time slots to carry user data traffic and / or control information to and / or from a plurality of UEs (scheduled entities).

[0088] In some examples, the resource assignment and scheduling circuit system 742 may be configured to schedule resources for transmitting an AN message from a user equipment (UE) to the base station 700. In addition, the resource assignment and scheduling circuit system 742 may be further configured to schedule resources for transmitting a registration acceptance message to the UE upon successful registration of the UE with the core network. The resource assignment and scheduling circuit system 742 may be further configured to execute resource assignment and scheduling software 752 stored on the computer-readable medium 706 to implement one or more functions described herein.

[0089] The processor 704 may further include a communication and processing circuit system 744, which is configured to communicate with one or more scheduled entities (e.g., UEs) via the transceiver 710. The communication and processing circuit system 744 may include one or more hardware components that provide a physical structure for performing processes related to wireless communication (e.g., signal reception and / or signal transmission) and signal processing (e.g., processing received signals and / or processing signals for transmission). For example, the communication and processing circuit system 744 may be configured to generate and transmit downlink user data traffic and downlink control channels in one or more subframes, time slots, and / or mini-slots based on resources assigned to downlink user data traffic and / or downlink control information by the resource assignment and scheduling circuit system 742. In addition, the communication and processing circuit system 744 may be configured to receive and process uplink user data traffic and uplink control channels in one or more subframes, time slots, and / or mini-slots based on resources assigned to uplink user data traffic and / or uplink control information by the resource assignment and scheduling circuit system 742.

[0090] In some examples, the communication and processing circuit system 744 may be configured to receive and process an AN message from the UE via the transceiver 710. The AN message may include a registration request and a ProSe indication that the UE supports ProSe communication. In some examples, the ProSe indication may be included in the registration request to indicate that the UE is configured to support ProSe communication for proximity usage services. In other examples, the AN message may further include one or more AN parameters containing the ProSe indication. For example, the AN parameter may include a ProSe capability indication indicating that the UE is configured to support ProSe communication for proximity usage services. In yet other examples, the AN parameter may include a ProSe slice identifier indicating that the UE is configured to support ProSe communication for proximity usage services. For example, the ProSe slice identifier may include ProSe network slice selection assistance information (PS-NSSAI) 715. In some examples, the PS-NSSAI 715 may be stored in the memory 705.

[0091] The communication and processing circuit system 744 may be further configured to forward the registration request included in the AN message to a core network service node (e.g., AMF or ProSe AMF) within the core network via interface 718. In addition, the communication and processing circuit system 744 may be configured to forward the registration acceptance message received from the core network service node to the UE via interface 712. The registration acceptance message may be transmitted to the UE via transceiver 710. The communication and processing circuit system 744 may be further configured to execute the communication and processing software 754 stored on the computer-readable medium 706 to implement one or more functions described herein.

[0092] The processor 704 may further include a ProSe registration circuit system 746, which is configured to operate with the communication and processing circuit system 744 to receive and process an AN message from the UE to facilitate the UE to register with the core network. The ProSe registration circuit system 746 may be further configured to select an AMF within the core network based on a ProSe indication included in the AN message (e.g., within a registration request or as an AN parameter of the AN message). In some examples, the ProSe registration circuit system 746 may select an AMF that supports ProSe authorization and policy provisioning. In other examples, the ProSe registration circuit system 746 may select a specific type of AMF (e.g., a ProSe AMF) that is configured for ProSe registration and supports ProSe service access authorization functions.

[0093] The ProSe registration circuit system 746 may be further configured to modify the registration request included in the AN message to include the PS-NSSAI and forward the modified registration request including the PS-NSSAI to the selected AMF. The ProSe registration circuit system 746 may be further configured to operate with the communication and processing circuit system 744 to forward the registration acceptance message received from the selected AMF to the UE. In some examples, when the core network (e.g., the selected AMF) has authorized the UE for ProSe operation, the registration acceptance message includes a ProSe support indication. The registration acceptance message may further include ProSe policy information for use by the UE in initiating one or more ProSe sessions. The ProSe registration circuit system 746 may be further configured to execute the ProSe registration software 756 stored on the computer-readable medium 706 to implement one or more functions described herein.

[0094] Figure 8 814 is a conceptual diagram illustrating an example of a hardware implementation of an exemplary core network service node 800 employing a processing system 814. For example, the core network service node 800 may be an AMF or a ProSe AMF, such as Figure 2 and / or as explained in 5.

[0095] According to various aspects of the present disclosure, an element, or any part of an element, or any combination of elements may be implemented with a processing system 814 including one or more processors 804. That is, a processor 804 such as that utilized in a core network service node 800 may be used to implement any one or more of the following processes. The processing system 814 may be used with Figure 7 The processing system 714 illustrated in FIG. 8 is substantially the same, including a bus interface 808, a bus 802, a memory 805, a processor 804, and a computer-readable medium 806. In addition, the core network service node 800 may include an optional user interface 812 and an interface 810 (e.g., a network interface) that provides a means for communicating with various other devices within the core network and with one or more radio access networks.

[0096] In some aspects of the present disclosure, the processor 804 may include a communication and processing circuit system 842. The communication and processing circuit system 842 may include one or more hardware components that provide a physical structure for performing various processes related to communication (e.g., signal reception and / or signal transmission) as described herein. The communication and processing circuit system 842 may further include one or more hardware components that provide a physical structure for performing various processes related to signal processing (e.g., processing received signals and / or processing signals for transmission) as described herein.

[0097] In an example where the core network service node 800 is an AMF or a ProSe AMF, the communication and processing circuit system 842 may be configured to receive and process a registration request from the UE via a RAN (e.g., a base station) serving the UE. The communication and processing circuit system 842 may be further configured to generate a registration acceptance message and transmit the registration acceptance message to the UE via the RAN. The communication and processing circuit system 842 may be further configured to execute the communication and processing software 852 stored on the computer-readable medium 806 to implement one or more functions described herein.

[0098] The processor 804 may further include a ProSe registration circuit system 844, a ProSe authorization circuit system 846, and a ProSe policy association circuit system 848. The ProSe registration circuit system 844 may be configured to register the UE for ProSe operation. In some examples, the ProSe registration circuit system 844 may be configured to perform a UE context transfer from an old AMF with which the UE was previously registered. For example, the ProSe registration circuit system 844 may request the old AMF to transfer ProSe SMF information when the registration request includes a PS-NSSAI or a ProSe support indication indicating that the UE supports ProSe communication.

[0099] The ProSe registration circuit system 844 may further operate with the ProSe authorization circuit system 846 to determine whether the UE is authorized for ProSe operation. In some examples, the ProSe registration circuit system 844 may be configured to retrieve subscription information (e.g., access and mobility subscription data and / or SMF selection subscription data) for the UE, and may further retrieve the UE context from the UDM in the core network. In some examples, the subscription information may include ProSe subscription data. The ProSe registration circuit system 844 may be configured to store ProSe subscription data / UE context (SD / context) 815, for example, in the memory 805. The ProSe authorization circuit system 846 may be configured to access the ProSe SD / context 815 in the memory 805 and utilize the ProSe SD / context 815 to determine whether the UE is authorized for ProSe operation, and is therefore allowed to utilize ProSe services.

[0100] The ProSe registration circuit system 844 may further operate with the ProSe policy association circuit system 848 to retrieve policy information for the UE from the PCF in the core network. In some examples, the policy information may include, for example, ProSe policy information 816 that may be stored in the memory 805. The ProSe policy association circuit system 848 may further associate the ProSe policy information 816 with the UE (e.g., UE context). In some examples, the ProSe policy information 816 may include at least one of in-coverage ProSe policy information, out-of-coverage ProSe policy information, or partial coverage ProSe policy information.

[0101] The ProSe registration circuitry 844 may be further configured to operate with the communication and processing circuitry 842 to generate a registration accept message for the UE upon successful registration of the UE. In some examples, when the ProSe authorization circuitry 846 determines that the UE is authorized for ProSe operation, the ProSe registration circuitry 844 may include a ProSe support indication in the registration accept message. Additionally, the ProSe registration circuitry 844 may include the ProSe policy information 816 in the registration accept message.

[0102] The ProSe registration circuit system 844 may be further configured to execute the ProSe registration software 854 stored on the computer-readable medium 806 to implement one or more functions described herein. In addition, the ProSe authorization circuit system 846 may be further configured to execute the ProSe authorization software 856 stored on the computer-readable medium 806 to implement one or more functions described herein. In addition, the ProSe policy association circuit system 848 may be further configured to execute the ProSe policy association software 858 stored on the computer-readable medium 806 to implement one or more functions described herein.

[0103] Fig. 9 900 is a flow chart of a method for facilitating ProSe authorization and provisioning at a user equipment according to some aspects. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and some of the illustrated features may not be required to implement all embodiments. In some examples, the method may be as described above and in Figure 6 The UE 600 illustrated in FIG. 6 is executed by a processor or a processing system, or by any suitable means for performing the described functions.

[0104] At block 902, the UE may transmit a message (e.g., an AN message) including a registration request and a proximity service (ProSe) indication to a RAN (e.g., a base station serving the UE). The ProSe indication indicates to the base station that the UE is configured to support ProSe communications for proximity usage services. In some examples, the registration request includes the ProSe indication. In some examples, the message further includes an AN parameter including the ProSe indication. For example, the ProSe indication may include a ProSe capability indication included in the AN parameter. As another example, the ProSe indication may include a ProSe slice identifier included in the AN parameter. The ProSe slice identifier may include ProSe network slice selection assistance information (PS-NSSAI). For example, in combination with the above Figure 6 The ProSe registration circuitry 644 , together with the communication and processing circuitry 642 and the transceiver 610 , as shown and described may provide a means for transmitting an AN message including a registration request and a ProSe indication to the RAN.

[0105] At block 904, the UE may receive a registration accept message including a ProSe support indication from the core network via the RAN. The ProSe support indication may indicate to the UE that the UE is authorized to utilize ProSe services in the RAN. In some examples, the registration accept message may further include ProSe policy information. For example, in combination with Figure 6The ProSe registration circuitry 644 , together with the communication and processing circuitry 642 and transceiver 610 , as shown and described may provide a means for receiving a registration accept message.

[0106] At block 906, the UE may initiate a ProSe session with another UE based on the ProSe support indication in the registration accept message. In some examples, the UE may be configured to initiate and establish a ProSe session based on the ProSe policy information included in the registration accept message. In some examples, the ProSe session may be established over the ProSe PC5 interface. For example, the above combination Figure 6 The ProSe session establishment circuitry 646 shown and described may provide means for initiating a ProSe session.

[0107] In one configuration, the UE 600 includes means for facilitating ProSe authorization and provisioning, as described in the present disclosure. In one aspect, the aforementioned means may be Figure 6 The processor 604 shown in the figure is configured to perform the functions recited by the aforementioned means. On the other hand, the aforementioned means may be a circuit or any equipment configured to perform the functions recited by the aforementioned means.

[0108] Of course, in the above examples, the circuit system included in the processor 604 is provided only as an example, and other means for performing the described functions may be included in various aspects of the present disclosure, including but not limited to instructions stored in the computer-readable storage medium 606, or in Figure 1-5 Any of the descriptions and using, for example, Fig. 9 Any other suitable equipment or means for implementing the described processes and / or algorithms.

[0109] Fig.10 1000 is a flow chart of a method for facilitating ProSe authorization and provisioning at a base station according to some aspects. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and some of the illustrated features may not be required to implement all embodiments. In some examples, the method may be as described above and in Figure 7 The base station 700 illustrated in FIG. 7 is executed by a processor or a processing system, or by any suitable means for performing the described functions.

[0110] At block 1002, a base station may receive a message (e.g., an AN message) including a registration request and a proximity service (ProSe) indication from a UE. The ProSe indication indicates to the base station that the UE is configured to support ProSe communications for proximity usage services. In some examples, the registration request includes the ProSe indication. In some examples, the message further includes an AN parameter including the ProSe indication. For example, the ProSe indication may include a ProSe capability indication included in the AN parameter. As another example, the ProSe indication may include a ProSe slice identifier included in the AN parameter. The ProSe slice identifier may include ProSe network slice selection assistance information (PS-NSSAI). For example, in combination with the above Figure 7 The ProSe registration circuitry 746 , together with the communication and processing circuitry 744 and the transceiver 710 , as shown and described may provide a means for receiving an AN message including a registration request and a ProSe indication.

[0111] At block 1004, the base station may select a core network service node within the core network that supports ProSe authorization and policy provisioning. In some examples, the base station may select a standard AMF within the core network that supports ProSe authorization and policy provisioning based on a ProSe slice identifier included in the AN message. In other examples, the base station may select an AMF specific to ProSe that is configured for ProSe registration and supports ProSe service access authorization functionality. For example, the above in conjunction with Figure 7 The ProSe registration circuitry 746 shown and described may provide means for selecting a core network serving node.

[0112] At block 1006, the base station may forward the registration request to the selected core network service node. Figure 7 The ProSe registration circuitry 746 , together with the communication and processing circuitry 744 and the transceiver 710 , as shown and described may provide means for forwarding a registration request to a selected core network serving node.

[0113] At block 1008, the base station may forward a registration accept message from the core network service node to the user equipment. The registration accept message may include a ProSe support indication, which indicates to the UE that the UE is authorized to utilize ProSe services. Figure 7 The ProSe registration circuitry 746 , together with the communication and processing circuitry 744 and transceiver 710 , as shown and described may provide means for forwarding a registration accept message from a core network service node to a user equipment.

[0114] Fig.111100 is a flow chart of a method for facilitating ProSe authorization and provisioning at a base station according to some aspects. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and some of the illustrated features may not be required to implement all embodiments. In some examples, the method may be as described above and in Figure 7 The base station 700 illustrated in FIG. 7 is executed by a processor or a processing system, or by any suitable means for performing the described functions.

[0115] At block 1102, a base station may receive a message (e.g., an AN message) including a registration request and a proximity service (ProSe) slice identifier from a UE. The ProSe slice identifier indicates to the base station that the UE is configured to support ProSe communications for proximity usage services. In some examples, the ProSe slice identifier is included in an AN parameter within the message. For example, the ProSe slice identifier may include ProSe network slice selection assistance information (PS-NSSAI). For example, the above in conjunction with Figure 7 The ProSe registration circuitry 746 , together with the communication and processing circuitry 744 and the transceiver 710 , as shown and described may provide a means for receiving an AN message including a registration request and a ProSe slice identifier.

[0116] At block 1104, the base station may modify the registration request to include the ProSe slice identifier to generate a modified registration request. Figure 7 The ProSe registration circuitry 746 shown and described may provide means for modifying a registration request.

[0117] At block 1106, the base station may forward the modified registration request including the ProSe slice identifier to a selected core network service node in the core network that supports ProSe authorization and policy provisioning. Figure 7 The ProSe registration circuitry 746 , together with the communication and processing circuitry 744 and the transceiver 710 , as shown and described may provide means for forwarding a modified registration request to a core network serving node.

[0118] In one configuration, the base station 700 includes means for facilitating ProSe authorization and provisioning, as described in the present disclosure. In one aspect, the aforementioned means may be Figure 7 The processor 704 shown in the figure is configured to perform the functions recited by the aforementioned means. On the other hand, the aforementioned means may be a circuit or any equipment configured to perform the functions recited by the aforementioned means.

[0119] Of course, in the above examples, the circuit system included in the processor 704 is provided only as an example, and other means for performing the described functions may be included in various aspects of the present disclosure, including but not limited to instructions stored in the computer-readable storage medium 706, or in Figure 1-5 Any of the descriptions and using, for example, Fig.10 and 11 Any other suitable equipment or means for implementing the described processes and / or algorithms.

[0120] Fig.12 1200 is a flow chart of a method for facilitating wireless communication at a core network service node within a core network. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and some of the illustrated features may not be required to implement all embodiments. In some examples, the method may be described above and in Figure 8 The core network service node 800 illustrated in FIG. 8 is executed by a processor or a processing system, or by any suitable device for performing the described functions.

[0121] At box 1202, the core network service node may receive a registration request for the UE from a base station. In some examples, the registration request includes a ProSe indication indicating that the user equipment supports ProSe communications. In other examples, the registration request includes a ProSe slice identifier indicating that the user equipment supports ProSe communications. In some examples, the ProSe slice identifier may include ProSe network slice selection assistance information (PS-NSSAI), which indicates to the core network service node that the UE is configured to support ProSe communications. In some examples, the core network service node may include a standard AMF within the core network that supports ProSe authorization and policy provisioning. In other examples, the core network service node may include a ProSe-specific AMF that is configured for ProSe registration and supports ProSe service access authorization functionality. For example, the above in combination Figure 8 The ProSe registration circuitry 844 , together with the communication and processing circuitry 842 and interface 810 , shown and described may provide a means for receiving a registration request.

[0122] At block 1204, the core network service node may obtain subscription information and context information (e.g., UE context) for the UE (e.g., from the UDM and / or old AMF in the core network). The subscription information may include proximity service (ProSe) subscription data indicating that the user equipment is configured to support ProSe communications. For example, the above combination Figure 8The ProSe registration circuitry 844 , together with the communication and processing circuitry 842 and interface 810 , as shown and described may provide a means for acquiring subscription information and context information for a user equipment.

[0123] At block 1206, the core network serving node may transmit a registration accept message including a ProSe support indication to the UE when the UE is authorized for ProSe operation. Figure 8 The illustrated and described ProSe registration circuitry 844 , together with the communication and processing circuitry 842 , the ProSe authorization circuitry 846 , and the interface 810 , may provide means for transmitting a registration accept message including a ProSe support indication to a UE.

[0124] Fig.13 1300 is a flow chart of a method for facilitating wireless communication at a core network service node within a core network. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and some of the illustrated features may not be required to implement all embodiments. In some examples, the method may be described above and in Figure 8 The core network service node 800 illustrated in FIG. 8 is executed by a processor or a processing system, or by any suitable device for performing the described functions.

[0125] At box 1302, the core network service node may receive a registration request for the UE from a base station. In some examples, the registration request includes a ProSe indication indicating that the user equipment supports ProSe communications. In other examples, the registration request includes a ProSe slice identifier indicating that the user equipment supports ProSe communications. In some examples, the ProSe slice identifier may include ProSe network slice selection assistance information (PS-NSSAI), which indicates to the core network service node that the UE is configured to support ProSe communications. In some examples, the core network service node may include a standard AMF within the core network that supports ProSe authorization and policy provisioning. In other examples, the core network service node may include a ProSe-specific AMF that is configured for ProSe registration and supports ProSe service access authorization functionality. For example, the above in combination Figure 8 The ProSe registration circuitry 844 , together with the communication and processing circuitry 842 and interface 810 , shown and described may provide a means for receiving a registration request.

[0126] At block 1304, the core network service node may obtain subscription information and context information (e.g., UE context) for the UE (e.g., from the UDM and / or old AMF in the core network). The subscription information may include proximity service (ProSe) subscription data indicating that the user equipment is configured to support ProSe communications. For example, the above Figure 8 The ProSe registration circuitry 844 , together with the communication and processing circuitry 842 and interface 810 , as shown and described may provide a means for acquiring subscription information and context information for a user equipment.

[0127] At block 1306, the core network serving node may determine that the user equipment is authorized for ProSe operation based on the ProSe subscription data and the context information. Figure 8 The illustrated and described ProSe authorization circuitry 846 may provide means for determining that a UE is authorized for ProSe operations.

[0128] At block 1308, the core network serving node may transmit a registration accept message including a ProSe support indication to the UE when the UE is authorized for ProSe operation. Figure 8 The illustrated and described ProSe registration circuitry 844 , together with the communication and processing circuitry 842 and interface 810 , may provide means for transmitting a registration accept message including a ProSe support indication to a UE.

[0129] Fig.14 1400 is a flow chart of a method for facilitating wireless communication at a core network service node within a core network. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and some of the illustrated features may not be required to implement all embodiments. In some examples, the method may be described above and in Figure 8 The core network service node 800 illustrated in FIG. 8 is executed by a processor or a processing system, or by any suitable device for performing the described functions.

[0130] At box 1402, the core network service node may receive a registration request for the UE from a base station. In some examples, the registration request includes a ProSe indication indicating that the user equipment supports ProSe communications. In other examples, the registration request includes a ProSe slice identifier indicating that the user equipment supports ProSe communications. In some examples, the ProSe slice identifier may include ProSe network slice selection assistance information (PS-NSSAI), which indicates to the core network service node that the UE is configured to support ProSe communications. In some examples, the core network service node may include a standard AMF within the core network that supports ProSe authorization and policy provisioning. In other examples, the core network service node may include a ProSe-specific AMF that is configured for ProSe registration and supports ProSe service access authorization functionality. For example, the above in combination Figure 8 The ProSe registration circuitry 844 , together with the communication and processing circuitry 842 and interface 810 , shown and described may provide a means for receiving a registration request.

[0131] At block 1404, the core network service node may obtain subscription information and context information (e.g., UE context) for the UE (e.g., from the UDM and / or old AMF in the core network). The subscription information may include proximity service (ProSe) subscription data indicating that the user equipment is configured to support ProSe communications. For example, the above combination Figure 8 The ProSe registration circuitry 844 , together with the communication and processing circuitry 842 and interface 810 , as shown and described may provide a means for acquiring subscription information and context information for a user equipment.

[0132] At block 1406, the core network service node may obtain ProSe policy information for the user equipment from a policy control function (PCF) within the core network. The ProSe policy information may include, for example, in-coverage ProSe policy information, out-of-coverage ProSe policy information, and / or partial coverage ProSe policy information. Figure 8 The illustrated and described ProSe authorization circuitry 846 , together with the ProSe policy association circuitry 848 , may provide means for acquiring ProSe policy information for a user equipment.

[0133] At block 1408, the core network serving node may transmit a registration acceptance message including a ProSe support indication and ProSe policy information to the UE when the UE is authorized for ProSe operation. Figure 8The illustrated and described ProSe registration circuitry 844 , together with the communication and processing circuitry 842 , the ProSe authorization circuitry 846 , the ProSe policy association circuitry 848 , and the interface 810 , may transmit a registration accept message including a ProSe support indication and ProSe policy information to the UE.

[0134] In one configuration, the core network service node 800 includes means for facilitating ProSe authorization and provisioning, as described in the present disclosure. In one aspect, the aforementioned means may be in Figure 8 The processor 804 shown in the figure is configured to perform the functions recited by the aforementioned means. On the other hand, the aforementioned means may be a circuit or any equipment configured to perform the functions recited by the aforementioned means.

[0135] Of course, in the above examples, the circuit system included in the processor 804 is provided only as an example, and other means for performing the described functions may be included in various aspects of the present disclosure, including but not limited to instructions stored in the computer-readable storage medium 806, or in Figure 1-5 Any of the descriptions and using, for example, Figure 12-14 Any other suitable equipment or means for implementing the described processes and / or algorithms.

[0136] An overview of various examples of the disclosure is provided below.

[0137] Example 1: A method for wireless communication at a user equipment, the method comprising: transmitting a message to a radio access network, the message comprising a registration request and a proximity service (ProSe) indication, wherein the ProSe indication indicates to the radio access network and a core network serving the radio access network that the user equipment is configured to support ProSe communication; receiving a registration accept message from the core network via the radio access network, wherein the registration accept message comprises the ProSe support indication; and initiating a ProSe session between the user equipment and another user equipment based on the ProSe support indication within the registration accept message.

[0138] Example 2: A method as in Example 1, wherein the registration acceptance message further includes ProSe policy information.

[0139] Example 3: The method as in Example 1 or 2, wherein initiating the ProSe session further includes: initiating the ProSe session based on the ProSe policy information.

[0140] Example 4: The method of any one of Examples 1 to 3, wherein the registration request includes the ProSe indication.

[0141] Example 5: The method of any one of Examples 1 to 3, wherein the message further includes an access network parameter including the ProSe indication:

[0142] Example 6: The method of Example 5, wherein the ProSe indication includes a ProSe slice identifier.

[0143] Example 7: A method as in Example 6, wherein the ProSe slice identifier includes ProSe network slice selection assistance information.

[0144] Example 8: The method of Example 5, wherein the ProSe indication includes a ProSe capability indication.

[0145] Example 9: The method of any one of Examples 1 to 8, wherein initiating the ProSe session further comprises: establishing the ProSe session over a ProSe PC5 interface.

[0146] Example 10: A user equipment (UE) in a wireless communication network, the UE comprising: a transceiver configured to communicate with a radio access network, a memory, a processor coupled to the transceiver and the memory, the processor and the memory being configured to execute a method as any one of Examples 1 to 9.

[0147] Example 11: A device configured for wireless communication, comprising at least one means for performing the method of any one of Examples 1 to 9.

[0148] Example 12: A non-transitory computer readable medium storing computer executable code, the computer executable code comprising code for causing an apparatus to perform the method of any one of Examples 1 to 9.

[0149] Example 13: A method for wireless communication at a base station, the method comprising: receiving a message from a user equipment, the message comprising a registration request and a proximity service (ProSe) indication, wherein the ProSe indication indicates to the base station that the user equipment is configured to support ProSe communication; selecting a core network service node within a core network that supports ProSe authorization and policy provisioning; forwarding the registration request to the core network service node; and forwarding a registration acceptance message from the core network service node to the user equipment, wherein the registration acceptance message includes the ProSe support indication.

[0150] Example 14: A method as in Example 13, wherein the core network service node includes access and mobility management functions within the core network.

[0151] Example 15: The method of Example 13, wherein the core network service node includes a ProSe access and mobility management function within the core network configured to support ProSe registration and ProSe service access authorization functions.

[0152] Example 16: The method of any one of Examples 13 to 15, wherein the registration request includes the ProSe indication.

[0153] Example 17: The method of any one of Examples 13 to 15, wherein the message further includes an access network parameter including the ProSe indication.

[0154] Example 18: The method of Example 17, wherein the ProSe indication includes a ProSe slice identifier.

[0155] Example 19: A method as in Example 18, wherein forwarding the registration request to the core network service node includes: modifying the registration request to include the ProSe slice identifier to generate a modified registration request; and forwarding the modified registration request to the core network service node.

[0156] Example 20: A base station in a wireless communication network, the base station comprising: a transceiver, a memory, a processor coupled to the transceiver and the memory, the processor and the memory being configured to perform a method as in any one of Examples 13 to 19.

[0157] Example 21: A device configured for wireless communication, comprising at least one device for performing any method of Examples 13 to 19.

[0158] Example 22: A non-transitory computer readable medium storing computer executable code, the computer executable code comprising code for causing an apparatus to perform the method of any one of Examples 13 to 19.

[0159] Example 23: A method for facilitating wireless communication at a core network service node within a core network, the method comprising: receiving a registration request for a user equipment from a base station; obtaining subscription information and context information for the user equipment, the subscription information including proximity service (ProSe) subscription data indicating that the user equipment is configured to support ProSe communication; and transmitting a registration acceptance message to the user equipment, wherein when the user equipment is authorized for ProSe operation, the registration acceptance message includes a ProSe support indication.

[0160] Example 24: The method of Example 23 further comprises: determining that the user equipment is authorized for ProSe operation based on the ProSe subscription data and the context information.

[0161] Example 25: A method as in Example 23 or 24, wherein the registration accept message further includes ProSe policy information.

[0162] Example 26: The method of Example 25, wherein the ProSe policy information includes at least one of in-coverage ProSe policy information, out-coverage ProSe policy information, or partial coverage ProSe policy information.

[0163] Example 27: The method of Example 25 or 26 further includes: obtaining the ProSe policy information for the user equipment from a policy control function (PCF) within the core network; and including the ProSe policy information in a registration acceptance message.

[0164] Example 28: The method of any one of Examples 23 to 27, wherein the core network serving node comprises an access and mobility management function within the core network.

[0165] Example 29: The method of any one of Examples 23 to 27, wherein the core network serving node comprises a ProSe access and mobility management function within the core network configured to support ProSe registration and ProSe service access authorization functionalities.

[0166] Example 30: The method of any one of Examples 23 to 29, wherein the registration request includes a ProSe indication indicating that the user equipment supports ProSe communications.

[0167] Example 31: A method as in any one of Examples 23 to 29, wherein the registration request includes a ProSe slice identifier indicating that the user equipment supports ProSe communication.

[0168] Example 32: A core network service node in a core network, the core network service node comprising: an interface, a memory, and a processor coupled to the transceiver and the memory, the processor and the memory being configured to perform a method as in any one of Examples 23 to 31.

[0169] Example 33: An apparatus in a core network, comprising at least one means for performing the method of any one of Examples 23 to 31.

[0170] Example 34: A non-transitory computer readable medium storing computer executable code, the computer executable code comprising code for causing an apparatus to perform the method of any one of Examples 23 to 31.

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

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

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

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

[0175] It should be understood that the specific order or hierarchy of steps in the disclosed methods is an illustration of an exemplary process. Based on design preferences, it should be understood that the specific order or hierarchy of steps in these methods can be rearranged. The attached method claims present elements of the various steps in a sample order and are not meant to be limited to the specific order or hierarchy presented unless specifically stated herein.

[0176] The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the universal principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the various aspects shown herein, but should be granted the full scope consistent with the language of the claims, wherein the singular reference to the element is not intended to mean "there is and only one" - unless specifically stated, but intended to mean "one or more". Unless specifically stated otherwise, the term "some / some" refers to one or more. The phrase "at least one of" a list of items refers to any combination of these items, including a single member. As an example, "at least one of a, b or c" is intended to cover: a; b; c; a and b; a and c; b and c; and a, b and c. The elements of the various aspects described throughout this disclosure are all structurally and functionally equivalent solutions currently or hereafter known to those of ordinary skill in the art, and are expressly incorporated herein by reference, and are intended to be covered by the claims. In addition, nothing disclosed herein is intended to be donated to the public, regardless of whether such disclosure is explicitly recorded in the claims.

Claims

1. A method for wireless communication at a user equipment, the method comprising: transmitting a message to a radio access network, the message comprising a registration request and a proximity service (ProSe) indication, wherein the ProSe indication indicates to the radio access network a core network serving the radio access network that the user equipment is configured to support ProSe communications; receiving a registration accept message from the core network via the radio access network, wherein the registration accept message includes a ProSe support indication and ProSe policy information, the ProSe policy information including at least one of in-coverage ProSe policy information, out-of-coverage ProSe policy information, or partial coverage ProSe policy information; as well as A ProSe session is initiated between the user equipment and another user equipment based on the ProSe support indication within the registration accept message.

2. The method of claim 1, wherein initiating the ProSe session further comprises: The ProSe session is initiated based on the ProSe policy information. 3 . The method of claim 1 , wherein the registration request includes the ProSe indication. 4 . The method of claim 1 , wherein the message further comprises access network parameters including the ProSe indication. The method of claim 4 , wherein the ProSe indication comprises a ProSe slice identifier.

6. The method of claim 5, wherein the ProSe slice identifier includes ProSe network slice selection assistance information. The method of claim 4 , wherein the ProSe indication comprises a ProSe capability indication.

8. The method of claim 1, wherein initiating the ProSe session further comprises: The ProSe session is established over the ProSe PC5 interface.

9. A user equipment UE in a wireless communication network, comprising: a transceiver configured to communicate with a radio access network; Memory; as well as a processor coupled to the transceiver and the memory, wherein the processor and the memory are configured to: transmitting, via the transceiver, a message to the radio access network, the message comprising a registration request and a proximity service (ProSe) indication, wherein the ProSe indication indicates to the radio access network a core network serving the radio access network that the user equipment is configured to support ProSe communications; receiving a registration accept message from the core network via the radio access network and the transceiver, wherein the registration accept message includes a ProSe support indication and ProSe policy information, the ProSe policy information including at least one of in-coverage ProSe policy information, out-of-coverage ProSe policy information, or partial coverage ProSe policy information; as well as A ProSe session is initiated between the user equipment and another user equipment based on the ProSe support indication within the registration accept message.

10. The UE of claim 9, wherein the processor and the memory are further configured to: The ProSe session is initiated based on the ProSe policy information.

11. The UE of claim 9, wherein the registration request includes the ProSe indication.

12. The UE of claim 9, wherein the message further comprises an access network parameter including the ProSe indication.

13. The UE of claim 12, wherein the ProSe indication comprises a ProSe slice identifier.

14. A method for wireless communication at a network element, the method comprising: receiving a message from a user equipment, the message comprising a registration request and a proximity service (ProSe) indication, wherein the ProSe indication indicates to the network element that the user equipment is configured to support ProSe communications; Select a core network service node in the core network that supports ProSe authorization and policy provisioning; Forwarding the registration request to the core network service node; as well as A registration accept message is forwarded from the core network service node to the user equipment, wherein the registration accept message includes a ProSe support indication and ProSe policy information, and the ProSe policy information includes at least one of in-coverage ProSe policy information, out-of-coverage ProSe policy information, or partial coverage ProSe policy information.

15. The method of claim 14, wherein the core network serving node comprises an access and mobility management function within the core network.

16. The method of claim 14, wherein the core network serving node comprises a ProSe access and mobility management function within the core network configured to support ProSe registration and ProSe service access authorization functionalities. The method of claim 14 , wherein the registration request includes the ProSe indication.

18. The method of claim 14, wherein the message further comprises access network parameters including the ProSe indication. The method of claim 18 , wherein the ProSe indication comprises a ProSe slice identifier.

20. The method of claim 19, wherein forwarding the registration request to the core network service node comprises: modifying the registration request to include the ProSe slice identifier to generate a modified registration request; as well as The modified registration request is forwarded to the core network service node.

21. A method for facilitating wireless communication at a core network serving node within a core network, the method comprising: receiving a registration request for user equipment from a network element; Acquire subscription information and context information for the user equipment, the subscription information comprising proximity service (ProSe) subscription data indicating that the user equipment is configured to support ProSe communication; as well as A registration accept message is transmitted to the user equipment, wherein when the user equipment is authorized for ProSe operation, the registration accept message includes a ProSe support indication and ProSe policy information, and the ProSe policy information includes at least one of in-coverage ProSe policy information, out-of-coverage ProSe policy information, or partial coverage ProSe policy information.

22. The method of claim 21, further comprising: It is determined based on the ProSe subscription data and the context information that the user equipment is authorized for ProSe operation.

23. The method of claim 21, further comprising: Acquire the ProSe policy information for the user equipment from a policy control function PCF in the core network; as well as The ProSe policy information is included in the registration acceptance message.

24. The method of claim 21, wherein the core network serving node comprises an access and mobility management function within the core network.

25. The method of claim 21, wherein the core network serving node comprises a ProSe access and mobility management function within the core network configured to support ProSe registration and ProSe service access authorization functionalities.

26. The method of claim 21, wherein the registration request comprises a ProSe indication indicating that the user equipment supports ProSe communication.

27. The method of claim 21, wherein the registration request includes a ProSe slice identifier indicating that the user equipment supports ProSe communication.

Images