TW201731320A - Downlink reachability for ultra low power saving devices using D2D - Google Patents

Abstract

An apparatus for use in a remote UE of a ProSe network facilitates downlink reachability of the remote UE. The apparatus includes a processing circuit configured to detect a paging message from an eNodeB of the ProSe network, over an air interface between the eNodeB and the remote UE or through a relay UE of the ProSe network over a PC5 interface between the relay UE and the remote UE. The processing circuit is further configured to generate and transmit a connection request message to the relay UE, in response to receiving the paging message, to establish a direct connection between the remote UE and the relay UE. Further, the processing circuit is configured to detect downlink data from the eNodeB through the relay UE over the PC5 interface using EPS bearer of the remote UE or the relay UE, in response to providing the connection request message.

Description

Downlink reachability of ultra low power savers using device-to-device communication (D2D)

The present invention relates to Proximity Services (ProSe) networks, and more particularly to apparatus and methods for receiving downlink (DL) data under a super power saver in a ProSe network.

In recent years, the demand for access to fast-moving wireless data for mobile electronic devices has stimulated the development of the Third Generation Partnership Project (3GPP) Long Term Evolution (LTE) communication system (hereinafter referred to as "LTE System"). Device-to-device (D2D) communication between nearby mobile devices increases spectrum utilization, overall throughput and energy consumption, while enabling new peer-to-peer and location-based applications and services. The primary use case for driving D2D communication is in a fallback public safety network where the D2D enabled LTE device must function when the cellular network is unavailable or faulty.

So far, ProSe-based D2D communication systems have focused on public safety services, while general use, for example, wearable devices Aid, most of them are out of scope. With advanced relay capabilities and power optimization for D2D devices, ProSe-based D2D communication can be used under normal use, for example, low-power wearable UE support.

100‧‧‧Proximity Service (ProSe) System

110‧‧‧Remote User Equipment (UE)

120‧‧‧ProSe UE to network relay

130‧‧‧Evolved Node B

140‧‧‧Evolution Packet Core (EPC)

150‧‧‧PC5 interface

160‧‧‧Old Uu interface

180‧‧‧S1 interface

200‧‧‧ProSe system

210‧‧‧Remote UE

212‧‧‧Relay UE

214‧‧‧Evolved Node B

216‧‧‧Action Management Entity (MME)

218‧‧‧Service Gateway (S-GW)

219‧‧‧Initial Attachment Establishment Procedure

220‧‧‧Connection request message

221‧‧‧DL notification message

222‧‧‧Connection response message

223‧‧‧Call Message

226‧‧‧ side link UE information message

228‧‧‧S1-AP message

231‧‧‧Service Request Procedure

232‧‧‧S1-U tunnel establishment

233‧‧‧Service Request Procedure

234‧‧‧DL notification response message

300‧‧‧ProSe system

310‧‧‧Remote UE

312‧‧‧Relay UE

312a‧‧‧paired call indication message

312b‧‧‧paired call indication message

314‧‧‧Evolved Node B

316‧‧‧Action Management Entity (MME)

318‧‧‧Service Gateway (S-GW)

319‧‧‧Initial Attachment Establishment Procedure

320‧‧‧PC5 direct communication request message

321‧‧‧pair call indication message

321a‧‧‧pair call indication message

321b‧‧‧pair call indication message

323‧‧‧Call Message

324‧‧‧DL Information Notification Message

325‧‧‧Connection request message

326‧‧‧ Side Link UE Information Message

327‧‧‧Connection response message

328‧‧‧S1-AP message

329‧‧‧Service Request Procedure

331‧‧‧Service Request Procedure

332‧‧‧S1-U tunnel establishment

333‧‧‧Service Request Procedure

334‧‧‧DL Information Notification Response Message

400‧‧‧ equipment

410‧‧‧ Receiver Circuit

420‧‧‧Transmitter circuit

430‧‧‧Processing circuit

440‧‧‧ memory circuit

500‧‧‧ equipment

510‧‧‧ Receiver Circuit

520‧‧‧Transmitter circuit

530‧‧‧Processing Circuit

540‧‧‧ memory circuit

600‧‧‧ equipment

610‧‧‧Transmitter circuit

620‧‧‧ Receiver Circuit

630‧‧‧Processing circuit

640‧‧‧ memory circuit

700‧‧‧ method

702‧‧‧Steps

704‧‧‧Steps

706‧‧‧Steps

708‧‧ steps

710‧‧ steps

800‧‧‧ method

802‧‧ steps

804‧‧‧ steps

806‧‧‧Steps

808‧‧‧Steps

810‧‧‧Steps

900‧‧‧ method

902‧‧ steps

904‧‧‧Steps

906‧‧‧Steps

908‧‧‧Steps

910‧‧ steps

1000‧‧‧ method

1002‧‧‧Steps

1004‧‧‧Steps

1006‧‧‧Steps

1008‧‧‧Steps

1010‧‧‧Steps

1012‧‧‧Steps

1100‧‧‧ method

1102‧‧‧Steps

1104‧‧‧Steps

1106‧‧‧Steps

1108‧‧‧Steps

1110‧‧‧Steps

1112‧‧‧Steps

1200‧‧‧ method

1202‧‧‧Steps

1204‧‧‧Steps

1206‧‧‧Steps

1208‧‧‧Steps

1210‧‧‧Steps

1212‧‧‧Steps

1300‧‧‧User Equipment (UE) device

1302‧‧‧Application Circuit

1304‧‧‧Base frequency circuit

1304a‧‧‧ fundamental frequency processing circuit

1304b‧‧‧ fundamental frequency processing circuit

1304c‧‧‧ fundamental frequency processing circuit

1304d‧‧‧ fundamental frequency processing circuit

1304e‧‧‧Central Processing Unit (CPU)

1304f‧‧‧Audio digital signal processing circuit

1306‧‧‧RF (RF) circuits

1306a‧‧‧Mixer circuit

1306b‧‧‧Amplifier Circuit

1306c‧‧‧Filter circuit

1306d‧‧‧Synthesizer circuit

1308‧‧‧ Front End Module (FEM) Circuit

1310‧‧‧Antenna

Some examples of circuits, devices, and/or methods are described below by way of example only. In this document, reference will be made to the drawings.

1 is a simplified block diagram of a ProSe system in accordance with a currently enhanced LTE device-to-device (D2D) ProSe work item in accordance with one embodiment of the present invention.

2 is a diagram depicting downlink reachability of a remote UE in a ProSe system based on receiving a paging message from an eNodeB associated therewith, based on an empty intermediation plane, in accordance with an embodiment of the present invention.

3 is a diagram depicting downlink reachability of a remote UE in a ProSe system based on receiving a paging message from an eNodeB associated therewith via a relaying UE over a PC5 interface, in accordance with an embodiment of the present invention.

4 is a block diagram of a device for use in a remote or wearable user equipment (UE) in a ProSe system in accordance with various embodiments described herein, which facilitates based on the remote UE The downlink reachability of the paging message received from the eNodeB.

5 is a block diagram of a device for use in a relay user equipment (UE) in a ProSe system in accordance with various embodiments described herein, which facilitates downlinking in a remote UE Up to nature.

6 is a block diagram of an apparatus for use in an eNodeB in a ProSe system in accordance with various embodiments described herein, which facilitates downlink reachability in a remote UE associated therewith .

7 is a flow chart of a method for a remote UE in a ProSe system including a relay UE and an eNodeB associated therewith, which facilitates downlink of the remote UE, in accordance with an embodiment of the present invention. Accessibility.

8 is a flow chart of a method for a remote UE in a ProSe system including a relay UE and an eNodeB associated therewith, which facilitates downlink of the remote UE, in accordance with an embodiment of the present invention. Accessibility.

9 is a flow chart of a method for relaying a UE in a ProSe system including a remote UE and an eNodeB associated therewith, which facilitates downlink of the remote UE, in accordance with an embodiment of the present invention. Accessibility.

10 is a flow chart of a method for relaying a UE in a ProSe system including a remote UE and an eNodeB associated therewith, which facilitates downlink of the remote UE, in accordance with an embodiment of the present invention. Accessibility.

11 is a flow chart of a method for an eNodeB in a ProSe system including a remote UE and a relay UE associated therewith, which facilitates the downlink of the remote UE, in accordance with an embodiment of the present invention. Accessibility.

12 is a flow chart of a method for an eNodeB in a ProSe system including a remote UE and a relay UE associated therewith, which facilitates the downlink of the remote UE, in accordance with an embodiment of the present invention. Accessibility.

13 is a diagram showing example components of a User Equipment (UE) device for one embodiment.

SUMMARY OF THE INVENTION AND EMBODIMENT

In one embodiment of the invention, a device for use in a remote UE comprising a relaying UE and a ProSe network of an eNodeB associated therewith is disclosed. The apparatus includes a memory circuit configured to store a remote UE ID associated with the remote UE and a paired association ID indicating a pairwise association of the remote UE with the relay UE. The apparatus further includes processing circuitry configured to receive, via the interfacing plane between the eNodeB and the remote UE, or through the PC5 interface between the relay UE and the remote UE, via the relay UE, including A paging message of the remote UE ID of the remote UE of the eNodeB. In some embodiments, the paging message informs the remote UE about the availability of downlink (DL) data for the far end UE. The processing circuit is further configured to generate a connection request message including a cause value for the paging in response to receiving the paging message, to be subsequently sent to the PC5 interface between the remote UE and the relay UE via a transmitting circuit Relay the UE. In some embodiments, the connection request message is grouped to form a relay UE to establish a direct connection between the remote UE and the relay UE to receive the DL data via the relay UE. In addition, the processing circuit is configured to receive, by the PC5 interface, a downlink data signal including the DL data from the eNodeB via the PC5 interface in response to transmitting the connection request message.

In one embodiment of the invention, a method is disclosed for including a distal end A device used in a relay UE of a UE and a ProSe network of an eNodeB associated therewith. The device includes: a memory circuit configured to store a relay UE ID associated with the relay UE, a remote UE ID of the remote UE, and a pair indicating the relay UE and the remote UE And a processing circuit configured to receive, by the PC5 interface between the remote UE and the relay UE, a connection request message including a cause value of a paging from the remote UE. In some embodiments, the cause value of the paging is indicative of an indication received at the remote UE through the null intermediate plane or via the relay UE from the eNodeB to the downlink (DL) data of the remote UE. Paging message for availability. In some embodiments, the connection request message is grouped to form a relay UE to establish a direct connection with the remote UE, so that the remote UE receives the remote UE from the eNodeB via the relay UE. The associated DL data. The processing circuit is further configured to establish a direct connection between the relay UE and the remote UE based on the connection request message; and when establishing the direct connection between the relay UE and the remote UE, Receiving, by the remote UE or the evolved packet system (EPS) bearer of the relay UE, a downlink data signal including the DL data from an S-gate (S-GW) associated with the eNodeB to transmit the The PC5 interface is then sent to the remote UE.

In one embodiment of the invention, an apparatus for use in an eNodeB comprising a ProSe network of a remote UE and its associated relay UE is disclosed. The apparatus includes: a memory circuit configured to store a relay UE ID associated with the relay UE and a remote UE ID of the remote UE; and processing circuitry configured to form an MME to be associated therewith Place Receiving, the paging message associated with the remote UE is provided to the sending circuit, so as to pass through an empty inter-plane between the eNodeB and the remote UE, or through a PC5 interface between the relay UE and the remote UE. The relay UE is then sent to the remote UE. In some embodiments, the paging message indicates the availability of downlink (DL) data for the remote UE. The processing circuit is further configured to receive a side link UE information message from the relay UE through the receiving circuit in response to providing the paging message, wherein the side link UE information message indicates the location at the remote UE The receipt of a paging message or the establishment of a direct connection between the remote UE and the relay UE or both. In addition, the processing circuit is configured to use the EPS bearer of the remote UE or the EPS bearer of the relay UE when the side link UE information message indicates that the connection is established between the remote UE and the relay UE. The DL data associated with the remote UE received from the S-Gate (S-GW) associated with the remote UE is forwarded to the remote UE.

The present invention will be described with reference to the drawings, wherein the same elements are used to indicate the same elements, and the structures and devices are not necessarily drawn to scale. As used herein, the terms "component", "system", "interface", "circuit", etc. are intended to mean a computer-related entity, hardware, software (eg, in progress) and/or firmware. . For example, the components can be processing circuits (eg, microprocessor circuits, controllers, or other processing devices), programs, controllers, objects, executables, programs, storage devices, computers, tablet PCs, and/or Or user equipment with processing devices (eg, mobile phones, etc.) Wait). By way of illustration, an application running on a server and the server can also be a component. One or more components can reside within a program and the components can be localized on a computer and/or distributed between two or more computers. A group of elements or a group of other components may be described herein, where the term "group" may be interpreted as "one or more."

