WO2013061115A1 - Procédé et appareil pour prendre en charge l'utilisation d'un protocole de transport multi-chemin - Google Patents

Procédé et appareil pour prendre en charge l'utilisation d'un protocole de transport multi-chemin Download PDF

Info

Publication number
WO2013061115A1
WO2013061115A1 PCT/IB2011/054807 IB2011054807W WO2013061115A1 WO 2013061115 A1 WO2013061115 A1 WO 2013061115A1 IB 2011054807 W IB2011054807 W IB 2011054807W WO 2013061115 A1 WO2013061115 A1 WO 2013061115A1
Authority
WO
WIPO (PCT)
Prior art keywords
multipath
network access
open
subflow
network
Prior art date
Application number
PCT/IB2011/054807
Other languages
English (en)
Inventor
Jukka Pekka REUNAMÄKI
Niko Tapani Kiukkonen
Janne Marin
Sverre Slotte
Original Assignee
Nokia Corporation
Nokia, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Corporation, Nokia, Inc. filed Critical Nokia Corporation
Priority to PCT/IB2011/054807 priority Critical patent/WO2013061115A1/fr
Publication of WO2013061115A1 publication Critical patent/WO2013061115A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/14—Multichannel or multilink protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/02—Standardisation; Integration
    • H04L41/0233—Object-oriented techniques, for representation of network management data, e.g. common object request broker architecture [CORBA]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/326—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the transport layer [OSI layer 4]

