Source: https://patents.google.com/patent/US9591679B2/en
Timestamp: 2019-12-15 18:10:36
Document Index: 391297209

Matched Legal Cases: ['Application No. 13707754', 'Application No. 13707748', 'Application No. 10', 'Application No. 102132482', 'Application No. 102132487', 'Application No. 201380060975', 'Application No. 10', 'Application No. 10', 'Application No. 201380060975', 'Application No. 10', 'Application No. 10']

US9591679B2 - Initiation of inter-device communication in wireless communication systems - Google Patents
Initiation of inter-device communication in wireless communication systems Download PDF
US9591679B2
US9591679B2 US13/621,703 US201213621703A US9591679B2 US 9591679 B2 US9591679 B2 US 9591679B2 US 201213621703 A US201213621703 A US 201213621703A US 9591679 B2 US9591679 B2 US 9591679B2
US13/621,703
US20140078952A1 (en
2012-09-17 Priority to US13/621,703 priority Critical patent/US9591679B2/en
2014-03-20 Publication of US20140078952A1 publication Critical patent/US20140078952A1/en
2017-03-07 Publication of US9591679B2 publication Critical patent/US9591679B2/en
Systems, methods, and apparatuses for initiation of inter-device communication in wireless communication systems are provided. Both a user equipment (UE) and a network entity may initiate a direct inter-device communication link between UEs located in proximity. The UE may simultaneously maintain an active communication link with its serving base station while communicating with other UEs over the inter-device communication link. Long term evolution (LTE) downlink or uplink radio resources may be used for communications over the inter-device communication link.
The present disclosure generally relates to communications in wireless communication systems, and more particularly, to initiation of inter-device communications in wireless communication systems.
FIG. 5 illustrates a flow diagram of another example method for initiating an inter-device communication link consistent with the present disclosure.
FIG. 1 illustrates an example cellular wireless communication system 100 in which systems and methods consistent with this disclosure may be implemented. The cellular network system 100 shown in FIG. 1 includes one or more base stations (i.e., 112 a and 112 b). In the LTE example of FIG. 1, the base stations are shown as evolved Node Bs (eNBs) 112 a and 112 b, although base stations operate in any wireless communications system, including for example, macro cell, femto cell, relay cell, and pico cell. Base stations are nodes that can relay signals for mobile devices, also referred to herein a user equipment, or other base stations. The base stations are also referred to as access node devices. The example LTE telecommunications environment 100 of FIG. 1 includes one or more radio access networks 110, core networks (CNs) 120, and external networks 130. In certain implementations, the radio access networks may be Evolved Universal Terrestrial Radio Access Networks (EUTRANs). In addition, core networks 120 may be evolved packet cores (EPCs). Further, as shown one or more mobile electronic devices 102 a, 102 b operate within the LTE system 100. In some implementations, 2G/3G systems 140, e.g., Global System for Mobile communication (GSM), Interim Standard 95 (IS-95), Universal Mobile Telecommunications System (UMTS) and Code Division Multiple Access (CDMA2000) may also be integrated into the LTE telecommunication system 100.
In the example LTE system shown in FIG. 1, the EUTRAN 110 includes eNB 112 a and eNB 112 b. Cell 114 a is the service area of eNB 112 a and Cell 114 b is the service area of eNB 112 b. User equipment (UEs) 102 a and 102 b operate in Cell 114 a and are served by eNB 112 a. The EUTRAN 110 can include one or more eNBs (e.g., eNB 112 a and eNB 112 b) and one or more UEs (e.g., UE 102 a and UE 102 b) can operate in a cell. The eNBs 112 a and 112 b communicate directly to the UEs 102 a and 102 b. In some implementations, the eNB 112 a or 112 b may be in a one-to-many relationship with the UEs 102 a and 102 b, e.g., eNB 112 a in the example LTE system 100 can serve multiple UEs (i.e., UE 102 a and UE 102 b) within its coverage area Cell 114 a, but each of UE 102 a and UE 102 b may be connected to one serving eNB 112 a at a time. In some implementations, the eNBs 112 a and 112 b may be in a many-to-many relationship with the UEs, e.g., UE 102 a and UE 102 b can be connected to eNB 112 a and eNB 112 b. The eNB 112 a may be connected to eNB 112 b such that handover may be conducted if one or both of the UEs 102 a and 102 b travels, e.g. from cell 114 a to cell 114 b. The UEs 102 a and 102 b may be any wireless electronic device used by an end-user to communicate, for example, within the LTE system 100.
The D2D Link Establishment Request message may include specific information for the direct communication link, for example, bandwidth requirements, data rate information, quality of service (QoS) information, time duration, etc., for the direct inter-device communication link. The NAS message may also include information of the other UE involved in the direct inter-device communication link. For example, the NAS message may include the UE identification (ID) information of the other UE, i.e., UE1, in the illustrated example. UE0 may obtain UE1's identity by, for example, scanning an ID bar code, which includes UE1's phone number or other identities. UE0 may also obtain UE1's identity by other alternatives, such as Email, Text, Near Field Communication (NFC), etc. UE0 and UE1 may also form a group and information regarding UEs in the group may be stored at the UEs. Hence when UE0 and UE1are in close proximity to one another, the ID information of UE0 and UE1 can be obtained to initiate the inter-device communication. The group may include more than 2 users. For example, an interactive group may consist of 10 or more users. The number of users in the group can be pre-determined by the network. The upper limit on the group size could be pre-set, for example, in the standards or by the operators. The group member information can be updated when there is a change to the group membership, such as the addition or deletion of a group member, or a change in the information associated with one or more members. The group and/or information regarding the group may be maintained on the application layer.
On the other hand, if the HSS responds positively to the MME at 406, indicating an acceptance of the UE0's request for a direct communication link with UE1, the MME may subsequently send a D2D Initialization Request message to UE0's serving eNB at 408 for enabling the direct communication link between UE0 and UE1. The communication interface between the MME and the eNB is referred to as an S1 interface. The MME may include the QoS requirements of the direct communication link between UE0 and UE1 in the D2D Initialization Request message. The eNB may check the QoS requirements of the requested inter-device link and available radio resources at the eNB. The eNB may then determine whether the direct communication link between UE0 and UE1 can be enabled based on the QoS requirements and the available radio resources. Correspondingly, the eNB may send a D2D Initialization Request Acknowledgement message to the MME via the S1 application protocol (AP) at 410, including a positive or negative acknowledgement. The eNB may include reasons for rejecting the D2D initialization request in the D2D Initialization Request Acknowledgement message when a negative acknowledgement is sent to the MME.
Upon successful completion of the device handshake procedure, the eNB may send a D2D Initialization Response message to the MME at 420, indicating a completion of the device handshake procedure. UE0 and UE1 may also send a D2D Link Establishment Acknowledgement message to the MME at 422 and 424, respectively, indicating a successful completion of the device handshake procedure. Consequently, the MME may communicate the QoS requirements of the direct inter-device link to the serving gateway (S-GW) at 426. The serving gateway may then forward this QoS information to the policy and charging rules function (PCRF) for charging the UEs at 428. In some implementation, the MME may communicate the QoS requirements of the direct inter-device link to the PCRF via the S-GW at an earlier time, for example, subsequent to receiving the positive acknowledgment from the eNB at 410.
In certain instances, the resources assigned by the eNB may be time limited and this time limitation may be set based on the requested application or the UE's request for specific bandwidth for the direct inter-device communication link. The UE may extend this time limit by, for example, sending another request or a NAS update request to the MME for extension. Similarly the UE may want to request modification to the QoS or want to add a new UE to the ongoing inter-device communication. The MME may send a NAS update response message to the UE subsequently. The UE may send the NAS update request message to the MME for extension of the time duration of the inter-device communication, modification to quality of service, addition of one or more other UEs to the inter-device communication link, or other updates related to the inter-device communication link.
If the UE wishes to terminate the inter-device communication at an earlier time before the time limit, the UE may send a message to the MME and subsequently the MME can instruct the eNB to stop the radio resource assignment to the UE for the inter-device communication. In some implementations, the UE may receive an indication that the inter-device communication link is to be terminated. The indication may be received from a user interface, from the network, or from a physical layer of the UE. After the inter-device link is terminated, MME/SGW may send a report to the PCRF, reporting the amount of data transmitted on the direct inter-device link, the actual duration of the communication over the direct inter-device link, etc for charging purpose.
The method described above in connection with FIG. 4 is a UE initiating an inter-device communication method, in which a UE identifies an opportunity for direct inter-device communication and requests the network to set up the inter-device communication. In some scenarios, the network may also identify the feasibility of direct inter-device communication and initiate the inter-device communication link.
FIG. 5 illustrates a flow diagram 500 a of an example method for initiating an inter-device communication link consistent with the present disclosure. As shown in FIG. 5, the MME performs inter-device communication decision making at 502 a. At 502 a, the MME may determine feasibility of the inter-device communication link between the UEs. For example, the MME may make decisions of setting up a direct inter-device communication link based on the UEs' geographical locations. The UEs may report their geographical locations to the network periodically when the UEs are equipped with certain navigation systems, such as global positioning system (GPS). In some implementations, the network may obtain knowledge of the UEs' location based on measurement reports sent from the UEs and geographical locations of the corresponding base stations.
In some other implementations, the base station may determine the UEs' locations based on pre-set configurations via operation and maintenance (O&M) for certain groups of UEs and then report this location information to the EPC. A location update report may be sent periodically, or may be triggered by one or more events to provide updated location information to the network. The events may be related to the rate of the UE changing its location, e.g., related to the physical speed of the UE. Furthermore, the location update report can be serving cell specific, i.e., based on the specific serving base station, or can be specific to one or more UEs.
Based on the location information available at the MME, if an incoming call or connection request identifies UEs that are close by, the network may initiate an inter-device communication link. Specifically, if an incoming call or connection request identifies one or more UEs with which the requesting UE can effectively communicate directly, as opposed to, or in addition to, going through the network, the network may initiate an inter-device communication link. For example, if an incoming call or connection request identifies UEs that are located near the requesting UE, the network may initiate an inter-device communication link. In FIG. 5, S1-AP represents S1 Application Protocol, which is used on the control plane between the eNB and the MME. MME may also contact HSS to determine whether the device is authorized to take part in an inter-device communication. The device authorization may be location dependent. If the MME decides to initiate an inter-device communication link at 502 a, the MME may send a D2D Discovery Initialization Request message to the UEs' serving eNB at 504 a, requesting the eNB to initiate a device discovery procedure. The device discovery procedure is to confirm whether the UEs can indeed communicate with each other over a direct inter-device communication link.
After receiving the D2D Discovery Initiation Request message from the MME, the eNB may subsequently send a D2D Discovery Initiation Request Acknowledgement message to the MME at 506 a. The D2D Discovery Initiation Request Acknowledgement message may be used to confirm whether a device discovery procedure will be conducted by the eNB.
If the eNB confirms to conduct a device discovery procedure at 506 a, the eNB may initiate the device discovery procedure by sending an RRC D2D Discovery Setup message to UE0 at 508 a. This message may include one or more of the following parameters: cell radio network temporary identities (C-RNTIs) of the UEs participating in the inter-device communication; temporary transmit point IDs for each UE participating in the inter-device communication; minimum and/or maximum transmit power levels for transmitting over the direct inter-device communication link; a DD-RNTI which is used to identify the direct inter-device communication link; a transmit power step for transmissions over the direct link; and a guard time for the direct communication link.
After receiving the D2D Discovery Setup message from the eNB, UE0 may send a D2D Discovery Setup Response message to the eNB at 510 a. The message may indicate a successful reception of the D2D Discovery Setup message. Additionally, or alternatively, the eNB may send an RRC D2D Discovery Setup message to UE1 which may include similar information such as DD-RNTI. Subsequent to receiving the D2D Discovery Setup message from the eNB, UE1 may also send a D2D Discovery Setup Response message to the eNB, indicating a successful reception of the D2D Discovery Setup message. After receiving the D2D Discovery Setup Response message from UE0 and/or UE1, the eNB may initiate a device discovery procedure with UE0 and UE1 at 512 a. On the other hand, if the eNB does not receive the D2D Discovery Setup Response message from UE0 or UE1 over a predetermined time period, the eNB may resend the D2D Discovery Setup message to UE0 or UE1. After resending the D2D Discovery Setup message a number of times, the eNB may abandon the direct link discovery procedure for the link between UE0 and UE1 and indicate a failure of the device discovery in the D2D Discovery Initialization Response message to the MME with clause set as “UEs not responding”. Transmission of a D2D Discovery Initialization Response message is shown in FIG. 5 at 514 a. The number of times for resending the D2D Discovery Setup message may be predetermined or configurable by the eNB.
Upon a successful discovery, the eNB may send a D2D Discovery Initialization Response message to the MME at 514 a. The message may indicate a successful discovery of the UEs that may communicate over a direct inter-device communication link. If the device discovery procedure is failed, the eNB may indicate a failure of the device discovery in the D2D Discovery Initialization Response message to the MME.
Subsequent to receiving the D2D Discovery Initialization Response message from the eNB, the MME may send a D2D Discovery Initialization Response Acknowledgement message to the eNB at 516 a, confirming a successful reception of the D2D Discovery Initialization Response message. If the D2D Discovery Initialization Response message indicates a successful device discovery, the MME may send a NAS D2D Link Establishment Setup message to UE0 at 518 a. After receiving the D2D Link Establishment Setup message from the MME, UE0 may send a D2D Link Establishment Setup Response message to the MME at 520 a, confirming that the D2D Link Establishment Setup message is received at the UE. Subsequent signaling procedures to enable the direct inter-device communication link may be similar to the procedure described previously in connection with FIG. 4.
After receiving the D2D Link Establishment Setup Response message from UE0, the MME may send a D2D Link Establishment Request message to the HSS at 522 a. The MME may also include information describing the UE in the D2D Link Establishment Request message sent to the HSS at 522 a.
After receiving the message from the MME, the HSS may check the QoS requirements of the inter-device communication link and send a D2D Link Establishment Response message to the MME at 524 a. If the HSS responds positively to the MME at 524 a, the MME may subsequently send a D2D Initialization Request message to the eNB at 526 a for enabling the direct communication link between UE0 and UE1. The MME may include the QoS requirements of the direct communication link between UE0 and UE1 in the D2D Initialization Request message. The eNB may check the QoS requirements of the requested inter-device link and available radio resources at the eNB. The eNB may determine whether a direct communication link between UE0 and UE1 can be enabled based on the QoS requirements and the available radio resources. Correspondingly, the eNB may send a D2D Initialization Request Acknowledgement message to the MME via the S1 AP at 528 a, including a positive or negative acknowledgement. The eNB may include reasons for rejecting the D2D initialization request in the D2D Initialization Request Acknowledgement message when a negative acknowledgement is sent to the MME.
When the eNB determines that the direct communication link between UE0 and UE1 may be enabled, the eNB may send an RRC D2D Connection Setup message to UE0 at 534 a. The D2D Connection Setup message may include one or more transmission parameters for the direct communication link, such as a C-RNTI of UE1, temporary transmit point identifications for each UE communicating over the inter-device communication link, minimum and/or maximum transmit power levels for transmitting over the inter-device communication link, a DD-RNTI for identifying the direct inter-device link, a transmit power step for the direct inter-device link, a guard time for the direct inter-device link, etc.
Subsequent to receiving the D2D Connection Setup message from the eNB, UE0 may send a D2D Connection Setup Response message to the eNB at 536 a, indicating a successful reception of the D2D Connection Setup message. In another example, the eNB may also send a radio resource control (RRC) message D2D Connection Setup to UE1 as well which includes the similar information such as DD-RNTI. Subsequent to receiving the D2D Connection Setup message from the eNB, UE1 may also send a D2D Connection Setup Response message to the eNB, indicating a successful reception of the D2D Connection Setup message. After receiving the D2D Connection Setup Response message from UE0 and/or UE1, the eNB may initiate a device handshake procedure with UE0 and UE1 at 538 a. During this procedure, the UEs may identify each other and initiate link parameter tuning such that a reliable communication link can be established between the UEs. In some implementations, the device handshake procedure may be omitted when the direct inter-device communication is initiated by the network and a device discovery procedure has been conducted. It may be possible to omit the device handshake procedure in certain scenarios because the UE may have already identified each other and performed link parameter tuning during the device discovery procedure at 512 a.
On the other hand, if the eNB does not receive the D2D Connection Setup Response message from UE0 or UE1 within a predetermined time period, the eNB may resend the D2D Connection Setup message to UE0 or UE1. After resending the D2D Connection Setup a predetermined number of times, the eNB may abandon the direct link setup procedure for the link between UE0 and UE1 and send a D2D Initialization Response message to the MME, indicating a failure to contact UE0 or UE1. The predetermined number could be pre-set, e.g., by the operators. A prohibit timer could also be used to regulate the transmission of the D2D Connection Setup messages. Basically, after the eNB sends out the D2D Connection Setup message, the eNB cannot send another D2D Connection Setup message until the prohibit timer is expired.
Upon successful completion of the device handshake procedure, the eNB may send a D2D Initialization Response message to the MME at 540 a, indicating a completion of the device handshake procedure. UE0 and UE1 may also send a D2D Link Establishment Acknowledgement message to the MME at 542 a and 544 a, respectively, indicating a successful completion of the device handshake procedure. Consequently, the MME may communicate the QoS requirements of the direct inter-device link to the serving gateway (S-GW) at 530. The serving gateway may then forward this QoS information to the Policy and Charging Rules Function (PCRF) for charging or billing the UEs at 532 a. In some implementations, the MME may communicate the QoS requirements of the direct inter-device link to the PCRF via the S-GW at an earlier time, for example, subsequent to receiving the positive acknowledgment from the eNB at 528 a. The network assisted inter-device communication between UE0 and UE1 may then be conducted over the direct inter-device communication link at 546 a. LTE downlink or uplink resources may be used for the inter-device communications between the UEs.
The resources assigned by the eNB may be time limited, as explained above, and this time limit may be set based on a requested application or a UE's request for specific bandwidth for the direct inter-device link. The UE may extend this time limit by, for example, sending another request or a NAS update request to the MME for extension. The MME may send a NAS update response message to the UE subsequently. The UE may send the NAS update request message to the MME for extension of the time duration of the inter-device communication, modification to quality of service, addition of one or more other UEs to the inter-device communication link, or other updates related to the inter-device communication link. If the UE wishes to terminate the inter-device communication at an earlier time before the time limit, the UE may send a message to the MME and subsequently the MME can instruct the eNB to stop the radio resource assignment to the UE for the inter-device communication. In some implementations, the UE may receive an indication that the inter-device communication link is to be terminated. The indication may be received from a user interface, from the network, or from a physical layer of the UE. After the inter-device link is terminated, MME/SGW may send a report to the PCRF, reporting link related information or statistics, such as the amount of data transmitted on the direct inter-device link, the actual duration of the communication over the direct inter-device link, etc for charging purpose.
While several implementations have been provided in the present disclosure, it should be understood that the disclosed systems and methods may be implemented in many other specific forms without departing from the scope of the present disclosure. The present examples are to be considered as illustrative and not restrictive, and the intention is not to be limited to the details given herein. For example, the various elements or components may be combined or integrated in another system or certain features may be omitted, or not implemented. Methods may be practiced with steps performed in an order that may differ from that presented herein.
sending, at the UE, a non-access stratum (NAS) request message to a network entity that initiates an inter-device communication link, wherein the network entity is a mobility management entity (MME);
receiving, at the UE and from the MME, a NAS response message associated with inter-device communication between two or more UEs, wherein the NAS response message includes at least one of an acceptance or a rejection of the NAS request message;
receiving a radio resource control (RRC) inter-device connection setup message from a base station, wherein the RRC inter-device connection setup message indicates at least two cell radio network temporary identities (C-RNTIs), and each of the at least two C-RNTIs correspond to a different UE of the two or more UEs; and
2. The method of claim 1, wherein the RRC inter-device connection setup message includes at least one of:
temporary transmit point identifications for the two or more UEs;
minimum and maximum transmit power levels for the two or more UEs communicating over the inter-device communication link;
a transmit power incremental value for the two or more UEs communicating over the inter-device communication link; or
performing a device handshake procedure; and
sending a NAS message to the network entity for acknowledging an establishment of the inter-device communication link.
4. The method of claim 1, wherein the NAS request message includes at least one of:
identifications of at least one of the two or more UEs;
a bandwidth requirement for the inter-device communication link;
data rate information for the inter-device communication link;
quality of service information for the inter-device communication link; or
a time duration of the inter-device communication link.
5. The method of claim 1, wherein a signal to interference plus noise ratio (SINR) of the inter-device communication link is higher than at least one of SINRs of links between the two or more UEs and their respective serving base stations.
6. The method of claim 1, wherein the two or more UEs communicate over the inter-device communication link using long term evolution (LTE) downlink resources.
7. The method of claim 1, wherein the two or more UEs communicate over the inter-device communication link using long term evolution (LTE) uplink resources.
8. The method of claim 1, wherein the two or more UEs maintain communication links with their respective serving base stations while communicating over the inter-device communication link.
sending, at the UE, a NAS update request message to the network entity for modifying or extending a time duration of the inter-device communication link; and
receiving, at the UE, a NAS update response message associated with the inter-device communication from the network entity.
10. The method of claim 9, wherein the UE sends the NAS update request message to the network entity upon an occurrence of one or more of the following:
extension of the time duration of the inter-device communication;
modification to quality of service; or
addition of one or more UEs to the inter-device communication.
receiving an initialization request message from a network entity for enabling at least one inter-device communication link for at least two user equipments (UEs), wherein the network entity is a mobility management entity (MME);
determining that the at least one inter-device communication link can be enabled;
sending, an initialization request acknowledgement message to the network entity, indicating that the at least one inter-device communication link can be enabled;
sending, in response to the initialization request message and the determination that the at least one inter-device communication link can be enabled, a radio resource control (RRC) inter-device connection setup message to one of the at least two UEs, wherein the RRC inter-device connection setup message indicates at least two cell radio network temporary identities (C-RNTIs), and each of the at least two C-RNTIs correspond to a different UE of the at least two UEs; and
receiving, in response to the radio resource control (RRC) inter-device connection setup message, a RRC connection setup response message from the one of the at least two UEs.
12. The method of claim 11, wherein the RRC inter-device connection setup message includes at least one of:
temporary transmit point identifications for the at least two UEs;
minimum and maximum transmit power levels for the at least two UEs;
a transmit power incremental value for the at least two UEs communicating over the at least one inter-device communication link; or
initiating a device handshake procedure with the at least two UEs; and
sending an initialization response message to the network entity for acknowledging an establishment of the at least one inter-device communication link for the at least two UEs.
14. The method of claim 11, wherein a signal to interference plus noise ratio (SINR) of the at least one inter-device communication link is higher than one or more SINRs of links between the at least two UEs and the base station.
15. The method of claim 11, wherein the at least one inter-device communication link uses long term evolution (LTE) downlink resources.
16. The method of claim 11, wherein the at least one inter-device communication link uses long term evolution (LTE) uplink resources.
sending a radio resource control (RRC) inter-device connection setup message to one of the at least two UEs;
determining that a RRC inter-device connection setup response message from the one of the at least two UEs is not received during a predetermined time period; and
resending the radio resource control (RRC) inter-device connection setup message to the one of the at least two UEs.
18. The method of claim 11, wherein the base station determines whether the at least one inter-device communication link can be enabled based on available radio resources at the base station when receiving the initialization request message.
a transmitter that sends, at the UE, a non-access stratum (NAS) request message to a network entity that initiates an inter-device communication link, wherein the network entity is a mobility management entity (MME); and
a receiver that receives, at the UE and from the MME, a NAS response message associated with inter-device communication between two or more UEs, wherein the NAS response message includes at least one of an acceptance or a rejection of the NAS request message that initiates the inter-device communication link,
wherein the receiver receives a radio resource control (RRC) inter-device connection setup message from a base station, the RRC inter-device connection setup message indicates at least two cell radio network temporary identities (C-RNTIs), and each of the at least two C-RNTIs correspond to a different UE of the two or more UEs, and
the transmitter sends a RRC inter-device connection setup response message to the base station.
20. The UE of claim 19, wherein the two or more UEs communicate over the inter-device communication link using long term evolution (LTE) uplink resources.
21. The UE of claim 19, wherein the two or more UEs maintain communication links with their respective serving base stations while communicating over the inter-device communication link.
a receiver that receives an initialization request message from a network entity for enabling at least one inter-device communication link for at least two user equipments (UEs), wherein the network entity is a mobility management entity (MME);
one or more processors configured to determine that the at least one inter-device communication link can be enabled;
a transmitter that sends an initialization request acknowledgement message to the network entity, indicating that the at least one inter-device communication link can be enabled, the transmitter sending, in response to the initialization request message and the determination that the at least one inter-device communication link can be enabled, a radio resource control (RRC) inter-device connection setup message to one of the at least two UEs, wherein the RRC inter-device connection setup message indicates at least two cell radio network temporary identities (C-RNTIs), and each of the at least two C-RNTIs correspond to a different UE of the at least two UEs; and
the receiver receiving, in response to the radio resource control (RRC) inter-device connection setup message, a RRC connection setup response message from the one of the at least two UEs.
23. The base station of claim 22, wherein the at least one inter-device communication link uses long term evolution (LTE) uplink resources.
24. The base station of claim 22, wherein the one of the at least two UEs maintains communication links with the base stations while communicating over the at least one inter-device communication link.
US13/621,703 2012-09-17 2012-09-17 Initiation of inter-device communication in wireless communication systems Active 2033-01-29 US9591679B2 (en)
US13/621,703 US9591679B2 (en) 2012-09-17 2012-09-17 Initiation of inter-device communication in wireless communication systems
EP13707250.0A EP2896264A1 (en) 2012-09-17 2013-02-14 Initiation of inter-device communication in wireless communication systems
PCT/US2013/026104 WO2014042674A1 (en) 2012-09-17 2013-02-14 Initiation of inter-device communication in wireless communication systems
CN201380060173.6A CN104823511B (en) 2012-09-17 2013-02-14 Method and apparatus for the initiation of communication between devices in wireless communication system
KR1020157010012A KR101696126B1 (en) 2012-09-17 2013-02-14 Initiation of inter-device communication in wireless communication systems
TW102132486A TWI508604B (en) 2012-09-17 2013-09-09 Initiation of inter-device communication in wireless communication systems
US20140078952A1 US20140078952A1 (en) 2014-03-20
US9591679B2 true US9591679B2 (en) 2017-03-07
ID=47780202
US13/621,703 Active 2033-01-29 US9591679B2 (en) 2012-09-17 2012-09-17 Initiation of inter-device communication in wireless communication systems
US (1) US9591679B2 (en)
EP (1) EP2896264A1 (en)
KR (1) KR101696126B1 (en)
CN (1) CN104823511B (en)
TW (1) TWI508604B (en)
WO (1) WO2014042674A1 (en)
US10455616B2 (en) 2014-06-05 2019-10-22 Intel IP Corporation Interference management techniques for full-duplex wireless communications
KR20190026432A (en) * 2017-09-05 2019-03-13 삼성전자주식회사 Device and method for performing data communication with slave device
2012-09-17 US US13/621,703 patent/US9591679B2/en active Active
2013-02-14 CN CN201380060173.6A patent/CN104823511B/en active IP Right Grant
2013-02-14 KR KR1020157010012A patent/KR101696126B1/en active IP Right Grant
2013-02-14 EP EP13707250.0A patent/EP2896264A1/en active Pending
2013-02-14 WO PCT/US2013/026104 patent/WO2014042674A1/en active Application Filing
2013-09-09 TW TW102132486A patent/TWI508604B/en active
"Lei Lei et al: "Operator controlled device-to-device communications in LTE-advanced networks", IEEE Wireless Communications, IEEE Service Center, Piscataway, NJ, US, vol. 19, No. 3, Jun. 2012; 9 pages".
Communication Pursuant to Article 94(3) EPC issued in related European Application No. 13707754.1 on Apr. 11, 2016.
Communication Pursuant to Article 94(3) EPC issured in European Application No. 13707748.3 on Oct. 18, 2016.
International Preliminary Report on Patentability in International Application No. PCT/US2013/026356, dated Apr. 30, 2015, 7 pages.
International Search Report for Application No. PCT/US2013/026104, dated Jun. 24, 2013, 13 pages.
Notice of Allowance issued in Korean Application No. 10-2015-7010010 on Jun. 27, 2016.
Office Action and Search Report issued in Taiwanese Application No. 102132482 on Dec. 26, 2014; 9 pages.
Office Action and Search Report issued in Taiwanese Application No. 102132487 on Dec. 26, 2014; 12 pages.
Office Action issued in Chinese Application No. 201380060975.7 on Dec. 5, 2016.
Office Action issued in Korean Application No. 10-2015-7010012 on Sep. 6, 2016.
Office Action issued in Korean Application No. 10-2015-7010443 on May 27, 2016.
Office Action issued in Korean Application No. Oct. 2015-7010443 on Nov. 25, 2016.
Office Action issued in related Chinese Application No. 201380060975.7 on May 5, 2016.
Office Action issued in related Korean Application No. 10-2015-7010012 on Apr. 19, 2016.
Office Action issued in related Korean Application No. 10-2015-7012597 on Mar. 18, 2016.
Office Action issued in U.S. Appl. No. 13/652,011 on Jan. 23, 2015.
KR20150060790A (en) 2015-06-03
EP2896264A1 (en) 2015-07-22
TW201419915A (en) 2014-05-16
CN104823511A (en) 2015-08-05
KR101696126B1 (en) 2017-01-13
CN104823511B (en) 2019-02-19
WO2014042674A1 (en) 2014-03-20
TWI508604B (en) 2015-11-11
US20140078952A1 (en) 2014-03-20
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BONTU, CHANDRA SEKHAR;REEL/FRAME:029346/0391
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:CAI, ZHIJUN;SONG, YI;SIGNING DATES FROM 20121018 TO 20121027;REEL/FRAME:029346/0435