WO2022218194A1 - 服务路由方法及设备 - Google Patents

服务路由方法及设备 Download PDF

Info

Publication number
WO2022218194A1
WO2022218194A1 PCT/CN2022/085388 CN2022085388W WO2022218194A1 WO 2022218194 A1 WO2022218194 A1 WO 2022218194A1 CN 2022085388 W CN2022085388 W CN 2022085388W WO 2022218194 A1 WO2022218194 A1 WO 2022218194A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
request
computing platform
edge computing
domain name
Prior art date
Application number
PCT/CN2022/085388
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 中国移动通信有限公司研究院
Publication of WO2022218194A1 publication Critical patent/WO2022218194A1/zh

Links

Images

Classifications

    • 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
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/30—Managing network names, e.g. use of aliases or nicknames
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5007—Internet protocol [IP] addresses
    • H04L61/5014—Internet protocol [IP] addresses using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • 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/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming

Definitions

  • the present disclosure relates to the field of mobile communication technologies, and in particular, to a service routing method and device.
  • OTT is the abbreviation of "Over The Top”.
  • OTT is the abbreviation of "Over The Top”.
  • UDP-based low-latency Internet transport layer protocol Quick UDP Internet Connection, QUIC
  • the prior art proposes a service routing (Service Routing) technical solution, which introduces a new service routing address, and the service routing address includes a service routing prefix (Service Routing).
  • ID Prefix which is the prefix of an IPv6 address
  • the service routing address is also called a Service ID.
  • the solution is based on the service ID (Service ID) routing addressing.
  • Service ID service ID
  • the destination address of the message directly fills in the Service ID, which can eliminate the domain name server (Domain Name Service, DNS) query process.
  • DNS Domain Name Service
  • the service routing address is a new IPv6 address.
  • one idea is to go to the Internet Assigned Numbers Authority (IANA) to apply for a separate address space for this IPv6 address, which is used for service routing ( Service Routing), at this time, the same service routing prefix is used when accessing different mobile edge computing (Mobile Edge Computing, MEC), which can be understood as an anycast (anycast) address;
  • another idea is that the terminal is accessing Before the service, the Dynamic Host Configuration Protocol (DHCP) is used to obtain the service routing prefix. At this time, different service routing prefixes are used to access different MECs.
  • DHCP Dynamic Host Configuration Protocol
  • At least one embodiment of the present disclosure provides a service routing method and device, which can reduce service access delay and reduce service routing implementation complexity.
  • At least one embodiment provides a service routing method, comprising:
  • the terminal sends a first connection establishment request and a first domain name resolution request for the target service to the first edge computing platform, wherein the first connection establishment request is a service routing-based connection establishment request, and the first domain name resolution request is Domain name resolution request based on DNS protocol;
  • the first connection establishment request has successfully established a connection before receiving the feedback message of the first edge computing platform for the first domain name resolution request, the first connection established by the first connection establishment request Access the target service.
  • the method before sending the first connection establishment request and the first domain name resolution request for the target service to the first edge computing platform, the method further includes:
  • the terminal receives the first service routing prefix of the first edge computing platform sent by the session management function SMF of the core network .
  • sending the first connection establishment request includes: the terminal determines a service identifier corresponding to the target service, and generates a routing prefix that includes the first service and the service identifier. the first destination address, and send an access request for the first destination address.
  • the method further includes: the terminal receiving the first domain name resolution request from the first edge computing platform The feedback message, the feedback message carries the second destination address corresponding to the target service;
  • the terminal sends a second connection establishment request for the second destination address; and, using the first connection request and the second connection establishment request The first connection established in the connection request accesses the target service.
  • it also includes:
  • the terminal After sending the first domain name resolution request for the target service, the terminal further receives a service routing address corresponding to the target service returned by the first edge computing platform;
  • the terminal determines whether the service routing address corresponding to the target service matches the first destination address: if so, then Continue to access the target service through the first connection; otherwise, disconnect the first connection, establish the second connection through the second connection establishment request, and access the target service through the second connection target service.
  • the method when it is determined that the service routing address corresponding to the target service matches the first destination address, the method further includes:
  • connection establishment process of the second connection establishment request is canceled.
  • the first service routing prefix is specifically:
  • each local server of the first edge computing platform includes a first public network IPv6 address and a second public network IPv6 address respectively;
  • the receiving the first service routing prefix sent by the first edge computing platform is specifically:
  • At least one embodiment provides a service routing method, comprising:
  • the first edge computing platform receives the first connection establishment request and the first domain name resolution request for the target service sent by the terminal, wherein the first connection establishment request is a service route-based connection establishment request, and the first domain name resolution request For domain name resolution requests based on DNS protocol;
  • the first edge computing platform establishes a first connection with the terminal according to the first connection establishment request, and obtains, according to the first domain name resolution request, the first parsed corresponding to the target service. Second destination address, sending a feedback message for the first domain name resolution request to the terminal, where the feedback message carries the second destination address.
  • the first connection establishment request is an access request for a first destination address
  • the first destination address includes a first service route of the first edge computing platform.
  • the method further includes:
  • a second connection establishment request for the second destination address sent by the terminal is received.
  • it also includes:
  • the target service is provided for the terminal by using the connection established first in the first connection request and the second connection request.
  • it also includes:
  • the first edge computing platform When sending the feedback message for the first domain name resolution request to the terminal, the first edge computing platform also sends the service routing address corresponding to the target service.
  • At least one embodiment provides a service routing method, comprising:
  • the session management function SMF of the core network sends the first service routing prefix of the first edge computing platform to the terminal in the process of establishing a session between the terminal and the user plane function of the first edge computing platform.
  • the first service routing prefix is specifically:
  • each local server of the first edge computing platform includes a first public network IPv6 address and a second public network IPv6 address respectively;
  • the sending the first service routing prefix of the first edge computing platform to the terminal is specifically:
  • the first service routing prefix is carried in the PDU session modification command or the PDU session establishment accept message and sent to the terminal.
  • At least one embodiment provides a terminal, comprising:
  • a sending module configured to send a first connection establishment request and a first domain name resolution request for the target service to the first edge computing platform, wherein the first connection establishment request is a service routing-based connection establishment request, and the first The domain name resolution request is a domain name resolution request based on the DNS protocol;
  • a service access module configured to: if the first connection establishment request has successfully established a connection before receiving the feedback message of the first edge computing platform for the first domain name resolution request, then pass the first connection The first connection requested to be established is established to access the target service.
  • At least one embodiment provides a terminal including a transceiver and a processor, wherein,
  • the transceiver is configured to send a first connection establishment request and a first domain name resolution request for the target service to the first edge computing platform, wherein the first connection establishment request is a service routing-based connection establishment request, and the The first domain name resolution request is a domain name resolution request based on the DNS protocol;
  • the processor is configured to, if the first connection establishment request has successfully established a connection before receiving the feedback message of the first edge computing platform for the first domain name resolution request, pass the first connection The first connection requested to be established is established to access the target service.
  • At least one embodiment provides a terminal including: a processor, a memory, and a program stored on the memory and executable on the processor, the program being processed by the processor.
  • At least one embodiment provides a first edge computing platform, comprising:
  • a receiving module configured to receive a first connection establishment request and a first domain name resolution request for a target service sent by the terminal, wherein the first connection establishment request is a service route-based connection establishment request, and the first domain name resolution request For domain name resolution requests based on DNS protocol;
  • a response module configured to establish a first connection with the terminal according to the first connection establishment request, and obtain a second purpose corresponding to the target service obtained by resolution according to the first domain name resolution request address, and send a feedback message for the first domain name resolution request to the terminal, where the feedback message carries the second destination address.
  • At least one embodiment provides a first edge computing platform including a transceiver and a processor, wherein,
  • the transceiver is configured to receive a first connection establishment request and a first domain name resolution request for the target service sent by the terminal, wherein the first connection establishment request is a service routing-based connection establishment request, and the first domain name
  • the resolution request is a domain name resolution request based on the DNS protocol;
  • the processor is configured to establish a first connection with the terminal according to the first connection establishment request, and, according to the first domain name resolution request, obtain the first parsed corresponding to the target service. Second destination address, sending a feedback message for the first domain name resolution request to the terminal, where the feedback message carries the second destination address.
  • At least one embodiment provides a first edge computing platform, comprising: a processor, a memory, and a program stored on the memory and executable on the processor, the program The steps of the method as described above are implemented when executed by the processor.
  • At least one embodiment provides a session management function of a core network, including:
  • the sending module is configured to send the first service routing prefix of the first edge computing platform to the terminal during the process of establishing the session between the terminal and the user plane function of the first edge computing platform.
  • At least one embodiment provides a session management function of a core network, including a transceiver and a processor, wherein,
  • the transceiver is configured to send the first service routing prefix of the first edge computing platform to the terminal during the process of establishing the session between the terminal and the user plane function of the first edge computing platform.
  • At least one embodiment provides a session management function of a core network, including: a processor, a memory, and a program stored on the memory and executable on the processor, the A program, when executed by the processor, implements the steps of the method as described above.
  • At least one embodiment provides a computer-readable storage medium, where a program is stored on the computer-readable storage medium, and when the program is executed by a processor, the above-mentioned method is implemented. step.
  • the service routing method and device provided by the embodiments of the present disclosure can use two requests to request to establish a connection with the target service, and use the connection successfully established first to access the target service, so that the The complex conflict detection and processing mechanism of the prior art is avoided, the implementation complexity of the service routing is reduced, and the access delay of the service can be reduced.
  • FIG. 1 is a schematic flowchart of the prior art service routing on the terminal side
  • FIG. 2 is a schematic flowchart of the prior art service routing on the network side
  • Fig. 6 is an example diagram of MEC service access when service routing is not introduced
  • FIG. 7 is a diagram of an example application of the service routing method according to an embodiment of the present disclosure.
  • FIG. 8 is a diagram of another application example of the service routing method according to an embodiment of the present disclosure.
  • FIG. 9 is a diagram of another application example of the service routing method according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic structural diagram of a terminal provided by an embodiment of the present disclosure.
  • FIG. 11 is another schematic structural diagram of a terminal provided by an embodiment of the present disclosure.
  • FIG. 12 is a schematic structural diagram of a first edge computing platform provided by an embodiment of the present disclosure.
  • FIG. 13 is another schematic structural diagram of a first edge computing platform provided by an embodiment of the present disclosure.
  • FIG. 14 is a schematic structural diagram of a session management function provided by an embodiment of the present disclosure.
  • FIG. 15 is another schematic structural diagram of a session management function provided by an embodiment of the present disclosure.
  • a service routing method in the prior art, in the solution flow, includes notification of user side information and service side information notification.
  • the terminal obtains information such as client (client) address and service routing prefix through the extended DHCP protocol; the server side and the network side can configure the node control plane and modify the forwarding table through the customized UDP protocol.
  • client client address and service routing prefix
  • server side and the network side can configure the node control plane and modify the forwarding table through the customized UDP protocol.
  • the process on the terminal side is shown in Figure 1, including:
  • the DHCP client (DHCP client) of the terminal actively initiates a discovery/request (discover/request) to the DHCP server (DHCP server).
  • the DHCP client After the DHCP client obtains the above address, it saves the service routing prefix and hash algorithm locally.
  • the DHCP client periodically sends a request to request a hash conflict list from the DHCP server Ext.
  • the DHCP ACK message returned by the DHCP server Ext contains a hash conflict list in the option field.
  • the content of the list supports fragmentation and can be sent in multiple ACKs.
  • the DHCP server Ext receives the reported URL_1, URL_2, serviceID_1, takes out a value serviceID_2 from the candidate database, and assigns it to one of the URL_2; returns the hash assignment result URL_2/serviceID_2 to the ServerID Server;
  • the DHCP server Ext records the URL_2/serviceID_2 locally and records it into the hash conflict list.
  • the server side sends out a protocol packet for publishing the ServiceID route.
  • the router receives the packet and sends the packet to the control plane for processing:
  • the router regularly maintains the connection state of the interface with the server, the connection state is valid, and all routes received from the interface are valid.
  • Service Routing is a new routing technology solution, which may be enabled in the public network (large network) in the future (for BGP anycast). This technology believes that in large networks, Service Routing supports service-aware routing based on service IDs (Service ID), and can support comprehensive service information and path information for routing decisions. Service routing may be applied in a limited domain (limited domain) first, such as MEC, which is beneficial to avoid the problem of more complex hash (HASH) collisions (because there will be fewer collisions).
  • MEC limited domain
  • HASH complex hash
  • the embodiments of the present disclosure provide a service routing method, which can reduce the implementation complexity of service routing, make the routing mechanism more lightweight, and facilitate implementation in existing networks.
  • the embodiment of the present disclosure avoids the processing of hash (HASH) conflict, and supports returning to the default DNS mechanism if a conflict occurs, so that optimal service experience can be provided only in some key/main scenarios.
  • the terminal can initiate a request according to two mechanisms at the same time (a connection establishment request based on service routing, and a domain name resolution request based on DNS protocol). On the premise that HASH is correctly hit, usually a connection request based on service routing will first establish a connection .
  • the solution in the embodiment of the present disclosure can also be considered as a configuration method of an IPv6 address in the MEC site, that is, the service routing prefix is enabled as the address of the MEC (used for routing) That is, the service routing prefix is set as the public prefix of the service of the MEC, so that in different MECs, the terminal can use the same HASH algorithm to obtain the corresponding service address and realize fast access.
  • a service routing method provided by an embodiment of the present disclosure, when executed by a terminal, includes:
  • Step 31 The terminal sends a first connection establishment request and a first domain name resolution request for the target service to the first edge computing platform, wherein the first connection establishment request is a service routing-based connection establishment request, and the first domain name
  • the resolution request is a domain name resolution request based on the DNS protocol.
  • the embodiment of the present disclosure will initiate two requests when requesting a target service, which specifically includes: a first connection establishment request based on service routing, and a domain name resolution request based on DNS protocol.
  • a target service which specifically includes: a first connection establishment request based on service routing, and a domain name resolution request based on DNS protocol.
  • the embodiment of the present disclosure not only sends one request for the target service, but sends two requests, wherein the domain name resolution request is used to obtain the IP address corresponding to the target service (No. second destination address), and then a second connection establishment request may be initiated according to the obtained IP address corresponding to the target service.
  • the service name of the target service may be a certain domain name, such as local-weather.com.
  • the terminal when sending the first connection establishment request for the target service, the terminal may send the service route corresponding to the target service address access request; when sending the first domain name resolution request, a domain name resolution request for the target service may be sent to request the IP address corresponding to the domain name of the target service.
  • Step 32 If the first connection establishment request has successfully established a connection before receiving the feedback message of the first edge computing platform for the first domain name resolution request, then the first connection establishment request establishes a connection through the first connection establishment request. The first connection accesses the target service.
  • the terminal After initiating the above two requests, if the first connection establishment request has successfully established a connection before receiving the feedback of the first domain name resolution request, the terminal establishes the connection through the first connection establishment request at this time. The first connection accesses the target service. Subsequently, if the terminal receives the feedback of the first domain name resolution request, the terminal may give up initiating the second connection establishment request.
  • the terminal in the embodiment of the present disclosure will initiate two requests in step 31 when requesting the target service. Enter the target service, and give up initiating the second connection establishment request.
  • the embodiments of the present disclosure can request to establish a connection with the target service using two requests, and use the connection successfully established first to access the target service.
  • the conflict detection process in the prior art may not be performed, but the domain name resolution request that has been initiated before is used to continue to establish a second connection to access the target service. Therefore, , the embodiment of the present disclosure can avoid the complex conflict detection and processing mechanism in the prior art, reduce the implementation complexity of service routing, and reduce service access delay.
  • the terminal before step 31, in the process of establishing or modifying the session with the user plane function of the first edge computing platform, the terminal receives the message sent by the session management function SMF of the core network.
  • the first service routing prefix of the first edge computing platform may be carried in a PDU session modification command or a PDU session establishment accept message.
  • the terminal may determine the service identifier (Service ID) corresponding to the target service, generate a first destination address (service routing address) including the first service routing prefix, and then send a message for the target service.
  • the access request of the first destination address For example, perform hash calculation on the service name corresponding to the target service (for example, the service name is local-weather.com), and obtain the service ID (Service ID) corresponding to the target service, that is, the last few digits of the first destination address, which are the same as those of the first destination address.
  • a service routing prefix is combined to obtain the first destination address.
  • the first edge computing platform After the terminal sends the first domain name resolution request in the above step 31, the first edge computing platform obtains the IP address (second destination address) corresponding to the domain name of the target service according to the first domain name resolution request and returns it through a feedback message to the terminal.
  • the terminal receives a feedback message from the first edge computing platform to the first domain name resolution request, where the feedback message carries a second destination address corresponding to the target service. If the first connection establishment request has not successfully established a connection when receiving the feedback message, the terminal sends a second connection establishment request for the second destination address; and, using the first connection request and the second connection establishment request The first connection established in the connection request accesses the target service.
  • the first service routing prefix may be any of the following:
  • the prefix of the first public network IPv6 address of the local server of the first edge computing platform, wherein each local server of the first edge computing platform includes a first public network IPv6 address and a second public network IPv6 address respectively address, the first public network IPv6 address and the second public network IPv6 address of each local server may be the same or different.
  • the prefixes of the first public network IPv6 addresses of all local servers may be the same.
  • the IP address corresponding to the domain name of the target service obtained by the first edge computing platform according to the first domain name resolution request above is the second public IPv6 address of the local server providing the target service.
  • the prefix of the private network IPv6 address of the local server of the first edge computing platform is an IPv6 unique local address (Unique Local IPv6 Unicast Address, ULA).
  • the ULA address is the unique local unicast address of IPv6 (Unique Local IPv6 Unicast Address), which is used exclusively for the internal network. If the source IP or destination IP address of the data packet is an address within this address range, it cannot be used in the public domain. forwarded online.
  • IPv6 Unicast Address
  • the prefixes of the private network IPv6 addresses of all local servers of the first edge computing platform are the same.
  • the first edge computing platform may further feed back the service routing address corresponding to the target service to the terminal when requesting to feed back the second destination address for the first domain name, so that the terminal can perform the processing. Verification of service routing addresses.
  • the terminal may also receive a service routing address corresponding to the target service returned by the first edge computing platform.
  • the terminal can determine the service routing address corresponding to the target service (that is, the target service returned by the first edge computing platform). Whether the corresponding service routing address) matches the first destination address:
  • the first connection is disconnected, the second connection is established through the second connection establishment request, and the target service is accessed through the second connection.
  • the terminal may also cancel the connection establishment process of the second connection establishment request.
  • the terminal may also establish a second connection through a second connection establishment request.
  • the terminal accesses the target service through the second connection established by the second connection establishment request.
  • the terminal may also cancel the subsequent process of the first connection establishment request.
  • SR Session Routing
  • IPv6 Segment Routing based on IPv6
  • the service routing method according to the embodiment of the present disclosure when applied to the first edge computing platform side, includes:
  • Step 41 The first edge computing platform receives the first connection establishment request and the first domain name resolution request for the target service sent by the terminal, wherein the first connection establishment request is a service routing-based connection establishment request, and the first The domain name resolution request is a domain name resolution request based on the DNS protocol.
  • the first connection establishment request is an access request for a first destination address, where the first destination address includes a first service routing prefix of the first edge computing platform and a service identifier corresponding to the target service.
  • the service identifier may be obtained by hashing the service name of the target service.
  • the first service routing prefix may be any of the following:
  • the prefix of the first public network IPv6 address of the local server of the first edge computing platform, wherein each local server of the first edge computing platform includes a first public network IPv6 address and a second public network IPv6 address respectively address, the first public network IPv6 address and the second public network IPv6 address of each local server may be the same or different.
  • the prefixes of the first public network IPv6 addresses of all local servers may be the same.
  • the IP address corresponding to the domain name of the target service obtained by the first edge computing platform according to the first domain name resolution request above is the second public IPv6 address of the local server providing the target service.
  • the prefix of the private network IPv6 address of the local server of the first edge computing platform is an IPv6 unique local address ULA address.
  • the prefixes of the private network IPv6 addresses of all the local servers of the first edge computing platform are the same.
  • Step 42 the first edge computing platform establishes a first connection with the terminal according to the first connection establishment request, and obtains the target service obtained by resolution according to the first domain name resolution request.
  • the corresponding second destination address sends a feedback message for the first domain name resolution request to the terminal, where the feedback message carries the second destination address.
  • the first edge computing platform may obtain the second destination address corresponding to the domain name of the target service obtained by resolution according to the first domain name resolution request, and send the request to the The terminal sends the second destination address.
  • domain name resolution may be performed by a DNS server in the first edge computing platform.
  • the terminal sends the two requests in step 41 when requesting the target service, and the first edge computing platform responds to the above requests, establishes the first connection between the terminal and the target service, and feeds back the second destination address.
  • the embodiment of the present disclosure provides the target service for the terminal through the first connection, so that the embodiment of the present disclosure can use two requests to establish the connection , and use the connection that was successfully established first to provide the target service.
  • the conflict detection process in the prior art may not be performed, but a domain name resolution request initiated before is used to establish a second connection to access the target service. Therefore, the embodiment of the present disclosure may The complex conflict detection and processing mechanism of the prior art is avoided, the implementation complexity of the service routing is reduced, and the access delay of the service can be reduced.
  • the first edge computing platform may also receive a second connection establishment request sent by the terminal for the second destination address, and then establish the terminal in response to the second connection establishment request.
  • a second connection to the target service is provided for the terminal by using the connection (may be the first connection or the second connection) established first in the first connection request and the second connection request.
  • the first edge computing platform when sending the feedback message for the first domain name resolution request to the terminal, the first edge computing platform also sends the service routing address corresponding to the target service to provide Verifying the service routing address for the terminal.
  • the service routing method according to the embodiment of the present disclosure when applied to the session management function (SMF) of the core network, includes:
  • Step 51 the session management function SMF of the core network, in the process of establishing the session between the terminal and the user plane function of the first edge computing platform, sends the first service routing prefix of the first edge computing platform to the terminal .
  • the SMF may carry the first service routing prefix in the PDU session modification command or the PDU session establishment accept message and send it to the terminal.
  • 5GC represents the 5G core network
  • 5GC-CP represents the control of the 5G core network. face, including the following situations 61 to 63:
  • the UE accesses the 5G network and establishes a session to the data plane of the User Plane Function (UPF) of the 5G Core Network (5GC). If it accesses local-weather.com, it needs to perform DNS resolution to obtain an IP address. For example, ABCD::0123:4567, and then access the corresponding server (Web Server) according to the IP address to obtain the service.
  • UPF User Plane Function
  • 5GC 5G Core Network
  • the UE accesses the edge computing platform 1 (MEC1). Under the control of the 5GC, a session between the UE and the UPF of the MEC1 is established. When accessing local-weather.com, it needs to perform local DNS resolution to obtain an IP address, such as AAAA ::9876:4567, and then access the corresponding server (Cache Server) according to the IP address to obtain the service. At this time, because the MEC1 is closer to the UE, there is a certain effect of low latency.
  • MEC1 edge computing platform 1
  • the UE accesses the MEC2, and under the control of the 5GC, establishes a session to the UPF of the MEC2. Assuming that the UE still accesses local-weather.com, it needs to perform local DNS resolution first to obtain the IP address, such as BBBB::4534:4567, and then access the corresponding server (Cache Server) according to the IP address to obtain the service.
  • the IP address such as BBBB::4534:4567
  • the MEC service access situation after the introduction of Service Routing includes:
  • the UE accesses the 5G network and establishes a session to the data plane of the UPF of the 5GC. If the UE accesses local-weather.com, it needs to perform DNS resolution to obtain an IP address, such as ABCD::0123:4567, and then access the server. to obtain services.
  • IP address such as ABCD::0123:4567
  • the UE accesses the MEC1, establishes a session to the UPF of the MEC1 under the control of the 5GC, and obtains a Service Routing prefix during the session establishment/modification process, such as AAAA:A100::/64.
  • the MEC1 needs to advertise the IPv6 prefix in the network, that is, the service of the MEC1 can be accessed by both addresses.
  • One of them is the traditional IPv6 address (the second public network IPv6 address above), and the other is the address of Service Routing (the first public network IPv6 address above).
  • the two addresses can also be the same (but according to the latter format).
  • the local DNS can return two addresses, such as BBBB::4534:4567, BBBB:B200::0001, for verification (the current DNS protocol needs to be extended at this time, and the second Description of each address and one Service Routing address.
  • HASH conflicts such as when there are many local services
  • SR access for more important services can be enabled, and the HASH algorithm on both sides can also be considered to be updated (the new algorithm may make this HASH conflict disappears).
  • Initiate DNS resolution local DNS resolves to an address, such as AAAA::9876:4567, and then the UE accesses the corresponding server according to the address.
  • the UE directly initiates service access according to the format of the service routing address of ⁇ SR Prefix:Hashvalue>, such as AAAA:A100::0001
  • the UE accesses the MEC2, establishes a session with the UPF of the MEC2 under the control of the 5GC, and obtains a Service Routing prefix, BBBB:B200::/64, when the session is established/modified.
  • the UE accesses local-weather.com and initiates two connection establishment procedures at the same time.
  • a) Initiate DNS resolution local DNS resolves to the address, such as BBBB::4534:4567, and then access the corresponding server according to the address.
  • the local DNS resolution can optionally return the above two addresses, such as BBBB::4534:4567, BBBB:B200::0001, for verification (this When you need to extend the current DNS protocol, give the following address a description)
  • 3GPP Extended Protocol configuration options can be used to exchange some protocol configuration parameters.
  • This embodiment of the present disclosure can extend an unoccupied field, for example, similar to the design in the DNS server, the following new field is designed: 0033H (Service-routing IPv6 Prefix), so that it can be carried in the PDU session modification command or the PDU session establishment accept command Service routing prefix.
  • 0033H Service-routing IPv6 Prefix
  • the PDU session establishment/modification successful message can carry some information to the UE.
  • ePCO options it is carried by the above-mentioned new extension field 0033H.
  • the MEC node has two sets of public network IPv6 addresses (or one set, but the set of Service Routing prefixes needs to be accommodated), that is, it is assumed that the MEC has many IPv6 addresses with the same prefix (corresponding to each set of IPv6 addresses in the MEC node). service), so that it can be accessed directly according to the HASH algorithm.
  • Example 2 it is no longer assumed that the MEC node has a set of network-wide routable service routing prefix addresses, but it is assumed that the local server of the MEC has a set of ULA addresses (Unique Local IPv6 Unicast Addresses), which can be accessed directly according to the HASH algorithm.
  • ULA addresses are valid only within the MEC and are routable.
  • the ULA address is an IPv6 address defined by the IETF, similar to the private network address of 10.1.*.* in IPv4, and is used for local communication.
  • the characteristics of ULA addresses are that they are locally valid, do not need to be published, and have a large address space, but all services are required to be within the MEC.
  • the ULA address helps the existing MEC to route over to the support service (no need to configure more multiple public addresses).
  • the UE accesses the 5G network and establishes a session to the data plane of the UPF of the 5GC. If it accesses local-weather.com, it needs to perform DNS resolution to the address, such as ABCD::0123:4567, and then access the server to obtain the service.
  • the UE accesses the MEC1, establishes a session with the UPF of the MEC1 under the control of the 5GC, and obtains a Service Routing prefix when the session is established/modified, FDAA:A100:1000:0001::/64.
  • the MEC does not need to advertise this IPv6 prefix in the external network, but within the MEC, both addresses of the MEC service can be accessed, one is the traditional IPv6 address and the other is the address of Service Routing. At this time, the two addresses different.
  • the UE accesses local-weather.com and initiates two connection establishment procedures at the same time.
  • the UE initiates DNS resolution, the local DNS resolves to an address, such as AAAA::9876:4567, and then the UE accesses the corresponding server according to the address.
  • an address such as AAAA::9876:4567
  • the UE directly initiates service access according to ⁇ SR Prefix:Hashvalue>, such as FDAA:A100:1000:0001::0001.
  • the UE accesses the MEC2, establishes a session with the UPF of the MEC2 under the control of the 5GC, and obtains a prefix of Service Routing in the process of establishing/modifying the PDU session, assuming FDAA:A100:1000: 0002::/64.
  • the UE accesses local-weather.com and initiates two connection establishment procedures at the same time.
  • a) Initiate DNS resolution local DNS resolves to the address, such as BBBB::4534:4567, and then access the corresponding server according to the address.
  • local DNS resolution can return two addresses, such as BBBB::4534:4567, FDAA:A100:1000:0002::0001, the latter is used for verification, for example, the connection has been initiated through At this time, the response of method a is obtained. If there is FDAA:A100:1000:0002::0001 in the response, the UE thinks that its fast connection address is OK, and continues to interact without making any changes. If not, Then it is judged whether the interacting object may be incorrect, and the connection can be initiated using BBBB::4534:4567 instead.
  • SRv6 address can be represented by a segment ID (Segment ID, SID). SID usually includes three parts: location identifier (Locator), function (Function) and variable (Args).
  • SRv6 addresses valid only inside the MEC, are routable. At this time, the Locator parts of these SRv6 addresses are the same. Therefore, to a certain extent, the SRv6 address can be considered to be similar to the LOC in SRv6, that is, the FUNCT architecture (Locator: FUNCTION).
  • MEC is a virtual large node
  • the IPv6 Prefix of Service Routing corresponds to LOC
  • FUNCT corresponds to a specific service.
  • the UE accesses the 5G network and establishes a session to the data plane of the UPF of the 5GC. If it accesses local-weather.com, it needs to perform DNS resolution to the address, such as ABCD::0123:4567, then access the server, and then access the server to obtain the service.
  • DNS resolution to the address, such as ABCD::0123:4567
  • the UE accesses MEC1, and establishes a session with the UPF of MEC1 under the control of 5GC.
  • MEC1 Mobility Management Entity
  • the MEC does not need to advertise this IPv6 prefix in the external network, but within the MEC, both addresses of the MEC service can be accessed, one is the traditional IPv6 address and the other is the address of Service Routing. At this time, the two addresses will not be the same.
  • Initiate DNS resolution local DNS resolves to an address, such as AAAA::9876:4567, and then the UE accesses the corresponding server according to the address.
  • the UE accesses MEC2, and under the control of 5GC, establishes a session to the UPF of MEC2, and obtains a Service Routing prefix (also a SRv6 Locator) when the session is established/modified, B1:0001::/64 .
  • a Service Routing prefix also a SRv6 Locator
  • the UE accesses local-weather.com and initiates two connection establishment procedures at the same time.
  • a) Initiate DNS resolution local DNS resolves to the address, such as BBBB::4534:4567, and then access the corresponding server according to the address.
  • the embodiment of the present disclosure implements a lightweight service routing technical solution for MEC.
  • This solution does not require the large network to perceive Service Routing routes, and does not require a custom UDP protocol to advertise Routing, for example, within the MEC, the gateway can communicate directly according to the IPv6 address, and this solution does not need to deal with the complex HASH conflict problem.
  • this solution can notify the IPv6 prefix of Service Routing services through 3GPP signaling, and does not need to extend the DHCP protocol.
  • the SR fast access of the service can also be enabled. .
  • the HASH address can be directly used to access the MEC content, so that the DNS resolution can be returned to a simple configuration.
  • an embodiment of the present disclosure provides a terminal, including:
  • a sending module 1001 is configured to send a first connection establishment request and a first domain name resolution request for a target service to a first edge computing platform, wherein the first connection establishment request is a service routing-based connection establishment request, and the first connection establishment request is a service routing-based connection establishment request.
  • a domain name resolution request is a domain name resolution request based on the DNS protocol;
  • the service access module 1002 is configured to, if the first connection establishment request has successfully established a connection before receiving the feedback message of the first edge computing platform for the first domain name resolution request, pass the first The first connection established by the connection establishment request accesses the target service.
  • the terminal further includes:
  • the first receiving module is configured to, before sending the first connection establishment request and the first domain name resolution request for the target service to the first edge computing platform, between establishing or modifying the user plane function of the first edge computing platform During the session, the first service routing prefix of the first edge computing platform sent by the session management function SMF of the core network is received.
  • the sending module 1001 is further configured to determine a service identifier corresponding to the target service, generate a first destination address including the first service routing prefix and the service identifier, and send a message for the first destination. address of the access request.
  • the terminal further includes:
  • the second receiving module is configured to, after sending the first domain name resolution request, receive a feedback message from the first edge computing platform to the first domain name resolution request, where the feedback message carries the corresponding information of the target service the secondary destination address;
  • the service access module 1002 is further configured to send a second connection establishment request for the second destination address if the first connection establishment request has not successfully established a connection when the feedback message is received; and , using the connection established first in the first connection request and the second connection request to access the target service.
  • the first service routing prefix is specifically:
  • each local server of the first edge computing platform includes a first public network IPv6 address and a second public network IPv6 address respectively;
  • the terminal further includes:
  • a third receiving module configured to further receive a service routing address corresponding to the target service returned by the first edge computing platform after sending the first domain name resolution request for the target service;
  • the service access module 1002 is further configured to determine whether the service routing address corresponding to the target service is the same as the first connection establishment request when the first connection establishment request successfully establishes a connection prior to the second connection establishment request. A destination address match: if yes, continue to access the target service through the first connection; otherwise, disconnect the first connection, establish the second connection through the second connection establishment request, and use the The second connection accesses the target service.
  • the service access module 1002 is further configured to cancel the connection establishment process of the second connection establishment request when it is determined that the service routing address corresponding to the target service matches the first destination address .
  • the first receiving module is further configured to receive the first service routing prefix carried by the first edge computing platform in the PDU session modification command or the PDU session establishment accept message.
  • the device in this embodiment is a device corresponding to the method shown in FIG. 3 above, and the implementation manners in each of the above embodiments are applicable to the embodiments of the device, and the same technical effect can also be achieved.
  • the above-mentioned device provided by the embodiment of the present disclosure can realize all the method steps realized by the above-mentioned method embodiment, and can achieve the same technical effect, and the parts and beneficial effects that are the same as the method embodiment in this embodiment will not be described in detail here. Repeat.
  • FIG. 11 is a schematic structural diagram of a terminal provided by an embodiment of the present disclosure.
  • the terminal includes: a processor 1101 , a transceiver 1102 , a memory 1103 , a user interface 1104 and a bus interface.
  • the terminal further includes: a program stored on the memory 1103 and executable on the processor 1101.
  • the processor 1101 implements the following steps when executing the program:
  • first connection establishment request is a service routing-based connection establishment request
  • first domain name resolution request is based on DNS protocol domain name resolution request
  • the first connection establishment request has successfully established a connection before receiving the feedback message of the first edge computing platform for the first domain name resolution request, the first connection established by the first connection establishment request Access the target service.
  • the processor further implements the following steps when executing the program:
  • the processor further implements the following steps when executing the program:
  • a service identifier corresponding to the target service is determined, a first destination address including the first service routing prefix and the service identifier is generated, and an access request for the first destination address is sent.
  • the processor further implements the following steps when executing the program:
  • connection establishment request has not successfully established a connection when the feedback message is received, sending a second connection establishment request for the second destination address; and, using the first connection request and the second connection request The connection that is first established in the service is connected to the target service.
  • the first service routing prefix is specifically:
  • the processor further implements the following steps when executing the program:
  • the first connection establishment request succeeds in establishing a connection prior to the second connection establishment request, determine whether the service routing address corresponding to the target service matches the first destination address: if so, continue to pass the The first connection is used to access the target service; otherwise, the first connection is disconnected, the second connection is established through the second connection establishment request, and the target service is accessed through the second connection.
  • the processor further implements the following steps when executing the program:
  • connection establishment process of the second connection establishment request is canceled.
  • the processor further implements the following steps when executing the program:
  • the bus architecture may include any number of interconnected buses and bridges, in particular one or more processors represented by processor 1101 and various circuits of memory represented by memory 1103 linked together.
  • the bus architecture may also link together various other circuits, such as peripherals, voltage regulators, and power management circuits, which are well known in the art and, therefore, will not be described further herein.
  • the bus interface provides the interface.
  • Transceiver 1102 may be a number of elements, including a transmitter and a receiver, that provide a means for communicating with various other devices over a transmission medium.
  • the user interface 1104 may also be an interface capable of externally connecting the required equipment, and the connected equipment includes but is not limited to a keypad, a display, a speaker, a microphone, a joystick, and the like.
  • the processor 1101 is responsible for managing the bus architecture and general processing, and the memory 1103 may store data used by the processor 1101 in performing operations.
  • the device in this embodiment is a device corresponding to the method shown in FIG. 3 above, and the implementation manners in each of the above embodiments are applicable to the embodiments of the device, and the same technical effect can also be achieved.
  • the transceiver 1102 and the memory 1103, as well as the transceiver 1102 and the processor 1101 can be communicated and connected through a bus interface, the function of the processor 1101 can also be realized by the transceiver 1102, and the function of the transceiver 1102 can also be realized by the processor 1101 realized.
  • a computer-readable storage medium on which a program is stored, and when the program is executed by a processor, the following steps are implemented:
  • first connection establishment request is a service routing-based connection establishment request
  • first domain name resolution request is based on DNS protocol domain name resolution request
  • the first connection establishment request has successfully established a connection before receiving the feedback message of the first edge computing platform for the first domain name resolution request, the first connection established by the first connection establishment request Access the target service.
  • Embodiments of the present disclosure provide a first edge computing platform shown in FIG. 12 , including:
  • the receiving module 121 is configured to receive a first connection establishment request and a first domain name resolution request for the target service sent by the terminal, wherein the first connection establishment request is a service route-based connection establishment request, and the first domain name resolution The request is a domain name resolution request based on the DNS protocol;
  • the response module 122 is configured to establish a first connection with the terminal according to the first connection establishment request, and, according to the first domain name resolution request, obtain a second parsed corresponding to the target service. destination address, and send a feedback message for the first domain name resolution request to the terminal, where the feedback message carries the second destination address.
  • the first connection establishment request is an access request for a first destination address, where the first destination address includes a first service routing prefix of the first edge computing platform and a service corresponding to the target service logo.
  • the first service routing prefix is specifically:
  • each local server of the first edge computing platform includes a first public network IPv6 address and a second public network IPv6 address respectively;
  • the response module 122 is further configured to, after sending the feedback message, receive a second connection establishment request for the second destination address sent by the terminal.
  • the response module 122 is further configured to provide the target service for the terminal by using the first connection established in the first connection request and the second connection request.
  • the response module 122 is further configured to send the service routing address corresponding to the target service when sending the feedback message for the first domain name resolution request to the terminal.
  • the device in this embodiment is a device corresponding to the method shown in FIG. 4 , and the implementation manners in the above embodiments are all applicable to the embodiments of the device, and the same technical effect can also be achieved. It should be noted here that the above-mentioned device provided by the embodiment of the present disclosure can realize all the method steps realized by the above-mentioned method embodiment, and can achieve the same technical effect, and the same as the method embodiment in this embodiment is not repeated here. The parts and beneficial effects will be described in detail.
  • an embodiment of the present disclosure provides a schematic structural diagram of a first edge computing platform, including: a processor 1301, a transceiver 1302, a memory 1303, and a bus interface, wherein:
  • the first edge computing platform further includes: a program stored on the memory 1303 and executable on the processor 1301, the program implements the following steps when executed by the processor 1301:
  • the terminal Receive the first connection establishment request and the first domain name resolution request for the target service sent by the terminal, wherein the first connection establishment request is a connection establishment request based on service routing, and the first domain name resolution request is based on the DNS protocol. Domain name resolution request;
  • the first connection establishment request is an access request for a first destination address, where the first destination address includes a first service routing prefix of the first edge computing platform and a service corresponding to the target service logo.
  • the first service routing prefix is specifically:
  • each local server of the first edge computing platform includes a first public network IPv6 address and a second public network IPv6 address respectively;
  • the processor further implements the following steps when executing the program:
  • the processor further implements the following steps when executing the program:
  • the target service is provided for the terminal by using the connection established first in the first connection request and the second connection request.
  • the processor further implements the following steps when executing the program:
  • the service routing address corresponding to the target service is also sent.
  • the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 1301 and various circuits of memory represented by memory 1303 linked together.
  • the bus architecture may also link together various other circuits, such as peripherals, voltage regulators, and power management circuits, which are well known in the art and, therefore, will not be described further herein.
  • the bus interface provides the interface.
  • Transceiver 1302 may be a number of elements, including a transmitter and a receiver, that provide a means for communicating with various other devices over a transmission medium.
  • the processor 1301 is responsible for managing the bus architecture and general processing, and the memory 1303 may store data used by the processor 1301 when performing operations.
  • the terminal in this embodiment is a device corresponding to the method shown in FIG. 4 , and the implementation manners in the above embodiments are all applicable to the embodiments of the terminal, and the same technical effect can also be achieved.
  • the transceiver 1302 and the memory 1303, as well as the transceiver 1302 and the processor 1301 can be communicated and connected through a bus interface, the function of the processor 1301 can also be realized by the transceiver 1302, and the function of the transceiver 1302 can also be realized by the processor 1301 realized.
  • a computer-readable storage medium on which a program is stored, and when the program is executed by a processor, the following steps are implemented:
  • the terminal Receive the first connection establishment request and the first domain name resolution request for the target service sent by the terminal, wherein the first connection establishment request is a connection establishment request based on service routing, and the first domain name resolution request is based on the DNS protocol. Domain name resolution request;
  • This embodiment of the present disclosure provides a session management function shown in FIG. 14, including:
  • the sending module 141 is configured to send the first service routing prefix of the first edge computing platform to the terminal during the process of establishing the session between the terminal and the user plane function of the first edge computing platform.
  • the sending module 141 is further configured to carry the first service routing prefix in the PDU session modification command or the PDU session establishment accept message and send it to the terminal.
  • the apparatus in this embodiment is a device corresponding to the method shown in FIG. 5 above, and the implementation manners in the above embodiments are all applicable to the embodiments of the device, and the same technical effect can also be achieved.
  • the above-mentioned device provided by the embodiment of the present disclosure can realize all the method steps realized by the above-mentioned method embodiment, and can achieve the same technical effect, and the same as the method embodiment in this embodiment is not repeated here. The parts and beneficial effects will be described in detail.
  • an embodiment of the present disclosure provides a schematic structural diagram of a session management function, including: a processor 1501, a transceiver 1502, a memory 1503, and a bus interface, wherein:
  • the session management function further includes: a program stored on the memory 1503 and executable on the processor 1501, the program implements the following steps when executed by the processor 1501:
  • the first service routing prefix of the first edge computing platform is sent to the terminal.
  • the processor further implements the following steps when executing the program:
  • the first service routing prefix is carried in the PDU session modification command or the PDU session establishment accept message and sent to the terminal.
  • the bus architecture may include any number of interconnected buses and bridges, in particular one or more processors represented by processor 1501 and various circuits of memory represented by memory 1503 linked together.
  • the bus architecture may also link together various other circuits, such as peripherals, voltage regulators, and power management circuits, which are well known in the art and, therefore, will not be described further herein.
  • the bus interface provides the interface.
  • Transceiver 1502 may be a number of elements, including a transmitter and a receiver, that provide a means for communicating with various other devices over a transmission medium.
  • the processor 1501 is responsible for managing the bus architecture and general processing, and the memory 1503 may store data used by the processor 1501 in performing operations.
  • the terminal in this embodiment is a device corresponding to the method shown in FIG. 5 above, and the implementation manners in the above embodiments are all applicable to the embodiments of the terminal, and the same technical effect can also be achieved.
  • the transceiver 1502 and the memory 1503, as well as the transceiver 1502 and the processor 1501 can be communicated and connected through a bus interface, the function of the processor 1501 can also be implemented by the transceiver 1502, and the function of the transceiver 1502 can also be implemented by the processor 1501 realized.
  • a computer-readable storage medium on which a program is stored, and when the program is executed by a processor, the following steps are implemented:
  • the first service routing prefix of the first edge computing platform is sent to the terminal.
  • the program When the program is executed by the processor, it can realize all the implementation manners in the above-mentioned service routing method applied to SMF, and can achieve the same technical effect. To avoid repetition, details are not repeated here.
  • the disclosed apparatus and method may be implemented in other manners.
  • the apparatus embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and 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 solutions of the embodiments of the present disclosure.
  • each functional unit in each embodiment of the present disclosure may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the functions, if implemented in the form of software functional units and sold or used as independent products, may be stored in a computer-readable storage medium. Based on such understanding, the technical solutions of the present disclosure can be embodied in the form of software products in essence, or the parts that contribute to the prior art or the parts of the technical solutions.
  • the computer software products are stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of the present disclosure.
  • the aforementioned storage medium includes: a U disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk and other mediums that can store program codes.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Multimedia (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请提供一种服务路由方法及设备，该方法包括：终端向第一边缘计算平台发送针对目标服务的第一连接建立请求和第一域名解析请求，其中，所述第一连接建立请求为基于服务路由的连接建立请求，所述第一域名解析请求为基于DNS协议的域名解析请求；如果在接收到所述第一边缘计算平台对所述第一域名解析请求的反馈消息之前，所述第一连接建立请求已经成功建立连接，则通过所述第一连接建立请求建立的第一连接接入所述目标服务。本公开能够降低服务的访问时延以及降低服务路由的实现复杂度。

Description

服务路由方法及设备
相关申请的交叉引用
本申请基于申请号为202110393967.0、申请日为2021年04月13日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本公开涉及移动通信技术领域，具体涉及一种服务路由方法及设备。
背景技术
OTT是“Over The Top”的缩写，在通信行业是指互联网公司越过运营商，发展基于开放互联网的各种视频及数据服务业务，强调服务与物理网络的无关性。OTT的一个需求是降低用户的Web应用的接入时延，相关的技术如基于UDP的低时延的互联网传输层协议(Quick UDP Internet Connection，QUIC)等。某些研究指出，服务的访问时延每降低几百毫秒，则用户量的访问量会提高若干个百分点。
为了提升用户对业务的访问体验，现有技术提出了一种服务路由(Service Routing)的技术方案，该方案引入了一种新的服务路由地址，该服务路由地址包括有一个服务路由前缀(Service ID Prefix)，即一个IPv6地址的前缀，该服务路由地址也被称为一个服务标识(Service ID)。该方案基于该服务标识(Service ID)路由寻址，Service ID存在多种实现方式，例如可以将服务名字(如网址)哈希为IPv6地址末若干位，再合并服务路由前缀，就可以构成一个Service ID。用户获取服务时，报文的目的地址直接填写Service ID，从而可以消除域名服务器(Domain Name Service，DNS) 的查询过程。
可以认为，服务路由地址是一种新的IPv6地址，在具体实现时，一种思路(solution1)是去互联网数字分配机构(IANA)为这种IPv6地址单独申请一段地址空间，用于服务路由(Service Routing)，此时访问不同的移动边缘计算(Mobile Edge Computing,MEC)时使用相同的服务路由前缀，可以理解成一个任播(anycast)地址；另一种思路(solution2)是终端在接入服务之前，使用动态主机配置协议(Dynamic Host Configuration Protocol，DHCP)得到服务路由前缀，此时访问不同的MEC使用不同的服务路由前缀。然而，现有技术的服务路由方案，其冲突检测机制设计的比较复杂，不利于在现网中的实现。
发明内容
本公开的至少一个实施例提供了一种服务路由方法及设备，能够降低服务的访问时延以及降低服务路由的实现复杂度。
根据本公开的一个方面，至少一个实施例提供了一种服务路由方法，包括：
终端向第一边缘计算平台发送针对目标服务的第一连接建立请求和第一域名解析请求，其中，所述第一连接建立请求为基于服务路由的连接建立请求，所述第一域名解析请求为基于DNS协议的域名解析请求；
如果在接收到所述第一边缘计算平台对所述第一域名解析请求的反馈消息之前，所述第一连接建立请求已经成功建立连接，则通过所述第一连接建立请求建立的第一连接接入所述目标服务。
较佳地，根据本公开的至少一个实施例，在向第一边缘计算平台发送针对目标服务的第一连接建立请求和第一域名解析请求之前，所述方法还包括：
所述终端在建立或修改与所述第一边缘计算平台的用户面功能之间的 会话的过程中，接收核心网的会话管理功能SMF发送的所述第一边缘计算平台的第一服务路由前缀。
较佳地，根据本公开的至少一个实施例，发送所述第一连接建立请求包括：所述终端确定所述目标服务对应的服务标识，生成包括所述第一服务路由前缀和所述服务标识的第一目的地址，发送针对所述第一目的地址的访问请求。
较佳地，根据本公开的至少一个实施例，在发送所述第一域名解析请求之后，所述方法还包括：所述终端接收到所述第一边缘计算平台对所述第一域名解析请求的反馈消息，所述反馈消息携带有所述目标服务对应的第二目的地址；
如果在接收到所述反馈消息时，所述第一连接建立请求尚未成功建立连接，所述终端发送针对所述第二目的地址的第二连接建立请求；以及，利用第一连接请求和第二连接请求中最先建立的连接，接入所述目标服务。
较佳地，根据本公开的至少一个实施例，还包括：
所述终端在发送针对所述目标服务的第一域名解析请求之后，还接收所述第一边缘计算平台返回的所述目标服务对应的服务路由地址；
在所述第一连接建立请求先于所述第二连接建立请求成功建立连接的情况下，所述终端判断所述目标服务对应的服务路由地址是否与所述第一目的地址匹配：若是，则继续通过所述第一连接接入所述目标服务；否则，断开所述第一连接，通过所述第二连接建立请求建立所述第二连接，并通过所述第二连接接入所述目标服务。
较佳地，根据本公开的至少一个实施例，在判断所述目标服务对应的服务路由地址与所述第一目的地址匹配的情况下，所述方法还包括：
取消所述第二连接建立请求的连接建立流程。
较佳地，根据本公开的至少一个实施例，所述第一服务路由前缀具体 为：
所述第一边缘计算平台的本地服务器的第一公网IPv6地址的前缀，其中，所述第一边缘计算平台的各个本地服务器分别包括有第一公网IPv6地址和第二公网IPv6地址；
或者，
所述第一边缘计算平台的本地服务器的私网IPv6地址的前缀，所述私网地址为IPv6唯一本地地址ULA地址；
或者，
所述第一边缘计算平台的本地服务器的分段路由SRv6的段标识SID中的位置标识(Locator)。此外，根据本公开的至少一个实施例，所述接收所述第一边缘计算平台发送的第一服务路由前缀，具体为：
接收所述第一边缘计算平台在PDU会话修改命令或PDU会话建立接受消息中携带的第一服务路由前缀。
根据本公开的另一方面，至少一个实施例提供了一种服务路由方法，包括：
第一边缘计算平台接收终端发送的针对目标服务的第一连接建立请求和第一域名解析请求，其中，所述第一连接建立请求为基于服务路由的连接建立请求，所述第一域名解析请求为基于DNS协议的域名解析请求；
所述第一边缘计算平台根据所述第一连接建立请求，建立与所述终端之间的第一连接，以及，根据所述第一域名解析请求，获取解析得到的所述目标服务对应的第二目的地址，向所述终端发送对所述第一域名解析请求的反馈消息，所述反馈消息携带有所述第二目的地址。
较佳地，根据本公开的至少一个实施例，所述第一连接建立请求为针对第一目的地址的访问请求，所述第一目的地址包括有所述第一边缘计算平台的第一服务路由前缀和所述目标服务对应的服务标识。
较佳地，根据本公开的至少一个实施例，在发送所述反馈消息之后，所述方法还包括：
接收所述终端发送的针对所述第二目的地址的第二连接建立请求。
较佳地，根据本公开的至少一个实施例，还包括：
利用所述第一连接请求和第二连接请求中最先建立的连接，为所述终端提供所述目标服务。
较佳地，根据本公开的至少一个实施例，还包括：
所述第一边缘计算平台在向所述终端发送对所述第一域名解析请求的反馈消息时，还发送所述目标服务对应的服务路由地址。
根据本公开的另一方面，至少一个实施例提供了一种服务路由方法，包括：
核心网的会话管理功能SMF，在建立终端与第一边缘计算平台的用户面功能之间的会话的过程中，向所述终端发送所述第一边缘计算平台的第一服务路由前缀。
较佳地，根据本公开的至少一个实施例，所述第一服务路由前缀具体为：
所述第一边缘计算平台的本地服务器的第一公网IPv6地址的前缀，其中，所述第一边缘计算平台的各个本地服务器分别包括有第一公网IPv6地址和第二公网IPv6地址；
或者，
所述第一边缘计算平台的本地服务器的私网IPv6地址的前缀，所述私网地址为IPv6唯一本地地址ULA地址；
或者，
所述第一边缘计算平台的本地服务器的分段路由SRv6的段标识SID中的位置标识(Locator)。
较佳地，根据本公开的至少一个实施例，所述向所述终端发送所述第一边缘计算平台的第一服务路由前缀，具体为：
在PDU会话修改命令或PDU会话建立接受消息携带第一服务路由前缀并发送给所述终端。
根据本公开的另一方面，至少一个实施例提供了一种终端，包括：
发送模块，配置为向第一边缘计算平台发送针对目标服务的第一连接建立请求和第一域名解析请求，其中，所述第一连接建立请求为基于服务路由的连接建立请求，所述第一域名解析请求为基于DNS协议的域名解析请求；
服务接入模块，配置为如果在接收到所述第一边缘计算平台对所述第一域名解析请求的反馈消息之前，所述第一连接建立请求已经成功建立连接，则通过所述第一连接建立请求建立的第一连接接入所述目标服务。
根据本公开的另一方面，至少一个实施例提供了一种终端，包括收发机和处理器，其中，
所述收发机，配置为向第一边缘计算平台发送针对目标服务的第一连接建立请求和第一域名解析请求，其中，所述第一连接建立请求为基于服务路由的连接建立请求，所述第一域名解析请求为基于DNS协议的域名解析请求；
所述处理器，配置为如果在接收到所述第一边缘计算平台对所述第一域名解析请求的反馈消息之前，所述第一连接建立请求已经成功建立连接，则通过所述第一连接建立请求建立的第一连接接入所述目标服务。
根据本公开的另一方面，至少一个实施例提供了一种终端，包括：处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序，所述程序被所述处理器执行时实现如上所述的方法的步骤。
根据本公开的另一方面，至少一个实施例提供了一种第一边缘计算平 台，包括：
接收模块，配置为接收终端发送的针对目标服务的第一连接建立请求和第一域名解析请求，其中，所述第一连接建立请求为基于服务路由的连接建立请求，所述第一域名解析请求为基于DNS协议的域名解析请求；
响应模块，配置为根据所述第一连接建立请求，建立与所述终端之间的第一连接，以及，根据所述第一域名解析请求，获取解析得到的所述目标服务对应的第二目的地址，向所述终端发送对所述第一域名解析请求的反馈消息，所述反馈消息携带有所述第二目的地址。
根据本公开的另一方面，至少一个实施例提供了一种第一边缘计算平台，包括收发机和处理器，其中，
所述收发机，配置为接收终端发送的针对目标服务的第一连接建立请求和第一域名解析请求，其中，所述第一连接建立请求为基于服务路由的连接建立请求，所述第一域名解析请求为基于DNS协议的域名解析请求；
所述处理器，配置为根据所述第一连接建立请求，建立与所述终端之间的第一连接，以及，根据所述第一域名解析请求，获取解析得到的所述目标服务对应的第二目的地址，向所述终端发送对所述第一域名解析请求的反馈消息，所述反馈消息携带有所述第二目的地址。
根据本公开的另一方面，至少一个实施例提供了一种第一边缘计算平台，包括：处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序，所述程序被所述处理器执行时实现如上所述的方法的步骤。
根据本公开的另一方面，至少一个实施例提供了一种核心网的会话管理功能，包括：
发送模块，配置为在建立终端与第一边缘计算平台的用户面功能之间的会话的过程中，向所述终端发送所述第一边缘计算平台的第一服务路由前缀。
根据本公开的另一方面，至少一个实施例提供了一种核心网的会话管理功能，包括收发机和处理器，其中，
所述收发机，配置为在建立终端与第一边缘计算平台的用户面功能之间的会话的过程中，向所述终端发送所述第一边缘计算平台的第一服务路由前缀。
根据本公开的另一方面，至少一个实施例提供了一种核心网的会话管理功能，包括：处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序，所述程序被所述处理器执行时实现如上所述的方法的步骤。
根据本公开的另一方面，至少一个实施例提供了一种计算机可读存储介质，所述计算机可读存储介质上存储有程序，所述程序被处理器执行时，实现如上所述的方法的步骤。
与现有技术相比，本公开实施例提供的服务路由方法及设备，能够利用两个请求来请求建立与目标服务之间的连接，并利用首先成功建立的连接来接入目标服务，从而可以规避现有技术复杂的冲突检测处理机制，降低了服务路由的实现复杂度，并能降低服务的访问时延。
附图说明
通过阅读下文优选实施方式的详细描述，各种其他的优点和益处对于本领域普通技术人员将变得清楚明了。附图仅用于示出优选实施方式的目的，而并不认为是对本公开的限制。而且在整个附图中，用相同的参考符号表示相同的部件。在附图中：
图1为现有技术的服务路由在终端侧的流程示意图；
图2为现有技术的服务路由在网络侧的流程示意图；
图3为本公开实施例提供的服务路由方法应用于终端侧时的流程图；
图4为本公开实施例提供的服务路由方法应用于MEC时的流程图；
图5为本公开实施例提供的服务路由方法应用于SMF时的流程图；
图6为未引入服务路由时的MEC服务访问的示例图；
图7为本公开实施例的服务路由方法的一种应用示例图；
图8为本公开实施例的服务路由方法的另一种应用示例图；
图9为本公开实施例的服务路由方法的又一种应用示例图；
图10为本公开实施例提供的终端的一种结构示意图；
图11为本公开实施例提供的终端的另一种结构示意图；
图12为本公开实施例提供的第一边缘计算平台的一种结构示意图；
图13为本公开实施例提供的第一边缘计算平台的另一种结构示意图；
图14为本公开实施例提供的会话管理功能的一种结构示意图；
图15为本公开实施例提供的会话管理功能的另一种结构示意图。
具体实施方式
下面将参照附图更详细地描述本公开的示例性实施例。虽然附图中显示了本公开的示例性实施例，然而应当理解，可以以各种形式实现本公开而不应被这里阐述的实施例所限制。相反，提供这些实施例是为了能够更透彻地理解本公开，并且能够将本公开的范围完整的传达给本领域的技术人员。
本申请的说明书和权利要求书中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的本申请的实施例例如能够以除了在这里图示或描述的那些以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。说明书以及权利要求中“和/或”表示所连接对象的至少其中之一。
以下描述提供示例而并非限定权利要求中阐述的范围、适用性或者配置。可以对所讨论的要素的功能和布置作出改变而不会脱离本公开的精神和范围。各种示例可恰适地省略、替代、或添加各种规程或组件。例如，可以按不同于所描述的次序来执行所描述的方法，并且可以添加、省去、或组合各种步骤。另外，参照某些示例所描述的特征可在其他示例中被组合。
现有技术的一种服务路由方法，其在方案流程上，包括用户侧信息的通告和服务侧信息通告。终端通过扩展的DHCP协议，得到客户端(client)地址和服务路由前缀等信息；服务器侧和网络侧可以通过自定义的UDP协议，配置节点控制面以及修改转发表。终端侧的流程如图1所示，包括：
11，终端的DHCP客户端(DHCP client)主动向DHCP服务器(DHCP server)发起发现/请求(discover/request)。
12，在DHCP server回复的DHCP ACK阶段option字段中携带服务路由前缀、哈希算法枚举值、冲突检测服务器(DHCP server Ext)地址。
13，DHCP client获得上述地址后，在本地保存服务路由前缀和哈希算法。
14，DHCP client定时发送请求(request)，向DHCP server Ext请求哈希冲突列表。
15，DHCP server Ext回复的DHCP ACK报文，option字段中携带哈希冲突列表，列表内容支持分片，可以在多个ACK中完成发送。
网络侧的流程如图2所示，包括：
21，当内容写入到服务标识服务器(ServerID server)时，将URL、域名(domain name)、哈希得到的serviceID记录保存；
22，Service ID写入时，检测到哈希(HASH)冲突，如原有URL_1对应serviceID_1，新写入的URL_2哈希的结果也是serverID_1，立即向冲 突检测服务器(DHCP server Ext)发布哈希冲突值；
23，DHCP server Ext收到上报的URL_1、URL_2、serviceID_1，从备选库中取出一个值serviceID_2，分配给其中一个URL_2；并向ServerID Server返回哈希分配结果URL_2/serviceID_2；
24，DHCP server Ext在本地记录URL_2/serviceID_2，记入到哈希冲突列表。
25，服务器侧发出发布ServiceID路由的协议报文。
26，路由器接收报文，将报文上送控制面处理：
A)从报文中解析出服务路由serviceID，作为前缀；
B)从报文中解析出服务器端口静态IP，作为下一跳(nexthop)；
C)记录上送端口，作为出接口；
D)下发路由。
27，向服务器回复确认消息(ACK)，说明哪条服务路由已经处理完成。
28，路由器定时维护与服务器的接口的连接状态，连接状态有效，所有从该接口接收的路由有效。
服务路由(Service Routing)是一种新的路由技术方案，未来可能会在公网(大网)中使能(用于BGP anycast)。该技术认为大网中，Service Routing支持基于服务标识(Service ID)的业务可感知路由，可以支持综合业务信息和路径信息进行路由决策。服务路由可能会先在有限域(limited domain)中应用，例如MEC，有利于规避比较复杂的哈希(HASH)冲突的问题(因为冲突会比较少)。在采用背景技术中所述的solution2，其冲突检测的机制设计的比较复杂，不利于现网中的实现。
为解决以上问题中的至少一种，本公开实施例提供了一种服务路由方法，能够降低服务路由的实现复杂度，使得路由机制更加轻量级，有利于在现网中的实现。具体的，本公开实施例规避了哈希(HASH)冲突的处理， 如果出现了冲突，则支持退回默认的DNS机制，这样可以仅在一些关键/主要场景中提供最优的业务体验。具体的，终端可以同时按照两种机制发起请求(基于服务路由的连接建立请求，和，基于DNS协议的域名解析请求)，在HASH正确命中前提下，通常基于服务路由的连接请求会首先建立连接。另外，当仅在MEC中实现时，本公开实施例的方案也可以认为是MEC站点内的一种IPv6地址的配置方式，也就是说，服务路由前缀使能为MEC的地址(用于路由)，即，将服务路由前缀设置为该MEC的服务的公共前缀，从而在不同的MEC，终端可以使用相同HASH算法，得到对应的服务地址，实现快速接入。
请参照图3，本公开实施例提供的一种服务路由方法，在由终端执行时包括：
步骤31，终端向第一边缘计算平台发送针对目标服务的第一连接建立请求和第一域名解析请求，其中，所述第一连接建立请求为基于服务路由的连接建立请求，所述第一域名解析请求为基于DNS协议的域名解析请求。
这里，本公开实施例在请求目标服务时，将发起两个请求，具体包括：基于服务路由的第一连接建立请求，和，基于DNS协议的域名解析请求。相比于现有技术，本公开实施例在请求目标服务时，不只是发送一个针对目标服务的请求，而是发送两个请求，其中，域名解析请求用于获取目标服务对应的IP地址(第二目的地址)，进而可以根据获得的目标服务对应的IP地址发起第二连接建立请求。
例如，目标服务的服务名字可以是某个域名，如local-weather.com，此时，终端在发送针对所述目标服务的第一连接建立请求时，可以发送针对所述目标服务对应的服务路由地址的访问请求；在发送第一域名解析请求时，可以发送针对所述目标服务的域名解析请求，请求所述目标服务的域名对应的IP地址。
步骤32，如果在接收到所述第一边缘计算平台对所述第一域名解析请求的反馈消息之前，所述第一连接建立请求已经成功建立连接，则通过所述第一连接建立请求建立的第一连接接入所述目标服务。
在发起上述两个请求后，如果在接收到所述第一域名解析请求的反馈之前，所述第一连接建立请求已经成功建立连接，此时所述终端通过所述第一连接建立请求建立的第一连接接入所述目标服务。后续，如果所述终端接收到所述第一域名解析请求的反馈，所述终端可以放弃发起第二连接建立请求。
通过以上步骤，本公开实施例的终端在请求目标服务时，将发起步骤31中的两个请求，当基于服务路由的请求首先建立第一连接时，本公开实施例通过所述第一连接接入所述目标服务，另外放弃发起第二连接建立请求。这样，本公开实施例能够利用两个请求来请求建立与目标服务之间的连接，并利用首先成功建立的连接来接入目标服务。这样，本公开实施例在服务路由发生哈希冲突后，可以不进行现有技术的冲突检测处理，而是利用之前已发起的域名解析请求继续建立第二连接以接入所述目标服务，因此，本公开实施例可以规避现有技术复杂的冲突检测处理机制，降低了服务路由的实现复杂度，并能降低服务的访问时延。
本公开实施例中，在步骤31之前，所述终端在建立或修改与所述第一边缘计算平台的用户面功能之间的会话的过程中，接收核心网的会话管理功能SMF发送的所述第一边缘计算平台的第一服务路由前缀。具体的，所述第一服务路由前缀可以携带在PDU会话修改命令或PDU会话建立接受消息中。
这样，在步骤31中，所述终端可以确定所述目标服务对应的服务标识(Service ID)，生成包括所述第一服务路由前缀的第一目的地址(服务路由地址)，然后发送针对所述第一目的地址的访问请求。例如，对所述目标服 务对应的服务名字(如服务名字为local-weather.com)进行哈希计算，得到目标服务对应的服务标识(Service ID)即第一目的地址的末若干位，与第一服务路由前缀组合，得到第一目的地址。
终端发送上述步骤31中的第一域名解析请求之后，第一边缘计算平台根据所述第一域名解析请求，获取所述目标服务的域名对应的IP地址(第二目的地址)并通过反馈消息返回给所述终端。所述终端接收到所述第一边缘计算平台对所述第一域名解析请求的反馈消息，所述反馈消息携带有所述目标服务对应的第二目的地址。如果在接收到所述反馈消息时，所述第一连接建立请求尚未成功建立连接，所述终端发送针对所述第二目的地址的第二连接建立请求；以及，利用第一连接请求和第二连接请求中最先建立的连接，接入所述目标服务。
这里，所述第一服务路由前缀可以是以下任一种：
1)所述第一边缘计算平台的本地服务器的第一公网IPv6地址的前缀，其中，所述第一边缘计算平台的各个本地服务器分别包括有第一公网IPv6地址和第二公网IPv6地址，每个本地服务器的第一公网IPv6地址和第二公网IPv6地址可以相同或不同。优选的，所有本地服务器的第一公网IPv6地址的前缀可以都相同。
此时，上文中第一边缘计算平台根据所述第一域名解析请求获取的所述目标服务的域名对应的IP地址，即为提供所述目标服务的本地服务器的第二公网IPv6地址。
2)所述第一边缘计算平台的本地服务器的私网IPv6地址的前缀。所述私网地址为IPv6唯一本地地址(Unique Local IPv6 Unicast Address，ULA)。
ULA地址是IPv6的本地单播地址(Unique Local IPv6 Unicast Address)，是专门用于内部网络的地址，如果数据包的源IP或者目的IP地址是这个地址段之内的地址，是不可以在公网上转发的。优选的，所述第一边缘计算 平台的所有本地服务器的私网IPv6地址的前缀均相同。
3)所述第一边缘计算平台的本地服务器的分段路由(SRv6)的段标识(Segment ID，SID)中的位置标识(Locator)。优选的，所述第一边缘计算平台的所有本地服务器都具有相同的Locator。
可选的，本公开实施例中，第一边缘计算平台还可以针对第一域名请求反馈所述第二目的地址时，进一步向终端反馈所述目标服务对应的服务路由地址，以用于终端进行服务路由地址的校验。这样，所述终端在发送针对所述目标服务的第一域名解析请求之后，还可以接收所述第一边缘计算平台返回的所述目标服务对应的服务路由地址。后续如果所述第一连接建立请求先于所述第二连接建立请求成功建立连接，所述终端则可以判断所述目标服务对应的服务路由地址(即第一边缘计算平台返回的所述目标服务对应的服务路由地址)是否与所述第一目的地址匹配：
若是，则继续通过所述第一连接接入所述目标服务；
否则，断开所述第一连接，通过所述第二连接建立请求建立所述第二连接，并通过所述第二连接接入所述目标服务。
进一步的，所述终端在判断所述目标服务对应的服务路由地址与所述第一目的地址匹配的情况下，还可以取消所述第二连接建立请求的连接建立流程。
本公开实施例在上述步骤31之后，所述终端也可能通过第二连接建立请求建立了第二连接，在所述第二连接建立请求先于第一连接建立请求成功建立连接的情况下，所述终端通过所述第二连接建立请求建立的第二连接接入所述目标服务，另外，所述终端还可以取消第一连接建立请求的后续流程。
另外需要说明的是，本文中涉及的SR的缩写，通常是表示服务路由(Service Routing)，而SRv6则表示基于IPv6的分段路由(Segment  Routing)。
请参照图4，本公开实施例的服务路由方法，在应用于第一边缘计算平台侧时，包括：
步骤41，第一边缘计算平台接收终端发送的针对目标服务的第一连接建立请求和第一域名解析请求，其中，所述第一连接建立请求为基于服务路由的连接建立请求，所述第一域名解析请求为基于DNS协议的域名解析请求。
这里，所述第一连接建立请求为针对第一目的地址的访问请求，所述第一目的地址包括有所述第一边缘计算平台的第一服务路由前缀和所述目标服务对应的服务标识。所述服务标识可以是对目标服务的服务名称进行哈希计算得到。所述第一服务路由前缀可以是以下任一种：
1)所述第一边缘计算平台的本地服务器的第一公网IPv6地址的前缀，其中，所述第一边缘计算平台的各个本地服务器分别包括有第一公网IPv6地址和第二公网IPv6地址，每个本地服务器的第一公网IPv6地址和第二公网IPv6地址可以相同或不同。优选的，所有本地服务器的第一公网IPv6地址的前缀可以都相同。
此时，上文中第一边缘计算平台根据所述第一域名解析请求获取的所述目标服务的域名对应的IP地址，即为提供所述目标服务的本地服务器的第二公网IPv6地址。
2)所述第一边缘计算平台的本地服务器的私网IPv6地址的前缀。所述私网地址为IPv6唯一本地地址ULA地址。优选的，所述第一边缘计算平台的所有本地服务器的私网IPv6地址的前缀均相同。
3)所述第一边缘计算平台的本地服务器的分段路由(SRv6)的段标识(Segment ID，SID)中的位置标识(Locator)。优选的，所述第一边缘计算平台的所有本地服务器都具有相同的Locator。
步骤42，所述第一边缘计算平台根据所述第一连接建立请求，建立与所述终端之间的第一连接，以及，根据所述第一域名解析请求，获取解析得到的所述目标服务对应的第二目的地址，向所述终端发送对所述第一域名解析请求的反馈消息，所述反馈消息携带有所述第二目的地址。
这里，第一边缘计算平台在接收所述第一域名解析请求之后，可以根据所述第一域名解析请求，获取解析得到的所述目标服务的域名所对应的第二目的地址，并向所述终端发送所述第二目的地址。这里，域名解析可以通过第一边缘计算平台中的DNS服务器执行。
通过上述步骤，终端请求目标服务时发送步骤41中的两种请求，第一边缘计算平台响应上述请求，建立所述终端与目标服务之间的第一连接，以及反馈第二目的地址。这样，当基于服务路由的第一连接建立请求首先建立第一连接时，本公开实施例通过所述第一连接为终端提供所述目标服务，从而本公开实施例能够利用两个请求来建立连接，并利用首先成功建立的连接来提供目标服务。本公开实施例在服务路由发生哈希冲突后，可以不进行现有技术的冲突检测处理，而是利用之前已发起的域名解析请求建立第二连接接入目标服务，因此，本公开实施例可以规避现有技术复杂的冲突检测处理机制，降低了服务路由的实现复杂度，并能降低服务的访问时延。
在发送所述反馈消息之后，第一边缘计算平台还可能接收到所述终端发送的针对所述第二目的地址的第二连接建立请求，进而响应所述第二连接建立请求，建立所述终端与目标服务之间的第二连接。然后，利用所述第一连接请求和第二连接请求中最先建立的连接(可能是第一连接或第二连接)，为所述终端提供所述目标服务。
可选的，本公开实施例中，所述第一边缘计算平台在向所述终端发送对所述第一域名解析请求的反馈消息时，还发送所述目标服务对应的服务 路由地址，以提供给所述终端进行服务路由地址的校验。
请参照图5，本公开实施例的服务路由方法，在应用于核心网的会话管理功能(SMF)时，包括：
步骤51，核心网的会话管理功能SMF，在建立终端与第一边缘计算平台的用户面功能之间的会话的过程中，向所述终端发送所述第一边缘计算平台的第一服务路由前缀。
这里，SMF可以在PDU会话修改命令或PDU会话建立接受消息携带第一服务路由前缀并发送给所述终端。
为了帮助更好的理解以上实施例，针对以上第一服务路由前缀的三种情况，下面通过三个对应的示例作进一步的说明。
示例1：
首先介绍在未引入服务路由(Service Routing)时的MEC服务访问情况，如图6所示，图6及后续的图7～9中，5GC表示5G核心网，5GC-CP表示5G核心网的控制面，包括以下61～63所示的几种情形：
61，UE接入5G网络，建立到5G核心网(5GC)的用户面功能(User Plane Function，UPF)的数据面的会话，如果访问local-weather.com，需要先进行DNS解析获取IP地址，例如ABCD::0123:4567，之后根据IP地址访问对应的服务器(Web Server)，从而获取服务。
62，UE接入到边缘计算平台1(MEC1)，在5GC控制下，建立UE到MEC1的UPF的会话，在访问local-weather.com时，需要先进行local DNS解析，获取IP地址，例如AAAA::9876:4567，之后根据IP地址访问对应的服务器(Cache Server)，从而获取服务。此时因为MEC1距离UE更近，则有一定的低时延的效果。
63，UE切换之后，接入到MEC2，在5GC控制下，建立到MEC2的UPF的会话。假设UE还是访问local-weather.com，此时需要先进行local DNS 解析，获取IP地址，例如BBBB::4534:4567，之后根据IP地址访问对应的服务器(Cache Server)，从而获取服务。
在引入Service Routing后的MEC服务访问情况，如图7所示，包括：
首先，UE接入5G网络，建立到5GC的UPF的数据面的会话，如果UE访问local-weather.com，需要先进行DNS解析获取IP地址，例如ABCD::0123:4567，之后访问该服务器，从而获取服务。
71，UE接入到MEC1，在5GC控制下，建立到MEC1的UPF的会话，在会话建立/修改过程中，得到一个服务路由(Service Routing)的前缀，如AAAA:A100::/64。
MEC1需要在网络中通告这个IPv6前缀，即该MEC1的服务可以有两个地址都可以接入。其中一个是传统的IPv6地址(上文的第二公网IPv6地址)，一个是Service Routing的地址(上文的第一公网IPv6地址)，可选的，两个地址也可以相同(但是按照后者的格式)。当两个地址不同时，local DNS解析时可返回两个地址，如BBBB::4534:4567，BBBB:B200::0001，用于验证(此时需要扩展目前的DNS协议，给后面的第2个地址一个Service Routing地址的说明。另外，当有HASH冲突时(如local service较多时)，则使能较重要业务的SR访问，也可考虑更新两侧HASH算法(新的算法有可能让该HASH冲突消失)。
这样，UE访问local-weather.com时，可以同时发起两种连接建立流程：
a)发起DNS解析，local DNS解析到地址，如AAAA::9876:4567，之后UE根据该地址访问对应的服务器。
b)同时，UE直接按照<SR Prefix:Hashvalue>的服务路由地址的格式，如AAAA:A100::0001，发起服务访问
如果b)首先成功建立连接，则按照b)发起访问。
72，UE接入到MEC2，在5GC控制下，建立到MEC2的UPF的会话， 在会话建立/修改时，得到一个Service Routing的前缀，BBBB:B200::/64。
类似的，UE访问local-weather.com，同时发起两种连接建立流程。
a)发起DNS解析，local DNS解析到地址，如BBBB::4534:4567，之后根据该地址访问对应的服务器。
b)同时，直接按照<SR Prefix:Hashvalue>，如BBBB:B200::0001，发起服务访问。
如果b)首先成功建立连接，则按照b)发起访问。
注意，当第一公网IPv6地址与第二公网IPv6地址不同时，local DNS解析可选返回上述两个地址，如BBBB::4534:4567，BBBB:B200::0001，用于验证(此时需要扩展目前的DNS协议，给后面的地址一个说明)
在UE接入场景中，3GPP扩展协议配置选项(Extended Protocol configuration options，，ePCO)可以用于交互一些协议配置参数。本公开实施例可以扩展一个未占用的字段，例如类似于DNS server中的设计，设计如下新的字段：0033H(Service-routing IPv6 Prefix)，从而在PDU会话修改命令或PDU会话建立接受命令中携带服务路由前缀。具体流程上，可以在UE接入MEC的时候，当UE和MEC的UPF建立新的PDU Session，或者修改之前的PDU session时，在PDU会话建立/修改成功的报文中，可以携带一些信息给UE。例如在ePCO options中，通过上述的一个新的扩展字段0033H进行携带。
以上示例1中假设MEC节点有两套公网IPv6地址(或者一套，但是需要迁就Service Routing前缀的这一套)，即假设MEC有很多的相同前缀的IPv6地址(对应着MEC节点中的各种服务)，这样可以直接按照HASH算法进行访问。
示例2：
在示例2中，不再假设MEC节点有一套全网可路由的服务路由前缀地 址，但是假设MEC的本地server有一套ULA地址(Unique Local IPv6 Unicast Addresses)，直接按照HASH算法可以访问。这些ULA地址，仅在MEC内部有效，且可路由。ULA地址是IETF定义的IPv6的一种地址，类似于IPv4中的10.1.*.*这种私网地址，用于本地的通信。ULA地址的特点是本地有效，不需要发布出去，并且地址空间也较大，但是要求服务全部是在MEC内部。
在MEC接入的场景中，使用ULA地址更加可行，因为一方面，UE本身就是在访问本地的内容，另外，使用ULA地址，有助于现有的MEC向支持服务路由过度(不需要配置更多的公网地址)。
该示例2中，引入Service Routing后的MEC服务访问情况如图8所示：
UE接入5G网络，建立到5GC的UPF的数据面的会话，如果访问local-weather.com，需要先进行DNS解析到地址，例如ABCD::0123:4567，之后访问该服务器，从而获取服务。
81，UE接入到MEC1，在5GC控制下，建立到MEC1的UPF的会话，在会话建立/修改时，得到一个Service Routing的前缀，FDAA:A100:1000:0001::/64。
该MEC不需要在外部的网络中通告这个IPv6前缀，但是该MEC内，MEC的服务两个地址都可以接入，一个是传统的IPv6地址，一个是Service Routing的地址，这时，两个地址不同。
UE访问local-weather.com，同时发起两种连接建立流程。
a)UE发起DNS解析，local DNS解析到地址，如AAAA::9876:4567，之后UE根据该地址访问对应的服务器。
b)UE直接按照<SR Prefix:Hashvalue>，如FDAA:A100:1000:0001::0001，发起服务访问。
如果b)首先成功建立连接，则按照b)发起访问。
82，UE接入到MEC2，在5GC控制下，建立到MEC2的UPF的会话，在PDU会话建立/修改的过程中，得到一个服务路由(Service Routing)的前缀，假设为FDAA:A100:1000:0002::/64。
UE访问local-weather.com，同时发起两种连接建立流程。
a)发起DNS解析，local DNS解析到地址，如BBBB::4534:4567，之后根据该地址访问对应的服务器。
b)直接按照<SR Prefix:Hashvalue>，如FDAA:A100:1000:0002::0001，发起服务访问。
如果b)首先成功建立连接，则按照b)发起访问
需要说明的是，local DNS解析可以返回两个地址，如BBBB::4534:4567，FDAA:A100:1000:0002::0001，后者用于验证，例如，已经通过方式b发起了连接，正在交互，这时得到了方式a的回应，如果回应中有FDAA:A100:1000:0002::0001，则UE认为自己的快速连接地址是没问题的，继续交互，不做任何改变，如果没有，则判断是否交互的对象可能不正确，可以转而使用BBBB::4534:4567发起了连接。
另外，当有HASH冲突时(local service较多)，可以使能较重要业务的SR访问，也可考虑更新两侧HASH算法(新的算法有可能让该HASH冲突消失)。
示例3：
该示例3中，不再假设MEC节点有一套全网可路由的Service Routing前缀地址；但是假设MEC的本地服务器(server)有一套分段路由(Segment Routing IPv6，SRv6)地址，这些SRv6地址有一个固定的前缀，可以直接按照HASH算法即可以访问。SRv6地址可以通过段标识(Segment ID，SID)来表示。SID通常包括位置标识(Locator)、功能(Function)和变量(Args)三个部分。
这些SRv6地址，仅在MEC内部有效，可路由。这时，这些SRv6地址的位置标识(Locator)部分是相同的。因此，在一定程度上，该SRv6地址，可以认为类似于SRv6中的LOC，即FUNCT的架构(Locator：FUNCTION)。MEC作为一个虚拟的大节点，Service Routing的IPv6 Prefix对应LOC，FUNCT对应于某个具体的服务。
该示例3中，引入Service Routing后的MEC服务访问情况如图9所示：
首先，UE接入5G网络，建立到5GC的UPF的数据面的会话，如果访问local-weather.com，需要先进行DNS解析到地址，例如ABCD::0123:4567，之后访问该服务器，之后访问该服务器，从而获取服务。
91，UE接入到MEC1，在5GC控制下，建立到MEC1的UPF的会话，在会话建立/修改时，得到一个Service Routing的前缀(同时也是一个SRv6的Locator)，A1:0001::/64。
该MEC不需要在外部的网络中通告这个IPv6前缀，但是该MEC内，MEC的服务两个地址都可以接入，一个是传统的IPv6地址，一个是Service Routing的地址，这时，两个地址不会相同。
这样，UE访问local-weather.com时，同时发起两种连接建立流程：
a)发起DNS解析，local DNS解析到地址，如AAAA::9876:4567，之后UE根据该地址访问对应的服务器。
b)直接按照<SR Prefix:Hashvalue>，如A1:0001::0001，发起服务访问。
如果b)首先成功建立连接，则按照b)发起访问。
92，UE接入到MEC2，在5GC控制下，建立到MEC2的UPF的会话，在会话建立/修改时，得到一个Service Routing的前缀(同时也是一个SRv6的Locator)，B1:0001::/64。
类似的，UE访问local-weather.com，同时发起两种连接建立流程。
a)发起DNS解析，local DNS解析到地址，如BBBB::4534:4567，之 后根据该地址访问对应的服务器。
b)直接按照<SR Prefix:Hashvalue>，如B1:0001::0001，发起服务访问。
如果b)首先成功建立连接，则按照b)发起访问
类似的，local DNS解析时可选返回两个地址，如BBBB::4534:4567，B1:0001::0001，用于验证。另外，当有HASH冲突时(local service较多)，则使能较重要业务的SR访问，也可考虑更新两侧HASH算法。
从以上示例可以看出，本公开实施例实现了一种轻量级的用于MEC的服务路由技术方案，该方案不需要大网对于Service Routing路由的感知，不需要自定义的UDP协议去通告路由，例如，在MEC内部，网关可以直接按照IPv6地址通信，该方案也不需要处理复杂的HASH冲突问题。另外，该方案可以通过3GPP的信令来通告Service Routing的服务的IPv6 Prefix，不需要进行DHCP协议的扩展，同时，3GPP的终端不使用DHCP的场景中，也可以使能服务的SR快速接入。另外，在3GPP定义的架构中，UE切换MEC时，如何准确的访问MEC的内容，一种方式是通过local DNS上的处理，但是相关的机制比较复杂，还有可能依赖EDNS0之类的扩展。而在本公开实施例中，可以直接使用HASH后的地址进行MEC内容的访问，让DNS解析回归简单的配置。
以上介绍了本公开实施例的各种方法。下面将进一步提供实施上述方法的装置。
请参照图10，本公开实施例提供了一种终端，包括：
发送模块1001，配置为向第一边缘计算平台发送针对目标服务的第一连接建立请求和第一域名解析请求，其中，所述第一连接建立请求为基于服务路由的连接建立请求，所述第一域名解析请求为基于DNS协议的域名解析请求；
服务接入模块1002，配置为如果在接收到所述第一边缘计算平台对所 述第一域名解析请求的反馈消息之前，所述第一连接建立请求已经成功建立连接，则通过所述第一连接建立请求建立的第一连接接入所述目标服务。
可选的，所述终端还包括：
第一接收模块，配置为在向第一边缘计算平台发送针对目标服务的第一连接建立请求和第一域名解析请求之前，在建立或修改与所述第一边缘计算平台的用户面功能之间的会话的过程中，接收核心网的会话管理功能SMF发送的所述第一边缘计算平台的第一服务路由前缀。
可选的，所述发送模块1001，还配置为确定所述目标服务对应的服务标识，生成包括所述第一服务路由前缀和所述服务标识的第一目的地址，发送针对所述第一目的地址的访问请求。
可选的，所述终端还包括：
第二接收模块，配置为在发送所述第一域名解析请求之后，接收到所述第一边缘计算平台对所述第一域名解析请求的反馈消息，所述反馈消息携带有所述目标服务对应的第二目的地址；
所述服务接入模块1002，还配置为如果在接收到所述反馈消息时，所述第一连接建立请求尚未成功建立连接，则发送针对所述第二目的地址的第二连接建立请求；以及，利用第一连接请求和第二连接请求中最先建立的连接，接入所述目标服务。
可选的，所述第一服务路由前缀具体为：
所述第一边缘计算平台的本地服务器的第一公网IPv6地址的前缀，其中，所述第一边缘计算平台的各个本地服务器分别包括有第一公网IPv6地址和第二公网IPv6地址；
或者，
所述第一边缘计算平台的本地服务器的私网IPv6地址的前缀，所述私网地址为IPv6唯一本地地址ULA地址；
或者，
所述第一边缘计算平台的本地服务器的分段路由SRv6的段标识SID中的位置标识Locator。
可选的，所述终端还包括：
第三接收模块，配置为在发送针对所述目标服务的第一域名解析请求之后，还接收所述第一边缘计算平台返回的所述目标服务对应的服务路由地址；
所述服务接入模块1002，还配置为在所述第一连接建立请求先于所述第二连接建立请求成功建立连接的情况下，判断所述目标服务对应的服务路由地址是否与所述第一目的地址匹配：若是，则继续通过所述第一连接接入所述目标服务；否则，断开所述第一连接，通过所述第二连接建立请求建立所述第二连接，并通过所述第二连接接入所述目标服务。
可选的，所述服务接入模块1002，还配置为在判断所述目标服务对应的服务路由地址与所述第一目的地址匹配的情况下，取消所述第二连接建立请求的连接建立流程。
可选的，所述第一接收模块，还配置为接收所述第一边缘计算平台在PDU会话修改命令或PDU会话建立接受消息中携带的第一服务路由前缀。
需要说明的是，该实施例中的设备是与上述图3所示的方法对应的设备，上述各实施例中的实现方式均适用于该设备的实施例中，也能达到相同的技术效果。本公开实施例提供的上述设备，能够实现上述方法实施例所实现的所有方法步骤，且能够达到相同的技术效果，在此不再对本实施例中与方法实施例相同的部分及有益效果进行具体赘述。
请参照图11，本公开实施例提供的终端的一种结构示意图，该终端包括：处理器1101、收发机1102、存储器1103、用户接口1104和总线接口。
在本公开实施例中，终端还包括：存储在存储器上1103并可在处理器 1101上运行的程序。
所述处理器1101执行所述程序时实现以下步骤：
向第一边缘计算平台发送针对目标服务的第一连接建立请求和第一域名解析请求，其中，所述第一连接建立请求为基于服务路由的连接建立请求，所述第一域名解析请求为基于DNS协议的域名解析请求；
如果在接收到所述第一边缘计算平台对所述第一域名解析请求的反馈消息之前，所述第一连接建立请求已经成功建立连接，则通过所述第一连接建立请求建立的第一连接接入所述目标服务。
可选的，所述处理器执行所述程序时还实现以下步骤：
在向第一边缘计算平台发送针对目标服务的第一连接建立请求和第一域名解析请求之前，在建立或修改与所述第一边缘计算平台的用户面功能之间的会话的过程中，接收核心网的会话管理功能SMF发送的所述第一边缘计算平台的第一服务路由前缀。
可选的，所述处理器执行所述程序时还实现以下步骤：
确定所述目标服务对应的服务标识，生成包括所述第一服务路由前缀和所述服务标识的第一目的地址，发送针对所述第一目的地址的访问请求。
可选的，所述处理器执行所述程序时还实现以下步骤：
在发送所述第一域名解析请求之后，接收到所述第一边缘计算平台对所述第一域名解析请求的反馈消息，所述反馈消息携带有所述目标服务对应的第二目的地址；
如果在接收到所述反馈消息时，所述第一连接建立请求尚未成功建立连接，则发送针对所述第二目的地址的第二连接建立请求；以及，利用第一连接请求和第二连接请求中最先建立的连接，接入所述目标服务。
可选的，所述第一服务路由前缀具体为：
所述第一边缘计算平台的本地服务器的第一公网IPv6地址的前缀，其 中，所述第一边缘计算平台的各个本地服务器分别包括有第一公网IPv6地址和第二公网IPv6地址；
或者，
所述第一边缘计算平台的本地服务器的私网IPv6地址的前缀，所述私网地址为IPv6唯一本地地址ULA地址；
或者，
所述第一边缘计算平台的本地服务器的分段路由SRv6的段标识SID中的位置标识Locator。
可选的，所述处理器执行所述程序时还实现以下步骤：
在发送针对所述目标服务的第一域名解析请求之后，还接收所述第一边缘计算平台返回的所述目标服务对应的服务路由地址；
在所述第一连接建立请求先于所述第二连接建立请求成功建立连接的情况下，判断所述目标服务对应的服务路由地址是否与所述第一目的地址匹配：若是，则继续通过所述第一连接接入所述目标服务；否则，断开所述第一连接，通过所述第二连接建立请求建立所述第二连接，并通过所述第二连接接入所述目标服务。
可选的，所述处理器执行所述程序时还实现以下步骤：
在判断所述目标服务对应的服务路由地址与所述第一目的地址匹配的情况下，取消所述第二连接建立请求的连接建立流程。
可选的，所述处理器执行所述程序时还实现以下步骤：
接收所述第一边缘计算平台在PDU会话修改命令或PDU会话建立接受消息中携带的第一服务路由前缀。
可理解的，本公开实施例中，所述计算机程序被处理器1101执行时可实现上述图3所示的方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
在图11中，总线架构可以包括任意数量的互联的总线和桥，具体由处理器1101代表的一个或多个处理器和存储器1103代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。收发机1102可以是多个元件，即包括发送机和接收机，提供用于在传输介质上与各种其他装置通信的单元。针对不同的用户设备，用户接口1104还可以是能够外接内接需要设备的接口，连接的设备包括但不限于小键盘、显示器、扬声器、麦克风、操纵杆等。
处理器1101负责管理总线架构和通常的处理，存储器1103可以存储处理器1101在执行操作时所使用的数据。
需要说明的是，该实施例中的设备是与上述图3所示的方法对应的设备，上述各实施例中的实现方式均适用于该设备的实施例中，也能达到相同的技术效果。该设备中，收发机1102与存储器1103，以及收发机1102与处理器1101均可以通过总线接口通讯连接，处理器1101的功能也可以由收发机1102实现，收发机1102的功能也可以由处理器1101实现。在此需要说明的是，本公开实施例提供的上述设备，能够实现上述方法实施例所实现的所有方法步骤，且能够达到相同的技术效果，在此不再对本实施例中与方法实施例相同的部分及有益效果进行具体赘述。
在本公开的一些实施例中，还提供了一种计算机可读存储介质，其上存储有程序，该程序被处理器执行时实现以下步骤：
向第一边缘计算平台发送针对目标服务的第一连接建立请求和第一域名解析请求，其中，所述第一连接建立请求为基于服务路由的连接建立请求，所述第一域名解析请求为基于DNS协议的域名解析请求；
如果在接收到所述第一边缘计算平台对所述第一域名解析请求的反馈 消息之前，所述第一连接建立请求已经成功建立连接，则通过所述第一连接建立请求建立的第一连接接入所述目标服务。
该程序被处理器执行时能实现上述应用于终端侧的服务路由方法中的所有实现方式，且能达到相同的技术效果，为避免重复，此处不再赘述。
本公开实施例提供了图12所示的一种第一边缘计算平台，包括：
接收模块121，配置为接收终端发送的针对目标服务的第一连接建立请求和第一域名解析请求，其中，所述第一连接建立请求为基于服务路由的连接建立请求，所述第一域名解析请求为基于DNS协议的域名解析请求；
响应模块122，配置为根据所述第一连接建立请求，建立与所述终端之间的第一连接，以及，根据所述第一域名解析请求，获取解析得到的所述目标服务对应的第二目的地址，向所述终端发送对所述第一域名解析请求的反馈消息，所述反馈消息携带有所述第二目的地址。
可选的，所述第一连接建立请求为针对第一目的地址的访问请求，所述第一目的地址包括有所述第一边缘计算平台的第一服务路由前缀和所述目标服务对应的服务标识。
可选的，所述第一服务路由前缀具体为：
所述第一边缘计算平台的本地服务器的第一公网IPv6地址的前缀，其中，所述第一边缘计算平台的各个本地服务器分别包括有第一公网IPv6地址和第二公网IPv6地址；
或者，
所述第一边缘计算平台的本地服务器的私网IPv6地址的前缀，所述私网地址为IPv6唯一本地地址ULA地址；
或者，
所述第一边缘计算平台的本地服务器的分段路由SRv6的段标识SID中的位置标识Locator。
可选的，所述响应模块122，还配置为在发送所述反馈消息之后，接收所述终端发送的针对所述第二目的地址的第二连接建立请求。
可选的，所述响应模块122，还配置为利用所述第一连接请求和第二连接请求中最先建立的连接，为所述终端提供所述目标服务。
可选的，所述响应模块122，还配置为在向所述终端发送对所述第一域名解析请求的反馈消息时，还发送所述目标服务对应的服务路由地址。
需要说明的是，该实施例中的装置是与上述图4所示的方法对应的设备，上述各实施例中的实现方式均适用于该设备的实施例中，也能达到相同的技术效果。在此需要说明的是，本公开实施例提供的上述设备，能够实现上述方法实施例所实现的所有方法步骤，且能够达到相同的技术效果，在此不再对本实施例中与方法实施例相同的部分及有益效果进行具体赘述。
请参考图13，本公开实施例提供了第一边缘计算平台的一结构示意图，包括：处理器1301、收发机1302、存储器1303和总线接口，其中：
在本公开实施例中，第一边缘计算平台还包括：存储在存储器上1303并可在处理器1301上运行的程序，所述程序被处理器1301执行时实现如下步骤：
接收终端发送的针对目标服务的第一连接建立请求和第一域名解析请求，其中，所述第一连接建立请求为基于服务路由的连接建立请求，所述第一域名解析请求为基于DNS协议的域名解析请求；
根据所述第一连接建立请求，建立与所述终端之间的第一连接，以及，根据所述第一域名解析请求，获取解析得到的所述目标服务对应的第二目的地址，向所述终端发送对所述第一域名解析请求的反馈消息，所述反馈消息携带有所述第二目的地址。
可选的，所述第一连接建立请求为针对第一目的地址的访问请求，所 述第一目的地址包括有所述第一边缘计算平台的第一服务路由前缀和所述目标服务对应的服务标识。
可选的，所述第一服务路由前缀具体为：
所述第一边缘计算平台的本地服务器的第一公网IPv6地址的前缀，其中，所述第一边缘计算平台的各个本地服务器分别包括有第一公网IPv6地址和第二公网IPv6地址；
或者，
所述第一边缘计算平台的本地服务器的私网IPv6地址的前缀，所述私网地址为IPv6唯一本地地址ULA地址；
或者，
所述第一边缘计算平台的本地服务器的分段路由SRv6的段标识SID中的位置标识Locator。
可选的，所述处理器执行所述程序时还实现以下步骤：
在发送所述反馈消息之后，接收所述终端发送的针对所述第二目的地址的第二连接建立请求。
可选的，所述处理器执行所述程序时还实现以下步骤：
利用所述第一连接请求和第二连接请求中最先建立的连接，为所述终端提供所述目标服务。
可选的，所述处理器执行所述程序时还实现以下步骤：
在向所述终端发送对所述第一域名解析请求的反馈消息时，还发送所述目标服务对应的服务路由地址。
可理解的，本公开实施例中，所述计算机程序被处理器1301执行时可实现上述图4所示的方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
在图13中，总线架构可以包括任意数量的互联的总线和桥，具体由处 理器1301代表的一个或多个处理器和存储器1303代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。收发机1302可以是多个元件，即包括发送机和接收机，提供用于在传输介质上与各种其他装置通信的单元。
处理器1301负责管理总线架构和通常的处理，存储器1303可以存储处理器1301在执行操作时所使用的数据。
需要说明的是，该实施例中的终端是与上述图4所示的方法对应的设备，上述各实施例中的实现方式均适用于该终端的实施例中，也能达到相同的技术效果。该设备中，收发机1302与存储器1303，以及收发机1302与处理器1301均可以通过总线接口通讯连接，处理器1301的功能也可以由收发机1302实现，收发机1302的功能也可以由处理器1301实现。在此需要说明的是，本公开实施例提供的上述设备，能够实现上述方法实施例所实现的所有方法步骤，且能够达到相同的技术效果，在此不再对本实施例中与方法实施例相同的部分及有益效果进行具体赘述。
在本公开的一些实施例中，还提供了一种计算机可读存储介质，其上存储有程序，该程序被处理器执行时实现以下步骤：
接收终端发送的针对目标服务的第一连接建立请求和第一域名解析请求，其中，所述第一连接建立请求为基于服务路由的连接建立请求，所述第一域名解析请求为基于DNS协议的域名解析请求；
根据所述第一连接建立请求，建立与所述终端之间的第一连接，以及，根据所述第一域名解析请求，获取解析得到的所述目标服务对应的第二目的地址，向所述终端发送对所述第一域名解析请求的反馈消息，所述反馈消息携带有所述第二目的地址。
该程序被处理器执行时能实现上述应用于MEC的服务路由方法中的所有实现方式，且能达到相同的技术效果，为避免重复，此处不再赘述。
本公开实施例提供了图14所示的一种会话管理功能，包括：
发送模块141，配置为在建立终端与第一边缘计算平台的用户面功能之间的会话的过程中，向所述终端发送所述第一边缘计算平台的第一服务路由前缀。
可选的，所述发送模块141，还配置为在PDU会话修改命令或PDU会话建立接受消息携带第一服务路由前缀并发送给所述终端。
需要说明的是，该实施例中的装置是与上述图5所示的方法对应的设备，上述各实施例中的实现方式均适用于该设备的实施例中，也能达到相同的技术效果。在此需要说明的是，本公开实施例提供的上述设备，能够实现上述方法实施例所实现的所有方法步骤，且能够达到相同的技术效果，在此不再对本实施例中与方法实施例相同的部分及有益效果进行具体赘述。
请参考图15，本公开实施例提供了会话管理功能的一结构示意图，包括：处理器1501、收发机1502、存储器1503和总线接口，其中：
在本公开实施例中，会话管理功能还包括：存储在存储器上1503并可在处理器1501上运行的程序，所述程序被处理器1501执行时实现如下步骤：
在建立终端与第一边缘计算平台的用户面功能之间的会话的过程中，向所述终端发送所述第一边缘计算平台的第一服务路由前缀。
可选的，所述处理器执行所述程序时还实现以下步骤：
在PDU会话修改命令或PDU会话建立接受消息携带第一服务路由前缀并发送给所述终端。
可理解的，本公开实施例中，所述计算机程序被处理器1501执行时可 实现上述图5所示的方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
在图15中，总线架构可以包括任意数量的互联的总线和桥，具体由处理器1501代表的一个或多个处理器和存储器1503代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。收发机1502可以是多个元件，即包括发送机和接收机，提供用于在传输介质上与各种其他装置通信的单元。
处理器1501负责管理总线架构和通常的处理，存储器1503可以存储处理器1501在执行操作时所使用的数据。
需要说明的是，该实施例中的终端是与上述图5所示的方法对应的设备，上述各实施例中的实现方式均适用于该终端的实施例中，也能达到相同的技术效果。该设备中，收发机1502与存储器1503，以及收发机1502与处理器1501均可以通过总线接口通讯连接，处理器1501的功能也可以由收发机1502实现，收发机1502的功能也可以由处理器1501实现。在此需要说明的是，本公开实施例提供的上述设备，能够实现上述方法实施例所实现的所有方法步骤，且能够达到相同的技术效果，在此不再对本实施例中与方法实施例相同的部分及有益效果进行具体赘述。
在本公开的一些实施例中，还提供了一种计算机可读存储介质，其上存储有程序，该程序被处理器执行时实现以下步骤：
在建立终端与第一边缘计算平台的用户面功能之间的会话的过程中，向所述终端发送所述第一边缘计算平台的第一服务路由前缀。
该程序被处理器执行时能实现上述应用于SMF的服务路由方法中的所有实现方式，且能达到相同的技术效果，为避免重复，此处不再赘述。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本公开的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本公开实施例方案的目的。
另外，在本公开各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本公 开的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本公开各个实施例所述的方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、ROM、RAM、磁碟或者光盘等各种可以存储程序代码的介质。
需要说明的是：本公开实施例所记载的技术方案之间，在不冲突的情况下，可以任意组合。
以上所述，仅为本发明的具体实施方式，但本发明的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本发明揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本发明的保护范围之内。因此，本发明的保护范围应以权利要求的保护范围为准。