Moreover, for example, the components can be executed from a variety of computer readable storage media, such as a module having various data structures stored thereon. The component can communicate via a zone and/or remote program, such as based on signals having one or more data packets (eg, data from one component interacts with another component in a regional system, a distribution system, and/or Across the network, such as the Internet, a regional network, a wide area network, or a network similar to other systems through the signal.

As another example, a component can be a device having a particular function provided by a mechanical portion that is operated by an electrical or electronic circuit, wherein the electrical or electronic circuit can be by a software application or by one or more processing circuits The executed firmware application to operate. The one or more processing circuits can be internal or external to the device and can execute at least a portion of the software or firmware application. As yet another example, a component can be a device that has a particular functionality provided by an electronic component that does not have a mechanical portion; the electronic component can include one or more processing circuitry therein to perform, at least in part, enabling the electronic component Functional soft body and / or firmware.

The exemplary use of words is intended to present concepts in a specific manner. As used in this application, the term "or" is intended to mean an inclusive "or" rather than an exclusive "or". That is, unless otherwise specified or from above It is clarified below, otherwise "X uses A or B" is intended to mean any of the natural inclusions. That is, if X uses A; X uses B; or X uses both A and B, it satisfies "X uses A or B" in any of the foregoing cases. In addition, the articles "a" and "an" are used in the application and the scope of the appended claims, unless otherwise indicated. To indicate "one or more". In addition, the terms "including", "includes", "having", "has", "with" are used in the detailed description and the scope of the claims. To the extent that it is a variant of the term, the term is intended to be inclusive in a manner similar to the term "comprising".

In the following description, numerous details are set forth to provide a more thorough explanation of the embodiments of the invention. It will be apparent to those skilled in the art, however, that the embodiments of the invention may be practiced without these specific details. The structures and devices of the present invention are shown in the form of a block diagram and not in detail to avoid obscuring the embodiments of the present invention. Furthermore, the features of the various embodiments described hereinafter may be combined with each other unless specifically stated otherwise.

The current enhanced LTE device-to-device ProSe work item (ie, 3GPP TS 23.303, "Technical Specification Group Service and System Aspects; Proximity Based Service (ProSe)") acts as a role between the remote UE and the eNodeB. The UE relaying the communication (also referred to herein as a "relay UE") provides for communication between the remote UE and the eNodeB. In the current enhanced LTE device-to-device ProSe work item, relay The UE functions as a Layer 3 relay (ie, an IP router), and the relay UE supports the following functions: unicast relay: based on a remote UE that is not directly served by the E-UTRAN. For a direct communication, including support for relaying unicast traffic (UL and DL) between the remote UE and the E-UTRAN, the ProSe UE to network relay provides a common Layer 3 forwarding function, It relays any type of IP traffic associated with public safety communications.

eMBMS Relay Support: One-to-many communication, which includes relaying support for Multimedia Broadcast Multicast Service (eMBMS) for remote UEs served by the UE to the network (UE to NW) NW trunk.

E-UTRAN Cell Global Identifier (ECGI) announcement: an announcement by the ProSe UE to the ECG of the NW relay, allowing the remote UE served by the NW relay by the ProSe UE to receive the cell serving the ProSe UE to the NW relay The value of ECGI.

1 is a simplified block diagram of a ProSe system 100 for a device-to-device ProSe work item in accordance with current enhanced LTE, in accordance with one embodiment of the present invention. The ProSe network 100 includes a remote UE 110, a ProSe UE-to-network relay 120, an eNodeB 130, and an evolved packet core (EPC) 140 associated with the eNodeB 130. In some embodiments, eNodeB 130 is referred to as "network" along with EPC 140. In some embodiments, EPC 140 includes a Mobility Management Entity (MME) and a Serving Gateway (S-GW). In some embodiments, the MME processes the control plane of the LTE architecture. The MME handles signaling related to the actions and security for the eNodeB access. The gateway, for example, the servo GW processes LTE The user plane of the architecture. The S-GW sends an IP data traffic between the user equipment (UE) and the external network. As shown in FIG. 1, the far end UE 110 is generally considered to be outside the coverage of the network, but relay support can be used to relay the network 120 via the ProSe UE (sometimes referred to herein as " The UE is relayed 120" or "relay" 120) to access the network. Alternatively, in other embodiments, the far end UE 110 may be within the coverage of the network. The eNodeB 130 is configured to serve as a communication point with which the relay UE 120 can communicate to access the EPC 140. The primary use case that drives this situation is public safety.

The remote UE 110 can access the network through the relay UE 120 using an interface called the "PC5" interface 150. The PC5 interface 150 is a direct communication interface between two ProSe support devices. In addition, relay UE 120 may connect to eNodeB 130 using an older Uu interface 160 (ie, a null interfacing plane) between relay UE 120 and eNodeB 130, and thereby connect to EPC 140. The eNodeB 130 can access the EPC 140 using the S1 interface 180. In an embodiment where the remote UE is within the coverage of the network, the remote UE can simultaneously support the connection through the PC5 interface 150 or an old Uu interface located between the remote UE 110 and the eNodeB 130. In some embodiments, the far end UE 110 includes a low power, low re-detachment device, such as a wearable UE such as a smart watch, which is preferably connected via the relay UE 120, rather than through the legacy version The Uu interface is directly connected to the eNodeB 130 to save power consumption. In some embodiments, the low power remote UE 110 relies on short range communication for transferring data in both the uplink and downlink directions. As described in this article In an embodiment, it is assumed that the remote UE and the relay UE are aware of their pairwise associations (eg, using a discovery procedure). Moreover, in some embodiments, it is assumed that the remote UE 110 is in an idle mode with respect to the Radio Resource Control (RRC) system that is through the Uu interface. In other words, the remote UE does not have any connection or bearer established with the network and communicates with the network using the PC5 interface to save power. Relay UE 120 is assumed to be within coverage for substantially all of the time period. The relay UE may be in an RRC idle mode or an RRC connected mode.

The introduced LTE ProSe framework can be further enhanced to support the general use of any type of data communication traffic between UEs, and also substantially improve network performance and user experience. So far, the design of the ProSe has focused on public safety services, while the general use is mainly outside the scope. Further enhancements to the side link empty intermediaries (i.e., PC5 interface 150) can be used for network optimization and have the potential to improve the user experience and increase the amount of service. For example, one of the general purposes of device-to-device (D2D) communication between the remote UE 110 and the relay UE 120 is the use of traffic management/unloading and its inherent multi-link attributes.

Embodiments disclosed herein relate to downlink reachability for use by remote UEs within and outside the coverage of the network to enable the remote UE to receive downlinks from the network (DL) )data. The basic principle is how the remote UE 110 (i.e., the low power wearable UE) in the coverage but in the idle mode can pass through the relay UE 120 through the PC5 interface 150 (which can be in the idle mode or the connected mode) )Come Receive data. One way to enable this is to use the L3 trunk to use the agreed Layer 3 relay (ie, IP router) to forward the EPS bearer using the relay UE 120 between the remote UE 110 and the network. Any type of IP traffic (eg, data). The relay UE 120 may only have a limited number of EPS bearers established, and thus, the use of the EPS bearer of the relay UE 120 to forward IP traffic between the remote UE 110 and the network limits the capacity of the network.

An alternative solution includes a Layer 2 or L2 relay, wherein the far end UE 110 is using the EPS bearer established for the far end UE 120 in the network via the relay UE 120 at the remote UE 110 and the network Transfer any type of IP traffic (for example, data). That is, the far end UE 110 can send or receive data that can be mapped in the network through its own EPS bearer. In other embodiments, downlink reachability is also considered for remote UEs outside the coverage of the network. In current LTE systems (from Release 13), power optimization and control plane enhancement are not considered to send or receive data through the PC5 interface.

In the embodiments described herein, different methods of downlink reachability under the remote UE in the RRC idle mode through the PC5 interface 150 are proposed. In some embodiments, it is assumed that the remote UE is within the coverage of the network, and in other embodiments, the remote UE is assumed to be out of coverage. In some embodiments, the proposed method of downlink reachability enables remote UE 110 to receive downlink (DL) data from the network via relay UE 120. In particular, it is proposed in one embodiment of the invention to be based on paging messages received from eNodeB 130 at remote UE 110. A first method of receiving DL data from the eNodeB 130 (not shown). In this embodiment, the paging message is received from the eNodeB 130 via an empty inter-plane between the remote UE 110 and the eNodeB 130. A second method for receiving DL data from the eNodeB 130 at the remote UE 110 based on a paging message (not shown) received from the eNodeB 130 is presented in another embodiment of the present invention. In this embodiment, the paging message is received from the eNodeB 130 via the relay UE 130 via the PC5 interface 150.

2 depicts a downlink UE 210 downlink in a ProSe system 200 that receives paging messages from an eNodeB associated with it based on an empty inter-plane between the remote UE and the eNodeB, in accordance with an embodiment of the present invention. Up to nature. In some embodiments, the proposed method of downlink reachability enables remote UE 210 to receive downlink (DL) data from the network via relay UE 212. The ProSe system 200 includes a remote UE 210, a relay UE 212, an eNodeB 214, an MME 216, and an S-GW 218. In some embodiments, MME 216 and S-GW 218 are Evolved Packet Core (EPC) or "core network." In some embodiments, eNodeB 214, MME 216, and S-GW 218 are collectively referred to as the "network." In some embodiments, it is assumed that both the far end UE 210 and the relay UE 212 pass the initial attach setup procedure 219 prior to initiating DL data transfer from the network to the remote UE 210 via the relay UE 212. It is temporarily stored on the network. In some embodiments, information regarding the pairwise association between the remote UE 210 and the relay UE 212 is provided to the network during the initial attach setup procedure 219. In some embodiments, the pairwise connection between the remote UE 210 and the relay UE 212 is predetermined, while in other implementations In the example, other programs (e.g., discovery) are used to determine the paired association. In some embodiments, the pairwise association ID identifying the pairwise association between the remote UE 210 and the relay UE 212 is generated at the MME 216 and is provided to the far during the initial attachment setup procedure 219. The UE 210 and the relay UE 212. The remote UE 210 is in RRC idle mode and the relay UE 212 is in RRC connected mode. However, in other embodiments, relay UE 212 may be in RRC idle mode.

When the S-GW 218 has DL data available to the remote UE 210, the DL data transfer to the remote UE 210 is initiated by the S-GW 218. In some embodiments, the DL data transfer is initiated by transmitting a DL notification message 221 to the MME 216 that includes the remote ID associated with the remote UE 210. In some embodiments, the DL notification message 221 further includes an EPS bearer ID of the remote UE 210 and the relay UE 212. In some embodiments, the DL notification message 221 is generated at the S-GW 218 and provides an indication of the availability of the DL data for the remote UE 210 to the MME 216. Upon receiving the DL notification message 221, the MME 216 is grouped to generate a paging message 223 based on the DL notification message 221 for subsequent transmission to the eNodeB 214. In some embodiments, the paging message 223 includes the far-end ID of the far-end UE 210, and the eNodeB 214 is further configured to transmit the paging message 223 to the far-end through an empty intermediate plane between the eNodeB 214 and the remote UE 210. UE 210. In some embodiments, the eNodeB 214 is grouped to form a remote UE 210 to check the paging message through the null plane to enable the remote UE 210 to receive DL data. In some embodiments, the far end UE 210 is grouped to monitor by far The paging message is received from the eNodeB 214 by the paging occasion of the UE 210. In some embodiments, the far end UE 210 is configured to monitor the paging occasion of the far end UE 210 based on the far end UE ID.

Upon receiving the paging message 223, the remote UE 210 is grouped to form a connection request message 220 that includes the cause value of the paging or DL data. The remote UE 210 is further configured to transmit a connection request message 220 to the relay UE 212 through the PC5 interface between the remote UE 210 and the relay UE 212 to establish direct communication with the relay UE 212. The UE 210 receives the DL data. In some embodiments, the cause value of the paging in the connection request message 220 indicates receipt of the paging message at the remote UE 210. In some embodiments, the relay UE 212 is configured to generate and send a connection response message 222 to the remote UE 210 as an acknowledgement to receive the connection request message 220. In this embodiment where the relay UE 212 is in the RRC idle mode, upon receiving the connection request message 220 from the remote UE 210, the relay UE 212 is grouped to establish its own RRC connection and enter the RRC connected mode. In some embodiments, relay UE 210 and remote UE 212 are grouped to perform mutual authentication to confirm the pairwise association between remote UE 210 and relay UE 212. In some embodiments, establishing the RRC connection includes setting an EPS bearer or the radio bearer, eg, a signaling radio bearer (SRB5) for the UE in the network. In some embodiments, in the RRC idle mode, the UE (e.g., relay UE 212) is known for the EPC (but not for the eNodeB 214), while in the RRC connected mode, the UE ( For example, relay UE 212) for both the EPC and the eNodeB 214 It is known.

In some embodiments, relay UE 212 is further configured to generate a side link UE information message 226 including the far end UE ID of remote UE 210 for subsequent transmission to eNodeB 214 to cause remote UE 210 It can be seen by the eNodeB 214 and its associated MME 216 for DL data transfer. In some embodiments, in order to receive DL data at the remote UE 210 using the L2 relay, the EPS bearer of the far end UE 210 must be established in the network. During the L3 relay, the EPS bearer for relaying the UE 212 (which has been established when the relay UE 212 is in the RRC connected mode) is used, and the DL data is received at the far end UE 210. In some embodiments, the relay UE 212 is configured to process the service request procedure to establish the EPS bearer of the far end UE 210 upon receiving the connection request message 220 from the remote UE 210.

In some embodiments, the service request procedure used to establish the EPS bearer of the far end UE 210 is initiated or executed by the relay UE 212 on behalf of the far end UE 210. In such embodiments, the service request procedure is performed by the relay UE 212 by providing the eNodeB 214 with one or more messages including the relay UE ID and the paired associated ID to enable The S1-U tunnel of the remote UE 210 in the core network is established 232. Alternatively, in other embodiments, the service request procedure to establish the EPS bearer of the remote UE 210 is performed by the remote UE 210 via the relay UE 212. In such embodiments, the remote UE 210 is configured to execute the service request procedure by generating one or more messages (eg, an RRC Connection Setup message), which is then carried in the container through the PC5 interface. Within (container), and relayed by relay UE 212 to eNodeB 214 for further processing. The EPS bearer setup initiated by the remote UE 210 based on the service request from the relay UE 212 implies that the remote UE 210 is still in RRC idle with respect to the RRC connection setup (or about the network) through the null plane. In the mode, however, the EPS bearer of the far end UE 210 is still activated to be used for data transfer in the path of the S-GW-eNodeB-Relay UE.

