US20100103864A1 - Cell relay protocol - Google Patents
Cell relay protocol Download PDFInfo
- Publication number
- US20100103864A1 US20100103864A1 US12/604,215 US60421509A US2010103864A1 US 20100103864 A1 US20100103864 A1 US 20100103864A1 US 60421509 A US60421509 A US 60421509A US 2010103864 A1 US2010103864 A1 US 2010103864A1
- Authority
- US
- United States
- Prior art keywords
- relay
- protocol
- identifier
- payload
- upper layer
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
- 238000004891 communication Methods 0.000 claims abstract description 162
- 238000000034 method Methods 0.000 claims abstract description 72
- 238000011144 upstream manufacturing Methods 0.000 claims abstract description 27
- 230000008569 process Effects 0.000 claims abstract description 16
- 238000004590 computer program Methods 0.000 claims description 23
- 230000005641 tunneling Effects 0.000 claims description 8
- 239000000284 extract Substances 0.000 claims description 7
- 238000012545 processing Methods 0.000 claims description 7
- 230000004044 response Effects 0.000 abstract description 10
- 230000006870 function Effects 0.000 description 13
- 238000005516 engineering process Methods 0.000 description 11
- 230000009471 action Effects 0.000 description 5
- 230000005540 biological transmission Effects 0.000 description 4
- 230000001143 conditioned effect Effects 0.000 description 3
- 230000000875 corresponding effect Effects 0.000 description 3
- 239000011159 matrix material Substances 0.000 description 3
- 230000001413 cellular effect Effects 0.000 description 2
- 239000000835 fiber Substances 0.000 description 2
- 230000007774 longterm Effects 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000008520 organization Effects 0.000 description 2
- 230000010363 phase shift Effects 0.000 description 2
- 238000013459 approach Methods 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 239000000969 carrier Substances 0.000 description 1
- 239000003795 chemical substances by application Substances 0.000 description 1
- 230000000295 complement effect Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 230000002596 correlated effect Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 229920001690 polydopamine Polymers 0.000 description 1
- 238000004353 relayed correlation spectroscopy Methods 0.000 description 1
- 230000008054 signal transmission Effects 0.000 description 1
- 238000000638 solvent extraction Methods 0.000 description 1
- 238000001228 spectrum Methods 0.000 description 1
- 230000002123 temporal effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04B—TRANSMISSION
- H04B7/00—Radio transmission systems, i.e. using radiation field
- H04B7/14—Relay systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/50—Address allocation
-
- 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/0072—Transmission or use of information for re-establishing the radio link of resource information of target access point
-
- 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
- H04B—TRANSMISSION
- H04B7/00—Radio transmission systems, i.e. using radiation field
- H04B7/14—Relay systems
- H04B7/15—Active relay systems
- H04B7/155—Ground-based stations
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2212/00—Encapsulation of packets
-
- 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/04—Protocols for data compression, e.g. ROHC
-
- 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/22—Parsing or analysis of headers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W40/00—Communication routing or communication path finding
- H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
- H04W40/22—Communication route or path selection, e.g. power-based or shortest path routing using selective relaying for reaching a BTS [Base Transceiver Station] or an access point
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/26—Network addressing or numbering for mobility support
-
- 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/04—Large scale networks; Deep hierarchical networks
- H04W84/042—Public Land Mobile systems, e.g. cellular systems
- H04W84/047—Public Land Mobile systems, e.g. cellular systems using dedicated repeater stations
Abstract
Systems and methodologies are described that facilitate providing a relay protocol to facilitate communicating upper layer protocol data among relay and donor nodes. In particular, a donor node can create a relay protocol packet upon receiving data for a relay node from a core network. Donor node can indicate an assigned relay identifier in the relay protocol packet header to facilitate routing the packet among related downstream relay nodes to arrive at the appropriate relay node, which can process the upper layer protocol data. In addition, a relay node can formulate a relay protocol packet for communication to a donor node through zero or more intermediary upstream relay nodes. Similarly, the relay node can insert the assigned relay identifier in the header to allow the donor node to associate response or related packets from the core network with the relay node.
Description
- The present application for patent claims priority to Provisional Application No. 61/108,287 entitled “CELL RELAY BASE STATION FOR LTE” filed Oct. 24, 2008, and assigned to the assignee hereof and hereby expressly incorporated by reference herein.
- 1. Field
- The following description relates generally to wireless communications, and more particularly to providing a protocol for relay node communications.
- 2. Background
- Wireless communication systems are widely deployed to provide various types of communication content such as, for example, voice, data, and so on. Typical wireless communication systems may be multiple-access systems capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, . . . ). Examples of such multiple-access systems may include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, and the like. Additionally, the systems can conform to specifications such as third generation partnership project (3GPP), 3GPP long term evolution (LTE), ultra mobile broadband (UMB), and/or multi-carrier wireless specifications such as evolution data optimized (EV-DO), one or more revisions thereof, etc.
- Generally, wireless multiple-access communication systems may simultaneously support communication for multiple mobile devices. Each mobile device may communicate with one or more access points (e.g., base stations) via transmissions on forward and reverse links. The forward link (or downlink) refers to the communication link from access points to mobile devices, and the reverse link (or uplink) refers to the communication link from mobile devices to access points. Further, communications between mobile devices and access points may be established via single-input single-output (SISO) systems, multiple-input single-output (MISO) systems, multiple-input multiple-output (MIMO) systems, and so forth. Access points, however, can be limited in geographic coverage area as well as resources such that mobile devices near edges of coverage and/or devices in areas of high traffic can experience degraded quality of communications from an access point.
- Cell relays can be provided to expand network capacity and coverage area by facilitating communication between mobile devices and access points. For example, a cell relay can establish a backhaul link with a donor access point, which can provide access to a number of cell relays, and the cell relay can establish an access link with one or more mobile devices or additional cell relays. To mitigate modification to backend core network components, communication interfaces, such as S1-U, can terminate at the donor access point. Thus, the donor access point appears as a normal access point to backend network components. To this end, the donor access point can route packets from the backend network components to the cell relays for communicating to the mobile devices.
- The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects, and is intended to neither identify key or critical elements of all aspects nor delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.
- In accordance with one or more aspects and corresponding disclosure thereof, various aspects are described in connection with facilitating providing a relay protocol that supports packet routing, point-to-point communications, and/or the like. In particular, relay evolved Node Bs (eNB) can communicate using a relay protocol layer that carriers upper layer protocol messages. Relay eNBs can create a header for packets communicated over the relay protocol layer, which can include fields indicating a type of upper layer protocol message, an identifier for a destination relay eNB, a destination internet protocol (IP) address, and/or the like. In one example, the relay eNB identifier can be assigned by a donor eNB and communicated to each relay eNB in the chain to the destination relay eNB. In this regard, packets received from a core network at the donor eNB can be routed to the destination relay eNB by populating a relay ID field in the relay protocol header. Receiving relay eNBs can obtain the relay ID and route the packet according to a routing table associating relay IDs to downstream relay eNB identifiers.
- According to related aspects, a method is provided that includes generating a relay protocol packet comprising an upper layer protocol payload. The method also includes populating a header of the relay protocol packet with a relay identifier and transmitting the relay protocol packet to one or more eNBs in a wireless network.
- Another aspect relates to a wireless communications apparatus. The wireless communications apparatus can include at least one processor configured to create a relay protocol packet having an upper layer protocol payload and insert a relay identifier in a header of the relay protocol packet. The at least one processor is further configured to communicate the relay protocol packet to one or more eNBs. The wireless communications apparatus also comprises a memory coupled to the at least one processor.
- Yet another aspect relates to an apparatus. The apparatus includes means for generating a relay protocol packet and means for inserting a relay identifier in a header of the relay protocol packet. The apparatus also includes means for communicating the relay protocol packet to one or more eNBs in a wireless network.
- Still another aspect relates to a computer program product, which can have a computer-readable medium including code for causing at least one computer to generate a relay protocol packet comprising an upper layer protocol payload. The computer-readable medium can also comprise code for causing the at least one computer to populate a header of the relay protocol packet with a relay identifier and code for causing the at least one computer to transmit the relay protocol packet to one or more eNBs in a wireless network.
- Moreover, an additional aspect relates to an apparatus including a relay protocol packet generating component that creates a relay protocol packet comprising an upper layer protocol payload and a relay protocol header populating component that inserts a relay identifier in a header of the relay protocol packet. The apparatus can further include a relay protocol communicating component that transmits the relay protocol packet to one or more eNBs in a wireless network.
- According to an additional aspect, a method is provided that includes receiving a relay protocol packet comprising an upper layer protocol payload and a relay identifier. The method also includes determining a relay eNB to receive the relay protocol packet based at least in part on the relay identifier and transmitting the relay protocol packet to the relay eNB.
- Another aspect relates to a wireless communications apparatus. The wireless communications apparatus can include at least one processor configured to obtain a relay protocol packet including an upper layer protocol payload and a relay identifier. The at least one processor is further configured to select a relay eNB to receive the relay protocol packet based at least in part on the relay identifier and forward the relay protocol packet to the relay eNB. The wireless communications apparatus also comprises a memory coupled to the at least one processor.
- Yet another aspect relates to an apparatus. The apparatus includes means for storing a relay identifier along with an identifier of a next hop relay eNB. The apparatus also includes means for forwarding a relay protocol packet to the next hop relay eNB based at least in part on locating the relay identifier extracted from the relay protocol packet in the means for storing.
- Still another aspect relates to a computer program product, which can have a computer-readable medium including code for causing at least one computer to receive a relay protocol packet comprising an upper layer protocol payload and a relay identifier and code for causing the at least one computer to determine a relay eNB to receive the relay protocol packet based at least in part on the relay identifier. The computer-readable medium can also comprise code for causing the at least one computer to transmit the relay protocol packet to the relay eNB.
- Moreover, an additional aspect relates to an apparatus including a routing table component that stores a relay identifier along with an identifier of a next hop relay eNB. The apparatus can further include a relay protocol forwarding component that transmits a relay protocol packet to the next hop relay eNB based at least in part on locating the relay identifier extracted from the relay protocol packet in the routing table component.
- According to yet another aspect, a method is provided that includes receiving a relay protocol packet comprising an upper layer protocol payload and a relay identifier and determining a type of the upper layer protocol payload. The method further includes communicating the upper layer protocol payload, along with the relay identifier, to a core network component over a disparate transport layer based at least in part on the type of the upper layer protocol payload
- Another aspect relates to a wireless communications apparatus. The wireless communications apparatus can include at least one processor configured to obtain a relay protocol packet comprising an upper layer protocol payload and a relay identifier and discern a type of the upper layer protocol payload. The at least one processor is further configured to transmit the upper layer protocol payload along with the relay identifier over a disparate transport layer to an upstream network component. The wireless communications apparatus also comprises a memory coupled to the at least one processor.
- Yet another aspect relates to an apparatus. The apparatus includes means for receiving a relay protocol packet comprising an upper layer protocol payload and a relay identifier and means for determining a type of the upper layer protocol payload. The apparatus also includes means for communicating the upper layer protocol payload along with the relay identifier to a core network component over a disparate transport layer.
- Still another aspect relates to a computer program product, which can have a computer-readable medium including code for causing at least one computer to receive a relay protocol packet comprising an upper layer protocol payload and a relay identifier and code for causing the at least one computer to determine a type of the upper layer protocol payload. The computer-readable medium can also comprise code for causing the at least one computer to communicate the upper layer protocol payload, along with the relay identifier, to a core network component over a disparate transport layer based at least in part on the type of the upper layer protocol payload.
- Moreover, an additional aspect relates to an apparatus including a relay protocol component that receives a relay protocol packet comprising an upper layer protocol payload and a relay identifier. The apparatus can further include a relay protocol header reading component that determines a type of the upper layer protocol payload and a backhaul link component that communicates the upper layer protocol payload along with the relay identifier to a core network component over a disparate transport layer.
- To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed and this description is intended to include all such aspects and their equivalents.
-
FIG. 1 is an illustration of an example wireless communications system that facilitates providing relays for wireless networks. -
FIG. 2 is an illustration of an example wireless communications system that facilitates communicating over a relay protocol. -
FIG. 3 is an illustration of an example wireless communications system that communicates over a relay protocol using a cell radio network temporary identifier. -
FIG. 4 is an illustration of an example relay protocol component in accordance with aspects described herein. -
FIG. 5 is an illustration of an example wireless communications system that utilizes cell relays to provide access to a wireless network. -
FIG. 6 is an illustration of example protocol stacks that facilitate providing cell relay functionality for data plane communications using a relay protocol. -
FIG. 7 is an illustration of an example methodology for communicating with upstream relay nodes using a relay protocol. -
FIG. 8 is an illustration of an example methodology for receiving communications over a relay protocol. -
FIG. 9 is an illustration of an example methodology that forwards relay protocol packets in a wireless network. -
FIG. 10 is an illustration of an example methodology that receives relay protocol packets from downstream relay nodes and formulates associated core network packets. -
FIG. 11 is an illustration of an example methodology that transmits relay protocol packets to downstream relay nodes. -
FIG. 12 is an illustration of a wireless communication system in accordance with various aspects set forth herein. -
FIG. 13 is an illustration of an example wireless network environment that can be employed in conjunction with the various systems and methods described herein. -
FIG. 14 is an illustration of an example system that facilitates transmitting relay protocol packets to and receiving relay protocol packets from upstream relay nodes. -
FIG. 15 is an illustration of an example system that facilitates forwarding relay protocol packets to relay nodes. -
FIG. 16 is an illustration of an example system that facilitates communicating between relay nodes and a core network. - Various aspects are now described with reference to the drawings. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of one or more aspects. It may be evident, however, that such aspect(s) may be practiced without these specific details.
- As used in this application, the terms “component,” “module,” “system” and the like are intended to include a computer-related entity, such as but not limited to hardware, firmware, a combination of hardware and software, software, or software in execution. For example, a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a computing device and the computing device can be a component. One or more components can reside within a process and/or thread of execution and a component may be localized on one computer and/or distributed between two or more computers. In addition, these components can execute from various computer readable media having various data structures stored thereon. The components may communicate by way of local and/or remote processes such as in accordance with a signal having one or more data packets, such as data from one component interacting with another component in a local system, distributed system, and/or across a network such as the Internet with other systems by way of the signal.
- Furthermore, various aspects are described herein in connection with a terminal, which can be a wired terminal or a wireless terminal. A terminal can also be called a system, device, subscriber unit, subscriber station, mobile station, mobile, mobile device, remote station, remote terminal, access terminal, user terminal, terminal, communication device, user agent, user device, or user equipment (UE). A wireless terminal may be a cellular telephone, a satellite phone, a cordless telephone, a Session Initiation Protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device having wireless connection capability, a computing device, or other processing devices connected to a wireless modem. Moreover, various aspects are described herein in connection with a base station. A base station may be utilized for communicating with wireless terminal(s) and may also be referred to as an access point, a Node B, or some other terminology.
- Moreover, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or.” That is, unless specified otherwise, or clear from the context, the phrase “X employs A or B” is intended to mean any of the natural inclusive permutations. That is, the phrase “X employs A or B” is satisfied by any of the following instances: X employs A; X employs B; or X employs both A and B. In addition, the articles “a” and “an” as used in this application and the appended claims should generally be construed to mean “one or more” unless specified otherwise or clear from the context to be directed to a singular form.
- The techniques described herein may be used for various wireless communication systems such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA and other systems. The terms “system” and “network” are often used interchangeably. A CDMA system may implement a radio technology such as Universal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includes Wideband-CDMA (W-CDMA) and other variants of CDMA. Further, cdma2000 covers IS-2000, IS-95 and IS-856 standards. A TDMA system may implement a radio technology such as Global System for Mobile Communications (GSM). An OFDMA system may implement a radio technology such as Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, etc. UTRA and E-UTRA are part of Universal Mobile Telecommunication System (UMTS). 3GPP Long Term Evolution (LTE) is a release of UMTS that uses E-UTRA, which employs OFDMA on the downlink and SC-FDMA on the uplink. UTRA, E-UTRA, UMTS, LTE and GSM are described in documents from an organization named “3rd Generation Partnership Project” (3GPP). Additionally, cdma2000 and UMB are described in documents from an organization named “3rd Generation Partnership Project 2” (3GPP2). Further, such wireless communication systems may additionally include peer-to-peer (e.g., mobile-to-mobile) ad hoc network systems often using unpaired unlicensed spectrums, 802.xx wireless LAN, BLUETOOTH and any other short- or long-range, wireless communication techniques.
- Various aspects or features will be presented in terms of systems that may include a number of devices, components, modules, and the like. It is to be understood and appreciated that the various systems may include additional devices, components, modules, etc. and/or may not include all of the devices, components, modules etc. discussed in connection with the figures. A combination of these approaches may also be used.
- Referring to
FIG. 1 , awireless communication system 100 is illustrated that facilitates providing relay functionality in wireless networks.System 100 includes adonor eNB 102 that provides one or more relay eNBs, such asrelay eNB 104, with access to acore network 106. Similarly, relayeNB 104 can provide one or more disparate relay eNBs, such asrelay eNB 108, or UEs, such asUE 110, with access to thecore network 106 viadonor eNB 102.Donor eNB 102, which can also be referred to as a cluster eNB, can communicate with thecore network 106 over a wired or wireless backhaul link, which can be an LTE or other technology backhaul link. In one example, thecore network 106 can be a 3GPP LTE or similar technology network. -
Donor eNB 102 can additionally provide an access link forrelay eNB 104, which can also be wired or wireless, LTE or other technologies, and therelay eNB 104 can communicate with thedonor eNB 102 using a backhaul link over the access link of thedonor eNB 102.Relay eNB 104 can similarly provide an access link for relay eNB 108 and/orUE 110, which can be a wired or wireless LTE or other technology link. In one example,donor eNB 102 can provide an LTE access link, to whichrelay eNB 104 can connect using an LTE backhaul, and relayeNB 104 can provide an LTE access link to relayeNB 108 and/orUE 110.Donor eNB 102 can connect to thecore network 106 over a disparate backhaul link technology.Relay eNB 108 and/orUE 110 can connect to therelay eNB 104 using the LTE access link to receive access tocore network 106, as described. A donor eNB and connected relay eNBs can be collectively referred to herein as a cluster. - According to an example, relay
eNB 104 can connect to adonor eNB 102 at the link layer (e.g., media access control (MAC) layer) as would a UE in regular LTE configurations. In this regard,donor eNB 102 can be a regular LTE eNB requiring no changes at the link layer or related interface (e.g., E-UTRA-Uu) to support therelay eNB 104. In addition,relay eNB 104 can appear toUE 110 as a regular eNB at the link layer, such that no changes are required forUE 110 to connect to relayeNB 104 at the link layer, for example. In addition,relay eNB 104 can configure procedures for resource partitioning between access and backhaul link, interference management, idle mode cell selection for a cluster, and/or the like. - With respect to transport layer communications, transport protocols related to relay
eNB 108 orUE 110 communications can terminate at thedonor eNB 102, referred to as cell relay functionality, since therelay eNB 104 is like a cell of thedonor eNB 102. For example, in a cell relay configuration,donor eNB 102 can receive communications for therelay eNB 104 from thecore network 106, terminate the transport protocol, and forward the communications to therelay eNB 104 over a disparate transport layer keeping the application layer substantially intact. It is to be appreciated that the forwarding transport protocol type can be the same as the terminated transport protocol type, but is a different transport layer established with therelay eNB 104. -
Relay eNB 104 can determine a relay eNB or UE related to the communications, and provide the communications to the relay eNB or UE (e.g., based on an identifier thereof within the communications). Similarly,donor eNB 102 can terminate the transport layer protocol for communications received fromrelay eNB 104, translate the communications to a disparate transport protocol, and transmit the communications over the disparate transport protocol to thecore network 106 with the application layer intact forrelay eNB 104 as a cell relay. In these examples, whererelay eNB 104 is communicating with another relay eNB, therelay eNB 104 can support application protocol routing to ensure communications reach the correct relay eNB. - Moreover, application layer protocols can terminate at upstream eNBs. Thus, for example, application layer protocols for relay eNB 108 and
UE 110 can terminate atrelay eNB 104, and similarly forrelay eNB 104 can terminate atdonor eNB 102. The transport and application layer protocols, for example, can relate to S1-U, S1-MME, and/or X2 interfaces. S1-U interface can be utilized to communicate in a data plane between a node and a serving gateway (not shown) of thecore network 106. S1-MME interface can be utilized for control plane communications between a node and a mobility management entity (MME) (not shown) of thecore network 106. X2 interface can be utilized for communications between eNBs. In addition, for example,donor eNB 102 can communicate with other relay eNBs to allow communications therebetween over the access network (e.g., relayeNB 104 can communicate with one or more additional relay eNBs connected to donor eNB 102). - According to an example, relay
eNBs donor eNB 102 can communicate over a relay protocol layer, which can be communicated over a packet data convergence protocol (PDCP) layer and can carry upper layer protocols. For example, communications over the relay protocol layer can utilize a header, which can include a field to indicate the upper layer protocol or interface type (e.g., S1-U, S1-MME, X2, another transport or application protocol, etc.) in the relay protocol packet payload, a destination or source relay eNB identifier, an internet protocol (IP) address related to a destination network node (e.g., MME, serving gateway (SGW), etc.), and/or the like. In one example, relayeNB 108 can request relay identifier assignment fromdonor eNB 102 viarelay eNB 104.Donor eNB 102 can assign a relay identifier to therelay eNB 108 unique to the cluster provided bydonor eNB 102, and provide the relay identifier to relayeNB 108 through one or more intermediary relay nodes, such asrelay eNB 104.Donor eNB 102 and the intermediary relay nodes can create a routing table that associates the relay identifier to an identifier of a next downstream relay eNB (e.g., a related cell radio network temporary identifier (C-RNTI)), for example. Subsequent routing of packets fromcore network 106 to relayeNB 108 can be based at least in part on determining identifiers of next hop relay eNBs associated with the relay identifier in respective routing tables. - In an example, relay
eNB 108 can subsequently communicate withrelay eNB 104 over a relay protocol, which can carry upper layer protocol data. A header for communications over the relay protocol can include the type of the upper layer protocol, an identifier forrelay eNB 108, and a destination IP address for a node incore network 106, where applicable.Relay eNB 104 can forward the relay protocol communication todonor eNB 102, anddonor eNB 102 can determine the type of upper layer protocol, formulate the appropriate transport layer packet, include the relay identifier in the packet, and transmit the packet to the appropriate node incore network 106; this can be based at least in part on the IP address if present, the upper layer protocol type, and/or the like. - Upon receiving a response or other related communication from
core network 106,donor eNB 102 can obtain the relay identifier from the communication. In addition,donor eNB 102 can establish a relay protocol layer for communication withrelay eNB 104 in place of a transport layer (e.g., user datagram protocol (UDP)/IP) utilized in communicating withcore network 106 and generate a related relay protocol header.Donor eNB 102 can populate the header with a relay identifier forrelay eNB 108, a protocol type for the application layer carried by the relay protocol, and/or the like, and attach the header to the application layer communication fromcore network 106.Donor eNB 102 can determine a next hop relay eNB from the routing table, described previously, by locating the relay identifier in the routing table and obtaining the related next hop relay eNB identifier.Donor eNB 102 can then transmit the relay protocol communication to the next hop relay, relayeNB 104, based at least in part on the identifier thereof in the routing table.Relay eNB 104 can receive the communication, extract the relay identifier, and forward the communication to relayeNB 108 based at least in part on locatingrelay eNB 108 as the next hop in a routing table, for example.Relay eNB 108 can receive the packet over the relay protocol and process that data. Where the data relates to a UE or other device communicating with therelay eNB 108, relayeNB 108 can forward at least a portion of the packet thereto. - Turning now to
FIG. 2 , an examplewireless communication system 200 that facilitates communicating among eNBs using a relay protocol is illustrated.System 200 includes adonor eNB 102 that provides relay eNB 104 (and/or other relay eNBs) with access tocore network 106. Additionally, as described,relay eNB 104 can providerelay eNB 108 with access to thecore network 106 through thedonor eNB 102. In an example, however, relayeNB 104 may not be present, and relayeNB 108 can communicate directly withdonor eNB 102. In a similar example, there can bemultiple relay eNBs 104 between thedonor eNB 102 and relayeNB 108. In addition, it is to be appreciated thatrelay eNB 108 can comprise the components ofrelay eNB 104 and provide similar functionality, in one example. Moreover,donor eNB 102 can be a macrocell access point, femtocell access point, picocell access point, mobile base station, and/or the like. Relay eNBs 104 (and relay eNB 108) can similarly be mobile or stationary relay nodes that communicate with donor eNB 102 (and relay eNB 104) over a wireless or wired backhaul, as described. -
Donor eNB 102 comprises an identifierrequest receiving component 202 that obtains a relay identifier assignment request from one or more relay eNBs, a relayidentifier assigning component 204 that selects a relay identifier for the one or more relay eNBs, arouting table component 206 that stores associations between assigned relay identifiers and identifiers of next hop relay eNBs to reach the relay eNB related to the relay identifier, abackhaul link component 208 that communicates withcore network 106 over a transport layer, and arelay protocol component 210 that communicates with relay eNBs over a disparate transport layer. -
Relay eNB 104 can include an identifierrequest receiving component 212 that obtains a request for a relay identifier from a downstream eNB and forwards the request to an upstream eNB, a relayidentifier receiving component 214 that obtains a relay identifier for a downstream eNB from one or more upstream eNBs and provides the relay identifier to a next hop downstream eNB, arouting table component 216 that stores an association between the relay identifier and an identifier of the next hop downstream eNB, and a relayprotocol forwarding component 218 that establishes and communicates over a relay protocol to one or more eNBs. -
Relay eNB 108 comprises anidentifier requesting component 220 that transmits a request for a relay identifier to one or more upstream eNBs, a relayidentifier receiving component 222 that obtains a relay identifier from the one or more upstream eNBs, arelay protocol component 224 that establishes and communicates over a relay protocol connection with one or more upstream eNBs, and apacket routing component 226 that communicates data received over a relay protocol to one or more UEs or other devices. - According to an example,
identifier requesting component 220 can formulate a request for a relay identifier for communicating with other relay or donor eNBs over a relay protocol in a wireless network.Identifier requesting component 220 can transmit the request to relayeNB 104, if present, ordonor eNB 102 ifrelay eNB 104 is not present. Whererelay eNB 104 is present, identifierrequest receiving component 212 can obtain the request fromrelay eNB 108 and forward the request upstream todonor eNB 102. It is to be appreciated, in one example, that there can be multiple relay eNBs in the communication chain fromrelay eNB 108 todonor eNB 102, and the multiple relay eNBs can similarly receive and forward the request. - In any case, identifier
request receiving component 202 can obtain the request for relay identifier assignment. Relayidentifier assigning component 204 can select a relay identifier forrelay eNB 108. The selection can conform to one or more specification details, such as size, character set, etc., and can be unique within the cluster served bydonor eNB 102.Routing table component 206 can store an association between the relay identifier and an identifier of next hop eNB (eNB 104 if present, oreNB 108 ifeNB 104 is not present), and relayidentifier assigning component 204 can provide the relay identifier to the next hop eNB. Ifrelay eNB 104 is present, relayidentifier receiving component 214 can obtain the relay identifier forrelay eNB 108, and routing table can store an association between the relay identifier and an identifier for the next hop relay eNB (relay eNB 108 in this example). It is to be appreciated that, where multiple relay eNBs exist in the communication chain betweenrelay eNB 108 anddonor eNB 102, each of the multiple relay eNBs can receive the relay identifier assignment, store an association to a next hop relay eNB in a routing table, and forward the relay identifier assignment to the next hop relay eNB. - In any case, relay
identifier receiving component 222 can obtain and store the relay identifier.Relay protocol component 224 can subsequently generate relay protocol layer communications to relayeNB 104, if present, ordonor eNB 102 ifrelay eNB 104 is not present. In one example,relay protocol component 224 can generate the relay protocol layer communications in response to receiving a request or other communications fromUE 110 or another device.Relay protocol component 224 can create a relay protocol packet comprising a relay protocol header and a payload, which can comprise upper layer protocol data (e.g., S1-U, S1-MME, X2 data and/or the like). In addition,relay protocol component 224 can populate the header with the relay identifier, a protocol type of upper layer protocol data in the payload, an optional destination IP address (e.g., of an MME or SGW in the core network 106), and can transmit the relay protocol packet to relayeNB 104, if present, ordonor eNB 102 ifrelay eNB 104 is not present. - Relay
protocol forwarding component 218 can receive the relay protocol communications fromrelay eNB 108, ifrelay eNB 104 is present, and can forward the communications todonor eNB 102 over the relay protocol. Similarly, if multiple relay eNBs are in the communication path betweenrelay eNB 108 anddonor eNB 102, each of the multiple relay eNBs can similarly receive and forward the relay protocol communications to the next upstream relay eNB.Relay protocol component 210 can receive the communications over the relay protocol fromrelay eNB 104 or relayeNB 108 and can obtain the relay identifier from the relay protocol header.Backhaul link component 208 can generate a communication forcore network 106 over a disparate transport layer, indicate the relay identifier in the communication, and transmit the communication to thecore network 106, for example. The disparate transport layer can be a UDP/IP layer and/or the like, for example. -
Backhaul link component 208 can receive a response or other communication related to relayeNB 108 fromcore network 106.Backhaul link component 208 can obtain the relay identifier from the communication, androuting table component 206 can determine a next hop relay eNB based on the relay identifier, as described.Relay protocol component 210 can generate a relay protocol packet comprising a header and payload, which can be the upper layer protocol data received fromcore network 106 by backhaul link component 208 (e.g., S1-U, S1-MME, or X2 data).Relay protocol component 210 can set the relay identifier field in the header to be the relay identifier ofrelay eNB 108 and the protocol type to indicate the type of upper layer protocol data in the payload.Relay protocol component 210 can transmit the relay protocol packet to the next hop relay eNB determined by the routing table component 206 (e.g., relayeNB 104 if present, or relayeNB 108 ifrelay eNB 104 is not present, in this example). - If
relay eNB 104 is present, relayprotocol forwarding component 218 can receive the packet fromdonor eNB 102 and can obtain the relay identifier in the relay protocol packet header.Routing table component 216 can determine the next hop relay eNB by locating the relay identifier in the routing table and retrieving the associated next hop relay eNB identifier. Relayprotocol forwarding component 218 can forward the relay protocol packet to the next hop relay eNB. Where additional relay eNBs exist in the communication chain betweenrelay eNB 108 anddonor eNB 102, the additional relay eNBs can similarly receive the relay protocol packet, determine the relay identifier, discern a next hop relay eNB based on the relay identifier, and forward the packet to the next hop eNB. -
Relay protocol component 224 can receive the relay protocol packet fromrelay eNB 104, if present, ordonor eNB 102 ifrelay eNB 104 is not present, and can determine the upper layer protocol message type from the relay protocol header. For example, where the upper layer protocol type is a S1-U, S1-MME, or other message relating to a communication fromUE 110 or another device,packet routing component 226 can forward the payload of the relay protocol message toUE 110 or other related device; this can be based on a previously created routing table, in one example. Where the protocol type is X2 or another message relating to eNB communications, relayeNB 108 can process the message. In one example, the relay protocol header can have a format similar to the following. -
Protocol (3 bits) I (1 bit) Reserved (4 bits) Relay ID (16 bits) Destination IP Address (optional)
In this format, for example, the protocol field, as described, can relate to an upper layer protocol type for the payload data in the packet, the I (indicator) field can specify whether the destination IP address is present, the reserved field can be reserved for additional data, the relay ID field can store the relay identifier described above, and the destination IP field can hold an IP address for a destination SGW, MME, etc. (e.g., in uplink packets). It is to be appreciated that this is but one example of a relay packet header; substantially limitless formats are possible. - Turning now to
FIG. 3 , an examplewireless communication system 300 that facilitates providing a relay protocol for a single tier relay node wireless network implementation is illustrated.System 300 includes adonor eNB 102 that provides relay eNB 108 (and/or other relay eNBs) with access tocore network 106. Moreover,donor eNB 102 can be a macrocell access point, femtocell access point, picocell access point, mobile base station, and/or the like.Relay eNB 108 can similarly be mobile or stationary relay nodes that communicate withdonor eNB 102 over a wireless or wired backhaul, as described. -
Donor eNB 102 comprises abackhaul link component 208 that communicates withcore network 106 over a transport layer and arelay protocol component 210 that communicates with relay eNBs over a disparate transport layer.Relay eNB 108 comprises arelay protocol component 224 that establishes and communicates over a relay protocol connection with one or more upstream eNBs and apacket routing component 226 that communicates data received over a relay protocol to one or more UEs or other devices. - According to an example,
relay protocol component 224 can generate a communication for one ormore core network 106 components (e.g., a SGW, MME, disparate eNB, and/or the like) along with a relay protocol packet for the communication. This can be based on receiving a communication fromUE 110, in one example.Relay protocol component 224 can populate a relay identifier field in the relay protocol header with a C-RNTI ofrelay eNB 108, which is unique in the cluster provided bydonor eNB 102 where only one tier of relay eNBs are attached to donor eNB 102 (e.g., there is only one relay eNB between end devices, such as UEs, and donor eNB 102). In this regard, no identifier requesting process is needed. -
Relay protocol component 224 can transmit the relay protocol packet todonor eNB 102, andrelay protocol component 210 can receive the packet.Relay protocol component 210 can additionally extract the relay identifier.Backhaul link component 208 can generate a packet over a disparate transport layer (e.g., UDP/IP layer) for transmission tocore network 106.Backhaul link component 208 can also include the relay identifier (C-RNTI) in the packet and transmit the packet tocore network 106. In addition,backhaul link component 208 can receive a response to the packet or other communication fromcore network 106 over the disparate transport layer. Backhaul link component can extract a relay identifier from the packet, for example.Relay protocol component 210 can generate a relay protocol packet with application layer data from the packet received over the backhaul link as the payload.Relay protocol component 210 can transmit the packet to relayeNB 108 based on the relay identifier (C-RNTI). Thus, no routing table is needed in this example either.Relay protocol component 224 can receive the packet and can communicate the payload toUE 110 usingpacket routing component 226, as described, where applicable. - Referring to
FIG. 4 , an examplerelay protocol component 400 is depicted in accordance with various aspects described herein. For example,relay protocol component 400 can be similar torelay protocol components Relay protocol component 400 can include a relayprotocol communicating component 402 that receives and transmits data over a relay protocol, a relay protocolheader reading component 404 that obtains one or more field values from a relay protocol header, a relay protocolpacket generating component 406 that creates a relay protocol packet for transmitting to one or more eNBs, and a relay protocolheader populating component 408 that initializes one or more fields in a relay protocol header. - According to an example, as described, relay
protocol communicating component 402 can receive a relay protocol packet from one or more eNBs, and relay protocolheader reading component 404 can extract one or more field values from the header, such as protocol type, relay identifier, destination IP address, and/or the like, as described. Other components, as described, can utilize the information to process payload of the relay protocol packet, route the packet, and/or the like. In another example, relay protocolpacket generating component 406 can create relay protocol packets for transmitting to one or more eNBs, as described. In addition, the relay protocolpacket generating component 406 can insert an upper layer protocol message in the payload of the relay protocol packet. Moreover, as described previously, the relay protocolheader populating component 408 can set field values in the relay protocol header. Relayprotocol communicating component 402 can transmit the relay protocol packet to one or more eNBs. - Now turning to
FIG. 5 , an examplewireless communication network 500 that provides cell relay functionality is depicted.Network 500 includes aUE 110 that communicates with arelay eNB 104, as described, to receive access to a wireless network.Relay eNB 104 can communicate with adonor eNB 102 using a relay protocol to provide access to a wireless network, and as described,donor eNB 102 can communicate with anMME 502 and/orSGW 504 that relate to therelay eNB 104.SGW 504 can connect to or be coupled with aPGW 506, which provides network access toSGW 504 and/or additional SGWs.PGW 506 can communicate with aPCRF 508 to authenticate/authorizeUE 110 to use the network, which can utilize anIMS 510 to provide addressing to theUE 110 and/or relayeNB 104. - According to an example,
MME 502 and/orSGW 504 andPGW 506 can be related todonor eNB 102 serving substantially all relay eNBs in the cluster.Donor eNB 102 can also communicate with anSGW 516 andPGW 518 that relate to theUE 110, such that thePGW 518 can assign UE 110 a network address to facilitate tunneling communications thereto through therelay eNB 104,donor eNB 102, andSGW 516. Moreover, for example,SGW 516 can communicate with anMME 514 to facilitate control plane communications to and from theUE 110. It is to be appreciated thatMME 502 andMME 514 can be the same MME, in one example.PGW 518 can similarly communicate with aPCRF 508 to authenticate/authorizeUE 110, which can communicate with anIMS 510. In addition,PGW 518 can communicate directly with theIMS 510 and/orinternet 512. - In an example,
UE 110 can communicate with therelay eNB 104 over an E-UTRA-Uu interface, as described, and therelay eNB 104 can communicate with thedonor eNB 102 using an E-UTRA-Uu interface or other interface using the relay protocol, as described herein.Donor eNB 102 communicates with theMME 502 using an S1-MME interface and theSGW 504 andPGW 506 over an S1-U interface, as depicted. In addition, as described, communications received fromrelay eNB 104 forMME 502 orSGW 504/PGW 506 can be over a relay protocol and can have an IP address ofMME 502 orSGW 504/PGW 506 in the relay protocol header.Donor eNB 102 can appropriately route the packet according to the IP address and/or payload type of the relay protocol. In addition, the transport layers used over the S1-MME and S1-U interfaces are terminated at thedonor eNB 102, as described. In this regard, upon receiving communications for therelay eNB 104 from theMME 502 orSGW 504,donor eNB 102 decouples the application layer from the transport layer by defining a new relay protocol packet and transmitting the application layer communication to therelay eNB 104 in the new relay protocol packet (over the E-UTRA-Uu interface, in one example). - Upon transmitting control plane communications from the
relay eNB 104 to theMME 502,donor eNB 102 can indicate an identifier of the relay eNB 104 (e.g., in an S1-AP message), andMME 502 can transmit the identifier in responding communications to thedonor eNB 102. When transmitting data plane communications fromrelay eNB 104 toSGW 504,donor eNB 102 can insert an identifier for the relay eNB 104 (orUE 110 or one or more related bearers) in the TEID of a general packet radio service (GPRS) tunneling protocol (GTP)-U header to identify the relay eNB 104 (orUE 110 or one or more related bearers). This can be an identifier generated forrelay eNB 104 bydonor eNB 102 such thatdonor eNB 102 can determine therelay eNB 104, or one or more downstream relay eNBs is to receive the translated packet, as described above. For example, this can be based at least in part on locating at least a portion of the identifier in a routing table atdonor eNB 102. In addition, headers can be compressed, in one example, as described. As shown,MME 502 can communicate withSGW 504, andMME 514 toSGW 516, using an S11 interface.PGWs PCRF 508 over a Gx interface. Furthermore,PCRF 508 can communicate withIMS 510 using an Rx interface, andPGW 518 can communicate withIMS 510 and/or theinternet 512 using an SGi interface. - Referring to
FIG. 6 , example protocol stacks 600 are illustrated that facilitate communicating in a wireless network to provide cell relay functionality for data (e.g., user) plane communications. AUE protocol stack 602 is shown comprising an L1 layer, MAC layer, an RLC layer, a PDCP layer, and an IP layer. A relay eNB1 (ReNB) accesslink protocol stack 604 is depicted having an L1 layer, MAC layer, RLC layer, and PDCP layer, as well as an ReNB1 backhaullink protocol stack 606 having an L1 layer, MAC layer, RLC layer, PDCP layer, relay protocol (RP) layer, and a C-GTP-U/UDP/IP layer, which can be a compressed or uncompressed layer in one example, to facilitate communicating packets on the backhaul. An intermediary ReNB2 accesslink protocol stack 608 is shown having an L1 layer, MAC layer, RLC layer, PDCP layer, and RP layer, as well as a backhaullink protocol stack 610 for the intermediary ReNB2 having the same layers. - A CeNB access
link protocol stack 608 is also shown having an L1 layer, MAC layer, RLC layer, PDCP layer, RP layer, and a C-GTP/UDP/IP layer, as well as a CeNB backhaullink protocol stack 610 having an L1 layer, L2 layer, a UDP/IP layer, and a GTP-U layer to maintain communications with a PGW/SGW using an address assigned by the PGW/SGW. PGW/SGW protocol stack 612 has an L1 layer, L2, layer, UDP/IP layer related to an address assigned to the CeNB, GTP-U layer, and another IP layer related to an address assigned to the UE. - According to an example, a UE can communicate with an ReNB1 to receive access to a PGW/SGW. In this regard, UE can communicate over L1, MAC, RLC, and PDCP layers with the ReNB1 over using a EUTRA-Uu interface, as shown between
protocol stacks protocol stacks protocol stacks protocol stacks - ReNB2, and any other intermediary ReNBs, can forward the RP communication to the CeNB, as shown between protocol stack s 610 and 612. In this example, CeNB can receive the RP packet, over the lower layers, and can extract the C-GTP-U/UDP/IP packet from the payload and communicate with the PGW over separate GTP-U, UDP, and IP layers on top of L1 and L2 physical layers over an S1-U interface, as shown between
protocol stacks SGW protocol stack 612 can include the relay identifier. In this regard, upon receiving downlink communications from PGW/SGW protocol stack 616 over CeNB backhaullink protocol stack 614, CeNB accesslink protocol stack 612 can generate an RP packet with a header comprising the relay identifier received over PGW/SGW protocol stack 616 and a compressed GTP-U/UDP/IP packet as the payload. CeNB accesslink protocol stack 612 can transmit the RP packet over ReNB2 backhaullink protocol stack 612, which can forward the RP packet over ReNB2 accesslink protocol stack 608 to ReNB backhaullink protocol stack 606 based on the relay identifier in the RP header, as described. ReNB1 backhaullink protocol stack 606 can obtain the C-GTP-U/UDP/IP payload of the RP packet and forward toUE protocol stack 602, where the RP packet payload is of certain types, as described. - Referring to
FIGS. 7-11 , methodologies relating to providing a relay protocol in relay node communications are illustrated. While, for purposes of simplicity of explanation, the methodologies are shown and described as a series of acts, it is to be understood and appreciated that the methodologies are not limited by the order of acts, as some acts may, in accordance with one or more aspects, occur in different orders and/or concurrently with other acts from that shown and described herein. For example, those skilled in the art will understand and appreciate that a methodology could alternatively be represented as a series of interrelated states or events, such as in a state diagram. Moreover, not all illustrated acts may be required to implement a methodology in accordance with one or more aspects. - Referring to
FIG. 7 , amethodology 700 is shown that facilitates transmitting upstream relay protocol packets with relay identifiers. At 702, a relay protocol packet can be generated comprising an upper layer protocol payload. For example, the relay protocol packet can be created based at least in part on receiving a request or other communication from a UE. In addition, the upper layer protocol payload can be the communication from the UE, which can be a S1-U, S1-MME, or similar protocol communication. In another example, the upper layer protocol payload can be an X2 protocol communication. At 704, a header of the relay protocol packet can be populated with a relay identifier. This can be an identifier previously received from a donor eNB, a C-RNTI, and/or the like, as described. At 706, the relay protocol packet can be transmitted. In one example, the packet can be transmitted to an upstream relay node to eventually reach a donor eNB. The donor eNB can utilize the relay identifier, as described herein, to associate response data to the transmitted packet. In another example, a destination IP address can be specified in the header, as described, to facilitate routing the packet to a certain core network component via the donor eNB. - Turning to
FIG. 8 , anexample methodology 800 that facilitates receiving relay protocol packets from upstream relay or donor nodes is illustrated. At 802, a downstream relay protocol packet can be received. For example, the relay protocol can be received from an upstream relay or donor node. At 804, a type of an upper layer protocol payload of the relay protocol packet can be determined. In one example, the type can be specified in a header of the relay protocol packet, and thus can be determined by obtaining the type field from the header. At 806, the upper layer protocol payload can be processed according to the type. For example, if the upper layer protocol type is S1-U or S1-MME, the payload can be transmitted to a related UE. If the upper layer protocol type is X2, however, the payload can be processed locally, in an example. - Referring to
FIG. 9 , anexample methodology 900 is shown that facilitates forwarding relay protocol packets among eNBs based on a relay identifier in the header of the relay protocol packets. At 902, a relay protocol packet comprising a relay identifier can be received. As described, the packet can be received from an upstream node, such as a donor eNB or a disparate relay eNB. A relay node to receive the relay protocol packet can be determined based at least in part on the relay identifier, at 904. As described, this step can include consulting a routing table to determine a next hop relay node relating to the relay identifier. The association can have been stored during an initial request for the relay identifier from a downstream relay node. At 906, the relay protocol packet can be forwarded to the relay node. - Turning to
FIG. 10 , anexample methodology 1000 that facilitates communicating relay protocol data to a core network is illustrated. At 1002, a relay protocol packet comprising an upper layer protocol payload and a relay identifier is received. The relay protocol packet can be received from a downstream relay node, as described. At 1004, a type of the upper layer protocol payload can be determined. In one example, the type can relate to an S1-U, S1-MME, X2, or similar protocol. At 1006, the upper layer protocol payload can be transmitted over a disparate transport layer along with the relay identifier. Thus, for example, the payload can be transmitted over a backhaul link to a core network over a UDP/IP or other transport protocol. Depending on the type of the upper layer protocol payload, for example, the packet can be transmitted to different core network components (e.g., an SGW for S1-U payload, MME for S1-MME payload, a disparate eNB for X2 payload, etc.). - Referring to
FIG. 11 , anexample methodology 1100 is shown that facilitates routing downstream packets from a core network to one or more relay nodes. At 1102, a communication can be received from a core network component comprising a relay identifier. A relay protocol packet can be generated including the communication as the payload at 1104. Using the relay protocol, as described, facilitates routing of the packets to one or more relay nodes, for example. At 1106, the relay protocol packet header can be populated with the relay identifier. Subsequent relay nodes, as described, can utilize the relay identifier to determine next hop relay nodes for the relay protocol packet. At 1108, a next hop relay node can be determined. In an example, this can be determined based at least in part on querying a routing table to locate an association between the relay identifier and an identifier of the next hop relay node, as described herein. At 1110, the relay protocol packet can be transmitted to the next hop relay node. - It will be appreciated that, in accordance with one or more aspects described herein, inferences can be made regarding generating a relay protocol packet, such as whether to include a destination IP address, etc., generating a relay identifier unique to a cluster, determining next hop relay eNBs, and/or other aspects described herein. As used herein, the term to “infer” or “inference” refers generally to the process of reasoning about or inferring states of the system, environment, and/or user from a set of observations as captured via events and/or data. Inference can be employed to identify a specific context or action, or can generate a probability distribution over states, for example. The inference can be probabilistic—that is, the computation of a probability distribution over states of interest based on a consideration of data and events. Inference can also refer to techniques employed for composing higher-level events from a set of events and/or data. Such inference results in the construction of new events or actions from a set of observed events and/or stored event data, whether or not the events are correlated in close temporal proximity, and whether the events and data come from one or several event and data sources.
- Referring now to
FIG. 12 , awireless communication system 1200 is illustrated in accordance with various embodiments presented herein.System 1200 comprises abase station 1202 that can include multiple antenna groups. For example, one antenna group can includeantennas antennas antennas Base station 1202 can additionally include a transmitter chain and a receiver chain, each of which can in turn comprise a plurality of components associated with signal transmission and reception (e.g., processors, modulators, multiplexers, demodulators, demultiplexers, antennas, etc.), as will be appreciated by one skilled in the art. -
Base station 1202 can communicate with one or more mobile devices such asmobile device 1216 andmobile device 1222; however, it is to be appreciated thatbase station 1202 can communicate with substantially any number of mobile devices similar tomobile devices Mobile devices wireless communication system 1200. As depicted,mobile device 1216 is in communication withantennas antennas mobile device 1216 over aforward link 1218 and receive information frommobile device 1216 over areverse link 1220. Moreover,mobile device 1222 is in communication withantennas antennas mobile device 1222 over aforward link 1224 and receive information frommobile device 1222 over areverse link 1226. In a frequency division duplex (FDD) system,forward link 1218 can utilize a different frequency band than that used byreverse link 1220, andforward link 1224 can employ a different frequency band than that employed byreverse link 1226, for example. Further, in a time division duplex (TDD) system,forward link 1218 andreverse link 1220 can utilize a common frequency band andforward link 1224 andreverse link 1226 can utilize a common frequency band. - Each group of antennas and/or the area in which they are designated to communicate can be referred to as a sector of
base station 1202. For example, antenna groups can be designed to communicate to mobile devices in a sector of the areas covered bybase station 1202. In communication overforward links base station 1202 can utilize beamforming to improve signal-to-noise ratio offorward links mobile devices base station 1202 utilizes beamforming to transmit tomobile devices mobile devices - According to an example,
system 1200 can be a multiple-input multiple-output (MIMO) communication system. Further,system 1200 can utilize substantially any type of duplexing technique to divide communication channels (e.g., forward link, reverse link, . . . ) such as FDD, FDM, TDD, TDM, CDM, and the like. In addition, communication channels can be orthogonalized to allow simultaneous communication with multiple devices over the channels; in one example, OFDM can be utilized in this regard. Thus, the channels can be divided into portions of frequency over a period of time. In addition, frames can be defined as the portions of frequency over a collection of time periods; thus, for example, a frame can comprise a number of OFDM symbols. Thebase station 1202 can communicate to themobile devices -
FIG. 13 shows an examplewireless communication system 1300. Thewireless communication system 1300 depicts onebase station 1310 and onemobile device 1350 for sake of brevity. However, it is to be appreciated thatsystem 1300 can include more than one base station and/or more than one mobile device, wherein additional base stations and/or mobile devices can be substantially similar or different fromexample base station 1310 andmobile device 1350 described below. In addition, it is to be appreciated thatbase station 1310 and/ormobile device 1350 can employ the systems (FIGS. 1-5 and 12), protocol stacks (FIG. 6 ) and/or methods (FIGS. 7-11 ) described herein to facilitate wireless communication therebetween. - At
base station 1310, traffic data for a number of data streams is provided from adata source 1312 to a transmit (TX)data processor 1314. According to an example, each data stream can be transmitted over a respective antenna.TX data processor 1314 formats, codes, and interleaves the traffic data stream based on a particular coding scheme selected for that data stream to provide coded data. - The coded data for each data stream can be multiplexed with pilot data using orthogonal frequency division multiplexing (OFDM) techniques. Additionally or alternatively, the pilot symbols can be frequency division multiplexed (FDM), time division multiplexed (TDM), or code division multiplexed (CDM). The pilot data is typically a known data pattern that is processed in a known manner and can be used at
mobile device 1350 to estimate channel response. The multiplexed pilot and coded data for each data stream can be modulated (e.g., symbol mapped) based on a particular modulation scheme (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM), etc.) selected for that data stream to provide modulation symbols. The data rate, coding, and modulation for each data stream can be determined by instructions performed or provided byprocessor 1330. - The modulation symbols for the data streams can be provided to a
TX MIMO processor 1320, which can further process the modulation symbols (e.g., for OFDM).TX MIMO processor 1320 then provides NT modulation symbol streams to NT transmitters (TMTR) 1322 a through 1322 t. In various aspects,TX MIMO processor 1320 applies beamforming weights to the symbols of the data streams and to the antenna from which the symbol is being transmitted. - Each transmitter 1322 receives and processes a respective symbol stream to provide one or more analog signals, and further conditions (e.g., amplifies, filters, and upconverts) the analog signals to provide a modulated signal suitable for transmission over the MIMO channel. Further, NT modulated signals from
transmitters 1322 a through 1322 t are transmitted from NT antennas 1324 a through 1324 t, respectively. - At
mobile device 1350, the transmitted modulated signals are received by NR antennas 1352 a through 1352 r and the received signal from each antenna 1352 is provided to a respective receiver (RCVR) 1354 a through 1354 r. Each receiver 1354 conditions (e.g., filters, amplifies, and downconverts) a respective signal, digitizes the conditioned signal to provide samples, and further processes the samples to provide a corresponding “received” symbol stream. - An
RX data processor 1360 can receive and process the NR received symbol streams from NR receivers 1354 based on a particular receiver processing technique to provide NT “detected” symbol streams.RX data processor 1360 can demodulate, deinterleave, and decode each detected symbol stream to recover the traffic data for the data stream. The processing byRX data processor 1360 is complementary to that performed byTX MIMO processor 1320 andTX data processor 1314 atbase station 1310. - A
processor 1370 can periodically determine which precoding matrix to utilize as discussed above. Further,processor 1370 can formulate a reverse link message comprising a matrix index portion and a rank value portion. - The reverse link message can comprise various types of information regarding the communication link and/or the received data stream. The reverse link message can be processed by a
TX data processor 1338, which also receives traffic data for a number of data streams from adata source 1336, modulated by amodulator 1380, conditioned bytransmitters 1354 a through 1354 r, and transmitted back tobase station 1310. - At
base station 1310, the modulated signals frommobile device 1350 are received by antennas 1324, conditioned by receivers 1322, demodulated by ademodulator 1340, and processed by aRX data processor 1342 to extract the reverse link message transmitted bymobile device 1350. Further,processor 1330 can process the extracted message to determine which precoding matrix to use for determining the beamforming weights. -
Processors base station 1310 andmobile device 1350, respectively.Respective processors memory Processors - It is to be understood that the aspects described herein can be implemented in hardware, software, firmware, middleware, microcode, or any combination thereof. For a hardware implementation, the processing units can be implemented within one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, micro-controllers, microprocessors, other electronic units designed to perform the functions described herein, or a combination thereof.
- When the aspects are implemented in software, firmware, middleware or microcode, program code or code segments, they can be stored in a machine-readable medium, such as a storage component. A code segment can represent a procedure, a function, a subprogram, a program, a routine, a subroutine, a module, a software package, a class, or any combination of instructions, data structures, or program statements. A code segment can be coupled to another code segment or a hardware circuit by passing and/or receiving information, data, arguments, parameters, or memory contents. Information, arguments, parameters, data, etc. can be passed, forwarded, or transmitted using any suitable means including memory sharing, message passing, token passing, network transmission, etc.
- For a software implementation, the techniques described herein can be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described herein. The software codes can be stored in memory units and executed by processors. The memory unit can be implemented within the processor or external to the processor, in which case it can be communicatively coupled to the processor via various means as is known in the art.
- With reference to
FIG. 14 , illustrated is asystem 1400 that facilitates communicating relay protocol packets to/from upstream relay or donor nodes. For example,system 1400 can reside at least partially within a base station, mobile device, etc. It is to be appreciated thatsystem 1400 is represented as including functional blocks, which can be functional blocks that represent functions implemented by a processor, software, or combination thereof (e.g., firmware).System 1400 includes alogical grouping 1402 of electrical components that can act in conjunction. For instance,logical grouping 1402 can include an electrical component for generating arelay protocol packet 1404. For example, as described, this can be in response to a communication from a UE, and the payload of the packet can be the communication from the UE. Additionally,logical grouping 1402 can include an electrical component for inserting a relay identifier in a header of therelay protocol packet 1406. Thus, for example, the header can be subsequently used to identify thesource system 1400 of the packet. Moreover,logical grouping 1402 can include an electrical component for communicating the relay protocol packet to one or more eNBs in awireless network 1408. -
Electrical component 1408 can additionally receive a disparate relay protocol packet, for example, in response or related to the communicated packet. In this regard,logical grouping 1402 can include an electrical component for determining a type of an upper layer protocol corresponding to a payload of a disparaterelay protocol packet 1410. Moreover,logical grouping 1402 can include an electrical component for providing the payload of the relay protocol packet to a UE based at least in part on the type of theupper layer protocol 1412. For example, if the type is S1-U, S1-MME, or a similar type,electrical component 1412 can provide the upper layer protocol payload to the UE. Furthermore,logical grouping 1402 includes an electrical component for receiving the relay identifier from thedonor eNB 1414. In addition,logical grouping 1402 includes an electrical component for requesting the relay identifier from thedonor eNB 1416. Additionally,system 1400 can include amemory 1418 that retains instructions for executing functions associated withelectrical components memory 1418, it is to be understood that one or more ofelectrical components memory 1418. - With reference to
FIG. 15 , illustrated is asystem 1500 that facilitates forwarding relay protocol packets based on a relay identifier comprised within packet headers. For example,system 1500 can reside at least partially within a base station, mobile device, etc. It is to be appreciated thatsystem 1500 is represented as including functional blocks, which can be functional blocks that represent functions implemented by a processor, software, or combination thereof (e.g., firmware).System 1500 includes alogical grouping 1502 of electrical components that can act in conjunction. For instance,logical grouping 1502 can include an electrical component for storing a relay identifier along with an identifier of a nexthop relay eNB 1504. For example, as described, this can be performed upon receiving a relay identifier assignment from an upstream node for a downstream node (e.g., the downstream node can be the next hop node). Moreover,logical grouping 1502 can include an electrical component for forwarding a relay protocol packet to the next hop relay eNB based at least in part on locating a relay identifier extracted from the relay protocol packet in the electrical component for storing 1506. Thus, the identifier for the next hop node can be determined and packet forwarded thereto, as described. Additionally,system 1500 can include amemory 1508 that retains instructions for executing functions associated withelectrical components memory 1508, it is to be understood that one or more ofelectrical components memory 1508. - With reference to
FIG. 16 , illustrated is asystem 1600 that facilitates communicating relay protocol packets to/from downstream relay nodes. For example,system 1600 can reside at least partially within a base station, mobile device, etc. It is to be appreciated thatsystem 1600 is represented as including functional blocks, which can be functional blocks that represent functions implemented by a processor, software, or combination thereof (e.g., firmware).System 1600 includes alogical grouping 1602 of electrical components that can act in conjunction. For instance,logical grouping 1602 can include an electrical component for receiving a relay protocol packet comprising an upper layer protocol payload and arelay identifier 1604. For example, as described, the packet can be received from a downstream relay node for communicating to a core network. Additionally,logical grouping 1602 can include an electrical component for determining a type of the upperlayer protocol payload 1606. This can facilitate determining a recipient of the payload, as described (e.g., S1-U payload can go to an SGW, S1-MME to an MME, etc.). Moreover,logical grouping 1602 can include an electrical component for communicating the upper layer protocol payload along with the relay identifier to a core network component over adisparate transport layer 1608. - Thus, for example, the payload can be transmitted over a UDP/IP layer. In addition,
logical grouping 1602 can include an electrical component for generating a disparate relay protocol packet including a communication as thepayload 1610. In this regard, for example,electrical component 1608 can also receive communications from the core network component for transmitting to one or more relay nodes, for which a relay protocol packet can be generated (and the payload can be the communication from the core network component, for example). Moreover,logical grouping 1602 can include an electrical component for determining a next hop relay eNB to receive the disparaterelay protocol packet 1612. As described, this can include searching a routing table to locate the next hop relay eNB identifier (e.g., C-RNTI) related to the relay identifier. In addition,logical grouping 1602 can include an electrical component for inserting the relay identifier in a header of the disparaterelay protocol packet 1614. This allows subsequent downstream relay eNBs to forward the packet on to the relay eNB related to the relay identifier. Additionally,system 1600 can include amemory 1616 that retains instructions for executing functions associated withelectrical components memory 1616, it is to be understood that one or more ofelectrical components memory 1616. - The various illustrative logics, logical blocks, modules, and circuits described in connection with the embodiments disclosed herein may be implemented or performed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but, in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. Additionally, at least one processor may comprise one or more modules operable to perform one or more of the steps and/or actions described above.
- Further, the steps and/or actions of a method or algorithm described in connection with the aspects disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium may be coupled to the processor, such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. Further, in some aspects, the processor and the storage medium may reside in an ASIC. Additionally, the ASIC may reside in a user terminal. In the alternative, the processor and the storage medium may reside as discrete components in a user terminal. Additionally, in some aspects, the steps and/or actions of a method or algorithm may reside as one or any combination or set of codes and/or instructions on a machine readable medium and/or computer readable medium, which may be incorporated into a computer program product.
- In one or more aspects, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage medium may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Also, any connection may be termed a computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and blu-ray disc where disks usually reproduce data magnetically, while discs usually reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.
- While the foregoing disclosure discusses illustrative aspects and/or embodiments, it should be noted that various changes and modifications could be made herein without departing from the scope of the described aspects and/or embodiments as defined by the appended claims. Furthermore, although elements of the described aspects and/or embodiments may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated. Additionally, all or a portion of any aspect and/or embodiment may be utilized with all or a portion of any other aspect and/or embodiment, unless stated otherwise. Furthermore, to the extent that the term “includes” is used in either the detailed description or the claims, such term is intended to be inclusive in a manner similar to the term “comprising” as “comprising” is interpreted when employed as a transitional word in a claim. Furthermore, although elements of the described aspects and/or aspects may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated. Additionally, all or a portion of any aspect and/or embodiment may be utilized with all or a portion of any other aspect and/or embodiment, unless stated otherwise.
Claims (99)
1. A method, comprising:
generating a relay protocol packet comprising an upper layer protocol payload;
populating a header of the relay protocol packet with a relay identifier; and
transmitting the relay protocol packet to one or more evolved Node Bs (eNB) in a wireless network.
2. The method of claim 1 , further comprising:
receiving a downstream relay protocol packet from the one or more eNBs;
determining a type of an upper layer protocol corresponding to a payload of the downstream relay protocol packet; and
processing the payload according to the type of the upper layer protocol.
3. The method of claim 2 , wherein the processing the payload includes providing the payload to a user equipment (UE) based at least in part on the type of the upper layer protocol.
4. The method of claim 3 , wherein the generating the relay protocol packet includes generating the relay protocol packet based on a communication received from the UE.
5. The method of claim 2 , wherein the type of the upper layer protocol is S1-U, S1-MME, X2, or other transport layer or application protocol.
6. The method of claim 1 , further comprising populating the header of the relay protocol packet with a destination address of a serving gateway (SGW) or a mobility management entity (MME).
7. The method of claim 1 , further comprising setting a protocol type value in the header of the relay protocol packet to a type of the upper layer protocol payload.
8. The method of claim 1 , wherein the upper layer protocol payload is a compressed or uncompressed general packet radio service (GPRS) tunneling protocol (GTP)-U/user datagram protocol (UDP)/internet protocol (IP) packet.
9. The method of claim 1 , further comprising receiving the relay identifier in an assignment from a donor eNB.
10. The method of claim 1 , wherein the relay identifier is a received cell radio network temporary identifier (C-RNTI).
11. A wireless communications apparatus, comprising:
at least one processor configured to:
create a relay protocol packet having an upper layer protocol payload;
insert a relay identifier in a header of the relay protocol packet; and
communicate the relay protocol packet to one or more evolved Node Bs (eNB); and
a memory coupled to the at least one processor.
12. The wireless communications apparatus of claim 11 , wherein the at least one processor is further configured to:
receive a disparate relay protocol packet from the one or more eNBs;
discern a type of an upper layer protocol related to a payload of the disparate relay protocol packet.
13. The wireless communications apparatus of claim 12 , wherein the at least one processor is further configured to provide the payload to a user equipment (UE) based at least in part on the type of the upper layer protocol.
14. The wireless communications apparatus of claim 12 , wherein the type of the upper layer protocol is S1-U, S1-MME, X2, or other transport or application protocol.
15. The wireless communications apparatus of claim 11 , wherein the at least one processor creates the relay protocol packet based at least in part on a request from a UE.
16. The wireless communications apparatus of claim 11 , wherein the at least one processor is further configured to insert a destination address of a serving gateway (SGW) or a mobility management entity (MME) in the header.
17. The wireless communications apparatus of claim 11 , wherein the at least one processor is further configured to initialize a protocol type field in the header to a type of the upper layer protocol payload.
18. The wireless communications apparatus of claim 11 , wherein the upper layer protocol payload is a compressed or uncompressed general packet radio service (GPRS) tunneling protocol (GTP)-U/user datagram protocol (UDP)/internet protocol (IP) packet.
19. An apparatus, comprising:
means for generating a relay protocol packet; and
means for inserting a relay identifier in a header of the relay protocol packet; and
means for communicating the relay protocol packet to one or more evolved Node Bs (eNB) in a wireless network.
20. The apparatus of claim 19 , further comprising means for determining a type of an upper layer protocol corresponding to a payload of a disparate relay protocol packet, wherein the means for communicating further receives the disparate relay protocol packet from the one or more eNBs.
21. The apparatus of claim 20 , further comprising means for providing the payload of the disparate relay protocol packet to a user equipment (UE) based at least in part on the type of the upper layer protocol.
22. The apparatus of claim 20 , wherein the type of the upper layer protocol is S1-U, S1-MME, X2, or other transport or application protocol.
23. The apparatus of claim 19 , wherein the means for generating the relay protocol packet generates the relay protocol packet based at least in part on a communication received from a UE.
24. The apparatus of claim 19 , wherein the means for inserting the relay identifier also inserts a destination address of a serving gateway (SGW) or mobility management entity (MME) in the header of the relay protocol packet.
25. The apparatus of claim 19 , wherein the means for inserting the relay identifier also inserts a type of an upper layer protocol payload of the relay protocol packet in the header of the relay protocol packet.
26. The apparatus of claim 25 , wherein the upper layer protocol payload is a compressed or uncompressed general packet radio service (GPRS) tunneling protocol (GTP)-U/user datagram protocol (UDP)/internet protocol (IP) packet.
27. The apparatus of claim 19 , further comprising means for receiving the relay identifier from a donor eNB.
28. The apparatus of claim 27 , further comprising means for requesting the relay identifier from the donor eNB, wherein the means for receiving the relay identifier receives the relay identifier based at least in part on requesting the relay identifier.
29. A computer program product, comprising:
a computer-readable medium comprising:
code for causing at least one computer to generate a relay protocol packet comprising an upper layer protocol payload;
code for causing the at least one computer to populate a header of the relay protocol packet with a relay identifier; and
code for causing the at least one computer to transmit the relay protocol packet to one or more evolved Node Bs (eNB) in a wireless network.
30. The computer program product of claim 29 , wherein the computer-readable medium further comprises:
code for causing the at least one computer to receive a downstream relay protocol packet from the one or more eNBs;
code for causing the at least one computer to determine a type of an upper layer protocol corresponding to a payload of the downstream relay protocol packet; and
code for causing the at least one computer to process the payload according to the type of the upper layer protocol.
31. The computer program product of claim 30 , wherein the code for causing the at least one computer to process the payload provides the payload to a user equipment (UE) based at least in part on the type of the upper layer protocol.
32. The computer program product of claim 31 , wherein the code for causing the at least one computer to generate the relay protocol packet generates the relay protocol packet based on a communication received from the UE.
33. The computer program product of claim 30 , wherein the type of the upper layer protocol is S1-U, S1-MME, X2, or other transport or application protocol.
34. The computer program product of claim 29 , wherein the computer-readable medium further comprises code for causing the at least one computer to populate the header of the relay protocol packet with a destination address of a serving gateway (SGW) or a mobility management entity (MME).
35. The computer program product of claim 29 , wherein the computer-readable medium further comprises code for causing the at least one computer to set a protocol type value in the header of the relay protocol packet to a type of the upper layer protocol payload.
36. The computer program product of claim 29 , wherein the upper layer protocol payload is a compressed or uncompressed general packet radio service (GPRS) tunneling protocol (GTP)-U/user datagram protocol (UDP)/internet protocol (IP) packet.
37. An apparatus, comprising:
a relay protocol packet generating component that creates a relay protocol packet comprising an upper layer protocol payload; and
a relay protocol header populating component that inserts a relay identifier in a header of the relay protocol packet; and
a relay protocol communicating component that transmits the relay protocol packet to one or more evolved Node Bs (eNB) in a wireless network.
38. The apparatus of claim 37 , further comprising a relay protocol header reading component that determines a type of an upper layer protocol corresponding to a payload of a disparate relay protocol packet, wherein the relay protocol communicating component further receives the disparate relay protocol packet from the one or more eNBs.
39. The apparatus of claim 38 , further comprising a packet routing component that provides the payload of the disparate relay protocol packet to a user equipment (UE) based at least in part on the type of the upper layer protocol.
40. The apparatus of claim 38 , wherein the type of the upper layer protocol is S1-U, S1-MME, X2, or other transport or application protocol.
41. The apparatus of claim 37 , wherein the relay protocol packet generating component creates the relay protocol packet based at least in part on a communication received from a UE.
42. The apparatus of claim 37 , wherein the relay protocol header populating component also inserts a destination address of a serving gateway (SGW) or mobility management entity (MME) in the header of the relay protocol packet.
43. The apparatus of claim 42 , wherein the relay protocol header populating component also inserts a type of the upper layer protocol payload in the header of the relay protocol packet.
44. The apparatus of claim 37 , wherein the upper layer protocol payload is a compressed or uncompressed general packet radio service (GPRS) tunneling protocol (GTP)-U/user datagram protocol (UDP)/internet protocol (IP) packet.
45. The apparatus of claim 37 , further comprising a relay identifier receiving component that receives the relay identifier from a donor eNB.
46. The apparatus of claim 45 , further comprising an identifier requesting component that requests the relay identifier from the donor eNB, wherein the relay identifier receiving component receives the relay identifier based at least in part on requesting the relay identifier.
47. A method, comprising:
receiving a relay protocol packet comprising an upper layer protocol payload and a relay identifier;
determining a relay evolved Node B (eNB) to receive the relay protocol packet based at least in part on the relay identifier; and
transmitting the relay protocol packet to the relay eNB.
48. The method of claim 47 , wherein the determining the relay eNB to receive the relay protocol packet includes locating the relay identifier in a routing table associating relay identifiers to cell radio network temporary identifier (C-RNTI) of next hop downstream relay eNBs.
49. The method of claim 47 , further comprising:
receiving a disparate relay protocol packet from the relay eNB; and
forwarding the disparate relay protocol packet to an eNB from which the relay protocol packet is received.
50. A wireless communications apparatus, comprising:
at least one processor configured to:
obtain a relay protocol packet including an upper layer protocol payload and a relay identifier;
select a relay evolved Node B (eNB) to receive the relay protocol packet based at least in part on the relay identifier; and
forward the relay protocol packet to the relay eNB; and
a memory coupled to the at least one processor.
51. The wireless communications apparatus of claim 50 , wherein the at least one processor is further configured to maintain a routing table associating relay identifiers with identifiers of next hop relay eNBs, and the at least one processor selects the relay eNB based at least in part on locating the relay identifier in the routing table along with an associated identifier of the relay eNB.
52. The wireless communications apparatus of claim 50 , wherein the at least one processor is further configured to:
receive a disparate relay protocol packet from the relay eNB; and
forward the disparate relay protocol packet to an eNB from which the relay protocol packet is obtained.
53. An apparatus, comprising:
means for storing a relay identifier along with an identifier of a next hop relay evolved Node B (eNB); and
means for forwarding a relay protocol packet to the next hop relay eNB based at least in part on locating the relay identifier extracted from the relay protocol packet in the means for storing.
54. The apparatus of claim 53 , wherein the means for forwarding determines a cell radio network temporary identifier (C-RNTI) of the next hop relay eNB associated with the relay identifier in the means for storing and forwards the relay protocol packet based on the C-RNTI.
55. The apparatus of claim 53 , wherein the means for forwarding further forwards a disparate relay protocol packet received from the next hop relay eNB to an eNB from which the relay protocol packet is received.
56. A computer program product, comprising:
a computer-readable medium comprising:
code for causing at least one computer to receive a relay protocol packet comprising an upper layer protocol payload and a relay identifier;
code for causing the at least one computer to determine a relay evolved Node B (eNB) to receive the relay protocol packet based at least in part on the relay identifier; and
code for causing the at least one computer to transmit the relay protocol packet to the relay eNB.
57. The computer program product of claim 56 , wherein the code for causing the at least one computer to determine the relay eNB to receive the relay protocol packet locates the relay identifier in a routing table associating relay identifiers to cell radio network temporary identifier (C-RNTI) of next hop downstream relay eNBs.
58. The computer program product of claim 56 , wherein the computer-readable medium further comprises:
code for causing the at least one computer to receive a disparate relay protocol packet from the relay eNB; and
code for causing the at least one computer to forward the disparate relay protocol packet to an eNB from which the relay protocol packet is received.
59. An apparatus, comprising:
a routing table component that stores a relay identifier along with an identifier of a next hop relay evolved Node B (eNB); and
a relay protocol forwarding component that transmits a relay protocol packet to the next hop relay eNB based at least in part on locating the relay identifier extracted from the relay protocol packet in the routing table component.
60. The apparatus of claim 59 , wherein the relay protocol forwarding component determines a cell radio network temporary identifier (C-RNTI) of the next hop relay eNB associated with the relay identifier in the routing table component and forwards the relay protocol packet based on the C-RNTI.
61. The apparatus of claim 59 , wherein the relay protocol forwarding component further forwards a disparate relay protocol packet received from the next hop relay eNB to an eNB from which the relay protocol packet is received.
62. A method, comprising:
receiving a relay protocol packet comprising an upper layer protocol payload and a relay identifier;
determining a type of the upper layer protocol payload; and
communicating the upper layer protocol payload, along with the relay identifier, to a core network component over a disparate transport layer based at least in part on the type of the upper layer protocol payload.
63. The method of claim 62 , further comprising determining a destination internet protocol (IP) address of the core network component from a header of the relay protocol packet, wherein the communicating is further based at least in part on the destination IP address.
64. The method of claim 62 , wherein the determining the type of the upper layer protocol payload includes determining the type of the upper layer protocol payload to be S1-U and the communicating includes communicating the upper layer protocol payload to a serving gateway (SGW).
65. The method of claim 62 , wherein the determining the type of the upper layer protocol payload includes determining the type of the upper layer protocol payload to be S1-MME and the communicating includes communicating the upper layer protocol payload to a mobility management entity (MME).
66. The method of claim 62 , further comprising:
receiving a communication from the core network component comprising the relay identifier;
generating a disparate relay protocol packet including the communication as a payload thereof;
determining an next hop relay evolved Node B (eNB) to receive the disparate relay protocol packet; and
transmitting the disparate relay protocol packet to the next hop relay eNB.
67. The method of claim 66 , further comprising populating a header of the disparate relay protocol packet with the relay identifier.
68. The method of claim 66 , wherein the determining the next hop relay eNB includes locating an association between an identifier of the next hop relay eNB and the relay identifier in a routing table of such identifier associations.
69. A wireless communications apparatus, comprising:
at least one processor configured to:
obtain a relay protocol packet comprising an upper layer protocol payload and a relay identifier;
discern a type of the upper layer protocol payload; and
transmit the upper layer protocol payload along with the relay identifier over a disparate transport layer to an upstream network component; and
a memory coupled to the at least one processor.
70. The wireless communications apparatus of claim 69 , wherein the at least one processor is further configured to determine the upstream network component based at least in part on the type of the upper layer protocol payload.
71. The wireless communications apparatus of claim 70 , wherein the type of the upper layer protocol payload is S1-U and the upstream network component is a serving gateway (SGW).
72. The wireless communications apparatus of claim 70 , wherein the type of the upper layer protocol payload is S1-MME and the upstream network component is a mobility management entity (MME).
73. The wireless communications apparatus of claim 69 , wherein the at least one processor is further configured to determine a destination internet protocol (IP) address of the upstream network component from a header of the relay protocol packet, and the at least one processor transmits the upper layer protocol payload to the upstream network component based on the destination IP address.
74. The wireless communications apparatus of claim 69 , wherein the at least one processor is further configured to:
obtain a communication from the upstream network component comprising the relay identifier;
create a disparate relay protocol packet having the communication as a payload;
select a next hop relay evolved Node B (eNB) to receive the disparate relay protocol packet; and
transmit the relay protocol packet to the next hop relay eNB.
75. The wireless communications apparatus of claim 74 , wherein the at least one processor is further configured to populate a header of the disparate relay protocol packet with the relay identifier.
76. The wireless communications apparatus of claim 74 , wherein the at least one processor selects the next hop relay eNB based at least in part on locating an association between the relay identifier and an identifier of the next hop relay eNB in a routing table.
77. An apparatus, comprising:
means for receiving a relay protocol packet comprising an upper layer protocol payload and a relay identifier; and
means for determining a type of the upper layer protocol payload; and
means for communicating the upper layer protocol payload along with the relay identifier to a core network component over a disparate transport layer.
78. The apparatus of claim 77 , wherein the means for communicating selects the core network component based at least in part on the type of the upper layer protocol payload.
79. The apparatus of claim 78 , wherein the type of the upper layer protocol payload is S1-U and the core network component is a serving gateway (SGW).
80. The apparatus of claim 78 , wherein the type of the upper layer protocol payload is S1-MME and the core network component is a mobility management entity (MME).
81. The apparatus of claim 77 , wherein the means for determining the type of the upper layer protocol payload further extracts a destination internet protocol (IP) address of the core network component from a header of the relay protocol packet, and the means for communicating selects the core network component based on the destination IP address.
82. The apparatus of claim 77 , further comprising:
means for generating a disparate relay protocol packet including a communication as a payload thereof; and
means for determining a next hop relay evolved Node B (eNB) to receive the disparate relay protocol packet, wherein the means for communicating receives the communication from the core network component, and the means for receiving transmits the disparate relay protocol packet to the next hop relay eNB.
83. The apparatus of claim 82 , further comprising means for inserting the relay identifier in a header of the disparate relay protocol packet.
84. The apparatus of claim 82 , wherein the means for determining the next hop relay eNB determines the next hop relay eNB based at least in part on locating the relay identifier in a routing table.
85. A computer program product, comprising:
a computer-readable medium comprising:
code for causing at least one computer to receive a relay protocol packet comprising an upper layer protocol payload and a relay identifier;
code for causing the at least one computer to determine a type of the upper layer protocol payload; and
code for causing the at least one computer to communicate the upper layer protocol payload, along with the relay identifier, to a core network component over a disparate transport layer based at least in part on the type of the upper layer protocol payload.
86. The computer program product of claim 85 , further comprising code for causing the at least one computer to determine a destination internet protocol (IP) address of the core network component from a header of the relay protocol packet, wherein the code for causing the at least one computer to communicate communicates the upper layer protocol payload further based at least in part on the destination IP address.
87. The computer program product of claim 85 , wherein the code for causing the at least one computer to determine the type of the upper layer protocol payload determines the type of the upper layer protocol payload to be S1-U and the code for causing the at least one computer to communicate communicates the upper layer protocol payload to a serving gateway (SGW).
88. The computer program product of claim 85 , wherein the code for causing the at least one computer to determine the type of the upper layer protocol payload determines the type of the upper layer protocol payload to be S1-MME and the code for causing the at least one computer to communicate communicates the upper layer protocol payload to a mobility management entity (MME).
89. The computer program product of claim 85 , wherein the computer-readable medium further comprises:
code for causing the at least one computer to receive a communication from the core network component comprising the relay identifier;
code for causing the at least one computer to generate a disparate relay protocol packet including the communication as a payload thereof;
code for causing the at least one computer to determine an next hop relay evolved Node B (eNB) to receive the disparate relay protocol packet; and
code for causing the at least one computer to transmit the disparate relay protocol packet to the next hop relay eNB.
90. The computer program product of claim 89 , wherein the computer-readable medium further comprises code for causing the at least one computer to populate a header of the disparate relay protocol packet with the relay identifier.
91. The computer program product of claim 89 , wherein the code for causing the at least one computer to determine the next hop relay eNB locates an association between an identifier of the next hop relay eNB and the relay identifier in a routing table of such identifier associations.
92. An apparatus, comprising:
a relay protocol component that receives a relay protocol packet comprising an upper layer protocol payload and a relay identifier; and
a relay protocol header reading component that determines a type of the upper layer protocol payload; and
a backhaul link component that communicates the upper layer protocol payload along with the relay identifier to a core network component over a disparate transport layer.
93. The apparatus of claim 92 , wherein the backhaul link component selects the core network component based at least in part on the type of the upper layer protocol payload.
94. The apparatus of claim 93 , wherein the type of the upper layer protocol payload is S1-U and the core network component is a serving gateway (SGW).
95. The apparatus of claim 93 , wherein the type of the upper layer protocol payload is S1-MME and the core network component is a mobility management entity (MME).
96. The apparatus of claim 92 , wherein the relay protocol header reading component further extracts a destination internet protocol (IP) address of the core network component from a header of the relay protocol packet, and the backhaul link component selects the core network component based on the destination IP address.
97. The apparatus of claim 92 , further comprising:
a relay protocol packet generating component that creates a disparate relay protocol packet including a communication as a payload thereof; and
a routing table component that determines a next hop relay evolved Node B (eNB) to receive the disparate relay protocol packet, wherein the backhaul link component receives the communication from the core network component, and the relay protocol component transmits the disparate relay protocol packet to the next hop relay eNB.
98. The apparatus of claim 97 , further comprising a relay protocol header populating component that inserts the relay identifier in a header of the disparate relay protocol packet.
99. The apparatus of claim 97 , wherein the routing table component determines the next hop relay eNB based at least in part on locating the relay identifier in a routing table.
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/604,215 US20100103864A1 (en) | 2008-10-24 | 2009-10-22 | Cell relay protocol |
PCT/US2009/061933 WO2010048565A1 (en) | 2008-10-24 | 2009-10-23 | Cell relay protocol |
TW098136014A TW201019760A (en) | 2008-10-24 | 2009-10-23 | Cell relay protocol |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10828708P | 2008-10-24 | 2008-10-24 | |
US12/604,215 US20100103864A1 (en) | 2008-10-24 | 2009-10-22 | Cell relay protocol |
Publications (1)
Publication Number | Publication Date |
---|---|
US20100103864A1 true US20100103864A1 (en) | 2010-04-29 |
Family
ID=42117409
Family Applications (7)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/603,392 Active 2031-11-22 US8902805B2 (en) | 2008-10-24 | 2009-10-21 | Cell relay packet routing |
US12/604,205 Active 2031-10-12 US9088939B2 (en) | 2008-10-24 | 2009-10-22 | Bearer QoS mapping for cell relays |
US12/604,189 Active 2031-02-07 US8401068B2 (en) | 2008-10-24 | 2009-10-22 | Device attachment and bearer activation using cell relays |
US12/604,198 Abandoned US20100103857A1 (en) | 2008-10-24 | 2009-10-22 | Cell relay network attachment procedures |
US12/604,210 Abandoned US20100103845A1 (en) | 2008-10-24 | 2009-10-22 | Cell relay mobility procedures |
US12/604,215 Abandoned US20100103864A1 (en) | 2008-10-24 | 2009-10-22 | Cell relay protocol |
US12/605,184 Abandoned US20100103865A1 (en) | 2008-10-24 | 2009-10-23 | Header compression for cell relay communications |
Family Applications Before (5)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/603,392 Active 2031-11-22 US8902805B2 (en) | 2008-10-24 | 2009-10-21 | Cell relay packet routing |
US12/604,205 Active 2031-10-12 US9088939B2 (en) | 2008-10-24 | 2009-10-22 | Bearer QoS mapping for cell relays |
US12/604,189 Active 2031-02-07 US8401068B2 (en) | 2008-10-24 | 2009-10-22 | Device attachment and bearer activation using cell relays |
US12/604,198 Abandoned US20100103857A1 (en) | 2008-10-24 | 2009-10-22 | Cell relay network attachment procedures |
US12/604,210 Abandoned US20100103845A1 (en) | 2008-10-24 | 2009-10-22 | Cell relay mobility procedures |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/605,184 Abandoned US20100103865A1 (en) | 2008-10-24 | 2009-10-23 | Header compression for cell relay communications |
Country Status (9)
Country | Link |
---|---|
US (7) | US8902805B2 (en) |
EP (3) | EP2359654A1 (en) |
JP (4) | JP5209796B2 (en) |
KR (5) | KR101383186B1 (en) |
CN (4) | CN102197679A (en) |
BR (1) | BRPI0919845B1 (en) |
ES (1) | ES2427172T3 (en) |
TW (7) | TW201032545A (en) |
WO (7) | WO2010048571A1 (en) |
Cited By (22)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20100103857A1 (en) * | 2008-10-24 | 2010-04-29 | Qualcomm Incorporated | Cell relay network attachment procedures |
US20100182970A1 (en) * | 2009-01-21 | 2010-07-22 | Qualcomm Incorporated | Multiple Subscriptions Using a Single Air-Interface Resource |
US20110041127A1 (en) * | 2009-08-13 | 2011-02-17 | Mathias Kohlenz | Apparatus and Method for Efficient Data Processing |
US20110040948A1 (en) * | 2009-08-13 | 2011-02-17 | Mathias Kohlenz | Apparatus and Method for Efficient Memory Allocation |
US20110041128A1 (en) * | 2009-08-13 | 2011-02-17 | Mathias Kohlenz | Apparatus and Method for Distributed Data Processing |
US20110092244A1 (en) * | 2009-10-15 | 2011-04-21 | Electronics And Telecommunications Research Institute | Ad-hoc wireless communication method using sector antenna, recovery method in ad-hoc wireless communication and ad-hoc wireless communication system |
US20110158155A1 (en) * | 2009-12-30 | 2011-06-30 | Samsung Electronics Co. Ltd. | Apparatus and method for managing quality of service in broadband wireless communication system with multiple hop relay communication |
US20120140701A1 (en) * | 2009-08-18 | 2012-06-07 | Zte Corporation | Relay Communication System Supporting Multiple Hops and Access Method Thereof |
US8788782B2 (en) | 2009-08-13 | 2014-07-22 | Qualcomm Incorporated | Apparatus and method for memory management and efficient data processing |
US8839373B2 (en) | 2010-06-18 | 2014-09-16 | Qualcomm Incorporated | Method and apparatus for relay node management and authorization |
US20150011158A1 (en) * | 2012-02-06 | 2015-01-08 | Alcatel Lucent | Apparatus, method, and computer program for a mobile relay station transceiver, system, and means for mass transportation |
US9385862B2 (en) | 2010-06-16 | 2016-07-05 | Qualcomm Incorporated | Method and apparatus for binding subscriber authentication and device authentication in communication systems |
US20180279118A1 (en) * | 2012-01-19 | 2018-09-27 | Samsung Electronics Co., Ltd | Method for establishing an interface and communication between a relay node and a core network |
CN110830170A (en) * | 2019-11-12 | 2020-02-21 | 北京理工大学 | Data transmission method based on ROHC compression in satellite communication |
US10735085B2 (en) * | 2016-03-30 | 2020-08-04 | Sprint Communications Company L.P. | Multi-core communication system to serve wireless relays and user equipment |
CN113133078A (en) * | 2021-04-19 | 2021-07-16 | 西安电子科技大学 | Light-weight inter-satellite switching device and method for giant low-orbit satellite network |
WO2021187848A1 (en) * | 2020-03-17 | 2021-09-23 | Samsung Electronics Co., Ltd. | Methods and systems for reducing fronthaul bandwidth in a wireless communication system |
US11172539B2 (en) * | 2016-11-22 | 2021-11-09 | Sony Corporation | Base station and terminal device |
US11252635B2 (en) | 2018-02-14 | 2022-02-15 | Kt Corporation | Method for processing uplink user data in relay node, and device for same |
EP4120743A1 (en) * | 2018-01-09 | 2023-01-18 | Guangdong Oppo Mobile Telecommunications Corp., Ltd. | Relay routing method and communication node |
US11706607B1 (en) | 2021-06-16 | 2023-07-18 | T-Mobile Usa, Inc. | Location based routing that bypasses circuit-based networks |
US11974208B2 (en) | 2018-01-09 | 2024-04-30 | Guangdong Oppo Mobile Telecommunications Corp., Ltd. | Relay routing method and communication node |
Families Citing this family (240)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP3484135A1 (en) | 2008-04-02 | 2019-05-15 | Twilio Inc. | System and method for processing telephony sessions |
US8837465B2 (en) | 2008-04-02 | 2014-09-16 | Twilio, Inc. | System and method for processing telephony sessions |
KR101236033B1 (en) * | 2008-07-21 | 2013-02-21 | 한국전자통신연구원 | Communication system for removing transmission overhead |
WO2010010708A1 (en) * | 2008-07-24 | 2010-01-28 | パナソニック株式会社 | Relay device and relay method |
CN102227904A (en) | 2008-10-01 | 2011-10-26 | 特维里奥公司 | Telephony web event system and method |
US8964781B2 (en) * | 2008-11-05 | 2015-02-24 | Qualcomm Incorporated | Relays in a multihop heterogeneous UMTS wireless communication system |
US8848594B2 (en) | 2008-12-10 | 2014-09-30 | Blackberry Limited | Method and apparatus for discovery of relay nodes |
US8355388B2 (en) | 2008-12-17 | 2013-01-15 | Research In Motion Limited | System and method for initial access to relays |
US8311061B2 (en) | 2008-12-17 | 2012-11-13 | Research In Motion Limited | System and method for multi-user multiplexing |
US8402334B2 (en) | 2008-12-17 | 2013-03-19 | Research In Motion Limited | System and method for hybrid automatic repeat request (HARQ) functionality in a relay node |
US8040904B2 (en) | 2008-12-17 | 2011-10-18 | Research In Motion Limited | System and method for autonomous combining |
US8265128B2 (en) | 2008-12-19 | 2012-09-11 | Research In Motion Limited | Multiple-input multiple-output (MIMO) with relay nodes |
EP2380392A1 (en) * | 2008-12-19 | 2011-10-26 | Telefonaktiebolaget LM Ericsson (publ) | Method and entity for conveying data units |
US8446856B2 (en) | 2008-12-19 | 2013-05-21 | Research In Motion Limited | System and method for relay node selection |
US8335466B2 (en) | 2008-12-19 | 2012-12-18 | Research In Motion Limited | System and method for resource allocation |
KR101531531B1 (en) * | 2009-01-08 | 2015-07-07 | 삼성전자주식회사 | Method for connecting user equipment to local packet data network by evolved node b |
KR101521886B1 (en) * | 2009-01-23 | 2015-05-28 | 삼성전자주식회사 | Apparatus and method for processing gtp in mobile communication system |
JP5671484B2 (en) | 2009-03-02 | 2015-02-18 | トゥイリオ インコーポレイテッドTwilio Inc. | Method and system for a multi-tenant telephone network |
CN101827451B (en) * | 2009-03-03 | 2012-12-12 | 华为技术有限公司 | Network access method of relaying node and device |
US20120002592A1 (en) * | 2009-03-06 | 2012-01-05 | Ning Yang | Method, system and network device for network access of relay node |
CN102282905B (en) * | 2009-03-17 | 2016-01-27 | 华为技术有限公司 | A kind of method, Apparatus and system setting up radio bearer |
JP5479571B2 (en) * | 2009-03-20 | 2014-04-23 | テレフオンアクチーボラゲット エル エム エリクソン(パブル) | Radio bearer identification for self-backhaul processing and relay processing in advanced LTE |
EP2416530B1 (en) * | 2009-03-30 | 2015-05-06 | Huawei Technologies Co., Ltd. | Method, network system and device for realizing data retransmission |
EP3236690B1 (en) | 2009-04-02 | 2019-08-21 | Telefonaktiebolaget LM Ericsson (publ) | Techniques for handling network traffic |
EP2417798A1 (en) * | 2009-04-09 | 2012-02-15 | Nokia Siemens Networks Oy | Base station caching for an efficient handover in a mobile telecommunication network with relays |
US9160566B2 (en) * | 2009-04-10 | 2015-10-13 | Qualcomm Incorporated | QOS mapping for relay nodes |
KR100968037B1 (en) * | 2009-04-21 | 2010-07-07 | 엘지전자 주식회사 | Apparatus and method of managing radio bearer in wireless communication system |
WO2010123279A2 (en) * | 2009-04-21 | 2010-10-28 | Lg Electronics Inc. | Method of utilizing a relay node in wireless communication system |
US8902827B2 (en) * | 2009-04-21 | 2014-12-02 | Htc Corporation | Relay for handling data forwarding in a wireless communication system and related method for controlling the same |
EP2259651A1 (en) * | 2009-06-05 | 2010-12-08 | Panasonic Corporation | QoS Multiplexing via base station-relay node interface |
US8588138B2 (en) * | 2009-07-23 | 2013-11-19 | Qualcomm Incorporated | Header compression for relay nodes |
CN101998449B (en) * | 2009-08-17 | 2015-07-22 | 中兴通讯股份有限公司 | Transmission system and method applied to wireless relay |
CN101998303B (en) * | 2009-08-18 | 2013-11-06 | 华为技术有限公司 | Data transmission method, system, donor base station, relay equipment and evolved packet core network node |
CN101998621B (en) * | 2009-08-21 | 2013-08-28 | 华为技术有限公司 | Buffer status report (BSR) reporting method, relay node (RN), evolved node base (eNB) and system |
US8213337B2 (en) * | 2009-09-23 | 2012-07-03 | Via Telecom, Inc. | IP multimedia subsystem for a multimode wireless device |
US9210275B2 (en) | 2009-10-07 | 2015-12-08 | Twilio, Inc. | System and method for running a multi-module telephony application |
EP2355608B1 (en) * | 2009-10-30 | 2016-03-09 | Institute for Imformation Industry | Donor evolved nodeb, relay node and communication method thereof |
US20110134826A1 (en) * | 2009-12-04 | 2011-06-09 | Xiangying Yang | Relay data path architecture for a wireless network |
JP4838377B2 (en) * | 2009-12-14 | 2011-12-14 | 株式会社エヌ・ティ・ティ・ドコモ | Mobile communication system and radio base station |
WO2011077065A1 (en) * | 2009-12-22 | 2011-06-30 | Fujitsu Limited | Quality of service control in a relay |
CN102118812B (en) * | 2009-12-31 | 2014-07-30 | 华为技术有限公司 | Switching method, system, relay station, control base station and base station in relay network, |
US9021072B2 (en) * | 2010-01-28 | 2015-04-28 | Verizon Patent And Licensing Inc. | Localized media offload |
IL206455A (en) | 2010-01-28 | 2016-11-30 | Elta Systems Ltd | Cellular communication system with moving base stations and methods and apparatus useful in conjunction therewith |
CN102149214B (en) * | 2010-02-05 | 2015-05-13 | 中兴通讯股份有限公司 | Data transmission method and system in communication system |
US20110194533A1 (en) * | 2010-02-11 | 2011-08-11 | Te-Ming Chen | Method of Handling Radio Resource Reconfiguration |
RU2563841C2 (en) | 2010-02-19 | 2015-09-20 | Телефонактиеболагет Л М Эрикссон (Пабл) | Identification of relay centres in communication network |
CN102088771B (en) * | 2010-03-12 | 2013-10-16 | 电信科学技术研究院 | Method, system and device for selecting data surface path according to UE (User Equipment) status |
US8724472B2 (en) * | 2010-03-25 | 2014-05-13 | Qualcomm Incorporated | Data radio bearer mapping in a telecommunication network with relays |
CN107580330B (en) | 2010-04-02 | 2021-10-01 | 交互数字专利控股公司 | Method and apparatus for supporting communication via a relay node |
GB2479904A (en) * | 2010-04-28 | 2011-11-02 | Sharp Kk | LTE-A relay apparatus, in particular for type 1 relays |
US20110267943A1 (en) * | 2010-04-30 | 2011-11-03 | Qualcomm Incorporated | Static uu-un bearer mapping based on quality of service |
CN102238667B (en) * | 2010-05-07 | 2015-09-16 | 北京三星通信技术研究有限公司 | A kind ofly set up the method connected between base station |
DE102010028974A1 (en) * | 2010-05-12 | 2011-11-17 | Vodafone Holding Gmbh | Providing an end-to-end connection from an end unit to a network |
EP3860280A1 (en) * | 2010-06-04 | 2021-08-04 | Board of Regents, The University of Texas System | Wireless communication method and appartus |
CN102271405B (en) * | 2010-06-04 | 2014-09-10 | 中兴通讯股份有限公司 | Method and device for allocating bearer resources |
CN102104930A (en) * | 2010-06-12 | 2011-06-22 | 电信科学技术研究院 | Mapping method and apparatus in resource status process |
JP4996718B2 (en) * | 2010-06-21 | 2012-08-08 | 株式会社エヌ・ティ・ティ・ドコモ | Mobile communication method and radio base station |
CN102291789B (en) * | 2010-06-21 | 2015-08-12 | 中兴通讯股份有限公司 | The cell switching method of acquisition adjacent cell information method, subscriber equipment and network |
US20120208495A1 (en) | 2010-06-23 | 2012-08-16 | Twilio, Inc. | System and method for monitoring account usage on a platform |
US9459926B2 (en) | 2010-06-23 | 2016-10-04 | Twilio, Inc. | System and method for managing a computing cluster |
US9590849B2 (en) | 2010-06-23 | 2017-03-07 | Twilio, Inc. | System and method for managing a computing cluster |
US9459925B2 (en) | 2010-06-23 | 2016-10-04 | Twilio, Inc. | System and method for managing a computing cluster |
JP5277210B2 (en) * | 2010-06-24 | 2013-08-28 | 株式会社エヌ・ティ・ティ・ドコモ | Mobile communication method and relay node |
US8897134B2 (en) * | 2010-06-25 | 2014-11-25 | Telefonaktiebolaget L M Ericsson (Publ) | Notifying a controller of a change to a packet forwarding configuration of a network element over a communication channel |
US8838707B2 (en) | 2010-06-25 | 2014-09-16 | Twilio, Inc. | System and method for enabling real-time eventing |
US8375245B2 (en) * | 2010-07-15 | 2013-02-12 | Verizon Patent And Licensing Inc. | Mobility management entity failover |
EP2996282B1 (en) | 2010-07-29 | 2019-05-15 | Telefonaktiebolaget LM Ericsson (publ) | Handling network traffic via a fixed access |
WO2012016187A2 (en) | 2010-07-30 | 2012-02-02 | Board Of Regents | Distributed rate allocation and collision detection in wireless networks |
CN106059647B (en) * | 2010-08-03 | 2019-06-14 | 日本电气株式会社 | Relay station apparatus, mobile communication system, base station apparatus and the method for controlling relay station |
US8495271B2 (en) * | 2010-08-04 | 2013-07-23 | International Business Machines Corporation | Injection of I/O messages |
US8549202B2 (en) | 2010-08-04 | 2013-10-01 | International Business Machines Corporation | Interrupt source controller with scalable state structures |
US9336029B2 (en) | 2010-08-04 | 2016-05-10 | International Business Machines Corporation | Determination via an indexed structure of one or more partitionable endpoints affected by an I/O message |
WO2012028200A1 (en) * | 2010-09-03 | 2012-03-08 | Nokia Siemens Networks Oy | Relay nodes in multi-operator scenario |
CN102404770B (en) * | 2010-09-08 | 2015-04-01 | 电信科学技术研究院 | Method and device for secondary measurement of wireless relay system layer |
JP5700856B2 (en) * | 2010-09-09 | 2015-04-15 | パナソニック インテレクチュアル プロパティ コーポレーション オブアメリカPanasonic Intellectual Property Corporation of America | COMMUNICATION SYSTEM, COMMUNICATION METHOD, MOBILE TERMINAL, AND BASE STATION DEVICE |
CN102438258A (en) * | 2010-09-29 | 2012-05-02 | 中兴通讯股份有限公司 | Bearer multiplexing method and bearer multiplexing device |
US8345603B2 (en) * | 2010-09-30 | 2013-01-01 | Alcatel Lucent | Method and apparatus for processing GTP triggered messages |
JP4932933B2 (en) * | 2010-10-06 | 2012-05-16 | 株式会社エヌ・ティ・ティ・ドコモ | Relay station and relay method for relaying wireless communication |
EP2625885A1 (en) * | 2010-10-08 | 2013-08-14 | Nokia Siemens Networks Oy | Relay nodes |
US20130237230A1 (en) * | 2010-10-19 | 2013-09-12 | Nokia Siemens Networks Oy | Reconfiguring a Base Station for Handover in Relay-Enhanced Communication Network |
US9204290B2 (en) * | 2010-11-03 | 2015-12-01 | Telefonaktiebolaget L M Ericsson (Publ) | Method and system for constructing a domain name for a radio network node in a cellular communication system |
JP4937398B1 (en) * | 2010-11-04 | 2012-05-23 | 株式会社エヌ・ティ・ティ・ドコモ | Relay station and reconnection method |
WO2012061680A2 (en) * | 2010-11-05 | 2012-05-10 | Interdigital Patent Holdings, Inc. | Relay node interface related layer 2 measurements and relay node handling in network load balancing |
SG190386A1 (en) | 2010-11-24 | 2013-06-28 | Elta Systems Ltd | Various routing architectures for dynamic multi-hop backhauling cellular network and various methods useful in conjunction therewith |
US9351173B2 (en) | 2010-11-24 | 2016-05-24 | Elta Systems Ltd. | Architecture and methods for traffic management by tunneling in hierarchical cellular networks |
CN102547892B (en) * | 2010-12-20 | 2014-12-10 | 大唐移动通信设备有限公司 | Nomadic data access system, device and transmission method |
CN102083006B (en) * | 2011-01-17 | 2014-06-04 | 大唐移动通信设备有限公司 | Data transmission method, device and system |
US8649268B2 (en) | 2011-02-04 | 2014-02-11 | Twilio, Inc. | Method for processing telephony sessions of a network |
US8750333B2 (en) * | 2011-02-14 | 2014-06-10 | Telefonaktiebolaget Lm Ericsson (Publ) | Backwards-compatible approach to fields of a protocol layer |
US8806042B2 (en) | 2011-02-18 | 2014-08-12 | Telefonaktiebolaget L M Ericsson (Publ) | Mobile router in EPS |
WO2012122508A2 (en) | 2011-03-09 | 2012-09-13 | Board Of Regents | Network routing system, method, and computer program product |
US20120238208A1 (en) * | 2011-03-17 | 2012-09-20 | Maik Bienas | Mobile radio communication devices and servers |
TW201246956A (en) * | 2011-03-29 | 2012-11-16 | Innovative Sonic Corp | Method and apparatus to improve high-speed mobility in a wireless communication system |
US8817690B2 (en) * | 2011-04-04 | 2014-08-26 | Qualcomm Incorporated | Method and apparatus for scheduling network traffic in the presence of relays |
CN102740278B (en) * | 2011-04-11 | 2016-01-20 | 普天信息技术研究院有限公司 | The method of eNB config update in wireless relay network |
US8780799B2 (en) * | 2011-05-02 | 2014-07-15 | Verizon Patent And Licensing Inc. | Handling multiple voice over internet protocol (VoIP) calls via a single bearer |
WO2012162397A1 (en) | 2011-05-23 | 2012-11-29 | Twilio, Inc. | System and method for connecting a communication to a client |
US20140044123A1 (en) | 2011-05-23 | 2014-02-13 | Twilio, Inc. | System and method for real time communicating with a client application |
US9648006B2 (en) | 2011-05-23 | 2017-05-09 | Twilio, Inc. | System and method for communicating with a client application |
JP5484399B2 (en) | 2011-05-31 | 2014-05-07 | 株式会社Nttドコモ | Mobile communication method, relay node, and radio base station |
EP2721843B1 (en) | 2011-06-16 | 2019-02-06 | Nokia Solutions and Networks Oy | Methods, apparatus, a system, and a related computer program product for activation and deacitivation of bearers |
CN103718602B (en) * | 2011-06-17 | 2018-05-15 | 瑞典爱立信有限公司 | The service quality and method of service node |
US8965415B2 (en) | 2011-07-15 | 2015-02-24 | Qualcomm Incorporated | Short packet data service |
EP2568749B1 (en) | 2011-09-06 | 2018-01-31 | Alcatel Lucent | Method of providing communication over a mobile communication network |
WO2013040744A1 (en) * | 2011-09-19 | 2013-03-28 | Telefonaktiebolaget L M Ericsson (Publ) | Method and apparatus for transmitting and receiving data in orthogonal frequency division multiplexing system |
US9510256B2 (en) * | 2011-09-20 | 2016-11-29 | Wildfire.Exchange, Inc. | Seamless handoff, offload, and load balancing in integrated Wi-Fi/small cell systems |
US10182147B2 (en) | 2011-09-21 | 2019-01-15 | Twilio Inc. | System and method for determining and communicating presence information |
US20130137469A1 (en) | 2011-11-30 | 2013-05-30 | Intel Mobile Communications GmbH | Method for transmitting an opportunistic network related message |
US20140321282A1 (en) * | 2011-12-08 | 2014-10-30 | Interdigital Patent Holdings, Inc. | High-rate dual-band cellular communications |
US20130155964A1 (en) * | 2011-12-19 | 2013-06-20 | Motorola Solutions, Inc. | Allowing end-user devices access to resources of a mobile broadband network at desired quality of service levels using a transit device |
US20130155918A1 (en) * | 2011-12-20 | 2013-06-20 | Nokia Siemens Networks Oy | Techniques To Enhance Header Compression Efficiency And Enhance Mobile Node Security |
EP2810506B1 (en) * | 2012-01-16 | 2017-12-06 | Telefonaktiebolaget LM Ericsson (publ) | Method and arrangement for relaying |
US8660078B2 (en) | 2012-02-07 | 2014-02-25 | Qualcomm Incorporated | Data radio bearer (DRB) enhancements for small data transmissions apparatus, systems, and methods |
US9495227B2 (en) | 2012-02-10 | 2016-11-15 | Twilio, Inc. | System and method for managing concurrent events |
JP5792661B2 (en) * | 2012-03-06 | 2015-10-14 | 株式会社日立製作所 | Ad hoc network system and meter reading information collection method |
TWI484853B (en) * | 2012-03-14 | 2015-05-11 | Inst Information Industry | Communication system and communication method thereof |
US9526091B2 (en) | 2012-03-16 | 2016-12-20 | Intel Corporation | Method and apparatus for coordination of self-optimization functions in a wireless network |
US9986535B2 (en) * | 2012-03-31 | 2018-05-29 | Tejas Networks Limited | Method and system for managing mobile management entity (MME) in a telecommunication network |
US9602586B2 (en) | 2012-05-09 | 2017-03-21 | Twilio, Inc. | System and method for managing media in a distributed communication network |
JP2013239817A (en) * | 2012-05-14 | 2013-11-28 | Sharp Corp | Relay device, radio terminal device, communication system and communication method |
WO2013185285A1 (en) * | 2012-06-12 | 2013-12-19 | Nokia Corporation | Methods, apparatuses and computer program products for configuration of signaling radio bearers |
JP6163204B2 (en) | 2012-06-14 | 2017-07-12 | テケレック・インコーポレイテッドTekelec, Inc. | Method, system, and computer-readable medium for providing an integrated OpenFlow controller for a policy and charging rules function (PCRF) |
US9247062B2 (en) | 2012-06-19 | 2016-01-26 | Twilio, Inc. | System and method for queuing a communication session |
CN102769930B (en) * | 2012-07-11 | 2018-05-11 | 中兴通讯股份有限公司 | Bearing processing method and device |
GB2503923A (en) * | 2012-07-12 | 2014-01-15 | Nec Corp | Coordinated multipoint transmissions to a relay node |
CN103580778B (en) * | 2012-07-20 | 2016-12-21 | 华为技术有限公司 | A kind of data transmission method, device and communication system |
US8737962B2 (en) | 2012-07-24 | 2014-05-27 | Twilio, Inc. | Method and system for preventing illicit use of a telephony platform |
JP5871750B2 (en) * | 2012-08-28 | 2016-03-01 | 株式会社Nttドコモ | Mobile communication system, radio base station and mobile station |
US8938053B2 (en) | 2012-10-15 | 2015-01-20 | Twilio, Inc. | System and method for triggering on platform usage |
US8948356B2 (en) | 2012-10-15 | 2015-02-03 | Twilio, Inc. | System and method for routing communications |
WO2014063319A1 (en) | 2012-10-24 | 2014-05-01 | 华为技术有限公司 | Processing method, base station and system for cooperative communication |
US9480106B2 (en) * | 2012-11-28 | 2016-10-25 | T-Mobile Usa, Inc. | Inter-base station logical interface communication using relay devices |
US9672527B2 (en) * | 2013-01-21 | 2017-06-06 | Tejas Networks Limited | Associating and consolidating MME bearer management functions |
US9537904B2 (en) * | 2013-01-24 | 2017-01-03 | Tekelec, Inc. | Methods, systems, and computer readable media for using policy knowledge of or obtained by a policy and charging rules function (PCRF) for needs based forwarding of bearer session traffic to network nodes |
JP6096325B2 (en) | 2013-02-18 | 2017-03-15 | テケレック・インコーポレイテッドTekelec, Inc. | Method, system, and computer-readable medium for providing a sinking Diameter network architecture |
EP2957068B1 (en) | 2013-02-18 | 2018-08-22 | Tekelec, Inc. | Methods, systems, and computer readable media for providing a virtualized diameter network architecture and for routing traffic to dynamically instantiated diameter resource instances |
US9282124B2 (en) | 2013-03-14 | 2016-03-08 | Twilio, Inc. | System and method for integrating session initiation protocol communication in a telecommunications platform |
CN104969653B (en) * | 2013-04-07 | 2019-07-26 | 华为技术有限公司 | The method for building up and equipment of wireless backhaul link |
KR101410248B1 (en) * | 2013-05-21 | 2014-06-20 | 주식회사 이노와이어리스 | method for measuring backhaul throughput for LTE small cell |
CN104244426B (en) | 2013-06-09 | 2019-02-05 | 华为技术有限公司 | A kind of resource allocation methods and device of Data Radio Bearer DRB |
US9225840B2 (en) | 2013-06-19 | 2015-12-29 | Twilio, Inc. | System and method for providing a communication endpoint information service |
US9160696B2 (en) | 2013-06-19 | 2015-10-13 | Twilio, Inc. | System for transforming media resource into destination device compatible messaging format |
US9483328B2 (en) | 2013-07-19 | 2016-11-01 | Twilio, Inc. | System and method for delivering application content |
US9391897B2 (en) | 2013-07-31 | 2016-07-12 | Oracle International Corporation | Methods, systems, and computer readable media for mitigating traffic storms |
US9137127B2 (en) | 2013-09-17 | 2015-09-15 | Twilio, Inc. | System and method for providing communication platform metadata |
US9274858B2 (en) | 2013-09-17 | 2016-03-01 | Twilio, Inc. | System and method for tagging and tracking events of an application platform |
US9510376B2 (en) | 2013-09-25 | 2016-11-29 | At&T Intellectual Property I, L.P. | Tunneling packet exchange in long term evolution protocol based networks |
KR102097408B1 (en) * | 2013-10-15 | 2020-04-06 | 삼성전자주식회사 | Apparatus and method for controlling to operate use carrier aggregation technology in mobile communication system |
US9553799B2 (en) | 2013-11-12 | 2017-01-24 | Twilio, Inc. | System and method for client communication in a distributed telephony network |
US9325624B2 (en) | 2013-11-12 | 2016-04-26 | Twilio, Inc. | System and method for enabling dynamic multi-modal communication |
US11388082B2 (en) | 2013-11-27 | 2022-07-12 | Oracle International Corporation | Methods, systems, and computer readable media for diameter routing using software defined network (SDN) functionality |
WO2015096008A1 (en) * | 2013-12-23 | 2015-07-02 | Telefonaktiebolaget L M Ericsson (Publ) | Method and network node for routing backhaul packets |
EP3095242B1 (en) * | 2014-01-14 | 2019-07-24 | LG Electronics Inc. | Method and apparatus for transmitting/receiving broadcasting signal including robust header compression packet stream and fast information |
US9344573B2 (en) | 2014-03-14 | 2016-05-17 | Twilio, Inc. | System and method for a work distribution service |
US9787595B2 (en) | 2014-03-24 | 2017-10-10 | Intel IP Corporation | Evolved node-B and mobility management entity and user equipment and methods for supporting attended and unattended services |
EP3132622B1 (en) * | 2014-04-15 | 2019-09-25 | Nokia Solutions and Networks Oy | Interworking with bearer-based system |
US9226217B2 (en) | 2014-04-17 | 2015-12-29 | Twilio, Inc. | System and method for enabling multi-modal communication |
US10506607B2 (en) | 2014-06-02 | 2019-12-10 | Qualcomm Incorporated | Discovery of multi-hop capabilities and routing on a per link basis |
US9961587B2 (en) | 2014-06-26 | 2018-05-01 | Gilat Satellite Networks Ltd. | Methods and apparatus for optimizing tunneled traffic |
US10021594B2 (en) | 2014-06-26 | 2018-07-10 | Gilat Satellite Networks Ltd. | Methods and apparatus for optimizing tunneled traffic |
RO130953A2 (en) * | 2014-07-04 | 2016-02-26 | Ixia, A California Corporation | Methods, system and computer-readable medium for distributing general packet radio service tunnelling protocol (gtp) traffic |
US9246694B1 (en) | 2014-07-07 | 2016-01-26 | Twilio, Inc. | System and method for managing conferencing in a distributed communication network |
US9774687B2 (en) | 2014-07-07 | 2017-09-26 | Twilio, Inc. | System and method for managing media and signaling in a communication platform |
US9516101B2 (en) | 2014-07-07 | 2016-12-06 | Twilio, Inc. | System and method for collecting feedback in a multi-tenant communication platform |
US9251371B2 (en) | 2014-07-07 | 2016-02-02 | Twilio, Inc. | Method and system for applying data retention policies in a computing platform |
US20160021161A1 (en) * | 2014-07-16 | 2016-01-21 | Alcatel-Lucent Usa, Inc. | Mobile network video optimization for centralized processing base stations |
CN105451282A (en) * | 2014-08-22 | 2016-03-30 | 电信科学技术研究院 | Relay terminal reselection method and apparatus |
WO2016051578A1 (en) * | 2014-10-02 | 2016-04-07 | 富士通株式会社 | Repeater and base station system |
US9538563B2 (en) | 2014-10-13 | 2017-01-03 | At&T Intellectual Property I, L.P. | System and methods for managing a user data path |
US9749428B2 (en) | 2014-10-21 | 2017-08-29 | Twilio, Inc. | System and method for providing a network discovery service platform |
DE102014221956A1 (en) * | 2014-10-28 | 2016-05-12 | Bayerische Motoren Werke Aktiengesellschaft | Apparatus, vehicle, method and computer program for a relay transceiver and a network component |
US20160135166A1 (en) * | 2014-11-06 | 2016-05-12 | Bruce Cilli | System and method for exporting real-time user equipment and bearer state information |
US9906973B2 (en) | 2014-11-28 | 2018-02-27 | Industrial Technology Research Institute | Evolved NodeB and traffic dispatch method thereof |
DE102014018873A1 (en) | 2014-12-16 | 2016-06-30 | Unify Gmbh & Co. Kg | A telecommunications device and method for establishing an RTC connection between a first endpoint and a second endpoint |
US9477975B2 (en) | 2015-02-03 | 2016-10-25 | Twilio, Inc. | System and method for a media intelligence platform |
US20160255632A1 (en) * | 2015-02-27 | 2016-09-01 | Nokia Solutions And Networks Oy | LTE/WI-FI Aggregation For Existing Network Nodes |
US10542457B2 (en) * | 2015-04-20 | 2020-01-21 | Qualcomm Incorporated | Enhanced compression formats for data compression |
CN107211329B (en) * | 2015-05-05 | 2020-07-10 | 诸暨易和项目投资有限公司 | Circuit domain fallback method, network equipment and system |
US10148509B2 (en) | 2015-05-13 | 2018-12-04 | Oracle International Corporation | Methods, systems, and computer readable media for session based software defined networking (SDN) management |
US9948703B2 (en) | 2015-05-14 | 2018-04-17 | Twilio, Inc. | System and method for signaling through data storage |
US10419891B2 (en) | 2015-05-14 | 2019-09-17 | Twilio, Inc. | System and method for communicating through multiple endpoints |
US9826422B2 (en) | 2015-05-28 | 2017-11-21 | Alcatel-Lucent Usa Inc. | System and method for controlling an operation of an application |
WO2016193864A1 (en) * | 2015-05-29 | 2016-12-08 | Nokia Technologies Oy | Minimization of service interruption during relay reselection in device-to-device (d2d) based user equipment (ue)-to-network relay |
US9838893B2 (en) | 2015-06-25 | 2017-12-05 | Alcatel Lucent | System and method for cooperatively controlling an application |
US10869209B2 (en) * | 2015-10-06 | 2020-12-15 | Lg Electronics Inc. | Method and device for transmitting/receiving data to/from base station in wireless communication system |
US9860786B1 (en) | 2016-02-01 | 2018-01-02 | Sprint Spectrum L.P. | Efficient backhaul for relay nodes |
US10659349B2 (en) | 2016-02-04 | 2020-05-19 | Twilio Inc. | Systems and methods for providing secure network exchanged for a multitenant virtual private cloud |
US9961588B2 (en) | 2016-02-24 | 2018-05-01 | Keysight Technologies Singapore (Holdings) Pte. Ltd. | Methods, systems, and computer readable media for distributing monitored network traffic |
CN108781365B (en) * | 2016-03-22 | 2022-04-26 | 瑞典爱立信有限公司 | Method and network node for multiple connectivity handling in a communication system |
WO2017169000A1 (en) * | 2016-03-31 | 2017-10-05 | ソニー株式会社 | Relay device, terminal device, and communication method |
US11425777B2 (en) * | 2016-05-13 | 2022-08-23 | Telecom Italia S.P.A. | Method and system for data tunneling in device to device communication assisted by a telecommunication network |
US10063713B2 (en) | 2016-05-23 | 2018-08-28 | Twilio Inc. | System and method for programmatic device connectivity |
US10686902B2 (en) | 2016-05-23 | 2020-06-16 | Twilio Inc. | System and method for a multi-channel notification service |
CN107707475B (en) * | 2016-08-09 | 2020-03-06 | 大唐移动通信设备有限公司 | Data transmission method and system |
CN108307528B (en) * | 2016-08-11 | 2021-05-25 | 中兴通讯股份有限公司 | Information transmission method, device and system |
US10499278B2 (en) * | 2016-08-31 | 2019-12-03 | Qualcomm Incorporated | Header compression for reduced bandwidth wireless devices |
EP4274373A3 (en) * | 2016-10-17 | 2024-01-17 | Sk Telecom Co., Ltd. | Base station device and qos control method in wireless section |
US10623989B2 (en) * | 2016-10-27 | 2020-04-14 | Qualcomm Incorporated | Techniques and apparatuses for unidirectional robust header compression |
US10142008B1 (en) | 2016-12-15 | 2018-11-27 | Sprint Communications Company L.P. | Data compression for wireless relays in a data communication network |
CN106658380A (en) * | 2016-12-30 | 2017-05-10 | 宇龙计算机通信科技(深圳)有限公司 | Data multiplex method of device and device relay network and intelligent terminal |
US10893446B2 (en) * | 2017-01-05 | 2021-01-12 | Lg Electronics Inc. | Method and apparatus for transmitting QoS flow to DRB mapping rule |
WO2018144855A1 (en) * | 2017-02-03 | 2018-08-09 | Intel IP Corporation | Quality of service flow to data radio bearer mapping override bit |
KR102012463B1 (en) * | 2017-02-28 | 2019-08-20 | 주식회사 이노와이어리스 | data processing data in mobile Xhaul network |
US10264612B2 (en) * | 2017-03-15 | 2019-04-16 | Qualcomm Incorporated | Discovery of controller function for wireless backhaul using cellular radio access technology |
CN108924824B (en) * | 2017-03-20 | 2020-10-09 | 电信科学技术研究院 | EPS bearing identifier distribution method and device, SMF and PCF |
WO2018175817A1 (en) * | 2017-03-23 | 2018-09-27 | Intel Corporation | Advanced radio resource management in next-gen multi-hop relaying cellular network |
JP6856117B2 (en) * | 2017-03-23 | 2021-04-07 | 日本電気株式会社 | Wireless relay station and communication method |
WO2018173461A1 (en) * | 2017-03-23 | 2018-09-27 | 日本電気株式会社 | Base station, wireless relay station, communication method, and non-temporary computer-readable medium storing program therein |
US10028186B1 (en) | 2017-03-24 | 2018-07-17 | Sprint Communications Company L.P. | Wireless communication system to redirect use equipment (UE) from a wireless relay to a donor base station |
US10433203B1 (en) | 2017-04-19 | 2019-10-01 | Sprint Spectrum L.P. | Providing a quality of service to wireless devices attached to relay access nodes |
US10299185B1 (en) | 2017-04-24 | 2019-05-21 | Sprint Communications Company L.P. | Wireless relay quality-of-service based on relay-delivered media services |
CN109245845B (en) * | 2017-05-05 | 2022-05-13 | 中兴通讯股份有限公司 | Signaling transmission method and device |
US10469358B2 (en) * | 2017-05-18 | 2019-11-05 | Qualcomm Incorporated | Wireless multihop relay |
WO2019001697A1 (en) | 2017-06-28 | 2019-01-03 | Huawei Technologies Co., Ltd. | Sub-band compression domain processing for uplink mimo systems |
US10873479B2 (en) * | 2017-08-03 | 2020-12-22 | Qualcomm Incorporated | Techniques and apparatuses for forwarding in multi-hop wireless networks via multi-layer tunneling and centralized control |
US11089527B2 (en) | 2018-01-17 | 2021-08-10 | T-Mobile Usa, Inc. | Telecommunications network bearer allocation and deallocation |
US10567954B2 (en) | 2018-01-18 | 2020-02-18 | At&T Intellectual Property I, L.P. | Integrated access backhaul under a non-standalone network architecture for 5G or other next generation network |
EP3737204B1 (en) | 2018-02-11 | 2022-03-09 | Guangdong Oppo Mobile Telecommunications Corp., Ltd. | Mobile communication system, method and device |
KR102322380B1 (en) * | 2018-02-14 | 2021-11-10 | 주식회사 케이티 | Methods for processing Uplink user data of relay node and Apparatuses thereof |
CN110418427B (en) * | 2018-04-28 | 2021-06-08 | 华为技术有限公司 | Communication method and device |
CN116406033A (en) | 2018-05-11 | 2023-07-07 | 大唐移动通信设备有限公司 | Bearer mapping method of wireless backhaul node, wireless backhaul node and donor base station |
CN110636583B (en) * | 2018-06-21 | 2021-08-13 | 华为技术有限公司 | Path changing method and device |
US10904795B2 (en) * | 2018-06-21 | 2021-01-26 | Qualcomm Incorporated | Remapping quality of service flows among data radio bearers |
CN110636570B (en) * | 2018-06-25 | 2022-08-02 | 中兴通讯股份有限公司 | Method and device for processing IAB node information in IAB network |
GB2576204B (en) | 2018-07-27 | 2021-02-17 | Samsung Electronics Co Ltd | Operation of automatic repeat request (ARQ) |
CN112567796B (en) * | 2018-08-09 | 2023-05-30 | 中兴通讯股份有限公司 | Method, apparatus and system for integrated access and backhaul bearer management |
WO2020036585A1 (en) * | 2018-08-13 | 2020-02-20 | Cisco Technology, Inc. | Centralized son assisted multi hop discovery and management |
CN110876175B (en) * | 2018-08-31 | 2021-07-16 | 大唐移动通信设备有限公司 | Link interruption processing method, relay node and computer readable storage medium |
WO2020056364A1 (en) * | 2018-09-14 | 2020-03-19 | Intel Corporation | Signaling configurations for cell selection in fifth generation (5g) new radio (nr) (5g-nr) integrated access and backhaul (iab) |
CN112771919A (en) * | 2018-09-27 | 2021-05-07 | 上海诺基亚贝尔股份有限公司 | Generation of tunnel endpoint identifiers for packet tunneling |
CN110971363B (en) | 2018-09-28 | 2022-03-08 | 华为技术有限公司 | Method and device for communication method of Ethernet data |
US20210352700A1 (en) * | 2018-11-01 | 2021-11-11 | Lenovo (Beijing) Limited | A buffer status report indicator |
EP3878201A4 (en) * | 2018-11-05 | 2022-08-03 | Parallel Wireless, Inc. | Locally-generated teids for core high availability |
US11349557B2 (en) | 2018-11-30 | 2022-05-31 | At&T Intellectual Property I, L.P. | System model and architecture for mobile integrated access and backhaul in advanced networks |
WO2020122676A1 (en) | 2018-12-14 | 2020-06-18 | Samsung Electronics Co., Ltd. | Apparatus and method for initial access in wireless communication system |
WO2020228937A1 (en) * | 2019-05-13 | 2020-11-19 | Nokia Technologies Oy | Address assignment |
US11239898B1 (en) * | 2019-11-19 | 2022-02-01 | T-Mobile Innovations Llc | Relaying data to multiple access points |
EP3913881A1 (en) * | 2020-05-20 | 2021-11-24 | Nokia Solutions and Networks Oy | Header compression management in a radio access network |
US11343715B1 (en) * | 2020-08-23 | 2022-05-24 | Rockwell Collins, Inc. | Header compression for network |
CN112399480B (en) * | 2020-11-05 | 2023-09-08 | 中国联合网络通信集团有限公司 | Method, apparatus and storage medium for reducing transmission overhead |
Citations (51)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5999980A (en) * | 1996-09-12 | 1999-12-07 | Cabletron Systems, Inc. | Apparatus and method for setting a congestion indicate bit in an backwards RM cell on an ATM network |
US20030223381A1 (en) * | 2002-06-04 | 2003-12-04 | Osmo Schroderus | Method for controlling parties in real-time data communication |
US6839339B1 (en) * | 2000-02-02 | 2005-01-04 | Lucent Technologies Inc. | Header compression for general packet radio service tunneling protocol (GTP)-encapsulated packets |
US20050265363A1 (en) * | 2002-09-24 | 2005-12-01 | Xiaobao Chen | Methods and apparatus for data transfer in a packet-switched data network |
US20060139869A1 (en) * | 2004-12-29 | 2006-06-29 | Matusz Pawel O | Extended compression arrangements within telecommunication systems and associated methods |
US20070072604A1 (en) * | 2005-08-17 | 2007-03-29 | Nortel Networks Limited | Method and system for a wireless multi-hop relay network |
US20070171871A1 (en) * | 2006-01-04 | 2007-07-26 | Nokia Corporation | Secure distributed handover signaling |
US20070213060A1 (en) * | 2006-03-07 | 2007-09-13 | Interdigital Technology Corporation | Method and apparatus for supporting handoff in an lte gtp based wireless communication system |
US20070230352A1 (en) * | 2006-03-28 | 2007-10-04 | Nec Laboratories America, Inc. | Multipath Routing Architecture for Large Data Transfers |
US7301947B2 (en) * | 2001-06-27 | 2007-11-27 | Nokia Corporation | Transmission of compression identifier of headers on data packet connection |
US20080080399A1 (en) * | 2006-10-03 | 2008-04-03 | Interdigital Technology Corporation | Enhanced node b configuration with a universal integrated circuit card |
US20080123660A1 (en) * | 2006-08-09 | 2008-05-29 | Interdigital Technology Corporation | Method and apparatus for providing differentiated quality of service for packets in a particular flow |
US20080144555A1 (en) * | 2006-11-29 | 2008-06-19 | Samsung Electronics Co., Ltd. | Apparatus and method for identifying header compression channel in broadband wireless communication system |
US20080165719A1 (en) * | 2007-01-05 | 2008-07-10 | Motorola, Inc. | Method and apparatus for relay zone bandwidth allocation |
US20080181176A1 (en) * | 2006-10-30 | 2008-07-31 | Hyunjeong Lee | Framework to design new mac message exchange procedure related to mobile station (ms) handover in multi-hop relay broadband wireless access network |
US20080219203A1 (en) * | 2007-03-09 | 2008-09-11 | Industrial Technology Research Institute. | Method for mac process and flexible connection in wireless multi-hop relaying network |
US20080240439A1 (en) * | 2007-03-15 | 2008-10-02 | Interdigital Technology Corporation | Methods and apparatus to facilitate data and security context transfer, and re-initialization during mobile device handover |
US20080268846A1 (en) * | 2007-02-12 | 2008-10-30 | Interdigital Technology Corporation | Method and apparatus for supporting handoff from gprs/geran to lte eutran |
US20080268852A1 (en) * | 2004-03-30 | 2008-10-30 | Matsushita Electric Industrial Co., Ltd. | Delayed Base Station Relocation in Distributed Radio Access Networks |
US20090042576A1 (en) * | 2007-07-27 | 2009-02-12 | Interdigital Patent Holdings, Inc. | Method and apparatus for handling mobility between non-3gpp to 3gpp networks |
US20090043902A1 (en) * | 2007-04-12 | 2009-02-12 | Stefano Faccin | Packet data network connectivity domain selection and bearer setup |
US20090052409A1 (en) * | 2004-07-30 | 2009-02-26 | Orange Sa | Telecommunications apparatus and method |
US20090111476A1 (en) * | 2007-10-29 | 2009-04-30 | Nokia Siemens Networks Oy | Allocation of user equipment identifier |
US20090111423A1 (en) * | 2007-10-25 | 2009-04-30 | Interdigital Patent Holdings, Inc. | Non-access stratum architecture and protocol enhancements for long term evolution mobile units |
US20090196177A1 (en) * | 2008-02-01 | 2009-08-06 | Nokia Siemens Networks Oy | Method, apparatus and computer program for uplink scheduling in a network that employs relay nodes |
US20090201878A1 (en) * | 2007-11-19 | 2009-08-13 | Cellco Partnership D/B/A Verizon Wireless | Low latency handover between wireless communication networks using different radio access technologies |
US20090215459A1 (en) * | 2008-02-25 | 2009-08-27 | Richard Lee-Chee Kuo | Method and Apparatus for Improving Random Access Procedure for Handover |
US20090238207A1 (en) * | 2008-03-21 | 2009-09-24 | Research In Motion Limited | Dynamic Aggregated Maximum Bit Rate for Evolved Packet System Non-Guaranteed Bit Rate Quality of Service Enforcement and Network Bandwidth Utilization |
US20090257432A1 (en) * | 2006-03-16 | 2009-10-15 | Tsuyoshi Yamaguchi | Terminal |
US20090296626A1 (en) * | 2008-05-30 | 2009-12-03 | Nokia Corporation | Method, apparatus and computer program for relay selection |
US20100091823A1 (en) * | 2008-10-13 | 2010-04-15 | Cisco Technology, Inc. | Two-hop Relay for Reducing Distance Vector Routing Information |
US20100097976A1 (en) * | 2008-10-16 | 2010-04-22 | Qualcomm Incorporated | Incremental redundancy relays for wireless communication |
US20100103861A1 (en) * | 2008-10-24 | 2010-04-29 | Qualcomm Incorporated | Cell relay packet routing |
US20100208645A1 (en) * | 2007-10-02 | 2010-08-19 | Haemaelaeinen Jyri | Method, Computer Program, Apparatus and System |
US20100226314A1 (en) * | 2007-09-27 | 2010-09-09 | Lixiang Xu | Method for user equipment performing direct communications via hnb access systems |
US20100238805A1 (en) * | 2007-08-22 | 2010-09-23 | Reiner Ludwig | Data Transmission Control Methods And Devices |
US20100246533A1 (en) * | 2006-08-18 | 2010-09-30 | Niklas Lundin | Intersystem Change Involving Mapping Between Different Types Of Radio Bearers |
US20100260126A1 (en) * | 2009-04-13 | 2010-10-14 | Qualcomm Incorporated | Split-cell relay packet routing |
US20100309881A1 (en) * | 2007-11-29 | 2010-12-09 | Samsung Electronics Co., Ltd. | Mobile communication system and tunnel management method thereof |
US7876808B2 (en) * | 2006-11-30 | 2011-01-25 | Broadcom Corp. | Method and apparatus for adaptive noise and/or signal filtering in an HSDPA channel quality indicator (CQI) selection |
US7881247B2 (en) * | 2006-08-17 | 2011-02-01 | Interdigital Technology Corporation | Method and apparatus for providing efficient precoding feedback in a MIMO wireless communication system |
US20110044279A1 (en) * | 2008-04-30 | 2011-02-24 | Niklas Johansson | Self-Backhauling in LTE |
US7986915B1 (en) * | 2006-02-24 | 2011-07-26 | Nortel Networks Limited | Method and system for a wireless multi-hop relay network |
US20110222428A1 (en) * | 2008-11-18 | 2011-09-15 | Nokia Corporation | Relaying in a communication system |
US8054806B2 (en) * | 2007-08-14 | 2011-11-08 | Alcatel Lucent | Method and apparatus for radio link failure recovery in a wireless communications network |
US8055263B2 (en) * | 2005-10-05 | 2011-11-08 | Samsung Electronics Co., Ltd. | Fast cell selection method and apparatus for high speed downlink packet access system |
US8064909B2 (en) * | 2007-10-25 | 2011-11-22 | Cisco Technology, Inc. | Interworking gateway for mobile nodes |
US8064395B2 (en) * | 2007-03-26 | 2011-11-22 | Vodafone Group Plc | Data transmission |
US20120120831A1 (en) * | 2009-06-05 | 2012-05-17 | Panasonic Corporation | Qos multiplexing via base station-relay node interface |
US20120140666A1 (en) * | 2009-06-08 | 2012-06-07 | Ntt Docomo, Inc. | Mobile communication system, relay node, radio base station, and gateway device |
US20120155375A1 (en) * | 2009-08-26 | 2012-06-21 | Huawei Technologies Co., Ltd. | Method and Apparatus for Header Compression in Network Relay Scenario |
Family Cites Families (53)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5963865A (en) | 1997-11-24 | 1999-10-05 | Telefonaktiebolaget Lm Ericsson | Traffic channel assignment in a cellular telephone system using an uplink interference driven frequency packing method |
JP3441367B2 (en) | 1998-05-25 | 2003-09-02 | 三菱電機株式会社 | Multiple communication connection setting method |
FI106288B (en) * | 1998-10-06 | 2000-12-29 | Nokia Networks Oy | Identifying a mobile station in a packet radio network |
US6608841B1 (en) | 1999-12-30 | 2003-08-19 | Nokia Networks Oy | System and method for achieving robust IP/UDP/RTP header compression in the presence of unreliable networks |
US6785510B2 (en) | 2000-03-09 | 2004-08-31 | Salbu Resarch & Development (Proprietary) Limited | Routing in a multi-station network |
TW490950B (en) | 2000-05-09 | 2002-06-11 | Nutex Comm Corp | Method and system for accessing and displaying area information |
FI111493B (en) | 2000-09-22 | 2003-07-31 | Nokia Corp | Defining a Contextual Tag in Compression of Header Fields |
US6967964B1 (en) | 2000-10-03 | 2005-11-22 | Telefonaktiebolaget Lm Ericsson (Publ) | Context identification using header compression key at link layer |
WO2002056564A1 (en) * | 2001-01-16 | 2002-07-18 | Operax Ab | Network resource manager in a mobile telecommunication system |
JP4684649B2 (en) * | 2002-06-21 | 2011-05-18 | トムソン ライセンシング | Registration of WLAN as a UMTS routing area in WLAN-UMTS interworking |
US7209491B2 (en) * | 2002-06-28 | 2007-04-24 | Nokia Corporation | Method and system for transmitting data in a packet based communication network |
EP1519519B1 (en) | 2003-09-23 | 2011-04-20 | Panasonic Corporation | Protocol context transfer in a mobile communication system |
TWI273853B (en) | 2004-02-11 | 2007-02-11 | Chunghwa Telecom Co Ltd | Method for planning and optimizing orientation angle of cellular antenna for base station |
KR20060009433A (en) | 2004-07-22 | 2006-02-01 | 삼성전자주식회사 | Method for packet service in a mobile communication using a header compression |
EP1689130A1 (en) * | 2005-02-07 | 2006-08-09 | Lg Electronics Inc. | Method for settling an error in a radio link control |
KR100762650B1 (en) | 2005-03-10 | 2007-10-01 | 삼성전자주식회사 | Transmission control method for tcp bi-directional transmission in asymmetric bandwidth pre-allocated subscriber network and apparatus therefor |
US7656835B2 (en) * | 2005-05-18 | 2010-02-02 | Nokia Corporation | Method for informing changed communications capabilities |
KR100744374B1 (en) * | 2005-07-15 | 2007-07-30 | 삼성전자주식회사 | Handover method between core network entities in packet-switched based network and therefor apparatus |
EP1748662A1 (en) * | 2005-07-25 | 2007-01-31 | Orange S.A. | Mobile network performance evaluation system and method |
CN1964225B (en) | 2005-11-11 | 2013-03-13 | 上海贝尔阿尔卡特股份有限公司 | A method to control wireless access, relay station and base station |
US20070213058A1 (en) | 2006-03-08 | 2007-09-13 | Interdigital Technology Corporation | Method and apparatus for supporting handoff and serving radio network subsystem relocation procedures in a single tunnel gprs-based wireless communication system |
EP2001246A2 (en) | 2006-03-28 | 2008-12-10 | NTT DoCoMo, Inc. | Base station, route control device, and handover control method |
JP5181472B2 (en) | 2006-04-21 | 2013-04-10 | 日本電気株式会社 | Communication control method |
CN101047421B (en) * | 2006-04-28 | 2011-12-07 | 华为技术有限公司 | Device and method for mobile communication using repeater station |
CA2651076A1 (en) | 2006-05-03 | 2007-11-15 | Interdigital Technology Corporation | Wireless communication method and system for activating multiple service bearers via efficient packet data protocol context activation procedures |
US8483123B2 (en) * | 2006-06-30 | 2013-07-09 | Nokia Corporation | QoS request and information distribution for wireless relay networks |
CN201134894Y (en) | 2006-07-12 | 2008-10-15 | 美商内数位科技公司 | Activation of multiple bearing services in long-term evolution system |
TW200805974A (en) | 2006-07-12 | 2008-01-16 | Interdigital Tech Corp | Activation of multiple bearer services in a long term evolution system |
CN101132564B (en) * | 2006-08-25 | 2011-09-14 | 华为技术有限公司 | Base station, relay station, wireless relay communication system and method thereof |
JP5192201B2 (en) | 2006-09-07 | 2013-05-08 | 財團法人工業技術研究院 | Wireless communication system and method |
US7995524B2 (en) * | 2006-09-07 | 2011-08-09 | Industrial Technology Research Institute | Wireless communication system and method |
KR20080024745A (en) * | 2006-09-14 | 2008-03-19 | 삼성전자주식회사 | Apparatus and method for operation of radio access network in broadband mobile communication system |
GB2442782A (en) | 2006-10-13 | 2008-04-16 | Fujitsu Ltd | Wireless communication systems |
JP4983208B2 (en) * | 2006-11-07 | 2012-07-25 | 富士通株式会社 | Relay station, wireless communication method |
EP1921807A1 (en) | 2006-11-13 | 2008-05-14 | Alcatel Lucent | Method for forwarding MAC protocol data units in a mobile radio communication network, corresponding communication end point and relay station |
MX2009006070A (en) * | 2006-12-15 | 2009-07-07 | Sharp Kk | Radio communication system and radio transmission path control method. |
US20080165776A1 (en) | 2007-01-08 | 2008-07-10 | Zhifeng Tao | Relay Tunneling in Wireless Multi-User Multi-Hop Relay Networks |
CN101227714B (en) | 2007-01-18 | 2011-04-06 | 华为技术有限公司 | System, apparatus and method for sharing network resource |
EP2575403B1 (en) | 2007-01-30 | 2016-03-02 | Nec Corporation | Mobile communication system, core network node, access network, terminal and corresponding multicast data distribution methods |
ATE523051T1 (en) | 2007-02-06 | 2011-09-15 | Ericsson Telefon Ab L M | METHOD AND SYSTEM FOR INTRA-E-UTRAN HANDOVER |
WO2008102547A1 (en) * | 2007-02-19 | 2008-08-28 | Panasonic Corporation | QoS ESTABLISHING METHOD, AND MOBILE TERMINAL AND RELAY NODE USED IN THE METHOD |
FI20075252A0 (en) | 2007-04-13 | 2007-04-13 | Nokia Corp | Procedure, radio system, mobile terminal and base station |
EP2158714B1 (en) * | 2007-05-04 | 2019-08-21 | Nokia Solutions and Networks Oy | Aggregated harq report |
US8340029B2 (en) * | 2007-07-06 | 2012-12-25 | Zte (Usa) Inc. | Resource allocation in wireless multi-hop relay networks |
US20090080422A1 (en) * | 2007-09-21 | 2009-03-26 | Posdata Co., Ltd. | Header-compression packet processing method, mobile station, base station, and control station in wireless communication system |
EP1973274B1 (en) * | 2007-10-05 | 2010-06-02 | Industrial Technology Research Institute | Method for MAC process and flexible connection in wireless multi-hop relaying network |
CN101150587B (en) * | 2007-10-24 | 2010-07-07 | 华为技术有限公司 | A method, device and system for traffic switching of multi-protocol label switching traffic engineering |
JP4882959B2 (en) * | 2007-10-26 | 2012-02-22 | 富士通株式会社 | Packet communication method, packet communication system, management device, wireless terminal, and packet communication device |
CN100583800C (en) * | 2007-11-23 | 2010-01-20 | 清华大学 | Method for multicast employing single static bidirectional sharing tree in flexible wire type tunnel |
FI20070995A0 (en) | 2007-12-19 | 2007-12-19 | Nokia Siemens Networks Oy | Scalable deployment of network nodes |
US20090213778A1 (en) * | 2008-01-14 | 2009-08-27 | Zhifeng Tao | Fragmentation and Packing for Wireless Multi-User Multi-Hop Relay Networks |
US9160566B2 (en) * | 2009-04-10 | 2015-10-13 | Qualcomm Incorporated | QOS mapping for relay nodes |
US8724472B2 (en) * | 2010-03-25 | 2014-05-13 | Qualcomm Incorporated | Data radio bearer mapping in a telecommunication network with relays |
-
2009
- 2009-10-21 US US12/603,392 patent/US8902805B2/en active Active
- 2009-10-22 US US12/604,205 patent/US9088939B2/en active Active
- 2009-10-22 US US12/604,189 patent/US8401068B2/en active Active
- 2009-10-22 US US12/604,198 patent/US20100103857A1/en not_active Abandoned
- 2009-10-22 US US12/604,210 patent/US20100103845A1/en not_active Abandoned
- 2009-10-22 US US12/604,215 patent/US20100103864A1/en not_active Abandoned
- 2009-10-23 TW TW098136021A patent/TW201032545A/en unknown
- 2009-10-23 CN CN2009801418892A patent/CN102197679A/en active Pending
- 2009-10-23 KR KR1020117011812A patent/KR101383186B1/en active IP Right Grant
- 2009-10-23 TW TW098135994A patent/TWI424766B/en active
- 2009-10-23 KR KR1020117011791A patent/KR101252031B1/en active IP Right Grant
- 2009-10-23 WO PCT/US2009/061939 patent/WO2010048571A1/en active Application Filing
- 2009-10-23 JP JP2011533388A patent/JP5209796B2/en active Active
- 2009-10-23 CN CN200980141865.7A patent/CN102197693B/en active Active
- 2009-10-23 ES ES09744859T patent/ES2427172T3/en active Active
- 2009-10-23 WO PCT/US2009/061943 patent/WO2010048574A2/en active Application Filing
- 2009-10-23 JP JP2011533385A patent/JP5384655B2/en active Active
- 2009-10-23 US US12/605,184 patent/US20100103865A1/en not_active Abandoned
- 2009-10-23 TW TW098136014A patent/TW201019760A/en unknown
- 2009-10-23 WO PCT/US2009/061947 patent/WO2010048577A1/en active Application Filing
- 2009-10-23 TW TW098135982A patent/TWI424728B/en active
- 2009-10-23 CN CN201610404530.1A patent/CN106102121B/en active Active
- 2009-10-23 WO PCT/US2009/061937 patent/WO2010048569A1/en active Application Filing
- 2009-10-23 EP EP09749249A patent/EP2359654A1/en not_active Withdrawn
- 2009-10-23 WO PCT/US2009/061934 patent/WO2010048566A1/en active Application Filing
- 2009-10-23 KR KR1020137021816A patent/KR20130106888A/en not_active Application Discontinuation
- 2009-10-23 EP EP09744859.1A patent/EP2359642B1/en active Active
- 2009-10-23 BR BRPI0919845-8A patent/BRPI0919845B1/en active IP Right Grant
- 2009-10-23 TW TW098136000A patent/TW201019762A/en unknown
- 2009-10-23 WO PCT/US2009/061933 patent/WO2010048565A1/en active Application Filing
- 2009-10-23 TW TW098135990A patent/TW201032544A/en unknown
- 2009-10-26 EP EP09744866A patent/EP2359566A2/en not_active Withdrawn
- 2009-10-26 CN CN2009801418820A patent/CN102197629A/en active Pending
- 2009-10-26 KR KR1020117011797A patent/KR20110074930A/en active IP Right Grant
- 2009-10-26 KR KR1020127032534A patent/KR20130008642A/en not_active Application Discontinuation
- 2009-10-26 TW TW098136223A patent/TW201032547A/en unknown
- 2009-10-26 JP JP2011533413A patent/JP2012507209A/en active Pending
- 2009-10-26 WO PCT/US2009/062100 patent/WO2010048621A2/en active Application Filing
-
2013
- 2013-04-02 JP JP2013076891A patent/JP5579895B2/en active Active
Patent Citations (56)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5999980A (en) * | 1996-09-12 | 1999-12-07 | Cabletron Systems, Inc. | Apparatus and method for setting a congestion indicate bit in an backwards RM cell on an ATM network |
US6839339B1 (en) * | 2000-02-02 | 2005-01-04 | Lucent Technologies Inc. | Header compression for general packet radio service tunneling protocol (GTP)-encapsulated packets |
US7301947B2 (en) * | 2001-06-27 | 2007-11-27 | Nokia Corporation | Transmission of compression identifier of headers on data packet connection |
US20030223381A1 (en) * | 2002-06-04 | 2003-12-04 | Osmo Schroderus | Method for controlling parties in real-time data communication |
US20050265363A1 (en) * | 2002-09-24 | 2005-12-01 | Xiaobao Chen | Methods and apparatus for data transfer in a packet-switched data network |
US20080268852A1 (en) * | 2004-03-30 | 2008-10-30 | Matsushita Electric Industrial Co., Ltd. | Delayed Base Station Relocation in Distributed Radio Access Networks |
US20090052409A1 (en) * | 2004-07-30 | 2009-02-26 | Orange Sa | Telecommunications apparatus and method |
US20060139869A1 (en) * | 2004-12-29 | 2006-06-29 | Matusz Pawel O | Extended compression arrangements within telecommunication systems and associated methods |
US20070072604A1 (en) * | 2005-08-17 | 2007-03-29 | Nortel Networks Limited | Method and system for a wireless multi-hop relay network |
US8055263B2 (en) * | 2005-10-05 | 2011-11-08 | Samsung Electronics Co., Ltd. | Fast cell selection method and apparatus for high speed downlink packet access system |
US20070171871A1 (en) * | 2006-01-04 | 2007-07-26 | Nokia Corporation | Secure distributed handover signaling |
US7986915B1 (en) * | 2006-02-24 | 2011-07-26 | Nortel Networks Limited | Method and system for a wireless multi-hop relay network |
US20070213060A1 (en) * | 2006-03-07 | 2007-09-13 | Interdigital Technology Corporation | Method and apparatus for supporting handoff in an lte gtp based wireless communication system |
US20090257432A1 (en) * | 2006-03-16 | 2009-10-15 | Tsuyoshi Yamaguchi | Terminal |
US20070230352A1 (en) * | 2006-03-28 | 2007-10-04 | Nec Laboratories America, Inc. | Multipath Routing Architecture for Large Data Transfers |
US20080123660A1 (en) * | 2006-08-09 | 2008-05-29 | Interdigital Technology Corporation | Method and apparatus for providing differentiated quality of service for packets in a particular flow |
US7881247B2 (en) * | 2006-08-17 | 2011-02-01 | Interdigital Technology Corporation | Method and apparatus for providing efficient precoding feedback in a MIMO wireless communication system |
US20100246533A1 (en) * | 2006-08-18 | 2010-09-30 | Niklas Lundin | Intersystem Change Involving Mapping Between Different Types Of Radio Bearers |
US20080080399A1 (en) * | 2006-10-03 | 2008-04-03 | Interdigital Technology Corporation | Enhanced node b configuration with a universal integrated circuit card |
US20080181176A1 (en) * | 2006-10-30 | 2008-07-31 | Hyunjeong Lee | Framework to design new mac message exchange procedure related to mobile station (ms) handover in multi-hop relay broadband wireless access network |
US20080144555A1 (en) * | 2006-11-29 | 2008-06-19 | Samsung Electronics Co., Ltd. | Apparatus and method for identifying header compression channel in broadband wireless communication system |
US7876808B2 (en) * | 2006-11-30 | 2011-01-25 | Broadcom Corp. | Method and apparatus for adaptive noise and/or signal filtering in an HSDPA channel quality indicator (CQI) selection |
US20080165719A1 (en) * | 2007-01-05 | 2008-07-10 | Motorola, Inc. | Method and apparatus for relay zone bandwidth allocation |
US20080268846A1 (en) * | 2007-02-12 | 2008-10-30 | Interdigital Technology Corporation | Method and apparatus for supporting handoff from gprs/geran to lte eutran |
US20080219203A1 (en) * | 2007-03-09 | 2008-09-11 | Industrial Technology Research Institute. | Method for mac process and flexible connection in wireless multi-hop relaying network |
US20080240439A1 (en) * | 2007-03-15 | 2008-10-02 | Interdigital Technology Corporation | Methods and apparatus to facilitate data and security context transfer, and re-initialization during mobile device handover |
US8064395B2 (en) * | 2007-03-26 | 2011-11-22 | Vodafone Group Plc | Data transmission |
US20090043902A1 (en) * | 2007-04-12 | 2009-02-12 | Stefano Faccin | Packet data network connectivity domain selection and bearer setup |
US20090042576A1 (en) * | 2007-07-27 | 2009-02-12 | Interdigital Patent Holdings, Inc. | Method and apparatus for handling mobility between non-3gpp to 3gpp networks |
US8054806B2 (en) * | 2007-08-14 | 2011-11-08 | Alcatel Lucent | Method and apparatus for radio link failure recovery in a wireless communications network |
US20100238805A1 (en) * | 2007-08-22 | 2010-09-23 | Reiner Ludwig | Data Transmission Control Methods And Devices |
US20100226314A1 (en) * | 2007-09-27 | 2010-09-09 | Lixiang Xu | Method for user equipment performing direct communications via hnb access systems |
US20100208645A1 (en) * | 2007-10-02 | 2010-08-19 | Haemaelaeinen Jyri | Method, Computer Program, Apparatus and System |
US20090111423A1 (en) * | 2007-10-25 | 2009-04-30 | Interdigital Patent Holdings, Inc. | Non-access stratum architecture and protocol enhancements for long term evolution mobile units |
US8064909B2 (en) * | 2007-10-25 | 2011-11-22 | Cisco Technology, Inc. | Interworking gateway for mobile nodes |
US20090111476A1 (en) * | 2007-10-29 | 2009-04-30 | Nokia Siemens Networks Oy | Allocation of user equipment identifier |
US20090201878A1 (en) * | 2007-11-19 | 2009-08-13 | Cellco Partnership D/B/A Verizon Wireless | Low latency handover between wireless communication networks using different radio access technologies |
US20100309881A1 (en) * | 2007-11-29 | 2010-12-09 | Samsung Electronics Co., Ltd. | Mobile communication system and tunnel management method thereof |
US20090196177A1 (en) * | 2008-02-01 | 2009-08-06 | Nokia Siemens Networks Oy | Method, apparatus and computer program for uplink scheduling in a network that employs relay nodes |
US20090215459A1 (en) * | 2008-02-25 | 2009-08-27 | Richard Lee-Chee Kuo | Method and Apparatus for Improving Random Access Procedure for Handover |
US20090238207A1 (en) * | 2008-03-21 | 2009-09-24 | Research In Motion Limited | Dynamic Aggregated Maximum Bit Rate for Evolved Packet System Non-Guaranteed Bit Rate Quality of Service Enforcement and Network Bandwidth Utilization |
US20110044279A1 (en) * | 2008-04-30 | 2011-02-24 | Niklas Johansson | Self-Backhauling in LTE |
US20090296626A1 (en) * | 2008-05-30 | 2009-12-03 | Nokia Corporation | Method, apparatus and computer program for relay selection |
US20100091823A1 (en) * | 2008-10-13 | 2010-04-15 | Cisco Technology, Inc. | Two-hop Relay for Reducing Distance Vector Routing Information |
US20100097976A1 (en) * | 2008-10-16 | 2010-04-22 | Qualcomm Incorporated | Incremental redundancy relays for wireless communication |
US20100103863A1 (en) * | 2008-10-24 | 2010-04-29 | Qualcomm Incorporated | BEARER QoS MAPPING FOR CELL RELAYS |
US20100103845A1 (en) * | 2008-10-24 | 2010-04-29 | Qualcomm Incorporated | Cell relay mobility procedures |
US20100103861A1 (en) * | 2008-10-24 | 2010-04-29 | Qualcomm Incorporated | Cell relay packet routing |
US20100103857A1 (en) * | 2008-10-24 | 2010-04-29 | Qualcomm Incorporated | Cell relay network attachment procedures |
US20100103862A1 (en) * | 2008-10-24 | 2010-04-29 | Qualcomm Incorporated | Device attachment and bearer activation using cell relays |
US20100103865A1 (en) * | 2008-10-24 | 2010-04-29 | Qualcomm Incorporated | Header compression for cell relay communications |
US20110222428A1 (en) * | 2008-11-18 | 2011-09-15 | Nokia Corporation | Relaying in a communication system |
US20100260126A1 (en) * | 2009-04-13 | 2010-10-14 | Qualcomm Incorporated | Split-cell relay packet routing |
US20120120831A1 (en) * | 2009-06-05 | 2012-05-17 | Panasonic Corporation | Qos multiplexing via base station-relay node interface |
US20120140666A1 (en) * | 2009-06-08 | 2012-06-07 | Ntt Docomo, Inc. | Mobile communication system, relay node, radio base station, and gateway device |
US20120155375A1 (en) * | 2009-08-26 | 2012-06-21 | Huawei Technologies Co., Ltd. | Method and Apparatus for Header Compression in Network Relay Scenario |
Cited By (35)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8401068B2 (en) | 2008-10-24 | 2013-03-19 | Qualcomm Incorporated | Device attachment and bearer activation using cell relays |
US20100103865A1 (en) * | 2008-10-24 | 2010-04-29 | Qualcomm Incorporated | Header compression for cell relay communications |
US20100103862A1 (en) * | 2008-10-24 | 2010-04-29 | Qualcomm Incorporated | Device attachment and bearer activation using cell relays |
US20100103845A1 (en) * | 2008-10-24 | 2010-04-29 | Qualcomm Incorporated | Cell relay mobility procedures |
US20100103861A1 (en) * | 2008-10-24 | 2010-04-29 | Qualcomm Incorporated | Cell relay packet routing |
US20100103863A1 (en) * | 2008-10-24 | 2010-04-29 | Qualcomm Incorporated | BEARER QoS MAPPING FOR CELL RELAYS |
US9088939B2 (en) | 2008-10-24 | 2015-07-21 | Qualcomm Incorporated | Bearer QoS mapping for cell relays |
US8902805B2 (en) | 2008-10-24 | 2014-12-02 | Qualcomm Incorporated | Cell relay packet routing |
US20100103857A1 (en) * | 2008-10-24 | 2010-04-29 | Qualcomm Incorporated | Cell relay network attachment procedures |
US20100182970A1 (en) * | 2009-01-21 | 2010-07-22 | Qualcomm Incorporated | Multiple Subscriptions Using a Single Air-Interface Resource |
US8788782B2 (en) | 2009-08-13 | 2014-07-22 | Qualcomm Incorporated | Apparatus and method for memory management and efficient data processing |
US8762532B2 (en) * | 2009-08-13 | 2014-06-24 | Qualcomm Incorporated | Apparatus and method for efficient memory allocation |
US20110041128A1 (en) * | 2009-08-13 | 2011-02-17 | Mathias Kohlenz | Apparatus and Method for Distributed Data Processing |
US20110040948A1 (en) * | 2009-08-13 | 2011-02-17 | Mathias Kohlenz | Apparatus and Method for Efficient Memory Allocation |
US9038073B2 (en) | 2009-08-13 | 2015-05-19 | Qualcomm Incorporated | Data mover moving data to accelerator for processing and returning result data based on instruction received from a processor utilizing software and hardware interrupts |
US20110041127A1 (en) * | 2009-08-13 | 2011-02-17 | Mathias Kohlenz | Apparatus and Method for Efficient Data Processing |
US9380637B2 (en) * | 2009-08-18 | 2016-06-28 | Zte Corporation | Relay communication system supporting multiple hops and access method thereof |
US20120140701A1 (en) * | 2009-08-18 | 2012-06-07 | Zte Corporation | Relay Communication System Supporting Multiple Hops and Access Method Thereof |
US20110092244A1 (en) * | 2009-10-15 | 2011-04-21 | Electronics And Telecommunications Research Institute | Ad-hoc wireless communication method using sector antenna, recovery method in ad-hoc wireless communication and ad-hoc wireless communication system |
US8452319B2 (en) * | 2009-10-15 | 2013-05-28 | Electronics And Telecommunications Research Institute | Ad-hoc wireless communication method using sector antenna, recovery method in ad-hoc wireless communication and ad-hoc wireless communication system |
US20110158155A1 (en) * | 2009-12-30 | 2011-06-30 | Samsung Electronics Co. Ltd. | Apparatus and method for managing quality of service in broadband wireless communication system with multiple hop relay communication |
US9385862B2 (en) | 2010-06-16 | 2016-07-05 | Qualcomm Incorporated | Method and apparatus for binding subscriber authentication and device authentication in communication systems |
US8839373B2 (en) | 2010-06-18 | 2014-09-16 | Qualcomm Incorporated | Method and apparatus for relay node management and authorization |
US20180279118A1 (en) * | 2012-01-19 | 2018-09-27 | Samsung Electronics Co., Ltd | Method for establishing an interface and communication between a relay node and a core network |
US10945124B2 (en) * | 2012-01-19 | 2021-03-09 | Samsung Electronics Co., Ltd. | Method for establishing an interface and communication between a relay node and a core network |
US20150011158A1 (en) * | 2012-02-06 | 2015-01-08 | Alcatel Lucent | Apparatus, method, and computer program for a mobile relay station transceiver, system, and means for mass transportation |
US10735085B2 (en) * | 2016-03-30 | 2020-08-04 | Sprint Communications Company L.P. | Multi-core communication system to serve wireless relays and user equipment |
US11172539B2 (en) * | 2016-11-22 | 2021-11-09 | Sony Corporation | Base station and terminal device |
EP4120743A1 (en) * | 2018-01-09 | 2023-01-18 | Guangdong Oppo Mobile Telecommunications Corp., Ltd. | Relay routing method and communication node |
US11974208B2 (en) | 2018-01-09 | 2024-04-30 | Guangdong Oppo Mobile Telecommunications Corp., Ltd. | Relay routing method and communication node |
US11252635B2 (en) | 2018-02-14 | 2022-02-15 | Kt Corporation | Method for processing uplink user data in relay node, and device for same |
CN110830170A (en) * | 2019-11-12 | 2020-02-21 | 北京理工大学 | Data transmission method based on ROHC compression in satellite communication |
WO2021187848A1 (en) * | 2020-03-17 | 2021-09-23 | Samsung Electronics Co., Ltd. | Methods and systems for reducing fronthaul bandwidth in a wireless communication system |
CN113133078A (en) * | 2021-04-19 | 2021-07-16 | 西安电子科技大学 | Light-weight inter-satellite switching device and method for giant low-orbit satellite network |
US11706607B1 (en) | 2021-06-16 | 2023-07-18 | T-Mobile Usa, Inc. | Location based routing that bypasses circuit-based networks |
Also Published As
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20100103864A1 (en) | Cell relay protocol | |
EP2356854B1 (en) | Relay architecture framework | |
US9160566B2 (en) | QOS mapping for relay nodes | |
US9247571B2 (en) | Concentrator for multiplexing access point to wireless network connections | |
US9198112B2 (en) | Device mobility for split-cell relay networks | |
US20110149848A1 (en) | Header compression for relay nodes |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: QUALCOMM INCORPORATED,CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ULUPINAR, FATIH;HORN, GAVIN B.;AGASHE, PARAG A.;AND OTHERS;SIGNING DATES FROM 20091029 TO 20091104;REEL/FRAME:023537/0539 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |