WO2017082955A1

WO2017082955A1 - Enhanced direct ue communication

Info

Publication number: WO2017082955A1
Application number: PCT/US2016/030069
Authority: WO
Inventors: Dave Cavalcanti; Ana Lucia Pinheiro; Maruti Gupta
Original assignee: Intel Corporation
Priority date: 2015-11-09
Filing date: 2016-04-29
Publication date: 2017-05-18

Abstract

A gateway user equipment (UE) processes an internal D2D UE identifier and an external D2D UE identifier of a D2D UE, received from the D2D UE. The gateway UE can transmit to a Prose function of a wireless communication network, an intemal gateway UE identifier of the gateway UE and the internal D2D UE identifier and the external D2D UE identifier of the D2D UE to enable the wireless communication network and external entities to communicate with the D2D UE. The intemal gateway UE identifier and the internal D2D identifier enables the D2D UE to be addressed and registered. The external D2D UE identifier enables the D2D UE to be address by the external entities. The gateway UE can relay communication messages between the D2D UE and the wireless communication network and external entities.

Description

ENHANCED DIRECT UE COMMUNICATION

RELATED APPLICATIONS

[0001] This application claims the benefit of and hereby incorporates by reference U.S. Provisional Patent Application Serial No. 62/253,028 filed November 9, 2015, with a docket number P94086Z.

BACKGROUND

[0002] Wireless mobile communication technology uses various standards and protocols to transmit data between a node (e.g., a transmission station) and a wireless device (e.g., a mobile device). Some wireless devices communicate using orthogonal frequency-division multiple access (OFDMA) in a downlink (DL) transmission and single carrier frequency division multiple access (SC-FDMA) in an uplink (UL) transmission. Standards and protocols that use orthogonal frequency-division multiplexing (OFDM) for signal transmission include the third generation partnership project (3 GPP) long term evolution (LTE), the Institute of Electrical and Electronics Engineers (IEEE) 802.16 standard (e.g., 802.16e, 802.16m), which is commonly known to industry groups as WiMAX

(Worldwide interoperability for Microwave Access), and the IEEE 802.11 standard, which is commonly known to industry groups as Wi-Fi. In 3GPP radio access network (RAN) LTE systems, the node can be a combination of Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node Bs (also commonly denoted as evolved Node Bs, enhanced Node Bs, eNodeBs, or eNBs) and Radio Network Controllers (RNCs), which communicates with the wireless device, known as a user equipment (UE). The downlink (DL) transmission can be a communication from the node (e.g., eNodeB) to the wireless device (e.g., UE), and the uplink (UL) transmission can be a communication from the wireless device to the node.

[0003] In addition, Internet of things (IoT) devices employing wireless communication systems and methods (e.g., cellular telephones, mobile computers and other mobile and fixed location devices) are increasingly prevalent. The increase in number of mobile devices has increased the capacity demand and load on cellular networks. However, current scalability, deployment, functionality, and protocols for communication between IoT devices (e.g., device to device "D2D" communication) can be inefficient to meet the current demands. Thus, a desire exits for a solution to provide functionality and protocols scalable and efficient to meet the constraints for communication between the IoT devices and/or communication between the IoT devices and a wireless communication network.

BRIEF DESCRIPTION OF THE DRAWINGS

[0004] Features and advantages of the disclosure will be apparent from the detailed description which follows, taken in conjunction with the accompanying drawings, which together illustrate, by way of example, features of the disclosure; and, wherein:

[0005] FIG. 1 depicts an illustrative wireless communications system in accordance with an example;

[0006] FIG. 2 illustrates a proximity service (ProSe) architecture and interfaces in accordance with an example;

[0007] FIG. 3 illustrates a proximity services (ProSe) protocol for direct discovery communication over media access control (MAC) and physical (PHY) layers in accordance in accordance with an example;

[0008] FIG. 4 illustrates triggering a machine type communication (MTC) UE by an application server in accordance with an example;

[0009] FIG. 5 illustrates a PC5-only UE registration procedure in accordance in accordance with an example;

[0010] FIG. 6 illustrates a gateway UE supporting direct device-to-device communication within a wireless communication network;

[0011] FIG. 7 depicts functionality of a ProSe function of a core network to support direct device-to-device communication within a wireless communication network in accordance with an example;

[0012] FIG. 8 depicts functionality of gateway user equipment (UE) operable to support direct device-to-device communication within a wireless communication network in accordance with an example;

[0013] FIG. 9 depicts functionality of a relay user equipment (UE) operable to support direct device-to-device communication within a wireless communication network in accordance with an example;

[0014] FIG. 10 illustrates a diagram of example components of a wireless device (e.g. User Equipment "UE") device in accordance with an example;

[0015] FIG. 11 illustrates a diagram of example components of a User Equipment (UE) device in accordance with an example;

[0016] FIG. 12 illustrates a diagram of a node (e.g., eNB) and wireless device (e.g., UE) in accordance with an example; and

[0017] FIG. 13 is a block diagram that provides an example illustration of a computing device that may be employed in the present technology.

[0018] Reference will now be made to the exemplary embodiments illustrated, and specific language will be used herein to describe the same. It will nevertheless be understood that no limitation of the scope of the technology is thereby intended. DETAILED DESCRIPTION

[0019] Before the present technology is disclosed and described, it is to be understood that this technology is not limited to the particular structures, process actions, or materials disclosed herein, but is extended to equivalents thereof as would be recognized by those ordinarily skilled in the relevant arts. It should also be understood that terminology employed herein is used for the purpose of describing particular examples only and is not intended to be limiting. The same reference numerals in different drawings represent the same element. Numbers provided in flow charts and processes are provided for clarity in illustrating actions and operations and do not necessarily indicate a particular order or sequence.

EXAMPLE EMBODIMENTS

[0020] An initial overview of technology embodiments is provided below and then specific technology embodiments are described in further detail later. This initial summary is intended to aid readers in understanding the technology more quickly but is not intended to identify key features or essential features of the technology nor is it intended to limit the scope of the claimed subject matter.

[0021] In one aspect, Internet of things (IoT) devices can be physical objects, such as devices, vehicles, buildings, and or other items embedded with electronics, software, sensors, and/or network connectivity that enables the physical objects to collect, processes, and/or exchange data. In one aspect, the IoT devices can be sensed and/or controlled remotely across one or more network infrastructures, to more directly integrate the physical world into computer-based systems. For example, IoT devices can connect and/or be used in vehicles, homes, wearable devices (e.g., smart wearables), objects or systems of virtual computing networks/storage systems, industries, and/or businesses. In short, "IoT" can refer to a network of physical objects that can communicate between each other and also connect with one or more external networks, such as through a gateway device. The external connectivity can occur over a cellular network, but it can also be a Wi-Fi network, or other wireless infrastructure.

[0022] In one aspect, IoT devices can provide low-cost/low-power devices and communicate within a limited range. For instance, a smart wearable IoT device can consist of resource constrained devices (e.g. sensors) sending data to a personal data aggregation hub (e.g., a smart phone) within a short coverage area. Wireless sensors in home automation systems and/or within vehicles can also send data to a gateway device, such as a gateway user equipment (UE). Accordingly, Device to Device (D2D) communications can be used in IoT device communication to improve spectrum utilization, and achieve latency and low power use. D2D communication can refer to the communications of users in cellular networks without a base station (BS) intervention and/or with reduced BS intervention. For example, a UE can communicate with another UE via a base station. Alternatively, the UEs may communicate directly by applying network resources dedicated by a cellular network for a device-to-device (D2D) communication. The D2D communication can improve network efficiency by offloading data traffic processed in the BS, for example. In one aspect, a UE can be an IoT device.

[0023] In one aspect, resource constrained IoT devices can communicate with a gateway (e.g., smart phone, vehicular gateway, or gateway device (e.g., a gateway UE, etc.) on a limited basis. For instance, an IoT device may communicate with a gateway UE to send data and receive control commands/requests. The gateway device can be responsible for managing and controlling the operation of the IoT devices, as illustrated in the example of FIG. 1.

[0024] FIG. 1 illustrates a PC5 interface between two UEs to enable D2D communication between the UEs. In one embodiment, one of the UEs may be an IoT device. The IoT device can be configured to implement a PC5 communication interface (e.g., "PC5 only UEs"), which can be used to communicate with a gateway UE operating as a Network Relay (NR) using the procedure defined for out of coverage scenarios defined in the 3GPP LTE specification, such as Rel. 12. In one aspect, multiple PC5 only UEs can connect through a single gateway UE. A PC5 only UE is a UE that can communicate with a 3GPP network only via a PC5 connection with a gateway UE. In one embodiment, a PC5 only UE can change its association between gateway UEs based on the gateway UE with which the PC5 only UE can communicate. In one aspect, the PC5 only UE can be a D2D only UE, which can be a direct communication only UE (e.g., PC5-only UE = D2D-only UE = Direct-communication-only UE).

[0025] Currently, however, third generation partnership project (3 GPP) long term evolution (LTE) networks, such as 3GPP LTE Rel. 12 networks, are unable to trigger a PC5 only UE connected to a gateway UE on the downlink (DL). Current 3GPP LTE networks have one or more technological problems and limitations. For example, 3GPP LTE networks are unable to map an external D2D UE identifier (ID) of the PC5-only UE to the Gateway UE. In fact, there is no concept of subscription for PC5- only UEs with the network. Also, due to the absence of any mapping, multiple PC5-only UEs are unable to be connected to a single Gateway UE. For example, multiple wearable IoT devices currently cannot use the same Gateway UE based on 3GPP LTE Rel. 12. Furthermore, current 3GPP LTE networks are unable to support a PC5-only UE to change its association from one gateway UE to another gateway UE (i.e. handover from one gateway UE to another). In one aspect, the handover between gateways can be the UE changing its association and access point from one access point to another access point.

[0026] Accordingly, the present technology provides a solution for a gateway user equipment (UE) to support direct device-to-device communication within a wireless communication network. The gateway UE can process at the gateway UE, an internal D2D UE identifier and an external D2D UE identifier of a D2D UE, received from the D2D UE. The gateway UE can signal a transceiver at the gateway UE, to transmit, to a Prose function of the wireless communication network, an internal gateway UE identifier of the gateway UE and the internal D2D UE identifier and the external D2D UE identifier of the D2D UE to enable the wireless communication network and one or more external entities to communicate with the D2D UE, wherein the internal gateway UE identifier and the internal D2D identifier enable the D2D UE to be addressed and registered with the wireless communication network. The external D2D UE identifier enables the D2D UE to be addressed by the one or more external entities that are external to the wireless communication network. The gateway UE can relay one or more communication messages between the D2D UE, one or more of the wireless communication networks, and the one or more external entities.

[0027] In one aspect, the present technology provides for a proximity service (ProSe) function of a core network. The ProSe function can process, at the ProSe function, an internal device-to-device (D2D) user equipment (UE) identifier of one or more D2D UEs, an external D2D UE identifier of the one or more D2D UEs, and an internal relay UE identifier, received from a relay UE to enable the core network and one or more external entities to communicate with the one or more D2D UEs. In one embodiment, the internal relay UE identifier and the internal D2D identifier can enable the one or more D2D UEs to be addressed and registered with the wireless communication network. The external D2D UE identifier enables the one or more D2D UEs to be address by the one or more external entities that are external to the wireless communication network. The ProSe function can communicate one or more communication messages via the relay UE to the one or more D2D UEs.

[0028] In one aspect, the present technology provides for a relay user equipment (UE) to support direct device-to-device communication within a wireless communication network. The relay UE can process at the relay UE, an internal D2D UE identifier and an external D2D UE identifier of a D2D UE, received from one or more D2D UEs. The relay UE can signal a transceiver at the relay UE, to transmit to the wireless communication network, an internal relay UE identifier of the relay UE and the internal D2D UE identifier and the external D2D UE identifier of the one or more D2D UEs to enable the wireless communication network and one or more external entities to communicate with the one or more D2D UEs. The relay UE can relay one or more communication messages between the one or more D2D UEs and one or more of the wireless communication network and the one or more external entities.

[0029] In one aspect, in a third generation partnership project (3 GPP) long term evolution (LTE) configured communication system, D2D communications can be supported through the PC5 interface between UEs, as shown in FIG. 1. FIG. 1 depicts a communication system 100 for one or more IoT devices, such as, for example, IoT devices (e.g., UE la or UE lb) associated with vehicles, persons (e.g., wearable UE's), homes, industries, and/or business etc. As depicted, the communication system 100 can include one or more UEs, such as UE la or UE lb, each having communication with a relay UE (e.g., UE 2). In one aspect, the communication system 100 can include one or more UEs, such as UE la or UE lb, which can communicate with one or more relay UEs, such as UE 2 via a PC5 interface. In one aspect, the relay UE can communicate with a core network (e.g., a 3GPP LTE network) via one or more network interfaces. The relay UE can relay information between the network and the PC5 UEs, such as UE la or UE lb.

[0030] Turning now to FIG. 2, a public land mobile network (PLMN) architecture is depicted. FIG. 2 depicts a Proximity-based Service (ProSe) communication system 200 developed as a technology which allows UEs to directly communicate with each other in close proximity without transmitting/receiving data and/or control signals via an eNB. The direct communication provides a local or direct path can be used between the UEs. That is, FIG. 2 depicts a ProSe application, user equipment (UE) A, UE B, a mobility management unit (MME), an evolved universal terrestrial radio access network (E- UTRAN), a ProSe function, a subscriber servicer (HSS), a Location Platform (SLP), a ProSe application server, and serving gateway (SGW) and/or a packet data network

(PDN) gateway (PGW) (e.g., S/P-GW), and one or more communication interfaces, such as, for example, LTE-Uu, SI, S6a, PC4a, PC4b, PCI, PC2, and PC3.

[0031] The ProSe function can be a logical function that can be used for network related actions configured for ProSe. The ProSe function can play different roles for each of the features of ProSe. PCI can be a reference point between the ProSe application in the UE and in the ProSe Application Server. PCI can be used to define application level signaling constraints. PC2 can be reference point between the ProSe Application Server and the ProSe Function. PC2 can be used to define the interaction between ProSe Application Server and ProSe functionality provided by the 3GPP EPS via ProSe Function (e.g. name translation) for an evolved packet core (EPC)-level ProSe discovery. PC3 can be a reference point between the UE and the ProSe Function. PC3 can rely on an EPC user plane for transport (i.e. an "over internet protocol (IP)" reference point). It is used to authorize ProSe Direct Discovery and EPC-level ProSe Discovery requests, and perform allocation of ProSe Application Codes corresponding to ProSe Application Identities used for ProSe Direct Discovery. PC3 can be used to define the authorization policy per PLMN for ProSe Direct Discovery (for Public Safety and non-Public Safety) and communication (for Public Safety only) between UE and ProSe Function. PC4a can be reference point between the HSS and ProSe Function. PC4a can be used to provide subscription information in order to authorize access for ProSe Direct Discovery and ProSe Direct Communication on a per PLMN basis. PC4a can also be used by the ProSe Function (i.e. EPC-level ProSe Discovery Function) for retrieval of EPC-level ProSe Discovery related subscriber data.

[0032] PC4b can be a reference point between a secure user plane location (SUPL) Location Platform (SLP) and the ProSe Function. PC4b can be used by the ProSe Function (i.e. EPC-level ProSe Discovery Function) (in the role of LCS client to query the SLP). PC5 can be a reference point between ProSe-enabled UEs used for control and user plane for ProSe Direct Discovery, ProSe Direct Communication and ProSe UE-to- Network Relay.

[0033] In addition to the relevant functions defined in 3 GPP TS 23.401 Rel. 12 for S6a, ProSe S6a can be used to download ProSe related subscription information to mobility management unit (MME) during evolved universal terrestrial radio access network (E- UTRAN) attach procedure or to inform the MME subscription information in the HSS has changed. In addition to the relevant functions defined in 3GPP TS 23.401 Rel. 12 for Sl-MME, ProSe Sl-MME can be also used to provide an indication to eNB that the UE is authorized to use ProSe Direct Discovery.

[0034] In one aspect, the PC5 interface can be a new communication interface (PC5) that enables direct discovery, control signaling and data communication between one or more UE's, such as UE A and UE B, both of which may be an IoT UE device (e.g., "wearable IoTs", "utility IoTs, "home device IoTs", and so forth). Direct discovery can be based on short messages exchanges between UEs, such as UE A and UE B that can be defined by a ProSe Protocol, and carried directly over a media access control (MAC) layer and a physical (PHY) layer, as illustrated in FIG. 3.

[0035] FIG. 3 illustrates a proximity services (ProSe) architecture and interfaces for enhanced proximity services (ProSe) protocols for D2D communication between IoT UE devices and gateway UEs. The ProSe architecture also enables direct D2D

communication with multiple IoT devices within a wireless communication network.

[0036] In one aspect, the PC5 interface provides direct data communication between

UEs, such as UE A and UE B. The direct data communication can be carried over a user- plane stack, which includes an internet protocol (IP), a packet data convergence protocol (PDCP), a radio resource control (RRC), the MAC layer, and the PHY layer. A new ProSe Function can be provided in a Core Network (CN) to control and configure how UEs use the new PC5 interface. A ProSe application on the UE can communicate with the ProSe Function over the PC3 reference point, which relies on the EPC user plane for transport (i.e. an "over IP" reference point). In one aspect, the 3GPP LTE ProSe architecture can ensure the UE's communication over the PC5 is always under control of the network through the ProSe Function.

[0037] It should be noted, as described herein, a "PC5 only UE" can be referred to as a "wearable UE" (wUE) and the gateway device may be referred to as gateway user equipment "gUE". However, although the PC5 only UE can be referred to as a wUE as described herein, it should be noted that the example embodiments described herein may apply to other types of UEs as well, as previously described.

[0038] Turning now to FIG. 4, FIG. 4 depicts a flow chart example for triggering a machine type communication (MTC) UE, such as an IoT UE, by an application server. In one aspect, the MTC UE can be a UE that can be used for IOT applications and which may have different capabilities than a 3GPP LTE UE. For instance, a MTC UE can require low power consumption and the MTC UE can operate with limited data rates. The MTC UE can still access the network through the eNB as well as accessing other UEs.

[0039] In one aspect, device Triggering can be constrained to be performed when an internet protocol (IP) address for the UE is unavailable and/or unreachable by a service capability server (SCS) and/or application server (AS). Therefore, it can be assumed that the device's IP is unknown. In one aspect, the application server can know the device through an external identification (ID) of the device, which can have 2 components in the following form: "Local_Name@Domain Name". It should be noted that a device can be constrained to subscribe to a triggering service. In so doing, the external ID along with an international mobile subscriber identity (IMSI) of the device can be stored in a home subscriber server (HSS). However, only one external D2D UE identifier can be mapped to an IMSI. In one aspect, the subscription can be used for MTC that has one IMSI and may have one or several External D2D UE identifier(s) that are stored in the HSS.

[0040] Thus, as described in FIG. 4, an AS can use the external ID to request service from a Service Capability Server (SCS). The SCS can look up a corresponding inter- working function (IWF) function over a telecommunications service provider (TSP) to send the request. The IWF can determine a mapping to an internal ID by querying the HSS on the external ID, check whether the trigger request by the SCS is authorized, and/or determine mobility management entity (MME) information. The IWF can then send the trigger request to the mobility management entity (MME) using the internal ID (i.e., IMSI) and can also send the trigger payload to the MME over a T5 interface. In one aspect, the MME can look up the current location of the UE. If the UE is in PSM (power save mode), the MME can wait. If the UE is in an idle mode, the MME can page the current location of the UE and if the UE is in connected mode, the MME can forward the trigger payload to an eNB.

[0041] In one aspect, an Application Port ID can be inserted into the trigger payload to identify which application the payload is directed to. The Application Port ID can be a 16- bit integer and can be the same as TCP/UDP port #s.

[0042] Thus, in summary, FIG. 4 can perform the following operations. 1. The SCS can query a domain name system (DNS). 2. The SCS can issue a device trigger request to the MTC -IWF. 3. The MTC-IWF can perform authorization and load control. 4. The MTC- IWF can issue to the home subscriber service/home local register (HSS/HLR) a subscriber information request. 5. The HSS/HLR can respond to the MTC-IWF with a subscriber information response. 6a. The MTC-IWF can trigger delivery selection. As illustrated in block A, a T5 device trigger delivery procedure can occur. 6b. The MTC- IWF can perform T5 failure or a T4 delivery selection. As illustrated in block B, the T4 device trigger delivery procedure can occur. 7. The MTC-IWF can issue to the SCS a device trigger report. 8. As illustrated in block 8, an action can be performed in response to the device trigger.

[0043] In one aspect, the present technology provides a solution for triggering of UEs through a gateway UE by external application servers when the UE is an IoT device, such as a wearable UE. The IoT device can be a PC5-only UE that is configured to connect to a wireless cellular network via a gateway UE. In one aspect, the present technology 1) identifies the PC5 only UE (both internally and externally), 2) communicates with the UE behind the gateway UE; and/or 3) supports mobility of PC5 only UEs between gateways. In one aspect, the PC5-only UE can support and enable short-range and power optimized connectivity while improving spectrum utilization. The gateway UE manages registration, authentication and service set up. The gateway UE also provides synchronization and control signaling to enable channel access. PC5-only UEs may use resource pools allocated to D2D under control of the gateway UE.

PC5 only UE Registration

[0044] In one aspect, once a UE connected via a PC5 gateway (i.e. a PC5 only UE) is identified, the PC5 only UE can establish a link connection with the PC5 gateway UE, which can include an exchange of security parameters, and send a registration request to a proximity services (ProSe) function via the PC5 gateway UE. The PC5-only UE registration procedure is depicted in FIG. 5.

[0045] Using one or more of the features and embodiments as described in FIG. 2, FIG. 5 illustrates a communication system 500 that can include a ProSe application, a relay or gateway UE (e.g. "UE" of FIG. 5), and one or more ProSe only UE (e.g., PC5-only UE, wearable UEs, a "wUE" of FIG. 5), a mobility management entity (MME), an E- UTRAN, a ProSe function, an HSS, a ProSe application server, a serving gateway (SGW) and a packet data network (PDN) gateway (PGW) (e.g., S/P-GW), a PCRF (Policy and Charging Rules Function), an SGSN (Serving GPRS (General Packet Radio Service) Support Node), a Global System for Mobile Communications (GSM)

Enhanced Data Rates for GSM Evolution (EDGE) Radio Access Network (RAN) universal terrestrial radio access network (GERAN), an operator's IP services, and one or more communication interfaces, such as, for example, LTE-Uu, Sl-U, S3, S4, S6a, S10, Sll, S 12, SGi, Gx, Rx, and/or a PC-5.

[0046] In one aspect, the E-UTRAN can exchange information or commands with the Serving Gateway by means of an S l-U interface. The Serving Gateway can be coupled to the PDN Gateway by means of an S 5 interface. The PDN Gateway and the PCRF can access IP (Internet Protocol) services (i.e. may access, for example, corresponding servers) provided by the operator of the communication system by means of an SGi interface and an Rx interface, respectively. The PCRF can be coupled to the PDN Gateway by means of a Gx interface. The Serving Gateway can be coupled by means of an S4 interface with the SGSN. The Serving Gateway can further be coupled to a UTRAN via an S12 interface. The MME can be coupled by means of an S6a interface with the HSS. The MME can further coupled by means of an S I -MME interface to the E-UTRAN. The SGSN can support legacy access to the UTRAN and/or a GERAN. The SGSN can be coupled with the MME via an S3 interface. The Serving Gateway can be coupled with the MME via an Sl l interface. In one aspect, the ProSe function can be included in the ProSe server. One or more external entities can be in communication with the PDN gateway. Thus, one or more external entities can communicate with one or more wearable UEs via the relay and/or gateway UE, which is in communication with the E-UTRAN and serving gateway /PDN gateway.