Definitions

  • communications technology and, more particularly, relate to a method and apparatus for supporting usage of a multipath transport protocol.
  • mobile computing devices have the capability to access a network via multiple network access technologies.
  • mobile computing devices may have multiple network access interfaces, such as a cellular network interface, Wireless Local Area Network (WLAN) interface, Bluetooth interface, and/or the like, which may be used to connect to a network when a compatible network access is available.
  • Some such mobile computing devices may connect to a network via multiple network access technologies concurrently.
  • Concurrent connections to a network via multiple network access technologies may provide flexibility in data transfer that may be used to improve access to network services for a mobile computing device.
  • benefits of using multiple network access technologies concurrently have not yet been fully leveraged, and work in this area is ongoing.
  • a system, method, and apparatus are herein provided for supporting usage of a multipath transport protocol.
  • Systems, methods, and apparatuses in accordance with various embodiments may provide several advantages to computing devices, computing device users, network operators, service providers, and consumers.
  • some example embodiments provide a network management entity configured to send a message to a network-connected apparatus that includes configuration information for usage of a multipath transport protocol.
  • a network-connected apparatus may in accordance with some example embodiments may be configured to determine one or more configuration settings for usage of the multipath transport protocol based at least in part on configuration information that may be included in a received message from a network management entity.
  • the network-connected apparatus of some example embodiments may use the determined configuration settings to control usage of multipath subflows for communicating with a device over the network.
  • some example embodiments provide for network operator control over when and how multipath transport protocol should be used by a network-connected apparatus.
  • some example embodiments provide for network-controlled configuration of a network-connected apparatus by providing a message to the network- connected apparatus indicating whether opening of a multipath subflow is permitted, mandatory, or prohibited in various circumstances.
  • the network operator may accordingly, through the network management entity of some example embodiments, control usage of multipath transport protocol by a network-connected apparatus to provide a desired (for example, guaranteed) quality of service level, provide flexibility to the network-connected apparatus to open a multipath subflow when available to provide additional bandwidth for communication with another device, and/or manage bandwidth usage on the network by encouraging opening of multipath subflows on alternative network accesses.
  • a method may comprise receiving, at an apparatus, a message comprising configuration information for usage of a multipath transport protocol sent by a network management entity.
  • the method of this example embodiment may further comprise determining one or more configuration settings for usage of the multipath transport protocol based at least in part on the configuration information in the received message.
  • the method of this example embodiment may also comprise determining whether to use the multipath transport protocol to open a multipath subflow over a network access for communicating with a second device based at least in part on the determined configuration settings.
  • an apparatus comprising at least one processor and at least one memory storing computer program code.
  • the at least one memory and stored computer program code may be configured, with the at least one processor, to cause the apparatus of this example embodiment to at least perform receiving a message comprising configuration information for usage of a multipath transport protocol sent by a network management entity.
  • the at least one memory and stored computer program code may be configured, with the at least one processor, to further cause the apparatus of this example embodiment to perform determining one or more configuration settings for usage of the multipath transport protocol based at least in part on the configuration information in the received message.
  • the at least one memory and stored computer program code may be configured, with the at least one processor, to also cause the apparatus of this example embodiment to perform determining whether to use the multipath transport protocol to open a multipath subflow over a network access for communicating with a second device based at least in part on the determined configuration settings.
  • an apparatus may comprise means for receiving a message comprising configuration information for usage of a multipath transport protocol sent by a network management entity.
  • the apparatus of this example embodiment may further comprise means for determining one or more configuration settings for usage of the multipath transport protocol based at least in part on the configuration information in the received message.
  • the apparatus of this example embodiment may also comprise means for determining whether to use the multipath transport protocol to open a multipath subflow over a network access for communicating with a second device based at least in part on the determined configuration settings.
  • FIG. 1 illustrates a system for supporting usage of a multipath transport protocol according to some example embodiments
  • FIG. 2 is a schematic block diagram of a mobile terminal according to some example embodiments.
  • FIG. 3 illustrates a block diagram of an apparatus for supporting usage of a multipath transport protocol according to some example embodiments
  • FIG. 4 illustrates a block diagram of a network management apparatus according to some example embodiments
  • FIG. 5 illustrates a portion of an Access Network Discovery and Selection
  • FIG. 6 illustrates an extension of the Access Network Discovery and Selection Function management object of FIG. 5 according to some example embodiments.
  • FIG. 7 illustrates a flowchart according to an example method for supporting usage of a multipath transport protocol according to some example embodiments.
  • the terms "data,” “content,” “information” and similar terms may be used interchangeably to refer to data capable of being transmitted, received, displayed and/or stored in accordance with various example embodiments. Thus, use of any such terms should not be taken to limit the spirit and scope of the disclosure.
  • a computing device is described herein to receive data from another computing device, it will be appreciated that the data may be received directly from the another computing device or may be received indirectly via one or more intermediary computing devices, such as, for example, one or more servers, relays, routers, network access points, base stations, and/or the like.
  • the term "computer-readable medium” as used herein refers to any medium configured to participate in providing information to a processor, including instructions for execution.
  • Such a medium may take many forms, including, but not limited to a non- transitory computer-readable storage medium (for example, non-volatile media, volatile media), and transmission media.
  • Transmission media include, for example, coaxial cables, copper wire, fiber optic cables, and carrier waves that travel through space without wires or cables, such as acoustic waves and electromagnetic waves, including radio, optical and infrared waves.
  • non-transitory computer-readable media examples include a floppy disk, hard disk, magnetic tape, any other non-transitory magnetic medium, a compact disc read only memory (CD-ROM), compact disc compact discrewritable (CD-RW), digital versatile disc (DVD), Blu-Ray, any other non-transitory optical medium, a random access memory (RAM), a programmable read only memory (PROM), an erasable programmable read only memory (EPROM), a FLASH-EPROM, any other memory chip or cartridge, or any other non-transitory medium from which a computer can read.
  • the term computer-readable storage medium is used herein to refer to any computer-readable medium except transmission media. However, it will be appreciated that where embodiments are described to use a computer-readable storage medium, other types of computer-readable mediums may be substituted for or used in addition to the computer-readable storage medium in alternative embodiments.
  • circuitry refers to (a) hardware-only circuit implementations (for example, implementations in analog circuitry and/or digital circuitry); (b) combinations of circuits and computer program product(s) comprising software and/or firmware instructions stored on one or more computer readable memories that work together to cause an apparatus to perform one or more functions described herein; and (c) circuits, such as, for example, a microprocessor(s) or a portion of a microprocessor(s), that require software or firmware for operation even if the software or firmware is not physically present.
  • This definition of 'circuitry' applies to all uses of this term herein, including in any claims.
  • the term 'circuitry' also includes an implementation comprising one or more processors and/or portion(s) thereof and accompanying software and/or firmware.
  • the term 'circuitry' as used herein also includes, for example, a baseband integrated circuit or applications processor integrated circuit for a mobile phone or a similar integrated circuit in a server, a cellular network device, other network device, and/or other computing device.
  • FIG. 1 illustrates a diagram of a system 100 for supporting usage of a multipath transport protocol according to some example embodiments.
  • the system 100 as well as the illustrations in other figures are each provided as an example of some embodiments and should not be construed to narrow the scope or spirit of the disclosure in any way.
  • the scope of the disclosure encompasses many potential embodiments in addition to those illustrated and described herein.
  • FIG. 1 illustrates one example of a configuration of a system for supporting usage of a multipath transport protocol, numerous other configurations may also be used to implement embodiments of the present invention.
  • the system 100 may include an apparatus 102.
  • the apparatus may comprise any computing device configured to connect to a network, such as the network 104, via one or more network accesses (for example, the first network access 106, second network access 108, and/or the like).
  • the apparatus 102 may be embodied as a computer, laptop computer, mobile terminal, mobile computer, mobile phone, mobile communication device, tablet computing device, game device, digital camera/camcorder, audio/video player, television device, radio receiver, digital video recorder, positioning device, wrist watch, portable digital assistant (PDA), a chipset, an apparatus comprising a chipset, any combination thereof, and/or the like.
  • PDA portable digital assistant
  • the apparatus 102 may be embodied as a mobile terminal, such as that illustrated in FIG. 2. It should be understood, however, that the mobile terminal 10 illustrated and hereinafter described is merely illustrative of one type of computing device that may implement and/or benefit from various embodiments and, therefore, should not be taken to limit the scope of the disclosure. While several embodiments of the electronic device are illustrated and will be hereinafter described for purposes of example, other types of electronic devices, such as mobile telephones, mobile computers, portable digital assistants (PDAs), pagers, laptop computers, desktop computers, gaming devices, televisions, and other types of electronic systems, may employ various embodiments of the invention.
  • PDAs portable digital assistants
  • the mobile terminal 10 may include an antenna 12 (or multiple antennas 12) in communication with a transmitter 14 and a receiver 16.
  • the mobile terminal 10 may also include a processor 20 configured to provide signals to and receive signals from the transmitter and receiver, respectively.
  • the processor 20 may, for example, be embodied as various means including circuitry, one or more
  • These signals sent and received by the processor 20 may include signaling information in accordance with an air interface standard of an applicable cellular system, and/or any number of different wireline or wireless networking techniques, comprising but not limited to Wi-Fi, wireless local access network (WLAN) techniques such as Institute of Electrical and Electronics Engineers (IEEE) 802.1 1 , 802.16, and/or the like.
  • these signals may include speech data, user generated data, user requested data, and/or the like.
  • the mobile terminal may be capable of operating with one or more air interface standards, communication protocols, modulation types, access types, and/or the like.
  • the mobile terminal may be capable of operating in accordance with various first generation (1 G), second generation (2G), 2.5G, third-generation (3G) communication protocols, fourth-generation (4G) communication protocols, Internet Protocol Multimedia Subsystem (IMS) communication protocols (for example, session initiation protocol (SIP)), and/or the like.
  • first generation (1 G) second generation (2G), 2.5G
  • third-generation (3G) communication protocols fourth-generation (4G) communication protocols
  • IMS Internet Protocol Multimedia Subsystem
  • SIP session initiation protocol
  • the mobile terminal may be capable of operating in accordance with 2G wireless
  • the mobile terminal may be capable of operating in accordance with 2.5G wireless communication protocols General Packet Radio Service (GPRS), Enhanced Data GSM Environment (EDGE), and/or the like.
  • GPRS General Packet Radio Service
  • EDGE Enhanced Data GSM Environment
  • 3G wireless communication protocols such as Universal Mobile Telecommunications System (UMTS), Code Division Multiple Access 2000 (CDMA2000), Wideband Code Division Multiple Access (WCDMA), Time Division-Synchronous Code Division Multiple Access (TD-SCDMA), and/or the like.
  • the mobile terminal may be additionally capable of operating in accordance with 3.9G wireless communication protocols such as Long Term Evolution (LTE) or Evolved Universal Terrestrial Radio Access Network (E-UTRAN) and/or the like. Additionally, for example, the mobile terminal may be capable of operating in accordance with fourth-generation (4G) wireless communication protocols and/or the like as well as similar wireless communication protocols that may be developed in the future.
  • LTE Long Term Evolution
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • NAMPS Narrow-band Advanced Mobile Phone System
  • TACS Total Access Communication System
  • the mobile terminal 10 may be capable of operating according to Wi-Fi or Worldwide Interoperability for Microwave Access (WiMAX) protocols.
  • the processor 20 may comprise circuitry for implementing audio/video and logic functions of the mobile terminal 10.
  • the processor 20 may comprise a digital signal processor device, a microprocessor device, an analog-to- digital converter, a digital-to-analog converter, and/or the like. Control and signal processing functions of the mobile terminal may be allocated between these devices according to their respective capabilities.
  • the processor may additionally comprise an internal voice coder (VC) 20a, an internal data modem (DM) 20b, and/or the like. Further, the processor may comprise functionality to operate one or more software programs, which may be stored in memory.
  • the processor 20 may be capable of operating a connectivity program, such as a web browser.
  • the connectivity program may allow the mobile terminal 10 to transmit and receive web content, such as location-based content, according to a protocol, such as Wireless Application Protocol (WAP), hypertext transfer protocol (HTTP), and/or the like.
  • WAP Wireless Application Protocol
  • HTTP hypertext transfer protocol
  • the mobile terminal 10 may be capable of using Transmission Control Protocol/Internet Protocol (TCP/IP) to transmit and receive web content across the internet or other networks.
  • TCP/IP Transmission Control Protocol/Internet Protocol
  • the mobile terminal 10 may also comprise a user interface including, for example, an earphone or speaker 24, a ringer 22, a microphone 26, a display 28, a user input interface, and/or the like, which may be operationally coupled to the processor 20.
  • the processor 20 may comprise user interface circuitry configured to control at least some functions of one or more elements of the user interface, such as, for example, the speaker 24, the ringer 22, the microphone 26, the display 28, and/or the like.
  • the processor 20 and/or user interface circuitry comprising the processor 20 may be configured to control one or more functions of one or more elements of the user interface through computer program instructions (for example, software and/or firmware) stored on a memory accessible to the processor 20 (for example, volatile memory 40, non-volatile memory 42, and/or the like).
  • the mobile terminal may comprise a battery for powering various circuits related to the mobile terminal, for example, a circuit to provide mechanical vibration as a detectable output.
  • the user input interface may comprise devices allowing the mobile terminal to receive data, such as a keypad 30, a touch display, a joystick, and/or other input device. In embodiments including a keypad, the keypad may comprise numeric (0-9) and related keys (#, * ), and/or other keys for operating the mobile terminal.
  • the mobile terminal 10 may also include one or more means for sharing and/or obtaining data.
  • the mobile terminal may comprise a short-range radio frequency (RF) transceiver and/or interrogator 64 so data may be shared with and/or obtained from electronic devices in accordance with RF techniques.
  • the mobile terminal may comprise other short-range transceivers, such as, for example, an infrared (IR) transceiver 66, a BluetoothTM (BT) transceiver 68 operating using BluetoothTM brand wireless technology developed by the BluetoothTM Special Interest Group, a wireless universal serial bus (USB) transceiver 70 and/or the like.
  • IR infrared
  • BT BluetoothTM
  • USB wireless universal serial bus
  • BluetoothTM transceiver 68 may be capable of operating according to BluetoothTM low energy technology .
  • the mobile terminal 10 and, in particular, the short- range transceiver may be capable of transmitting data to and/or receiving data from electronic devices within a proximity of the mobile terminal, such as within 10 meters, for example.
  • the mobile terminal may be capable of transmitting and/or receiving data from electronic devices according to various wireless networking techniques, including Wi-Fi, WLAN techniques such as IEEE 802.1 1 techniques, IEEE 802.15 techniques, IEEE 802.16 techniques, and/or the like.
  • the mobile terminal 10 may comprise memory, such as a removable or nonremovable subscriber identity module (SIM) 38, a soft SIM 38, a fixed SIM 38, a removable or non-removable universal subscriber identity module (USIM) 38, a soft USIM 38, a fixed USIM 38, a removable user identity module (R-UIM), and/or the like, which may store information elements related to a mobile subscriber.
  • SIM subscriber identity module
  • USIM universal subscriber identity module
  • R-UIM removable user identity module
  • the mobile terminal 10 may include volatile memory 40 and/or non-volatile memory 42.
  • volatile memory 40 may include Random Access Memory (RAM) including dynamic and/or static RAM, on-chip or off-chip cache memory, and/or the like.
  • RAM Random Access Memory
  • Non-volatile memory 42 which may be embedded and/or removable, may include, for example, readonly memory, flash memory, magnetic storage devices (for example, hard disks, floppy disk drives, magnetic tape, etc.), optical disc drives and/or media, non-volatile random access memory (NVRAM), and/or the like. Like volatile memory 40, non-volatile memory 42 may also include a cache area for temporary storage of data.
  • the memories may store one or more software programs, instructions, pieces of information, data, and/or the like which may be used by the mobile terminal for performing functions of the mobile terminal.
  • the memories may comprise an identifier, such as an international mobile equipment identification (IMEI) code, capable of uniquely identifying the mobile terminal 10.
  • IMEI international mobile equipment identification
  • the network 104 may comprise any network or combination of a plurality of networks by which computing devices may communicate.
  • the network 104 may comprise one or more wireless networks (for example, a cellular network, a structured wireless local area network, wireless metropolitan area network, and/or the like), one or more wireline networks, or some combination thereof, and in some embodiments may comprise at least a portion of the internet.
  • the network 104 may be accessed by multiple network access technologies, which are interchangeably referred to herein as "network accesses.” Two such network accesses - the first network access 106 and the second network access 108 - are illustrated in FIG. 1 by way of example.
  • the system 100 may comprise one or more additional network accesses, with which, depending on configuration, the apparatus 102 may be configured to interface to access the network 104.
  • a network access may provide network access via any respective network access technology, such as a cellular access technology (for example, Long Term Evolution cellular access technology, Long Term Evolution Advanced cellular access technology, Global Systems for Mobile
  • Wireless Local Area Network Wireless Local Area Network
  • IEEE Institute of Electrical and Electronics Engineers
  • WMAN Wireless Metropolitan Area Network
  • IEEE 802.16 any network access implementing a version of the IEEE 802.16 standard
  • Bluetooth any network access implementing a version of the IEEE 802.16 standard
  • ZigBee any Wireless Personal Area Networking (WPAN) technology
  • wired network access for example, Ethernet access
  • a network access in accordance with some example embodiments may include an access point, such as a wireless access point that the apparatus 102 may connect to using an appropriate network access technology.
  • an access point that may provide a network access such as the first network access 106, second network access 108, and/or the like may comprise a cellular base station, NodeB, Evolved Node B(eNB), a router, wireless router, satellite transceiver, and/or the like.
  • the system 100 may further comprise a network device 1 10.
  • the network device 1 10 may comprise any computing device with which the apparatus 102 may
  • the network device 1 10 may be embodied as one or more servers, a server cluster, a cloud computing infrastructure, one or more desktop computers, one or more laptop computers, one or more network nodes, multiple computing devices in communication with each other, a mobile terminal, a mobile computer, a mobile phone, a mobile communication device, a tablet computing device, a game device, a digital camera/camcorder, an audio/video player, a television device, a radio receiver, a digital video recorder, a positioning device, a wrist watch, a portable digital assistant (PDA), some combination thereof, and/or the like.
  • PDA portable digital assistant
  • the system 100 may additionally comprise a network management entity 1 12.
  • the network management entity 1 12 may be embodied as any computing device or plurality of computing devices that is configured to provide configuration information governing communication via and/or usage of the network 104, one or more network accesses (for example, the first network access 106, second network access 108, and/or the like), and/or the like by the apparatus 102.
  • the network management entity 1 12 may be configured to provide configuration information for usage of a multipath transport protocol to the apparatus 102, as described further herein below.
  • the network management 1 12 entity may be embodied as one or more servers, a server cluster, a cloud computing infrastructure, one or more desktop computers, one or more laptop computers, one or more network nodes, multiple computing devices in
  • the network management entity 1 12 may comprise as an Access Network Discovery and Selection Function (ANDSF).
  • ANDSF Access Network Discovery and Selection Function
  • the ANDSF may, for example, comprise an entity within an Evolved Packet Core (EPC) of the System Architecture Evolution (SAE) for a Third Generation
  • EPC Evolved Packet Core
  • SAE System Architecture Evolution
  • a portion of the network 104 and/or one or more network accesses for the network 104 may comprise a 3GPP-compliant mobile network.
  • the network management entity 1 12 comprises an ANDSF
  • the ANDSF may provide data
  • the ANDSF may be configured to respond to requests from the apparatus 102 for access network discovery information (pull mode operation).
  • the ANDSF may be configured to initiate data transfer to the apparatus 102 (push mode operation), such as based on network triggers or as a result of previous communication with the apparatus 102 (for example, in response to a request by the apparatus 102).
  • the network management entity 1 12 may be configured to manage intersystem mobility policy as well as access network discovery information that may be stored in an apparatus 102.
  • the network management 1 12 may be configured to provide management of and/or support for IP Flow Mobility (IFOM), Multi Access PDN Connectivity (MAPCON) and non-seamless WLAN offload.
  • IFOM IP Flow Mobility
  • MAPCON Multi Access PDN Connectivity
  • non-seamless WLAN offload In some example embodiments wherein the network management entity 1 12 is configured to support IFOM, the first network access 106 may comprise a 3GPP cellular network access, and the second network access 108 may comprise a WLAN access.
  • IFOM may specify a mechanism for the apparatus 102 of some example embodiments to simultaneously connect to the 3GPP access and WLAN and exchange different Internet Protocol (IP) flows belonging to the same Packet Data Network (PDN) connection through different accesses.
  • IP Internet Protocol
  • IFOM support may be based on Dual Stack Mobile IP Version 6 (DSMIPv6), and may enable seamless IP flow mobility.
  • seamless IP flow mobility may allow IP flows belonging to the same or different applications to be moved seamlessly between a 3GPP access and
  • IFOM in accordance with some example embodiments may provide a finer granularity in access system connectivity and inter system mobility in that the handover procedures may be applied to a single or multiple IP flows belonging to the same PDN connection.
  • some IP flows of one PDN connection may be routed via one access system (for example, the first network access 106) while simultaneously some IP flows of the same PDN connection may be routed via another access system (for example, the second network access 108).
  • the system 100 may additionally or alternatively support non-seamless WLAN offload.
  • the apparatus 102 may, while connected to WLAN access (for example, the second network access 108), route specific IP flows via the WLAN access without traversing the EPC.
  • These offloaded IP flows may be identified via policies that may be statically pre- configured by the operator on the apparatus 102, dynamically set by the operator via the network management entity 1 12, via user preferences, and/or the like.
  • the apparatus 102 may use the local IP address allocated by the WLAN access network for the non- seamlessly offloaded IP flows, and, as such, IP address preservation between WLAN and 3GPP accesses may not be provided.
  • the apparatus 102 may acquire a local IP address on the WLAN access (for example, the second network access 108), but may not be required to connect to an evolved Packet Data Gateway (ePDG).
  • ePDG evolved Packet Data Gateway
  • an apparatus 102 supporting both seamless and non-seamless WLAN offload to perform seamless WLAN offload for some IP flows and non-seamless WLAN offload for some other IP flows (for example, simultaneously).
  • multiple paths may exist for a connection between the apparatus 102 and a peer, such as the network device 1 10.
  • a peer such as the network device 1 10.
  • the apparatus 102 may be configured to use a multipath transport protocol to communicate with the network device 1 10 via a plurality of concurrent multipath subflows distributed over the paths.
  • a first multipath subflow may exist between the apparatus 102 and network device 1 10 via the first network access 106
  • a second multipath subflow may exist between the apparatus 102 and network device 1 10 via the second network access 108.
  • Usage of multiple paths for a session between the apparatus 102 and network device 1 10 may improve resource usage within the network 104, and thus may improve user experience through higher throughput and improved resilience to network failure.
  • the multipath transport protocol may comprise multipath transmission control protocol (MPTCP).
  • the network management entity 1 12 of some example embodiments may be configured to provision the apparatus 102 with a configuration for using a multipath transport protocol. Accordingly, some example embodiments may enable a network operator to support and control usage of multipath transport protocol by a network- connected apparatus, such as the apparatus 102. Having generally described features of the system 100, several examples of such embodiments wherein the network
  • management entity 1 12 is configured to provision the apparatus 102 with a configuration to support usage of a multipath transport protocol will now be described.
  • FIG. 3 illustrates a block diagram of an apparatus 302 for supporting usage of a multipath transport protocol according to some example
  • the apparatus 302 may comprise an apparatus that may be implemented on the apparatus 102.
  • the apparatus 302 may include various means for performing the various functions herein described. These means may comprise one or more of a processor 310, memory 312, communication interface 314, user interface 316, or multipath control module 318.
  • the means of the apparatus 302 as described herein may be embodied as, for example, circuitry, hardware elements (for example, a suitably programmed processor, combinational logic circuit, and/or the like), a computer program product comprising a computer-readable medium (for example memory 312) storing computer-readable program instructions (for example, software or firmware) that are executable by a suitably configured processing device (for example, the processor 310), or some combination thereof.
  • a suitably programmed processor, combinational logic circuit, and/or the like a computer program product comprising a computer-readable medium (for example memory 312) storing computer-readable program instructions (for example, software or firmware) that are executable by a suitably configured processing device (for example, the processor 310), or some combination thereof.
  • one or more of the means illustrated in FIG. 3 may be embodied as a chip or chip set.
  • the apparatus 302 may comprise one or more physical packages (for example, chips) including materials, components and/or wires on a structural assembly (for example, a baseboard).
  • the structural assembly may provide physical strength, conservation of size, and/or limitation of electrical interaction for component circuitry included thereon.
  • the processor 310, memory 312, communication interface 314, user interface 316, and/or multipath control module 318 may be embodied as a chip or chip set.
  • the apparatus 302 may therefore, in some example embodiments, be configured to implement example embodiments on a single chip or as a single "system on a chip.” As another example, in some example embodiments, the apparatus 302 may comprise component(s) configured to implement embodiments of the present invention on a single chip or as a single
  • a chip or chipset may constitute means for performing one or more operations for providing the functionalities described herein and/or for enabling user interface navigation with respect to the functionalities and/or services described herein.
  • the processor 310 may, for example, be embodied as various means including one or more microprocessors with accompanying digital signal processor(s), one or more processor(s) without an accompanying digital signal processor, one or more
  • processors may comprise a plurality of processors.
  • the plurality of processors may be in operative communication with each other and may be collectively configured to perform one or more functionalities of the apparatus 302 as described herein.
  • the plurality of processors may be embodied on a single computing device or distributed across a plurality of computing devices collectively configured to function as the apparatus 302.
  • the processor 310 may be embodied as or may comprise the processor 20.
  • the processor 310 may be configured to execute instructions stored in the memory 312 or otherwise accessible to the processor 310. These instructions, when executed by the processor 310, may cause the apparatus 302 to perform one or more of the functionalities of the apparatus 302 as described herein.
  • the processor 310 may comprise an entity capable of performing operations according to embodiments of the present invention while configured accordingly.
  • the processor 310 when the processor 310 is embodied as an ASIC, FPGA or the like, the processor 310 may comprise specifically configured hardware for conducting one or more operations described herein.
  • the processor 310 is embodied as an executor of instructions, such as may be stored in the memory 312, the instructions may specifically configure the processor 310 to perform one or more algorithms and operations described herein.
  • the memory 312 may comprise, for example, volatile memory, non-volatile memory, or some combination thereof.
  • the memory 312 may comprise a non-transitory computer-readable storage medium.
  • the memory 312 may comprise a plurality of memories.
  • the plurality of memories may be embodied on a single computing device or may be distributed across a plurality of computing devices collectively configured to function as the apparatus 302.
  • the memory 312 may comprise a hard disk, random access memory, cache memory, flash memory, a compact disc read only memory (CD- ROM), digital versatile disc read only memory (DVD-ROM), an optical disc, circuitry configured to store information, or some combination thereof.
  • the memory 312 may comprise the volatile memory 40 and/or the non-volatile memory 42.
  • the memory 312 may be configured to store information, data, applications, instructions, or the like for enabling the apparatus 302 to carry out various functions in accordance with various example embodiments.
  • the memory 312 may be configured to buffer input data for processing by the processor 310.
  • the memory 312 may be configured to store program instructions for execution by the processor 310.
  • the memory 312 may store information in the form of static and/or dynamic information. This stored information may be stored and/or used by the multipath control module 318 during the course of performing its functionalities.
  • the communication interface 314 may be embodied as any device or means embodied in circuitry, hardware, a computer program product comprising a computer- readable medium (for example memory 312) storing computer-readable program instructions (for example, software or firmware) that are executable by a suitably configured processing device (for example, the processor 310), or a combination thereof that is configured to receive and/or transmit data from/to another computing device.
  • the communication interface 314 may be at least partially embodied as or otherwise controlled by the processor 310.
  • the communication interface 314 may be in communication with the processor 310, such as via a bus.
  • the communication interface 314 may additionally be in communication with the memory 312, user interface 316, and/or multipath control module 318, such as via a bus.
  • the communication interface 314 may include, for example, an antenna, a transmitter, a receiver, a transceiver and/or supporting hardware or software for enabling communications with one or more computing devices.
  • the communication interface 314 may be configured to receive and/or transmit data using any protocol that may be used for communications between computing devices.
  • the communication interface 314 may be configured to receive and/or transmit data using any protocol that may be used for transmission of data over a wireless network, wireline network, some combination thereof, or the like by which the apparatus 302 and one or more computing devices or computing resources may be in communication.
  • the communication interface 314 may comprise and/or may be in operative communication with a plurality of network access interfaces 315. Two such network access interfaces 315 are illustrated by way of example in FIG. 3. However, it will be appreciated that in some example embodiments, the apparatus 302 may include three or more network access interfaces 315.
  • a network access interface 315 may be embodied as various means, such as circuitry, hardware, a computer program product comprising a computer-readable medium (for example memory 312) storing computer-readable program instructions (for example, software or firmware) that are executable by a suitably configured processing device (for example, the processor 310), or some combination thereof and, in some example embodiments, may be embodied as or otherwise controlled by the processor 310.
  • a network access interface 315 may be configured to facilitate connection to a network (for example, the network 304) via a network access (for example, the first network access 106, second network access 108, and/or the like) so that the apparatus 302 may communicate with one or more devices (for example, the network device 1 10, network management entity 1 12, and/or the like) over the network.
  • a network access interface 315 may be configured to support a particular network access technology for accessing a network.
  • the apparatus 102 may include a network access interface 315 configured to facilitate connection to a cellular network access, a network access interface 315 configured to facilitate connection to a WLAN network access, a network access interface 315 configured to facilitate connection to a Bluetooth network access, and/or the like.
  • the user interface 316 may be in communication with the processor 310 to receive an indication of a user input and/or to provide an audible, visual, mechanical, or other output to a user.
  • the user interface 316 may include, for example, a keyboard, a mouse, a joystick, a display, a touch screen display, a microphone, a speaker, and/or other input/output mechanisms.
  • the user interface 316 may additionally be configured to detect and/or receive an indication of a touch gesture or other input to the touch screen display.
  • the user interface 316 may be in communication with the memory 312, communication interface 314, and/or multipath control module 318, such as via a bus.
  • the multipath control module 318 may be embodied as various means, such as circuitry, hardware, a computer program product comprising a computer-readable medium (for example memory 312) storing computer-readable program instructions (for example, software or firmware) that are executable by a suitably configured processing device (for example, the processor 310), or some combination thereof and, in some example embodiments, may be embodied as or otherwise controlled by the processor 310.
  • the multipath control module 318 may be in communication with the processor 310.
  • the multipath control module 318 may further be in communication with one or more of the memory 312, communication interface 314, or user interface 316, such as via a bus.
  • FIG. 4 illustrates a block diagram of a network
  • the network management apparatus 402 may include various means for performing the various functions herein described. These means may comprise one or more of a processor 410, memory 412, communication interface 414, or multipath configuration module 418.
  • the means of the network management apparatus 402 as described herein may be embodied as, for example, circuitry, hardware elements (for example, a suitably programmed processor, combinational logic circuit, and/or the like), a computer program product comprising a computer-readable medium (for example memory 412) storing computer-readable program instructions (for example, software or firmware) that are executable by a suitably configured processing device (for example, the processor 410), or some combination thereof.
  • one or more of the means illustrated in FIG. 4 may be embodied as a chip or chip set.
  • the network management apparatus 402 may comprise one or more physical packages (for example, chips) including materials, components and/or wires on a structural assembly (for example, a baseboard).
  • the structural assembly may provide physical strength, conservation of size, and/or limitation of electrical interaction for component circuitry included thereon.
  • the processor 410, memory 412, communication interface 414, and/or multipath configuration module 418 may be embodied as a chip or chip set.
  • the network management apparatus 402 may therefore, in some example embodiments, be configured to implement one or more embodiments on a single chip or as a single "system on a chip.”
  • the network management apparatus 402 may comprise component(s) configured to implement embodiments of the present invention on a single chip or as a single "system on a chip.”
  • a chip or chipset may constitute means for performing one or more operations for providing the functionalities described herein and/or for enabling user interface navigation with respect to the functionalities and/or services described herein.
  • the processor 410 may, for example, be embodied as various means including one or more microprocessors with accompanying digital signal processor(s), one or more processor(s) without an accompanying digital signal processor, one or more
  • the processor 410 may comprise a plurality of processors.
  • the plurality of processors may be in operative communication with each other and may be collectively configured to perform one or more functionalities of the network management apparatus 402 as described herein.
  • the plurality of processors may be embodied on a single computing device or distributed across a plurality of computing devices collectively configured to function as the network management apparatus 402.
  • the processor 410 may be configured to execute instructions stored in the memory 412 or otherwise accessible to the processor 410. These instructions, when executed by the processor 410, may cause the network management apparatus 402 to perform one or more of the functionalities of the network management apparatus 402 as described herein. As such, whether configured by hardware or software methods, or by a combination thereof, the processor 410 may comprise an entity capable of performing operations according to embodiments of the present invention while configured accordingly. Thus, for example, when the processor 410 is embodied as an ASIC, FPGA or the like, the processor 410 may comprise specifically configured hardware for conducting one or more operations described herein. Alternatively, as another example, when the processor 410 is embodied as an executor of instructions, such as may be stored in the memory 412, the instructions may specifically configure the processor 410 to perform one or more algorithms and operations described herein.
  • the memory 412 may comprise, for example, volatile memory, non-volatile memory, or some combination thereof.
  • the memory 412 may comprise a non-transitory computer-readable storage medium.
  • the memory 412 may comprise a plurality of memories.
  • the plurality of memories may be embodied on a single computing device or may be distributed across a plurality of computing devices collectively configured to function as the network management apparatus 402.
  • the memory 412 may comprise a hard disk, random access memory, cache memory, flash memory, a compact disc read only memory (CD-ROM), digital versatile disc read only memory (DVD-ROM), an optical disc, circuitry configured to store information, or some combination thereof.
  • the memory 412 may be configured to store information, data, applications, instructions, or the like for enabling the network management apparatus 402 to carry out various functions in accordance with various example embodiments.
  • the memory 412 may be configured to buffer input data for processing by the processor 410.
  • the memory 412 may be configured to store program instructions for execution by the processor 410.
  • the memory 412 may store information in the form of static and/or dynamic information. This stored information may be stored and/or used by the multipath configuration module 418 during the course of performing its functionalities.
  • the communication interface 414 may be embodied as any device or means embodied in circuitry, hardware, a computer program product comprising a computer readable medium (for example, the memory 412) storing computer readable program instructions that are executable by a suitably configured processing device (for example, the processor 410), or a combination thereof that is configured to receive and/or transmit data from/to another computing device.
  • the communication interface 414 may be at least partially embodied as or otherwise controlled by the processor 410.
  • the communication interface 414 may be in communication with the processor 410, such as via a bus.
  • the communication interface 414 may include, for example, an antenna, a transmitter, a receiver, a transceiver and/or supporting hardware or software for enabling communications with one or more remote computing devices.
  • the communication interface 414 may, for example, be configured to receive and/or transmit data using any protocol that may be used for communications between the network management apparatus 402 and another computing device, such as an apparatus 102.
  • the communication interface 414 may be configured to receive and/or transmit data using any protocol that may be used for transmission of data over the network 104.
  • the communication interface 414 may additionally be in communication with the memory 412, and/or multipath
  • configuration module 418 such as via a bus.
  • the multipath configuration module 418 may be embodied as various means, such as circuitry, hardware, a computer program product comprising a computer readable medium (for example, the memory 412) storing computer readable program instructions that are executable by a suitably configured processing device (for example, the processor 410), or some combination thereof and, in some example embodiments, may be embodied as or otherwise controlled by the processor 410. In embodiments wherein the multipath configuration module 418 is embodied separately from the processor 410, the multipath configuration module 418 may be in communication with the processor 410. The multipath configuration module 418 may further be in communication with one or more of the memory 412, or communication interface 414, such as via a bus.
  • a multipath configuration module 418 such as may be associated with a network management entity 1 12, may be configured to provision an apparatus 102 with configuration information for usage of a multipath transport protocol.
  • the multipath configuration module 418 may be configured to provision every apparatus 102 on a network (for example, the network 104, or portion thereof) that may be managed by the network management entity 1 12 with a static set of configuration information for use on the network.
  • the multipath configuration module 418 may be configured to dynamically provision configuration information to an apparatus 102 such that a first network-connected apparatus may be provisioned with a different set of configuration information than a second network-connected apparatus.
  • the multipath configuration module 418 may be configured to determine the configuration information to be provided to an apparatus 102 based at least in part on any of a variety of factors. For example, the multipath configuration module 418 may be configured to determine the configuration information to be provided to the apparatus 102 based at least in part on network conditions, access technologies available to the apparatus 102, capabilities of the apparatus 102, and/or the like. As a further example, the multipath configuration module 418 may be configured to determine the configuration information to be provided to the apparatus 102 based at least in part on a data plan, account type, and/or the like that may be associated with the apparatus 102.
  • an apparatus 102 associated with a customer who has subscribed to a higher level data plan, account, and/or the like may receive preferential provisioning of network access options.
  • the configuration information may specify any of a variety of configuration settings for an apparatus 102 regarding parameters for using a multipath transport protocol including, for example, parameters for whether the apparatus 102 is permitted to open a multipath subflow under certain circumstances.
  • the configuration information may specify whether the apparatus 102 is permitted to open a multipath subflow over a particular network access, such as over a WLAN access.
  • the configuration information may specify whether the apparatus 102 is permitted to open a multipath subflow for communication of a particular data type.
  • a network operator may desire to provide at least a guaranteed quality of service for some types of data, such as voice data (for example, voice over IP data packets), and may prohibit the apparatus 102 from opening a multipath subflow for such data so that all of the data is routed via a path through the operator's network so that the operator may provide the guaranteed quality of service level.
  • voice data for example, voice over IP data packets
  • data types such as non-real time video streaming, data transfer, and/or the like may benefit from the availability of multiple subflows over multiple network accesses, even if opening a multipath subflow inhibits provision of a guaranteed quality of service for the communications.
  • the configuration information may permit opening a multipath subflow for such data types.
  • the configuration information may specify whether the apparatus 102 is permitted to open a multipath subflow for communications with a particular device (for example, the network device 1 10).
  • the configuration information may specify multipath subflow permissions for a particular network address, domain name, and/or the like. For example, in some instances it may be preferred to confine traffic with a certain entity to a certain network access, path, tunnel, and/or the like.
  • the apparatus 102 may be prohibited from opening a multipath subflow for communications with an entity providing sensitive data, communications with a virtual private network entity, and/or the like so as to avoid compromising data by transmitting the data via a multipath subflow over a potentially-non-trusted network access.
  • the configuration information specifying whether the apparatus 102 is permitted to open a multipath subflow in certain circumstances, such that the apparatus 102 (for example, a multipath control module 318 that may be associated with an apparatus 102) is left to make the decision on whether to open a multipath subflow in instances wherein the apparatus 102 is so permitted.
  • the configuration information may specify one or more circumstances in which opening a multipath subflow is mandatory.
  • the configuration information may specify that opening a multipath subflow over a particular network access is mandatory when that network access is available.
  • the configuration information may provide for mandatory offloading of at least a portion of data traffic for a communication session from a first network access, such as a cellular access, to a multipath subflow on another network access, such as a WLAN access.
  • the configuration information may specify that opening a multipath subflow is mandatory when possible for communications involving a particular data type, communications with a particular entity (for example, communications with the network device 1 10), and/or the like.
  • a network management entity 1 12 may manage network bandwidth such that data traffic may be routed via another network access so as to avoid congestion and/or manage network resources in times of congestion.
  • the multipath configuration module 418 may be configured to provide an apparatus 102 with provisioned configuration information by causing a message including provisioned configuration information for usage of a multipath transport protocol to be sent to the apparatus 102.
  • the message may comprise a device management object, such as a device management object in accordance with Open Mobile Alliance (OMA) Device Management (DM) object standards.
  • OMA Open Mobile Alliance
  • DM Device Management
  • FIG. 5 illustrates a portion of an ANDSF management object according to some example embodiments, which may be extended to include configuration information for usage of a multipath transport protocol.
  • the portion of the ANDSF management object illustrated in FIG. 5 includes a RoutingRule node 502 and a Routing Rule node 504, either or both of which may be extended to include a sub-node for specifying rules for multipath subflows in accordance with some example embodiments.
  • FIG. 6 illustrates an extension of the ANDSF management object of FIG. 5 according to some example embodiments.
  • FIG. 5 illustrates a portion of an ANDSF management object according to some example embodiments, which may be extended to include configuration information for usage of a multipath transport protocol.
  • the portion of the ANDSF management object illustrated in FIG. 5 includes a RoutingRule node 502 and a Routing Rule node 504, either or both of which may be extended to include a sub-node for specifying rules for multipath subflows in accordance with some example embodiments.
  • the RoutingRule node 502 and/or the RoutingRule node 504 may be extended to include a Subflow sub node 602, which may include components, such as one or more of the components 604-612, specifying configuration information for usage of a multipath transport protocol.
  • the components 604-612 may, for example, comprise extensible markup language (XML) elements carrying configuration information.
  • the AccessTechnology component 604 may, for example, illustrate a prioritized access technology (for example, a prioritized network access).
  • the Accessld component 606 may, for example, indicate an access network identifier.
  • the Secondary AccessID component 608 may, for example, indicate a secondary access network identifier.
  • the AccessNetworkPriority component 610 may, for example, indicate an access technology priority (for example, a prioritized network access).
  • the NetworkType component 612 may, for example, define whether the subflow definition relates to IFOM, MAPCON, non-seamless WLAN offloading, and/or the like.
  • a multipath control module 318 such as may be associated with an apparatus 102, may be configured to receive a message sent by the network management entity 1 12 that comprises configuration information for usage of a multipath transport protocol.
  • the message may, for example, be received via the first network access 106.
  • the network management entity 1 12 may be configured to send a message including configuration information for usage of a multipath transport protocol to the apparatus 102 in a variety of circumstances in accordance with various example embodiments. As an example, such a message may be sent in response to a request for configuration information by the apparatus 102. As another example, the network management entity 1 12 may be configured to send a message including configuration information for usage of a multipath transport protocol to the apparatus 102 in an instance in which the apparatus 102 has not yet been provisioned with such configuration information (for example, after connecting to a network, after switching networks, after moving to a new location, and/or the like).
  • the network management entity 1 12 may be configured to send a message including configuration information for usage of a multipath transport protocol to the apparatus 102 in response to a change in data plan, subscription plan, account level and/or the like that may be associated with the apparatus 102.
  • the network management entity 1 12 may be configured to send a message including configuration information for usage of a multipath transport protocol to the apparatus 102 in response to a network operator changing preferences, modifying access networks, adding an access network, and/or the like.
  • the multipath control module 318 may be configured to extract the configuration information from the message, and may determine one or more configuration settings for usage of the multipath transport protocol based at least in part on the configuration information.
  • the multipath control module 318 may be further configured to apply the configuration settings to determine whether to open a multipath subflow over a network access (for example, the second network access 108) for communicating with a device, such as the network device 1 10.
  • a network access for example, the second network access 108
  • the multipath control module 318 may determine whether to open a subflow over the specified network access for communicating with the network device 1 10.
  • the multipath control module 318 may consider any of a variety of factors when making the determination, such as whether the specified network access offers more bandwidth than an existing flow or subflow over another network access (for example, the first network access 106), conditions (for example, congestion conditions) of an existing flow or subflow, whether the specified network access has lower data rate charges than a network access compared to a network access used for an existing flow or subflow, and/or the like. Accordingly, where permitted, the multipath control module 318 may leverage opening a multipath subflow over a network access to provide more bandwidth, reduce incurred data charges, and/or the like.
  • the multipath control module 318 may determine whether to open a multipath subflow based at least in part on a data type being or to be communicated with the network device 1 10. In this regard, if opening a multipath subflow for a data type being communicated is not permitted, then the multipath control module 318 may determine to not open a multipath subflow.
  • the multipath control module 318 may, for example, determine whether to open a multipath subflow based at least in part on one or more factors, such as whether the multipath subflow would offer more bandwidth or higher data rate than an existing flow or subflow, whether opening a multipath subflow would offer reduced data charges, and/or the like.
  • the multipath control module 318 may determine whether to open a multipath subflow based at least in part on the identity (for example, the address) of the device with which it is communicating. In this regard, if opening a multipath subflow for communications with the network apparatus 1 10 is prohibited, then the multipath control module 318 may determine to not open a multipath subflow.
  • the multipath control module 318 may, for example, determine whether to open a multipath subflow based at least in part on one or more factors, such as whether the multipath subflow would offer more bandwidth or higher data rate than an existing flow or subflow, whether opening a multipath subflow would offer reduced data charges, and/or the like.
  • configuration information that may be provisioned by the network management entity 1 12 may specify one or more circumstances in which opening a multipath subflow is mandatory.
  • circumstances may include availability of a particular network access, communicating with a particular device, communications involving a particular data type, some combination thereof, or the like. Accordingly, if the multipath control module 318 determines the existence of a circumstance, or combination of circumstances, for which opening a multipath subflow is mandatory, the multipath control module 318 may determine to open the multipath subflow.
  • the multipath control module 318 may be configured to perform ongoing monitoring (for example, periodic, aperiodic, continuous, and/or otherwise) for network conditions, circumstances, and/or the like during a communication session to determine whether to open a multipath subflow for an ongoing communication session.
  • network conditions may change, a new network access may become available to the apparatus 102, and/or other event may occur during a communication session such that in accordance with configuration settings the apparatus 102 may be permitted to open a multipath subflow and/or may be mandated to open a multipath subflow.
  • the multipath control module 318 may be configured to cause the multipath subflow to be opened via the communication interface 314 and an appropriate network access interface 315 corresponding to the network access via which the multipath subflow is to be opened.
  • FIG. 7 illustrates a flowchart according to an example method for supporting usage of a multipath transport protocol according to some example embodiments.
  • FIG. 7 illustrates operations that may be performed at an apparatus 102.
  • the operations illustrated in and described with respect to FIG. 7 may, for example, be performed by, with the assistance of, and/or under the control of one or more of the processor 310, memory 312, communication interface 314, a network access interface 315, or multipath control module 318.
  • Operation 700 may comprise receiving a message comprising configuration information for usage of a multipath transport protocol sent by a network management entity.
  • the processor 310, memory 312, communication interface 314, a network access interface 315, and/or the multipath control module 318 may, for example, provide means for performing operation 700.
  • Operation 710 may comprise determining one or more configuration settings for usage of the multipath transport protocol based at least in part on the configuration information in the received message.
  • the processor 310, memory 312, and/or multipath control module 318 may, for example, provide means for performing operation 710.
  • Operation 720 may comprise determining whether to use the multipath transport protocol to open a multipath subflow over a network access for communicating with a device based at least in part on the determined configuration settings.
  • the processor 310, memory 312, and/or multipath control module 318 may, for example, provide means for performing operation 720.
  • FIG. 7 illustrates a flowchart of a system, method, and computer program product according to some example embodiments. It will be understood that each block of the flowchart, and combinations of blocks in the flowchart, may be implemented by various means, such as hardware and/or a computer program product comprising one or more computer-readable mediums having computer readable program instructions stored thereon. For example, one or more of the procedures described herein may be embodied by computer program instructions of a computer program product.
  • the computer program product(s) which embody the procedures described herein may be stored by one or more memory devices of a mobile terminal, server, or other computing device (for example, in the memory 312 and/or in the memory 412) and executed by a processor in the computing device (for example, by the processor 310 and/or by the processor 410).
  • the computer program instructions comprising the computer program product(s) which embody the procedures described above may be stored by memory devices of a plurality of computing devices.
  • any such computer program product may be loaded onto a computer or other programmable apparatus (for example, a network management apparatus 402, apparatus 302, and/or other apparatus) to produce a machine, such that the computer program product including the instructions which execute on the computer or other programmable apparatus creates means for implementing the functions specified in the flowchart block(s).
  • the computer program product may comprise one or more computer-readable memories on which the computer program instructions may be stored such that the one or more computer-readable memories can direct a computer or other programmable apparatus to function in a particular manner, such that the computer program product may comprise an article of manufacture which implements the function specified in the flowchart block(s).
  • the computer program instructions of one or more computer program products may also be loaded onto a computer or other programmable apparatus (for example, a network management apparatus 402, apparatus 302, and/or other apparatus) to cause a series of operations to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus implement the functions specified in the flowchart block(s).
  • a computer or other programmable apparatus for example, a network management apparatus 402, apparatus 302, and/or other apparatus
  • blocks of the flowcharts support combinations of means for performing the specified functions. It will also be understood that one or more blocks of the flowcharts, and combinations of blocks in the flowcharts, may be implemented by special purpose hardware-based computer systems which perform the specified functions, or combinations of special purpose hardware and computer program product(s).
  • a suitably configured processor for example, the processor 310 and/or processor 410 may provide all or a portion of the elements.
  • all or a portion of the elements may be configured by and operate under control of a computer program product.
  • the computer program product for performing the methods of some example embodiments may include a computer-readable storage medium (for example, the memory 312 and/or the memory 412), such as the non-volatile storage medium, and computer-readable program code portions, such as a series of computer instructions, embodied in the computer-readable storage medium.

Landscapes

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

Abstract

L'invention concerne un procédé et un appareil pour prendre en charge l'utilisation d'un protocole de transport multi-chemin. Un procédé peut consister à recevoir, au niveau d'un appareil, un message comprenant des informations de configuration pour l'utilisation d'un protocole de transport multi-chemin envoyé par une entité de gestion de réseau. Le procédé peut consister en outre à déterminer un ou plusieurs réglages de configuration pour l'utilisation du protocole de transport multi-chemin sur la base au moins en partie des informations de configuration figurant dans le message reçu. Le procédé peut consister en outre à déterminer d'utiliser ou non le protocole de transport multi-chemin afin d'ouvrir un sous-flux multi-chemin sur un accès réseau pour communiquer avec un dispositif sur la base au moins en partie des réglages de configuration déterminés. Un appareil correspondant est également décrit.
PCT/IB2011/054807 2011-10-28 2011-10-28 Procédé et appareil pour prendre en charge l'utilisation d'un protocole de transport multi-chemin WO2013061115A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/IB2011/054807 WO2013061115A1 (fr) 2011-10-28 2011-10-28 Procédé et appareil pour prendre en charge l'utilisation d'un protocole de transport multi-chemin

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/IB2011/054807 WO2013061115A1 (fr) 2011-10-28 2011-10-28 Procédé et appareil pour prendre en charge l'utilisation d'un protocole de transport multi-chemin

Publications (1)

Publication Number Publication Date
WO2013061115A1 true WO2013061115A1 (fr) 2013-05-02

Family

ID=48167181

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2011/054807 WO2013061115A1 (fr) 2011-10-28 2011-10-28 Procédé et appareil pour prendre en charge l'utilisation d'un protocole de transport multi-chemin

Country Status (1)

Country Link
WO (1) WO2013061115A1 (fr)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FR3027478A1 (fr) * 2014-10-20 2016-04-22 Sagemcom Broadband Sas Procede de creation d'un sous flux de paquets de donnees.
WO2016110318A1 (fr) * 2015-01-06 2016-07-14 Telefonaktiebolaget Lm Ericsson (Publ) Procédé pour commander un protocole de commande de transmission (tcp) multipoint dans des réseaux de communication sans fil et dispositifs destinés à être utilisés dans ce dernier
US20160262080A1 (en) * 2015-03-04 2016-09-08 Nokia Technologies Oy Multipath interfaces in new scenarios
US10999882B2 (en) 2014-09-05 2021-05-04 Telefonaktiebolaget Lm Ericsson (Publ) Multipath control of data streams
CN114071634A (zh) * 2020-07-30 2022-02-18 中国电信股份有限公司 多路径传输控制方法、装置和移动终端
CN114885034A (zh) * 2017-09-29 2022-08-09 苹果公司 针对mptcp的rohc标头压缩

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011097321A2 (fr) * 2010-02-05 2011-08-11 Qualcomm Incorporated Utilisation de politiques de délestage et de mobilité des flux dans des systèmes de communication sans fil

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011097321A2 (fr) * 2010-02-05 2011-08-11 Qualcomm Incorporated Utilisation de politiques de délestage et de mobilité des flux dans des systèmes de communication sans fil

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
BAGNULO M. ET AL: "Boosting mobility performance with Multi-Path TCP", 2010 FUTURE NETWORK & MOBILE SUMMIT, 16 June 2010 (2010-06-16) - 18 June 2010 (2010-06-18), PISCATAWAY, JJ, USA, pages 1 - 8, XP031922052 *
FORD A. ET AL: "TCP Extensions for Multipath Operation with Multiple Addresses; draft-ford-mptcp-multiaddressed-03.txt; 20100309", INTERNET ENGINEERING TASK FORCE, IETF; STANDARD WORKING DRAFT, GENEVA, SWITZERLAND, pages 1 - 35, XP015068003 *
LG ELECTRONICS: "Enhancing Inter-System Routing Policies to include routing of IP flows across multiple APNs", 3GPP DRAFT; S2- 105491, 15 November 2010 (2010-11-15) - 19 November 2010 (2010-11-19), XP050467907 *
NEC: "IP Flow Mobility for individual flows of a single PDN Connection", 3GPP DRAFT; S2-087607, 17 November 2008 (2008-11-17) - 21 November 2008 (2008-11-21), XP050332046 *

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10999882B2 (en) 2014-09-05 2021-05-04 Telefonaktiebolaget Lm Ericsson (Publ) Multipath control of data streams
FR3027478A1 (fr) * 2014-10-20 2016-04-22 Sagemcom Broadband Sas Procede de creation d'un sous flux de paquets de donnees.
WO2016062606A1 (fr) * 2014-10-20 2016-04-28 Sagemcom Broadband Sas Procédé de création d'un sous flux de paquets de données
CN107005470B (zh) * 2014-10-20 2020-06-05 萨热姆通信宽带简易股份有限公司 创建数据分组的子流的方法、装置、通信系统和存储装置
CN107005470A (zh) * 2014-10-20 2017-08-01 萨热姆通信宽带简易股份有限公司 用于创建数据分组的子流的方法
US10270684B2 (en) 2014-10-20 2019-04-23 Sagemcom Broadband Sas Method for creating a subflow of data packets
US10433215B2 (en) 2015-01-06 2019-10-01 Telefonaktiebolaget Lm Ericsson (Publ) Method for controlling multipoint TCP in wireless communications networks and devices for use therein
WO2016110318A1 (fr) * 2015-01-06 2016-07-14 Telefonaktiebolaget Lm Ericsson (Publ) Procédé pour commander un protocole de commande de transmission (tcp) multipoint dans des réseaux de communication sans fil et dispositifs destinés à être utilisés dans ce dernier
US10448308B2 (en) * 2015-03-04 2019-10-15 Nokia Technologies Oy Multipath interfaces in new scenarios
US20160262080A1 (en) * 2015-03-04 2016-09-08 Nokia Technologies Oy Multipath interfaces in new scenarios
CN114885034A (zh) * 2017-09-29 2022-08-09 苹果公司 针对mptcp的rohc标头压缩
CN114071634A (zh) * 2020-07-30 2022-02-18 中国电信股份有限公司 多路径传输控制方法、装置和移动终端
CN114071634B (zh) * 2020-07-30 2023-11-21 中国电信股份有限公司 多路径传输控制方法、装置和移动终端

Similar Documents

Publication Publication Date Title
US11588710B2 (en) Intelligent prioritized mobility of low-latency applications
JP7304451B2 (ja) 通信方法、アクセスネットワークデバイス、コアネットワークデバイス及びユーザ装置
US11736981B2 (en) Method, apparatus and computer readable media for enforcing a rule related to traffic routing
EP2868143B1 (fr) Continuité d'application avec reroutage dans un réseau de communication sans fil
US11871330B2 (en) Transparent session migration between user plane functions
CN111052787A (zh) 基于5g环境中的利用水平的功能选择
CN110662308B (zh) 一种通信方法及装置
CN111937421A (zh) 一种订阅服务的方法及装置
JP2021504991A (ja) アプリケーションのためのトラフィックをハンドリングするための方法および機能
US9955381B2 (en) Steering traffic between cellular networks and WLAN networks
WO2019199311A1 (fr) Qos et itinérance à acheminement domestique
WO2013061115A1 (fr) Procédé et appareil pour prendre en charge l'utilisation d'un protocole de transport multi-chemin
WO2022046756A1 (fr) Calcul de transport de charge de travail sur un plan de commande dans des réseaux cellulaires de nouvelle génération
JP6396489B2 (ja) インターネットプロトコルメディアサブシステムサービスに基づくネットワークアクセス選択
US20220369198A1 (en) System and method for processing enhanced route selection descriptors
US9374735B2 (en) Method and apparatus for data flow management
US11729600B2 (en) Managing UE configuration in a serving PLMN in the presence of a default configuration for the UE for all PLMNs
JP2024515006A (ja) データ中心コンピューティングおよび通信インフラストラクチャのためのメカニズム
CN116601929A (zh) 到5gc功能连接的边缘计算
US11843512B2 (en) Integration of a standalone non-public network and a public land mobile network using an application function session
KR20230046280A (ko) 컴퓨트 오프로드 서비스들에 대한 능력 매니페스트 정의
JP2024532684A (ja) 第１のノード、第２のノード、および第３のノード、通信システム、ならびにそれによって実行される、デバイスのための１つ以上の進行中の通信セッションのモビリティを処理するための方法
KR20230039614A (ko) 5g 시스템들을 위한 에지 컴퓨팅 애플리케이션들
WO2023023034A1 (fr) Suppression d'abonnement de contrôleur intelligent de réseau d'accès radio (ran) (ric) initiée par un nœud e2 dans un ric en quasi-temps réel (rt)

Legal Events

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

Ref document number: 11874604

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11874604

Country of ref document: EP

Kind code of ref document: A1