CN112738855B - Multilink-based transmission method and device applied to QUIC - Google Patents
Multilink-based transmission method and device applied to QUIC Download PDFInfo
- Publication number
- CN112738855B CN112738855B CN202011050346.4A CN202011050346A CN112738855B CN 112738855 B CN112738855 B CN 112738855B CN 202011050346 A CN202011050346 A CN 202011050346A CN 112738855 B CN112738855 B CN 112738855B
- Authority
- CN
- China
- Prior art keywords
- quic
- link
- client
- server
- app
- Prior art date
- Legal status (The legal status 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 status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 26
- 230000005540 biological transmission Effects 0.000 title claims abstract description 19
- 230000001413 cellular effect Effects 0.000 claims abstract description 19
- 238000004891 communication Methods 0.000 claims abstract description 18
- 238000001514 detection method Methods 0.000 claims abstract description 13
- 238000012217 deletion Methods 0.000 claims description 28
- 230000037430 deletion Effects 0.000 claims description 28
- 238000012795 verification Methods 0.000 claims description 20
- 206010010099 Combined immunodeficiency Diseases 0.000 claims description 7
- 238000001360 collision-induced dissociation Methods 0.000 claims description 7
- 238000012545 processing Methods 0.000 claims description 5
- 238000004590 computer program Methods 0.000 claims description 3
- 239000000523 sample Substances 0.000 claims 1
- 230000006870 function Effects 0.000 description 30
- 238000005516 engineering process Methods 0.000 description 24
- 238000007726 management method Methods 0.000 description 16
- 238000010586 diagram Methods 0.000 description 5
- 230000008569 process Effects 0.000 description 5
- 238000013461 design Methods 0.000 description 3
- GVVPGTZRZFNKDS-JXMROGBWSA-N geranyl diphosphate Chemical compound CC(C)=CCC\C(C)=C\CO[P@](O)(=O)OP(O)(O)=O GVVPGTZRZFNKDS-JXMROGBWSA-N 0.000 description 3
- 230000003993 interaction Effects 0.000 description 3
- 238000013523 data management Methods 0.000 description 2
- 230000000977 initiatory effect Effects 0.000 description 2
- CNQCVBJFEGMYDW-UHFFFAOYSA-N lawrencium atom Chemical group [Lr] CNQCVBJFEGMYDW-UHFFFAOYSA-N 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- ORQBXQOJMQIAOY-UHFFFAOYSA-N nobelium Chemical compound [No] ORQBXQOJMQIAOY-UHFFFAOYSA-N 0.000 description 2
- 238000000275 quality assurance Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 1
- 230000014509 gene expression Effects 0.000 description 1
- 239000011521 glass Substances 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 239000004984 smart glass Substances 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
- H04W36/0027—Control or signalling for completing the hand-off for data sessions of end-to-end connection for a plurality of data sessions of end-to-end connections, e.g. multi-call or multi-bearer end-to-end data connections
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
- H04L43/0811—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking connectivity
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0852—Delays
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0852—Delays
- H04L43/087—Jitter
-
- 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/164—Adaptation or special uses of UDP protocol
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/24—Reselection being triggered by specific parameters
- H04W36/30—Reselection being triggered by specific parameters by measured or perceived connection quality data
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Environmental & Geological Engineering (AREA)
- Computer Security & Cryptography (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The embodiment of the invention discloses a multilink-based transmission method and device applied to a QUIC, relates to the technical field of communication, and can realize multilink detection in the QUIC and facilitate the QUIC to switch links according to detection results. The invention comprises the following steps: the method comprises the steps that a QUIC client requests to build a link from a QUIC server by taking an address IPc _ w as a source IP and a Wi-Fi network as an output interface, wherein the IP of the QUIC server is IPs, the QUIC client is built in an APP client, and the QUIC server is built in the APP server; the APP client side sends application data to the server side through the established QUIC connection; the QUIC client establishes a cellular link to the server, the source IP is IPc _ c, and the output interface is a cellular network. The invention is suitable for QUIC multi-path management.
Description
Technical Field
The invention relates to the technical field of communication, in particular to a multilink-based transmission method and device applied to a QUIC.
Background
QUIC (Quick UDP Internet Connection) is a UDP-based low-latency Internet transport layer protocol, and well solves various requirements faced by the current transport layer and application layer, including handling more connections, security, and low latency. Google has begun to adopt QUIC as a transport layer in practical applications.
Currently, widely used terminal hosts are generally equipped with multiple network interfaces, such as Wi-Fi and cellular networks, and some important services are expected to provide the highest communication quality, and use the link with the best quality without increasing the complexity of the application.
At present, MP-QUIC has tried the multi-path of QUIC, but based on the idea of MPTCP, a hierarchy is added in the protocol, so that the protocol message load proportion is reduced, and the dynamic routing according to the link quality cannot be realized, thereby limiting the further development of the technical route.
Disclosure of Invention
The embodiment of the invention provides a multilink-based transmission method and device applied to a QUIC, which can realize multilink detection in the QUIC and also facilitate that the QUIC can switch links according to detection results.
In order to achieve the above purpose, the embodiment of the invention adopts the following technical scheme:
in one aspect, an embodiment of the present application provides a multilink-based transmission method applied to a QUIC, including: the method comprises the steps that a QUIC client requests to build a link from a QUIC server by taking an address IPc _ w as a source IP and a Wi-Fi network as an output interface, wherein the IP of the QUIC server is IPs, the QUIC client is built in an APP client, and the QUIC server is built in the APP server; the APP client side sends application data to the server side through the established QUIC connection; the QUIC client establishes a cellular link to the server, the source IP is IPc _ c, and the output interface is a cellular network.
Further comprising: and the QUIC client informs the QUIC server to add a new link, wherein the QUIC client maintains all link information provided by the APP client. The QUIC client detects the communication quality of all links of the APP client; and selecting the optimal link to send the application data, and keeping the selected suboptimal link alive. And/or the QUIC server side starts path verification for the new link and stores each link in the QUIC link for use.
The QUIC client informs the QUIC server to add a new link, and the method comprises the following steps: the QUIC client sends a link adding request to the QUIC server on a new link, wherein a target connection ID is a CIDs (common identifier) used by the QUIC link, and a source connection ID of the new link is a CIDc; the QUIC server side initiates address verification for the new link and records a new source IP and PORT in a local QUIC link, and the state of the new link is to be verified; the QUIC client replies link verification; the QUIC server side modifies the state of a new link into usable state and replies a message of successful addition to the QUIC client side; the QUIC client initiates probing of all links.
The APP client side informs the QUIC client side of deleting an IP or a port number; the QUIC client sends a link deletion message to the QUIC server; the QUIC server side deletes the link and replies the deletion success to the QUIC client side; or if the QUIC server side does not receive the link deletion message sent by the QUIC client side and does not receive the keep-alive message after the preset time, the keep-alive fails, the link is deleted after the link is broken, and the deletion success is replied to the QUIC client side.
In another aspect, an embodiment of the present application provides a transmission apparatus based on multiple links for use in a QUIC, including:
the link establishing module is used for triggering the QUIC client to request link establishment from the QUIC server by taking an address IPc _ w as a source IP and a Wi-Fi network as an output interface, wherein the IP of the QUIC server is IPs, the QUIC client is established in the APP client, and the QUIC server is established in the APP server;
the transmission module is used for the APP client side to send application data to the server side through the established QUIC connection;
and the link processing module is used for establishing a cellular link from the QUIC client to the server, wherein the source IP is IPc _ c, and the output interface is a cellular network.
The link establishing module is also used for triggering the QUIC client to inform the QUIC server to add a new link, wherein the QUIC client maintains all link information provided by the APP client, the QUIC server starts path verification for the new link, and each link is stored in the QUIC link for later use;
and/or the link establishing module is further configured to trigger the QUIC client to detect communication quality for all links of the APP client; and selecting the optimal link to send the application data, and keeping the unselected suboptimal links alive.
The link establishing module is specifically configured to trigger the QUIC client to send a link adding request to the QUIC server on a new link, where a destination connectID is a CIDs in use of the QUIC link, and a source connectID of the new link is a CIDc; the QUIC server side initiates address verification for the new link and records a new source IP and PORT in a local QUIC link, and the state of the new link is to be verified; the QUIC client replies to link verification; the QUIC server side modifies the state of a new link into usable state and replies a message of successful addition to the QUIC client side; the QUIC client initiates probing of all links.
The link establishment module is specifically used for triggering the APP client to inform the QUIC client of deleting an IP or a port number; the QUIC client sends a link deletion message to the QUIC server; the QUIC server side deletes the link and replies the deletion success to the QUIC client side; or if the QUIC server side does not receive the link deletion message sent by the QUIC client side and does not receive the keep-alive message after the preset time, the keep-alive fails, the link is deleted after the link is broken, and the deletion success is replied to the QUIC client side.
The embodiment of the invention provides a multilink-based transmission method and device applied to a QUIC.
In yet another aspect, a storage medium is provided that stores a computer program or instructions that, when executed, implements the above-described multilink-based transmission method for a QUIC.
This embodiment proposes a more efficient way of using the multiple links of the QUIC. Providing better quality assurance to the user compared to MPTCP or MP-QUIC. Aiming at the application using the QUIC, a solution of dynamic routing of the QUIC protocol under the condition that multiple links are available is provided, a plurality of addresses or ports are introduced into a client, the link quality including connectivity, time delay, jitter, bandwidth and the like is detected between each address or port and a server, and the most appropriate link is selected to transmit data according to the application requirements. Therefore, the user experience is enhanced, and meanwhile, the service complexity and the message length are not increased. And multi-link detection is realized in the QUIC, so that the QUIC can switch links conveniently according to detection results.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without creative efforts.
FIG. 1 is a schematic diagram of a process flow provided by an embodiment of the present application;
fig. 2 and fig. 3 are schematic diagrams of a possible implementation scenario provided by an embodiment of the present application;
fig. 4 and 5 are schematic diagrams of interaction processes of specific examples provided by an embodiment of the present application;
fig. 6 is a schematic diagram of a process of actively deleting a link by an application in a specific example provided in the embodiment of the present application.
Detailed Description
It should be noted that in the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or explanations. Any embodiment or design described herein as "exemplary" or "e.g.," is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present concepts related in a concrete fashion. In this application, "at least one" means one or more, "a plurality" means two or more. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone, wherein A and B can be singular or plural. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. "at least one of the following" or similar expressions refer to any combination of these items, including any combination of the singular or plural items. For example, at least one (one) of a, b, or c, may represent: b, c, a-b, a-c, b-c, or a-b-c, wherein a, b, c may be single or multiple. In addition, in order to facilitate clear description of technical solutions of the embodiments of the present application, in the embodiments of the present application, terms such as "first" and "second" are used to distinguish the same items or similar items having substantially the same functions and actions. Those skilled in the art will appreciate that the terms "first," "second," etc. do not denote any order or quantity, nor do the terms "first," "second," etc. denote any order or importance.
The system architecture and the service scenario described in the embodiment of the present application are for more clearly illustrating the technical solution of the embodiment of the present application, and do not form a limitation on the technical solution provided in the embodiment of the present application, and as a person of ordinary skill in the art knows that along with the evolution of the network architecture and the appearance of a new service scenario, the technical solution provided in the embodiment of the present application is also applicable to similar technical problems.
As shown in fig. 3, fig. 3 is a schematic diagram of a communication system provided in an embodiment of the present application, where the communication system includes: a core network, an access network, and one or more terminals 104. One or more terminals 104 (only one terminal is shown in fig. 3) access the core network through the access network. Wherein the core network comprises the following network elements: a session management network element 101, one or more user plane function network elements 102 (only one user plane function network element is shown in fig. 3) connected to the session management network element 101, and a policy control network element 103 connected to the session management network element 101.
The access network may be an access network device that adopts multiple access technologies. When the terminal 104 accesses the wireless network through different access technologies, the terminal 104 may connect to the core network device through different access network devices. Optionally, in this embodiment of the application, at least one of the one or more terminals 104 may have a session with the user plane function network element 102, and the session may support multiple access technologies. For example, the multiple access technologies are taken as a first access technology and a second access technology. The session may be accessed via a first access technology or via a second access technology. The first access technology in the embodiment of the present application may be an access technology compliant with a 3GPP standard specification. For example, third Generation Partnership project (3 GPP) access technology. For example, an access technology employed in Long Term Evolution (LTE), 2g,3g,4g or 5G systems. An Access Network that employs the 3GPP Access technology is referred to as a Radio Access Network (RAN). For example, the terminal 104 may access the wireless network through an access network device in a 2g,3g,4g or 5G system using 3GPP access technology. The second access technology may be a radio access technology not defined in the 3GPP standard specification. For example, a non-third Generation Partnership project (non 3 gpp) access technology. The non-3 GPP access technology may be an untrusted non3GPP access technology or a trusted non3GPP access technology. Non-3 GPP access technologies may include: wireless fidelity (Wi-Fi), worldwide Interoperability for Microwave Access (WiMAX), code Division Multiple Access (CDMA), wireless Local Area Network (WLAN), fixed network technology or wired technology, and the like. The terminal 104 may access a network through an air interface technology represented by Wireless Fidelity (WIFI), where the access network device may be an Access Point (AP).
In embodiments of the present invention, the terminals may be distributed in the wireless network, and each terminal may be static or mobile. The wireless network can be a 3G,4G, 5G and other mobile wireless networks, and can also be a wifi and other regional wireless networks.
In the embodiment of the present application, the session management network element 101, the user plane function network element 102, and the policy control network element 103 all belong to network elements in a core network element, and may be collectively referred to as core network elements. The core network element is mainly responsible for forwarding of packet data packets, quality of Service (Qos) control, charging statistics information, and the like (e.g., a user plane functional network element). And is mainly responsible for user registration authentication, mobility management, and data packet forwarding policy, qoS control policy, etc. (e.g., session management network element) issue to the user plane function network element. The session management element is responsible for establishing a corresponding session connection (e.g., a PDU session) on a network side when a user initiates a service, and providing specific services for the user, and in particular, issuing a packet forwarding policy, a QoS policy, and the like to the user plane functional element based on an interface between the session management element and the user plane functional element.
If the communication system shown in fig. 3 is applied to a 5G network, as shown in fig. 4, a network element or an entity corresponding to the Session Management network element 101 may be a Session Management Function (SMF) network element or a User Plane Function (UPF) network element in 5G. The policy control network element may be a Policy Control Function (PCF) network element. In addition, as shown in fig. 4, the 5G network may further include: AN Access and Mobility Management Function (AMF) Network element, AN Application Function (AF) Network element, AN Access Network device (e.g., AN Access Network (AN)), which may also be referred to as a Radio Access Network device (RAN), AN Authentication Server Function (AUSF) Network element, a Unified Data Management (UDM) Network element, a Network Slice Selection Function (NSSF) Network element, a Network capability opening Function (NEF) Network element, a Network Repository storage Function (Network reliability Function, NRF) Network element, and a Data Network (Data Network, DN), etc., which are not particularly limited in this embodiment.
The terminal communicates with the AMF network element through an N1 interface (N1 for short). The AMF network element communicates with the SMF network element via an N11 interface (abbreviated as N11). The SMF network element communicates with one or more UPF network elements over an N4 interface (referred to as N4 for short). Any two UPF network elements of the one or more UPF network elements communicate over an N9 interface (referred to as N9). The UPF Network element communicates with a Data Network (DN) over an N6 interface (N6 for short). The terminal accesses the network through an access network device (e.g., a RAN device). The access network equipment and the AMF network element communicate through an N2 interface (N2 for short). The SMF network element communicates with the PCF network element via an N7 interface (abbreviated as N7), and the PCF network element communicates with the AF network element via an N5 interface. The access network equipment communicates with the UPF network element through an N3 interface (referred to as N3 for short). Any two or more AMF network elements communicate with each other through an N14 interface (N14 for short). The SMF network element communicates with the UDM network element via an N10 interface (abbreviated N10). The AMF network element communicates with the AUSF network element through an N12 interface (referred to as N12). The AUSF network element communicates with the UDM network element via an N13 interface (abbreviated N13). The AMF network element communicates with the UDM network element via an N8 interface (N8 for short). It should be noted that the interface name between each network element in fig. 4 is only an example, and the interface name may be other names in a specific implementation, which is not specifically limited in this embodiment of the present application. The access network device, the AF network element, the AMF network element, the SMF network element, the AUSF network element, the UDM network element, the UPF network element, the PCF network element, etc. in fig. 4 are only names, and the names do not limit the device itself. In a 5G network and other future networks, network elements corresponding to an access network device, an AF network element, an AMF network element, an SMF network element, an AUSF network element, a UDM network element, a UPF network element, and a PCF network element may also be other names, which is not specifically limited in this embodiment of the present application. For example, the UDM network element may also be replaced by a Home Subscriber Server (HSS) or a User Subscription Database (USD) or a Database entity, and the like, which are described in the unified description herein and will not be described in detail later.
The access Network device referred to in the embodiments of the present application refers to a device accessing a core Network, and may be, for example, a base station, a Broadband Network Gateway (BNG), a convergence switch, a non-third Generation Partnership project (3 rd Generation Partnership project,3 gpp) access Network device, and the like. The base stations may include various forms of base stations, such as: macro base stations, micro base stations (also referred to as small stations), relay stations, access points, etc. The AMF network element may also be responsible for functions such as registration flow when the terminal accesses, location management during the terminal moving process, and lawful interception, which is not specifically limited in this embodiment of the present application. The SMF network element is used for carrying out session management and comprises: session establishment, session modification, session release, internet Protocol (IP) address allocation and management of interconnection between networks of the terminal, selection and control of UPF network elements, lawful interception and other control functions related to the session. The UPF Network element, in addition to having the function of the user plane functional Network element shown in fig. 4, may also implement the user plane functions of a Serving Gateway (SGW) and a Packet Data Network Gateway (PGW). In addition, the UPF Network element may also be a Software Defined Network (SDN) Switch (Switch), which is not specifically limited in this embodiment of the present application. The AUSF network element is an authentication server function and is mainly responsible for authenticating the terminal and determining the legality of the terminal. For example, the terminal is authenticated based on the user subscription data of the terminal. The UDM network element is unified user data management and is mainly used for storing subscription data of the terminal. In addition, the UDM network element further includes functions such as authentication, processing of identifier information of the terminal, subscription management, and the like, which is not specifically limited in this embodiment of the present application. And the PCF network element is mainly used for sending the service-related strategy to the AMF network element or the SMF network element. And the AF network element sends the application related requirements to the PCF network element so that the PCF network element generates a corresponding strategy. And the DN provides services for the terminal, such as mobile operator service, internet service or third-party service and the like.
The PDU session in the embodiment of the present application refers to: and the data transmission channel which is established by the session management network element and is used for connecting the terminal 104 and the UPF network element to the DN. The network element involved in the data transmission channel comprises: the terminal, the access network equipment, and the UPF network element selected by the SMF network element for the session. The data transmission channel comprises a plurality of links between two adjacent network elements. For example, the link between the terminal and the access network device, the link between the access network device and the UPF network element, and the link between the UPF network element and the UPF network element are included.
The terminal in the embodiments of the present application is a device providing voice and/or data connectivity to a user, for example, a handheld device, a vehicle-mounted device, etc. having a wireless connection function. A Terminal may also be referred to as a User Equipment (UE), an Access Terminal (Access Terminal), a subscriber Unit (User Unit), a subscriber Station (User Station), a Mobile Station (Mobile Station), a Remote Station (Remote Station), a Remote Terminal (Remote Terminal), a Mobile device (Mobile Equipment), a User Terminal (User Terminal), a Wireless communication device (Wireless Terminal Equipment), a User Agent (User Agent), user Equipment (User Equipment), or a User device. The terminal may be a station (Sta) in a Wireless Local Area Network (WLAN), and may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with Wireless communication function, a computing device or other processing device connected to a Wireless modem, a vehicle-mounted device, a wearable device, and a terminal in a next Generation communication system (e.g., a Fifth Generation (5G) communication Network) or a terminal in a future evolved Public Land Mobile Network (PLMN) Network, and the like. Among them, 5G may also be referred to as New Radio (NR).
In practical applications, the terminal may also be a wearable device. Wearable equipment can also be called wearable intelligent equipment, is the general term of applying wearable technique to carry out intelligent design, develop the equipment that can dress to daily wearing, like glasses, gloves, wrist-watch, dress and shoes etc.. A wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also realizes powerful functions through software support, data interaction and cloud interaction. The generalized wearable smart device has full functions and large size, and can realize complete or partial functions without depending on a smart phone, for example: smart watches or smart glasses and the like, and only focus on a certain type of application functions, and need to be used in cooperation with other devices such as smart phones, such as various smart bracelets for physical sign monitoring, smart jewelry and the like.
The embodiment of the invention provides a multilink-based transmission method applied to QUIC, as shown in figure 1, comprising the following steps:
s101, the QUIC client requests to establish a link from the QUIC server by taking the address IPc _ w as a source IP and the output interface as a Wi-Fi network.
Wherein, the addresses IPc _ w and IPc _ c are IPv4 or IPv6 addresses for wifi. Wherein, the address IPc _ w is an IPv4 or IPv6 address of the QUIC client for wifi. The address IPc _ c is the IPv4 or IPv6 address used by the QUIC client to establish the cellular link.
And S102, the APP client side sends application data to the server side through the established QUIC connection.
S103, the QUIC client establishes a cellular link to the server, the source IP is IPc _ c, and the output interface is a cellular network.
The IP of the QUIC (Quick UDP Internet Connection, a UDP-based low-delay Internet transport layer protocol) service end is IPs, and the IPs are IPv4 or IPv6 addresses of the QUIC service end. The QUIC client is established in the APP client, and the QUIC server is established in the APP server. The QUIC client side takes the address IPc _ w as a source IP and an output interface Wi-Fi to build a link to a QUIC server side (the IP is IPs), the source connect ID of the QUIC connection is CIDc, the destination connect ID is CIDs, and application data are sent based on the source connect ID and the destination connect ID. Then add cellular link, source IP IPc _ c, outgoing interface cellular network.
Taking the specific scenario shown in fig. 2 as an example: the system of the embodiment has three main bodies, namely an APP client, an APP server and a QUIC. QUIC has three parts at the same time: the QUIC client, the QUIC server and the QUIC are connected. The APP client can operate on the terminal, and the APP server can operate on a public cloud or a private cloud. The APP client needs to create a QUIC client, and besides the traditional specified server, it needs to add available links, delete available links, and give a selection policy, for simplicity, no policy may be provided, and a default policy is provided by the QUIC: such as connectable, with minimal latency. The APP server needs to create a QUIC server.
Due to the complexity of implementation that needs to be masked, the QUIC undertakes major tasks including address notification, path verification, path quality probing, path switching, etc. The present invention extends message and frame types on an IETF QUIC basis. The QUIC client maintains information of all links (mainly local IP and port numbers) provided by application, informs the server to add a new link, detects communication quality for all links, selects an optimal link to send application data, and keeps alive for unselected suboptimal links. The QUIC server initiates path verification for the new link and maintains the relationship between the multiple links and the QUIC connection.
Further, this embodiment further includes:
and the QUIC client informs the QUIC server to add a new link.
And the QUIC server side starts path verification for the new link and stores each link in the QUIC link for use.
And/or the QUIC client detects the communication quality for all links of the APP client; and selecting the optimal link to send application data, and keeping alive for the unselected suboptimal link. And the QUIC client maintains all link information provided by the APP client.
Specifically, the step of informing the QUIC server of adding a new link by the QUIC client includes:
the QUIC client sends a link adding request to the QUIC server on a new link, wherein a target connection ID is a CIDs (ChannelID signature) used by the QUIC link, and a source connection ID of the new link is a CIDc; the QUIC server side initiates address verification for the new link and records a new source IP and PORT in a local QUIC link, and the state of the new link is to be verified; the QUIC client replies to link verification; the QUIC server side modifies the state of a new link into usable state and replies a message of successful addition to the QUIC client side; the QUIC client initiates probing of all links. For example, as shown in fig. 5, the process of establishing a new link includes:
and the QUIC client sends an add link request to the QUIC server on the new link.
And 2, initiating address verification for the new link by the QUIC server, and recording a new source IP and a PORT in the local QUIC link, wherein the state is to be verified.
And the QUIC client replies to the link verification.
And 4, the QUIC server modifies the state of the new link into usable state and replies the addition success of the QUIC client.
And 5, the QUIC client starts the detection of all links, the invention does not limit the specific implementation of the detection, and the existing path quality detection means or the implementation in the QUIC can be realized. And determining whether to replace the link according to the result, wherein the link to be selected needs to be kept alive.
Further, the method also comprises the following steps: the APP client side informs the QUIC client side to delete the IP or the port number;
the QUIC client sends a link deletion message to the QUIC server; the QUIC server side deletes the link and replies the deletion success to the QUIC client side; or if the QUIC server side does not receive the link deletion message sent by the QUIC client side and does not receive the keep-alive message after the preset time, the keep-alive fails, the link is deleted after the link is broken, and the deletion success is replied to the QUIC client side. For example, as shown in fig. 6, applying the active deletion link flow includes:
1. and the client APP informs the QUIC client to delete the IP or the port number, and the QUIC client sends a link deletion message.
And 2, the QUIC server replies to the successful deletion.
When the QUIC client is deleted in a silent mode, the QUIC server may not receive a deletion request of the QUIC client, and the QUIC server needs to delete automatically after not receiving keep-alive in a certain time.
The present embodiment further provides a multilink-based transmission device applied to a QUIC, including:
the link building module is used for triggering the QUIC client to request for building a link from the QUIC server by taking an address IPc _ w as a source IP and a Wi-Fi network as an output interface, wherein the IP of the QUIC server is IPs, the QUIC client is built in the APP client, and the QUIC server is built in the APP server;
the transmission module is used for the APP client side to send application data to the server side through the established QUIC connection;
and the link processing module is used for establishing a cellular link from the QUIC client to the server, wherein the source IP is IPc _ c, and the output interface is a cellular network.
The link establishing module is also used for triggering the QUIC client to inform the QUIC server to add a new link, wherein the QUIC client maintains all link information provided by the APP client, the QUIC server starts path verification for the new link, and each link is stored in the QUIC link for later use;
and/or the link establishing module is further configured to trigger the QUIC client to detect communication quality for all links of the APP client; and selecting the optimal link to send the application data, and keeping the selected suboptimal link alive.
The link establishing module is specifically configured to trigger the QUIC client to send a link adding request to the QUIC server on a new link, where a destination connectID is a CIDs in use of the QUIC link, and a source connectID of the new link is a CIDc; the QUIC server side initiates address verification for the new link and records a new source IP and PORT in a local QUIC link, and the state of the new link is to be verified; the QUIC client replies to link verification; the QUIC server side modifies the state of the new link into usable state and replies a message of successful addition to the QUIC client side; the QUIC client initiates probing of all links.
The link establishment module is specifically used for triggering the APP client to notify the QUIC client to delete the IP or the port number; the QUIC client sends a link deletion message to the QUIC server; the QUIC server side deletes the link and replies the deletion success to the QUIC client side; or if the QUIC server side does not receive the link deletion message sent by the QUIC client side and does not receive the keep-alive message after the preset time, the keep-alive fails, the link is deleted after the link is broken, and the deletion success is replied to the QUIC client side.
This embodiment proposes a more efficient way of using multiple links of a QUIC. Providing better quality assurance to the user compared to MPTCP or MP-QUIC. Specifically, aiming at the application using the QUIC, a solution of dynamic routing of the QUIC protocol under the condition that multiple links are available is provided, multiple addresses or ports are introduced into a client, link quality including connectivity, time delay, jitter, bandwidth and the like is detected between each address or port and a server, and the most appropriate link is selected to transmit data according to the application requirements. Therefore, the user experience is enhanced, and meanwhile, the service complexity and the message length are not increased. And multi-link detection is realized in the QUIC, so that the QUIC can switch links according to detection results.
The steps of a method or algorithm described in connection with the disclosure herein may be embodied in hardware or in software instructions executed by a processor. The software instructions may be comprised of corresponding software modules that may be stored in Random Access Memory (RAM), flash memory, read Only Memory (ROM), erasable Programmable Read Only Memory (EPROM), electrically Erasable Programmable Read Only Memory (EEPROM), registers, a hard disk, a removable disk, a compact disc read only memory (CD-ROM), or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. Of course, the storage medium may also be integral to the processor. The processor and the storage medium may reside in an ASIC. Additionally, the ASIC may reside in a core network interface device. Of course, the processor and the storage medium may reside as discrete components in a core network interface device.
Those skilled in the art will recognize that in one or more of the examples described above, the functions described herein may be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer.
The above-mentioned embodiments, objects, technical solutions and advantages of the present application are further described in detail, it should be understood that the above-mentioned embodiments are only examples of the present application, and are not intended to limit the scope of the present application, and any modifications, equivalent substitutions, improvements and the like made on the basis of the technical solutions of the present application should be included in the scope of the present application.
Claims (9)
1. A method for multi-link based transmission in a QUIC, comprising:
the method comprises the steps that a QUIC client requests to build a link to a QUIC server by taking an address IPc _ w as a source IP and a Wi-Fi network as an output interface, wherein the IP of the QUIC server is IPs, the QUIC client is built in an APP client, the QUIC server is built in the APP server, and a QUIC connection formed by link building is used for sending application data to the QUIC server by the APP client;
the QUIC client establishes a cellular link to the QUIC server, the source IP is IPc _ c, and the output interface is a cellular network;
the QUIC client informs the QUIC server to add a new link, wherein the QUIC client maintains all link information provided by the APP client;
path verification of the added new link is started by the QUIC server and the relationship between a plurality of links and the QUIC connection is maintained by the QUIC server; the QUIC server is used for recording a new source IP and a PORT on a local QUIC link, and the state of the new link is to be verified; and after the QUIC client side replies link verification, the QUIC server side is used for modifying the state of a new link into usable state and replying a message of successful addition to the QUIC client side.
2. The method of claim 1, further comprising: the QUIC client detects the communication quality of all links of the APP client; and selecting the optimal link to send the application data, and keeping the unselected suboptimal links alive.
3. The method according to claim 1, wherein the QUIC client informs the QUIC server to add a new link, including:
the QUIC client sends a link adding request to the QUIC server on a new link, wherein a target connection ID is a CIDs in use by the QUIC link, and a source connection ID of the new link is a CIDc;
and after the QUIC server side modifies the state of the new link into usable state and replies a message of successful addition to the QUIC client side, starting detection on all links by the QUIC client side.
4. The method of claim 3, further comprising:
the APP client side informs the QUIC client side of deleting an IP or a port number;
the QUIC client sends a link deletion message to the QUIC server;
the QUIC server side deletes the link and replies the deletion success to the QUIC client side;
or if the QUIC server side does not receive the link deletion message sent by the QUIC client side and does not receive the keep-alive message after the preset time, the keep-alive fails, the link is deleted after the link is broken, and the deletion success is replied to the QUIC client side.
5. A multi-link based transmission apparatus for use in a QUIC, comprising:
the link building module is used for triggering a QUIC client to request for building a link from a QUIC server by taking an address IPc _ w as a source IP and a Wi-Fi network as an output interface, wherein the IP of the QUIC server is IPs, the QUIC client is built in the APP client, the QUIC server is built in the APP server, and the QUIC connection formed by the link building is used for sending application data to the QUIC server by the APP client;
the transmission module is used for triggering the APP client to send application data to the QUIC server through the QUIC connection formed by the link establishment;
the link processing module is used for establishing a cellular link from the QUIC client to the QUIC server, wherein the source IP is IPc _ c, and the output interface is a cellular network;
the link establishing module is further used for triggering the QUIC client to notify the QUIC server to add a new link, wherein the QUIC client maintains all link information provided by the APP client;
path verification of the added new link is started by the QUIC server and the relationship between a plurality of links and the QUIC connection is maintained by the QUIC server; the QUIC server is used for recording a new source IP and PORT in a local QUIC link, and the state of the new link is to be verified; and after the QUIC client side replies link verification, the QUIC server side is used for modifying the state of a new link into usable state and replying a message of successful addition to the QUIC client side.
6. The apparatus according to claim 5, wherein the link establishment module is further configured to trigger the QUIC client to probe communication quality for all links of the APP client; and selecting the optimal link to send the application data, and keeping the selected suboptimal link alive.
7. The apparatus according to claim 5, wherein the link establishment module is specifically configured to trigger the QUIC client to send a request for adding a link to the QUIC server over a new link, where a destination connectID is a CIDs being used by the QUIC link, and a source connectID of the new link is a CIDc; and after the QUIC server side modifies the state of the new link into usable state and replies a message of successful addition to the QUIC client side, starting detection on all links by the QUIC client side.
8. The apparatus according to claim 7, wherein the link establishment module is specifically configured to trigger the APP client to notify the QUIC client to delete an IP or port number; the QUIC client sends a link deletion message to the QUIC server; the QUIC server side deletes the link and replies the deletion success to the QUIC client side; or if the QUIC server side does not receive the link deletion message sent by the QUIC client side and does not receive the keep-alive message after the preset time, the keep-alive fails, the link is deleted after the link is broken, and the deletion success is replied to the QUIC client side.
9. A storage medium, storing a computer program or instructions which, when executed by a processor, implements the method of any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011050346.4A CN112738855B (en) | 2020-09-29 | 2020-09-29 | Multilink-based transmission method and device applied to QUIC |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011050346.4A CN112738855B (en) | 2020-09-29 | 2020-09-29 | Multilink-based transmission method and device applied to QUIC |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112738855A CN112738855A (en) | 2021-04-30 |
| CN112738855B true CN112738855B (en) | 2023-04-18 |
Family
ID=75597241
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011050346.4A Active CN112738855B (en) | 2020-09-29 | 2020-09-29 | Multilink-based transmission method and device applied to QUIC |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112738855B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114615178B (en) * | 2022-03-16 | 2024-02-13 | 北京轻网科技股份有限公司 | Link quality detection method and device |
| CN115277560B (en) * | 2022-09-28 | 2023-01-17 | 鹏城实验室 | Heterogeneous network fusion transmission method and system based on MPTCP and MPQUIC |
| CN118101782A (en) * | 2022-11-16 | 2024-05-28 | 腾讯科技（深圳）有限公司 | Data transmission method, device, electronic equipment and storage medium |
| CN117938550B (en) * | 2024-03-21 | 2024-05-24 | 北京火山引擎科技有限公司 | Path verification method and device in content distribution network |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109218186B (en) * | 2017-07-05 | 2021-02-23 | 华为技术有限公司 | Multipath data transmission processing method and network equipment |
| CN109818905B (en) * | 2017-11-21 | 2022-06-03 | 中国移动通信有限公司研究院 | Method, network element equipment and system for adapting transport layer protocol |
| US11019545B2 (en) * | 2018-06-27 | 2021-05-25 | Charter Communications Operating, Llc | Handover methods and apparatus |
| US10791485B2 (en) * | 2018-10-16 | 2020-09-29 | Cisco Technology, Inc. | Systems and methods for quick user datagram protocol internet connection (QUIC) with multipath |
| CN111211933B (en) * | 2018-11-22 | 2021-12-14 | 华为技术有限公司 | Method and device for determining quality of transmission link |
| WO2020155148A1 (en) * | 2019-02-02 | 2020-08-06 | 华为技术有限公司 | Method and apparatus for transmitting data |
-
2020
- 2020-09-29 CN CN202011050346.4A patent/CN112738855B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN112738855A (en) | 2021-04-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112738855B (en) | Multilink-based transmission method and device applied to QUIC | |
| US11159976B2 (en) | Handling of mapped EPS bearer context for invalid QoS flow description | |
| US8554876B2 (en) | User profile service | |
| EP3525545A1 (en) | Method for selecting session and service continuity mode in wireless communication system and device therefor | |
| JP5793812B2 (en) | Method, network side device, user equipment, and network system for triggering data offload | |
| CN108632944B (en) | User plane functional entity selection method and device | |
| EP4024956A1 (en) | Communication method, apparatus, and system | |
| US9788353B2 (en) | Mobile network communications method, communications apparatus, and communications system | |
| WO2010098146A1 (en) | Method for a communication node with a plurality of communication interfaces to notify dynamic path setup and associated apparatus thereof | |
| WO2019196643A1 (en) | Communication method and communication apparatus | |
| CN113055879B (en) | User identification access method and communication device | |
| CN105874756B (en) | The transmission method and equipment of control signaling | |
| US11438942B2 (en) | Method for establishing tunnel between local gateways, and gateway | |
| JP2021503199A (en) | Communication terminals, how to request a connection, network components and how to service the communication terminal | |
| WO2022021971A1 (en) | Communication method, first policy control network element, and communication system | |
| US11570847B2 (en) | Systems and methods for establishing and modifying user plane communications | |
| US20230328596A1 (en) | Handover for Communication Networks | |
| WO2019149177A1 (en) | Service offloading method and apparatus | |
| WO2019136606A1 (en) | Relay transmission method and relay node | |
| WO2015058339A1 (en) | Routing method between base stations, serving gateway and base station | |
| CN115915196A (en) | Link state detection method, communication device and communication system | |
| CN113507733B (en) | MEC-based user switching method, server and storage medium | |
| JP2020519108A (en) | Paging method and device | |
| WO2022056794A1 (en) | Communication method and apparatus | |
| WO2023143270A1 (en) | Communication method and apparatus |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |