US20150089382A1 - Application context migration framework and protocol - Google Patents

Application context migration framework and protocol Download PDF

Info

Publication number
US20150089382A1
US20150089382A1 US14/226,684 US201414226684A US2015089382A1 US 20150089382 A1 US20150089382 A1 US 20150089382A1 US 201414226684 A US201414226684 A US 201414226684A US 2015089382 A1 US2015089382 A1 US 2015089382A1
Authority
US
United States
Prior art keywords
computer system
context
static object
target
associated
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.)
Abandoned
Application number
US14/226,684
Inventor
Wu-chi Feng
Muthaiah Venkatachalam
Meghashree Kedalagudde
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.)
Intel IP Corp
Original Assignee
Intel IP Corp
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
Priority to US201361883127P priority Critical
Application filed by Intel IP Corp filed Critical Intel IP Corp
Priority to US14/226,684 priority patent/US20150089382A1/en
Assigned to Intel IP Corporation reassignment Intel IP Corporation ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: FENG, WU-CHI, KEDALAGUDDE, Meghashree, VENKATACHALAM, MUTHAIAH
Publication of US20150089382A1 publication Critical patent/US20150089382A1/en
Application status is Abandoned legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/0001Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0023Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the signalling
    • H04L1/0027Scheduling of signalling, e.g. occurrence thereof
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W24/00Supervisory, monitoring or testing arrangements
    • H04W24/04Arrangements for maintaining operational condition
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46Multiprogramming arrangements
    • G06F9/48Program initiating; Program switching, e.g. by interrupt
    • G06F9/4806Task transfer initiation or dispatching
    • G06F9/4843Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
    • G06F9/485Task life-cycle, e.g. stopping, restarting, resuming execution
    • G06F9/4856Task life-cycle, e.g. stopping, restarting, resuming execution resumption being on a different machine, e.g. task migration, virtual machine migration
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04BTRANSMISSION
    • H04B7/00Radio transmission systems, i.e. using radiation field
    • H04B7/02Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/06Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station
    • H04B7/0613Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission
    • H04B7/0615Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission of weighted versions of same signal
    • H04B7/0619Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission of weighted versions of same signal using feedback from receiving side
    • H04B7/0621Feedback content
    • H04B7/0626Channel coefficients, e.g. channel state information [CSI]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04BTRANSMISSION
    • H04B7/00Radio transmission systems, i.e. using radiation field
    • H04B7/02Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/06Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station
    • H04B7/0613Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission
    • H04B7/0615Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission of weighted versions of same signal
    • H04B7/0619Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission of weighted versions of same signal using feedback from receiving side
    • H04B7/0621Feedback content
    • H04B7/0632Channel quality parameters, e.g. channel quality indicator [CQI]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04BTRANSMISSION
    • H04B7/00Radio transmission systems, i.e. using radiation field
    • H04B7/02Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/06Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station
    • H04B7/0613Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission
    • H04B7/0615Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission of weighted versions of same signal
    • H04B7/0619Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission of weighted versions of same signal using feedback from receiving side
    • H04B7/0636Feedback format
    • H04B7/0639Using selective indices, e.g. of a codebook, e.g. pre-distortion matrix index [PMI] or for beam selection
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/0001Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0023Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the signalling
    • H04L1/0026Transmission of channel quality indication
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/1607Details of the supervisory signal
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18Automatic repetition systems, e.g. van Duuren system ; ARQ protocols
    • H04L1/1829Arrangements specific to the receiver end
    • H04L1/1854Scheduling and prioritising arrangements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18Automatic repetition systems, e.g. van Duuren system ; ARQ protocols
    • H04L1/1867Arrangements specific to the transmitter end
    • H04L1/1887Scheduling and prioritising arrangements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic regulation in packet switching networks
    • H04L47/10Flow control or congestion control
    • H04L47/12Congestion avoidance or recovery
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic regulation in packet switching networks
    • H04L47/10Flow control or congestion control
    • H04L47/12Congestion avoidance or recovery
    • H04L47/122Diverting traffic away from congested spots
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/0001Arrangements for dividing the transmission path
    • H04L5/0003Two-dimensional division
    • H04L5/0005Time-frequency
    • H04L5/0007Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • H04L5/001Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT the frequencies being arranged in component carriers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/003Arrangements for allocating sub-channels of the transmission path
    • H04L5/0032Distributed allocation, i.e. involving a plurality of allocating devices, each making partial allocation
    • H04L5/0035Resource allocation in a cooperative multipoint environment
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/003Arrangements for allocating sub-channels of the transmission path
    • H04L5/0037Inter-user or inter-terminal allocation
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/003Arrangements for allocating sub-channels of the transmission path
    • H04L5/0048Allocation of pilot signals, i.e. of signals known to the receiver
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/003Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053Allocation of signaling, i.e. of overhead other than pilot signals
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/003Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053Allocation of signaling, i.e. of overhead other than pilot signals
    • H04L5/0055Physical resource allocation for ACK/NACK
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/003Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053Allocation of signaling, i.e. of overhead other than pilot signals
    • H04L5/0057Physical resource allocation for CQI
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network-specific arrangements or communication protocols supporting networked applications
    • H04L67/02Network-specific arrangements or communication protocols supporting networked applications involving the use of web-based technology, e.g. hyper text transfer protocol [HTTP]
    • H04L67/025Network-specific arrangements or communication protocols supporting networked applications involving the use of web-based technology, e.g. hyper text transfer protocol [HTTP] for remote control or remote monitoring of the application
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network-specific arrangements or communication protocols supporting networked applications
    • H04L67/10Network-specific arrangements or communication protocols supporting networked applications in which an application is distributed across nodes in the network
    • H04L67/104Network-specific arrangements or communication protocols supporting networked applications in which an application is distributed across nodes in the network for peer-to-peer [P2P] networking; Functionalities or architectural details of P2P networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network-specific arrangements or communication protocols supporting networked applications
    • H04L67/10Network-specific arrangements or communication protocols supporting networked applications in which an application is distributed across nodes in the network
    • H04L67/104Network-specific arrangements or communication protocols supporting networked applications in which an application is distributed across nodes in the network for peer-to-peer [P2P] networking; Functionalities or architectural details of P2P networks
    • H04L67/1061Network-specific arrangements or communication protocols supporting networked applications in which an application is distributed across nodes in the network for peer-to-peer [P2P] networking; Functionalities or architectural details of P2P networks involving node-based peer discovery mechanisms
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W24/00Supervisory, monitoring or testing arrangements
    • H04W24/10Scheduling measurement reports ; Arrangements for measurement reports
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic or resource management
    • H04W28/02Traffic management, e.g. flow control or congestion control
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/24Reselection being triggered by specific parameters used to improve the performance of a single terminal
    • H04W36/32Reselection being triggered by specific parameters used to improve the performance of a single terminal by location or mobility data, e.g. speed data
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W40/00Communication routing or communication path finding
    • H04W40/02Communication route or path selection, e.g. power-based or shortest path routing
    • H04W40/22Communication route or path selection, e.g. power-based or shortest path routing using selective relaying for reaching a BTS [Base Transceiver Station] or an access point
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W40/00Communication routing or communication path finding
    • H04W40/24Connectivity information management, e.g. connectivity discovery or connectivity update
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W48/00Access restriction; Network selection; Access point selection
    • H04W48/16Discovering, processing access restriction or access information
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W52/00Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02Power saving arrangements
    • H04W52/0209Power saving arrangements in terminal devices
    • H04W52/0261Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level
    • H04W52/0274Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level by switching on or off the equipment or parts thereof
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management, e.g. wireless traffic scheduling or selection or allocation of wireless resources
    • H04W72/04Wireless resource allocation
    • H04W72/0406Wireless resource allocation involving control information exchange between nodes
    • H04W72/042Wireless resource allocation involving control information exchange between nodes in downlink direction of a wireless link, i.e. towards terminal
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management, e.g. wireless traffic scheduling or selection or allocation of wireless resources
    • H04W72/04Wireless resource allocation
    • H04W72/044Wireless resource allocation where an allocation plan is defined based on the type of the allocated resource
    • H04W72/0446Wireless resource allocation where an allocation plan is defined based on the type of the allocated resource the resource being a slot, sub-slot or frame
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management, e.g. wireless traffic scheduling or selection or allocation of wireless resources
    • H04W72/04Wireless resource allocation
    • H04W72/044Wireless resource allocation where an allocation plan is defined based on the type of the allocated resource
    • H04W72/0453Wireless resource allocation where an allocation plan is defined based on the type of the allocated resource the resource being a frequency, carrier or frequency band
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup
    • H04W76/14Direct-mode setup
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup
    • H04W76/18Management of setup rejection or failure
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/20Manipulation of established connections
    • H04W76/27Transitions between radio resource control [RRC] states
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/30Connection release
    • H04W76/38Connection release triggered by timers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/005Discovery of network devices, e.g. terminals
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W88/00Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02Terminal devices
    • H04W88/06Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W88/00Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08Access point devices
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/03Reselecting a link using a direct mode connection
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W84/00Network topologies
    • H04W84/02Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/10Small scale networks; Flat hierarchical networks
    • H04W84/12WLAN [Wireless Local Area Networks]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W92/00Interfaces specially adapted for wireless communication networks
    • H04W92/16Interfaces between hierarchically similar devices
    • H04W92/20Interfaces between hierarchically similar devices between access points
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THIR OWN ENERGY USE
    • Y02D10/00Energy efficient computing
    • Y02D10/20Reducing energy consumption by means of multiprocessor or multiprocessing based techniques, other than acting upon the power supply
    • Y02D10/24Scheduling
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THIR OWN ENERGY USE
    • Y02D10/00Energy efficient computing
    • Y02D10/30Reducing energy consumption in distributed systems
    • Y02D10/32Delegation or migration
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THIR OWN ENERGY USE
    • Y02D70/00Techniques for reducing energy consumption in wireless communication networks
    • Y02D70/10Techniques for reducing energy consumption in wireless communication networks according to the Radio Access Technology [RAT]
    • Y02D70/12Techniques for reducing energy consumption in wireless communication networks according to the Radio Access Technology [RAT] in 3rd Generation Partnership Project [3GPP] networks
    • Y02D70/122Techniques for reducing energy consumption in wireless communication networks according to the Radio Access Technology [RAT] in 3rd Generation Partnership Project [3GPP] networks in 2nd generation [2G] networks
    • Y02D70/1224Techniques for reducing energy consumption in wireless communication networks according to the Radio Access Technology [RAT] in 3rd Generation Partnership Project [3GPP] networks in 2nd generation [2G] networks in General Packet Radio Service [GPRS] networks
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THIR OWN ENERGY USE
    • Y02D70/00Techniques for reducing energy consumption in wireless communication networks
    • Y02D70/10Techniques for reducing energy consumption in wireless communication networks according to the Radio Access Technology [RAT]
    • Y02D70/12Techniques for reducing energy consumption in wireless communication networks according to the Radio Access Technology [RAT] in 3rd Generation Partnership Project [3GPP] networks
    • Y02D70/124Techniques for reducing energy consumption in wireless communication networks according to the Radio Access Technology [RAT] in 3rd Generation Partnership Project [3GPP] networks in 3rd generation [3G] networks
    • Y02D70/1242Techniques for reducing energy consumption in wireless communication networks according to the Radio Access Technology [RAT] in 3rd Generation Partnership Project [3GPP] networks in 3rd generation [3G] networks in Universal Mobile Telecommunications Systems [UMTS] networks
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THIR OWN ENERGY USE
    • Y02D70/00Techniques for reducing energy consumption in wireless communication networks
    • Y02D70/10Techniques for reducing energy consumption in wireless communication networks according to the Radio Access Technology [RAT]
    • Y02D70/12Techniques for reducing energy consumption in wireless communication networks according to the Radio Access Technology [RAT] in 3rd Generation Partnership Project [3GPP] networks
    • Y02D70/124Techniques for reducing energy consumption in wireless communication networks according to the Radio Access Technology [RAT] in 3rd Generation Partnership Project [3GPP] networks in 3rd generation [3G] networks
    • Y02D70/1244Techniques for reducing energy consumption in wireless communication networks according to the Radio Access Technology [RAT] in 3rd Generation Partnership Project [3GPP] networks in 3rd generation [3G] networks in High-Speed Downlink Packet Access [HSDPA] networks
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THIR OWN ENERGY USE
    • Y02D70/00Techniques for reducing energy consumption in wireless communication networks
    • Y02D70/10Techniques for reducing energy consumption in wireless communication networks according to the Radio Access Technology [RAT]
    • Y02D70/12Techniques for reducing energy consumption in wireless communication networks according to the Radio Access Technology [RAT] in 3rd Generation Partnership Project [3GPP] networks
    • Y02D70/126Techniques for reducing energy consumption in wireless communication networks according to the Radio Access Technology [RAT] in 3rd Generation Partnership Project [3GPP] networks in 4th generation [4G] networks
    • Y02D70/1262Techniques for reducing energy consumption in wireless communication networks according to the Radio Access Technology [RAT] in 3rd Generation Partnership Project [3GPP] networks in 4th generation [4G] networks in Long-Term Evolution [LTE] networks
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THIR OWN ENERGY USE
    • Y02D70/00Techniques for reducing energy consumption in wireless communication networks
    • Y02D70/10Techniques for reducing energy consumption in wireless communication networks according to the Radio Access Technology [RAT]
    • Y02D70/12Techniques for reducing energy consumption in wireless communication networks according to the Radio Access Technology [RAT] in 3rd Generation Partnership Project [3GPP] networks
    • Y02D70/126Techniques for reducing energy consumption in wireless communication networks according to the Radio Access Technology [RAT] in 3rd Generation Partnership Project [3GPP] networks in 4th generation [4G] networks
    • Y02D70/1264Techniques for reducing energy consumption in wireless communication networks according to the Radio Access Technology [RAT] in 3rd Generation Partnership Project [3GPP] networks in 4th generation [4G] networks in Long-Term Evolution Advanced [LTE-A] networks
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THIR OWN ENERGY USE
    • Y02D70/00Techniques for reducing energy consumption in wireless communication networks
    • Y02D70/10Techniques for reducing energy consumption in wireless communication networks according to the Radio Access Technology [RAT]
    • Y02D70/14Techniques for reducing energy consumption in wireless communication networks according to the Radio Access Technology [RAT] in Institute of Electrical and Electronics Engineers [IEEE] networks
    • Y02D70/142Techniques for reducing energy consumption in wireless communication networks according to the Radio Access Technology [RAT] in Institute of Electrical and Electronics Engineers [IEEE] networks in Wireless Local Area Networks [WLAN]
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THIR OWN ENERGY USE
    • Y02D70/00Techniques for reducing energy consumption in wireless communication networks
    • Y02D70/10Techniques for reducing energy consumption in wireless communication networks according to the Radio Access Technology [RAT]
    • Y02D70/14Techniques for reducing energy consumption in wireless communication networks according to the Radio Access Technology [RAT] in Institute of Electrical and Electronics Engineers [IEEE] networks
    • Y02D70/144Techniques for reducing energy consumption in wireless communication networks according to the Radio Access Technology [RAT] in Institute of Electrical and Electronics Engineers [IEEE] networks in Bluetooth and Wireless Personal Area Networks [WPAN]
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THIR OWN ENERGY USE
    • Y02D70/00Techniques for reducing energy consumption in wireless communication networks
    • Y02D70/10Techniques for reducing energy consumption in wireless communication networks according to the Radio Access Technology [RAT]
    • Y02D70/14Techniques for reducing energy consumption in wireless communication networks according to the Radio Access Technology [RAT] in Institute of Electrical and Electronics Engineers [IEEE] networks
    • Y02D70/146Techniques for reducing energy consumption in wireless communication networks according to the Radio Access Technology [RAT] in Institute of Electrical and Electronics Engineers [IEEE] networks in Worldwide Interoperability for Microwave Access [WiMAX] networks
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THIR OWN ENERGY USE
    • Y02D70/00Techniques for reducing energy consumption in wireless communication networks
    • Y02D70/10Techniques for reducing energy consumption in wireless communication networks according to the Radio Access Technology [RAT]
    • Y02D70/16Techniques for reducing energy consumption in wireless communication networks according to the Radio Access Technology [RAT] in other wireless communication networks
    • Y02D70/164Techniques for reducing energy consumption in wireless communication networks according to the Radio Access Technology [RAT] in other wireless communication networks in Satellite Navigation receivers
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THIR OWN ENERGY USE
    • Y02D70/00Techniques for reducing energy consumption in wireless communication networks
    • Y02D70/10Techniques for reducing energy consumption in wireless communication networks according to the Radio Access Technology [RAT]
    • Y02D70/16Techniques for reducing energy consumption in wireless communication networks according to the Radio Access Technology [RAT] in other wireless communication networks
    • Y02D70/166Techniques for reducing energy consumption in wireless communication networks according to the Radio Access Technology [RAT] in other wireless communication networks in Radio Frequency Identification [RF-ID] transceivers
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THIR OWN ENERGY USE
    • Y02D70/00Techniques for reducing energy consumption in wireless communication networks
    • Y02D70/20Techniques for reducing energy consumption in wireless communication networks independent of Radio Access Technologies
    • Y02D70/21Techniques for reducing energy consumption in wireless communication networks independent of Radio Access Technologies in machine-to-machine [M2M] and device-to-device [D2D] communications
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THIR OWN ENERGY USE
    • Y02D70/00Techniques for reducing energy consumption in wireless communication networks
    • Y02D70/20Techniques for reducing energy consumption in wireless communication networks independent of Radio Access Technologies
    • Y02D70/22Techniques for reducing energy consumption in wireless communication networks independent of Radio Access Technologies in peer-to-peer [P2P], ad hoc and mesh networks
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THIR OWN ENERGY USE
    • Y02D70/00Techniques for reducing energy consumption in wireless communication networks
    • Y02D70/20Techniques for reducing energy consumption in wireless communication networks independent of Radio Access Technologies
    • Y02D70/23Techniques for reducing energy consumption in wireless communication networks independent of Radio Access Technologies in Voice over IP [VoIP] networks
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THIR OWN ENERGY USE
    • Y02D70/00Techniques for reducing energy consumption in wireless communication networks
    • Y02D70/20Techniques for reducing energy consumption in wireless communication networks independent of Radio Access Technologies
    • Y02D70/26Techniques for reducing energy consumption in wireless communication networks independent of Radio Access Technologies in wearable devices, e.g. watches, glasses

Abstract

Embodiments described herein relate generally to the migration of a static object, such as an electronic document, across separate computer systems while retaining context data associated with the static object. In one embodiment, a source computer system is adapted to package a static object and associated context information and transmit the package over a network to a target computer system. The target computer system may present the static object in an application with the associated context information to substantially approximate presentation of the same at the source computer system. Other embodiments may be described and claimed.

Description

    CROSS REFERENCE TO RELATED APPLICATIONS
  • This application claims priority under 35 U.S.C. §119(e) to U.S. Provisional Patent Application No. 61/883,127 entitled “ADVANCED WIRELESS COMMUNICATION SYSTEMS AND TECHNIQUES,” filed Sep. 26, 2013, the disclosure of which is incorporated herein by reference.
  • FIELD OF INVENTION
  • Embodiments of the present invention relate generally to the technical field of data processing, and more particularly, to computer systems adapted to operate to communicate data over networks.
  • BACKGROUND
  • The background description provided herein is for the purpose of generally presenting the context of the disclosure. Work of the presently named inventors, to the extent it is described in this background section, as well as aspects of the description that may not otherwise qualify as prior art at the time of filing, are neither expressly nor impliedly admitted as prior art against the present disclosure. Unless otherwise indicated herein, the approaches described in this section are not prior art to the claims in the present disclosure and are not admitted to be prior art by the inclusion in this section.
  • Computer systems are generally adapted to execute a plurality of applications. These applications may be adapted to present a digital file to a user. Illustratively, a word processing application may be adapted to present a textual file to a user on a display of a computer system. Similarly, a multimedia application may be adapted to present a digital video and/or audio file to a user on a display and/or through a speaker of a computer system.
  • In presenting a digital file, an application may be adapted to receive input from a user. The input received from the user may be associated with the presentation of the digital file. For example, through an application, the user may adjust the playback position of an audio file or select a block of text in a textual file. In order to present such a digital file to a second user at a second computer system, the digital file may be transferred to the second computer system—e.g., via email, cloud storage, removable flash storage, etc. However, this method of transfer would not retain much of the input received at the first computer system from the first user.
  • As an alternative means of presentation of a digital file to a second user at a second computer system, the first and second computer systems may interface through remote desktop sharing. Through remote desktop sharing, the second computer system may present the digital file to the second user and, additionally, may present some interaction or input of the first user at the first computer system. However, the digital file would exist at the first computer system. Furthermore, the first and second computer systems would require an active connection to maintain the remote desktop sharing.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • The embodiments of the invention are illustrated by way of example and not by way of limitation in the figures of the accompanying drawings in which like references indicate similar elements. It should be noted that references to “an” or “one” embodiment of the invention in this disclosure are not necessarily to the same embodiment, and they mean at least one.
  • FIG. 1 is a block diagram illustrating a system for transferring a static object and associated context information from a source computer system to a target computer system, in accordance with various embodiments.
  • FIG. 2 is a block diagram illustrating a computer system that includes an application that is to present a static object with context information, in accordance with various embodiments.
  • FIG. 3 is a block diagram illustrating a computer system that is to facilitate transfer of a static object and context information between two separate computer systems, in accordance with various embodiments.
  • FIG. 4 is a block diagram illustrating transfer of a static object and associated context information between a source computer system and a target computer system, in accordance with various embodiments.
  • FIG. 5A is a block diagram illustrating one example of an application that is to present a static object with associated context information, in accordance with various embodiments.
  • FIG. 5B is a block diagram illustrating another example of an application that is to present a static object with associated context information, in accordance with various embodiments.
  • FIG. 6 is a sequence diagram illustrating one example of transfer of a static object and associated context information between separate computer systems through a manager computer system, in accordance with various embodiments.
  • FIG. 7 is a sequence diagram illustrating another example of transfer of a static object and associated context information between separate computer systems through a manager computer system, in accordance with various embodiments.
  • FIG. 8 is a flow diagram illustrating a method for generating a context package to transfer a static object and associated context information, in accordance with various embodiments.
  • FIG. 9 is a flow diagram illustrating a method for facilitating transfer of a context package between separate computer systems, in accordance with various embodiments.
  • FIG. 10 is a flow diagram illustrating a method for presenting a static object with associated context information based on a received context package, in accordance with various embodiments.
  • FIG. 11 is a flow diagram illustrating a method for collecting and transferring context data associated with a static object based on user interaction, in accordance with various embodiments.
  • DETAILED DESCRIPTION
  • In the following detailed description, reference is made to the accompanying drawings, which form a part hereof wherein like numerals designate like parts throughout, and in which is shown by way of illustration embodiments that may be practiced. It is to be understood that other embodiments may be utilized and structural or logical changes may be made without departing from the scope of the present disclosure. Therefore, the following detailed description is not to be taken in a limiting sense, and the scope of embodiments is defined by the appended claims and their equivalents.
  • Various operations may be described as multiple discrete actions or operations in turn, in a manner that is most helpful in understanding the claimed subject matter. However, the order of description should not be construed as to imply that these operations are necessarily order dependent. In particular, these operations may not be performed in the order of presentation. Operations described may be performed in a different order than the described embodiment. Various additional operations may be performed and/or described operations may be omitted in additional embodiments.
  • For the purposes of the present disclosure, the phrases “A or B” and “A and/or B” means (A), (B), or (A and B). For the purposes of the present disclosure, the phrase “A, B, and/or C” means (A), (B), (C), (A and B), (A and C), (B and C), or (A, B, and C).
  • The description may use the phrases “in an embodiment,” or “in embodiments,” which may each refer to one or more of the same or different embodiments. Furthermore, the terms “comprising,” “including,” “having,” and the like, as used with respect to embodiments of the present disclosure, are synonymous.
  • As used herein, the terms “module” and/or “logic” may refer to, be part of, or include an Application Specific Integrated Circuit (“ASIC”), an electronic circuit, a processor (shared, dedicated, or group), and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality.
  • Beginning first with FIG. 1, a block diagram shows a system 100 for transferring a static object and associated context information from a source computer system 160 to a plurality of target computer systems 110 a-b, in accordance with various embodiments. The system 100 includes, but is not limited to, a source computer system 160, a plurality of target computer systems 110 a-b, a manager computer system 150, and a network 130. Each of the target computer systems 110 a-b may be any type of computer system adapted to receive data, such as a personal computer (e.g., a desktop computer, laptop computer, server, a tablet computer), a workstation, a handheld device, a web-enabled appliance, a gaming device, a mobile phone (e.g., a Smartphone), an eBook reader, or any computing device operable to communicate over the network 130. According to embodiments, the target computer systems 110 a-b are adapted to execute at least one application that is to present a static object. A static object may be any digital file, document, or similar resource—e.g., a text document, an image file, a uniform resource identifier (“URI”), a video file, an audio file, or essentially any other type of digital file suitable to be presented by an application. Accordingly, an application may be any set of instructions adapted to present a static object—e.g., a word processing application may present a static text document, a video application may present a Moving Picture Experts Group-4 (“MPEG-4”) static video file, a web browser may present a resource pointed to by a static URI, etc. The presentation of the static object by the application may include associated context data—e.g., the presentation of an MPEG-4 static video by a video application may include context data related to a presentation resolution, a position in the presentation time, etc. According to embodiments, the target computer systems 110 a-b may be adapted to receive a static object and associated context data from the manager computer system 150 and/or the source computer system 160.
  • The target computer systems 110 a-b may be configured for intersystem communication across a network 130. The network 130 may be a public, private, wired, wireless, or hybrid network, or a combination of different types of networks. The network 130 may be implemented as a local area network (“LAN”), a wide area network (“WAN”) such as the Internet, a corporate intranet, a metropolitan area network (“MAN”), a storage area network (“SAN”), a Fibre Channel (“FC”) network, a wireless cellular network (e.g., a cellular data network), or a combination thereof.
  • The network 130 may communicatively couple the target computer systems 110 a-b with a manager computer system 150. The manager computer system 150 may include any arrangement of hardware and software embodied in a computing device configured to provide access to one or more services to the target computer systems 110 a-b over the network 130. In various embodiments, the manager computer system 150 may include a server operating system, one or more software applications, and/or hardware (e.g., dedicated hardware) adapted to transmit a static object and/or associated context data to and receive requests for the same from the target computer systems 110 a-b over the network 130. Further, the components of the manager computer system 150 may allow the manager computer system 150 to receive that static object and/or associated context data from the source computer system 160.
  • In some embodiments, the manager computer system 150 may include a plurality of physical devices (e.g., hardware distributed in multiple physical machines). Thus, the manager computer system 150 may include two or more coupled computer devices that cooperatively operate. According to such embodiments, the plurality of physical devices may be hierarchically arranged and addressable as such. This hierarchical arrangement and addressing may extend to and incorporate each of the target computer systems 110 a-b. Thus, a target computer system 110 a may be addressable by the source computer system 160 through a hierarchical address, such as an Internet Protocol (“IP”) address or other similar address.
  • The manager computer system 150 may be communicatively coupled with a source computer system 160. The source computer system 160 may be connected with the manager computer system 150 through an interconnect 170, which may be a bus or a network (e.g., a network similar to the network 130). In the system 100, the manager computer system 150 may be implemented locally (e.g., integrated with the source computer system 160) or remotely (e.g., external from the source computer system 160). In embodiments in which the manager computer system 150 is locally implemented with the source computer system 160, the source computer system 160 may engage in peer-to-peer communication with the target computer systems 110 a-b. In another embodiment, the manager computer system 150 may communicate an address (e.g., an IP address) of the source computer system to the target computer systems 110 a-b so that the source computer system 160 may communicate directly with the target computer systems 110 a-b, such as through a peer-to-peer connection.
  • Similar to the target computer systems 110 a-b, the source computer system 160 may be any type of computer system adapted to transmit data, such as a personal computer (e.g., a desktop computer, laptop computer, server, or tablet computer), a workstation, a handheld device, a web-enabled appliance, a gaming device, a mobile phone (e.g., a Smartphone), an eBook reader, or any other similar computing device. According to embodiments, the source computer system 160 is adapted to execute at least one application that is to present a static object. The presentation of the static object by the application may include associated context data. According to embodiments, the source computer system 160 may be adapted to transmit a static object and associated context data to the manager computer system 150 and/or the target computer systems 110 a-b.
  • Turning now to FIG. 2, a block diagram illustrates a computer system 200 that includes an application 211 that is to present a static object 212 with context information 214, in accordance with various embodiments. The computer system 200 may be or may be included in the target computer systems 110 a-b and/or the source computer system 160 of FIG. 1. The computer system 200 includes at least one application 211 that is adapted to present a static object with context information 214.
  • The computer system 200 includes, but is not limited to, main memory 210, storage 217, processor 218, network interface 220, a user interface 222, a display 224, and/or a speaker 226. These components may be communicatively coupled through a bus 219. The bus 219 may be any subsystem adapted to transfer data within the computer system 200. The bus 219 may include a plurality of computer buses as well as additional circuitry adapted to transfer data.
  • To communicate data with a second computer system (not shown) (e.g., a source or target computer system, depending upon the embodiment, and/or a manager computer system), the computer system 200 includes a network interface 220. The network interface 220 may accept data across a network (not shown) from an external computer system to be processed by the computer system 200. Correspondingly, the network interface 220 may transmit data across a network. The network interface 220 may be implemented in hardware, software, or a combination of the two and may include, for example, components such as a network card, network access controller, or host bus adapter. The network interface 220 is communicatively coupled with the processor 218, which executes instructions for the computer system 200. In one embodiment, some or all of the instructions for the network interface 220 are executed by the processor 218.
  • As an additional means of receiving data, the computer system 200 may include a user interface 222 to receive input from a user. The user interface 222 may allow a user to interact with the computer system 200 through various means, according to different embodiments—e.g., the user interface 222 may be presented to a user on a display 224 as a graphical user interface or through a command line interface. To receive user input, the user interface 222 may be implemented in hardware, software, or a combination of the two and may include or may be communicatively coupled with one or more hardware devices suitable for user input (e.g., a keyboard, mouse, or touch screen). Further, some or all of the instructions for the user interface 222 may be executed by the processor 218.
  • The processor 218 may be any processor suitable to execute instructions, such as instructions from the main memory 210. Accordingly, the processor 218 may be, for example, a central processing unit (“CPU”), a microprocessor, or another similar processor. In some embodiments, the processor 218 includes a plurality of processors, such as a dedicated processor (e.g., a graphics processing unit), a network processor, or any processor suitable to execute operations of the computer system 200.
  • Coupled to the processor 218 is the main memory 210. The main memory 210 may offer both short-term and long-term storage and may in fact be divided into several units (including a unit located at the processor 218). The main memory 210 may be volatile, such as static random access memory (“SRAM”) and/or dynamic random access memory (“DRAM”), and may provide storage (at least temporarily) of computer-readable instructions, data structures, software applications, and other data for the computer system 200. Such data may be loaded from the storage 217. The main memory 210 may also include cache memory, such as a cache located at the processor 218. The main memory 210 may include, but is not limited to, instructions related to the elements 211-216 that are to be executed by the processor 218: an application 211 adapted to present a static object 212 with context information 214, a context stub module 215, and an operating system 216.
  • In various embodiments, the operating system 216 is configured to initiate the execution of the instructions, such as instructions provided by the application 211 or the context stub module 215. In particular, the operating system 216 may be adapted to serve as a platform for running the application 211. The operating system 216 may be adapted to perform other operations across the components of the computer system 200, including threading, resource management, data storage control, and other similar functionalities.
  • The operating system 216 may cause the processor 218 to execute instructions for the application 211. The application 211 may include code representing instructions configured to present a static object 212 by the computer system 200. According to embodiments, the application 211 may be, for example, a word processing application, a media application, a graphics program, an editing application, a web browser application, or essentially any other type of application adapted to present the static object 212. In various embodiments, the static object 212 may be, for example, a text document, an image file, a uniform resource identifier (“URI”), a video file, an audio file, or essentially any other type of digital file suitable to be presented by the application 211.
  • In some embodiments, the presentation of the static object 212 by the application 211 may be at the display 224. The display 224 may be any suitable device adapted to graphically present data to a user, such as a light-emitting diode (“LED”), an organic LED (“OLED”), a liquid crystal display (“LCD”), an LED-backlit LCD, a plasma display panel (“PDP”), a cathode ray tube (“CRT”), or other display technology. According to some embodiments, the presentation of the static object 212 by the application 211 may be at the speaker 226, which may be any electroacoustic transducer adapted to produce sound in response to an audio signal from the application 211. The application 211 may cause the static object 212 to be contemporaneously presented at both the display 224 and the speaker 226. The display 224 and the speaker 226 are illustrative devices for the presentation of the static object 212 by the application 211, and other methods of presentation of the static object 212 by the application 211 are contemplated herein.
  • In various embodiments, context information 214 may be associated with the presentation of the static object 212 by the application 211. Context information 214 may be received, such as through the network interface 220 and/or the user interface 222, and/or may be stored at the storage 217 of the computer system 200, such as a default setting for the application 211. Context information 214 may be essentially any information associated with the presentation of the static object 212 by the application 211. According to embodiments, context information 214 may include, for example, resolution information, a location associated with presentation of the static object 212 through the application 211 (e.g., the fifth paragraph of a text document, four minutes into an audio file, etc.), an object on a clipboard accessible by the application 211, a command history associated with the presentation of the static object 212 by the application 211 (e.g., one or more commands that the application 211 may undo and/or redo), a context of one or more objects included in the static object 212 (e.g., a status of an embedded image, a playback position of a video, etc.), a toolbar configuration, a presentation configuration (e.g., split screen, maximized, minimized, etc.), cookie information, session information, or other information associated with the presentation of the static object 212 by the application 211.
  • To re-create the presentation of the static object 212 with the context information 214 by the application 211, the application 211 may communicate with a context stub module 215. Where the computer system 200 is a source computer system, the context stub module 215 may be responsible for packaging and/or transmitting the static object 212 and the context information 214 (e.g., through the network interface 220). The context stub module 215 may receive a selection of a target computer device and/or manager computer device that is to receive the static object 212 and the context information 214 (e.g., as user input through user interface 222). The context stub module 215 may be adapted to generate a context package that is to include the static object 212 and the context information 214 without copying registers (not shown), or other memory. The context stub module 215 may then be adapted to transmit the generated context package.
  • Where the computer system 200 is a target computer system, the context stub module 215 may be responsible for receiving the static object 212 and the context information 214 and/or extracting the same from a context package. Accordingly, the context stub module 215 may communicate with the application 211 to re-create presentation of the static object 212 with associated context information 214 that is similar to the presentation at a source computer device. In embodiments, the context stub module 215 may receive a selection of a context package, a source computer device, and/or a manager computer system from which to receive the context package. The context stub module 215 may receive a context package through, for example, a push service or a pull service (e.g., the context module 215 may transmit a request for a context package).
  • With respect to FIG. 3, a block diagram is shown illustrating a manager computer system 300 that is to facilitate transfer of a context package 311 between two separate computer systems (not shown), in accordance with various embodiments. The manager computer system 300 may be or may be included in the manager computer system 150 of FIG. 1. The manager computer system 300 may include a main memory 310, storage 317, processor 318, bus or interconnect system 319, and/or network interface 320 similar to those elements described with respect to the computer system 200 of FIG. 2.
  • The main memory 310 may include, but is not limited to, instructions related to the elements 311-316 that are to be executed by the processor 318: a context package 311, a source list 312, a target list 314, a request manager 315, and an operating system 316. In various embodiments, the operating system 316 is configured to initiate the execution of the instructions, such as instructions provided by the request manager 315. The operating system 316 may be adapted to perform other operations across the components of the manager computer system 300, including threading, resource management, data storage control, and other similar functionality. The operating system 316 may cause the processor 318 to execute instructions.
  • The manager computer system 300 is adapted to facilitate the transfer of a static object and associated context information between source and target computer systems (not shown). In embodiments, the static object and associated context information may be received, from a source computer system, at the manager computer system 300 as a context package 311. In response, the manager computer system 300 may cache the context package 311 in, for example, the main memory 310 and/or store the context package 311 in the storage 317. The manager computer system 300 may be adapted to supply a target list 314 to the transmitting source computer system. Similarly, the manager computer system 300 may be adapted to supply a source list 312 to a target computer system. Additionally, the manager computer system 300 may be adapted to transmit the context package 311 to a target computer system.
  • According to some embodiments, the manager computer system may be adapted to manage reception and transmission of the context package 311 through a request manager 315. The request manager 315 may receive a selection of a target computer system (e.g., a target computer system included in the target list 314) from a source computer system that is to transmit the context package 311. Therefore, the request manager 315 may associate the context package 311 with an address for a target computer system, such as an IP address or similar hierarchical address. The request manager 315 may therefore cause the context package 311 to be transmitted to the addressed target machine.
  • In embodiments, the request manager 315 may receive a selection of a source computer system (e.g., a source computer system included in the source list 312) from a target computer system that is to receive the context package 311. Alternatively, the request manager 315 may receive a request for the context package 311 specifically. In response, the request manager 315 may transmit the context package 311 to the target computer system.
  • FIG. 4 illustrates a block diagram of a system 400 for transfer of a static object 415 and associated context settings 411 between a source computer system 405 and a target computer system 450, in accordance with various embodiments. The source computer system 405 may be or may be included in the source computer system 160, the target computer system 450 may be or may be included in one of the target computer systems 110 a-b, and the manager computer system 430 may be or may be included in the manager computer system 150, as illustrated in FIG. 1.
  • According to embodiments, the source computer system 405 may present a static object 415 through an application 410. The presentation of the static object 415 by the application 410 may be associated with a plurality of context settings 411 (collectively, context data or context information). In various embodiments, the source computer system 405 may include a source framework 420. The source framework 420 may be, for example, a platform, application, compiler, library, software tool set, application programming interface, and/or other resource that allows the source computer system 405 to transmit the static object 415 and associated context settings 411 to the target computer system 450.
  • The source framework 420 may allow communication between the application 410 and the source context stub 418. The source context stub 418 may access the application 410 through the source framework 420 to obtain the static object 415 and associated context settings 411. The source context stub 418 may subsequently generate a context package 425 that is to include the static object 415 and associated context settings 411. In various embodiments, the source context stub 418 may include an address for the destination of the context package 425, such as an address of the manager computer system 430 and/or the target computer system 450. In embodiments, the source context stub 418 may transmit the context package 425 to the manager computer system 430 through one or more resources provided by the source framework 420.
  • The manager computer system 430 may subsequently transmit the context package 425 to the target computer system 450. In embodiments, the manager computer system 430 may transmit the context package 425 according to an address associated with the context package 425 and/or in response to a request received from the target computer system 450. The target computer system 450 may include a target framework 460 that may allow communication between the manager computer system 430 and the target context stub 478. The target framework 460 may be, for example, a platform, application, complier, library, software tool set, application programming interface, and/or other resource that allows the target computer system 450 to receive the context package 425 and/or extract the contents therefrom. The target context stub 478 may interface with the manager computer system 430 through the target framework 460 to obtain the context package 425. For example, the target context stub 478 may be adapted to transmit a request for the context package 425 through a function provided by the target framework 460 and/or the target context stub 478 may be adapted to receive the context package 425 through a push service initiated by the manager computer system 430 through the target framework 460.
  • The target context stub 478 may subsequently extract the static object 475 and associated context settings 471 from the context package 425 at the target computer system 450. In various embodiments, the target framework 460 may facilitate communication between the target context stub 478 and the application 470. Accordingly, the target context stub 478 may launch the application 470 at the target computer system 450 via an interface provided by the target framework 460. The target context stub 478 may then cause the application 470 to present the extracted static object 475 with associated context settings 471. The presentation of the static object 475 with associated context settings 471 by the application 470 may be similar to, or may attempt to approximate, the presentation of the static object 415 and associated context settings 411 by the application 410 at the source computer system 405. In various embodiments, the target context stub 478 may add system-dependent context settings and/or may override one or more context settings 471 extracted from the context package 425 (e.g., a resolution setting may be adjusted).
  • In various embodiments, a computer system may function as both a source computer system 405 and a target computer system 450. Thus, the source context stub 418 and the target context stub 478 may be integrated and/or the source framework 420 may be integrated with the target framework 460. Accordingly, the functions of a context stub and/or framework may depend upon whether a computer system is to receive a context package 425 or transmit a context package 425. According to another embodiment, the manager computer system 430 may be omitted or integrated in another computer system so that the transmission of the context package 425 between the source computer system 405 and the target computer system 450 is through a direct transmission (e.g., a peer-to-peer connection).
  • With respect to FIG. 5A, a block diagram illustrates one example of an application 500 that is to present a static object 505 with associated context information 510-520, in accordance with various embodiments. In this exemplary embodiment, the application 500 may be a word processing application. The word processing application 500 may be adapted to present a textual static object 505 having a plurality of characters that may be editable by input to the application 500.
  • The word processing application 500 may include a plurality of context settings 510-520 associated with the presentation of the textual static object 505. For example, the application 500 may include a toolbar configuration context setting 510 that presents one or more tools for the manipulation of the textual static object 505 (e.g., cut, copy, paste, etc.). Additionally, the application 500 may include a clipboard object context setting 515 associated with the presentation of the static object 505. The clipboard object context setting 515 may be, for example, text, an image, or another object that may supplement or otherwise be included in the presentation of the textual static object 505 by the application 500. As illustrated, the application 500 may include a location context setting 520 associated with the presentation of the static object 505. The location context setting 520 may indicate a location (e.g., a page, paragraph, etc.) of the static object 505 that is presented by the application 500.
  • In various embodiments, other context settings may be associated with the presentation of the textual static object 505 by the word processing application 500. For example, a context setting may include a command executed on the textual static object 505 (e.g., a command that may be undone or redone by the application 500), a window setting associated with presentation of the textual static object 505 by the application 500 (e.g., full screen, split screen, minimized), an aspect ratio, or essentially any other context setting associated with the presentation by the application 500.
  • With respect to FIG. 5B, a block diagram illustrates another example of an application 550 that is to present a static object 555 with associated context settings 560-575, in accordance with various embodiments. In this exemplary embodiment, the application 550 may be a web browsing application. The web browsing application 550 may be adapted to present a resource (e.g., a web page) that is referenced by a URI static object 555.
  • The web browsing application 550 may include a plurality of context settings 560-575 associated with the presentation of the resource pointed to by the URI static object 555. For example, the application 550 may include a cookie context setting 560 that includes one or more cookies used to store stateful information associated with the presentation of the resource pointed to by the URI static object 555. Similarly, the application 550 may include a session context setting 565 that includes, for example, a session identification (“ID”) used to associate information with visitors to the resource pointed to by the URI static object 555. Additionally, the application 550 may include an object context setting 570 associated with the presentation of an object included in the resource pointed to by the URI static object 555, such as a status of an embedded video or image. Further, the application 550 may include a location context setting 575 associated with the presentation of the URI static object 555. The location context setting 575 may indicate a location (e.g., a section, tag location, etc.) of the presentation of the resource pointed to by the URI static object 555 by the application 550.
  • In various embodiments, other context settings may be associated with the presentation of the resource pointed to by the URI static object 555 by the web browsing application 550. For example, a context setting may include a toolbar configuration, a window setting associated with presentation of the resource pointed to by the URI static object 555 by the application 550 (e.g., full screen, split screen, minimized), an aspect ratio, or essentially any other context setting associated with the presentation by the application 550.
  • Turning to FIG. 6, a sequence diagram illustrates one example of transfer of a static object and associated context information between separate computer systems through a manager computer system, in accordance with various embodiments. The sequence 600 may be performed by the computer systems illustrated in FIG. 1. Accordingly, the target computer system 620 may be one of the target computer systems 110 a-b, the manager 616 may be the manager computer system 150, and/or the source computer system 605 may be the source computer system 160. While FIG. 6 illustrates a plurality of sequential operations, one of ordinary skill would understand that one or more operations of the sequence 600 may be transposed and/or performed contemporaneously.
  • To begin, a source computer system 605 may connect and/or register with a manager 616 over a network 615 (operation 652). According to embodiments, the source computer system 605 may connect and/or register through a source context stub 608 adapted to facilitate the transfer of a static object and associated context data. In response, the manager 616 may be adapted to return a list of target computer systems that may receive the static object and associated context data (operation 654).
  • A target computer system 620 additionally may connect and/or register with a manager 616 over a network 615 (operation 656). The target computer system 620 may connect and/or register through a target context stub 622 adapted to facilitate the reception of a static object and associated context data. In response, the manager 616 may be adapted to return a list to the target computer system 620 through the target context stub 622 (operation 658). In some embodiments, this list may include a list of source computer systems (e.g., the source computer system 605) available to transmit a static object and associated context data and/or a list of static objects and respective associated context data available to be transmitted. Because source computer systems may be target computer systems as well, this list may identify target computer systems on the network which are both source and target computer systems. Based on the connection and/or registration of the target computer system 620, the manager 616 may transmit an updated list of target computer systems to the source computer system 605 (operation 660).
  • A source application 606 may be adapted to transfer a static object and associated context data to the source context stub 608 (operation 662). In various embodiments, the source context stub 608 may receive the static object and associated context data in response to a request. For example, the source computer system 605 may receive a request to transfer the static object and associated context data from a user, and contemporaneously receive a selection of a target computer system included in a list received from the manager 616. Based on the transfer from the source application 606, the source context stub 608 may be adapted to transfer the static object and associated context data to the manager 616 (operation 664). In various embodiments, the source context stub 608 may include an identification of the target computer system 620 that is to receive the static object and associated context data.
  • Subsequently, the manager 616 may be adapted to transfer the static object and associated context data to the target computer system 620 (operation 668). In various embodiments, the manager 616 may be adapted to make this transfer as part of a push service between the manager 616 and the target computer system 620. This push service may be appropriate where, for example, the target computer system 620 is substantially perpetually connected with and/or available to the manager 616 over the network 615. According to embodiments, the static object and associated context data may be received at the target computer system 620 by a target context stub 622. The target context stub 622 may be adapted to cause a target application 624 to launch (operation 670). In so doing, the target context stub 622 may load the received static object and associated context data in an attempt to approximate the static object and associated context data at the source application 606.
  • In various embodiments, the connection between the source context stub 608 and the target context stub 622 may be direct through a peer-to-peer connection. Therefore, even where the source computer system 605 and/or the target computer system 620 receive lists of computer systems on the network 615 from the manager computer system 616, the actual transfer of a static object and associated context information from the source computer system 605 to the target computer system 620 may be direct.
  • FIG. 7 shows a sequence diagram illustrating another example of transfer of a static object and associated context information between separate computer systems through a manager computer system, in accordance with various embodiments. The sequence 700 may be performed by the computer systems illustrated in FIG. 1. Accordingly, the target computer system 720 may be one of the target computer systems 110 a-b, the manager 716 may be the manager computer system 150, and/or the source computer system 705 may be the source computer system 160. While FIG. 7 illustrates a plurality of sequential operations, one of ordinary skill would understand that one or more operations of the sequence 700 may be transposed and/or performed contemporaneously.
  • To begin, a source computer system 705 may connect and/or register with a manager 716 over a network 715 through functionality provided by a source context stub 708 (operation 752). Based on the connection and/or registration, the manager 716 may be adapted to return a list of target computer systems that may receive a static object and associated context data from the source computer system 705 (operation 754). Similarly, a target computer system 720 may connect and/or register with a manager 716 over the network 715 through functionality provided by a target context stub 722 (operation 756). Based on this connection and/or registration, the manager 716 may be adapted to return a list of source/target computer systems (e.g., a list of computer systems that may participate in the sharing of static object and associated context data) and/or static objects and respective associated context data to the target computer system 720 through the target context stub 722 (operation 758). Thereafter, the manager 716 may refresh the list of target computer systems for the source computer system 705 (operation 760).
  • A source application 706 may be adapted to transfer a static object and associated context data to the source context stub 708 (operation 762). Based on the transfer from the source application 706, the source context stub 708 may be adapted to transfer the static object and associated context data to the manager 716 (operation 764). In various embodiments, the source context stub 708 may include an identification (e.g., a hierarchal address) of the target computer system 720 that is to receive the static object and associated context data. According to embodiments, however, the target computer system 720 may be disconnected from the network 715 and, therefore, unavailable to receive the static object and associated context data (operation 768). Should the manager 716 be unable to transfer the static object and associated context data to the target computer system 720, the manager 716 may cache the transfer request (operation 770). When the target computer system 720 is again able to communicate over the network 715, the target computer system 720 may transmit a request to the manager 716 for the static object and associated context data through a target context stub 722 (operation 772). This pull service may be appropriate where, for example, the target computer system 720 may be intermittently connected with and/or available to the manager 716 over the network 715. Based on the request, the manager 716 may be adapted to transfer the static object and associated context data to the target computer system 720 through the target context stub 722 (operation 774). The target context stub 722 may be adapted to cause a target application 724 to launch with the received static object and associated context data in an attempt to approximate the static object and associated context data at the source application 706 (operation 776).
  • FIG. 8 illustrates a flow diagram of a method 800 for generating a context package to transfer a static object and associated context information, in accordance with various embodiments. The method 800 may be performed by a source computer system, such as the source computer system 160 of FIG. 1. While FIG. 8 illustrates a plurality of sequential operations, one of ordinary skill would understand that one or more operations of the method 800 may be transposed and/or performed contemporaneously.
  • At operation 805, the method 800 may include presenting a static object. The static object may be presented by an application at the source computer system. Operation 810 may include determining context information associated with the static object based on the presentation. The determining based on the presentation may include, for example, receiving input that affects the presentation and/or recording data associated with the static object. Subsequently, operation 815 may include generating a context package that includes the static object and the determined context information.
  • According to an embodiment, the method 800 may proceed to operation 840 for transmitting the context package. In such an embodiment, the context package may be transmitted directly to a target computer system, such as through a peer-to-peer transfer. In an alternative embodiment, some operations 820-835 may optionally occur before operation 840. The method 800 may include operation 820 for registering with a manager computer system that may be adapted to facilitate the transfer of the context package. Based on the registering, operation 825 may include processing a list of target computer systems that are adapted to receive the context package through the manager computer system. This list may be received from a manager computer system. The method 800 may then include operation 830 for selecting a target computer system based on the list of target computer systems. Correspondingly, operation 835 may include addressing the context package to the selected target computer system. Operation 835 may include associating a hierarchical address (e.g., an IP address) with the context package. The method 800 may proceed to operation 840 for transmitting the context package to the selected target computer system.
  • With respect to FIG. 9, a flow diagram illustrates a method 900 for facilitating transfer of a context package between separate computer systems, in accordance with various embodiments. The method 900 may be performed by a manager computer system, such as the manager computer system 150 of FIG. 1. While FIG. 9 illustrates a plurality of sequential operations, one of ordinary skill would understand that one or more operations of the method 900 may be transposed and/or performed contemporaneously.
  • According to an embodiment, the method 900 may include operation 930 for processing a context package from a source computer system. According to embodiments, this context package may be received from the source computer system. Although not necessary, the context package may identify a target computer system that is to receive the context package. The method 900 may then reach operation 940 for processing a request to transmit the context package to the target computer system. In one embodiment, this request may be received from the source computer system in association with the context package. In another embodiment, this request may be received from the target computer system as part of a pull service between the manager computer system and the target computer system. Based on the request, operation 945 may include transmitting the context package to the target computer system.
  • In various embodiments, the method 900 may include one or more optional operations 905-925. At operation 905, the method 900 may include processing a registration request received from a source computer system. This registration request may allow the manager computer system to register the source computer system, which may allow the manager computer system to identify the source computer system as a source of one or more context packages. Subsequently, operation 910 may include adding the source computer system to a list of source computer systems. Operation 915 may include processing a registration request received from a target computer system. This registration request may allow the manager computer system to register and/or identify the target computer system as adapted to receive one or more context packages. Operation 920 may include adding the target computer system to a list of target computer systems. So that the source computer system may identify a destination for the context package, operation 925 may include transmitting the list of target computer systems to the source computer system. The method 900 may reach operation 930, as described herein.
  • According to one embodiment, operation 945 for transmitting the context package to the target computer system may be delayed, such as where the target computer system is unavailable to the manager computer system (e.g., disconnected from a network). Therefore, the method 900 may include operation 935 for caching the context package. When the target computer system becomes available, the method 900 may reach operation 940, which may include processing the pull request received from the target computer system.
  • Turning to FIG. 10, a flow diagram illustrates a method 1000 for presenting a static object with associated context information based on a received context package, in accordance with various embodiments. The method 1000 may be performed by a target computer system, such as the target computer systems 110 a-b of FIG. 1. While FIG. 10 illustrates a plurality of sequential operations, one of ordinary skill would understand that one or more operations of the method 1000 may be transposed and/or performed contemporaneously.
  • In various embodiments, the method 1000 may include operation 1010 for processing a context package that includes a static object and associated context information. This context package may be received from, for example, a source computer system or a manager computer system. Based on the context package, an operation 1015 may include loading the context information included in the context package. Embodiments of operation 1015 may comprise launching an application adapted to present the static object, loading the context information into the application, and loading the static object. Operation 1025 may include presenting the static object based on the loaded context information. Accordingly, the static object may be presented by the target computer system such that the presentation approximates a remote presentation at a computer system that is the source of the context package. The context information may include a plurality of context settings, and not all of these context settings may be suitable for presentation at the target computer system. Therefore, various embodiments may include an optional operation 1020 for overriding a context setting included in the context information.
  • According to some embodiments, the context package may be transmitted in response to a request. Therefore, an optional operation 1005 may precede operation 1010. Operation 1005 may include transmitting a pull request for the context package. In one embodiment, this pull request may be transmitted to a manager computer system adapted to cache the context package in anticipation of the pull request. In another embodiment, this pull request may be transmitted to a computer system that is the source of the context package, such as where the target computer system is directly connected to the source computer system.
  • With reference to FIG. 11, a flow diagram shows a method 1100 for collecting and transferring context data associated with a static object based on user interaction, in accordance with various embodiments. The method 1100 may be performed by a source computer system, such as the source computer system 160 of FIG. 1. While FIG. 11 illustrates a plurality of sequential operations, one of ordinary skill would understand that one or more operations of the method 1100 may be transposed and/or performed contemporaneously.
  • The method 1100 may begin with operation 1105 for receiving user interaction associated with a static object. In embodiments, this user interaction may be received through an application adapted to present the static object to the user. This user interaction may include essentially any input received at the application during or contemporaneous with the presentation of the static object by the application. Based on the user interaction, operation 1110 may include collecting context data associated with the static object. The context data may include one or more context settings that are associated with or based on the received user interaction, either directly or indirectly—e.g., a direct user interaction may cause an object to be placed on a clipboard, whereas an indirect user interaction may cause a cookie to be stored.
  • The method 1100 may include operation 1120 for receiving a selection of a target computer system. In one embodiment, the source computer system may be adapted to communicate with one or more target computer systems, such as through a manager computer system. Therefore, the method 1100 may include an optional operation 1115 for receiving a list of target computer systems that each are adapted to present the static object. In such an embodiment, the operation 1120 for receiving the selection of the target computer system may be based on the received list of target computer systems. Subsequently, operation 1125 may include transferring the static object and the collected context data to the selected target computer system. According to the embodiment, this transfer may be direct (e.g., through a peer-to-peer communication) or may be indirect (e.g., through a manager computer system).
  • In various embodiments, example 1 may include a computer system for transferring context data associated with an electronic document, the system comprising: at least one processor; and at least one memory having processor-executable instructions that, in response to execution by the at least one processor, cause the computer system to: present a static object; determine context information associated with the static object based on the presentation of the static object; generate a context package that is to include the static object and the associated context information; and transmit the generated context package to an external computer system over a network for external presentation of the static object with the associated context information. Example 2 may include the computer system of example 1, wherein the static object is a text document and the context information includes a command executed on the text document that can be undone by an application adapted to present the text document, a clipboard object, a location within the text document, a toolbar configuration, or a window setting associated with presentation of the text document. Example 3 may include the computer system of example 1, wherein the static object is a uniform resource identifier (“URI”) and the context information includes a location within a page of the URI, a status of an embedded object in the page, a cookie associated with the page, session information associated with the page, and a toolbar configuration. Example 4 may include the computer system of any of examples 1-3, wherein the determination of the context information and the generation of the context package are made using a framework adapted for transmission of context packages. Example 5 may include the computer system of any of examples 1-3, wherein the external computer system to which the generated context package is to be transmitted is a target computer system adapted to present the static object with the associated context information and the transmission is to be a peer-to-peer connection. Example 6 may include the computer system of any of examples 1-3, wherein the external computer system to which the generated context package is to be transmitted is a manager computer system adapted to transmit the context package to a target computer system. Example 7 may include the computer system of example 6, wherein the instructions, in response to execution by the at least one processor, cause the computer system to:
  • process a list of target computer systems adapted to receive the context package, the list to be received from a manager computer system; select a target computer system based on the list of target computer systems; and hierarchically address the context package to the selected target computer system, so that the transmission includes a hierarchal address. Example 8 may include the computer system of example 6, wherein the instructions, in response to execution by the at least one processor, cause the computer system to: transmit a registration request to the manager computer system.
  • In various embodiments, 9 may be a computer system for migrating context information associated with an electronic document between separate computer systems, the system comprising: at least one processor; and at least one memory having processor-executable instructions that, in response to execution by the at least one processor, cause the computer system to: process a source context package, received from a source computer system, that is to include a static object and context information associated with the static object; process a target request to transmit the source context package to a target computer system; and transmit, based on the request, the source context package to the target computer system to support presentation of the static object with the associated context information. Example 10 may include the computer system of example 9, wherein the instructions, in response to execution by the at least one processor, further cause the computer system to: transmit, to the source computer system, a list of target computer systems adapted to receive context packages, including the target computer system. Example 11 may include the computer system of example 10, wherein the instructions, in response to execution by the at least one processor, further cause the computer system to: process a registration request from the target computer system; and add the target computer system to the list of target computer systems based on the received registration request. Example 12 may include the computer system of any of example 9-11, wherein the instructions, in response to execution by the at least one processor, cause the computer system to: transmit, to the target computer system, a list of source computer systems adapted to generate context packages for presentation of static objects, including the source computer system. Example 13 may include the computer system of example 12, wherein the instructions, in response to execution by the at least one processor, further cause the computer system to: process a registration request from the source computer system; and add the source computer system to the list of source computer systems based on the received registration request. Example 14 may include the computer system of any of example 9-11, wherein the target request is received from the target computer system, and further wherein the instructions, in response to execution by the at least one processor, cause the computer system to: cache the source context package received from the source computer system. Example 15 may include the computer system of any of example 9-11, wherein the target request is received from the source computer system and includes a hierarchical address associated with the target computer system.
  • In various embodiments, example 16 may be computer system for re-creating an electronic document with associated context data from a separate computer system, the system comprising: at least one processor; and at least one memory having processor-executable instructions that, in response to execution by the at least one processor, cause the computer system to: process a context package, received from an external computer system over a network, that is to include a static object and context information associated with the static object; load the context information from the context package; and present the static object based on the loaded context information. Example 17 may include the computer system of example 16, wherein the static object is a text document and the context information includes a command executed on the text document that can be undone by an application adapted to present the text document, a clipboard object, a location within the text document, a toolbar configuration, or a window setting associated with presentation of the text document. Example 18 may include the computer system of example 16, wherein the static object is a uniform resource identifier (“URI”) and the context information includes a location within a page of the URI, a status of an embedded object in the page, a cookie associated with the page, session information associated with the page, and a toolbar configuration. Example 19 may include the computer system of example 16, wherein the instructions, in response to execution by the at least one processor, cause the computer system to: override a context setting included in the context information. Example 20 may include the computer system of example 16, wherein the external computer system from which the generated context package is to be received is a source computer system adapted to present the static object with the associated context information, and further wherein the reception over the network is to be a peer-to-peer connection. Example 21 may include the computer system of any of examples 16-20, wherein the external computer system to from which the generated context package is to be received is a manager computer system adapted to receive the context package from a source computer system. Example 22 may include the computer system of any of examples 16-20, wherein the instructions, in response to execution by the at least one processor, cause the computer system to: transmit, to a manager computer system, a pull request to receive the context package from the manager computer system.
  • In various embodiments, example 23 may be a method to be performed by a computer system for transferring context data associated with a static object, the method comprising: receiving user interaction associated with the static object; collecting the context data associated with the static object based on the receiving of the user interaction; receiving a selection of a target computer system adapted to present the static object; and transferring the static object and the collected context data to the selected target computer system. Example 24 may include the method of example 23, wherein the transferring the static object and the collected context data to the selected target computer system comprises: sending the static object and the collected context data to a manager computer system adapted to send the static object and the collected context data to the target computer system. Example 25 may include the method of any of examples 23-24, wherein selection is based on a list of target computer systems, and the method further comprising: receiving the list of target computer systems.
  • In various embodiments, example 26 may be one or more non-transitory computer system-readable media comprising computer system-executable instructions, wherein the instructions, in response to execution by a computer system, cause the computer system to: present a static object; determine context information associated with the static object based on the presentation of the static object; generate a context package that is to include the static object and the associated context information; and transmit the generated context package to an external computer system over a network for external presentation of the static object with the associated context information. Example 27 may include the one or more non-transitory computer system-readable media of example 26, wherein the static object is a text document and the context information includes a command executed on the text document that can be undone by an application adapted to present the text document, a clipboard object, a location within the text document, a toolbar configuration, or a window setting associated with presentation of the text document. Example 28 may include the one or more non-transitory computer system-readable media of example 26, wherein the static object is a uniform resource identifier (“URI”) and the context information includes a location within a page of the URI, a status of an embedded object in the page, a cookie associated with the page, session information associated with the page, and a toolbar configuration. Example 29 may include the one or more non-transitory computer system-readable media of any of examples 26-28, wherein the determination of the context information and the generation of the context package are made using a framework adapted for transmission of context packages. Example 30 may include the one or more non-transitory computer system-readable media of any of examples 26-28, wherein the external computer system to which the generated context package is to be transmitted is a target computer system adapted to present the static object with the associated context information and the transmission is to be a peer-to-peer connection.
  • In various embodiments, example 31 may be a method to be performed by a computer system for migrating context information associated with an electronic document, the method comprising: receiving, from a source computer system, a source context package that is to include a static object and context information associated with the static object; receiving a target request to transmit the source context package to a target computer system; and transmitting, based on the target request, the source context package to the target computer system to support presentation of the static object with the associated context information. Example 32 may include the method of example 31, further comprising: transmitting, to the source computer system, a list of target computer systems adapted to receive context packages, including the target computer system. Example 33 may include the method of example 32, further comprising: receiving a registration request from the target computer system; and adding the target computer system to the list of target computer systems based on the received registration request. Example 34 may include the method of any of examples 31-33, further comprising: transmitting, to the target computer system, a list of source computer systems adapted to generate context packages for presentation of static objects, including the source computer system. Example 35 may include the method of example 34, further comprising: receiving a registration request from the source computer system; and adding the source computer system to the list of source computer systems based on the received registration request. Example 36 may include the method of any of examples 31-33, wherein the target request is received from the target computer system, and the method further comprising: caching the context package received from the source computer system.
  • In various embodiments, example 37 may be one or more non-transitory computer system-readable media comprising computer system-executable instructions, wherein the instructions, in response to execution by a computer system, cause the computer system to: process a context package, received from an external computer system over a network, that is to include a static object and context information associated with the static object; load the context information from the context package; and present the static object based on the loaded context information. Example 38 may include the one or more non-transitory computer system-readable media of example 37, wherein the instructions, in response to execution by the computer system, cause the computer system to: override a context setting included in the context information. Example 39 may include the one or more non-transitory computer system-readable media of any of examples 37-38, wherein the external computer system from which the generated context package is to be received is a source computer system adapted to present the static object with the associated context information or a manager computer system adapted to receive the context package from a source computer system. Example 40 may include the one or more non-transitory computer system-readable media of any of examples 37-38, wherein the instructions, in response to execution by the computer system, cause the computer system to: transmit, to a manager computer system, a pull request to receive the context package from the manager computer system.
  • Some portions of the preceding detailed description have been presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. These algorithmic descriptions and representations are the ways used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm is here, and generally, conceived to be a self-consistent sequence of operations leading to a desired result. The operations are those requiring physical manipulations of physical quantities.
  • It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the above discussion, it is appreciated that throughout the description, discussions utilizing terms such as those set forth in the claims below refer to the action and processes of a computer system, or similar electronic computing device, that manipulates and transforms data represented as physical (electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage, transmission, or display devices.
  • Embodiments of the invention also relate to an apparatus for performing the operations herein. Such a computer program is stored in a non-transitory computer-readable medium. A machine-readable medium includes any mechanism for storing information in a form readable by a machine (e.g., a computer). For example, a machine-readable (e.g., computer-readable) medium includes a machine- (e.g., a computer-) readable storage medium (e.g., read only memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical storage media, flash memory devices).
  • The processes or methods depicted in the preceding figures can be performed by processing logic that comprises hardware (e.g., circuitry, dedicated logic, etc.), software (e.g., embodied on a non-transitory computer-readable medium), or a combination of both. Although the processes or methods are described above in terms of some sequential operations, it should be appreciated that some of the operations described can be performed in a different order. Moreover, some operations can be performed in parallel rather than sequentially.
  • Embodiments of the present invention are not described with reference to any particular programming language. It will be appreciated that a variety of programming languages can be used to implement the teachings of embodiments of the invention as described herein.
  • In the foregoing Specification, embodiments of the invention have been described with reference to specific exemplary embodiments thereof. It will be evident that various modifications can be made thereto without departing from the broader spirit and scope of the invention as set forth in the following claims. The Specification and drawings are, accordingly, to be regarded in an illustrative sense rather than a restrictive sense.

Claims (25)

What is claimed is:
1. A computer system for transferring context data associated with an electronic document, the system comprising:
at least one processor; and
at least one memory having processor-executable instructions that, in response to execution by the at least one processor, cause the computer system to:
present a static object;
determine context information associated with the static object based on the presentation of the static object;
generate a context package that is to include the static object and the associated context information; and
transmit the generated context package to an external computer system over a network for external presentation of the static object with the associated context information.
2. The computer system of claim 1, wherein the static object is a text document and the context information includes a command executed on the text document that can be undone by an application adapted to present the text document, a clipboard object, a location within the text document, a toolbar configuration, or a window setting associated with presentation of the text document.
3. The computer system of claim 1, wherein the static object is a uniform resource identifier (“URI”) and the context information includes a location within a page of the URI, a context of an embedded object in the page, a cookie associated with the page, session information associated with the page, and a toolbar configuration.
4. The computer system of claim 1, wherein the determination of the context information and the generation of the context package are made using a framework adapted for transmission of context packages.
5. The computer system of claim 1, wherein the external computer system to which the generated context package is to be transmitted is a target computer system adapted to present the static object with the associated context information and the transmission is to be a peer-to-peer connection.
6. The computer system of claim 1, wherein the external computer system to which the generated context package is to be transmitted is a manager computer system adapted to transmit the context package to a target computer system.
7. The computer system of claim 6, wherein the instructions, in response to execution by the at least one processor, cause the computer system to:
process a list of target computer systems adapted to receive the context package, the list to be received from the manager computer system;
select the target computer system based on the list of target computer systems; and
hierarchically address the context package to the selected target computer system, so that the transmission includes a hierarchal address.
8. The computer system of claim 6, wherein the instructions, in response to execution by the at least one processor, cause the computer system to:
transmit a registration request to the manager computer system.
9. A computer system for migrating context information associated with an electronic document between separate computer systems, the system comprising:
at least one processor; and
at least one memory having processor-executable instructions that, in response to execution by the at least one processor, cause the computer system to:
process a source context package, received from a source computer system, that is to include a static object and context information associated with the static object;
process a target request to transmit the source context package to a target computer system; and
transmit, based on the request, the source context package to the target computer system to support presentation of the static object with the associated context information.
10. The computer system of claim 9, wherein the instructions, in response to execution by the at least one processor, further cause the computer system to:
transmit, to the source computer system, a list of target computer systems adapted to receive context packages, including the target computer system.
11. The computer system of claim 10, wherein the instructions, in response to execution by the at least one processor, further cause the computer system to:
process a registration request from the target computer system; and
add the target computer system to the list of target computer systems based on the received registration request.
12. The computer system of claim 9, wherein the instructions, in response to execution by the at least one processor, cause the computer system to:
transmit, to the target computer system, a list of computer systems associated with the re-creation of static objects with associated context information, including the source computer system.
13. The computer system of claim 12, wherein the instructions, in response to execution by the at least one processor, further cause the computer system to:
process a registration request from the source computer system; and
add the source computer system to the list of source computer systems based on the received registration request.
14. The computer system of claim 9, wherein the target request is received from the target computer system, and further wherein the instructions, in response to execution by the at least one processor, cause the computer system to:
cache the source context package received from the source computer system.
15. The computer system of claim 9, wherein the target request is received from the source computer system and includes a hierarchical address associated with the target computer system.
16. A computer system for re-creating an electronic document with associated context data from a separate computer system, the system comprising:
at least one processor; and
at least one memory having processor-executable instructions that, in response to execution by the at least one processor, cause the computer system to:
process a context package, received from an external computer system over a network, that is to include a static object and context information associated with the static object;
load the context information from the context package; and
present the static object based on the loaded context information.
17. The computer system of claim 16, wherein the static object is a text document and the context information includes a command executed on the text document that can be undone by an application adapted to present the text document, a clipboard object, a location within the text document, a toolbar configuration, or a window setting associated with presentation of the text document.
18. The computer system of claim 16, wherein the static object is a uniform resource identifier (“URI”) and the context information includes a location within a page of the URI, a context of an embedded object in the page, a cookie associated with the page, session information associated with the page, and a toolbar configuration.
19. The computer system of claim 16, wherein the instructions, in response to execution by the at least one processor, cause the computer system to:
override a context setting included in the context information.
20. The computer system of claim 16, wherein the external computer system from which the generated context package is to be received is a source computer system adapted to present the static object with the associated context information, and further wherein the reception over the network is to be a peer-to-peer connection.
21. The computer system of claim 16, wherein the external computer system from which the generated context package is to be received is a manager computer system adapted to receive the context package from a source computer system.
22. The computer system of claim 21, wherein the instructions, in response to execution by the at least one processor, cause the computer system to:
transmit, to the manager computer system, a pull request to receive the context package from the manager computer system.
23. A method to be performed by a computer system for transferring context data associated with a static object, the method comprising:
receiving user interaction associated with the static object;
collecting the context data associated with the static object based on the receiving of the user interaction;
receiving a selection of a target computer system adapted to present the static object; and
transferring the static object and the collected context data to the selected target computer system.
24. The method of claim 23, wherein the transferring the static object and the collected context data to the selected target computer system comprises:
sending the static object and the collected context data to a manager computer system adapted to send the static object and the collected context data to the target computer system.
25. The method of claim 23, wherein selection is based on a list of target computer systems, and the method further comprising:
receiving the list of target computer systems.
US14/226,684 2013-09-26 2014-03-26 Application context migration framework and protocol Abandoned US20150089382A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US201361883127P true 2013-09-26 2013-09-26
US14/226,684 US20150089382A1 (en) 2013-09-26 2014-03-26 Application context migration framework and protocol

Applications Claiming Priority (5)

Application Number Priority Date Filing Date Title
US14/226,684 US20150089382A1 (en) 2013-09-26 2014-03-26 Application context migration framework and protocol
EP14849895.9A EP3049955A4 (en) 2013-09-26 2014-08-29 Application context migration framework and protocol
CN201480047677.9A CN105493067A (en) 2013-09-26 2014-08-29 Application context migration framework and protocol
PCT/US2014/053433 WO2015047659A1 (en) 2013-09-26 2014-08-29 Application context migration framework and protocol
HK16111028.5A HK1222927A1 (en) 2013-09-26 2016-09-20 Application context migration framework and protocol

Publications (1)

Publication Number Publication Date
US20150089382A1 true US20150089382A1 (en) 2015-03-26

Family

ID=52690831

Family Applications (12)

Application Number Title Priority Date Filing Date
US14/226,684 Abandoned US20150089382A1 (en) 2013-09-26 2014-03-26 Application context migration framework and protocol
US14/316,156 Active 2034-11-06 US9504088B2 (en) 2013-09-26 2014-06-26 Systems, methods, and devices for device-to-device discovery
US14/317,900 Active 2035-04-12 US9560684B2 (en) 2013-09-26 2014-06-27 Mitigation of traffic congestion in dual connectivity systems
US14/318,143 Active 2034-11-21 US9538565B2 (en) 2013-09-26 2014-06-27 HARQ timelines for TDD-FDD carrier aggregation
US14/317,184 Active 2034-07-15 US9258723B2 (en) 2013-09-26 2014-06-27 Systems, methods, and devices with different radio link failure timers based on user equipment speed
US14/317,837 Active 2034-10-04 US9462629B2 (en) 2013-09-26 2014-06-27 Reduction of packet retransmissions in dual connectivity systems
US14/914,331 Active 2035-02-03 US9986447B2 (en) 2013-09-26 2014-09-18 User equipment and protocol and methods for device-to-device communication
US14/583,595 Active US10200890B2 (en) 2013-09-26 2014-09-25 Methods for aperiodic CSI report triggering for flexible subframes in LTE TDD eIMTA systems with dynamic UL-DL reconfiguration
US14/496,152 Active 2035-01-29 US9572185B2 (en) 2013-09-26 2014-09-25 Bearer split ratios for dual connectivity systems
US14/915,849 Abandoned US20160205716A1 (en) 2013-09-26 2014-09-26 Systems, methods, and devices for cellular network-assisted low cost opportunistic social networking
US14/986,245 Active US9420627B2 (en) 2013-09-26 2015-12-31 Systems, methods, and devices with different radio link failure timers based on user equipment speed
US15/858,429 Active US10327163B2 (en) 2013-09-26 2017-12-29 User equipment and protocol and methods for device-to-device communication

Family Applications After (11)

Application Number Title Priority Date Filing Date
US14/316,156 Active 2034-11-06 US9504088B2 (en) 2013-09-26 2014-06-26 Systems, methods, and devices for device-to-device discovery
US14/317,900 Active 2035-04-12 US9560684B2 (en) 2013-09-26 2014-06-27 Mitigation of traffic congestion in dual connectivity systems
US14/318,143 Active 2034-11-21 US9538565B2 (en) 2013-09-26 2014-06-27 HARQ timelines for TDD-FDD carrier aggregation
US14/317,184 Active 2034-07-15 US9258723B2 (en) 2013-09-26 2014-06-27 Systems, methods, and devices with different radio link failure timers based on user equipment speed
US14/317,837 Active 2034-10-04 US9462629B2 (en) 2013-09-26 2014-06-27 Reduction of packet retransmissions in dual connectivity systems
US14/914,331 Active 2035-02-03 US9986447B2 (en) 2013-09-26 2014-09-18 User equipment and protocol and methods for device-to-device communication
US14/583,595 Active US10200890B2 (en) 2013-09-26 2014-09-25 Methods for aperiodic CSI report triggering for flexible subframes in LTE TDD eIMTA systems with dynamic UL-DL reconfiguration
US14/496,152 Active 2035-01-29 US9572185B2 (en) 2013-09-26 2014-09-25 Bearer split ratios for dual connectivity systems
US14/915,849 Abandoned US20160205716A1 (en) 2013-09-26 2014-09-26 Systems, methods, and devices for cellular network-assisted low cost opportunistic social networking
US14/986,245 Active US9420627B2 (en) 2013-09-26 2015-12-31 Systems, methods, and devices with different radio link failure timers based on user equipment speed
US15/858,429 Active US10327163B2 (en) 2013-09-26 2017-12-29 User equipment and protocol and methods for device-to-device communication

Country Status (10)

Country Link
US (12) US20150089382A1 (en)
EP (9) EP3050268A4 (en)
JP (3) JP6151445B2 (en)
KR (3) KR101775295B1 (en)
CN (9) CN105474595A (en)
ES (2) ES2682593T3 (en)
HK (8) HK1222486A1 (en)
HU (2) HUE039898T2 (en)
RU (1) RU2631671C2 (en)
WO (10) WO2015047556A1 (en)

Families Citing this family (65)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102833802B (en) * 2012-08-15 2015-09-23 电信科学技术研究院 A data forwarding method and apparatus
CN109194457A (en) * 2013-01-18 2019-01-11 华为技术有限公司 It was found that the transmission and detection method and device of reference signal
US9326122B2 (en) 2013-08-08 2016-04-26 Intel IP Corporation User equipment and method for packet based device-to-device (D2D) discovery in an LTE network
WO2015020736A1 (en) * 2013-08-08 2015-02-12 Intel IP Corporation Method, apparatus and system for electrical downtilt adjustment in a multiple input multiple output system
US20150089382A1 (en) 2013-09-26 2015-03-26 Wu-chi Feng Application context migration framework and protocol
KR20150035291A (en) * 2013-09-27 2015-04-06 주식회사 아이티엘 Method and apparatus of uplink scheduling and harq timing
KR20150035673A (en) * 2013-09-27 2015-04-07 주식회사 케이티 Methods for setting control channel timing with TDD-FDD joint operation and Apparatuses thereof
EP2854444A1 (en) 2013-09-27 2015-04-01 Panasonic Intellectual Property Corporation of America Efficient uplink scheduling mechanism for dual connectivity
US9924405B2 (en) * 2013-10-04 2018-03-20 Industrial Technology Research Institute Method for buffer status report in dual connectivity
KR20150040149A (en) 2013-10-04 2015-04-14 주식회사 아이티엘 Method and apparatus of controlling uplink scheduling and harq timing
JP5864034B2 (en) * 2013-10-11 2016-02-17 京セラ株式会社 Communication control method, user terminal, and communication device
CN104581824A (en) * 2013-10-17 2015-04-29 中兴通讯股份有限公司 Method and system for data packet shunting transmission
WO2015063963A1 (en) * 2013-10-31 2015-05-07 日本電気株式会社 Wireless communication system, base station device, and wireless terminal
WO2015064738A1 (en) * 2013-11-01 2015-05-07 シャープ株式会社 Terminal device, base station device, and method
WO2015088276A1 (en) * 2013-12-12 2015-06-18 엘지전자 주식회사 Method and device for performing measurement in wireless communication system
CN104812075A (en) * 2014-01-27 2015-07-29 中兴通讯股份有限公司 Device discovery signal transmitting method, device and system
US10075381B2 (en) * 2014-01-28 2018-09-11 Mediatek Inc. Buffer status report and logical channel prioritization for dual connectivity
US9560574B2 (en) * 2014-01-31 2017-01-31 Intel IP Corporation User equipment and method for transmit power control for D2D tranmissions
US20160352643A1 (en) * 2014-02-08 2016-12-01 Sharp Kabushiki Kaisha Methods for discarding radio link control (rlc) service data unit (sdu) and base station
US9491672B2 (en) * 2014-03-05 2016-11-08 Qualcomm Incorporated Timer adaptation based on change of handover parameter
WO2015141478A1 (en) * 2014-03-19 2015-09-24 株式会社Nttドコモ User device and uplink data transmission method
CN108306708A (en) * 2014-03-21 2018-07-20 电信科学技术研究院 A kind of data package processing method and device
US20150271836A1 (en) * 2014-03-21 2015-09-24 Qualcomm Incorporated Techniques for bearer prioritization and data mapping in multiple connectivity wireless communications
WO2015147523A1 (en) * 2014-03-24 2015-10-01 Samsung Electronics Co., Ltd. Apparatus and method for monitoring d2d transmission in connected state
US9930643B2 (en) * 2014-05-02 2018-03-27 Qualcomm Incorporated Resource allocation control for long term evolution device-to-device discovery
WO2015169405A1 (en) * 2014-05-08 2015-11-12 Telefonaktiebolaget L M Ericsson (Publ) Method and apparatus for indicating and adapting the activity state of a wireless device having device-to-device communication capabilities
US20150334686A1 (en) * 2014-05-19 2015-11-19 Qualcomm Incorporated Apparatus and method for inter-band pairing of carriers for time division duplex transmit- and receive-switching and its application to multiplexing of different transmission time intervals
EP3155748A1 (en) * 2014-06-13 2017-04-19 Nokia Solutions and Networks Oy Hybrid automatic repeat request for enhanced interference management and traffic adaptation
CN105338572A (en) * 2014-06-23 2016-02-17 北京三星通信技术研究有限公司 Data distribution method and device for segmented bearing in double-connection
US9825828B2 (en) * 2014-08-26 2017-11-21 T-Mobile Usa, Inc. Cross-layer link failure alerts
US9497299B2 (en) * 2014-09-18 2016-11-15 Blackberry Limited Configuring a discard timer
US9894558B2 (en) * 2014-09-26 2018-02-13 Nokia Solutions And Networks Oy Lower and upper bounds for flow-control data requests between network nodes
US9699800B2 (en) * 2014-10-23 2017-07-04 Intel IP Corporation Systems, methods, and appartatuses for bearer splitting in multi-radio HetNet
US9832808B2 (en) * 2014-12-02 2017-11-28 Cisco Technology, Inc. Method to provide dual connectivity using LTE master eNodeB and Wi-Fi based secondary eNodeB
EP3235220A4 (en) * 2014-12-18 2018-08-22 LG Electronics Inc. Method for reconfiguring a pdcp reordering timer in a wireless communication system and device therefor
WO2016152140A1 (en) * 2015-03-25 2016-09-29 日本電気株式会社 Communication device, communication system, and control method
US10455481B2 (en) * 2015-05-08 2019-10-22 Lg Electronics Inc. Method and device for transmitting and receiving discovery signal of device-to-device communication terminal in wireless communication system
US9894702B2 (en) * 2015-05-14 2018-02-13 Intel IP Corporation Performing primary cell functions in a secondary cell
WO2017012091A1 (en) * 2015-07-22 2017-01-26 Telefonaktiebolaget Lm Ericsson (Publ) Method and communication node of scheduling radio resources
KR20170019982A (en) 2015-08-13 2017-02-22 삼성전자주식회사 Scheme for communication using beamformed csi-rs in mobile communication system
WO2017026863A1 (en) * 2015-08-13 2017-02-16 삼성전자 주식회사 Method and apparatus for transmitting and receiving reference signal in communication system
US10439698B2 (en) 2015-08-21 2019-10-08 Lg Electronics Inc. Channel state reporting method in wireless communication system and device for same
US9801234B2 (en) * 2015-08-25 2017-10-24 Logitech Europe S.A. Power efficient mesh network
US20180241687A1 (en) * 2015-09-11 2018-08-23 Telefonaktiebolaget Lm Ericsson (Publ) Technique For Multi-Connectivity
WO2017053957A1 (en) 2015-09-25 2017-03-30 Fsa Technologies, Inc. High-speed communications platform
CN106658719A (en) * 2015-10-30 2017-05-10 中国电信股份有限公司 Data distribution method and device
WO2017091218A1 (en) * 2015-11-25 2017-06-01 Nokia Solutions And Networks Oy Event-triggered measurement reporting in 5g mmwave communication system
CN106937396A (en) * 2015-12-31 2017-07-07 上海无线通信研究中心 Uplink resource scheduling method, terminal and base station thereof
US10404332B2 (en) * 2016-01-28 2019-09-03 Qualcomm Incorporated Downlink common burst channelization
EP3200550A1 (en) * 2016-01-29 2017-08-02 Alcatel Lucent Method for sharing resources between mobile devices thanks to a location tracking server
WO2017138978A1 (en) * 2016-02-12 2017-08-17 Intel IP Corporation Systems and methods for reducing interruptions in data transmissions due to handover operations
CN108702714A (en) * 2016-02-17 2018-10-23 瑞典爱立信有限公司 The system and method for providing protection interval for the transmission in communication system
CN108141427A (en) * 2016-03-10 2018-06-08 华为技术有限公司 A kind of reference signal production method and device
US20190021026A1 (en) * 2016-03-23 2019-01-17 Intel IP Corporation Systems, methods and devices for uplink bearer split using wireless local area network aggregation
US10021597B2 (en) 2016-04-04 2018-07-10 At&T Intellectual Property I, L.P. Flow control in multi-RAT 5G wireless networks
US20190098640A1 (en) * 2016-04-19 2019-03-28 Nokia Technologies Oy Split Bearer Dual/Multiple Connectivity Retransmission Diversity
WO2017220855A1 (en) * 2016-06-22 2017-12-28 Nokia Technologies Oy Method and apparatus for performing packet duplication in a multi-connectivity scenario
US20180054282A1 (en) * 2016-08-22 2018-02-22 Qualcomm Incorporated Uplink common burst symbol configuration
CN106455125A (en) * 2016-10-25 2017-02-22 深圳市万普拉斯科技有限公司 Communication control method and related device
CN106713648B (en) * 2016-12-30 2019-07-26 Oppo广东移动通信有限公司 A kind of communication means and mobile terminal
KR20180090148A (en) * 2017-02-02 2018-08-10 삼성전자주식회사 Method of data processing in communications systems
US10237784B2 (en) * 2017-03-24 2019-03-19 Motorola Mobility Llc Split bearer packet data converge protocol protocol data unit routing
CN107018106A (en) * 2017-05-18 2017-08-04 江阴市创新气门嘴有限公司 Code element waveform frequency deviation compensation method for Bluetooth receiver
WO2019056298A1 (en) * 2017-09-22 2019-03-28 Qualcomm Incorporated Mechanisms for resource allocation of csi feedback
CN109729551A (en) * 2017-10-30 2019-05-07 惠州Tcl移动通信有限公司 Communication means, base station and the device with storage function

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020198941A1 (en) * 2001-04-16 2002-12-26 Alexandru Gavrilescu Web site cobrowsing
US6625622B1 (en) * 1999-05-14 2003-09-23 Eisenworld, Inc. Apparatus and method for transfering information between platforms
US8504654B1 (en) * 2010-12-10 2013-08-06 Wyse Technology Inc. Methods and systems for facilitating a remote desktop session utilizing long polling
USRE45729E1 (en) * 2005-12-12 2015-10-06 Electronics And Telecommunications Research Institute Apparatus and method for managing application context

Family Cites Families (197)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6335933B1 (en) * 1999-05-21 2002-01-01 Broadcom Homenetworking, Inc. Limited automatic repeat request protocol for frame-based communication channels
JP4231593B2 (en) * 1999-07-21 2009-03-04 株式会社日立コミュニケーションテクノロジー Communication system and communication method thereof
US8386920B2 (en) * 2000-04-27 2013-02-26 Alcatel Lucent Method and apparatus for data visualization
DE10039193A1 (en) * 2000-08-10 2002-02-21 Siemens Ag Method and arrangement for carrying out a handover in mobile communication systems with data duplication
GB2372172B (en) 2001-05-31 2002-12-24 Ericsson Telefon Ab L M Congestion handling in a packet data network
US7251246B2 (en) * 2001-09-14 2007-07-31 Snowshore Networks, Inc. Selective packet processing in a packet based media processor for latency reduction
AT460801T (en) * 2002-01-03 2010-03-15 Innovative Sonic Ltd Mechanism for avoiding a data flow in wireless high-speed communication systems by means of a time switch
US7403996B2 (en) * 2002-02-21 2008-07-22 Bea Systems, Inc. Systems and methods for migratable services
US20030206532A1 (en) * 2002-05-06 2003-11-06 Extricom Ltd. Collaboration between wireless lan access points
US6885638B2 (en) 2002-06-13 2005-04-26 Motorola, Inc. Method and apparatus for enhancing the quality of service of a wireless communication
US7403528B2 (en) * 2002-09-13 2008-07-22 Lucent Technologies Inc. Method of data communication using a control message
KR100584431B1 (en) * 2003-02-14 2006-05-26 삼성전자주식회사 System and method for uplink data retransmission in code division multiple access communication system
US7349400B2 (en) * 2003-04-29 2008-03-25 Narus, Inc. Method and system for transport protocol reconstruction and timer synchronization for non-intrusive capturing and analysis of packets on a high-speed distributed network
US8553611B2 (en) * 2004-01-30 2013-10-08 Hewlett-Packard Development Company, L.P. Systems and methods for multi-access point transmission of data using a plurality of access points
US7124143B2 (en) * 2004-05-10 2006-10-17 Hitachi, Ltd. Data migration in storage system
KR100713394B1 (en) * 2004-06-16 2007-05-04 삼성전자주식회사 Method and apparatus for reordering uplink data packets in mobile telecommunication system using transmission sequence number and time stamp
KR101014933B1 (en) * 2005-08-01 2011-02-15 샤프 가부시키가이샤 Base station selection control method of cellular mobile communication system
NZ566202A (en) * 2005-08-24 2010-07-30 Qualcomm Inc Varied transmission time intervals for wireless communication system
WO2007023555A1 (en) * 2005-08-25 2007-03-01 Fujitsu Limited Mobile terminal and base station device
JP5120700B2 (en) * 2005-10-07 2013-01-16 日本電気株式会社 MIMO radio communication system and method using a plurality of base stations and mobile stations
KR100715681B1 (en) * 2005-12-06 2007-05-01 한국전자통신연구원 Apparatus and method of ubiquitous context-aware agent based on sensor networks
US8014415B2 (en) * 2005-12-30 2011-09-06 Meshnetworks, Inc. Apparatus, system and method for communicating information in a wireless communication network
KR100912784B1 (en) * 2006-01-05 2009-08-18 엘지전자 주식회사 Data transmission method and data retransmission method
US7782862B2 (en) * 2006-01-13 2010-08-24 Alcatel-Lucent Usa Inc. Method for controlling packet delivery in a packet switched network
US7444670B2 (en) * 2006-03-21 2008-10-28 International Business Machines Corporation Method and apparatus for migrating a virtual TPM instance and preserving uniqueness and completeness of the instance
WO2007126192A1 (en) * 2006-05-02 2007-11-08 Lg Electronics Inc. Data transmission method in mobile communications system
TW200814641A (en) * 2006-06-07 2008-03-16 Qualcomm Inc Methods and apparatus for using control values to control communications processing
CA2655406A1 (en) * 2006-06-20 2007-12-27 Ntt Docomo, Inc. User apparatus, base station and method for use in mobile communication system
US20080056171A1 (en) * 2006-08-21 2008-03-06 Khayrallah Ali S Arrangement and method for cellular data transmission
GB0616682D0 (en) * 2006-08-22 2006-10-04 Nec Corp Mobile telecommunications
JP5233102B2 (en) * 2006-09-14 2013-07-10 富士通株式会社 Mobile communication system and communication method thereof
US8094794B2 (en) * 2006-09-27 2012-01-10 At&T Intellectual Property I. L.P. Advertising message referrals
EP2088790B1 (en) * 2006-11-10 2014-10-22 Mitsubishi Electric Corporation Managing the resources of a plurality of base stations by a mobile station
US20080144572A1 (en) * 2006-12-15 2008-06-19 Makhijani Mahesh A Method and Apparatus for Achieving Frequency Diversity in Scheduled Packet Data Transmissions
US8830914B2 (en) * 2007-02-09 2014-09-09 Nokia Corporation Method and apparatus for acknowledgement signaling
US8594069B2 (en) * 2007-08-06 2013-11-26 Qualcomm Incorporated In-order data delivery during handover in a wireless communication system
US8451795B2 (en) * 2007-08-08 2013-05-28 Qualcomm Incorporated Handover in a wireless data packet communication system that avoid user data loss
US8767739B2 (en) * 2007-08-13 2014-07-01 Qualcomm Incorporated Optimizing in-order delivery of data packets during wireless communication handover
WO2009045945A2 (en) * 2007-10-01 2009-04-09 Interdigital Patent Holdings, Inc. Method and apparatus for pcdp discard
US8339944B2 (en) 2007-11-05 2012-12-25 Qualcomm Incorporated SDU discard mechanisms for wireless communication systems
EP2255572B1 (en) 2008-01-18 2018-12-26 Telefonaktiebolaget LM Ericsson (publ) Method and apparatus for radio link failure recovery in a telecommunication system
US20090204966A1 (en) * 2008-02-12 2009-08-13 Johnson Conrad J Utility for tasks to follow a user from device to device
US8199758B2 (en) * 2008-02-13 2012-06-12 Qualcomm Incorporated Variable abort timer
EP2104261A1 (en) * 2008-03-17 2009-09-23 Panasonic Corporation Improved HARQ process management
US20090238116A1 (en) * 2008-03-21 2009-09-24 Qual Comm Incorporated Method and apparatus for media access control -based fast cell switching for high-speed packet access
EP2107731B1 (en) * 2008-03-31 2016-11-09 Mitsubishi Electric R&D Centre Europe B.V. Method and a device for transferring a flow of data by a first telecommunication device to a second telecommunication device
US8107815B2 (en) * 2008-03-31 2012-01-31 Fujitsu Limited System and method for communicating wireless data utilizing a passive optical network
US7991378B2 (en) * 2008-04-14 2011-08-02 Telefonaktiebolaget Lm Ericsson (Publ) Time-error and frequency-error correction in a multi-carrier wireless communications system
US8321874B2 (en) * 2008-09-30 2012-11-27 Microsoft Corporation Intelligent context migration for user mode scheduling
US9320067B2 (en) 2008-11-24 2016-04-19 Qualcomm Incorporated Configuration of user equipment for peer-to-peer communication
US8638773B2 (en) * 2009-01-29 2014-01-28 Qualcomm Incorporated RLC for multi-carrier LTE systems
EP2410780A4 (en) * 2009-03-17 2017-05-10 Nec Corporation Wireless base station apparatus, wireless communication system, wireless communication method, and program
CN102007795B (en) * 2009-03-17 2016-05-25 华为技术有限公司 Packet transmission method, apparatus and system
US20100257239A1 (en) * 2009-04-02 2010-10-07 Qualcomm Incorporated Method and apparatus for establishing a social network through file transfers
WO2010148356A1 (en) * 2009-06-19 2010-12-23 Research In Motion Limited Mechanisms for data handling during a relay handover with s1 termination at evolved universal terrestrial radio access network access node
US8848548B2 (en) 2009-08-04 2014-09-30 Qualcomm Incorporated Internet radio broadcast using cellular
US8458353B2 (en) * 2009-08-13 2013-06-04 Qualcomm Incorporated Method and apparatus for link aggregation in a heterogeneous communication system
US8666403B2 (en) * 2009-10-23 2014-03-04 Nokia Solutions And Networks Oy Systems, methods, and apparatuses for facilitating device-to-device connection establishment
WO2011053490A1 (en) * 2009-10-30 2011-05-05 Motorola Mobility, Inc. Method and apparatus for communicating delivery of data packets to a user equipment in a wireless communication system
US8932223B2 (en) * 2009-11-02 2015-01-13 Board Of Regents, The University Of Texas System Catheter for intravascular ultrasound and photoacoustic imaging
WO2011069096A2 (en) * 2009-12-04 2011-06-09 Interdigital Patent Holdings, Inc. Bandwidth management for a converged gateway in a hybrid network
JP5506362B2 (en) * 2009-12-15 2014-05-28 キヤノン株式会社 Transmission device and transmission method
MY162196A (en) * 2010-01-08 2017-05-31 Interdigital Patent Holdings Inc Channel state information transmission for multiple carriers
KR101638195B1 (en) 2010-02-01 2016-07-08 삼성전자주식회사 A method and appratus for flow control between rlc and pdcp in a communication
KR101480929B1 (en) * 2010-02-12 2015-01-12 인터디지탈 테크날러지 코포레이션 Data split between multiple sites
KR20170127577A (en) * 2010-02-12 2017-11-21 인터디지탈 패튼 홀딩스, 인크 Method and apparatus for enhancing cell-edge user performance and signaling radio link failure conditions via downlink cooperative component carriers
US9516686B2 (en) 2010-03-17 2016-12-06 Qualcomm Incorporated Method and apparatus for establishing and maintaining peer-to-peer (P2P) communication on unlicensed spectrum
WO2011116823A1 (en) 2010-03-25 2011-09-29 Nokia Siemens Networks Oy Signalling of channel information
US9455897B2 (en) * 2010-04-06 2016-09-27 Qualcomm Incorporated Cooperative bandwidth aggregation using multipath transport
US9226288B2 (en) 2010-04-13 2015-12-29 Qualcomm Incorporated Method and apparatus for supporting communications in a heterogeneous network
US9485069B2 (en) 2010-04-15 2016-11-01 Qualcomm Incorporated Transmission and reception of proximity detection signal for peer discovery
US8498666B2 (en) * 2010-05-05 2013-07-30 Nokia Siemens Networks Oy Carrier aggregation for two radio systems
US8649363B2 (en) * 2010-06-01 2014-02-11 Htc Corporation Method of hybrid automatic repeat request entity handling and communication device thereof
WO2011156769A1 (en) * 2010-06-10 2011-12-15 Interdigital Patent Holdings, Inc. Reconfiguration and handover procedures for fuzzy cells
US8989087B2 (en) * 2010-06-15 2015-03-24 Telefonaktiebolaget L M Ericsson (Publ) Methods and devices for managing radio access in a communication system
US8891356B2 (en) * 2010-06-28 2014-11-18 Qualcomm Incorporated System and method for multi-point HSDPA communication utilizing a multi-link RLC sublayer
EP3253113B1 (en) 2010-07-26 2019-05-01 LG Electronics Inc. Aperiodic feedback in a wireless access system supporting multi-carrier aggregation
GB2484117A (en) 2010-09-30 2012-04-04 Fujitsu Ltd Automated network coverage hole detection by systematically modifying a connection reestablishment timer (T311) in a number of UEs
CN103141051B (en) * 2010-10-01 2016-01-27 交互数字专利控股公司 A method for the received two-stage reordering pdu and wtru
US8989004B2 (en) * 2010-11-08 2015-03-24 Qualcomm Incorporated System and method for multi-point HSDPA communication utilizing a multi-link PDCP sublayer
JP5759555B2 (en) * 2010-11-16 2015-08-05 テレフオンアクチーボラゲット エル エム エリクソン(パブル) Dynamic SAR release control to minimize RF exposure
US8744458B2 (en) * 2010-11-19 2014-06-03 Nokia Corporation Signaling mixed resource allocations for D2D communications
US9245047B2 (en) * 2010-12-10 2016-01-26 Wyse Technology L.L.C. Methods and systems for facilitating a remote desktop session utilizing a remote desktop client common interface
JP2012134829A (en) * 2010-12-22 2012-07-12 Ntt Docomo Inc Communication terminal device and data amount reporting method
KR101734480B1 (en) 2010-12-23 2017-05-12 한국전자통신연구원 Method for allocating home network prefix, inter-handoff and multi-homing system thereof
US20120163357A1 (en) * 2010-12-24 2012-06-28 Electronics And Telecommunications Research Institute Method of retransmitting and receiving packets in heterogeneous network environment
US9264881B2 (en) * 2011-01-04 2016-02-16 Qualcomm Incorporated Methods and apparatus for enhanced system access control for peer-to-peer wireless communication networks
US8611541B2 (en) * 2011-01-17 2013-12-17 Samsung Electronics Co., Ltd Method and apparatus for applying a ciphering configuration in a wireless communication network
US9673945B2 (en) * 2011-02-18 2017-06-06 Qualcomm Incorporated Implicitly linking aperiodic channel state information (A-CSI) reports to CSI-reference signal (CSI-RS) resources
WO2012118357A2 (en) * 2011-03-03 2012-09-07 엘지전자 주식회사 Method and device for transmitting control information in wireless communication system
WO2012124996A2 (en) * 2011-03-15 2012-09-20 엘지전자 주식회사 Method for transmitting/receiving signal and device therefor
EP2688226B1 (en) * 2011-03-18 2016-10-05 LG Electronics Inc. Method and device for communicating device-to-device
US9337999B2 (en) * 2011-04-01 2016-05-10 Intel Corporation Application usage continuum across platforms
KR20140035364A (en) * 2011-04-07 2014-03-21 인터디지탈 패튼 홀딩스, 인크 Method and apparatus for local data caching
EP2695420B1 (en) * 2011-04-07 2019-08-21 Nokia Solutions and Networks Oy Functional split for a multi-node carrier aggregation transmission scheme
US9042277B2 (en) 2011-04-11 2015-05-26 Qualcomm Incorporated Transmission of control information for FDD-TDD carrier aggregation
US20120268361A1 (en) * 2011-04-21 2012-10-25 Htc Corporation Hand-held electronic device and operation method applicable thereto
WO2012161510A2 (en) * 2011-05-23 2012-11-29 엘지전자 주식회사 Method and apparatus for transmitting control information in a wireless communication system
US8934350B2 (en) * 2011-05-23 2015-01-13 Qualcomm Incorporated Channel state information feedback for carrier aggregation with flexible carrier configurations
US20140198655A1 (en) 2011-06-01 2014-07-17 Ntt Docomo, Inc. Enhanced local access in mobile communications using small node devices
US20140153489A1 (en) * 2011-06-02 2014-06-05 Interdigital Patent Holdings, Inc. Methods, Apparatus and Systems for Inter-Converged Gateway (ICGW) Communications
EP2719235B1 (en) * 2011-06-10 2018-05-02 Nokia Technologies Oy Carrier aggregation
KR101595167B1 (en) * 2011-06-10 2016-02-17 엘지전자 주식회사 Method and apparatus for transmitting aperiodic channel state information in wireless communication system
US9271320B2 (en) * 2011-06-21 2016-02-23 Lg Electronics Inc. Method for performing communication between devices in a wireless access system, and device for same
KR20130008482A (en) * 2011-07-12 2013-01-22 한국전자통신연구원 Terminal of supporting direct communication using infra communication and direct communication method of the same
US8977268B2 (en) 2011-07-21 2015-03-10 Alcatel Lucent Methods and systems for controlling handovers in a co-channel network
US9160513B2 (en) * 2011-07-28 2015-10-13 Qualcomm Incorporated Method and apparatus for signaling control data of aggregated carriers
US9258086B2 (en) * 2011-08-03 2016-02-09 Qualcomm Incorporated Allocating physical hybrid ARQ indicator channel (PHICH) resources
RU2586892C2 (en) 2011-08-04 2016-06-10 Телефонактиеболагет Л М Эрикссон (Пабл) Improved stability of handover in cellular radio communication
CN103843261A (en) * 2011-08-05 2014-06-04 英特尔公司 Mobile device and method for cellular assisted device-to-device communication
KR101663392B1 (en) 2011-08-10 2016-10-06 인터디지탈 패튼 홀딩스, 인크 Uplink feedback for multi-site scheduling
GB2494460B (en) 2011-09-12 2013-10-23 Renesas Mobile Corp Methods and apparatus for controlling device-to-device discovery procedure
CN103021432B (en) * 2011-09-22 2017-06-16 南京中兴软件有限责任公司 A processing method and a terminal advertising
KR20130035964A (en) 2011-09-30 2013-04-09 한국전자통신연구원 Method for device-to-device communication based on cellular telecommunication system
US9338580B2 (en) 2011-10-21 2016-05-10 Qualcomm Incorporated Method and apparatus for packet loss rate-based codec adaptation
CN103095432A (en) * 2011-11-07 2013-05-08 北京三星通信技术研究有限公司 Method for sending hybridautomatic repeat-request acknowledgement (HARQ-ACK) feedback information
CN103918213B (en) 2011-11-10 2018-04-03 瑞典爱立信有限公司 Communication means, radio base station and radio network controller
GB2497916B (en) * 2011-11-11 2014-06-25 Broadcom Corp Methods, apparatus and computer programs for monitoring for discovery signals
KR101320230B1 (en) * 2011-12-09 2013-10-21 삼성전기주식회사 Apparatus for base station dual communication network
GB2497589A (en) * 2011-12-16 2013-06-19 Renesas Mobile Corp Resource Allocation in a Wireless Communication System
GB2497752B (en) * 2011-12-19 2014-08-06 Broadcom Corp Apparatus and methods for supporting device-to-device discovery in cellular communications
US8819798B2 (en) * 2011-12-29 2014-08-26 Ebay Inc. System and method for transferring states between electronic devices
US9036546B2 (en) * 2012-01-04 2015-05-19 Futurewei Technologies, Inc. System and method for device discovery for device-to-device communication in a cellular network
EP2613586B1 (en) 2012-01-06 2016-03-30 Alcatel Lucent Improved handling of high-speed users within a heterogeneous mobile network by means of RLF timer adjustment
WO2013104413A1 (en) * 2012-01-10 2013-07-18 Nokia Siemens Networks Oy Providing a radio bearer on a plurality of component carriers
GB2498575A (en) * 2012-01-20 2013-07-24 Renesas Mobile Corp Device-to-device discovery resource allocation for multiple cells in a device-to-device discovery area
US9507630B2 (en) * 2012-02-09 2016-11-29 Cisco Technology, Inc. Application context transfer for distributed computing resources
PL2815530T3 (en) 2012-02-14 2018-09-28 Samsung Electronics Co., Ltd. Method and apparatus for transmitting uplink and downlink data in tdd system
ES2671419T3 (en) * 2012-03-23 2018-06-06 Mediatek Inc. Methods for aggregation of multi-point carriers of physical layer and multi-point feedback configuration
US9686056B2 (en) * 2012-05-11 2017-06-20 Blackberry Limited PHICH transmission in time division duplex systems
US20150109973A1 (en) * 2012-05-11 2015-04-23 Nokia Solutions And Networks Oy Channel State Information (CSI) Report Subsets Under Flexible Time Division Duplex (TDD) UL/DL Configuration
US9225449B2 (en) * 2012-05-11 2015-12-29 Intel Corporation Performing a handover in a heterogeneous wireless network
KR101917766B1 (en) * 2012-05-25 2018-11-13 삼성전자주식회사 Method and apparatus for controlling congestion in a wireless communication system
KR101956195B1 (en) * 2012-05-31 2019-03-08 삼성전자 주식회사 Method and apparatus to transmit/receive physical channels supporting inter-enb carrier aggregation in communication systems
KR101443650B1 (en) * 2012-06-15 2014-09-23 엘지전자 주식회사 Method and user equipment for transmitting channel state information, and method and base station for receiving channels state information
US9160497B2 (en) * 2012-07-02 2015-10-13 Intel Corporation Application continuity with reroute and reset in a wireless communication network
EP2870710B1 (en) * 2012-07-06 2017-11-15 LG Electronics Inc. Method and apparatus for service access barring
US9912430B2 (en) * 2012-07-06 2018-03-06 Samsung Electronics Co. Ltd. Method and apparatus for channel state information feedback reporting
CN103546208B (en) * 2012-07-09 2016-08-24 电信科学技术研究院 A method for transmitting aperiodic channel state information, equipment and systems
EP3136619A1 (en) * 2012-07-13 2017-03-01 Electronics and Telecommunications Research Institute Discovery method for device to device communication between terminals
CN103580830B (en) * 2012-07-18 2018-11-27 北京三星通信技术研究有限公司 A method of sending HARQ-ACK feedback information
US9641299B2 (en) * 2012-07-31 2017-05-02 Lg Electronics Inc. Method for reporting aperiodic channel information in multi cell-based wireless communication system and device therefor
US9258741B2 (en) * 2012-08-03 2016-02-09 Blackberry Limited Carrier aggregation acknowledgement bits
US9197982B2 (en) * 2012-08-08 2015-11-24 Golba Llc Method and system for distributed transceivers for distributed access points connectivity
CA2882856A1 (en) * 2012-08-23 2014-02-27 Interdigital Patent Holdings, Inc. Method and apparatus for performing device-to-device discovery
KR101708574B1 (en) * 2012-08-23 2017-02-20 인터디지탈 패튼 홀딩스, 인크 Operating with multiple schedulers in a wireless system
JP5886968B2 (en) * 2012-08-28 2016-03-16 京セラ株式会社 Base station, user terminal and processor
CN103686676A (en) * 2012-08-31 2014-03-26 中兴通讯股份有限公司 Communication method and device of device-to-device communication system and system
US8923880B2 (en) * 2012-09-28 2014-12-30 Intel Corporation Selective joinder of user equipment with wireless cell
CN103858466A (en) * 2012-09-28 2014-06-11 华为技术有限公司 Aperiodic CSI feedback processing method and device
CN103716885B (en) * 2012-09-28 2017-09-29 电信科学技术研究院 A kind of local load bearing management method and equipment
WO2014058223A2 (en) * 2012-10-09 2014-04-17 엘지전자 주식회사 Method and apparatus for performing device-to-device communication in wireless communication system
CN103716776B (en) * 2012-10-09 2018-01-02 华为技术有限公司 A kind of D2D communication means and user equipment
US20140112194A1 (en) * 2012-10-19 2014-04-24 Samsung Electronics Co., Ltd System and method for ad-hoc/network assisted device discovery protocol for device to device communications
WO2014076857A1 (en) 2012-11-14 2014-05-22 Nec Corporation Control signalling method
US8594632B1 (en) * 2012-12-11 2013-11-26 Intel Corporation Device to-device (D2D) discovery without authenticating through cloud
US9462450B2 (en) * 2012-12-20 2016-10-04 Lg Electronics Inc. Signal transmission method and device for device-to-device (D2D) in wireless communication system
US9185697B2 (en) * 2012-12-27 2015-11-10 Google Technology Holdings LLC Method and apparatus for device-to-device communication
US9313607B2 (en) * 2013-01-18 2016-04-12 Telefonaktiebolaget L M Ericsson (Publ) Network-assisted UE detection in direct mode UE-to-UE communication
US9986380B2 (en) * 2013-01-25 2018-05-29 Blackberry Limited Proximity and interest determination by a wireless device
CN103997727B (en) * 2013-02-18 2019-08-30 中兴通讯股份有限公司 A kind of method for discovering equipment and device
US9955408B2 (en) * 2013-02-22 2018-04-24 Samsung Electronics Co., Ltd. Network-assisted multi-cell device discovery protocol for device-to-device communications
US9622064B2 (en) * 2013-03-14 2017-04-11 Fujitsu Limited Power control of neighbor discovery signals
US9706481B2 (en) * 2013-03-15 2017-07-11 Futurewei Technologies, Inc. System and method for time-power frequency hopping for D2D discovery
JP6099806B2 (en) * 2013-04-05 2017-03-22 エルジー エレクトロニクス インコーポレイティド Method and apparatus for proximity-based service between two or more operators
KR20140122178A (en) * 2013-04-09 2014-10-17 삼성전자주식회사 Method and apparatus for transmitting and receiving signal for device to device communication in wireless communication system
US9936405B2 (en) * 2013-05-07 2018-04-03 Lg Electronics Inc. Method for performing measurement in wireless communications system and apparatus therefor
US9674881B2 (en) * 2013-05-08 2017-06-06 Nokia Technologies Oy Device to device beacon, user equipment discovery, and resource allocation
US9713026B2 (en) * 2013-05-17 2017-07-18 Qualcomm Incorporated Channel state information (CSI) measurement and reporting for enhanced interference management for traffic adaptation (eIMTA) in LTE
US9642140B2 (en) * 2013-06-18 2017-05-02 Samsung Electronics Co., Ltd. Methods of UL TDM for inter-enodeb carrier aggregation
US9706568B2 (en) 2013-06-28 2017-07-11 Texas Instruments Incorporated Uplink control signaling for joint FDD and TDD carrier aggregation
US20160234670A1 (en) * 2013-07-11 2016-08-11 Nokia Technologies Oy Device-to-device synchronization method and apparatus for partial coverage
US9559817B2 (en) * 2013-07-19 2017-01-31 Sharp Kabushiki Kaisha Systems and methods for carrier aggregation
WO2015013862A1 (en) 2013-07-29 2015-02-05 Qualcomm Incorporated Dynamic indication of time division (tdd) duplex uplink/downlink subframe configurations
EP3029651A4 (en) * 2013-08-02 2017-01-25 LG Electronics Inc. Method for obtaining traffic information using local area communication, and apparatus therefor
US9125112B2 (en) * 2013-08-06 2015-09-01 Blackberry Limited Communicating radio resource configuration information
US9326122B2 (en) * 2013-08-08 2016-04-26 Intel IP Corporation User equipment and method for packet based device-to-device (D2D) discovery in an LTE network
US9648514B2 (en) * 2013-08-09 2017-05-09 Blackberry Limited Method and system for protocol layer enhancements in data offload over small cells
HUE039120T2 (en) * 2013-08-12 2018-12-28 Intel Corp Resource management in multiple radio access networks
JP6130605B2 (en) * 2013-08-14 2017-05-17 エルジー エレクトロニクス インコーポレイティド Method and apparatus for proximity based services
JP6078208B2 (en) * 2013-08-15 2017-02-08 テレフオンアクチーボラゲット エルエム エリクソン(パブル) Method and radio node for processing CSI reports
US20150089382A1 (en) 2013-09-26 2015-03-26 Wu-chi Feng Application context migration framework and protocol
US10014912B2 (en) * 2013-09-27 2018-07-03 Telefonaktiebolaget Lm Ericsson (Publ) Method and wireless device for monitoring a downlink control channel
US9924405B2 (en) * 2013-10-04 2018-03-20 Industrial Technology Research Institute Method for buffer status report in dual connectivity
US20150098416A1 (en) * 2013-10-04 2015-04-09 Innovative Sonic Corporation Method and apparatus for supporting device-to-device (d2d) discovery in a wireless communication system
JP5864034B2 (en) * 2013-10-11 2016-02-17 京セラ株式会社 Communication control method, user terminal, and communication device
CN104581613B (en) * 2013-10-29 2019-07-30 索尼公司 Enhance the method and apparatus of the proximity service discovery between user apparatus
CN105723778B (en) * 2013-11-06 2019-08-23 诺基亚技术有限公司 Method and apparatus for controlling D2D discovery procedure
US9661657B2 (en) * 2013-11-27 2017-05-23 Intel Corporation TCP traffic adaptation in wireless systems
US20150195056A1 (en) 2014-01-06 2015-07-09 Intel IP Corporation Systems, methods, and devices to support a fast tdd configuration indication
KR101918830B1 (en) * 2014-01-29 2018-11-14 인터디지탈 패튼 홀딩스, 인크 Resource selection for device to device discovery or communication
US9609502B2 (en) * 2014-02-24 2017-03-28 Intel IP Corporation Adaptive silencing mechanism for device-to-device (D2D) discovery
US20150264552A1 (en) * 2014-03-14 2015-09-17 Gang Xiong Systems, methods, and devices for device-to-device discovery and communication
US9847848B2 (en) * 2014-05-09 2017-12-19 Samsung Electronics Co., Ltd. Method and apparatus for performing communication by D2D communication terminal
KR20150128611A (en) * 2014-05-09 2015-11-18 삼성전자주식회사 Apparatus and method for avoiding interference in a device to device wireless communication system
WO2016021942A1 (en) * 2014-08-06 2016-02-11 Samsung Electronics Co., Ltd. Signal transmission/reception method and apparatus of d2d terminal
US20170223760A1 (en) * 2014-08-07 2017-08-03 Kyocera Corporation User terminal and base station

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6625622B1 (en) * 1999-05-14 2003-09-23 Eisenworld, Inc. Apparatus and method for transfering information between platforms
US20020198941A1 (en) * 2001-04-16 2002-12-26 Alexandru Gavrilescu Web site cobrowsing
USRE45729E1 (en) * 2005-12-12 2015-10-06 Electronics And Telecommunications Research Institute Apparatus and method for managing application context
US8504654B1 (en) * 2010-12-10 2013-08-06 Wyse Technology Inc. Methods and systems for facilitating a remote desktop session utilizing long polling

Also Published As

Publication number Publication date
US9560684B2 (en) 2017-01-31
US9504088B2 (en) 2016-11-22
CN105493554B (en) 2019-06-21
WO2015047659A1 (en) 2015-04-02
JP2018088703A (en) 2018-06-07
US20150085800A1 (en) 2015-03-26
CN106899382A (en) 2017-06-27
EP3050352B1 (en) 2019-02-27
US20180192309A1 (en) 2018-07-05
KR20160027987A (en) 2016-03-10
US20150085667A1 (en) 2015-03-26
US20160381587A1 (en) 2016-12-29
EP3050350A4 (en) 2017-10-18
EP3050268A1 (en) 2016-08-03
CN105493555B (en) 2019-04-16
HK1222927A1 (en) 2017-07-14
KR101775295B1 (en) 2017-09-05
EP3050345A4 (en) 2017-05-10
EP3049955A4 (en) 2017-05-03
HK1223218A1 (en) 2017-07-21
EP3064027B1 (en) 2018-06-13
HK1223224A1 (en) 2017-07-21
KR20160037981A (en) 2016-04-06
EP3050348A4 (en) 2017-09-20
WO2015047858A1 (en) 2015-04-02
US20150085764A1 (en) 2015-03-26
US20160205716A1 (en) 2016-07-14
JP2016531517A (en) 2016-10-06
US9986447B2 (en) 2018-05-29
HK1222970A1 (en) 2017-07-14
KR101903621B1 (en) 2018-10-04
EP3049955A1 (en) 2016-08-03
EP3050268A4 (en) 2017-08-23
US9572185B2 (en) 2017-02-14
EP3064027A1 (en) 2016-09-07
RU2016107020A (en) 2017-08-29
HUE042552T2 (en) 2019-07-29
HK1222486A1 (en) 2017-06-30
WO2015047569A1 (en) 2015-04-02
US20160128134A1 (en) 2016-05-05
CN105474595A (en) 2016-04-06
CN105493552A (en) 2016-04-13
EP3050348A1 (en) 2016-08-03
WO2015047556A1 (en) 2015-04-02
WO2015047580A1 (en) 2015-04-02
EP3050350A1 (en) 2016-08-03
WO2015047854A1 (en) 2015-04-02
CN105493616A (en) 2016-04-13
US20150087317A1 (en) 2015-03-26
ES2720512T3 (en) 2019-07-22
ES2682593T3 (en) 2018-09-21
HK1223219A1 (en) 2017-07-21
US9538565B2 (en) 2017-01-03
JP6285033B2 (en) 2018-02-28
CN105493555A (en) 2016-04-13
WO2015048287A1 (en) 2015-04-02
CN105519228B (en) 2019-09-24
US9258723B2 (en) 2016-02-09
EP3064027A4 (en) 2017-05-31
US9462629B2 (en) 2016-10-04
US20150085713A1 (en) 2015-03-26
EP3050227A4 (en) 2017-07-05
WO2015047866A1 (en) 2015-04-02
US9420627B2 (en) 2016-08-16
RU2631671C2 (en) 2017-09-26
US20160234702A1 (en) 2016-08-11
EP3050352A1 (en) 2016-08-03
CN105519182A (en) 2016-04-20
EP3050395A1 (en) 2016-08-03
EP3050352A4 (en) 2017-07-05
US10327163B2 (en) 2019-06-18
WO2015048277A1 (en) 2015-04-02
CN105519182B (en) 2019-04-23
CN105493067A (en) 2016-04-13
KR101780609B1 (en) 2017-09-20
KR20170107583A (en) 2017-09-25
CN105519228A (en) 2016-04-20
US20150085646A1 (en) 2015-03-26
EP3050395A4 (en) 2017-05-10
US10200890B2 (en) 2019-02-05
JP6151445B2 (en) 2017-06-21
WO2015048497A1 (en) 2015-04-02
HK1223765A1 (en) 2017-08-04
EP3050227A1 (en) 2016-08-03
HK1223763A1 (en) 2017-08-04
HUE039898T2 (en) 2019-02-28
EP3050345A1 (en) 2016-08-03
CN105493554A (en) 2016-04-13
JP2016532342A (en) 2016-10-13

Similar Documents

Publication Publication Date Title
EP2279602B1 (en) Systems and methods for remoting multimedia plugin calls
US10244039B2 (en) Shell integration on a mobile device for an application executing remotely on a server
US8782323B2 (en) Data storage management using a distributed cache scheme
US8732571B2 (en) Methods and systems for generating and displaying a preview image of a content area
DE202011110894U1 (en) Server-based data sharing in computer applications
US20120005346A1 (en) Hypervisor selection for hosting a virtual machine image
KR20110128846A (en) Programming model for synchronizing browser caches across devices and web services
US20100306381A1 (en) Mechanism for migration of client-side virtual machine system resources
US9330106B2 (en) Selective synchronization of remotely stored content
US20100262582A1 (en) Content synchronization across multiple computers
KR20130066603A (en) Initiating font subsets
US8493579B2 (en) Wireless printing from a device outside the network
US20110050712A1 (en) Extension To A Hypervisor That Utilizes Graphics Hardware On A Host
JP5551363B2 (en) Integrated charts in documents
US8924965B2 (en) Memory state transfer of virtual machine-controlled peripherals during migrations of the virtual machine
US20080218808A1 (en) Method and System For Universal File Types in a Document Review System
EP2656210B1 (en) Providing a persona-based application experience
US20100332489A1 (en) Interactive search monitoring in a virtual machine environment
US20110307788A1 (en) Role-based presentation views
US9063772B2 (en) Automated caching and mirroring of immutable data in distributed virtual machines via native interface components
US8467631B2 (en) Method and apparatus for identification of image uniqueness
CN102449602A (en) System and method for reducing startup cost of a software application
US20140222874A1 (en) Dynamic media content previews
AU2013293535B2 (en) Providing access to a remote application via a web client
US9292319B2 (en) Global computing interface

Legal Events

Date Code Title Description
AS Assignment

Owner name: INTEL IP CORPORATION, CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:FENG, WU-CHI;VENKATACHALAM, MUTHAIAH;KEDALAGUDDE, MEGHASHREE;SIGNING DATES FROM 20140407 TO 20140422;REEL/FRAME:033118/0583

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION