WO2019170114A1 - 发送报文的方法、网络设备及计算机可读存储介质 - Google Patents

发送报文的方法、网络设备及计算机可读存储介质 Download PDF

Info

Publication number
WO2019170114A1
WO2019170114A1 PCT/CN2019/077243 CN2019077243W WO2019170114A1 WO 2019170114 A1 WO2019170114 A1 WO 2019170114A1 CN 2019077243 W CN2019077243 W CN 2019077243W WO 2019170114 A1 WO2019170114 A1 WO 2019170114A1
Authority
WO
WIPO (PCT)
Prior art keywords
packet
address
client
message
service node
Prior art date
Application number
PCT/CN2019/077243
Other languages
English (en)
French (fr)
Inventor
刘冰洋
夏成贵
李广鹏
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP19763170.8A priority Critical patent/EP3758339A4/en
Publication of WO2019170114A1 publication Critical patent/WO2019170114A1/zh
Priority to US17/015,503 priority patent/US11546259B2/en

Links

Images

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/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
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/74—Address processing for routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/02—Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
    • H04L63/0227—Filtering policies
    • H04L63/0236—Filtering by address, protocol, port number or service, e.g. IP-address or URL
    • 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/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • 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/14—Session management
    • H04L67/146—Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding

Definitions

  • the present application relates to the field of computers, and more particularly to a method of transmitting a message, a network device, and a computer readable storage medium.
  • the server Before the client accesses the server (such as the data center), it needs to establish a connection with the server.
  • a transport layer connection is bound to a five-tuple. Once the connection between the client and the server is established successfully, it is not allowed to change the 5-tuple used in the establishment of the connection, otherwise the connection will be broken.
  • the client usually initiates a connection establishment request with the Internet protocol (IP) address of the server (for example, the IP address of the front-end server that can be the server) as the destination IP address.
  • IP Internet protocol
  • the IP address of the server is bound to the connection as the destination IP address of the client, and changes are not allowed.
  • the server usually includes at least one service node, and the target service node for serving the client is one of the at least one network node (such as the client's topology nearest node). Because the packets sent by the client are based on the IP address of the server, the packet can only be routed to the target service node based on the IP address of the server. Therefore, in the conventional technology, the server needs to record a large amount of binding relationship information (which can be used to indicate the target service node corresponding to the client), so as to correctly route the packet sent by the client to the target service node. With the continuous expansion of the server scale, the number of service nodes included in the server is also increasing, resulting in more and more binding relationship information that the server needs to record. A large number of binding relationship information records will cause a huge network. Overhead.
  • the first aspect provides a method for sending a packet, where the target service node of the server receives the first packet sent by the client, where the destination address of the first packet is an IP address of the server, and the server includes at least a service node, the target service node is one of the at least one service node, and the IP address of the server is different from the IP address of the target service node; the target service node sends a second packet to the client, where the second packet includes The IP address of the target serving node; the target serving node receives the third packet sent by the client, and the destination address of the third packet is the IP address of the target serving node.
  • the target service node in the process of establishing a connection between the client and the server, records the IP address of the node in the second packet.
  • the client After receiving the second packet, the client changes the destination address from the IP address of the server to the IP address of the target serving node, and sends the third packet.
  • the server can directly forward the third packet to the target service node without recording the correspondence between the client and the target service node, thereby reducing the network overhead.
  • the destination port number of the first packet is a port number of the server
  • the destination port number of the second packet is a port number of the client
  • the second packet further includes a target service. Port number of the node.
  • the destination port number of the third packet is the port number of the target service node.
  • the port number of the local node may be recorded in the packet.
  • the client changes the destination port number of the third packet to the port number of the target service node, so that the third packet can be directly routed to the exact port location of the target service node, which simplifies. Process flow.
  • the second packet is a packet based on a QUIC protocol.
  • the first packet is a QUIC initial packet
  • the second packet is a QUIC handshake packet or a QUIC retry packet.
  • the source address of the first packet is an IP address of the client
  • the source address of the second packet is an IP address of the server
  • the destination address of the second packet is the client.
  • the connection established by the client with the target service node is a first connection
  • the second message includes a connection identifier
  • the third message includes the connection identifier
  • the method further includes The target service node determines, according to the quintuple information and/or the connection identifier in the third packet, that the third packet belongs to the first connection.
  • the method further includes: the target service node sending a fourth packet to the client, where the source address of the fourth packet is an IP address of the target serving node, and the fourth packet The destination address is the IP address of the client.
  • the second aspect provides a method for sending a packet, where the client sends a first packet, where the destination address of the first packet is an IP address of the server, and the client receives the second packet sent by the target serving node.
  • the second message includes an IP address of the target service node, the server includes at least one service node, the target service node is one of the at least one service node, and an IP address of the target service node and an IP of the server The address is different; the client sends a third packet to the target serving node, and the destination address of the third packet is the IP address of the target serving node.
  • the target service node in the process of establishing a connection between the client and the server, records the IP address of the node in the second packet.
  • the client After receiving the second packet, the client changes the destination address from the IP address of the server to the IP address of the target serving node, and sends the third packet.
  • the server can directly forward the third packet to the target service node without recording the correspondence between the client and the target service node, thereby reducing network overhead.
  • the destination port number of the first packet is a port number of the server
  • the destination port number of the second packet is a port number of the client
  • the first packet further includes a target service.
  • the destination port number of the third packet is the port number of the target service node.
  • the target service node may record the port number of the local node in the second message.
  • the client After receiving the second packet, the client changes the destination port number of the third packet to the port number of the target service node, so that the third packet can be directly routed to the exact port location of the target service node, which simplifies. Process flow.
  • the second packet is a packet based on a QUIC protocol.
  • the first packet is a QUIC initial packet
  • the second packet is a QUIC handshake packet or a QUIC retry packet.
  • the source address of the first packet is an IP address of the client
  • the source address of the second packet is an IP address of the server
  • the destination address of the second packet is the client.
  • the connection established by the client with the target service node is a first connection
  • the method further includes: determining, by the client, the second according to the quintuple information in the second packet.
  • the message belongs to the first connection.
  • the third packet includes a connection identifier
  • the method further includes: receiving, by the client, a fourth packet sent by the target serving node, where the fourth packet includes the connection identifier; The client determines, according to the quintuple information in the fourth packet and/or the connection identifier, that the fourth packet belongs to the first connection.
  • a network device comprising means for performing the method of any of the first aspect or the implementation of the first aspect.
  • a network device comprising means for performing the method of any of the above second aspect or the second aspect.
  • a network device comprising: a processor and a transceiver, configured to perform the method of any one of the foregoing first aspect or the first aspect.
  • a network device comprising: a processor and a transceiver, configured to perform the method of any of the foregoing second aspect or the second aspect.
  • a seventh aspect a computer readable storage medium for storing computer software instructions, comprising the method of performing the first aspect or the implementation of any of the first aspects, The program designed.
  • a computer readable storage medium for storing computer software instructions, comprising the method of any one of the second aspect or the second aspect described above The program designed.
  • a computer program product comprising: computer program code, when the computer program code is run on a computer, causing the computer to perform any of the first aspect or the first aspect Said method.
  • a computer program product comprising: computer program code, when the computer program code is run on a computer, causing the computer to perform any one of the second aspect or the second aspect Said method.
  • FIG. 1 is a schematic diagram of a communication manner between a legacy client and a service node.
  • FIG. 2 is a schematic flowchart of a method for sending a message according to an embodiment of the present application.
  • FIG. 3 is a diagram of an example of a first packet provided by an embodiment of the present application.
  • FIG. 4 is a diagram showing an example of a second message provided by an embodiment of the present application.
  • FIG. 5 is a diagram showing an example of a third packet provided by an embodiment of the present application.
  • FIG. 6 is a schematic block diagram of a network device according to an embodiment of the present application.
  • FIG. 7 is a schematic block diagram of another network device according to an embodiment of the present application.
  • FIG. 8 is a schematic block diagram of another network device according to an embodiment of the present application.
  • FIG. 9 is a schematic block diagram of another network device according to an embodiment of the present application.
  • the technical solution provided by the embodiment of the present application can be applied to a scenario in which a client and a server communicate by establishing a transport layer connection.
  • a client communicates with a data center
  • CDN content delivery network
  • the client mentioned in the embodiment of the present application may be located on a terminal device, and the client may be, for example, an application (APP) on the terminal device.
  • a terminal device may refer to a user equipment, an access terminal, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user device.
  • the terminal device may also be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), with wireless communication.
  • SIP session initiation protocol
  • WLL wireless local loop
  • PDA personal digital assistant
  • a service node can refer to an entity that the server can provide one or more services.
  • a service node can sometimes also be called a service instance.
  • the service node can be, for example, a physical server or a virtual machine, or even a load balancer with an application layer protocol at the server. The specific form of the service node is not limited in this embodiment of the present application.
  • the following takes the data center as an example to describe the communication mode between the traditional client and the service node.
  • the first packet is sent with the IP address of the server as the destination address.
  • the first packet can be, for example, a connection request packet.
  • the IP address of the server can be, for example, the IP address of the front-end server of the server.
  • the server is the data center, and the IP address of the data center is 1.1.1.1.
  • the client can send the first packet to the data center with the IP address of 1.1.1.1.
  • the data center may select the service node 1 as the target service node of the client from the service node 1-6 according to the load condition of the service node in the data center or the topological distance between the service node and the client. .
  • the IP address of the client used by the connection establishment process the port number of the client, the IP address of the server, the port number of the server, and the transport layer protocol type will be between the client and the server.
  • the connections are bound together and no changes are allowed (once the changes are made, the connections are broken).
  • the server needs to record the binding relationship between the client and the service node 1. As the number of clients and service nodes increases, the two The recording of the binding relationship between them causes a lot of network overhead.
  • the method for sending a message provided by the embodiment of the present application is described in detail below with reference to FIG. As shown in FIG. 2, the method can include steps 210-230.
  • the client sends the first message.
  • the source address of the first packet is the IP address of the client
  • the destination IP address of the first packet is the IP address of the server.
  • the IP address of the server can be, for example, the front-end IP address of the server, or other IP addresses that are opened by the server to the outside world and used by the outside world to access the server.
  • the client can query the IP address of the server through a domain name system (DNS) or the like.
  • DNS domain name system
  • the first packet may be referred to as a connection request packet, and the first packet may be, for example, the first packet sent by the client to the server. Taking QUIC as an example, the first packet may be a QUIC initial packet.
  • the first message is received by the target service node of the server.
  • the manner of determining the target service node is not specifically limited in this embodiment of the present application.
  • the server may select a lightly loaded service node as the target service node according to the load condition of the service node.
  • the server may select the nearest node of the client as the target service node according to the topological relationship between the client and the service node.
  • FIG. 3 is a diagram of an example of a first packet provided by an embodiment of the present application.
  • the client can record the quintuple information such as the source address and the destination address in the IP header of the first packet.
  • the target serving node sends a second message to the client.
  • the source address of the second packet is the IP address of the server, and the destination address is the IP address of the client.
  • the second packet may be referred to as a connection reply packet, and the second packet may be, for example, the first packet sent by the server to the client.
  • the second packet may be a QUIC retry packet or a QUIC handshake packet.
  • the second message may contain the IP address of the target service node.
  • the IP address of the target service node is different from the IP address of the server.
  • the IP address of the target service node can uniquely identify the location of the target service node.
  • the message between the client and the target service node may be forwarded through an intermediate node (such as a front-end server or a router of the server), and the location and number of the intermediate node are related to a specific network configuration. Not limited.
  • an intermediate node such as a front-end server or a router of the server
  • FIG. 4 is a diagram showing an example of a second message provided by an embodiment of the present application.
  • the target service node sets the IP address of the node in the QUIC header, and sets the quintuple information such as the source address and the destination address in the IP header.
  • FIG. 4 is merely an exemplary illustration, and the application is not limited thereto.
  • the target service node may also set the IP address of the node to the load location of the QUIC message.
  • step 230 the client sends the third packet to the target serving node with the IP address of the target serving node as the destination address.
  • the client may extract the IP address of the target serving node from the second packet, and use the IP address of the target serving node as the destination IP address of the third packet to be subsequently sent.
  • the third packet in the embodiment of the present application may be a QUIC protected packet, a QUIC initial packet, or a QUIC handshake packet.
  • the QUIC protected packet can be a data packet.
  • FIG. 5 is a diagram showing an example of a third packet provided by an embodiment of the present application. Taking QUIC as an example, after extracting the IP address of the target service node, the client sets the destination address in the third packet to the IP address of the target service node.
  • the server can directly forward the third packet to the target serving node, and does not need to record the binding relationship between the server and the client as in the conventional technology. Can reduce network overhead.
  • one or more messages sent by the client are collectively referred to as a third packet after the second packet, that is, the third packet may be used.
  • the text is understood as any message sent by the client after the second message.
  • the second message may further include a port number of the target service node.
  • the client can send the third packet to the target serving node by using the port number of the target service node as the destination port number.
  • the destination port number of the first packet is the port number of the server
  • the destination port number of the second packet is the port number of the client
  • the second packet further includes the port number of the target service node
  • the destination of the third packet The port number is the port number of the target service node.
  • the port number of the local node may be recorded in the packet.
  • the client changes the destination port number of the third packet to the port number of the target service node, so that the third packet can be directly routed to the exact port location of the target service node, which simplifies. Process flow.
  • the source address and the destination address mentioned in this application may be public network addresses or private network addresses, which are not specifically limited in this embodiment of the present application.
  • the public network address refers to the address after the address converter is converted.
  • the private network address is the original address that is not converted by the address translator.
  • source port number and the destination port number mentioned in this application may also be a public network port number or a private network port number, which is not specifically limited in this embodiment of the present application.
  • the client after transmitting the first packet, the client locally records the connection related to the first packet as the first connection. The client then determines the message related to the first packet as the message in the first connection.
  • the client after receiving the second packet sent by the target serving node, the client identifies the second packet according to the quintuple information in the second packet, and determines that the second packet belongs to the first connection.
  • the embodiment of the present application does not specifically limit the communication protocol on which the connection establishment mode shown in FIG. 2 is based, and may be a newly introduced communication protocol, or may modify a connection establishment of a conventional protocol.
  • the QUIC protocol is taken as an example for detailed description.
  • the QUIC protocol is a low-latency Internet transport layer protocol based on UDP.
  • the QUIC protocol allows you to modify the information in the quintuple, such as the IP address and port number of the client and server in the quintuple, after the connection is established, while ensuring that the connection is not broken.
  • the traditional QUIC protocol does not allow the information in the quintuple to be changed during the connection establishment process. In this way, during the connection establishment process and the initial stage after the connection is established, the network side still needs to maintain the relationship between the client and the target service node. Binding relationships cause large network overhead.
  • the embodiment of the present application improves the connection establishment process of the QUIC protocol to reduce network overhead.
  • the embodiment of the present application briefly introduces the handshake communication process of the QUIC protocol.
  • Step 1 The client sends a first initial packet, where the first initial packet includes a connection identifier connection ID' determined by the client.
  • the client locally records the connection related to the first initial packet as the first connection.
  • Step 2 After receiving the first initial packet, the target serving node sends a retry packet or a first handshake packet to the client according to the actual situation.
  • the retry packet or the first handshake packet carries the IP address and/or port number of the target service node.
  • the target service node may further carry the connection identifier connection ID determined by the local node in the retry packet or the first handshake packet.
  • the destination IP address and/or port number of the first initial packet is different from the IP address and/or port number of the target serving node.
  • connection ID carried by the retry packet or the first handshake packet may be the same as the connection ID', and may be different, which is not specifically limited in this embodiment of the present application.
  • the connection related to the first handshake packet is locally recorded as the first connection.
  • Step 3 After receiving the retry packet sent by the target service node, the client sends the second initial to the target service node by using the IP address of the target service node as the destination address and/or the port number of the target service node as the destination port number.
  • the packet is re-established.
  • the connection identifier used by the second initial packet may be any connection identifier.
  • the connection identifier used by the second initial packet may be a connection ID or a connection ID'.
  • the connection identifier used by the second initial packet may be other connection identifiers than the connection ID and connection ID'.
  • the client may determine the retry packet as the packet in the first connection according to the quintuple information in the retry packet.
  • the client After receiving the first handshake packet sent by the target serving node, the client sends the protected packet or the second handshake packet to the target serving node by using the IP address of the target serving node as the destination address.
  • the connection identifier used by the second handshake packet is a connection ID
  • the connection identifier used by the protected packet may be a connection ID' or a connection ID.
  • Step 4 After receiving the second initial packet sent by the client, the target serving node may send a retry packet or a handshake packet to the client according to the actual situation.
  • the target serving node After receiving the protected packet or handshake packet sent by the client, the target serving node determines, according to the quintuple information and/or the connection identifier in the protected packet or the handshake packet, that the protected packet or the handshake packet belongs to the first connection. Text.
  • the target service node sends a fourth packet to the client.
  • the source address of the fourth packet is the IP address of the target serving node
  • the destination address is the IP address of the client
  • the connection identifier used by the fourth packet is the connection ID.
  • Step 5 After receiving the fourth packet, the client identifies the fourth packet according to the quintuple information and/or the connection identifier in the fourth packet, and determines that the fourth packet belongs to the first connection. Text.
  • FIG. 6 is a schematic block diagram of a network device according to an embodiment of the present application.
  • the network device 600 includes a first receiving unit 610, a first transmitting unit 620, and a second receiving unit 630.
  • the first receiving unit 610 is configured to receive the first packet sent by the client, where the source address of the first packet is an IP address of the client, and the destination IP address of the first packet is an IP address of the server.
  • the IP address of the server can be, for example, the front-end IP address of the server, or other IP addresses that are opened by the server to the outside world and used by the outside world to access the server.
  • the client can query the IP address of the server through DNS or the like.
  • the first packet may be referred to as a connection request packet, and the first packet may be, for example, the first packet sent by the client to the server. Taking QUIC as an example, the first packet may be a QUIC initial packet.
  • the first sending unit 620 is configured to send a second packet to the client, where the second packet includes an IP address of the network device.
  • the second packet may be referred to as a connection reply packet, and the second packet may be, for example, the first packet sent by the server to the client.
  • the second packet may be a QUIC retry packet, or may be a QUIC handshake packet.
  • the second receiving unit 630 is configured to receive a third packet sent by the client, where the destination address of the third packet is an IP address of the network device.
  • the client may extract the IP address of the network device from the second packet, and use the IP address of the network device as the destination IP address of the third packet to be subsequently sent.
  • the third packet in the embodiment of the present application may be a QUIC protected packet, a QUIC initial packet, or a QUIC handshake packet.
  • the QUIC protected packet can be a data packet.
  • the server can directly forward the third packet to the network device, and does not need to record the binding relationship between the server and the client as in the conventional technology. Can reduce network overhead.
  • the second message may further include a port number of the target service node.
  • the client can send the third packet to the target serving node by using the port number of the target service node as the destination port number.
  • the destination port number of the first packet is the port number of the server
  • the destination port number of the second packet is the port number of the client
  • the second packet further includes the port number of the target service node
  • the destination of the third packet The port number is the port number of the target service node.
  • the port number of the local node may be recorded in the packet.
  • the client changes the destination port number of the third packet to the port number of the network device, so that the third packet can be directly routed to the exact port location of the network device, simplifying the processing flow. .
  • the second packet in the embodiment of the present application may be a packet based on a QUIC protocol.
  • the embodiment of the present application further provides a network device 700.
  • the network device 700 includes a processor 710, a memory 720 and a transceiver 730.
  • the memory 720 is for storing instructions, and the processor 710 and the transceiver 730 are configured to execute instructions stored by the memory 720.
  • network device 600 shown in FIG. 6 or the network device 700 shown in FIG. 7 may be used to perform related operations or processes in the foregoing method embodiments, and operations of various units in the network device 600 or the network device 700 and/or The functions are respectively implemented in order to implement the corresponding processes in the foregoing method embodiments, and are not described herein for brevity.
  • FIG. 8 is a schematic block diagram of another network device according to an embodiment of the present application.
  • the network device 800 includes a first receiving unit 810, a first transmitting unit 820, and a second receiving unit 830.
  • the first sending unit 810 is configured to send the first packet, where the source address of the first packet is an IP address of the client, and the destination IP address of the first packet is an IP address of the server.
  • the IP address of the server can be, for example, the front-end IP address of the server, or other IP addresses that are opened by the server to the outside world and used by the outside world to access the server.
  • the client can query the IP address of the server through DNS or the like.
  • the first packet may be referred to as a connection request packet, and the first packet may be, for example, the first packet sent by the network device to the server. Taking QUIC as an example, the first packet may be a QUIC initial packet.
  • the first receiving unit 820 is configured to receive a second packet sent by the target serving node, where the second packet includes an IP address of the target serving node.
  • the second packet may be referred to as a connection reply packet, and the second packet may be, for example, the first packet sent by the server to the network device.
  • the second packet may be a QUIC retry packet, or may be a QUIC handshake packet.
  • the second sending unit 830 is configured to send a third packet to the target serving node, where the destination address of the third packet is an IP address of the target serving node.
  • the network device may extract the IP address of the target serving node from the second packet, and use the IP address of the target serving node as the destination IP address of the third packet to be subsequently sent.
  • the third packet in the embodiment of the present application may be a QUIC protected packet, a QUIC initial packet, or a QUIC handshake packet.
  • the QUIC protected packet can be a data packet.
  • the server can directly forward the third packet to the target serving node, and does not need to record the binding relationship between the server and the network device as in the conventional technology. Can reduce network overhead.
  • the second message may further include a port number of the target service node.
  • the network device may send the third packet to the target serving node by using the port number of the target service node as the destination port number.
  • the destination port number of the first packet is the port number of the server
  • the destination port number of the second packet is the port number of the client
  • the second packet further includes the port number of the target service node
  • the destination of the third packet The port number is the port number of the target service node.
  • the port number of the local node may be recorded in the packet.
  • the network device changes the destination port number of the third packet to the port number of the target serving node, so that the third packet can be directly routed to the exact port location of the target service node, which simplifies Process flow.
  • the second packet in the embodiment of the present application may be a packet based on a QUIC protocol.
  • the embodiment of the present application further provides a network device 900.
  • the network device 900 includes a processor 910, a memory 920, and a transceiver 930.
  • the memory 920 is for storing instructions, and the processor 910 and the transceiver 930 are configured to execute instructions stored by the memory 920.
  • the network device 800 shown in FIG. 8 or the network device 900 shown in FIG. 9 may be used to perform related operations or processes in the foregoing method embodiments, and operations of various units in the network device 800 or the network device 900 and/or The functions are respectively implemented in order to implement the corresponding processes in the foregoing method embodiments, and are not described herein for brevity.
  • processors mentioned in the embodiment of the present application may be a central processing unit (CPU), and may also be other general-purpose processors, digital signal processors (DSPs), and application specific integrated circuits ( Application specific integrated circuit (ASIC), field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the memory referred to in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be a read-only memory (ROM), a programmable read only memory (ROMM), an erasable programmable read only memory (erasable PROM, EPROM), or an electrical Erase programmable EPROM (EEPROM) or flash memory.
  • the volatile memory can be a random access memory (RAM) that acts as an external cache.
  • RAM random access memory
  • RAM random access memory
  • many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (Synchronous DRAM). SDRAM), double data rate synchronous dynamic random access memory (DDR), enhanced synchronous dynamic random access memory (ESDRAM), synchronously connected dynamic random access memory (synchlink DRAM, SLDRAM) ) and direct memory bus random access memory (DR RAM).
  • processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, the memory (storage module) is integrated in the processor.
  • memories described herein are intended to comprise, without being limited to, these and any other suitable types of memory.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product.
  • the technical solution of the present application which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including
  • the instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program code. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请提供了一种发送报文的方法、网络设备及计算机可读存储介质。该方法包括：目标服务节点接收客户端发送的第一报文，第一报文的目的地址为服务端IP地址；目标服务节点向客户端发送第二报文，第二报文包括目标服务节点的IP地址；目标服务节点接收客户端发送的第三报文，第三报文的目的地址为目标服务节点的IP地址。上述技术方案中，目标服务节点将本节点的IP地址记录在第二报文中。客户端在收到该第二报文后，将目的地址由服务端的IP地址改为目标服务节点的IP地址进行第三报文的发送，服务端无需记录客户端与目标服务节点的对应关系，直接将第三报文转发至目标服务节点，从而降低了网络开销。

Description

发送报文的方法、网络设备及计算机可读存储介质
本申请要求于2018年3月9日提交中国专利局、申请号为201810193364.4、申请名称为“发送报文的方法、网络设备及计算机可读存储介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及计算机领域，并且更具体地，涉及一种发送报文的方法、网络设备及计算机可读存储介质。
背景技术
客户端在对服务端(如数据中心)进行访问前，需要先与服务端建立连接。传统技术中，一个传输层的连接会与一个五元组进行绑定。一旦客户端和服务端之间的连接建立成功，则不允许改变建立连接过程中使用的五元组，否则该连接就会断掉。
实际通信过程中，客户端通常会以服务端的互联网协议(internet protocol，IP)地址(例如可以是服务端的前端服务器的IP地址)作为目的IP地址发起连接建立请求。一旦客户端与服务端的连接建立成功，服务端的IP地址就会作为客户端的目的IP地址与该连接绑定在一起，不允许对其进行更改。
服务端通常包括至少一个服务节点，用于为客户端服务的目标服务节点为该至少一个网络节点中的一个网络节点(如客户端的拓扑最近节点)。由于客户端发送的报文均以服务端的IP地址为目的地址，仅基于服务端的IP地址通常无法将该报文路由至该目标服务节点。因此，传统技术中，服务端需要记录大量的绑定关系信息(可用于指示客户端对应的目标服务节点)，以便将客户端发送的报文正确路由至目标服务节点。随着服务端规模的不断扩大，服务端包含的服务节点的数量也越来越多，导致服务端需要记录的绑定关系信息越来越多，大量绑定关系信息的记录会造成巨大的网络开销。
发明内容
第一方面，提供了一种发送报文的方法，包括：服务端的目标服务节点接收客户端发送的第一报文，该第一报文的目的地址为服务端的IP地址，该服务端包括至少一个服务节点，该目标服务节点为该至少一个服务节点之一，该服务端的IP地址与目标服务节点的IP地址不同；该目标服务节点向客户端发送第二报文，该第二报文包括该目标服务节点的IP地址；该目标服务节点接收该客户端发送的第三报文，该第三报文的目的地址为该目标服务节点的IP地址。
根据本申请提供的方法，在客户端与服务端建立连接的过程中，目标服务节点会将本节点的IP地址记录在第二报文中。客户端在收到该第二报文后，将目的地址由服务端的IP地址改为目标服务节点的IP地址，进行第三报文的发送。这样服务端可直接将该第三 报文转发至目标服务节点，而无需记录客户端与目标服务节点的对应关系，从而能够降低网络的开销。
在一种可能的实现方式中，该第一报文的目的端口号为该服务端的端口号，该第二报文的目的端口号为该客户端的端口号，该第二报文还包括目标服务节点的端口号，该第三报文的目的端口号为该目标服务节点的端口号。
根据本申请提供的方法，目标服务节点发送第二报文时，可以将本节点的端口号记录在该报文中。客户端在收到该第二报文后，将第三报文的目的端口号更改为目标服务节点的端口号，从而可以直接将第三报文路由至目标服务节点的准确端口位置，简化了处理流程。
在一种可能的实现方式中，该第二报文是基于QUIC协议的报文。
在一种可能的实现方式中，该第一报文为QUIC初始报文，该第二报文为QUIC握手报文或QUIC重试报文。
在一种可能的实现方式中，该第一报文的源地址为该客户端的IP地址，该第二报文的源地址为该服务端的IP地址，该第二报文的目的地址为该客户端的IP地址。
在一种可能的实现方式中，该客户端与该目标服务节点建立的连接为第一连接，该第二报文包括连接标识符，该第三报文包括该连接标识符，该方法还包括：该目标服务节点根据该第三报文中的五元组信息和/或该连接标识符，确定该第三报文属于该第一连接。
在一种可能的实现方式中，该方法还包括：该目标服务节点向该客户端发送第四报文，该第四报文的源地址为该目标服务节点的IP地址，该第四报文的目的地址为该客户端的IP地址。
第二方面，提供了一种发送报文的方法，包括：客户端发送第一报文，该第一报文的目的地址为服务端的IP地址；该客户端接收目标服务节点发送的第二报文，该第二报文包括该目标服务节点的IP地址，该服务端包括至少一个服务节点，该目标服务节点为至少一个服务节点之一，且该目标服务节点的IP地址与该服务端的IP地址不同；该客户端向该目标服务节点发送第三报文，该第三报文的目的地址为该目标服务节点的IP地址。
根据本申请提供的方法，在客户端与服务端建立连接的过程中，目标服务节点会将本节点的IP地址记录在第二报文中。客户端在收到该第二报文后，将目的地址由服务端的IP地址改为目标服务节点的IP地址，进行第三报文的发送。这样服务端可直接将该第三报文转发至目标服务节点，而无需记录客户端与目标服务节点的对应关系，从而能够降低网络的开销。
在一种可能的实现方式中，该第一报文的目的端口号为该服务端的端口号，该第二报文的目的端口号为该客户端的端口号，该第一报文还包括目标服务节点的端口号，该第三报文的目的端口号为该目标服务节点的端口号。
根据本申请提供的方法，目标服务节点在发送的第二报文中，可以将本节点的端口号记录在该报文中。客户端在收到该第二报文后，将第三报文的目的端口号更改为目标服务节点的端口号，从而可以直接将第三报文路由至目标服务节点的准确端口位置，简化了处理流程。
在一种可能的实现方式中，该第二报文是基于QUIC协议的报文。
在一种可能的实现方式中，该第一报文为QUIC初始报文，该第二报文为QUIC握手 报文或QUIC重试报文。
在一种可能的实现方式中，该第一报文的源地址为该客户端的IP地址，该第二报文的源地址为该服务端的IP地址，该第二报文的目的地址为该客户端的IP地址。
在一种可能的实现方式中，该客户端与该目标服务节点建立的连接为第一连接，该方法还包括：该客户端根据该第二报文中的五元组信息，确定该第二报文属于该第一连接。
在一种可能的实现方式中，该第三报文包括连接标识符，该方法还包括：该客户端接收该目标服务节点发送的第四报文，该第四报文包括该连接标识符；该客户端根据该第四报文中的五元组信息和/或该连接标识符，确定该第四报文属于该第一连接。
第三方面，提供了一种网络设备，包括用于执行上述第一方面或第一方面中任一种实现方式所述的方法的模块。
第四方面，提供了一种网络设备，包括用于执行上述第二方面或第二方面中任一种实现方式所述的方法的模块。
第五方面，提供了一种网络设备，该网络设备包括：处理器和收发器，用于执行上述第一方面或第一方面的任一种实现方式所述的方法。
第六方面，提供了一种网络设备，该网络设备包括：处理器和收发器，用于执行上述第二方面或第二方面的任一种实现方式所述的方法。
第七方面，提供了一种计算机可读存储介质，该计算机可读存储介质用于存储计算机软件指令，其包含用于执行上述第一方面或第一方面中任一种实现方式所述的方法所设计的程序。
第八方面，提供了一种计算机可读存储介质，该计算机可读存储介质用于存储计算机软件指令，其包含用于执行上述第二方面或第二方面中任一种实现方式所述的方法所设计的程序。
第九方面，提供了一种计算机程序产品，该计算机程序产品包括：计算机程序代码，当该计算机程序代码在计算机上运行时，使得计算机执行上述第一方面或第一方面中任一种实现方式所述的方法。
第十方面，提供了一种计算机程序产品，该计算机程序产品包括：计算机程序代码，当该计算机程序代码在计算机上运行时，使得计算机执行上述第二方面或第二方面中任一种实现方式所述的方法。
附图说明
图1是传统客户端与服务节点的通信方式的示意图。
图2是本申请实施例提供的发送报文的方法的示意性流程图。
图3是本申请实施例提供的第一报文的示例图。
图4是本申请实施例提供的第二报文的示例图。
图5是本申请实施例提供的第三报文的示例图。
图6是本申请实施例提供的一种网络设备的示意性框图。
图7是本申请实施例提供的另一种网络设备的示意性框图。
图8是本申请实施例提供的另一种网络设备的示意性框图。
图9是本申请实施例提供的另一种网络设备的示意性框图。
具体实施方式
本申请实施例提供的技术方案可应用于客户端与服务端通过建立传输层连接进行通信的场景。例如，可应用于客户端与数据中心进行数据通信的场景，或者可应用于内容分发网络(content delivery network，CDN)。
本申请实施例提及的客户端可以位于终端设备上，该客户端例如可以是该终端设备上的应用程序(application，APP)。终端设备可以指用户设备、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。终端设备还可以是蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字处理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，未来5G网络中的终端设备或者未来演进的公用陆地移动通信网络(public land mobile network，PLMN)中的终端设备等，本申请实施例对此并不限定。
当前互联网上，随着客户端数量的不断增多，访问服务的客户端数量也不断增加。为了满足大量客户端的访问需求，服务端通常需要设置至少一个服务节点。一般情况下，服务端需要设置至少两个或至少三个服务节点。服务节点可以指服务端能够提供一种或多种服务的实体。服务节点有时也可以称为服务实例。服务节点例如可以是物理的服务器，也可以是虚拟机，甚至可以是位于服务端的具有应用层协议的负载均衡器，本申请实施例对服务节点的具体形态并不限定。
下面结合图1，以数据中心为例，对传统客户端与服务节点的通信方式进行说明。
客户端需要从服务端获取某种服务时，会以该服务端的IP地址为目的地址发送第一报文，该第一报文例如可以为连接请求报文。服务端的IP地址例如可以是服务端的前端服务器的IP地址。如图1所示，服务端为数据中心，数据中心的IP地址为1.1.1.1。客户端可以以1.1.1.1为目的IP地址，向数据中心发送第一报文。数据中心收到该连接建立请求之后，可以根据数据中心中的服务节点的负载情况或者服务节点与客户端之间的拓扑距离，从服务节点1-6中选取服务节点1作为客户端的目标服务节点。连接建立成功之后，连接建立过程所使用的客户端的IP地址、客户端的端口号、服务端的IP地址、服务端的端口号、传输层协议类型等五元组将会与客户端与服务端之间的连接绑定在一起，不允许改变(一旦改变，连接就会断开)。为了保证客户端通过该连接发送的后续报文能够正确路由至服务节点1，服务端需要记录客户端与服务节点1的绑定关系，随着客户端与服务节点数量的不断增大，二者之间的绑定关系的记录会造成很大的网络开销。
随着通信技术的发展，出现了一些新的协议类型，如快速用户数据报协议互联网连接(quick UDP internet connection，QUIC)协议，这些新的协议允许在连接建立之后，在保证连接不会断开的情况下对五元组进行更改。本申请实施例利用这些协议所带来的灵活性，对连接建立过程的通信方式进行改进，从而降低如图1所示的传统的客户端与服务端通信方式所需的网络开销。
下面结合图2，详细描述本申请实施例提供的发送报文的方法。如图2所示，该方法可以包括步骤210-230。
在步骤210中，客户端发送第一报文。第一报文的源地址为客户端的IP地址，第一报文的目的IP地址为服务端的IP地址。服务端的IP地址例如可以是服务端的前端IP地址，也可以是服务端向外界开放的、供外界访问该服务端时使用的其他IP地址。客户端例如可以通过域名系统(domain name system，DNS)等手段查询到服务端的IP地址。
第一报文可以称为连接请求报文，第一报文例如可以是客户端向服务端发送的首报文。以QUIC为例，该第一报文可以为QUIC初始报文(QUIC initial packet)。
该第一报文会被服务端的目标服务节点接收到。本申请实施例对目标服务节点的确定方式不做具体限定。作为一个示例，服务端可以根据服务节点的负载情况，选择轻载的服务节点作为目标服务节点。作为另一个示例，服务端可以根据客户端与服务节点之间的拓扑关系，选择客户端的拓扑最近节点作为目标服务节点。
图3是本申请实施例提供的第一报文的示例图。以QUIC为例，客户端可以在该第一报文的IP头中记载源地址、目的地址等五元组信息。
在步骤220中，目标服务节点向客户端发送第二报文。该第二报文的源地址为服务端的IP地址，目的地址为客户端的IP地址。
第二报文可以称为连接回复报文，第二报文例如可以是服务端向客户端发送的首报文。以QUIC协议为例，该第二报文可以是QUIC重试报文(QUIC retry packet)，或者也可以是QUIC握手报文(QUIC handshake packet)。
第二报文可以包含目标服务节点的IP地址。目标服务节点的IP地址与服务端的IP地址不同。目标服务节点的IP地址可以唯一标识目标服务节点的位置。
应理解，客户端和目标服务节点之间的报文可以通过中间节点(如服务端的前端服务器或路由器)进行转发，中间节点的位置和数量与具体的网络形态有关，本申请实施例对此并不限定。
图4是本申请实施例提供的第二报文的示例图。以QUIC协议为例，目标服务节点将本节点的IP地址设置在QUIC头部，将源地址、目的地址等五元组信息设置在IP头中。
图4仅为示例性说明，本申请并不限于此。例如，目标服务节点也可以将将本节点的IP地址设置在QUIC报文的负载位置。
在步骤230中，客户端以目标服务节点的IP地址为目的地址，向目标服务节点发送第三报文。
客户端收到第二报文后，可以从该第二报文中提取目标服务节点的IP地址，并将目标服务节点的IP地址作为后续发送的第三报文的目的IP地址。
本申请实施例中的第三报文可以为QUIC保护报文(QUIC protected packet)、QUIC initial packet或QUIC handshake packet。其中，QUIC protected packet可以是数据报文。
图5是本申请实施例提供的第三报文的示例图。以QUIC为例，客户端提取出目标服务节点的IP地址后，将第三报文中的目的地址设置为目标服务节点的IP地址。
由于第三报文的目的地址为目标服务节点的IP地址，服务端可以直接将第三报文转发至目标服务节点，无需像传统技术那样记录服务端与客户端之间的绑定关系，从而能够降低网络开销。
需要说明的是，本申请实施例中，为了便于说明，将在上述第二报文之后，客户端发送的一个或多个报文统称为第三报文，也就是说，可以将第三报文理解为在上述第二报文 之后客户端发送的任意报文。
可选地，在一些实施例中，第二报文还可以包含目标服务节点的端口号。客户端可以目标服务节点的端口号为目的端口号，向目标服务节点发送第三报文。具体地，第一报文的目的端口号为服务端的端口号，第二报文的目的端口号为客户端的端口号，第二报文还包括目标服务节点的端口号，第三报文的目的端口号为目标服务节点的端口号。
根据本申请实施例提供的方法，目标服务节点发送第二报文时，可以将本节点的端口号记录在该报文中。客户端在收到该第二报文后，将第三报文的目的端口号更改为目标服务节点的端口号，从而可以直接将第三报文路由至目标服务节点的准确端口位置，简化了处理流程。
本申请提及的源地址和目的地址可以为公网地址，也可以为私网地址，本申请实施例对此不做具体限定。公网地址是指经过地址转换器转换之后的地址。私网地址是指不经过地址转换器转换的原始地址。
此外，本申请提及的源端口号和目的端口号也可以为公网端口号，也可以为私网端口号，本申请实施例对此不做具体限定。
可选地，作为一个示例，客户端在发送第一报文后，在本地记录与该第一报文有关的连接为第一连接。之后客户端将与该第一报文有关的报文都确定为第一连接内的报文。
具体地，客户端收到目标服务节点发送的第二报文后，根据第二报文中的五元组信息识别该第二报文，确定该第二报文属于该第一连接。
本申请实施例对图2所示的连接建立方式所基于的通信协议不做具体限定，可以是新引入的通信协议，也可以对传统的协议的连接建立进行改造。下面以QUIC协议为例进行详细说明。
QUIC协议是一种基于UDP的低时延的互联网传输层协议。QUIC协议允许在建立连接后，在保证连接不断开的情况下，修改五元组中的信息，如五元组中的客户端和服务端的IP地址和端口号。但是，传统QUIC协议不允许在连接建立过程更改五元组中的信息，这样一来，在连接建立过程中以及连接建立后的初始阶段，网络侧仍需要维护客户端与目标服务节点之间的绑定关系，造成较大的网络开销。本申请实施例对QUIC协议的连接建立过程进行改进，以降低网络开销。
为了便于理解，本申请实施例对QUIC协议的握手通信过程进行简单介绍。
步骤一、客户端发送第一initial packet，该第一initial packet包括客户端确定的连接标识符connection ID’。此外，客户端在本地记录与第一initial packet有关的连接为第一连接。
步骤二、目标服务节点收到该第一initial packet后，根据实际情况，向客户端发送retry packet或第一handshake packet。
需要说明的是，上述retry packet或第一handshake packet携带目标服务节点的IP地址和/或端口号。此外，目标服务节点还可以将本节点确定的连接标识符connection ID携带在上述retry packet或第一handshake packet中。其中，上述第一initial packet的目的IP地址和/或端口号与目标服务节点的IP地址和/或端口号不同。
应理解，上述retry packet或第一handshake packet携带的connection ID可以与connection ID’相同，也可以不同，本申请实施例对此不做具体限定。
目标服务节点向客户端发送第一handshake packet后，在本地记录与该第一handshake  packet有关的连接为第一连接。
步骤三、当客户端收到目标服务节点发送的retry packet后，以目标服务节点的IP地址为目的地址，和/或目标服务节点的端口号为目的端口号，向目标服务节点发送第二initial packet重新进行连接建立。其中，该第二initial packet使用的连接标识符可以为任意连接标识符。作为一个示例，该第二initial packet使用的连接标识可以为connection ID或connection ID’。作为另一个示例，该第二initial packet使用的连接标识符可以为不同于connection ID和connection ID’的其他连接标识符。
可选地，客户端可以根据retry packet中的五元组信息，将该retry packet确定为第一连接内的报文。
当客户端收到目标服务节点发送的第一handshake packet后，以目标服务节点的IP地址为目的地址，向目标服务节点发送protected packet或第二handshake packet。其中，第二handshake packet所使用的连接标识符为connection ID，protected packet使用的连接标识符可以为connection ID’，也可以为connection ID。
步骤四、当目标服务节点收到客户端发送的第二initial packet后，可以根据实际情况，向客户端发送retry packet或handshake packet。
当目标服务节点收到客户端发送的protected packet或handshake packet后，根据protected packet或handshake packet中的五元组信息和/或连接标识符，确定该protected packet或handshake packet属于第一连接内的报文。此外，目标服务节点向客户端发送第四报文，第四报文的源地址为目标服务节点的IP地址，目的地址为客户端的IP地址，第四报文使用的连接标识符为connection ID。
步骤五、客户端收到第四报文后，会根据第四报文中的五元组信息和/或连接标识符来识别第四报文，确定第四报文属于第一连接内的报文。
上文结合图1至图5，详细描述了本申请的方法实施例，下面结合图6至图9，详细描述本申请的装置实施例。应理解，方法实施例的描述与装置实施例的描述相互对应，因此，未详细描述的部分可以参见前面方法实施例。
图6是本申请实施例提供的网络设备的示意性框图。该网络设备600包括第一接收单元610、第一发送单元620、第二接收单元630。
第一接收单元610，用于接收客户端发送的第一报文，第一报文的源地址为客户端的IP地址，第一报文的目的IP地址为服务端的IP地址。服务端的IP地址例如可以是服务端的前端IP地址，也可以是服务端向外界开放的、供外界访问该服务端时使用的其他IP地址。客户端例如可以通过DNS等手段查询到服务端的IP地址。
第一报文可以称为连接请求报文，第一报文例如可以是客户端向服务端发送的首报文。以QUIC为例，该第一报文可以为QUIC initial packet。
第一发送单元620，用于向客户端发送第二报文，该第二报文包括该网络设备的IP地址。
第二报文可以称为连接回复报文，第二报文例如可以是服务端向客户端发送的首报文。以QUIC协议为例，该第二报文可以是QUIC retry packet，或者也可以是QUIC handshake packet。
第二接收单元630，用于接收客户端发送的第三报文，该第三报文的目的地址为该网 络设备的IP地址。
客户端收到第二报文后，可以从该第二报文中提取网络设备的IP地址，并将网络设备的IP地址作为后续发送的第三报文的目的IP地址。
本申请实施例中的第三报文可以为QUIC protected packet、QUIC initial packet或QUIC handshake packet。其中，QUIC protected packet可以是数据报文。
由于第三报文的目的地址为该网络设备的IP地址，服务端可以直接将第三报文转发至该网络设备，无需像传统技术那样记录服务端与客户端之间的绑定关系，从而能够降低网络开销。
可选地，在一些实施例中，第二报文还可以包含目标服务节点的端口号。客户端可以目标服务节点的端口号为目的端口号，向目标服务节点发送第三报文。
具体地，第一报文的目的端口号为服务端的端口号，第二报文的目的端口号为客户端的端口号，第二报文还包括目标服务节点的端口号，第三报文的目的端口号为目标服务节点的端口号。
根据本申请实施例提供的方法，网络设备在发送的第二报文中，可以将本节点的端口号记录在该报文中。客户端在收到该第二报文后，将第三报文的目的端口号更改为网络设备的端口号，从而可以直接将第三报文路由至网络设备的准确端口位置，简化了处理流程。
可选地，本申请实施例中的第二报文可以是基于QUIC协议的报文。
如图7所示，本申请实施例还提供一种网络设备700。该网络设备700包括处理器710，存储器720与收发器730。该存储器720用于存储指令，该处理器710与收发器730用于执行该存储器720存储的指令。
应理解，图6所示的网络设备600或图7所示的网络设备700可用于执行上述方法实施例中相关的操作或流程，并且网络设备600或网络设备700中的各个单元的操作和/或功能分别为了实现上述方法实施例中的相应流程，为了简洁，在此不再赘述。
图8是本申请实施例提供的另一种网络设备的示意性框图。该网络设备800包括第一接收单元810、第一发送单元820、第二接收单元830。
第一发送单元810，用于发送第一报文，第一报文的源地址为客户端的IP地址，第一报文的目的IP地址为服务端的IP地址。服务端的IP地址例如可以是服务端的前端IP地址，也可以是服务端向外界开放的、供外界访问该服务端时使用的其他IP地址。客户端例如可以通过DNS等手段查询到服务端的IP地址。
第一报文可以称为连接请求报文，第一报文例如可以是网络设备向服务端发送的首报文。以QUIC为例，该第一报文可以为QUIC initial packet。
第一接收单元820，用于接收目标服务节点发送的第二报文，该第二报文包括该目标服务节点的IP地址。
第二报文可以称为连接回复报文，第二报文例如可以是服务端向网络设备发送的首报文。以QUIC协议为例，该第二报文可以是QUIC retry packet，或者也可以是QUIC handshake packet。
第二发送单元830，用于向目标服务节点发送第三报文，该第三报文的目的地址为该目标服务节点的IP地址。
网络设备收到第二报文后，可以从该第二报文中提取目标服务节点的IP地址，并将 目标服务节点的IP地址作为后续发送的第三报文的目的IP地址。
本申请实施例中的第三报文可以为QUIC protected packet、QUIC initial packet或QUIC handshake packet。其中，QUIC protected packet可以是数据报文。
由于第三报文的目的地址为目标服务节点的IP地址，服务端可以直接将第三报文转发至目标服务节点，无需像传统技术那样记录服务端与网络设备之间的绑定关系，从而能够降低网络开销。
可选地，在一些实施例中，第二报文还可以包含目标服务节点的端口号。网络设备可以目标服务节点的端口号为目的端口号，向目标服务节点发送第三报文。
具体地，第一报文的目的端口号为服务端的端口号，第二报文的目的端口号为客户端的端口号，第二报文还包括目标服务节点的端口号，第三报文的目的端口号为目标服务节点的端口号。
根据本申请实施例提供的方法，目标服务节点在发送的第二报文中，可以将本节点的端口号记录在该报文中。网络设备在收到该第二报文后，将第三报文的目的端口号更改为目标服务节点的端口号，从而可以直接将第三报文路由至目标服务节点的准确端口位置，简化了处理流程。
可选地，本申请实施例中的第二报文可以是基于QUIC协议的报文。
如图9所示，本申请实施例还提供一种网络设备900。该网络设备900包括处理器910，存储器920与收发器930。该存储器920用于存储指令，该处理器910与收发器930用于执行该存储器920存储的指令。
应理解，图8所示的网络设备800或图9所示的网络设备900可用于执行上述方法实施例中相关的操作或流程，并且网络设备800或网络设备900中的各个单元的操作和/或功能分别为了实现上述方法实施例中的相应流程，为了简洁，在此不再赘述。
应理解，本申请实施例中提及的处理器可以是中央处理单元(central processing unit，CPU)，还可以是其他通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
还应理解，本申请实施例中提及的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double dta rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。
需要说明的是，当处理器为通用处理器、DSP、ASIC、FPGA或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件时，存储器(存储模块)集成在处理器中。
应注意，本文描述的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (30)

  1. 一种发送报文的方法，其特征在于，包括：
    服务端的目标服务节点接收客户端发送的第一报文，所述第一报文的目的地址为所述服务端的互联网协议IP地址，所述服务端包括至少一个服务节点，所述目标服务节点为所述至少一个服务节点之一，所述服务端的IP地址与所述目标服务节点的IP地址不同；
    所述目标服务节点向所述客户端发送第二报文，所述第二报文包括所述目标服务节点的IP地址；
    所述目标服务节点接收所述客户端发送的第三报文，所述第三报文的目的地址为所述目标服务节点的IP地址。
  2. 根据权利要求1所述的方法，其特征在于，所述第一报文的目的端口号为所述服务端的端口号，所述第二报文的目的端口号为所述客户端的端口号，所述第二报文还包括所述目标服务节点的端口号，所述第三报文的目的端口号为所述目标服务节点的端口号。
  3. 根据权利要求1或2所述的方法，其特征在于，所述第二报文是基于快速用户数据报协议互联网连接QUIC协议的报文。
  4. 根据权利要求3所述的方法，其特征在于，所述第一报文为QUIC初始报文，所述第二报文为QUIC握手报文或QUIC重试报文。
  5. 根据权利要求1-4中任一项所述的方法，其特征在于，所述第一报文的源地址为所述客户端的IP地址，所述第二报文的源地址为所述服务端的IP地址，所述第二报文的目的地址为所述客户端的IP地址。
  6. 根据权利要求1-5中任一项所述的方法，其特征在于，所述客户端与所述目标服务节点建立的连接为第一连接，所述第二报文包括连接标识符，所述第三报文包括所述连接标识符，
    所述方法还包括：
    所述目标服务节点根据所述第三报文中的五元组信息和/或所述连接标识符，确定所述第三报文属于所述第一连接。
  7. 根据权利要求1-6所述的方法，其特征在于，所述方法还包括：
    所述目标服务节点向所述客户端发送第四报文，所述第四报文的源地址为所述目标服务节点的IP地址，所述第四报文的目的地址为所述客户端的IP地址。
  8. 一种发送报文的方法，其特征在于，包括：
    客户端发送第一报文，所述第一报文的目的地址为服务端的互联网协议IP地址；
    所述客户端接收所述服务端的目标服务节点发送的第二报文，所述第二报文包括所述目标服务节点的IP地址，所述服务端包括至少一个服务节点，所述目标服务节点为所述至少一个服务节点之一，且所述目标服务节点的IP地址与所述服务端的IP地址不同；
    所述客户端向所述目标服务节点发送第三报文，所述第三报文的目的地址为所述目标服务节点的IP地址。
  9. 根据权利要求8所述的方法，其特征在于，所述第一报文的目的端口号为所述服务端的端口号，所述第二报文的目的端口号为所述客户端的端口号，所述第二报文还包括 所述目标服务节点的端口号，所述第三报文的目的端口号为所述目标服务节点的端口号。
  10. 根据权利要求8或9所述的方法，其特征在于，所述第二报文是基于快速用户数据报协议互联网连接QUIC协议的报文。
  11. 根据权利要求10所述的方法，其特征在于，所述第一报文为QUIC初始报文，所述第二报文为QUIC握手报文或QUIC重试报文。
  12. 根据权利要求8-11中任一项所述的方法，其特征在于，所述第一报文的源地址为所述客户端的IP地址，所述第二报文的源地址为所述服务端的IP地址，所述第二报文的目的地址为所述客户端的IP地址。
  13. 根据权利要求8-12中任一项所述的方法，其特征在于，所述客户端与所述目标服务节点建立的连接为第一连接，所述方法还包括：
    所述客户端根据所述第二报文中的五元组信息，确定所述第二报文属于所述第一连接。
  14. 根据权利要求13所述的方法，其特征在于，所述第三报文包括连接标识符，所述方法还包括：
    所述客户端接收所述目标服务节点发送的第四报文，所述第四报文包括所述连接标识符；
    所述客户端根据所述第四报文中的五元组信息和/或所述连接标识符，确定所述第四报文属于所述第一连接。
  15. 一种网络设备，其特征在于，包括：
    第一接收单元，用于接收客户端发送的第一报文，所述第一报文的目的地址为服务端的互联网协议IP地址，所述服务端包括至少一个服务节点，所述网络设备为所述至少一个服务节点之一，所述服务端的IP地址与网络设备的IP地址不同；
    第一发送单元，用于向所述客户端发送第二报文，所述第二报文包括所述网络设备的IP地址；
    第二接收单元，用于接收所述客户端发送的第三报文，所述第三报文的目的地址为所述网络设备的IP地址。
  16. 根据权利要求15所述的网络设备，其特征在于，所述第一报文的目的端口号为所述服务端的端口号，所述第二报文的目的端口号为所述客户端的端口号，所述第二报文还包括网络设备的端口号，所述第三报文的目的端口号为所述网络设备的端口号。
  17. 根据权利要求15或16所述的网络设备，其特征在于，所述第二报文是基于快速用户数据报协议互联网连接QUIC协议的报文。
  18. 根据权利要求17所述的网络设备，其特征在于，所述第一报文为QUIC初始报文，所述第二报文为QUIC握手报文或QUIC重试报文。
  19. 根据权利要求15-18中任一项所述的网络设备，其特征在于，所述第一报文的源地址为所述客户端的IP地址，所述第二报文的源地址为所述服务端的IP地址，所述第二报文的目的地址为所述客户端的IP地址。
  20. 根据权利要求15-19中任一项所述的网络设备，其特征在于，所述客户端与所述目标服务节点建立的连接为第一连接，所述第二报文包括连接标识符，所述第三报文包括所述连接标识符，所述网络设备还包括：
    确定单元，用于根据所述第三报文中的五元组信息和/或所述连接标识符，确定所述第三报文属于所述第一连接。
  21. 根据权利要求15-20中任一项所述的网络设备，其特征在于，所述网络设备还包括：
    第二发送单元：用于向所述客户端发送第四报文，所述第四报文的源地址为所述目标服务节点的IP地址，所述第四报文的目的地址为所述客户端的IP地址。
  22. 一种网络设备，其特征在于，包括：
    第一发送单元，用于发送第一报文，所述第一报文的目的地址为服务端的互联网协议IP地址；
    第一接收单元，用于接收目标服务节点发送第二报文，所述第二报文包括所述目标服务节点的IP地址，所述服务端包括至少一个服务节点，所述目标服务节点为所述至少一个服务节点之一，且所述目标服务节点的IP地址与所述服务端的IP地址不同；
    第二发送单元，用于向所述目标服务节点发送第三报文，所述第三报文的目的地址为所述目标服务节点的IP地址。
  23. 根据权利要求22所述的网络设备，其特征在于，所述第二报文还包括目标服务节点的端口号，所述第三报文的目的端口号为所述目标服务节点的端口号。
  24. 根据权利要求22或23所述的网络设备，其特征在于，所述第二报文是基于快速用户数据报协议互联网连接QUIC协议的报文。
  25. 根据权利要求24所述的网络设备，其特征在于，所述第一报文为QUIC初始报文，所述第二报文为QUIC握手报文或QUIC重试报文。
  26. 根据权利要求22-25中任一项所述的网络设备，其特征在于，所述第一报文的源地址为所述客户端的IP地址，所述第二报文的源地址为所述服务端的IP地址，所述第二报文的目的地址为所述客户端的IP地址。
  27. 根据权利要求22-26中任一项所述的网络设备，其特征在于，所述客户端与所述目标服务节点建立的连接为第一连接，所述网络设备还包括：
    第一确定单元，用于根据所述第二报文中的五元组信息，确定所述第二报文属于所述第一连接。
  28. 根据权利要求27所述的网络设备，其特征在于，所述第三报文包括连接标识符，所述网络设备还包括：
    第二接收单元，用于接收所述目标服务节点发送的第四报文，所述第四报文包括所述连接标识符；
    第二确定单元，用于根据所述第四报文中的五元组信息和/或所述连接标识符，确定所述第四报文属于所述第一连接。
  29. 一种计算机可读存储介质，其特征在于，包括计算机指令，当所述计算机指令在计算机上运行时，使得所述计算机执行如权利要求1-7中任一项所述的方法。
  30. 一种计算机可读存储介质，其特征在于，包括计算机指令，当所述计算机指令在计算机上运行时，使得所述计算机执行如权利要求8-14中任一项所述的方法。
