CN109076096B - Apparatus for wireless device - Google Patents

Abstract

The transmitter device encodes an LWIPEP (LWIP encapsulation protocol) Service Data Unit (SDU) for transmission to the receiver device via an LWIP tunnel. The transmitter device determines whether adding LWIPEP SDUs to the concatenated buffer would cause the size of the concatenated buffer to exceed a predetermined LWIP Maximum Transmission Unit (MTU) size. The transmitter device encodes, within an LWIPEP Packet Data Unit (PDU), a transmission of one or more LWIPEP SDUs from the cascaded buffer to the transmitter device if adding LWIPEP SDUs to the cascaded buffer would cause the size of the cascaded buffer to exceed a predetermined LWIP MTU size or a cascaded timer to expire. The transmitter device adds the LWIPEP SDU to the concatenation buffer if adding the LWIPEP SDU to the concatenation buffer does not cause the concatenation buffer size to exceed the predetermined LWIP MTU size and the concatenation timer has not expired.

Description

Apparatus for wireless device

Priority requirement

Priority of U.S. provisional patent application serial No. 62/336,392 entitled "ENHANCEMENTS TO SUPPORT CONCATENATION AND SEGMENTATION IN LTE WIFI international WITH IPSEC (LWIP)" filed 2016, 5, 13, 5, 2016, the entire contents of which are incorporated herein by reference, is claimed herein according to 35u.s.c. § 119.

Technical Field

Embodiments relate to wireless communications. Some embodiments relate to Radio Access Network (RAN) layers 2 and 3. Some embodiments relate to LWIP (long term evolution (LTE)/Wireless Local Area Network (WLAN) wireless level integration protocol) enhancements to support concatenation and segmentation in RAN-based LTE/WLAN integration with internet protocol security (IPSec). Some embodiments relate to Multiple Access Management Protocol (MAMP) in the Internet Engineering Task Force (IETF).

Background

In a cellular network, for example, in response to a User Equipment (UE) moving into or out of a Wi-Fi coverage area, the UE may sometimes switch from accessing data over a Long Term Evolution (LTE) network to accessing data over a Wi-Fi network, and vice versa. There may be a need to seamlessly switch from one wireless transmission mode (e.g., LTE, Wi-Fi, 5G, MultiFire, etc.) to another wireless transmission mode.

Therefore, there is a general need for systems and methods for LWIP (long term evolution (LTE)/Wireless Local Area Network (WLAN) radio level integration protocol) or MAMP (multiple access management protocol) enhancements to support concatenation and fragmentation in Radio Access Network (RAN) -based LTE/WLAN integration with internet protocol security (IPSec) or MAMP-based general integration of multiple access networks.

Disclosure of Invention

According to an aspect of the present disclosure, there is provided an apparatus of a wireless device, the apparatus comprising: processing circuitry and memory; the processing circuitry is to: encoding a multiple access management protocol, MAMP, service data unit, SDU, for transmission via a MAMP tunnel; determining whether adding a MAMP SDU to a cascaded buffer would cause the size of the cascaded buffer to exceed a predetermined MAMP maximum transmission unit, MTU, size; encoding one or more MAMP SDUs from the cascaded buffer for transmission within a MAMP packet data unit PDU if adding a MAMP SDU to the cascaded buffer would cause the size of the cascaded buffer to exceed a predetermined MAMP MTU size or the cascaded timer to expire; and if adding the MAMP SDU to the concatenation buffer does not cause the concatenation buffer size to exceed the predetermined MAMP MTU size and the concatenation timer has not expired, adding the MAMP SDU to the concatenation buffer.

Drawings

Fig. 1 is a block diagram of an example LWIP (long term evolution (LTE)/Wireless Local Area Network (WLAN) wireless class integration protocol) system, in accordance with some embodiments.

Fig. 2 is a block diagram of an example LWIP tunnel packet for concatenation, in accordance with some embodiments.

Fig. 3 is a data flow diagram of an example of enhanced LWIP ep (LWIP encapsulation protocol) concatenation and segmentation, according to some embodiments.

Fig. 4 is a block diagram of an exemplary MAMP (multiple access management protocol) system with universal integration of multiple access networks, in accordance with some embodiments.

Fig. 5 is a functional diagram of a wireless network according to some embodiments.

Fig. 6 illustrates components of a communication device according to some embodiments.

Fig. 7 illustrates a block diagram of a communication device, in accordance with some embodiments.

Fig. 8 illustrates another block diagram of a communication device in accordance with some embodiments.

Detailed Description

The following description and the annexed drawings set forth in detail certain illustrative embodiments sufficiently to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, and other changes. Portions and features of some example embodiments may be included in, or substituted for, those of other example embodiments. Embodiments set forth in the claims encompass all available equivalents of those claims.

Fig. 1 is a block diagram of an exemplary LWIP (long term evolution (LTE)/Wireless Local Area Network (WLAN) wireless class integration protocol) system 100, in accordance with some embodiments. As shown, system 100 includes an evolved node b (enb)110, User Equipment (UE)120, WLAN 130, and LWIP security gateway (LWIP-SeGW) 140. The eNB 110 communicates with the UE 120 over LTE, and the WLAN 130 communicates with the UE 120 over Wi-Fi. The LWIP-SeGW 140 communicates with the eNB 110 and the WLAN 130.

The eNB 110 includes the following layers: internet Protocol (IP), Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), Medium Access Control (MAC), and Physical (PHY). The IP layer includes LWIP encapsulation protocol (LWIPEP).

The UE 120 includes the following layers: PHY, MAC, RLC, PDCP, RRC, non-Access stratum (NAS), IP, Application (APP)/higher layers, WLAN PHY, and WLAN MAC. The IP layer includes LWIPEP.

As shown, the LWIP at the UE 120 communicates with the LWIP-SeGW 140 and the LWIP at the eNB 110 using LWIP tunnels. The LWIP tunnel includes the private IP of eNB 110 and the public IP of LWIP-SeGW 140. The LWIP tunnel includes a UE-LWIP-SeGW Internet protocol security (IPsec) tunnel. The LWIP tunnel is used to transport user plane IP packets from a Data Radio Bearer (DRB).

Fig. 1 illustrates an exemplary protocol architecture for LWIP. Here, the eNB 110 is the mobility anchor point and WLAN link aggregation is transparent to 3GPP (third Generation partnership project) core network elements (e.g., MME, S-GW, P-GW). The UE 120 establishes an LWIP tunnel with the eNB through the LWIP-SeGW via the WLAN, and IPSec is used to protect the IP traffic of the UE 120 through the LWIP tunnel, which is transparent to the WLAN and, in some cases, does not change existing WLAN deployments. Furthermore, traffic steering and multi-RAT (radio access technology) RRM (radio resource management) occurs at the top of the LTE RAN u-plane protocol stack (above the PDCP).

Some aspects of the subject technology address the case where the Maximum Transmission Unit (MTU) size of the LWIP tunnel is larger than the cellular MTU size. For example, Wi-Fi links for LWIP tunnels are based on 60GHz mmWave technology (e.g., IEEE 802.11ad/ay), which can support Gbps peak throughput and very large MTU sizes (e.g., 8K). In this case, it is desirable to concatenate a plurality of LWIPEP SDUs (service data units) into one LWIPEP PDU (packet data unit). Some aspects of the subject technology provide LWIPEP enhancements to support cascading.

