The present disclosure generally relates to communications in wireless communication systems, and more particularly, to transmit power adjustment for inter-device communications in wireless communication systems.
In wireless networks such as Long Term Evolution (LTE) and LTE-Advanced communication networks, a user equipment (UE) may communicate with other UEs via a base station and an evolved packet core (EPC) network. For example, a UE may send data packets to its serving base station on an uplink. The serving base station may forward the data packets to the EPC network and the EPC network may forward the data packet to another base station or to the same base station that is serving another UE. Data transfer between the UEs is routed through the base station and the EPC. The communication between the UEs is controlled by the policies set by the operator administering the network.
The UEs may communicate directly with each other using other radio access technology (RAT), such as, wireless local area network (WLAN) or Bluetooth when the UEs are located in close proximity and have access to the other RAT. However, this multi-RAT communication requires the availability of the other RAT and the capability of the UEs to operate in the other RAT. Moreover, handover from cellular technology to other RATs may result in service interruption and dropped calls.
The accompanying drawings, which are incorporated in and constitute part of this specification, and together with the description, illustrate and serve to explain various examples.
The present disclosure is directed to systems, methods, and apparatuses for inter-device communication in cellular wireless communication systems. In the current cellular communication system, data transfer between UEs has to be routed through a base station and a core network. When UEs located in close proximity communicate with each other, it would be advantageous for the UEs to communicate via a direct inter-device communication link between them, instead of transferring the data via a network. By providing a direct inter-device communication link between the UEs, improved overall spectral efficiency may be achieved. Moreover, the direct link between the UEs requires lower transmit power at the UE compared to transmitting to the base station, thereby resulting in battery savings at the UEs. Additionally, communicating over the direct link between the UEs may improve quality of service (QoS).
Although the UE may be able to communicate over a direct communication link using another RAT, such as, WLAN, Bluetooth, etc., it requires availability of the services of the other RAT and also requires implementation of the other RAT at the UE. Furthermore, service interruptions and dropped calls may result from switching or handover between different RATs. Therefore, it may be advantageous to enable communications over the inter-device communication link using the same cellular radio access technology and operating in the same radio band.
Reference will now be made in detail to example approaches implemented according to the disclosure; the examples are illustrated in the accompanying drawings. Wherever possible, the same reference numbers will be used throughout the drawings to refer to the same or like parts.
In the example LTE system shown in
The UEs 102a and 102b may transmit voice, video, multimedia, text, web content and/or any other user/client-specific content. The transmission of some content, e.g., video and web content, may require high channel throughput to satisfy the end-user demand. In some instances, however, the channel between UEs 102a, 102b and eNBs 112a, 112b may be contaminated by multipath fading due to the multiple signal paths arising from many reflections in the wireless environment. Accordingly, the UEs' transmission may adapt to the wireless environment. In short, the UEs 102a and 102b may generate requests, send responses or otherwise communicate in different means with Evolved Packet Core (EPC) 120 and/or Internet Protocol (IP) networks 130 through one or more eNBs 112a and 112b.
In some implementations, the UEs 102a and 102b may communicate over an inter-device communication link when they are located in close proximity to one another, without routing the data through the eNB 112a. The boundary of the distance of the inter-device communication link may be limited by the transmission power of the UEs. In one example, close proximity could be a few meters. In another example, close proximity could be tens of meters. It is also possible that in certain circumstances, the close proximity may mean larger distance such as hundreds of meters. For example, the UEs 102a and 102b may communicate directly over the inter-device communication link 104, instead of communicating with each other through their links with the eNB 112a, i.e., 106 and 108 respectively. The inter-device communication link may also be referred to as a device-to-device (D2D) communication link. The UEs 102a and 102b may simultaneously maintain an active communication link with the eNB 112a such that the UEs 102a and 102b may still receive messages from the eNB or other UEs, when communicating with each other over the direct inter-device link.
Examples of UEs include, but are not limited to, a mobile phone, a smart phone, a telephone, a television, a remote controller, a set-top box, a computer monitor, a computer (including a tablet computer such as a BlackBerry® Playbook tablet, a desktop computer, a handheld or laptop computer, a netbook computer), a personal digital assistant (PDA), a microwave, a refrigerator, a stereo system, a cassette recorder or player, a DVD player or recorder, a CD player or recorder, a VCR, an MP3 player, a radio, a camcorder, a camera, a digital camera, a portable memory chip, a washer, a dryer, a washer/dryer, a copier, a facsimile machine, a scanner, a multi-functional peripheral device, a wristwatch, a clock, a game device, etc. The UE 102a or 102b may include a device and a removable memory module, such as a Universal Integrated Circuit Card (UICC) that includes a Subscriber Identity Module (SIM) application, a Universal Subscriber Identity Module (USIM) application, or a Removable User Identity Module (R-UIM) application. Alternatively, the UE 102a or 102b may include the device without such a module. The term “UE” can also refer to any hardware or software component that can terminate a communication session for a user. In addition, the terms “user equipment,” “UE,” “user equipment device,” “user agent,” “UA,” “user device,” and “mobile device” can be used synonymously herein.
A radio access network is part of a mobile telecommunication system which implements a radio access technology, such as Universal Mobile Telecommunications System (UMTS), CDMA2000 and 3rd Generation Partnership Project (3GPP) LTE. In many applications, the Radio Access Network (RAN) included in an LTE telecommunications system 100 is called an EUTRAN 110. The EUTRAN 110 can be located between the UEs 102a, 102b and EPC 120. The EUTRAN 110 includes at least one eNB 112a or 112b. The eNB can be a radio base station that may control all, or at least some, radio related functions in a fixed part of the system. One or more of eNB 112a or 112b can provide radio interface within their coverage area or a cell for the UEs 102a, 102b to communicate. The eNBs 112a and 112b may be distributed throughout the cellular network to provide a wide area of coverage. The eNBs 112a and 112b may directly communicate with one or more UEs 102a, 102b, other eNBs, and the EPC 120.
The eNBs 112a and 112b may be the end point of the radio protocols towards the UEs 102a, 102b and may relay signals between the radio connection and the connectivity towards the EPC 120. The communication interface between the eNB and the EPC is often referred to as an S1 interface. In certain implementations, EPC 120 is a central component of a core network (CN). The CN can be a backbone network, which may be a central part of the telecommunications system. The EPC 120 can include a mobility management entity (MME), a serving gateway (S-GW), and a packet data network gateway (PGW). The MME may be the main control element in the EPC 120 responsible for the functionalities comprising the control plane functions related to subscriber and session management. The SGW can serve as a local mobility anchor, such that the packets are routed through this point for intra EUTRAN 110 mobility and mobility with other legacy 2G/3G systems 140. The S-GW functions may include user plane tunnel management and switching. The PGW may provide connectivity to the services domain comprising external networks 130, such as the IP networks. The UEs 102a, 102b, EUTRAN 110, and EPC 120 are sometimes referred to as the evolved packet system (EPS). It is to be understood that the architectural evolvement of the LTE system 100 is focused on the EPS. The functional evolution may include both EPS and external networks 130.
Though described in terms of
The processing unit 302 may include components and perform functionality similar to the processing module 202 described with regard to
The user interface 308 can include, for example, one or more of a screen or touch screen (for example, a liquid crystal display (LCD), a light emitting display (LED), an organic light emitting display (OLED), a microelectromechanical system (MEMS) display, a keyboard or keypad, a tracking device (e.g., trackball, trackpad), a speaker, and a microphone).
The I/O interface 310 can include, for example, a universal serial bus (USB) interface. One skilled in the art will readily appreciate that various other components can also be included in the example UE device 300.
For UEs to communicate over a direct inter-device communication link, an inter-device communication link is enabled between the UEs. The direct inter-device communication link allows data exchange between the UEs, without routing through the base station and the core network. Descriptions will now be made about methods for UE transmit power adjustment for the inter-device communication in the cellular wireless communication system, according to certain examples of the present disclosure.
The UE may adjust its transmit power for transmissions over the inter-device communication link during a device handshake/discovery procedure and/or during the data transmission. For example, a UE may determine whether to adjust a transmit power level based on a data exchange between the UE and at least one other UE over an inter-device communication link, and adjust the transmit power level based on the determination. The transmit power can be slowly controlled, e.g., in tens of radio frames or can be fast controlled, e.g., in the subframe level. The power control could be eNB based, UE based or both. In one example, eNB could directly control the transmission power based on the feedback information from the UE. In another example, the UE could directly control the transmission power over the D2D link but in this case, the feedback is needed from another UE. ENB and the UE may also be collaborated for the power control. The power control could be single step or multiple step procedure.
LTE uplink and/or downlink radio resources may be used for the data exchange between the UEs over the inter-device communication link. The UE may start transmitting transmission pattern with a transmit power equal to Pmn and increase the transmit power by an increment of ΔTP each time the detection of the predetermined transmission pattern does not meet a required performance target. If the transmit power reaches a maximum transmit power level Pmx, or the received signal quality meets the required performance target, the UE may determine not to increase the transmit power.
Although not shown in
The RRC D2D HS Setup messages 402 and 404 may contain transmission/reception parameters associated with a device handshake. Device handshake transmission/reception parameters may include: transmission patterns, transmit point IDs, device-to-device radio network temporary identity (DD-RNTI) etc. The transmission patterns may be indicated by an index of a transmission pattern. For example, a set of transmission patterns may be defined, such as in a standards document, with corresponding indices. Alternatively specific parameters which may be used to generate the transmission pattern/sequence may be indicated. This message may also include an indication of whether the uplink (UL) radio resources or downlink (DL) radio resources are assigned for handshake procedure and the subsequent data transmission over the direct inter-device communication link.
The eNB may indicate minimum and maximum transmit power levels Pmn and Pmx to the UEs as part of the RRC message, for example, in the RRC D2D HS Setup messages 402 and 404, or in an RRC D2D Connection Setup message. The eNB may set the minimum and maximum transmit power levels based, e.g., on the vicinity of the UEs participating in the inter-device communication and the link loss profile in that specific area.
A quality test procedure 426 may then be performed by one or more of UE0, UE1, and the eNB over the direct communication link. The quality test procedure may include a number of message exchanges between UE1 and UE0 over the direct inter-device communication link between UE1 and UE0, e.g., 414-420, to set up an appropriate transmit power level for UE1 and UE0. The eNB may allocate/ grant radio resources for UE1 and UE0 to transmit over the inter-device communication link in PDCCH messages 410 and 412. The Cyclic Redundancy Check (CRC) of these PDCCH messages are scrambled by the DD-RNTI. The radio resources over which a specific UE transmits the transmission patterns are indicated by tagging those resources with the UE's TP ID. The time between recurring resource grants for the same UE are decided by the expected time for UE to detect the transmission pattern and respond. To differentiate from the regular data transmission over the inter-device communication link, the PDCCH message may include a bit to indicate that the handshake transmission pattern will be transmitted over the inter-device communication link.
As illustrated in
If the received signal quality at UE1 is acceptable, UE1 may then transmit a sequence s1 at a transmit power level, PUE1, Pmn≤PUE1≤Pmx, at 416. In one approach, the transmit power is set as Pmn or close to Pmn at the start of the handshake procedure. Otherwise, UE1 may transmit sequence s0 at the transmit power level PUE1 at 416. Correspondingly, if UE0 receives sequence s0 at 416, the transmit power level of UE0 is increased to PUE0=PUE0+ΔTP for the subsequent transmission at 418 and future transmissions to UE1. ΔTP represents an incremental value for the transmit power level and may be called a transmit power step. If the received signal quality of s0 is acceptable, UE0 transmits sequence s1 in the next transmission 418 at the increased power level. If the received signal quality of s0 is not acceptable, UE0 transmits sequence s0 in the next transmission 418 at the increased power level.
On the other hand, if UE0 receives sequence s1 at 416, the transmit power level of UE0 may be fixed at PUE0 for the subsequent transmission 418 and future transmissions to UE1. If the received signal quality of s0 is acceptable, UE0 transmits sequence s1 in the next transmission 418 at the fixed power level PUE0. If the received signal quality of s0 is not acceptable, UE0 transmits sequence s0 in the next transmission 418 at the fixed power level PUE0. If neither sequence s0 nor s1 is detected from the received signal, UE0 may indicate to the eNB that the device handshake/discovery procedure is unsuccessful.
UE0 and UE1 may repeat steps 414-418 until an acceptable received signal quality is reached at both UE0 and UE1. At the end of a successful handshake/discovery procedure, UE0 and UE1 may send RRC D2D HS Response messages 422 and 424 to the eNB, including their respective transmit power levels and indicating to the eNB that the device discovery/handshake procedure is successful. A Channel Quality Indicator (CQI) of the direct communication link may also be measured by UE0 and UE1 and reported to the eNB such that the eNB may assign an appropriate modulation and coding scheme (MCS) for future data exchanges over the inter-device communication link. It is to be understood that similar procedures may be applied to a scenario where more than 2 UEs are involved in a group inter-device communication, such as interactive gaming, conference calling, etc. The above described transmit power level optimization can be modified with the introduction of another transmit pattern/sequence s2. This is useful if the UEs are allowed to select any initial transmit power level between Pmn and Pmx. In this case a third transmit pattern may be used to indicate a decrease the transmit power level during the next transmission.
If sequence s1 is not received at 506, UE0 may proceed to check whether sequence s0 is received at 516. For example, UE0 determines that s0 is transmitted if Γ0>Γ1 and Γ0>η. If sequence s0 is received, UE0 may further check whether the received signal quality is acceptable at 518. If the received signal quality is acceptable, i.e. Γ0>β, UE0 may transmit sequence s1 at an increased power level PUE0=PUE0+ΔTP over the inter-device communication link at 520. If the received signal quality is not acceptable, UE0 may transmit sequence s0 at the increased power level PUE0=PUE0+ΔTP at 522 and return to 504 of the flow chart.
If sequence s0 is not received at 516, UE0 may set the transmit power level to PUE0=PUE0+ΔTP at 524 for the next transmission over the inter-device communication link. For example, UE0 determines that neither s0 or s1 are transmitted if Γ0≤η+ϵ and Γ1≤η+ϵ, where ϵ is a positive number and specified by the UE receiver. UE0 may further check whether the increased transmit power level PUE0 is less than the maximum transmit power level Pmx at 526. If the increased transmit power level PUE0 is less than the maximum transmit power level, UE0 may transmit sequence s0 at the next transmit instant at 528 and return to 504 of the flow chart. Otherwise, if the increased transmit power level PUE0 is not less than the maximum transmit power level, UE0 may indicate a device handshake/discovery failure to the serving eNB at 530. The above described transmit power level optimization can be modified with the introduction of another transmit pattern/sequence s2. This may be useful, e.g., if the UEs are allowed to select any initial transmit power level between Pmn and Pmx. In this case the third transmit pattern s2 is used to indicate a decrease the transmit power level during the next transmission.
In some implementations, to facilitate the device discovery process, the UE that intends to get involved in the direct-link communication may start periodically broadcast a “beacon” signal to identify itself. The beacon signal could be transmitted over the pre-defined resource or UE specific resource. In one example, if the beacon signal is transmitted over the pre-defined resource, the UE may use orthogonal code sequence for the beacon signal in order to identify itself. In another example, if the beacon signal is transmitted over the UE specific resource, the UE may share the same code sequence. The resource may be directly assigned by the eNB or linked directly with the UE ID. The beacon signal carries at least the UE ID information and is transmitted periodically on pre-determined resources. Other UEs that are capable of conducting inter-device communications may detect the “beacon” signal. The periodic beacon signal may be transmitted/detected only when the UE intends to get involved in the direct-link communication. For example, when UE0 intends to participate in direct-link communication and starts to broadcast a beacon signal, surrounding UEs may detect the beacon signal and consider UE0 as a potential direct-link communication candidate if the beacon signal strength is above a pre-defined threshold value. Then one or more surrounding UEs may initiate a direct-link communication with UE0. The transmit power of this beacon signal may be set by the network such that transmitted beacon signals in a cell do not cause excessive interference within the network. For example, the power level of the beacon signal can be set to be very low, e.g. 10-15 dBm, when the user density within a cell is high.
The systems and methods described above may be implemented by any hardware, software or a combination of hardware and software having the above described functions. The software code, either in its entirety or a part thereof, may be stored in a computer readable memory.
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. Method steps may be implemented in an order that differs from that presented herein.
Also, techniques, systems, subsystems and methods described and illustrated in the various implementations as discrete or separate may be combined or integrated with other systems, modules, techniques, or methods without departing from the scope of the present disclosure. Other items shown or discussed as coupled or directly coupled or communicating with each other may be indirectly coupled or communicating through some interface, device, or intermediate component, whether electrically, mechanically, or otherwise. Other examples of changes, substitutions, and alterations are ascertainable by one skilled in the art and could be made without departing from the spirit and scope disclosed herein.
While the above detailed description has shown, described, and pointed out the fundamental novel features of the disclosure as applied to various implementations, it will be understood that various omissions and substitutions and changes in the form and details of the system illustrated may be made by those skilled in the art, without departing from the intent of the disclosure. Although certain illustrated examples in this disclosure may show only two UEs, the described systems and methods for the inter-device communications can be applied to more than two UEs without departing from the scope of the present disclosure.
Number | Name | Date | Kind |
---|---|---|---|
6925286 | Kraiem | Aug 2005 | B1 |
7969968 | De Luca et al. | Jun 2011 | B2 |
8504052 | Hakola | Aug 2013 | B2 |
8515500 | Das et al. | Aug 2013 | B2 |
8582593 | Chen et al. | Nov 2013 | B2 |
8631466 | Cha et al. | Jan 2014 | B2 |
8649809 | R{umlaut over (b)}ke et al. | Feb 2014 | B2 |
9521683 | Van Phan et al. | Dec 2016 | B2 |
20020111144 | Schiff | Aug 2002 | A1 |
20040202295 | Shen et al. | Oct 2004 | A1 |
20040209634 | Hrastar | Oct 2004 | A1 |
20050026597 | Kim et al. | Feb 2005 | A1 |
20050111383 | Grob et al. | May 2005 | A1 |
20050239451 | Periyalwar et al. | Oct 2005 | A1 |
20060075263 | Taylor | Apr 2006 | A1 |
20060190470 | Lemnotis | Aug 2006 | A1 |
20070129076 | Cho et al. | Jun 2007 | A1 |
20080002658 | Soliman | Jan 2008 | A1 |
20080069063 | Li et al. | Mar 2008 | A1 |
20090075630 | Mclean | Mar 2009 | A1 |
20090119776 | Palnitkar et al. | May 2009 | A1 |
20090130984 | Lee et al. | May 2009 | A1 |
20100009675 | Wijting et al. | Jan 2010 | A1 |
20100095123 | He | Apr 2010 | A1 |
20100240312 | Pend et al. | Sep 2010 | A1 |
20100279672 | Koskela et al. | Nov 2010 | A1 |
20110081908 | Michaelis et al. | Apr 2011 | A1 |
20110106952 | Doppler et al. | May 2011 | A1 |
20110143771 | Edge et al. | Jun 2011 | A1 |
20110145421 | Yao et al. | Jun 2011 | A1 |
20110147462 | Speich | Jun 2011 | A1 |
20110159799 | Chen et al. | Jun 2011 | A1 |
20110194530 | Tinnakornsrisuphap et al. | Aug 2011 | A1 |
20110216739 | Lee et al. | Sep 2011 | A1 |
20110258313 | Mallik et al. | Oct 2011 | A1 |
20110268004 | Doppler et al. | Nov 2011 | A1 |
20110275382 | Hakola et al. | Nov 2011 | A1 |
20110294474 | Barany et al. | Dec 2011 | A1 |
20110317569 | Kneckt et al. | Dec 2011 | A1 |
20120026971 | Khandelia et al. | Feb 2012 | A1 |
20120044865 | Singh | Feb 2012 | A1 |
20120051315 | Wang et al. | Mar 2012 | A1 |
20120093070 | Huang | Apr 2012 | A1 |
20120115518 | Zeira | May 2012 | A1 |
20120129540 | Hakola | May 2012 | A1 |
20120163235 | Ho et al. | Jun 2012 | A1 |
20120163252 | Ahn et al. | Jun 2012 | A1 |
20120179789 | Griot et al. | Jul 2012 | A1 |
20120240216 | Gutierrez | Sep 2012 | A1 |
20130003629 | Jeong et al. | Jan 2013 | A1 |
20130028235 | Barrett et al. | Jan 2013 | A1 |
20130083719 | Seo | Apr 2013 | A1 |
20130159522 | Hakola et al. | Jun 2013 | A1 |
20130160101 | Hakola et al. | Jun 2013 | A1 |
20130244585 | Chen | Sep 2013 | A1 |
20130315196 | Lim et al. | Nov 2013 | A1 |
20130329689 | Choi et al. | Dec 2013 | A1 |
20140004796 | Cakulev et al. | Jan 2014 | A1 |
20140010175 | Chiu | Jan 2014 | A1 |
20140018010 | Gao | Jan 2014 | A1 |
20140022986 | Wu | Jan 2014 | A1 |
20140078952 | Bontu et al. | Mar 2014 | A1 |
20140078971 | Bontu et al. | Mar 2014 | A1 |
20140086152 | Bontu et al. | Mar 2014 | A1 |
20140086153 | Bontu et al. | Mar 2014 | A1 |
20140106707 | Bontu et al. | Apr 2014 | A1 |
20140122607 | Fodor et al. | May 2014 | A1 |
20140140296 | Choi et al. | May 2014 | A1 |
20140153390 | Ishii et al. | Jun 2014 | A1 |
20140342738 | Ishii et al. | Nov 2014 | A1 |
20150036495 | Venkatachalam | Feb 2015 | A1 |
20150131475 | Van Phan | May 2015 | A1 |
Number | Date | Country |
---|---|---|
1331868 | Jan 2002 | CN |
101617548 | Dec 2009 | CN |
102098796 | Jun 2011 | CN |
102217411 | Oct 2011 | CN |
102340829 | Feb 2012 | CN |
102550117 | Jul 2012 | CN |
102647246 | Aug 2012 | CN |
102668493 | Sep 2012 | CN |
102696267 | Sep 2012 | CN |
1063785 | Dec 2000 | EP |
2665299 | Nov 2013 | EP |
2001044932 | Feb 2001 | JP |
20120074251 | Jul 2012 | KR |
200027045 | May 2000 | WO |
2009138820 | Nov 2009 | WO |
2010007498 | Jan 2010 | WO |
2010059856 | May 2010 | WO |
2011036507 | Mar 2011 | WO |
2011050519 | May 2011 | WO |
2011147462 | Dec 2011 | WO |
2012052911 | Apr 2012 | WO |
2012060934 | May 2012 | WO |
2012088470 | Jun 2012 | WO |
2012097075 | Jul 2012 | WO |
Entry |
---|
International Search Report for Application No. PCT/US20/026372, dated Apr. 24, 2013, 13 pages. |
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resoorce Control (RCC); Protocol Specification (Release 11),” V11.1.0, Sep. 2012 (Sep. 24, 2012), 325 pages. |
3GPP TS 36.300 V10.5.0 (Sep. 2011) Technical Specification: Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 10). |
3GPP TS 36.211 V10.3.0 (Sep. 2011) Technical Specification: Evolved Universal Terrestrial Radio Access (E-UTRA); Physical Channels and Modulation (Release 10). |
3GPP TS 36.212 V10.1.0 (Mar. 2011) Technical Specification: Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and channel coding (Release 10). |
3GPP TS 36.213 V10.1.0 (Mar. 2011) Technical Specification: Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures (Release 10). |
3GPP TS 36.331 V10.1.0 (Mar. 2011) Technical Specification: Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification (Release 10). |
Fodor et al., “Design Aspects of Network Assisted Device-to-Device Communications” IEEE Communications Magazine, IEEE Service Center, Piscataway, US, vol. 50, No. 3, Mar. 1, 2012 (Mar. 1, 2012), pp. 170-177; 8 pages. |
“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.”. |
Intel: “Pro se Use Case for Unidirectional D2D Communication”, A 3GPP Draft; S1-120065; 3GPP TSG-SA WG1, Meeting #57; Kyoto, Japan; Feb. 2012; 3 pages. |
Office Action issued in U.S. Appl. No. 13/621,703 dated Nov. 19, 2014. |
Office Action issued in U.S. Appl. No. 13/624,736 dated Aug. 27, 2014; 14 pages. |
International Search Report for Application No. PCT/US2013/026157, dated Jul. 30, 2013, 24 pages. |
International Search Report for Application No. PCT/US2013/026174, dated Jul. 17, 2013, 5 pages. |
International Search Report for Application No. PCT/US2013/026104, dated Jun. 24, 2013, 3 pages. |
International Search Report for Application No. PCT/US2013/026356, dated Jun. 19, 2013, 3 pages. |
International Search Report for Application No. PCT/US2013/026382, dated Jul. 11, 2013, 5 pages. |
Search Report issued in TW Application No. 102132479 dated Nov. 7, 2014, 1 page. |
“Intel: ““Operator Managed and Operator Assisted D2D””, 3GPP Draft; S1-120063; 3GPP TSG-SA WG1; Meeting #57, Kyoto, Japan; Feb. 2012 ; 4 pages.”. |
Office Action and Search Report issued in TW Application No. 102132483 dated Dec. 25, 2014; 8 pages. |
Office Action issued in U.S. Appl. No. 13/652,011 dated Jan. 23, 2015. |
Office Action and Search Report issued in Taiwanese Application No. 102132482 dated Dec. 26, 2014; 9 pages. |
Office Action and Search Report issued in Taiwanese Application No. 102132487 dated Dec. 26, 2014; 12 pages. |
Taiwanese Office Action and Search Report in Taiwanese Application No. 102132478, dated Jan. 22, 2015, 11 pages. |
International Preliminary Report on Patentability in International Application No. PCT/US2013/026157, dated Apr. 2, 2015, 17 pages. |
International Preliminary Report on Patentability in International Application No. PCT/US2013/026382, dated Apr. 2, 2015, 10 pages. |
International Preliminary Report on Patentability in International Application No. PCT/US2013/026372, dated Mar. 31, 2015, 8 pages. |
International Preliminary Report on Patentability in International Application No. PCT/US2013/026356, dated Apr. 30, 2013, 7 pages. |
International Preliminary Report on Patentability in International Application No. PCT/US2013/026174, dated Apr. 2, 2015, 13 pages. |
Advisory Action issued in U.S. Appl. No. 13/622,137 dated Jul. 26, 2017, 4 pages. |
Office Action issued in Korean Application No. 10-2015-7012597 dated Mar. 18, 2016, 19 pages. |
Office Action issued in Korean Application No. 10-2015-7010012 dated Apr. 19, 2016, 13 pages. |
Office Action issued in Korean Application No. 10-2015-7010443 dated May 27, 2016, 10 pages. |
Office Action issued in Korean Application No. 10-2015-7010012 dated Sep. 6, 2016, 4 pages. |
Office Action issued in Korean Application No. 10-2015-7010443 dated Nov. 25, 2016, 11 pages. |
Office Action issued in Chinese Application No. 201380060975.7 dated May 5, 2016, 8 pages. |
Office Action issued in Chinese Application No. 201380060975.7 dated Dec. 5, 2016, 18 pages. |
Office Action issued in Chinese Application No. 201380060975.7 dated May 4, 2017, 19 pages. |
Office Action issued in Chinese Application No. 201380060975.7 dated Oct. 11, 2017, 21 pages. |
Office Action issued in Chinese Application No. 201380061529.8 dated Nov. 16, 2017; 6 pages, 26 pages. |
Office Action issued in Chinese Application No. 201380053808.X dated Nov. 16, 2017; 9 pages, 19 pages. |
Office Action issued in Chinese Application No. 201380060173.6 dated Nov. 23, 2017; 23 pages. |
Office Action issued in Chinese Application No. 201380058840.7 dated Nov. 27, 2017; 7 pages, 14 pages. |
Communication Pursuant to Article 94(3) EPC issued in European Application No. 13707754.1 dated Apr. 11, 2016, 5 pages. |
Communication Pursuant to Article 94(3) EPC issued in European Application No. 13707748.3 dated Oct. 18, 2016, 6 pages. |
Communication Pursuant to Article 94(3) EPC issued in European Application No. 13707748.3 dated Feb. 8, 2017, 7 pages. |
Communication Pursuant to Article 94(3) EPC issued in European Application No. 13707753.3 dated Nov. 20, 2017; 3 pages. |
Communication Pursuant to Article 94(3) EPC issued in European Application No. 13707748.3 dated Jan. 12, 2018, 9 pages. |
Office Action issued in Chinese Application No. 201380060975.7 dated Apr. 4, 2018, 13 pages. |
Office Action issued in Chinese Application No. 201380061529.8 dated Apr. 27, 2018, 2 pages. |
Office Action issued in Chinese Application No. 201380060975.5 dated Sep. 5, 2018, 6 pages. |
Number | Date | Country | |
---|---|---|---|
20140086157 A1 | Mar 2014 | US |