EP3075138B1 - Tcp-verkehrsanpassung in drahtlosen systemen - Google Patents

Tcp-verkehrsanpassung in drahtlosen systemen Download PDF

Info

Publication number
EP3075138B1
EP3075138B1 EP14866534.2A EP14866534A EP3075138B1 EP 3075138 B1 EP3075138 B1 EP 3075138B1 EP 14866534 A EP14866534 A EP 14866534A EP 3075138 B1 EP3075138 B1 EP 3075138B1
Authority
EP
European Patent Office
Prior art keywords
tcp
data
packets
layer circuitry
packet
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.)
Active
Application number
EP14866534.2A
Other languages
English (en)
French (fr)
Other versions
EP3075138A1 (de
EP3075138A4 (de
Inventor
Yifan Yu
Xiang Li
Guangjie Li
Xu Zhang
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.)
Apple Inc
Original Assignee
Intel 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
Application filed by Intel Corp filed Critical Intel Corp
Publication of EP3075138A1 publication Critical patent/EP3075138A1/de
Publication of EP3075138A4 publication Critical patent/EP3075138A4/de
Application granted granted Critical
Publication of EP3075138B1 publication Critical patent/EP3075138B1/de
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/24—Radio transmission systems, i.e. using radiation field for communication between two or more posts
    • H04B7/26—Radio transmission systems, i.e. using radiation field for communication between two or more posts at least one of which is mobile
    • H04B7/2621—Radio transmission systems, i.e. using radiation field for communication between two or more posts at least one of which is mobile using frequency division multiple access [FDMA]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0023—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the signalling
    • H04L1/0026—Transmission of channel quality indication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements 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/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1825—Adaptation of specific ARQ protocol parameters according to transmission conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L27/00—Modulated-carrier systems
    • H04L27/26—Systems using multi-frequency codes
    • H04L27/2601—Multicarrier modulation systems
    • H04L27/2602—Signal structure
    • H04L27/2605—Symbol extensions, e.g. Zero Tail, Unique Word [UW]
    • H04L27/2607—Cyclic extensions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/25—Flow control; Congestion control with rate being modified by the source upon detecting a change of network conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0032—Distributed allocation, i.e. involving a plurality of allocating devices, each making partial allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0048—Allocation of pilot signals, i.e. of signals known to the receiver
    • H04L5/0051—Allocation of pilot signals, i.e. of signals known to the receiver of dedicated pilots, i.e. pilots destined for a single user or terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0058—Allocation criteria
    • H04L5/0073—Allocation arrangements that take into account other cell interferences
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0078—Timing of allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/14—Two-way operation using the same type of signal, i.e. duplex
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/14—Two-way operation using the same type of signal, i.e. duplex
    • H04L5/1469—Two-way operation using the same type of signal, i.e. duplex using time-sharing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/22—Arrangements affording multiple use of the transmission path using time-division multiplexing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
    • H04L69/161—Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
    • H04L69/163—In-band adaptation of TCP data exchange; In-band control procedures
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/321—Interlayer communication protocols or service data unit [SDU] definitions; Interfaces between layers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/324—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the data link layer [OSI layer 2], e.g. HDLC
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/326—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the transport layer [OSI layer 4]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/14—Spectrum sharing arrangements between different networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0205—Traffic management, e.g. flow control or congestion control at the air interface
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0069—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/24—Connectivity information management, e.g. connectivity discovery or connectivity update
    • H04W40/30—Connectivity information management, e.g. connectivity discovery or connectivity update for proactive routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave
    • H04W52/0216—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave using a pre-established activity schedule, e.g. traffic indication frame
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0251—Power saving arrangements in terminal devices using monitoring of local events, e.g. events related to user activity
    • H04W52/0254—Power saving arrangements in terminal devices using monitoring of local events, e.g. events related to user activity detecting a user operation or a tactile contact or a motion of the device
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/02—Selection of wireless resources by user or terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446—Resources in time domain, e.g. slots or frames
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0453—Resources in frequency domain, e.g. a carrier in FDMA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/51—Allocation or scheduling criteria for wireless resources based on terminal or device properties
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/04—Scheduled access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/28—Discontinuous transmission [DTX]; Discontinuous reception [DRX]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/24—Cell structures
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/06—Transport layer protocols, e.g. TCP [Transport Control Protocol] over wireless
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/10—Small scale networks; Flat hierarchical networks
    • H04W84/12—WLAN [Wireless Local Area Networks]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H04W88/10—Access point devices adapted for operation in multiple networks, e.g. multi-mode access points
    • Y—GENERAL 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
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/50—Reducing energy consumption in communication networks in wire-line communication networks, e.g. low power modes or reduced link rate
    • Y—GENERAL 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
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • Embodiments of the present invention relate generally to the technical field of data processing, and more particularly, to computer devices operable to communicate data over a network.
  • the Internet protocol suite includes a plurality of protocols used to communicate data over the Internet.
  • the Internet Protocol (“IP”) is one of the main protocols used in the Internet protocol suite to route data over the Internet.
  • IP Internet Protocol
  • TCP Transmission Control Protocol
  • the TCP may enable communication of data between an application and the IP so that data from the application may be communicated over the Internet.
  • the TCP provides reliable and ordered data communication.
  • US 6,208,620 B1 shows a system for minimizing the effects of faults over an air link of a wireless transmission channel utilizing Transport Control Protocol (TCP).
  • TCP Transport Control Protocol
  • the system includes a TCP-Aware Agent Sublayer (TAS) in a protocol stack, which has a mechanism for caching both TCP packets during forward transmission and acknowledgment (ACK) return packets.
  • the caching mechanism is located near a wireless link of the wireless transmission channel.
  • the system also includes a link monitoring agent coupled to the TAS.
  • the link monitoring agent monitors the condition of the wireless transmission channel for an occurrence of a predefined fault. Once a predefined fault is detected, a system response is implemented based on the type of fault encountered.
  • the fault is an air link packet loss
  • an associated packet is immediately retransmitted from the cache, and when the fault is a temporary disconnect, a congestion window of the TCP source is closed.
  • phrases “A or B” and “A and/or B” means (A), (B), or (A and B).
  • phrase “A, B, and/or C” means (A), (B), (C), (A and B), (A and C), (B and C), or (A, B, and C).
  • 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.
  • ASIC Application Specific Integrated Circuit
  • a block diagram shows an environment 100 in which a user equipment (“UE") 110 is to communicate data with a remote host 150 according to TCP via a network node 120, in accordance with various embodiments.
  • the UE 110 may be any type of mobile computing device equipped with mobile broadband circuitry, such as a netbook, a tablet computer, a handheld computing device, a web-enabled appliance, a gaming device, a mobile phone, a smartphone, an eBook reader, a personal data assistant, or the like.
  • the UE 110 may be any device adapted to communicate over a network (e.g., the radio network 115) according to, for example, one or more 3rd Generation Partnership Project (“3GPP”) technical specifications.
  • 3GPP 3rd Generation Partnership Project
  • the UE 110 may be configured for intersystem communication across the radio network 115.
  • the radio network 115 may comprise a wireless cellular network, such as a Global System for Mobile Communications ("GSM”) network, Universal Mobile Telecommunications System (“UTMS”), and/or a code division multiple access (“CDMA”) network.
  • GSM Global System for Mobile Communications
  • UTMS Universal Mobile Telecommunications System
  • CDMA code division multiple access
  • a wireless cellular network may adhere to one or more standards, such as Long Term Evolution (“LTE”) or LTE-Advanced (“LTE-A”), third Generation (“3G”), fourth Generation (“4G”), fifth Generation (“5G”), Worldwide Interoperability for Microwave Access (“WiMAX”) (e.g., mobile WiMAX), or other similar standard.
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • 3G third Generation
  • 4G fourth Generation
  • 5G Fifth Generation
  • WiMAX Worldwide Interoperability for Microwave Access
  • WiMAX Worldwide Intero
  • the UE 110 may operate on a cell.
  • the network node 120 may be adapted to provide this cell and, therefore, the network node 120 may be an access node, such as a Node B or an evolved Node B (“eNB”) (macro-, pico-, or femto-eNB).
  • the network node 120 may be a gateway, such as a serving gateway ("S-GW”) or a packet data network gateway (“P-GW").
  • S-GW serving gateway
  • P-GW packet data network gateway
  • the radio network 115 and the network node 120 may be coupled with a plurality of components (not shown) associated with coupling the radio network 115 to a core network in which the network node 120 is provided.
  • the UE 110 may be adapted to communicate with the remote host across the Internet 130.
  • the remote host 150 may be any system adapted to provide a resource (e.g., streaming content, a website, or the like) over the Internet 130.
  • a resource e.g., streaming content, a website, or the like
  • TCP e.g., TCP/IP
  • data communicated between the UE 110 and the remote host 150 may be encapsulated in TCP packets. Because TCP is a reliable protocol, a TCP packet may prompt a TCP acknowledgment ("ACK") to confirm successful delivery.
  • ACK TCP acknowledgment
  • TCP packets originating at the UE 110 and intended for the remote host 150 may traverse the radio network 115 to the network node 120.
  • the network node 120 may respond to TCP packets from the UE 110 with TCP ACKs and then transmit those TCP packets over the Internet 130 to the remote host 150.
  • TCP packets originating at the remote host 150 and intended for the UE 110 may be similarly processed and acknowledged by the network node 120. In effect, this communication approach may generate appreciable TCP ACKs between the UE 110 and the network node 120.
  • the architectures of the UE 110 and the network node 120 may include reliable data transmission through lower level circuitry that enables the communication of TCP packets.
  • data transmitted between the UE 110 to the network node 120 over the radio network 115 may be reliably communicated through an Automatic Repeat Request (“ARQ”) mechanism implemented at link layer of the UE 110 and the network node 120.
  • ARQ Automatic Repeat Request
  • Radio Link Control (“RLC”) sub-layer of the link layer may transmit an ARQ ACK based on received data when the RLC sub-layer is operating in Acknowledged Mode (“AM”).
  • RLC Radio Link Control
  • MAC Media Access Control
  • HARQ Hybrid ARQ
  • UM Unacknowledged Mode
  • a layer/sub-layer circuitry may be dedicated circuitry configured to implement only the operations associated with that particular layer/sub-layer or may be shared circuitry configured to implement operations associated with more than one layer/sub-layer.
  • the TCP layer circuitry may be provided TCP ACKs for TCP packets without actually transmitting TCP ACKs over the radio network 115.
  • TCP packets to be transmitted between UE 110 and the network node 120 may be intercepted before transmission over the radio network 115.
  • the payload data from the TCP packets may be encapsulated according to a private protocol, which may be tunneled in a user datagram protocol ("UDP"), used for communication between the UE 110 and the network node 120.
  • UDP user datagram protocol
  • Data from the TCP layer circuitry may then be communicated between the UE 110 and the network 120 based on the private protocol, which may not require its own acknowledgment data to be transmitted over the radio network 115.
  • the UE 110 and the network node 120 may then generate TCP ACKs locally based on ARQ ACKs from the respective link layer circuitries.
  • data received according to the private protocol may be locally adapted to TCP packets and provided to TCP layer circuitry so that the TCP layer circuitry may be agnostic to the transmission mechanism implemented at the lower layer circuitry while still maintaining reliable data transmission.
  • the network node 120 may adapt data received according to the private protocol to TCP packets before transmission over the Internet 130 to the remote host 150. In this way, TCP ACKs to be transmitted over the radio network 115 may be reduced while the TCP semantic between the UE 110 and the remote host 150 may still be maintained.
  • a block diagram illustrates a UE 200 that is to adapt packets from TCP to a private protocol for transmission over a radio network, in accordance with various embodiments.
  • the UE 200 may be any UE adapted to communicate over a radio network, such as the UE 110 of FIG. 1 .
  • the UE 200 may include, but is not limited to, a main memory 210, a processor 218, a storage 220, a user interface 222, a display 224, and a communication interface 230.
  • One or more of these components may be communicatively coupled through a bus 219.
  • the bus 219 may be any subsystem adapted to transfer data within the UE 200.
  • the bus 219 may include a plurality of computer buses as well as additional circuitry adapted to transfer data.
  • the UE 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 UE 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.
  • 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, touch screen, or gesture recognition).
  • the processor 218 may execute some or all of the instructions for the user interface 222.
  • the processor 218 may be any processor suitable to execute instructions, such as instructions from the main memory 210 and/or instructions from the communication interface 230. 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 UE 200.
  • a dedicated processor e.g., a graphics processing unit
  • a network processor e.g., a network processor
  • 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 UE 200. Such data may be loaded from the storage 220 and/or the communication interface 230.
  • 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 an application 211 that is to be executed by the processor 218.
  • the application 211 may be any application associated with communication of resources over the Internet.
  • the application 211 may be a web browser application, a voice over IP ("VoIP") application, a file-sharing application, a messaging application (e.g., an email application, an instant messaging application, etc.), a social media application, a media application (e.g., an application adapted to stream audio and/or video), or the like.
  • VoIP voice over IP
  • a file-sharing application e.g., a messaging application, e.g., an email application, an instant messaging application, etc.
  • a social media application e.g., an application adapted to stream audio and/or video
  • media application e.g., an application adapted to stream audio and/or video
  • the application 211 may cause the communication interface 230 to communicate data to and from a remote host that is accessible over the Internet. Based on the communication over the Internet, data to be communicated to and from the application 211 may be processed at the IP layer circuitry 233. However, the application 211 may first generate data to be processed at the TCP layer circuitry 231 for reliable communication over the Internet. The TCP layer circuitry 231 may packetize data received from the application 211.
  • the UE 200 may not be directly connected to the Internet, but may rely on a network node to relay TCP packets associated with the application 211 over a radio network.
  • an agent 232 may be implemented at the communication interface 230, for example, between the TCP layer circuitry 231 and the IP layer circuitry 233.
  • the agent 232 may be hardware, software, firmware, and/or a combination of such.
  • the agent 232 may be included in an ASIC or other integrated circuit.
  • instructions associated with the agent 232 are to be executed by the processor 218 and, therefore, instructions associated with the agent 232 may be stored, at least temporarily, in main memory 210.
  • the agent 232 may be implemented at least partially in circuitry of the UE 200, such as processing circuitry, processor circuitry, logic circuitry, and the like.
  • agent circuitry may include circuitry configured to perform various operations described with respect to the agent 232.
  • the agent 232 may be adapted to implement a private protocol between the UE 200 and a network node.
  • the private protocol may feature connection-oriented data stream support so that the TCP layer circuitry 231 and the application 211 may operate without any appreciable adaptations from standard configurations - e.g., the TCP semantic between the UE 200 and the remote host to provide resources to the UE 200 may be maintained.
  • the private protocol may be tunneled in another transport-layer protocol other than TCP, for example, a protocol that does not require reliability, guaranteed delivery, duplication protection, and/or initial connection establishment.
  • the private protocol may be tunneled in UDP.
  • the agent 232 may be adapted to process a TCP synchronize packet ("SYN"), which may be received from the TCP layer circuitry 231.
  • the agent 232 may intercept the TCP SYN and identify a source port value and a destination port value from the TCP SYN.
  • the agent 232 may then apply a hash function to the source port value and the destination port value to generate a hash value.
  • the hash value may then be inserted into a data packet according to the private protocol (e.g., into a header of a private-protocol data packet).
  • the hash value may consume fewer bytes than the source port value and the destination port value such that the data packet itself consumes fewer resources when transmitted to a network node over a radio network - e.g., a source port value may be two bytes and a destination port value may be two bytes, but a hash value computed from the source port value and the destination port value may itself only require two bytes.
  • the agent 232 may include or be communicatively coupled with a lookup table that maps hash values to source and destination port values.
  • the agent 232 may cause a data packet to be transmitted to a network node that includes the source port value and the destination port value as well as a predetermined value that indicates the data packet is to be used to maintain the TCP semantic (e.g., the network node may be adapted to apply the same hash function to the source port value and destination port value, as well as maintain a lookup table that is to map the hash value to the source port value and the destination port value).
  • the agent 232 may be adapted to process a data packet from a network node that includes the source port value and the destination port value as well as a predetermined value that indicates the data packet is to be used to maintain the TCP semantic between the remote host and the UE 200.
  • the agent 232 may be adapted to intercept TCP packets generated at the TCP layer circuitry 231. For each TCP packet, the agent 232 may extract payload data and insert that payload data into a data packet according to the private protocol. Additionally, the agent 232 may identify a source port value, a destination port value, and a TCP sequence number ("SN") from the header of the TCP packet. The agent 232 may then determine a hash value associated with the source port value and the destination port value, such as by accessing a lookup table that maps the source and destination port values to a hash value or by applying a hash function to the source and destination port values. The agent 232 may then provide the data packet to the lower layer circuitry 233-238 to be transmitted to the remote host.
  • SN TCP sequence number
  • the lower layer circuitry 233-238 may include IP layer circuitry 233 adapted to communicate data based on IP addresses.
  • the IP layer circuitry 233 may be communicatively coupled with Packet Data Convergence Protocol ("PDCP") layer circuitry 234.
  • PDCP Packet Data Convergence Protocol
  • the PDCP layer circuitry 234 may be associated with, for example, interface control over the radio network and user planes. Further, the PDCP layer circuitry 234 may perform compression and decompression of IP headers.
  • the PDCP layer circuitry 234 may be communicatively coupled with link layer circuitry 235.
  • the link layer circuitry 235 may be comprised of at least two sub-layers: Radio Link Control (“RLC”) layer circuitry 236 and Media Access Control (“MAC”) layer circuitry 237.
  • RLC Radio Link Control
  • MAC Media Access Control
  • the RLC layer circuitry 236 may provide, for example, concatenation, segmentation, and/or reassembly of data units (e.g., protocol data units and/or service data units), sequential delivery of data units, duplication detection, error recovery, and the like for communication with the network node over the radio network.
  • the MAC layer circuitry 237 may provide addressing and channel access mechanisms, as well as interfacing with the physical (“PHY") layer circuitry 238.
  • the link layer circuitry 235 may be communicatively coupled with the PHY layer circuitry 238, which may include hardware for transmitting data over the radio network.
  • the PHY layer circuitry 238 may include one or more network adapters and or circuitries for communication of data over one or more radio networks (e.g., a Wi-Fi network, a cellular data network, etc.).
  • the link layer circuitry 235 may provide ARQ mechanisms - e.g., the RLC layer circuitry 236 may process ARQ data when operating in AM, and the MAC layer circuitry 237 may process HARQ data when the RLC layer circuitry 236 is operating in UM.
  • the agent 232 may be adapted to use ARQ data from the link layer circuitry 235 to locally generate TCP ACK data for the TCP layer circuitry 231. For each TCP packet having payload data, the agent 232 may identify a TCP SN from the header of the TCP packet.
  • the agent 232 may map a protocol data unit ("PDU") SN to a TCP SN, such as by updating a lookup table. For example, the agent 232 may interact with the PDCP layer circuitry 234 to obtain a PDU SN associated with the data packet at the link layer circuitry 235, which the agent 232 may then map to the original TCP SN.
  • the link layer circuitry 235 may receive ARQ data associated with that data packet.
  • the agent 232 may communicate with the link layer circuitry 235, directly or through PDCP layer circuitry 234, to determine if the ARQ data indicates that the data packet has been successfully transmitted to the network node.
  • the agent 232 may access a lookup table based on a PDU that is indicated by the ARQ data as successfully transmitted to the network node and, based on that ARQ data, locally generate a TCP ACK for the TCP SN corresponding to the PDU SN.
  • the agent 232 may provide this locally generated TCP ACK to the TCP layer circuitry 231 so that the reliable TCP data communication may be maintained and the TCP layer circuitry 231 (and, by association, the application 211) may operate agnostic to the private protocol implemented by the agent 232 to reduce TCP traffic over the radio network.
  • the agent 232 may be adapted to receive private-protocol data packets from the lower level circuitry 233-238. For each private-protocol data packet, the agent 232 may extract payload data and insert that payload data into a TCP packet according to TCP. Additionally, the agent 232 may identify a hash value from the private-protocol data packet (e.g., from a header of the data packet) and determine a source port value and a destination port value from the hash value, such as by accessing a lookup table. The agent 232 may insert the source and destination port values into a header of the TCP packet and provide the TCP packet to the TCP layer circuitry 231. The TCP layer circuitry 231 may then process the TCP packet from the agent according to the TCP semantic, such as by providing payload data to the application 211.
  • TCP Transmission Control Protocol
  • a private-protocol data packet may be transmitted between the agent 232 and the network node.
  • This private-protocol data packet may serve as a TCP connection termination message ("FIN") for the TCP layer circuitry 231.
  • this private-protocol data packet may include a hash value that is based on the source port value and the destination port value of the TCP connection, but may have no payload data.
  • the agent 232 may be adapted to generate such a private-protocol data packet based on a TCP FIN received from the TCP layer circuitry 231.
  • the agent 232 may be adapted to generate a TCP FIN for the TCP layer circuitry 231 based on such a private-protocol data packet.
  • a block diagram illustrates a network node 300 that is to adapt data for transmission between a private protocol and TCP, in accordance with various embodiments.
  • the network node 300 may be any server adapted to facilitate communication between a UE and a remote host over the Internet, such as the network node 120 of FIG. 1 .
  • the network node 300 may include, but is not limited to, processor 318, storage 320, a main memory 310, and a communication interface 330. These components may be communicatively coupled through a bus 319.
  • the bus 319 may be any subsystem adapted to transfer data within the network node 300.
  • the bus 319 may include a plurality of computer buses as well as additional circuitry adapted to transfer data.
  • the processor 318 may be any processor suitable to execute instructions, such as instructions from the main memory 310. Accordingly, the processor 318 may be, for example, a central processing unit ("CPU"), a microprocessor, or another similar processor. In some embodiments, the processor 318 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 network node 300.
  • a dedicated processor e.g., a graphics processing unit
  • network processor e.g., a network processor, or any processor suitable to execute operations of the network node 300.
  • the main memory 310 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 318).
  • the main memory 310 may also include cache memory, such as a cache located at the processor 318.
  • the main memory 310 may be volatile, such as SRAM and/or DRAM, and may provide storage (at least temporarily) of computer-readable instructions, data structures, software applications, and other data for the network node 300.
  • Such data may be loaded from the storage 320, which may be, for example, one or more hard disk drives, solid state drives, compact disks and drives, digital versatile disks and drives, and the like.
  • the network node 300 may be adapted to communicate with a UE over a radio network and with a remote host over the Internet.
  • the network node 300 may include a communication interface 330.
  • the communication interface 330 may allow the network node 300 to relay data between the UE and the remote host.
  • the network node 300 may include a proxy 332, for example, between the TCP layer circuitry 331 and the IP layer circuitry 333.
  • the proxy 332 may be hardware, software, firmware, and/or a combination of such.
  • the proxy 332 may be included in an ASIC or other integrated circuit.
  • instructions associated with the proxy 332 are to be executed by the processor 318 and, therefore, instructions associated with the proxy 332 may be stored, at least temporarily, in main memory 310.
  • the proxy 332 may be implemented at least partially in circuitry of the network node 300, such as processing circuitry, processor circuitry, logic circuitry, and the like.
  • proxy circuitry may include circuitry configured to perform various operations described with respect to the proxy 332.
  • the proxy 332 may be adapted to implement a private protocol between the network node 300 and the UE.
  • the private protocol may allow TCP layer circuitries of the UE and the remote host to maintain the TCP semantic while reducing TCP traffic over a radio network between the network node 300 and the UE.
  • the private protocol may be tunneled, for example, in UDP.
  • the proxy 332 may be adapted to process a packet that indicates a TCP connection is to be established, which may be received from the UE or the remote host.
  • the proxy 332 may receive a data packet according to the private protocol that includes a source port value and a destination port value as well as a predetermined value that indicates the data packet is to be used to maintain the TCP semantic between the UE and the remote host.
  • the proxy 332 may be adapted to apply a hash function to the source port value and destination port value, as well as maintain a lookup table that is to map the hash value to the source port value and the destination port value.
  • a TCP SYN may be transmitted to the remote host to establish a TCP connection at that endpoint.
  • the proxy 332 may intercept a TCP SYN (that includes a source port value and a destination port value) from the remote host to establish a TCP connection with the UE. The proxy 332 may then apply a hash function to the source port value and the destination port value from the TCP SYN to generate a hash value.
  • a TCP SYN that includes a source port value and a destination port value
  • the proxy 332 may generate a data packet according to the private protocol that includes the source port value and the destination port value from the TCP SYN as well as a predetermined value that indicates the data packet is to be used to maintain the TCP semantic (e.g., the UE may be adapted to apply the same hash function to the source port value and destination port value, as well as maintain a lookup table that is to map the hash value to the source port value and the destination port value). Accordingly, respective TCP layer circuitries at the UE and the remote host may operate according to that TCP connection with respective endpoints established at the UE and the remote host.
  • the proxy 332 may be adapted to intercept TCP packets received from the remote host at the TCP layer circuitry 331 and to be relayed to the UE. For each TCP packet, the proxy 332 may extract payload data and insert that payload data into a data packet according to the private protocol. Additionally, the proxy 332 may identify a source port value, a destination port value, and/or a TCP SN from the header of the TCP packet.
  • the proxy 332 may then determine a hash value associated with the source port value and the destination port value, such as by accessing a lookup table that maps the source and destination port values to a hash value or by applying a hash function to the source and destination port values.
  • the proxy 332 may then provide the data packet to the lower layer circuitry 333-338 to be transmitted to the remote host.
  • the proxy 332 may be adapted to receive private-protocol data packets from the lower level circuitry 333-338. For each private-protocol data packet, the proxy 332 may extract payload data and insert that payload data into a TCP packet according to TCP. Additionally, the proxy 332 may identify a hash value from the private-protocol data packet (e.g., from a header of the data packet) and determine a source port value and a destination port value from the hash value, such as by accessing a lookup table. The proxy 332 may insert the source and destination port values into a header of the TCP packet and provide the TCP packet to the TCP layer circuitry 331. The TCP layer circuitry 331 may then process the TCP packet from the agent according to the TCP semantic, such as by providing the TCP packet to the lower layer circuitry 333-338 for transmission to the remote host.
  • TCP Transmission Control Protocol
  • the lower layer circuitry 333-338 may include IP layer circuitry 333 adapted to communicate data based on IP addresses.
  • the IP layer circuitry 333 may be communicatively coupled with PDCP layer circuitry 334.
  • the PDCP layer circuitry 334 may perform, among other operations, compression and decompression of IP headers.
  • the PDCP layer circuitry 334 may be communicatively coupled with link layer circuitry 335.
  • the link layer circuitry 335 may be comprised of at least two sub-layers: RLC layer circuitry 336 and MAC layer circuitry 337.
  • the RLC layer circuitry 336 may provide, for example, concatenation, segmentation, and/or reassembly of data units (e.g., protocol data units and/or service data units), sequential delivery of data units, duplication detection, error recovery, and the like for communication with the UE over the radio network.
  • the MAC layer circuitry 337 may provide addressing and channel access mechanisms, as well as interfacing with the PHY layer circuitry 338.
  • the link layer circuitry 335 may be communicatively coupled with the PHY layer circuitry 338, which may include hardware circuitries for transmitting data over the radio network UE as well as over the Internet to the remote host.
  • the PHY layer circuitry 338 may include one or more network adapters, modems, and or circuitries for communication of data over one or more networks.
  • the link layer circuitry 335 may implement ARQ mechanisms - e.g., the RLC layer circuitry 336 may transmit ARQ data and/or the MAC layer circuitry 337 may transmit HARQ data. For each private-protocol data packet received at the link layer circuitry 335, the link layer circuitry 335 may transmit an ARQ ACK and/or an HARQ ACK to the UE, which the UE may use to locally generate a TCP ACK.
  • the proxy 332 may be adapted to use ARQ data from the link layer circuitry 335 to locally generate TCP ACK data for the TCP layer circuitry 331. For each TCP packet having payload data, the proxy 332 may identify a TCP SN from the header of the TCP packet. As the proxy 332 encapsulates payload data from the TCP packet to the lower layer circuitry 333-338, the proxy 332 may map a PDU SN to a TCP SN, such as by updating a lookup table.
  • the proxy 332 may interact with the PDCP layer circuitry 334 to obtain a PDU SN associated with the data packet at the link layer circuitry 335, which the proxy 332 may then map to the original TCP SN.
  • the link layer circuitry 335 may receive ARQ data associated with that data packet.
  • the proxy 332 may communicate with the link layer circuitry 335, directly or through PDCP layer circuitry 334, to determine if the ARQ data indicates that the data packet has been successfully transmitted to the UE.
  • the proxy 332 may access a lookup table based on a PDU that is indicated by the ARQ data as successfully transmitted to the UE and, based on that ARQ data, locally generate a TCP ACK for the TCP SN corresponding to the PDU SN.
  • the proxy 332 may provide this locally generated TCP ACK to the TCP layer circuitry 331 so that the reliable TCP data communication may be maintained and the TCP layer circuitry 331 may operate agnostic to the private protocol implemented by the proxy 332 to reduce TCP traffic over the radio network.
  • the proxy 332 may implement or be communicatively coupled with a cache, such as a cache at main memory 310.
  • the proxy 332 may cache payload data from data packets from the UE. This caching mechanism may allow the proxy 332 to retransmit data, received from the UE, to the remote host when a TCP ACK is not received from the remote host without requiring the UE to retransmit data that was not acknowledged as received by the remote host.
  • a private-protocol data packet may be transmitted between the proxy 332 and the UE.
  • This private-protocol data packet may serve as a TCP FIN for the TCP layer circuitry 331.
  • this private-protocol data packet may include a hash value that is based on the source port value and the destination port value of the TCP connection, but may have no payload data.
  • the proxy 332 may be adapted to generate a private-protocol data packet based on a TCP FIN received from the TCP layer circuitry 331 (e.g., a TCP FIN originating at the remote host).
  • the proxy 332 may be adapted to generate a TCP FIN for the TCP layer circuitry 331 (e.g., to be transmitted to the remote host) based on such a private-protocol data packet received from the UE.
  • the network node 300 may be adapted to provide a wireless cell on which a UE may operate. However, this cell may have limited coverage and, therefore, the network node 300 may be adapted to hand the UE over to another network node adapted to provide another cell to the UE.
  • the proxy 332 may be adapted to transmit a mapping table (e.g., a mapping table that is to map a hash value to a source port value and a destination port value) to the other network node based on the handover of the UE to the other network node.
  • a mapping table e.g., a mapping table that is to map a hash value to a source port value and a destination port value
  • FIG. 4 a block diagram shows a system 400 having reduced TCP traffic between a UE 405 and a network node 440 while maintaining a TCP semantic 480 between the UE 405 and a remote host 470.
  • FIG. 4 may illustrate an embodiment of the environment 100 shown in FIG. 1 . Accordingly, the UE 405 may an embodiment of the UE 110, the network node 440 may be an embodiment of the network node 120, and/or the remote host 470 may be an embodiment of the remote host 150 of FIG. 1 .
  • an application 410 executed by the UE 405 may wish to reliably communicate with an application 472 executed by the remote host 470.
  • the application 472 at the remote host 470 may be accessible to the application 410 at the UE 405 over the Internet and, therefore, the UE 405 and the remote host 470 may use TCP/IP. Accordingly, the respective TCP layer circuitries 412, 474 at the UE 405 and the remote host 470 may communicate according to the TCP semantic 480.
  • Data to be communicated between the UE 405 and the remote host 470 may traverse through the network node 440.
  • the arrangement may cause an appreciable volume of TCP ACK data to be communicated between the UE 405 and the network node 440 that may be effectively repetitive of the ARQ and/or HARQ mechanisms implemented by the RLC layer circuitries 424, 454 and MAC layer circuitries 426, 456, respectively. That is, because the ARQ and/or HARQ mechanisms already provide reliable data communication at the link layer circuitries 424, 426, 454, 456, the TCP ACK mechanisms of the TCP layer circuitries 412, 442 may be unnecessary. Therefore, the ARQ and/or HARQ mechanisms may be used at the UE 405 and the network node 440 to locally generate TCP ACK data without requiring transmission of TCP ACK data over the air between the UE 405 and the network node 440.
  • the application 410 may provide data to the TCP layer circuitry 412.
  • the TCP layer circuitry 412 may be adapted to generate a plurality of TCP packets 414 based on this data.
  • the agent 416 may be adapted to intercept the TCP packets 414 as they are provided to the lower level circuitries 420-428.
  • the agent 416 may be adapted to communicate with a proxy 446 at the network node 440 according to a private protocol 484.
  • the private protocol 484 may be a system of digital rules for exchanging data.
  • the agent 416 and the proxy 446 may be adapted to receive, process, and/or interpret data received according to this system of digital rules.
  • Other layer circuitries 412, 420-428, 442, 450-458 may not be adapted to communicate data according to the private protocol 484.
  • the agent 416 may encapsulate payload data from the plurality of TCP packets 414 into data packets according to the private protocol 484. To identify the source and destination endpoints associated with each TCP packet, the agent 416 may be adapted to identify a source port value and destination port value from the TCP packet. The agent may apply a hash function to the source and destination port values to generate a hash value and store the hash value in a table that associates the hash value with the source and destination port values.
  • the agent 416 may identify a TCP SN from each header of each TCP packet 414 provided thereto. As the agent 416 provides the private-protocol data packets 418 to the lower layer circuitries 420-428, the agent 416 may associate each TCP SN with a PDU from the lower level circuitries 420-428. At the RLC layer circuitry 424, each data packet may be associated with an RLC PDU. Similarly, each data packet may be associated with an MAC PDU at the MAC layer circuitry 426.
  • the agent 416 may be adapted to receive the RLC PDU and/or MAC PDU and associate the TCP SN with at least one of the RLC PDU or the MAC PDU (e.g., the agent 416 may store the TCP SN and the PDU in a table that is to map TCP SNs to PDUs).
  • the link layer circuitries 424, 426 may provide the private-protocol data packets to the PHY layer circuitry 428, which may then transmit the private-protocol data packets to the network node 440. From the PHY layer circuitry 458 of the network node 440, the link layer circuitries 454, 456 may receive those private-protocol data packets. As data packets are received at the link layer circuitries 454, 456, the link layer circuitries 454, 456 may cause ARQ and/or HARQ ACK data to be transmitted to the UE 405.
  • the agent 416 may be adapted to determine from the ARQ and/or HARQ ACK data whether each data packet has been successfully transmitted to the network node 440.
  • the RLC layer circuitry 424 may provide ARQ data 430 to the agent 416. From the ARQ data 430, the agent 416 may identify an acknowledgment that a data packet corresponding to an RLC PDU has been successfully transmitted to the network node 440. In an embodiment in which the RLC layer circuitry 424 is operating in UM mode, the MAC layer circuitry 426 may provide HARQ data 432 to the agent 416. From the HARQ data 432, the agent 416 may identify an acknowledgment that a data packet corresponding to an MAC PDU has been successfully transmitted to the network node 440.
  • the agent 416 may then identify a TCP SN based on the PDU, such as by accessing a lookup table with the PDU, and locally generate a TCP ACK for the identified TCP SN.
  • the agent 416 may provide the locally generated TCP ACK to the TCP layer circuitry 412 so that the TCP layer circuitry 412 may provide reliable data communication for the application 410.
  • the private-protocol data packets 448 may reach the proxy 446 from the lower level circuitries 450-458.
  • the proxy 446 may extract payload data and insert that payload data into a TCP packet to maintain the TCP semantic 480.
  • the proxy 446 may identify a hash value from the private-protocol data packet (e.g., from a header of the data packet) and determine a source port value and a destination port value from the hash value, such as by accessing a lookup table.
  • the proxy 446 may insert the source and destination port values into a header of the TCP packet and provide the TCP packet to the TCP layer circuitry 442.
  • the TCP layer circuitry 442 may then provide the TCP packet to the IP layer circuitry 450.
  • the IP layer circuitry 450 may cause the TCP packet to be transported over the Internet to the IP layer circuitry 476 of the remote host according to IP 486.
  • an application 472 may provide data to TCP layer circuitry 474 to be communicated to the UE 405 according to the TCP semantic 480.
  • the TCP layer circuitry 474 may packetize this application data and provide the TCP packets to the IP layer circuitry 476, which may transmit the TCP packets to the network node 440 according to IP 486.
  • the TCP packets may reach the TCP layer circuitry 442, and the proxy 446 may intercept these TCP packets 444 that are to be transmitted to the UE 405. For each TCP packet, the proxy 446 may extract payload data and insert that payload data into a data packet according to the private protocol 484.
  • the proxy 446 may identify a source port value, a destination port value, and/or a TCP SN from the header of the TCP packet. The proxy 446 may then determine a hash value associated with the source port value and the destination port value, such as by accessing a lookup table that associates the source and destination port values to a hash value or by applying a hash function to the source and destination port values. The proxy 446 may then provide the data packet, as part of a plurality of private-protocol data packets 448, to the lower layer circuitry 450-458 to be transmitted to the UE 405.
  • the proxy 446 may identify a TCP SN from each header of each TCP packet 444 provided thereto. As the proxy 446 provides the private-protocol data packets 448 to the lower layer circuitries 450-458, the proxy 446 may associate each TCP SN with a PDU from the lower level circuitries 450-458. At the RLC layer circuitry 454, each data packet may be associated with an RLC PDU. Similarly, each data packet may be associated with an MAC PDU at the MAC layer circuitry 456.
  • the proxy 446 may be adapted to receive the RLC PDU and/or MAC PDU and associate the TCP SN with at least one of the RLC PDU or the MAC PDU (e.g., the proxy 446 may store the TCP SN and the PDU in a table that is to map TCP SNs to PDUs).
  • the link layer circuitries 454, 456 may provide the private-protocol data packets to the PHY layer circuitry 458, which may then transmit the private-protocol data packets to the UE 405. From the PHY layer circuitry 428 of the UE 405, the link layer circuitries 424, 426 may receive those private-protocol data packets. As data packets are received at the link layer circuitries 424, 426, the link layer circuitries 424, 426 may cause ARQ and/or HARQ ACK data to be transmitted to the network node 440.
  • the proxy 446 may be adapted to determine from the ARQ and/or HARQ ACK data whether each data packet has been successfully transmitted to the UE 405.
  • the RLC layer circuitry 454 may provide ARQ data 460 to the proxy 446. From the ARQ data 460, the proxy 446 may identify an acknowledgment that a data packet corresponding to an RLC PDU has been successfully transmitted to the UE 405. In an embodiment in which the RLC layer circuitry 454 is operating in UM mode, the MAC layer circuitry 456 may provide HARQ data 462 to the proxy 446. From the HARQ data 462, the proxy 446 may identify an acknowledgment that a data packet corresponding to an MAC PDU has been successfully transmitted to the UE 405.
  • the proxy 446 may then identify a TCP SN based on the PDU, such as by accessing a lookup table with the PDU, and locally generate a TCP ACK for the identified TCP SN.
  • the proxy 446 may provide the locally generated TCP ACK to the TCP layer circuitry 442 so that the TCP layer circuitry 442 may provide reliable data communication.
  • the agent 416 may be adapted to receive private-protocol data packets from the lower level circuitries 420-428. For each private-protocol data packet 418, the agent 416 may extract payload data and insert that payload data into a TCP packet according to TCP. Additionally, the agent 416 may identify a hash value from the private-protocol data packet (e.g., from a header of the data packet) and determine a source port value and a destination port value from the hash value, such as by accessing a lookup table. The agent 416 may insert the source and destination port values into a header of the TCP packet and provide the TCP packet, included in a plurality of TCP packets 414, to the TCP layer circuitry 412. The TCP layer circuitry 412 may then process the TCP packet according to the TCP semantic 480 maintained between the TCP layer circuitry 412 of the UE 405 and the TCP layer circuitry 474 of the remote host 470.
  • TCP TCP semantic 480 maintained between the TCP
  • FIG. 5 a sequence diagram illustrates a sequence 500 of uplink data transmission between a UE 505 and a remote host 530 according to a TCP semantic, according to various embodiments.
  • FIG. 5 may illustrate an embodiment of a sequence of data communication in the environment 100 shown in FIG. 1 .
  • the UE 505 may be an embodiment of the UE 110
  • the network node 520 may be an embodiment of the network node 120
  • the remote host 530 may be an embodiment of the remote host 150 of FIG. 1 .
  • TCP layer circuitry 510 of the UE 505 may provide a TCP packet to an agent 512 that is to be communicated to the remote host 530 (operation 552).
  • the agent 512 may extract a source port value, a destination port value, and a TCP SN from a header of the TCP packet.
  • the agent 512 may store the TCP SN in a table that associates the TCP SN with a PDU SN from the lower layer circuitry 514 (operation 554).
  • the agent may adapt the TCP packet to a private-protocol data packet and provide the private-protocol data packet to the lower layer circuitry 514 (operation 556).
  • the lower layer circuitry 514 of the UE 505 may transmit the data packet over a radio network 540 to the lower layer circuitry 522 of the network node 520 (operation 558).
  • the lower layer circuitry 522 of the network node 520 may provide the private-protocol data packet to a proxy 524 (operation 560). To acknowledge that the private-protocol data packet has been successfully received at the network node 520, the lower layer circuitry 522 may transmit an ARQ ACK to the UE 505 (operation 562).
  • the ARQ ACK may be an ARQ ACK from RLC sub-layer circuitry of the lower layer circuitry 522 or an HARQ ACK from MAC sub-layer circuitry of the lower layer circuitry 522.
  • the proxy 524 may adapt the private-protocol data packet to a TCP packet and cache the payload data from the private-protocol data packet (operation 564).
  • the proxy 524 may then cause the TCP packet to be transmitted over the Internet 542 to circuitry 532 of the remote host 530 (operation 566). Based on the TCP packet, circuitry 532 of the remote host 530 may cause a TCP ACK to be transmitted over the Internet 542 to the network node 520 (operation 568). In the event that a TCP ACK is not received for the transmitted TCP packet and/or the TCP ACK indicates an error, the proxy 524 may cause the payload data from the private-protocol data packet to be retransmitted (operation 570).
  • the ARQ ACK for the data packet is received at the lower layer circuitry 514 (e.g., an ARQ ACK at RLC sub-layer circuitry or an HARQ ACK at MAC sub-layer circuitry).
  • the lower layer circuitry 514 may notify the agent 512 that the private-protocol data packet has been indicated as received at the network node 520 based on the ARQ ACK (operation 572).
  • the notification may include a PDU SN associated with the lower layer circuitry 514, and the agent 512 may use the PDU SN to determine a corresponding TCP SN based on the table in which the TCP SN was associated with the PDU SN (operation 574).
  • the agent 512 may then locally generate a TCP ACK that includes the TCP SN determined from the table lookup and provide that TCP ACK to the TCP layer circuitry 510 (operation 576).
  • traffic over the radio network 540 may be reduced, for example, through reduction of transmission of TCP ACK data.
  • FIG. 6 a block diagram illustrates a TCP header 600 that may be implemented in a TCP semantic, in accordance with various embodiments.
  • the TCP header 600 may be locally generated and communicated between circuitry of a computing device, such as the UE 110 and/or the network node 120 of FIG. 1 . Additionally, the TCP header 600 may be transmitted over the Internet between a network node and a remote host, such as the network node 120 and the remote host 150 of FIG. 1 .
  • the TCP header includes a source port field 605 and a destination port field 610.
  • the source port field 605 and the destination port field 610 may be respective communication endpoints at a UE and/or a remote host, depending upon whether the TCP header is to be transmitted in the uplink or downlink direction.
  • the SN field 615 may include the SN of the first data octet in a TCP segment associated with the TCP header 600 (except when a SYN indication is present). If a SYN indication is present in the SN field 615, then the SN may be an initial SN.
  • the ACK field 620 may include the value of a next SN that an endpoint (e.g., a UE or remote host) is expecting for acknowledgment that a TCP packet has been successfully received.
  • the checksum field 625 may include a value computed for error detection.
  • TCP acknowledgment and congestion control mechanisms can be implemented through ARQ mechanisms, and a value from TCP SN field 615 can be mapped to a PDU SN from RLC and/or MAC circuitry.
  • the private protocol described herein may be used instead of TCP.
  • some fields of the TCP header 600 may be eliminated and/or locally implemented so that no changes are required to the TCP circuitry. For example, a value for the checksum field 625 may be locally calculated.
  • a block diagram illustrates a plurality of data packets 700, 720, 740 that may be used to implement a private protocol between a UE and a network node, in accordance with various embodiments.
  • the plurality of data packets 700, 720, 740 may be generated and/or communicated between computing devices, such as between the UE 110 and the network node 120 over the radio network 115 of FIG. 1 .
  • a TCP SYN may be used for TCP connection establishment.
  • the TCP SYN may be implemented in the private protocol using a data packet 700.
  • the private-protocol data packet 700 may include an indication for connection establishment 705 - e.g., a connection establishment indication 705 may be a zero value that is two bytes.
  • the private-protocol data packet 700 may include a source port value 710 and a destination port value 715. An agent and/or a proxy may then apply a hash function to the source port value 710 and the destination port value 715 to generate a hash value for implementation of the private protocol.
  • the agent and/or proxy may include or be communicatively coupled with respective lookup tables that map hash values to source and destination port values.
  • the hash value may consume fewer bytes than the source port value 710 and the destination port value 715 such that a second data packet 720 having payload data consumes fewer resources when transmitted to a network node over a radio network - e.g., a source port value 710 may be two bytes and a destination port value 715 may be two bytes, but a hash value computed from the source port value 710 and the destination port value 715 may itself only require two bytes.
  • the hash value 725 may then be inserted into a data packet according to the private protocol, as shown with the second private-protocol data packet 720.
  • the second private-protocol data packet 720 may include payload data 730.
  • the payload data 730 may be locally extracted from a TCP packet.
  • the second private-protocol data packet 720 may be communicated between a UE and a network node to reduce TCP traffic over a radio network.
  • a private-protocol data packet 740 include the hash value 745 that corresponds to the source port value 710 and destination port value 715. However, this private-protocol data packet 740 may have no payload data, and the absence of payload data may indicate that this private-protocol data packet is to implement a TCP FIN for TCP layer circuitry.
  • a block diagram illustrates a device 800 for wireless reception and transmission of data between computing systems, in accordance with various embodiments.
  • the device 800 may be or may be included in a UE or network node, such as the UE 110 and/or the network node 120 of FIG. 1 .
  • the circuitry of the device may be integrated with and/or communicatively coupled with a communication interface, such as a communication interface 230 of a UE 200 shown in FIG. 2 and/or a communication interface 330 of a network node 300 shown in FIG. 3 .
  • the device 800 may include, but is not limited to, transmitter circuitry 805, receiver circuitry 810, communications circuitry 815, and/or one or more antennas 820 coupled with each at least as shown.
  • the communications circuitry 815 may be coupled with the antennas 820 to facilitate over-the-air communication of signals to/from the device 800.
  • Operations of the communications circuitry 815 may include, but are not limited to, filtering, amplifying, storing, modulating, demodulating, transforming, etc.
  • the transmitter circuitry 805 may be coupled with the communications circuitry 815 and may be configured to provide signals to the communications circuitry 815 for transmission by the antennas 820. In various embodiments, the transmitter circuitry 805 may be configured to provide various signal processing operations on the signal to provide the signal to the communications circuitry 815 with appropriate characteristics. In some embodiments, the transmitter circuitry 805 may be configured to wirelessly transmit one or more data packets.
  • the transmitter circuitry 805 may be configured to receive signals for transmission by the communications circuitry 815. In some embodiments, the transmitter circuitry 805 may be adapted to generate signals. Further, the transmitter circuitry 805 may be adapted to scramble, multiplex, and/or modulate various signals prior to transmission by the communications circuitry 815.
  • the receiver circuitry 810 may be coupled with the communications circuitry 815 and may be configured to receive signals for and/or from the communications circuitry 815, such as signals detected by one or more antennas 820. In some embodiments, the receiver circuitry 810 may be adapted to generate, adapt, or otherwise change signals. Further, the receiver circuitry 810 may be adapted to send received signals to another module or component (not shown), communicatively coupled with the device 800 so that data received from outside a device having the device 800 may utilize that data at the device. In some embodiments, the receiver circuitry 810 may receive one or more data packets.
  • communications circuitry 815, transmitter circuitry 805, and/or receiver circuitry 810 may be included in, for example, a communication chip and/or communicatively coupled with a printed circuit board.
  • FIG. 9 a flow diagram illustrates a method 900 for providing acknowledgment data to TCP layer circuitry based on transmission of a plurality of data packets that encapsulate data from a plurality of TCP packets, in accordance with various embodiments.
  • the method 900 may be performed by a UE, such as the UE 110 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.
  • the method 900 may include operation 905 for generating a plurality of TCP packets intended for transmission to a remote host.
  • TCP layer circuitry may generate the plurality of TCP packets, for example, based on application data received from an application.
  • the TCP layer circuitry may generate the plurality of TCP packets such that a header of a respective TCP packet includes a source port value associated with the application that provides the data from which the TCP packets are generated and a destination port value associated with a remote host (e.g., an end point or application executed at the remote host).
  • Operation 910 may include encapsulating data of the plurality of generated TCP packets into a plurality of data packets according to another protocol, such as a private protocol that may be tunneled in UDP.
  • an agent communicatively coupled with the TCP layer circuitry may intercept the plurality of TCP packets before the TCP packets are processed at lower layer circuitry (e.g., IP layer circuitry and/or link layer circuitry).
  • the agent may extract payload data, encapsulate the payload data in a data packet according to the other protocol, and discard the TCP header from the TCP packet.
  • the agent may identify a source port value and/or a destination port value.
  • the agent may calculate a hash value based on at least one of the source port value and/or the destination port value and include the hash value in a header of the data packet in which the payload data is encapsulated.
  • the agent may encapsulate the data from the TCP packets into the plurality of data packets based at least in part on a compression algorithm, such as an SPDY algorithm to reduce traffic over a wireless radio network.
  • operation 910 may include operations associated with updating a mapping table. From each TCP header, a TCP sequence number may be identified. As a data packet encapsulating payload data from a TCP packet is provided to link layer circuitry (e.g., RLC sub-layer circuitry and/or MAC sub-layer circuitry), a PDU sequence number associated with that data packet may be mapped to the TCP sequence number of the TCP packet that originally included the payload data. For example, the agent may interact with PDCP layer circuitry to obtain a PDU sequence number associated with the data packet at the link layer circuitry, which the agent may then map to the original TCP sequence number. From the link layer circuitry, the plurality of data packets may reach physical layer circuitry, which may transmit the plurality of data packets to a network node over a radio network.
  • link layer circuitry e.g., RLC sub-layer circuitry and/or MAC sub-layer circuitry
  • the method 900 may include determining ARQ data based on transmission of the plurality of data packets to the network node.
  • Link layer circuitry e.g., RLC sub-layer circuitry and/or MAC sub-layer circuitry
  • the plurality of data packets may be transmitted to the network node over the radio network and, based on the transmission of the plurality of data packets, the link layer circuitry may receive ARQ data.
  • the link layer circuitry may receive an acknowledgment message from the network node that indicates the data packet was correctly received at the network node and, if no acknowledgment message is received, then the link layer circuitry may cause the unacknowledged data packet to be retransmitted until the acknowledgment is received or a predefined number of retransmissions is exceeded.
  • the ARQ data may be ARQ data from RLC sub-layer circuitry of the link layer circuitry or HARQ data from the MAC sub-layer circuitry of the link layer circuitry. If the RLC sub-layer circuitry is operating in AM mode, then the RLC sub-layer circuitry may communicate the ARQ data to the agent, for example, directly or through PDCP circuitry. If the RLC sub-layer circuitry is operating in UM mode, then the MAC sub-layer circuitry may communicate HARQ data to the agent.
  • operation 920 may comprise providing, to the TCP layer circuitry, acknowledgment data associated with the plurality of TCP packets based on the ARQ data from the link layer circuitry.
  • the link layer circuitry may communicate, to the agent, ARQ data that indicates whether each data packet of the plurality is received at the network node.
  • the agent may access a lookup table with the PDU sequence number of the data packet to determine a corresponding TCP sequence number.
  • the agent may generate a TCP ACK for that TCP sequence number.
  • a source port value and a destination port value may similarly be determined based on a lookup table and inserted into the TCP ACK.
  • the generated TCP ACK may then be provided to the TCP layer circuitry. If the ARQ data does not indicate that a data packet has been received at the network node (e.g., the link layer circuitry determines that a predefined number of retransmissions for a data packet is exceeded), the TCP layer circuitry may provide a duplicate TCP packet to be retransmitted as described in the aforementioned operations 910-920.
  • a flow diagram illustrates a method 1000 for providing data to TCP layer circuitry based on reception of a plurality of data packets according to another protocol, in accordance with various embodiments.
  • the method 1000 may be performed by a UE, such as the UE 110 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.
  • the method 1000 may include operation 1005 for processing a plurality of data packets received according to a protocol that is not TCP.
  • the data packets may be received over a radio network from a network node and may be, for example, processed according to a private protocol that is tunneled in UDP.
  • link layer circuitry may transmit ARQ data to the network node.
  • Operation 1010 may comprise adapting the plurality of data packets to a plurality of TCP packets.
  • an agent may encapsulate payload data from a respective data packet into a TCP packet.
  • the agent may identify at least one hash value from a header of the data packet.
  • the agent may determine at least one port value (e.g., a destination port value and/or a source port value) based on the hash value - e.g., the agent may access a lookup table and determine the source port value and the destination port value based on the identified hash value.
  • the agent may then insert the at least one port value into a header of the TCP packet.
  • operation 1015 may include providing the plurality of TCP packets to TCP layer circuitry.
  • this operation 1015 may be performed by the agent.
  • the TCP layer circuitry may communicate the payload data from the generated TCP packets based on the port values included in the TCP headers of the TCP packets - e.g., the TCP layer circuitry may communicate payload data to an application.
  • a flow diagram illustrates a method 1100 for providing data, received according to a private protocol, to a remote host according to TCP, in accordance with various embodiments.
  • the method 1100 may be performed by a network node, such as the network node 120 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 processing a plurality of data packets associated with a private protocol and having data for a remote host.
  • the plurality of data packets may be received from a UE and processed at link layer circuitry (e.g., RLC sub-layer circuitry and/or MAC sub-layer circuitry).
  • link layer circuitry e.g., RLC sub-layer circuitry and/or MAC sub-layer circuitry
  • operation 1110 may include transmitting ARQ data to the UE.
  • the link layer circuitry may transmit ARQ data that acknowledges that the data packet has been received.
  • RLC sub-layer circuitry may cause an ARQ acknowledgment message to be transmitted for each data packet
  • MAC sub-layer circuitry may cause an HARQ acknowledgment message to be transmitted for each data packet.
  • the method 1100 may include adapting the plurality of data packets to a plurality of TCP packets.
  • the link layer circuitry may cause the plurality of data packets to be provided to a proxy that is to perform the adaptation.
  • the proxy may be adapted to process data packets according to the private protocol, which may be tunneled in UDP.
  • the proxy may communicate with TCP layer circuitry to adapt the plurality of data packets to the plurality of TCP packets.
  • operation 1115 may include operations associated with encapsulating payload data from a respective data packet into a TCP packet.
  • the proxy may identify at least one hash value from a header of the data packet.
  • the proxy may determine at least one port value (e.g., a destination port value and/or a source port value) based on the hash value - e.g., the proxy may access a lookup table and determine the source port value and the destination port value based on the identified hash value.
  • the at least one port value may be inserted into a header of the TCP packet.
  • the proxy may adapt the plurality of data packets into the plurality of TCP packets.
  • the proxy may cause the plurality of data packets to be adapted to the plurality of TCP packets by providing the payload data and the at least one port value to the TCP layer circuitry, which may then perform packetization.
  • the payload data may be adapted from the data packets into the plurality of TCP packets based at least in part on restoration of the payload data based on a compression algorithm, such as an SPDY algorithm.
  • the method 1100 may include an operation 1120 for transmitting the plurality of TCP packets to the remote host.
  • the TCP semantic may be maintained between the UE and the remote host while reducing TCP traffic across a radio network over which the UE and the network node are to communicate.
  • the TCP packets may be transmitted to the remote host over the Internet by TCP layer circuitry communicatively coupled with IP layer circuitry.
  • the payload data from the plurality of data packets may be cached, either before or after TCP packetization, so that if a TCP ACK is not received from the remote host for a TCP packet, then that TCP packet may be retransmitted without requiring retransmission from the UE.
  • a flow diagram illustrates a method 1200 for transmitting, to a UE, a plurality of data packets adapted from TCP to another protocol, in accordance with various embodiments.
  • the method 1200 may be performed by a network node, such as the network node 120 of FIG. 1 . While FIG. 12 illustrates a plurality of sequential operations, one of ordinary skill would understand that one or more operations of the method 1200 may be transposed and/or performed contemporaneously.
  • the method 1200 may begin with an operation 1205 for processing a plurality of TCP packets received from a remote host.
  • the TCP packets may be received over the Internet at TCP circuitry.
  • the TCP packets may be intended for an endpoint (e.g., an application) executed by a UE that operates on a cell, such as a cell provided by the network node or a cell provided by an access node communicatively coupled with the network node.
  • Operation 1210 may comprise adapting the plurality of TCP packets to a plurality of data packets according to another protocol.
  • a proxy may encapsulate payload data from a respective TCP packet into a data packet.
  • the proxy may identify at least one port value (e.g., a destination port value and/or a source port value) from the header of the TCP packet.
  • At least one hash value may be determined from the at least one port value.
  • the at least one hash value may be determined, for example, by applying a predetermined hash function to the at least one port value (e.g., a destination port value and/or a source port value) or by accessing a lookup table with the at least one port value to determine the hash value.
  • the determined hash value may then be inserted into a header of a data packet, with the payload data of the TCP packet inserted into the payload of the data packet.
  • operation 1215 may include transmitting the plurality of data packets to the UE.
  • the proxy may provide the plurality of data packets to lower layer circuitry (e.g., link layer circuitry and physical layer circuitry) for transmission over a radio network to the UE.
  • the TCP layer circuitry may communicate the payload data from the generated TCP packets based on the port values included in the TCP headers of the TCP packets - e.g., the TCP layer circuitry may communicate payload data to an application.
  • example 1 may be an apparatus to be included in a user equipment (“UE"), the apparatus comprising: TCP layer circuitry to generate a plurality of TCP packets intended for transmission to a remote host; an agent, coupled with the TCP layer circuitry, to intercept the plurality of TCP packets, to encapsulate data from the plurality of TCP packets into a plurality of data packets according to another protocol, and to provide acknowledgment data to the TCP layer circuitry based on Automatic Repeat Request (“ARQ”) data that is based on transmission of the plurality of data packets; and link layer circuitry, coupled with the agent, to determine the ARQ data based on the transmission of the plurality of data packets over a network.
  • UE user equipment
  • Example 2 may be apparatus of example 1, wherein the plurality of data packets are to be included in a plurality of Uniform Datagram Protocol ("UDP") datagrams.
  • Example 3 may be the apparatus of example 1, further comprising: physical layer circuitry, coupled with the link layer circuitry, to transmit the data packets over the network to a network node.
  • Example 4 may be the apparatus of example 1, wherein the link layer circuitry comprises: RLC sub-layer circuitry; and MAC sub-layer circuitry.
  • Example 5 may be the apparatus of example 4, wherein the agent is further to map a respective TCP sequence number associated with a respective TCP packet of the plurality of TCP packets to a protocol data unit ("PDU") sequence number associated with the RLC sub-layer circuitry or the MAC sub-layer circuitry, and further wherein the agent is to provide acknowledgment data for the respective TCP packet based on ARQ data associated with the PDU sequence number mapped to the respective TCP sequence number.
  • PDU protocol data unit
  • Example 6 may be the apparatus of example 4, wherein the agent is to provide acknowledgment data to the TCP layer circuitry based on ARQ data by generation, at the UE, of a TCP acknowledgment ("ACK") corresponding to at least one TCP packet of the plurality of TCP packets based on ARQ data, associated with transmission of a data packet, received from the RLC sub-layer circuitry or hybrid ARQ ("HARQ") data received from the MAC sub-layer.
  • Example 7 may be the apparatus of any of examples 1-6, wherein the TCP layer circuitry is to: receive application data from an application for the transmission to the remote host; and generate the plurality of TCP packets based on the application data.
  • Example 8 may be the apparatus of example 7, wherein a respective TCP packet of the plurality of TCP packets is to include a source port value and a destination port value, and further wherein the agent is to calculate a hash value based on the source port value and the destination port value to identify the application at the UE and include the hash value in a header of a respective data packet of the plurality of data packets.
  • Example 9 may be the apparatus of any of examples 1-6, wherein the agent is to encapsulate the data from the plurality of TCP packets into the plurality of data packets according to the other protocol based at least in part on a compression algorithm.
  • Example 10 may be the apparatus of any of examples 1-6, wherein the agent is to process a second plurality of data packets that are received according to the other protocol, to adapt the second plurality of processed data packets to a second plurality of TCP packets, and to provide the second plurality of TCP packets to the TCP layer circuitry.
  • example 11 may be an apparatus to be included in a network node, the apparatus comprising: a proxy to process a plurality of received data packets having data for a remote host according to a private protocol and to adapt, or cause to be adapted, the plurality of data packets to a plurality of Transmission Control Protocol (“TCP”) packets; link layer circuitry, coupled to the proxy, to provide Automatic Repeat Request (“ARQ") data to a user equipment (“UE”) based on the reception of the plurality of data packets; and TCP layer circuitry, coupled with the proxy, to provide the plurality of TCP packets to the remote host.
  • TCP Transmission Control Protocol
  • ARQ Automatic Repeat Request
  • UE user equipment
  • Example 12 may be the apparatus of example 11, wherein the private protocol is tunneled in a user datagram protocol (“UDP”) and the plurality of received data packets is included in a plurality of UDP datagrams.
  • Example 13 may be the apparatus of example 11, wherein the link layer circuitry comprises: a Radio Link Control (“RLC”) sub-layer circuitry; and a Media Access Control (“MAC”) sub-layer circuitry.
  • RLC Radio Link Control
  • MAC Media Access Control
  • Example 14 may be the apparatus of example 11, wherein the proxy is to adapt a respective data packet to a respective TCP packet based on extraction of a hash value in a header of the respective data packet, identification of a source port value and a destination port value based on the extracted hash value, and insertion of the source port value and the destination port value into a header of the respective TCP packet.
  • Example 15 may be the apparatus of example 14, wherein the proxy is further to cause a mapping table to be transmitted to another network node based on a handover of the UE to the other network node, the mapping table to map the hash value to the source port value and the destination port value.
  • Example 16 may be the apparatus of any of examples 11-15, wherein the proxy is to cache data associated with the plurality of TCP packets, to process acknowledgment data associated with the plurality of TCP packets from the remote host, and to cause retransmission of a respective TCP packet if acknowledgment data corresponding to the respective TCP packet is not processed.
  • Example 17 may the apparatus of any of examples 11-15, wherein the proxy is to adapt the plurality of data packets to the plurality of TCP packets based on restoration of data included in the plurality of data packets according to a compression algorithm.
  • Example 18 may be the apparatus of any of examples 11-15, wherein the proxy is to process a plurality of TCP packets, received from the remote host, to adapt the plurality of received TCP packets to a second plurality of data packets according to the private protocol, and to provide the second plurality of data packets to physical layer circuitry for transmission to the UE, and the apparatus further comprising: the physical layer circuitry, coupled with the link layer circuitry, to transmit the second plurality of data packets to the UE.
  • Example 19 may be the apparatus of example 18, wherein the proxy is adapt a respective TCP packet of the plurality of received TCP packets to a respective data packet of the second plurality of data packets by extraction of a source port value and a destination port value from a header of the TCP packet, calculation of a hash value based on the source port value and the destination port value, and insertion of the calculated hash value into a header of the respective data packet.
  • Example 20 may be the apparatus of any of examples 11-15, wherein the network node is an access node adapted to provide a cell on which the UE is to operate, a serving gateway, or a packet data network gateway.
  • example 21 may be one or more non-transitory computer system-readable media comprising computing device-executable instructions, wherein the instructions, in response to execution by a computing device, cause the computing device to: generate a plurality of Transmission Control Protocol (“TCP”) packets intended for transmission to a remote host; encapsulate, by an agent, data associated with the plurality of TCP packets into a plurality of data packets according to a private protocol; determine Automatic Repeat Request (“ARQ”) data based on transmission of the plurality of data packets over a network; and generate acknowledgment data associated with the plurality of TCP packets based on the ARQ data determined by the link layer circuitry.
  • TCP Transmission Control Protocol
  • ARQ Automatic Repeat Request
  • Example 22 may be the one or more non-transitory computer system-readable media of example 21, wherein the private protocol is tunneled in a user datagram protocol (“UDP").
  • Example 23 may be the one or more non-transitory computer system-readable media of any of examples 21-22, wherein the instructions further cause the computing device to map a respective TCP sequence number associated with a respective TCP packet of the plurality of TCP packets to a protocol data unit ("PDU”) sequence number associated with a Radio Link Control (“RLC”) layer or Media Access Control (“MAC”) layer.
  • PDU protocol data unit
  • RLC Radio Link Control
  • MAC Media Access Control
  • example 24 may be one or more non-transitory computer system-readable media comprising computing device-executable instructions, wherein the instructions, in response to execution by a computing device, cause the computing device to: process a plurality of data packets received from a user equipment (“UE"), the plurality of received data packets to be associated with a private protocol and to have data for a remote host; transmit Automatic Repeat Request (“ARQ") data to a user equipment (“UE") based on the reception of the plurality of data packets; adapt, by a proxy, the plurality of data packets to a plurality of Transmission Control Protocol (“TCP”) packets; and transmit the plurality of TCP packets to the remote host.
  • UE user equipment
  • ARQ Automatic Repeat Request
  • TCP Transmission Control Protocol
  • Example 25 may be the one or more non-transitory computer system-readable media comprising computing device-executable instructions of example 24, wherein the adaptation, by the proxy, of the plurality of data packets to the plurality of TCP packets comprises instructions to: restore data from the plurality of received data packets according to a compression algorithm; extract a respective hash value from a respective header of a respective received data packet; identify a respective source port value and a respective destination port value based on the extracted hash value; and insert the restored data, the respective source port value, and the respective destination port value into a respective header of a respective TCP packet of the plurality of TCP packets.
  • example 26 may be a method to be performed by a user equipment (“UE"), the method comprising: generating a plurality of Transmission Control Protocol (“TCP”) packets intended for transmission to a remote host; encapsulating data from the plurality of TCP packets into a plurality of data packets according to another protocol; transmitting the plurality of data packets over a network; receiving Automatic Repeat Request (“ARQ”) data based on the transmitting of the plurality of data packets; and locally generating TCP acknowledgement data based on the receiving of the ARQ data.
  • Example 27 may be the method of example 26, wherein the plurality of data packets is to be included in a plurality of Uniform Datagram Protocol (“UDP”) datagrams.
  • UDP Uniform Datagram Protocol
  • Example 28 may be the method of example 26, further comprising: mapping a respective TCP sequence number associated with a respective TCP packet of the plurality of TCP packets to a protocol data unit ("PDU") sequence number associated with an RLC layer or an MAC layer.
  • Example 29 may be the method of example 28, wherein the ARQ data comprises ARQ acknowledgment data associated with the RLC layer or hybrid ARQ ("HARQ") acknowledgment data associated with the MAC layer.
  • Example 30 may be the method of any of examples 26-29, wherein plurality of TCP packets are generated based on application data from an application associated with the UE.
  • Example 31 may be the method of any of examples 26-29, further comprising: calculating a hash value based on a source port value and a destination port value included in a header of a first TCP packet of the plurality of TCP packets; and including the hash value in a header of a first data packet of the plurality of data packets.
  • Example 32 the method of any of examples 26-29, wherein the data from the plurality of TCP packets is to be encapsulated into the plurality of data packets according to the other protocol based at least in part on a compression algorithm.
  • Example 33 may be the method of any of examples 26-29, further comprising: receiving a second plurality of data packets according to the other protocol; and adapting the second plurality of processed data packets to a second plurality of TCP packets.
  • example 34 may be a method to be performed in a network node, the method comprising: receiving a plurality data packets having data for a remote host according to a private protocol; adapting, or causing to be adapted, the plurality of data packets to a plurality of Transmission Control Protocol (“TCP") packets; transmitting Automatic Repeat Request (“ARQ") data to a user equipment (“UE") based on the receiving of the plurality of data packets; and transmitting the plurality of TCP packets to the remote host.
  • TCP Transmission Control Protocol
  • ARQ Automatic Repeat Request
  • Example 35 may be the method of example 34, wherein the private protocol is tunneled in a user datagram protocol (“UDP") and the plurality of received data packets is included in a plurality of UDP datagrams.
  • UDP user datagram protocol
  • Example 36 may be the method of example 34, wherein the adapting, or causing to be adapted, of the plurality of data packets to the plurality of TCP packets comprises: extracting, from a respective data packet, a hash value; identifying a source port value and a destination port value based on the extracted hash value; and inserting the source port value and the destination port value into a header of the respective TCP packet.
  • Example 37 may be the method of example 36, further comprising: transmitting a mapping table to another network node based on a handover of the UE to the other network node, the mapping table to map the hash value to the source port value and the destination port value.
  • Example 38 may be the method of any of examples 34-37, further comprising: caching data associated with the plurality of TCP packets; and retransmitting a respective TCP packet of the plurality of TCP packets to the remote host if acknowledgment data corresponding to the respective TCP packet is not received.
  • Example 39 may be the method of any of examples 34-37, further comprising: processing a plurality of TCP packets received from the remote host; adapting the plurality of received TCP packets to a second plurality of data packets according to the private protocol; and transmitting the second plurality of data packets to the UE.
  • Example 40 may be the method of example 39, the method further comprising: extracting a source port value and a destination port value from a header of a respective TCP packet of the plurality of TCP packets received from the remote host; calculating a hash value based on the source port value and the destination port value; and inserting the calculated hash value into a header of a respective data packet of the second plurality of data packets.
  • Embodiments of the invention also relate to an apparatus for performing the operations herein.
  • 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).
  • 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).
  • 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.
  • processing logic comprises hardware (e.g., circuitry, dedicated logic, etc.), software (e.g., embodied on a non-transitory computer-readable medium), or a combination of both.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Computer Security & Cryptography (AREA)
  • Quality & Reliability (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Communication Control (AREA)
  • Digital Transmission Methods That Use Modulated Carrier Waves (AREA)

Claims (15)

  1. Vorrichtung, die in eine Benutzerausrüstung (405, 505) aufgenommen werden soll, wobei die Vorrichtung aufweist:
    TCP-Schicht-Schalttechnik (412, 510), die konfiguriert ist, um eine Vielzahl von TCP-Paketen (414, 552) zu erzeugen, die zur Übertragung zu einem entfernten Host (470, 530) vorgesehen sind;
    ein Agent (416, 412), der mit der TCP-Schicht-Schalttechnik (412, 510) gekoppelt ist und konfiguriert ist, um die Vielzahl von TCP-Paketen (414, 552) abzufangen, konfiguriert ist, um Nutzlastdaten von der Vielzahl von TCP-Paketen (414, 552) in eine Vielzahl von Datenpaketen (418, 556) gemäß einem anderen Protokoll (484) einzukapseln, und konfiguriert ist, um Bestätigungsdaten an die TCP-Schicht-Schalttechnik (412, 510) bereitzustellen, basierend auf ARQ-Daten, die auf der Übertragung der Vielzahl von Datenpaketen (418, 556) basiert; und
    Verbindungsschicht-Schalttechnik (454, 456, 514), die mit dem Agenten (416, 412) gekoppelt ist und konfiguriert ist, um die ARQ-Daten zu bestimmen basierend auf der Übertragung der Vielzahl von Datenpaketen (418, 556) über ein Netzwerk.
  2. Vorrichtung gemäß Anspruch 1, wobei die Vielzahl von Datenpaketen (418, 556) in eine Vielzahl von UDP-Datagrammen aufgenommen werden sollen.
  3. Vorrichtung gemäß Anspruch 1, die weiter aufweist:
    Physikalische-Schicht-Schalttechnik (428), die mit der Verbindungsschicht-Schalttechnik (454,456, 514) gekoppelt ist, um die Datenpakete (418, 556) über das Netzwerk zu einem Netzwerkknoten (440, 520) zu übertragen,
    wobei die Verbindungsschicht-Schalttechnik (514) RLC- Unterschicht-Schalttechnik (424) aufweist; und MAC-Unterschicht-Schalttechnik (426).
  4. Vorrichtung gemäß Anspruch 3, wobei der Agent (416, 412) weiter konfiguriert ist, um eine jeweilige TCP-Sequenznummer zu mappen, die mit einem jeweiligen TCP-Paket der Vielzahl von TCP-Paketen (414, 552) verknüpft ist, auf eine PDU-Sequenznummer, die mit der RLC-Unterschicht-Schalttechnik oder der MAC-Unterschicht-Schalttechnik verknüpft ist, und weiter wobei der Agent (416, 412) konfiguriert ist, um Bestätigungsdaten für das jeweilige TCP-Paket basierend auf ARQ-Daten bereitzustellen, die mit der PDU- Sequenznummer verknüpft sind, die auf die jeweilige TCP-Sequenznummer gemappt ist.
  5. Vorrichtung gemäß Anspruch 3, wobei der Agent (416, 412) konfiguriert ist, um Bestätigungsdaten an die TCP-Schicht-Schalttechnik (412, 510) bereitzustellen basierend auf ARQ-Daten durch Erzeugung an der Benutzerausrüstung (405, 505) einer TCP-Bestätigung entsprechend zumindest einem TCP-Paket der Vielzahl von TCP-Paketen (414, 552) basierend auf ARQ-Daten, die mit der Übertragung eines Datenpaketes verknüpft sind, empfangen von der RLC-Unterschicht-Schalttechnik oder HARQ-Daten, die von der MAC-Unterschicht empfangen worden sind.
  6. Vorrichtung gemäß einem der Ansprüche 1 bis 5, wobei die TCP-Schicht-Schalttechnik (412, 510) konfiguriert ist, um:
    Anwendungsdaten von einer Anwendung (410) für die Übertragung zu dem entfernten Host (470, 530) zu empfangen; und
    die Vielzahl von TCP-Paketen (414, 552) basierend auf den Anwendungsdaten zu erzeugen;
    wobei ein jeweiliges TCP-Paket der Vielzahl von TCP-Paketen (414, 552) konfiguriert ist, um einen Quellport-Wert und einen Zielport-Wert zu umfassen, und weiter wobei der Agent (416, 412) konfiguriert ist, um einen Hash-Wert basierend auf dem Quellport-Wert und dem Zielport-Wert zu berechnen, um die Anwendung an der Benutzerausrüstung (405, 505) zu identifizieren und den Wert in einem Header des jeweiligen Datenpakets der Vielzahl von Datenpaketen (414, 552) einzubinden.
  7. Vorrichtung gemäß einem der Ansprüche 1 bis 5, wobei der Agent (416, 412) konfiguriert ist, um die Daten von der Vielzahl von TCP-Paketen (414, 552) in die Vielzahl von Datenpaketen (418, 556) gemäß dem anderen Protokoll basierend zumindest teilweise auf einem Kompressionsalgorithmus einzukapseln.
  8. Vorrichtung gemäß einem der Ansprüche 1 bis 5, wobei der Agent (416, 412) konfiguriert ist, um eine zweite Vielzahl von Datenpaketen (418, 556) zu verarbeiten, die gemäß dem anderen Protokoll empfangen worden sind, um die zweite Vielzahl von verarbeiteten Datenpaketen (418, 556) an eine zweite Vielzahl von TCP-Paketen (414, 552) anzupassen und die zweite Vielzahl von TCP-Paketen (414. 552) an die TCP-Schicht-Schalttechnik (412, 510) bereit zu stellen.
  9. Vorrichtung, die in einen Netzwerkknoten (440, 520) eingebunden werden soll, wobei die Vorrichtung aufweist:
    einen Proxy (446, 524), der konfiguriert ist, um eine Vielzahl von Datenpaketen (448,560) zu verarbeiten, die von einer Benutzerausrüstung (405, 505) empfangen worden sind, wobei die Datenpakete (448, 560) Daten für einen entfernten Host (470, 530) gemäß einem privaten Protokoll (484) haben, wobei der Proxy (446, 524) weiter konfiguriert ist, um die Vielzahl von Datenpaketen (448, 560) an eine Vielzahl von TCP-Paketen (566) anzupassen oder zu veranlassen, dass sie angepasst werden;
    Verbindungsschicht-Schalttechnik (522), die mit dem Proxy gekoppelt ist, um ARQ-Daten an die Benutzerausrüstung (405, 505) bereitzustellen basierend auf dem Empfang der Vielzahl von Datenpaketen (448, 560); und
    TCP-Schicht-Schalttechnik, die mit dem Proxy gekoppelt ist, um die Vielzahl von TCP-Paketen (566) an den entfernten Host (470, 530) bereitzustellen.
  10. Vorrichtung gemäß Anspruch 10, wobei das private Protokoll (484) in ein UDP-Protokoll getunnelt ist und die Vielzahl von empfangenen Datenpaketen (448, 560) in einer Vielzahl von UDP-Datagrammen umfasst ist.
  11. Vorrichtung gemäß Anspruch 9, wobei die Verbindungsschicht-Schalttechnik (335, 522) umfasst:
    eine RLC Unterschicht-Schalttechnik (336, 454); und
    eine MAC-Unterschicht-Schalttechnik (337, 456).
  12. Vorrichtung gemäß Anspruch 9, wobei der Proxy (446, 524) konfiguriert ist, um ein jeweiliges Datenpaket an ein jeweiliges TCP-Paket anzupassen basierend auf der Extraktion eines Wertes in einem Header des jeweiligen Datenpaketes, der Identifikation eines Quellport-Wertes und eines Zielport-Wertes basierend auf dem extrahierten Hash-Wert, und dem Einfügen des Quellport-Wertes und des Zielport-Wertes in einen Header des jeweiligen TCP-Pakets.
  13. Vorrichtung gemäß Anspruch 12, wobei der Proxy (446, 524) weiter konfiguriert ist, um zu veranlassen, dass eine Map-Tafel zu einem anderen Netzwerkknoten (440, 520) übertragen wird basierend auf einer Übergabe der Benutzerausrüstung (405, 505) an den anderen Netzwerkknoten (440, 520) wobei die Map-Tafel den Hash-Wert mit dem Quellport-Wert und dem Zielport-Wert mappen soll.
  14. Vorrichtung gemäß einem der Ansprüche 9 bis 13 wobei der Proxy (446, 524) konfiguriert ist, um Daten, die mit der Vielzahl von TCP-Paketen (566) verknüpft sind, zu cachespeichern, um Bestätigungsdaten, die mit der Vielzahl von TCP-Paketen (566) von dem entfernten Host (470, 530) verknüpft sind, zu verarbeiten und um eine neue Übertragung eines jeweiligen TCP-Paketes zu veranlassen, wenn Bestätigungsdaten entsprechend dem jeweiligen TCP-Paket nicht verarbeitet sind.
  15. Vorrichtung gemäß einem der Ansprüche 9 bis 14, wobei der Proxy (446, 524) angepasst ist, um die Vielzahl von Datenpaketen (448, 560) an die Vielzahl von TCP-Paketen (566) basierend auf einer Restaurierung von Daten anzupassen, die in der Vielzahl von Datenpaketen (448, 560) umfasst sind, gemäß einem Kompressionsalgorithmus.
EP14866534.2A 2013-11-27 2014-11-06 Tcp-verkehrsanpassung in drahtlosen systemen Active EP3075138B1 (de)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US201361909938P 2013-11-27 2013-11-27
US14/314,397 US9661657B2 (en) 2013-11-27 2014-06-25 TCP traffic adaptation in wireless systems
PCT/US2014/064422 WO2015080850A1 (en) 2013-11-27 2014-11-06 Tcp traffic adaptation in wireless systems

Publications (3)

Publication Number Publication Date
EP3075138A1 EP3075138A1 (de) 2016-10-05
EP3075138A4 EP3075138A4 (de) 2017-07-05
EP3075138B1 true EP3075138B1 (de) 2020-08-12

Family

ID=53182599

Family Applications (8)

Application Number Title Priority Date Filing Date
EP14866388.3A Active EP3075189B1 (de) 2013-11-27 2014-09-26 Virtuelle wifi-trägerabtastung für lte/wifi-cokanalkoordination
EP14865094.8A Active EP3075116B1 (de) 2013-11-27 2014-10-22 Systeme, verfahren und vorrichtungen zur steuerung des transports ratenlos codierter meldungen
EP14866769.4A Withdrawn EP3075124A4 (de) 2013-11-27 2014-11-06 Signalentwürfe für d2d-teilrahmen
EP14866534.2A Active EP3075138B1 (de) 2013-11-27 2014-11-06 Tcp-verkehrsanpassung in drahtlosen systemen
EP20217432.2A Pending EP3836473A1 (de) 2013-11-27 2014-11-06 Signalentwürfe für d2d-teilrahmen
EP14866014.5A Withdrawn EP3075188A4 (de) 2013-11-27 2014-11-11 Funkverbindungsüberwachung
EP14865220.9A Active EP3078237B1 (de) 2013-11-27 2014-11-28 Techniken zur koordination der funkressourcenkontrollstatusverwaltung bei architekturen mit dualer konnektivität
EP14865415.5A Withdrawn EP3075186A4 (de) 2013-11-27 2014-11-28 Koordinationsverfahren für diskontinuierlichen empfang (drx) bei dualkonnektivitätsarchitekturen

Family Applications Before (3)

Application Number Title Priority Date Filing Date
EP14866388.3A Active EP3075189B1 (de) 2013-11-27 2014-09-26 Virtuelle wifi-trägerabtastung für lte/wifi-cokanalkoordination
EP14865094.8A Active EP3075116B1 (de) 2013-11-27 2014-10-22 Systeme, verfahren und vorrichtungen zur steuerung des transports ratenlos codierter meldungen
EP14866769.4A Withdrawn EP3075124A4 (de) 2013-11-27 2014-11-06 Signalentwürfe für d2d-teilrahmen

Family Applications After (4)

Application Number Title Priority Date Filing Date
EP20217432.2A Pending EP3836473A1 (de) 2013-11-27 2014-11-06 Signalentwürfe für d2d-teilrahmen
EP14866014.5A Withdrawn EP3075188A4 (de) 2013-11-27 2014-11-11 Funkverbindungsüberwachung
EP14865220.9A Active EP3078237B1 (de) 2013-11-27 2014-11-28 Techniken zur koordination der funkressourcenkontrollstatusverwaltung bei architekturen mit dualer konnektivität
EP14865415.5A Withdrawn EP3075186A4 (de) 2013-11-27 2014-11-28 Koordinationsverfahren für diskontinuierlichen empfang (drx) bei dualkonnektivitätsarchitekturen

Country Status (12)

Country Link
US (12) US9661657B2 (de)
EP (8) EP3075189B1 (de)
JP (2) JP2016540436A (de)
KR (3) KR20160065139A (de)
CN (8) CN105659660B (de)
AU (2) AU2014355101A1 (de)
BR (2) BR112016009418B1 (de)
ES (1) ES2693393T3 (de)
HK (5) HK1224488A1 (de)
MX (1) MX363211B (de)
RU (4) RU2633392C1 (de)
WO (7) WO2015080796A1 (de)

Families Citing this family (151)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP6174714B2 (ja) * 2013-01-16 2017-08-02 エルジー エレクトロニクス インコーポレイティド 端末間通信実行方法及びそのための装置
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
US9762306B2 (en) * 2013-08-08 2017-09-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
JP6183148B2 (ja) * 2013-10-24 2017-08-23 富士通株式会社 通信端末装置、通信制御システムおよび通信制御方法
US20150117295A1 (en) * 2013-10-30 2015-04-30 Electronics And Telecommunications Research Institute Method and apparatus for device-to-device communication
US9661657B2 (en) * 2013-11-27 2017-05-23 Intel Corporation TCP traffic adaptation in wireless systems
PL3078126T3 (pl) 2013-12-04 2017-12-29 Telefonaktiebolaget Lm Ericsson (Publ) Skracanie długości podramki łącza zstępującego w systemach transmisji dwukierunkowej z podziałem czasu (TDD)
DK3557784T3 (da) * 2013-12-04 2020-10-26 Ericsson Telefon Ab L M Uplink-underammeforkortelse i tidsdelt duplex (TDD)-systemer
US9338136B2 (en) 2013-12-05 2016-05-10 Alcatel Lucent Security key generation for simultaneous multiple cell connections for mobile device
US10206147B2 (en) * 2013-12-19 2019-02-12 Qualcomm Incorporated Serving gateway relocation and secondary node eligibility for dual connectivity
JPWO2015107942A1 (ja) * 2014-01-14 2017-03-23 シャープ株式会社 基地局装置および端末装置
US20150207603A1 (en) * 2014-01-23 2015-07-23 Humax Holdings Co., Ltd. Apparatus for transmission on lte device to device communication
US10306695B2 (en) 2014-01-31 2019-05-28 Qualcomm Incorporated Procedures for managing secondary eNB (SeNB) radio link failure (S-RLF) in dual connectivity scenarios
US9491269B2 (en) * 2014-04-11 2016-11-08 Apple Inc. Uplink transmission rate in a wireless communication device
US9794821B2 (en) 2014-04-28 2017-10-17 Intel IP Corporation Channel reservation for operation in an unlicensed spectrum
US10462704B2 (en) * 2014-04-30 2019-10-29 Nokia Solutions And Networks Oy Method, apparatus and system
US10123318B2 (en) * 2014-05-07 2018-11-06 Kyocera Corporation Communication control method, base station, and user terminal
KR102220934B1 (ko) 2014-05-07 2021-02-26 삼성전자 주식회사 무선 통신 시스템에서 비연속적 수신을 제어하기 위한 방법, 사용자 장치 및 기지국
US10548071B2 (en) 2014-05-16 2020-01-28 Huawei Technologies Co., Ltd. System and method for communicating traffic over licensed or un-licensed spectrums based on quality of service (QoS) constraints of the traffic
US10873941B2 (en) * 2014-05-16 2020-12-22 Huawei Technologies Co., Ltd. System and method for joint transmission over licensed and unlicensed bands using fountain codes
US10536386B2 (en) 2014-05-16 2020-01-14 Huawei Technologies Co., Ltd. System and method for dynamic resource allocation over licensed and unlicensed spectrums
US10813043B2 (en) 2014-05-16 2020-10-20 Huawei Technologies Co., Ltd. System and method for communicating wireless transmissions spanning both licensed and un-licensed spectrum
US10701729B2 (en) * 2014-06-03 2020-06-30 Qualcomm Incorporated Protected CET transmission and reception
US9680678B2 (en) 2014-06-23 2017-06-13 Intel IP Corporation Communication systems and methods
US20170127473A1 (en) * 2014-06-24 2017-05-04 Nokia Technologies Oy Dual connectivity management
WO2016003332A1 (en) * 2014-07-01 2016-01-07 Telefonaktiebolaget L M Ericsson (Publ) Methods and nodes for congestion control
US9455750B2 (en) * 2014-07-28 2016-09-27 Qualcomm Incorporated Source block size selection
US10165553B2 (en) * 2014-07-29 2018-12-25 Htc Corporation Device and method of handling communication operations in a licensed frequency band and an unlicensed frequency band
WO2016018383A1 (en) 2014-07-31 2016-02-04 Hewlett-Packard Development Company Live migration of data
US10540109B2 (en) 2014-09-02 2020-01-21 Hewlett Packard Enterprise Development Lp Serializing access to fault tolerant memory
JP6619742B2 (ja) * 2014-09-26 2019-12-11 京セラ株式会社 基地局及びユーザ端末
US10945134B2 (en) * 2014-09-29 2021-03-09 Nec Corporation Method and devices for signaling transmission in unlicensed band
WO2016064397A1 (en) 2014-10-23 2016-04-28 Hewlett Packard Enterprise Development Lp Admissions control of a device
US10594442B2 (en) 2014-10-24 2020-03-17 Hewlett Packard Enterprise Development Lp End-to-end negative acknowledgment
US10699031B2 (en) 2014-10-30 2020-06-30 Hewlett Packard Enterprise Development Lp Secure transactions in a memory fabric
US10715332B2 (en) 2014-10-30 2020-07-14 Hewlett Packard Enterprise Development Lp Encryption for transactions in a memory fabric
CN105634699B (zh) * 2014-11-07 2020-08-11 中兴通讯股份有限公司 载波选择方法及装置、接入点
CN107078984B (zh) * 2014-11-14 2019-12-06 华为技术有限公司 无线局域网中的用于自动增益控制的方法和通信设备
US9667303B2 (en) * 2015-01-28 2017-05-30 Lam Research Corporation Dual push between a host computer system and an RF generator
US9974049B2 (en) * 2015-01-29 2018-05-15 Intel IP Corporation Adaptive paging techniques for extended coverage-capable devices
US10110363B2 (en) * 2015-01-29 2018-10-23 Qualcomm Incorporated Low latency in time division duplexing
US9986586B2 (en) 2015-01-29 2018-05-29 Intel IP Corporation Reservation of unlicensed spectrum in a wireless communications network
US9992775B2 (en) * 2015-01-30 2018-06-05 Qualcomm Incorporated Band preference in wireless networks
WO2016122642A1 (en) 2015-01-30 2016-08-04 Hewlett Packard Enterprise Development Lp Determine failed components in fault-tolerant memory
US10402287B2 (en) 2015-01-30 2019-09-03 Hewlett Packard Enterprise Development Lp Preventing data corruption and single point of failure in a fault-tolerant memory
CN107210826B (zh) * 2015-01-30 2021-06-29 Lg 电子株式会社 无线通信系统中的无线电链路监测方法及其设备
WO2016122637A1 (en) 2015-01-30 2016-08-04 Hewlett Packard Enterprise Development Lp Non-idempotent primitives in fault-tolerant memory
GB2534865A (en) * 2015-01-30 2016-08-10 Nec Corp Communication system
US20180026736A1 (en) * 2015-02-20 2018-01-25 Nec Corporation Wireless communication system, base station device, mobile station device, and wireless communication control method
US10402261B2 (en) 2015-03-31 2019-09-03 Hewlett Packard Enterprise Development Lp Preventing data corruption and single point of failure in fault-tolerant memory fabrics
US10129873B2 (en) * 2015-04-08 2018-11-13 Qualcomm Incorporated Non-contiguous channel allocation and bonding for wireless communication networks
EP3286957A4 (de) * 2015-04-20 2018-12-12 Nokia Solutions and Networks Oy Verfahren und vorrichtung zur handhabung von datenaktivität einer sekundärbatterie
US9965369B2 (en) 2015-04-28 2018-05-08 Viasat, Inc. Self-organized storage nodes for distributed delivery network
US9585149B1 (en) * 2015-05-07 2017-02-28 Sprint Spectrum L.P. Method and system for selecting duplex mode of second RF carrier based on performance on first RF carrier
EP3675408A1 (de) * 2015-07-16 2020-07-01 Huawei Technologies Co., Ltd. Verfahren und vorrichtung zur endgerät-zu-endgerät-datenübertragung
EP3326408B1 (de) * 2015-07-22 2020-04-01 Intel IP Corporation Konvergenzschicht für 5g-kommunikationssysteme
CN107005986B (zh) * 2015-07-27 2021-05-14 华为技术有限公司 数据包的传输方法和设备
CN105050189B (zh) * 2015-08-10 2019-02-05 上海华为技术有限公司 一种无线资源调度的方法及相关设备
US11310852B2 (en) 2015-08-11 2022-04-19 Nec Corporation Apparatus and method related to dual connectivity
EP3335511A4 (de) * 2015-08-14 2019-03-20 Intel IP Corporation Listen-ebfore-talk mit mehreren trägern
US10727979B2 (en) 2015-08-14 2020-07-28 Electronics And Telecommunications Research Institute Operation methods of communication node in network supporting licensed and unlicensed bands
US9876613B2 (en) * 2015-08-28 2018-01-23 Qualcomm Incorporated Transport protocol communications reduction
WO2017041274A1 (zh) * 2015-09-10 2017-03-16 广东欧珀移动通信有限公司 信道测量与测量结果上报的方法和装置
EP3349486B1 (de) * 2015-09-11 2021-03-24 Nec Corporation Vorrichtung und verfahren im zusammenhang mit drahtloser kommunikation
US9936414B2 (en) * 2015-09-25 2018-04-03 Nec Corporation Enabling long-term-evolution/wifi coexistence
US10034200B2 (en) * 2015-10-23 2018-07-24 Motorola Mobility Llc Iteratively transmitting random linear network encoded packets from multiple transmission nodes
CA3003388C (en) * 2015-11-10 2022-04-26 Telefonaktiebolaget Lm Ericsson (Publ) Uplink and/or downlink signaling related to different radio access technologies
US10341833B2 (en) 2015-11-10 2019-07-02 At&T Mobility Ii Llc Automatic proximity discovery area technique
EP3375109B1 (de) * 2015-11-12 2021-01-06 Telefonaktiebolaget LM Ericsson (PUBL) System und methode zum bereitstellen von 3 gpp basierten kommunikationen in einer indoor umgebung
US9755979B2 (en) 2015-11-19 2017-09-05 Viasat, Inc. Enhancing capacity of a direct communication link
CN106899527B (zh) * 2015-12-17 2020-10-27 华为技术有限公司 一种数据符号传输方法及无线网络设备
US10193674B2 (en) * 2015-12-18 2019-01-29 Qualcomm Incorporated Methods and systems for processing a global navigation satellite system signal
CN106961703B (zh) * 2016-01-11 2021-07-23 中兴通讯股份有限公司 一种信息传输方法、装置和系统
JP6659147B2 (ja) 2016-01-19 2020-03-04 キヤノン株式会社 通信装置、通信方法、およびプログラム
WO2017125129A1 (en) * 2016-01-19 2017-07-27 Nokia Solutions And Networks Oy Guard period between subframe portions of same link direction in wireless networks
US10285028B2 (en) * 2016-02-05 2019-05-07 Qualcomm Incorporated Adaptive radio link monitoring
US9838865B2 (en) 2016-02-10 2017-12-05 Qualcomm Incorporated Techniques for providing network access
WO2017155439A1 (en) * 2016-03-11 2017-09-14 Telefonaktiebolaget Lm Ericsson (Publ) Selective access information broadcat in overlapping service areas
US20170317794A1 (en) * 2016-04-29 2017-11-02 Lg Electronics Inc. Method and user equipment for transmitting uplink signal, and method and base station for receiving uplink signal
US10517021B2 (en) 2016-06-30 2019-12-24 Evolve Cellular Inc. Long term evolution-primary WiFi (LTE-PW)
US10945263B2 (en) 2016-07-27 2021-03-09 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Communication method and communication apparatus
CN107666693B (zh) * 2016-07-29 2019-09-17 电信科学技术研究院 终端路径转移、控制终端状态转换的方法、终端及基站
US11146377B2 (en) 2016-08-02 2021-10-12 Samung Electronics Co., Ltd Method and apparatus for communicating in a wireless communication system
US10356733B2 (en) 2016-08-11 2019-07-16 Qualcomm Incorporated Distributed joint access for unlicensed sidelink
WO2018033659A1 (en) 2016-08-17 2018-02-22 Nokia Technologies Oy Method for coordinated sleep mode in ran for energy savings
US10193634B2 (en) 2016-09-19 2019-01-29 Hewlett Packard Enterprise Development Lp Optical driver circuits
US10149133B2 (en) * 2016-09-22 2018-12-04 Qualcomm Incorporated Facilitating a location determination of a user equipment that is connected to a master radio based upon slave radio measurements
CN107872415B (zh) * 2016-09-23 2022-07-15 中兴通讯股份有限公司 一种数据传输方法及装置
US10218484B2 (en) 2016-09-27 2019-02-26 Qualcomm Incorporated Enhanced transmission acknowledgment delivery and processing
ES2965202T3 (es) 2016-09-30 2024-04-11 Ericsson Telefon Ab L M Conocimiento de la red central de un estado de equipo de usuario
WO2018062249A1 (ja) * 2016-09-30 2018-04-05 京セラ株式会社 無線端末及び基地局
EP3322254A1 (de) * 2016-11-11 2018-05-16 Nokia Technologies Oy Verbindungssteuerung zur dualen konnektivität und zusammenarbeit in drahtlosen netzwerken
CN108617016B (zh) * 2016-12-15 2020-07-31 中国电信股份有限公司 载波聚合无线资源控制方法和系统
MX2019006854A (es) * 2016-12-20 2019-08-22 Ericsson Telefon Ab L M Metodos, dispositivo inalambrico, nodo de red y nodo central para administrar la accesibilidad del dispositivo inalambrico.
JP6773224B2 (ja) * 2016-12-23 2020-10-21 富士通株式会社 データ送信／受信装置、方法及び通信システム
TWI616111B (zh) 2016-12-23 2018-02-21 財團法人工業技術研究院 在未授權頻譜中的無線電資源排程方法及使用其之基地台
CN106850002B (zh) * 2017-01-20 2019-12-17 建荣半导体（深圳）有限公司 一种蓝牙数据发送方法、系统及蓝牙收发器
US10257831B2 (en) * 2017-03-01 2019-04-09 Alcatel Lucent Adaptive allocation of temporal resources for massive multiple-input-multiple-output (MIMO) in unlicensed frequency bands
US10069575B1 (en) 2017-03-01 2018-09-04 Alcatel Lucent Dynamic interference suppression for massive multiple-input-multiple-output (MIMO) in unlicensed frequency bands
CN110447261B (zh) * 2017-03-23 2024-03-01 Oppo广东移动通信有限公司 传输数据的方法、终端设备和网络设备
WO2018175842A1 (en) * 2017-03-24 2018-09-27 Intel Corporation Carrier aggregation and high order modulation in vehicle-to-vehicle (v2v) sidelink communication
WO2018199707A1 (ko) * 2017-04-28 2018-11-01 엘지전자 주식회사 무선 통신 시스템에서 v2x 통신을 위한 단말의 신호 전송 방법 및 상기 방법을 이용하는 단말
EP3621403A4 (de) * 2017-05-04 2021-01-06 LG Electronics Inc. Verfahren zur durchführung eines direktzugriffsverfahrens und vorrichtung dafür
WO2018209553A1 (en) * 2017-05-16 2018-11-22 Telefonaktiebolaget Lm Ericsson (Publ) Methods supporting multicast/multiuser transmission using listen after talk and related network nodes
CN115515257A (zh) * 2017-06-15 2022-12-23 高通股份有限公司 用于多连接性模式中的用户设备移动性的技术和装置
US10389342B2 (en) 2017-06-28 2019-08-20 Hewlett Packard Enterprise Development Lp Comparator
CN109429360B (zh) * 2017-07-11 2020-10-16 华为技术有限公司 一种连接建立的方法、装置及系统
CN109428702A (zh) * 2017-08-30 2019-03-05 索尼公司 电子装置、无线通信方法和计算机可读介质
KR102394217B1 (ko) 2017-09-15 2022-05-04 삼성전자 주식회사 전력 소모 절감을 위한 전력 제어 방법 및 장치
CN116347670A (zh) * 2017-09-27 2023-06-27 三菱电机株式会社 通信系统、基站装置及通信终端装置
US11388616B2 (en) * 2017-11-16 2022-07-12 Telefonaktiebolaget Lm Ericsson (Publ) Method for performing radio link monitoring
CN110138678B (zh) * 2018-02-08 2023-02-24 华为技术有限公司 数据传输控制方法和装置、以及网络传输设备和存储介质
US10834749B2 (en) * 2018-02-19 2020-11-10 Electronics And Telecommunications Research Institute Method for bandwidth part management in communication system and apparatus for the same
CN108347714A (zh) * 2018-04-02 2018-07-31 西安交通大学 一种利用软件无线电平台实现d2d通信的方法
KR102544861B1 (ko) * 2018-05-24 2023-06-19 삼성전자 주식회사 무선 통신 시스템에서 단말의 전력 소모 감소 방법 및 장치
US11006446B2 (en) * 2018-05-31 2021-05-11 Qualcomm Incorporated Traffic scheduling in cellular V2X communication
US10897705B2 (en) 2018-07-19 2021-01-19 Tectus Corporation Secure communication between a contact lens and an accessory device
US10602513B2 (en) * 2018-07-27 2020-03-24 Tectus Corporation Wireless communication between a contact lens and an accessory device
US10609750B2 (en) * 2018-08-03 2020-03-31 Apple Inc. Devices and methods for next generation technology indicators
EP3808136B1 (de) * 2018-08-07 2022-06-29 Google LLC Bestimmung eines ressourcensteuerungsstatus auf basis eines leistungsstatus
US11452169B2 (en) * 2018-08-15 2022-09-20 Google Llc Preventing inadvertent idle mode in multi-node connectivity environments
WO2020047810A1 (zh) * 2018-09-06 2020-03-12 深圳市汇顶科技股份有限公司 链路处理方法、设备及存储介质
US11096186B2 (en) * 2018-09-11 2021-08-17 Qualcomm Incorporated Modulation and coding scheme table design for power efficiency
WO2020068651A1 (en) * 2018-09-26 2020-04-02 Intel Corporation Rlf handling during multi-connectivity handover
CN113169838A (zh) * 2018-09-26 2021-07-23 瑞典爱立信有限公司 用于副链路无线电通信的技术
CN112602347B (zh) * 2018-09-27 2024-05-07 株式会社Ntt都科摩 用户装置
JP7148622B2 (ja) * 2018-09-27 2022-10-05 株式会社Ｎｔｔドコモ 端末及び通信方法
CN112806094B (zh) * 2018-10-10 2024-03-22 株式会社Ntt都科摩 终端、无线通信系统以及无线通信方法
WO2020085816A1 (ko) * 2018-10-24 2020-04-30 엘지전자 주식회사 무선통신시스템에서 사이드 링크 단말이 사이드링크 신호를 검출하는 방법 및 장치
KR102662626B1 (ko) 2018-11-02 2024-05-03 삼성전자 주식회사 V2x 시스템에서 자동 이득 제어 방법 및 장치
WO2020091556A1 (en) * 2018-11-02 2020-05-07 Samsung Electronics Co., Ltd. Method and apparatus for automatic gain control in vehicle-to-everything system
US10904059B2 (en) * 2018-11-02 2021-01-26 Qualcomm Incorporated Control channel for vehicle-to-everything (V2X) communication
US20220046536A1 (en) * 2018-11-12 2022-02-10 Sony Corporation Method and apparatus for network management of assistance information signaling
EP3893532A4 (de) 2018-12-20 2022-07-06 Beijing Xiaomi Mobile Software Co., Ltd. Datenübertragungsverfahren und -vorrichtung
CN111355561B (zh) * 2018-12-24 2023-01-24 中兴通讯股份有限公司 数据重传的指示、处理方法及装置
KR20200086149A (ko) 2019-01-08 2020-07-16 삼성전자주식회사 무선 통신 시스템에서 단말의 전력 소모 감소 방법 및 장치
CN111278091A (zh) * 2019-01-31 2020-06-12 维沃移动通信有限公司 辅助信息上报方法和终端
JP7311991B2 (ja) 2019-03-26 2023-07-20 キヤノン株式会社 通信装置、通信装置の制御方法、プログラム
JP7340941B2 (ja) 2019-03-26 2023-09-08 キヤノン株式会社 通信装置、制御方法、及びプログラム
KR20200132605A (ko) 2019-05-17 2020-11-25 삼성전자주식회사 무선 통신 시스템에서 지연 감소를 위한 전송 경로 결정 방법 및 장치
US20220287002A1 (en) * 2019-08-08 2022-09-08 Google Llc Network-triggered paging for multi-radio dual connectivity
US11816052B2 (en) * 2019-10-22 2023-11-14 Intel Corporation System, apparatus and method for communicating telemetry information via virtual bus encodings
US11540178B2 (en) * 2019-12-05 2022-12-27 Qualcomm Incorporated Wireless communication with non-punctured symbols
US11357006B2 (en) 2020-01-02 2022-06-07 Apple Inc. Selective multi-link operation in a wireless local area network
CN111771421B (zh) * 2020-04-28 2024-03-08 北京小米移动软件有限公司 信息处理方法及装置、通信设备及存储介质
CN115553059A (zh) * 2020-05-19 2022-12-30 Oppo广东移动通信有限公司 终端辅助信息上报方法、终端设备和网络设备
EP4179808A4 (de) * 2020-07-10 2024-05-01 Lenovo Beijing Ltd Verfahren und vorrichtung zur erkennung von sidelink-übertragungsbursts über ein unlizenziertes spektrum
CN116114293A (zh) * 2020-08-06 2023-05-12 中兴通讯股份有限公司 Ue辅助信息评估
CN113839750B (zh) * 2021-11-25 2022-02-18 之江实验室 一种语义通信系统中的信息传输方法
WO2023110087A1 (en) * 2021-12-15 2023-06-22 Nokia Technologies Oy Control signalling

Family Cites Families (202)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6553540B1 (en) * 1998-12-07 2003-04-22 Telefonaktiebolaget Lm Ericsson Efficient system and method for forward error correction
US6208620B1 (en) 1999-08-02 2001-03-27 Nortel Networks Corporation TCP-aware agent sublayer (TAS) for robust TCP over wireless
US6788702B1 (en) * 1999-10-15 2004-09-07 Nokia Wireless Routers, Inc. Protocol for neighborhood-established transmission scheduling
EP1102441A1 (de) * 1999-11-18 2001-05-23 Telefonaktiebolaget Lm Ericsson Verfahren und Vorrichtung zur Verbesserung eines Datendurchsatzes in einem Kommunikationssystem
GB2370189B (en) 2000-12-13 2002-11-27 Ericsson Telefon Ab L M Radio link monitoring in a telecommunications network
US7280517B2 (en) * 2001-11-02 2007-10-09 At&T Corp. Wireless LANs and neighborhood capture
US6985741B2 (en) * 2001-11-09 2006-01-10 Telefonaktiebolaget Lm Ericsson (Publ) Estimation of interference in a radio communication network
DE60232023D1 (de) * 2002-02-19 2009-05-28 Alcatel Lucent Telekommunikationsendgerät, verfahren zum senden und empfangen und sendungssystem
WO2003096730A1 (en) 2002-05-07 2003-11-20 Nokia Corporation Adaptive release/inactivity timer for controlling non real-time data connection resources in a mobile communication network
US8015303B2 (en) 2002-08-02 2011-09-06 Astute Networks Inc. High data rate stateful protocol processing
US7814218B1 (en) 2002-10-17 2010-10-12 Astute Networks, Inc. Multi-protocol and multi-format stateful processing
US7990883B2 (en) * 2003-05-16 2011-08-02 Sony Corporation Communication system, communication method, communication apparatus, communication control method, and computer program
US20040246962A1 (en) 2003-06-06 2004-12-09 Kopeikin Roy A. Dynamically assignable resource class system to directly map 3GPP subscriber communications to a MPLS-based protocol
JP4569328B2 (ja) 2004-03-18 2010-10-27 パナソニック株式会社 無線通信装置および経路探索方法
US7328393B2 (en) * 2004-04-13 2008-02-05 Cisco Technology, Inc. Forward error correction in packet networks
JP4779438B2 (ja) * 2004-05-31 2011-09-28 パナソニック株式会社 無線通信方法および無線通信装置
US7551568B2 (en) * 2004-06-22 2009-06-23 Ntt Docomo Inc. Power mode aware packet communication method and apparatus
KR100922021B1 (ko) * 2004-08-25 2009-10-19 메시네트웍스, 인코포레이티드 통신 네트워크, 통신 네트워크에서 통신하는 노드, 및 통신 네크워크에서 노드들간의 통신을 제어하는 방법
KR100678939B1 (ko) * 2004-08-27 2007-02-07 삼성전자주식회사 인프라스트럭처 모드의 무선 네트워크 환경에 있어서,무선 데이터 전송 방법
US8374087B2 (en) * 2004-09-23 2013-02-12 Sony Corporation Reliable audio-video transmission system using multi-media diversity
US9240868B2 (en) * 2004-11-05 2016-01-19 Ruckus Wireless, Inc. Increasing reliable data throughput in a wireless network
US8879511B2 (en) * 2005-10-27 2014-11-04 Qualcomm Incorporated Assignment acknowledgement for a wireless communication system
US20070019578A1 (en) 2005-07-14 2007-01-25 Siano Mobile Silicon Ltd. Method for efficient energy consumption in battery powered handheld and mobile devices
KR100962519B1 (ko) 2005-08-22 2010-06-14 노키아 코포레이션 향상 다운링크 채널 릴리즈, 구성 및 재구성을 제공하는 장치, 방법 및 컴퓨터 프로그램 생성물
US8019346B2 (en) * 2005-09-30 2011-09-13 Telefonaktiebolaget L M Ericsson (Publ) Means and Methods for Improving the Handover Characteristics of Integrated Radio Access Networks
US7573859B2 (en) * 2005-10-13 2009-08-11 Trapeze Networks, Inc. System and method for remote monitoring in a wireless network
ES2396309T3 (es) * 2005-12-14 2013-02-20 Research In Motion Limited Método y aparato para el control de recursos de radio dirigido a un equipo de usuario
US7664085B2 (en) * 2005-12-30 2010-02-16 Intel Corporation Wireless communication device and method for coordinating communications among wireless local area networks (WLANs) and broadband wireless access (BWA) networks
US9369246B2 (en) 2005-12-30 2016-06-14 Vtech Telecommunications Limited System and method of enhancing WiFi real-time communications
EP1835677A1 (de) * 2006-03-15 2007-09-19 STMicroelectronics N.V. Verfahren zum Kalibrieren der Übertragungskette eines kabellosen Senders-Empfängers mit dem dazugehörigen kabellosen Senders-Empfängers
US20070274233A1 (en) * 2006-05-25 2007-11-29 Amnon Ptashek Method, apparatus and system for multi peer to peer services
US7760676B2 (en) 2006-06-20 2010-07-20 Intel Corporation Adaptive DRX cycle length based on available battery power
US8743825B2 (en) 2006-08-17 2014-06-03 Nokia Corporation Handovers in a communication system
US7792138B2 (en) 2006-09-13 2010-09-07 Seoul National University Foundation Distributed opportunistic scheduling in IEEE 802.11 wireless location area networks (WLANs)
US8050206B2 (en) * 2006-11-20 2011-11-01 Micropower Technologies, Inc. Wireless network camera systems
KR100965712B1 (ko) * 2006-11-20 2010-06-24 삼성전자주식회사 통신시스템에서 신호 송수신 방법 및 장치
US7783300B2 (en) 2006-11-22 2010-08-24 Airdefense, Inc. Systems and methods for proactively enforcing a wireless free zone
CN101212393B (zh) * 2006-12-29 2010-10-13 华为技术有限公司 介质无关切换消息的传输方法、系统及设备
US8077801B2 (en) * 2007-01-10 2011-12-13 Qualcomm Incorporated Pilot structure with multiplexed unicast and SFN transmissions
US20080189429A1 (en) * 2007-02-02 2008-08-07 Sony Corporation Apparatus and method for peer-to-peer streaming
EP1959601A1 (de) 2007-02-13 2008-08-20 Matsushita Electric Industrial Co., Ltd. Wiederübertragungsschema zum Austausch von Steuerinformation zwischen einem Netzwerkgateway und einem mobilen Knoten
JP4899098B2 (ja) * 2007-03-19 2012-03-21 富士通株式会社 光ロス検出装置
US8867518B2 (en) 2007-04-30 2014-10-21 Avaya Inc. Method and apparatus performing express forwarding bypass for time-critical frames
BRPI0816680A2 (pt) * 2007-09-12 2015-03-17 Qualcomm Inc Gerar e comunicar informações de identificação de origem pra habilitar comunicações confiáveis.
US8265065B2 (en) * 2007-09-14 2012-09-11 Sharp Laboratories Of America, Inc. Method and system for voice-over-internet-protocol (VoIP) transmission in a wireless communications network
WO2009073744A2 (en) * 2007-12-04 2009-06-11 Nextwave Broadband Inc. Intercell interference mitigation
TW200926847A (en) * 2007-12-14 2009-06-16 Interdigital Patent Holdings System level information for system information, paging and measurements
CN101483858B (zh) 2008-01-08 2014-08-06 株式会社Ntt都科摩 根据用户设备的可用能量设置其参数的方法及装置
US8320250B2 (en) * 2008-02-12 2012-11-27 Nvidia Corporation Method and arrangement for TCP flow control
US7984132B2 (en) 2008-06-27 2011-07-19 Qualcomm Incorporated Multi-rate peer discovery methods and apparatus
US8554200B2 (en) 2008-09-12 2013-10-08 Nokia Corporation Method and apparatus for providing interference measurements for device to-device communication
US8599734B1 (en) * 2008-09-30 2013-12-03 Meru Networks TCP proxy acknowledgements
US7822856B2 (en) 2008-10-15 2010-10-26 Patentvc Ltd. Obtaining erasure-coded fragments using push and pull protocols
CN103491646B (zh) * 2008-11-17 2017-03-29 高通股份有限公司 远程接入本地网络
US8615049B2 (en) * 2009-03-25 2013-12-24 Alcatel Lucent Method and apparatus for controlling co-channel interference in a wireless communication system
US8730938B2 (en) * 2009-04-08 2014-05-20 Qualcomm Incorporated Minimizing the impact of self synchronization on wireless communication devices
US8432848B2 (en) * 2009-05-21 2013-04-30 Indian Institute of Science (IISc) Queued cooperative wireless networks configuration using rateless codes
US8614984B2 (en) 2009-05-29 2013-12-24 Lg Electronics Inc. Method and device for efficiently transmitting precoded reference signal in radio communication system
US20100329211A1 (en) * 2009-06-29 2010-12-30 Ou Meng-Hui Method and Apparatus for Handling Inter-RAT Handover
US8248996B2 (en) * 2009-07-28 2012-08-21 Qualcomm Incorporated Methods and apparatus for using a licensed spectrum to transmit a signal when an unlicensed spectrum is congested
WO2012037635A1 (en) 2009-09-02 2012-03-29 Nortel Networks Limited Mac packet data unit construction for wireless systems
FR2949931B1 (fr) 2009-09-10 2011-08-26 Canon Kk Procedes et dispositifs de transmission d'un flux de donnees, produit programme d'ordinateur et moyen de stockage correspondants.
CN102550117A (zh) 2009-09-28 2012-07-04 诺基亚公司 蜂窝辅助d2d网络中的d2d探测的随机接入过程再用
US8457079B2 (en) * 2009-10-05 2013-06-04 Motorola Mobility Llc Method and apparatus for mitigating downlink control channel interference
KR20110048456A (ko) * 2009-11-02 2011-05-11 엘지전자 주식회사 무선 통신 시스템에서 셀 측정 방법 및 장치
WO2011069442A1 (en) * 2009-12-07 2011-06-16 Mediatek Inc. Method of reducing interference between two communication systems operating in adjacent frequency bands
US8996946B2 (en) * 2009-12-09 2015-03-31 Thomson Licensing Application of fountain forward error correction codes in multi-link multi-path mobile networks
US8885507B2 (en) 2009-12-11 2014-11-11 Nokia Corporation Method, apparatus and computer program product for allocating resources in wireless communication network
KR101670746B1 (ko) 2009-12-15 2016-11-09 엘지전자 주식회사 무선 통신 시스템에서의 멀티캐스트 및 브로드캐스트 서비스 데이터를 위한 자원 할당 방법 및 이를 위한 장치
CN101765210B (zh) 2009-12-31 2012-05-23 上海华为技术有限公司 小区边缘频带资源使用方法、装置及基站
KR101761419B1 (ko) 2010-01-13 2017-07-26 엘지전자 주식회사 단말의 위치 정보 갱신 방법 및 장치
CN101814961B (zh) * 2010-03-18 2013-11-06 华为终端有限公司 数据传输方法及装置
US8627073B2 (en) 2010-03-24 2014-01-07 GM Global Technology Operations LLC Adaptive certificate distribution mechanism in vehicular networks using forward error correcting codes
KR20110126034A (ko) 2010-05-14 2011-11-22 엘지전자 주식회사 무선 통신 시스템에서 비주기적 사운딩 참조 신호 전송 방법 및 장치
EP2578045B1 (de) * 2010-06-02 2018-01-10 Telefonaktiebolaget LM Ericsson (publ) Verfahren und vorrichtung zur steuerung der änderung eines funkressourcensteuerungsstatus (rrc) für ein benutzergerät
US8750926B2 (en) * 2010-06-18 2014-06-10 Mediatek Inc. System and method for coordinating multiple radio transceivers within the same device platform
US8380234B2 (en) * 2010-09-14 2013-02-19 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for transmitting available radio access possibilities in a communications area
US8792900B2 (en) * 2010-09-23 2014-07-29 Nokia Corporation Autonomous unlicensed band reuse in mixed cellular and device-to-device network
CN102448151B (zh) * 2010-09-30 2016-05-18 索尼公司 非连续接收方法、移动台、基站和无线通信系统
CN103416017B (zh) * 2010-11-12 2016-11-16 交互数字专利控股公司 用于执行信道聚合和媒介访问控制重传的方法和设备
EP3748893B1 (de) * 2010-12-03 2022-02-02 Samsung Electronics Co., Ltd. Verfahren und vorrichtung für drahtlose kommunikation auf mehreren spektrumsbändern
WO2012077971A2 (ko) * 2010-12-07 2012-06-14 엘지전자 주식회사 무선 통신 시스템에서 단말 간의 통신 방법 및 장치
CN102547961B (zh) * 2010-12-10 2016-06-08 华为技术有限公司 基站间同步的方法、装置及系统
TWI445323B (zh) 2010-12-21 2014-07-11 Ind Tech Res Inst 資料傳送的混合式編解碼裝置與方法
US8958307B2 (en) * 2010-12-25 2015-02-17 Intel Corporation Enabling coexistence of high-density and low-density transmissions
WO2012103683A1 (en) * 2011-02-01 2012-08-09 Renesas Mobile Corporation Timing advance without random access channel access
WO2012112872A1 (en) 2011-02-17 2012-08-23 Massachusetts Institute Of Technology Rateless and rated coding using spinal codes
US20120213108A1 (en) 2011-02-22 2012-08-23 Qualcomm Incorporated Radio resource monitoring (rrm) and radio link monitoring (rlm) procedures for remote radio head (rrh) deployments
CN103430467B (zh) * 2011-03-11 2016-05-11 Lg电子株式会社 终端在应用了载波聚合技术的无线通信系统中发送/接收信号的方法和装置
US9482734B2 (en) 2011-03-28 2016-11-01 Qualcomm Incorporated Methods and apparatus for triggering cooperative positioning or learning in a wireless network
TWI443984B (zh) * 2011-04-01 2014-07-01 Mediatek Inc 支援裝置內共存干擾迴避的方法
WO2012139278A1 (en) * 2011-04-12 2012-10-18 Renesas Mobile Corporation Methods and apparatuses of spectrum sharing for cellular-controlled offloading using unlicensed band
US9351185B2 (en) * 2011-04-15 2016-05-24 Broadcom Corporation LTE carrier aggregation configuration on TV white space bands
US9232418B2 (en) 2011-04-15 2016-01-05 Telefonaktiebolaget L M Ericsson (Publ) Methods and devices for radio link monitoring
CN103503360A (zh) * 2011-04-29 2014-01-08 交互数字专利控股公司 具有子帧限制的载波的载波聚合
US8792369B2 (en) * 2011-05-02 2014-07-29 Broadcom Corporation Method for setting a mobile node specific cyclic prefix in a mobile communication
US9042315B2 (en) * 2011-05-03 2015-05-26 Mediatek Inc. SCELL radio link monitoring and radio link failure handling
US8797924B2 (en) * 2011-05-06 2014-08-05 Innovative Sonic Corporation Method and apparatus to improve discontinuous reception (DRX) operation for TDD (time division duplex) and FDD (frequency division duplex) mode in carrier aggregation (CA)
EP2719218B1 (de) * 2011-06-08 2015-07-08 Telefonaktiebolaget LM Ericsson (PUBL) Verfahren und vorrichtungen zur meldung der qualität eines downlink-kanals
WO2012177002A2 (ko) 2011-06-21 2012-12-27 엘지전자 주식회사 무선 접속 시스템에서 장치 간 통신 수행 방법 및 이를 위한 장치
KR20130003596A (ko) 2011-06-30 2013-01-09 주식회사 케이아이 자동 실링 결합형 온수 난방 단위패널 및 이를 이용한 온수 난방 시스템
US9007972B2 (en) 2011-07-01 2015-04-14 Intel Corporation Communication state transitioning control
WO2013006988A1 (en) * 2011-07-14 2013-01-17 Renesas Mobile Corporation Methods and apparatuses for provision of a flexible time sharing scheme on an unlicensed band of a system
WO2013013409A1 (en) * 2011-07-28 2013-01-31 Renesas Mobile Corporation Signaling and procedure design for cellular cluster contending on license-exempt bands
WO2013025057A2 (ko) 2011-08-16 2013-02-21 엘지전자 주식회사 무선 접속 시스템에서 단말 간 통신 수행 방법 및 이를 위한 장치
US9485693B2 (en) 2011-08-25 2016-11-01 Telefonaktiebolaget Lm Ericsson (Publ) Adapting a triggering threshold for cell re-selection measurements
KR20140068088A (ko) 2011-08-30 2014-06-05 엘지전자 주식회사 셀룰러 네트워크에서 단말 간 직접 통신을 지원하는 방법 및 이를 위한 장치
US9319909B2 (en) * 2011-09-29 2016-04-19 Sharp Kabushiki Kaisha Devices for radio link monitoring
US20130107727A1 (en) * 2011-10-27 2013-05-02 Nokia Corporation Apparatus and Method for the Management of Reception Parameters in a Communication System
RU118142U1 (ru) * 2011-11-21 2012-07-10 Открытое акционерное общество "Научно-исследовательский институт "Вектор" Широкополосное радиоприемное устройство
CN104094623B (zh) * 2011-12-15 2018-06-05 诺基亚通信公司 载波聚合系统中的无线电操作
KR101915133B1 (ko) * 2011-12-16 2018-11-05 엘지전자 주식회사 무선 접속 시스템에서 채널 상태 정보 측정 방법 및 이를 위한 장치
WO2013094967A1 (ko) * 2011-12-19 2013-06-27 엘지전자 주식회사 Tdd 기반 무선통신 시스템에서 통신 방법 및 무선기기
US8817815B2 (en) * 2011-12-22 2014-08-26 Cisco Technology, Inc. Traffic optimization over network link
EP2803235A1 (de) 2012-01-10 2014-11-19 Nokia Solutions and Networks Oy Bereitstellung eines funkträgers auf mehreren komponententrägern
EP2803159B1 (de) * 2012-01-11 2018-08-15 Nokia Solutions and Networks Oy Sekundärzellenherstellung für eine standortübergreifende trägeraggregation
EP3937551A3 (de) 2012-01-25 2022-02-09 Comcast Cable Communications, LLC Direktzugriffskanal in einer drahtlosen mehrträgerkommunikation mit zeitvorlaufsgruppen
US8964683B2 (en) * 2012-04-20 2015-02-24 Ofinno Technologies, Llc Sounding signal in a multicarrier wireless device
US8953478B2 (en) 2012-01-27 2015-02-10 Intel Corporation Evolved node B and method for coherent coordinated multipoint transmission with per CSI-RS feedback
US9160511B2 (en) * 2012-01-30 2015-10-13 Qualcomm Incorporated Cyclic prefix in evolved multimedia broadcast multicast service with high transmit power
US20150215830A1 (en) * 2012-01-30 2015-07-30 Nokia Solutions And Networks Oy Mobility with Discontinuous Reception Using Mobility State
US9537759B2 (en) 2012-01-31 2017-01-03 Massachusetts Institute Of Technology Multi-path data transfer using network coding
US9531527B2 (en) 2012-02-17 2016-12-27 Lg Electronics Inc. Method and apparatus for transmitting signals of user equipment (UE) configured to perform D2D communication in wireless communication system
US9185690B2 (en) 2012-02-29 2015-11-10 Sharp Kabushiki Kaisha Allocating and determining resources for a device-to-device link
EP3203780A1 (de) 2012-03-02 2017-08-09 Interdigital Patent Holdings, Inc. Verfahren und system zur bereitstellung von bakeninformationen
US20130229931A1 (en) * 2012-03-02 2013-09-05 Electronics And Telecommunications Research Institute Methods of managing terminal performed in base station and terminal
KR102047706B1 (ko) 2012-03-13 2019-11-22 엘지전자 주식회사 무선 통신 시스템에서 신호 송수신 방법 및 장치
US20130250853A1 (en) * 2012-03-20 2013-09-26 Qualcomm Incorporated Methods and apparatuses to improve round trip time in transfer control protocol using accelerated acknowledgement messages
WO2013141647A1 (ko) 2012-03-22 2013-09-26 엘지전자 주식회사 무선 접속 시스템에서 상향링크 전송 파워 제어 방법 및 이를 위한 장치
US9125197B2 (en) * 2012-03-23 2015-09-01 Mediatek Inc. Methods for physical layer multi-point carrier aggregation and multi-point feedback configuration
EP2832177B1 (de) 2012-03-26 2019-04-03 Telefonaktiebolaget LM Ericsson (publ) Benutzervorrichtung, netzwerkknoten und verfahren darin zur verstellung der länge eines diskontinuierlichen empfangszyklus in einer benutzervorrichtung in einem drahtlosen kommunikationssystem
US9264249B2 (en) * 2012-03-28 2016-02-16 Qualcomm Incorporated Extending cyclic prefix length in wireless communication network having mixed carrier
US9143984B2 (en) * 2012-04-13 2015-09-22 Intel Corporation Mapping of enhanced physical downlink control channels in a wireless communication network
US9002281B2 (en) 2012-04-30 2015-04-07 Intel Corporation Apparatus and method to enable device-to-device (D2D) communication in cellular networks
KR20150018531A (ko) 2012-05-09 2015-02-23 삼성전자주식회사 이동통신 시스템에서 불연속 수신을 제어하는 방법 및 장치
WO2013169074A1 (en) 2012-05-10 2013-11-14 Samsung Electronics Co., Ltd. Method and apparatus for transmitting and receiving frame configuration information in tdd wireless communication system
US9584297B2 (en) * 2012-05-11 2017-02-28 Qualcomm Incorporated Interference management for adaptive TDD with frequency domain separations
WO2013167748A1 (en) * 2012-05-11 2013-11-14 Nokia Siemens Networks Oy Wireless communication scheduling on shared spectra
US9515757B2 (en) 2012-05-11 2016-12-06 Intel Corporation Systems and methods for enhanced user equipment assistance information in wireless communication systems
CN103428728B (zh) * 2012-05-14 2016-06-08 上海贝尔股份有限公司 在无线异构通信网中优化无线链路监视窗口参数的方法
US9100941B2 (en) * 2012-05-24 2015-08-04 Nokia Solutions And Networks Oy Using unique preambles for D2D communications in LTE
WO2013181394A1 (en) 2012-05-31 2013-12-05 Interdigital Patent Holdings, Inc. Device-to-device (d2d) link adaptation
US8831655B2 (en) * 2012-06-05 2014-09-09 Apple Inc. Methods and apparatus for coexistence of wireless subsystems in a wireless communication device
US9713167B2 (en) * 2012-06-13 2017-07-18 Verizon Patent And Licensing Inc. Multistage hierarchical packet scheduling
US8804740B2 (en) * 2012-06-15 2014-08-12 Citrix Systems, Inc. Systems and methods for reassembly of packets distributed across a cluster
US20130343252A1 (en) * 2012-06-25 2013-12-26 Broadcom Corporation Power Saving for Mobile Terminals
US9154267B2 (en) 2012-07-02 2015-10-06 Intel Corporation Sounding reference signal (SRS) mechanism for intracell device-to-device (D2D) communication
US9693306B2 (en) * 2012-07-11 2017-06-27 Blackberry Limited Mechanisms to support UE power preference signaling
CN104521169B (zh) * 2012-08-01 2017-10-03 Lg 电子株式会社 用信号传送控制信息的方法及其设备
US9445364B2 (en) * 2012-08-02 2016-09-13 Telefonaktiebolaget L M Ericsson (Publ) Systems and methods for blocking excessive transmitter message signaling
US9191828B2 (en) 2012-08-03 2015-11-17 Intel Corporation High efficiency distributed device-to-device (D2D) channel access
US9813920B2 (en) * 2012-09-19 2017-11-07 Qualcomm, Incorporated Systems and methods for transmitting and receiving discovery messages
US8976780B2 (en) * 2012-09-27 2015-03-10 Blackberry Limited Uplink timing maintenance upon time alignment timer expiry
CA2887219C (en) * 2012-10-10 2018-11-27 Telefonaktiebolaget L M Ericsson (Publ) Discontinuous reception method and user equipment using the same
WO2014070066A1 (en) * 2012-10-29 2014-05-08 Telefonaktiebolaget L M Ericsson (Publ) Radio resource management in inter-operator time sharing of frequency spectrum
US9313695B2 (en) * 2012-10-30 2016-04-12 Intel Deutschland Gmbh Radio communication devices, network devices, methods for controlling a radio communication device, and methods for controlling a network device
CN104871593B (zh) * 2012-12-18 2019-03-26 诺基亚技术有限公司 通过用户设备(ue)进行有效测量报告
US9271324B2 (en) * 2012-12-19 2016-02-23 Blackberry Limited Method and apparatus for assisted serving cell configuration in a heterogeneous network architecture
IN2015DN04173A (de) 2012-12-21 2015-10-16 Ericsson Telefon Ab L M
WO2014101958A1 (en) * 2012-12-28 2014-07-03 Telecom Italia S.P.A. Activating deactivated small coverage nodes in heterogeneous cellular network
EP2944156B1 (de) * 2013-01-11 2018-11-21 Interdigital Patent Holdings, Inc. Bereichserweiterung in drahtlosen lokalen netzwerken
JP6174714B2 (ja) * 2013-01-16 2017-08-02 エルジー エレクトロニクス インコーポレイティド 端末間通信実行方法及びそのための装置
GB2509910B (en) * 2013-01-16 2019-02-20 Sony Corp Telecommunications apparatus and methods
WO2014110727A1 (zh) * 2013-01-16 2014-07-24 华为技术有限公司 定位处理方法、装置及系统
WO2014110691A1 (en) * 2013-01-17 2014-07-24 Qualcomm Incorporated Intra-cluster coordination for cell clustering interference mitigation
CN104956612B (zh) * 2013-01-17 2018-10-09 Lg 电子株式会社 在无线通信系统中接收控制信息的方法及其设备
US9986380B2 (en) 2013-01-25 2018-05-29 Blackberry Limited Proximity and interest determination by a wireless device
US9648603B2 (en) * 2013-01-26 2017-05-09 Lg Electronics Inc. Method for receiving downlink control information by UE in wireless communication system, and apparatus for same
EP2954624A1 (de) * 2013-02-07 2015-12-16 Interdigital Patent Holdings, Inc. Design einer physikalischen schicht (phy) für ein millimeterwellen (mmw)-backhaulsystem mit niedriger latenz
US9173200B2 (en) 2013-02-28 2015-10-27 Intel Mobile Communications GmbH Communication terminal, network component, base station and method for communicating
US9179451B2 (en) * 2013-03-04 2015-11-03 Qualcomm Incorporated Apparatus and methods of frequency spectrum usage in a wireless communication system
CN105122886B (zh) * 2013-03-08 2019-03-08 诺基亚技术有限公司 用于设备到设备通信的切换的方法和装置
US9549371B2 (en) * 2013-03-14 2017-01-17 Qualcomm Incorporated Access point proxy and multi-hop wireless communication
US9232460B2 (en) * 2013-03-14 2016-01-05 Fujitsu Limited Network supervised wireless device neighbor discovery
US9160515B2 (en) * 2013-04-04 2015-10-13 Intel IP Corporation User equipment and methods for handover enhancement using scaled time-to-trigger and time-of-stay
WO2014185840A1 (en) 2013-05-16 2014-11-20 Telefonaktiebolaget L M Ericsson (Publ) A wireless device, network nodes and methods therein for handling a device-to-device (d2d) communication during handover in a wireless telecommunications network
CN104412122A (zh) * 2013-05-30 2015-03-11 英特尔Ip公司 确定移动装置位于室内位置还是室外位置的装置、系统和方法
US9479230B2 (en) * 2013-05-31 2016-10-25 Blackberry Limited Systems and methods for data offload in wireless networks
CN104244354A (zh) * 2013-06-09 2014-12-24 中兴通讯股份有限公司 减少邻频段网络间共设备互扰的方法及装置
US20140370904A1 (en) 2013-06-12 2014-12-18 Research In Motion Limited Device-to-device discovery
US9814037B2 (en) * 2013-06-28 2017-11-07 Intel Corporation Method for efficient channel estimation and beamforming in FDD system by exploiting uplink-downlink correspondence
US9325480B2 (en) * 2013-07-10 2016-04-26 Google Technology Holdings LLC Methods and device for performing device-to-device communication
US9900029B2 (en) * 2013-08-07 2018-02-20 Qualcomm Incorporated Intra-frequency and inter-RAT receiver
US9445431B2 (en) * 2013-08-08 2016-09-13 Mediatek Inc. Wireless communications devices supporting WiFi and LTE communications and methods for transmission control thereof
ES2701254T3 (es) 2013-08-08 2019-02-21 Intel Corp Señalización para servicios de proximidad y descubrimiento D2D en una red LTE
BR112015033063B1 (pt) 2013-08-08 2023-10-03 Apple Inc Equipamento de usuário, método para operações de descoberta de dispositivo para dispositivo (d2d) com base em pacote e mídia de armazenamento legível por computador não transitória
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
US10034283B2 (en) * 2013-08-23 2018-07-24 Qualcomm Incorporated CSI and ACK reporting enhancements in LTE/LTE-A with unlicensed spectrum
US9510222B2 (en) * 2013-08-23 2016-11-29 Qualcomm Incorporated Detection of bursty WiFi interference in LTE/LTE-A communications in an unlicensed spectrum
US20150063148A1 (en) * 2013-09-04 2015-03-05 Qualcomm Incorporated Robust inter-radio access technology operations in unlicensed spectrum
US9807786B2 (en) * 2013-09-11 2017-10-31 Lg Electronics Inc. Method and apparatus for transmitting signal of device to device user equipment in wireless communication system
EP2876968A1 (de) * 2013-10-09 2015-05-27 Nokia Corporation Verfahren und Vorrichtung zur Durchführung eines diskontinuierlichen Empfangs
US9332465B2 (en) * 2013-10-15 2016-05-03 Qualcomm Incorporated Long term evolution interference management in unlicensed bands for wi-fi operation
US9220115B2 (en) * 2013-10-23 2015-12-22 Qualcomm Incorporated Techniques for channel access in asynchronous unlicensed radio frequency spectrum band deployments
CN105706515A (zh) * 2013-10-25 2016-06-22 瑞典爱立信有限公司 接收机信道预留
US9271205B2 (en) * 2013-10-31 2016-02-23 Google Technology Holdings LLC Measurement management in small-cell systems
US20160262184A1 (en) * 2013-11-14 2016-09-08 Qualcomm Incorporated Wi-fi compatible dedicated protocol interval announcement
CN105745960B (zh) * 2013-11-19 2019-05-28 诺基亚技术有限公司 用于标识切换故障模式的装置、方法和计算机可读存储介质
US9661657B2 (en) * 2013-11-27 2017-05-23 Intel Corporation TCP traffic adaptation in wireless systems
US9408095B2 (en) * 2014-02-05 2016-08-02 Telefonaktiebolaget L M Ericsson (Publ) Autonomous determination of overlapping coverage in heterogeneous networks
US9967902B2 (en) * 2016-02-04 2018-05-08 Sharp Laboratories Of America, Inc. Systems and methods for contention access region in a licensed-assisted access(LAA)
US11229050B2 (en) * 2019-03-29 2022-01-18 Samsung Electronics Co., Ltd. Method and apparatus for frame based equipment operation of NR unlicensed

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None *

Also Published As

Publication number Publication date
US20150146562A1 (en) 2015-05-28
CN105684499B (zh) 2019-08-30
EP3075124A4 (de) 2017-12-06
BR112016009420B1 (pt) 2023-02-23
JP6330037B2 (ja) 2018-05-23
AU2014355109B2 (en) 2017-12-14
EP3075116B1 (de) 2019-09-11
EP3075124A1 (de) 2016-10-05
KR20170118239A (ko) 2017-10-24
US9661657B2 (en) 2017-05-23
CN105659692A (zh) 2016-06-08
EP3078237A1 (de) 2016-10-12
EP3836473A1 (de) 2021-06-16
RU2017136548A (ru) 2019-02-08
ES2693393T3 (es) 2018-12-11
EP3075186A4 (de) 2017-07-05
US10375727B2 (en) 2019-08-06
US20180160450A1 (en) 2018-06-07
CN112887055A (zh) 2021-06-01
EP3075116A1 (de) 2016-10-05
US20150146615A1 (en) 2015-05-28
EP3075186A1 (de) 2016-10-05
US20150146585A1 (en) 2015-05-28
CN105659660A (zh) 2016-06-08
US20170006632A1 (en) 2017-01-05
CN105659660B (zh) 2019-12-17
JP2016540436A (ja) 2016-12-22
US20150146614A1 (en) 2015-05-28
WO2015081324A1 (en) 2015-06-04
WO2015081322A1 (en) 2015-06-04
US20160249405A1 (en) 2016-08-25
US9801207B2 (en) 2017-10-24
CN105659658B (zh) 2019-10-08
RU2016116705A (ru) 2017-11-01
US9681487B2 (en) 2017-06-13
US10231263B2 (en) 2019-03-12
KR101871645B1 (ko) 2018-06-26
KR20160060122A (ko) 2016-05-27
EP3075188A4 (de) 2017-08-16
RU2682928C1 (ru) 2019-03-22
CN105659544B (zh) 2019-07-09
HK1224488A1 (zh) 2017-08-18
EP3075138A1 (de) 2016-10-05
US20150146645A1 (en) 2015-05-28
US20190373632A1 (en) 2019-12-05
CN105684396B (zh) 2020-04-07
EP3075189A1 (de) 2016-10-05
CN105684499A (zh) 2016-06-15
WO2015080861A1 (en) 2015-06-04
EP3075116A4 (de) 2017-08-09
US9974099B2 (en) 2018-05-15
KR20160065139A (ko) 2016-06-08
US20150146599A1 (en) 2015-05-28
US10206226B2 (en) 2019-02-12
EP3078237A4 (de) 2017-08-23
AU2014355101A1 (en) 2016-05-05
WO2015080796A1 (en) 2015-06-04
WO2015080850A1 (en) 2015-06-04
US20170273106A1 (en) 2017-09-21
EP3078237B1 (de) 2018-08-22
HK1224493A1 (zh) 2017-08-18
EP3075188A1 (de) 2016-10-05
WO2015080853A1 (en) 2015-06-04
BR112016009418B1 (pt) 2023-04-18
MX363211B (es) 2019-03-14
CN105659658A (zh) 2016-06-08
CN105684396A (zh) 2016-06-15
BR112016009420A2 (de) 2017-08-01
JP2016538766A (ja) 2016-12-08
AU2014355109A1 (en) 2016-04-21
HK1224462A1 (zh) 2017-08-18
CN105684374A (zh) 2016-06-15
EP3075138A4 (de) 2017-07-05
MX2016004513A (es) 2017-01-11
EP3075189A4 (de) 2017-08-09
CN105659692B (zh) 2019-10-18
US20150146647A1 (en) 2015-05-28
RU2635091C2 (ru) 2017-11-09
US9615395B2 (en) 2017-04-04
RU2633392C1 (ru) 2017-10-12
EP3075189B1 (de) 2020-04-29
WO2015080817A1 (en) 2015-06-04
BR112016009418A2 (de) 2017-08-01
US10477575B2 (en) 2019-11-12
HK1224494A1 (zh) 2017-08-18
HK1224495A1 (zh) 2017-08-18
CN105659544A (zh) 2016-06-08
US11140710B2 (en) 2021-10-05

Similar Documents

Publication Publication Date Title
EP3075138B1 (de) Tcp-verkehrsanpassung in drahtlosen systemen
EP3554022B1 (de) Paketübertragungsverfahren und endgerät
RU2691240C1 (ru) Способ пакетной передачи и абонентское устройство
JP5523350B2 (ja) Ｔｃｐフロー制御のための方法及び装置
RU2543996C2 (ru) Управление перегрузкой в сети связи
JP4456608B2 (ja) 端末における確認応答メッセージの処理
US10142206B2 (en) Method and apparatus for packet communication using header compression
CN107005341B (zh) 无线电设备中的sdu的失序递送
US9923695B2 (en) Call processing method and apparatus for use in LTE system
US7480301B2 (en) Method, system and article for improved TCP performance during retransmission in response to selective acknowledgement
TW201517542A (zh) 用於在無線區域網路系統中執行混合自動重複請求之系統及方法
EP3490293B1 (de) Datenempfangsverfahren, datensendeverfahren, empfangsvorrichtung und system
JP2020171015A (ja) Ｌｔｅシステムを用いた呼の実行方法及び装置
CN102694631A (zh) 一种用于控制数据传输的方法和装置
US9510242B2 (en) Reducing superfluous traffic in a network
US11470502B2 (en) Congestion notification by data packet from intermediate node
WO2020154872A1 (zh) 一种传输控制协议加速方法和装置
US20170195085A1 (en) Transmission control protocol segment recovery

Legal Events

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

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20160425

AK Designated contracting states

Kind code of ref document: A1

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

AX Request for extension of the european patent

Extension state: BA ME

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

Effective date: 20170607

RIC1 Information provided on ipc code assigned before grant

Ipc: H04L 29/06 20060101ALI20170531BHEP

Ipc: H04L 1/16 20060101ALI20170531BHEP

Ipc: H04L 29/08 20060101AFI20170531BHEP

Ipc: H04W 80/06 20090101ALI20170531BHEP

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602014068993

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04L0029080000

Ipc: H04L0029060000

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

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

Free format text: STATUS: GRANT OF PATENT IS INTENDED

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 52/02 20090101ALI20191216BHEP

Ipc: H04W 36/00 20090101ALI20191216BHEP

Ipc: H04W 76/28 20180101ALI20191216BHEP

Ipc: H04W 40/30 20090101ALI20191216BHEP

Ipc: H04W 76/27 20180101ALI20191216BHEP

Ipc: H04L 1/00 20060101ALI20191216BHEP

Ipc: H04L 29/06 20060101AFI20191216BHEP

Ipc: H04W 80/06 20090101ALI20191216BHEP

RIN1 Information on inventor provided before grant (corrected)

Inventor name: LI, GUANGJIE

Inventor name: LI, XIANG

Inventor name: ZHANG, XU

Inventor name: YU, YIFAN

INTG Intention to grant announced

Effective date: 20200122

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

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

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

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

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602014068993

Country of ref document: DE

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1302676

Country of ref document: AT

Kind code of ref document: T

Effective date: 20200915

RAP2 Party data changed (patent owner data changed or rights of a patent transferred)

Owner name: APPLE INC.

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20200812

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

Ref country code: LT

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

Effective date: 20200812

Ref country code: SE

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

Effective date: 20200812

Ref country code: BG

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

Effective date: 20201112

Ref country code: HR

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

Effective date: 20200812

Ref country code: FI

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

Effective date: 20200812

Ref country code: NO

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

Effective date: 20201112

Ref country code: GR

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

Effective date: 20201113

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1302676

Country of ref document: AT

Kind code of ref document: T

Effective date: 20200812

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

Ref country code: RS

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

Effective date: 20200812

Ref country code: LV

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

Effective date: 20200812

Ref country code: NL

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

Effective date: 20200812

Ref country code: PL

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

Effective date: 20200812

Ref country code: IS

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

Effective date: 20201212

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

Ref country code: RO

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

Effective date: 20200812

Ref country code: SM

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

Effective date: 20200812

Ref country code: EE

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

Effective date: 20200812

Ref country code: CZ

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

Effective date: 20200812

Ref country code: DK

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

Effective date: 20200812

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602014068993

Country of ref document: DE

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

Ref country code: ES

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

Effective date: 20200812

Ref country code: AL

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

Effective date: 20200812

Ref country code: AT

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

Effective date: 20200812

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

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

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

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

Ref country code: MC

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

Effective date: 20200812

Ref country code: SK

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

Effective date: 20200812

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

26N No opposition filed

Effective date: 20210514

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

Ref country code: LU

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

Effective date: 20201106

Ref country code: IT

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

Effective date: 20200812

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20201130

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

Ref country code: SI

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

Effective date: 20200812

Ref country code: LI

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

Effective date: 20201130

Ref country code: CH

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

Effective date: 20201130

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

Ref country code: IE

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

Effective date: 20201106

Ref country code: FR

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

Effective date: 20201130

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602014068993

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04L0029060000

Ipc: H04L0065000000

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

Ref country code: GB

Payment date: 20210922

Year of fee payment: 8

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

Ref country code: DE

Payment date: 20210923

Year of fee payment: 8

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

Ref country code: TR

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

Effective date: 20200812

Ref country code: MT

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

Effective date: 20200812

Ref country code: CY

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

Effective date: 20200812

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

Ref country code: MK

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

Effective date: 20200812

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

Ref country code: PT

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

Effective date: 20200812

Ref country code: BE

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

Effective date: 20201130

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 602014068993

Country of ref document: DE

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20221106

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

Ref country code: GB

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

Effective date: 20221106

Ref country code: DE

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

Effective date: 20230601