JP2018529248A - Efficient application synchronization using out-of-band device-to-device communication - Google Patents

Abstract

  The present disclosure relates to synchronizing application account data using out-of-band device-to-device (D2D) communication between peer wireless devices. More specifically, the first device may generate a local unique representation that includes a name, user certificate, and last update time associated with an application registered with a D2D-based application synchronization service. In response to detecting one or more external specific expressions from one or more peer devices in proximity that match the name and user certificate associated with the registered application, the first device Identifies the update device associated with an external named entity that has a last updated time that is more recent than the last updated time associated with a local named entity from one or more peer devices and updates it through out-of-band D2D connections An update may be requested to synchronize application account data from the device.

Description

  Various aspects described herein relate generally to device-to-device (D2D) communication, and more particularly to synchronizing application data using out-of-band D2D communication between peer wireless devices.

  Wireless communication systems are widely deployed to provide various types of communication content including, inter alia, voice, video, packet data, messaging, and broadcast. Wireless communication systems (e.g., multi-access networks that can share available network resources to support multiple users) include first generation analog wireless telephone service (1G), second generation (2G) digital wireless telephone service ( It has evolved through various generations, including provisional 2.5G and 2.75G networks), and third generation (3G) and fourth generation (4G) high-speed data / internet-enabled wireless services. Currently, many different wireless communication systems are in use, including cellular systems and personal communication service (PCS) systems. Examples of exemplary cellular systems include Cellular Analog Advanced Mobile Phone System (AMPS), as well as code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), and orthogonal FDMA (OFDMA). ), TDMA variants of single carrier FDMA (SC-FDMA), Global System for Mobile access (GSM), and newer hybrid digital communication systems that use both TDMA and CDMA technologies. More recently, Long Term Evolution (LTE) has been developed as a wireless communication protocol for high-speed data wireless communication for mobile phones and other data terminals. LTE is based on GSM, and various GSM related protocols (e.g., Enhanced Data rates for GSM Evolution (EDGE)) and Universal Mobile Telecommunications System (UMTS) protocols (e.g., High-Speed Packet Access (HSPA)). Includes contributions from

  In general, a wireless communication network may include various base stations (referred to as evolved node B, eNB, or access node) that can support communication for user equipment (UE). In a WAN, the UE typically communicates via uplink / downlink channels between the UE and the base station, thereby communicating with the base station. However, if two or more UEs are sufficiently close to each other, the UEs may be able to communicate directly, i.e. without passing through any base station. Thus, a UE may support direct peer-to-peer (P2P) or device-to-device (D2D) communication with one or more other UEs. For example, LTE Direct (LTE-D, sometimes referred to as “LTE-Advanced”) is a proposed 3GPP (Release 12) D2D strategy for proximity discovery. LTE-D obviates the need for location tracking and network calls by directly monitoring services on other LTE Direct devices within a wide range (approximately 500 meters with line of sight). Thus, among other benefits, LTE-D directly monitors services on other LTE-D devices in the synchronization system and simultaneously detects many nearby services in a continuous and battery-efficient manner. can do.

  LTE-D operates on the licensed spectrum as a service for mobile applications and provides a D2D strategy that enables service layer discovery. A mobile application on an LTE-D device monitors LTE mobile application services on other devices and announces its services at the physical layer for detection by services on other LTE-D devices. D can be instructed so that the application can be closed while LTE-D is running substantially continuously and the client application will be notified when a match with the monitor is detected Receive. Thus, LTE-D is an attractive alternative for mobile developers seeking to deploy proximity discovery strategies to extend their existing services. For example, LTE-D is a distributed discovery (as opposed to the centralized discovery that exists today) that allows mobile applications to refrain from centralized database processing when identifying relevance matches. This is because, instead of centralized database processing, relevance can be determined autonomously at the device level through sending and monitoring relevant attributes. LTE-D provides additional benefits in terms of power consumption because it does not constantly track location to determine proximity, and the discovery can be kept on the device as a result of which users can share more information with external devices. Since it can be controlled, it provides an additional advantage in terms of privacy.

  Furthermore, LTE-D can increase network efficiency because devices communicate directly using the cellular spectrum without utilizing the cellular network infrastructure. Therefore, since LTE-D uses a licensed cellular spectrum, cellular coverage can be expanded and interference from other devices can be controlled (unlike D2D communication in an unlicensed band). Thus, LTE-D can transfer significant data between LTE-D capable devices that are close enough using a direct connection, thereby offloading traffic from the network infrastructure. Moreover, in addition to enabling high data transfer rates, LTE-D has low delay and energy consumption in UEs communicating over LTE-D links. In addition, LTE-D has applications in national security and public safety networks, which provide high data rates that allow LTE to exchange real-time data and multimedia between emergency personnel in crisis situations. However, D2D functionality can improve the performance of LTE-based public safety networks in events where the LTE infrastructure can become completely or partially unusable (e.g. in disaster situations such as earthquakes, hurricanes, terrorist attacks, etc.) .

  Therefore, it efficiently supports D2D communications, among other things, to enable new services, improve existing services, eliminate interference and / or reduce, and / or reduce traffic load on the network infrastructure A technique for this is desired.

  The following presents a simplified summary of one or more aspects disclosed herein. Accordingly, the following summary should not be taken as an extensive overview of all contemplated aspects, and the following outlines identify key or critical elements for all contemplated aspects or are optional And should not be construed as defining the scope associated with any particular embodiment. Accordingly, the following summary is intended solely to present some concepts related to one or more aspects disclosed herein in a simplified form prior to the detailed description presented below. Have

  According to various aspects, the present disclosure generally relates to device-to-device (D2D) application synchronization. For example, according to various aspects, a method for D2D application synchronization includes, on a first device, an application registered with a name, one or more user certificates, and a D2D-based application data synchronization service. Generating a local unique representation that includes a last update time associated with and at a first device received and registered from one or more peer devices proximate to the first device Detect one or more external specific expressions that match the name associated with the application and one or more user certificates, and associate with local specific expressions from one or more peer devices Updates associated with an external named entity that have a last modified time that is more recent than the last modified time It may comprise identifying a device, and a step of requesting an update to synchronize the application data associated with the application that is registered from the update device through out-of-band D2D connection. Further, according to various aspects, the first device starts one or more timers when requesting an update to synchronize application data over a D2D connection, and the one or more timers have not expired. Applications that are registered from the network server in response to determining that one or more timers have expired, while synchronizing application data using updated data received from the update device over a D2D connection Application data associated with can be synchronized. In addition, according to various aspects, the method further optionally broadcasts a local native representation associated with the registered application, and a second device of the one or more peer devices. Receiving a request to update application data associated with an application registered through a second D2D connection, wherein the last update time in the local named representation is received from the second device. And sending updated data associated with the application through the second D2D connection to the second device that is more recent than the last update time in the external specific representation.

  According to various aspects, the wireless device may include a local unique name including a name, one or more user certificates, and a last update time associated with an application registered with a D2D-based application data synchronization service. A transmitter configured to broadcast the representation, a receiver configured to receive one or more external specific representations from one or more peer devices proximate to the wireless device, and 1 Detects that one or more external unique expressions match the name and one or more user certificates associated with the registered application, and from among one or more peer wireless devices, the local unique External specific expressions and relationships that include a last modified time that is more recent than the last modified time One or more processors configured to identify update devices to be attached and to request updates to synchronize application data associated with registered applications from the update device through an out-of-band D2D connection. Can be prepared.

  According to various aspects, an apparatus includes a local unique representation including a name, one or more user certificates, and a last update time associated with an application registered with a D2D-based application data synchronization service. One or more matching names and one or more user certificates received from one or more peer devices proximate to the device and associated with the registered application A means for detecting multiple external specific expressions and associated with an external specific expression that includes a last update time that is more recent than one associated with the local specific expression from one or more peer devices To identify the update device to be registered and the registered apps from the update device through out-of-band D2D connection It may comprise means for requesting an update to synchronize the application data associated with Shon.

  According to various aspects, a computer-readable storage medium may store computer-executable instructions that, when executed on a wireless device, give the wireless device a name, 1 One or more user certificates and one or more close to the wireless device that generates a local representation that includes the last update time associated with an application registered with a D2D-based application data synchronization service Detect one or more external specific expressions that match the name and user certificate received from multiple peer devices and associated with a registered application, and from within one or more peer devices Last update more recent than the last update time associated with An update device associated with an external named representation that includes the new time may be identified and an update requested to synchronize application data associated with registered applications from the update device through an out-of-band D2D connection.

  Other objects and advantages associated with the various aspects disclosed herein will become apparent to those skilled in the art based on the accompanying drawings and detailed description.

  Many aspects of the present disclosure and its attendant advantages may be better understood when considered in conjunction with the accompanying drawings presented by way of example only and not limitation of the present disclosure with reference to the following detailed description. So a more complete understanding of them will be easily obtained.

FIG. 7 illustrates an example wireless network architecture that supports device-to-device (D2D) communication in accordance with various aspects. FIG. 7 illustrates an example access network that supports D2D communication, in accordance with various aspects. FIG. 7 illustrates an example downlink (DL) frame structure in LTE, according to various aspects. FIG. 3 illustrates an example uplink (UL) frame structure in LTE, according to various aspects. FIG. 3 illustrates an example user plane and control plane radio protocol architecture in accordance with various aspects. FIG. 7 illustrates an exemplary evolved Node B (eNB) and user equipment (UE) in an access network, according to various aspects. FIG. 7 illustrates an example wireless environment in which two wireless devices may establish and communicate through an out-of-band D2D connection to efficiently synchronize application data, in accordance with various aspects. FIG. 6 illustrates an exemplary representation that a wireless device may broadcast and discover to efficiently synchronize application data through an out-of-band D2D connection with a peer wireless device, in accordance with various aspects. FIG. 8 illustrates an example synchronization procedure that a wireless device may perform to synchronize application data over an out-of-band D2D connection with a peer wireless device, according to various aspects. FIG. 8 illustrates an example synchronization procedure that a wireless device may perform to synchronize application data over an out-of-band D2D connection with a peer wireless device, according to various aspects. FIG. 7 illustrates an example asynchronous procedure that a wireless device may perform to synchronize application data over an out-of-band D2D connection with a peer wireless device, according to various aspects. FIG. 7 illustrates an example asynchronous procedure that a wireless device may perform to synchronize application data over an out-of-band D2D connection with a peer wireless device, according to various aspects. FIG. 7 illustrates an example UE that can support efficient application data synchronization using out-of-band D2D communication, according to various aspects. Exemplary conceptual data between various modules, means, and / or components in an exemplary apparatus that can support efficient application data synchronization using out-of-band D2D communication, according to various aspects. It is a figure which shows the flow of. FIG. 6 illustrates an example hardware implementation corresponding to a wireless device that can support efficient application data synchronization using out-of-band D2D communication, according to various aspects.

  Various aspects are disclosed in the following description and related drawings to set forth specific examples relating to exemplary embodiments. Alternate embodiments will become apparent to those skilled in the art upon reading this disclosure, and may be constructed and practiced without departing from the scope or spirit of this disclosure. In addition, well-known elements may not be described in detail or may be omitted so as not to obscure the relevant details of the aspects and embodiments disclosed herein.

  The word “exemplary” is used herein to mean “serving as an example, instance, or illustration”. Any embodiment described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments. Similarly, the term “embodiment” does not require that all embodiments include the features, advantages, or modes of operation described below.

  The terminology used herein is for the purpose of describing particular embodiments only and is not to be construed as limiting any embodiment disclosed herein. As used herein, the singular forms “a”, “an”, and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. The terms "comprises", "comprising", "includes", and / or "including" are stated as used herein. Clarify the presence of a feature, integer, step, action, element, and / or component, but the presence of one or more other features, integers, steps, actions, elements, components, and / or groups thereof Or, those skilled in the art will further appreciate that the addition is not excluded.

  Moreover, many aspects are described in terms of a series of activities to be performed by, for example, elements of a computing device. The various activities described herein can be performed by particular circuits (e.g., application specific integrated circuits (ASICs)), program instructions being executed by one or more processors, or combinations thereof. Those skilled in the art will recognize that. In addition, these series of activities described herein can be any form that, when executed, stores a corresponding set of computer instructions that cause the associated processor to perform the functions described herein. Can be considered to be fully embodied in a computer readable storage medium. Thus, various aspects of the disclosure may be embodied in a number of different forms, all considered to be within the scope of the claimed subject matter. Further, for each aspect described herein, the corresponding form of any such aspect is described herein as, for example, "logic configured to" perform the activities described. Sometimes.

  The techniques described herein may be used for various wireless communication systems such as CDMA, TDMA, FDMA, OFDMA, and SC-FDMA systems. The terms “system” and “network” are often used interchangeably. A CDMA system may implement a radio technology such as Universal Terrestrial Radio Access (UTRA), cdma2000. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. cdma2000 covers IS-2000, IS-95, and IS-856 standards. A TDMA system may implement a radio technology such as Global System for Mobile Communications (GSM). The OFDMA system uses wireless technologies such as Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE802.11 (Wi-Fi), IEEE802.16 (WiMAX), IEEE802.20, and Flash-OFDM (trademark). Can be implemented. UTRA and E-UTRA are part of the Universal Mobile Telecommunication System (UMTS). 3GPP Long Term Evolution (LTE) is a release of UMTS that uses E-UTRA, which uses OFDMA for the downlink and SC-FDMA for the uplink. UTRA, E-UTRA, UMTS, LTE and GSM are , Described in documents from an organization named “3rd Generation Partnership Project” (3GPP). CDMA2000 and UMB are described in documents from an organization named “3rd Generation Partnership Project 2” (3GPP2). For clarity, some aspects are described below for LTE, and LTE terminology may be used in much of the description below.

