TWI738678B - 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 saving devices using device-to-device communication (D2D)

The present invention relates to ProSe (ProSe) networks, and more specifically to devices and methods for receiving downlink (DL) data of ultra-power-saving devices in ProSe networks.

In recent years, the demand for accessing fast-moving wireless data for mobile electronic devices has stimulated the development of the Long Term Evolution (LTE) communication system (hereinafter referred to as "LTE system") of the Third Generation Partnership Project (3GPP). Utilizing device-to-device (D2D) communication between nearby mobile devices improves spectrum utilization, overall processing capacity, and energy consumption, while enabling new peer-to-peer and location-based applications and services. The main use case for driving D2D communication is in fallback public safety networks, where D2D-enabled LTE devices can only function when the cellular network is unavailable or fails.

So far, the ProSe-based D2D communication system is mainly focused on public safety services, and the general usage, for example, wearable device support Aid, most of them are out of scope. Utilizing advanced relay capabilities and power optimization for D2D devices, ProSe-based D2D communication can be used in general use cases, such as low-power wearable UE support.

100‧‧‧Proximity Service (ProSe) System

110‧‧‧Remote User Equipment (UE)

120‧‧‧ProSe UE to network relay

130‧‧‧Evolution Node B

140‧‧‧Evolved Packet Core (EPC)

150‧‧‧PC5 interface

160‧‧‧Old Uu interface

180‧‧‧S1 interface

200‧‧‧ProSe System

210‧‧‧Remote UE

212‧‧‧Relay UE

214‧‧‧Evolution Node B

216‧‧‧Mobile Management Entity (MME)

218‧‧‧Service Gateway (S-GW)

219‧‧‧Initial attachment creation 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 instruction message

312b‧‧‧Paired call instruction message

314‧‧‧Evolution Node B

316‧‧‧Mobile Management Entity (MME)

318‧‧‧Service Gateway (S-GW)

319‧‧‧Initial attachment creation procedure

320‧‧‧PC5 direct communication request message

321‧‧‧Paired call instruction message

321a‧‧‧Paired call instruction message

321b‧‧‧Paired call instruction message

323‧‧‧Call message

324‧‧‧DL data 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 data 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‧‧‧Step

704‧‧‧Step

706‧‧‧Step

708‧‧‧Step

710‧‧‧Step

800‧‧‧Method

802‧‧‧step

804‧‧‧Step

806‧‧‧Step

808‧‧‧Step

810‧‧‧Step

900‧‧‧Method

902‧‧‧Step

904‧‧‧Step

906‧‧‧Step

908‧‧‧Step

910‧‧‧Step

1000‧‧‧Method

1002‧‧‧step

1004‧‧‧Step

1006‧‧‧Step

1008‧‧‧Step

1010‧‧‧Step

1012‧‧‧Step

1100‧‧‧Method

1102‧‧‧Step

1104‧‧‧Step

1106‧‧‧Step

1108‧‧‧Step

1110‧‧‧Step

1112‧‧‧Step

1200‧‧‧Method

1202‧‧‧Step

1204‧‧‧Step

1206‧‧‧Step

1208‧‧‧Step

1210‧‧‧Step

1212‧‧‧Step

1300‧‧‧User Equipment (UE) Device

1302‧‧‧Application circuit

1304‧‧‧Baseband circuit

1304a‧‧‧Baseband processing circuit

1304b‧‧‧Baseband processing circuit

1304c‧‧‧Baseband processing circuit

1304d‧‧‧Baseband processing circuit

1304e‧‧‧Central Processing Unit (CPU)

1304f‧‧‧Audio digital signal processing circuit

1306‧‧‧Radio Frequency (RF) Circuit

1306a‧‧‧Mixer circuit

1306b‧‧‧Amplifier circuit

1306c‧‧‧Filter circuit

1306d‧‧‧Synthesizer circuit

1308‧‧‧Front End Module (FEM) Circuit

1310‧‧‧antenna

Hereinafter, some examples of circuits, devices and/or methods will be described by way of examples only. In this article, reference will be made to the drawings.

FIG. 1 is a simplified block diagram of a ProSe system according to the current device-to-device (D2D) ProSe work item of enhanced LTE according to an embodiment of the present invention.

FIG. 2 depicts the downlink reachability of a remote UE in a ProSe system based on receiving paging messages from an eNodeB associated with it through an air interface according to an embodiment of the present invention.

FIG. 3 depicts the downlink reachability of the remote UE in the ProSe system based on receiving paging messages from the eNodeB associated with the relay UE through the PC5 interface according to an embodiment of the present invention.

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

FIG. 5 is a block diagram of a device used in a relay user equipment (UE) in a ProSe system according to various embodiments described herein, which facilitates downlink availability in a remote UE Reachability.

FIG. 6 is a block diagram of a device used in an eNodeB in a ProSe system according to various embodiments described herein, which promotes downlink reachability in the remote UE associated therewith .

FIG. 7 is a flowchart of a method for a remote UE in a ProSe system including a relay UE and an eNodeB associated with it according to an embodiment of the present invention, which facilitates the downlink of the remote UE Accessibility.

FIG. 8 is a flowchart of a method for a remote UE in a ProSe system including a relay UE and an eNodeB associated with it according to an embodiment of the present invention, which facilitates the downlink of the remote UE Accessibility.

FIG. 9 is a flowchart of a method for relaying UE in a ProSe system including a remote UE and an eNodeB associated with it according to an embodiment of the present invention, which facilitates downlink of the remote UE Accessibility.

FIG. 10 is a flowchart of a method for relaying UE in a ProSe system including a remote UE and an eNodeB associated with it according to an embodiment of the present invention, which facilitates downlink of the remote UE Accessibility.

FIG. 11 is a flowchart of a method for eNodeB in a ProSe system including a remote UE and a relay UE associated with it according to an embodiment of the present invention, which facilitates the downlink of the remote UE Accessibility.

FIG. 12 is a flowchart of a method for eNodeB in a ProSe system including a remote UE and a relay UE associated with it according to an embodiment of the present invention, which facilitates the downlink of the remote UE Accessibility.

Figure 13 shows example components of a user equipment (UE) device for one embodiment.

[Content and Implementation of the Invention]

In one embodiment of the present invention, a device used in a remote UE of a ProSe network including a relay UE and an eNodeB associated with it is disclosed. The device includes a memory circuit, which is configured to store a remote UE ID associated with the remote UE and a paired association ID indicating the paired association between the remote UE and the relay UE. The device further includes a processing circuit configured to receive data from the relay UE through the air interface between the eNodeB and the remote UE or through the PC5 interface between the relay UE and the remote UE. The paging message of the remote UE ID of the remote UE in the eNodeB. In some embodiments, the paging message informs the remote UE about the availability of downlink (DL) data for the remote 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, so as to be subsequently sent to the sending circuit through the PC5 interface between the remote UE and the relay UE. Relay UE. In some embodiments, the connection request message is organized into the relay UE to establish a direct connection between the remote UE and the relay UE, so as to receive the DL data via the relay UE. In addition, the processing circuit is configured to receive downlink data signals including the DL data from the eNodeB via the relay UE through the PC5 interface in response to sending the connection request message.

In one embodiment of the present invention, a method for The equipment used in the relay UE of the ProSe network of the UE and its associated eNodeB. The device includes: a memory circuit, which is configured to store the relay UE ID associated with the relay UE, the remote UE ID of the remote UE, and the pairwise association between the relay UE and the remote UE. A pair of associated ID; and a processing circuit, which is configured to receive a connection request message including the cause value of the paging from the remote UE through the PC5 interface between the remote UE and the relay UE. In some embodiments, the cause value of the paging indicates that the remote UE receives an indication from the eNodeB through the air interface or via the relay UE to the remote UE downlink (DL) data Availability of paging messages. In some embodiments, the connection request message is organized to construct the relay UE to establish a direct connection with the remote UE, so that the remote UE can receive and communicate with the remote UE from the eNodeB via the relay UE. The associated DL information. 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, use The Evolved Packet System (EPS) bearer of the remote UE or the relay UE receives the downlink data signal including the DL data from the S-Gateway (S-GW) associated with the eNodeB so as to pass the The PC5 interface is then sent to the remote UE.

In one embodiment of the present invention, a device for use in an eNodeB of a ProSe network including a remote UE and a relay UE associated with it is disclosed. The equipment includes: a memory circuit, which is configured to store the relay UE ID associated with the relay UE and the remote UEID of the remote UE; and a processing circuit, which is configured to store the MME associated with it Place The received paging message associated with the remote UE is provided to the sending circuit so as to pass through the air interface between the eNodeB and the remote UE, or through the PC5 interface between the relay UE and the remote UE The relay UE then sends 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 the 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 side link UE information message at the remote UE Reception of a paging message or 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. , Forward the DL data associated with the remote UE received from the S-Gateway (S-GW) associated with the remote UE to the remote UE.

The present invention will now be described with reference to the drawings, in which the same element symbols are used throughout to indicate the same elements, and in which, the illustrated structures and devices are not necessarily drawn to scale. As used in this article, the terms "component", "system", "interface", "circuit", etc. are intended to refer to computer-related entities, hardware, software (for example, running) and/or firmware . For example, the component can be a processing circuit (for example, a micro processing circuit, a controller, or other processing device), a program, a controller, an object, an executable program, a program, a storage device, a computer, a tablet PC, and/or running on the processing circuit. Or user equipment with processing device (for example, mobile phone, etc.) Wait). By way of explanation, applications running on the server and the server can also be components. One or more components may reside in the program, and the components may be localized on one computer and/or distributed between two or more computers. A group of elements or a group of other components can be described herein, where the term "group" can be interpreted as "one or more."

Furthermore, for example, these components can be executed from various computer-readable storage media such as modules having various data structures stored thereon. The component can communicate through regional and/or remote processes, such as based on a signal with one or more data packets (for example, data from one component interacts with another component in a regional system, a distributed system, and/or Across the network, such as the Internet, local area network, wide area network or similar networks with other systems through the signal).

As another example, a component can be a device with a specific function provided by a mechanical part operated by an electrical or electronic circuit, where the electrical or electronic circuit can be implemented by a software application or by one or more processing circuits Run the firmware application to operate. The one or more processing circuits can be inside or outside the device, and can execute at least a part of the software or firmware application. As yet another example, the component may be a device with a specific function provided by an electronic component without a mechanical part; the electronic component may include one or more processing circuits therein to perform at least partially enabling the electronic component The software and/or firmware of the function.

The exemplified use of words is to present concepts in a concrete way. As used in this application, the term "or" is intended to mean an inclusive "or" rather than an exclusive "or". Meaning, unless otherwise specified or from the above It is clarified below, otherwise "X uses A or B" is intended to indicate any of the natural inclusive arrangements. This means that if X uses A; X uses B; or X uses both A and B, then "X uses A or B" in any of the foregoing cases. In addition, unless otherwise stated or clearly indicating the singular form from the context, the articles "a (a)" and "one (an)" used in the scope of this application and the appended patent application should normally be interpreted To mean "one or more". Furthermore, the terms "including", "includes", "having", "has" and "with" are used in the detailed description and the scope of the patent application. To the extent of its conjugation, such terms are intended to be inclusive in a manner similar to the term "comprising."

In the following description, a number of details are set forth to provide a more thorough explanation of the embodiments of the present invention. However, it will be obvious to those skilled in the art that the embodiments of the present invention can be implemented without these specific details. In other examples, the conventional structures and devices are shown in block diagram form rather than in detail, so as to avoid obscuring the embodiments of the present invention. In addition, unless specifically stated otherwise, the features of the different embodiments described below can be combined with each other.

The current enhanced LTE device-to-device ProSe work item (that is, 3GPP TS 23.303, "Technical Specification Group Service and System State; ProSe (ProSe)") is used to communicate between the remote UE and the eNodeB. The communication relay UE (also referred to as "relay UE" in this document) is used to provide communication between the remote UE and the eNodeB. Under the current enhanced LTE device-to-device ProSe project, 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 E-UTRAN For a direct communication, it includes a relay that supports unicast traffic (UL and DL) between the remote UE and the E-UTRAN. The ProSe UE-to-network relay provides a general layer 3 forwarding function, It can relay any type of IP communications related to public safety communications.

eMBMS relay support: one-to-many communication, which includes support for multimedia broadcast multicast service (eMBMS) relay for remote UEs served by the UE-to-network (UE-to-NW) NW relay.

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

FIG. 1 is a simplified block diagram of a ProSe system 100 according to the current device-to-device ProSe work item of enhanced LTE according to an 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 and EPC 140 are collectively referred to as a "network." In some embodiments, EPC 140 includes a mobility management entity (MME) and a service gateway (S-GW). In some embodiments, the MME handles the control plane of the LTE architecture. The MME handles signaling related to actions and security for the eNodeB access. The gateway, for example, the server GW handles LTE The user plane of the architecture. The S-GW sends IP data traffic between the user equipment (UE) and the external network. As shown in Figure 1, the remote UE 110 is generally considered to be outside the coverage of the network, but can use relay support to relay 120 to the network via the ProSe UE (sometimes referred to as " Relay UE" 120 or "Relay" 120) to access the network. Alternatively, in other embodiments, the remote UE 110 may be within the coverage area of the network. The eNodeB 130 is configured to be a communication point where the UE 120 can communicate with the relay to access the EPC 140. The main use case driving this situation is public safety.

The remote UE 110 can use an interface called the "PC5" interface 150 to access the network through the relay UE 120. The PC5 interface 150 is a direct communication interface between two ProSe supporting devices. In addition, the relay UE 120 can use the old Uu interface 160 (ie, air interface) located between the relay UE 120 and the eNodeB 130 to connect to the eNodeB 130 and thereby connect to the EPC 140. The eNodeB 130 can use the S1 interface 180 to access the EPC 140. In the 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 the old Uu interface between the remote UE 110 and the eNodeB 130. In some embodiments, the remote UE 110 includes a low-power, low-redisconnection device, for example, a wearable UE such as a smart watch, which is better connected through the relay UE 120, rather than through the old 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. Described in this article In this embodiment, it is assumed that the remote UE and the relay UE know their pairwise association (for example, using a discovery procedure). Furthermore, in some embodiments, it is assumed that the remote UE 110 is in an idle mode with respect to the radio resource control (RRC) through the Uu interface. In other words, the remote UE does not have any connection or bearer established with the network, and uses the PC5 interface to communicate with the network to save power. The relay UE 120 is assumed to be within the coverage area for substantially all time periods. The relay UE may be in RRC idle mode or RRC connected mode.

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

The embodiments disclosed in this article are related to downlink reachability for remote UEs within and outside the coverage of the network, so as to enable the remote UE to receive downlink (DL) from the network. )material. The basic principle relates to how a remote UE 110 (ie, a low-power wearable UE) that is in the coverage area but in idle mode can relay through the PC5 interface 150 through the UE 120 (which can be in idle mode or connected mode) )Come Receive information. One way to enable this is to use L3 relays to use agreed layer 3 relays (ie, IP routers) to relay the EPS bearer of the UE 120 between the remote UE 110 and the network. Any type of IP communications (for example, data). The relay UE 120 may only have a limited number of EPS bearers established, and therefore, using 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.