Claims (26)

  1. 一种服务路由方法，包括：
    终端向第一边缘计算平台发送针对目标服务的第一连接建立请求和第一域名解析请求，其中，所述第一连接建立请求为基于服务路由的连接建立请求，所述第一域名解析请求为基于DNS协议的域名解析请求；
    如果在接收到所述第一边缘计算平台对所述第一域名解析请求的反馈消息之前，所述第一连接建立请求已经成功建立连接，则通过所述第一连接建立请求建立的第一连接接入所述目标服务。
  2. 如权利要求1所述的方法，其中，在向第一边缘计算平台发送针对目标服务的第一连接建立请求和第一域名解析请求之前，所述方法还包括：
    所述终端在建立或修改与所述第一边缘计算平台的用户面功能之间的会话的过程中，接收核心网的会话管理功能SMF发送的所述第一边缘计算平台的第一服务路由前缀。
  3. 如权利要求2所述的方法，其中，
    发送所述第一连接建立请求包括：所述终端确定所述目标服务对应的服务标识，生成包括所述第一服务路由前缀和所述服务标识的第一目的地址，发送针对所述第一目的地址的访问请求。
  4. 如权利要求3所述的方法，其中，
    在发送所述第一域名解析请求之后，所述方法还包括：所述终端接收到所述第一边缘计算平台对所述第一域名解析请求的反馈消息，所述反馈消息携带有所述目标服务对应的第二目的地址；
    如果在接收到所述反馈消息时，所述第一连接建立请求尚未成功建立连接，所述终端发送针对所述第二目的地址的第二连接建立请求；以及，利用第一连接请求和第二连接请求中最先建立的连接，接入所述目标服务。
  5. 如权利要求4所述的方法，其中，还包括：
    所述终端在发送针对所述目标服务的第一域名解析请求之后，还接收所述第一边缘计算平台返回的所述目标服务对应的服务路由地址；
    在所述第一连接建立请求先于所述第二连接建立请求成功建立连接的情况下，所述终端判断所述目标服务对应的服务路由地址是否与所述第一目的地址匹配：若是，则继续通过所述第一连接接入所述目标服务；否则，断开所述第一连接，通过所述第二连接建立请求建立所述第二连接，并通过所述第二连接接入所述目标服务。
  6. 如权利要求5所述的方法，其中，在判断所述目标服务对应的服务路由地址与所述第一目的地址匹配的情况下，所述方法还包括：
    取消所述第二连接建立请求的连接建立流程。
  7. 如权利要求2至5任一项所述的方法，其中，所述第一服务路由前缀具体为：
    所述第一边缘计算平台的本地服务器的第一公网IPv6地址的前缀，其中，所述第一边缘计算平台的各个本地服务器分别包括有第一公网IPv6地址和第二公网IPv6地址；
    或者，
    所述第一边缘计算平台的本地服务器的私网IPv6地址的前缀，所述私网地址为IPv6唯一本地地址ULA地址；
    或者，
    所述第一边缘计算平台的本地服务器的分段路由SRv6的段标识SID中的位置标识Locator。
  8. 如权利要求2至5任一项所述的方法，其中，所述接收所述第一边缘计算平台发送的第一服务路由前缀，具体为：
    接收所述第一边缘计算平台在PDU会话修改命令或PDU会话建立接受消息中携带的第一服务路由前缀。
  9. 一种服务路由方法，包括：
    第一边缘计算平台接收终端发送的针对目标服务的第一连接建立请求和第一域名解析请求，其中，所述第一连接建立请求为基于服务路由的连接建立请求，所述第一域名解析请求为基于DNS协议的域名解析请求；
    所述第一边缘计算平台根据所述第一连接建立请求，建立与所述终端之间的第一连接，以及，根据所述第一域名解析请求，获取解析得到的所述目标服务对应的第二目的地址，向所述终端发送对所述第一域名解析请求的反馈消息，所述反馈消息携带有所述第二目的地址。
  10. 如权利要求9所述的方法，其中，
    所述第一连接建立请求为针对第一目的地址的访问请求，所述第一目的地址包括有所述第一边缘计算平台的第一服务路由前缀和所述目标服务对应的服务标识。
  11. 如权利要求9所述的方法，其中，在发送所述反馈消息之后，所述方法还包括：
    接收所述终端发送的针对所述第二目的地址的第二连接建立请求。
  12. 如权利要求11所述的方法，其中，还包括：
    利用所述第一连接请求和第二连接请求中最先建立的连接，为所述终端提供所述目标服务。
  13. 如权利要求9所述的方法，其中，还包括：
    所述第一边缘计算平台在向所述终端发送对所述第一域名解析请求的反馈消息时，还发送所述目标服务对应的服务路由地址。
  14. 如权利要求10至13任一项所述的方法，其中，所述第一服务路由前缀具体为：
    所述第一边缘计算平台的本地服务器的第一公网IPv6地址的前缀，其中，所述第一边缘计算平台的各个本地服务器分别包括有第一公网IPv6地 址和第二公网IPv6地址；
    或者，
    所述第一边缘计算平台的本地服务器的私网IPv6地址的前缀，所述私网地址为IPv6唯一本地地址ULA地址；
    或者，
    所述第一边缘计算平台的本地服务器的分段路由SRv6的段标识SID中的位置标识Locator。
  15. 一种服务路由方法，包括：
    核心网的会话管理功能SMF，在建立终端与第一边缘计算平台的用户面功能之间的会话的过程中，向所述终端发送所述第一边缘计算平台的第一服务路由前缀。
  16. 如权利要求15所述的方法，其中，所述向所述终端发送所述第一边缘计算平台的第一服务路由前缀，具体为：
    在PDU会话修改命令或PDU会话建立接受消息携带第一服务路由前缀并发送给所述终端。
  17. 一种终端，包括：
    发送模块，配置为向第一边缘计算平台发送针对目标服务的第一连接建立请求和第一域名解析请求，其中，所述第一连接建立请求为基于服务路由的连接建立请求，所述第一域名解析请求为基于DNS协议的域名解析请求；
    服务接入模块，配置为如果在接收到所述第一边缘计算平台对所述第一域名解析请求的反馈消息之前，所述第一连接建立请求已经成功建立连接，则通过所述第一连接建立请求建立的第一连接接入所述目标服务。
  18. 一种终端，包括收发机和处理器，其中，
    所述收发机，配置为向第一边缘计算平台发送针对目标服务的第一连 接建立请求和第一域名解析请求，其中，所述第一连接建立请求为基于服务路由的连接建立请求，所述第一域名解析请求为基于DNS协议的域名解析请求；
    所述处理器，配置为如果在接收到所述第一边缘计算平台对所述第一域名解析请求的反馈消息之前，所述第一连接建立请求已经成功建立连接，则通过所述第一连接建立请求建立的第一连接接入所述目标服务。
  19. 一种终端，包括：处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序，所述程序被所述处理器执行时实现如权利要求1至8任一项所述的方法的步骤。
  20. 一种第一边缘计算平台，包括：
    接收模块，配置为接收终端发送的针对目标服务的第一连接建立请求和第一域名解析请求，其中，所述第一连接建立请求为基于服务路由的连接建立请求，所述第一域名解析请求为基于DNS协议的域名解析请求；
    响应模块，配置为根据所述第一连接建立请求，建立与所述终端之间的第一连接，以及，根据所述第一域名解析请求，获取解析得到的所述目标服务对应的第二目的地址，向所述终端发送对所述第一域名解析请求的反馈消息，所述反馈消息携带有所述第二目的地址。
  21. 一种第一边缘计算平台，包括收发机和处理器，其中，
    所述收发机，配置为接收终端发送的针对目标服务的第一连接建立请求和第一域名解析请求，其中，所述第一连接建立请求为基于服务路由的连接建立请求，所述第一域名解析请求为基于DNS协议的域名解析请求；
    所述处理器，配置为根据所述第一连接建立请求，建立与所述终端之间的第一连接，以及，根据所述第一域名解析请求，获取解析得到的所述目标服务对应的第二目的地址，向所述终端发送对所述第一域名解析请求的反馈消息，所述反馈消息携带有所述第二目的地址。
  22. 一种第一边缘计算平台，包括：处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序，所述程序被所述处理器执行时实现如权利要求9至14任一项所述的方法的步骤。
  23. 一种核心网的会话管理功能，包括：
    发送模块，配置为在建立终端与第一边缘计算平台的用户面功能之间的会话的过程中，向所述终端发送所述第一边缘计算平台的第一服务路由前缀。
  24. 一种核心网的会话管理功能，包括收发机和处理器，其中，
    所述收发机，配置为在建立终端与第一边缘计算平台的用户面功能之间的会话的过程中，向所述终端发送所述第一边缘计算平台的第一服务路由前缀。
  25. 一种核心网的会话管理功能，包括：处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序，所述程序被所述处理器执行时实现如权利要求15至16任一项所述的方法的步骤。
  26. 一种计算机可读存储介质，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现如权利要求1至16任一项所述的方法的步骤。
PCT/CN2022/085388 2021-04-13 2022-04-06 服务路由方法及设备 WO2022218194A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110393967.0A CN115250289A (zh) 2021-04-13 2021-04-13 服务路由方法及设备
CN202110393967.0 2021-04-13

Publications (1)

Publication Number Publication Date
WO2022218194A1 true WO2022218194A1 (zh) 2022-10-20

Family

ID=83639479

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/085388 WO2022218194A1 (zh) 2021-04-13 2022-04-06 服务路由方法及设备

Country Status (2)

Country Link
CN (1) CN115250289A (zh)
WO (1) WO2022218194A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101014046A (zh) * 2007-02-02 2007-08-08 清华大学 服务承载网中服务定位和服务质量路由的集成方法
WO2011113289A1 (zh) * 2010-03-17 2011-09-22 华为技术有限公司 一种业务路由方法和业务网络
US20180317157A1 (en) * 2017-04-27 2018-11-01 Samsung Electronics Co., Ltd. Method and apparatus for registration type addition for service negotiation
CN110225144A (zh) * 2018-03-02 2019-09-10 华为技术有限公司 获取及提供服务的方法、用户设备和管理服务器

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101296225B (zh) * 2007-04-29 2012-08-08 华为技术有限公司 会话管理功能装置及提供业务的系统和方法
US10104039B1 (en) * 2017-09-28 2018-10-16 Cloudflare, Inc. Establishing and using a tunnel from an origin server in a distributed edge compute and routing service

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101014046A (zh) * 2007-02-02 2007-08-08 清华大学 服务承载网中服务定位和服务质量路由的集成方法
WO2011113289A1 (zh) * 2010-03-17 2011-09-22 华为技术有限公司 一种业务路由方法和业务网络
US20180317157A1 (en) * 2017-04-27 2018-11-01 Samsung Electronics Co., Ltd. Method and apparatus for registration type addition for service negotiation
CN110225144A (zh) * 2018-03-02 2019-09-10 华为技术有限公司 获取及提供服务的方法、用户设备和管理服务器