In some embodiments, the eNodeB 214 is grouped to generate an S1-AP message 228 including the far end UE ID of the far end UE 210 for subsequent transmission to the MME 216. In some embodiments, the S1-AP message 228 is generated in response to the received side link UE information message 226 and an indication is provided to the MME 216 when the paging message 223 is received at the remote UE 210. In some embodiments, the S1-AP message 228 further includes an EPS bearer ID of the far end UE 210 during the L2 relay or an EPS bearer ID of the relay UE 212 during the L3 relay. In some embodiments, the S1-AP message 228 provides information to the MME 216 on the EPS bearer to be used for transmission of the DL data. Upon receiving the S1-AP message 228, the MME 216 is further grouped to generate a DL notification response message 234 for subsequent transmission to the S-GW. In some embodiments, the content of the S1-AP message 228 and the DL notification response message 234 are the same. Upon receiving the DL Notification Response message 234, the S-GW 218 is grouped to send the DL data to the eNodeB 214 for subsequent transmission to the remote UE 210 via the relay UE 212. In some embodiments, the DL data is transmitted by the S-GW 218 using an EPS bearer (eg, an L2 relay) of the far end UE 210. The DL data, while in other embodiments, the DL data is transmitted by the S-GW 218 using the EPS bearer (e.g., L3 relay) of the relay UE 212 to transmit the DL data.

In some embodiments, after establishing the direct communication between the remote UE 210 and the relay UE 212 through the PC5 interface, the relay UE 210 can reach out of coverage of the network. In such embodiments, the far end UE 210 will continue to receive the DL data via the relay UE 212 until the far end UE 210 becomes inactive for a particular period of time. In this case, the direct connection between the remote UE 210 and the relay UE 212 is released and the remote UE 210 enters the newly defined PC5 idle mode. During the PC5 idle mode of the remote UE 210, the relay UE 212 buffers the DL data received from the eNodeB 214 until the remote UE 210 establishes a direct communication link with the relay UE 212.

Alternatively, in some embodiments, when the remote UE uses pre-composed resources outside the coverage, a resource restriction pattern may be defined for each remote UE, whereby the remote UE may check for inclusion The paging information of the remote UE ID is used to identify whether the remote UE has any DL data it wants. Moreover, in some embodiments, if the relay UE 212 notifies the eNodeB 214 about the PC5 idle mode of the far end UE 210, the eNodeB 214 can buffer the DL data. In some embodiments, the relay UE 212 uses the side link UE information message 226 to inform the eNodeB 214 about the PC5 idle mode of the far end UE 210.

3 depicts a transmission received from an eNodeB associated therewith via a relay UE based on a PC5 interface, in accordance with an embodiment of the present invention. The far-end UE 310 in the ProSe system 300 of the call message has downlink reachability. In some embodiments, the proposed method of downlink reachability enables the remote UE 310 to receive downlink (DL) data from the network via the relay UE 312. The ProSe system 300 includes a remote UE 310, a relay UE 312, an eNodeB 314, an MME 316, and an S-GW 318. In some embodiments, MME 316 and S-GW 318 include an Evolution Packet Core (EPC) or "Core Network." In some embodiments, eNodeB 314, MME 316, and S-GW 318 are collectively referred to as the "network." In this embodiment, it is assumed that both the relay UE 312 and the remote UE 310 are within the coverage of the network. However, in other embodiments, the remote UE 310 can reach out of coverage of the network.

In some embodiments, it is assumed that both the far end UE 310 and the relay UE 312 are both passed through the initial attach setup procedure 319 prior to initiating the DL data transfer to the far end UE 310 via the relay UE 312. Temporarily save to the network. In some embodiments, the initial attachment procedure 319 is performed when the respective device is turned on. In some embodiments, the PDN connection with the network and the necessary bearers of the remote UE 310 and the relay UE 312 are established during the initial attach procedure 319. In some embodiments, information regarding pairwise associations between the far end UE 310 and the relay UE 312 is provided to the network during the initial attach setup procedure 319. In some embodiments, the pairwise association between the remote UE 310 and the relay UE 312 is predetermined, while in other embodiments other programs (e.g., discovery) are used to determine the pairwise association. In some embodiments, during the initial attach setup procedure 319, identification at the MME 316 is generated at the remote UE 310 and the relay UE 312. The pairs of the pair are associated with the ID and are provided to the remote UE 310 and the relay UE 312. Once the initial attach procedure 319 is completed, the far end UE 310 and the relay UE 312 enter the RRC connected mode.

In some embodiments, once the remote UE 310 selects the relay UE 312 associated with it (e.g., by discovery), the remote UE 310 is configured to send the PC5 direct communication request message 320 to the PC5 interface. Relaying the UE 312 to establish a direct communication link between the remote UE 310 and the relay UE 312 through the PC5 interface, and further for mutual authentication to confirm the pair between the remote UE 310 and the relay UE 312 Association. In some embodiments, the PC5 direct communication request message 320 from the remote UE 320 further includes a request to make a paired page with the relay UE 312. In some embodiments, the PC5 direct communication request message 320 from the remote UE 310 enables paired paging to be established at the relay UE 312, whereby the relay UE 312 can monitor the paging occasion of the remote UE 310 so that A paging message for the remote UE 310 is received from the MME 316.

In some embodiments, the PC5 direct communication request message 320 further includes the remote UE ID to cause the relay UE to calculate the paging occasion of the remote UE 310 (ie, the paging frame and the child to be monitored) Frame) as defined in the 3GPP specification TS36.304. When a paired paging is established between the remote UE 310 and the relay UE 312, the remote UE 310 or the relay UE 312 is grouped to transmit a paired paging indication message (eg, a paired paging indication message 312b or a paired paging indication) Message 312a) to inform eNodeB 314 about the status of the paired page. In some embodiments, the paired paging indication message 321a or 321b includes new or existing a Radio Resource Control (RRC) message and including information about the UE ID (i.e., the relay UE ID for message 321a or the remote UE ID for message 321b), the paired association id, about The transmitting UE is an identification information of the relay UE 312 or the remote UE 310 and an implicit/external paired paging indication.

In some embodiments, upon establishing the paired paging indication message 321, the remote UE 310 or the relaying UE 312 is further grouped to use the tracking area update defined in the 3GPP specifications TS 23.401 and TS 24.301. The (TAU) procedure informs the MME 316 about the status of the paired page. In some embodiments, the paired paging indication message 321a or 321b is further configured to notify the eNodeB 314 about the remote UE 310 and the relay when the pair of paging between the remote UE 310 and the relay UE 312 is released. The release of the state of the paired paging between the UEs 312. In these embodiments, the paired paging indication message 321a or 321b includes information about the UE ID (ie, the relaying UE ID for the message 321a or the remote UE ID for the message 321b), The paired association id, the identification information about the transmitting UE relay UE 312 or the remote UE 310, and the implicit/external release of the paired paging indication.

In some embodiments, once there is data inactivity at the relay UE 312, the RRC connection of the relay UE 312 is released. Moreover, the PC5 communication link between the relay UE 312 and the remote UE 310 is also released, and both the remote UE 310 and the relay UE 312 enter the RRC idle mode. In some embodiments, once the relay UE 312 enters the RRC idle mode, the relay UE 312 is grouped into a paired paging based on the establishment. Status to check the paging message 323 for the remote UE 310 from the eNodeB 314. In other embodiments, even if the relay UE 312 is in the RRC connected mode, the relay UE 312 is configured to check the paging message 323 for the remote UE 310 from the eNodeB 314 based on the established paired paging status. In some embodiments, the paging message 323 indicates the availability of downlink (DL) data for the remote UE 310. In some embodiments, the relay UE 312 is grouped to monitor only the paging occasions of the relay UE 312 to receive the paging message 323. In some embodiments, the paging message 323 includes a paging message associated with the remote UE and a paging message associated with the relay UE. In some embodiments, the paging UE relay 312 is calculated using the relay UE ID as defined in the 3GPP specification TS 36.304. Alternatively, in other embodiments, the relay UE 312 is grouped to both monitor the paging occasion of the relay UE 312 and the paging occasion of the remote UE 310. In such embodiments, the relay UE 312 is grouped to monitor the paging occasion of the remote UE 310 to receive the paging message associated with the remote UE. In some embodiments, the relay UE ID is used to calculate the paging occasion of the relay UE 312, and the remote UE ID is calculated using the remote UE ID as defined in the 3GPP specification TS 36.304. The paging opportunity.

The DL data transfer to the remote UE 310 is initiated by the S-GW 318 when the S-GW 318 has DL data available to the remote UE 310. In some embodiments, the DL data transfer is initiated to send a DL material notification message 324 including the remote ID associated with the remote UE 310 to the MME 316. In some embodiments, the DL data notification message 324 is further The steps include the EPS bearer IDs of the remote UE 310 and the relay UE 312. In some embodiments, DL data notification message 324 is generated at S-GW 218 and provides an indication to MME 316 regarding the availability of DL data for remote UE 310. Upon receiving the DL data notification message 324, based on the DL data notification message 324, the MME 316 is grouped to generate a paging message 323 for the remote UE 310. The MME 316 is further configured to transmit the paging message 323 to the eNodeB 314 based on the information of the paired paging states of the remote UE 310 and the relay UE 312 (ie, belonging to the tracking area in which the relay UE 312 is temporarily stored). The eNodeB).

In some embodiments, the eNodeB 314 is grouped to forward or transmit the paging message 323 received from the MME 316 to the relay UE 312 for subsequent transmission to the remote UE 310 in the paging occasion of the relay UE 312. In some embodiments, the paging message 323 includes paging information for relaying the UE 312 and the remote UE 310, and determining the relay UE using the relay UE ID as defined in the 3GPP specification TS 36.331 The timing of the paging of 312. Alternatively, in other embodiments, the eNodeB 314 is configured to forward or transmit the paging message 323 received from the MME 316 to the relay UE in the paging occasion based on the remote UE 310 determined by the remote UE ID. 312 for subsequent transmission to the remote UE 310. In these embodiments, if the paging time of the remote UE 310 is different from the paging occasion of the relay UE 312, the paging message as defined in the 3GPP specification TS 36.331 includes only the remote end. The paging information of the UE 310.

Upon receiving the paging message 323, the relay UE 312 performs the The service requesting procedure 329 of the UE 312 is relayed and enters the RRC connected mode. In some embodiments, entering the RRC connected mode causes the relay UE 312 to transfer the paging message 323 to the far end UE 310. In some embodiments, the paging message 323 is transmitted from the relay UE 312 to the remote UE 310 based on a periodic discovery message using a Physical Downlink Shared Channel (PSDCH). In such embodiments, the remote UE 310 is configured to monitor periodic announcement messages including the periodic discovery message from the relay UE 312 (e.g., per N seconds of configuration) to receive paging messages from the eNodeB 314. 323. In some embodiments, the paging message 323 is transmitted from the relay UE 312 to the remote UE 310 using one of the pre-configured resource patterns with the paging occasion (PO) being monitored by the remote UE 310 or multiple discovery resource elements. .

In some embodiments, the paging message 323 is relayed from the side link paging control channel defined by the PC5 interface that is used to transmit the remote UE 310 periodically to check the downlink paging information and system information. The UE 312 sends to the far end UE 310. In these embodiments, the relay UE 312 can use the PC5 interface to time-divide the remote UEs 310 into different paging occasions by utilizing the periodicity of the paging used to check the paging from the relaying UE 312. Moreover, in some embodiments, the paging message 323 is transmitted from the relay UE 312 through the PC5 interface using resources configured by the eNodeB 314 for relay communications periodically checked or read by the remote UE 310. It is sent directly to the remote UE 310.

Upon receiving the paging message 323, the remote UE 310 is grouped to form a connection request message 325 that generates a cause value including a paging or DL data. far The end UE 310 is further configured to transmit a connection request message 325 to the relay UE 312 through the PC5 interface between the remote UE 310 and the relay UE 312 to establish direct communication with the relay UE 312 for The UE 310 is relayed to receive the DL data. In some embodiments, the cause value of the paging in the connection request message 325 indicates the receipt of the paging message 323 at the remote UE 310. In some embodiments, the relay UE 312 is configured to generate a connection response message 327 and send a connection response message 327 to the remote UE 310 as an acknowledgement to receive the connection request message 325. In some embodiments, relay UE 310 and remote UE 312 are grouped to perform mutual authentication to confirm the pairwise association between remote UE 310 and relay UE 312.

In some embodiments, the relay UE 312 is further configured to generate a side link UE information message 326 including the far end UE ID of the remote UE 310 for subsequent transmission to the eNodeB 314 to cause the remote UE 310 It can be seen by the eNodeB 314 and its associated MME 316 for DL data transfer. In some embodiments, the side-link UE information messages 326 are further grouped into a fabric eNodeB 314 to generate communication resources for the far-end UEs 310. In some embodiments, a side link UE response message (not shown) including the generated fabric parameters is sent from the eNodeB 314 to the relay UE 312 for subsequent transmission to the remote UE via the PC5 interface. 310. In some embodiments, in order to receive DL data at the remote UE 310 using the L2 relay, the EPS bearer of the far end UE 310 must be established in the network. During the L3 relay, the EPS bearer used to relay the UE 312 is used (when the relay UE 312 enters the RRC connected mode) The DL data is received at the remote UE 310. In some embodiments, the relay UE 312 is configured to process the service request procedure to establish the EPS bearer of the far end UE 310 upon receiving the connection request message 325 from the remote UE 310.

In some embodiments, the service request procedure used to establish the EPS bearer of the remote UE 310 is initiated or executed by the relay UE 312 on behalf of the remote UE 310. In such embodiments, the service request procedure 331 is provided by the relay UE 312 by providing one or more messages including the relay UE ID (e.g., S-TMSI) and the paired associated ID to the eNodeB 314. Executing to enable the S1-U tunnel establishment 332 for the remote UE 310 in the core network. Alternatively, in other embodiments, the service request procedure to establish the EPS bearer of the remote UE 310 is performed by the remote UE 310 via the relay UE 312. In these embodiments, the remote UE 310 is configured to implement a service request procedure 333 by generating one or more messages (eg, an RRC Connection Setup message), which is then carried in the container through the PC5 interface. And is explicitly forwarded by relay UE 312 to eNodeB 314 for further processing. The EPS bearer setup initiated by the remote UE 310 based on the service request from the relay UE 312 implies that the remote UE 310 is still in RRC with respect to the RRC connection setup (or about the network) through the null plane. In the idle mode, however, the EPS bearer of the far end UE 310 is still activated to be used for data transfer in the path of the S-GW-eNodeB-Relay UE.

In some embodiments, the eNodeB 314 is grouped to generate an S1-AP message 328 including the remote UE ID of the remote UE 310 for subsequent Sent to MME 316. In some embodiments, the S1-AP message 328 is generated in response to the received side link UE information message 326 and an indication is provided to the MME 316 when the paging message 323 is received at the remote UE 310. In some embodiments, the S1-AP message 328 further includes the EPS bearer ID of the far end UE 310 during the L2 relay or the EPS bearer ID of the relay UE 312 during the L3 relay. In some embodiments, the S1-AP message 328 provides information to the MME 316 regarding the EPS bearer to be used for transmission of the DL data. Upon receiving the S1-AP message 328, the MME 316 is further grouped to generate a DL data notification response message 334 for subsequent transmission to the S-GW 318. In some embodiments, the content of the S1-AP message 328 and the DL data notification response message 334 are the same. Upon receiving the DL data notification response message 334, the S-GW 318 is grouped to send the DL data to the eNodeB 314 for subsequent transmission to the remote UE 310 via the relay UE 312. In some embodiments, the DL data is transmitted by the S-GW 318 using the EPS bearer (e.g., L2 relay) of the remote UE 310, while in other embodiments, the DL data is The S-GW 318 uses the EPS bearer (e.g., L3 relay) of the relay UE 312 to transmit the DL data.

In some embodiments, after the direct communication is established between the remote UE 310 and the relay UE 312 through the PC5 interface, the relay UE 310 can reach out of coverage of the network. In such embodiments, the far end UE 310 will continue to receive the DL data via the relay UE 312 until the far end UE 310 becomes inactive during a particular time period. In this case, the direct connection between the remote UE 310 and the relay UE 312 is solved. In addition, and the remote UE 310 enters the newly defined PC5 idle mode. During the PC5 idle mode of the remote UE 310, the relay UE 312 buffers the DL data received from the eNodeB 314 until the remote UE 310 establishes a direct communication link with the relay UE 312.

Or, in some embodiments, since the remote UE uses pre-configured resources outside the coverage, the remote UE can check the paging information including the remote UE ID for each remote UE. A resource restriction pattern is defined to identify whether the remote UE has any DL data it wants. Moreover, in some embodiments, if the relay UE 312 notifies the eNodeB 314 about the PC5 idle mode of the far end UE 310, the eNodeB 314 can buffer the DL data. In some embodiments, the relay UE 312 uses the side link UE information message 326 to inform the eNodeB 314 about the PC5 idle mode of the far end UE 310.

4 illustrates a block diagram of a device 400 for use in a remote or wearable user equipment (UE) in a ProSe system in accordance with the various embodiments described herein, which facilitates the remote UE Downlink reachability. In some embodiments, the downlink reachability of the remote UE is based on the paging message received from the eNodeB through an empty inter-plane between the remote UE and the eNodeB. Or in other embodiments, the downlink reachability of the remote UE is based on the paging received from the eNodeB via the relaying UE through the PC5 interface between the relay UE and the remote UE. The message is reached. For the embodiment in which the paging message is received through the null intermediaries, the remote UE is described herein with reference to the remote UE 210 in FIG. 2, for which This embodiment of receiving the paging message by the relay UE, the remote UE is described herein with reference to the remote UE 310 in FIG.

Apparatus 400 includes a receiver circuit 410, a processing circuit 430, and a transmitter circuit 420. Moreover, in some embodiments, device 400 includes a memory circuit 440 that is coupled to processing circuitry 430. Each of the receiver circuit 410 and the transmitter circuit 420 is configured to be coupled to one or more antennas, which may be the same or different antennas. In some embodiments, receiver circuit 410 and transmitter circuit 420 can have one or more components in common, and both can be included in the transceiver circuit, while in other aspects they are not included in Inside the transceiver circuit. In various embodiments, device 400 can be included within a UE, for example, with device 400 (or a portion thereof) within the receiver and transmitter or transceiver circuitry of the UE.

In order to enable downlink reachability in the remote UE in the ProSe system, the processing circuitry 430 of the device 400 is configured to receive the paging message from the eNodeB or its associated MME via the receiving circuitry 410 (eg, at The paging message 223 in FIG. 2 or the paging message 323 in FIG. In some embodiments, device 400 can be included within remote UE 210 of FIG. In such embodiments, the paging message is received directly from the eNodeB (e.g., eNodeB 214 in FIG. 2) at processing circuitry 430 via an empty intermediation plane between the eNodeB and the remote UE ( For example, the paging message 223 in Figure 2. Upon receiving the paging message, processing circuitry 430 is grouped to generate a connection request message (e.g., connection request message 220) that includes the cause value of the paging or DL data. The processing circuit 430 is further configured to transmit through the transmitting circuit 420 Transmitting the connection request message to the relay UE through the PC5 interface between the remote UE 210 and the relay UE to establish direct communication with the relay UE to receive via the relay UE The DL data. In some embodiments, processing circuit 430 is further configured to receive a connection response message (e.g., connection response message 222) from the relay UE via transmit circuitry 410 as an acknowledgement to transmit connection request message 220. In some embodiments, the memory circuit 440 is configured to store a remote UE ID associated with the remote UE (eg, the remote UE 210) and to indicate the remote UE with the relay UE (eg, A pairwise association ID (obtained during the initial attachment procedure indicated above) following the paired association of UEs 212).

In some embodiments, processing circuit 430 is further configured to initiate a service request procedure to establish an EPS bearer for the remote UE in the network when establishing direct communication with the relay UE. In such embodiments, the processing circuit 430 is configured to execute the service request procedure (eg, the service request procedure 233) by generating one or more messages (eg, an RRC Connection Setup message), which is then transmitted through the container. The transmitting circuit 420 is transmitted to the relay UE through the PC5 interface for subsequent transmission to the eNodeB. Once the EPS bearer of the remote UE is established in the network, the processing circuit 430 is configured to receive DL data from the eNodeB via the relay UE using the EPS bearer of the remote UE during the L2 relay. In some embodiments, processing circuit 430 is configured to receive DL data from the eNodeB via the relay UE using an EPS bearer of the relay UE during an L3 relay.

In some embodiments, device 400 can be included within remote UE 310 of FIG. In such embodiments, the PC5 interface between the relay UE and the remote UE is processed by the processing node 430 via the relay UE (e.g., relay UE 312 in FIG. 3) from the eNodeB (eg, The paging message (e.g., paging message 323 in FIG. 3) is received by eNodeB 314) in FIG. In some embodiments, processing circuit 430 is configured to monitor periodic discovery messages from the relay UE to receive the paging message via the relay UE. In some embodiments, processing circuitry 430 is configured to monitor one or more discovery resource elements of the pre-composed resource pattern of the relay UE to receive the paging message via the relay UE. In some embodiments, the processing circuit 430 is configured to periodically monitor the side link paging control channel through the PC5 interface defined for transmitting downlink paging information and system information for communication via the relay UE. Receive the paging message.

In some embodiments, the memory circuit 440 is configured to store a remote UE ID associated with the remote UE (eg, the remote UE 310) and to indicate the remote UE with the relay UE (eg, A pairwise association ID (acquired during the initial attachment procedure indicated above) following the paired association of UEs 312). In some embodiments, the processing circuit 430 is configured to receive the paging message via the relay UE based on the paired paging association between the remote UE and the relay UE. In some embodiments, processing circuit 430 is configured to transmit a PC5 direct communication request message (eg, PC5 direct communication request message 320) to the relay via transmission circuitry 420 prior to receiving the paging message from the relay UE. UE to establish the far The pair of pagings between the UE and the relay UE. In some embodiments, the PC5 direct communication request message from the remote UE includes a request for a paired page with the relay UE. When the paired paging is established between the remote UE and the relay UE, the processing circuit 430 is configured to selectively send a paired paging indication message (eg, a paired paging indication message 321) to notify the eNodeB about The state of the paired paging.

Upon receiving the paging message from the eNodeB via the relay UE, the processing circuit 430 is grouped to generate a connection request message (e.g., connection request message 325) that includes the cause value of the paging or DL data. The processing circuit 430 is further configured to transmit, by using the transmitting circuit 420, the connection request message to the relay UE through the PC5 interface between the remote UE and the relay UE, to establish a connection with the relay UE. Direct communication to receive the DL data via the relay UE. In some embodiments, processing circuit 430 is further configured to receive a connection response message (e.g., connection response message 327) from the relay UE via receive circuitry 410 as an acknowledgement to transmit the connection request message.

In some embodiments, processing circuit 430 is further configured to initiate a service request procedure to establish an EPS bearer for the remote UE in the network when establishing direct communication with the relay UE. In such embodiments, the processing circuit 430 is configured to execute the service request procedure (eg, the service request procedure 333) by generating one or more messages (eg, an RRC Connection Setup message), which is then transmitted through the container. The transmitting circuit 420 is transmitted to the relay UE through the PC5 interface for subsequent transmission to the eNodeB. Once the EPS bearer of the remote UE is established in the network, The processing circuit 430 is configured to receive DL data from the eNodeB via the relay UE using the EPS bearer of the remote UE during the L2 relay. In some embodiments, the processing circuit 430 is configured to receive DL data from the eNodeB via the relay UE using the EPS bearer of the relay UE during the L3 relay.

5 illustrates a block diagram of a device 500 for use in a relay user equipment (UE) in a ProSe system in accordance with the various embodiments described herein, which facilitates a remote UE associated therewith Downlink accessibility. In some embodiments, the downlink reachability of the far end UE is enabled based on transmitting downlink (DL) data associated with the far end UE via the relay UE. Or in other embodiments, the downlink reachability of the remote UE is based on transmitting a paging message associated with the remote UE and also transmitting, by the relay UE, a downlink associated with the remote UE. Link (DL) data is reached. Apparatus 500 includes a receiver circuit 510, a processing circuit 530, and a transmitter circuit 520. Moreover, in some embodiments, device 500 includes a memory circuit 540 that is coupled to processing circuitry 530. Each of receiver circuit 510 and transmitter circuit 520 is configured to be coupled to one or more antennas, which may be the same or different antennas. In some embodiments, receiver circuit 510 and transmitter circuit 520 can have one or more components in common, and both can be included in the transceiver circuit, while in other aspects they are not included in Inside the transceiver circuit. In various embodiments, device 500 can be included within a UE, for example, with device 500 (or a portion thereof) within the receiver and transmitter or transceiver circuitry of the UE.

In some embodiments, device 500 can be included within relay UE 212 of FIG. Processing circuitry 530 is configured to receive a connection request message (e.g., connection request message 220) from a remote UE (e.g., remote UE 210) via receive circuitry 510. In some embodiments, processing circuit 530 is configured to establish a direct connection between the relay UE and the remote UE based on the connection request message. Processing circuit 530 is further configured to generate a connection response message (e.g., connection response message 222) and transmit a connection response message (e.g., connection response message 222) to the remote UE via transmission circuitry 520 as a request to receive the connection. Confirmation of the message. In some embodiments, the processing circuit 530 is further configured to generate a side link UE information message including the remote UE ID of the remote UE when establishing direct communication with the remote UE (eg, sidechain The UE information message 226) is then transmitted to the eNodeB (e.g., eNodeB 214) via the transmitting circuit 520 to enable the remote UE to be visible to the eNodeB and its associated MME (e.g., MME 216) for Transfer of DL data. In some embodiments, the relay UE is further configured to process a service request procedure to establish the EPS bearer of the remote UE upon receiving the connection request message from the remote UE.

In some embodiments, the processing circuit 540 is configured to perform one or more messages including the relay UE ID and the paired associated ID to the eNodeB through the transmitting circuit 520 for the remote end. The service request procedure (e.g., service request procedure 231) of the UE is enabled for S1-U tunnel establishment 232 of the remote UE in the core network. or In other embodiments, the processing circuit 540 is configured to perform the service request procedure (eg, the service request procedure 233) by forwarding one or more messages from the remote UE to the eNodeB for further use. Processing. Once the EPS bearer of the far end UE is established in the network, the processing circuit 530 is configured to receive DL data from the eNodeB using the EPS bearer of the far end UE during the L2 relay to use the transmit circuit 520 for subsequent Send to the remote UE. In some embodiments, processing circuit 530 is configured to receive DL data from the eNodeB using the EPS bearer of the relay UE during the L3 relay. In some embodiments, after the release of the direct connection between the remote UE and the relay UE, the processing circuit 530 is further configured to buffer the DL data for a predetermined period of time.

In some embodiments, device 500 can be included within relay UE 312 of FIG. The processing circuit 530 is configured to receive a connection request message (e.g., connection request message 325) from a remote UE (e.g., remote UE 310) through the receiving circuit 510. In some embodiments, processing circuit 530 is configured to establish a direct connection between the relay UE and the remote UE based on the connection request message. In some embodiments, processing circuit 530 is configured to receive the connection request message from the remote UE in response to transmitting a paging message (e.g., paging message 323) from processing circuit 530 to the remote UE. In some embodiments, processing circuit 530 is configured to transmit the paging message received from the eNodeB to the remote UE using a periodic discovery message. In some embodiments, the processing circuit 530 is grouped to form one of the resource patterns of the pre-composition of the relay UE or The plurality of discovery resource elements transmit the paging message received from the eNodeB to the remote UE. In some embodiments, the processing circuit 530 is configured to receive the paging message from the eNodeB using a side link paging control channel of the PC5 interface defined for transmitting downlink paging information and system information. Send to the remote UE.

In some embodiments, processing circuit 530 is configured to receive the paging message from an eNodeB (e.g., eNodeB 314) associated therewith for pairwise paging between the remote UE and the relay UE The association is then sent to the remote UE via the transmitting circuit 520. In some embodiments, the paging message associated with the remote UE is received from the eNodeB at processing circuitry 530 based on monitoring a paging occasion of the far end UE or a paging occasion of the relay UE. In some embodiments, the processing circuit 530 is further configured to receive the PC5 direct communication request message (eg, the PC5 direct communication request message 320) through the receiving circuit 510 before transmitting the paging message to the remote UE. The paired paging is established between the remote UE and the relay UE. In some embodiments, the PC5 direct communication request message from the remote UE includes a request to page with the relay UE. When the paired paging is established between the remote UE and the relay UE, the processing circuit 530 is configured to selectively transmit a paired paging indication message (eg, a paired paging indication message 321a) to notify the eNodeB about The state of the paired paging.

In some embodiments, processing circuit 530 is further configured to generate a connection response message (e.g., connection response message 327) and send a connection response message (e.g., connection response message 327) via transmission circuitry 520. To the remote UE as an acknowledgment for receiving the connection request message. In some embodiments, the processing circuit 530 is further configured to generate a side link UE information message including the remote UE ID of the remote UE when establishing direct communication with the remote UE (eg, sidechain The UE information message 326) is then transmitted to the eNodeB (e.g., eNodeB 314) via the transmitting circuit 520 to enable the remote UE to be visible to the eNodeB and its associated MME (e.g., MME 316) to For the transfer of DL data. In some embodiments, processing circuit 530 is further configured to process a service request procedure to establish an EPS bearer for the remote UE upon receiving the connection request message from the remote UE.

In some embodiments, the memory circuit 540 is configured to store a relay UE ID associated with the relay UE (e.g., relay UE 312), the remote UE ID associated with the remote UE ( For example, the remote UE 310) and a paired association ID indicating the pairwise association of the remote UE with the relay UE (e.g., relay UE 312) (obtained during the initial attachment procedure indicated above) ). In some embodiments, the processing circuit 540 is configured to perform one or more messages including the relay UE ID and the paired associated ID to the eNodeB through the transmitting circuit 520 for the remote end. The service request procedure (e.g., service request procedure 331) of the UE is enabled for S1-U tunnel establishment 332 of the remote UE in the core network. Alternatively, in other embodiments, the processing circuit 540 is configured to execute the service request procedure by forwarding one or more messages from the remote UE to the eNodeB (eg, a service request procedure) 333) for further processing. Once the EPS bearer of the far end UE is established in the network, the processing circuit 530 is configured to receive DL data from the eNodeB using the EPS bearer of the far end UE during the L2 relay to use the transmit circuit 520 for subsequent Send to the remote UE. In some embodiments, processing circuit 530 is configured to receive DL data from the eNodeB using the EPS bearer of the relay UE during the L3 relay. In some embodiments, after the release of the direct connection between the remote UE and the relay UE, the processing circuit 530 is further configured to buffer the DL data for a predetermined period of time.