Fig. 2 is a block diagram of an exemplary LWIP tunnel packet 200 for concatenation. As shown, the LWIP tunnel packet 20 includes an IP header (Wi-Fi)205, an IPSec ESP (encapsulating security payload) header 210, an LWPEP PDU 215, an IPSec ESP trailer 250, and an IPSec ESP Auth trailer 255. LWIPEP PDU 215 includes a plurality of LWIPEP SDUs 220.1-3 (although three LWIPEP SDUs are shown, the subject technology can include any number of LWIPEP SDUs) and an LWIP tail 235. Each LWIPEP SDU 220.k (where k is a number between 1 and 3) includes an IP header (LTE)225.k and an IP payload (LTE)230. k.

In some aspects, the subject technology includes adding two new control fields in the LWIPEP trailer 235 and adding new functions to the LWIPEP protocol stack-concatenation and reassembly. The new control field allows multiple LWIPEP SDUs 220.1-3 to be placed into a single LWIPEP PDU 215. Furthermore, it is proposed to use a new timer, the LWIPEP cascade timer, to limit the amount of time LWIPEP waits for cascade at the transmitter.

According to some aspects, the subject technology includes enhancing the existing LWIPEP PDU 215 format to include two new fields: a 1-bit "concatenation indicator" field 240 in the LWIP tail 235 and a 2-byte "IP length of first SDU" field 245.

Fig. 3 is a data flow diagram of an example of enhanced LWIPEP concatenation and segmentation 300. The enhanced LWIPEP concatenation and partitioning includes a transmitter 305 (downlink eNB; uplink UE) and a receiver 335 (downlink UE; uplink eNB). The transmitter 305 accesses SDUs from an IP (internet protocol) layer 310. The LWIPEP entity 315 of the transmitter concatenates (320) SDUs into PDUs and adds an LWIPEP trailer 325. The PDUs are provided to the LWIP tunnel 330. The receiver 335 accesses the LWIP tunnel 330 to receive the PDUs. The LWIPEP entity 345 at the receiver reassembles 350 the SDU and removes the LWIPEP trailer 355. The SDUs are passed to the IP layer 360, from which they may be provided to S1-U.

Fig. 3 illustrates an enhanced LWIPEP model that supports concatenation and segmentation. The LWIPEP transmitter maintains a cascade buffer and a cascade timer. The buffer gracefully stores LWIPEP SDUs waiting for concatenation. The timer controls how long LWIPEP SDUs can reside in the cascaded buffers and can be configured by the eNB via RRC signaling during the LWIP tunnel establishment procedure.

The LWIPEP transmitter 305 prepares an LWIPEP PDU based on the SDU in the buffer, and transmits the LWIPEP PDU if any of the following events occur: expiration of the concatenation timer, or including a newly arrived LWIPEP SDU in the current LWIPEP PDU, causes the LWIPEP PDU size to exceed the LWIP MTU size.

The timer starts when an LWIPEP SDU is placed in the buffer and the buffer is empty, and the timer pauses when an LWIPEP PDU is issued.

At the transmitter 305, when the LWIPEP entity 315 receives LWIPEP SDUs (IP packets) from an upper layer, if the LWIPEP PDU size exceeds the LWIP MTU size when newly arrived SDUs are included in the current LWIPEP PDU, the transmitter 305 prepares LWIPEP PDUs based on the LWIPEP SDUs in the buffer area and sends out LWIPEP PEDUs. The transmitter 305 then stores the newly arrived SDU in a buffer. If the buffer is empty, a cascade timer is started.

At the receiver 335, when the LWIPEP entity 345 receives LWIPEP PDUs from the lower layers, the LWIPEP entity 345 checks the "concatenation indicator" field 240 in the LWIP tail 235 to determine if the PDU includes multiple SDUs. If the PDU includes multiple SDUs, the LWIPEP entity 345 examines the "IP length of first SDU" field 245 in the LWIP tail 235 to obtain the length of the first LWIPEP SDU and to obtain the first SDU. It will then check the IP header length in the IP header of the second LWIPEP SDU and obtain the second SDU. This process continues until the last SDU.

The subject technology is described above in connection with LWIP. However, the subject technology is also applicable to the universal integration of multiple access networks based on the Internet Engineering Task Force (IETF) Multiple Access Management Protocol (MAMP). The MAMP framework bears many similarities to the LWIP framework. Thus, the solution proposed herein is applicable to MAMP and LWIP.

Fig. 4 is a block diagram of an exemplary MAMP system 400. As shown, the MAMP system includes a core (IP anchor) 405.1 for network 1 (e.g., LTE), a core (IP anchor) 405.2 for network 2 (e.g., WLAN), NCM (network connection manager) 410, MADP (multiple access data proxy) 415, access 420.1 for network 1, access 420.2 for network 2, and client device 425.

The client device 425 is an end user device that may support connections with multiple access nodes through different technologies.

The access 420 network element is a functional element in the network that delivers user data packets to the client device 425 via a point-to-point access link, such as a Wi-Fi air link, LTE air link, or Digital Subscriber Line (DSL).

The core 405 is a functional element that anchors the IP address of the client device 425 for communicating with applications via the network.

The NCM 410 is a functional entity in the network that monitors the distribution of data packets over the multiple available access 420 and core 405 network paths.

Client device 425 includes a CCM (client connection manager) 430. CCM 430 is a functional entity in client device 425 that exchanges MAMS (multiple access management system) signaling with NCM 410 and configures multiple network paths for the transmission of user data. The CCM also provides MAMS-specific u-plane functionality at the client device 425.

The MADP 415 handles the forwarding of user data traffic across multiple network paths. The MADP 415 provides MAMS-specific u-plane functionality on the network.

In some cases of the subject technology, LWIP may be considered an example of a MAMP framework. One difference is that the transmission of control signaling in LWIP is supported by RRC messages, while the control signaling in MAMP is delivered on top of user plane packets, such as User Datagram Protocol (UDP) or Transmission Control Protocol (TCP). In terms of similarity, CCM 430 in MAMP is similar to LWIPEP (u-plane) and RRC (c-plane) at the UE in LWIP. The NCM 410 is similar to RRC at an eNB implementing LWIP. MADP 415 is similar to LWIPEP at eNB. The LWIP solution disclosed herein is applicable to MAMP.

Fig. 5 illustrates an example of a portion of an end-to-end network architecture of a Long Term Evolution (LTE) network 500 having various components of the network, in accordance with some embodiments. As used herein, LTE networks refer to LTE and LTE-advanced (LTE-a) networks and other releases of LTE networks to be developed. The network 500 may include a Radio Access Network (RAN) (e.g., E-UTRAN or evolved universal terrestrial radio access network as depicted) 501 and a core network 520 (e.g., shown as Evolved Packet Core (EPC)) coupled together by an S1 interface 515. For convenience and brevity, only a portion of the core network 520 and the RAN 501 are shown in the example. The network 500 includes a UE 502 configured to: selecting an eNB Tx beam in a 6G eNB based on BRS measurements; transmitting PRACH or SR on the dedicated resource allocated by the LTE eNB; a report indicating the selected eNB Tx beam in the 6G eNB via PUSCH or PUCCH transmission in the LTE eNB; receiving a PDCCH order from an LTE eNB or an xPDCCH order from a 6G eNB for triggering xRACH transmission in the 6G eNB; and transmitting xPRACH on a resource indicated by the received PDCCH or xPDCCH command in the 6G eNB.

The core network 520 may include a Mobility Management Entity (MME)522, a serving gateway (serving GW)524, and a packet data network gateway (PDN GW) 526. RAN 501 may include an evolved node b (enb)504 (which may operate as a base station) for communicating with User Equipment (UE) 502. The enbs 504 may include a macro eNB 504a and a Low Power (LP) eNB 504 b. UE 502 may correspond to UE 120, transmitter 610, or receiver 620. The eNB 504 may correspond to the eNB 80, the transmitter 610, or the receiver 620.

The MME 522 may be similar in function to the control plane of a conventional Serving GPRS Support Node (SGSN). The MME 522 may manage mobility aspects in access such as gateway selection and tracking area list management. The serving GW 524 may terminate the interface towards the RAN 501 and route data packets between the RAN 501 and the core network 520. In addition, the serving GW 524 may be a local mobility anchor for inter-eNB handover, and may also provide an anchor for inter-3 GPP mobility. Other responsibilities may include lawful interception, charging, and some policy enforcement. The serving GW 524 and MME 522 may be implemented in one physical node or separate physical nodes.

The PDN GW 526 may terminate the SGi interface towards the Packet Data Network (PDN). The PDN GW 526 may route data packets between the EPC 520 and the external PDN, and may implement policy enforcement and charging data collection. The PDN GW 526 may also provide an anchor point for mobile devices with non-LTE access. The external PDN may be any kind of IP network as well as IP Multimedia Subsystem (IMS) domain. The PDN GW 526 and serving GW 524 may be implemented in a single physical node or in separate physical nodes.

The eNB 504 (macro and micro) may terminate the air interface protocol and may be the first point of contact for the UE 502. In some embodiments, the eNB 504 may perform various logical functions of the RAN 501 including, but not limited to, RNC (radio network controller) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management. According to an embodiment, the UE 502 may be configured to communicate OFDM communication signals with the eNB 504 over a multicarrier communication channel in accordance with an Orthogonal Frequency Division Multiple Access (OFDMA) communication technique. The OFDM signal may include a plurality of orthogonal subcarriers.

The S1 interface 515 may be an interface that separates the RAN 501 and the EPC 520. It can be divided into two parts: S1-U, which may carry traffic data between the eNB 504 and the serving GW 524, and SI-MME, which may serve as a signaling interface between the eNB 504 and the MME 522. The X2 interface may be an interface between enbs 504. The X2 interface may include two parts, X2-C and X2-U. X2-C may be a control plane interface between eNBs 504, while X2-U may be a user plane interface between eNBs 504.

For cellular networks, LP cell 504b may be generally used to extend coverage to indoor areas where outdoor signals do not reach well, or to increase network capacity in heavily used areas. In particular, it may be desirable to use different sized cells (macro, micro, pico, and femto cells) to enhance the coverage of a wireless communication system to improve system performance. The different sized cells may operate on the same frequency band, or may operate on different frequency bands, each cell operating on a different frequency band, or only different sized cells operating on different frequency bands. As used herein, the term LP eNB refers to any suitable opposing LP eNB for implementing a smaller cell (smaller than a macro cell), e.g., a femto cell, pico cell, or micro cell. Femto cell enbs may typically be provided by mobile network operators to their residential or business customers. A femto cell may typically be the size of a home gateway or smaller and is typically connected to a broadband line. A femto cell may connect to a mobile operator's mobile network and provide additional coverage typically in the range of 30 to 60 meters. Thus, LP eNB 504b may be a femto cell eNB because it is coupled through PDN GW 526. Similarly, a pico cell may be a wireless communication system that typically covers a small area, such as an area within a building (office, mall, train station, etc.) or further within an aircraft. A picocell eNB may typically be connected to another eNB through an X2 link, for example to a macro eNB through its Base Station Controller (BSC) functionality. Thus, the LP eNB may be implemented with a picocell eNB, as it may be coupled to the macro eNB 504a via an X2 interface. The pico cell eNB or other LP eNB 504b may include some or all of the functionality of the macro eNB or LP eNB 504 a. In some cases, this may be referred to as an access point base station or an enterprise femtocell.

In some embodiments, the UE 502 may communicate with an Access Point (AP)504 c. AP 504c may communicate with UE 502 using only unlicensed spectrum (e.g., WiFi frequency bands). AP 504c may communicate with macro eNB 504A (or LP eNB 504B) over an Xw interface. In some embodiments, the AP 504c may communicate with the UE 502 independently of communication between the UE 502 and the macro eNB 504A. In other embodiments, the AP 504c may be controlled by the macro eNB 504A and use LWA, as described in more detail below.

Communications over an LTE network may be divided into 7ms frames, each of which may contain 10 1ms subframes. Each subframe in the frame may in turn contain two 0.5ms slots. Each subframe may be used for Uplink (UL) communication from the UE to the eNB or Downlink (DL) communication from the eNB to the UE. In one embodiment, the eNB may allocate a greater amount of DL communications than UL communications in a particular frame. The eNB may schedule various frequency bands (f)₁And f₂) Or (c) is transmitted. The resource allocation in a subframe used in one frequency band may be different from that in another frequency band. Each slot of a subframe may contain 7 to 7 OFDM symbols, depending on the system used. In one embodiment, a subframe may contain 12 subcarriers. The downlink resource grid may be used for downlink transmissions from the eNB to the UE, while the uplink resource grid may be used for uplink transmissions from the UE to the eNB or from the UE to another UE. The resource grid may be a time-frequency grid, which is a physical resource on the downlink in each slot. The smallest time-frequency unit in the resource grid may be denoted as a Resource Element (RE). Each column and each row of the resource grid may correspond to one OFDM symbol and one OFDM subcarrier, respectively. The resource grid may contain Resource Blocks (RBs) describing the mapping of physical channels to resource elements and physical RBs (prbs). A PRB may be the smallest resource unit that may be allocated to a UE. The frequency of a resource block may be 180kHz wide and the time may be 1 slot long. In frequency, a resource block may be 12x15kHz subcarrier or 24x8.5kHz subcarrier wide. For most channels and signals, 12 subcarriers may be used per resource block, depending on the systemBandwidth. In Frequency Division Duplex (FDD) mode, the uplink and downlink frames may be 7ms and separated in frequency (full duplex) or time (half duplex). In Time Division Duplexing (TDD), uplink and downlink subframes may be transmitted on the same frequency and multiplexed in the time domain. The duration of the resource grid 500 in the time domain corresponds to one subframe or two resource blocks. Each resource grid may include 12 (subcarriers) × 14 (symbols) ═ 168 resource elements.

Each OFDM symbol may contain a Cyclic Prefix (CP) which may be used to effectively cancel inter-symbol interference (ISI) and a Fast Fourier Transform (FFT) period. The duration of the CP may be determined by the highest expected degree of delay spread. Although distortion from the previous OFDM symbol may exist within the CP, where the CP has sufficient duration, the previous OFDM symbol does not enter the FFT period. Once the FFT periodic signal is received and digitized, the receiver can ignore the signal in the CP.

There may be several different physical downlink channels transmitted using such resource blocks, including a Physical Downlink Control Channel (PDCCH) and a Physical Downlink Shared Channel (PDSCH). Each subframe may be divided into a PDCCH and a PDSCH. The PDCCH may typically occupy the first two symbols of each subframe and carry, among other things, information about the transmission format and resource allocation associated with the PDSCH channel and H-ARQ information associated with the uplink shared channel. The PDSCH may carry user data and higher layer signaling to the UE and occupy the remainder of the subframe. In general, downlink scheduling may be performed on the eNB based on channel quality information provided from the UEs to the eNB (e.g., assigning control and shared channel resource blocks to UEs within a cell), and then downlink resource assignment information may be sent to each UE on the PDCCH used for (assigned to) the UE. The PDCCH may contain Downlink Control Information (DCI) in one of a plurality of formats that instruct the UE how to find and decode data transmitted on the PDSCH in the same subframe from the resource grid. The DCI format may provide details such as the number of resource blocks, resource allocation type, modulation scheme, transport block, redundancy version, coding rate, etc. Each DCI format may have a Cyclic Redundancy Code (CRC) and be scrambled with a Radio Network Temporary Identifier (RNTI) that identifies the target UE for which the PDSCH is intended. Using the UE-specific RNTI may limit the decoding of the DCI format (and thus the corresponding PDSCH) to only the intended UE.

The embodiments described herein may be implemented into a system using suitably configured hardware and/or software. Fig. 6 illustrates components of a UE according to some embodiments. For example, at least some of the illustrated components may be used in an eNB or MME, such as UE 502 or eNB 504 illustrated in fig. 5. UE 600 and other components may be configured to use the synchronization signals described herein. The UE 600 may be one of the UEs 602 shown in fig. 1 and may be a fixed, non-mobile device or may be a mobile device. In some embodiments, UE 600 may include application circuitry 602, baseband circuitry 604, Radio Frequency (RF) circuitry 606, Front End Module (FEM) circuitry 608, and one or more antennas 610, coupled together at least as shown. At least some of baseband circuitry 604, RF circuitry 606, and FEM circuitry 608 may form a transceiver. In some embodiments, other network elements (e.g., enbs) may include some or all of the components shown in fig. 6. Other network elements (e.g., MME) may contain interfaces such as S1 interface to communicate with eNB through wired connection with UE.

The application or processing circuitry 602 may include one or more application processors. For example, the application circuitry 602 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor may include any combination of general-purpose processors and special-purpose processors (e.g., graphics processors, application processors, etc.). The processor may be coupled to and/or may include memory/storage and may be configured to: the instructions stored in the memory/storage are executed to enable various applications and/or operating systems to run on the system.

The baseband circuitry 604 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. Baseband circuitry 604 may include one or more baseband processors and/or control logic to process baseband signals received from the receive signal path of RF circuitry 606 and to generate baseband signals for the transmit signal path of RF circuitry 606. Baseband circuitry 604 may be connected with application circuitry 602 for generating and processing baseband signals and controlling operation of RF circuitry 606. For example, in some embodiments, the baseband circuitry 604 may include a second generation (2G) baseband processor 604a, a third generation (3G) baseband processor 604b, a fourth generation (4G) baseband processor 604c, and/or other baseband processors 604d for other existing generations, generations in development or to be developed in the future (e.g., fifth generation (5G), 7G, etc.). Baseband circuitry 604 (e.g., one or more of baseband processors 604 a-d) may process various radio control functions that enable communication with one or more radio networks via RF circuitry 606. Wireless control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency offset, and the like. In some embodiments, the modulation/demodulation circuitry of the baseband circuitry 604 may include FFT, precoding, and/or constellation mapping/demapping functionality. In some embodiments, the encoding/decoding circuitry of baseband circuitry 604 may include convolution, tail-biting convolution, turbo, viterbi, and/or Low Density Parity Check (LDPC) encoder/decoder functionality. Embodiments of modulation/demodulation and encoder/decoder functions are not limited to these examples, and other suitable functions may be included in other embodiments.

In some embodiments, the baseband circuitry 604 may include elements of a protocol stack, such as, for example, elements of an evolved universal terrestrial radio access network (E-UTRAN) protocol, including, for example, Physical (PHY) elements, Medium Access Control (MAC) elements, Radio Link Control (RLC) elements, Packet Data Convergence Protocol (PDCP) elements, and/or Radio Resource Control (RRC) elements. The Central Processing Unit (CPU)604e of the baseband circuitry 604 may be configured to: elements of the protocol stack are run for signaling at the PHY, MAC, RLC, PDCP, and/or RRC layers. In some embodiments, the baseband circuitry may include one or more audio Digital Signal Processors (DSPs) 604 f. The audio DSP 604f may include elements for compression/decompression and echo cancellation, and may include other suitable processing elements in other embodiments. In some embodiments, components of the baseband circuitry may be combined as appropriate in a single chip, a single chipset, or disposed on the same circuit board. In some embodiments, some or all of the constituent components of the baseband circuitry 604 and the application circuitry 602 may be implemented together, such as, for example, on a system on a chip (SOC).

In some embodiments, the baseband circuitry 604 may provide communications compatible with one or more radio technologies. For example, in some embodiments, baseband circuitry 604 may support communication with an Evolved Universal Terrestrial Radio Access Network (EUTRAN) and/or other Wireless Metropolitan Area Networks (WMANs), Wireless Local Area Networks (WLANs), or Wireless Personal Area Networks (WPANs). Embodiments in which the baseband circuitry 604 is configured to support wireless communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry. In some embodiments, the device may be configured to operate in accordance with communication standards or other protocols or standards, including Institute of Electrical and Electronics Engineers (IEEE)502.16 wireless technology (WiMax), IEEE502.11 wireless technology (WiFi), including IEEE502.11ad operating in the 70GHz millimeter wave spectrum, various other wireless technologies (e.g., 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, 5G, 6G, etc. technologies that have been or will be developed).

The RF circuitry 606 may enable communication with a wireless network using modulated electromagnetic radiation through a non-solid medium. In various embodiments, RF circuitry 606 may include switches, filters, amplifiers, and the like to facilitate communication with a wireless network. RF circuitry 606 may include a receive signal path, which may include circuitry to down-convert RF signals received from FEM circuitry 608 and provide baseband signals to baseband circuitry 604. RF circuitry 606 may also include a transmit signal path, which may include circuitry to up-convert baseband signals provided by baseband circuitry 604 and provide RF output signals to FEM circuitry 608 for transmission.

In some embodiments, RF circuitry 606 may include a receive signal path and a transmit signal path. The receive signal path of RF circuitry 606 may include mixer circuitry 606a, amplifier circuitry 606b, and filter circuitry 606 c. The transmit signal path of RF circuitry 606 may include filter circuitry 606c and mixer circuitry 606 a. RF circuitry 606 may further include synthesizer circuitry 606d for synthesizing the frequencies used by mixer circuitry 606a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuit 606a of the receive signal path may be configured to: the RF signal received from the FEM circuit 608 is downconverted based on the synthesized frequency provided by the synthesizer circuit 606 d. The amplifier circuit 606b may be configured to: the downconverted signal is amplified, and the filter circuit 606c may be a Low Pass Filter (LPF) or a Band Pass Filter (BPF) configured to: unwanted signals are removed from the down-converted signal to generate an output baseband signal. The output baseband signal may be provided to baseband circuitry 604 for further processing. In some embodiments, the output baseband signal may be a zero frequency baseband signal, but this is not required. In some embodiments, mixer circuit 606a of the receive signal path may comprise a passive mixer, although the scope of the embodiments is not limited in this respect.

In some embodiments, the mixer circuit 606a of the transmit signal path may be configured to: the input baseband signal is upconverted based on the synthesized frequency provided by synthesizer circuit 606d to generate an RF output signal for FEM circuit 608. The baseband signal may be provided by baseband circuitry 604 and may be filtered by filter circuitry 606 c. Filter circuit 606c may include a Low Pass Filter (LPF), although the scope of the embodiments is not limited in this respect.