[0047] Accordingly, in one aspect, the PC5-only UE registration procedure can occur as follows. 1. A wearable UE (such as a PC5 only UE) can send to a gateway UE a ProSe registration request via the PC-5 communication interface. 2. The gateway UE can forward the registration request to an eNB (e.g., the E-UTRAN or radio access node "RAN" node) via the LTE-Uu interface. 3. The eNB (e.g., the E-UTRAN or radio access node "RAN" node) can forward the registration request to the ProSe Function via the serving gateway /PDN gateway. 4. The ProSe function can process the registration request and generate a response. 5. The ProSe function can send, via the serving gateway /PDN gateway, the response to the RAN node to be forwarded to the destination UE (e.g., the wearable UE or "PC5 only UE). 6. The RAN node can send the response to the gateway UE. 7. The gateway UE can send the respond to the destination UE (e.g., a wUE) via the PC-5 communication interface.

PC5 only UE - Gateway association registration with ProSe and HSS

[0048] In one aspect, the PC5 only UEs can associate with a gateway UE and can register their (e.g., the PC5 only UE) association with the proximity services (ProSe) function. For this registration to occur, the PC5 only UE can be granted two identifiers, 2) an internal D2D UE identifier that allows the PC5 only UE to be addressed within a core network (e.g., a wireless communication network) and 2) an external D2D UE identifier that allows the PC5 only UE to be addressed by entities external to the core network, such as an application server of the internet. Also, if the PC5 only UE does not have an external IP address, then the PC5 only UE can also contain a mapping to a valid Gateway or network relay (NR) device by which it may be reached.

PC5 only UE triggering for PL communication from external server

[0049] In one aspect, for PC5 only UE triggering for DL communication from an external server, consider the following examples.

Case 1: The UE behind the Gateway is a PC5 only UE.

[0050] In one aspect, in order for the core network to be able to reach a PC5 only UE, such as a wUE, an internal D2D UE identifier can be used. The internal D2D UE identifier can be a unique UE identity, such as an IMSI used in 3GPP LTE Rel. 12. The internal D2D UE identifier can be part of the UE subscription. The wUE can also be associated with an external D2D UE identifier. The external D2D UE identifier can be used by external application servers to communicate with the wUE. In one aspect, within an MTC architecture, these two identifiers can be linked. However, the core network is constrained to know the internal D2D UE identifier of the gUE that is to be used to communicate with the wUE. In order to obtain this information, the following embodiments can be used.

[0051] In one aspect, the wUE can register with the core network and can inform the core network where the wUE is currently located (i.e., using the internal D2D UE identifier of the gUE). This registration process can be an attach procedure used in 3GPP LTE defined protocols. When the wUE moves between two gateway UEs (gUEs), a location update procedure can be performed, such as by using a tracking area update procedure. However, rather than updating a tracking area, the wUE can update the gateway information (e.g., the internal D2D UE identifier of the gUE) so as to enable the network to know the location of the wUE at any given point in time.

[0052] In an additional aspect, the wUE can "register" or "associate" with the gUE. When a wUE associates with a gUE, the gateway UE can provide the information to the core network. If the wUE moves or transitions to an alternative gUE, the new gUE can update the information with the core network. In this way, the network can know the location of the wUE at any point in time, whenever the wUE is attached to the core network.

[0053] In one aspect, the information about the linkage between the wUE and gUE can be maintained and store in a database of the network. For example, the information can be maintained in the MTC-interworking function (IWF), in the ProSe Function, in the MME, and/or in the HSS. Optionally a new network node can be created to store the information. The database is then consulted when an external entity requests to trigger the wUE.

[0054] Turning now to FIG. 6, a gateway UE supporting direct device-to-device communication within a wireless communication network is depicted. As depicted in FIG. 6, one or more of the following can be performed. 1. An initial communication can occur between a PC5 only UE (e.g., UE 2) and a UE Relay / gateway UE (e.g., UE 1). Ongoing communication can occur between UE 1 and UE 2 over a PC5 communication interface. 2. The gateway UE (e.g., UE 1) can register with a ProSe function/ wireless communication network and/or notify the Prose function of the PC5 only UE (e.g., UE 1) 3a. The ProSe function can issue a trigger message (e.g., a dedicated message) to the gateway UE (UE 1) indicating intent and/or requesting to communicate with the PC5 only UE (UE 2). It should be noted that one or more external entities may also request and/or have intent to communicate with the PC5 only UE (e.g., UE2). Thus, the External Entity can 3b) send a trigger message to the core network (CN) to indicate an intent and/or request to communicate with the PC5 only UE. The core network can then execute 3A and send the relay/gateway UE the triggering message (e.g., dedicated message) requesting to communicate with the PC5 only UE.

[0055] A timer may be started with an "allowed delay in response" time granted in the message. The "allowed delay in response" can be a selected period of time granted by the core network for receiving a response from the gateway UE regarding successful and/or unsuccessful delivery of the trigger message by the gateway UE to the PC5 only UE. 4. The gateway UE (UE 1) can send to the core network failure notification indicating the gateway UE (UE 1) failed to communicate with the PC5 only UE (UE 2). For example, if a selected time period of the timer expires prior to the PC5 only UE (UE 2) commences a next communication, the gateway UE (UE 1) can send to the core network a response indicating the gateway UE failed to contact the PC5 only UE (e.g., delivery of the trigger message by the gateway UE to the PC5 only UE failed). 5.

Communication can re-start between the PC5 only UE (e.g., UE 2) and the UE Relay / gateway UE (e.g., UE 1). Ongoing communication can once again occur between UE 1 and UE 2 over a PC5 communication interface. It should also be noted that the communication between an external entity and the PC5 only UE can be considered successful if there is a session between the two UEs (e.g., UE2 and UE1) before the timer expires, which can assume the packet is successfully delivered.

[0056] In summary, FIG. 6 illustrates that the first time both UEs, such as UE 1 and UE 2, communicate over a PC5 interface, the gUE (e.g., UE 1) can inform the network and/or ProSe function that the wUE (e.g., UE 2) is nearby and communication over PC5 can occur. Later, if the core network wants to communicate with the wUE, the core network can send a trigger message to the gUE (UE 1) to trigger the connection with wUE (UE 2). In this case, there are 2 scenarios possible. It should be note, as described herein, there can be 3 possible scenarios. 1). The gUE and the PC5 only UE have an active connection (i.e., they are communicating over a PC5 communication interface when the gUE receives a trigger from an external entity. In this case, the data packet can be delivered to the PC5 UE as part of the ongoing active connection session. 2. The gUE knows and is aware there is a PC UE using the gUE as gateway, but the PC5 UE is operating in a power saving mode so the gUE is unable to send a packet to the PC5 UE right away. In this case, the gUE waits for a selected period of time and if the PC5 UE awakes and connects back to the gUE prior to the timer expires, the packet can be delivered. 3: Same scenario as 2, but the timer expires before PC5 UE wakes up, so the delivery fails. [0057] It should be noted that FIG. 6 depicts the delivery of data from the external entity to the UE through the gUE (UE 1). However, although FIG. 6 is the registration process is not specifically described herein, it should be note that the registration process can be assumed to apply to FIG. 6. For example, as indicated above in 2 (e.g., step 2 referring to the gateway UE (e.g., UE 1) registering with a ProSe function/ wireless

communication network and/or notify the Prose function of the PC5 only UE), the gateway UE can update the CN with information about the PC5-only UE, but if the PC5- only UE has already registered with the gUE, this update may not be essential. In one aspect, the registration process can be constrained in the first time UE 1 and UE2 associate with each other and can periodically maintain and update the information in the CN. Also, FIG. 6 depicts one case where the packet is not delivered. FIG. 6 can also apply to one or more cases where one or more packet delivery is successful, as described herein.

[0058] In one aspect, the gUE can be actively connected to the wUE. When the gUE receives the trigger message from the core network, the gUE can identify which wUE is being triggered and can send the trigger message to the wUE. It should be noted there can be a mapping of the external ID to the gUE and the internal ID of the wUE. The gUE can identify the wUE being triggered and can be aware the PC5 only UE is in a power-saving mode (PSM). The gUE can wait to forward the triggering message until the wUE wakes up when the wUE is in the PSM. When the gUE has successfully triggered the wUE (for example, by receiving an acknowledgement message back from wUE), then the gUE can notify the network that the PC5 link to the wUE has been established, and thus, messages between the network and the wUE can be relayed by the gUE. If the wUE fails to start communicating over PC5 within a defined time of the gUE sending the wUE the triggering message, then the core network can be notified that the gUE was unable to trigger the wUE. This procedure, for example, can be particularly useful if messages are not delay sensitive and/or if the wUE periodically checks with the gUE if there are any pending messages, as described in FIG. 6

Case 2: UE behind the Gateway is a non-3GPP UE

[0059] In one aspect, for a wUE communicating to a gUE using a non-3GPP interface, such as, for example, a 802.11/Wi-Fi and/or Bluetooth, a core network can be enabled to contact the wUE via the 3GPP network. Thus, in one aspect, an internal D2D UE identifier previously used cannot be the same type of identifier, such as an internal gateway UE identifier of the gUE. For example, in 3GPP LTE, the internal D2D UE identifier can be an IMSI. However, the Wi-Fi only device does not have an IMSI.

Accordingly, the wUE can register with the gUE using a media access control (MAC) address of the wUE and an external D2D UE identifier can be used by the wUE. The gUE can map the MAC address to the external D2D UE identifier and can register the wUE with the network using the external D2D UE identifier of the wUE. In one aspect, the external D2D UE identifier can have a form of "Name@Domain". When one or more external entities (e.g., external entities outside the core network) want to trigger one or more selected wUEs, the core network can use the external D2D UE identifier. The core network is able to identify, locate, and know that the external D2D UE identifier maps to a given gUE, and can trigger the one or more selected wUEs by contacting the gUE.

[0060] Another example provides functionality 700 of a proximity service (ProSe) function of a core network, as shown in the flow chart in FIG. 7. The functionality can be implemented as a method or the functionality can be executed as instructions on a machine, where the instructions are included one or more computer readable mediums or one or more transitory or non-transitory machine readable storage mediums. The ProSe function can comprise one or more processors and memory configured to: process, at the ProSe function, an internal device-to-device (D2D) user equipment (UE)identifier of one or more D2D UEs, an external D2D UE identifier of the one or more D2D UEs, and an internal relay UE identifier, received from a relay UE to enable the core network and one or more external entities to communicate with the one or more D2D UEs, wherein: the internal relay UE identifier and the internal D2D identifier enables the one or more D2D UEs to be addressed and registered with the wireless communication network, and the external D2D UE identifier enables the one or more D2D UEs to be addressed by the one or more external entities that are external to the wireless communication network, as in block 710. In one aspect, the ProSe function is included in a ProSe function server that includes the one or more processors and memory. The ProSe function can comprise one or more processors and memory configured to: communicate one or more communication messages via the relay UE to the one or more D2D UEs, as in block 720. [0061] Another example provides functionality 800 of gateway user equipment (UE) operable to support direct device-to-device communication within a wireless

communication network, as shown in the flow chart in FIG. 8. The functionality can be implemented as a method or the functionality can be executed as instructions on a machine, where the instructions are included one or more computer readable mediums or one or more transitory or non-transitory machine readable storage mediums. The gateway UE can comprise one or more processors and memory configured to: process at the gateway UE, an intemal D2D UE identifier and an external D2D UE identifier of a D2D UE, received from the D2D UE, as in block 810. The gateway UE can comprise one or more processors and memory configured to: signal a transceiver at the gateway UE, to transmit to a Prose function of the wireless communication network, an intemal gateway UE identifier of the gateway UE and the intemal D2D UE identifier and the external D2D UE identifier of the D2D UE to enable the wireless communication network and one or more external entities to communicate with the D2D UE, wherein the internal gateway UE identifier and the internal D2D identifier enables the D2D UE to be addressed and registered with the wireless communication network, and the external D2D UE identifier enables the D2D UE to be address by the one or more extemal entities that are external to the wireless communication network, as in block 820. The gateway UE can comprise one or more processors and memory configured to: relay one or more communication messages between the D2D UE and one or more of the wireless communication network and the one or more external entities, as in block 830.

[0062] Another example provides functionality 900 of relay user equipment (UE) operable to support direct device-to-device communication within a wireless

communication network, as shown in the flow chart in FIG. 9. The functionality can be implemented as a method or the functionality can be executed as instructions on a machine, where the instructions are included one or more computer readable mediums or one or more transitory or non-transitory machine readable storage mediums. The relay UE can comprise one or more processors and memory configured to: process at the relay UE, an intemal D2D UE identifier and an extemal D2D UE identifier of a D2D UE, received from one or more D2D UEs, as in block 910. The relay UE can comprise one or more processors and memory configured to: signal a transceiver at the relay UE, to transmit to the wireless communication network, an internal relay UE identifier of the relay UE and the internal D2D UE identifier and the external D2D UE identifier of the one or more D2D UEs to enable the wireless communication network and one or more external entities to communicate with the one or more D2D UEs, as in block 920. The relay UE can comprise one or more processors and memory configured to: relay one or more communication messages between the one or more D2D UEs and one or more of the wireless communication network and the one or more external entities, as in block 930.

[0063] FIG. 10 illustrates a diagram of a wireless device (e.g., UE) in accordance with an example. FIG. 10 provides an example illustration of the wireless device, such as a user equipment (UE) UE, a mobile station (MS), a mobile wireless device, a mobile communication device, a tablet, a handset, or other type of wireless device. In one aspect, the wireless device can include at least one of an antenna, a touch sensitive display screen, a speaker, a microphone, a graphics processor, a baseband processor, an application processor, internal memory, a non-volatile memory port, and combinations thereof.

[0064] The wireless device can include one or more antennas configured to communicate with a node or transmission station, such as a base station (BS), an evolved Node B (eNB), a baseband unit (BBU), a remote radio head (RRH), a remote radio equipment (RRE), a relay station (RS), a radio equipment (RE), a remote radio unit (RRU), a central processing module (CPM), or other type of wireless wide area network (WWAN) access point. The wireless device can be configured to communicate using at least one wireless communication standard including 3GPP LTE, WiMAX, High Speed Packet Access (HSPA), Bluetooth, and Wi-Fi. The wireless device can communicate using separate antennas for each wireless communication standard or shared antennas for multiple wireless communication standards. The wireless device can communicate in a wireless local area network (WLAN), a wireless personal area network (WPAN), and/or a WWAN. The mobile device can include a storage medium. In one aspect, the storage medium can be associated with and/or communicate with the application processor, the graphics processor, the display, the non-volatile memory port, and/or internal memory. In one aspect, the application processor and graphics processor are storage mediums.

[0065] FIG. 11 illustrates a diagram of example components of a User Equipment (UE) device in accordance with an example. Fig. 11 illustrates, for one aspect, example components of a User Equipment (UE) device 1100. In some aspects, the UE device 1100 can include application circuitry 1102, baseband circuitry 1104, Radio Frequency (RF) circuitry 1106, front-end module (FEM) circuitry 1108 and one or more antennas 1110, coupled together at least as shown.

[0066] The application circuitry 1102 can include one or more application processors. For example, the application circuitry 1102 can include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor(s) can include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.). The processors can be coupled with and/or can include memory /storage and can be configured to execute instructions stored in the memory /storage to enable various applications and/or operating systems to run on the system.

[0067] The processor(s) can include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.). The processors can be coupled with and/or can include a storage medium 1112, and can be configured to execute instructions stored in the storage medium 1112 to enable various applications and/or operating systems to run on the system.

[0068] The baseband circuitry 1104 can include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 1104 can include one or more baseband processors and/or control logic to process baseband signals received from a receive signal path of the RF circuitry 1106 and to generate baseband signals for a transmit signal path of the RF circuitry 1106. Baseband processing circuitry 1104 can interface with the application circuitry 1102 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 1106. For example, in some aspects, the baseband circuitry 1104 can include a second generation (2G) baseband processor 1104a, third generation (3G) baseband processor 1104b, fourth generation (4G) baseband processor 1104c, and/or other baseband processor(s) 1104d for other existing generations, generations in development or to be developed in the future (e.g., fifth generation (5G), 6G, etc.). The baseband circuitry 1104 (e.g., one or more of baseband processors 1104a-d) can handle various radio control functions that

enable communication with one or more radio networks via the RF circuitry 1106. The radio control functions can include, but are not limited to, signal

modulation/demodulation, encoding/decoding, radio frequency shifting, etc. In some aspects, modulation/demodulation circuitry of the baseband circuitry 1104 can include Fast-Fourier Transform (FFT), precoding, and/or constellation mapping/demapping functionality. In some aspects, encoding/decoding circuitry of the baseband circuitry 1104 can include convolution, tail-biting convolution, turbo, Viterbi, and/or Low Density Parity Check (LDPC) encoder/decoder functionality. Aspects of

modulation/demodulation and encoder/decoder functionality are not limited to these examples and can include other suitable functionality in other aspects.

[0069] In some aspects, the baseband circuitry 1104 can include elements of a protocol stack such as, for example, elements of an evolved universal terrestrial radio access network (EUTRAN) protocol including, for example, physical (PHY), media access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), and/or radio resource control (RRC) elements. A central processing unit (CPU) 1104e of the baseband circuitry 1104 can be configured to run elements of the protocol stack for signaling of the PHY, MAC, RLC, PDCP and/or RRC layers. In some aspects, the baseband circuitry can include one or more audio digital signal processor(s) (DSP) 1104f. The audio DSP(s) 1104f can be include elements for compression/decompression and echo cancellation and can include other suitable processing elements in other aspects. Components of the baseband circuitry can be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some aspects. In some aspects, some or all of the constituent components of the baseband circuitry 1104 and the application circuitry 1102 can be implemented together such as, for example, on a system on a chip (SOC).

[0070] In some aspects, the baseband circuitry 1104 can provide for

communication compatible with one or more radio technologies. For example, in some aspects, the baseband circuitry 1104 can support communication with an evolved universal terrestrial radio access network (EUTRAN) and/or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN). Aspects in which the baseband circuitry 1104 is configured to support radio communications of more than one wireless protocol can be referred to as multi- mode baseband circuitry. [0071] RF circuitry 1106 can enable communication with wireless networks

using modulated electromagnetic radiation through a non-solid medium. In various aspects, the RF circuitry 1106 can include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. RF circuitry 1106 can include a receive signal path which can include circuitry to down-convert RF signals received from the FEM circuitry 1108 and provide baseband signals to the baseband circuitry 1104. RF circuitry 1106 can also include a transmit signal path which can include circuitry to up-convert baseband signals provided by the baseband circuitry 1104 and provide RF output signals to the FEM circuitry 1108 for transmission.

[0072] In some aspects, the RF circuitry 1106 can include a receive signal path and a transmit signal path. The receive signal path of the RF circuitry 1106 can include mixer circuitry 1106a, amplifier circuitry 1106b and filter circuitry 1106c. The transmit signal path of the RF circuitry 1106 can include filter circuitry 1106c and mixer circuitry 1106a. RF circuitry 1106 can also include synthesizer circuitry 1106d for synthesizing a frequency for use by the mixer circuitry 1106a of the receive signal path and the transmit signal path. In some aspects, the mixer circuitry 1106a of the receive signal path can be configured to down-convert RF signals received from the FEM circuitry 1108 based on the synthesized frequency provided by synthesizer circuitry 1106d. The amplifier circuitry 1106b can be configured to amplify the down-converted signals and the filter circuitry 1106c can be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals. Output baseband signals can be provided to the baseband circuitry 1104 for further processing. In some aspects, the output baseband signals can be zero-frequency baseband signals, although the output baseband signals do not have to be zero-frequency baseband signals. In some aspects, mixer circuitry 1106a of the receive signal path can comprise passive mixers, although the scope of the aspects is not limited in this respect.

[0073] In some aspects, the mixer circuitry 1106a of the transmit signal path can be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 1106d to generate RF output signals for the FEM circuitry 1108. The baseband signals can be provided by the baseband circuitry 1104 and can be filtered by filter circuitry 1106c. The filter circuitry 1106c can include a low-pass filter (LPF), although the scope of the aspects is not limited in this respect.

[0074] In some aspects, the mixer circuitry 1106a of the receive signal path and the mixer circuitry 1106a of the transmit signal path can include two or more mixers and can be arranged for quadrature downconversion and/or upconversion respectively. In some aspects, the mixer circuitry 1106a of the receive signal path and the mixer circuitry 1106a of the transmit signal path can include two or more mixers and can be arranged for image rejection (e.g., Hartley image rejection). In some aspects, the mixer circuitry 1106a of the receive signal path and the mixer circuitry 1106a can be arranged for direct

downconversion and/or direct upconversion, respectively. In some aspects, the mixer circuitry 1106a of the receive signal path and the mixer circuitry 1106a of the transmit signal path can be configured for super-heterodyne operation.

[0075] In some aspects, the output baseband signals and the input baseband signals can be analog baseband signals, although the scope of the aspects is not limited in this respect. In some alternate aspects, the output baseband signals and the input baseband signals can be digital baseband signals. In these alternate aspects, the RF circuitry 1106 can include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 1104 can include a digital baseband interface to communicate with the RF circuitry 1106.

[0076] In some dual-mode embodiments, a separate radio IC circuitry can be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.

[0077] In some embodiments, the synthesizer circuitry 1106d can be a fractional -N synthesizer or a fractional N/N+l synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers can be suitable. For example, synthesizer circuitry 1106d can be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.

[0078] The synthesizer circuitry 1106d can be configured to synthesize an output frequency for use by the mixer circuitry 1106a of the RF circuitry 1106 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 1106d can be a fractional N/N+l synthesizer. [0079] In some embodiments, frequency input can be provided by a voltage controlled oscillator (VCO), although that is not a constraint. Divider control input can be provided by either the baseband circuitry 1104 or the applications processor 1102 depending on the desired output frequency. In some embodiments, a divider control input (e.g., N) can be determined from a look-up table based on a channel indicated by the applications processor 1102.

[0080] Synthesizer circuitry 1106d of the RF circuitry 1106 can include a divider, a delay -locked loop (DLL), a multiplexer and a phase accumulator. In some embodiments, the divider can be a dual modulus divider (DMD) and the phase accumulator can be a digital phase accumulator (DPA). In some embodiments, the DMD can be configured to divide the input signal by either N or N+l (e.g., based on a carry out) to provide a fractional division ratio. In some example embodiments, the DLL can include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop. In these embodiments, the delay elements can be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

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

[0082] FEM circuitry 1108 can include a receive signal path which can include circuitry configured to operate on RF signals received from one or more antennas 1110, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 1106 for further processing. FEM circuitry 1108 can also include a transmit signal path which can include circuitry configured to amplify signals for transmission provided by the RF circuitry 1106 for transmission by one or more of the one or more antennas 1110.

[0083] In some embodiments, the FEM circuitry 1108 can include a TX/RX switch to switch between transmit mode and receive mode operation. The FEM circuitry can include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry can include a low-noise amplifier (LNA) to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 1106). The transmit signal path of the FEM circuitry 1108 can include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 1106), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 1110.

[0084] In some embodiments, the UE device 1100 can include additional elements such as, for example, memory/storage, display, camera, sensor, and/or input/output (I/O) interface.

[0085] FIG. 12 illustrates a diagram 1200 of a node 1210 (e.g., eNB and/or a base station) and wireless device (e.g., UE) in accordance with an example. The node can include a base station (BS), a Node B (NB), an evolved Node B (eNB), a baseband unit (BBU), a remote radio head (RRH), a remote radio equipment (RRE), a remote radio unit (RRU), or a central processing module (CPM). In one aspect, the node can be a Serving GPRS Support Node. The node 1210 can include a node device 1212. The node device 1212 or the node 1210 can be configured to communicate with the wireless device 1220. The node device 1212 can be configured to implement the technology described. The node device 1212 can include a processing module 1214 and a transceiver module 1216. In one aspect, the node device 1212 can include the transceiver module 1216 and the processing module 1214 forming a circuitry 1218 for the node 1210. In one aspect, the transceiver module 1216 and the processing module 1214 can form a circuitry of the node device 1212. The processing module 1214 can include one or more processors and memory. In one embodiment, the processing module 1222 can include one or more application processors. The transceiver module 1216 can include a transceiver and one or more processors and memory. In one embodiment, the transceiver module 1216 can include a baseband processor.

[0086] The wireless device 1220 can include a transceiver module 1224 and a processing module 1222. The processing module 1222 can include one or more processors and memory. In one embodiment, the processing module 1222 can include one or more application processors. The transceiver module 1224 can include a transceiver and one or more processors and memory. In one embodiment, the transceiver module 1224 can include a baseband processor. The wireless device 1220 can be configured to implement the technology described. The node 1210 and the wireless devices 1220 can also include one or more storage mediums, such as the transceiver module 1216, 1224 and/or the processing module 1214, 1222. It should be noted that one or more components of the transceiver module 1216 can be included in separate devices such as in, for example, a cloud-RAN (C-RAN).

[0087] FIG. 13 illustrates a computing device 1310 on which modules of this technology may execute. A computing device 1310 is illustrated on which a high level example of the technology may be executed, such as in an evolved packet core (EPC) having a proximity service (ProSe) function of a core network in a cellular communications network, as referenced herein. The computing device 1310 may include one or more processors 1312 that are in communication with memory devices 1320. The computing device may include a local communication interface 1318 for the components in the computing device. For example, the local communication interface may be a local data bus and/or any related address or control busses as may be desired.

[0088] The memory device 1320 may contain modules 1324 that are executable by the processor(s) 1312 and data for the modules 1324. The modules 1324 may execute the functions described earlier. A ProSe Function 1322 (e.g., a ProSe Function application) may also be located in the memory device 1320 for storing data related to the modules 1324 and other applications along with an operating system that is executable by the processor(s) 1312.

[0089] Other applications may also be stored in the memory device 1320 and may be executable by the processor(s) 1312. Components or modules discussed in this description that may be implemented in the form of software using high programming level languages that are compiled, interpreted or executed using a hybrid of the methods.

[0090] The computing device may also have access to I/O (input/output) devices 1314 that are usable by the computing devices. An example of an I/O device is a display screen that is available to display output from the computing devices. Other known I/O device may be used with the computing device as desired. Networking devices 1316 and similar communication devices may be included in the computing device. The networking devices 1316 may be wired or wireless networking devices that connect to the Internet, a LAN, WAN, or other computing network.

[0091] The components or modules that are shown as being stored in the memory device 1320 may be executed by the processor 1312. The term "executable" may mean a program file that is in a form that may be executed by a processor 1312. For example, a program in a higher level language may be compiled into machine code in a format that may be loaded into a random access portion of the memory device 1320 and executed by the processor 1312, or source code may be loaded by another executable program and interpreted to generate instructions in a random access portion of the memory to be executed by a processor. The executable program may be stored in any portion or component of the memory device 1320. For example, the memory device 1320 may be random access memory (RAM), read only memory (ROM), flash memory, a solid-state drive, memory card, a hard drive, optical disk, floppy disk, magnetic tape, or any other memory components.

[0092] The processor 1312 may represent multiple processors and the memory 1320 may represent multiple memory units that operate in parallel to the processing circuits. This may provide parallel processing channels for the processes and data in the system. The local interface 1318 may be used as a network to facilitate communication between any of the multiple processors and multiple memories. The local interface 1318 may use additional systems designed for coordinating communication such as load balancing, bulk data transfer, and similar systems.

Examples

[0093] The following examples pertain to specific technology embodiments and point out specific features, elements, or steps that can be used or otherwise combined in achieving such embodiments.

[0094] Example 1 includes an apparatus of a proximity service (ProSe) function of a core network in a cellular communications network, the apparatus comprising one or more processors and memory configured to: process, at the ProSe function, an internal device- to-device (D2D) user equipment (UE) identifier of one or more D2D UEs, an external D2D UE identifier of the one or more D2D UEs, and an internal relay UE identifier, received from a relay UE to enable the core network and one or more external entities to communicate with the one or more D2D UEs; associate, at the ProSe function, the external D2D UE identifier of the one or more D2D UEs with the internal relay UE identifier of the relay UE to enable one or more external entities to communicate with the one or more D2D UEs using the external D2D UE identifier; associate, at the ProSe function, the D2D UE identifier of the one or more D2D UEs with the internal relay UE identifier of the relay UE to enable the cellular communications network to communicate with the one or more D2D UEs using the internal D2D UE identifier; and communicate one or more communication messages via the relay UE to the one or more D2D UEs.

[0095] Example 2 includes the apparatus of example 1, wherein the internal D2D UE identifier and the internal relay UE identifier of the relay UE are each a unique UE identity assigned to the one or more D2D UEs or the relay UE, a media access control (MAC) address, or an international mobile subscriber identity.

[0096] Example 3 includes the apparatus of example 1 or 2, wherein the one or more processors and memory are further configured to: link the internal relay UE identifier and the internal D2D UE identifier; store the internal D2D UE identifier and the internal relay UE identifier in the core network for addressing the one or more D2D UEs; or perform a location update procedure to locate the one or more D2D UEs.

[0097] Example 4 includes the apparatus of example 1, wherein the one or more processors and memory are further configured to send to the relay UE a trigger message requesting to communicate with the one or more D2D UEs.

[0098] Example 5 includes the apparatus of example 1 or 4, wherein the one or more processors and memory are further configured to receive, from the relay UE, a response message, sent to the relay UE from the one or more D2D UEs, indicating receipt of the trigger message.

[0099] Example 6 includes the apparatus of example 5, wherein the one or more processors and memory are further configured to: receive a notification from the relay UE that a trigger message was successfully delivered to the one or more D2D UEs prior to an expiration of a selected time period. [00100] Example 7 includes the apparatus of example 1 or 6, wherein the one or more processors and memory are further configured to receive a notification from the relay UE that a trigger message was unsuccessfully delivered to the one or more D2D UEs prior to an expiration of a selected time period.

[00101] Example 8 includes the apparatus of example 1, wherein the one or more processors and memory are further configured to identify a location of the one or more D2D UEs using the internal D2D UE identifier.

[00102] Example 9 includes the apparatus of example 1, wherein the one or more processors and memory are further configured to map a media access control (MAC) address of the one or more D2D UEs to the external D2D UE identifier of the one or more D2D UEs to enable one or more external entities that are external to the wireless communication network to communicate with the one or more D2D UEs.

[00103] Example 10 includes the apparatus of example 1 or 9, wherein the one or more processors and memory are further configured to receive one or more messages from the one or more external entities to communicate with the one or more D2D UEs.

[00104] Example 11 includes the apparatus of example 10, wherein the one or more processors and memory are further configured to forward via the relay UE, to the one or more D2D UEs, the one or more messages received from the one or more external entities.

[00105] Example 12 includes an apparatus of a gateway user equipment (UE), the gateway UE configured to support direct device-to-device (D2D) communication within a wireless communication network, the apparatus comprising one or more processors and memory configured to: process at the gateway UE, an internal D2D UE identifier and an external D2D UE identifier of a D2D UE, received from the D2D UE; signal a transceiver at the gateway UE, to transmit to a Prose function of the wireless communication network, an internal gateway UE identifier of the gateway UE and the internal D2D UE identifier and the external D2D UE identifier of the D2D UE to enable the wireless communication network and one or more external entities to communicate with the D2D UE, wherein: the internal gateway UE identifier and the internal D2D identifier enables the D2D UE to be addressed and registered with the wireless communication network, and the external D2D UE identifier enables the D2D UE to be addressed by the one or more external entities that are external to the wireless communication network; and relay one or more communication messages between the D2D UE and one or more of the wireless communication network and the one or more external entities.

[00106] Example 13 includes the apparatus of example 12, wherein the internal D2D UE identifier of the D2D UE and an internal gateway UE identifier of the gateway UE are each a unique UE identity assigned to the D2D UE or the gateway UE, a media access control (MAC) address, or an international mobile subscriber identity.

[00107] Example 14 includes the apparatus of example 12 or 13, wherein the one or more processors and memory are further configured to link the internal gateway UE identifier and the internal D2D UE identifier, wherein the internal D2D UE identifier and the internal gateway UE identifier are stored in the wireless communication network for addressing the D2D UE.

[00108] Example 15 includes the apparatus of example 12, wherein the one or more processors and memory are further configured to receive, from the wireless

communication network, a trigger message requesting to communicate with the D2D UE.

[00109] Example 16 includes the apparatus of example 12 or 15, wherein the one or more processors and memory are further configured to send, to the D2D UE, the trigger message received from the wireless communication network.

[00110] Example 17 includes the apparatus of example 16, wherein the one or more processors and memory are further configured to signal to the transmitter of the gateway UE a response message to transmit to the wireless communication network, received from the D2D UE, indicating receipt of the trigger message.

[00111] Example 18 includes the apparatus of example 16, wherein the one or more processors and memory are further configured to: notify the wireless communication network that the trigger message was successfully delivered to the D2D UE prior to the expiration of a selected time period; or notify the wireless communication network that the trigger message was unsuccessfully delivered to the D2D UE prior to expiration of the selected time period.

[00112] Example 19 includes the apparatus of example 12, wherein the one or more processors and memory are further configured to forward one or more messages received from the wireless communication network to the D2D UE.

[00113] Example 20 includes the apparatus of example 12, wherein the one or more processors and memory are further configured to communicate with the D2D UE using a PC5 communication interface.

[00114] Example 21 includes the apparatus of example 12 or 20, wherein the one or more processors and memory are further configured to: identify a location of the D2D UE using the internal D2D UE identifier; or notify the wireless communication network of the location of the D2D UE.

[00115] Example 22 includes the apparatus of example 12 or 13, wherein the one or more processors and memory are further configured to: map a media access control (MAC) address of the D2D UE to the external D2D UE identifier to enable one or more external entities that are external to the wireless communication network to communicate with the D2D UE; receive one or more messages from the one or more external entities to communicate with the D2D UE; or forward, to the D2D UE, the one or more messages received from the one or more external entities.

[00116] Example 23 includes the apparatus of example 12, wherein the apparatus includes at least one of an antenna, a touch sensitive display screen, a speaker, a microphone, a graphics processor, a baseband processor, an application processor, internal memory, a non-volatile memory port, and combinations thereof.

[00117] Example 24 includes at least one machine readable storage medium having instructions embodied thereon for a relay user equipment (UE) to support direct device- to-device (D2D) communication within a wireless communication network, the instructions when executed by one or more processors and memory cause the relay UE to: process at the relay UE, an internal D2D UE identifier and an external D2D UE identifier of a D2D UE, received from one or more D2D UEs; signal a transceiver at the relay UE, to transmit to the wireless communication network, an internal relay UE identifier of the relay UE and the internal D2D UE identifier and the external D2D UE identifier of the one or more D2D UEs to enable the wireless communication network and one or more external entities to communicate with the one or more D2D UEs; and relay one or more communication messages between the one or more D2D UEs and one or more of the wireless communication network and the one or more external entities. [00118] Example 25 includes the at least one machine readable storage medium of example 24, wherein the internal D2D UE identifier of the one or more D2D UEs is a unique UE identity assigned to the one or more D2D UEs, a media access control (MAC) address, or an international mobile subscriber identity, and the internal relay UE identifier and the internal D2D identifier enables the one or more D2D UE to be addressed and registered with the wireless communication network, and the external D2D UE identifier enables the one or more D2D UEs to be address by the one or more external entities that are external to the wireless communication network.