Alternative solutions include layer 2 or L2 relays, where the remote UE 110 uses the EPS bearer established in the network for the remote UE 120 to communicate between the remote UE 110 and the network via the relay UE 120. Transfer any type of IP traffic (for example, data) between. That is, the remote UE 110 can send or receive data that can be mapped through its own EPS bearer in the network. In other embodiments, the downlink reachability of remote UEs outside the coverage of the network is also considered. In the current LTE system (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 for the downlink reachability of 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 area of the network, and in other embodiments, it is assumed that the remote UE is outside the coverage area. In some embodiments, the proposed method of downlink reachability enables the remote UE 110 to receive downlink (DL) data from the network via the relay UE 120. In detail, in one embodiment of the present invention, it is proposed to be used at the remote UE 110 based on the paging message received from the eNodeB 130 (Not shown) The first method of receiving DL data from eNodeB 130. In this embodiment, the paging message is received from the eNodeB 130 through the air interface between the remote UE 110 and the eNodeB 130. In another embodiment of the present invention, a second method for receiving DL data from the eNodeB 130 based on the paging message (not shown) received from the eNodeB 130 at the remote UE 110 is proposed. In this embodiment, the paging message is received from the eNodeB 130 via the relay UE 130 through the PC5 interface 150.

FIG. 2 depicts the downlink performance of the remote UE 210 in the ProSe system 200 that receives paging messages from the eNodeB associated therewith through the air interface between the remote UE and the eNodeB according to an embodiment of the present invention. Reachability. In some embodiments, the proposed method of downlink reachability enables the remote UE 210 to receive downlink (DL) data from the network via the 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 include 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 before the DL data transfer from the network to the remote UE 210 is initiated via the relay UE 212, both the remote UE 210 and the relay UE 212 go through the initial attachment establishment procedure 219 And it is temporarily saved to the network. In some embodiments, information about the pairwise association between the remote UE 210 and the relay UE 212 is provided to the network during the initial attachment establishment procedure 219. In some embodiments, the paired relationship between the remote UE 210 and the relay UE 212 is predetermined, while in other implementations. In the embodiment, other procedures (for example, discovery) are used to determine the pairwise association. In some embodiments, the paired association ID identifying the paired association between the remote UE 210 and the relay UE 212 is generated at the MME 216 and is provided to the remote during the initial attachment establishment procedure 219. End UE 210 and relay UE 212. The remote UE 210 is in the RRC idle mode, and the relay UE 212 is in the RRC connected mode. However, in other embodiments, the relay UE 212 may be in the RRC idle mode.

When the S-GW 218 has DL data available for the remote UE 210, the S-GW 218 initiates the transfer of the DL data to the remote UE 210. In some embodiments, the DL data transfer is initiated by sending a DL notification message 221 including the remote ID associated with the remote UE 210 to the MME 216. In some embodiments, the DL notification message 221 further includes the 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 configured 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 remote ID of the remote UE 210, and the eNodeB 214 is further configured to send the paging message 223 to the remote through the air interface between the eNodeB 214 and the remote UE 210 UE 210. In some embodiments, the eNodeB 214 is configured to configure the remote UE 210 to check the paging message through the air interface, so as to enable the remote UE 210 to receive DL data. In some embodiments, the remote UE 210 is grouped to monitor the remote End the paging occasion of the UE 210 and receive the paging message from the eNodeB 214. In some embodiments, the remote UE 210 is grouped to monitor the paging occasion of the remote UE 210 based on the remote UE ID.

Upon receiving the paging message 223, the remote UE 210 is configured to generate a connection request message 220 including the cause value of the paging or DL data. The remote UE 210 is further configured to send a connection request message 220 to the relay UE 212 through the PC5 interface between the remote UE 210 and the relay UE 212, so as to establish direct communication with the relay UE 212 so as to pass through the middle. Then the UE 210 receives the DL data. In some embodiments, the paging reason value in the connection request message 220 indicates the reception of the paging message at the remote UE 210. In some embodiments, the relay UE 212 is grouped to generate and send a connection response message 222 to the remote UE 210 as a confirmation of receiving 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 configured to establish its own RRC connection and enter the RRC connection mode. In some embodiments, the relay UE 210 and the remote UE 212 are grouped to perform mutual authentication to confirm the paired association between the remote UE 210 and the relay UE 212. In some embodiments, establishing the RRC connection includes setting the EPS bearer or the radio bearer, for example, a signaling radio bearer (SRB5) for the UE in the network. In some embodiments, in the RRC idle mode, the UE (e.g., the relay UE 212) is known to the EPC (but not to the eNodeB 214), and in the RRC connected mode, the UE ( For example, the relay UE 212) is for both the EPC and eNodeB 214 Department is known.

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

In some embodiments, the service request procedure for establishing the EPS bearer of the remote UE 210 is initiated or executed by the relay UE 212 on behalf of the remote UE 210. In these embodiments, the service request procedure is performed by the relay UE 212 by providing one or more messages including the relay UE ID and the paired association ID to the eNodeB 214 to enable the The S1-U tunnel of the remote UE 210 in the core network is established 232. Alternatively, in other embodiments, the service request procedure for establishing the EPS bearer of the remote UE 210 is performed by the remote UE 210 via the relay UE 212. In these embodiments, the remote UE 210 is configured to perform the service request procedure by generating one or more messages (for example, RRC connection establishment messages), which are then carried in the container through the PC5 interface (container) and transparently forwarded by the relay UE 212 to the eNodeB 214 for further processing. Starting the EPS bearer establishment of the remote UE 210 based on the service request from the relay UE 212 implies that the remote UE 210 is still in the RRC idle state regarding the establishment of the RRC connection through the air interface (or regarding the network) In the mode, however, the EPS bearer of the remote UE 210 is still activated and used for data transfer in the path of the S-GW-eNodeB-relay UE.

In some embodiments, the eNodeB 214 is configured to generate an S1-AP message 228 including the remote UE ID of the remote 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 the EPS bearer ID of the remote UE 210 during the L2 relay or the 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 the transmission of the DL data. Upon receiving the S1-AP message 228, the MME 216 is further configured 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 configured to send the DL data to the eNodeB 214 for the relay UE 212 and then to the remote UE 210. In some embodiments, the DL data is sent by the S-GW 218 using the EPS bearer (for example, L2 relay) of the remote UE 210 DL data. In other embodiments, the DL data is sent by the S-GW 218 using the EPS bearer (for example, L3 relay) of the relay UE 212 to transmit the DL data.

In some embodiments, after the direct communication is established between the remote UE 210 and the relay UE 212 through the PC5 interface, the relay UE 210 can reach out of the coverage area of the network. In these embodiments, the remote UE 210 will continue to receive the DL data via the relay UE 212 until the remote UE 210 becomes inactive for a certain 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.

Or, in some embodiments, when the remote UE uses pre-structured resources outside the coverage area, a resource restriction pattern can be defined for each remote UE, and accordingly the remote UE can check that it contains The paging information of the remote UE ID to identify whether the remote UE has any DL data it needs. Furthermore, in some embodiments, if the relay UE 212 informs the eNodeB 214 about the PC5 idle mode of the remote UE 210, the eNodeB 214 may 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 remote UE 210.

Figure 3 depicts a transmission based on a relay UE received from its associated eNodeB via a PC5 interface according to an embodiment of the present invention. The downlink reachability of the remote UE 310 in the ProSe system 300 of the call message. 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 Evolved 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 may reach out of the coverage area of the network.

In some embodiments, it is assumed that before the DL data transfer to the remote UE 310 is initiated via the relay UE 312, both the remote UE 310 and the relay UE 312 are processed through the initial attachment establishment procedure 319. Temporarily save to this network. In some embodiments, the initial attach procedure 319 is executed when the respective devices are turned on. In some embodiments, during the initial attach procedure 319, a PDN connection is established with the network and the necessary bearers for the remote UE 310 and the relay UE 312 are established. In some embodiments, information about the pairwise association between the remote UE 310 and the relay UE 312 is provided to the network during the initial attachment establishment procedure 319. In some embodiments, the paired relationship between the remote UE 310 and the relay UE 312 is predetermined, while in other embodiments, other procedures (for example, discovery) are used to determine the paired relationship. In some embodiments, during the initial attachment establishment procedure 319, an identification is generated at the MME 316 between the remote UE 310 and the relay UE 312. The paired association ID between the paired associations is provided to the remote UE 310 and the relay UE 312. Once the initial attach procedure 319 is completed, the remote UE 310 and the relay UE 312 enter the RRC connection mode.

In some embodiments, once the remote UE 310 selects the relay UE 312 associated with it (for example, through discovery), the remote UE 310 is configured to send the PC5 direct communication request message 320 to the PC5 interface through the PC5 interface. The relay UE 312 is used to establish a direct communication link between the remote UE 310 and the relay UE 312 through the PC5 interface, and is further used for mutual authentication to confirm the pairing between the remote UE 310 and the relay UE 312 Associated. In some embodiments, the PC5 direct communication request message 320 from the remote UE 320 further includes a request for paired paging with the relay UE 312. In some embodiments, the PC5 direct communication request message 320 from the remote UE 310 enables the establishment of a paired paging at the relay UE 312, whereby the relay UE 312 can monitor the paging occasion of the remote UE 310 so as to The 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, so that the relay UE can calculate the paging occasion of the remote UE 310 (that is, the paging frame and sub-frame 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 send a paired paging instruction message (for example, a paired paging instruction message 312b or a paired paging instruction Message 312a) to inform the eNodeB 314 about the status of the paired paging. In some embodiments, the paired paging instruction message 321a or 321b includes new or existing A radio resource control (RRC) message, and includes information about the UE ID (ie, the relay UE ID for message 321a or the remote UE ID for message 321b), the paired association id, and information about The sending UE is the identification information of the relay UE 312 or the remote UE 310 and the implicit/explicit paired paging instruction.

In some embodiments, when the paired paging instruction message 321 is established, the remote UE 310 or the relay UE 312 is further configured to use the tracking area update defined in the 3GPP specifications TS23.401 and TS24.301 (TAU) procedure to inform MME 316 about the status of the paired paging. In some embodiments, the paired paging indication message 321a or 321b is further grouped to form. When the paired paging between the remote UE 310 and the relay UE 312 is released, the eNodeB 314 is notified about the connection between the remote UE 310 and the relay UE 312. The state of the paired paging between UEs 312 is released. In these embodiments, the paired paging instruction message 321a or 321b includes information about the UE ID (that is, the relay UE ID for the message 321a or the remote UE ID for the message 321b), The paired association id, the identification information about the sending UE being the relay UE 312 or the remote UE 310, and the implicit/explicit release of the paired paging instruction.

In some embodiments, once there is data inoperability at the relay UE 312, the RRC connection of the relay UE 312 is released. Furthermore, 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 to form a paired paging based on the establishment Status to check the paging message 323 from the eNodeB 314 for the remote UE 310. 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 from the eNodeB 314 for the remote UE 310 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 configured to only monitor the paging occasion of the relay UE 312 in order 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 relay UE ID as defined in the 3GPP specification TS36.304 is used to calculate the paging occasion of the relay UE 312. Or, in other embodiments, the relay UE 312 is grouped to monitor both the paging occasion of the relay UE 312 and the paging occasion of the remote UE 310. In these embodiments, the relay UE 312 is configured to monitor the paging occasion of the remote UE 310 in order 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 as defined in the 3GPP specification TS36.304 is used to calculate the remote UE 310 The timing of the paging.

When the S-GW 318 has DL data available for the remote UE 310, the S-GW 318 initiates the transfer of the DL data to the remote UE 310. In some embodiments, the DL data transfer is activated to send a DL data 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 step includes the EPS bearer ID of the remote UE 310 and the relay UE 312. In some embodiments, the DL data notification message 324 is generated at the S-GW 218 and provides the MME 316 with an indication of the availability of the DL data of the remote UE 310. Upon receiving the DL data notification message 324, based on the DL data notification message 324, the MME 316 is configured to generate a paging message 323 for the remote UE 310. The MME 316 is further configured to send the paging message 323 to the eNodeB 314 based on the information of the paired paging status of the remote UE 310 and the relay UE 312 (that is, belong to the tracking area where the relay UE 312 is temporarily stored) The eNodeB).

In some embodiments, the eNodeB 314 is configured to forward or send the paging message 323 received from the MME 316 to the relay UE 312 for subsequent transmission to the remote UE 310 during the paging occasion of the relay UE 312. In some embodiments, the paging message 323 includes paging information for the relay UE 312 and the remote UE 310, and the relay UE ID as defined in the 3GPP specification TS36.331 is used to determine the relay UE 312 the timing of the paging. Or, in other embodiments, the eNodeB 314 is formed in the paging occasion of the remote UE 310 determined based on the remote UE ID, and forwards or sends the paging message 323 received from the MME 316 to the relay UE. 312 for subsequent transmission to the remote UE 310. In these embodiments, if the paging timing of the remote UE 310 is different from the paging timing of the relay UE 312, the paging message as defined in the 3GPP specification TS36.331 only includes The paging information of UE 310.

Upon receiving the paging message 323, the relay UE 312 executes The service request procedure 329 of the UE 312 is relayed, and the RRC connection mode is entered. In some embodiments, entering the RRC connected mode enables the relay UE 312 to transfer the paging message 323 to the remote UE 310. In some embodiments, the paging message 323 is sent from the relay UE 312 to the remote UE 310 based on a periodic discovery message using the physical downlink shared channel (PSDCH). In these embodiments, the remote UE 310 is configured to monitor the periodic announcement message including the periodic discovery message from the relay UE 312 (for example, organized every N seconds) in order to receive the paging message from the eNodeB 314 323. In some embodiments, the paging message 323 is sent from the relay UE 312 to the remote UE 310 using one or more discovery resource elements of a pre-configured resource pattern with a paging occasion (PO) that the remote UE 310 is monitoring .

In some embodiments, the paging message 323 is relayed from the PC5 interface through the side link paging control channel defined to transmit the remote UE 310 periodically to check downlink paging information and system information. The UE 312 sends to the remote UE 310. In these embodiments, the relay UE 312 can check the periodicity of the paging from the relay UE 312 by assigning it to divide the remote UE 310 into different paging occasions in time through the PC5 interface. Furthermore, in some embodiments, the paging message 323 uses the resources of the relay communication configured by the eNodeB 314 for the remote UE 310 to periodically check or read to relay from the UE 312 through the PC5 interface. Send directly to the remote UE 310.

Upon receiving the paging message 323, the remote UE 310 is configured to generate a connection request message 325 including the cause value of the paging or DL data. Far The end UE 310 is further configured to send a connection request message 325 to the relay UE 312 through the PC5 interface between the remote UE 310 and the relay UE 312, so as to establish direct communication with the relay UE 312 so as to pass through The UE 310 is relayed to receive the DL data. In some embodiments, the paging reason value in the connection request message 325 indicates the reception of the paging message 323 at the remote UE 310. In some embodiments, the relay UE 312 is configured to generate the connection response message 327 and send the connection response message 327 to the remote UE 310 as a confirmation of receiving the connection request message 325. In some embodiments, the relay UE 310 and the remote UE 312 are grouped to perform mutual authentication to confirm the paired association between the remote UE 310 and the relay UE 312.

In some embodiments, the relay UE 312 is further configured to generate a side link UE information message 326 including the remote UE ID of the remote UE 310 for subsequent transmission to the eNodeB 314 to cause the remote UE 310 It can be seen in eNodeB 314 and its associated MME 316 for DL data transfer. In some embodiments, the side link UE information message 326 is further organized into the fabric eNodeB 314 to generate communication resources for the remote UE 310. In some embodiments, the side link UE response message (not shown) including the generated configuration parameters is sent from the eNodeB 314 to the relay UE 312 for subsequent transmission to the remote UE through the PC5 interface 310. In some embodiments, in order to use the L2 relay to receive DL data at the remote UE 310, the EPS bearer of the remote UE 310 must be established in the network. During the L3 relay, use the EPS bearer for the relay UE 312 (it has been established when the relay UE 312 enters the RRC connection 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 remote UE 310 when receiving the connection request message 325 from the remote UE 310.

In some embodiments, the service request procedure for establishing 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 these embodiments, the service request procedure 331 is performed by the relay UE 312 by providing one or more messages including the relay UE ID (for example, S-TMSI) and the paired association ID to the eNodeB 314. Execute to enable S1-U tunnel establishment 332 for the remote UE 310 in the core network. Alternatively, in other embodiments, the service request procedure for establishing 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 the service request procedure 333 by generating one or more messages (for example, an RRC connection establishment message), which is then carried in a container through the PC5 interface, And it is obviously forwarded by the relay UE 312 to the eNodeB 314 for further processing. Initiating the EPS bearer establishment of the remote UE 310 based on the service request from the relay UE 312 implies that the remote UE 310 is still in RRC regarding the establishment of the RRC connection through the air interface (or regarding the network). In the idle mode, however, the EPS bearer of the remote 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 configured to generate the S1-AP message 328 including the remote UE ID of the remote UE 310 for subsequent Send 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 remote 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 about the EPS bearer to be used for the transmission of the DL data. Upon receiving the S1-AP message 328, the MME 316 is further configured 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 configured to send the DL data to the eNodeB 314 for the relay UE 312 and then to the remote UE 310. In some embodiments, the DL data is sent by the S-GW 318 using the EPS bearer (for example, L2 relay) of the remote UE 310, while in other embodiments, the DL data is sent by The S-GW 318 uses the EPS bearer (for example, 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 the coverage area of the network. In these embodiments, the remote UE 310 will continue to receive the DL data via the relay UE 312 until the remote UE 310 becomes inactive for a certain period of time. In this case, the direct connection between the remote UE 310 and the relay UE 312 is resolved. In addition, 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 area, it can be used for each remote UE when the remote UE can check the paging information including the remote UE ID. To define the resource restriction pattern to identify whether the remote UE has any DL data it needs. Furthermore, in some embodiments, if the relay UE 312 informs the eNodeB 314 about the PC5 idle mode of the remote UE 310, the eNodeB 314 may 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 remote UE 310.

4 shows a block diagram of a device 400 for use in a remote or wearable user equipment (UE) in a ProSe system according to the various embodiments described herein, which facilitates the remote UE Downlink reachability. In some embodiments, the downlink reachability of the remote UE is achieved based on the paging message received from the eNodeB through the air interface 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 relay UE through the PC5 interface between the relay UE and the remote UE The message comes. For the embodiment in which the paging message is received through the air interface, the remote UE is described herein with reference to the remote UE 210 in FIG. The embodiment in which the relay UE receives the paging message is described herein with reference to the remote UE 310 in FIG. 3.

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

In order to enable downlink reachability in the remote UE in the ProSe system, the processing circuit 430 of the device 400 is configured to receive paging messages from the eNodeB or its associated MME through the receiving circuit 410 (for example, in The paging message 223 in FIG. 2 or the paging message 323 in FIG. 3). In some embodiments, the device 400 may be included in the remote UE 210 of FIG. 2. In these embodiments, the processing circuit 430 directly receives the paging message ( For example, paging message 223 in Figure 2). Upon receiving the paging message, the processing circuit 430 is configured to generate a connection request message (for example, the connection request message 220) including the cause value of the paging or DL data. The processing circuit 430 is further grouped to form a transmission circuit 420 The connection request message is sent to the relay UE through the PC5 interface located between the remote UE 210 and the relay UE to establish direct communication with the relay UE, so that it can be received via the relay UE The DL information. In some embodiments, the processing circuit 430 is further configured to receive the connection response message (for example, the connection response message 222) from the relay UE through the receiving circuit 410, as a confirmation for sending the connection request message 220. In some embodiments, the memory circuit 440 is configured to store the remote UE ID associated with the remote UE (for example, the remote UE 210) and to indicate the remote UE and the relay UE (for example, the middle UE). The paired association ID following the paired association of UE 212) (obtained during the initial attach procedure indicated above).

In some embodiments, the processing circuit 430 is further configured to initiate a service request procedure when establishing direct communication with the relay UE so as to establish the EPS bearer of the remote UE in the network. In these embodiments, the processing circuit 430 is configured to perform the service request procedure (for example, the service request procedure 233) by generating one or more messages (for example, the RRC connection establishment message), which is then configured to execute the service request procedure (for example, the service request procedure 233) in the container The sending circuit 420 is sent to the relay UE through the PC5 interface for subsequent sending to the eNodeB. Once the EPS bearer of the remote UE is established in the network, the processing circuit 430 is configured to use the EPS bearer of the remote UE during the L2 relay to receive DL data from the eNodeB via the relay UE. In some embodiments, the processing circuit 430 is configured to use the EPS bearer of the relay UE during the L3 relay to receive DL data from the eNodeB via the relay UE.

In some embodiments, the device 400 may be included in the remote UE 310 in FIG. 3. In these embodiments, the processing circuit 430 uses the PC5 interface between the relay UE and the remote UE via the relay UE (eg, the relay UE 312 in FIG. 3) from the eNodeB (eg, The eNodeB 314 in FIG. 3) receives the paging message (for example, the paging message 323 in FIG. 3). In some embodiments, the processing circuit 430 is configured to monitor periodic discovery messages from the relay UE in order to receive the paging message via the relay UE. In some embodiments, the processing circuit 430 is configured to monitor one or more discovery resource elements of the pre-configured resource pattern of the relay UE so as 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 that is defined for transmitting downlink paging information and system information, so that the relay UE can communicate with each other. Receive the paging message.

In some embodiments, the memory circuit 440 is configured to store the remote UE ID associated with the remote UE (for example, the remote UE 310) and to indicate the remote UE and the relay UE (for example, the middle UE). The paired association ID following the paired association of UE 312) (obtained during the initial attach procedure indicated above). 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, the processing circuit 430 is configured to send the PC5 direct communication request message (for example, the PC5 direct communication request message 320) to the relay through the sending circuit 420 before receiving the paging message from the relay UE. UE in order to establish the remote The paired paging between the end UE and the relay UE. In some embodiments, the PC5 direct communication request message from the remote UE includes a request for paired paging 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 instruction message (for example, a paired paging instruction message 321) to notify the eNodeB about The status of the paired paging.

When receiving the paging message from the eNodeB via the relay UE, the processing circuit 430 is configured to generate a connection request message (for example, the connection request message 325) including the cause value of the paging or DL data. The processing circuit 430 is further configured to send the connection request message to the relay UE through the sending circuit 420 through the PC5 interface between the remote UE and the relay UE, so as to establish a connection with the relay UE. Direct communication to receive the DL data via the relay UE. In some embodiments, the processing circuit 430 is further configured to receive the connection response message (for example, the connection response message 327) from the relay UE through the receiving circuit 410 as a confirmation for sending the connection request message.

In some embodiments, the processing circuit 430 is further configured to initiate a service request procedure when establishing direct communication with the relay UE so as to establish the EPS bearer of the remote UE in the network. In these embodiments, the processing circuit 430 is configured to perform the service request procedure (for example, the service request procedure 333) by generating one or more messages (for example, the RRC connection establishment message), which is then arranged in the container The sending circuit 420 is sent to the relay UE through the PC5 interface for subsequent sending to the eNodeB. Once the EPS bearer of the remote UE is established in the network, The processing circuit 430 is configured to use the EPS bearer of the remote UE during the L2 relay to receive DL data from the eNodeB via the relay UE. In some embodiments, the processing circuit 430 is configured to use the EPS bearer of the relay UE during the L3 relay to receive DL data from the eNodeB via the relay UE.

FIG. 5 shows a block diagram of a device 500 used in a relay user equipment (UE) in a ProSe system according to the various embodiments described herein, which facilitates the remote UE associated therewith Accessibility of the middle and downlink links. In some embodiments, the downlink reachability of the remote UE is enabled based on transmitting downlink (DL) data associated with the remote 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 downlinks associated with the remote UE through the relay UE. Link (DL) data to achieve. The device 500 includes a receiver circuit 510, a processing circuit 530, and a transmitter circuit 520. Furthermore, in some embodiments, the device 500 includes a memory circuit 540 coupled to the processing circuit 530. Each of the receiver circuit 510 and the transmitter circuit 520 is grouped to be coupled to one or more antennas, and the antennas may be the same or different antennas. In some embodiments, the receiver circuit 510 and the transmitter circuit 520 may have one or more components in common, and both may be included in the transceiver circuit, while in other aspects, they are not included in the Inside the transceiver circuit. In various embodiments, the device 500 may be included in the UE, for example, having the device 500 (or a portion thereof) in the receiver and transmitter or transceiver circuits of the UE.

In some embodiments, the device 500 may be included in the relay UE 212 of FIG. 2. The processing circuit 530 is configured to receive the connection request message (for example, the connection request message 220) from the remote UE (for example, the remote UE 210) through the receiving circuit 510. In some embodiments, the processing circuit 530 is configured to establish a direct connection between the relay UE and the remote UE based on the connection request message. The processing circuit 530 is further configured to generate a connection response message (for example, a connection response message 222) and send the connection response message (for example, a connection response message 222) to the remote UE through the sending circuit 520 as a response to receiving the connection request 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 (for example, side link Route UE information message 226) to be subsequently sent to the eNodeB (for example, eNodeB 214) through the sending circuit 520, so that the remote UE can be visible to the eNodeB and its associated MME (for example, MME 216) for use For DL data transfer. In some embodiments, the relay UE is further configured to process the service request procedure to establish the EPS bearer of the remote UE when receiving the connection request message from the remote UE.

In some embodiments, the processing circuit 540 is configured to provide one or more messages including the relay UE ID and the paired association ID to the eNodeB through the sending circuit 520 to perform the operation for the remote The service request procedure of the UE (for example, the service request procedure 231) in order to enable the S1-U tunnel establishment 232 for the remote UE in the core network. or Alternatively, in other embodiments, the processing circuit 540 is configured to perform the service request procedure (for example, the service request procedure 233) by forwarding one or more messages from the remote UE to the eNodeB for further use.的处理。 The treatment. Once the EPS bearer of the remote UE is established in the network, the processing circuit 530 is configured to use the EPS bearer of the remote UE to receive DL data from the eNodeB during the L2 relay, so as to use the transmitting circuit 520 for subsequent Sent to the remote UE. In some embodiments, the processing circuit 530 is configured to use the EPS bearer of the relay UE to receive DL data from the eNodeB during the L3 relay. In some embodiments, after the direct connection between the remote UE and the relay UE is released, the processing circuit 530 is further configured to buffer the DL data for a predetermined period of time.

In some embodiments, the device 500 may be included in the relay UE 312 of FIG. 3. The processing circuit 530 is configured to receive the connection request message (for example, the connection request message 325) from the remote UE (for example, the remote UE 310) through the receiving circuit 510. In some embodiments, the 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, the processing circuit 530 is configured to respond to sending a paging message (eg, paging message 323) from the processing circuit 530 to the remote UE and receiving the connection request message from the remote UE. In some embodiments, the processing circuit 530 is configured to use periodic discovery messages to send the paging message received from the eNodeB to the remote UE. In some embodiments, the processing circuit 530 is configured to use one of the pre-configured resource types of the relay UE or A plurality of discovery resource elements send the paging message received from the eNodeB to the remote UE. In some embodiments, the processing circuit 530 is configured to use the paging message received from the eNodeB through the side link paging control channel of the PC5 interface defined for transmitting downlink paging information and system information Sent to the remote UE.

In some embodiments, the processing circuit 530 is configured to receive the paging message from its associated eNodeB (for example, eNodeB 314), for paging based on the pair between the remote UE and the relay UE The association is then sent to the remote UE through the sending circuit 520. In some embodiments, the paging message associated with the remote UE is received from the eNodeB at the processing circuit 530 based on monitoring the paging timing of the remote UE or the paging timing of the relay UE. In some embodiments, the processing circuit 530 is further configured to receive the PC5 direct communication request message (for example, the PC5 direct communication request message 320) through the receiving circuit 510 before sending 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 for paired paging 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 send a paired paging instruction message (for example, a paired paging instruction message 321a) to notify the eNodeB about The status of the paired paging.

In some embodiments, the processing circuit 530 is further configured to generate a connection response message (for example, a connection response message 327) and send the connection response message (for example, a connection response message 327) through the sending circuit 520 To the remote UE as a confirmation 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 (for example, side link The UE information message 326) is sent to the eNodeB (for example, eNodeB 314) through the sending circuit 520, so that the remote UE can be visible to the eNodeB and its associated MME (for example, MME 316). For DL data transfer. In some embodiments, the processing circuit 530 is further configured to process the service request procedure to establish the EPS bearer of the remote UE when the connection request message is received from the remote UE.

In some embodiments, the memory circuit 540 is configured to store the relay UE ID associated with the relay UE (e.g., relay UE 312), and the remote UE ID associated with the remote UE ( For example, the remote UE 310) and the paired association ID indicating the paired association between the remote UE and the relay UE (for example, the relay UE 312) (obtained during the initial attach procedure indicated above) ). In some embodiments, the processing circuit 540 is configured to provide one or more messages including the relay UE ID and the paired association ID to the eNodeB through the sending circuit 520 to perform the operation for the remote The service request procedure of the UE (for example, the service request procedure 331) in order to enable the S1-U tunnel establishment 332 for the remote UE in the core network. Or, in other embodiments, the processing circuit 540 is configured to perform the service request procedure (for example, the service request procedure) by forwarding one or more messages from the remote UE to the eNodeB. 333) for further processing. Once the EPS bearer of the remote UE is established in the network, the processing circuit 530 is configured to use the EPS bearer of the remote UE to receive DL data from the eNodeB during the L2 relay, so as to use the transmitting circuit 520 for subsequent Sent to the remote UE. In some embodiments, the processing circuit 530 is configured to use the EPS bearer of the relay UE to receive DL data from the eNodeB during the L3 relay. In some embodiments, after the direct connection between the remote UE and the relay UE is released, the processing circuit 530 is further configured to buffer the DL data for a predetermined period of time.

FIG. 6 shows a block diagram of a device 600 used in an eNodeB in a ProSe system according to the various embodiments described herein, which facilitates downlink availability in the remote UE associated therewith Reachability. In some embodiments, the downlink reachability of the remote UE is based on sending a paging message associated with the remote UE from the eNodeB through the air interface between the remote UE and the eNodeB And it is achieved by sending downlink (DL) data associated with the remote UE from the eNodeB through the relay UE associated therewith. Or, in other embodiments, the downlink reachability of the remote UE is based on sending and sending from the eNodeB through the relay UE through the PC5 interface between the relay UE and the remote UE. The paging message associated with the remote UE is achieved by sending downlink (DL) data associated with the remote UE from the eNodeB via the relay UE.

The device 600 includes a receiver circuit 620, a processing circuit 630, and a transmitter circuit 610. Furthermore, in some embodiments, the device 600 includes a coupled The memory circuit 640 connected 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, and the antennas may be the same or different antennas. Furthermore, in some embodiments, the device includes a memory circuit 640 coupled to the processing circuit 630. In some embodiments, the receiver circuit 620 and the transmitter circuit 610 may have one or more components in common, and both may be included in the transceiver circuit, while in other aspects, they are not included in the Inside the transceiver circuit. In various embodiments, the 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, the device 600 may be included in the eNodeB 214 in FIG. 2. In these embodiments, the processing circuit 630 is configured to transmit the paging message associated with the remote UE (for example, the remote UE 210) through the air interface between the remote UE and the eNodeB through the transmission circuit 610 (For example, paging message 223) is sent to the remote UE. In some embodiments, the memory circuit 640 is configured to store the relay UE ID associated with the relay UE (eg, the relay UE 212) and the information obtained during the initial attach procedure indicated above The remote ID associated with the remote UE (for example, the remote UE 210). In some embodiments, the processing circuit 630 is configured to send the paging message to the remote UE in the paging timing of the remote UE determined based on the remote UE ID.