In some embodiments, mixer circuit 606a of the receive signal path and mixer circuit 606a of the transmit signal path may comprise two or more mixers and may be arranged for quadrature down-conversion and/or up-conversion, respectively. In some embodiments, the mixer circuit 606a of the receive signal path and the mixer circuit 606a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuit 606a of the receive signal path and the mixer circuit 606a of the transmit signal path may be arranged for direct down-conversion and/or direct up-conversion, respectively. In some embodiments, mixer circuit 606a of the receive signal path and mixer circuit 606a of the transmit signal path may be configured for superheterodyne operation.

In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, RF circuitry 606 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry, and baseband circuitry 604 may include a digital baseband interface to communicate with RF circuitry 606.

In some dual-mode embodiments, separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.

In some embodiments, synthesizer circuit 606d may be a fractional-N synthesizer or a fractional-N/N +1 synthesizer, although the scope of embodiments is not so limited as other types of frequency synthesizers may be suitable. For example, the synthesizer circuit 606d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase locked loop with a frequency divider.

The synthesizer circuit 606d may be configured to: the output frequency used by mixer circuit 606a of RF circuit 606 is synthesized based on the frequency input and the divider control input. In some embodiments, the synthesizer circuit 606d may be a fractional N/N +1 synthesizer.

In some embodiments, the frequency input may be provided by a Voltage Controlled Oscillator (VCO), but this is not required. The divider control input may be provided by the baseband circuitry 604 or the application processor 602, depending on the desired output frequency. In some embodiments, the divider control input (e.g., N) may be determined from a look-up table based on the channel indicated by the application processor 602.

Synthesizer circuit 606d of RF circuit 606 may include dividers, Delay Locked Loops (DLLs), multiplexers, and phase accumulators. In some embodiments, the divider may be a dual-mode divider (DMD) and the phase accumulator may be a Digital Phase Accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by N or N +1 (e.g., based on a carry) to provide a fractional division ratio. In some example embodiments, the DLL may include a set of cascaded, tunable delay elements, a phase detector, a charge pump, and a D-type flip-flop. In these embodiments, the delay elements may be configured to decompose the VCO period into Nd equal phase groups, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

In some embodiments, the synthesizer circuit 606d may be configured to: a carrier frequency is generated as the output frequency, while in other embodiments the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with a quadrature generator and divider circuit to generate a plurality of signals at the carrier frequency having a plurality of different phases relative to each other. In some embodiments, the output frequency may be the LO frequency (f)_LO). In some embodiments, the RF circuitry 606 may include an IQ/polar converter.

FEM circuitry 608 may include a receive signal path, which may include circuitry configured to operate on RF signals received from one or more antennas 610, amplify the received signals, and provide amplified versions of the received signals to RF circuitry 606 for further processing. FEM circuitry 608 may further include a transmit signal path, which may include circuitry configured to amplify signals provided by RF circuitry 606 for transmission by one or more of one or more antennas 610.

In some embodiments, FEM circuitry 608 may include a TX/RX switch to switch between transmit mode and receive mode operation. The FEM circuitry may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry may include a Low Noise Amplifier (LNA) to amplify the received RF signal and provide the amplified received RF signal as an output (e.g., to RF circuitry 606). The transmit signal path of the FEM circuitry 608 may include: a Power Amplifier (PA) to amplify an input RF signal (e.g., provided by RF circuitry 606); and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 610).

In some embodiments, the UE 600 may include additional elements, such as memory/storage, a display, a camera, sensors, and/or an input/output (I/O) interface, as described in more detail below. In some embodiments, the UE 600 described herein may be part of a portable wireless communication device, such as a Personal Digital Assistant (PDA), a laptop or portable computer with wireless communication capability, a network tablet, a wireless telephone, a smart phone, a wireless headset, a pager, an instant messaging device, a digital camera, an access point, a television, a medical device (e.g., a heart rate monitor, a blood pressure monitor, etc.), or other device that may receive and/or transmit information wirelessly. In some embodiments, the UE 600 may include one or more user interfaces designed to enable a user to interact with the system and/or peripheral component interfaces designed to enable peripheral components to interact with the system. For example, the UE 600 may include one or more of a keyboard, keypad, touch pad, display, sensor, non-volatile memory port, Universal Serial Bus (USB) port, audio jack, power interface, one or more antennas, graphics processor, application processor, speaker, microphone, and other I/O components. The display may be an LCD or LED screen including a touch screen. The sensors may include a gyroscope sensor, an accelerometer, a proximity sensor, an ambient light sensor, and a positioning unit. The positioning unit may communicate with components of a positioning network, such as Global Positioning System (GPS) satellites.

Antenna 610 may include one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas or other types of antennas suitable for transmission of RF signals. In some multiple-input multiple-output (MIMO) embodiments, antennas 610 may be effectively separated to take advantage of spatial diversity and different channel characteristics that may result.

Although UE 600 is illustrated as having several separate functional elements, one or more of the functional elements may be combined and may be implemented by combinations of software-configured elements, such as processing elements including Digital Signal Processors (DSPs), and/or other hardware elements. For example, some elements may comprise one or more microprocessors, DSPs, Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Radio Frequency Integrated Circuits (RFICs), and combinations of various hardware and logic circuitry for performing at least the functions described herein. In some embodiments, a functional element may refer to one or more processes operating on one or more processing elements.

Embodiments may be implemented in one or a combination of hardware, firmware, and software. Embodiments may also be implemented as instructions stored on a computer-readable storage device, which may be read and executed by at least one processor to perform the operations described herein. A computer-readable storage device may include any non-transitory mechanism for storing information in a form readable by a machine (e.g., a computer). For example, a computer-readable storage device may include Read Only Memory (ROM), Random Access Memory (RAM), magnetic disk storage media, optical storage media, flash memory devices, and other storage devices and media. Some embodiments may include one or more processors and may be configured with instructions stored on a computer-readable storage device.

Fig. 7 is a block diagram of a communication device according to some embodiments. For example, the device may be a UE or eNB, such as UE 502 or eNB 504 shown in fig. 5. Physical layer circuitry 702 may implement various encoding and decoding functions that may include forming a baseband signal for transmission and decoding of received signals. The communication device 700 may also include a medium access control layer (MAC) circuit 704 for controlling access to the wireless medium. The communication device 700 may also include processing circuitry 706 (e.g., one or more single-core or multi-core processors) and memory 708 arranged to perform the operations described herein. Physical layer circuitry 702, MAC circuitry 704, and processing circuitry 706 may handle various radio control functions that enable communication between one or more wireless networks that are compatible with one or more radio technologies. The wireless control functions may include signal modulation, encoding, decoding, radio frequency shifting, and the like. For example, similar to the devices shown in fig. 2, in some embodiments, communication may be accomplished using one or more of WMAN, WLAN, and WPAN. In some embodiments, the communication device 700 may be configured to operate in accordance with 3GPP standards or other protocols or standards, including WiMax, WiFi, WiGig, GSM, EDGE, GERAN, UMTS, UTRAN or other 3G, 5G, 6G, etc., technologies that have been or will be developed. The communication device 700 may include: a transmitter circuit 712 for enabling wireless communication with other external devices; and an interface 714 for enabling wired communication with other external devices. As another example, the transceiver circuitry 712 may perform various transmit and receive functions, such as signal conversion between the baseband range and the Radio Frequency (RF) range.

Antenna 701 may include one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas or other types of antennas suitable for transmission of RF signals. In some MIMO embodiments, antennas 701 may be effectively separated to take advantage of spatial diversity and different channel characteristics that may result.