In accordance with various aspects, FIG. 1 illustrates an exemplary wireless network architecture 100 that may support out-of-band device-to-device (D2D) communication, where the wireless network architecture 100 is Long Term Evolution (LTE) (or Evolved Packet System (EPS) network architecture 100 may be provided. In various embodiments, the network architecture 100 includes a first user equipment (UE ₁ ) 102, a second user equipment (UE ₂ ) 104, an Evolved UMTS Terrestrial Radio Access Network (E-UTRAN) 110, and an Evolved Packet Core (EPC) 120, Home Subscriber Server (HSS) 135, and Internet Protocol (IP) service 140 associated with an operator (eg, a mobile operator) may be included. The EPS network architecture 100 can be interconnected with other access networks and core networks (not shown), such as UMTS access networks or IP core networks. As shown, EPS network architecture 100 provides packet-switched services, but those skilled in the art will readily appreciate that the various concepts disclosed herein can be extended to networks that provide circuit-switched services. Will.

According to various embodiments, the E-UTRAN 110 includes a _first evolved Node B (eNB ₁ ) 112 communicating with UE ₁ 102 and a second eNB (eNB ₂ ) communicating with UE ₂ 104. 114. The eNBs 112, 114 may provide user plane protocol and control plane protocol terminations towards the UEs 102, 104 and may be connected to each other via a backhaul (eg, X2 interface). eNB112, 114, base station, Node B, access point, transceiver base station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), or some other suitable Sometimes called terminology. Each eNB 112, 114 provides an access point to the EPC 120 for each UE 102, 104. Exemplary UEs 102, 104 include, but are not limited to, mobile phones, smartphones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices , Digital audio players (eg, MP3 players), cameras, game consoles, tablets, or any other device that functions similarly. Further, UE ₁ 102 and / or UE ₂ 104 may be a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station Those skilled in the art will appreciate that they may also be referred to as access terminals, mobile terminals, wireless terminals, remote terminals, handsets, user agents, mobile clients, clients, and the like.

  Each eNB 112, 114 can connect to the EPC 120 via a Si interface, which is a mobility management entity (MME) 122, another MME 124, a serving gateway 126, a multimedia broadcast multicast service (MBMS) gateway 130, a broadcast A multicast service center (BM-SC) 132 and a packet data network (PDN) gateway 128 may be included. The MME 122 is a control node that can process signaling between the UEs 102 and 104 and the EPC 120. In general, the MME 122 performs bearer and connection management, while all user IP packets are forwarded through the serving gateway 126, which can be connected to the PDN gateway 128. The PDN gateway 128 may provide UE IP address allocation as well as other functions. PDN gateway 128 is connected to operator IP service 140, which includes the Internet, Intranet, IP Multimedia Subsystem (IMS), PS Streaming Service (PSS), and / or other suitable services. obtain. The BM-SC 132 provides functions for provisioning and deployment of MBMS user services and may serve as an entry point for content provider MBMS transmissions. Further, according to various aspects, the BM-SC 132 may authenticate and initialize an MBMS bearer service in the PLMN, schedule and distribute MBMS transmissions, and / or provide other similar functions. MBMS gateway 130 is used to distribute MBMS traffic to one or more eNBs (e.g., eNB112, 114) belonging to a multicast broadcast single frequency network (MBSFN) area that is broadcasting a specific service And may be responsible for session management (start / stop) and collection of eMBMS-related billing information.