In some embodiments, the processing circuit 630 is configured to receive the paging message from its associated MME (for example, MME 216) before sending the paging message to the remote UE. In some embodiments, to 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 (for example, the relay UE 212) through the receiving circuit 620 in response to sending the paging message to the remote UE. Information message (for example, side link UE information message 226). In some embodiments, the side link UE information message indicates the reception 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 directly from the relay UE, so as to establish the network in the network. EPS bearer of the remote UE. Upon receiving the one or more messages (that is, through the service request procedure 231 or 233), the processing circuit 630 establishes the EPS bearer of the remote UE in the network. When receiving the side link UE information message, the processing circuit is further configured to generate an S1-AP message (for example, the S1-AP message 228) for subsequent transmission to the MME through the sending circuit 610. In some embodiments, the S1-AP message includes the remote UE ID, which is used to indicate the reception of the paging message at the remote UE. In some embodiments, the S1-AP message further includes information about the EPS bearer ID of the relay UE used to send the DL data to the remote UE or the EPS bearer of the remote UE. The processing circuit 630 is further configured to use the EPS bearer of the remote UE for L2 relay and is used for The EPS bearer of the relay UE of the L3 relay transfers the DL data for the remote UE from the MME to the relay UE through the transmission circuit 610.

In some embodiments, the device 600 may be included in the eNodeB 314 of FIG. 3. In these embodiments, the processing circuit 630 is formed based on the paired paging association between the remote UE and the relay UE, and is related to the remote UE (for example, the remote UE 310) through the transmission circuit 610 The associated paging message (for example, paging message 323) is sent to the relay UE (for example, the relay UE 312). In some embodiments, the processing circuit 630 is further configured to receive a paired paging instruction message from the relay UE or the remote UE through the receiving circuit 620 before sending the paging message to the relay UE (for example, , Paired paging instruction message 321a or 312b). In some embodiments, the paired paging indication message provides information about the paired paging association 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 and the relay UE ID associated with the relay UE (eg, relay UE 312) obtained during the initial attach procedure indicated above. The remote ID associated with the remote UE (for example, the remote UE 310). In some embodiments, the processing circuit 630 is configured to send the paging message associated with the remote UE to the relay UE based on the paging timing of the relay UE determined based on the relay UE ID. Or, in other embodiments, the processing circuit 630 is configured to determine the paging occasion of the remote UE based on the remote UE ID, and associate the paging message with the remote UE Sent to the relay UE.

In some embodiments, the processing circuit 630 is configured to receive the paging message from its associated MME (for example, MME 316) before sending 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 (for example, the relay UE 312) through the receiving circuit 620 in response to sending the paging message to the relay UE. Information message (for example, side link UE information message 326). In some embodiments, the side link UE information message indicates the reception 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 on behalf of the remote UE, so as to communicate on the network The EPS bearer of the remote UE is established on the road. Upon receiving the one or more messages (associated with the service request procedure 331 or 333), the processing circuit 630 establishes the EPS bearer of 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 (for example, the S1-AP message 328) for subsequent transmission to the MME through the sending circuit 610. In some embodiments, the S1-AP message includes the remote UE ID, which is used to indicate the reception of the paging message at the remote UE. In a certain In some embodiments, the S1-AP message further includes information about the EPS bearer ID of the relay UE used to send the DL data to the remote UE or the EPS bearer of the remote UE. Upon receiving the S1-AP message, the processing circuit 630 is configured to use the EPS bearer of the remote UE for L2 relay and use the EPS bearer of the relay UE for L3 relay, through the sending circuit 610 The DL data for the remote UE is transferred from the MME to the relay UE.

FIG. 7 shows a flowchart of a method 700 for a remote UE in a ProSe system including a relay UE and an eNodeB associated with it, according to an embodiment of the present invention, which facilitates downlink of the remote UE Accessibility. The method 700 is described herein with reference to the device 400 in FIG. 4 and the ProSe system 200 in FIG. 2. In some embodiments, the device 400 is included in the remote UE 210 of the ProSe system 200. At 702, the remote UE ID associated with the remote UE and the paired association ID indicating the paired association between the remote UE and the relay UE (obtained during initial attachment) are stored in In 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 receiving circuit 410 through the air interface between the eNodeB and the remote UE. In some embodiments, the paging message indicates the remote UE about the availability of downlink (DL) data for the remote UE.

At 706, in response to receiving the paging message, a connection request message including the reason value for the paging is generated at the processing circuit 430, so as to pass through the sending 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 setting message is organized to construct the relay UE to establish a PC5 direct connection between the remote UE and the relay UE, so as to receive the DL data through the relay UE. At 708, when the PC5 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 via the relay UE is It is selectively activated at the processing circuit 430. In other embodiments, the service request procedure for establishing the EPS bearer of the remote UE in the network is initiated by the relay UE. At 710, use the EPS bearer of the remote UE during the L2 relay or use the EPS bearer of the relay UE during the L3 relay and pass through the PC5 interface through the relay UE through the receiving circuit 410 at the processing circuit 430 To receive the downlink data signal including the DL data.

FIG. 8 shows a flowchart of a method 800 for a remote UE in a ProSe system including a relay UE and an eNodeB associated with it according to an embodiment of the present invention, which facilitates the downlink of the remote UE Accessibility. The method 800 is described herein with reference to the device 400 in FIG. 4 and the ProSe system 300 in FIG. 3. In some embodiments, the device 400 is included in the remote UE 310 of the ProSe system 200. At 802, the remote UE ID associated with the remote UE and the paired association ID indicating the paired association between the remote UE and the relay UE (obtained during initial attachment) are stored in In the memory circuit 440 of the remote UE. At 804, the paging message includes the PC5 interface between the relay UE and the remote UE and the reception circuit 410 via the relay UE. The processing circuit 430 processes the remote UE ID of the remote UE received from the eNodeB. In some embodiments, the paging message indicates the remote UE about the availability of 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 responding to receiving the paging message through the PC5 interface between the remote UE and the relay UE. The sending circuit 420 then sends to the relay UE. In some embodiments, the connection setting message is organized to construct the relay UE to establish a PC5 direct connection between the remote UE and the relay UE, so as to receive the DL data through the relay UE. At 808, when the PC5 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 via the relay UE is It is selectively activated at the processing circuit 430. In other embodiments, the service request procedure for establishing the EPS bearer of the remote UE in the network is initiated by the relay UE. At 810, use the EPS bearer of the remote UE during the L2 relay or use the EPS bearer of the relay UE during the L3 relay and pass through the PC5 interface through the relay UE through the receiving circuit 410 at the processing circuit 430 To receive the downlink data signal including the DL data.

FIG. 9 shows a flowchart of a method 900 for relaying UE in a ProSe system including a remote UE and an eNodeB associated with it according to an embodiment of the present invention, which facilitates downlink of the remote UE Accessibility. The method 900 is described herein with reference to the device 500 in FIG. 5 and the ProSe system 200 in FIG. 2. In some embodiments, the device 500 is included in the relay UE 212 of the ProSe system 200. At 902, the relay UE ID associated with the relay UE, the remote UE ID of the remote UE, and the paired association ID indicating the paired association between the relay UE and the remote UE are stored in the The memory circuit 540 of the relay UE. At 904, through the PC5 interface between the remote UE and the relay UE, the connection request message including the cause value of the paging is received from the remote UE through the receiving circuit 510 at the processing circuit 530. In some embodiments, the cause value of the paging indicates the reception of a paging message at the remote UE, which indicates the availability of downlink (DL) data to the remote UE. In some embodiments, the connection request message is organized to construct the relay UE to establish a direct connection with the remote UE, so that the remote UE can receive and receive the remote UE from the eNodeB via the relay UE. The DL data associated with the UE.

At 906, based on the connection request message, the 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, the service request procedure for establishing the EPS bearer of the remote UE in the network is selected at the processing circuit 530 Sexually start. In other embodiments, the service request procedure for establishing the EPS bearer of the remote UE in the network is initiated by the remote UE. At 910, the EPS bearer of the remote UE is used during L2 relay or the EPS bearer of the relay UE is used during L3 relay, and the processing circuit 530 receives the data including the DL data from the MME associated with it. The downlink data signal is then forwarded to the remote UE.

FIG. 10 shows a flowchart of a method 1000 for relaying a UE in a ProSe system including a remote UE and an eNodeB associated with it according to an embodiment of the present invention, which facilitates the downlink of the remote UE Accessibility. The method 1000 is described herein with reference to the device 500 in FIG. 5 and the ProSe system 300 in FIG. 3. In some embodiments, the device 500 is included in the relay UE 312 of the ProSe system 300. At 1002, the relay UE ID associated with the relay UE, the remote UE ID of the remote UE, and the paired association ID indicating the paired association between the relay UE and 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 sent from the processing circuit 530 of the relay UE to the remote UE through the sending 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 sending the paging message, through the PC5 interface between the remote UE and the relay UE, receive the connection including the cause value of the paging from the remote UE at the processing circuit 530 through the receiving circuit 510 Request message. In some embodiments, the cause value of the paging indicates the reception of the paging message at the remote UE, which indicates the availability of downlink (DL) data to the remote UE. In some embodiments, the connection request message is organized to construct the relay UE to establish a direct connection with the remote UE, so that the remote UE receives and receives the remote UE from the eNodeB via the relay UE. The DL data associated with the UE. At 1008, based on the connection request message, the processing circuit 530 is used to establish a direct connection between the relay UE and the remote UE. At 1010, when that 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 for establishing the EPS bearer of the remote UE in the network is initiated by the remote UE. At 1012, use the EPS bearer of the remote UE during the L2 relay or use the EPS bearer of the relay UE during the L3 relay to receive the downlink data signal including the DL data at the processing circuit 530 and It is then forwarded to the remote UE.

FIG. 11 shows a flowchart of a method 1100 for eNodeB in a ProSe system including a remote UE and a relay UE associated with it according to an embodiment of the present invention, which facilitates downlink of the remote UE Accessibility. The method 1100 is described herein with reference to the device 600 in FIG. 6 and the ProSe system 200 in FIG. 2. In some embodiments, the device 600 is included in the eNodeB 214 of the ProSe system 200. At 1102, the relay UE ID associated with the relay UE and the remote UE ID of the remote UE (both obtained during the initial attach) are stored in the memory circuit 640 of the eNodeB . At 1104, the paging message associated with the remote UE is directly sent from the processing circuit 630 of the eNodeB to the remote UE through the air interface between the eNodeB and the remote UE through the sending circuit 610 . In some embodiments, the paging message associated with the remote UE is received from the MME associated with the eNodeB. In some embodiments, the paging message indicates the availability of downlink (DL) data for the remote UE.

At 1106, in response to sending the paging message to the remote UE, The side link UE information message is received from the relay UE at the processing circuit 630 through the receiving circuit 620. In some embodiments, the side link UE information message includes the remote UE ID and indicates the reception of the paging message at the remote UE or the connection between the remote UE and the relay UE Build or both. At 1108, the processing circuit 630 receives through the receiving circuit 620 at the processing circuit 630 one or more messages associated with the service request procedure used for L2 relay to establish the EPS bearer of the remote UE in the network. At 1110, upon receiving the side link UE information message, an S1-AP message is generated at the processing circuit 630 for use in the sending circuit 610 and then sent to the associated MME. 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's ID 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 data from the S-GW. At 1112, through the processing circuit 630, 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 DL data associated with the remote UE Transfer from the S-Gateway (S-GW) associated with the eNodeB to the relay UE.

FIG. 12 shows a flowchart of a method 1200 for an eNodeB in a ProSe system including a remote UE and a relay UE associated with it, according to an embodiment of the present invention, which facilitates the downlink of the remote UE Accessibility. The method 1200 is described herein with reference to the device 600 in FIG. 6 and the ProSe system 300 in FIG. 3. In some embodiments, the device 600 is included in the eNodeB 314 of the ProSe system 300. exist At 1202, the relay UE ID associated with the relay UE and the remote UE ID of the remote UE (both obtained during the initial attachment) are stored in the memory circuit 640 of the eNodeB. At 1204, the paging message associated with the remote UE is sent from the processing circuit 630 of the eNodeB to the relay UE through the sending 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 its associated MME. In some embodiments, the paging message indicates the availability of downlink (DL) data for the remote UE.

At 1206, in response to sending the paging message to the relay UE, the processing circuit 630 receives the side link UE information message from the relay UE through the receiving circuit 620. In some embodiments, the side link UE information message includes the remote UE ID and indicates the reception of the paging message at the remote UE or the connection between the remote UE and the relay UE Build or both. At 1208, the processing circuit 630 of the eNodeB receives through the receiving circuit 620 one or more messages associated with the service request procedure used for L2 relay to establish the EPS bearer of the remote UE in the network. At 1210, upon receiving the side link UE information message, an S1-AP message is generated at the processing circuit 630 for use in the sending circuit 610 and then sent to the associated MME. 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's ID during the L2 relay. EPS bearer or use the EPS bearer of the relay UE during the L3 relay to forward the DL data from the S-GW material. At 1212, using the EPS bearer of the remote UE during the L2 relay or the EPS bearer of the relay UE during the L3 relay by the processing circuit 630, the DL data associated with the remote UE Transfer from the S-Gateway (S-GW) associated with the eNodeB to the relay UE.

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

The embodiments described herein can be implemented in a system using any suitably configured hardware and/or software. FIG. 13 shows example components of a user equipment (UE) device 1300 for one embodiment. In some embodiments, the UE device 1300 may 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, which are at least as shown in the figure It is coupled together.

The application circuit 1302 may include one or more application processing circuits. For example, the application circuit 1302 may include circuits such as (but not limited to) one or more single-core or multi-core processing circuits. The processing circuit may include any combination of general-purpose processing circuits and special-purpose processing circuits (eg, graphics processing circuits, application processing circuits, etc.). The processing circuit can be combined with memory/storage The device is coupled and/or may include memory/storage, and may be configured to execute instructions stored in the memory/storage to cause various applications and/or operating systems to run on the system.

The baseband circuit 1304 may include circuits, such as (but not limited to) one or more single-core or multi-core processing circuits. The baseband circuit 1304 may include one or more baseband processing circuits and/or control logic to process the baseband signal received from the receive signal path of the RF circuit 1306 and generate a baseband signal for the transmit signal path of the RF circuit 1306 Frequency signal. The baseband processing circuit 1304 can be interfaced with the application circuit 1302 for the generation and processing of the baseband signal and for the control operation of the RF circuit 1306. For example, in some embodiments, the baseband circuit 1304 may 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 (for example, fifth generation (5G), 6G, etc.). The baseband circuit 1304 (for example, one or more of the baseband processing circuits 1304a to d) can process various radio control functions that enable communication with one or more radio networks through the RF circuit 1306. The radio control function may include (but is not limited to) signal modulation/demodulation, encoding/decoding, radio frequency conversion, and so on. In some embodiments, the modulation/demodulation circuit of the baseband circuit 1304 may include fast-Fourier transform (FFT), precoding, and/or constellation mapping/demapping functions. In some embodiments, the encoding/decoding circuit of the baseband circuit 1304 may include convolution, tail-revolution, turbo, Viterbi, and/or low-density parity check (LDPC) coding Decoder/decoder function. The embodiments of modulation/demodulation and encoder/decoder functions are not limited to these examples, and other appropriate functions may be included in other embodiments.

In some embodiments, the baseband circuit 1304 may include protocol stacking components, such as, for example, components of the Evolved Universal Terrestrial Radio Access Network (EUTRAN) protocol, which include, for example, physical (PHY), media 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 to form a stack of elements running the protocol for signaling of the PHY, MAC, RLC, PDCP, and/or RRC layers. In some embodiments, the baseband circuit may include one or more audio digital signal processing circuits (DSP) 1304f. The audio DSP 1304f may include components for compression/decompression and echo cancellation, and may include other suitable processing components in other embodiments. In some embodiments, the components of the baseband circuit can be appropriately combined in a single chip, a single chip group, or placed on the same circuit board. In some embodiments, some or all of the constituent components of the baseband circuit 1304 and the application circuit 1302 may be implemented together, such as, for example, on a system-on-chip (SOC).

In some embodiments, the baseband circuit 1304 can provide communication compatible 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 urban area networks (WMAN), wireless local area networks (WLAN), wireless personal Local Area Network (WPAN) communication. The embodiment in which the baseband circuit 1304 is configured to support more than one wireless protocol radio communication can be called a multi-mode baseband circuit.

The RF circuit 1306 can enable the use of modulated electromagnetic radiation through non-solid media to communicate with the wireless network. In various embodiments, the RF circuit 1306 may include switches, filters, amplifiers, etc., to facilitate the communication with the wireless network. The RF circuit 1306 may include a receiving signal path, and the receiving signal path may include a circuit for down-converting the RF signal received from the FEM circuit 1308 and providing the baseband signal to the baseband circuit 1304. The RF circuit 1306 may also include a transmission signal path, and the transmission signal path may include a circuit for up-converting 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, the RF circuit 1306 may include a receive signal path and a transmit signal path. The receiving signal path of the RF circuit 1306 may include a mixer circuit 1306a, an amplifier circuit 1306b, and a filter circuit 1306c. The transmission signal path of the RF circuit 1306 may include a filter circuit 1306c and a mixer circuit 1306a. The RF circuit 1306 may also include a synthesizer circuit 1306d for synthesizing frequencies used by the mixer circuit 1306a of the receiving signal path and the transmitting signal path. In some embodiments, the mixer circuit 1306a of the receive signal path can be configured to down-convert the RF signal received from the FEM circuit 1308 based on the synthesized frequency provided by the synthesizer circuit 1306d. The amplifier circuit 1306b can be configured to amplify the down-converted signal and the filter circuit 1306c can be configured to remove unwanted signals from the down-converted signal to generate an output. Low-pass filter (LPF) or band-pass filter (BPF) to output the fundamental frequency signal. The output baseband signal can be provided to the baseband circuit 1304 for further processing. In some embodiments, the output fundamental frequency signal may be a zero frequency fundamental frequency signal, although this is not a necessary condition. In some embodiments, the mixer circuit 1306a of the receive signal path may include a passive mixer, although the scope of the embodiment is not limited thereto.

In some embodiments, the mixer circuit 1306a of the transmission signal path can be configured to up-convert the input baseband signal based on the synthesized frequency provided by the synthesizer circuit 1306d to generate the signal for the FEM circuit 1308 RF output signal. The fundamental frequency signal can be provided by the fundamental frequency circuit 1304 and can be filtered by the filter circuit 1306c. The filter circuit 1306c may include a low-pass filter (LPF), although the scope of the embodiment is not limited thereto.

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

In some embodiments, the output fundamental frequency signal and the input fundamental frequency signal may be analog fundamental frequency signals, although the scope of the embodiment is not limited thereto. In some alternative embodiments, the output fundamental frequency signal and the input fundamental frequency signal may be digital fundamental frequency signals. In these alternative embodiments, the RF circuit 1306 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuits, and the baseband circuit 1304 may include a digital baseband interface to communicate with the 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 embodiment is not limited to this.

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 embodiment is not limited to this, because other types of frequency synthesizers may be suitable . For example, the synthesizer circuit 1306d may be an integral triangular synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

The synthesizer circuit 1306d can be configured to synthesize the output frequency used by the mixer circuit 1306a of the RF circuit 1306 based on the frequency input and the divider control input. In some embodiments, the synthesizer circuit 1306d may 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. Depending on the desired output frequency, the frequency divider control input can be provided by the baseband circuit 1304 or the application processing circuit 1302. In some embodiments, it can be based on The channel indicated by circuit 1302 is processed to determine the divider control input (for example, N) from the look-up table.

The synthesizer circuit 1306d of the RF circuit 1306 may include a divider, a delay locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by N or N+1 (e.g., based on execution) to provide a fractional frequency division ratio. In some example embodiments, the DLL may include a series of tunable delay elements, phase detectors, charge pumps, and D-type flip-flops. In these embodiments, the delay elements can be grouped to decompose the VCO period into Nd equal-phase packets, 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, the synthesizer circuit 1306d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (for example, twice the carrier frequency) , Four times the carrier frequency) and used in combination with a quadrature generator and divider circuit to generate multiple signals at the carrier frequencies having multiple different phases relative to each other. In some embodiments, the output frequency may be the LO frequency (fLO). In some embodiments, the RF circuit 1306 may include an IQ/polarity converter.

The FEM circuit 1308 may include a receiving signal path, which may include a circuit that is grouped to form a pair of 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 the RF circuit 1306 for further processing. The FEM circuit 1308 may also include a transmission signal path, which may include a circuit 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 it.

In some embodiments, the FEM circuit 1308 may include a TXIRX switch to switch between the operation of the transmission mode and the reception mode. The FEM circuit may include a receiving signal path and a transmitting signal path. The receiving signal path of the FEM circuit may include a low noise amplifier (LNA) to amplify the received RF signal, and provide the amplified received RF signal as an output (for example, to the RF circuit 1306). The transmission signal path of the FEM circuit 1308 may include: a power amplifier (PA), which is used to amplify the input RF signal (for example, provided by the RF circuit 1306); and one or more filters, which are used to generate RF signals for subsequent transmission (e.g., via one or more of one or more antennas 1310).

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

Although the device has been illustrated and described with respect to one or more embodiments, changes and/or modifications can be made to the illustrated examples without departing from the spirit and scope of the scope of the patent application attached. In detail, with regard to the various functions implemented by the above-described components or structures (components, devices, circuits, systems, etc.), they are used to describe such components The terms (including references to "devices"), unless otherwise stated, are intended to correspond to any component or structure that implements the specific function of the described component (for example, it is functionally equivalent), even if the structure The above is not equivalent to the disclosed structure implementing the function in the exemplary embodiment of the present invention depicted herein.

Examples may include patented subject matter, such as methods, means for performing actions or blocks of methods, and at least one machine-readable medium containing instructions that, when implemented by a machine, can cause the machine to follow what is described herein The embodiments and examples use multiple communication technologies to implement the actions of the method, device, or system for simultaneous communication.

Example 1 is a device used in a ProSe network-based remote user equipment (UE), including a processing circuit, which is grouped to pass through when executing instructions from a memory circuit The air interface between the eNodeB and the remote UE or the PC5 interface between the relay UE and the remote UE through the relay UE of the ProSe network to detect the inclusion of the eNodeB from the ProSe network The paging message of the remote UE ID of the remote UE, wherein the paging message informs the remote UE about the availability of downlink (DL) data for the remote UE; in response to the received paging message, Generate a connection request message including a cause value for paging to be sent to the relay UE through the PC5 interface, so as to establish a direct connection between the remote UE and the relay UE to communicate via the relay UE Receiving the DL data; and in response to the sent connection request message, detect the downlink from the eNodeB including the DL data through the relay UE through the PC5 interface Data signal.

Example 2 is a device including the patent subject 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 pass the relay UE The Evolved Packet System (EPS) bearer of the remote UE is established in the network.

Example 3 is a device (including or omitting components) that includes the patented subject matter of Examples 1 to 2, wherein activating the service request procedure includes providing one or more messages associated with the service request procedure to the service request procedure through the PC5 interface A relay UE, where the one or more messages are then obviously forwarded to the eNodeB by the relay UE.

Example 4 is a device (including or omitting components) that includes the patent subjects of Examples 1 to 3, wherein the downlink data signal is detected during L2 relay using the EPS bearer of the remote UE, and wherein, The downlink data signal is received during the L3 relay using the EPS bearer of the relay UE.

Example 5 is a device (including or omitting components) that includes the patented subject matter of Examples 1 to 4, wherein the processing circuit is further configured to monitor periodic discovery messages from the relay UE so as to receive it via the relay UE The paging message.

Example 6 is a device (including or omitting elements) that includes the patent subjects 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 type of the relay UE, In order to receive the paging message via the relay UE.

Example 7 is a device (including or omitting components) that includes the patented subject matter of Examples 1 to 6, wherein the processing circuit is further configured to periodically pass through the PC5 interface defined for transmitting downlink paging information and system information Ground monitoring of the side link paging control channel so as to receive the paging message via the relay UE.

Example 8 is a device (including or omitting components) that includes the patented subject matter of Examples 1 to 7, wherein the processing circuit is configured to generate the paging message 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 a paired paging request to establish a paired paging between the remote UE and the relay UE.

Example 9 is a device (including or omitting components) that includes the patented subject matter of Examples 1 to 8, wherein the processing circuit is further configured to generate a pair of paging between the remote UE and the relay UE. A paired paging instruction message subsequently sent to the eNodeB, where the paired paging instruction message includes the instruction of the paired paging between the remote UE and the relay UE, the remote UE ID, and the instruction of the remote The paired association ID of the paired association between the UE and the relay UE and the UE sending the paired paging indication message is an indication of the relay UE or the remote UE.

Example 10 is a device used in a relay user equipment (UE) of a ProSe network, which includes: a memory circuit, which is configured to store the relay UE ID associated with the relay UE, the The remote UE ID of the remote UE of the ProSe network and the paired association ID indicating the paired association between the relay UE and the remote UE; the processing circuit, which is grouped through The PC5 interface between the remote UE and the relay UE detects the connection request message including the cause value of the paging from the remote UE, where the cause value of the paging indicates that the remote UE is through the air interface Or receive the paging message from the eNodeB of the ProSe network via the relay UE, the paging message indicates the availability of downlink (DL) data to the remote UE; when the connection request message is received, The relay UE and the remote UE establish a direct connection; and use the remote UE or the relay UE's evolved packet system (EPS) bearer to receive data from the S-gateway associated with the eNodeB The (S-GW) downlink data signal of the DL data is used to establish the direct connection between the relay UE and the remote UE and then send it to the remote UE through the PC5 interface.

Example 11 is a device including the patent subject of Example 10, wherein, before detecting the downlink data signal, the processing circuit is further configured to generate a side link UE including the remote UE ID of the remote UE Information messages for subsequent transmission to the eNodeB so that the remote UE can be visible to the eNodeB and its associated MME for DL data transfer.

Example 12 is a device (including or omitting components) that includes the patented subject matter of Examples 10 to 11, wherein, after the direct connection between the relay UE and the remote UE is established, the processing circuit is further configured in the 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 (including the patented subject matter of Examples 10-12) (Including or omitting components), wherein the processing circuit is further configured to represent 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 service request procedure is used to establish the EPS bearer of the remote UE.

Example 14 is a device (including or omitting components) that includes the patent subjects of Examples 10 to 13, wherein the processing circuit is further configured to communicate between the remote UE received from the remote UE and the remote UE through the PC5 interface. One or more messages associated with the service request procedure are forwarded to the eNodeB to establish an EPS bearer for the remote UE.

Example 15 is a device (including or omitting components) that includes the patent subjects of Examples 10 to 14, wherein the processing circuit is grouped based on the paired paging association between the remote UE and the relay UE. Before detecting the connection request message, detect the paging message associated with the remote UE from the eNodeB for subsequent transmission to the remote UE.

Example 16 is a device (including or omitting components) that includes the patent subjects of Examples 10 to 15, wherein the processing circuit is further configured to transmit the paging message to the remote UE through the PC5 interface from the remote The end 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 a device (including or omitting components) that includes the patent subjects of Examples 10 to 16, wherein the processing circuit is further configured to establish the paired paging between the remote UE and the relay UE to generate Then send a paired paging instruction message to the eNodeB to notify the The eNodeB relates to the paired paging, wherein the paired paging instruction message includes the paired paging instruction between the remote UE and the relay UE, the relay UE ID, the paired association ID, and the sending of the paired paging instruction. The UE for the paging indication message is an indication of the relay UE or the remote UE.

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

Example 19 is a device (including or omitting components) that includes the patent subjects of Examples 10 to 18, wherein the paging message associated with the remote UE is generated by the processing circuit using periodic discovery notification messages for use Provided to the remote UE.

Example 20 is a device (including or omitting components) that includes the patented subject matter of Examples 10 to 19, wherein the paging message associated with the remote UE uses the pre-configuration structure that the remote UE is monitoring through the processing circuit One or more discovery resource elements of the resource type are generated for provision to the remote UE.

Example 21 is a device (including or omitting components) that includes the patent subjects of Examples 10 to 20, wherein the paging message associated with the remote UE is defined for transmitting downlink paging through the use of the processing circuit The side link paging control channel of the PC5 interface of information and system information is generated for providing to the remote UE.

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

Example 23 is a device used in the eNodeB of the ProSe network, including: a memory circuit, which is configured to store the relay user equipment (UE) ID associated with the relay UE and the distance of the remote UE End UE ID; processing circuit, which is composed of the air interface between the eNodeB and the remote UE or through the relay UE and will receive from the mobile management entity (MME) associated with it and the remote 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, detect the side link UE information message from the relay UE, where the side link UE information message indicates that it is 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 that it is between the remote UE and the relay UE When the direct connection is established, the Evolved Packet System (EPS) bearer of the remote UE or the EPS bearer of the relay UE is used and the sum received from the S-gateway (S-GW) associated with it is used. The DL data associated with the remote UE is provided to the relay UE for subsequent transmission to the remote UE.

Example 24 is a device that includes the patent subject of Example 23, wherein, before forwarding the DL data, the processing circuit is further configured to detect one or more messages associated with the service request process in order to establish use in the network The EPS bearer of the remote UE on the L2 relay, wherein the one or The multiple messages include the EPS bearer ID associated with the remote UE.