Also Published As

Publication number Publication date
CN115250289A (zh) 2022-10-28

Similar Documents

Publication Publication Date Title
KR100953805B1 (ko) 이동 컴퓨팅 장치를 위한 가상사설망 구조 재사용
US10284659B2 (en) Hybrid unicast/multicast DNS-based service discovery
US7991854B2 (en) Dynamic session maintenance for mobile computing devices
US20230354149A1 (en) Method for identification of traffic suitable for edge breakout and for traffic steering in a mobile network
US9319377B2 (en) Auto-split DNS
JP2013527632A (ja) マルチｎａｔ６４環境のための方法及びホストノード
JP2011205614A (ja) Ｉｐｓｅｃとｉｐｖ６近隣要請の競合解消方法及びそのシステム
US8018847B2 (en) System and method for redirecting requests
WO2019170114A1 (zh) 发送报文的方法、网络设备及计算机可读存储介质
JP2006086800A (ja) ソースアドレスを選択する通信装置
US9794115B2 (en) Method, device and system for an application layer traffic optimization server
JP5147995B2 (ja) ホスト・アイデンティティ・プロトコル・サーバ・アドレス構成
JP2015507379A (ja) Ｉｄ／ロケータ分離ベースのネットワークにおいてネームレジストリ，ネットワークアクセスおよびデータ通信を安全に行う方法
WO2011131097A1 (zh) 数据报文处理方法、系统及接入服务节点
WO2019165948A1 (zh) 获取及提供服务的方法、用户设备和管理服务器
CN111711705B (zh) 基于代理节点作双向nat实现网络连接的方法和装置
US8705471B2 (en) Method and system for implementing ID/locator mapping
CN114338522A (zh) 基于标识管理的IPv6编址与组网方法
US20120201250A1 (en) Method, apparatus and system for implementing multi-party communication
WO2022218194A1 (zh) 服务路由方法及设备
US20120072513A1 (en) Method and system for obtaining host identity tag
JP4586721B2 (ja) 通信中にアドレス変更が可能な通信装置、システム及び通信方法
WO2022135132A1 (zh) 业务处理方法、装置、电子设备及存储介质
WO2015139397A1 (zh) 一种nat64资源获取方法及获取/分配装置
JP3864397B2 (ja) ユーザエッジルータ、ゲートウェイルータ、マルチホーミング通信システム、マルチホーミング通信方法およびマルチホーミング通信プログラム

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205 DATED 08/02/2024)