According to various embodiments, a UE pair (eg, UE ₁ 102 and UE ₂ 104) establishes an out-of-band device-to-device (D2D) connection and utilizes the respective eNB ₁ 112 and eNB ₂ 114, respectively. Without direct communication, and then can forward data traffic through its out-of-band D2D connection. In general, one or more entities in the network infrastructure (e.g., entities in eNB 112, 114, EPC 120, etc.) can coordinate out-of-band D2D communication between UE pairs 102, 104, which Means that the network entity can help establish an out-of-band D2D connection, can control usage in D2D and legacy modes, can provide security support, and so on. As used herein, the terms “out-of-band D2D connection”, “D2D mode”, and / or other variations thereof generally refer to direct communication between two or more UEs 102, 104 that do not pass through any base station. The terms “legacy connection”, “legacy mode”, and / or other variations thereof may generally refer to communication over a network (eg, via eNB 112, 114). In various embodiments, the UE pair 102, 104 can autonomously establish an out-of-band D2D connection, where the initial discovery used to establish the out-of-band D2D connection is the UE 102, 104. Based on the ability to communicate signals directly between. In addition (or alternatively), the UE is connected to a network that does not support D2D mode but allows D2D mode, and UEs 102, 104 connect through the network and exchange serving cell and location information, It may be determined whether D2D mode is possible. As the D2D mode becomes in progress, the UEs 102, 104 may monitor the relative positions associated with them. In addition, groups with more than two UEs can enter D2D mode, which allows some or all UE pairs in the group to maintain direct D2D communication between each other, Some UEs in can act as relays to relay D2D communication between other UEs in the group. For example, one UE in the group acts as a relay to maintain direct D2D communication with other UEs in the group, and other UEs communicate indirectly via D2D communication Can be designated to act as a relay to enable In this example, a UE acting as a relay may act to relay communications between other UEs in the group. A group that includes several UEs that utilize D2D communication between each other monitors the relative location associated with them, and any UE in the group based on the current relative location associated with them Can be assigned (and / or reassigned) a relay role.

  Returning to FIG. 1, in another aspect, legacy mode may not be available and / or impossible (for example, if the network is congested or part of the network is temporarily not functioning) Or if it does not provide continuous radio coverage for both UEs 102, 104), the network may assist two or more UEs 102, 104 for entering D2D mode. In another aspect, a network (eg, one or more network entities) may control entering D2D mode and support handover between D2D mode and legacy mode.

  In accordance with various aspects, FIG. 2 shows an exemplary access network 200 in which some devices can be connected via out-of-band direct device-to-device (D2D) connections (e.g., LTE Direct (LTE- D), Wi-Fi Direct (WFD), or another suitable D2D radio access technology). In addition, devices in access network 200 may also connect to a wireless wide area network (WWAN) or other suitable network infrastructure. Referring to FIG. 2, an application server 270 may be connected to a first cell 230 having a first base station 232 and a second cell 240 having a second base station 242; Further, it may be coupled to first base station 232 and second base station 242 via network link 220 (eg, Rx link, Gx link, etc.). The coverage area associated with a given base station is represented via the cell in which the given base station is located, whereby in FIG. 2, the first cell 230 corresponds to the first base station 232 The second cell 240 includes a coverage area corresponding to the second base station 242. Cells 230, 240 in access network 200 include various UEs that communicate with respective base stations 232, 242 and communicate with application server 270 via respective base stations 232, 242. For example, in FIG. 2, the first cell 230 includes UE 234, UE 236, and UE 238, while the second cell 240 includes UE 244, UE 246, and UE 248, and one or more of the UEs in the access network 200 or The plurality can be mobile or fixed. Although not shown in FIG. 2, the base stations 232, 242 may be connected to each other via a backhaul link.

  According to various aspects, one or more of UE234, UE236, UE238, UE244, UE246, and UE248 can support direct device-to-device (D2D) communication, such as The UEs can communicate with each other directly out of band (ie, without having to communicate through another device or network infrastructure elements such as the first base station 232 and the second base station 242). In addition, such UEs may further support legacy communication through network infrastructure elements such as first base station 232 and / or second base station 242. In legacy communications with network infrastructure, signals may generally be transmitted and received through uplink and downlink connections between various UEs and base stations 232, 242, and these uplink and downlink connections. The link connection may include a link 222 in the first cell 230 and a link 224 in the second cell 240, and the base stations 232, 242 generally each UE in the corresponding cell 230, 240. To support communication between UEs served in those cells. According to various aspects, traffic from a base station 232 serving UEs 234, 236 when two or more UEs, such as UE234 and UE236, wish to communicate with each other and are located sufficiently close to each other. A direct D2D link is established between those UEs that may allow the UEs 234, 236 to communicate more efficiently or provide other benefits that will be apparent to those skilled in the art. obtain.

  As shown in FIG. 2, UE 246 may communicate with UE 248 through intermediary base station 242 via link 224, and UE 246, 248 may further communicate via D2D link 256. In addition, for inter-cell communication where the participating UEs are in different nearby cells, a direct D2D communication link is still possible, which means that UE 238 and UE 244 use direct D2D communication as indicated by dashed link 254. The communication is shown in FIG. In some situations, two or more UEs in the access network 200 may in some cases have specific users using the same application (e.g., email application) with the same username and certificate across multiple devices. May be associated. However, under existing synchronization algorithms and implementations, multiple devices running the same application with the same username and certificate individually run the same application with the same username and certificate. The synchronization procedure with the corresponding application server 270 may be performed without utilizing or considering the latest synchronization data that may be available on other closely located devices, for several reasons Tend to be an inefficient method. For example, two UEs (e.g. UE pair 234, 236, UE pair 238, 244, UE pair 246, 256, etc.) both belong to the same user (e.g. via LTE-Direct, Wi-Fi Direct, etc.) Consider a use case that supports direct D2D communication and has the same application installed and logged into the application server 270 using the same user certificate. Furthermore, assuming that one UE in the UE pair has performed synchronization procedures with the application server 270 more recently than the other UEs in the UE pair, the other UEs are also close to that one UE. Rather than utilizing or taking into account the more recently synchronized application data available on other UEs located at the same location, it may be inefficient to synchronize data associated with the application through the application server 270. For example, in a situation where the access network 200 corresponds to a cellular network (eg, an LTE network) and the UE 244 is synchronizing application data via the application server 270 more recently than the UE 238, via the legacy cellular links 222, 220. When UE 238 uses cellular resources to synchronize application data through application server 270, it consumes resources unnecessarily in cellular access network 200, and data rate decreases depending on the load in cellular access network 200 The UE 238 may consume more power due to the need to transmit with greater power to close the loop with the base station 232, and so on. In another example, in a situation where the first cell 230 corresponds to a Wi-Fi network and the UE 234 is synchronizing application data via the application server 270 more recently than the UE 236, the legacy Wi-Fi links 222, 220 Using the Wi-Fi network 230 to allow UE236 to synchronize application data through the application server 270 over the network results in greater round trip time (RTT) delays and reduced data rates depending on backhaul congestion There are things. Thus, as discussed in more detail below, the above-referenced problems are mitigated through efficient synchronization of application data through out-of-band D2D connections rather than legacy links 222, 224, 220. This, among other benefits, improves the performance at the UE performing synchronization procedures through out-of-band D2D connections, reduces backhaul congestion and load on the access network, and other users in the same access network 200 High throughput can be achieved by allowing more resource blocks to be allocated from the base stations 232,242.

  For example, when a closely located UE that can synchronize data associated with the same application and the same user certificate through a D2D communication link, instead uses a legacy communication link to synchronize application data with the application server individually. Various data and signaling problems that may arise are illustrated in FIGS. 3 and 4, which illustrate an exemplary downlink (DL) frame structure 300 in LTE and an exemplary uplink (UL) frame structure 400 in LTE, respectively. It will become clearer. However, the following description discusses the data and signaling issues referred to above in the LTE context to simplify the discussion given herein, and the same or similar issues may be considered for other D2D radios. Those skilled in the art will appreciate that this may apply in wireless communication systems that support access technologies (eg, Wi-Fi Direct, Bluetooth, ZigBee, NFC, etc.).

  More specifically, referring to FIG. 3, a DL frame structure 300 in LTE may divide a 10 millisecond (10 ms) frame into 10 equally sized subframes 306. Each subframe 306 may include two consecutive time slots 308. A resource grid may be used to represent two time slots, where each time slot includes a resource block (RB) 310. In LTE, the resource grid may be divided into multiple resource elements. Furthermore, in LTE, RB310 includes 12 consecutive subcarriers in the frequency domain, and for the normal cyclic prefix in each OFDM symbol, 7 consecutive OFDM symbols in the time domain, i.e., 84 May contain resource elements. For an extended cyclic prefix, a resource block may include 6 consecutive OFDM symbols in the time domain and may have 72 resource elements. A physical DL control channel (PDCCH), a physical DL shared channel (PD-SCH), and other channels may be mapped to resource elements. In addition, some resource elements shown as R302, 304 include DL reference signals (DL-RS), which are cell specific reference signals (CRS) (sometimes referred to as common RS) 302 and UE specific A reference signal (UE-RS) 304 may be included. In general, UE-RS 304 may be transmitted only on the resource block to which the corresponding PD-SCH is mapped. The number of bits carried by each resource element may vary depending on the modulation scheme. Therefore, the more RBs the eNB allocates to the UE and the higher the modulation scheme, the higher the UE data rate.

  In LTE Direct (eg, D2D communication in an LTE environment as applicable to out-of-band D2D communication as described herein), the D2D communication link may be the subject of a distributed scheduling mechanism. For example, according to various aspects, a request-to-send (RTS) / clear-to-send (CTS) handshake signaling exchange allows each device in a potential D2D pair to communicate data over an out-of-band D2D communication link. Can be performed before trying. In LTE-Direct (LTE-D), 24 RBs may be available for RTS / CTS signaling. Furthermore, in LTE-D, for each D2D communication link, one RB may be assigned as the RTS block 312 and another RB may be assigned as the CTS block 314. In other words, each D2D communication link may use RB pairs for RTS / CTS signaling. In this specification, an RB pair may be referred to as a connection identifier (CID) 316.

  Referring now to FIG. 4, an uplink (UL) frame structure 400 in LTE may partition the available resource blocks on the UL into a data section and a control section. The control section may be formed at the two ends of the system bandwidth and may have a configurable size. Resource blocks in the control section may be allocated to the UE for transmission of control information. The data section may include all resource blocks that are not included in the control section. With this UL frame structure, a data section may contain continuous subcarriers, which allows a single UE to be assigned all of the continuous subcarriers in the data section Can be.

  The UE may be assigned resource blocks 410, 412 in the control section to transmit control information to the eNB. The UE may be assigned resource blocks 420, 422 in the data section to transmit data to the eNB. The UE may send control information on a physical UL control channel (PUCCH) on the assigned resource block in the control section. The UE may transmit data alone or both data and control information on a physical UL shared channel (PUSCH) on the allocated resource block in the data section. UL transmissions may span both slots of a subframe and may hop across the frequency.

  The set of resource blocks may be used to perform initial system access and achieve UL synchronization in a physical random access channel (PRACH) 430. PRACH 430 may carry a random sequence and may not carry any UL data / signaling. In an aspect, a RACH sequence may be reserved for communication of ACK / NACK information from the UE while in idle mode. Each random access preamble may occupy a bandwidth corresponding to six consecutive resource blocks. The starting frequency can be specified by the network. That is, transmission of random access preambles can be limited to a number of time and frequency resources. For PRACH, frequency hopping may not exist. PRACH attempts may be carried in one subframe (1ms) or in a few consecutive subframes, and the UE may only have a single PRACH attempt every frame (10ms). May not be done.

  Thus, the context with the situation mentioned above, where two or more UEs individually synchronize data associated with a particular application using the same username and user certificate via a particular target application server Then, the eNB in the cell associated with each UE may allocate at least some resource blocks to each UE using the legacy cellular communication link to communicate with the target application server. Thus, in doing so, fewer resource blocks may be available to allocate to other UEs in each cell. However, the first UE performs a synchronization procedure with the target application server, followed by a second UE that is sufficiently close to the first UE, and uses the legacy communication link to transmit the most recent application data. If it is obtained from the first UE through out-of-band D2D connection instead of obtaining from the server, the eNB associated with the second UE can communicate with other UEs in the cell associated with the second UE (i.e. More resource blocks can be allocated (from resource blocks that no longer need to be allocated to allow communication between the second UE and the target application server). In that sense, D2D communication between the first UE and the second UE can offload some traffic from the cellular network, which reduces the load and backhaul congestion in the cellular network. No longer need to transmit with large power to close the loop with the eNB, allowing other UEs in the cell associated with the second UE to enjoy higher data rate and / or throughput There may be improved performance at the second UE that is not, and possibly lower data rates due to any load and backhaul congestion that may be present in the cellular network.

  According to various aspects, FIG. 5 is an example for a user plane and control plane in LTE to support wireless communication between UE 502 and UE 532 via eNB 504, SWG 526, and PDN gateway 530. A user plane and control plane radio protocol architecture 501 is shown. Further, in various embodiments, substantially the same and / or similar signaling as described herein may be transmitted between the eNB, the SWG, and a PDN gateway (not shown) that supports UE532. Those skilled in the art will appreciate what can be done. In various embodiments, UE 502 shown in FIG. 5 may correspond to UE 102 and UE 532 may correspond to UE 104 shown in FIG. Similarly, the eNB 504 may correspond to the eNB 112 in FIG. 1, the SWG 526 may correspond to the SWG 126 in FIG. 1, and the PDN gateway 530 may correspond to the PDN gateway 128 in FIG. As mentioned above, additional entities not shown in FIG. 5 may exist to carry user plane signaling between the PDN gateway 530 and the UE 532 (eg, eNB, SWG, PDN gateway, etc.).

  In various embodiments, radio protocol architecture 501 for UE 502 and eNB 504 is shown using three layers: layer 1 (L1 layer), layer 2 (L2 layer), and layer 3 (L3 layer). Data / signaling communication may occur between UE 502 and eNB 504 across three layers. The L1 layer 506 is the lowest layer and implements various physical layer signal processing functions. L1 layer 506 may also be referred to as physical layer 506, physical L1 layer 506, or variations thereof. The L2 layer is above the physical L1 layer 506 and is responsible for the link between the UE 502 and the eNB 504 on the physical L1 layer 506. In the user plane associated with UE 502, the L2 layer includes medium access control (MAC) sublayer 510, radio link control (RLC) sublayer 512, and packet data convergence protocol (PDCP) sublayer 514, which are in the eNB on the network side. Terminated. UE 502 may have several upper layers above the L2 layer, which connect to a network layer (e.g., IP layer) 518 that may correspond to an L3 layer that may terminate at the PDN gateway 530 on the network side Application layer 520 that may terminate at the other end (eg, far end UE 532, server, etc.).

  The PDCP sublayer 514 performs multiplexing between various radio bearers and logical channels. PDCP sublayer 514 also supports header compression for higher layer data packets to reduce radio transmission overhead, security by encrypting data packets, and handover support for UEs between eNBs. provide. RLC sublayer 512 segments and reassembles upper layer data packets, retransmits lost data packets, and reorders data packets to compensate for out-of-order reception due to hybrid automatic repeat request (HARQ) obtain. The MAC sublayer 510 may perform multiplexing between logical channels and transport channels. The MAC sublayer 510 may also allocate various radio resources (eg, resource blocks) in one cell among UEs. The MAC sublayer 510 may also be responsible for HARQ operations. In some usable aspects, user plane signaling from the UE 502 (e.g., MAC 510 layer signaling, RLC 512 layer signaling, PDCP 514 layer signaling) may include some level 2 (L2) protocol 508, user datagram protocol / IP (UDP / IP ) 522, and other protocol layers such as General Packet Radio Service (GPRS) Tunneling Protocol-User Plane (GTP-U) 524 may be carried into the network.

  FIG. 5 further illustrates an example radio protocol architecture 503 for the user plane in LTE to support direct radio communication between UE 502 and UE 532. In an aspect, each layer associated with UE 502 (e.g., layers 520, 518, 514, 512, 510, and 506) may communicate directly with the corresponding layer associated with UE 532, and may be As described in, it may be the same layer used to communicate between UE 502 and eNB 504 in legacy mode.

  In the control plane, the radio protocol architecture for the UE 502 and eNB 504 is substantially the same for the physical L1 layer 506 and the L2 layer, except that there is no header compression function for the control plane. The control plane also includes a radio resource control (RRC) sublayer 516 in the L3 layer. The RRC sublayer 516 may be responsible for obtaining radio resources (ie, radio bearers) and configuring lower layers using RRC signaling between the eNB 504 and the UE 502.

  According to various aspects, FIG. 6 shows an example LTE network entity (e.g., eNB, MME, PDN gateway, CSCF, etc.) 610 that is in direct or indirect communication with the example UE 650, where the UE 650 1 may be UE 102 or 104 in FIG. 1, and LTE network entity 610 may be any entity associated with E-UTRAN 110, EPC 120, etc. in FIG. On the downlink (DL), upper layer packets from the core network are provided to a controller / processor 675 that implements the L2 layer functionality described above. In DL, the controller / processor 675 is responsible for header compression, encryption, packet segmentation and reordering, multiplexing between logical and transport channels, and radio resources to the UE 650 based on various priority measures. Make an allocation. The controller / processor 675 is also responsible for HARQ operations, retransmission of lost packets, and signaling to the UE 650.

  The transmit (TX) processor 616 at the network entity 610 can implement various signal processing functions for the L1 layer (i.e., the physical layer), and the signal processing functions performed at the TX processor 616 are in order at the UE 650. Directional error correction (FEC) and various modulation schemes (e.g. binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M phase shift keying (M-PSK), M quadrature amplitude modulation (M- Coding and interleaving may be included to facilitate mapping to signal constellations based on QAM)). The coded and modulated symbols may then be divided into parallel streams, and each stream is then mapped to OFDM subcarriers to generate a physical channel that carries a time-domain OFDM symbol stream and time It may be multiplexed with a reference signal (eg, pilot) in the domain and / or frequency domain and then combined together using an inverse fast Fourier transform (IFFT). The OFDM stream may be spatially precoded to generate multiple spatial streams. Channel estimates from channel estimator 674 may be used to determine coding and modulation schemes and perform spatial processing. The channel estimate may be derived from a reference signal transmitted by UE 650 and / or channel state feedback. Each spatial stream may then be provided to a different antenna 620 via a separate transmitter TX618, which may each modulate an RF carrier with a respective spatial stream for transmission.

  At UE 650, each receiver RX 654 may receive a signal through a respective antenna 652, recover information modulated on the RF carrier, and provide the modulated information to a receive (RX) processor 656. RX processor 656 may implement various signal processing functions associated with the L1 layer described above. For example, according to various aspects, the RX processor 656 may perform spatial processing on the modulated information to recover any spatial stream destined for the UE 650. If multiple spatial streams are destined for UE 650, RX processor 656 can combine multiple spatial streams into a single OFDM symbol, and RX processor 656 can then use Fast Fourier Transform (FFT). A single OFDM symbol stream can be transformed from the time domain to the frequency domain. The frequency domain signal may comprise a separate OFDM symbol stream for each subcarrier of the OFDM signal. In order to recover and demodulate the symbols and reference signals on each subcarrier, the most likely signal constellation points transmitted from LTE network entity 610 may be determined, and these soft decisions are channel estimates. May be based on a channel estimate calculated in the device 658. The soft decision may then be decoded and deinterleaved to recover the data and control signals that LTE network entity 610 originally transmitted on the physical channel, and the recovered data and recovered control signals are then / May be provided to processor 659.

  According to various aspects, controller / processor 659 may implement the L2 layer described above, and controller / processor 659 may store memory 660 that stores program code, data, and / or other suitable information. May be associated with According to various aspects, memory 660 can be referred to as a computer-readable medium. On UL, the controller / processor 659 performs demultiplexing between transport and logical channels, packet reassembly, decoding, header decompression, and control signal processing to recover higher layer packets from the core network. Can be done. The upper layer packet may then be provided to the data sink 662, which may represent all protocol layers above the L2 layer as described above. Various control signals may be provided to the data sink 662 for L3 processing. The controller / processor 659 may also be responsible for performing error detection using acknowledgment (ACK) and / or negative acknowledgment (NACK) protocols to support HARQ operations.

  In the UL direction, the data source 667 at UE 650 can be used to provide higher layer packets to the controller / processor 659. Data source 667 may represent all protocol layers above the L2 layer as described above. Similar to the functions described above for DL transmission from LTE network entity 610, the controller / processor 659 can implement the L2 layer for the user plane and control plane, which includes header compression, encryption , Packet segmentation and reordering, and functionality for multiplexing between logical and transport channels based on radio resources that the LTE network entity 610 may have allocated. Controller / processor 659 may also be responsible for performing HARQ operations, retransmission of lost packets, and signaling to LTE network entity 610.

  According to various aspects, TX processor 668 can use the channel estimate derived from channel reference 658 from a reference signal and / or feedback transmitted from LTE network entity 610 to provide an appropriate coding and modulation scheme. Can be selected to support spatial processing. Spatial streams generated at TX processor 668 may be provided to different antennas 652 via separate transmitters TX654 that may modulate each RF carrier with the respective spatial stream for transmission.

  The UL transmission may be processed in LTE network entity 610 in a manner similar to that described above for the receiver function at UE 650. Specifically, each receiver RX618 in LTE network entity 610 receives the signal through its respective antenna 620, recovers the modulated information on the RF carrier, and provides the modulated information to RX processor 670. RX processor 670 may implement the L1 layer as described above. The controller / processor 675 may implement the L2 layer, and the controller / processor 675 may be associated with a memory 676 that stores program code, data, and / or other suitable information. Memory 676 may also be referred to as a computer readable medium. On the UL, the controller / processor 675 performs demultiplexing between the transport and logical channels, packet reassembly, decoding, header decompression, and control signal processing to route higher layer packets from the UE650. Can recover. Upper layer packets from the controller / processor 675 may be provided to the core network. The controller / processor 675 may also be responsible for performing error detection using ACK and / or NACK protocols to support HARQ operations and retransmit lost packets and signal to the UE 650.

  According to various aspects, FIG. 7 illustrates that two wireless devices 710, 720 are located close enough to establish an out-of-band D2D connection 750, and either wireless device 710 or wireless device 720 is the other. When synchronizing application data with application server 790 more recently than other wireless devices, two wireless devices 710, 720 may establish and communicate through out-of-band D2D connection 750 to efficiently synchronize application data An exemplary wireless environment 700 is shown.

  More specifically, as shown in FIG. 7, a wireless device 710 can be used by the wireless device 710 to communicate within a wireless environment 700, a near field communication (NFC) radio 711, a wireless wide area network (WWAN). ) Radio 713, Wireless Local Area Network (WLAN) radio 715, and Bluetooth radio 717. For example, as shown in FIG. 7, wireless device 710 can communicate wirelessly with cellular base station 740 over WWAN link 741 using WWAN radio 713. The wireless device 710 can also communicate wirelessly with the Wi-Fi access point 760 over the WLAN link 761 using the WLAN radio 715. In addition, the wireless device 710 can use the Bluetooth radio 717 to communicate wirelessly with the Bluetooth headset 780 and the Bluetooth wearable device 782 via the Bluetooth links 781, 783, and the Bluetooth headset 780 and the Bluetooth wearable device 782 May further be communicating wirelessly with each other via a Bluetooth link 784. Still further, the wireless device 710 can communicate wirelessly with one or more NFC devices in the “near field” of the wireless device 710 using NFC radio 711 via induction of the magnetic field.

  Further, according to various aspects, second wireless device 720 can similarly have multiple radios each operating in accordance with different radio access technologies. For example, as shown in FIG. 7, the second wireless device 720 may also have an NFC radio 721, a WWAN radio 723, a WLAN radio 725, and a Bluetooth radio 727, where the wireless device 720 is within the wireless environment 700. Wireless 721, 723, 725, 727 can be used to communicate over the Internet. For example, as shown in FIG. 7, a wireless device 720 can communicate with a cellular base station 740 through a WWAN link 745 using a WWAN radio 723 and a Wi-Fi access point 760 through a WLAN link 765 using a WLAN radio 725. Bluetooth wireless 727 can be used to communicate wirelessly with Bluetooth headset 785 and Bluetooth wearable device 787 via Bluetooth links 786 and 788, and Bluetooth headset 785 and Bluetooth wearable device 787 can further communicate via Bluetooth link 789. They may be communicating wirelessly with each other. Still further, the wireless device 720 can communicate wirelessly with one or more NFC devices in the “near field” of the wireless device 720 using the NFC radio 721 via induction of the magnetic field. Further, the wireless devices 710, 720 are shown in FIG. 7 as communicating with the same cellular base station 740, where the WWAN links 741, 745 may have a common endpoint, but the wireless devices 710, 720 One skilled in the art will appreciate that in practice, it may be communicating with different cellular base stations via respective WWAN links 741, 745. Similarly, although wireless devices 710, 720 are shown in FIG. 7 as communicating with the same Wi-Fi access point 760, the wireless devices 710, 720 are actually each WLAN link 761, 765. Those skilled in the art will appreciate that they may be communicating with different Wi-Fi access points via

  According to various aspects, WWAN links 741, 745 used by wireless devices 710, 720 to communicate with cellular base station 740, and wireless devices 710, 720 used to communicate with Wi-Fi access point 760. In addition to WLAN links 761, 765, wireless devices 710, 720 may communicate directly with each other through an out-of-band D2D connection 750 if they are located sufficiently close to each other. For example, when the wireless device 710, 720 is within a range of up to about 500 meters, the wireless device 710, 720 may form a D2D link over LTE Direct using the WWAN radio 713, 723. Further, if the wireless devices 710, 720 are within range sufficient to discover each other via the WLAN radios 715, 725, the wireless devices 710, 720 may form a D2D link over Wi-Fi Direct. In other examples, when wireless devices 710, 720 are within a range of operation ranging from a few meters to tens of meters, using Bluetooth radios 717, 727, or within close proximity of each other (e.g., about 10 NFC radio 711, 721 may be used to form a D2D link. However, if the wireless devices 710, 720 are both associated with the same user and run their respective applications 718, 728 (e.g., email applications) associated with the same username and certificate, the existing synchronization algorithms and implementations are Typically, each wireless device 710, 720 individually, without utilizing or considering the fact that the latest account data 719, 729 associated with the applications 718, 728 may be available on the other device in proximity This involves running a synchronization procedure with the corresponding application server 790, which tends to be an inefficient approach for several reasons.

  Thus, in the use case shown in FIG. 7, the wireless devices 710, 720 belong to the same user together, and direct D2D communication (e.g., using WWAN radios 713, 723 over LTE-Direct, WLAN radio 715 (Via Wi-Fi Direct using 725, etc.), and both wireless devices 710, 720 log into the application server 790 with the same user certificate The same applications 718 and 728 are installed. Assuming further that the first wireless device 710 has performed the synchronization procedure with the application server 790 more recently than the second wireless device 720, the second wireless device 720 is also located in close proximity to the first wireless device 720. Rather than utilizing or taking into account the more recently synchronized application data 719 available on the device 710, it is used on the second wireless device 720 through the application server 790 using the WWAN link 745 and / or the WLAN link 765. Synchronizing data associated with a running application 728 can be inefficient. For example, if the second wireless device 720 utilizes the WWAN link 745 to synchronize the application account data 729 through the application server 790, resources may be unnecessarily consumed in the cellular access network, Device 720 consumes more power due to reduced data rate depending on cellular access network load, needs to transmit with more power to close loop with cellular base station 740, etc. There is. Similarly, if the second wireless device 720 communicates with the Wi-Fi access point 760 and synchronizes the application data 729 through the application server 790 via the legacy WLAN link 765, the second wireless device 720 It may be necessary to deal with large round trip time (RTT) delays, reduced data rates depending on backhaul congestion, and so on. Accordingly, as described in further detail herein, the inefficiencies referred to above are not via the legacy cellular link 745 and / or the legacy Wi-Fi link 765, rather than the first wireless device 710. Through the out-of-band D2D connection 750 with the application data 729 synchronized at the second wireless device 720, which improves the performance at the second wireless device 720, It may reduce backhaul congestion and load in the Wi-Fi access network and may allow other users in the same cellular network and / or Wi-Fi access network to achieve higher throughput.

  For example, according to various aspects, the second wireless device 720 initiates a procedure for synchronizing account data 729 associated with an application 728 running thereon, with the last known update being approximately 1 hour Assume that the second wireless device 720 must download 50 MB from the application server 790 in order for the synchronization to succeed since it was executed previously. In this example, the first wireless device 710 in proximity to the second wireless device 720 further performs a procedure for synchronizing the account data 719 associated with the application 718 running thereon with the application server 790. May be assumed to be running more recently, so that the account data 719 currently stored on the first wireless device 710 is current (or stored on the second wireless device 720). Account data 729 at least newer). Thus, under the current synchronization algorithm, the second wireless device 720 downloads the entire 50MB from the application server 790 via the WWAN link 745 and / or the WLAN link 765, and then the second wireless device 720 Utilize the resources of the cellular network and / or Wi-Fi network without utilizing or considering the newer account data 719 available at the first wireless device 710 that performed the synchronization procedure more recently. Thus, according to various aspects described herein, the second wireless device 720 utilizes account data 719 stored on the first wireless device 710 utilizing an out-of-band D2D connection 750. Local application 728 (e.g., via LTE-Direct D2D connection 750 formed between WWAN radios 713, 723, Wi-Fi Direct D2D connection 750 formed between WLAN radios 715, 725, etc.) Associated account data 729 may be intelligently synchronized. Accordingly, the wireless devices 710, 720 each have an identifier associated with the application 718, 728, a username associated with the application 718, 728, and a certificate to determine whether to initiate a synchronization procedure over the out-of-band D2D connection 750. Document and one or more public and / or private “representations” that enclose the last update time associated with the account data 719, 729 may be configured to be broadcast and discovered.

  Therefore, synchronizing the account data 719, 729 through the out-of-band D2D connection 750 is done otherwise, using cellular links 741, 745 and / or Wi-Fi links 761, 765 to communicate with the application server 790. Can be used to avoid inefficient procedures to synchronize account data 719, 729, and this also adds overhead that can occur when using network resources to synchronize account data 719, 729 In addition to reducing, it may add value to WWAN radios 713, 723, WLAN radios 715, 725, and / or other radios that support D2D communications, allowing higher data rates with less RTT delay. Therefore, enabling wireless devices 710, 720 to synchronize account data 719, 729 through out-of-band D2D connection 750 can ensure better performance while minimizing power and resource consumption. This means that the wireless device 710, 720, other end users who do not need to compete with the wireless device 710, 720 for bandwidth or other network resources, traffic offload due to synchronization traffic off-band D2D connection 750 It can be beneficial for network operators and / or service providers who may have less backhaul congestion. In addition, facts such as reduced transmission (Tx) power requirements for synchronizing account data 719, 729 can reduce network interference, and wireless device 710, 720 can consume less battery power By this, all parties can benefit. In addition, the wireless devices 710, 720 are legacy in order to facilitate synchronization of account data 719, 729 via the application server 790, such as when synchronization over the D2D connection 750 fails or times out. It may have the ability to go back to using cellular links 741, 745 and / or legacy Wi-Fi links 761, 765.

  Thus, according to various aspects, FIG. 8 shows an exemplary representation 800 that a wireless device may broadcast and discover to efficiently synchronize application data through an out-of-band D2D connection with a peer wireless device. . In general, the following description may refer to an exemplary representation 800 in the context of LTE-Direct representation to simplify the discussion provided herein. However, the structure and characteristics associated with the representation 800 shown in FIG. 8 and described in more detail herein can be easily adapted to other D2D radio access technologies (e.g., Wi-Fi Direct), Those skilled in the art will appreciate.

  According to various aspects, as described above, LTE Direct (LTE-D, sometimes referred to as “LTE-Advanced”) is a proposed 3GPP for proximity discovery (Release 12). This is a device-to-device (D2D) strategy. LTE-D eliminates location tracking and network calls by directly monitoring services on other LTE-D devices in the long range (approximately 500m in line of sight) and continues to do so in synchronous systems. Doing so provides battery efficiency and the ability to detect thousands of nearby services simultaneously. LTE-D has a wider range than other D2D P2P technologies such as Wi-Fi Direct (WFD) or Bluetooth and operates on the licensed spectrum as a service to mobile applications. LTE-D is a D2D strategy that also enables service layer discovery and D2D communication, where mobile applications on LTE-D devices monitor mobile application services on other devices and at the physical layer (other LTE-D can be instructed to announce locally available services (for detection by services on LTE-D devices), so that LTE-D functions substantially continuously. While the application is closed, the client application is notified when a match with the “monitor” established by the associated application is detected. For example, an application can establish a monitor for a “synchronization event” and the LTE-D discovery layer can launch the application when a synchronization-related LTE-D representation is detected. LTE-D is therefore an attractive alternative for mobile developers seeking to deploy proximity discovery strategies as an extension of their existing cloud services. LTE-D refrains from centralized database processing when mobile applications identify relevance matches, but instead determines associations autonomously at the device level by sending and monitoring relevant attributes It is a distributed discovery strategy (as opposed to the centralized discovery that exists today). LTE-D offers some benefits in terms of privacy and power consumption in that LTE-D does not use persistent location tracking to determine proximity. By continuing discovery on the device rather than in the cloud, the user has more control over what information is shared with the external device.

  LTE-D generally uses “representation” to both discover neighboring peers and facilitate communication between neighboring peers. In LTE-D, expressions in the application layer and / or service layer are called “expression names” (for example, ShirtSale@Gap.com, Jane@Facebook.com, etc.) and are expressed in the application layer and / or service layer. Are mapped to a bit string called “expression code” in the physical layer. In one example, each representation code may have a length of 192 bits (eg, “11001111 ... 1011”, etc.). As will be appreciated, any reference to a particular expression may refer to the associated expression name, expression code, or both, depending on the context, and the expression may be private or public based on the mapping type. It can be either. Thus, while public expressions can be published and identified by any application, private expressions are targeted to a specific audience. Discovery in LTE-D operates synchronously based on parameters configured by the LTE network. For example, frequency division duplex (FDD) and / or time division duplex (TDD) may be assigned by a serving eNB via a session information block (SIB). The serving eNB may also configure an interval (eg, every 20 seconds, etc.) at which the LTE-D device should announce itself via transmission of a service discovery (or P2P discovery) message. For example, in the case of a 10 MHz FDD system, the eNB is 44 physical uplink shared channel (PUSCH) radio bearers (RB) to be used for discovery according to a discovery period that occurs every 20 seconds and includes 64 subframes. Therefore, the number of directly discovered resources (DRID) is 44 × 64 = 2816.

  In at least one embodiment, after two or more LTE-D devices want to discover each other and establish an LTE-D session for communication, the LTE network is referred to herein as a network-assisted connection. It may be asked to authorize the establishment of an LTE-D session, called setup. If the LTE network authorizes the LTE-D session, the actual media is exchanged via D2D communication between the LTE-D devices, where the peer device with LTE-D capability is a proximity service, application, and context The representation can be used to discover and direct D2D communication can be established in an efficient manner.

  Thus, according to various aspects, FIG. 8 illustrates that two or more LTE-D devices can discover LTE-D devices and establish appropriate out-of-band D2D connections with LTE-D sessions. 2 illustrates an example structure associated with an LTE-D representation 800 that may be broadcast. In various embodiments, each LTE-D device may broadcast and / or discover LTE-D representation 800 at regular intervals (eg, every 20 seconds) and serving eNB associated with LTE-D. May configure the periodic interval via a service discovery message, a P2P discovery message, or other suitable message. In various embodiments, as shown in FIG. 8, the LTE-D representation 800 includes a phenotype field 810 having 6 bits, an expression code field 820 having 192 bits, and a cyclic redundancy check (CRC) having 24 bits. ) Field 830. In general, the phenotype field 810, the expression code field 820, and the CRC field 830 may be encoded as a single coding block through a convolutional encoder. Further, in various embodiments, the expression code field 820 may comprise a unique identifier 822 associated with the broadcasting LTE-D device and one or more content fields that may include other suitable data.

  For example, the use case described above, where two wireless devices located close enough to each other form a D2D connection to synchronize data associated with an application that uses the same username and user certificate In FIG. 8, the content field in the LTE-D representation 800 includes an application name 824 used to identify a particular application, a user certificate field 826 containing a user certificate associated with the application, and a representation. And a last synchronization time field 828 that indicates the last time that the wireless device broadcasting 800 synchronized the data associated with the application. Thus, other nearby peer wireless devices can discover the broadcast LTE-D representation 800 and determine whether any nearby devices have newer synchronization data associated with the application. If so, the discovering wireless device and the broadcasting wireless device are appropriate instead of communicating through legacy cellular networks and / or Wi-Fi networks to synchronize application data through application servers located on the network A simple D2D connection and application data can be synchronized through the D2D connection.

  According to various aspects, FIGS. 9A-9B illustrate an example synchronization procedure 900 that a wireless device may perform to synchronize application data through an out-of-band D2D connection with a peer wireless device. More specifically, at block 910, a request to register for D2D-based application synchronization may be received from one or more applications running on the wireless device, and the D2D-based application synchronization Only registered applications may be allowed to synchronize data associated with the application through out-of-band D2D connections. According to various aspects, the wireless device can then create a local native representation associated with the application registered at block 912, where the local native representation is at least a name, one or more user certificates. , And data associated with the application may comprise the last time synchronized with the network application server. The wireless device can then add its local named representation to a named list that contains local named representations associated with each application registered for D2D-based application synchronization, which is optionally faster Can be stored in cache memory for secure access. The wireless device can then broadcast each local specific expression in the specific expression list during the next discovery period at block 914, and the wireless device can further broadcast one or more other adjacent ones. Expressions that the wireless device broadcasts during the next discovery period can be monitored.

In various embodiments, the wireless device may then determine at block 916 whether any potential peer device has been detected. If a potential peer device is not detected, at block 926, the wireless device waits until the next discovery period to rebroadcast and close each local specific expression in the specific expression list. The peer device discovery process may be retried by monitoring expressions broadcast by one or more other wireless devices. However, if one or more potential peer devices are detected at block 916, then at block 918, the wireless device then maintains information associated with the unique representation discovered during the discovery period and other Compare the specific expressions received from the peer device to the local specific expressions in the list of specific expressions stored on the wireless device, and any specific expressions received from the potential peer device will be It can be determined whether it matches any local specific expression. If no match is found between the unique expression received from the potential peer device and the local one in the list of unique expressions, at block 926, the wireless device waits until the next discovery period. Broadcast each local specific expression in the specific expression list again and retry the peer device discovery process by monitoring the expression broadcast by one or more other wireless devices in proximity . However, in response to finding at least one arbitrary specific expression received from a potential peer device that matches the local specific expression in the specific expression list, at block 920, the wireless device then matches. The details associated with the application and associated timing information may be extracted from the representation to be. For example, according to various aspects, the extracted details associated with an application may include at least a name and a user certificate, which are registered applications on the wireless device. Can be verified to ensure that it matches. In addition, the associated timing information may comprise the last time (T _T-last ) that the sending device performed a synchronization procedure or other suitable procedure to obtain updated data from the application server on the network .

According to various aspects, if the application details extracted from the matching representation indicate the same application name and user certificate associated with the application registered with the D2D-based account synchronization service, at block 922, the wireless device Then the last time that the sending device performed the synchronization procedure with the network application server (T _T-last ) and the _last time that the receiving wireless device performed the synchronization procedure with the network application server (T _R-last ) You can compare. Accordingly, in response to the determination in block 922 that the transmitting device has performed synchronization procedures with the network application server more recently than the receiving wireless device (i.e., T _T-last is less than T _R-last ), block 924 The wireless device may store information associated with the peer device and information suitable for establishing a D2D connection with the peer device. For example, in various embodiments, the wireless device may include information associated with the peer device, information suitable for establishing a D2D connection with the peer device, and a name and user corresponding to the application associated with the matching expression. The certificate may be added to the appropriate device list. The wireless device can then refer to the appropriate device list, which can be used when necessary (e.g., the application automatically initiates the synchronization procedure, the user manually initiates the synchronization procedure) In order to quickly establish a D2D connection (such as in response), it can optionally be stored in cache memory for faster access. However, a block that the transmitting device has performed a synchronization procedure with the network application server (ie, T _T-last is greater than or equal to T _R-last ) at substantially the same time as the receiving wireless device or more recently. In response to the determination at 922, at block 926, the wireless device may wait until the next discovery period and retry the peer device discovery process during the next discovery period.

  Referring now to FIG. 9B, at some later time, the wireless device may receive a D2D-based account synchronization request from a registered application at block 930. For example, in various embodiments, an application can initiate a synchronization procedure automatically (e.g., at regular intervals, based on some trigger event, etc.), or a user can manually initiate a synchronization procedure be able to. In any case, the wireless device can then determine at block 932 whether the appropriate device list stored on the wireless device is empty, and if so, at block 946, the application data is Can be simply synchronized with the network application server using a legacy cellular link and / or Wi-Fi link (e.g., a suitable peer device in close proximity that has performed synchronization procedures with the network application server more recently) Since there is no). On the other hand, in response to the determination in block 932 that the appropriate device list is not empty, the wireless device selects a first appropriate peer device from the list and application data through a D2D connection with the selected peer device. You can try to synchronize.