Example 25 is a device (including or omitting components) that includes the patented subject matter of Examples 23 to 24. After detecting the UE information message of the side link, the processing circuit is further configured to generate the S1 application protocol (S1-AP ) Message for using the sending circuit and then sending it to the associated MME, 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 As a result, the MME can use the EPS bearer of the remote UE during the L2 relay or use the EPS bearer of the relay UE during the L3 relay to transfer DL data from the S-GW.

Example 26 is a device (including or omitting components) that includes the patented subject matter of Examples 23 to 25, wherein the processing circuit is configured to pass through the relay based on the paired paging association between the relay UE and the remote UE The UE provides the paging message to the remote UE.

Example 27 is a device (including or omitting components) that includes the patent subjects of Examples 23 to 26, wherein the processing circuit is further configured to detect from the relay UE before the paging message is provided to the remote UE Or a paired paging instruction message of the remote UE, where the paired paging instruction message includes an instruction to establish or release a paired paging between the remote UE and the relay UE, based on sending the paired paging instruction The relay UE ID of the UE or the remote UE ID of the message, the paired association ID, and the UE sending the paired paging indication message is an indication of the relay UE or the remote UE.

Example 28 is a device (including the patented subject matter of Examples 23-27) (Including or omitting components), wherein the processing circuit is configured to provide the paging message of both the relay UE and the remote UE in the paging occasion of the relay UE, wherein the paging occasion of the relay UE It is determined based on the relay UE ID.

Example 29 is a device (including or omitting components) including the patent subjects 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, wherein, The paging occasion of the remote UE is determined based on the remote UE ID.

Example 30 is a device (including or omitting components) that includes the patent subjects of Examples 23 to 29, 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 message indicates the release of the direct connection between the remote UE and the relay UE, the processing circuit is configured to buffer the DL data to be forwarded to the remote UE .

Various illustrative logics, logic blocks, modules, and circuits described in combination with the aspects disclosed in this article can be designed as general-purpose processors and digital signal processors that implement the functions described in this article ( DSP), dedicated integrated circuit (ASIC), field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic, discrete hardware components or any combination thereof to implement or implement. The 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 illustrated embodiment of the disclosure of the patent subject is contained in the abstract The content described in the summary is not intended to be exhaustive or to limit the disclosed embodiments to the precise form disclosed. Although specific embodiments and examples are described herein for illustrative purposes, as those skilled in the related art can understand, various modifications are possible, which are considered to be within the scope of such embodiments and examples Inside.

In this regard, although the disclosed patent subject matter has been described in conjunction with various embodiments and corresponding drawings, it should be understood that other similar embodiments can be used or the described implementation can be implemented where applicable The examples are modified and added without departing from them to perform the same, similar, substitute or replacement functions of the disclosed patent subject matter. Therefore, the disclosed patent subject matter should not be limited to any single embodiment described in this document, but should be interpreted in a broad sense and scope in accordance with the scope of the patent application appended below.

In detail, with regard to the various functions performed by the components or structures described above (components, devices, circuits, systems, etc.), terms (including references to "devices") are used to describe such components, Unless otherwise stated, it is intended to correspond to any component or structure that performs a specific function of the described component (for example, it is functionally equivalent), even if it is not structurally equivalent to performing the specific function depicted in this document The disclosed structure of the function in the exemplary embodiment of the present invention. In addition, although a specific feature may be disclosed for only one of several embodiments, such a feature may be combined with one or more other features of other embodiments because it may be relevant for any given or specific application. Desired and advantageous.

100‧‧‧Proximity Service (ProSe) System

150‧‧‧PC5 interface

160‧‧‧Old Uu interface

180‧‧‧S1 interface

Claims (25)

A device used in a remote user equipment (UE) of a ProSe network including a relay UE and an evolved node B (eNodeB) associated with it. The device includes a processing circuit that executes data from a memory circuit After the command, it is grouped and constituted: through the air interface between the eNodeB and the remote UE or through the relay UE through the PC5 interface between the relay UE and the remote UE, receive from the eNodeB including the The paging message of the remote UE ID of the remote UE, where the paging message informs the remote UE about the availability of downlink (DL) data for the remote UE; The reason value of the paging for the connection request message sent to 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 sending the connection request message, receiving the downlink data signal including the DL data from the eNodeB via the relay UE through the PC5 interface. For example, the device of claim 1, wherein, after the direct connection between the remote UE and the relay UE is established, the processing circuit is further configured to initiate a service request procedure to establish via the relay UE The Evolved Packet System (EPS) of the remote UE is carried in the network. For example, the device of the second item of the patent application, in which the activation of the service request procedure includes the provision of one or more messages associated with the service request procedure to the relay UE through the PC5 interface, wherein the one or more The message is then obviously forwarded to the eNodeB by the relay UE. For example, the device of claim 2, wherein the EPS bearer of the remote UE is used to receive the downlink data signal during L2 relay, and the EPS of the relay UE is used during L3 relay Bearer to receive the downlink data signal. For example, 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, wherein the The PC5 direct communication request message includes the remote UE ID and a paired paging request to establish a paired paging between the remote UE and the relay UE. For example, the device of item 5 of the scope of patent application, wherein the processing circuit is further configured to generate a paired paging instruction for subsequent transmission to the eNodeB after the paired paging is established between the remote UE and the relay UE Message, wherein the paired paging indication message includes an indication of the paired paging between the remote UE and the relay UE, the remote UE ID, and an indication of the paired association between the remote UE and the relay UE The paired association ID of and the UE sending the paired paging indication message is an indication of the relay UE or the remote UE. A device used in a relay user equipment (UE) of a ProSe network including a remote UE and its associated evolved node B (eNodeB), including: a memory circuit, which is assembled to store and store the relay UE The associated relay UE ID, the remote UE ID of the remote UE, and the paired association ID indicating the paired association between the relay UE and the remote UE; the processing circuit is composed of: A connection request message including a paging cause value is received from the remote UE through the PC5 interface between the remote UE and the relay UE, wherein the paging cause value indicates the reception of a paging message, and the paging message is The remote UE indicates the availability of downlink (DL) data from the eNodeB at the remote UE through the air interface or via the relay UE; after receiving the connection request message, the relay UE and the remote A direct connection is established between the end UE; and after the direct connection between the relay UE and the remote UE is established, the remote UE or the evolved packet system (EPS) bearer of the relay UE is used to communicate with The S-Gateway (S-GW) associated with the eNodeB receives the downlink data signal including the DL data for subsequent transmission to the remote UE through the PC5 interface. For example, the device of claim 7 in which, before receiving the downlink data signal, the processing circuit is further configured to generate a side link UE information message including the remote UE ID of the remote UE, so as to For subsequent transmission to the eNodeB, where the side link UE information message provides an indication of the reception 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 . For example, the device of item 7 of the scope of patent application, 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 EPS bearer in order to receive the downlink data signal during the L2 relay. For example, the device of item 9 of the scope of patent application, in which the EPS bearer of the remote UE is borrowed It is established by performing service request procedures 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. For example, the device of the seventh item of the scope of patent application, wherein, before receiving the connection request message from the remote UE, the processing circuit is grouped and configured based on the paired paging association between the remote UE and the relay UE, and the eNodeB The paging message associated with the remote UE is received for subsequent transmission to the remote UE. For example, the device of claim 11, in which, before sending the paging message to the remote UE, the processing circuit is further configured to receive the PC5 direct communication request message from the remote UE through the PC5 interface, wherein, The PC5 direct communication request message includes the remote UE ID and a paired paging request to establish the paired paging between the remote UE and the relay UE. For example, the device of item 12 of the scope of patent application, wherein the processing circuit is further configured to generate the paired paging for subsequent transmission to the eNodeB after the paired paging is established between the remote UE and the relay UE Instruction message to notify the eNodeB of the paired paging, wherein the paired paging instruction message includes the instruction of the paired paging between the remote UE and the relay UE, the relay UE ID, and the eNodeB. The indication to the associated ID and the UE sending the paired paging instruction message is the relay UE or the remote UE. For example, the device of claim 11, wherein the paging message associated with the remote UE is sent from the eNodeB at the processing circuit based on monitoring the paging timing of the remote UE or the paging timing of the relay UE Was received. For example, the device of claim 11, wherein the paging message associated with the remote UE is sent from the processing circuit to the remote UE using a periodic discovery notification message. For example, the device of claim 11, wherein the paging message associated with the remote UE uses one or more discovery resource elements of the pre-configured resource type being monitored by the remote UE. The processing circuit is sent to the remote UE. For example, the device of claim 11, wherein the paging message associated with the remote UE uses a side link paging control channel through the PC5 interface that is defined to transmit downlink paging information and system information. It is sent from the processing circuit to the remote UE. For example, the device of item 7 of the scope of patent application, wherein, after the direct connection between the remote UE and the relay UE is released, the processing circuit is further configured to buffer the DL data for a predetermined period of time . A device used in an eNodeB in a ProSe network including a remote user equipment (UE) and a relay UE associated with it, including: a memory circuit, which is configured to store the relay associated with the relay UE UE ID and the remote UE ID of the remote UE; a processing circuit, which is composed of: through the air interface between the eNodeB and the remote UE or through the relay UE through the relay UE and the remote UE PC5 interface between the end UEs and then send to the remote The end UE provides the paging message associated with the remote UE received from the MME associated with the remote UE to the remote UE, wherein the paging message indication is used for the remote UE downlink ( DL) Availability of data; receiving a side link UE information message including the remote UE ID of the remote UE from the relay UE, wherein, in response to providing the paging message, the side link UE information message indicates that The reception 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; and when the side link UE information message indicates that the remote UE and the When the direct connection between the relay UE is established, the Evolved Packet System (EPS) bearer of the remote UE or the EPS bearer of the relay UE will be used from the S-gateway associated with the remote UE. (S-GW) The received DL data associated with the remote UE is provided to the relay UE for subsequent transmission to the remote UE. For example, the device of item 19 of the scope of patent application, wherein, before forwarding the DL data, the processing circuit is further configured to receive one or more messages associated with the service request process so as to be established for the L2 relay in the network The EPS bearer of the remote UE, wherein the one or more messages include an EPS bearer ID associated with the remote UE. For example, the device of item 20 of the scope of patent application, 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 the associated MME, wherein the The S1-AP message includes the remote UE ID and the EPS bearer ID of the remote UE or the relay UE, so as to cause the MME to use the EPS bearer of the remote UE during L2 relay or during L3 relay The EPS bearer using the relay UE is forwarded from the S-GW DL information. For example, the device of claim 19, wherein the processing circuit is configured to provide the paging message to the remote UE through the relay UE based on the paired paging association between the relay UE and the remote UE . For example, the device of claim 22, wherein the processing circuit is configured to provide the paging message of both the relay UE and the remote UE in the paging occasion of the relay UE, wherein the relay UE The paging timing is determined based on the relay UE ID. For example, the device of claim 22, wherein the processing circuit is configured to provide the paging message of the remote UE in the paging timing of the remote UE, wherein the paging timing of the remote UE is based on the paging timing of the remote UE. The remote UE ID is used to determine. For example, 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 the release of the direct connection between the remote UE and the relay UE, the processing circuit is configured to buffer the DL data to be forwarded to the remote UE.

Images