[00119] Example 26 includes the at least one machine readable storage medium of example 24, further comprising instructions which when executed cause the relay UE to: communicate with the one or more D2D UEs using a PC5 communication interface; or relay the one or more communication messages between the one or more D2D UEs and one or more of a proximity service (ProSe) function of the wireless communication network and the one or more external entities.

[00120] Example 27 includes the at least one machine readable storage medium of example 24 or 26, further comprising instructions which when executed cause the relay UE to: receive, from the ProSe function, a trigger message requesting to communicate with the one or more D2D UEs; communicate, to the one or more D2D UEs, the trigger message received from the ProSe function; or receive a response message, received from the one or more D2D UEs, indicating receipt of the trigger message.

[00121] Example 28 includes the at least one machine readable storage medium of example 24 or 26, wherein the one or more processors and memory are further configured to: notify the ProSe Function the trigger message was successfully delivered to the one or more D2D UEs prior to the expiration of a selected time period; or notify the ProSe Function the trigger message was unsuccessfully delivered to the one or more D2D UEs prior upon expiration of the selected time period.

[00122] Example 29 includes the at least one machine readable storage medium of example 24, wherein the one or more processors and memory are further configured to: link the internal relay UE identifier and the internal D2D UE identifier; identify a location of the one or more D2D UEs using the internal D2D UE identifier of the one or more D2D UEs; or notify the wireless communication network of the location of the one or more D2D UEs.

[00123] Example 30 includes the at least one machine readable storage medium of example 24 or 25, wherein the one or more processors and memory are further configured to: map a media access control (MAC) address of the one or more D2D UEs to the external D2D UE identifier of the one or more D2D UEs to enable one or more external entities that are external to the wireless communication network to communicate with the one or more D2D UEs; receive one or more messages from the one or more external entities to communicate with the one or more D2D UEs; or forward, to the one or more D2D UEs, the one or more messages received from the one or more external entities.

[00124] Example 31 includes an apparatus of a proximity service (ProSe) function of a core network in a cellular communications network, the apparatus comprising one or more processors and memory configured to: process, at the ProSe function, an internal device-to-device (D2D) user equipment (UE) identifier of one or more D2D UEs, an external D2D UE identifier of the one or more D2D UEs, and an internal relay UE identifier, received from a relay UE to enable the core network and one or more external entities to communicate with the one or more D2D UEs; associate, at the ProSe function, the external D2D UE identifier of the one or more D2D UEs with the internal relay UE identifier of the relay UE to enable one or more external entities to communicate with the one or more D2D UEs using the external D2D UE identifier; associate, at the ProSe function, the D2D UE identifier of the one or more D2D UEs with the internal relay UE identifier of the relay UE to enable the cellular communications network to communicate with the one or more D2D UEs using the internal D2D UE identifier; and communicate one or more communication messages via the relay UE to the one or more D2D UEs.

[00125] Example 32 includes the apparatus of example 31, wherein the internal D2D UE identifier and the internal relay UE identifier of the relay UE are each a unique UE identity assigned to the one or more D2D UEs or the relay UE, a media access control (MAC) address, or an international mobile subscriber identity.

[00126] Example 33 includes the apparatus of example 32, wherein the one or more processors and memory are further configured to: link the internal relay UE identifier and the internal D2D UE identifier; store the internal D2D UE identifier and the internal relay UE identifier in the core network for addressing the one or more D2D UEs; or perform a location update procedure to locate the one or more D2D UEs.

[00127] Example 34 includes the apparatus of example 31, wherein the one or more processors and memory are further configured to send to the relay UE a trigger message requesting to communicate with the one or more D2D UEs.

[00128] Example 35 includes the apparatus of example 34, wherein the one or more processors and memory are further configured to receive, from the relay UE, a response message, sent to the relay UE from the one or more D2D UEs, indicating receipt of the trigger message.

[00129] Example 36 includes the apparatus of example 35, wherein the one or more processors and memory are further configured to: receive a notification from the relay UE that a trigger message was successfully delivered to the one or more D2D UEs prior to an expiration of a selected time period.

[00130] Example 37 includes the apparatus of example 36, wherein the one or more processors and memory are further configured to receive a notification from the relay UE that a trigger message was unsuccessfully delivered to the one or more D2D UEs prior to an expiration of a selected time period.

[00131] Example 38 includes the apparatus of example 31, wherein the one or more processors and memory are further configured to identify a location of the one or more D2D UEs using the internal D2D UE identifier.

[00132] Example 39 includes the apparatus of example 31, wherein the one or more processors and memory are further configured to map a media access control (MAC) address of the one or more D2D UEs to the external D2D UE identifier of the one or more D2D UEs to enable one or more external entities that are external to the wireless communication network to communicate with the one or more D2D UEs.

[00133] Example 40 includes the apparatus of example 39, wherein the one or more processors and memory are further configured to receive one or more messages from the one or more external entities to communicate with the one or more D2D UEs.

[00134] Example 41 includes the apparatus of example 40, wherein the one or more processors and memory are further configured to forward via the relay UE, to the one or more D2D UEs, the one or more messages received from the one or more external entities.

[00135] Example 42 apparatus of a gateway user equipment (UE), the gateway UE configured to support direct device-to-device (D2D) communication within a wireless communication network, the apparatus comprising one or more processors and memory configured to: process at the gateway UE, an internal D2D UE identifier and an external D2D UE identifier of a D2D UE, received from the D2D UE; signal a transceiver at the gateway UE, to transmit to a Prose function of the wireless communication network, an internal gateway UE identifier of the gateway UE and the internal D2D UE identifier and the external D2D UE identifier of the D2D UE to enable the wireless communication network and one or more external entities to communicate with the D2D UE, wherein: the internal gateway UE identifier and the internal D2D identifier enables the D2D UE to be addressed and registered with the wireless communication network, and the external D2D UE identifier enables the D2D UE to be addressed by the one or more external entities that are external to the wireless communication network; and relay one or more communication messages between the D2D UE and one or more of the wireless communication network and the one or more external entities.

[00136] Example 43 includes the apparatus of example 42, wherein the internal D2D UE identifier of the D2D UE and an internal gateway UE identifier of the gateway UE are each a unique UE identity assigned to the D2D UE or the gateway UE, a media access control (MAC) address, or an international mobile subscriber identity.

[00137] Example 44 includes the apparatus of example 43, wherein the one or more processors and memory are further configured to link the internal gateway UE identifier and the internal D2D UE identifier, wherein the internal D2D UE identifier and the internal gateway UE identifier are stored in the wireless communication network for addressing the D2D UE.

[00138] Example 45 includes the apparatus of example 42, wherein the one or more processors and memory are further configured to receive, from the wireless

[00139] Example 46 includes the apparatus of example 45, wherein the one or more processors and memory are further configured to send, to the D2D UE, the trigger message received from the wireless communication network. [00140] Example 47 includes the apparatus of example 46, wherein the one or more processors and memory are further configured to signal to the transmitter of the gateway UE a response message to transmit to the wireless communication network, received from the D2D UE, indicating receipt of the trigger message.

[00141] Example 48 includes the apparatus of example 46, wherein the one or more processors and memory are further configured to: notify the wireless communication network that the trigger message was successfully delivered to the D2D UE prior to the expiration of a selected time period; or notify the wireless communication network that the trigger message was unsuccessfully delivered to the D2D UE prior to expiration of the selected time period.

[00142] Example 49 includes the apparatus of example 42, wherein the one or more processors and memory are further configured to forward one or more messages received from the wireless communication network to the D2D UE.

[00143] Example 50 includes the apparatus of example 42, wherein the one or more processors and memory are further configured to communicate with the D2D UE using a PC5 communication interface.

[00144] Example 51 includes the apparatus of example 50, wherein the one or more processors and memory are further configured to: identify a location of the D2D UE using the internal D2D UE identifier; or notify the wireless communication network of the location of the D2D UE.

[00145] Example 52 includes the apparatus of example 43, wherein the one or more processors and memory are further configured to: map a media access control (MAC) address of the D2D UE to the external D2D UE identifier to enable one or more external entities that are external to the wireless communication network to communicate with the D2D UE; receive one or more messages from the one or more external entities to communicate with the D2D UE; or forward, to the D2D UE, the one or more messages received from the one or more external entities.

[00146] Example 53 includes the apparatus of example 42, wherein the apparatus includes at least one of an antenna, a touch sensitive display screen, a speaker, a microphone, a graphics processor, a baseband processor, an application processor, internal memory, a non-volatile memory port, and combinations thereof.

[00147] Example 54 includes at least one non-transitory machine readable storage medium having instructions embodied thereon for a relay user equipment (UE) to support direct device-to-device (D2D) communication within a wireless communication network, the instructions when executed by one or more processors and memory cause the relay UE to: process at the relay UE, an internal D2D UE identifier and an external D2D UE identifier of a D2D UE, received from one or more D2D UEs; signal a transceiver at the relay UE, to transmit to the wireless communication network, an internal relay UE identifier of the relay UE and the internal D2D UE identifier and the external D2D UE identifier of the one or more D2D UEs to enable the wireless communication network and one or more external entities to communicate with the one or more D2D UEs; and relay one or more communication messages between the one or more D2D UEs and one or more of the wireless communication network and the one or more external entities.

[00148] Example 55 includes the at least one non-transitory machine readable storage medium of claim 54, wherein the internal D2D UE identifier of the one or more D2D UEs is a unique UE identity assigned to the one or more D2D UEs, a media access control (MAC) address, or an international mobile subscriber identity, and the internal relay UE identifier and the internal D2D identifier enables the one or more D2D UE to be addressed and registered with the wireless communication network, and the external D2D UE identifier enables the one or more D2D UEs to be address by the one or more external entities that are external to the wireless communication network.

[00149] Example 56 includes the at least one non-transitory machine readable storage medium of claim 54, further comprising instructions which when executed cause the relay UE to: communicate with the one or more D2D UEs using a PC5 communication interface; or relay the one or more communication messages between the one or more D2D UEs and one or more of a proximity service (ProSe) function of the wireless communication network and the one or more external entities.

[00150] Example 57 includes the at least one non-transitory machine readable storage medium of claim 56, further comprising instructions which when executed cause the relay UE to: receive, from the ProSe function, a trigger message requesting to communicate with the one or more D2D UEs; communicate, to the one or more D2D UEs, the trigger message received from the ProSe function; or receive a response message, received from the one or more D2D UEs, indicating receipt of the trigger message.

[00151] Example 58 includes the at least one non-transitory machine readable storage medium of claim 56, wherein the one or more processors and memory are further configured to: notify the ProSe Function the trigger message was successfully delivered to the one or more D2D UEs prior to the expiration of a selected time period; or notify the ProSe Function the trigger message was unsuccessfully delivered to the one or more D2D UEs prior upon expiration of the selected time period.

[00152] Example 59 includes the at least one non-transitory machine readable storage medium of claim 54, wherein the one or more processors and memory are further configured to: link the internal relay UE identifier and the internal D2D UE identifier; identify a location of the one or more D2D UEs using the internal D2D UE identifier of the one or more D2D UEs; or notify the wireless communication network of the location of the one or more D2D UEs.

[00153] Example 60 includes the at least one non-transitory machine readable storage medium of claim 54, wherein the one or more processors and memory are further configured to: map a media access control (MAC) address of the one or more D2D UEs to the external D2D UE identifier of the one or more D2D UEs to enable one or more external entities that are external to the wireless communication network to communicate with the one or more D2D UEs; receive one or more messages from the one or more external entities to communicate with the one or more D2D UEs; or forward, to the one or more D2D UEs, the one or more messages received from the one or more external entities.

