ROHC header compression for MPTCP
By introducing non-compression mode, secure compression mode and full compression mode into the MPTCP packet, the problem of low ROHC compression efficiency of the MPTCP packet is solved, and more efficient and reliable data transmission is achieved.
Patent Information
- Application Number
- CN202210545424.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2017-09-29
- Publication Date
- 2024-11-26
- Estimated Expiration
- 2037-09-29
AI Technical Summary
The ROHC compression efficiency of the MPTCP packet is low, which often leads to transmission delay and failure. The existing methods are prone to errors in the decompressor state machine.
Introduce three ROHC header compression modes: non-compression mode, safe compression mode and full compression mode. According to the support and context information of the decompressor, select the appropriate compression mode to avoid error feedback and enable full feedback during the MPTCP data transfer phase. Compress mode for efficiency.
It improves the transmission efficiency of MPTCP packets, reduces delays and failures, and ensures the reliability and stability of data transmission through appropriate compression mode selection and data processing.
Smart Images

Figure CN114885034B_ABST
Abstract
Description
[0001] This application is a divisional application of the invention patent application with application number 201780095383.7, application date September 29, 2017, and name “ROHC header compression for MPTCP”. Technical Field
[0002] The present application relates to wireless communications, including providing techniques for ROHC header compression for MPTCP packets. Background Art
[0003] The use of wireless communication systems is growing rapidly. In addition, wireless communication technology has evolved from only voice communication to also include the transmission of data (such as the Internet and multimedia content).
[0004] ROHC (Robust Header Compression) is a standardized (see, e.g., Internet Engineering Task Force (IETF) Request for Comments (RFC) 3095, IETF RFC 3759, IETF RFC 4815, IETF RFC 5225, and IETF RFC 6846) method for compressing headers of Internet packets of various types, such as UPD (User Datagram Protocol), RTP (Real-time Transport Protocol), and TCP (Transmission Control Protocol). In a typical streaming application, the header ranges from 40 bytes for IPv4 (Internet Protocol Version 4) to 60 bytes for IPv6. ROHC compresses the header from 40 to 60 bytes to 1 or 3 bytes via a compressor before the link. The decompressor after the link decompresses these headers.
[0005] MPTCP is a transport layer protocol built on top of traditional TCP to provide a transport layer over which applications can send / receive data through multiple paths (see, e.g., IETF RFC 6824). For example, multipath TCP can be used to aggregate TCP connections or substreams created over multiple networks on a multi-interface device into a single pipe or trunk for sending / receiving data. IETF RFC 6846 standardizes ROHC for TCP packets and has also been implemented for use with MPTCP packets.
[0006] However, in many cases ROHC of MPTCP packets results in transmission failures due in part to the format of the MPTCP packets. Thus, improvements are desired in the art. Summary of the invention
[0007] Embodiments presented herein relate particularly to a user equipment device (UE) and related methods for performing ROHC header compression on TCP packets with MPTCP option enabled.
[0008] In some embodiments, a compressor (e.g., one or more processors or processing circuits) included in a UE may determine (at least in part) based on first information included in a header of a data packet stream that a first portion of the data packet stream is formatted according to a transmission control protocol (TCP) with a multipath transmission control protocol (MPTCP) option enabled. The compressor may establish a context with a corresponding decompressor and may operate in one of three compression modes based on the context. In some embodiments, when the context indicates that the corresponding decompressor supports decompression of TCP packets with the MPTCP option enabled, the compressor may operate in a first compression mode or a second compression mode. In some embodiments, when the context indicates that the corresponding decompressor does not support decompression of TCP packets with the MPTCP option enabled, the compressor may operate in a third compression mode. The compressor may then generate a compressed data packet chain and transmit the compressed data packet chain to the corresponding decompressor.
[0009] In some embodiments, a first compression mode (e.g., secure compression mode) may include transmitting a first portion of a packet stream with MPTCP options enabled with partial ROHC, and transmitting a second portion of a packet stream without MPTCP options enabled with ROHC. In some embodiments, partial ROHC may include performing ROHC on packets that do not include MPTCP options and transmitting the MPTCP options as part of a compression list. In some embodiments, a second compression mode (e.g., full compression mode) may include transmitting a first portion of a packet stream with MPTCP options enabled with ROHC, and transmitting a second portion of a packet stream without MPTCP options enabled with ROHC. In some embodiments, a third compression mode (e.g., non-compression mode) may include transmitting a first portion of a packet stream with MPTCP options enabled without compression, and transmitting a second portion of a packet stream without MPTCP options enabled with ROHC.
[0010] The techniques described herein may be implemented in and / or used with a number of different types of devices, including, but not limited to, any of cellular telephones, tablet computers, wearable computing devices, portable media players, and a variety of other computing devices.
[0011] The present invention is intended to provide a brief overview of some of the themes described in this document. Therefore, it should be understood that the above features are only examples and should not be interpreted as narrowing the scope or essence of the themes described in this invention in any way. Other features, aspects and advantages of the themes described herein will become apparent through the following detailed description, drawings and claims. BRIEF DESCRIPTION OF THE DRAWINGS
[0012] A better understanding of the present subject matter may be obtained when the following detailed description of the embodiments is considered in conjunction with the following drawings.
[0013] Figure 1 to Figure 2 An exemplary wireless communication system is shown in accordance with some embodiments.
[0014] Figure 3 A cellular base station (eNB / gNB) and a Wi-Fi (or WLAN) access point (AP) communicating with a wireless user equipment device (UE) are shown according to some embodiments.
[0015] Figure 4 A block diagram illustrating an exemplary UE according to some embodiments.
[0016] Figure 5 An exemplary block diagram of a base station according to some embodiments is shown.
[0017] Figure 6 An example simplified block diagram of a WLAN access point (AP) is shown in accordance with some embodiments.
[0018] Fig. 7A An example of a technique for compressing IP packets according to ROHC is shown.
[0019] Figure 7B An example of a technique for decompressing IP packets according to ROHC is shown.
[0020] Fig. 8A An example of a ROHC compressor state machine is shown.
[0021] Figure 8B An example of a ROHC decompressor state machine is shown.
[0022] Fig.9A An example of the operation of the ROHC compressor state machine for a unidirectional mode of operation is shown.
[0023] Fig. 9B An example of the operation of the ROHC compressor state machine for a bidirectional optimistic mode of operation is shown.
[0024] Fig. 9CAn example of the operation of the ROHC compressor state machine for a bidirectional reliable mode of operation is shown.
[0025] Fig.10 The TCP header and options that may be used for ROHC compression according to IETF RFC 6846 are shown.
[0026] Fig.11 The TCP packet format according to IETF RFC 793 is shown.
[0027] Fig.12 The MPTTCP option format of the TCP header according to IETF RFC 6824 is shown.
[0028] Fig.13 MPTCP subtypes according to IETF RRFC 6824 are shown.
[0029] Fig.14 An example of a ROHC MPTCP compressor state machine is shown according to some embodiments.
[0030] Fig.15 An example of an item-option mapping table according to some embodiments is shown.
[0031] Fig.16 A block diagram illustrating an example of a method for ROHC compression of MPTCP packets according to some embodiments.
[0032] Although the features described herein are susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and are described in detail herein. However, it should be understood that the drawings and detailed description thereof are not intended to limit this document to the specific forms disclosed, but on the contrary, the purpose is to cover all modifications, equivalents and alternatives that fall within the spirit and scope of the subject matter as defined by the appended claims. DETAILED DESCRIPTION
[0033] the term
[0034] The following is a glossary of terms used in this disclosure:
[0035] Memory medium - any of various types of non-transitory memory devices or storage devices. The term "memory medium" is intended to include installation media, for example, CD-ROM, floppy disk or tape device; computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; non-volatile memory such as flash memory, magnetic media, for example, hard disk drive or optical storage device; registers or other similar types of memory elements, etc. The memory medium may also include other types of non-transitory memory or a combination thereof. In addition, the memory medium may be located in the first computer system executing the program, or may be located in a different second computer system connected to the first computer system via a network such as the Internet. In the latter case, the second computer system may provide program instructions to the first computer for execution. The term "memory medium" may include two or more memory media that may reside in different locations in different computer systems connected, for example, via a network. The memory medium may store program instructions (e.g., expressed as a computer program) that may be executed by one or more processors.
[0036] Carrier Medium—storage media as described above, and physical transmission media such as a bus, network, and / or other physical transmission media that transport signals such as electrical, electromagnetic or digital signals.
[0037] Programmable hardware element - includes various hardware devices that include multiple programmable function blocks connected via programmable interconnects. Examples include FPGA (field programmable gate array), PLD (programmable logic device), FPOA (field programmable object array), and CPLD (complex PLD). Programmable function blocks can vary from fine-grained (combinational logic unit or lookup table) to coarse-grained (arithmetic logic unit or processor core). Programmable hardware elements may also be referred to as "configurable logic units".
[0038] Computer System - Any of various types of computing or processing systems, including a personal computer system (PC), a mainframe computer system, a workstation, a network appliance, an Internet appliance, a personal digital assistant (PDA), a television system, a grid computing system, or other devices or combinations of devices. In general, the term "computer system" can be broadly defined to encompass any device (or combination of devices) having at least one processor that executes instructions from a memory medium.
[0039] User Equipment (UE) (or "UE device") - any of various types of computer system devices that are mobile or portable and that perform wireless communications. Examples of UE devices include mobile phones or smart phones (e.g., iPhone TM , based on Android TMphones), portable gaming devices (e.g., Nintendo DS TM , PlayStation Portable TM 、Gameboy Advance TM , iPhone TM ), laptops, wearable devices (e.g., smart watches, smart glasses), PDAs, portable Internet devices, music players, data storage devices or other handheld devices, etc. In general, the term "UE" or "UE device" can be broadly defined to cover any electronic device, computing device and / or telecommunication device (or combination of devices) that can be easily transmitted by a user and capable of wireless communication.
[0040] Base Station—The term “base station” (also referred to as “eNB” or “gNB”) has the full breadth of its ordinary meaning and includes at least a wireless communication station installed at a fixed location and used to communicate as part of a wireless cellular communication system.
[0041] TCP—refers to the Transmission Control Protocol used for Internet packet transmission and has the full range of its ordinary meaning. TCP is standardized by at least IETF RFCs 675, 793, 1122, and 7414.
[0042] MPTCP—refers to Multipath TCP, a transport layer protocol built on traditional TCP to provide a transport layer over which applications can send / receive data through multiple paths (see, e.g., IETF RFC 6824). MPTCP has the full scope of its ordinary meaning. MPTCP is standardized at least by IETF RCF 6824.
[0043] ROHC—refers to Robust Header Compression, and has the full range of its ordinary meaning. ROHC is standardized by at least IETF RFCs 3095, 3759, 4815, 4996, 4997, 5225, 5795, and 6846.
[0044] WI-FI—The term "WI-FI" or "Wi-Fi" has the full scope of its ordinary meaning and includes at least a wireless communication network or RAT that is served by wireless LAN (WLAN) access points and provides connectivity to the Internet through these access points. Most modern Wi-Fi networks (or WLAN networks) are based on the IEEE 802.11 standard and are marketed under the name "WI-FI". WI-FI (WLAN) networks are different from cellular networks.
[0045] BLUETOOTH TM – The term “BLUETOOTHTM ” has the full scope of its ordinary meaning and includes at least any of the various implementations of the Bluetooth standard, including Bluetooth Low Energy (BTLE) and Bluetooth Low Energy for Audio (BTLEA), including future implementations of the Bluetooth standard, etc.
[0046] Processing Element - refers to various elements or combinations of elements. Processing elements include, for example, circuits such as ASICs (application specific integrated circuits), portions or circuits of individual processor cores, entire processor cores, individual processors, programmable hardware devices such as field programmable gate arrays (FPGAs), and / or larger portions of systems including multiple processors.
[0047] Automatic—refers to an action or operation performed by a computer system (e.g., software executed by a computer system) or a device (e.g., a circuit, a programmable hardware element, an ASIC, etc.) without the need for user input to directly specify or perform the action or operation. Thus, the term "automatic" is in contrast to a user manually performing or specifying an action, where the user provides input to directly perform the action. An automatic process may be initiated by input provided by a user, but subsequent actions performed "automatically" are not specified by the user, i.e., are not performed "manually," where the user specifies each action to be performed. For example, a user filling out an electronic form by selecting each field and providing input specifying information (e.g., by typing in information, selecting check boxes, radio selections, etc.) is manually filling out the form, even though the computer system must update the form in response to the user action. The form may be automatically filled out by a computer system, where the computer system (e.g., software executed on the computer system) analyzes the fields of the form and fills out the form without any user input specifying the answers to the fields. As indicated above, a user may invoke automatic filling out of a form, but not participate in the actual filling out of the form (e.g., the user does not manually specify the answers to the fields but rather they are automatically completed). This specification provides various examples of operations that are automatically performed in response to actions taken by a user.
[0048] About - refers to a value that is close to a correct or exact value. For example, about can refer to a value that is within 1% to 10% of an exact (or desired) value. However, it should be noted that the actual threshold value (or tolerance) may depend on the application. For example, in one embodiment, "about" may mean within 0.1% of a specified or desired value, while in various other embodiments, the threshold value may be, for example, 2%, 3%, 5%, etc., depending on the desires or requirements of a particular application.
[0049] The titles used herein are only for organizational purposes and are not intended to be used to limit the scope of the specification. As used throughout this application, the word "may" is used in an allowed sense (i.e., meaning with possibility) rather than a mandatory sense (i.e., meaning must). The word "includes" indicates an open relationship, and therefore indicates including but not limited to. Similarly, the word "have" also indicates an open relationship, and therefore indicates having but not limited to. The terms "first", "second", "third", etc. used here are used as labels for the nouns after them, and unless otherwise clearly indicated, do not imply any type of ordering (e.g., space, time, logic, etc.). For example, unless otherwise specified, "a third component electrically connected to a module substrate" does not exclude the situation where "a fourth component electrically connected to a module substrate" is connected before the third component. Similarly, unless otherwise specified, the "second" feature portion does not require the "first" feature portion to be implemented before the "second" feature portion.
[0050] Various components may be described as being "configured to" perform one or more tasks. In such environments, "configured to" is a broad statement that generally means "having a structure" that performs one or more tasks during operation. Thus, even when the component is not currently performing the task, the component can be configured to perform the task (for example, a set of electrical conductors can be configured to electrically connect a module to another module even when the two modules are not connected). In some environments, "configured to" can be a broad statement that generally means "having a circuit system that performs one or more tasks during operation." Thus, even when the component is not currently turned on, the component can be configured to perform the task. Typically, the circuits that form the structure corresponding to "configured to" may include hardware circuits.
[0051] For ease of description, various components may be described as performing one or more tasks. Such descriptions should be interpreted as including the phrase "configured to". The description of a component being configured to perform one or more tasks is expressly intended not to invoke 35 U.S.C. §112(f) interpretation of that component.
[0052] Figures 1 to 3 —Wireless communication system
[0053] Figure 1 to Figure 2 An exemplary (and simplified) communication system is shown. Note that Figure 1 to Figure 2 The systems are merely examples of possible systems, and embodiments may be implemented in any of a variety of systems as desired.
[0054] Figure 1 The exemplary wireless communication system shown in includes two endpoints with multiple communication paths between them. Thus, endpoint 122 may be able to communicate with endpoint 124 via path 126 or path 128.
[0055] Each of endpoints 122 and endpoint 124 may be a "fixed" endpoint or a "mobile" endpoint. A fixed endpoint may be an endpoint that is substantially stationary and / or an endpoint that communicates via one or more wired communication technologies. Some examples may include a server computer that provides cloud-based services via the Internet, a bridge, a load balancer, a personal desktop computer or workstation, a set-top box, a television, etc. A mobile endpoint may be an endpoint that is substantially mobile and / or an endpoint that communicates via one or more wireless communication technologies. Some examples may include a user equipment device (UE) (such as a mobile phone smartphone or tablet), a portable gaming device, a portable media player, etc. It should be noted that an endpoint may also be a hybrid endpoint that shares the features of a fixed endpoint and a mobile endpoint. For example, many laptop computers may be able to perform wireless (e.g., Wi-Fi / BLUETOOTH) and wired (e.g., Ethernet) communications, and may also be able to be substantially mobile (e.g., when operating from a battery backup power source) or substantially stationary (e.g., when docked and / or connected to a wall outlet for a power source) at different times.
[0056] One or both of the endpoints 122, 124 may be multi-interfaced. For example, one or both of the endpoints 122, 124 may be capable of communicating via multiple network interfaces. Thus, there may be multiple possible communication paths 126, 128 between the endpoints 122, 124. It should be noted that although Figure 1 126 and 128), but any number of paths may exist between endpoints. For example, if each of endpoints 122, 124 is capable of communicating via two different network interfaces, then there may be four possible communication paths between endpoints 122, 124. Other numbers of different network interfaces and possible communication paths are also possible.
[0057] Multiple communication paths 126, 128 may be used to establish a multipath transport control protocol (MPTCP) session or connection between endpoints 122 and 124. The MPTCP session may be established according to and / or may include any of the various features described in the MPTCP specification IETF RFC 6824. For example, one subflow of the MPTCP connection may be established via path 126 while another subflow of the MPTCP connection may be established via path 128. Such MPTCP connections may be established and configured / controlled according to various aspects of the present disclosure.
[0058] Figure 2 The exemplary wireless communication system shown in FIG. Figure 11. Specifically, a first endpoint (e.g., wireless user equipment device (UE) 106) may be able to communicate with another endpoint (e.g., server 210) using either a first communication path (e.g., via cellular base station 102, core network 100, and wide area network 104) or a second communication path (e.g., via Wi-Fi access point 112 and wide area network 104).
[0059] As shown, UE 106 can communicate with Wi-Fi access point (AP) 112 and cellular base station 102. AP 112 can be an access point that provides a wireless local area network (WLAN). AP 112 can be equipped to communicate with a wide area network (WAN) 104 such as the Internet. Therefore, AP 112 can facilitate communication between UE 106 and WAN 104. AP 112 and UE 106 can be configured to communicate through a transmission medium using Wi-Fi (including any of the various versions of IEEE 802.11 (e.g., a, b, g, n, ac, ad and / or ax) or LTE in an unlicensed band (LAA)). It should be noted that AP 112 can also facilitate communication between UE and other computing devices that also directly participate in the WLAN.
[0060] The base station 102 may be a base transceiver station (BTS) or a cell site ("cellular base station") and may include hardware that enables wireless communications with cellular devices (such as UE 106) according to one or more cellular communication protocols. The communication area (or coverage area) of the base station 102 may be referred to as a "cell". The base station 102 and the UE 106 may be configured to communicate over a transmission medium using any of a variety of radio access technologies (RATs) or wireless communication technologies, such as GSM, UMTS (WCDMA, TDS-CDMA), LTE, Advanced LTE (LTE-A), 5G-NR, HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), Wi-Fi, WiMAX, etc. An example of LTE or LTE-A communications may be VoLTE (Voice over LTE).
[0061] As shown, the cellular base station can be configured to communicate with the core network 100 of the cellular service provider. Thus, the base station 102 can facilitate communication between the UE 106 and the core network 100. The core network 100 can in turn be configured to communicate with the WAN 1040 (e.g., the Internet or another wide area network). It should be noted that the core network 100 can also or alternatively be configured to communicate with one or more other networks (e.g., communication networks such as the public switched telephone network (PSTN), one or more core networks of other cellular service providers, etc.). The cellular base station 102 can thus provide various communication capabilities to the UE 106 (and potentially many other UEs), such as voice, text messaging (e.g., SMS (Short Message Service) and similar text messaging technologies such as iMessage, Facebook Messenger, Whatsapp, etc.) and / or data services.
[0062] Thus, the UE 106 may be capable of communicating using a plurality of wireless communication standards, including at least one wireless networking protocol (e.g., Wi-Fi) and at least one cellular communication protocol (e.g., GSM, UMTS (WCDMA), LTE, Advanced LTE (LTE-A), 5G-NR, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), etc.). Note also that, if desired, the UE 106 may also or alternatively be configured to communicate using one or more global navigation satellite systems (GNSS, such as GPS or GLONASS), one or more mobile television broadcast standards (e.g., ATSC-M / H or DVB-H), and / or any other wireless communication protocols (e.g., BLUETOOTH, NAN, Wi-Fi Direct, etc.). Additionally or alternatively, the UE 106 may be capable of communicating using one or more wired communication standards. For example, the UE 106 may be capable of communicating with one or more wired access points (e.g., via Ethernet). For example, in addition to or as an alternative to utilizing Wi-Fi communications, UE 106 might be coupled via wired means to Wi-Fi access point 112. Other combinations of wireless and wired communication standards (including more than two wireless and / or wired communication standards) are also possible.
[0063] The server 210 may also be configured to communicate with the WAN 104. The server 210 may provide access to a cluster or server farm configured to provide one or more cloud-based services via the Internet. For example, the server 210 may be further configured to communicate with service centers, which may each include one or more computing devices (e.g., servers) configured to provide cloud-based services. Each service center may, for example, be configured to provide services for a specific application (such as a mapping application, an intelligent personal assistant application, an e-commerce application, a media streaming application, a gaming application, etc.). It should be noted that although the server 210 is Figure 2 104 is shown as one possible exemplary access port (and potential MPTCP endpoint), but if desired, any of a variety of devices may be used (alternatively or in combination with server 210) as an intermediary / access port device / entity to the service center, such as a gateway, router, firewall, and / or any of a variety of other "middle boxes." In addition, it should be noted that, although not explicitly shown, server 210 may include any number of network interfaces for connecting to WAN 104, including one or more wired network interfaces and / or one or more wireless network interfaces.
[0064] Figure 3 A UE 106 is shown communicating with a cellular base station 102 and a Wi-Fi access point 112. The UE 106 may be a device with multiple wireless network connectivity, such as a mobile phone, handheld device, computer or tablet computer, or virtually any type of wireless device.
[0065] UE 106 may include a processor configured to execute program instructions stored in a memory. UE 106 may perform any of the method embodiments described herein by executing such stored instructions. Alternatively or in addition, UE 106 may include a programmable hardware element, such as a field programmable gate array (FPGA) configured to perform any of the method embodiments described herein or any portion of any of the method embodiments described herein.
[0066] UE 106 may be configured to communicate using any of a plurality of wireless communication protocols. For example, UE 106 may be configured to communicate using at least one cellular communication protocol (such as CDMA2000, LTE, LTE-A, 5G-NR, etc.) and Wi-Fi. Other combinations of wireless and / or wired communication standards are also possible.
[0067] UE 106 may include one or more antennas for communicating using one or more wireless communication protocols. UE 106 may share one or more portions of a receive chain and / or a transmit chain between multiple wireless communication standards; for example, UE 106 may be configured to communicate using CDMA2000 (1xRTT / 1xEV-DO / HRPD / eHRPD) or any one of LTE / LTE-A using partially or fully shared wireless communication circuits (e.g., using shared radios or at least shared radio components). As another example, UE 106 may be configured to communicate using any one of LTE / LTE-A or 5G-NR using partially or fully shared wireless communication circuits (e.g., using shared radios or at least shared radio components). The shared communication circuit may be coupled to a single antenna or may be coupled to multiple antennas (e.g., for MIMO) for performing wireless communication. Alternatively, UE 106 may include an independent transmit chain and / or receive chain (e.g., including independent antennas and other radio components) for each wireless communication protocol configured to communicate therewith. As another possibility, UE 106 may include one or more radios or radio components shared between multiple wireless communication protocols and one or more radios or radio components dedicated to a single wireless communication protocol. For example, UE 106 may include a shared radio for communicating using any one of LTE / LTE-A or CDMA20001xRTT (or any one of LTE or GSM) and an independent radio for communicating using each of Wi-Fi and BLUETOOTH. For another example, UE 106 may include a shared radio for communicating using any one of 5G-NR or LTE / LTE-A and an independent radio for communicating using each of Wi-Fi and / or BLUETOOTH. Other configurations are also possible.
[0068] Figure 4 -Exemplary block diagram of UE
[0069] Figure 4A possible block diagram of a user equipment device (UE) 106 is shown. As shown, the UE 106 may include a system on a chip (SOC) 300, which may include parts for various purposes. For example, as shown, the SOC 300 may include a processor 302 that can execute program instructions for the UE 106 and a display circuit 304 that can perform graphics processing and provide display signals to a display 360. The processor 302 may also be coupled to a memory management unit (MMU) 340, which may be configured to receive addresses from the processor 302 and convert these addresses to locations in a memory (e.g., a memory 306 and a read-only memory (ROM) 350, a flash memory 310). The MMU 340 may be configured to perform memory protection and page table translation or setup. In some embodiments, the MMU 340 may be included as part of the processor 302.
[0070] UE 106 may also include other circuits or devices, such as display circuitry 304 , radio 330 , connector I / F 320 , and / or display 360 .
[0071] In the illustrated embodiment, ROM 350 may include a boot loader that may be executed by processor 302 during startup or initialization. Also as shown, SOC 300 may be coupled to various other circuits of UE 106. For example, UE 106 may include various types of memory, a connector interface 320 (e.g., for coupling to a computer system), a display 360, and wireless communication circuitry (e.g., for communication using 5G-NR, LTE, CDMA2000, BLUETOOTH, Wi-Fi, NFC, GPS, etc.).
[0072] UE 106 may include at least one antenna, and in some embodiments may include multiple antennas, for performing wireless communications with base stations and / or other devices. For example, UE 106 may use antenna 335 to perform wireless communications. As described above, UE 106 may be configured in some embodiments to perform wireless communications using multiple wireless communication standards or radio access technologies (RATs).
[0073] As described herein, UE 106 may include hardware components and software components for implementing methods according to embodiments of the present disclosure. The processor 302 of UE 106 may be configured to implement some or all of the methods described herein, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). In other embodiments, the processor 302 may be configured as a programmable hardware element such as an FPGA (field programmable gate array), or as an ASIC (application-specific integrated circuit).
[0074] Figure 5 —Exemplary block diagram of a base station
[0075] Figure 5 An exemplary block diagram of a base station 102 according to some embodiments is shown. Note that Figure 5 The base station of is only one example of a possible base station. As shown, the base station 102 may include a processor 504 that can execute program instructions for the base station 102. The processor 504 may also be coupled to a memory management unit (MMU) 540 or other circuit or device, which may be configured to receive addresses from the processor 504 and convert these addresses to locations in memory (e.g., memory 560 and read-only memory (ROM) 550).
[0076] The base station 102 may include at least one network port 570. The network port 570 may be configured to couple to a telephone network and provide multiple devices, such as the UE 106, with access to the telephone network.
[0077] The network port 570 (or an additional network port) may be further configured or alternatively configured to couple to a cellular network, such as a core network of a cellular service provider. The core network may provide mobility-related services and / or other services to multiple devices, such as UE 106. In some cases, the network port 570 may be coupled to a telephone network via the core network, and / or the core network may provide a telephone network (e.g., in other UE devices served by the cellular service provider).
[0078] The base station 102 may include at least one antenna 534 and possibly multiple antennas. The antenna 534 may be configured to operate as a wireless transceiver and may be further configured to communicate with the UE 106 via the radio component 530. The antenna 534 communicates with the radio component 530 via a communication chain 532. The communication chain 532 may be a receive chain, a transmit chain, or both. The radio component 530 may be configured to communicate via various wireless telecommunication standards including, but not limited to, 5G-NR, LTE, LTE-A, UMTS, CDMA2000, Wi-Fi, etc.
[0079] Base station 102 may be configured to communicate wirelessly using multiple wireless communication standards. In some cases, base station 102 may include multiple radio components that enable base station 102 to communicate according to multiple wireless communication technologies. For example, as one possibility, base station 102 may include an LTE radio component for performing communications according to LTE and a Wi-Fi radio component for performing communications according to Wi-Fi. In such cases, base station 102 may be able to operate as both an LTE base station and a Wi-Fi access point. As another possibility, base station 102 may include a multi-mode radio component capable of performing communications according to any of multiple wireless communication technologies (e.g., LTE and Wi-Fi).
[0080] Base station 102 may include hardware and software components for implementing or supporting specific implementations of the features described herein.
[0081] Figure 6 —Access Point Block Diagram
[0082] Figure 6 An exemplary block diagram of an access point (AP) 112 is shown. Note that Figure 6 The AP block diagram of FIG. 1 is only one example of a possible system. As shown, the AP 112 may include a processor 604 that may execute program instructions for the AP 112. The processor 604 may also be coupled (directly or indirectly) to a memory management unit (MMU) 640 or other circuit or device that may be configured to receive addresses from the processor 604 and translate those addresses into locations in memory (e.g., memory 660 and read-only memory (ROM) 650).
[0083] AP 112 may include at least one network port 670. Network port 670 may be configured to couple to a wired network and provide access to the Internet to multiple devices such as UE 106. For example, network port 670 (or an additional network port) may be configured to couple to a local network, such as a home network or an enterprise network. For example, port 670 may be an Ethernet port. The local network may provide a connection to an additional network such as the Internet.
[0084] The AP 112 may include at least one antenna 634, which may be configured to operate as a wireless transceiver and may be further configured to communicate with the mobile device 106 via the wireless communication circuit 630. The antenna 634 communicates with the wireless communication circuit 630 via a communication chain 632. The communication chain 632 may include one or more receive chains, one or more transmit chains, or both. The wireless communication circuit 630 may be configured to communicate via Wi-Fi or WLAN (e.g., 802.11). For example, in the case of a small cell when the AP is co-located with a base station or in other situations where it may be desirable for the AP 112 to communicate via a variety of different wireless communication technologies, the wireless communication circuit 630 may also or alternatively be configured to communicate via various other wireless communication technologies (including but not limited to Long Term Evolution (LTE), Advanced LTE (LTE-A), LLA, 5G-NR, Global System for Mobile (GSM), Wideband Code Division Multiple Access (WCDMA), CDMA2000, etc.).
[0085] AP 112 may include hardware components and software components for implementing or supporting specific implementations of the features described herein.
[0086] ROHC compression for MPTCP packets
[0087] In existing implementations, the Robust Header Compression (ROHC) protocol is used to reduce bandwidth usage on network links with limited capacity and / or high cost, such as mobile networks. Therefore, ROHC defines a lossless compression schedule for network headers. The ROHC protocol is capable of compressing various Internet packets such as IPv4 packets, IPv6 packets, and TCP packets. It should be noted that the ROHC protocol only compresses the network header and exploits the information redundancy in the network header. Fig. 7A As shown, at 702, the ROHC compressor may parse the uncompressed packets, and at 704, the ROHC compressor may associate the parsed uncompressed packets with a stream or chain (e.g., packets with inter-packet redundancy). At 706, the ROHC compressor may construct corresponding ROHC packets (e.g., by appending non-redundant (or irregular) items when they appear in the uncompressed packets), and at 708, the ROHC compressor may transmit the corresponding ROHC packets to an associated ROHC decompressor. Figure 7B As shown, at 710, the ROHC decompressor may receive a ROHC packet, and at 712, the ROHC decompressor may parse the ROHC packet. At 714, the ROHC decompressor may decode packet fields of the ROHC packet according to the ROHC protocol, and at 716, the ROHC may construct an uncompressed packet based on the decoded packet fields.
[0088] like Fig. 8AAs shown, the ROHC compressor can operate in one of three states. As shown, at 810, the ROHC compressor can operate in the initialization and refresh states. Once the context is established with the ROHC decompressor, the ROHC compressor can transition to either state 812 or state 814. State 812 represents a first order state, and state 814 represents a second order state. When the ROHC compressor becomes more confident in the context of the ROHC decompressor, the ROHC compressor can transition from state 812 to state 814, indicating an increase in compression of the packet header. Conversely, when the ROHC compressor becomes less confident in the context of the ROHC decompressor (e.g., via a feedback packet indicating an error condition at the ROHC decompressor), the ROHC compressor can transition from state 814 to either state 812 or state 810 (and similarly transition from state 812 to state 810). Furthermore, in some cases, the ROHC compressor may periodically transition from a higher state (eg, states 814 , 812 ) to a lower state (eg, states 812 , 810 ) to ensure context validity at the ROHC decompressor.
[0089] Similarly, if Figure 8B As shown, the ROHC decompressor may also operate in one of three states. As shown, at 820, the ROHC decompressor may initially operate in the no-context state. Once the ROHC decompressor has received and successfully decompressed the initialization and refresh packets containing both static and dynamic information (e.g., as generated by the ROHC compressor operating in state 810), the decompressor may generate context information and transition to the full-context state at 824. The ROHC decompressor may then transition to a lower state (e.g., states 822, 820) upon an error condition. Note that when transitioning from state 824 to a lower state, the ROHC decompressor may first transition to state 822 (e.g., the static context state) and attempt to recover and transition back to state 824. However, if the error condition persists, the ROHC decompressor may transition back to the no-context state 820, causing the ROHC compressor to transition back to state 810.
[0090] Furthermore, the ROHC protocol defines three modes of operation, and selection of the mode of operation may be based on one or more parameters, including availability of a feedback channel, error probability, and / or header size variation. Fig.9A shows the unidirectional operating mode of the ROHC compressor, Fig. 9B shows the bidirectional optimistic mode of operation of the ROHC compressor, and Fig. 9C The bidirectional reliable operation mode of the ROHC compressor is shown. Fig.9AAs shown, the ROHC compressor starts in state 810 and transmits a plurality of initialization and refresh (IR) packets to the ROHC decompressor, and then transitions to state 814 (e.g., at 910). Note that for the unidirectional mode of operation of the ROHC compressor, packets are sent in one direction from the ROHC compressor to the ROHC decompressor. Once in state 814, a timeout / update mechanism may be enabled to periodically transition the ROHC compressor (e.g., at 920) from state 814 to state 812. Further, while in state 814, a timeout mechanism may be enabled (e.g., when necessary) to transition the ROHC compressor (e.g., at 912) back to state 810. Once in state 812, another timeout mechanism may be enabled (e.g., when necessary) to transition (e.g., at 916) from state 812 to state 810. Further, if the state machine does not time out in state 812, the ROHC compressor may return to state 814 (e.g., at 918). Furthermore, if the state machine does return to state 810, the state machine may optionally transition (e.g., at 914) back to state 812 or (e.g., at 910) back to state 814. Note that the ROHC compressor may determine to transition to either bidirectional operating mode if the ROHC compressor receives feedback from the ROHC decompressor.
[0091] Therefore, if Fig. 9B As shown, once the context of the ROHC decompressor is established, the ROHC compressor may transition from state 810 to state 814 (e.g., at 930). Once in state 814, if the ROHC compressor receives an acknowledgement (ACK) from the ROHC decompressor (e.g., at 942), the ROHC compressor may remain in state 814. However, if the ROHC compressor receives a negative ACK (NACK) or a context update request, the ROHC compressor may transition to state 812 (e.g., at 940). Furthermore, while in state 814, if the ROHC compressor receives a static NACK, the ROHC compressor may transition back to state 810 (e.g., at 932). Once in state 812, if the ROHC compressor receives an ACK, the ROHC compressor may transition back to state 814 (e.g., at 938). Conversely, if the ROHC compressor receives a NACK or a static NACK, the ROHC compressor may transition to state 810 (e.g., at 936). Once in state 810 , the ROHC compressor may optionally transition back to state 812 (eg, at 934 ) or transition back to state 814 (eg, at 930 ).
[0092] Go to Fig. 9C, in bidirectional reliable mode, once the context of the ROHC decompressor is established and an ACK is received from the ROHC decompressor, the ROHC compressor may (e.g., at 950) transition from state 810 to state 814. Once in state 814, if the ROHC compressor receives an acknowledgement (ACK) from the ROHC decompressor (e.g., at 942), the ROHC compressor may remain in state 814. However, if the ROHC compressor receives a negative ACK (NACK) or a context update request, the ROHC compressor may (e.g., at 940) transition to state 812. Furthermore, while in state 814, if the ROHC compressor receives a static NACK, the ROHC compressor may (e.g., at 932) transition back to state 810. Once in state 812, if the ROHC compressor receives an ACK, the ROHC compressor may (e.g., at 958) transition back to state 814. Conversely, if the ROHC compressor receives a NACK or a static NACK, the ROHC compressor may transition (e.g., at 936) to state 810. Once in state 810, the ROHC compressor may optionally transition (e.g., at 954) back to state 812 or (e.g., at 950) back to state 814 upon receiving an ACK from the ROHC decompressor.
[0093] As mentioned above, the ROHC protocol has been implemented for TCP packet compression. Figures 10 to 13 Various structures and formats of TPC and MPTCP headers are shown. For example, Fig.10793, a TCP packet format according to IETF RFC 793 is shown. Note that as shown, one tick mark may represent a bit position. The TCP packet format includes header fields for: source port (e.g., 16 bits for the source port number), destination port (e.g., 16 bits for the destination port number), sequence number (e.g., 32 bits for the sequence number of the first data byte in the segment), acknowledgment number (e.g., 32 bits for the value of the next sequence number that the sender of the segment expects to receive), data offset (e.g., 4 bits for the 32-bit word number in the TCP header), reserved (e.g., 6 bits reserved for future use), control bits (e.g., 6 bits for control bits such as URG (urgent pointer field flag), ACK (acknowledgement field flag), PSH (push-in function flag), etc.), and the like. The header may include a header that is a 16-bit string that is used to send data to the sender, a 16-bit string that is used to send data to the sender, and a 16-bit string that is used to send data to the sender. The header may include a 16-bit string that is used to send data to the sender, a 16-bit string that is used to send data to the sender, and a 16-bit string that is used to send data to the sender. The header may include a 16-bit string that is used to send data to the sender, a 16-bit string that is used to send data to the sender, and a 16-bit string that is used to send data to the sender. The header may include a 16-bit string that is used to send data to the sender, a 16-bit string that is used to send data to the sender, and a 16-bit string that is used to send data to the sender. The header may include a 16-bit string that is used to send data to the sender, and a 16-bit string that is used to send data to the sender.
[0094] IETF RFC 6846 specifies various TCP header fields that can be used for ROHC compression. For example, Fig.11 As shown, the TCP header fields that can be used for compression include IPv4 identification (IP-ID), TCP sequence number (SN), TCP acknowledgment number, TCP reservation, TCP ECN flag (ECN), TCP window, and TCP options. Fig.11 As further shown, supported TCP options include Maximum Segment Size (MSS), Window Scaling (WSCALE), Allow Selective Acknowledgement (SACK), TCP SACK (SACK), and TCP Timestamp (TS).
[0095] Fig.12The MPTCP option format of the TCP header according to IETF RFC 6824 is shown. IETF RFC 6824 defines the Multipath TCP (MPTCP) protocol as a set of extensions to conventional TCP to provide multipath TCP services, which can enable a transport connection to run simultaneously across multiple paths. For example, MPTCP can extend the use of the TCP option field, and can transmit all MPTCP signaling and control information in the TCP option field. In addition, since the data offset field is 4 bits (0-15) and the maximum TCP header size is 60 bytes, the option field can occupy up to 20 bytes. For example, if Fig.12 As shown, the TCP option field includes a type field, a length field, a subtype field, and subtype specific data (variable length). Note that a single TCP option number (eg, "type" field) has been assigned to MPTCP, and each message can be identified by the value of the subtype field.
[0096] Fig.13 MPTCP subtypes according to IETF RRFC 6824 are shown. For example, a value of 0x0 is an indication of multipath capability (e.g., as defined in section 3.1 of IETF RFC 6824), a value of 0x1 is an indication of joining a connection (e.g., as defined in section 3.2 of IETF RFC 6824), a value of 0x2 is a data sequence signal (e.g., as defined in section 3.3 of IETF RFC 6824), a value of 0x3 is an indication of adding an address (e.g., as defined in section 3.4.1 of IETF RFC 6824), a value of 0x4 is an indication of deleting an address (e.g., as defined in section 3.4.2 of IETF RFC 6824), a value of 0x5 is an indication of changing sub-flow priority (e.g., as defined in section 3.3.8 of IETF RFC 6824), a value of 0x6 is an indication of fallback (e.g., as defined in section 3.6 of IETF RFC 6824), a value of 0x7 is an indication of fast close (e.g., as defined in IETF RFC 6824, section 3.5), values 0x8 to 0xe are unassigned, and value 0xf is reserved.
[0097] As TCP has evolved, more options have been used, such as the MPTCP options described above. MPTCP has been widely used in mobile devices, however, the ROHC compression method defined in IETF RFC 6824 does not explicitly allow MPTCP packets, so the compression of MPTCP packet headers is not efficient. In addition, when attempting to perform ROHC compression on MPTCP packet headers, current methods often cause errors in the decompressor state machine, resulting in delays and / or failures in MPTCP packet transmission.
[0098] Therefore, the embodiments of the present disclosure define (specify) ROHC compression processes and algorithms specifically for MPTCP. In some embodiments, such as Fig.14 As shown in state machine 1400 of , three additional ROHC header compression modes may be enabled for MPTCP—non-compression mode (e.g., state 1410), secure compression mode (e.g., state 1420), and full compression mode (e.g., state 1430). In some embodiments, a device such as UE 106 described above may start in non-compression mode 1420 when both a compressor (e.g., included within a device) and a decompressor (e.g., included within a base station (such as base station 102 or AP 112)) support ROHC-TCP, but the decompressor experiences an error condition when attempting to decompress a TCP packet with an MPTCP option. In some embodiments, the non-compression mode may be entered in response to the decompressor providing error feedback to the compressor, for example, when performing compression operations in one of the bidirectional operating modes. In such cases, the compressor may only compress TCP packets without the MPTCP option to avoid future error feedback.
[0099] In some embodiments, a device (e.g., UE 106) may select (or transition to, e.g., at 1401) a secure compression mode (e.g., state 1420). In such embodiments, the device may initially compress TCP packets without MPTCP options and leave the MPTCP options portion uncompressed. In such embodiments, the device may transmit the MPTCP options into a compression list. Further, in some embodiments, the secure compression mode may be initially used during MPTCP startup (e.g., MPTCP connection establishment). In some embodiments, the same compression mode may be used when an MPTCP address needs to be added and / or when an MPTCP address needs to be deleted.
[0100] In some embodiments, when in secure compression mode 1420 and after context startup (e.g., connection establishment) and presentation of MPTCP options to the decompressor, irregular content (e.g., including MPTCP options) may be sent (transmitted by the device) as part of an irregular chain if the structure and content of the compression list has not changed, and the structure and content include the MPTCP options, subtype, and subtype-specific data. In other words, when the structure and content of the compression list has not changed, information about the compression list does not need to be sent in the compressed basic header, and the irregular content (including the MPTCP options) may be sent (transmitted) as part of an irregular chain. Note that in some embodiments, the MPTCP content may be considered unchanged only if the type, length, subtype, and subtype-specific data are all unchanged.
[0101] Also note that the compressed header chain is used to group fields based on similar characteristics. For example, the chain is formed by appending the items for each header to the chain in the order of appearance in the uncompressed packet. In some embodiments, for compressed MPTCP packets, the irregular chain may include irregular chain items for TCP options. Note that these chain items can be placed after the irregular chain items of the TCP header.
[0102] In some embodiments, while in secure compression mode 1420 and after context startup (e.g., connection establishment) and presentation of the MPTCP options to the decompressor, if the structure of the compression list is constant and the content defined within the irregular format for the options has changed, then the irregular content (e.g., including the MPTCP options) may be sent (transmitted by the device) as part of an irregular chain. In other words, when the structure of the compression list has not changed but the content defined within the irregular format for the options has changed, information about the compression list need not be sent in the compressed basic header, and the irregular content (including the MPTCP options) may be sent (transmitted) as part of an irregular chain. Note that in some embodiments, the MPTCP content may be considered to have changed if any bytes in the length, subtype, and / or subtype specific data have changed.
[0103] In some embodiments, while in secure compression mode 1420 and after context startup (e.g., connection establishment) and presentation of the MPTCP option to the decompressor, the compressed list and the irregular content may be sent (transmitted by the device) if the structure of the list changes. In other words, the compressed list may be sent in a compressed basic header, including an indication of the structure and order of the compressed list. Additionally, content defined within the irregular format of the option may be sent as part of an irregular chain, provided that the item content is not part of the compressed list.
[0104] In some embodiments, the device (e.g., UE 106) may select (or transition to, e.g., at 1402) full compression mode (e.g., state 1430). In such embodiments, the device may compress the entire MPTCP packet, including the TCP header, TCP options, and MPTCP options. Note that in some embodiments, full compression mode may be enabled during the MPTCP data transmission phase (e.g., after context startup). In some embodiments, full compression mode may only be enabled for MPTCP subtype 0x02.
[0105] In some embodiments, while in full compression mode 1430 and after context startup (e.g., connection establishment) and presentation of the MPTCP options to the decompressor (e.g., the compressor has transmitted a complete compressed list of options), information about the compression list may not be sent (e.g., transmitted by the device) in the compressed base header if the structure and content of the compression list has not changed. In other words, if the structure and content of the compression list is constant, the compression list may not be transmitted, e.g., to save transmission overhead.
[0106] In some embodiments, when in full compression mode 1430 and after context startup (e.g., connection establishment) and presentation of the MPTCP options to the decompressor (e.g., the compressor has transmitted a complete compressed list of options), if the structure of the compression list is constant and the content defined within the irregular format for the options has changed, then the irregular content (e.g., MPTCP options) may be sent (transmitted by the device) as part of an irregular chain. In other words, when the structure of the compression list has not changed (e.g., constant) but the content defined within the irregular format for the options has changed, then information about the compression list need not be sent in the compressed basic header and the irregular content may be sent (transmitted) as part of an irregular chain. Note that in some embodiments, the MPTCP content may be considered to have changed if any bytes in the length, subtype, and / or subtype specific data have changed.
[0107] In some embodiments, while in full compression mode 1430 and after context startup (e.g., connection establishment) and presentation of the MPTCP option to the decompressor, the compressed list and the irregular content may be sent (transmitted by the device) if the structure of the list changes. In other words, the compressed list may be sent in a compressed basic header, including an indication of the structure and order of the compressed list. Additionally, content defined within the irregular format of the option may be sent as part of an irregular chain, provided that the item content is not part of the compressed list.
[0108] Note that in some embodiments, the device (e.g., UE 106) may transition from non-compressed mode 1410 to secure compressed mode 1420 (and vice versa) based on feedback (positive ACK or negative ACK) from the decompressor (e.g., at 1401). In addition, the device may transition (e.g., at 1402) from secure compressed mode 1420 to full compressed mode 1430. Note that if an error condition occurs (or persists) while in secure compressed mode 1420, the device may transition (e.g., at 1403) to non-compressed mode 1410.
[0109] In some embodiments, a device (e.g., UE 106) may implement table-based item compression. Fig.15 As shown, a table may associate an index with an item. In some embodiments, a compressor (included in or implemented by a device) may maintain the table. In addition, a decompressor (included in or implemented on a base station such as base station 106 or AP 112) may also maintain a table of all received (index, item) pairs. Thus, Fig.14 As shown, the (index, item) pair (7, MPTCP) may indicate an MPTCP option. In addition, the (index, item) pair (0, NOP) may indicate a no operation option, the (index, item) pair (1, EOL) may indicate the termination of parsing of the option, the (index, item) pair (2, MSS) may indicate a maximum segment length option, the (index, item) pair (3, Window Scale) may indicate a window scaling option, the (index, item) pair (4, TIMESTAMP) may indicate a timestamp option, the (index, item) pair (5, SACK-PERMITTED) may indicate a SACK option is allowed, the (index, item) pair (6, SACK) may indicate a SACK option, and indexes 8-15 may indicate various general options.
[0110] Fig.16 A block diagram illustrating an example of a method for ROHC compression of MPTCP packets according to some embodiments. Among other devices, Fig.16 The method shown can be used in conjunction with any of the systems or devices shown in the above figures. In various embodiments, some of the method elements shown can be performed concurrently in an order different from the order shown, or can be omitted. Additional method elements can also be performed as required. As shown, the method can be operated as follows.
[0111] At 1602, a compressor (e.g., one or more processors or processing circuits of a UE, such as UE 106) may determine that a first portion of a data packet stream is formatted according to a multipath transport protocol (MPTCP). In other words, the compressor may determine (e.g., based on content of a header of one or more data packets) that the data packets are formatted using a transmission control protocol (TCP) and an MPTCP option of an enabled TCP option. For example, first information included in a header of the data stream may indicate that the first portion of the data packet stream is formatted according to TCP with an MPTCP option enabled.
[0112] At 1604, the compressor may establish a context for data transmission with a corresponding decompressor. Note that the decompressor may be located in (or included in) a base station or access point such as the base station 106 or AP 112 described above.
[0113] At 1606, the context may indicate that the corresponding decompressor supports MPTCP, and the method may continue at 1608. In other words, the context may indicate that the corresponding decompressor is configured to decompress packets including the compressed MPTCP option. Alternatively, at 1616, the context may indicate that the corresponding decompressor does not support MPTCP, and the method may continue at 1618. In other words, the context may indicate that the corresponding decompressor is not configured to decompress packets including the compressed MPTCP option. In some embodiments, an indication may be received from the corresponding decompressor via feedback, such as an error indication.
[0114] At 1608, ROHC may be performed in a first compression mode or a second compression mode when the corresponding decompressor supports MPTCP. Compression may generate a compressed packet chain. In some embodiments, the first compression mode may correspond to transmitting a first portion of the packet stream with partial ROHC and transmitting a second portion of the packet stream with ROHC. Note that the second portion of the packet stream may include packets for which MPTCP options are not enabled. In some embodiments, partial ROHC may include performing ROHC on packets that do not include MPTCP options and transmitting the MPTCP options as part of a compression list. In some embodiments, the second compression mode may correspond to transmitting a first portion of the packet stream with ROHC and transmitting a second portion of the packet stream with ROHC. In some embodiments, to perform ROHC in the second compression mode, the compressor may first determine that the first portion of the packet stream includes an MPTCP subtype that supports the second compression mode (e.g., subtype 0x02).
[0115] At 1610, the compressor may transmit the chain of compressed data packets.
[0116] At 1618, when the corresponding decompressor does not support MPTCP, the compressor may operate in a third compression mode in which the first portion of the packet stream is not compressed, and the compressor transmits the first portion of the packets without compression. In addition, at 1620, the compressor may perform ROHC on a second portion of the packet stream (e.g., packets without the MPTCP option enabled), and transmit the second portion as compressed packets.
[0117] The embodiments of the present disclosure may be implemented in any of a variety of forms. For example, some embodiments may be implemented as computer-implemented methods, computer-readable storage media, or computer systems. Other embodiments may be implemented using one or more custom-designed hardware devices such as ASICs. Other embodiments may be implemented using one or more programmable hardware elements such as FPGAs.
[0118] In some embodiments, a non-transitory computer-readable storage medium may be configured such that it stores program instructions and / or data, wherein if the program instructions are executed by a computer system, the computer system is caused to perform a method, such as any one of the method embodiments described herein, or any combination of the method embodiments described herein, or any subset of any of the method embodiments described herein or any combination of such subsets.
[0119] In some embodiments, a device (e.g., UE 106) may be configured to include a processor (or a group of processors) and a memory medium, wherein the memory medium stores program instructions, wherein the processor is configured to read and execute program instructions from the memory medium, wherein the program instructions can be executed to implement a method, such as any method implementation in the various method implementations described herein (or any combination of the method implementations described herein, or any subset of any method implementation in the method implementations described herein or any combination of such subsets). The device may be implemented in any of various forms.
[0120] Although the above embodiments have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to encompass all such variations and modifications.
Claims
1. A user equipment device, comprising: at least one antenna, the at least one antenna configured to perform wireless communication; at least one radio coupled to the at least one antenna, wherein the at least one radio is configured to perform cellular communications with a base station; one or more processors coupled to the at least one radio, wherein the one or more processors and the at least one radio are configured to perform wireless communications using the at least one antenna; wherein the one or more processors are configured as a data compressor, wherein the data compressor is configured to: determining that a first portion of a packet stream is formatted according to a transmission control protocol (TCP) with a multipath transmission control protocol (MPTCP) option enabled; When a context established with a corresponding decompressor indicates that the corresponding decompressor supports decompression of TCP packets with MPTCP options enabled, robust header compression (ROHC) is performed on the packet stream, the execution generating a chain of compressed packets, wherein in a first compression mode, the MPTCP options are not compressed, and wherein in a second compression mode, the MPTCP options are compressed.
2. The user equipment device according to claim 1, The data compressor is further configured to transmit the chain of compressed data packets to the corresponding decompressor.
3. The user equipment device according to claim 1, in, When the context indicates that the corresponding decompressor does not support ROHC decompression of the TCP data packet with the MPTCP option enabled, the data compressor is further configured to: transmitting the first portion of the packet stream with the MPTCP option enabled without compression; and A second portion of the packet stream is transmitted without the MPTCP option enabled in case of ROHC.
4. The user equipment device according to claim 3, in, In order to establish the context, the data compressor is further configured to: An error is received, the error indicating that the corresponding decompressor does not support ROHC decompression of the TCP data packet with the MPTCP option enabled.
5. The user equipment device according to claim 1, Wherein in the first compression mode, the data compressor is configured as follows: transmitting the first portion of the packet flow with the MPTCP option enabled with partial ROHC; and A second portion of the packet stream is transmitted without the MPTCP option enabled in case of ROHC.
6. The user equipment device according to claim 5, The ROHC parts include: performing ROHC on packets not including the MPTCP option; as well as The MPTCP options are transmitted as part of a compressed list.
7. The user equipment device according to claim 1, Wherein in the second compression mode, the data compressor is configured as follows: transmitting the first portion of the packet flow with the MPTCP option enabled with ROHC; and A second portion of the packet stream is transmitted without the MPTCP option enabled in case of ROHC.
8. The user equipment device according to claim 1, In order to perform ROHC in the second compression mode, the data compressor is further configured as follows: Determining that a first portion of the packet flow includes an MPTCP subtype that supports the second compression mode, wherein the MPTCP subtype includes subtype 0x02.
9. The user equipment device according to claim 1, The data compressor is further configured as follows: Maintain a table of (index, entry) pairs for TCP options included in headers of the packet flow, where the MPTCP option corresponds to table index 7.
10. A compressor comprising: Memory; as well as a processing element in communication with the memory, wherein the processing element is configured to: identifying a first portion of a packet stream formatted according to a transmission control protocol (TCP) with a multipath transmission control protocol (MPTCP) option enabled; A header of the packet stream is compressed based at least in part on the packet stream being formatted according to the MPTCP protocol, the compression generating a compressed packet chain, wherein in a first compression mode, the MPTCP options are not compressed, and wherein in a second compression mode, the MPTCP options are compressed.
11. The compressor according to claim 10, The processing element is further configured to: receiving feedback from a corresponding decompressor, the feedback indicating that the corresponding decompressor does not support decompression of packets formatted according to the MPTCP protocol; generating instructions to transmit a first portion of the packet stream with the MPTCP option enabled without compression; and A second portion of the packet stream without the MPTCP option enabled is transmitted with compression.
12. The compressor according to claim 10, The processing element is further configured to: generating instructions to transmit a partially compressed header, wherein the partially compressed header does not include compression of the MPTCP option; and An indication is received from a corresponding decompressor that the corresponding decompressor supports decompression of the MPTCP option.
13. The compressor according to claim 10, The data packet stream includes MPTCP subtype 0x02 packets.
14. The compressor according to claim 10, The processing element is further configured to: A table of (index, item) pairs for TCP options included in headers of the packet flow is maintained.
15. The compressor according to claim 14, The MPTCP option corresponds to table index 7.
16. A non-transitory computer-readable storage medium storing program instructions executable by a processing circuit of a user equipment device (UE) to: After establishing a context with a corresponding decompressor, generating instructions to transmit a data transmission to the corresponding decompressor in a Multipath Transmission Control Protocol (MPTCP) Robust Header Compression (ROHC) secure compression mode, including compressing a data packet in a first format, wherein the first format corresponds to a data packet formatted according to a Transmission Control Protocol (TCP) without an MPTCP option enabled; and Converting the data transmission to MPTCP ROHC full compression mode includes compressing the data packets in the first format.
17. The non-transitory computer readable storage medium of claim 16, Wherein, for transmission in the MPTCP ROHC secure compression mode, the program instructions can be further executed to: A data packet in a second format is partially compressed, wherein the second format corresponds to a data packet formatted according to TCP with the MPTCP option enabled.
18. The non-transitory computer readable storage medium of claim 16, Wherein, for transmission in the MPTCP ROHC full compression mode, the program instructions are further executable to: Compressing data packets in a second format, wherein the second format corresponds to data packets formatted according to TCP with the MPTCP option enabled.
19. The non-transitory computer readable storage medium of claim 16, Wherein, in order to convert the data transmission to the MPTCP ROHC full compression mode, the program instructions are further executable to: Determine that a data packet formatted according to the Transmission Control Protocol (TCP) with the MPTCP option enabled is a subtype 0x02 MPTCP data packet.
20. The non-transitory computer readable storage medium of claim 16, Wherein, when the context indicates that the corresponding decompressor does not support ROHC decompression of TCP packets with the MPTCP option enabled, the program instructions are further configured to: generating instructions to transmit a first portion of the data packet with the MPTCP option enabled without compression; and Instructions are generated to transmit a second portion of the data packet without the MPTCP option enabled in the case of ROHC.
Citation Information
Patent Citations
Multipath Data Stream Optimization
CN106464582A
Data Transfer using a multipath TCP Connection
GB201407227D0
Method for concurrent bandwidth aggregation using a second path on a second wireless network that utilizes the packet core network of a first path on a first wireless network
US20120236801A1
Multipath transport tunnel over multiple air interfaces connecting wireless stations
US20130064198A1
Method and system for handling audio packets during a volte call
US20150124699A1
