Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W76/00—Connection management
  • H04W76/10—Connection setup
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L67/00—Network arrangements or protocols for supporting network services or applications
  • H04L67/14—Session management
  • H04L67/141—Setup of application sessions
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L67/00—Network arrangements or protocols for supporting network services or applications
  • H04L67/50—Network services
  • H04L67/56—Provisioning of proxy services
  • H04L67/562—Brokering proxy services
• • 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
  • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
  • H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
  • H04L69/163—In-band adaptation of TCP data exchange; In-band control procedures
• • 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/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
  • H04L69/168—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP] specially adapted for link layer protocols, e.g. asynchronous transfer mode [ATM], synchronous optical network [SONET] or point-to-point protocol [PPP]
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
  • H04W80/06—Transport layer protocols, e.g. TCP [Transport Control Protocol] over wireless

Definitions

• Certain embodiments may relate to communication systems. For example, some embodiments may relate to multi-path legs.
• Network multipath proxies provide a mechanism for multipath-capable clients to leverage the benefits of bandwidth aggregation and seamless handovers by sending traffic over one or more available access connections, even when the clients are connected to a single path application server.
• the multipath proxy can be part of network infrastructure of one of the networks, or hosted separately from the network infrastructure.
• a method may include receiving, at a user equipment, at least one user plane setup configuration message comprising at least one (MPC) key.
• the method may further include establishing, by the user equipment, at least one initial connection to at least one multi-path proxy.
• the method may further include initiating, by the user equipment, at least one multi-path leg based upon the at least one multi-path client key.
• an apparatus may include means for receiving at least one user plane setup configuration message comprising at least one multi-path client key.
• the apparatus may further include means for establishing at least one initial connection to at least one multi-path proxy.
• the apparatus may further include means initiating at least one multi-path leg based upon the at least one multi-path client key.
• an apparatus may include at least one processor and at least one memory including computer program code.
• the at least one memory and the computer program code may be configured to, with the at least one processor, cause the apparatus to at least receive at least one user plane setup configuration message comprising at least one multi-path client key.
• the at least one memory and the computer program code may be further configured to, with the at least one processor, cause the apparatus to at least establish at least one initial connection to at least one multi-path proxy.
• the at least one memory and the computer program code may be further configured to, with the at least one processor, cause the apparatus to at least initiate at least one multi-path leg based upon the at least one multi-path client key.
• a non-transitory computer readable medium may be encoded with instructions that may, when executed in hardware, perform a method.
• the method may receive at least one user plane setup configuration message comprising at least one multi-path client key.
• the method may further establish at least one initial connection to at least one multi- path proxy.
• the method may further initiate at least one multi-path leg based upon the at least one multi-path client key.
• a computer program product may perform a method.
• the method may receive at least one user plane setup configuration message comprising at least one multi-path client key.
• the method may further establish at least one initial connection to at least one multi- path proxy.
• the method may further initiate at least one multi-path leg based upon the at least one multi-path client key.
• an apparatus may include circuitry configured to receive at least one user plane setup configuration message comprising at least one multi-path client key.
• the circuitry may further establish at least one initial connection to at least one multi-path proxy.
• the circuitry may further initiate at least one multi-path leg based upon the at least one multi-path client key.
• a method may include allocating, by the network entity, at least one multi-path client key.
• the method may further include transmitting, by the network entity, at least one user plane setup configuration message comprising at least one multi-path client key.
• the method may further include receiving, by the network entity, at least one multi-path client key.
• an apparatus may include means for allocating at least one multi-path client key.
• the apparatus may further include means for transmitting at least one user plane setup configuration message comprising at least one multi-path client key.
• the apparatus may further include means for receiving at least one multi-path client key.
• an apparatus may include at least one processor and at least one memory including computer program code.
• the at least one memory and the computer program code may be configured to, with the at least one processor, cause the apparatus to at least allocate at least one multi-path client key.
• the at least one memory and the computer program code may be further configured to, with the at least one processor, cause the apparatus to at least transmit at least one user plane setup configuration message comprising at least one multi-path client key.
• the at least one memory and the computer program code may be further configured to, with the at least one processor, cause the apparatus to at least receive at least one multi-path client key.
• a non-transitory computer readable medium may be encoded with instructions that may, when executed in hardware, perform a method.
• the method may allocate at least one multi-path client key.
• the method may further transmit at least one user plane setup configuration message comprising at least one multi-path client key.
• the method may further receive at least one multi-path client key.
• a computer program product may perform a method.
• the method may allocate at least one multi-path client key.
• the method may further transmit at least one user plane setup configuration message comprising at least one multi-path client key.
• the method may further receive at least one multi-path client key.
• an apparatus may include circuitry configured to allocate at least one multi-path client key.
• the circuitry may further transmit at least one user plane setup configuration message comprising at least one multi-path client key.
• the circuitry may further receive at least one multi-path client key.
• FIG. 1 illustrates an example of multi-path proxying solution components according to certain embodiments.
• FIG. 2 illustrates an example of MAMS session establishment and MP session initiation according to certain embodiments.
• FIG. 3 illustrates an example of association of MP leg to an existing MP session according to certain embodiments.
• FIG. 4 illustrates an example of a method performed by a user equipment according to certain embodiments.
• FIG. 5 illustrates another example of a method performed by a user equipment according to certain embodiments.
• FIG. 6 illustrates an example of a method performed by a network entity according to certain embodiments.
• FIG. 7 illustrates another example of a method performed by a network entity according to certain embodiments.
• FIG. 8 illustrates a system according to certain embodiments.
• network multipath proxies provide a mechanism for multipath-capable clients to leverage the benefits of bandwidth aggregation and seamless handovers by sending traffic over one or more available access connections.
• challenges may arise in ensuring routing of the different connection legs coming from the different access networks to the multipath proxy, as well as the correlation of these legs. This is especially challenging when the networks are independently owned/managed, and it would be infeasible to implement interfaces between the different network infrastructures.
• MAMS is the control plane framework for configuring multipath proxies, but there exist no specifications of an explicit mechanism to correlate the application traffic streams landing on the proxy from different access connection legs.
• the present disclosure describes mechanisms for the generation and communication of a unique multi path client (MPC) key related to the multi path proxy (MPP) to the multi path client device by the MAMS control plane entity - the network connection manager (NCM).
• MCP multi path client
• NCM network connection manager
• the disclosure describes the deployment of a multi path proxy in the network along with the MAMS Control plane framework for configuration of the client to reach the appropriate proxy from any of the accesses, as well as ensuring that, at the network multi path proxy, the legs landing onto the proxy from the different access network paths can be correlated.
• the solution does not depend on a specific placement of the MAMS NCM and the multi path proxy (MPP).
• the NCM and MPP may be placed flexibility either in the 3GPP MNO network, or non-3GPP MSO network, or even hosted outside of the network operator domains by a 3rd party host or a UE manufacture datacentre based on solution deployment needs.
• a MAMS and multi-path capable client may setup an initial multipath leg and associate it with the MAMS session, as illustrated in FIG. 2.
• a NCM may use at least one MPC key to associate at least one MP session with a MAMS session, as illustrated in FIG. 3.
• Certain embodiments described herein enable correlating of connection legs across multiple access networks without impacting the actual multi-path protocol standard procedures, such as MP-TCP MP-QUIC. Certain embodiments are, therefore, directed to improvements in computer-related technology, specifically, by allowing scalable deployment of multi-path proxies across any mix of access networks with flexibility to place the network multipath proxy in 3 GPP, non-3GPP or in datacenters beyond the network packet data gateways. Certain embodiments may further conserve network resources and reduce power consumption of network entities and/or user equipment located within the network by reducing redundant operations.
• FIG. 4 illustrates an example of a method performed by user equipment, such as user equipment 810 in FIG. 8.
• the user equipment may receive policy information for access selection from at least one network policy function of a network entity, such as network entity 820 in FIG. 8.
• the network policy function may be a policy control function.
• step 401 may be performed at any time during the process.
• the policy information may be received at a multi-path client (MPC) as part of 3 GPP routing rules of the user equipment.
• MPC multi-path client
• the user equipment may transmit at least one multi-access management services (MAMS) session identifier request to the network entity.
• MAMS client connection manager (CCM) of the user equipment may transmit the at least one multi-access management services session identifier request, which may be transmitted to a MAMS network connection manager (NCM).
• NCM MAMS network connection manager
• the at least one MAMS session identifier request may include at least one multi-path capability proposal associated with at least one MX capability request message.
• the user equipment may receive one or more of at least one multi-path capability indication and at least one MAMS session identifier.
• the one or more of at least one multi-path capability indication and at least one MAMS session identifier may be received from the MAMS NCM, and may be received at the MAMS CCM.
• the user equipment may receive at least one user plane setup configuration message comprising at least one multi-path client key (“MPC key” or“client key”).
• the at least one user plane setup configuration message comprising at least one MPC key may be received at the MAMS CCM from the MAMS NCM.
• the at least one MPC key may be configured for setting up a connection with an MPP of the network entity.
• the at least one MPC key may be received as part of at least one MX user plane (UP) setup configuration message.
• the MPC key may be a uniquely generated MPC key.
• the proxy may be an MPTCP Proxy, the MPC key is the Client’s Key used when initiating a multi-path transmission control protocol (MPTCP) connection.
• the proxy may be a multi-path quick user datagram protocol internet connections (QUIC) proxy, where the MPC key is a source connection ID used by the user equipment to identify a MP-QUIC session at a MPQUIC proxy.
• QUIC multi-path quick user datagram protocol internet connections
• the user equipment may establish at least one initial connection to at least one multi-path proxy using the at least one MPC key.
• the CCM of the user equipment may pass the MPC key to the MPC software.
• the MPC software may use the MPC key when establishing an initial leg to the MPP.
• the user equipment may receive at least one multi-path proxy server instance address.
• the CCM may store the MPP server instance address, and may convey the MPP server instance address to the MPC software for use in setup of additional legs with the MPP over other access network connections.
• the user equipment may receive at least one user plane setup configuration message in which the at least one multi-path proxy server instance address may be comprised.
• the at least one user plane setup configuration message comprising the at least one multi- path proxy server instance address may be received from the NCM at the CCM.
• the at least one multi-path proxy server instance address may also be received as part of at least one MX user plane setup configuration message. Link conditions from the different access connections at the user equipment may be reported from CCM to NCM.
• the user equipment may determine that at least one multi- path leg needs to be setup over an access connection, for example, according to local and/or network provided policies.
• the user equipment may initiate at least one multi-path leg based upon the at least one multi-path client key.
• FIG. 5 illustrates an example of a method performed by user equipment, such as user equipment 810 in FIG. 8.
• the user equipment may receive policy information for access selection from at least one network policy function, for example, at least one policy control function of a network entity, such as network entity 820 in FIG. 8.
• step 501 may be performed at any time during the process.
• the user equipment may transmit at least one link measurement to the network entity.
• a MAMS client connection manager (CCM) of the user equipment may transmit the at least one link measurement, which may be transmitted to a MAMS network connection manager (NCM).
• the user equipment may receive at least one traffic steering request.
• the NCM may inform the CCM to setup at least one multipath leg over other access.
• the CCM may inform the multi-path client software to setup the multipath leg with the specified MPP. For example, the CCM may provide a MPP server instance address that the CCM had previously received from NCM.
• the user equipment may determine when to establish at least one multi-path leg. In some embodiments, the determination may be partially based on CCM instructions, policies from the network (3GPP PCRF), and/or OS/user settings.
• the user equipment may establish at least one multi-path leg over other access connection partially based on, for example, information provided by the CCM.
• the user equipment may receive at least one acknowledgement of the setup of the at least one multi-path leg, which may be according to the standard procedures of the multi path protocol.
• the user equipment may use multiple access connections via Proxy to connect to a single path application server, with MAMS signaling providing information to correlate the multi path legs at the proxy and using device measurements to provide network intelligence based guidance for establishment/removal of multi path legs for best performance.
• FIG. 6 illustrates an example of a method performed by a network entity, such as network entity or network function 820 in FIG. 8.
• the network entity may transmit policy information for access selection from at least one network policy function to a user equipment, such as user equipment 810 in FIG. 8.
• the network policy function may be a policy control function.
• step 601 may be performed at any time during the process.
• the policy information may be transmitted to a multi-path client (MPC) as part of 3 GPP routing rules of the user equipment.
• MCP multi-path client
• the network entity may receive at least one MAMS session identifier request.
• a MAMS client connection manager (CCM) of the user equipment may transmit the at least one multi-access management services session identifier request to the network entity which may be a MAMS network connection manager (NCM).
• the request may be transmitted via a base station (node B / evolved node B / 5G node B).
• the NCM may be part of or incorporated into a base station.
• the at least one MAMS session identifier request may include at least one multi-path capability proposal associated with at least one MX capability request message.
• the network entity may query at least one policy function of the network, such as a 3 GPP PCF, to determine at least one MPP server instance (or MPP function) supported in the network.
• the at least one MPP server instance may be configured to inform the user equipment of at least one MPP server instance supported by the network.
• the network entity may transmit one or more of at least one multi-path capability indication and at least one multi-access management services session identifier.
• the NCM may set up at least one MAMS session for the user equipment.
• the network entity may allocate at least one multi-path client key (MPC key).
• MPC key multi-path client key
• the NCM (which may be the network entity or may be part of the network entity) may allocate at least one MPC key, which may be unique for the user equipment, for each supported MPP proxy.
• the MPP may be configured to report all MP leg establishments to the NCM, or alternatively, there may be an additional step where NCM, after step 609, subscribes for notifications from the MPP when a user equipment establishes an MP leg using the MPC key.
• the network entity may transmit at least one user plane setup configuration message comprising the at least one (MPC) key.
• the at least one user plane setup configuration message comprising at least one MPC key may be received at the MAMS CCM from the MAMS NCM.
• the at least one MPC key may be configured for setting up a connection with an MPP.
• the MPP may be part of the network entity.
• the at least one MPC key may be received as part of at least one MX user plane (UP) setup configuration message.
• the MPC key may be a uniquely generated MPC key.
• the proxy may be an MPTCP Proxy, the MPC key is the Client’s Key used when initiating a multi-path transmission control protocol (MPTCP) connection.
• the proxy may be a multi-path - quick user datagram protocol internet connections (QUIC) proxy, where the MPC key is a source connection ID used by the user equipment to identify a MP-QUIC session at a MPQUIC proxy.
• QUIC multi-path - quick user
• the network entity may receive the at least one MPC key and an MPP server instance address.
• the network entity may initiate the multi-path leg based on the MPC key.
• the network entity may determine that a client identified by the MPC key has established an MP session with the MPP server instance having the MPP server instance address.
• the MPP server instance address is known by the network entity.
• a load balancer may have selected the MPP server instance which sets up the multi path leg with the MPC.
• the network entity may transmit the at least one multi-path proxy server instance address to the user equipment, for example to the CCM.
• the CCM may store the MPP server instance address, and may convey the MPP server instance address to the MPC software for use in setup of additional legs with the MPP over other access network connections.
• the network entity may transmit at least one user plane setup configuration message comprising the multi-path proxy server instance address to the user equipment.
• the user plane setup configuration message comprising the MPP server instance address may be received at the MAMS CCM, from the MAMS NCM.
• the MPP server instance address may also be received as part of an MX user plane setup configuration message.
• the NCM may configure the CCM to report at least one link condition from the different access connections of the user equipment.
• the MPP server instance may complete signalling with the MPC per standard procedures, involving the MPP key as well as the MPC key.
• FIG. 7 illustrates an example of a method performed by a network entity, such as network entity 820 in FIG. 8.
• the network entity may transmit policy information for access selection to a user equipment, such as user equipment 810 in FIG. 8, from at least one network policy function, for example, at least one policy control function.
• step 701 may be performed at any time during the process.
• the network entity may receive at least one link measurement to the network entity.
• a MAMS CCM of the user equipment may transmit the at least one link measurement, which may be transmitted to a MAMS NCM.
• the network entity such as with a NCM, may determine based on at least one link measurement corresponding to the access selection, that at least one condition has improved and/or that at least one multipath leg can be setup over that access connection.
• the network entity may transmit at least one traffic steering request.
• the network entity may receive at least one indication of when to establish at least one multi-path leg, and may establish at least one multi-path leg over other access connections using the information received, such as from a CCM.
• the network entity may transmit at least one acknowledgement of setup of at least one multi-path leg.
• FIG. 8 illustrates an example of a system according to certain embodiments.
• a system may include multiple devices, such as, for example, user equipment 810 and/or network entity 820.
• User equipment 810 may include one or more of a mobile device, such as a mobile phone, smart phone, personal digital assistant (PDA), tablet, or portable media player, digital camera, pocket video camera, video game console, navigation unit, such as a global positioning system (GPS) device, desktop or laptop computer, single-location device, such as a sensor or smart meter, or any combination thereof.
• GPS global positioning system
• Network entity 820 may be one or more of a base station, such as an evolved node B (eNB) or 5G or New Radio node B (gNB), a serving gateway, a server, and/or any other access node or combination thereof
• a base station such as an evolved node B (eNB) or 5G or New Radio node B (gNB)
• eNB evolved node B
• gNB New Radio node B
• Network entity 820 may also be a network function, such as a MAMS Network Connection Manager.
• network entity 810 and/or user equipment 820 may be one or more of a citizens broadband radio service device (CBSD).
• CBSD citizens broadband radio service device
• processors 811 and 821 may be embodied by any computational or data processing device, such as a central processing unit (CPU), application specific integrated circuit (ASIC), or comparable device.
• the processors may be implemented as a single controller, or a plurality of controllers or processors.
• At least one memory may be provided in one or more of devices indicated at 812 and 822.
• the memory may be fixed or removable.
• the memory may include computer program instructions or computer code contained therein.
• Memories 812 and 822 may independently be any suitable storage device, such as a non-transitory computer-readable medium.
• a hard disk drive (HDD), random access memory (RAM), flash memory, or other suitable memory may be used.
• the memories may be combined on a single integrated circuit as the processor, or may be separate from the one or more processors.
• the computer program instructions stored in the memory and which may be processed by the processors may be any suitable form of computer program code, for example, a compiled or interpreted computer program written in any suitable programming language.
• Memory may be removable or non-removable.
• Processors 811 and 821 and memories 812 and 822 or a subset thereof may be configured to provide means corresponding to the various blocks of FIGS. 1-7.
• the devices may also include positioning hardware, such as GPS or micro electrical mechanical system (MEMS) hardware, which may be used to determine a location of the device.
• MEMS micro electrical mechanical system
• Other sensors are also permitted and may be included to determine location, elevation, orientation, and so forth, such as barometers, compasses, and the like.
• transceivers 813 and 823 may be provided, and one or more devices may also include at least one antenna, respectively illustrated as 814 and 824.
• the device may have many antennas, such as an array of antennas configured for multiple input multiple output (MIMO) communications, or multiple antennas for multiple radio access technologies. Other configurations of these devices, for example, may be provided.
• Transceivers 813 and 823 may be a transmitter, a receiver, or both a transmitter and a receiver, or a unit or device that may be configured both for transmission and reception.
• Network entity 820 may also be a network function - in this case, transceiver 823 and antenna 824 may not be part of the network function, but may be accessible for use by the network function.
• the memory and the computer program instructions may be configured, with the processor for the particular device, to cause a hardware apparatus such as user equipment to perform any of the processes described below (see, for example, FIGS. 1-7). Therefore, in certain embodiments, a non-transitory computer-readable medium may be encoded with computer instructions that, when executed in hardware, perform a process such as one of the processes described herein. Alternatively, certain embodiments may be performed entirely in hardware.
• an apparatus may include circuitry configured to perform any of the processes or functions illustrated in FIGS. 1-7.
• circuitry may be hardware-only circuit implementations, such as analog and/or digital circuitry.
• circuitry may be a combination of hardware circuits and software, such as a combination of analog and/or digital hardware circuit(s) with software or firmware, and/or any portions of hardware processor(s) with software (including digital signal processor(s)), software, and at least one memory that work together to cause an apparatus to perform various processes or functions.
• circuitry may be hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that include software, such as firmware for operation. Software in circuitry may not be present when it is not needed for the operation of the hardware.
• E-UTRAN Evolved Universal Mobile Telecommunications System

Landscapes

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

Applications Claiming Priority (2)

Publications (1)

Family

ID=69701195

Family Applications (1)

Country Status (2)

Family Cites Families (3)

• 2020
  • 2020-02-25 EP EP20707240.6A patent/EP3932040A1/de active Pending
  • 2020-02-25 WO PCT/EP2020/054865 patent/WO2020173920A1/en unknown

Also Published As

Similar Documents

Legal Events