[00154] Example 61 includes an apparatus of a proximity service (ProSe) function of a core network in a cellular communications network, the apparatus comprising one or more processors and memory configured to: process, at the ProSe function, an internal device-to-device (D2D) user equipment (UE) identifier of one or more D2D UEs, an external D2D UE identifier of the one or more D2D UEs, and an internal relay UE identifier, received from a relay UE to enable the core network and one or more external entities to communicate with the one or more D2D UEs; associate, at the ProSe function, the external D2D UE identifier of the one or more D2D UEs with the internal relay UE identifier of the relay UE to enable one or more external entities to communicate with the one or more D2D UEs using the external D2D UE identifier; associate, at the ProSe function, the D2D UE identifier of the one or more D2D UEs with the internal relay UE identifier of the relay UE to enable the cellular communications network to communicate with the one or more D2D UEs using the internal D2D UE identifier; and communicate one or more communication messages via the relay UE to the one or more D2D UEs.

[00155] Example 62 includes the apparatus of example 61, wherein the internal D2D UE identifier and the internal relay UE identifier of the relay UE are each a unique UE identity assigned to the one or more D2D UEs or the relay UE, a media access control (MAC) address, or an international mobile subscriber identity.

[00156] Example 63 includes the apparatus of example 61 or 62, wherein the one or more processors and memory are further configured to: link the internal relay UE identifier and the internal D2D UE identifier; store the internal D2D UE identifier and the internal relay UE identifier in the core network for addressing the one or more D2D UEs; perform a location update procedure to locate the one or more D2D UEs; send to the relay UE a trigger message requesting to communicate with the one or more D2D UEs; receive, from the relay UE, a response message, sent to the relay UE from the one or more D2D UEs, indicating receipt of the trigger message; or receive a notification from the relay UE that a trigger message was successfully delivered to the one or more D2D UEs prior to an expiration of a selected time period.

[00157] In example 64, the subject matter of Example 61 or any of the Examples described herein may further include, wherein the one or more processors and memory are further configured to receive a notification from the relay UE that a trigger message was unsuccessfully delivered to the one or more D2D UEs prior to an expiration of a selected time period.

[00158] In example 65, the subject matter of Example 61 or any of the Examples described herein may further include, wherein the one or more processors and memory are further configured to: identify a location of the one or more D2D UEs using the internal D2D UE identifier; or map a media access control (MAC) address of the one or more D2D UEs to the external D2D UE identifier of the one or more D2D UEs to enable one or more external entities that are external to the wireless communication network to communicate with the one or more D2D UEs ;receive one or more messages from the one or more external entities to communicate with the one or more D2D UEs; or forward via the relay UE, to the one or more D2D UEs, the one or more messages received from the one or more external entities.

[00159] Example 66 includes an apparatus of a gateway user equipment (UE), the gateway UE configured to support direct device-to-device (D2D) communication within a wireless communication network, the apparatus comprising one or more processors and memory configured to: process at the gateway UE, an internal D2D UE identifier and an external D2D UE identifier of a D2D UE, received from the D2D UE; signal a transceiver at the gateway UE, to transmit to a Prose function of the wireless communication network, an internal gateway UE identifier of the gateway UE and the internal D2D UE identifier and the external D2D UE identifier of the D2D UE to enable the wireless communication network and one or more external entities to communicate with the D2D UE, wherein: the internal gateway UE identifier and the internal D2D identifier enables the D2D UE to be addressed and registered with the wireless communication network, and the external D2D UE identifier enables the D2D UE to be addressed by the one or more external entities that are external to the wireless communication network; and relay one or more communication messages between the D2D UE and one or more of the wireless communication network and the one or more external entities.

[00160] Example 67 includes the apparatus of example 66, wherein the internal D2D UE identifier of the D2D UE and an internal gateway UE identifier of the gateway UE are each a unique UE identity assigned to the D2D UE or the gateway UE, a media access control (MAC) address, or an international mobile subscriber identity.

[00161] Example 68 includes the apparatus of example 66 or 67, wherein the one or more processors and memory are further configured to: link the internal gateway UE identifier and the internal D2D UE identifier, wherein the internal D2D UE identifier and the internal gateway UE identifier are stored in the wireless communication network for addressing the D2D UE; receive, from the wireless communication network, a trigger message requesting to communicate with the D2D UE; send, to the D2D UE, the trigger message received from the wireless communication network; signal to the transmitter of the gateway UE a response message to transmit to the wireless communication network, received from the D2D UE, indicating receipt of the trigger message; notify the wireless communication network that the trigger message was successfully delivered to the D2D UE prior to the expiration of a selected time period; or notify the wireless communication network that the trigger message was unsuccessfully delivered to the D2D UE prior to expiration of the selected time period.

[00162] In example 69, the subject matter of Example 66 or any of the Examples described herein may further include, wherein the one or more processors and memory are further configured to: forward one or more messages received from the wireless communication network to the D2D UE; communicate with the D2D UE using a PC5 communication interface; identify a location of the D2D UE using the internal D2D UE identifier; or notify the wireless communication network of the location of the D2D UE.

[00163] In example 70, the subject matter of Example 66 or any of the Examples described herein may further include, wherein the one or more processors and memory are further configured to: map a media access control (MAC) address of the D2D UE to the external D2D UE identifier to enable one or more external entities that are external to the wireless communication network to communicate with the D2D UE; receive one or more messages from the one or more external entities to communicate with the D2D UE; or forward, to the D2D UE, the one or more messages received from the one or more external entities.

[00164] In example 71, the subject matter of Example 66 or any of the Examples described herein may further include, wherein the apparatus includes at least one of an antenna, a touch sensitive display screen, a speaker, a microphone, a graphics processor, a baseband processor, an application processor, internal memory, a non-volatile memory port, and combinations thereof.

[00165] Example 72 includes at least one machine readable storage medium having instructions embodied thereon for a relay user equipment (UE) to support direct device- to-device (D2D) communication within a wireless communication network, the instructions when executed by one or more processors and memory cause the relay UE to: process at the relay UE, an internal D2D UE identifier and an external D2D UE identifier of a D2D UE, received from one or more D2D UEs; signal a transceiver at the relay UE, to transmit to the wireless communication network, an internal relay UE identifier of the relay UE and the internal D2D UE identifier and the external D2D UE identifier of the one or more D2D UEs to enable the wireless communication network and one or more external entities to communicate with the one or more D2D UEs; and relay one or more communication messages between the one or more D2D UEs and one or more of the wireless communication network and the one or more external entities.

[00166] Example 73 includes the at least one machine readable storage medium of example 72, wherein the internal D2D UE identifier of the one or more D2D UEs is a unique UE identity assigned to the one or more D2D UEs, a media access control (MAC) address, or an international mobile subscriber identity, and the internal relay UE identifier and the internal D2D identifier enables the one or more D2D UE to be addressed and registered with the wireless communication network, and the external D2D UE identifier enables the one or more D2D UEs to be address by the one or more external entities that are external to the wireless communication network.

[00167] Example 74 includes the at least one machine readable storage medium of example 72 or 73, further comprising instructions which when executed cause the relay UE to: communicate with the one or more D2D UEs using a PC5 communication interface; relay the one or more communication messages between the one or more D2D UEs and one or more of a proximity service (ProSe) function of the wireless

communication network and the one or more external entities; receive, from the ProSe function, a trigger message requesting to communicate with the one or more D2D UEs; communicate, to the one or more D2D UEs, the trigger message received from the ProSe function; receive a response message, received from the one or more D2D UEs, indicating receipt of the trigger message; notify the ProSe Function the trigger message was successfully delivered to the one or more D2D UEs prior to the expiration of a selected time period; or notify the ProSe Function the trigger message was unsuccessfully delivered to the one or more D2D UEs prior upon expiration of the selected time period.

[00168] In example 75, the subject matter of Example 66 or any of the Examples described herein may further include, wherein the one or more processors and memory are further configured to: link the internal relay UE identifier and the internal D2D UE identifier; identify a location of the one or more D2D UEs using the internal D2D UE identifier of the one or more D2D UEs; notify the wireless communication network of the location of the one or more D2D UEs; map a media access control (MAC) address of the one or more D2D UEs to the external D2D UE identifier of the one or more D2D UEs to enable one or more external entities that are external to the wireless communication network to communicate with the one or more D2D UEs; receive one or more messages from the one or more external entities to communicate with the one or more D2D UEs; or forward, to the one or more D2D UEs, the one or more messages received from the one or more external entities.

[00169] Example 76 includes a device to support direct device-to-device (D2D) communication within a wireless communication network, the device comprising: means for processing at the relay UE, an internal D2D UE identifier and an external D2D UE identifier of a D2D UE, received from one or more D2D UEs; means for signaling a transceiver at the relay UE, to transmit to the wireless communication network, an internal relay UE identifier of the relay UE and the internal D2D UE identifier and the external D2D UE identifier of the one or more D2D UEs to enable the wireless communication network and one or more external entities to communicate with the one or more D2D UEs; and means for relaying one or more communication messages between the one or more D2D UEs and one or more of the wireless communication network and the one or more external entities.

[00170] Example 77 includes the device of example 76, wherein the internal D2D UE identifier of the one or more D2D UEs is a unique UE identity assigned to the one or more D2D UEs, a media access control (MAC) address, or an international mobile subscriber identity, and the internal relay UE identifier and the internal D2D identifier enables the one or more D2D UE to be addressed and registered with the wireless communication network, and the external D2D UE identifier enables the one or more D2D UEs to be address by the one or more external entities that are external to the wireless communication network.

[00171] Example 78 includes the device of example 76, further comprising means for: communicating with the one or more D2D UEs using a PC5 communication interface; or relaying the one or more communication messages between the one or more D2D UEs and one or more of a proximity service (ProSe) function of the wireless communication network and the one or more external entities. [00172] Example 79 includes the device of example 76 or 78, further comprising means for: receiving, from the ProSe function, a trigger message requesting to communicate with the one or more D2D UEs; communicating, to the one or more D2D UEs, the trigger message received from the ProSe function; or receiving a response message, received from the one or more D2D UEs, indicating receipt of the trigger message.

[00173] Example 80 includes the device of example 76 or 78, further comprising means for: notifying the ProSe Function the trigger message was successfully delivered to the one or more D2D UEs prior to the expiration of a selected time period; or notifying the ProSe Function the trigger message was unsuccessfully delivered to the one or more D2D UEs prior upon expiration of the selected time period.

[00174] Example 81 includes the device of example 76, further comprising means for: linking the internal relay UE identifier and the internal D2D UE identifier; identifying a location of the one or more D2D UEs using the internal D2D UE identifier of the one or more D2D UEs; or notifying the wireless communication network of the location of the one or more D2D UEs.

[00175] Example 82 includes the device of example 76 or 77, further comprising means for: mapping a media access control (MAC) address of the one or more D2D UEs to the external D2D UE identifier of the one or more D2D UEs to enable one or more external entities that are external to the wireless communication network to communicate with the one or more D2D UEs; receiving one or more messages from the one or more external entities to communicate with the one or more D2D UEs; or forwarding, to the one or more D2D UEs, the one or more messages received from the one or more external entities.

[00176] As used herein, the term "circuitry" can refer to, be part of, or include

an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor

(shared, dedicated, or group), and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality. In some aspects, the circuitry can be implemented in, or functions associated with the circuitry can be implemented by, one or more software or firmware modules. In some aspects, circuitry can include logic, at least partially operable in hardware. [00177] Various techniques, or certain aspects or portions thereof, may take the form of program code (i.e., instructions) embodied in tangible media, such as floppy diskettes, compact disc-read-only memory (CD-ROMs), hard drives, transitory or non-transitory computer readable storage medium, or any other machine-readable storage medium wherein, when the program code is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the various techniques. Circuitry can include hardware, firmware, program code, executable code, computer instructions, and/or software. A non-transitory computer readable storage medium can be a computer readable storage medium that does not include signal. In the case of program code execution on programmable computers, the computing device may include a processor, a storage medium readable by the processor (including volatile and nonvolatile memory and/or storage elements), at least one input device, and at least one output device. The volatile and non-volatile memory and/or storage elements may be a random-access memory (RAM), erasable programmable read only memory (EPROM), flash drive, optical drive, magnetic hard drive, solid state drive, or other medium for storing electronic data. The node and wireless device may also include a transceiver module (i.e., transceiver), a counter module (i.e., counter), a processing module (i.e., processor), and/or a clock module (i.e., clock) or timer module (i.e., timer). One or more programs that may implement or utilize the various techniques described herein may use an application programming interface (API), reusable controls, and the like. Such programs may be implemented in a high level procedural or object oriented programming language to communicate with a computer system. However, the program(s) may be implemented in assembly or machine language, if desired. In any case, the language may be a compiled or interpreted language, and combined with hardware implementations.

[00178] As used herein, the term processor can include general purpose processors, specialized processors such as VLSI, FPGAs, or other types of specialized processors, as well as base band processors used in transceivers to send, receive, and process wireless communications.

[00179] It should be understood that many of the functional units described in this specification have been labeled as modules, in order to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising custom very -large-scale integration (VLSI) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.

[00180] Modules may also be implemented in software for execution by various types of processors. An identified module of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions, which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module may not be physically located together, but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the module and achieve the stated purpose for the module.

[00181] Indeed, a module of executable code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network. The modules may be passive or active, including agents operable to perform desired functions.

[00182] Reference throughout this specification to "an example" or "exemplary" means that a particular feature, structure, or characteristic described in connection with the example is included in at least one embodiment of the present technology. Thus, appearances of the phrases "in an example" or the word "exemplary" in various places throughout this specification are not necessarily all referring to the same embodiment.

[00183] As used herein, a plurality of items, structural elements, compositional elements, and/or materials may be presented in a common list for convenience. However, these lists should be construed as though each member of the list is individually identified as a separate and unique member. Thus, no individual member of such list should be construed as a de facto equivalent of any other member of the same list solely based on their presentation in a common group without indications to the contrary. In addition, various embodiments and example of the present technology may be referred to herein along with alternatives for the various components thereof. It is understood that such embodiments, examples, and altematives are not to be construed as defacto equivalents of one another, but are to be considered as separate and autonomous representations of the present technology.

[00184] Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided, such as examples of layouts, distances, network examples, etc., to provide a thorough understanding of embodiments of the technology. One skilled in the relevant art will recognize, however, that the technology can be practiced without one or more of the specific details, or with other methods, components, layouts, etc. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the technology.

[00185] While the forgoing examples are illustrative of the principles of the present technology in one or more particular applications, it will be apparent to those of ordinary skill in the art that numerous modifications in form, usage and details of implementation can be made without the exercise of inventive faculty, and without departing from the principles and concepts of the technology. Accordingly, it is not intended that the technology be limited, except as by the claims set forth below.

Claims

What is claimed is:

1. An apparatus of a proximity service (ProSe) function of a core network in a cellular communications network, the apparatus comprising one or more processors and memory configured to:

process, at the ProSe function, an internal device-to-device (D2D) user equipment (UE) identifier of one or more D2D UEs, an external D2D UE identifier of the one or more D2D UEs, and an internal relay UE identifier, received from a relay UE to enable the core network and one or more extemal entities to communicate with the one or more D2D UEs;

associate, at the ProSe function, the external D2D UE identifier of the one or more D2D UEs with the internal relay UE identifier of the relay UE to enable one or more extemal entities to communicate with the one or more D2D UEs using the external D2D UE identifier;

associate, at the ProSe function, the D2D UE identifier of the one or more D2D UEs with the internal relay UE identifier of the relay UE to enable the cellular communications network to communicate with the one or more D2D UEs using the internal D2D UE identifier; and

communicate one or more communication messages via the relay UE to the one or more D2D UEs.

2. The apparatus of claim 1, wherein the internal D2D UE identifier and the internal relay UE identifier of the relay UE are each a unique UE identity assigned to the one or more D2D UEs or the relay UE, a media access control (MAC) address, or an international mobile subscriber identity.

3. The apparatus of claim 1 or 2, wherein the one or more processors and

memory are further configured to:

link the internal relay UE identifier and the internal D2D UE identifier; store the internal D2D UE identifier and the internal relay UE identifier in the core network for addressing the one or more D2D UEs; or perform a location update procedure to locate the one or more D2D

UEs.

The apparatus of claim 1, wherein the one or more processors and memory are further configured to: send to the relay UE a trigger message requesting to communicate with the one or more D2D UEs.

The apparatus of claim 1 or 4, wherein the one or more processors and memory are further configured to: receive, from the relay UE, a response message, sent to the relay UE from the one or more D2D UEs, indicating receipt of the trigger message.

The apparatus of claim 5, wherein the one or more processors and memory are further configured to:

receive a notification from the relay UE that a trigger message was successfully delivered to the one or more D2D UEs prior to an expiration of a selected time period.

The apparatus of claim 1 or 6, wherein the one or more processors and memory are further configured to: receive a notification from the relay UE that a trigger message was unsuccessfully delivered to the one or more D2D UEs prior to an expiration of a selected time period.

The apparatus of claim 1, wherein the one or more processors and memory are further configured to: identify a location of the one or more D2D UEs using the internal D2D UE identifier.

The apparatus of claim 1, wherein the one or more processors and memory are further configured to: map a media access control (MAC) address of the one or more D2D UEs to the external D2D UE identifier of the one or more D2D UEs to enable one or more external entities that are external to the wireless communication network to communicate with the one or more D2D UEs.

10. The apparatus of claim 1 or 9, wherein the one or more processors and memory are further configured to: receive one or more messages from the one or more external entities to communicate with the one or more D2D UEs.

11. The apparatus of claim 10, wherein the one or more processors and memory are further configured to: forward via the relay UE, to the one or more D2D UEs, the one or more messages received from the one or more external entities.

12. An apparatus of a gateway user equipment (UE), the gateway UE configured to support direct device-to-device (D2D) communication within a wireless communication network, the apparatus comprising one or more processors and memory configured to:

process at the gateway UE, an internal D2D UE identifier and an external D2D UE identifier of a D2D UE, received from the D2D UE;

signal a transceiver at the gateway UE, to transmit to a Prose function of the wireless communication network, an internal gateway UE identifier of the gateway UE and the internal D2D UE identifier and the external D2D UE identifier of the D2D UE to enable the wireless communication network and one or more external entities to communicate with the D2D UE, wherein:

the internal gateway UE identifier and the internal D2D identifier enables the D2D UE to be addressed and registered with the wireless communication network, and the external D2D UE identifier enables the D2D UE to be addressed by the one or more external entities that are external to the wireless communication network; and

relay one or more communication messages between the D2D UE and one or more of the wireless communication network and the one or more external entities.

13. The apparatus of claim 12, wherein the internal D2D UE identifier of the D2D UE and an internal gateway UE identifier of the gateway UE are each a unique UE identity assigned to the D2D UE or the gateway UE, a media access control (MAC) address, or an international mobile subscriber identity.

14. The apparatus of claim 12 or 13, wherein the one or more processors and memory are further configured to link the internal gateway UE identifier and the internal D2D UE identifier, wherein the internal D2D UE identifier and the internal gateway UE identifier are stored in the wireless communication network for addressing the D2D UE.

15. The apparatus of claim 12, wherein the one or more processors and memory are further configured to receive, from the wireless communication network, a trigger message requesting to communicate with the D2D UE.

16. The apparatus of claim 12 or 15, wherein the one or more processors and memory are further configured to send, to the D2D UE, the trigger message received from the wireless communication network.

17. The apparatus of claim 16, wherein the one or more processors and memory are further configured to signal to the transmitter of the gateway UE a response message to transmit to the wireless communication network, received from the D2D UE, indicating receipt of the trigger message.

18. The apparatus of claim 16, wherein the one or more processors and memory are further configured to:

notify the wireless communication network that the trigger message was successfully delivered to the D2D UE prior to the expiration of a selected time period; or

notify the wireless communication network that the trigger message was unsuccessfully delivered to the D2D UE prior to expiration of the selected time period.

19. The apparatus of claim 12, wherein the one or more processors and memory are further configured to forward one or more messages received from the wireless communication network to the D2D UE.

20. The apparatus of claim 12, wherein the one or more processors and memory are further configured to communicate with the D2D UE using a PC5 communication interface.

21. The apparatus of claim 12 or 20, wherein the one or more processors and

memory are further configured to:

Identify a location of the D2D UE using the internal D2D UE identifier; or notify the wireless communication network of the location of the D2D UE.

22. The apparatus of claim 12 or 13, wherein the one or more processors and

memory are further configured to:

map a media access control (MAC) address of the D2D UE to the external D2D UE identifier to enable one or more external entities that are external to the wireless communication network to communicate with the D2D UE;

receive one or more messages from the one or more external entities to communicate with the D2D UE; or

forward, to the D2D UE, the one or more messages received from the one or more external entities.

23. The apparatus of claim 12, wherein the apparatus includes at least one of an antenna, a touch sensitive display screen, a speaker, a microphone, a graphics processor, a baseband processor, an application processor, internal memory, a non-volatile memory port, and combinations thereof.

24. At least one machine readable storage medium having instructions embodied thereon for a relay user equipment (UE) to support direct device-to-device (D2D) communication within a wireless communication network, the instructions when executed by one or more processors and memory cause the relay UE to:

process at the relay UE, an internal D2D UE identifier and an external D2D UE identifier of a D2D UE, received from one or more D2D UEs; signal a transceiver at the relay UE, to transmit to the wireless communication network, an intemal relay UE identifier of the relay UE and the internal D2D UE identifier and the external D2D UE identifier of the one or more D2D UEs to enable the wireless communication network and one or more external entities to communicate with the one or more D2D UEs; and relay one or more communication messages between the one or more D2D UEs and one or more of the wireless communication network and the one or more external entities.

25. The at least one machine readable storage medium of claim 24, wherein the internal D2D UE identifier of the one or more D2D UEs is a unique UE identity assigned to the one or more D2D UEs, a media access control (MAC) address, or an international mobile subscriber identity, and the internal relay UE identifier and the intemal D2D identifier enables the one or more D2D UE to be addressed and registered with the wireless communication network, and the external D2D UE identifier enables the one or more D2D UEs to be address by the one or more external entities that are external to the wireless communication network.

26. The at least one machine readable storage medium of claim 24, further

comprising instructions which when executed cause the relay UE to:

communicate with the one or more D2D UEs using a PC5 communication interface; or

relay the one or more communication messages between the one or more D2D UEs and one or more of a proximity service (ProSe) function of the wireless communication network and the one or more external entities.

27. The at least one machine readable storage medium of claim 24 or 26, further comprising instructions which when executed cause the relay UE to:

receive, from the ProSe function, a trigger message requesting to communicate with the one or more D2D UEs;

communicate, to the one or more D2D UEs, the trigger message received from the ProSe function; or

receive a response message, received from the one or more D2D UEs, indicating receipt of the trigger message.

28. The at least one machine readable storage medium of claim 24 or 26, wherein the one or more processors and memory are further configured to:

notify the ProSe Function the trigger message was successfully delivered to the one or more D2D UEs prior to the expiration of a selected time period; or

notify the ProSe Function the trigger message was unsuccessfully delivered to the one or more D2D UEs prior upon expiration of the selected time period.

29. The at least one machine readable storage medium of claim 24, wherein the one or more processors and memory are further configured to:

link the internal relay UE identifier and the internal D2D UE identifier; identify a location of the one or more D2D UEs using the internal D2D UE identifier of the one or more D2D UEs; or

notify the wireless communication network of the location of the one or more D2D UEs.

30. The at least one machine readable storage medium of claim 24 or 25, wherein the one or more processors and memory are further configured to:

map a media access control (MAC) address of the one or more D2D UEs to the external D2D UE identifier of the one or more D2D UEs to enable one or more external entities that are external to the wireless communication network to communicate with the one or more D2D UEs; receive one or more messages from the one or more extemal entities to communicate with the one or more D2D UEs; or

forward, to the one or more D2D UEs, the one or more messages received from the one or more external entities.