WO2017135986A1 - Transmission de support multiple dans la liaison montante pour une intégration d'évolution à long terme et wifi - Google Patents

Transmission de support multiple dans la liaison montante pour une intégration d'évolution à long terme et wifi Download PDF

Info

Publication number
WO2017135986A1
WO2017135986A1 PCT/US2016/036424 US2016036424W WO2017135986A1 WO 2017135986 A1 WO2017135986 A1 WO 2017135986A1 US 2016036424 W US2016036424 W US 2016036424W WO 2017135986 A1 WO2017135986 A1 WO 2017135986A1
Authority
WO
WIPO (PCT)
Prior art keywords
wlan
bearer
lte
radio
lwip
Prior art date
Application number
PCT/US2016/036424
Other languages
English (en)
Inventor
Alexander Sasha SIROTKIN
Original Assignee
Intel IP Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Intel IP Corporation filed Critical Intel IP Corporation
Publication of WO2017135986A1 publication Critical patent/WO2017135986A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/02—Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
    • H04L63/0272—Virtual private networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals

Definitions

  • the present disclosure relates to wireless communications, and more specifically, to a multiple bearer transmission in the uplink for wireless communications.
  • a wireless device e.g., a user equipment (UE)
  • a network device of a network coverage area could drop or lose connection suddenly due to blockage from building, vehicles, human movement, or other conditions.
  • Two types of blockage for example could be from a channel condition or an environmental change within a short time interval, which may last for tens of milliseconds, as well as from a human blockage, which can be for several hundreds of milliseconds, more or less.
  • TCP transmission control protocol
  • QoE quality of experience
  • the node can be a combination of any one of Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node Bs (also commonly denoted as evolved Node Bs, enhanced Node Bs, eNodeBs, or eNBs) or Radio Network Controllers (RNCs), which
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • Node Bs also commonly denoted as evolved Node Bs, enhanced Node Bs, eNodeBs, or eNBs
  • RNCs Radio Network Controllers
  • the downlink (DL) transmission can be a communication from the node (e.g., eNB) to the UE, and the uplink (UL) transmission can be a communication from the wireless device (e.g., the UE) to the node.
  • the wireless device e.g., the UE
  • data can be transmitted from the eNodeB to the UE via a physical downlink shared channel
  • PDSCH Physical uplink control channel
  • PUCCH physical uplink control channel
  • TDD time-division duplexing
  • FDD frequency-division duplexing
  • FIG. 1 illustrates a block diagram illustrating an example radio access network (RAN) wireless local area network (WLAN) wireless communications network environment for a UE or eNB to differentiate bearers over an IPsec tunnel according to various aspects or embodiments.
  • RAN radio access network
  • WLAN wireless local area network
  • FIG. 2 illustrates another example network environment of a UE or eNB with protocol layer architecture applicable to the various aspects or embodiments.
  • FIG. 3 illustrates a wireless communications network protocol architecture for a UE or eNB according to various aspects or embodiments.
  • FIG. 4 illustrates another wireless communications network protocol architecture for a WLAN access point (AP) according to various aspects or
  • FIG. 5 illustrates an example generic routing (GRE) encapsulation header format according to various aspects or embodiments
  • FIG. 6 illustrates an example process flow for a UE according to various embodiments.
  • FIG. 7 illustrates an example process flow for an eNB according to various embodiments.
  • FIG. 8 is a block diagram illustrating an example UE or eNB useable in connection with various aspects described herein.
  • FIG. 9 is a block diagram of an eNB, UE or other network device that facilitates bearer splitting according to various aspects described herein.
  • a component or module can be a processor, a process running on a processor, a controller, a circuit or a circuit element, an object, an executable, a program, a storage device, a computer, a tablet PC and/or a mobile phone with a processing device.
  • an application running on a server and the server can also be a component.
  • One or more components or modules can reside within a process, and a component or module can be localized on one computer and/or distributed between two or more computers.
  • a set of elements or a set of other components can be described herein, in which the term "set" can be interpreted as "one or more.”
  • these components can execute from various computer readable storage media having various data structures stored thereon such as with a module, for example.
  • the components can communicate via local and/or remote processes such as in accordance with a signal having one or more data packets (e.g., data from one component interacting with another component in a local system, distributed system, and/or across a network, such as, the Internet, a local area network, a wide area network, or similar network with other systems via the signal).
  • a signal having one or more data packets (e.g., data from one component interacting with another component in a local system, distributed system, and/or across a network, such as, the Internet, a local area network, a wide area network, or similar network with other systems via the signal).
  • a component or module can be an apparatus with specific functionality provided by mechanical parts operated by electric or electronic circuitry, in which the electric or electronic circuitry can be operated by a software application or a firmware application executed by one or more processors.
  • the one or more processors can be internal or external to the apparatus and can execute at least a part of the software or firmware application.
  • a component can be an apparatus that provides specific functionality through electronic components or elements without mechanical parts; the electronic components can include one or more processors therein to execute software and/or firmware that confer(s), at least in part, the functionality of the electronic components.
  • LTE long term evolution
  • WLAN wireless local area network
  • IPsec internet protocol security tunnel
  • LWIP can also refer to an ongoing endeavour to enable integration between LTE networks and WLAN networks at the radio level without any impact on the existing WLAN infrastructure.
  • IPsec tunnel can refer to the communication channel or protocol for encapsulating or formulating packets in communication sessions over networks involved with Internet protocol (IP) communications, including security, authentication, encryption, data origin, data integrity, data flow, or other related parameters (e.g., quality of service (QoS) parameters or the like).
  • IP Internet protocol
  • an apparatus employed in a user equipment can comprise a processor with a memory storing computer-executable instructions that execute the computer-executable components.
  • the computer-executable components can include an LTE-WIFI integration with internet protocol security LWIP module that generates an internet protocol security (I Psec) tunnel with the WLAN AP and communicates the LTE communications (e.g., packet data units or other data communicated via an LTE link to an eNB or base station (e.g., pico cell network device, a macro cell network device, a Femto cell network device, or other similar network devices or base station) via the IPsec tunnel to the WLAN AP.
  • LTE communications e.g., packet data units or other data communicated via an LTE link to an eNB or base station (e.g., pico cell network device, a macro cell network device, a Femto cell network device, or other similar network devices or base station
  • an eNB can also comprise the LWIP module to communicate via the I Psec tunnel by way of a WLAN AP or other internet protocol WiFi access component to a UE, in which the LWIP module can include a component or device such as a security gateway (e.g., an SeGW). Additional aspects and details of the disclosure are further described below with reference to figures.
  • a security gateway e.g., an SeGW
  • FIG. 1 illustrates a wireless network architecture 1 00 for WLAN WiFi, as well as for wireless gigabit alliance (WiGig) and LTE integration in accordance with various aspects or embodiments or aspects being described in this disclosure.
  • the network architecture 100 can comprise an end-to-end network for cellular communications, including a UE 1 10, an eNB 120, and gateway entities, including an evolved packet core (EPC), or other network core, which are examples of network entities and can be extended to other network entities such as for 5G or otherwise including: a serving gateway (S-GW) 130 and a packet data network (PDN) gateway (PDN GW, or P-GW) 140, as well as other network entities or components, for example.
  • S-GW serving gateway
  • PDN gateway packet data network gateway
  • P-GW packet data network gateway
  • an EPC can include other network entities, cores or interfaces such as for 5G networks or otherwise and the eNB 1 20 can operate to forward data packets from the UE 1 1 0 to any one of a plurality of core networks or network devices based on one or more parameters of different bearers.
  • the UE 1 1 0 can communicate with the eNB 120 through an air interface Uu 150 (also referred to as a cellular link), which can comprise a wireless radio
  • the UE 1 10 can also operate as a dual connected device or dual radio UE 1 10 by being communicatively coupled the WLAN AP 180 and the eNB 120 at the same time.
  • the UE can further communicate to the eNB 120 at the IP adaptation protocol layer via a user plane internet protocol interface 196 or one or more other communication links / interfaces on the network
  • the WLAN AP 180 independently, concurrently or at the same time as being connected to the WLAN AP 180, the LTE eNB 120, or both.
  • the LTE eNB can include am LTE module 1 86 for processing or generating communications via the Uu interface 1 50.
  • a WLAN module 188 of the eNB can enable processing and generation of communications with the WLAN AP 180 and an LWIP module 194 (e.g., an LWIP-SeGW, an application processor or other component) enables processing and generation of communications for IPsec channel communications transparently through the WLAP 180 to the UE 1 10.
  • LWIP module 194 e.g., an LWIP-SeGW, an application processor or other component
  • the UE 1 10 can communicate encapsulated data packets to the eNB 120 by generating an internet protocol security (IPsec) tunnel at the user plane internet protocol interface 196 via the WLAN AP 1 80 to the eN B 1 20.
  • IPsec internet protocol security
  • LTE communications that are encapsulated by the UE 1 1 0 can be communicated to the eNB 1 20 via the IPsec tunnel of the interface 1 96 to the WLAN AP 1 20.
  • the IPsec tunnel can be transparent to the WLAN AP 1 20 so that legacy devices and operations are able to operate without significant structural re-configuration.
  • the UE 1 10 can communicate with the eNB 1 20 through an air interface Uu 150 (also referred to as a cellular link), which can comprise a wireless radio communication channel defined in 3GPP standards for LTE wireless networks, which can be formed or generated via an LTE module 1 82.
  • the LTE module 1 82 can be configured to generate an LTE link with the eNB and provide LTE communication data via the LTE link or Uu interface 1 50.
  • the UE 1 1 0 can thus also operate as a dual connected device or dual radio UE 1 10 by also being communicatively coupled to a WiFi interface 197 or one or more other communication links / interfaces on the network concurrently or at the same time, in which the WiFi interface can be enabled via the WLAN module 1 98, for example.
  • the S-GW 130 in communication with the eNB 120 through an interface 160 (e.g., an S1 or other interface), can provide a point of interconnect between the wireless radio side and the EPC side of the network architecture 100, as a co-located or a non-collated eNB 120, in which "collocated” refers to the LTE AP (e.g., the eNB 120) being located in the same network device or component as the WLAN AP 180.
  • the interface 1 60 can also be connected separately and independently to both the LTE eNB 120 and the WLAN AP 180.
  • Network devices herein can be a gateway support node device, a cellular management entity device, a packet data gateway device, an eNB, for example, as well as other network devices functionally serving network communications for UEs and combinations of these devices communicatively coupled to one another.
  • the S-GW 130 can comprise the anchor point for the intra-LTE mobility, i.e., in case of a handover between eNBs and between LTE and other 3GPP accesses such as a secondary cell or other macro cell.
  • the S-GW 130 can be connected to the other gateway, the P-GW 140, through an S5/8 interface 170, for example.
  • the P-GW 140 can further provide a point of interconnect between the EPC and an external internet protocol (IP) network (not shown).
  • IP internet protocol
  • An external IP network can also be referred to as a packet data network (PDN).
  • PDN packet data network
  • the P-GW 140 for example, can further route IP packets to and from various PDNs based one or more parameters of different bearers for example.
  • FIG. 1 further illustrates that the UE 1 1 0 can include a WLAN module configured to generate a WLAN link 1 97 with the WLAN AP 1 80 and provide WLAN
  • the UE 1 10 can thus further
  • the eNB 120 communicates with the eNB 120 through the WLAN 180 via the IPsec tunnel of the LWIP interface 196, and can be connected to both the WLAN AP 180 and the eNB 120 concurrently or simultaneously via interfaces 196, 197 or 150, respectively.
  • the UE device 1 10 can include a LTE-WIFI integration with internet protocol security (LWIP) module 1 92 that is configured to establish an IPsec tunnel 1 96 via the WLAN AP 1 80 to the eNB 1 20.
  • LTE communications can be encapsulated and sent via the IPsec tunnel 1 96 as it is generated for uplink communication opportunities to the eNB 1 20.
  • the IPsec tunnel 1 96 can pass through the WLAN AP 1 80 to the eNB 1 20 and be a transparent communication to the WLAN AP 1 80.
  • the eNB 1 20 is then capable of identifying packets and mapping them to the correct core or EPC based on one or more identifiers therein.
  • a bearer represents a class of traffic having a set of network parameters (e.g., quality of service parameters) that can establish a specific standard treatment for the traffic or data being communicated on the particular class of traffic (e.g., voice or the like) for one or more UEs or network devices (e.g., eNBs or the like), which can depend on the equipment technology, processing needs, an application for data or communication, or the like.
  • Bearers can be used to carry user plane traffic (i.e., user data) on an air interface, for example, as well as extract data or parameters for quality of service indications, fallback operation or for selecting a core network to handover or forward UE data.
  • the LWIP module 192 of the UE 180 can map uplink packets to data radio bearers (DRBs) of the LTE communication data based on a traffic flow template (TFT).
  • the LWIP module 1 92 can determine which DRBs of a plurality of DRBs utilize the LTE link 1 50 and which DRBs of the plurality of DRBs are utilize the interface link via the IPsec tunnel 1 97. This determination can be based on a configuration received from the eN B 1 20 via radio resource control (RRC) signaling for example.
  • RRC radio resource control
  • the UE 1 10 can be configured by an RRC layer with the LWIP module 1 92 when LWIP operations are enabled, or, in other words, when at least one bearer is switched to WLAN / IPsec.
  • the LWIP module 192 can be configured with the TFT / packet filters to map uplink traffic to DRB identifiers. For every uplink the LWIP module 1 92 identifies using TFT, which DRB it should be mapped to. As such, if a particular DRB is configured to use WLAN / IPsec, the LWIP module 192 can add a GRE header with a DRB identifier (DRB ID). The UE 1 10 can then send the DRB identifier (DRB ID).
  • DRB ID DRB identifier
  • the LWIP module 192 sends it to a corresponding PDCP entity for communication to the eNB 120.
  • FIG. 2 illustrates an example protocol layer architecture 200, for example, in which multiple bearer offloading or packet forwarding, in which PDCP service data units (SDUs) belonging to multiple bearers can be sent via a single IPsec tunnel 196 generated to the eNB 1 20 via the WLAN AP 197, and from the eNB 120 to other core networks or components, which can be of different radio access technologies (RATs), via one or more different interfaces.
  • SDUs PDCP service data units
  • RATs radio access technologies
  • Service data units can be from upper layers, processed and submitted as resulting packet data units (PDU) to a lower layer on a network and forwarded by the eNB 120.
  • the eNB 120 can forward packets to different cores along the S1 -U interface (similar to the interface 160 of FIG. 1 ) to a serving gateway, or, for example, a mobility management entity (MME) via the S1 -MME interface, which facilitates or enables various services, such as paging, authentication, or the like.
  • MME mobility management entity
  • these interfaces can serve to deactivate dedicated packet bearers, which could be used for real-time services.
  • the eNB 1 20 can operate to identify the different data packets from the UE 1 1 0 and forward them on based on the different bearer identified. As such the UE 1 10 can utilized different protocol architectures with embodiments herein for forwarding bearers by the eNB 1 20 to one or more different communication links (e.g., WLAN, eNB or other communication links associated with one or more different radio access technologies (RATs) or core networks).
  • LWIP supports multiple bearer offloading, in which PDCP SDUs are received at the IP layer (module) 202 that are belonging to multiple bearers. These bearers can be identified and sent from the WLAN PHY/MAC layer 222 of the UE 1 1 0 via single IPsec tunneh 96. At least in uplink, the eNB 1 10' can use the
  • E-UTRAN evolved universal terrestrial radio access network
  • E-RABs evolved universal terrestrial radio access bearers
  • the interface 196 can be a user plane protocol that the UE 1 10 generates through the WLAN AP 180 to send encapsulated packets with DRBs being differentiated from among one another in order to apply different quality of service parameters, as applicable to uplink communications.
  • the UE 1 10 does this by adding an additional protocol as a generic routing encapsulation protocol (GRE) as a GRE tunnel or layer with the IPsec tunnel 196.
  • GRE generic routing encapsulation protocol
  • the UE 1 1 0 can encapsulate IP packet as the payload into GRE packets, and send these via the IPsec tunnel 196, and not an actual IP payload.
  • the UE 1 1 0, inserts a DRB identifier in a set of bits of a key field. For example, the five least significant bits of the key field can be utilized by the UE 1 10 to populate the DRB identifier for
  • the eNB 1 20 can receive the encapsulated packets via the IPsec tunnel from the UE 1 10 via the WLAN AP 180 and process the packets by inspecting the GRE header, searching for the key field therein, and then using the DRB identifier from the key field to map the packets or data traffic to the appropriate S1 bearer.
  • the eNB 120 then takes the data payload, encapsulates it (e.g., in a GTP-U), and sends it to the core network with the corresponding E-RAB via the S1 interface (e.g., S1 -MME, S1 -U or other interface).
  • S1 interface e.g., S1 -MME, S1 -U or other interface
  • the UE 1 10 can operate to generate one or more GRE tunnel(s) inside the IPsec tunnel 196.
  • the GRE header (as defined in RFC 2890) includes a "key" field,.
  • the key field can include a four octet number which was inserted by an encapsulator or other module / component (e.g., LWIP module 192).
  • the key field can be generated via the LWIP module 192 for identifying an individual traffic flow within the IPsec tunnel 196 to the eNB 120 through the WLAN 180.
  • the GRE header can be used on the WLAN link (e.g., interface 197 of FIG. 1 ) alone as well, while normal LTE protocol used on the LTE link (e.g., interface 150 of FIG. 1 ).
  • the UE 1 10 can utilize the key field within the GRE header as well as a protocol type field to identify that a bearer identifier is present and comprise the bearer identifier, which identifies one or more parameters or data corresponding to different E-RABs for uplink packets.
  • the UE 1 10 inserts the bearer identifier in the GRE key field and the eNB 120 uses the identifier data to map uplink packets to the different E-RABs and communicate them accordingly.
  • the eNB 120 can also inserts the bearer identifier in the GRE key field for every downlink packet sent to the UE 1 1 0 via the WLAN AP 180 also, and embodiments disclosed herein can apply for the LWIP module 194 similar to the LWIP module 192.
  • the UE1 1 0 and the eNB 120 further include IP layers (or modules) 202, 226, as well as RRC layers 204, 214, Packet Data Convergence Protocol (PDCP) layer(s) 206, 206, 216, 216', radio link control (RLC) layer(s) 208, 208', 218, 218', MAC and physical (PHY) layers 210, 210', 220, 222, non-access stratum (NAS) layer 212 and one or more other application or higher layers 226, for example.
  • the UE1 10 and the eNB 120 can comprise these stack layers or protocol modules in various architectural configurations and according to one or more communication channels or interfaces, such as for RRC signaling, S1 -MME, S1 -U, or the like for example.
  • the IP layers (modules) 202 and 226 includes a transmission control protocol / Internet Protocol layers that is the basic communication language or protocol of the Internet, and can be used as a communications protocol in a private network (either an intranet or an extranet).
  • the IP layer 202 facilitates communications protocols used to connect network devices on the Internet, for example.
  • the RRC layers 204 and 214 operate for radio resource control and handling control plane signaling.
  • the PDCP layer(s) 206, 206, 21 6, 216' can be one of the layers of the radio traffic stack in
  • the RLC layer(s) ) 208, 208', 218, 218' can be below or lower than the PDCP layer(s) 206, 206' and can handle an automatic repeat request fragmentation protocol used over a wireless air interface.
  • the RLC can detect packet losses and perform various other retransmissions aside from fall back conditions from an access node to bring packet loss down to a low percentage rate, which is suitable for TCP/IP applications, for example.
  • the NAS 212 can be in the UMTS and LTE wireless telecom protocol stacks between the core network and user equipment, and used to manage the establishment of communication sessions and maintain continuous communications with the user equipment as it moves.
  • the PHY and MAC layers 210, 210', 220, 222, can correspond to separate RATs respectively, can operate to provide an electrical, mechanical, and procedural interface to the transmission medium.
  • the physical layer translates logical
  • the MAC sublayer provides addressing and channel access control mechanisms that make it possible for several terminals or network nodes to communicate within a multiple access network that incorporates a shared medium.
  • the UE (or eNB) protocol stack 300 can be used to support multiple bearer transmission simultaneously or concurrently in an uplink for LWIP, and implementing bearer identifiers for differentiation at the same time.
  • the UE 1 10 can implement the protocol stack 300 comprising a TCP/IP layer 302 above a LWIP layer (module / component) 304, which can comprise or consist of two protocol stack layers a GRE layer and an IPsec layer.
  • the LWIP layer 304 is operable with different basebands such as for LTE and WLAN operation, for example, or basebands of different vendors, for example.
  • the LWIP layer or module 304 integrates both the LTE stack (comprising the PDCP 306, the RLC 308, and the MAC 310) and the WLAN stack (comprising the logical link control/ subnetwork access protocol (LLC/SNAP) layer 312 and 802.1 1 layer 314), for example, for higher level signaling to the TCP/IP layer 302 above, which is similar to the IP layer 226 of FIG. 2.
  • LTE stack comprising the PDCP 306, the RLC 308, and the MAC 3
  • the WLAN stack comprising the logical link control/ subnetwork access protocol (LLC/SNAP) layer 312 and 802.1 1 layer 314)
  • the LWIP layer 304 as part of the protocol stack 300 can be implemented in an application processor, a modem (e.g., a baseband circuitry 804e of Fig. 8, the application processor 802 of Fig. 8, or other component) or other component of the UE 1 1 0, for example, and is configured to map uplink packets to DRBs based on a TFT, which can be an information structure used to map data flows (e.g., service data flows) to particular radio bearers.
  • the LWIP layer 304 similar to the LWIP module 1 92 of FIG. 1 , adds a GRE header to the IPsec tunnel 196 in response to the DRB being configured to use the WLAN/IPsec via 302.
  • the GRE header is used as a GRE tunnel inside the IPsec tunnel and utilizes a GRE key field to carry a bearer identifier (DRB ID) therein.
  • DRB ID bearer identifier
  • the DRB can then be sent by the UE 1 10 via 802.1 1 layer 314, via LTE, or otherwise, for example.
  • the eNB 1 20 can operate with a same or similar protocol stack 300 as the UE 1 1 0. After the eNB 1 20 receives encapsulated packets via the IPsec tunnel 196 generated by the UE 1 10 via the WLAN AP 180, then utilizes the DRB ID in the GRE key field to map uplink packets to an E-RAB by removing the GRE heading and forwarding the packet, payload or data traffic to an appropriate interface (S1 interface).
  • S1 interface appropriate interface
  • the LWIP layer 304 enables network support of multiple bearer offloading, that is - PDCP SDUs belonging to multiple bearers. These PDCP SDUs can be sent via a single I Psec tunnel. At least in the uplink, the eNB 1 20 has to know or be able to identify which bearer received uplink packets belong to in order to map them to corresponding E-RABs on S1 . Although the LWIP layer 304 operates in the uplink path for uplink packets in the UE 1 10, it can also be enabled for downlink support in a similar way or similar embodiments at the eNB 120 via the LWIP module 1 96 of FIG. 1 , for example.
  • a user plane protocol stack 400 for differentiating bearers in uplink communication in accordance with various aspects.
  • the user planet protocol stack 400 can be used within a WLAN AP 180 to support multiple bearer transmission simultaneously or concurrently in an uplink for offloading of different bearers from the UE 1 10 to the eNB 120.
  • a IP payload or layer 402 lies above or on top of a GRE header 404 that is encapsulated with payload data via the IPsec tunnel by the UE 1 10, for example.
  • the GRE header 404 can be inserted within the IPsec header 406.
  • LLC/SNAP 408 is used for WiFi operation together with an 802.1 header 410.
  • the GRE header 600 provides an example format of a GRE header 600 for encapsulation of data packets by LWIP module 1 92 or 194 of FIG. 1 .
  • the LWIP module 192 or 194 can utilize the "Protocol Type" field 602 and "Key” fields 604.
  • the IPsec tunnel 1 96 can carry PDCP Protocol Data Units (PDUs), that is - IP packets. Therefore the Protocol Type field 602 can be set accordingly, e.g. , to 0x0800 for Internet Protocol version 4 (I Pv4).
  • the K bit 606 can be set (e.g., to one) to indicate that the optional "Key" field 604 is being used.
  • the Key field 604 can be set to a particular a bearer identifier, e.g., DRB ID.
  • the least significant bits of the field can be used to implement the DRB I D.
  • the UE 1 1 0 can use a TFT (or packet filters) to map the uplink packets to DRB I Ds and then populate the GRE Key field 604 with the DRB ID.
  • the eNB 1 20 then can use the DRB ID to differentiate different bearers and map uplink packets to different E-RABs.
  • the eNB 1 20 can map the E-RAB to the DRB ID and then populates the GRE Key field 604 with the DRB ID while further providing an indication (e.g., 606) that the DRB ID is being used to differentiate between multiple bearers being communicated.
  • the UE 1 1 0 can then use the DRB I D to map downlink packets to packet data network (PDN) connections (Operating System (OS) network interfaces), for example.
  • PDN packet data network
  • OS Operating System
  • the UE 1 1 0 can use the destination IP address in the downlink to map packets to network interfaces via the IPsec tunnel 1 96, in which case bearer identifier could be absent in the downlink but present in the uplink.
  • the LWIP module 192 or 1 94 can implement the protocol stack 300 in response to the LWIP being enabled at the UE 1 10 or eNB 120, which can occur when multiple bearers are being communicated via the IPsec tunnel 196 for different interfaces, or when at least one bearer is switched to WLAN/IPsec, for example.
  • a single LWIP entity, module or component therefore can operate with TFT/packet filters to map uplink packets to DRB identifiers or DRB IDs. For every uplink, the LWIP module 192 or 194 can utilize TFT to determine which DRB it should be mapped to.
  • the LWIP module can add a GRE header with the "Key” and other relevant fields populated as described above and sends it via 802.1 1 . If the DRB is configured to use LTE, the LWIP module can send it to the corresponding PDCP entity as detailed above with reference to FIG. 3.
  • FIG. 6 illustrates a method 600 that can be employed within a UE (e.g., 1 10) for facilitating network operations for generating an IPsec tunnel via a WLAN AP (e.g., 180) to communicate bearer identification to an eNB via the IPsec tunnel.
  • the method 600 for example, and various aspects/embodiments disclosed can be implemented on a computer-readable storage device, media or medium and is described with reference to the figures above for example.
  • the media or medium can comprise executable instructions that, in response to execution, cause a network device comprising one or more processors to perform operations in a multi-radio heterogeneous network of a RAN, such as with an LTE node, WLAN, or other technology node.
  • the method initiates with determining a first radio bearer to be transmitted over an LTE radio link (e.g. , 1 50) of an air interface and a second radio bearer to be transmitted over a wireless local area network WLAN radio link (e.g., 1 97) of an air interface.
  • LTE radio link e.g. , 1 50
  • WLAN radio link e.g., 1 97
  • the method includes encapsulating a bearer identifier (e.g., DRB ID) inside an uplink packet that identifies the second radio bearer from the first radio bearer, or vice versa.
  • a bearer identifier e.g., DRB ID
  • the method includes providing the uplink packet to an IPsec tunnel 1 96 and communicating the uplink packet to an eNB 1 20 via a WLAN AP 1 80with the I Psec tunnel.
  • the encapsulating of the bearer identifier (e.g., DRB ID) by the UE 1 1 0, for example, can include inserting a GRE header with the bearer identifier inside the uplink packet to enable the eNB 1 20 to identify the second radio bearer and also map the uplink packet(s) to a corresponding E-RAB.
  • the bearer identifier or DRB ID can be included in a GRE key field 604 of the GRE header 600.
  • the UE can set a protocol type field 602 of the GRE header to comprise a value that indicates that the uplink packet being encapsulated comprises an internet protocol version 4 IPv4 packet, which can trigger the eNB 1 20 to find the GRE header and DRB identifier to differentiate which bearer belongs to which E-RAB.
  • a protocol type field 602 of the GRE header to comprise a value that indicates that the uplink packet being encapsulated comprises an internet protocol version 4 IPv4 packet, which can trigger the eNB 1 20 to find the GRE header and DRB identifier to differentiate which bearer belongs to which E-RAB.
  • the UE 1 1 0 can map uplink packets to a corresponding one of a plurality of bearer identifiers based on a TFT, which, for example, can be communicated.
  • the U E 1 1 0 can receive one or more RRC signals from the eNB 1 20, which can be based on or in response to an indication that an IPsec tunnel is being initiated.
  • the UE 1 1 0 can then determine, based on the one or more RRC signals, an LWIP module configuration to enable the LWI P module (e.g., 1 92) such that at least one bearer can be switched to be a WLAN bearer from an LTE bearer, for example.
  • an LWIP module configuration to enable the LWI P module (e.g., 1 92) such that at least one bearer can be switched to be a WLAN bearer from an LTE bearer, for example.
  • FIG. 7 illustrates a method 700 that can be employed within an eNB 120 for facilitating network operations with an IPsec tunnel via a WLAN AP 180 from UE 1 10 to enable bearer identification.
  • the method 700 for example, and various
  • the media or medium can comprise executable instructions that, in response to execution, cause a network device comprising one or more processors to perform operations in a multi- radio heterogeneous network of a RAN, such as with an LTE node, WLAN, or other technology node.
  • the method 700 initiates at 702 with receiving an uplink packet including a radio bearer over a WLAN radio link.
  • the method includes extracting a bearer identifier from a GRE header inside the uplink packet.
  • the method includes providing the uplink packet over an S1 interface to a desired core network component using the bearer identifier.
  • the eNB can map an E-RAB to data radio bearer ("DRB") identifiers ("ID”) and populate a GRE key field with the DRB I D to enable a UE to map the downlink packet to a packet data network connection or use a destination internet protocol address to map downlink packets to network interfaces.
  • DRB data radio bearer
  • FIG. 8 illustrates, for oneembodiment, example components of a cell network device 800, such as a base station, a macro cell network device, a secondary cell network device, a small cell network device, an evolved/enhanced NodeB (eNB), or any other network device (e.g. a user equipment, pico cell, Femto cell or the like).
  • the cell network device 800 can include application circuitry 802, baseband circuitry 804, Radio Frequency (RF) circuitry 806, front-end module (FEM) circuitry 808 and one or more antennas 810, coupled together at least as shown.
  • RF Radio Frequency
  • FEM front-end module
  • the application circuitry 802 can include one or more application processors.
  • the application circuitry 802 can include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the processor(s) can include any combination of eralgen- purpose processors anddedicated processors (e.g., graphics processors, application processors, etc.).
  • the processors can be coupled with and/or can include memory/storage and can be configured to execute instructions stored in the memory/o enable various applications andstorage t/ oroperating systems to run on the system.
  • the baseband circuitry 804 can include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the baseband circuitry804 can include one or more baseband processors and/or control logic to process baseband signals received from a receive signal path of the RF circuitry 806 and to generate baseband signals for a transmit signal path of the RF circuitry 806.
  • Baseband processing circuity 804 can interface with the application circuitry 802 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 806.
  • the baseband circuitry 804 can include a second generation (2G) baseband processor 804a, third generation (3G) baseband processor 804b, fourth generation (4G) baseband processor 804c, and/or other baseband processor(s) 804d for other existing generations, generations in development or to be developed in the future (e.g., fifth generation (5G), 6G, etc.).
  • the baseband circuitry 804 e.g., one or more of baseband processors 804a-d
  • the radio control functions can include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc.
  • modulation/ demodulation circuitry of the baseband circuitry804 can include Fast-Fourier Transform (FFT), precoding, and/or constellation mapping / demapping functionality.
  • FFT Fast-Fourier Transform
  • encoding/decoding circuitry of the baseband circuitry 804 can include convolution, tail-biting convolution, turbo, Viterbi, and/or Low Density Parity Check (LDPC) encoder/decoder functionality.
  • LDPC Low Density Parity Check
  • the baseband circuitry 804 can include elements of a protocol stack such as, for example, elements of an evolved universal terrestrial radio access network (EUTRAN) protocol including, for example, physical (PHY), medical access control (MAC), 10 radio link control(er), packet data convergence protocol (PDCP), or radio resource control (RRC) elements.
  • EUTRAN evolved universal terrestrial radio access network
  • a central processing unit (CPU) 804e of the baseband circuitry 804 can be configured to run elements of the protocol stack for signaling of the PHY, MAC, RLC, PDCP or RRC layers.
  • the baseband circuitry can include one or more audio digital signal processor(s) (DSP) 804f.
  • the audio DSP(s) 804f can be include elements for compression/decompression and echo cancellation and can include other suitable processing elements in other embodiments.
  • Components of the baseband circuitry can be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments.
  • some or all of the constituent components of the baseband circuitry804 and the application circuitry 802 can be implemented together such as, for example, on a system on a chip(SOC).
  • the baseband circuitry 804 can provide for communication re radio technologiescompatible with one or mo.
  • thebaseband circuitry 804 can support communication with an evolved universal terrestrial radio access network(EUTRAN) and/or other wireless metropolitan area networks(WMAN) , a wireless local area network(WLAN) , a wireless personal area network (WPAN).
  • EUTRAN evolved universal terrestrial radio access network
  • WMAN wireless metropolitan area networks
  • WLAN wireless local area network
  • WPAN wireless personal area network
  • multi-mode baseband circuitry Embodiments in which the baseband circuitry 804 is configured to support radio communications of more than one wireless protocolcan be referred to as multi-mode baseband circuitry.
  • RF circuitry 806 can enable communication with wireless networks using modulatedelectromagnetic radiation through a non-solid medium.
  • the RF circuitry806 can include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network.
  • RF circuitry806 can include a receive signal path which can include circuitry to down-convert RF signals received from the FEM circuitry 808 and provide baseband signals to the baseband circuitry 804.
  • RF circuitry 806 can also include a transmit signal path which can include circuitry to up- convert baseband signals provided by the baseband circuitry 804 and provide RF output signals to the FEM circuitry 808 for transmission.
  • the RF circuitry 806 can include a receive signal path and a transmit signal path.
  • the receive signal path of the RF circuitry 806 can include mixer circuitry 806a, amplifier circuitry 806b and filter circuitry 806c.
  • the transmit signal path of the RF circuitry 806 can include filter circuitry 806c and mixer circuitry 806a.
  • RF circuitry 806 can also include synthesizer circuitry 806d for synthesizing a frequency for use by the mixer circuitry 806a of the receive signal path and the transmit signal path.
  • the mixer circuitry 806a of the receive signal path can be configured to down-convert RF signals received from the FEM circuitry 808 based on the synthesized frequency provided by synthesizer circuitry 806d.
  • the amplifier circuitry 806b can be configured to amplify the down-converted signals and the filter circuitry 806c can be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals.
  • LPF low-pass filter
  • BPF band-pass filter
  • Output baseband signals can be provided to the baseband circuitry 804 for further processing.
  • the output baseband signals can be zero- frequency baseband signals, although this is not a requirement.
  • mixer circuitry 806a of the receive signal path can comprise passive mixers, although the scope of the embodiments is not limited in this respect.
  • the mixer circuitry 806a of the transmit signal path can be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 806d to generate RF output signals for the FEM circuitry 808.
  • the baseband signals can be provided by the baseband circuitry 804 and can be filtered by filter circuitry 806c.
  • the filter circuitry 806c can include a low-pass filter (LPF), although the scope of the embodiments is not limited in this respect.
  • the mixer circuitry 806a of the receive signal path and the mixer circuitry 806a of the transmit signal path can include two or more mixers and can be arranged for quadrature down-conversion or up-conversion respectively.
  • the mixer circuitry 806a of the receive signal path and the mixer circuitry 806a of the transmit signal path can include two or more mixers and can be arranged for image rejection (e.g., Hartley image rejection).
  • the mixer circuitry 806a of the receive signal path and the mixer circuitry 806a can be arranged for direct down-conversion or direct up-conversion, respectively.
  • the mixer circuitry 806a of the receive signal path and the mixer circuitry 806a of the transmit signal path can be configured for super-heterodyne operation.
  • the output baseband signals and the input baseband signals can be analog baseband signals, although the scope of the embodiments is not limited in this respect.
  • the output baseband signals and the input baseband signals can be digital baseband signals.
  • the RF circuitry 806 can include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 804 can include a digital baseband interface to communicate with the RF circuitry 806.
  • ADC analog-to-digital converter
  • DAC digital-to-analog converter
  • a separate radio IC circuitry can be provided for processing signals for each spectrum, although the scope of the
  • the synthesizer circuitry 806d can be a fractional-N synthesizer or a fractional N/N+8 synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers can be suitable.
  • synthesizer circuitry 806d can be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
  • the synthesizer circuitry 806d can be configured to synthesize an output frequency for use by the mixer circuitry 806a of the RF circuitry 806 based on a frequency input and a divider control input.
  • the synthesizer circuitry 806d can be a fractional N/N+8 synthesizer.
  • frequency input can be provided by a voltage controlled oscillator (VCO), although that is not a requirement.
  • VCO voltage controlled oscillator
  • Divider control input can be provided by either the baseband circuitry 804 or the applications processor 802 depending on the desired output frequency.
  • a divider control input e.g., N
  • N can be determined from a look-up table based on a channel indicated by the applications processor 802.
  • Synthesizer circuitry 806d of the RF circuitry 806 can include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator.
  • the divider can be a dual modulus divider (DMD) and the phase accumulator can be a digital phase accumulator (DPA).
  • the DMD can be configured to divide the input signal by either N or N+8 (e.g., based on a carry out) to provide a fractional division ratio.
  • the DLL can include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip- flop.
  • the delay elements can be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line.
  • Nd is the number of delay elements in the delay line.
  • synthesizer circuitry 806d can be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency can be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other.
  • the output frequency can be a LO frequency (fLO).
  • the RF circuitry 806 can include an IQ/polar converter.
  • FEM circuitry 808 can include a receive signal path which can include circuitry configured to operate on RF signals received from one or more antennas 810, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 806 for further processing.
  • FEM circuitry 808 can also include a transmit signal path which can include circuitry configured to amplify signals for transmission provided by the RF circuitry 806 for transmission by one or more of the one or more antennas 81 0.
  • the FEM circuitry 808 can include a TX/RX switch to switch between transmit mode and receive mode operation.
  • the FEM circuitry can include a receive signal path and a transmit signal path.
  • the receive signal path of the FEM circuitry can include a low-noise amplifier (LNA) to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 806).
  • LNA low-noise amplifier
  • the transmit signal path of the FEM circuitry 808 can include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 806), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 81 0.
  • PA power amplifier
  • the cell network device 800 can include additional elements such as, for example, memory/storage, display, camera, sensor, and/or utinp/ output(l/0) interface.
  • the electronic device of Figure 8 may be configured to perform one or more processes, techniques, and/or methods as described herein, or portions thereof.
  • a system can be a mobile computing device suchas, but not limited to, a laptop computing device, a tablet computing device, a netbook, an ultrabook , a smartphone, etc.
  • system can have more or lesscomponents, and/or different architectures.
  • the RF logic and/or the baseband logic can be embodied in
  • the communication logic can include oneor more single-core or multi-core processors and logic circuits to provide signal processing techniques, for example, encoding, modulation, filtering, converting, amplifying, etc., suitable to the appropriate communication interface over which communications will take place.
  • the communication logic can communicate over wireline, optical, or wireless communication mediums.
  • the communication logic can include the RF logic and/or baseband logic to provide for communication compatible with one or more radio technologies.
  • the communication logic can support communication with an evolved universal terrestrial radio access network(EUTRAN) and/ orother wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN).
  • EUTRAN evolved universal terrestrial radio access network
  • WMAN wireless metropolitan area networks
  • WLAN wireless local area network
  • WPAN wireless personal area network
  • Embodiments herein can be described as related to the third generation partnership project (3GPP) long term evolution (LTE) or LTE-advanced (LTE-A) standards.
  • 3GPP third generation partnership project
  • LTE long term evolution
  • LTE-A LTE-advanced
  • terms or entities such as eNodeB (eNB), mobility management entity (MME), user equipment (UE), etc. may be used that may be viewed as LTE- related terms or entities.
  • the technology may be used in or related to other wireless technologies such as the Institute of Electrical and Electronic Engineers (IEEE) 802.16 wireless technology (WiMax), IEEE 802.1 1 wireless technology (WiFi), various other wireless technologies such as global system for mobile communications (GSM), enhanced data rates for GSM evolution (EDGE), GSM EDGE radio access network (GERAN), universal mobile telecommunications system (UMTS), UMTS terrestrial radio access network (UTRAN), or other 2G, 3G, 4G, 5G, etc.
  • IEEE Institute of Electrical and Electronic Engineers
  • WiMax WiMax
  • WiFi wireless technology
  • GSM global system for mobile communications
  • EDGE enhanced data rates for GSM evolution
  • GSM EDGE radio access network GERAN
  • UMTS universal mobile telecommunications system
  • UTRAN universal mobile telecommunications system
  • LTE-related terms such as eNB, MME, UE, etc.
  • one or more entities or components may be used that may be considered to be equivalent or approximately equivalent to one or more of the LTE-based terms or entities.
  • processor can refer to substantially any computing processing unit or device including, but not limited to including, single-core processors; single-processors with software multithread execution capability; multi-core processors; multi-core processors with software multithread execution capability; multi-core processors with hardware multithread technology;
  • a processor can refer to an integrated circuit, an application specific integrated circuit, a digital signal processor, a field programmable gate array, a programmable logic controller, a complex programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions and/or processes described herein.
  • Processors can exploit nano-scale architectures such as, but not limited to, molecular and quantum-dot based transistors, switches and gates, in order to optimize space usage or enhance performance of mobile devices.
  • a processor may also be implemented as a combination of computing processing units.
  • memory components or entities embodied in a “memory,” or components including the memory. It is noted that the memory components described herein can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory.
  • nonvolatile memory for example, can be included in a memory, non-volatile memory, disk storage, and memory storage. Further, nonvolatile memory can be included in read only memory, programmable read only memory, electrically programmable read only memory, electrically erasable programmable read only memory, or flash memory. Volatile memory can include random access memory, which acts as external cache memory. By way of illustration and not limitation, random access memory is available in many forms such as synchronous random access memory, dynamic random access memory, synchronous dynamic random access memory, double data rate synchronous dynamic random access memory, enhanced synchronous dynamic random access memory, Synchlink dynamic random access memory, and direct Rambus random access memory.
  • FIG. 9 illustrates a block diagram of an embodiment of access (or user) equipment related to access of a network (e.g., network device, base station, wireless access point, femtocell access point, and so forth) that can enable and/or exploit features or aspects disclosed herein.
  • a network e.g., network device, base station, wireless access point, femtocell access point, and so forth
  • Access equipment e.g., eNB, network entity, or the like
  • UE or software related to access of a network can receive and transmit signal(s) from and to wireless devices, wireless ports, wireless routers, etc. through segments 902 902 B (B is a positive integer).
  • Segments 902 902 B can be internal and/or external to access equipment and/or software related to access of a network, and can be controlled by a monitor component 904 and an antenna component 906.
  • Monitor component 904 and antenna component 906 can couple to communication platform 908, which can include electronic components and associated circuitry that provide for processing and manipulation of received signal(s) and other signal(s) to be transmitted.
  • communication platform 908 includes a receiver/transmitter 910 that can convert analog signals to digital signals upon reception of the analog signals, and can convert digital signals to analog signals upon transmission.
  • receiver/transmitter 910 can divide a single data stream into multiple, parallel data streams, or perform the reciprocal operation.
  • Coupled to receiver/transmitter 910 can be a multiplexer / demultiplexer 912 that can facilitate manipulation of signals in time and frequency space. Multiplexer/demultiplexer 912 can multiplex information
  • multiplexer/demultiplexer component 912 can scramble and spread information (e.g., codes, according to substantially any code known in the art, such as Hadamard-Walsh codes, Baker codes, Kasami codes, polyphase codes, and so forth).
  • a modulator/demodulator 914 is also a part of communication platform 908, and can modulate information according to multiple modulation techniques, such as frequency modulation, amplitude modulation (e.g., M-ary quadrature amplitude modulation, with M a positive integer); phase-shift keying; and so forth).
  • modulation techniques such as frequency modulation, amplitude modulation (e.g., M-ary quadrature amplitude modulation, with M a positive integer); phase-shift keying; and so forth).
  • Access equipment and/or software related to access of a network also includes a processor 916 configured to confer, at least in part, functionality to
  • access equipment and/or software can facilitate configuration of access equipment and/or software through, for example, monitor component 904, antenna component 906, and one or more components therein.
  • access equipment and/or software can include display interface 918, which can display functions that control functionality of access equipment and/or software or reveal operation conditions thereof.
  • display interface 918 can include a screen to convey information to an end user.
  • display interface 918 can be a liquid crystal display, a plasma panel, a monolithic thin-film based electrochromic display, and so on.
  • display interface 918 can include a component (e.g., speaker) that facilitates communication of aural indicia, which can also be employed in connection with messages that convey operational instructions to an end user.
  • Display interface 918 can also facilitate data entry (e.g., through a linked keypad or through touch gestures), which can cause access equipment and/or software to receive external commands (e.g., restart operation).
  • Broadband network interface 920 facilitates connection of access equipment and/or software to a service provider network (not shown) that can include one or more cellular technologies (e.g., third generation partnership project universal mobile telecommunication system, global system for mobile communication, and so on) through backhaul link(s) (not shown), which enable incoming and outgoing data flow.
  • Broadband network interface 920 can be internal or external to access equipment and/or software and can utilize display interface 918 for end-user interaction and status information delivery.
  • Processor 916 can be functionally connected to communication platform 908 and can facilitate operations on data (e.g., symbols, bits, or chips) for
  • processor 916 can be functionally connected, through data, system, or an address bus 922, to display interface 91 8 and broadband network interface 920, to confer, at least in part, functionality to each of such components.
  • access equipment and/or software memory 924 can retain location and/or coverage area (e.g., macro sector, identifier(s)) access list(s) that authorize access to wireless coverage through access equipment and/or software sector intelligence that can include ranking of coverage areas in the wireless environment of access equipment and/or software, radio link quality and strength associated therewith, or the like.
  • location and/or coverage area e.g., macro sector, identifier(s)
  • Memory 924 also can store data structures, code instructions and program modules, system or device information, code sequences for scrambling, spreading and pilot transmission, access point configuration, and so on.
  • Processor 91 6 can be coupled (e.g., through a memory bus), to memory 924 in order to store and retrieve information used to operate and/or confer functionality to the components, platform, and interface that reside within access equipment and/or software.
  • the memory 924 can comprise one or more machine-readable medium / media including instructions that, when performed by a machine or component herein cause the machine to perform acts of the method or of an apparatus or system for concurrent communication using multiple communication technologies according to embodiments and examples described herein. It is to be understood that aspects described herein can be implemented by hardware, software, firmware, or any combination thereof. When implemented in software, functions can be stored on or transmitted over as one or more instructions or code on a computer-readable medium (e.g., the memory described herein or other storage device).
  • Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a storage media or a computer readable storage device can be any available media that can be accessed by a general purpose or special purpose computer.
  • 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 other tangible and/or non-transitory medium, that can be used to carry or store desired information or executable instructions.
  • any connection can also be termed a computer-readable medium.
  • Disk and disc 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 reproduce data optically with lasers.
  • Examples can include subject matter such as a method, means for performing acts or blocks of the method, at least one machine-readable medium including instructions that, when performed by a machine cause the machine to perform acts of the method or of an apparatus or system for concurrent communication using multiple communication technologies according to embodiments and examples described herein.
  • Example 1 is an apparatus employed in a user equipment (“UE") device comprising: at least one processor, communicatively coupled to a memory storing computer-executable components, configured to execute the computer-executable components, the computer-executable components comprising: a long term evolution (“LTE”) module configured to generate an LTE link with an evolved nodeB (“eNB”) and provide LTE communication data via the LTE link; a wireless local area network (“WLAN”) module configured to generate a WLAN link with a WLAN access point (“AP”) and provide WLAN communication data via the WLAN link; and a LTE-WIFI integration with internet protocol security (“LWIP”) module configured to establish an internet protocol security (“IPsec”) tunnel via the WLAN AP to the eNB and communicate the LTE communication to the eN B via the IPsec tunnel to the WLAN AP.
  • LTE long term evolution
  • eNB evolved nodeB
  • WLAN wireless local area network
  • AP WLAN access point
  • LWIP LTE-WIFI integration with internet protocol security
  • IPsec internet protocol security
  • Example 2 includes the subject matter of Example 1 , wherein the LWIP module is further configured to map uplink packets to data radio bearers ("DRBs") of the LTE communication data based on a traffic flow template ("TFT"), and wherein the LWIP module is further configured to determine which DRBs of the plurality of DRBs are configured to utilize the LTE link and which DRBs of the plurality of DRBs are configured to utilize the WLAN link via the IPsec tunnel, based on a configuration received from the eN B via radio resource control (“RRC”) signaling.
  • DRBs data radio bearers
  • TFT traffic flow template
  • RRC radio resource control
  • Example 3 includes the subject matter of any of Examples 1 -2, including or omitting any elements, wherein the LWIP module is further configured to add a generic routing encapsulation ("GRE") header to packets to be sent via the WLAN link, including inserting a DRB identification (“DRB ID”) into a GRE key field of the GRE header to differentiate between DRBs of the packets.
  • GRE generic routing encapsulation
  • Example 4 includes the subject matter of any of Examples 1 -3, including or omitting any elements, wherein the LWIP module is further configured to generate a GRE tunnel inside the IPsec tunnel via the WLAN AP and provide the LTE communication data with a differentiation between radio bearers of data packets of the LTE communication data, wherein the differentiation enables the eN B to differentiate between the radio bearers and map uplink packets to evolved universal terrestrial radio access network ("E-UTRAN”) radio access bearers (“E-RABs").
  • E-UTRAN evolved universal terrestrial radio access network
  • E-RABs evolved universal terrestrial radio access bearers
  • Example 5 includes the subject matter of any of Examples 1 -4, including or omitting any elements, wherein the LWIP module is further configured to map the downlink to a packet data network ("PDN") based on the radio bearer, or to a network interface with a destination I P address based on the radio bearer.
  • PDN packet data network
  • Example 6 is an apparatus employed in a evolved nodeB (“eNB”) comprising: at least one processor, communicatively coupled to a memory storing computer-executable components, configured to execute the computer-executable components, the computer-executable components comprising: a long term evolution (“LTE”) module configured to generate an LTE link with a user equipment (“UE"), and provide LTE communication data via the LTE link; a wireless local area network (“WLAN”) module configured to generate a WLAN link with a WLAN access point (“AP”) and provide WLAN communication data via the WLAN link; and a LTE-WIFI integration with internet protocol security (“LWIP”) module configured to enable an internet protocol security (“IPsec”) tunnel via the WLAN AP and communicate the LTE communication to the UE via the IPsec tunnel to the WLAN AP.
  • LTE long term evolution
  • WLAN wireless local area network
  • AP WLAN access point
  • LWIP LTE-WIFI integration with internet protocol security
  • IPsec internet protocol security
  • Example 7 includes the subject matter of Examples 6, wherein the LWIP module is configured to extract, from uplink packets, data radio bearer (“DRB”) identifiers ("DRB IDs”), map the DRB IDs to an S1 bearer and forward the uplink packets to a core network based on the mapped DRB I Ds.
  • DRB data radio bearer
  • DRB IDs data radio bearer identifiers
  • Example 8 includes the subject matter of any of Examples 6-7, including or omitting any elements, wherein the LWIP module is further configured to extract the DRB ID from a protocol type field of a GRE header.
  • Example 9 includes the subject matter of any of Examples 6-8, including or omitting any elements, wherein the LWIP module is further configured to generate a determination of which DRBs are configured to utilize the LTE link and which DRBs of the plurality of DRBs are configured to utilize the WLAN link via the IPsec tunnel, and provide a configuration to the UE via radio resource control (“RRC”) signaling to indicate the determination.
  • RRC radio resource control
  • Example 10 includes the subject matter of any of Examples 6-9, including or omitting any elements, wherein the LWIP module is further configured to receive, from the UE, an indication that an IPsec tunnel is being initiated, and provide one or more RRCs signals to the UE based on the indication, wherein the one or more RRC signals include an LWIP entity configuration to enable the UE such that at least one bearer is switched to be a WLAN bearer from an LTE bearer.
  • Example 1 1 is a computer-readable storage device (e.g., a computer readable medium) comprising executable instructions that, in response to execution, cause one or more processors of a user equipment (“UE") to perform operations, the operations comprising: determining, via the one or more processors, a first radio bearer to be transmitted over a long term evolution (“LTE") radio link and a second radio bearer to be transmitted over a wireless local area network (“WLAN”) radio link; encapsulating a bearer identifier inside an uplink packet that identifies the second radio bearer; and providing the uplink packet to an internet protocol security (“IPsec”) tunnel and communicating the uplink packet to an evolved nodeB (“eNB”) via a WLAN access point (AP) with the IPsec tunnel.
  • LTE long term evolution
  • WLAN wireless local area network
  • Example 12 includes the subject matter of Example 1 1 , wherein the encapsulating the bearer identifier comprises encapsulating a generic routing encapsulation ("GRE") header with the bearer identifier inside the uplink packet to enable the eNB to identify the second radio bearer and map uplink packets to Evolved Universal Terrestrial Radio Access Network (“E-UTRAN”) Radio Access Bearers (“E-RABs”), wherein the bearer identifier is included in a GRE key field of the GRE header.
  • GRE generic routing encapsulation
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • E-RABs Radio Access Bearers
  • Example 13 includes the subject matter of any of Examples 1 1 -12, including or omitting any elements, wherein the operations further comprise: setting a protocol type field of the GRE header to comprise a value that indicates that the uplink packet comprises an internet protocol version 4 ("I Pv4") packet.
  • I Pv4 internet protocol version 4
  • Example 14 includes the subject matter of any of Examples 1 1 -13, including or omitting any elements, wherein the operations further comprise: setting one or more bits of the GRE header to have a value that indicates that the GRE key field is being utilized as the bearer identifier.
  • Example 15 includes the subject matter of any of Examples 1 1 -14, including or omitting any elements, wherein the operations further comprise: mapping a plurality of uplink packets to a corresponding one of a plurality of bearer identifiers based on a Traffic Flow Template ("TFT"), wherein the bearer identifier is associated with a corresponding one of a plurality of bearers; determining based on the mapping, the bearer identifier to identify the second radio bearer from among the plurality of bearer identifiers that is associated with the uplink packet; and populating the bearer identifier into the GRE key field to identify the second radio bearer.
  • TFT Traffic Flow Template
  • Example 16 includes the subject matter of any of Examples 1 1 -15, including or omitting any elements, wherein the operations further comprise: communicating to the eNB an indication that an I Psec tunnel is being initiated; receiving one or more Radio Resource Control (“RRC") signals from the eNB based on the indication; and determining, based on the one or more RRC signals, an LWIP module configuration to enable the LWIP module such that at least one bearer is switched to be a WLAN bearer from an LTE bearer.
  • RRC Radio Resource Control
  • Example 1 7 is a computer-readable storage device comprising executable instructions that, in response to execution, cause one or more processors of an evolved nodeB (“eNB”) to perform operations, the operations comprising: receiving, by the one or more processors, an uplink packet including a radio bearer over a wireless local area network (“WLAN”) radio link; extracting, by the one or more processors, a bearer identifier from a generic routing encapsulation (“GRE”) header inside the uplink packet; and providing, by the one or more processors, the uplink packet over an S1 interface to a desired core network component using the bearer identifier.
  • eNB evolved nodeB
  • Example 18 includes the subject matter of Example 17, wherein the operations further comprising: mapping, by the one or more processors, the uplink packet to an evolved universal terrestrial radio access network (E-UTRAN) radio access bearers (E-RABs) using the bearer identifier.
  • E-UTRAN evolved universal terrestrial radio access network
  • E-RABs radio access bearers
  • Example 19 includes the subject matter of any of Examples 17-18, including or omitting any elements, wherein the bearer identifier is included in a GRE key field of the GRE header.
  • Example 20 includes the subject matter of any of Examples 17-19, including or omitting any elements, wherein a protocol type field of the GRE header includes a value comprising a plurality of bits, wherein the value indicates that the packet comprises an internet protocol security (I Psec) packet.
  • I Psec internet protocol security
  • Example 21 includes the subject matter of any of Examples 17-20, including or omitting any elements, wherein the operations further comprise: receiving, or causing to receive from a UE, in response to receiving the uplink pack, an indication to indicate that an LWI P entity is enabled at the UE; and transmitting, or causing to transmit one or more radio resource control (“RRC") signals to the U E based on the indication, wherein the one or more RRC signals include an LWIP entity configuration to enable the LWIP entity at the UE such that at least one bearer is switched to be a WLAN bearer from an LTE bearer or to be an LTE bearer from a WLAN bearer.
  • RRC radio resource control
  • Example 22 includes the subject matter of any of Examples 17-21 , including or omitting any elements, wherein the operations further comprise: removing, in response to receiving the uplink packet, the GRE header from the uplink packet prior to transmitting the uplink packet to the desired core network component over the S1 interface.
  • Example 23 includes the subject matter of any of Examples 17-22, including or omitting any elements, wherein the operations further comprise: generating an internet protocol security ("IPsec") tunnel with a WLAN access point ("WLAN AP") and communicating a packet data unit to a UE via the IPsec tunnel via the WLAN AP.
  • IPsec internet protocol security
  • WLAN AP WLAN access point
  • Example 24 includes the subject matter of any of Examples 17-23, including or omitting any elements, wherein a protocol type field of the GRE header includes a value of 0x0800, wherein the value of 0x0800 indicates that the uplink packet is an internet protocol version 4 ("I Pv4") packet.
  • I Pv4 internet protocol version 4
  • Example 25 includes the subject matter of any of Examples 17-23, including or omitting any elements, wherein the operations further comprise: in response to bearer differentiation being desired in a downlink packet, mapping an E-RAB to data radio bearer ("DRB") identifiers ("I D") and populating a GRE key field with the DRB ID to enable a UE to map the downlink packet to a packet data network connection or use a destination internet protocol address to map downlink packets to network interfaces.
  • DRB data radio bearer
  • Example 26 is an apparatus configured to be employed within a user equipment (UE) comprising: means for determining a first radio bearer to be transmitted over a long term evolution (“LTE”) radio link and a second radio bearer to be transmitted over a wireless local area network (“WLAN”) radio link; means for encapsulating a bearer identifier inside an uplink packet that identifies the second radio bearer; and means for providing the uplink packet to an internet protocol security (“IPsec”) tunnel and communicating the uplink packet to an evolved nodeB (“eNB”) via a WLAN access point (AP) with the IPsec tunnel.
  • LTE long term evolution
  • WLAN wireless local area network
  • Example 27 includes the subject matter of Example 26, wherein the means for encapsulating the bearer identifier comprises encapsulating a generic routing encapsulation ("GRE") header with the bearer identifier inside the uplink packet to enable the eNB to identify the second radio bearer and map uplink packets to Evolved Universal Terrestrial Radio Access Network (“E-UTRAN”) Radio Access Bearers (“E-RABs”), wherein the bearer identifier is included in a GRE key field of the GRE header.
  • GRE generic routing encapsulation
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • E-RABs Radio Access Bearers
  • Example 28 includes the subject matter of any of Examples 26-27, including or omitting any elements, further comprising : means for setting a protocol type field of the GRE header to comprise a value that indicates that the uplink packet comprises an internet protocol version 4 ("IPv4") packet.
  • IPv4 internet protocol version 4
  • Example 29 includes the subject matter of any of Examples 26-28, including or omitting any elements, further comprising : means for setting one or more bits of the GRE header to have a value that indicates that the GRE key field is being utilized as the bearer identifier.
  • Example 31 includes the subject matter of any of Examples 26-30, including or omitting any elements, further comprising : means for communicating to the eNB an indication that an IPsec tunnel is being initiated ; means for receiving one or more Radio Resource Control (“RRC") signals from the eNB based on the indication; and means for determining, based on the one or more RRC signals, an LWIP module configuration to enable the LWIP module such that at least one bearer is switched to be a WLAN bearer from an LTE bearer.
  • RRC Radio Resource Control
  • Example 32 is an apparatus configured to be employed within an evolved NodeB (eNB) comprising: means for receiving, by the one or more processors, an uplink packet including a radio bearer over a wireless local area network (“WLAN”) radio link; means for extracting, by the one or more processors, a bearer identifier from a generic routing encapsulation (“GRE”) header inside the uplink packet; and means for providing, by the one or more processors, the uplink packet over an S1 interface to a desired core network component using the bearer identifier.
  • eNB evolved NodeB
  • Example 33 includes the subject matter of Example 32, further comprising: means for mapping, by the one or more processors, the uplink packet to an evolved universal terrestrial radio access network (E-UTRAN) radio access bearers (E-RABs) using the bearer identifier.
  • E-UTRAN evolved universal terrestrial radio access network
  • E-RABs radio access bearers
  • Example 34 includes the subject matter of any of Examples 32-33, including or omitting any elements, wherein the bearer identifier is included in a GRE key field of the GRE header.
  • Example 35 includes the subject matter of any of Examples 32-34, including or omitting any elements, wherein a protocol type field of the GRE header includes a value comprising a plurality of bits, wherein the value indicates that the packet comprises an internet protocol security (I Psec) packet.
  • I Psec internet protocol security
  • Example 36 includes the subject matter of any of Examples 32-35, including or omitting any elements, further comprising : means for receiving, or causing to receive from a UE, in response to receiving the uplink pack, an indication to indicate that an LWIP entity is enabled at the UE; and means for transmitting, or causing to transmit one or more radio resource control (“RRC") signals to the U E based on the indication, wherein the one or more RRC signals include an LWIP entity configuration to enable the LWIP entity at the UE such that at least one bearer is switched to be a WLAN bearer from an LTE bearer or to be an LTE bearer from a WLAN bearer.
  • RRC radio resource control
  • Example 37 includes the subject matter of any of Examples 32-36, including or omitting any elements, further comprising : means for removing, in response to receiving the uplink packet, the GRE header from the uplink packet prior to transmitting the uplink packet to the desired core network component over the S1 interface.
  • Example 38 includes the subject matter of any of Examples 32-37, including or omitting any elements, further comprising : means for generating an internet protocol security ("IPsec") tunnel with a WLAN access point (“WLAN AP”) and communicating a packet data unit to a U E via the IPsec tunnel via the WLAN AP.
  • IPsec internet protocol security
  • WLAN AP WLAN access point
  • Example 39 includes the subject matter of any of Examples 32-38, including or omitting any elements, wherein a protocol type field of the GRE header includes a value of 0x0800, wherein the value of 0x0800 indicates that the uplink packet is an internet protocol version 4 ("I Pv4") packet.
  • a protocol type field of the GRE header includes a value of 0x0800, wherein the value of 0x0800 indicates that the uplink packet is an internet protocol version 4 ("I Pv4") packet.
  • Example 40 includes the subject matter of any of Examples 32-39, including or omitting any elements, further comprising : in response to bearer differentiation being desired in a downlink packet, means for mapping an E-RAB to data radio bearer ("DRB") identifiers ("I D") and populating a G RE key field with the DRB I D to enable a UE to map the downlink packet to a packet data network connection or use a destination internet protocol address to map downlink packets to network interfaces.
  • DRB data radio bearer
  • Example 41 is an apparatus employed in a user equipment (“UE") device comprising: a processor configured to: generate an LTE link with an evolved nodeB (“eNB”) and provide LTE communication data via the LTE link; generate a WLAN link with a WLAN access point (“AP”) and provide WLAN communication data via the WLAN link; and establish an internet protocol security (“IPsec”) tunnel via the WLAN AP to the eNB and communicate the LTE communication to the eNB via the IPsec tunnel to the WLAN AP.
  • a processor configured to: generate an LTE link with an evolved nodeB (“eNB”) and provide LTE communication data via the LTE link; generate a WLAN link with a WLAN access point (“AP”) and provide WLAN communication data via the WLAN link; and establish an internet protocol security (“IPsec”) tunnel via the WLAN AP to the eNB and communicate the LTE communication to the eNB via the IPsec tunnel to the WLAN AP.
  • eNB evolved nodeB
  • AP WLAN access point
  • IPsec internet protocol security
  • Example 42 is an apparatus employed in a evolved nodeB (“eNB") comprising: a processor configured to: generate an LTE link with a user equipment (“U E”), and provide LTE communication data via the LTE link; generate a WLAN link with a WLAN access point (“AP”) and provide WLAN communication data via the WLAN link; and enable an internet protocol security (“IPsec”) tunnel via the WLAN AP and communicate the LTE communication to the UE via the I Psec tunnel to the WLAN AP.
  • U E user equipment
  • AP WLAN access point
  • IPsec internet protocol security
  • Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a storage media or a computer readable storage device can be any available media that can be accessed by a general purpose or special purpose computer.
  • 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 other tangible and/or non-transitory medium, that can be used to carry or store desired information or executable instructions.
  • any connection is properly termed a computer-readable medium.
  • a computer-readable medium 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 reproduce data optically with lasers.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • a general-purpose processor can be a microprocessor, but, in the alternative, processor can be any conventional processor, controller, microcontroller, or state machine.
  • a processor can also be implemented as a combination of computing devices, for example, 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 can comprise one or more modules operable to perform one or more of the s and/or actions described herein.
  • modules e.g., procedures, functions, and so on
  • Software codes can be stored in memory units and executed by processors.
  • Memory unit can be implemented within processor or external to processor, in which case memory unit can be communicatively coupled to processor through various means as is known in the art.
  • at least one processor can include one or more modules operable to perform functions described herein.
  • a CDMA system can implement a radio technology such as Universal Terrestrial Radio Access (UTRA), CDMA1800, etc.
  • UTRA includes Wideband-CDMA (W-CDMA) and other variants of CDMA.
  • W-CDMA Wideband-CDMA
  • CDMA1800 covers IS-1800, IS-95 and IS-856 standards.
  • a TDMA system can implement a radio technology such as Global System for Mobile
  • GSM Global System for Mobile Communications
  • An OFDMA system can implement a radio technology such as Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.1 1 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.18, Flash-OFDML , etc.
  • E-UTRA Evolved UTRA
  • UMB Ultra Mobile Broadband
  • Wi-Fi Wi-Fi
  • WiMAX WiMAX
  • IEEE 802.18, Flash-OFDML 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 downlink and SC-FDMA on uplink.
  • UTRA, E-UTRA, UMTS, LTE and GSM are described in documents from an organization named "3rd Generation Partnership Project" (3GPP).
  • CDMA1 800 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2).
  • 3GPP2 3rd Generation Partnership Project 2
  • such wireless communication systems can 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.
  • SC-FDMA Single carrier frequency division multiple access
  • SC-FDMA has similar performance and essentially a similar overall complexity as those of OFDMA system.
  • SC-FDMA signal has lower peak-to-average power ratio (PAPR) because of its inherent single carrier structure.
  • PAPR peak-to-average power ratio
  • SC-FDMA can be utilized in uplink communications where lower PAPR can benefit a mobile terminal in terms of transmit power efficiency.
  • various aspects or features described herein can be implemented as a method, apparatus, or article of manufacture using standard programming and/or engineering techniques.
  • article of manufacture as used herein is intended to encompass a computer program accessible from any computer-readable device, carrier, or media.
  • computer-readable media can include but are not limited to magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips, etc.), optical disks (e.g., compact disk (CD), digital versatile disk (DVD), etc.), smart cards, and flash memory devices (e.g., EPROM, card, stick, key drive, etc.).
  • various storage media described herein can represent one or more devices and/or other machine-readable media for storing information.
  • machine-readable medium can include, without being limited to, wireless channels and various other media capable of storing, containing, and/or carrying instruction(s) and/or data.
  • a computer program product can include a computer readable medium having one or more instructions or codes operable to cause a computer to perform functions described herein.
  • Communications media embody computer-readable instructions, data structures, program modules or other structured or unstructured data in a data signal such as a modulated data signal, e.g., a carrier wave or other transport mechanism, and includes any information delivery or transport media.
  • modulated data signal or signals refers to a signal that has one or more of its characteristics set or changed in such a manner as to encode information in one or more signals.
  • communication media include wired media, such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media.
  • a software module can 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 can be coupled to processor, such that processor can read information from, and write information to, storage medium.
  • storage medium can be integral to processor.
  • processor and storage medium can reside in an ASIC.
  • ASIC can reside in a user terminal.
  • processor and storage medium can reside as discrete components in a user terminal.
  • the s and/or actions of a method or algorithm can reside as one or any combination or set of codes and/or instructions on a machine-readable medium and/or computer readable medium, which can be incorporated into a computer program product.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Selon l'invention, un nœud B évolué (eNB) et un équipement utilisateur (UE) peuvent fonctionner pour faciliter une connexion entre un autre avec une liaison d'évolution à long terme (LTE) sur une interface radio, et des données de communication LTE peuvent être fournies par l'intermédiaire de la liaison LTE. En outre, une liaison de réseau local sans fil (WLAN) peut être générée par l'intermédiaire d'un point d'accès (AP) de WLAN et de données de communication de WLAN fournies entre l'eNB et l'UE par l'intermédiaire de la liaison de WLAN. Une intégration LTE-WiFi avec une liaison de sécurité de protocole Internet (LWIP) est générée par un tunnel de sécurité de protocole Internet (IPsec) avec l'AP de WLAN et des communications LTE peuvent être fournies simultanément par l'intermédiaire du tunnel IPsec à l'AP de WLAN. Un module de LWIP peut ajouter un en-tête d'encapsulation de routage générique (GRE) à des paquets à envoyer par l'intermédiaire de la liaison de WLAN, comprenant l'insertion d'une identification (ID) de DRB dans un champ clé de l'en-tête de GRE pour effectuer une différenciation entre des supports radio des paquets.
PCT/US2016/036424 2016-02-05 2016-06-08 Transmission de support multiple dans la liaison montante pour une intégration d'évolution à long terme et wifi WO2017135986A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201662292100P 2016-02-05 2016-02-05
US62/292,100 2016-02-05

Publications (1)

Publication Number Publication Date
WO2017135986A1 true WO2017135986A1 (fr) 2017-08-10

Family

ID=56148720

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2016/036424 WO2017135986A1 (fr) 2016-02-05 2016-06-08 Transmission de support multiple dans la liaison montante pour une intégration d'évolution à long terme et wifi

Country Status (1)

Country Link
WO (1) WO2017135986A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10694560B2 (en) 2018-09-09 2020-06-23 Cisco Technology, Inc. Integrating private LTE radio service with WiFi access architectures
US20220377819A1 (en) * 2019-07-03 2022-11-24 Zte Corporation Method and apparatus for establishing data transmission link and computer-readable storage medium

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 13)", 11 January 2016 (2016-01-11), XP051065223, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG2_RL2/Specifications/201512_final_specs_after_RAN_70/> [retrieved on 20160111] *
BLACKBERRY UK LTD ET AL: "DRB identification for IPSec tunnel based LWA", vol. RAN WG2, no. Anaheim, USA; 20151116 - 20151120, 6 November 2015 (2015-11-06), XP051042441, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG2_RL2/TSGR2_92/Docs/> [retrieved on 20151106] *
ERICSSON: "LWA bearer ID addition in LTE-WLAN aggregation", vol. RAN WG2, no. Anaheim, USA; 20151116 - 20151120, 16 November 2015 (2015-11-16), XP051005979, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN2/Docs/> [retrieved on 20151116] *
INTEL CORPORATION ET AL: "Transfer of DRB ID for LWA", vol. RAN WG2, no. Anaheim, US; 20151116 - 20151120, 16 November 2015 (2015-11-16), XP051006069, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN2/Docs/> [retrieved on 20151116] *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10694560B2 (en) 2018-09-09 2020-06-23 Cisco Technology, Inc. Integrating private LTE radio service with WiFi access architectures
US20220377819A1 (en) * 2019-07-03 2022-11-24 Zte Corporation Method and apparatus for establishing data transmission link and computer-readable storage medium

Similar Documents

Publication Publication Date Title
US10848957B2 (en) Cellular IoT network architecture
US10257753B2 (en) WLAN mobility for LTE/WLAN aggregation
US11871291B2 (en) Data forwarding tunnel establishment between two user plane functions in fifth generation
EP3482602B1 (fr) Systèmes, procédés et dispositifs de séparation de plan utilisateur de commande pour des réseaux d&#39;accès radio 5g
US10749587B2 (en) Systems, methods and devices for using S-measure with new radio
US11122453B2 (en) Systems, methods and devices for measurement configuration by a secondary node in EN-DC
US11792838B2 (en) Bearer-less architecture for a wireless cellular network
US20200110627A1 (en) Centralized unit and distributed unit connection in a virtualized radio access network
US11122643B2 (en) LWIP enhancements for reliable DRB switching
WO2017014802A1 (fr) Couche de convergence pour systèmes de communication 5g
WO2018057473A1 (fr) Prise en charge de la continuité de session et de la signalisation de plan de commande dans des environnements à multiples technologies d&#39;accès radio
WO2018031081A1 (fr) Systèmes et procédés de séquençage de protocole de convergence de données par paquets
TWI720133B (zh) 用於使用配置管理功能的網路功能虛擬化生命週期管理的裝置及方法
WO2017135986A1 (fr) Transmission de support multiple dans la liaison montante pour une intégration d&#39;évolution à long terme et wifi
CN109155786B (zh) 从用户设备到网络的卸载处理的装置和方法
CN109076096B (zh) 无线设备的装置
US11778529B2 (en) Robust header compression indication after path switch during handover
WO2017200554A1 (fr) Stratégies de planification optimisées pour double connectivité et groupement de liaison
EP3437381A1 (fr) Échelonnement d&#39;un trafic sans surveillance dans un système d&#39;évolution à long terme (lte) après une interdiction

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16730974

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16730974

Country of ref document: EP

Kind code of ref document: A1