Although communication device 700 is shown with several separate functional elements, one or more of the functional elements may be combined and may be implemented by combinations of software-configured elements (e.g., processing elements including DSPs) and/or other hardware elements. For example, some elements may comprise one or more microprocessors, DSPs, FPGAs, ASICs, RFICs, and combinations of various hardware and logic circuitry for performing at least the functions described herein. In some embodiments, a functional element may refer to one or more processes operating on one or more processing elements. Embodiments may be implemented in one or a combination of hardware, firmware, and software. Embodiments may also be implemented as instructions stored on a computer-readable storage device, which may be read and executed by at least one processor to perform the operations described herein.

Fig. 8 illustrates another block diagram of a communication device 800 in accordance with some embodiments. The communication device 800 may correspond to the UE 502 or the eNB 504. In alternative embodiments, the communication device 800 may operate as a standalone device or may be connected (e.g., networked) to other communication devices. In a networked deployment, the communication device 800 may operate in the capacity of a server communication device, a client communication device, or both, in a server-client network environment. In an example, the communications device 800 may operate as a peer to peer communications device in a peer to peer (P2P) (or other distributed) network environment. The communication device 800 may be a UE, eNB, PC, tablet PC, STB, PDA, mobile phone, smartphone, network device, network router, switch or bridge, or any communication device capable of executing instructions (sequential or otherwise) that specify actions to be taken by the communication device. Further, while only a single communication device is shown, the term "communication device" should also be understood to include any collection of communication devices, such as cloud computing, software as a service (SaaS), other computer cluster configurations, that individually or jointly execute a set (or multiple sets) of instructions to implement any one or more of the methods discussed herein.

As described herein, examples may include or may operate on logic or multiple components, modules, or mechanisms. A module is a tangible entity (e.g., hardware) capable of performing specified operations and may be configured or arranged in a certain manner. In an example, a circuit may be arranged (e.g., internally or with respect to an external entity such as other circuits) as a module in a specified manner. In an example, all or a portion of one or more computer systems (e.g., a separate client or server computer system) or one or more hardware processors may be configured by firmware or software (e.g., instructions, application portions, or applications) as a module to perform specified operations. In an example, the software may reside on a communication device readable medium. In an example, the software, when executed by the underlying hardware of the module, causes the hardware to perform specified operations.

Thus, the term "module" is understood to encompass a tangible entity, either a physically constructed, specifically configured (e.g., hardwired), or temporarily (e.g., temporarily) configured (e.g., programmed) entity, for performing, or operating in a specified manner, some or all of any of the operations described herein. Given the example of temporarily configuring modules, each module need not be instantiated at any time. For example, where the modules include a general purpose hardware processor configured using software, the general purpose hardware processor may be configured as respective different modules at different times. The software may configure the hardware processor accordingly, e.g., to constitute a particular module at one point in time and to constitute different modules at different points in time.

The communication device (e.g., computer system) 800 may include a hardware processor 802 (e.g., a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), a hardware processor core, or any combination thereof), a main memory 804 and a static memory 806, some or all of which may communicate with each other via an interconnection link (e.g., bus) 808. The communication device 800 may also include a display unit 810, an alphanumeric input device 812 (e.g., a keyboard), and a User Interface (UI) navigation device 814 (e.g., a mouse). In an example, the display unit 810, the input device 812, and the UI navigation device 814 may be a touch screen display. The communication device 800 may additionally include a storage device (e.g., drive unit) 816, a signal generation device 818 (e.g., a speaker), a network interface device 820, and one or more sensors 821, such as a Global Positioning System (GPS) sensor, compass, accelerometer, or other sensor. The communication device 800 may include an output controller 828, such as a serial (e.g., Universal Serial Bus (USB), parallel, or other wired or wireless (e.g., Infrared (IR), Near Field Communication (NFC), etc.) connection to communicate with or control one or more peripheral devices (e.g., printer, card reader, etc.).

The storage device 816 may include a communication device-readable medium 822 on which is stored one or more sets of data structures and instructions 824 (e.g., software) embodying or used by any one or more of the techniques or functions described herein. The instructions 824 may also reside, completely or at least partially, within the main memory 804, within static memory 806, or within the hardware processor 802 during execution thereof by the communication device 800. In an example, one or any combination of the hardware processor 802, the main memory 804, the static memory 806, and the storage device 816 may constitute communication device readable media.

While the communication device-readable medium 822 is shown to be a single medium, the term "communication device-readable medium" can include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) configured to store the one or more instructions 824.

The term "communication device-readable medium" can include any medium that is capable of storing, encoding or carrying instructions for execution by communication device 800 and that cause communication device 800 to perform any one or more of the techniques of this disclosure, or that is capable of storing, encoding or carrying data structures used by or associated with such instructions. Non-limiting examples of communication device readable media may include solid state memory, as well as optical and magnetic media. Specific examples of the communication device readable medium may include: non-volatile memories such as semiconductor memory devices (e.g., electrically programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; random Access Memory (RAM); and CD-ROM and DVD-ROM disks. In some examples, the communication device readable medium may include a non-transitory communication device readable medium. In some examples, the communication device readable medium may include a communication device readable medium that is not a transitory propagating signal.

The instructions 824 may also be transmitted or received over a communication network 826 using a transmission medium via the network interface device 820 utilizing any one of a number of transmission protocols (e.g., frame relay, Internet Protocol (IP), Transmission Control Protocol (TCP), User Datagram Protocol (UDP), hypertext transfer protocol (HTTP), etc.). Exemplary communication networks can include a Local Area Network (LAN), a Wide Area Network (WAN), a packet data network (e.g., the Internet), a mobile telephone network (e.g., a cellular network), a Plain Old Telephone (POTS) network, and a wireless data network (e.g., referred to as

Of the Institute of Electrical and Electronics Engineers (IEEE)502.11 series of standards, referred to as

IEEE 502.16 series of standards), IEEE 502.15.4 series of standards, Long Term Evolution (LTE) series of standards, Universal Mobile Telecommunications System (UMTS) series of standards, or peer-to-peer (P2P) networks, etc. In an example, the network interface device 820 may include one or more physical jacks (e.g., ethernet, coaxial, or telephone jacks) or one or more antennas to connect to the communication network 826. In an example, the network interface device 820 may include multiple antennas to wirelessly communicate using at least one of single-input multiple-output (SIMO), MIMO, and multiple-input single-output (MISO) techniques. In some examples, the network interface device 820 may wirelessly communicate using multi-user MIMO techniques. The term "transmission medium" shall be taken to include any intangible medium that is capable of storing, encoding or carrying instructions for execution by the communication device 800, and includes digital or analog communication signals or other intangible medium to facilitate communication of such software.

The subject technology is described above in connection with various examples.

Example 1 is an apparatus of a wireless device, the apparatus comprising: processing circuitry and memory; the processing circuitry is to: encoding a MAMP (multiple access management protocol) Service Data Unit (SDU) for transmission via a MAMP tunnel; determining whether adding a MAMP SDU to a concatenation buffer would cause the size of the concatenation buffer to exceed a predetermined MAMP Maximum Transmission Unit (MTU) size; encoding one or more MAMP SDUs from a cascaded buffer for transmission within a MAMP Packet Data Unit (PDU) if adding a MAMP SDU to the cascaded buffer would cause the size of the cascaded buffer to exceed a predetermined MAMP MTU size or a concatenation timer to expire; and if adding the MAMP SDU to the concatenation buffer does not cause the concatenation buffer size to exceed the predetermined MAMP MTU size and the concatenation timer has not expired, adding the MAMP SDU to the concatenation buffer.

Example 2 is the apparatus of example 1, wherein the MAMP PDU comprises: an Internet Protocol (IP) header, a tunnel header, one or more MAMP SDUs, a MAMP trailer, or a MAMP header and a tunnel trailer.

Example 3 is the apparatus of example 2, wherein the processing circuitry is further to: adding a MAMP tail to the MAMP PDU prior to transmission of the MAMP PDU, wherein the MAMP tail includes a concatenation indicator and an indication of an IP length of a first MAMP SDU of the one or more MAMP SDUs.

Example 4 is the apparatus of example 3, wherein the concatenation indicator indicates whether the one or more MAMP SDUs include a single MAMP SDU or a plurality of MAMP SDUs.

Example 5 is the apparatus of example 4, wherein the IP length of the first MAMP SDU is included only if the concatenation indicator indicates that multiple SDUs are included in the one or more MAMP SDUs.

Example 6 is the apparatus of example 2, wherein the processing circuitry is further to: adding a MAMP header to the MAMP PDU prior to transmission of the MAMP PDU, wherein the MAMP header includes a concatenation indicator.

Example 7 is the apparatus of any one of examples 1-2, wherein the MAMP SDU comprises an Internet Protocol (IP) header and an IP payload.

Example 8 is the apparatus of any one of examples 1-2, wherein the processing circuitry is further to: a Network Connection Manager (NCM) signal is decoded, the NCM signal indicating a length of the cascaded timer.

Example 9 is the apparatus of any one of examples 1-2, wherein the MAMP MTU size exceeds an MTU size of an access network (e.g., a cellular network).

Example 10 is the apparatus of any one of examples 1-2, wherein the MAMP SDU comprises a fragmentation control field comprising information for reconstructing the fragmented MAMP SDU.

Example 11 is the apparatus of example 10, wherein the information comprises two bits indicating whether the MAMP SDU is from a first fragment, a last fragment, an intermediate fragment, or an unfragmented packet.

Example 12 is the apparatus of any one of examples 1-2, wherein the wireless device comprises a User Equipment (UE).

Example 13 is the apparatus of any one of examples 1-2, wherein the wireless device comprises an evolved node b (enb).

Example 14 is the apparatus of any one of examples 1-2, wherein the processing circuitry comprises a baseband processor.

Example 15 is the apparatus of any one of examples 1-2, further comprising transceiver circuitry to: if adding a MAMP SDU to the concatenation buffer would cause the size of the concatenation buffer to exceed a predetermined MAMP MTU size or the concatenation timer expires, an LWIPEP PDU is transmitted.

Example 16 is the apparatus of example 15, further comprising an antenna coupled to the transceiver circuitry.

Example 17 is an apparatus of a wireless device, the apparatus comprising: processing circuitry and memory; the processing circuitry is to: decoding an LWIPEP (Long term evolution (LTE)/Wireless Local Area Network (WLAN) Wireless level integration protocol encapsulation protocol) Packet Data Unit (PDU) received via an LWIP (LTE)/Wireless Local Area Network (WLAN) Wireless level integration protocol) tunnel; determining that the LWIPEP PDU comprises a plurality of LWIPEP Service Data Units (SDUs); determining a length of a first SDU of the plurality of LWIPEP SDUs based on an LWIP tail of the LWIPEP PDU; decoding a first SDU based on the determined length of the first SDU; for each additional SDU of the plurality of LWIPEP SDUs, determining a length based on an Internet Protocol (IP) header of the additional SDU; and decodes each additional SDU.

Example 18 is the apparatus of example 17, wherein the processing circuitry is to determine that the LWIPEP PDU includes a plurality of LWIPEP SDUs based on a concatenation indicator in the LWIP tail.

Example 19 is the apparatus of example 17, wherein the LWIPEP PDU comprises: an Internet Protocol (IP) header, a tunnel header, a plurality of LWIPEP SDUs, an LWIP trailer, and a tunnel trailer.

Example 20 is the apparatus of example 17, wherein the processing circuitry is further to: the LWIP tail is removed from the LWIPEP PDU.

Example 21 is the apparatus of example 17, wherein the processing circuitry comprises a baseband processor.

Example 22 is the apparatus of example 17, further comprising transceiver circuitry to: an LWIPEP PDU is received.

Example 23 is the apparatus of example 22, further comprising an antenna coupled to the transceiver circuitry.

Example 24 is a machine-readable medium storing instructions for execution by processing circuitry of an LWIP (long term evolution (LTE)/Wireless Local Area Network (WLAN) wireless class integration protocol) wireless device, the instructions to cause the processing circuitry to: encoding an LWIPEP (LTE/WLAN Wireless level integration protocol encapsulation protocol) Service Data Unit (SDU) for transmission via an LWIP tunnel; determining whether adding an LWIPEP SDU to a cascaded buffer would cause the size of the cascaded buffer to exceed a predetermined LWIP Maximum Transmission Unit (MTU) size; encoding, within an LWIPEP Packet Data Unit (PDU), a transmission of one or more LWIPEP SDUs from a cascaded buffer if adding the LWIPEP SDUs to the cascaded buffer would cause the size of the cascaded buffer to exceed a predetermined LWIP MTU size or a cascaded timer to expire; and adding the LWIPEP SDU to the concatenation buffer if adding the LWIPEP SDU to the concatenation buffer does not cause the concatenation buffer size to exceed the predetermined LWIP MTU size and the concatenation timer has not expired.

Example 25 is the machine-readable medium of example 24, wherein the LWIP wireless device comprises a User Equipment (UE).

Example 26 is the machine-readable medium of example 24, wherein the LWIP wireless device comprises an evolved node b (enb).

Example 27 is an apparatus of an LWIP (long term evolution (LTE)/Wireless Local Area Network (WLAN) wireless class integration protocol) wireless device, the apparatus comprising: means for decoding an LWIPEP (LTE/WLAN Wireless level integration protocol encapsulation protocol) Packet Data Unit (PDU) received via an LWIP tunnel; means for determining that an LWIPEP PDU comprises a plurality of LWIPEP Service Data Units (SDUs); means for determining a length of a first SDU of the plurality of LWIPEP SDUs based on an LWIP tail of the LWIPEP PDU; means for decoding a first SDU based on the determined length of the first SDU; means for determining a length for each additional SDU of the plurality of LWIPEP SDUs based on an Internet Protocol (IP) header of the additional SDU; and means for decoding each additional SDU.

Example 28 is the apparatus of example 27, wherein the LWIP wireless device comprises an evolved node b (enb).

Example 29 is the apparatus of example 27, wherein the LWIP wireless device comprises a User Equipment (UE).

Example 30 is an apparatus of a transmitter device, the apparatus comprising: processing circuitry and memory; the processing circuitry is to: encoding an LWIPEP (Long term evolution (LTE)/Wireless Local Area Network (WLAN) Wireless level integration protocol encapsulation protocol) Service Data Unit (SDU) for transmission to a receiver device via an LWIP (LTE/WLAN Wireless level integration protocol) tunnel; determining whether adding an LWIPEP SDU to a cascaded buffer would cause the size of the cascaded buffer to exceed a predetermined LWIP Maximum Transmission Unit (MTU) size; encoding, within an LWIPEP Packet Data Unit (PDU), transmission of one or more LWIPEP SDUs from a cascaded buffer to a receiver device if adding LWIPEP SDUs to the cascaded buffer would cause the size of the cascaded buffer to exceed a predetermined LWIP MTU size or a cascaded timer to expire; and adding the LWIPEP SDU to the concatenation buffer if adding the LWIPEP SDU to the concatenation buffer does not cause the concatenation buffer size to exceed the predetermined LWIP MTU size and the concatenation timer has not expired.

Example 31 is the apparatus of example 30, wherein the LWIPEP PDU comprises: an Internet Protocol (IP) header, an IP security (IPSec) Encapsulating Security Payload (ESP) header, one or more LWIPEP SDUs, an LWIP tail or LWIP header, an IPSec ESP tail, and an IPSec ESP authentication (Auth) tail.

Example 32 is the apparatus of example 31, wherein the processing circuitry is further to: adding an LWIP tail to the LWIPEP PDU prior to transmission of the LWIPEP PDU, wherein the LWIP tail includes a concatenation indicator and an indication of an IP length of a first LWIPEP SDU of the one or more LWIPEP SDUs.

Example 33 is the apparatus of example 32, wherein the concatenation indicator indicates whether the one or more LWIPEP SDUs include a single LWIPEP SDU or a plurality of LWIPEP SDUs.

Example 34 is the apparatus of example 33, wherein the IP length of the first LWIPEP SDU is included only if the concatenation indicator indicates that a plurality of SDUs are included in the one or more LWIPEP SDUs.

Example 35 is the apparatus of example 30, wherein the processing circuitry is further to: adding an LWIP header to the LWIPEP PDU prior to transmitting the LWIPEP PDU, wherein the LWIP header includes a concatenation indicator.

Example 36 is the apparatus of any one of examples 29-30, wherein the LWIPEP SDU comprises an Internet Protocol (IP) header and an IP payload.

Example 37 is the apparatus of any one of examples 29-30, wherein the processing circuitry is further to: a Radio Resource Control (RRC) signal from an evolved node b (enb) is decoded, the RRC signal indicating a length of a concatenation timer.

Example 38 is the apparatus of any one of examples 29-30, wherein the LWIP MTU size exceeds the cellular MTU size.

Example 39 is the apparatus of any one of examples 29-30, wherein the LWIPEP SDU comprises a segmentation control field including information for reconstructing the segmented LWIPEP SDU at the receiver device.

Example 40 is the apparatus of example 39, wherein the information comprises two bits indicating whether the LWIPEP SDU is from a first fragment, a last fragment, an intermediate fragment, or an unsegmented packet.

Example 41 is the apparatus of any one of examples 29-30, wherein the transmitter device comprises a User Equipment (UE) and the receiver device comprises an evolved node b (enb).

Example 42 is the apparatus of any one of examples 29-30, wherein the transmitter device comprises an evolved node b (enb) and the receiver device comprises a User Equipment (UE).

Example 43 is the apparatus of any one of examples 29-30, wherein the processing circuitry comprises a baseband processor.

Example 44 is the apparatus of any one of examples 29-30, further comprising transceiver circuitry to: if adding the LWIPEP SDU to the concatenated buffer would cause the size of the concatenated buffer to exceed a predetermined LWIP MTU size or the concatenated timer expires, an LWIPEP PDU is transmitted to the receiver device.

Example 45 is the apparatus of example 44, further comprising an antenna coupled to the transceiver circuit.

Although embodiments have been described with reference to specific exemplary embodiments, it will be apparent that various modifications and changes may be made to these embodiments. The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense. The accompanying drawings that form a part hereof show, by way of illustration and not of limitation, specific embodiments in which the subject matter may be practiced. The embodiments illustrated are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed herein. Other embodiments may be utilized and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. This detailed description, therefore, is not to be taken in a limiting sense, and the scope of various embodiments is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled.

Although specific embodiments have been illustrated and described herein, it should be appreciated that any arrangement calculated to achieve the same purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent to those of skill in the art upon reviewing the above description.

In this document, the use of the words "a" or "an" as is conventional in patent documents is intended to include one or more, independent of any other instances or usages of "at least one" or "one or more". Unless otherwise indicated, the word "or" is used herein to mean nonexclusive, or such that "a or B" includes "a, but not B," B, but not a, "and" a and B. In this document, the words "include" and "wherein" are used as equivalents of the respective words "comprising" and "wherein". Furthermore, in the appended claims, the words "include" and "comprising" are open-ended; that is, a system, UE, article, composition, formula, or process that includes elements in addition to those listed after such a word in a claim is still considered to fall within the scope of that claim. Furthermore, in the following claims, the terms "first," "second," and "third," etc. are used merely as labels, and are not intended to impose numerical requirements on their objects.

The claims appended hereto are included in the detailed description, where each claim may stand on its own as a separate embodiment.

Claims (15)

1. An apparatus of a wireless device, the apparatus comprising:

processing circuitry and memory; the processing circuitry is to:

encoding a multiple access management protocol, MAMP, service data unit, SDU, for transmission via a MAMP tunnel;

determining whether adding the MAMP SDU to a concatenation buffer would cause a size of the concatenation buffer to exceed a predetermined MAMP Maximum Transmission Unit (MTU) size;

encoding one or more MAMP SDUs from the cascaded buffer for transmission within a MAMP packet data Unit PDU if adding the MAMP SDU to the cascaded buffer would cause the size of the cascaded buffer to exceed the predetermined MAMP MTU size or a cascaded timer has expired; and is

Adding the MAMP SDU to the concatenation buffer if adding the MAMP SDU to the concatenation buffer does not cause the concatenation buffer size to exceed the predetermined MAMP MTU size and the concatenation timer has not expired.

2. The apparatus of claim 1, wherein the MAMP PDU comprises: an internet protocol IP header, a tunnel header, the one or more MAMP SDUs, a MAMP tail, or a MAMP header and a tunnel tail.

3. The apparatus of claim 2, wherein the processing circuit is further to:

adding the MAMP tail to a MAMP PDU prior to transmission of the MAMP PDU, wherein the MAMP tail includes a concatenation indicator and an indication of an IP length of a first MAMP SDU from the one or more MAMP SDUs.

4. The apparatus of claim 3, wherein the concatenation indicator indicates whether the one or more MAMP SDUs comprise a single MAMP SDU or a plurality of MAMP SDUs.

5. The apparatus of claim 4, wherein the IP length of the first MAMP SDU is included only if the concatenation indicator indicates that multiple SDUs are included in the one or more MAMP SDUs.

6. The apparatus of claim 2, wherein the processing circuit is further to:

adding the MAMP header to the MAMP PDU prior to transmission of the MAMP PDU, wherein the MAMP header includes a concatenation indicator.

7. The apparatus of claim 1, wherein the MAMP SDU comprises an internet protocol, IP, header and an IP payload.

8. The apparatus of claim 1, wherein the processing circuit is further to:

decoding a network connection manager, NCM, signal indicating a length of a cascaded timer.

9. The apparatus of claim 1, wherein the MAMP MTU size exceeds an MTU size of an access network.

10. The apparatus of claim 1, wherein the MAMP SDU comprises a fragmentation control field comprising information for reconstructing a fragmented MAMP SDU.

11. The apparatus of claim 10, wherein the information comprises two bits indicating whether the MAMP SDU is from a first fragment, a last fragment, an intermediate fragment, or an unfragmented packet.

12. The apparatus of claim 1, wherein the wireless device comprises a User Equipment (UE).

13. The apparatus of claim 1, wherein the wireless device comprises a base station.

14. The apparatus of claim 1, wherein the processing circuitry comprises a baseband processor.

15. The apparatus of claim 1, further comprising a transceiver circuit to:

transmitting a Long term evolution/Wireless local area network Wireless level integration protocol encapsulation protocol, LWIPEP, PDU if adding the MAMP SDU to the concatenation buffer would cause the size of the concatenation buffer to exceed the predetermined MAMP MTU size or the concatenation timer has expired.

Images