6 is a block diagram of an apparatus 600 for use in an eNodeB in a ProSe system in accordance with the various embodiments described herein, which facilitates downlinking in a remote UE associated therewith. Up to nature. In some embodiments, the downlink reachability of the remote UE is based on transmitting a paging message associated with the remote UE from the eNodeB by using an empty inter-plane between the remote UE and the eNodeB. And via the associated relay UE to transmit the downlink (DL) data associated with the remote UE from the eNodeB. Or in other embodiments, the downlink reachability of the remote UE is sent from the eNodeB via the relay UE by using a PC5 interface between the relay UE and the remote UE. A paging message associated with the remote UE and via the relay UE transmits the downlink (DL) data associated with the remote UE from the eNodeB.

Apparatus 600 includes a receiver circuit 620, a processing circuit 630, and a transmitter circuit 610. Moreover, in some embodiments, device 600 includes a coupled The memory circuit 640 is coupled to the processing circuit 630. Each of the receiver circuit 620 and the transmitter circuit 610 is configured to be coupled to one or more antennas, which may be the same or different antennas. Moreover, in some embodiments, the device includes a memory circuit 640 that is coupled to processing circuitry 630. In some embodiments, receiver circuit 620 and transmitter circuit 610 can have one or more components in common, and both can be included in the transceiver circuit, while in other aspects they are not included Inside the transceiver circuit. In various embodiments, device 600 may be included in an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (eNodeB (Evolved NodeB), eNodeB (eNodeB), or eNB).

In some embodiments, device 600 can be included within eNodeB 214 of FIG. In these embodiments, the processing circuit 630 is configured to form a paging message associated with the remote UE (e.g., the remote UE 210) through the transmitting circuit 610 through the null inter-plane between the remote UE and the eNodeB. (For example, paging message 223) is sent to the remote UE. In some embodiments, the memory circuit 640 is grouped to store a relay UE ID associated with the relay UE (e.g., relay UE 212) and acquired during the initial attach procedure indicated above. A remote ID associated with the remote UE (e.g., remote UE 210). In some embodiments, the processing circuit 630 is configured to transmit the paging message to the remote UE in a paging occasion of the remote UE determined based on the remote UE ID.

In some embodiments, processing circuit 630 is configured to receive the paging message from an MME (e.g., MME 216) associated therewith prior to transmitting the paging message to the remote UE. In some embodiments, come The paging message from the eNodeB provides an indication of the availability of downlink (DL) data for the remote UE. In some embodiments, the processing circuit 630 is further configured to receive the side-link UE from the relay UE (e.g., relay UE 212) via the receiving circuit 620 in response to transmitting the paging message to the remote UE. Information message (eg, side link UE information message 226). In some embodiments, the side link UE information message indicates the receipt of the paging message at the remote UE or the establishment of a direct connection between the remote UE and the relay UE or both . In some embodiments, the side link UE information message indicates the release of the direct connection between the remote UE and the relay UE.

In some embodiments, processing circuitry 630 is further configured to receive one or more messages from the remote UE (through the relay UE) or directly from the relay UE to establish the network in the network EPS bearer of the remote UE. Upon receiving the one or more messages (i.e., through the service request procedure 231 or 233), the processing circuit 630 establishes an EPS bearer for the remote UE in the network. Upon receiving the side link UE information message, the processing circuit is further configured to generate an S1-AP message (e.g., S1-AP message 228) for subsequent transmission to the MME via the transmission circuit 610. In some embodiments, the S1-AP message includes the remote UE ID to indicate receipt of the paging message at the remote UE. In some embodiments, the S1-AP message further includes information regarding the EPS bearer ID used by the relay UE or the EPS bearer of the remote UE for transmitting the DL data to the remote UE. The processing circuit 630 is further configured to use an EPS bearer for the remote UE for L2 relay and used for The EPS bearer of the relay UE of the L3 relay transmits the DL data for the remote UE from the MME to the relay UE through the transmitting circuit 610.

In some embodiments, device 600 can be included within eNodeB 314 of FIG. In these embodiments, the processing circuit 630 is configured to be associated with the remote UE (eg, the remote UE 310) via the transmitting circuit 610 based on the paired paging association between the remote UE and the relay UE. The outgoing paging message (e.g., paging message 323) is sent to the relay UE (e.g., relay UE 312). In some embodiments, the processing circuit 630 is further configured to receive a paired paging indication message from the relay UE or the remote UE via the receiving circuit 620 prior to transmitting the paging message to the relay UE (eg, , the paired paging indication message 321a or 312b). In some embodiments, the paired paging indication message provides information about the paired paging associated between the relay UE and the remote UE to the eNodeB.

In some embodiments, the memory circuit 640 is configured to store the relay UE ID associated with the relay UE (e.g., relay UE 312) acquired during the initial attachment procedure indicated above and A remote ID associated with the remote UE (e.g., remote UE 310). In some embodiments, the processing circuit 630 is configured to transmit the paging message associated with the remote UE to the relay UE based on the paging occasion of the relay UE determined based on the relay UE ID. Alternatively, in other embodiments, the processing circuit 630 is configured to associate the paging message with the remote UE based on the paging occasion of the remote UE determined by the remote UE ID. Send to the relay UE.

In some embodiments, processing circuit 630 is configured to receive the paging message from an MME (e.g., MME 316) associated therewith prior to transmitting the paging message to the relay UE. In some embodiments, the paging message from the eNodeB provides an indication of the availability of downlink (DL) data for the remote UE. In some embodiments, the processing circuit 630 is further configured to receive the side-link UE from the relay UE (e.g., relay UE 312) via the receiving circuit 620 in response to transmitting the paging message to the relay UE. Information message (eg, side link UE information message 326). In some embodiments, the side link UE information message indicates the receipt of the paging message at the remote UE or the establishment of a direct connection between the remote UE and the relay UE or both . In some embodiments, the side link UE information message indicates the release of the direct connection between the remote UE and the relay UE.

In some embodiments, the processing circuit 630 is further configured to receive one or more messages from the remote UE (through the relay UE) or from the relay UE representing the remote UE, in order to The EPS bearer of the remote UE is established in the road. Upon receiving the one or more messages (associated with the service requestor 331 or 333), the processing circuit 630 establishes an EPS bearer for the remote UE in the network. Upon receiving the side link UE information message, the processing circuit is further configured to generate an S1-AP message (e.g., S1-AP message 328) for subsequent transmission to the MME via transmission circuitry 610. In some embodiments, the S1-AP message includes the remote UE ID to indicate receipt of the paging message at the remote UE. In a certain In some embodiments, the S1-AP message further includes information about an EPS bearer ID of the EPS bearer used by the relay UE or the remote UE that is used to send the DL data to the remote UE. Upon receiving the S1-AP message, the processing circuit 630 is grouped to form an EPS bearer for the remote UE using the L2 relay and uses the EPS bearer for the relay UE for the L3 relay, through the transmitting circuit 610. And transmitting the DL data for the remote UE from the MME to the relay UE.

7 is a flow diagram of a method 700 for a remote UE in a ProSe system including a relay UE and an eNodeB associated therewith, which facilitates downlinking of the far end UE, in accordance with an embodiment of the present invention. Accessibility. Method 700 is described herein with reference to device 400 in FIG. 4 and ProSe system 200 in FIG. In some embodiments, device 400 is included within remote UE 210 of ProSe system 200. At 702, a remote UE ID associated with the remote UE and a paired association ID (obtained at initial attachment) indicating that the remote UE is paired with the relay UE are stored at The memory circuit 440 of the remote UE. At 704, the paging message includes the remote UE ID of the remote UE received from the eNodeB at the processing circuit 430 through the null interfacing plane between the eNodeB and the remote UE. In some embodiments, the paging message indicates the availability of the far end UE for downlink (DL) data for the far end UE.

At 706, in response to receiving the paging message, a connection request message including a cause value for the paging is generated at the processing circuit 430 to transmit the transmission circuit through the PC5 interface between the remote UE and the relay UE. 420 is then sent to the relay UE. In some embodiments, the connection setup message is grouped to form the relay UE to establish a PC5 direct connection between the remote UE and the relay UE to receive the DL data via the relay UE. At 708, when the PC5 direct connection is established between the remote UE and the relay UE, a service request procedure for establishing an EPS bearer of the remote UE in the network via the relay UE is performed. It is selectively activated at processing circuit 430. In other embodiments, the service request procedure for establishing an EPS bearer for the remote UE in the network is initiated by the relay UE. At 710, the EPS bearer of the remote UE is used during the L2 relay or the EPS bearer of the relay UE is used during the L3 relay and the processing circuit 430 is transmitted through the receiving circuit 410 via the PC5 interface through the PC5 interface. To receive the downlink data signal including the DL data.

8 is a flow diagram of a method 800 for a remote UE in a ProSe system including a relay UE and an eNodeB associated therewith, which facilitates downlinking of the far end UE, in accordance with an embodiment of the present invention. Accessibility. Method 800 is described herein with reference to device 400 in FIG. 4 and ProSe system 300 in FIG. In some embodiments, device 400 is included within remote UE 310 of ProSe system 200. At 802, a remote UE ID associated with the remote UE and a paired association ID (obtained at initial attachment) indicating that the remote UE is paired with the relay UE are stored at The memory circuit 440 of the remote UE. At 804, the paging message is transmitted through the receiving circuit 410 via the relay UE through the PC5 interface between the relay UE and the remote UE. The remote UE ID of the remote UE received from the eNodeB at the processing circuit 430. In some embodiments, the paging message indicates the availability of the remote UE for downlink (DL) data for the remote UE.

At 806, a connection request message including a cause value for paging is generated at the processing circuit 430 for transmitting in response to receiving the paging message through the PC5 interface between the remote UE and the relay UE. Transmit circuit 420 is then sent to the relay UE. In some embodiments, the connection setup message is grouped to form the relay UE to establish a PC5 direct connection between the remote UE and the relay UE to receive the DL data via the relay UE. At 808, when the PC5 direct connection is established between the remote UE and the relay UE, a service request procedure for establishing an EPS bearer of the remote UE in the network via the relay UE is performed. It is selectively activated at processing circuit 430. In other embodiments, the service request procedure for establishing an EPS bearer for the remote UE in the network is initiated by the relay UE. At 810, the EPS bearer of the remote UE is used during the L2 relay or the EPS bearer of the relay UE is used during the L3 relay and the processing circuit 430 is transmitted through the receiving circuit 410 via the PC5 interface through the PC5 interface. To receive the downlink data signal including the DL data.

9 is a flow diagram of a method 900 for relaying a UE in a ProSe system including a remote UE and an eNodeB associated therewith, facilitating the downlink of the remote UE, in accordance with an embodiment of the present invention. Accessibility. Method 900 is described herein with reference to device 500 in FIG. 5 and ProSe system 200 in FIG. In some embodiments, the device 500 is included in the relay UE 212 of the ProSe system 200. At 902, a relay UE ID associated with the relay UE, a remote UE ID of the remote UE, and a paired association ID indicating a pairwise association of the relay UE with the remote UE are stored in the The memory circuit 540 of the relay UE. At 904, a connection request message including a cause value of the paging is received from the remote UE through the receiving circuit 510 via the PC5 interface between the remote UE and the relay UE at the processing circuit 530. In some embodiments, the cause value of the paging indicates the receipt of a paging message at the remote UE indicating the availability of downlink (DL) data to the remote UE. In some embodiments, the connection request message is grouped to form a relay UE to establish a direct connection with the remote UE, such that the remote UE receives and remotes from the eNodeB via the relay UE. The DL data associated with the UE.

At 906, based on the connection request message, processing circuit 530 is used to establish a direct connection between the relay UE and the remote UE. At 908, when the direct connection is established between the remote UE and the relay UE, a service request procedure for establishing an EPS bearer of the remote UE in the network is selected at the processing circuit 530. Start sexually. In other embodiments, the service request procedure to establish an EPS bearer for the remote UE in the network is initiated by the remote UE. At 910, the EPS bearer of the far end UE is used during the L2 relay or the EPS bearer of the relay UE is used during the L3 relay and the MME including the DL data is received at the processing circuit 530 from the MME associated therewith. The downlink profile signal is then forwarded to the far end UE.

10 is a flow diagram of a method 1000 for relaying a UE in a ProSe system including a remote UE and an eNodeB associated therewith, which facilitates downlinking of the remote UE, in accordance with an embodiment of the present invention. Accessibility. Method 1000 is described herein with reference to device 500 in FIG. 5 and ProSe system 300 in FIG. In some embodiments, device 500 is included within relay UE 312 of ProSe system 300. At 1002, a relay UE ID associated with the relay UE, a remote UE ID of the remote UE, and a paired association ID indicating a pairwise association of the relay UE with the remote UE are stored in the The memory circuit 540 of the relay UE. At 1004, the paging message associated with the remote UE is transmitted from the processing circuit 530 of the relay UE to the remote UE via the transmitting circuit 520. In some embodiments, the paging message associated with the remote UE is received from the eNodeB at the relay UE.

At 1006, in response to transmitting the paging message, the connection including the cause value of the paging is received from the remote UE through the receiving circuit 510 through the receiving circuit 510 through the PC5 interface between the remote UE and the relay UE. Request message. In some embodiments, the cause value of the paging indicates receipt of the paging message at the remote UE indicating the availability of downlink (DL) data to the remote UE. In some embodiments, the connection request message is grouped to form a relay UE to establish a direct connection with the remote UE, such that the remote UE receives and remotes from the eNodeB via the relay UE. The DL data associated with the UE. At 1008, based on the connection request message, processing circuit 530 is used to establish a direct connection between the relay UE and the remote UE. At 1010, when at When the direct connection is established between the remote UE and the relay UE, the service request procedure for establishing the EPS bearer of the remote UE in the network is selectively performed at the processing circuit 530 of the relay UE. start up. In other embodiments, the service request procedure to establish an EPS bearer for the remote UE in the network is initiated by the remote UE. At 1012, using the EPS bearer of the remote UE during L2 relay or using the EPS bearer of the relay UE during L3 relay to receive the downlink profile signal including the DL data at processing circuit 530 and It is then forwarded to the remote UE.

11 is a flow diagram of a method 1100 for an eNodeB in a ProSe system including a remote UE and a relay UE associated therewith, facilitating the downlink of the remote UE, in accordance with an embodiment of the present invention. Accessibility. Method 1100 is described herein with reference to device 600 in FIG. 6 and ProSe system 200 in FIG. In some embodiments, device 600 is included within eNodeB 214 of ProSe system 200. At 1102, the relay UE ID associated with the relay UE and the remote UE ID of the remote UE (both acquired at the time of initial attachment) are stored in the memory circuit 640 of the eNodeB. . At 1104, the paging message associated with the remote UE is directly transmitted from the processing circuit 630 of the eNodeB to the remote UE through the null interfacing plane between the eNodeB and the remote UE through the transmitting circuit 610. . In some embodiments, the paging message associated with the remote UE is received at the eNodeB from an MME associated therewith. In some embodiments, the paging message indicates the availability of downlink (DL) data for the far end UE.

At 1106, in response to transmitting the paging message to the remote UE, The side link UE information message is received from the relay UE at the processing circuit 630 via the receiving circuit 620. In some embodiments, the side link UE information message includes the far end UE ID and indicates reception of the paging message at the remote UE or a connection between the remote UE and the relay UE. Establish or both. At 1108, one or more messages associated with a service request procedure for an L2 relay for establishing an EPS bearer for the remote UE in the network are received at processing circuit 630 via receiving circuitry 620. At 1110, upon receiving the side link UE information message, an S1-AP message is generated at processing circuit 630 for use by transmitting circuitry 610 and subsequently to the MME associated therewith. In some embodiments, the S1-AP message includes the remote UE ID of the remote UE or the relay UE and the EPS bearer ID, so that the MME can use the remote UE during the L2 relay. The EPS bearers or uses the EPS bearer of the relay UE during the L3 relay to forward the DL data from the S-GW. At 1112, the DL data associated with the remote UE is used by the processing circuit 630, using the EPS bearer of the remote UE during L2 relay or using the EPS bearer of the relay UE during L3 relay The S-gate (S-GW) associated with the eNodeB is forwarded to the relay UE.

12 is a flow diagram of a method 1200 for an eNodeB in a ProSe system including a remote UE and a relay UE associated therewith, facilitating the downlink of the remote UE, in accordance with an embodiment of the present invention. Accessibility. Method 1200 is described herein with reference to device 600 in FIG. 6 and ProSe system 300 in FIG. In some embodiments, device 600 is included within eNodeB 314 of ProSe system 300. in At 1202, the relay UE ID associated with the relay UE and the remote UE ID of the remote UE (both acquired at the initial attachment) are stored in the memory circuit 640 of the eNodeB. At 1204, the paging message associated with the remote UE is transmitted from the processing circuit 630 of the eNodeB to the relay UE via the transmitting circuit 610 for subsequent transmission to the remote UE. In some embodiments, the paging message associated with the remote UE is received at the eNodeB from an MME associated therewith. In some embodiments, the paging message indicates the availability of downlink (DL) data for the far end UE.

At 1206, in response to transmitting the paging message to the relay UE, the processing circuit 630 receives the side link UE information message from the relay UE via the receiving circuit 620. In some embodiments, the side link UE information message includes the far end UE ID and indicates reception of the paging message at the remote UE or a connection between the remote UE and the relay UE. Establish or both. At 1208, one or more messages associated with a service request procedure for an L2 relay for establishing an EPS bearer for the remote UE in the network are received by the receiving circuit 620 at the processing circuit 630 of the eNodeB. At 1210, upon receiving the side link UE information message, an S1-AP message is generated at processing circuit 630 for use by transmitting circuitry 610 and subsequent transmission to the MME associated therewith. In some embodiments, the S1-AP message includes the remote UE ID of the remote UE or the relay UE and the EPS bearer ID, so that the MME can use the remote UE during the L2 relay. The EPS bearer or the EPS bearer of the relay UE is used during the L3 relay to forward the DL capital from the S-GW. material. At 1212, the DL data associated with the remote UE is used by the processing circuit 630, using the EPS bearer of the remote UE during L2 relay or using the EPS bearer of the relay UE during L3 relay The S-gate (S-GW) associated with the eNodeB is forwarded to the relay UE.

Although the method above is illustrated and described as a series of acts or events, it should be understood that the order of the acts or events should not be construed as limiting. For example, some acts may occur in different orders and/or concurrently with other acts or events other than those illustrated and/or described herein. In addition, not all illustrated acts may be required to implement one or more aspects or embodiments of the disclosure herein. Moreover, one or more of the acts depicted herein may be performed in one or more separate acts and/or stages.

Embodiments described herein may be implemented into the system using any suitably organized hardware and/or software. FIG. 13 illustrates example components of a User Equipment (UE) device 1300 for one embodiment. In some embodiments, the UE device 1300 can include an application circuit 1302, a baseband circuit 1304, a radio frequency (RF) circuit 1306, a front end module (FEM) circuit 1308, and one or more antennas 1310, at least as shown They are coupled together.

Application circuit 1302 can include one or more application processing circuits. For example, application circuit 1302 can include circuitry such as, but not limited to, one or more single core or multi-core processing circuitry. The processing circuit can include any combination of general purpose processing circuitry and special purpose processing circuitry (e.g., graphics processing circuitry, application processing circuitry, etc.). The processing circuit can be combined with memory/storage The devices are coupled and/or can include a memory/storage and can be grouped to execute instructions stored in the memory/storage to cause various applications and/or operating systems to operate on the system.

The baseband circuit 1304 can include circuitry such as, but not limited to, one or more single core or multi-core processing circuitry. The baseband circuit 1304 can include one or more baseband processing circuits and/or control logic to process the baseband signals received from the receive signal path of the RF circuitry 1306 and to generate a base for the transmit signal path of the RF circuitry 1306. Frequency signal. The baseband processing circuit 1304 can interface with the application circuit 1302 for the generation and processing of the baseband signals and for the control operations of the RF circuitry 1306. For example, in some embodiments, the baseband circuit 1304 can include a second generation (2G) baseband processing circuit 1304a, a third generation (3G) baseband processing circuit 1304b, and a fourth generation (4G) baseband processing circuit 1304c. And/or other baseband processing circuits 1304d for other existing generations, generations under development or to be developed in the future (eg, fifth generation (5G), 6G, etc.). The baseband circuit 1304 (e.g., one or more of the baseband processing circuits 1304a-d) can process various radio control functions that enable communication with one or more radio networks via the RF circuitry 1306. The radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency conversion, and the like. In some embodiments, the modulation/demodulation transformer circuit of the baseband circuit 1304 can include fast Fourier transform (FFT), precoding, and/or constellation mapping/demapping functions. In some embodiments, the encoding/decoding circuitry of the baseband circuit 1304 can include encoding of convolution, tail-to-tail convolution, turbo, Viterbi, and/or low density parity check (LDPC). / decoder function. Embodiments of the functions of modulation/demodulation and encoder/decoder are not limited to these examples, and other suitable functions may be included in other embodiments.

In some embodiments, the baseband circuit 1304 can include elements of a protocol stack, such as elements of an Evolved Universal Terrestrial Radio Access Network (EUTRAN) protocol, including, for example, a physical (PHY), medium access control (MAC). , Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP) and/or Radio Resource Control (RRC) components. The central processing unit (CPU) 1304e of the baseband circuit 1304 can be grouped into elements that operate the protocol stack for signaling of the PHY, MAC, RLC, PDCP, and/or RRC layers. In some embodiments, the baseband circuit can include one or more audio digital signal processing circuits (DSPs) 1304f. The audio DSP 1304f may include components for compression/decompression and echo cancellation, and may include other suitable processing elements in other embodiments. In some embodiments, the components of the baseband circuit can be suitably combined in a single wafer, in a single wafer set, or on the same circuit board. In some embodiments, some or all of the constituent components of baseband circuit 1304 and application circuit 1302 can be implemented together, such as, for example, on a system single chip (SOC).

In some embodiments, baseband circuitry 1304 can provide communications for compatibility with one or more radio technologies. For example, in some embodiments, the baseband circuit 1304 can support and evolve the Universal Terrestrial Radio Access Network (EUTRAN) and/or other wireless metropolitan area network (WMAN), wireless local area network (WLAN), wireless individuals. Regional Network (WPAN) communication. Embodiments in which the baseband circuit 1304 is grouped to support radio communications that support more than one wireless protocol may be referred to as a multi-mode baseband circuit.

RF circuit 1306 can enable communication with a wireless network using modulated electromagnetic radiation via a non-solid medium. In various embodiments, RF circuit 1306 can include switches, filters, amplifiers, etc. to facilitate communication with the wireless network. The RF circuit 1306 can include a receive signal path that can include circuitry for downconverting the RF signal received from the FEM circuit 1308 and providing the baseband signal to the baseband circuit 1304. The RF circuit 1306 can also include a transmit signal path that can include circuitry for upconverting the baseband signal provided by the baseband circuit 1304 and providing the RF output signal to the FEM circuit 1308 for transmission.

In some embodiments, RF circuit 1306 can include a receive signal path and a transmit signal path. The receive signal path of RF circuit 1306 can include mixer circuit 1306a, amplifier circuit 1306b, and filter circuit 1306c. The transmit signal path of RF circuit 1306 can include filter circuit 1306c and mixer circuit 1306a. The RF circuit 1306 can also include a synthesizer circuit 1306d for synthesizing the frequencies used by the mixer circuit 1306a of the received signal path and the transmit signal path. In some embodiments, the mixer circuit 1306a of the receive signal path can be configured to downconvert the RF signal received from the FEM circuit 1308 based on the synthesized frequency provided by the synthesizer circuit 1306d. Amplifier circuit 1306b can be grouped to amplify the downconverted signal and filter circuit 1306c can be configured to remove unwanted signals from the downconverted signal to produce an input A low pass filter (LPF) or a band pass filter (BPF) of the fundamental frequency signal. The output baseband signal can be provided to the baseband circuit 1304 for further processing. In some embodiments, the output baseband signal can be a zero frequency baseband signal, despite this non-essential condition. In some embodiments, the mixer circuit 1306a that receives the signal path can include a passive mixer, although the scope of the embodiments is not limited thereto.

In some embodiments, the transmit signal path mixer circuit 1306a can be grouped to upconvert the input baseband signal based on the synthesized frequency provided by the synthesizer circuit 1306d to generate the FEM circuit 1308. RF output signal. The baseband signal may be provided by baseband circuitry 1304 and may be filtered by filter circuitry 1306c. Filter circuit 1306c may include a low pass filter (LPF), although the scope of the embodiments is not limited thereto.

In some embodiments, the mixer circuit 1306a that receives the signal path and the mixer circuit 1306a of the transmit signal path can include two or more mixers, and can be configured to be used separately Cross-conversion and/or up-conversion. In some embodiments, the mixer circuit 1306a that receives the signal path and the mixer circuit 1306a of the transmit signal path can include two or more mixers and can be configured for image rejection ( For example, Hartley image exclusion). In some embodiments, the mixer circuit 1306a and the mixer circuit 1306a of the receive signal path can be configured for direct down conversion and/or direct up conversion, respectively. In some embodiments, the mixer circuit 1306a of the receive signal path and the mixer circuit 1306a of the transmit signal path can be grouped. Used for superheterodyne operation.

In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, although the scope of the embodiments is not limited thereto. In some alternative embodiments, the output baseband signal and the input baseband signal can be digital baseband signals. In these alternative embodiments, RF circuit 1306 can include an analog to digital converter (ADC) and a digital to analog converter (DAC) circuit, and base frequency circuit 1304 can include a digital baseband interface for operation with RF circuit 1306. communication.

In some dual mode embodiments, a separate radio IC circuit may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited thereto.

In some embodiments, the synthesizer circuit 1306d may be a fractional-N synthesizer or a fractional N/N+1 synthesizer, although the scope of the embodiments is not limited thereto, as other types of frequency synthesizers may be suitable. . For example, the synthesizer circuit 1306d can be an integrating delta synthesizer, a frequency multiplier, or a synthesizer including a phase locked loop having a frequency divider.

Synthesizer circuit 1306d can be configured to synthesize the output frequencies used by mixer circuit 1306a of RF circuit 1306 based on the frequency input and divider control inputs. In some embodiments, synthesizer circuit 1306d can be a fractional N/N+1 synthesizer.

In some embodiments, the frequency input can be provided by a voltage controlled oscillator (VCO), although it is not a necessary condition. The divider control input can be provided by the baseband circuit 1304 or the application processing circuitry 1302, depending on the desired output frequency. In some embodiments, based on the application The channel indicated by the circuit 1302 determines the divider control input (e.g., N) from the lookup table.

The synthesizer circuit 1306d of the RF circuit 1306 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 grouped to divide the input signal by N or N+1 (eg, based on execution) to provide a fractional division ratio. In some example embodiments, the DLL may include a set of tunable delay elements, phase detectors, charge pumps, and D-type flip-flops. In such embodiments, the delay elements can be grouped into packets that decompose the VCO period into Nd equal phases, 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.

In some embodiments, synthesizer circuit 1306d can be grouped to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency can be a multiple of the carrier frequency (eg, twice the carrier frequency) Four times the carrier frequency) and used in conjunction with an orthogonal generator and divider circuit to generate multiple signals at the carrier frequency having a plurality of different phases relative to each other. In some embodiments, the output frequency can be the LO frequency (fLO). In some embodiments, RF circuit 1306 can include an IQ/polarity converter.

FEM circuit 1308 can include a receive signal path that can include circuitry that is grouped to form an RF received from one or more antennas 1310 The signal operates, amplifies the received signal and provides an amplified version of the received signal to RF circuit 1306 for further processing. The FEM circuit 1308 can also include a transmit signal path, which can include circuitry that is configured to amplify the signal provided by the RF circuit 1306 for transmission for use by one or more of the one or more antennas 1310 To send.

In some embodiments, FEM circuit 1308 can include a TXIRX switch to switch between transmit mode and receive mode operation. The FEM circuit can include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit can include a low noise amplifier (LNA) to amplify the received RF signal and provide the amplified received RF signal as an output (e.g., to RF circuit 1306). The transmit signal path of FEM circuit 1308 can include a power amplifier (PA) for amplifying the input RF signal (eg, provided by RF circuit 1306) and one or more filters for generating The RF signal for subsequent transmission (eg, by one or more of one or more antennas 1310).

In some embodiments, the UE device 1300 can include additional elements such as, for example, a memory/storage, a display, a video camera, a sensor, and/or an input/output (I/O) interface.

Although the device has been illustrated and described with respect to one or more embodiments, modifications and/or modifications may be made to the illustrated examples without departing from the spirit and scope of the appended claims. In particular, various functions implemented by the components or structures (components, devices, circuits, systems, etc.) described above are used to describe such components. The term (including references to "a device"), unless otherwise stated, is intended to mean any component or structure that corresponds to the specific function of the described components (eg, functionally equivalent), even in the structure. The above disclosed structure is not equivalent to the implementation of the functions of the exemplary embodiments of the invention illustrated herein.

An example may include a subject matter, such as a method, means for performing the acts or blocks of the method, and at least one machine readable medium containing instructions which, when implemented by a machine, may cause the machine to be as described herein. Embodiments and Examples A variety of communication techniques are used to implement the actions of the method or device or system for simultaneous communication.

Example 1 is a device for use in a remote user equipment (UE) based on a ProSe network, including processing circuitry that is configured to be configured when executing instructions from a memory circuit Detecting the inclusion of the eNodeB from the ProSe network via the interworking plane between the eNodeB and the remote UE or through the PC5 interface between the relay UE and the remote UE via the relay UE of the ProSe network a paging message of the remote UE ID of the remote UE, wherein the paging message notifies the remote UE of the availability of downlink (DL) data for the remote UE; in response to the received paging message, Generating a connection request message including a cause value for paging for subsequent transmission to the relay UE through the PC5 interface to establish a direct connection between the remote UE and the relay UE via the relay UE Receiving the DL data; and in response to the connection request message sent, detecting, by the relay UE, the downlink information including the DL data from the eNodeB through the PC5 interface Data signal.

Example 2 is the device comprising the patent of Example 1, wherein, after the direct connection is established between the remote UE and the relay UE, the processing circuit is further configured to initiate a service request procedure to communicate via the relay UE An evolved packet system (EPS) bearer of the remote UE is established in the network.

Example 3 is a device (including or omitting an element) of the patents of Examples 1 to 2, wherein initiating the service requesting program includes providing one or more messages associated with the service requesting program to the PC5 interface through the PC5 interface The UE is relayed, wherein the one or more messages are then explicitly forwarded to the eNodeB by the relay UE.

Example 4 is the device (including or omitting the component) of the patents of Examples 1 to 3, wherein the downlink data signal is detected by using the EPS bearer of the remote UE during the L2 relay, and wherein The downlink profile signal is received during the L3 relay using the EPS bearer of the relay UE.

Example 5 is an apparatus (including or omitting elements) of the patents of Examples 1 to 4, wherein the processing circuit is further configured to monitor periodic discovery messages from the relay UE for reception via the relay UE The paging message.

Example 6 is an apparatus (including or omitting elements) comprising the patents of Examples 1 to 5, wherein the processing circuit is further configured to monitor one or more discovery resource elements of the pre-configured resource pattern of the relay UE, The paging message is received via the relay UE.

Example 7 is an apparatus (including or omitting elements) comprising the patents of Examples 1 to 6, wherein the processing circuit is further configured to periodically periodically through the PC5 interface defined for transmitting downlink paging information and system information. The side link paging control channel is monitored to receive the paging message via the relay UE.

Example 8 is an apparatus (including or omitting elements) of the patents of Examples 1 to 7, wherein the processing circuit is configured to be generated for subsequent transmission to the relay UE before receiving the paging message via the relay UE The PC5 direct communication request message, wherein the PC5 direct communication request message includes the remote UE ID and the paired paging request to establish a paired paging between the remote UE and the relay UE.

Example 9 is an apparatus (including or omitting elements) of the patents of Examples 1 to 8, wherein the processing circuit is further configured to generate the pair of pagings between the remote UE and the relay UE for generation Then, the paired paging indication message is sent to the eNodeB, where the paired paging indication message includes an indication of the paired paging between the remote UE and the relaying UE, the remote UE ID, and the remote end The paired association ID of the UE and the paired paging UE and the UE transmitting the paired paging indication message are indications of the relay UE or the remote UE.

Example 10 is a device for use in a relay user equipment (UE) of a ProSe network, comprising: a memory circuit configured to store a relay UE ID associated with the relay UE, a remote UE ID of the remote UE of the ProSe network and a paired association ID indicating a pairwise association of the relay UE with the remote UE; the processing circuit is configured to The PC5 interface between the remote UE and the relay UE detects a connection request message including a cause value of the paging from the remote UE, where the cause value of the paging indicates that the air interface is transmitted through the remote UE Or receiving, by the relay UE, a paging message from an eNodeB of the ProSe network, the paging message indicating availability of downlink (DL) data to the remote UE; when receiving the connection request message, Establishing a direct connection between the relay UE and the remote UE; and receiving, using the remote UE or an evolved packet system (EPS) bearer of the relay UE, an S-channel including from the eNodeB The downlink data signal of the DL data of the (S-GW) is used to be subsequently sent to the remote UE through the PC5 interface when the direct connection is established between the relay UE and the remote UE.

Example 11 is the apparatus of claim 10, wherein the processing circuit is further configured to generate a side link UE including the far end UE ID of the remote UE before detecting the downlink data signal Information messages for subsequent transmission to the eNodeB to enable the remote UE to be visible to the eNodeB and its associated MME for DL data transfer.

Example 12 is the apparatus (including or omitting elements) of the patents of Examples 10 to 11, wherein the processing circuit is further configured after the direct connection between the relay UE and the remote UE is established. The EPS bearer of the remote UE is established in the network to detect the downlink data signal during the L2 relay.

Example 13 is a device comprising the patents of Examples 10 to 12 (package) Include or omit the component), wherein the processing circuit is further configured to implement the remote UE by providing the relay UE ID, the EPS bearer ID of the remote UE, and the paired association id to the eNodeB The service request procedure to establish an EPS bearer for the remote UE.

Example 14 is an apparatus (including or omitting elements) of the patents of Examples 10 to 13, wherein the processing circuit is further configured to receive from the remote UE through the PC5 interface with the remote UE One or more messages associated with the service requester are forwarded to the eNodeB to establish an EPS bearer for the remote UE.

Example 15 is an apparatus (including or omitting elements) of the patents of Examples 10 to 14, wherein the processing circuit is grouped based on a paired paging association of the remote UE with the relay UE, from the remote UE Before detecting the connection request message, detecting the paging message associated with the remote UE from the eNodeB for subsequent transmission to the remote UE.

Example 16 is an apparatus (including or omitting elements) of the patents of Examples 10 to 15, wherein the processing circuit is further configured to pass the PC5 interface from the remote before transmitting the paging message to the remote UE The UE detects the PC5 direct communication request message, where the PC5 direct communication request message includes the remote UE ID and the paired paging request to establish the paired paging between the remote UE and the relay UE.

Example 17 is an apparatus (including or omitting elements) of the patents of Examples 10 to 16, wherein the processing circuit is further configured to generate the pair of pagings between the remote UE and the relay UE, And then send a paired paging indication message to the eNodeB to notify the And the paired paging indication, where the paired paging indication message includes the indication of the paired paging between the remote UE and the relay UE, the relay UE ID, the paired association ID, and the sending the The UE that is the paging indication message is an indication of the relay UE or the remote UE.

Example 18 is a device (including or omitting elements) of the patents of Examples 10 to 17, wherein the paging message associated with the remote UE is based on monitoring a paging occasion of the remote UE or a paging of the relay UE The timing is detected from the eNodeB at the processing circuit.

Example 19 is a device (including or omitting elements) of the patents of Examples 10 to 18, wherein the paging message associated with the remote UE is generated by the processing circuit using a periodic discovery notification message for Provided to the remote UE.

Example 20 is a device (including or omitting elements) of the patents of Examples 10 to 19, wherein the paging message associated with the remote UE is used by the processing circuit to use a pre-configuration that the remote UE is monitoring One or more discovery resource elements of the resource pattern are generated for provision to the remote UE.