More specifically, when attempting to synchronize application data over a D2D connection with a selected peer device, at block 934, the wireless device sets a synchronization update timer (T _update ) and a synchronization response timer (T _response ). Synchronous update timers and synchronous response timers can be started, as will be apparent to those skilled in the art, real-time timers, timers based on system clocks, and / or any other suitable timer or combination of timers Can be provided. The wireless device then sends a synchronization request to the selected peer device from the appropriate device list stored on the wireless device at block 936 and whether a response has been received from the selected peer device at block 938. Can be determined. If no response has been received from the selected peer device, at block 940, the wireless device can determine whether a synchronization response timer (T _response ) has expired and, if so, method 900 Can return to block 932. At that point, the wireless device may synchronize application data with the network application server using the legacy cellular link and / or Wi-Fi link at block 946 if the appropriate device list is empty, or Either select the next appropriate peer device from the device list and attempt to synchronize application data through a D2D connection with the next appropriate peer device in the same manner as described herein possible. However, in response to the determination in block 940 that the synchronization response timer (T _response ) has not expired, the wireless device can again check whether a response has been received in block 938 and the method 900 can include: Blocks 938, 940 may be repeated until a response is received or until the synchronization response timer (T _response ) expires.

Thus, assuming that the wireless device receives a response from the currently selected peer device, at block 942, the wireless device then proceeds while the application is attempting to synchronize application data through a D2D connection with the peer device. Can wait. If the synchronization procedure succeeds in downloading the latest updated application data through a D2D connection with the peer device, the method 900 may end properly. However, while waiting for the application to complete the synchronization procedure through the D2D connection, at block 944, the wireless device can periodically check whether the synchronization update timer (T _update ) has expired. If expired, the wireless device may synchronize application data with the network application server. However, in response to the determination in block 944 that the synchronization update timer (T _update ) has not expired, the wireless device waits in block 942 while the application synchronizes data over the D2D connection with the peer device. The method 900 may repeat blocks 942, 944 until the D2D-based synchronization procedure is complete, or until the synchronization update timer (T _update ) expires.

  According to various aspects, FIGS. 10A-10B illustrate an example asynchronous procedure 1000 that a wireless device may perform to synchronize application data through an out-of-band D2D connection with a peer wireless device. In general, the asynchronous procedure 1000 determines that application data when a wireless device discovers a potential suitable peer device rather than repeating the appropriate device list after receiving an explicit synchronization request from the application and / or user. May be substantially similar to the synchronization procedure described above. More specifically, at block 1010, the wireless device can similarly receive a request from one or more applications running on the wireless device to register for D2D-based application synchronization, and D2D Only applications registered for base application synchronization may be allowed to synchronize data associated with the application through an out-of-band D2D connection. According to various aspects, the wireless device can then create a local native representation associated with the application registered at block 1012, where the local native representation is a name, one or more user certificates, And the last time that data associated with the application was synchronized with the network application server. The wireless device can then add its local named representation to a named list that contains local named representations associated with each application registered for D2D-based application synchronization, which is optionally faster Can be stored in cache memory for secure access. The wireless device may then broadcast each local unique representation in the unique representation list during the next discovery period at block 1014, and the wireless device may further be notified by other neighboring wireless devices Expressions that are broadcast during the discovery period can be monitored.

In various embodiments, the wireless device may then determine at block 1016 whether any potential peer device has been detected. If no potential peer device is detected, at block 1026, the wireless device waits until the next discovery period to rebroadcast and close each local named entity in the named list The peer device discovery process may be retried by monitoring expressions broadcast by one or more other wireless devices. However, if one or more potential peer devices are detected at block 1016, at block 1018, the wireless device tracks the specific expressions discovered during the discovery period and other Compare the specific expressions received from the peer device with the local specific expressions in the specific expression list, and any specific expressions received from the potential peer device can be any local specific expressions in the specific expression list. Can be determined. If no match is found between the unique expression received from the potential peer device and the local one in the list of unique expressions, at block 1026, the wireless device waits for the next discovery period. Broadcast each local specific expression in the specific expression list again and retry the peer device discovery process by monitoring the expression broadcast by one or more other wireless devices in proximity . However, in response to finding at least one arbitrary specific expression received from a potential peer device that matches a local specific expression in the specific expression list, the wireless device then matches in block 1020 The details associated with the application and associated timing information may be extracted from the representation to be. For example, according to various aspects, the extracted details associated with an application may include at least a name and a user certificate, which are registered applications on the wireless device. Can be verified to ensure that it matches. In addition, the associated timing information may comprise the last time (T _T-last ) that the sending device performed a synchronization procedure or other suitable procedure to obtain updated data from the application server on the network .

According to various aspects, if the application details extracted from the matching representation indicate the same application name and user certificate associated with the application registered with the D2D-based account synchronization service, at block 1022, the wireless device Then the last time that the sending device performed the synchronization procedure with the network application server (T _T-last ) and the _last time that the receiving wireless device performed the synchronization procedure with the network application server (T _R-last ) You can compare. Accordingly, in response to the determination in block 1022 that the sending device has performed synchronization procedures with the network application server more recently than the receiving wireless device (i.e., T _T-last is less than T _R-last ), As described more fully, the method 1000 may proceed to the flow shown in FIG. 10B. However, a block that the transmitting device has performed a synchronization procedure with the network application server (ie, T _T-last is greater than or equal to T _R-last ) at substantially the same time as the receiving wireless device or more recently. In response to the determination at 1022, at block 1026, in a manner similar to that described above, the wireless device waits for the next discovery period and re-starts the peer device discovery process during the next discovery period. You can try.

Referring now to FIG. You can try to synchronize. More specifically, when attempting to synchronize application data over a D2D connection with a sending peer device, at block 1034, the wireless device initiates a synchronization update timer (T _update ) and a synchronization response timer (T _response ). The sync update timer and sync response timer may comprise a real time timer, a timer based on the system clock, and / or any other suitable timer or combination of timers, as will be apparent to those skilled in the art. obtain. The wireless device may then request updated application data from the peer device at block 1036 and determine at block 1038 whether a response has been received from the selected peer device. If no response has been received from the selected peer device, at block 1040, the wireless device can determine whether a synchronization response timer (T _response ) has expired, and if so, block 1046. In, a wireless device can synchronize application data with a network application server using a legacy cellular link and / or Wi-Fi link. However, in response to the determination in block 1040 that the synchronization response timer (T _response ) has not expired, the wireless device can again check whether a response has been received in block 1038 and the method 1000 can include: Blocks 1038, 1040 may be repeated until a response is received or until the synchronization response timer (T _response ) expires.

Thus, assuming that the wireless device receives a response from the peer device at some point prior to the expiration of the synchronization response timer (T _response ), at block 1042, the wireless device then selects the application through a D2D connection with the peer device. While trying to synchronize data, it can wait. If the synchronization procedure succeeds in downloading the latest updated application data through a D2D connection with the peer device, the method 1000 may finish properly. However, while waiting for the application to complete the synchronization procedure over the D2D connection, at block 1044, the wireless device can periodically check whether the synchronization update timer (T _update ) has expired. . If the synchronization update timer (T _update ) expires at block 1044 before the application completes the synchronization procedure over the D2D connection, at block 1046, the wireless device may synchronize application data with the network application server. Otherwise, prior to expiration of the synchronization update timer (T _update ), the method 1000 may block 1042 until the application completes the synchronization procedure with the peer device or until the synchronization update timer (T _update ) expires. , 1044 can be repeated.

  In accordance with various aspects, FIG. 11 illustrates an example that may support out-of-band D2D communication that can be used to efficiently synchronize application data in accordance with various aspects and embodiments described herein. UE1100A and 1100B are shown. Referring to FIG. 11, UE 1100A is shown as a mobile phone and UE 1100B is shown as a touch screen device (eg, smartphone, tablet computer, etc.). As shown in FIG. 11, the outer casing of UE 1100A includes, inter alia, antenna 1105A, display 1110A, at least one button 1115A (e.g., power button, volume control button, PTT button, as is known in the art. And the like, and keypad 1120A. The UE1100B also includes, among other things, a touch screen display 1105B, peripheral buttons 1110B, 1115B, 1120B, and 1125B (e.g., power control buttons, volume or vibration control buttons, airplane mode toggle buttons, as known in the art. Etc.) and an outer casing comprised of components such as at least one front panel button 1130B (eg, home button, etc.). Further, although not explicitly shown in FIG. 11, the UE 1100B is not limited to a Wi-Fi antenna, a cellular antenna, a satellite positioning system (SPS) antenna (e.g., a global positioning system (GPS) antenna) May include one or more external antennas and / or one or more integrated antennas that may be incorporated into an outer casing associated with UE 1100B.

  Although UE 1100A, 1100B may have internal components that may be implemented according to different hardware configurations, the basic high-level UE configuration for internal hardware components is shown in FIG. 11 as platform 1102. Has been. Specifically, according to various aspects, platform 1102 is installed on operator IP service 140, the Internet, and / or other remote servers and networks (eg, UE 1100A, 1100B using the same username and certificate) Software applications, data, and / or commands transmitted from the access network that may eventually come from the application server associated with the application being executed). Platform 1102 can also run locally stored applications independently without interacting or communicating with the access network and / or out-of-band D2D with another UE located sufficiently close to the access network Processing functions related to communication can be supported. Platform 1102 may include a transceiver 1106 operably coupled to an application specific integrated circuit (ASIC) 1108 or another suitable processor, microprocessor, logic circuit, and / or data processing device. The ASIC 1108 and / or other suitable processor may execute an application programming interface (API) 1110 layer, which may interface with any suitable program that resides in the memory 1112. According to various aspects, the memory 1112 comprises read only memory (ROM), random access memory (RAM), EEPROM, flash card, and / or any other suitable memory that is common to computer platforms. obtain. Platform 1102 may also include a local database 1114 that may store applications not actively used in memory 1112 as well as other suitable data. Local database 1114 may typically be a flash memory cell, but may be any secondary storage device known in the art, such as magnetic media, EEPROM, optical media, tape, soft disk or hard disk. .

  Thus, one embodiment disclosed herein may include a UE (eg, UE 1100A, 1100B, etc.) that includes the ability to perform the functions described herein. As those skilled in the art will appreciate, the various logic elements are discrete elements, software modules executing on a processor, or any combination of software and hardware to implement the functions disclosed herein. Can be embodied in. For example, ASIC 1108, memory 1112, API 1110, and local database 1114 may all be used cooperatively to load, store, and execute various functions disclosed herein, and thus The logic for performing these functions may be distributed among various elements. Alternatively, the functionality can be incorporated into one separate component. Accordingly, the features associated with UEs 1100A, 1100B shown in FIG. 11 are to be considered merely exemplary and the present disclosure is not limited to the features or configurations shown here.

  Wireless communication between UE1100A and 1100B, between UE1100A, 1100B, and access networks, and / or between UE1100A, 1100B, and other appropriate network entities is not limited to CDMA, W-CDMA, sometimes To a variety of different technologies, which may include division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiplexing (OFDM), GSM, or other protocols that may be used in wireless or data communication networks Can be based. As discussed above and as known in the art, voice transmissions and / or data may be transmitted from the access network to UE 1100A, 1100B using various networks and configurations. Accordingly, the illustrations provided herein are not intended to limit the embodiments disclosed herein, but merely to assist in the description of the various aspects and embodiments provided herein. Absent.

  According to various aspects, FIG. 12 illustrates an example apparatus 1200 that can support efficient application data synchronization using out-of-band D2D communication, according to various aspects and embodiments described herein. 2 illustrates an exemplary conceptual data flow between various modules, means, and / or components.

  In various embodiments, the apparatus 1200 can include a receiving module 1210 that can receive a representation from the second UE 1260, where the received representation is a name associated with the application, one or more associated with the application, or It may include the last time the second UE 1260 synchronized multiple user certificates and account data associated with the application. In addition, the receiving module 1210 may further receive signaling and data from a current base station or other access point 1270 associated with legacy cellular links and / or Wi-Fi links. Thus, the representation received from the second UE 1260 matches the application registered for D2D-based account synchronization, and the last time the second UE 1260 synchronized the account data associated with the application is In response to determining that the representation indicates that the account data associated with the application is more recent than the last time device 1200 synchronized, device 1200 establishes a D2D connection with a second UE 1260. The D2D communication module 1230 may be used to attempt to synchronize application data using more recent application account data stored on the second UE 1260 over the D2D connection. Alternatively, if the representation received from the second UE 1260 does not match any application registered for D2D-based account synchronization on the device 1200, or the account data associated with the application is second If the received representation indicates that the last time that the UE 1260 synchronized was not more recent than the last time the device 1200 synchronized account data, the device 1200 may use the legacy communication module 1220. Application data may be synchronized using the latest data stored in the application server 1280 via the access point 1270. In a further alternative, if the attempt to synchronize application data using the more recent application account data stored in the second UE 1260 using the D2D communication module 1230 fails, times out, or otherwise If not successful, the device 1200 may use the legacy communication module 1220 to synchronize application data using the latest data stored on the application server 1280 via the access point 1270. In various embodiments, the apparatus 1200 can further transmit information associated with the D2D link and / or legacy link with the access point 1270 directly to the second UE 1260 using the D2D link. The transmission module 1250 may further transmit information associated with the D2D link and / or the legacy link to the access point 1270 using the legacy link. Further, those skilled in the art will appreciate that the second UE 1260 may include similar components as the device 1200, so that the device 1200 and the second UE 1260 can synchronize application data on the second UE 1260. Between which the application data stored in the device 1200 was more recently updated than the application data stored in the second UE 1260.

  Apparatus 1200 may include additional modules that perform each of the steps of the efficient out-of-band D2D-based application synchronization procedure described above. Thus, a module can perform each step in the aforementioned out-of-band D2D-based application synchronization procedure, and the device 1200 can include one or more of such modules. The module is particularly adapted to execute a described process / algorithm implemented by a processor configured to execute the described process / algorithm stored in a computer readable medium for implementation by the processor. There may be one or more configured hardware components, or some combination thereof.

  In accordance with various aspects, FIG. 13 illustrates an example corresponding to a wireless device 1300 that can support efficient application data synchronization using an out-of-band D2D connection in accordance with various aspects and embodiments described herein. A typical hardware implementation is shown. In various embodiments, wireless device 1300 may comprise a processing system implemented using a bus architecture generally represented by bus 1390. Bus 1390 may include any number of interconnecting buses and bridges depending on the specific application of wireless device 1300 and the overall design constraints. Bus 1390 is represented by one or more processors and / or hardware represented by processor 1360, computer readable medium 1370, receive module 1310, legacy communication module 1320, D2D communication module 1330, application synchronization module 1340, and transmit module 1350. Various circuits, including wear modules, are connected together. Bus 1390 may also connect various other circuits, such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and thus No further explanation.

  In various embodiments, the wireless device 1300 can further comprise a transceiver 1380 that can be coupled to one or more antennas 1382. The transceiver 1380 may provide a means (eg, LTE Direct modem, Wi-Fi Direct modem, etc.) for communicating with various other devices over a transmission medium. The wireless device 1300 includes a processor 1360 coupled to a computer readable medium 1370, which may be responsible for general processing, including the execution of software stored on the computer readable medium 1370. When executed by the processor 1360, the software may cause the processor 1360 to perform various functions described in further detail above for any particular device. The computer-readable medium 1370 may also be used for storing data that can be manipulated by the processor 1360 when executing software. The wireless device 1300 further includes at least one of a reception module 1310, a legacy communication module 1320, a D2D communication module 1330, an application synchronization module 1340, and a transmission module 1350. A module may be a software module that runs on processor 1360 resident / stored in computer readable medium 1370, one or more hardware modules coupled to processor 1360, or some combination thereof. The wireless device may further correspond to a UE and other suitable components as described herein (e.g., memory, TX processor, RX processor, controller, as shown for UE 610 in FIG. 6). / Processor etc.).

  In various embodiments, the device 1000 shown in FIG. 10 and the wireless device 1100 shown in FIG. 11 can communicate with a name, one or more user certificates, and a device-to-device (D2D) based application data synchronization service. Means for generating a local representation, including the last update time associated with the registered application, and received and registered from one or more other devices in proximity to the first device A means for finding one or more external named entities that match the current application, and one or more other devices that are more recent than the last update time associated with the local named entity Means to identify the update device associated with the external entity including the last update time, and update via out-of-band D2D connection Means for requesting an update to synchronize application data associated with a registered application from the new device. In various embodiments, the means referred to above are shown in FIG. 11 UE 1100A, 1100B shown in FIG. 11, configured or configurable to perform the functions listed for the aforementioned means. Device 1200 and / or one or more of the aforementioned modules of the wireless device 1300 shown in FIG. As noted above, the wireless device may further include a number of components associated with the UE 610 shown in FIG. 6, so that in one example, the means referred to above are referred to above. May comprise a TX processor 668, an RX processor 656, a controller / processor 659, and / or other components configured or configurable to perform the functions listed for the means recited.

  Those of skill in the art will appreciate that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the above description are voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, light fields or light particles, or any of them. Can be represented by a combination.

  Further, those skilled in the art will appreciate that the various exemplary logic blocks, modules, circuits, and algorithm steps described in connection with the aspects disclosed herein may be implemented as electronic hardware, computer software, or combinations thereof. Will be understood. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functions are implemented as hardware or software depends on the specific application and design constraints imposed on the overall system. Those skilled in the art may implement the described functionality in a variety of ways for each specific application, but such implementation decisions should not be construed as departing from the scope of the present disclosure.

  Various exemplary logic blocks, modules, and circuits described in connection with aspects disclosed herein include general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays ( FPGA) or other programmable logic device, individual gate or transistor logic, individual hardware components, or any combination thereof designed to perform the functions described herein. obtain. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor is also implemented as a combination of computing devices (e.g., a DSP and microprocessor combination, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration). obtain.

  The methods, sequences, and / or algorithms described with respect to aspects disclosed herein may be implemented directly in hardware, in software modules executed by a processor, or in combinations thereof. A software module may reside in RAM, flash memory, ROM, EPROM, EEPROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium can reside in an ASIC. An ASIC may reside in a wireless device (eg, an IoT device). In the alternative, the processor and the storage medium may reside as discrete components in a user terminal.

  In one or more exemplary aspects, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can be RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage device, or any desired form in the form of instructions or data structures. Any other medium that can be used to carry or store the program code and be accessed by a computer can be included. Also, any connection is properly termed a computer-readable medium. For example, if the software is sent from a website, server, or other remote source using coaxial technology, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, wireless, and microwave, Wireless technologies such as fiber optic cable, twisted pair, DSL, or infrared, radio, and microwave are included in the media definition. Discs and discs used in the present specification include CDs, laser discs, optical discs, DVDs, floppy discs, and Blu-ray discs. ) Usually reproduces data magnetically and / or optically using a laser. Combinations of the above should also be included within the scope of computer-readable media.

  While the above disclosure represents exemplary embodiments of the present disclosure, various changes and modifications may be made herein without departing from the scope of the present disclosure as defined by the appended claims. Those skilled in the art will appreciate that. The functions, steps and / or activities of method claims according to aspects of the present disclosure described herein need not be performed in any particular order. Further, although elements of the disclosure may be described or claimed in the singular, the plural is contemplated unless expressly stated to be limited to the singular.