PCT/CN2019/077243 2018-03-09 2019-03-07 发送报文的方法、网络设备及计算机可读存储介质 WO2019170114A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP19763170.8A EP3758339A4 (en) 2018-03-09 2019-03-07 PROCEDURE FOR SENDING PACKAGES, NETWORK DEVICE AND COMPUTER READABLE STORAGE MEDIUM
US17/015,503 US11546259B2 (en) 2018-03-09 2020-09-09 Packet sending method, network device, and computer-readable storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810193364.4A CN110247848B (zh) 2018-03-09 2018-03-09 发送报文的方法、网络设备及计算机可读存储介质
CN201810193364.4 2018-03-09

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/015,503 Continuation US11546259B2 (en) 2018-03-09 2020-09-09 Packet sending method, network device, and computer-readable storage medium

Publications (1)

Publication Number Publication Date
WO2019170114A1 true WO2019170114A1 (zh) 2019-09-12

Family

ID=67846925

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/077243 WO2019170114A1 (zh) 2018-03-09 2019-03-07 发送报文的方法、网络设备及计算机可读存储介质

Country Status (4)

Country Link
US (1) US11546259B2 (zh)
EP (1) EP3758339A4 (zh)
CN (2) CN113824642B (zh)
WO (1) WO2019170114A1 (zh)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113596184B (zh) * 2020-04-30 2023-08-08 华为云计算技术有限公司 混合云系统、网闸、网络访问方法及存储介质
CN111901364A (zh) * 2020-08-17 2020-11-06 扬州网桥软件技术有限公司 一种防火墙穿透方法及系统
CN112333169B (zh) * 2020-10-28 2023-05-23 锐捷网络股份有限公司 一种报文处理方法、装置、电子设备及计算机可读介质
CN112653740A (zh) * 2020-12-11 2021-04-13 北京金山云网络技术有限公司 支持quic连接迁移的负载均衡方法、装置及计算机产品
CN112838966A (zh) * 2021-04-22 2021-05-25 北京拓课网络科技有限公司 一种udp链路监控方法、系统及电子设备
CN115801675A (zh) * 2021-09-09 2023-03-14 华为技术有限公司 一种报文处理方法及相关装置
CN114285805A (zh) * 2021-12-28 2022-04-05 赛尔网络有限公司 Quic报文过滤方法、系统、设备及介质
CN114500379A (zh) * 2022-02-18 2022-05-13 吉旗（成都）科技有限公司 报文的传输方法、装置、设备及存储介质
CN115361268A (zh) * 2022-08-19 2022-11-18 湖北天融信网络安全技术有限公司 重定向方法、装置、电子设备及计算机可读存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150256448A1 (en) * 2014-03-07 2015-09-10 Nicira, Inc. Method and system for path discovery
CN106330715A (zh) * 2015-06-30 2017-01-11 杭州华三通信技术有限公司 报文处理方法及装置
CN106878193A (zh) * 2017-02-10 2017-06-20 新华三技术有限公司 一种负载分担方法及装置