Example 21 is an apparatus (including or omitting elements) of the patents of Examples 10 to 20, wherein the paging message associated with the remote UE is defined by the processing circuit for transmission for transmitting downlink paging The side link paging control channel of the PC5 interface of the information and system information is generated for provision to the remote UE.

Example 22 is a device (including or omitting elements) comprising the patents of Examples 10 to 21, wherein between the remote UE and the relay UE After the release of the direct connection, the processing circuit is further configured to buffer the DL data for a predetermined period of time.

Example 23 is an apparatus for use in an eNodeB of a ProSe network, comprising: a memory circuit configured to store a relay user equipment (UE) ID associated with a relay UE and a far end of the remote UE End-end UE ID; processing circuitry that is grouped to receive an optical inter-plane between the eNodeB and the remote UE or via the relay UE from a mobile management entity (MME) associated therewith and the remote end The paging message associated with the UE is provided to the remote UE for subsequent transmission to the remote UE through the PC5 interface between the relay UE and the remote UE, wherein the paging message is indicated for the remote UE The availability of downlink (DL) data; in response to providing the paging message, detecting a side link UE information message from the relay UE, wherein the side link UE information message is indicated at the remote UE The reception of the paging message or the establishment of a direct connection between the remote UE and the relay UE or both; and when the side link UE information message indicates between the remote UE and the relay UE The establishment of the direct connection, using the evolved packet system (EPS) bearer of the remote UE or the relay U The EPS bearer of E provides the DL data associated with the remote UE received from its associated S-Gate (S-GW) to the relay UE for subsequent transmission to the remote end UE.

Example 24 is the device of claim 23, wherein the processing circuit is further configured to detect one or more messages associated with the service requesting program for use in the network prior to forwarding the DL data. The EPS bearer of the remote UE of the L2 relay, where the one or The plurality of messages includes an EPS bearer ID associated with the remote UE.

Example 25 is a device (including or omitting elements) of the patents of Examples 23 to 24, wherein the processing circuit is further configured to generate an S1 application protocol (S1-AP) after detecting the side link UE information message. a message for subsequently transmitting to the MME associated therewith using the transmitting circuit, wherein the S1-AP message includes the remote UE ID and the EPS bearer ID of the remote UE or the relay UE, so that The MME is enabled to forward the DL data from the S-GW using the EPS bearer of the remote UE during the L2 relay or using the EPS bearer of the relay UE during the L3 relay.

Example 26 is an apparatus (including or omitting elements) of the patents of Examples 23 to 25, wherein the processing circuit is configured to be based on a paired paging association between the relay UE and the remote UE via the relay The UE provides the paging message to the remote UE.

Example 27 is an apparatus (including or omitting elements) of the patents of Examples 23 to 26, wherein the processing circuit is further configured to detect from the relay UE before providing the paging message to the remote UE Or the paired paging indication message of the remote UE, where the paired paging indication message includes an indication of establishment or cancellation of the paired paging between the remote UE and the relay UE, based on sending the paired paging indication The relay UE ID of the UE or the remote UE ID, the paired association ID, and the UE that sends the paired paging indication message are indications of the relay UE or the remote UE.

Example 28 is a device comprising the patents of Examples 23 to 27 (package) Include or omit the component), wherein the processing circuit is configured to provide the paging message of the relay UE and the remote UE in a paging occasion of the relay UE, where the paging occasion of the relay UE It is determined based on the relay UE ID.

Example 29 is the device (including or omitting the component) of the patents of Examples 23 to 28, wherein the processing circuit is configured to provide the paging message of the remote UE in the paging occasion of the remote UE, where The paging timing of the remote UE is determined based on the remote UE ID.

Example 30 is an apparatus (including or omitting elements) of the patents of Examples 23 to 29, wherein the side link UE information message further includes information regarding the release of the direct connection between the relay UE and the remote UE And when the side link UE information message indicates that the direct connection between the remote UE and the relay UE is released, the processing circuit is configured to buffer the DL data to be forwarded to the remote UE .

The various illustrative logic, logic blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented by a general purpose processor, digital signal processor designed to carry out the functions described herein ( DSP), dedicated integrated circuit (ASIC), field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, implemented or implemented. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine.

The above description of the disclosed subject matter is included in the above description. The present invention is not intended to be exhaustive or to limit the embodiments disclosed. Although the specific embodiments and examples are described herein for illustrative purposes, various modifications are possible, which are considered to be within the scope of such embodiments and examples, as would be understood by those skilled in the relevant art. Inside.

In this regard, although the disclosed subject matter has been described in connection with the various embodiments and the accompanying drawings, it should be understood that other similar embodiments may be used or may be described. The examples are modified and added to perform the same, similar, alternative or alternate functions of the disclosed subject matter without departing from the invention. Therefore, the disclosed subject matter should not be limited to any single embodiment described herein, but should be construed in accordance with the broad scope and scope of the appended claims.

In particular, various functions performed by the components or structures (components, devices, circuits, systems, etc.) described above are used to describe the terms of such components (including references to "devices"), Unless otherwise stated, any component or structure that is intended to perform a particular function of the described components (e.g., functionally equivalent), even if not structurally equivalent to execution as illustrated herein. The disclosed structure of the functions of the exemplary embodiments of the present invention. In addition, although specific features may be disclosed in only one of several embodiments, such features may be combined with one or more other features of other embodiments, as may be used for any given or particular application. Expected and advantageous.

100‧‧‧Proximity Service (ProSe) System

150‧‧‧PC5 interface

160‧‧‧Old Uu interface

180‧‧‧S1 interface

Claims (25)

A device in a remote user equipment (UE) for use in a ProSe network comprising a relaying UE and an associated evolved Node B (eNodeB) thereof, comprising processing circuitry for performing processing from a memory circuit The instruction is configured to receive from the eNodeB through an empty inter-plane between the eNodeB and the remote UE or via the relay UE through a PC5 interface between the relay UE and the remote UE. a paging message of the remote UE ID of the remote UE, wherein the paging message notifies the remote UE of the availability of downlink (DL) data for the remote UE; and generates, in response to receiving the paging message, The reason value of the paging is sent to the connection request message of the relay UE through the PC5 interface, so as to establish a direct connection between the remote UE and the relay UE, and receive the DL data via the relay UE. And in response to transmitting the connection request message, receiving, by the PC5 interface, the downlink data signal including the DL data from the eNodeB via the relay UE. The device of claim 1, wherein after the establishing the direct connection between the remote UE and the relay UE, the processing circuit is further configured to start a service request procedure to establish via the relay UE. The evolved packet system (EPS) of the remote UE is carried in the network. The device of claim 2, wherein the initiating the service requesting program comprises providing one or more messages associated with the service requesting program to the relaying UE through the PC5 interface, wherein the one or more The message is then explicitly forwarded to the eNodeB by the relaying UE. The device of claim 2, wherein the EPS bearer of the remote UE is used to receive the downlink profile signal during an L2 relay, and wherein the EPS of the relay UE is used during an L3 relay The bearer receives the downlink data signal. The device of claim 1, wherein the processing circuit is configured to generate a PC5 direct communication request message for subsequent transmission to the relay UE before receiving the paging message via the relay UE, where The PC5 direct communication request message includes the remote UE ID and the paired paging request to establish a paired paging between the remote UE and the relay UE. The device of claim 5, wherein the processing circuit is further configured to generate a pair of paging indications for subsequent transmission to the eNodeB after the pair of pagings are established between the remote UE and the relay UE a message, where the paired paging indication message includes an indication of the paired paging between the remote UE and the relaying UE, the remote UE ID, and a pair indicating the remote UE and the relay UE The paired association ID and the UE that sends the paired paging indication message are indications of the relay UE or the remote UE. A device in a relay user equipment (UE) for use in a ProSe network including a remote UE and an evolved Node B (eNodeB) associated therewith, comprising: a memory circuit configured to be stored and stored in the relay UE Associated relay UE ID, remote UE ID of the remote UE, and indication of the relay UE a paired association ID associated with the pair of remote UEs; a processing circuit configured to receive a cause value including a paging from the remote UE through a PC5 interface between the remote UE and the relay UE a connection request message, wherein the reason value of the paging indicates reception of a paging message indicating to the remote UE that the air interface is transmitted through the null intermediate plane or the downlink node from the eNodeB via the relay UE ( DL) availability of the data; after receiving the connection request message, establishing a direct connection between the relay UE and the remote UE; and after establishing the direct connection between the relay UE and the remote UE Receiving, by using the remote UE or the evolved packet system (EPS) bearer of the relay UE, receiving an uplink data signal including the DL data from an S-gate (S-GW) associated with the eNodeB, For subsequent transmission to the remote UE via the PC5 interface. The device of claim 7, wherein the processing circuit is further configured to generate a side link UE information message including the remote UE ID of the remote UE, before receiving the downlink data signal, to For subsequent transmission to the eNodeB to cause the remote UE to be visible to the eNodeB and its associated MME for DL data transfer. The device of claim 7, wherein after the direct connection between the relay UE and the remote UE is established, the processing circuit is further configured to establish the remote UE in the network. The EPS bearers to receive the downlink profile signal during the L2 relay. Such as the device of claim 9th, wherein the remote end The EPS bearer of the UE is established by implementing a service request procedure on behalf of the remote UE based on providing the relay UE ID, the EPS bearer ID of the remote UE, and the paired association ID to the eNodeB. The device of claim 7, wherein the processing circuit is configured to associate with the paired paging of the remote UE and the relay UE from the eNodeB before receiving the connection request message from the remote UE. The paging message associated with the remote UE is received for subsequent transmission to the remote UE. The device of claim 11, wherein the processing circuit is further configured to receive a PC5 direct communication request message from the remote UE through the PC5 interface before sending the paging message to the remote UE, where The PC5 direct communication request message includes the remote UE ID and the paired paging request to establish the paired paging between the remote UE and the relay UE. The device of claim 12, wherein the processing circuit is further configured to generate a pair of pagings for subsequent transmission to the eNodeB after the pair of pagings are established between the remote UE and the relay UE. Instructing a message to notify the eNodeB of the paired paging, wherein the paired paging indication message includes an indication of the paired paging between the remote UE and the relay UE, the relay UE ID, the The UE that is the association ID and the paired paging indication message is an indication of the relay UE or the remote UE. The device of claim 11, wherein the paging message associated with the remote UE is based on monitoring at the processing circuit The paging occasion of the remote UE or the paging occasion of the relay UE is received from the eNodeB. The device of claim 11, wherein the paging message associated with the remote UE is transmitted from the processing circuit to the remote UE using a periodic discovery notification message. The device of claim 11, wherein the paging message associated with the remote UE is from one or more discovery resource elements of a pre-configured resource pattern being monitored by the remote UE. The processing circuit is sent to the remote UE. The device of claim 11, wherein the paging message associated with the remote UE is configured to use a side link paging control channel through the PC5 interface defined to transmit downlink paging information and system information. From the processing circuit is sent to the remote UE. The device of claim 7, wherein the processing circuit is further configured to buffer the DL data for a predetermined period of time after the direct connection between the remote UE and the relay UE is released. . An apparatus for use in an eNodeB of a ProSe network including a remote user equipment (UE) and a relay UE associated therewith, comprising: a memory circuit configured to store a relay associated with the relay UE a UE ID and a remote UE ID of the remote UE; processing circuitry configured to: pass through an empty inter-plane between the eNodeB and the remote UE or via the relay UE through the relay UE and the far PC5 between UEs The interface is then sent to the remote UE, and a paging message associated with the remote UE received from the MME associated with the remote UE is provided to the remote UE, wherein the paging message indicates for the remote UE The availability of downlink (DL) data of the UE; receiving, by the relay UE, a side link UE information message, wherein the side link UE information message is indicated at the remote UE in response to providing the paging message The reception of the paging message or the establishment of a direct connection between the remote UE and the relay UE or both; and when the side link UE information message indicates between the remote UE and the relay UE The establishment of the direct connection, the Evolved Packet System (EPS) bearer of the remote UE or the EPS bearer of the relay UE will be associated with the S-Gate (S-GW) associated with the remote UE The DL data received in association with the remote UE is provided to the relay UE for subsequent transmission to the remote UE. The device of claim 19, wherein before processing the DL data, the processing circuit is further configured to receive one or more messages associated with the service requesting program for establishing in the network for the L2 relay The EPS bearer of the remote UE, wherein the one or more messages include an EPS bearer ID associated with the remote UE. The device of claim 20, wherein after receiving the side link UE information message, the processing circuit is further configured to generate an S1-AP message for subsequent transmission to an MME associated therewith, wherein The S1-AP message includes the remote UE ID and the EPS bearer ID of the remote UE or the relay UE, so that the MME is in the L2 relay period. The EPS bearer of the remote UE is used or the DL data is forwarded from the S-GW using the EPS bearer of the relay UE during the L3 relay. The device of claim 19, wherein the processing circuit is configured to provide the paging message to the remote UE via the relay UE based on a paired paging association between the relay UE and the remote UE . The device of claim 22, wherein the processing circuit is configured to provide the paging message of the relay UE and the remote UE in a paging occasion of the relay UE, where the relay UE The paging timing is determined based on the relay UE ID. The device of claim 22, wherein the processing circuit is configured to provide the paging message of the remote UE in a paging occasion of the remote UE, wherein the paging time of the remote UE is based on The far end UE ID is used to determine. The device of claim 19, wherein the side link UE information message further includes information about the release of the direct connection between the relay UE and the remote UE, and when the side link UE information When the message indicates that the direct connection between the remote UE and the relay UE is released, the processing circuit is configured to buffer the DL data to be forwarded to the remote UE.