100 EPS
102 First user equipment
104 Second user equipment
110 E-UTRAN
112 eNB ₁
114 eNB ₂
120 EPC
122 MME
124 Other MME
126 Serving gateway
128 PDN gateway
130 MBMS GW
132 BM-SC
135 HSS
140 Provider IP Service
200 access network
220 Network link
222 Legacy Cellular Link
224 links
230 1st cell
232 1st base station
234 UE
236 UE
238 UE
240 Second cell
242 2nd base station
244 UE
246 UE
248 UE
254 Dashed link
256 D2D link
270 Application Server
300 Downlink frame structure
302 Resource element
304 Resource element
306 subframe
308 slots
310 Resource Block
312 RTS block
314 CTS block
316 connection identifier
400 uplink frame structure
410 Resource Block
412 Resource block
420 resource block
422 resource block
430 physical random access channel
501 Control plane radio protocol architecture
502 UE
503 Wireless Protocol Architecture
504 eNB
506 Physical layer
508 L2 protocol
510 MAC sublayer
512 RLC sublayer
514 PDCP sublayer
516 RRC sublayer
518 Network layer
520 Application layer
522 UDP / IP
524 GTP-U
526 SWG
530 PDN gateway
532 UE
610 LTE network entity
616 TX processor
618 transmitter
620 antenna
650 UE
652 Antenna
654 receiver
656 RX processor
658 channel estimator
659 Controller / Processor
660 memory
662 Data Sync
667 data sources
668 TX processor
670 RX processor
674 channel estimator
675 Controller / Processor
676 memory
700 wireless environment
710 devices 1
711 NFC radio
713 WWAN wireless
715 WLAN radio
717 Bluetooth wireless
718 Application
719 account data
720 devices 2
721 NFC wireless
723 WWAN wireless
725 WLAN radio
727 Bluetooth wireless
728 Application
729 account data
740 Cellular Base Station
741 WWAN link
745 WWAN link
750 D2D link
760 Wi-Fi access point
761 WLAN link
765 WLAN link
780 Bluetooth headset
781 Bluetooth link
782 Wearable device for Bluetooth
783 Bluetooth link
784 Bluetooth link
785 Bluetooth headset
786 Bluetooth link
787 Wearable device for Bluetooth
788 Bluetooth link
789 Bluetooth link
790 application server
800 expressions
810 phenotype field
820 Expression code field
822 unique identifier
824 Application name
826 User certificate field
828 Last Sync Time field
830 CRC field
900 synchronization steps
1000 asynchronous procedures
1100A UE
1100B UE
1102 platform
1105A antenna
1105B antenna
1106 transceiver
1108 ASIC
1110 API
1110A UE
1110B UE
1112 memory
1114 Local database
1115A button
1115B Peripheral button
1120A keypad
1120B Peripheral button
1125B Peripheral button
1130B Front panel button
1200 equipment
1210 Receiver module
1220 Legacy communication module
1230 D2D communication module
1240 Application synchronization module
1250 transmitter module
1260 2nd UE
1270 access point
1280 Application server
1300 wireless devices
1310 Receiver module
1320 Legacy communication module
1330 D2D communication module
1340 Application synchronization module
1350 Transmitter module
1360 processor
1370 Computer-readable media
1380 transceiver
1382 Antenna
1390 bus

Claims (30)

A method for device-to-device (D2D) application synchronization,
Generating a local specific representation on a first device, including a name associated with an application registered with a D2D-based application data synchronization service, one or more user certificates, and a last update time;
At the first device, received from one or more peer devices proximate to the first device and matches the name and the one or more user certificates associated with the registered application Detecting one or more external named entities; and
Identifying, from among the one or more peer devices, an update device associated with an external specific expression that includes a last update time that is more recent than the last update time associated with the local specific expression;
Requesting an update to synchronize the application data associated with the registered application from the update device through an out-of-band D2D connection. Requesting the update to synchronize the application data over the D2D connection, starting one or more timers;
The method further comprises synchronizing the application data using updated data received from the update device over the D2D connection while the one or more timers have not expired. the method of.   3. The method of claim 2, further comprising synchronizing the application data associated with the registered application from a network server in response to determining that the one or more timers have expired.   The method of claim 1, wherein upon finding the external named representation including the more recent last update time, the update to synchronize the application data is requested from the update device. Maintaining a D2D device list at the first device, wherein the D2D device list matches the name associated with the registered application and the one or more user certificates. Comprising one or more potential update devices received therefrom;
The method of claim 1, further comprising: adding the update device to the D2D device list maintained at the first device. Requesting the update to synchronize the application data associated with the registered application;
Selecting the update device from the D2D device list;
Requesting the update to synchronize the application data from the update device, and starting a response timer and an update timer;
If the update device responds to the update request before the response timer expires, the updated data received from the update device over the D2D connection while the update timer has not expired is used. 6. The method of claim 5, further comprising synchronizing application data. Requesting the update to synchronize the application data associated with the registered application;
The application data associated with the registered application through an out-of-band D2D connection with the next update device selected from the D2D device list if the response timer expires before the update device responds to the update request Requesting the update to synchronize
Resuming the response timer upon requesting the update to synchronize the application data from the next update device;
If the next update device responds to the update request before the resumed response timer expires, updated data received from the update device over the D2D connection while the update timer has not expired 7. The method of claim 6, further comprising synchronizing the application data using.   The method of claim 6, further comprising synchronizing the application data associated with the registered application from a network server when the update timer expires.   The method of claim 1, further comprising constraining the D2D-based application data synchronization service to applications registered with the D2D-based application data synchronization service. Broadcasting the local specific expression associated with the registered application;
Receiving a request to update the application data associated with the registered application through a second D2D connection from a second device of the one or more peer devices, the local device comprising: The last update time in the specific representation of is more recent than the last update time in the external specific representation received from the second device; and
The method of claim 1, further comprising: sending updated data associated with the application to the second device through the second D2D connection. A wireless device,
Configured to broadcast a local unique representation, including name, one or more user certificates, and last update time associated with an application registered with a device-to-device (D2D) based application data synchronization service A transmitter,
A receiver configured to receive one or more external specific representations from one or more peer wireless devices proximate to the wireless device;
One or more processors, the one or more processors,
Detecting that the one or more external specific expressions match the name and the one or more user certificates associated with the registered application;
Identifying an update device associated with an external specific representation that includes a last update time more recent than the last update time associated with the local specific representation among the one or more peer wireless devices;
A wireless device configured to request an update to synchronize the application data associated with the registered application from the update device through an out-of-band D2D connection. The one or more processors further comprises:
Requesting the update to synchronize the application data through the D2D connection, start one or more timers;
12.The device is configured to synchronize the application data using updated data received from the update device over the D2D connection while the one or more timers have not expired. Wireless devices.   The one or more processors are further configured to synchronize the application data associated with the registered application from a network server in response to expiration of the one or more timers. 12. The wireless device according to 12. The one or more processors further comprises:
Maintaining a D2D device list in the first device, wherein the D2D device list matches the name associated with the registered application and the one or more user certificates Comprising one or more potential update devices from which are received, and
Adding the updated device to the D2D device list maintained in the first device;
Selecting the update device from the D2D device list;
Requesting the update to synchronize the application data from the update device, starting a response timer and an update timer;
If the update device responds to the update request before the response timer expires, the updated data received from the update device over the D2D connection while the update timer has not expired is used. 12. The wireless device of claim 11, wherein the wireless device is configured to synchronize application data. The one or more processors further comprises:
Associate with the registered application through an out-of-band D2D connection with the next update device selected from the D2D device list in response to the response timer expiring before the update device responds to the update request Requesting the update to synchronize the application data
Resuming the response timer upon requesting the update to synchronize the application data from the next update device;
If the next update device responds to the update request before the resumed response timer expires, updated data received from the update device over the D2D connection while the update timer has not expired 15. The wireless device of claim 14, wherein the wireless device is configured to use to synchronize the application data.   15. The wireless device of claim 14, wherein the one or more processors are further configured to synchronize the application data associated with the registered application from a network server when the update timer expires.   12. The wireless device of claim 11, wherein the one or more processors are further configured to constrain the D2D-based application data synchronization service to applications registered with the D2D-based application data synchronization service. The receiver further receives a request to update the application data associated with the registered application through a second D2D connection from a second device of the one or more peer wireless devices. The last update time in the local entity is more recent than the last update time in the external entity received from the second device;
12. The wireless device of claim 11, wherein the transmitter is further configured to transmit updated data associated with the application to the second device over the second D2D connection. A device,
Means for generating a local unique representation, including a name, one or more user certificates, and a last update time associated with an application registered with a device-to-device (D2D) based application data synchronization service;
One or more external uniques received from one or more peer devices proximate to the device and that match the name and the one or more user certificates associated with the registered application Means for detecting the expression;
Means for identifying, from among the one or more peer devices, an update device that is associated with an external specific expression that includes a last update time that is more recent than the last update time associated with the local specific expression;
Means for requesting an update to synchronize the application data associated with the registered application from the update device through an out-of-band D2D connection. Means for initiating one or more timers upon requesting the update to synchronize the application data over the D2D connection;
Means for synchronizing the application data using updated data received from the update device over the D2D connection while the one or more timers have not expired. The device described in 1.   21. The apparatus of claim 20, further comprising means for synchronizing the application data associated with the registered application from a network server in response to the one or more timers expiring. A D2D device list comprising one or more potential update devices from which the name associated with the registered application and an external specific representation matching the one or more user certificates are received; Means to maintain,
Means for adding the update device to the D2D device list;
Means for selecting the update device from the D2D device list;
Means for starting a response timer and an update timer upon requesting the update to synchronize the application data from the update device;
If the update device responds to the update request before the response timer expires, the updated data received from the update device over the D2D connection while the update timer has not expired is used. 20. The apparatus of claim 19, further comprising means for synchronizing application data. Associate with the registered application through an out-of-band D2D connection with the next update device selected from the D2D device list in response to the response timer expiring before the update device responds to the update request Means for requesting the update to synchronize the application data
Means for restarting the response timer upon requesting the update to synchronize the application data from the next update device;
If the next update device responds to the update request before the resumed response timer expires, updated data received from the update device over the D2D connection while the update timer has not expired 23. The apparatus of claim 22, further comprising: means for synchronizing the application data using.   23. The apparatus of claim 22, further comprising means for synchronizing the application data associated with the registered application from a network server when the update timer expires.   20. The apparatus of claim 19, further comprising means for constraining the D2D based application data synchronization service to applications registered with the D2D based application data synchronization service. Means for broadcasting the local specific expression associated with the registered application;
Means for receiving a request from a second device of the one or more peer devices to update the application data associated with the registered application through a second D2D connection; Means for the last update time in the local entity to be more recent than the last update time in the external entity received from the second device;
20. The apparatus of claim 19, further comprising means for transmitting updated data associated with the application to the second device over the second D2D connection. A computer-readable storage medium having recorded thereon computer-executable instructions, wherein when the computer-executable instructions are executed on a wireless device, the wireless device includes:
Generate a local unique representation that includes the name, one or more user certificates, and the last update time associated with an application registered with a device-to-device (D2D) based application data synchronization service,
One or more externals received from one or more peer devices proximate to the wireless device and matching the name and the one or more user certificates associated with the registered application Let's detect proper expressions,
Identifying an update device associated with an external specific expression including a last update time more recent than the last update time associated with the local specific expression from the one or more peer devices;
A computer readable storage medium that requests an update to synchronize the application data associated with the registered application from the update device through an out-of-band D2D connection. When the computer-executable instructions are executed on the wireless device, the wireless device further includes
Requesting the update to synchronize the application data through the D2D connection, start one or more timers;
28. The computer-readable storage medium of claim 27, wherein the application data is synchronized using updated data received from the update device over the D2D connection while the one or more timers have not expired. .   When the computer-executable instructions are executed on the wireless device, the wireless device is further associated with the registered application from a network server in response to expiration of the one or more timers. 30. The computer readable storage medium of claim 28, wherein application data is synchronized. The computer-executable instructions are further on the wireless device,
Broadcasting the local specific expression associated with the registered application;
Receiving a request from a second device of the one or more peer devices to update the application data associated with the registered application through a second D2D connection, the local device comprising: Receiving the last update time in the specific representation of the external device is more recent than the last update time in the external specific representation received from the second device;
28. The computer readable storage medium of claim 27, causing the updated data associated with the application to be transmitted to the second device over the second D2D connection.