Family Cites Families (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7161947B1 (en) * 2002-07-30 2007-01-09 Cisco Technology, Inc. Methods and apparatus for intercepting control and data connections
US8230067B2 (en) * 2003-10-31 2012-07-24 Ericsson Ab DHCP proxy in a subscriber environment
US8145908B1 (en) * 2004-10-29 2012-03-27 Akamai Technologies, Inc. Web content defacement protection system
CN101697633B (zh) * 2009-11-10 2011-12-28 西安西电捷通无线网络通信股份有限公司 一种基于ip自适应的负载均衡方法及其系统
CN102075445B (zh) * 2011-02-28 2013-12-25 杭州华三通信技术有限公司 负载均衡方法及装置
US9026783B2 (en) 2013-03-07 2015-05-05 Google Inc. Low latency server-side redirection of UDP-based transport protocols traversing a client-side NAT firewall
WO2015088416A1 (en) * 2013-12-11 2015-06-18 Telefonaktiebolaget L M Ericsson (Publ) Proxy interception
US10412159B1 (en) * 2014-02-07 2019-09-10 Amazon Technologies, Inc. Direct load balancing using a multipath protocol
US9985896B2 (en) * 2014-03-31 2018-05-29 Nicira, Inc. Caching of service decisions
US9807016B1 (en) * 2015-09-29 2017-10-31 Juniper Networks, Inc. Reducing service disruption using multiple virtual IP addresses for a service load balancer
US9882972B2 (en) * 2015-10-30 2018-01-30 International Business Machines Corporation Packet forwarding optimization without an intervening load balancing node
CN107026890B (zh) * 2016-02-02 2020-10-09 华为技术有限公司 一种基于服务器集群的报文生成方法和负载均衡器
CN111866064B (zh) * 2016-12-29 2021-12-28 华为技术有限公司 一种负载均衡的方法、装置和系统
US10305973B2 (en) * 2017-01-09 2019-05-28 International Business Machines Corporation Distributed load-balancing for software defined networks
EP3364630A1 (en) * 2017-02-20 2018-08-22 Nokia Solutions and Networks Oy A method of distributing load and a network apparatus
US10298711B2 (en) * 2017-06-09 2019-05-21 Hewlett Packard Enterprise Development Lp Service function chains using correlation cookies
US10785020B2 (en) * 2018-01-19 2020-09-22 Microsoft Technology Licensing, Llc Hardware offload for QUIC connections

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150256448A1 (en) * 2014-03-07 2015-09-10 Nicira, Inc. Method and system for path discovery
CN106330715A (zh) * 2015-06-30 2017-01-11 杭州华三通信技术有限公司 报文处理方法及装置
CN106878193A (zh) * 2017-02-10 2017-06-20 新华三技术有限公司 一种负载分担方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3758339A4

Also Published As

Publication number Publication date
US11546259B2 (en) 2023-01-03
CN110247848B (zh) 2021-08-20
US20200403914A1 (en) 2020-12-24
EP3758339A1 (en) 2020-12-30
CN113824642A (zh) 2021-12-21
EP3758339A4 (en) 2021-04-21
CN110247848A (zh) 2019-09-17
CN113824642B (zh) 2023-02-03

Similar Documents

Publication Publication Date Title
WO2019170114A1 (zh) 发送报文的方法、网络设备及计算机可读存储介质
US9917914B2 (en) Facilitating content accessibility via different communication formats
US11277313B2 (en) Data transmission method and corresponding device
TWI437863B (zh) 異質性ｉｐｖ４網路中之同級間行動能力管理
WO2021042398A1 (zh) 一种通信方法及装置、网络设备、终端设备
JP3668047B2 (ja) 移動通信方法、移動計算機装置及び暗号化通信装置
US8725883B2 (en) Method for the establishing of peer-to-peer multimedia sessions in a communication system
WO2017143859A1 (zh) 数据传输方法、网络设备以及终端
WO2022033345A1 (zh) 一种pdu会话建立方法、终端设备和芯片系统
JP7502484B2 (ja) ネットワークアクセス方法、メディアゲートウェイ、電子機器及び記憶媒体
US20110087789A1 (en) Subscription based network routing tables and enforcement for overlay networks
WO2015169044A1 (zh) 一种漫游场景下的会话绑定方法、裝置和系统
WO2007019809A1 (fr) Procede et systeme d'etablissement d'un canal direct point par point
WO2021217869A1 (zh) 一种传递客户端真实ip地址的方法及系统
WO2014201600A1 (zh) 一种会话管理方法、地址管理方法及相关装置
WO2022042395A1 (zh) 确定业务服务器地址的方法和通信装置
WO2012041168A1 (zh) 用于IPv6网络的网络连接处理方法及其装置
JP2008516554A (ja) ダイレクトルーティングを実施する方法及び装置
WO2009062453A1 (fr) Procédé et appareil de fourniture d'informations utilisateur
WO2023116165A1 (zh) 网络负载均衡方法、装置、电子设备、介质和程序产品
WO2012088830A1 (zh) 一种通信方法、消息处理方法及系统
WO2022135132A1 (zh) 业务处理方法、装置、电子设备及存储介质
WO2011044810A1 (zh) 实现多方通信的方法、装置及系统
WO2015100748A1 (zh) 路由方法及路由装置
US11902052B1 (en) Separate PFCP session model for network access by residential gateways

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: 19763170

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2019763170

Country of ref document: EP

Effective date: 20200921