EP2679036A1 - Amélioration de la connectivité d'une session entre des dispositifs - Google Patents

Amélioration de la connectivité d'une session entre des dispositifs

Info

Publication number
EP2679036A1
EP2679036A1 EP11859206.2A EP11859206A EP2679036A1 EP 2679036 A1 EP2679036 A1 EP 2679036A1 EP 11859206 A EP11859206 A EP 11859206A EP 2679036 A1 EP2679036 A1 EP 2679036A1
Authority
EP
European Patent Office
Prior art keywords
client node
client
individual
location data
message
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
EP11859206.2A
Other languages
German (de)
English (en)
Other versions
EP2679036A4 (fr
EP2679036B1 (fr
Inventor
Robert Novak
David Steer
Dongsheng Yu
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
BlackBerry Ltd
Original Assignee
BlackBerry Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by BlackBerry Ltd filed Critical BlackBerry Ltd
Publication of EP2679036A1 publication Critical patent/EP2679036A1/fr
Publication of EP2679036A4 publication Critical patent/EP2679036A4/fr
Application granted granted Critical
Publication of EP2679036B1 publication Critical patent/EP2679036B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/14—Direct-mode setup
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/23—Updating
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/28—Databases characterised by their database models, e.g. relational or object models
    • G06F16/282—Hierarchical databases, e.g. IMS, LDAP data stores or Lotus Notes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H04L5/0055—Physical resource allocation for ACK/NACK
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/80—Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/005—Discovery of network devices, e.g. terminals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/18—Self-organising networks, e.g. ad-hoc networks or sensor networks

Definitions

  • the present invention is directed in general to communications systems and methods for operating same.
  • the present invention relates to devices and methods for managing device-to-device communication sessions in a wireless-enabled communication environment.
  • D2D device-to-device
  • SSUF session-set-up filter
  • the SSUF not only directly assigns and supervises the use of inter-device communication channels among devices, but also identifies which devices are located within inter-device channel communication range of each other.
  • the SSUF typically administers the inter-device communication channels to manage interference, device location information, and handover requests between D2D and conventional wireless communication technologies.
  • the SSUF enables the broadcast of inter-device communication channel availability information within a cell to D2D-enabled devices, which then use the broadcast information to initiate a D2D session on their own.
  • the SSUF assists neighboring devices in locating other devices that are within inter- device channel range.
  • a device wishing to use inter-device channels for communication would send its identification and the identification of any desired devices to the SSUF.
  • the SSUF would then broadcast a page message to request the desired devices to listen to the inter-device channel for communications from its neighbor.
  • D2D session set-ups performed by a network entity may result in delays that are noticeable to the user of the devices.
  • some D2D sessions may not be successful due to signal interference or shadowing of the radio signals, despite the fact that appear to be possible due to device proximity.
  • Figure 1 depicts an exemplary system in which the present invention may be implemented
  • Figure 2 shows a wireless-enabled communications environment including an embodiment of a client node
  • FIG. 3 is a simplified block diagram of an exemplary client node comprising a digital signal processor (DSP);
  • DSP digital signal processor
  • Figure 4 is a simplified block diagram of a software environment that may be implemented by a DSP;
  • Figure 5 is a simplified block diagram for performing device-to-device (D2D) session operations;
  • D2D device-to-device
  • Figure 6 is a generalized flowchart for monitoring D2D cell IDs and locations
  • Figure 7 is a generalized flowchart for receiving D2D cell ID and location data.
  • Figure 8 is a generalized flowchart for initiating D2D communications.
  • a first client node comprises a database containing location and ID information associated with a plurality of second client nodes.
  • the location information in the database is updated as individual second client nodes change their location. As the location information is updated, it is processed by the first client node to determine the distance between it and each of the second client nodes. If the distance between the first client node and an individual second client node is within a viable D2D communications range, then the user of the first client node is notified that a D2D communications session can be initiated with the individual second client node.
  • D2D communications include
  • Such configurations may comprise client nodes operating in Multiple Input Multiple Output (MIMO) configurations, Cooperative Multipoint (CoMP) configurations, Interference Control (IC), direct device-to-device communications, and relaying of information among client nodes.
  • MIMO Multiple Input Multiple Output
  • CoMP Cooperative Multipoint
  • IC Interference Control
  • the updates to the location data are received by the first client node in a location update message provided by an individual second client node.
  • the first client node provides its associated location and ID data to the second client node in a location data response message.
  • the first client node requests additional location data from the individual second client node in an additional location data request message.
  • the frequency of the timing of the receipt of the location data update message is dependant upon the distance between the first client node and the individual second client node.
  • the first client node generates and subsequently sends a D2D session test message to a second client node. If the second client node successfully receives the D2D session test message, it generates and subsequently sends a D2D session test acknowledgement message to the first client. If the D2D session test message is successfully received by the first client node, then a D2D session with the second client node is initiated by the first client node.
  • a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, or a computer.
  • a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, or a computer.
  • an application running on a computer and the computer itself can be a component.
  • One or more components may reside within a process or thread of execution and a component may be localized on one computer or distributed between two or more computers.
  • node broadly refers to a connection point, such as a redistribution point or a communication endpoint, of a communication environment, such as a network. Accordingly, such nodes refer to an active electronic device capable of sending, receiving, or forwarding information over a
  • nodes include data circuit-terminating equipment (DCE), such as a modem, hub, bridge or switch, and data terminal equipment (DTE), such as a handset, a printer or a host computer (e.g., a router, workstation or server).
  • DCE data circuit-terminating equipment
  • DTE data terminal equipment
  • LAN local area network
  • WAN wide area network
  • nodes include computers, packet switches, cable modems, Data Subscriber Line (DSL) modems, and wireless LAN (WLAN) access points.
  • DSL Data Subscriber Line
  • WLAN wireless LAN
  • Examples of Internet or Intranet nodes include host computers identified by an Internet Protocol (IP) address, bridges and WLAN access points.
  • IP Internet Protocol
  • examples of nodes in cellular communication include base stations, base station controllers, home location registers, Gateway GPRS Support Nodes (GGSN), and Serving GPRS Support Nodes (SGSN).
  • GGSN Gateway GPRS Support Nodes
  • SGSN Serving GPRS Support Nodes
  • nodes include client nodes, server nodes, peer nodes and access nodes.
  • a client node may refer to wireless devices such as mobile telephones, smart phones, personal digital assistants (PDAs), handheld devices, portable computers, tablet computers, and similar devices or other user equipment (UE) that has telecommunications capabilities.
  • PDAs personal digital assistants
  • client nodes may likewise refer to a mobile, wireless device, or conversely, to devices that have similar capabilities that are not generally transportable, such as desktop computers, set-top boxes, or sensors.
  • a server node refers to an information processing device (e.g., a host computer), or series of information processing devices, that perform information processing requests submitted by other nodes.
  • a peer node may sometimes serve as client node, and at other times, a server node.
  • a node that actively routes data for other networked devices as well as itself may be referred to as a supernode.
  • An access node refers to a node that provides a client node access to a communication environment.
  • Examples of access nodes include cellular network base stations and wireless broadband (e.g., WiFi, WiMAX, etc) access points, which provide corresponding cell and WLAN coverage areas.
  • a macrocell is used to generally describe a traditional cellular network cell coverage area. Such macrocells are typically found in rural areas, along highways, or in less populated areas.
  • a microcell refers to a cellular network cell with a smaller coverage area than that of a macrocell. Such micro cells are typically used in a densely populated urban area.
  • a picocell refers to a cellular network coverage area that is less than that of a microcell.
  • An example of the coverage area of a picocell may be a large office, a shopping mall, or a train station.
  • a femtocell as used herein, currently refers to the smallest commonly accepted area of cellular network coverage. As an example, the coverage area of a femtocell is sufficient for homes or small offices.
  • a coverage area of less than two kilometers typically corresponds to a microcell, 200 meters or less for a picocell, and on the order of 10 meters for a femtocell.
  • a client node communicating with an access node associated with a macrocell is referred to as a "macrocell client.”
  • a client node communicating with an access node associated with a microcell, picocell, or femtocell is respectively referred to as a "microcell client,” “picocell client,” or "femtocell client.”
  • computer readable media can include but are not limited to magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips, etc.), optical disks such as a compact disk (CD) or digital versatile disk (DVD), smart cards, and flash memory devices (e.g., card, stick, etc.).
  • magnetic storage devices e.g., hard disk, floppy disk, magnetic strips, etc.
  • optical disks such as a compact disk (CD) or digital versatile disk (DVD)
  • smart cards e.g., card, stick, etc.
  • FIG. 1 illustrates an example of a system 100 suitable for implementing one or more embodiments disclosed herein.
  • the system 100 comprises a processor 1 10, which may be referred to as a central processor unit (CPU) or digital signal processor (DSP), network connectivity devices 120, random access memory (RAM) 130, read only memory (ROM) 140, secondary storage 150, and input/output (I/O) devices 160.
  • processor 1 10 may be referred to as a central processor unit (CPU) or digital signal processor (DSP), network connectivity devices 120, random access memory (RAM) 130, read only memory (ROM) 140, secondary storage 150, and input/output (I/O) devices 160.
  • CPU central processor unit
  • DSP digital signal processor
  • RAM random access memory
  • ROM read only memory
  • secondary storage 150 secondary storage
  • I/O input/output
  • I/O input/output
  • some of these components may not be present or may be combined in various combinations with one another or with other components not shown.
  • These components may be located in a single physical
  • the processor 1 10 executes instructions, codes, computer programs, or scripts that it might access from the network connectivity devices 120, RAM 130, or ROM 140. While only one processor 1 10 is shown, multiple processors may be present. Thus, while instructions may be discussed as being executed by a processor 1 10, the instructions may be executed simultaneously, serially, or otherwise by one or multiple processors 1 10 implemented as one or more CPU chips.
  • the network connectivity devices 120 may take the form of modems, modem banks, Ethernet devices, universal serial bus (USB) interface devices, serial interfaces, token ring devices, fiber distributed data interface (FDDI) devices, wireless local area network (WLAN) devices, radio transceiver devices such as code division multiple access (CDMA) devices, global system for mobile communications (GSM) radio transceiver devices, worldwide interoperability for microwave access (WiMAX) devices, and/or other well-known devices for connecting to networks, including Personal Area Networks (PANs) such as Bluetooth.
  • These network connectivity devices 120 may enable the processor 1 10 to connect to networks, including Personal Area Networks (PANs) such as Bluetooth.
  • PANs Personal Area Networks
  • the network connectivity devices 120 may also be capable of transmitting or receiving data wirelessly in the form of electromagnetic waves, such as radio frequency signals or microwave frequency signals.
  • Information transmitted or received by the network connectivity devices 120 may include data that has been processed by the processor 1 10 or instructions that are to be executed by processor 1 10. The data may be ordered according to different sequences as may be desirable for either processing or generating the data or transmitting or receiving the data.
  • the RAM 130 may be used to store volatile data and instructions that are executed by the processor 110.
  • the ROM 140 shown in Figure 1 may be used to store instructions and perhaps data that are read during execution of the instructions. Access to both RAM 130 and ROM 140 is typically faster than to secondary storage 150.
  • the secondary storage 150 is typically comprised of one or more disk drives or tape drives and may be used for non-volatile storage of data or as an over-flow data storage device if RAM 130 is not large enough to hold all working data. Secondary storage 150 may be used to store programs that are loaded into RAM 130 when such programs are selected for execution.
  • the I/O devices 160 may include liquid crystal displays (LCDs), Light Emitting Diode (LED) displays, Organic Light Emitting Diode (OLED) displays, projectors, televisions, touch screen displays, keyboards, keypads, switches, dials, mice, track balls, voice recognizers, card readers, paper tape readers, printers, video monitors, or other well-known input/output devices.
  • LCDs liquid crystal displays
  • LED Light Emitting Diode
  • OLED Organic Light Emitting Diode
  • projectors televisions, touch screen displays, keyboards, keypads, switches, dials, mice, track balls, voice recognizers, card readers, paper tape readers, printers, video monitors, or other well- known input/output devices.
  • FIG. 2 shows a wireless-enabled communications environment including an embodiment of a client node as implemented in an embodiment of the invention.
  • the client node 202 may take various forms including a wireless handset, a pager, a smart phone, or a personal digital assistant (PDA).
  • the client node 202 may also comprise a portable computer, a tablet computer, a laptop computer, or any computing device operable to perform data communication operations. Many suitable devices combine some or all of these functions.
  • the client node 202 is not a general purpose computing device like a portable, laptop, or tablet computer, but rather is a special- purpose communications device such as a telecommunications device installed in a vehicle.
  • the client node 202 may likewise be a device, include a device, or be included in a device that has similar capabilities but that is not transportable, such as a desktop computer, a set-top box, or a network node. In these and other embodiments, the client node 202 may support specialized activities such as gaming, inventory control, job control, task management functions, and so forth.
  • the client node 202 includes a display 204.
  • the client node 202 may likewise include a touch- sensitive surface, a keyboard or other input keys 206 generally used for input by a user.
  • the input keys 206 may likewise be a full or reduced alphanumeric keyboard such as QWERTY, Dvorak, AZERTY, and sequential keyboard types, or a traditional numeric keypad with alphabet letters associated with a telephone keypad.
  • the input keys 206 may likewise include a trackwheel, an exit or escape key, a trackball, and other navigational or functional keys, which may be inwardly depressed to provide further input function.
  • the client node 202 may likewise present options for the user to select, controls for the user to actuate, and cursors or other indicators for the user to direct.
  • the client node 202 may further accept data entry from the user, including numbers to dial or various parameter values for configuring the operation of the client node 202.
  • the client node 202 may further execute one or more software or firmware applications in response to user commands. These applications may configure the client node 202 to perform various customized functions in response to user interaction.
  • the client node 202 may be programmed or configured over-the-air (OTA), for example from a wireless network access node 'A' 210 through 'n' 216 (e.g., a base station), a server node 224 (e.g., a host computer), or a peer client node 202.
  • OTA over-the-air
  • the various applications executable by the client node 202 are a web browser, which enables the display 204 to display a web page.
  • the web page may be obtained from a server node 224 through a wireless connection with a wireless network 220.
  • the various applications may likewise be obtained from a peer client node 202 or other system over a connection to the wireless network 220 or any other wireless communication network or system.
  • the wireless network 220 comprises a plurality of wireless sub-networks (e.g., cells with corresponding coverage areas) 'A' 212 through 'n' 218.
  • the client node 202 transmits and receives communication signals, which are respectively communicated to and from the wireless network nodes 'A' 210 through 'n' 216 by wireless network antennas 'A' 208 through 'n' 214 (e.g., cell towers).
  • the communication signals are used by the wireless network access nodes 'A' 210 through 'n' 216 to establish a wireless communication session with the client node 202.
  • the wireless network access points 'A' 210 through 'n' 216 are respectively coupled to wireless sub-networks 'A' 212 through 'n' 218, which are connected to the wireless network 220.
  • the wireless network 220 is coupled to a physical network 222, such as the Internet. Via the wireless network 220 and the physical network 222, the client node 202 has access to information on various hosts, such as the server node 224. In these and other embodiments, the server node 224 may provide content that may be shown on the display 204. Alternately, the client node 202 may access the wireless network 220 through a peer client node 202 acting as an intermediary, in a relay type or hop type of connection. Alternately, the client node 202 is tethered and obtains its data from a tethered device that is connected to the wireless network 212. Skilled practitioners of the art will recognize that many such embodiments are possible and the foregoing is not intended to limit the spirit, scope, or intention of the disclosure.
  • FIG. 3 depicts a block diagram of an exemplary client node as implemented with a digital signal processor (DSP) in accordance with an embodiment of the invention. While various components of a client node 202 are depicted, various embodiments of the client node 202 may include a subset of the listed components or additional components not listed. As shown in Figure 3, the client node 202 includes a DSP 302 and a memory 304.
  • DSP digital signal processor
  • the client node 202 may further include an antenna and front end unit 306, a radio frequency (RF) transceiver 308, an analog baseband processing unit 310, a microphone 312, an earpiece speaker 314, a headset port 316, a bus 318, such as a system bus or an input/output (I/O) interface bus, a removable memory card 320, a universal serial bus (USB) port 322, a short range wireless communication sub-system 324, an alert 326, a keypad 328, a liquid crystal display (LCD) 330, which may include a touch sensitive surface, an LCD controller 332, a charge-coupled device (CCD) camera 334, a camera controller 336, and a global positioning system (GPS) sensor 338, and a power management module 340 operably coupled to a power storage unit, such as a battery 342.
  • the client node 202 may include another kind of display that does not provide a touch sensitive screen.
  • the DSP 302 communicate
  • the DSP 302 or some other form of controller or central processing unit (CPU) operates to control the various components of the client node 202 in accordance with embedded software or firmware stored in memory 304 or stored in memory contained within the DSP 302 itself.
  • the DSP 302 may execute other applications stored in the memory 304 or made available via information carrier media such as portable data storage media like the removable memory card 320 or via wired or wireless network communications.
  • the application software may comprise a compiled set of machine- readable instructions that configure the DSP 302 to provide the desired functionality, or the application software may be high-level software instructions to be processed by an interpreter or compiler to indirectly configure the DSP 302.
  • the antenna and front end unit 306 may be provided to convert between wireless signals and electrical signals, enabling the client node 202 to send and receive information from a cellular network or some other available wireless communications network or from a peer client node 202.
  • the antenna and front end unit 106 may include multiple antennas to support beam forming and/or multiple input multiple output (MIMO) operations.
  • MIMO operations may provide spatial diversity which can be used to overcome difficult channel conditions or to increase channel throughput.
  • the antenna and front end unit 306 may include antenna tuning or impedance matching components, RF power amplifiers, or low noise amplifiers.
  • the RF transceiver 308 provides frequency shifting, converting received RF signals to baseband and converting baseband transmit signals to RF.
  • a radio transceiver or RF transceiver may be understood to include other signal processing functionality such as modulation/ demodulation, coding/decoding, interleaving/ deinterleaving,
  • IFFT inverse fast Fourier transforming
  • FFT fast Fourier transforming
  • cyclic prefix appending/removal and other signal processing functions.
  • IFFT inverse fast Fourier transforming
  • FFT fast Fourier transforming
  • cyclic prefix appending/removal and other signal processing functions.
  • the description here separates the description of this signal processing from the RF and/or radio stage and conceptually allocates that signal processing to the analog baseband processing unit 310 or the DSP 302 or other central processing unit.
  • the RF Transceiver 108, portions of the Antenna and Front End 306, and the analog base band processing unit 310 may be combined in one or more processing units and/or application specific integrated circuits (ASICs).
  • ASICs application specific integrated circuits
  • the analog baseband processing unit 310 may provide various analog processing of inputs and outputs, for example analog processing of inputs from the microphone 312 and the headset 316 and outputs to the earpiece 314 and the headset 316.
  • the analog baseband processing unit 310 may have ports for connecting to the built-in microphone 312 and the earpiece speaker 314 that enable the client node 202 to be used as a cell phone.
  • the analog baseband processing unit 310 may further include a port for connecting to a headset or other hands-free microphone and speaker configuration.
  • the analog baseband processing unit 310 may provide digital-to-analog conversion in one signal direction and analog-to-digital conversion in the opposing signal direction.
  • at least some of the functionality of the analog baseband processing unit 310 may be provided by digital processing components, for example by the DSP 302 or by other central processing units.
  • the DSP 302 may perform modulation/demodulation, coding/decoding, interleaving/deinterleaving, spreading/despreading, inverse fast Fourier transforming (IFFT)/fast Fourier transforming (FFT), cyclic prefix appending/removal, and other signal processing functions associated with wireless communications.
  • IFFT inverse fast Fourier transforming
  • FFT fast Fourier transforming
  • cyclic prefix appending/removal and other signal processing functions associated with wireless communications.
  • CDMA code division multiple access
  • the DSP 302 may perform modulation, coding, interleaving, inverse fast Fourier transforming, and cyclic prefix appending, and for a receiver function the DSP 302 may perform cyclic prefix removal, fast Fourier transforming, deinterleaving, decoding, and demodulation.
  • OFDMA orthogonal frequency division multiplex access
  • the DSP 302 may communicate with a wireless network via the analog baseband processing unit 310.
  • the communication may provide Internet connectivity, enabling a user to gain access to content on the Internet and to send and receive e-mail or text messages.
  • the input/output interface 318 interconnects the DSP 302 and various memories and interfaces.
  • the memory 304 and the removable memory card 320 may provide software and data to configure the operation of the DSP 302.
  • the interfaces may be the USB interface 322 and the short range wireless communication sub-system 324.
  • the USB interface 322 may be used to charge the client node 202 and may also enable the client node 202 to function as a peripheral device to exchange information with a personal computer or other computer system.
  • the short range wireless communication sub-system 324 may include an infrared port, a Bluetooth interface, an IEEE 802.1 1 compliant wireless interface, or any other short range wireless communication sub-system, which may enable the client node 202 to communicate wirelessly with other nearby client nodes and access nodes.
  • the input/output interface 318 may further connect the DSP 302 to the alert 326 that, when triggered, causes the client node 202 to provide a notice to the user, for example, by ringing, playing a melody, or vibrating.
  • the alert 326 may serve as a mechanism for alerting the user to any of various events such as an incoming call, a new text message, and an appointment reminder by silently vibrating, or by playing a specific pre-assigned melody for a particular caller.
  • the keypad 328 couples to the DSP 302 via the I/O interface 318 to provide one mechanism for the user to make selections, enter information, and otherwise provide input to the client node 202.
  • the keyboard 328 may be a full or reduced alphanumeric keyboard such as QWERTY, Dvorak, AZERTY and sequential types, or a traditional numeric keypad with alphabet letters associated with a telephone keypad.
  • the input keys may likewise include a trackwheel, an exit or escape key, a trackball, and other navigational or functional keys, which may be inwardly depressed to provide further input function.
  • Another input mechanism may be the LCD 330, which may include touch screen capability and also display text and/or graphics to the user.
  • the LCD controller 332 couples the DSP 302 to the LCD 330.
  • the CCD camera 334 if equipped, enables the client node 202 to take digital pictures.
  • the DSP 302 communicates with the CCD camera 334 via the camera controller 336.
  • a camera operating according to a technology other than Charge Coupled Device cameras may be employed.
  • the GPS sensor 338 is coupled to the DSP 302 to decode global positioning system signals, thereby enabling the client node 202 to determine its position.
  • Various other peripherals may also be included to provide additional functions, such as radio and television reception.
  • FIG. 4 illustrates a software environment 402 that may be implemented by a digital signal processor (DSP).
  • DSP digital signal processor
  • the DSP 302 shown in Figure 3 executes an operating system 404, which provides a platform from which the rest of the software operates.
  • the operating system 404 likewise provides the client node 202 hardware with standardized interfaces (e.g., drivers) that are accessible to application software.
  • the operating system 404 likewise comprises application management services (AMS) 406 that transfer control between applications running on the client node 202.
  • AMS application management services
  • Also shown in Figure 4 are a web browser application 408, a media player application 410, Java applets 412, an inter-device interaction module 416, and a cell ID - location mapping module 418.
  • the web browser application 408 configures the client node 202 to operate as a web browser, allowing a user to enter information into forms and select links to retrieve and view web pages.
  • the media player application 410 configures the client node 202 to retrieve and play audio or audiovisual media.
  • the Java applets 412 configure the client node 202 to provide games, utilities, and other functionality.
  • the inter-device interaction module 416 is used to send and receive messages to and from device-to-device (D2) enabled client nodes 202, and is likewise used to perform data processing operations, described in greater detail herein, related to maintaining D2D-related data and cooperative operating configurations.
  • the cell ID - location mapping module 418 is used to compare the physical locations of cell IDs that belong to different networks.
  • two devices subtending to different networks and having different cell ID number bases, to determine if their locations are similar.
  • two cell IDs may have overlapping coverage areas.
  • the short-range wireless communications subsystem 324 may include antennas representative of possible multiple radio link capabilities. This may, in practice, involve several radios each with multiple antennas.
  • the client node 202 e.g. a radio device
  • the client node 202 and associated antennas may be shared among a number of different radio modes of operation.
  • a wired interface may likewise be included in the short-range wireless communications subsystem 324 as it may be applicable to devices that have wired, or fiber, connections to a network (e.g. access nodes).
  • This wired interface may not be present on the client node 202, and for fixed devices such as access nodes there may be multiple wired connections or connections to other network equipment.
  • the client node 202, the wireless network nodes 'A' 210 through 'n' 216, and the server node 224 shown in Figure 2 may likewise include a processing component that is capable of executing instructions related to the actions described above.
  • FIG. 5 is a simplified block diagram for performing device-to-device (D2D) session operations as implemented in accordance with an embodiment of the invention.
  • a mobile wireless access network 502 comprises session set-up filter (SSUF) server 516 and a mobile wireless network access node 504.
  • the SSUF server 516 further comprises a SSUF system 518 and a repository of D2D and SSUF data as described in greater detail herein.
  • the mobile wireless network access node 504 comprises a corresponding access node coverage area 506 for providing mobile wireless communication capabilities for client nodes 'A' 508 and 'B' 512.
  • the client nodes 'A' 508 and 'B' 512 are enabled to initiate and subsequently conduct D2D communication sessions and respectively comprise a repository of D2D data 'A' 510 and 'B' 514.
  • the repositories of D2D data 'A' 510 and 'B' 514 comprise a contact list store where client nodes 'A' 508 and 'B' 512 respectively maintains a list of other client nodes (e.g., other mobile devices) that are likewise D2D-enabled.
  • the repositories of D2D data 'A' 510 and 'B' 514 may, for example, be contained in the memory 304 or the removable memory card 320 of the client node 202.
  • the repositories of D2D data 'A' 510 and 'B' 514 are automatically updated with client node location proximity information maintained in the repository of D2D and SSUF data 520 by the SSUF system 518.
  • individual listings within these lists may include the status of the other client nodes including their current location and whether a D2D link has been tested and is possible at the client nodes' 'A' 508 and 'B' 512 current locations.
  • a client node 'A' 508 is determined to be available to use an inter-device channel for D2D communication with client node 'B' 512 if the client nodes 'A' 508 and 'B' 512 are within a viable D2D communication range 522.
  • client node 'B' 512 is capable of D2D communications if it is within 400 meters (e.g., the viable D2D communication range 522) from client node 'A' 508, then it will appear as available to client node 'A' 508 for D2D communications.
  • the viable D2D communication range 522 can be set to a predetermined communication range that is dependent upon the aforementioned factors and on observed performance.
  • the client node 'A' 508 monitors its current location as it operates. This may be, for example, through monitoring of the cell-ID associated with the mobile wireless network access node 504 associated with the access node coverage area 506, through which it subtends the mobile wireless access network 502. However other location mechanism such as Global Positioning System (GPS), can be used to determine its approximate location within the access node coverage area 506.
  • GPS Global Positioning System
  • the location of client node 'B' 512 is requested from a network entity, such as the SSUF system 518, in response to client node 'A' 508 requesting updated information on available devices (e.g., client node 'B' 512).
  • a location data update message is sent from client node 'A' 508 to other client node members (e.g., client node 'B' 512) stored in its repository of D2D data 'A' 510 to indicate its current location.
  • the messages provide the identity of the sender (e.g., client node 'A' 508), and associated location information, to those receivers (e.g., client node 'B' 512) that receive the message.
  • the receiver Upon successfully receiving the message, the receiver will be aware of the sender's presence and its capability for D2B communication.
  • the client node 'B' 512 provides the client node 'A' 508 a location data response message comprising its associated location and identification data in response to receiving the location data update message.
  • the client node 'A' 508 provides the client node 'B' 512 a location data update response message comprising updated location data and identification data associated with the client node 'A' 508 in response to receiving the location data update message.
  • the client node 'A' 508 provides the client node 'B' 512 an additional location data update message requesting additional location data associated with the client node 'B' 512 in response to receiving the location data update message.
  • the messages are sent at intervals, but not frequently enough to significantly load the implemented radio access technology. For example, a message may be sent to possible contacts (e.g., client node 'B' 512) every 5 minutes if a message has not been received from those contacts in that time. In certain other of these various embodiments, the messages are sent more frequently to members of the contact list that are nearby, such as those currently associated within the same cell-ID or a similar location area, and less frequently to members who are in the most distant locations, such as those located within a geographically distant cell- ID.
  • possible contacts e.g., client node 'B' 512
  • the messages are sent more frequently to members of the contact list that are nearby, such as those currently associated within the same cell-ID or a similar location area, and less frequently to members who are in the most distant locations, such as those located within a geographically distant cell- ID.
  • the content of the messages sent from client node 'A' 508 to members of its contact list is dependent on the assumed distance of each contact.
  • the granularity of the location of the client node 'A' 508 may be more coarse when sending updates to more distant client nodes, and finer when updating client nodes that are nearer. For example, client nodes that are known to be across the world may only receive an update on the country location of the client node 'A' 508, whereas a client node assumed to be with a few kilometers are sent more specific information such as cell-ID, or precise GPS locations of a high level of accuracy.
  • the client node 'A' 508 is made aware of other client nodes (e.g., client node 'B' 512) that are within the viable D2D communication range by sending a message to possible contacts (e.g., the client node 'B' 512) with an inquiry related to possible D2D communications.
  • the client node 'A' 508 sends a message over a radio channel, such as a mobile network communications channel, to other client nodes (e.g., the client node 'B' 512) requesting the client node's location.
  • the location information may be indicated by absolute location, including location error range, from GPS or other source, or another reference point such as a cell tower ID or a similar location area reference.
  • the receiving client node e.g., client node 'B' 512
  • the initiating client node determines whether they are available for D2D communications.
  • the initiating client node includes its location information in the initial message to other client nodes. The response from the other client nodes may not need to contain location information, but instead, an indication if D2D communication is possible. These embodiments may be used to limit the distribution of location information to other client nodes.
  • the contact list may be updated without requiring the detailed location information of each other device.
  • a client node (e.g., the client node 'B' 512) receiving a location message from an initiating client node (e.g., the client node 'A' 508) may do one or more of sending a response with their location, request additional location information, or update their repository of D2D data (e.g., repository of D2D data 'B' 514).
  • the location information from the initiating client node may indicate that the two client nodes are beyond the viable D2D communication range 522 significantly larger than the distance suitable for D2D communications. If so, then the receiving client node updates its repository of D2D data with the information associated with the initiating client node.
  • the client node receiving a location update message from a member of its contact list may determine that the initiating client node is close enough to update the location information associated with the initiating node in its repository of D2D data.
  • the receiving client node may send its position to the initiating client node or request more detailed location information from the initiating client node, if applicable.
  • client nodes send messages to members of the contact list stored in their repository of D2D data in response to a significant perceived change in their location.
  • a client node e.g., the client node 'A' 508 may determine it has changed countries or geographical regions based on identification information associated with the mobile wireless access node 504 or from associated operator information.
  • the client node may detect it has moved a significant distance from the location previously reported to members of the contact list stored in its repository of D2D data (e.g., the repository of D2D data 'A' 510).
  • the client node 'A' 508 determines that it has moved a significant distance and provides a location update to members of its contact list.
  • the determination of a significant distance to require sending location information can be achieved by determining that the information last provided to a member of the contact list is no longer valid.
  • the client node may determine that it has moved into proximity on the order of, or less than, the granularity of the location information provided by another client node in its contact list.
  • the client nodes 'A' 508 and 'B' 512 may likewise provide multi-level information of their availability for D2D
  • the availability of client nodes 'A' 508 and 'B' 512' for D2D communication is indicated on the basis of distance to a client node.
  • a network entity e.g., the SSUF system 5128 determining the availability of inter-device communications between two client nodes (e.g., client nodes 'A' 508 and 'B' 512) provides a multilevel indication related to the distance separating the client nodes.
  • a separation of 200 to 300 meters may be indicated as 'excellent.
  • a separation of 300-400 meters may be indicated as 'average
  • a separation of 400-500 meters is indicated as 'poor'
  • a separation of greater than 500 meters is indicated as 'unavailable'.
  • an autonomous test message is sent across the inter- device channel to test its performance between two client nodes appearing on each other's respective contact lists.
  • the test message provides identification and location data associated with an initiating client node to a receiving client node.
  • the identification and location data associated with the receiving client node is provided in a response message to the initiating client node. If the test message is successful (e.g., a successful response if received by the initiating client node), then the users' of the initiating and receiving client node are informed of the current availability of the member of the contact list.
  • some D2D communication traffic destined for recipient client nodes is stored internally within the initiating client node until a suitable inter-device channel is available. Once a suitable inter-device channel is available, the traffic is automatically communicated by the initiating client node to the recipient client node. In certain of these various embodiments, the transmission of the stored communication traffic is initiated by the user upon being informed that the inter-device channel is available. In various embodiments, the quality of the inter- device channel is determined from the aforementioned test message exchange. In certain of these various embodiments, multi-level information regarding the quality of the link is indicated based on the signal communications quality of the two-way messaging, rather than solely upon distance measurements.
  • a new D2D session may be initiated by an initiating client node without requiring further testing of the inter-device channel for suitability of D2D communications.
  • the initiating client node checks its contact list for verification of the recipient client node's availability for D2D communication.
  • the contact list may provide existing estimates of the recipient client node's location, proximity and estimated link quality based on the initial, or previous, link test. In this manner the link may not require further testing before beginning a new D2D session.
  • the invention likewise provides the advantage of not requiring network-based resources to monitor status and manage D2D communication links, thereby obviating the need for a network server. Furthermore, the use of such D2D communication links improves radio resource utilization by moving local traffic away from wide area spectrum and radio network resources. Furthermore, the knowledge of the availability of the D2D links can facilitate the operation of cooperative node communications including client nodes operating in Multiple Input Multiple Output (MIMO) configurations,
  • MIMO Multiple Input Multiple Output
  • CoMP Cooperative Multipoint
  • IC Interference Control
  • FIG. 6 is a generalized flowchart for monitoring device-to-device (D2D) cell identifiers (IDs) and locations as implemented in accordance with an embodiment of the invention.
  • D2D cell ID and location monitoring operations are begun in step 602, followed by a client node (e.g., a mobile device) performing list maintenance operations in step 604 to maintain a contact list of other client nodes available for D2D communications.
  • the contact list of client nodes may include client nodes that have been previously selected by the user, client nodes that have been automatically included as a result of prior D2D communications previously, or some combination thereof.
  • the client node monitors its current physical location.
  • the client node monitors the cell ID of the cell tower associated with the cellular base station through which it subtends a mobile wireless access network.
  • the client node's physical location is determined through the implementation of a Global Positioning System (GPS).
  • GPS Global Positioning System
  • various area location selectors are used to filter client nodes that are local (e.g., within a viable D2D communication range), those for which D2D communications may become possible (e.g., poor radio conditions), and those for which the distance is large and communications is likely impossible for the operable radio frequency band.
  • the client node may comprise multiple forms of communications equipment that are suitable for communications over various communication ranges.
  • location-based filtering provides an effective means to minimize the signaling necessary to maintain the currency of the aforementioned client node contact list.
  • the client node may be mobile. If so then a determination is made in step 608 whether the client node has moved to a different location. As an example, the client node may perform location-based filtering to determine changes in cell IDs or GPS location data to determine whether it has settled in a new cell, or instead, is simply transiting through it.
  • step 608 If it is determined in step 608 that the client node is not in a new location, then a determination is made in step 624 whether to continue D2D cell ID and location monitoring operations. If so, then the process is continued, proceeding with step 604. Otherwise, D2D cell ID and location monitoring operations are ended in step 626. However, if it is determined in step 608 that the client node is in a new location, then it checks its repository of D2D data in step 610 to determine whether its new cell ID or location area corresponds to any of the other client nodes in client node contact list.
  • the client node sends detailed data related to its current location, such as its GPS coordinates, to client nodes that are currently within the same cell or locations within viable communications range. Thereafter, the process is continued, proceeding with step 604.
  • the detailed location information may be sent using any suitable messaging service (e.g. such as IP, PPP, PIN communication or SMS).
  • the client node processes cell ID mapping data to determine whether the other client nodes are in similar areas, such as when the other client nodes are in a different network.
  • the client node sends its new cell-ID information, but not its detailed location coordinates, to other client nodes on the client node contact list that are not known to have the same cell ID or be in a similar area.
  • the client node automatically sends updated location information to other client nodes in their client node contact list whenever there is significant change in their location.
  • the client node will send other related information whenever there is a significant change in radio communication conditions (e.g. signal blockage due to shadowing) or status information (e.g. power on/off, user available/unavailable).
  • updates in location information, or other related conditions are sent at predetermined intervals. For example, the update message may be sent within 10 minutes of the most recent communication with another client node in the client node contact list.
  • step 610 if it is determined in step 610 that the client node's new cell ID or similar area does not correspond to any of the other client nodes in its client node contact list, then the client node communicates its location and related information in step 614 to the client nodes that are not located in the same cell ID or similar area at a later time. Thereafter, the process is continued, proceeding with step 604.
  • the client node performs filtering operations to determine the timing of sending the location update messages to reduce the volume of signaling traffic. For example, a client node may send location and cell ID information less frequently to client nodes in its client node contact list that are known to be very far away, and hence, unlikely to within a viable D2D communication range in the near term.
  • the update messages may only be sent at infrequent intervals, such as intervals of many hours, or when the client node has made a significant change in its location. Accordingly, client nodes that are known to be in closer proximity would automatically receive more frequent updates, while client nodes that are at a great distance would be updated infrequently.
  • FIG. 7 is a generalized flowchart for receiving device-to-device (D2D) cell identifier (ID) and location data as implemented in accordance with an embodiment of the invention.
  • D2D device-to-device
  • ID location data
  • operations for the receipt of D2D Cell ID and location data are begun in step 702, followed by the receipt in step 704 of new cell ID (or associated location data) and client node ID data by a receiving client node from a sending client node.
  • the information may be transmitted from the sending client node to the receiving client node using any suitable messaging service, such as IP, PPP, PIN communication or SMS.
  • step 710 A determination is then made in step 710 whether the cell ID or similar location area of the sending client node matches that of the receiving client node. If not, then the process is continued, proceeding with step 704. Otherwise, the receiving client node communicates its location information to the sending client node in step 712 to confirm that the two client nodes are in proximity and to likewise enable them to calculate if a D2D communications session is viable by calculating the distance between them.
  • the receiving client node is within the same cell as the sending client node. In these embodiments, the receiving client node receives the sending client nodes' coordinates, in addition to its cell ID, and it calculates the distance between the client nodes by using its own location information.
  • step 714 A determination is then made in step 714 whether the two client nodes are within a viable D2D communications range. If not, then the receiving client node communicates its current location to, or distance from, the sending client node in step 716 and the process is continued, proceeding with step 604. Otherwise, the receiving node communicates its current location to, or distance from, the sending client node in step 716 and indicates that they are within a viable range for D2D communications. The process is then continued, proceeding with step 704.
  • the receiving node proposes various aspects
  • the viability of a D2D communications session is based on whether the distance between the two client nodes is less than a distance threshold.
  • the distance threshold is predetermined. In another embodiment, it is dynamically calculated based on results of prior D2D
  • FIG 8 is a generalized flowchart for initiating device-to-device (D2D) communications as implemented in accordance with an embodiment of the invention.
  • operations for the initiation of D2D communications are begun in step 802, followed by the receipt in step 804 of new cell ID (or associated location data) and client node ID data by a receiving client node from a sending client node.
  • the information may be transmitted from the sending client node to the receiving client node using any suitable messaging service, such as IP, PPP, PIN communication or SMS.
  • step 806 A determination is made by the receiving node in step 806 whether the sending client node ID is on its client node contact list. If not, then the message is ignored and a determination is made in step 824 whether to continue operations for the initiation of D2D communications. If so, the process is continued, proceeding with step 804. However, if it is determined in step 806 that the sending client node ID is on the receiving client node's contact list, then the distance between the receiving client node and the sending client node is calculated in step 808.
  • step 814 A determination is then made in step 814 whether the two client nodes are within a viable D2D communication range, as described in greater detail herein. If not, then the process is continued, proceeding with step 802. Otherwise, the receiving client node initiates a D2D test link, such as a ping transmission, to the sending client node in step 816. A determination is then made in step 818 whether the D2D test link was successful. If not, then the process is continued, proceeding with step 804. Otherwise, both client nodes mark the other client node as being communicable in their respective client node contact list in step 820. Then, in step 822, either the receiving client node, or the sending client node, may establish a D2D
  • either of the two client nodes may indicate to its respective user that a client node on its client node list is within range for D2D communications.
  • an application implemented on either of the client nodes guides the user in establishing a D2D communications session with the other client node.
  • a D2D communication session is automatically established between the two client nodes to communicate traffic that has been saved until a D2D communication session is established.
  • a D2D session may be handed-over for continuation in a non-D2D communication session using other communications channels. Thereafter, the process is continued, proceeding with step 804.
  • multi-node links are established using multicast transmissions known to those of skill in the art.
  • the multi-cast transmissions are supported in radio access technologies through the implementation of a group address for a multi-cast group.
  • Client nodes sending to the group use the group address to address their transmission and receivers of the group transmission decode messages based on the group address.
  • the multi-node links may be a combination of paired links among client nodes as well as common multi-cast communications links among multiple client nodes.

Abstract

La présente invention concerne des dispositifs et des procédés permettant de gérer des sessions de communications de dispositif à dispositif (D2D) dans un environnement de communication sans fil. Un premier nœud client comprend une base de données contenant des informations de position et d'identifiant associées à une pluralité de seconds nœuds clients. Les informations de position dans la base de données sont mises à jour lorsque des seconds nœuds clients particuliers changent de position. Lorsque les informations de position sont mises à jour, elles sont traitées par le premier nœud client afin que ce dernier effectue une détermination de la distance entre lui et un second nœud client particulier. Si la distance entre le premier nœud client et le second nœud client particulier est à l'intérieur d'une portée de communications D2D viable, l'utilisateur du premier nœud client est alors averti qu'une session de communications D2D peut être démarrée avec le second nœud client particulier.
EP11859206.2A 2011-02-25 2011-02-25 Amélioration de la connectivité d'une session entre des dispositifs Active EP2679036B1 (fr)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/IB2011/050828 WO2012114160A1 (fr) 2011-02-25 2011-02-25 Amélioration de la connectivité d'une session entre des dispositifs

Publications (3)

Publication Number Publication Date
EP2679036A1 true EP2679036A1 (fr) 2014-01-01
EP2679036A4 EP2679036A4 (fr) 2016-12-07
EP2679036B1 EP2679036B1 (fr) 2018-09-05

Family

ID=46720158

Family Applications (1)

Application Number Title Priority Date Filing Date
EP11859206.2A Active EP2679036B1 (fr) 2011-02-25 2011-02-25 Amélioration de la connectivité d'une session entre des dispositifs

Country Status (5)

Country Link
US (2) US9237590B2 (fr)
EP (1) EP2679036B1 (fr)
CN (1) CN103416081B (fr)
CA (1) CA2828074C (fr)
WO (1) WO2012114160A1 (fr)

Families Citing this family (27)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CA2827866C (fr) 2011-02-25 2016-07-12 Blackberry Limited Determination de la proximite de dispositifs a l'interieur d'une portee de communication
WO2012114160A1 (fr) 2011-02-25 2012-08-30 Research In Motion Limited Amélioration de la connectivité d'une session entre des dispositifs
CN102244873A (zh) * 2011-08-26 2011-11-16 北京邮电大学 一种基于d2d用户对的位置为其和蜂窝用户选择资源复用模式的方法
US20150016364A1 (en) * 2011-09-22 2015-01-15 Nokia Corporation Method And Apparatus For Facilitating Remote Participance In A Community
US9516691B2 (en) * 2012-01-16 2016-12-06 Lg Electronics Inc. Method and apparatus for providing proximity service in wireless communication system
EP2810529B1 (fr) 2012-02-03 2019-05-22 Nokia Technologies Oy Procédé et appareil pour faciliter la participation à distance à une communauté
US9307564B2 (en) * 2012-05-18 2016-04-05 Qualcomm Incorporated Automatic device-to-device connection control by environmental information
GB2503441A (en) 2012-06-26 2014-01-01 Ibm Managing mobile devices using other mobile devices based on loation
KR101897761B1 (ko) * 2012-12-06 2018-09-12 한국전자통신연구원 이동통신 시스템에서 디바이스간 직접통신을 위한 근접도 측정 방법 및 장치
US9635657B2 (en) 2012-12-21 2017-04-25 Blackberry Limited Resource scheduling in direct device to device communications systems
US9699589B2 (en) 2012-12-21 2017-07-04 Blackberry Limited Managing sessions for direct device to device communications
US9295044B2 (en) 2012-12-21 2016-03-22 Blackberry Limited Resource scheduling in direct device to device communications systems
US9271302B2 (en) 2012-12-21 2016-02-23 Blackberry Limited Network-managed direct device to device communications
EP2753133B1 (fr) * 2013-01-08 2016-04-06 HTC Corporation Procédé de gestion de service de proximité dans un système de communication sans fil
ES2643413T3 (es) 2013-03-26 2017-11-22 Telefonaktiebolaget Lm Ericsson (Publ) Procedimiento y aparato para posicionamiento cooperativo en una red de comunicación inalámbrica
EP3051851B1 (fr) * 2013-09-27 2019-07-31 Kyocera Corporation Terminal utilisateur et dispositif de réseau
US9609680B2 (en) * 2014-03-18 2017-03-28 Qualcomm Incorporated Signaling flows and buffer status report for a group in device-to-device broadcast communication
US20150289127A1 (en) * 2014-04-02 2015-10-08 Innovative Sonic Corporation Method and apparatus for providing proximity information in a wireless communication system
DE102015105238A1 (de) * 2014-04-08 2015-10-08 Broadcom Corp. System zur präemptiven und approximativen verknüpfung in industrienetzwerken
RU2663711C2 (ru) * 2014-04-22 2018-08-08 Хуавей Текнолоджиз Ко., Лтд. Способ, устройство и система обнаружения передачи данных d2d
CN105338018A (zh) * 2014-06-30 2016-02-17 奇点新源国际技术开发(北京)有限公司 一种地图信息推送方法及装置
US9628565B2 (en) 2014-07-23 2017-04-18 Here Global B.V. Highly assisted driving platform
US20160050572A1 (en) * 2014-08-18 2016-02-18 Rohde & Schwarz Gmbh & Co. Kg Radio communication test apparatus and method for testing
US10034155B2 (en) 2014-08-19 2018-07-24 Ernesto Nebel Decentralized systems and methods for facilitating social discovery
CN105592550B (zh) * 2014-11-17 2019-05-24 电信科学技术研究院 一种资源分配方法、设备及系统
US20160157193A1 (en) * 2014-12-01 2016-06-02 Emily Qi Exchanging ranging and location information among peer-to-peer devices
CN112188529B (zh) * 2020-10-22 2023-05-16 中国联合网络通信集团有限公司 微基站运行的方法、微基站

Family Cites Families (36)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5666661A (en) 1994-03-10 1997-09-09 Motorola, Inc. Method for automatically bypassing the use of a communication system infrastructure
US7606936B2 (en) * 1998-05-29 2009-10-20 Research In Motion Limited System and method for redirecting data to a wireless device over a plurality of communication paths
US6580704B1 (en) 1999-08-26 2003-06-17 Nokia Corporation Direct mode communication method between two mobile terminals in access point controlled wireless LAN systems
JP3515027B2 (ja) * 1999-10-14 2004-04-05 三菱電機株式会社 無線端末管理装置
US7027820B2 (en) 2001-01-31 2006-04-11 Hewlett-Packard Development Company, L.P. Location data validation by static entities receiving location data items by short-range communication
GB2390510A (en) 2002-07-05 2004-01-07 Nokia Corp Direct mode communication between mobiles
FR2842984B1 (fr) 2002-07-25 2004-09-17 Nec Technologies Uk Ltd Procede et dispositif de selection de reseaux de telecommunication
US7248625B2 (en) * 2002-09-05 2007-07-24 Silicon Storage Technology, Inc. Compensation of I-Q imbalance in digital transceivers
US7256711B2 (en) * 2003-02-14 2007-08-14 Networks In Motion, Inc. Method and system for saving and retrieving spatial related information
CN1549613A (zh) * 2003-05-19 2004-11-24 �ʼҷ����ֵ��ӹɷ����޹�˾ 在无线通信系统的p2p通信模式与传统通信模式之间软切换的方法和装置
US8639819B2 (en) 2004-02-05 2014-01-28 Nokia Corporation Ad-hoc connection between electronic devices
CA2573214C (fr) * 2004-07-09 2013-06-11 Codemate Aps Entite homologue de reseau d'entites homologues, et reseau de ce type
US7164930B2 (en) 2004-12-31 2007-01-16 Motorola, Inc. Switching a call from a network assisted communication mode to a direct communication mode
US20060240855A1 (en) * 2005-04-22 2006-10-26 Amit Kalhan Systems and methods for updating presence in a mobile communication network
US7444137B1 (en) * 2005-11-01 2008-10-28 At&T Mobility Ii Llc Cell broadcast via encoded message to an embedded client
US20080139114A1 (en) * 2006-12-06 2008-06-12 Motorola, Inc. Method for determining user location based on association with seamless mobility context
US7812717B1 (en) 2007-02-02 2010-10-12 Resource Consortium Limited Situational network
US8522019B2 (en) 2007-02-23 2013-08-27 Qualcomm Incorporated Method and apparatus to create trust domains based on proximity
EP1968243A1 (fr) 2007-03-07 2008-09-10 British Telecommunications Public Limited Company Procédé de transmission de données dans un dispositif portable
US7944905B2 (en) * 2007-05-29 2011-05-17 Motorola Solutions, Inc. Method for dynamically identifying locations of mobile nodes in a time division multiple access based ad hoc communication network
US8254350B2 (en) * 2007-06-14 2012-08-28 International Business Machines Corporation Routing packets in an ad hoc wireless network
US20080318592A1 (en) * 2007-06-22 2008-12-25 International Business Machines Corporation Delivering telephony communications to devices proximate to a recipient after automatically determining the recipient's location
US8521194B2 (en) 2007-07-10 2013-08-27 Qualcomm Incorporated Performing paging in a wireless peer-to-peer network
GB2454645B (en) 2007-08-31 2012-05-09 Ericsson Telefon Ab L M Location update of a mobile node
CN201173970Y (zh) 2008-04-08 2008-12-31 北京浩澜高科科技发展有限公司 带有指纹身份识别的监控定位终端及监控定位系统
US8554200B2 (en) 2008-09-12 2013-10-08 Nokia Corporation Method and apparatus for providing interference measurements for device to-device communication
US8010131B2 (en) 2008-09-16 2011-08-30 Rothschild Leigh M System and method for enabling social interactive wireless communications
US8818861B2 (en) * 2008-10-01 2014-08-26 Nokia Corporation Finding mobile station for device-to-device communication
GB2466049A (en) * 2008-12-10 2010-06-16 Symbian Software Ltd Distance determination between two or more communicating devices
US9351340B2 (en) 2009-04-08 2016-05-24 Nokia Technologies Oy Apparatus and method for mode selection for device-to-device communications
US8385240B2 (en) * 2009-09-03 2013-02-26 Qualcomm Incorporated Selection and utilization of shared wireless wide area network modems
US8666403B2 (en) 2009-10-23 2014-03-04 Nokia Solutions And Networks Oy Systems, methods, and apparatuses for facilitating device-to-device connection establishment
US8884817B2 (en) * 2009-12-31 2014-11-11 CSR Technology Holdings Inc. GPS with aiding from ad-hoc peer-to-peer bluetooth networks
US8588803B2 (en) 2010-06-18 2013-11-19 Nokia Corporation Method and apparatus for resource scheduling for network controlled D2D communications
WO2012114160A1 (fr) 2011-02-25 2012-08-30 Research In Motion Limited Amélioration de la connectivité d'une session entre des dispositifs
CA2827866C (fr) 2011-02-25 2016-07-12 Blackberry Limited Determination de la proximite de dispositifs a l'interieur d'une portee de communication

Also Published As

Publication number Publication date
US9468032B2 (en) 2016-10-11
EP2679036A4 (fr) 2016-12-07
WO2012114160A1 (fr) 2012-08-30
US20160128122A1 (en) 2016-05-05
CN103416081A (zh) 2013-11-27
CA2828074C (fr) 2017-08-15
EP2679036B1 (fr) 2018-09-05
CA2828074A1 (fr) 2012-08-30
US20130331135A1 (en) 2013-12-12
US9237590B2 (en) 2016-01-12
CN103416081B (zh) 2017-08-04

Similar Documents

Publication Publication Date Title
US9468032B2 (en) Inter-device session connectivity enhancement
US10959168B2 (en) Collaborative scheme for selection of optimal accesses and seamless transition between accesses
EP2679034B1 (fr) Détermination de la proximité de dispositifs à l'intérieur d'une portée de communication
US9781199B2 (en) Managed peer-to-peer sharing in cellular networks
US20180115924A1 (en) Dynamic Exchange Of Wireless Communication Services
KR20120003931A (ko) 통신 시스템에서 피어 발견을 위한 방법들 및 장치
JP2010136291A (ja) コグニティブ無線システムにおける利用周波数帯調整方法および無線通信装置
CN105453615B (zh) 无线终端、无线终端的搜索处理方法和无线通信系统
TW201130365A (en) Multi-user, multi-mode baseband signaling methods, timing/frequency synchronization, and receiver architectures
EP3063962A1 (fr) Services basés sur la proximité
JP2014143651A (ja) 移動体通信システム、通信方法、および基地局装置
WO2018014669A1 (fr) Procédé et dispositif de transmission de données
KR101553601B1 (ko) 단말간 핸드오버를 지원하기 위한 방법 및 시스템
JP2018042138A (ja) 通信切替装置、アクセスポイント、端末、通信切替方法

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20130925

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

DAX Request for extension of the european patent (deleted)
RA4 Supplementary search report drawn up and despatched (corrected)

Effective date: 20161107

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 76/02 20090101ALI20161031BHEP

Ipc: H04W 84/18 20090101ALI20161031BHEP

Ipc: H04W 8/20 20090101AFI20161031BHEP

Ipc: H04W 4/02 20090101ALI20161031BHEP

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602011051884

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04W0008200000

Ipc: H04W0076140000

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

RIC1 Information provided on ipc code assigned before grant

Ipc: H04L 5/00 20060101ALN20180308BHEP

Ipc: G06F 17/30 20060101ALN20180308BHEP

Ipc: H04W 8/08 20090101ALN20180308BHEP

Ipc: H04W 76/14 20180101AFI20180308BHEP

Ipc: H04W 4/80 20180101ALN20180308BHEP

Ipc: H04W 8/00 20090101ALN20180308BHEP

Ipc: H04W 84/18 20090101ALN20180308BHEP

INTG Intention to grant announced

Effective date: 20180405

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1039439

Country of ref document: AT

Kind code of ref document: T

Effective date: 20180915

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602011051884

Country of ref document: DE

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20180905

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180905

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181205

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180905

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180905

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180905

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181205

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181206

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1039439

Country of ref document: AT

Kind code of ref document: T

Effective date: 20180905

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180905

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180905

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180905

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180905

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180905

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180905

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180905

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180905

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180905

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180905

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190105

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180905

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190105

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180905

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180905

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602011051884

Country of ref document: DE

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180905

26N No opposition filed

Effective date: 20190606

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180905

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180905

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190225

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20190228

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190228

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190228

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190225

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190228

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180905

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MT

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190225

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180905

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20110225

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180905

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20230223

Year of fee payment: 13

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20230227

Year of fee payment: 13

Ref country code: DE

Payment date: 20230223

Year of fee payment: 13