Communication method, device and system

Abstract

Provided are a communication method, apparatus and system, comprising: a first network element receiving a first query message of a first anchor point of a session from a terminal device, the first query message comprising a domain name, the first query message being used for querying an address of a server providing a service corresponding to the domain name for the terminal device; the first network element obtains an address of a first server according to the first query message, wherein the first server is used for providing a service corresponding to the domain name for the terminal device; the first network element determines a data network access identifier corresponding to the address of the first server; and the first network element sends a first message used for determining a shunting point to the session management network element, the first message comprises the address of the first server and the data network access identifier, and the shunting point is used for sending the data of the session to the first server through the second anchor point. According to the method, data transmission between the terminal equipment and the server is facilitated.

Description

Technical Field

[0001] This application relates to the field of communications, and more particularly, to a communication method, apparatus, and system. Background Art

[0002] After a terminal device accesses a network, it can establish a session with the network. Then, through the anchor point of the session, it transmits data of a service to a server providing the service in a data network, so as to use the service provided by the server. When the terminal device wants to use a new service, the network can select a server providing the new service for the terminal device, but the anchor point of the session may not guarantee the quality of data transmission between the terminal device and the server providing the new service. Summary of the Invention

[0003] Embodiments of this application provide a communication method, apparatus, and system, which are beneficial to data transmission between a terminal device and a server.

[0004] In a first aspect, a communication method is provided. This method can be executed by a first network element, or can also be executed by a chip or circuit of the first network element. This application does not make any limitations in this regard. For ease of description, the following takes the execution by the first network element as an example for illustration.

[0005] The method includes: The first network element receives a first query message from a first user plane network element. The first query message includes a domain name, and the first query message is used to query the address of a server providing the service corresponding to the domain name for the terminal device. The first user plane network element serves the session of the terminal device. The first network element obtains the address of a first server according to the first query message. The first network element determines a data network access identifier corresponding to the address of the first server. The first network element sends a first message for determining a second user plane network element to a session management network element. The first message includes the address of the first server and the data network access identifier. The second user plane network element is used to forward data packets belonging to the session sent by the terminal device to the first server to the first server.

[0006] Based on this method, the first network element can provide a first message for determining a second user plane network element to the session management network element according to the address of the first server providing the service for the terminal device. Thus, data sent by the terminal device in the session to the first server can be forwarded to the first server by the second user plane network element instead of the first user plane network element, which is beneficial to data transmission between the terminal device and the first server.

[0007] In combination with the first aspect, in some implementation manners of the first aspect, the first user plane network element is the anchor point of the session, and the second user plane network element includes a split point and a local anchor point of the session. The split point is used to send data packets of the session to the server via the local anchor point.

[0008] In a second aspect, a communication method is provided. This method can be executed by a first network element, or alternatively, by a chip or circuit of the first network element. This application does not limit this. For ease of description, the following takes the execution by the first network element as an example for illustration.

[0009] The method includes: the first network element receives a first query message of a first anchor point of a session from a terminal device. The first query message includes a domain name and is used to query the address of a server that provides services corresponding to the domain name for the terminal device; the first network element obtains the address of a first server according to the first query message, where the first server is used to provide services corresponding to the domain name for the terminal device; the first network element determines a data network access identifier corresponding to the address of the first server; the first network element sends a first message for determining a traffic splitting point to a session management network element. The first message includes the address of the first server and the data network access identifier, and the traffic splitting point is used to send the data of the session to the first server via a second anchor point. Here, the first anchor point and the second anchor point are different.

[0010] Based on this method, the first network element can provide a first message for determining a traffic splitting point to the session management network element according to the address of the first server that provides services for the terminal device. Under the processing of the traffic splitting point, the data of the session, such as the data sent by the terminal device to the first server, can be sent to the first server via the second anchor point instead of the first anchor point, which is beneficial to data transmission between the terminal device and the first server.

[0011] Among them, that the first message is used to determine the traffic splitting point can be that the data network access identifier in the first message is used to determine the traffic splitting point.

[0012] Combined with the second aspect, in some implementation manners of the second aspect, the first anchor point is an anchor point configured by the session management network element for data transmission between the terminal device and the data network, and the first server is a server in the data network.

[0013] Combined with the first aspect and the second aspect, in some implementation manners of the first aspect and the second aspect, the first message is further used to determine the second anchor point. For example, the data network access identifier in the first message is further used to determine the second anchor point.

[0014] Combining the first aspect and the second aspect, in some implementations of the first aspect and the second aspect, the server deployment information includes the correspondence between each of one or more data network access identifiers and the address of the server, where the one or more data network access identifiers include the data network access identifier, and the address of the server includes the address of the first server; the first network element determines the data network access identifier corresponding to the address of the first server, including: the first network element determines the data network access identifier corresponding to the address of the first server according to the server deployment information. The data network access identifier determined by the first network element according to the server deployment information helps to select a transmission path with higher session quality.

[0015] Optionally, the server deployment information is pre-configured in the first network element or is received by the first network element from other network elements.

[0016] Optionally, the first network element combines the server deployment information and the location of the terminal device to determine the data network access identifier corresponding to the address of the first server, which helps to obtain a more suitable data network access identifier for the terminal device.

[0017] Combining the first aspect and the second aspect, in some implementations of the first aspect and the second aspect, before the first network element sends a first message for determining a traffic splitting point to the session management network element, it further includes: the first network element determines to send the first message to the session management network element according to a processing rule (such as a DNS processing rule), where the processing rule matches the domain name or the address of the first server, and the processing rule indicates that the first message needs to be sent to the session management network element. The first network element can communicate with the session management network element based on the management mechanism of the processing rule.

[0018] Combining the first aspect and the second aspect, in some implementations of the first aspect and the second aspect, the first network element obtains the address of the first server according to the first query message, including: the first network element determines that the second query message includes option information according to a processing rule, where the option information is used to determine the address of the first server, the processing rule matches the domain name and corresponds to the session, and the processing rule indicates that the query message sent to the domain name server needs to include option information; the first network element sends a second query message to the domain name server, the second query message includes the domain name and the option information, and the second query message is used to query the address of the server corresponding to the domain name; the first network element receives the address of the first server from the domain name server. Based on the clear indication of the processing rule, the first network element can accurately determine whether option information needs to be included in the second query message.

[0019] Combining the first aspect and the second aspect, in some implementations of the first aspect and the second aspect, the first network element obtains the address of the first server according to the first query message, including: the first network element sends a second query message to the domain name server according to a processing rule, where the processing rule matches the domain name and corresponds to the session, the processing rule includes the address of the domain name server, the second query message includes the domain name, and the second query message is used to query the address of the server corresponding to the domain name; the first network element receives the address of the first server from the domain name server. Based on the processing rule, the first network element can quickly determine which domain name server to send the second query message to.

[0020] Combining the first aspect and the second aspect, in some implementations of the first aspect and the second aspect, the method further includes: the first network element generates the processing rule according to the server deployment information and / or the feature information, the server deployment information indicates how each server is deployed in the data network, the first server is a server in the data network, and the feature information is used to describe the features of the session or the terminal device. The processing rule generated by the method facilitates the first network element to determine the information related to the transmission path of the session.

[0021] Combining the first aspect and the second aspect, in some implementations of the first aspect and the second aspect, before the first network element generates the processing rule according to the server deployment information and / or the feature information, the method further includes: the first network element receives indication information from the session management network element, the indication information is used to indicate the first network element to generate a processing rule corresponding to the session; or, the method further includes: the first network element receives the processing rule from the session management network element, the processing rule includes the identification information of the baseline processing rule, the baseline processing rule is generated by the first network element according to the server deployment information and / or the feature information, the server deployment information indicates how each server is deployed in the data network, the first server is a server in the data network, and the feature information is used to describe the features of the session or the terminal device. The first network element can accept the indication or rule of the session management network element, which helps the network to manage the session.

[0022] In a third aspect, a communication method is provided. This method can be executed by a session management network element, or can also be executed by a chip or circuit of the session management network element. This application does not make any limitation in this regard. For the sake of convenience of description, the following takes the execution by the session management network element as an example for illustration.

[0023] The method includes: the session management network element selects a first anchor point for the session of the terminal device, where the first anchor point is used to transmit data between the terminal device and the data network, and the data includes a first query message which includes a domain name and is used to query the address of the server that provides services corresponding to the domain name for the terminal device; the session management network element receives a first message from a first network element, where the first message includes the address of the first server and a data network access identifier, and the first server is a server in the data network; the session management network element determines a splitting point according to the first message; the session management network element instructs the splitting point to send the data of the session to the first server via a second anchor point. Herein, the first anchor point and the second anchor point are different.

[0024] Based on this method, the session management network element determines a splitting point according to the first message provided by the first network element, and configures the splitting point to send the data of the session, such as the data sent by the terminal device to the first server, to the first server via the second anchor point instead of the first anchor point, which is beneficial to the data transmission between the terminal device and the first server.

[0025] Herein, the session management network element may determine the splitting point according to the data network access identifier in the first message.

[0026] In combination with the third aspect, in some implementation manners of the third aspect, the method further includes: the session management network element determines the second anchor point according to the first message. For example, the session management network element determines the second anchor point according to the data network access identifier in the first message. The session management network element can determine the splitting point and the second anchor point simultaneously according to the same message, which can improve the processing efficiency of the session management network element, thereby quickly establishing a data transmission path between the terminal device and the first server.

[0027] In combination with the third aspect, in some implementation manners of the third aspect, the first query message further includes the address of the first network element, and the method further includes: when at least one of the following conditions is satisfied, the session management network element sends the address of the first network element to the terminal device: the terminal device is outside the service range of the session management network element; the data network access identifier of the session is a data network access identifier not supported by the session management network element; the terminal device is within the service range of the first network element; the data network access identifier of the session corresponds to the first network element; or, the domain name in the first query message corresponds to the first network element. The session management network element determines to let the first network element provide query services for the terminal device according to the conditions, which helps to improve the reliability of the query.

[0028] In combination with the third aspect, in some implementation manners of the third aspect, when the at least one condition is satisfied, the session management network element sends indication information to the first network element, where the indication information is used to instruct the first network element to generate a processing rule corresponding to the session, the processing rule is used to obtain the address of the server, or the processing rule is used to indicate that the first message needs to be sent to the session management network element. The session management network element instructing the first network element to generate a processing rule helps the network to manage the session.

[0029] In combination with the third aspect, in some implementation manners of the third aspect, the session management network element sends feature information to the first network element, where the feature information is used to describe the features of the session or the terminal device, and the feature information is used to generate the processing rule. The session management network element providing the first network element with the feature information for generating the processing rule facilitates the first network element to generate a processing rule for determining information related to the transmission path of the session to be more in line with the features of the session or the terminal device.

[0030] In combination with the third aspect, in some implementation manners of the third aspect, the method further includes: when the at least one condition is satisfied, the session management network element sends a processing rule corresponding to the session to the first network element, the processing rule is used to obtain the address of the server, or the processing rule is used to indicate that the first message needs to be sent to the session management network element; where the processing rule includes identification information of a baseline processing rule, and the baseline processing rule is generated by the first network element according to server deployment information and / or feature information, the server deployment information indicates how each server is deployed in the data network, the first server is a server in the data network, and the feature information is used to describe the features of the session or the terminal device. The session management network element sending the processing rule to the first network element helps the network to manage the session

[0031] In combination with the third aspect, in some implementation manners of the third aspect, the method further includes: before the session management network element receives the first message from the first network element, the method further includes: the session management network element receives the domain name from the second network element, where the second network element is used to provide the address of the server for the terminal device; the session management network element sends a second message to the second network element according to the domain name, and the second message is used to instruct the second network element to send a query message including the domain name to the first network element. The session management network element clearly instructing the second network element to forward the query message to the first network element helps to implement the session management network element's management of the session.

[0032] In combination with the third aspect, in some implementation manners of the third aspect, the method further includes: before the session management network element receives a first message from a first network element, the method further includes: the session management network element sends a second processing rule to a second network element, where the second network element is used to provide an address of a server for the terminal device, the second processing rule corresponds to the session and matches the domain name, and the second processing rule further includes: sending a query message including the domain name to the first network element. Configuring the processing rule for the second network element by the session management network element helps to implement the management of the session by the session management network element.

[0033] In a fourth aspect, a communication device is provided, and the communication device is configured to execute the method in the first aspect or any possible implementation manner of the first aspect. The communication device includes a unit configured to execute the method in the first aspect or any possible implementation manner of the first aspect.

[0034] In a fifth aspect, a communication device is provided, and the communication device is configured to execute the method in the second aspect or any possible implementation manner of the second aspect. The communication device includes a unit configured to execute the method in the second aspect or any possible implementation manner of the second aspect.

[0035] In a sixth aspect, a communication device is provided, and the communication device is configured to execute the method in the third aspect or any possible implementation manner of the third aspect. The communication device includes a unit configured to execute the method in the third aspect or any possible implementation manner of the third aspect.

[0036] In the fourth aspect, the fifth aspect, or the sixth aspect, the above-mentioned communication device may include a transceiver unit and a processing unit. For the specific descriptions of the transceiver unit and the processing unit, reference may also be made to the device embodiments shown below. The beneficial effects of the above-mentioned fourth aspect to the sixth aspect may refer to the relevant descriptions of the foregoing first aspect to the third aspect, and will not be elaborated here.

[0037] In a seventh aspect, a communication device is provided, and the communication device includes a processor configured to execute the method shown in the first aspect, the second aspect, the third aspect, or any possible implementation manner of any one of the foregoing aspects. Alternatively, the processor is configured to execute a program stored in a memory, and when the program is executed, the method shown in the first aspect, the second aspect, the third aspect, or any possible implementation manner of any one of the foregoing aspects is executed.

[0038] In combination with the seventh aspect, in a possible implementation manner, the memory is located outside the above-mentioned communication device.

[0039] In combination with the seventh aspect, in a possible implementation manner, the memory is located inside the above-mentioned communication device.

[0040] In this application, the processor and the memory may also be integrated into one device, that is, the processor and the memory may also be integrated together.

[0041] Combined with the seventh aspect, in a possible implementation, the communication device further includes a transceiver, which is used to send or receive information.

[0042] In the eighth aspect, a communication device is provided. The communication device may include a processor and an interface circuit, and the processor is connected to the interface circuit. Among them, the interface circuit is used to interact (or send and receive or input and output) information or data, and the processor is used to run program instructions so that the communication device executes the method described in any possible implementation of the first aspect, the second aspect, the third aspect, or any one of them above. Among them, the interface circuit may be a communication interface or a transceiver. The transceiver may be a radio frequency module in the communication device, or a combination of a radio frequency module and an antenna, or an input / output interface of a chip or a circuit.

[0043] In the ninth aspect, a readable storage medium is provided. Program instructions are stored on the readable storage medium, and when it runs on a computer, it causes the computer to execute the method described in any possible implementation of the first aspect, the second aspect, the third aspect, or any one of them above.

[0044] In the tenth aspect, a program product containing program instructions is provided. When it runs, it causes the method described in any possible implementation of the first aspect, the second aspect, the third aspect, or any one of them above to be executed.

[0045] In the eleventh aspect, a device is provided. The device may be implemented in the form of a chip or in the form of a device. The device includes a processor. The processor is used to read and execute the program stored in the memory to execute one or more of the first aspect, the second aspect, or the third aspect, or one or more of the communication methods provided in any possible implementation of any one of them above. Optionally, the device further includes a memory, and the memory is connected to the processor through a circuit. Further optionally, the device further includes a communication interface, and the processor is connected to the communication interface. The communication interface is used to receive information to be processed, and the processor obtains the information from the communication interface, processes the information, and outputs the processing result through the communication interface. The communication interface may be an input / output interface.

[0046] In a possible implementation, the above-mentioned processor and memory may be physically independent units, or the memory may also be integrated with the processor.

[0047] In a twelfth aspect, a communication system is provided. The communication system includes a first network element and a session management network element. Optionally, the communication system further includes one or more of a traffic splitting point, a first anchor point, or a second anchor point. The first network element may be used to execute the method described in any possible implementation manner of the above first aspect, or the second aspect, or any one of them. The session management network element may execute the method described in any possible implementation manner of the above third aspect, or any one of them. The traffic splitting point is used to send the data of the session of the terminal device to the first server via the second anchor point. The first anchor point is used to transmit the data between the terminal device and the data network, and the first server is a server in the data network. The second anchor point is used to send the data of the session from the traffic splitting point to the first server.

[0048] In a thirteenth aspect, a communication system is provided. The communication system includes a session management network element, a traffic splitting point, a first anchor point, and a second anchor point. Optionally, the communication system further includes a first network element. The session management network element may execute the method described in any possible implementation manner of the above third aspect, or any one of them. The traffic splitting point is used to send the data of the session of the terminal device to the first server via the second anchor point. The first anchor point is used to transmit the data between the terminal device and the data network, and the first server is a server in the data network. The second anchor point is used to send the data of the session from the traffic splitting point to the first server. The first network element may be used to execute the method described in any possible implementation manner of the above first aspect, or the second aspect, or any one of them.

[0049] In a fourteenth aspect, a communication method is provided. The method includes: the session management network element selects a first anchor point for the session of the terminal device. The first anchor point is used to transmit the data between the terminal device and the data network, and the data includes a first query message. The first query message includes a domain name, and the first query message is used to query the address of the server that provides the service corresponding to the domain name for the terminal device. The first network element receives the first query message from the first anchor point. The first network element obtains the address of the first server according to the first query message. The first server is a server in the data network. The first network element determines the data network access identifier corresponding to the address of the first server. The first network element sends a first message to the session management network element. The first message includes the address of the first server and the data network access identifier. The session management network element determines the traffic splitting point according to the first message. The session management network element instructs the traffic splitting point to send the data of the session to the first server via the second anchor point.

[0050] In combination with the fourteenth aspect, in certain implementations of the fourteenth aspect, the method further includes: the first anchor point sending the first query message to the first network element; the traffic splitting point sending the data of the session to the second anchor point; the second anchor point receiving the data of the session from the traffic splitting point and sending the data of the session to the first server.

[0051] The fifteenth aspect provides a communication method, which includes: a session management network element selecting a first anchor point for a session of a terminal device; the first anchor point sending a first query message to a first network element, the first query message including a domain name, and the first query message being used to query the address of a server that provides services corresponding to the domain name for the terminal device; the session management network element receiving a first message from the first network element, the first message including the address of the first server and a data network access identifier, and the first server being a server in the data network; the session management network element determining a traffic splitting point according to the first message; the session management network element instructing the traffic splitting point to send the data of the session to the first server via a second anchor point; the traffic splitting point sending the data of the session to the second anchor point; the second anchor point receiving the data of the session from the traffic splitting point and sending the data of the session to the first server.

[0052] In combination with the fifteenth aspect, in certain implementations of the fifteenth aspect, the method further includes: the first network element receiving a first query message from the first anchor point of the session of the terminal device, the first query message including a domain name, and the first query message being used to query the address of a server that provides services corresponding to the domain name for the terminal device; the first network element obtaining the address of the first server according to the first query message, the first server being used to provide services corresponding to the domain name for the terminal device; the first network element determining a data network access identifier corresponding to the address of the first server; the first network element sending a first message for determining a traffic splitting point to the session management network element, the first message including the address of the first server and the data network access identifier, and the traffic splitting point being used to send the data of the session to the first server via a second anchor point.

[0053] The technical effects achieved by the above aspects can be referred to each other or to the beneficial effects in the method embodiments shown below. Details are not described herein again. BRIEF DESCRIPTION OF THE DRAWINGS

[0054] Figure 1 FIG. 15 is a schematic diagram of a network architecture 100 applicable to embodiments of the present application.

[0055] Figure 2 FIG. 19 is a flowchart of a communication method 200 provided by an embodiment of the present application.

[0056] Figure 3 FIG. 23 is a flowchart of a communication method 300 provided by an embodiment of the present application.

[0057] Figure 4 It is a schematic flowchart of a communication method 400 provided by an embodiment of the present application.

[0058] Figure 5 It is a schematic flowchart of a communication method 500 provided by an embodiment of the present application.

[0059] Figure 6 It is a schematic block diagram of a communication device 1000 provided by an embodiment of the present application.

[0060] Figure 7 It is a schematic block diagram of another communication device 2000 provided by an embodiment of the present application.

[0061] Figure 8 It is a schematic diagram of a chip system 3000 provided by an embodiment of the present application. Detailed implementation manners

[0062] All kinds of communication systems involve data transmission. For example, a common operator network, also known as a public land mobile network (PLMN), is a network established and operated by a government or its approved operator, such as a mobile network operator (MNO), for the purpose of providing public land mobile communication services, which involves data transmission. The embodiments of the present application may be exemplified based on a PLMN or a network that meets the requirements of the 3rd generation partnership project (3GPP) standard, simply referred to as a 3GPP network. Among them, the 3GPP network includes but is not limited to the 5th-generation (5G) mobile communication network, the 4th-generation (4G) mobile communication network (also known as the long term evolution (LTE) network), and future other communication systems, such as the 6th-generation (6G) mobile communication network, etc.

[0063] Figure 1 Taking the 5G network based on the service-based architecture (SBA) in the 3GPP non-roaming scenario as an example, a schematic diagram of a network architecture 100 applicable to the embodiments of the present application is provided. As Figure 1As shown, the network architecture 100 may include a terminal device 110, a data network (DN) 140, and a carrier network portion. The carrier network may include, but is not limited to, a (radio) access network ((R)AN) 120 and a core network (CN). A brief description of the devices or network elements of each part will be given below.

[0064] Among them, the (R)AN 120 may include one or more access network elements or access network devices. Hereinafter, the access network device will be taken as an example for illustration. The interface between the access network device and the terminal device may be the Uu interface (or also referred to as the air interface). Of course, in future communications, the interface name may remain unchanged or may be replaced by other names, and this application does not limit this. The access network device is a device that provides wireless communication functions for the terminal device and can connect the terminal device to a node or device in the network, that is, a network device. The (R)AN can be regarded as a sub-network of the operator network and is an implementation system between the service node and the terminal device in the operator network. For example, the terminal device can be connected to the service node of the operator network through the (R)AN to obtain the service provided by the service node. The access network devices in the (R)AN include but are not limited to: the next generation node base station (gNB) in the 5G system, the evolved node B (eNB) in the long term evolution (LTE), the radio network controller (RNC), the node B (NB), the base station controller (BSC), the base transceiver station (BTS), the home base station (for example, home evolved nodeB, or home nodeB, HNB), the base band unit (BBU), the transmitting and receiving point (TRP), the transmitting point (TP), the small cell device, the mobile switching center, or the network device in the future network, etc. The access network device may also be a module or unit that completes the base station function. For example, it includes a central unit (CU) and a distributed unit (DU); in a possible network structure, the CU can be used to support communications under protocols such as radio resource control (RRC), packet data convergence protocol (PDCP), and service data adaptation protocol (SDAP); the DU can be used to support communications under the radio link control (RLC) layer protocol, the medium access control (MAC) layer protocol, and the physical layer protocol.The embodiments of the present application do not limit the specific technologies and specific device forms adopted by the access network devices. In systems adopting different radio access technologies, the names of the devices with the functions of access network devices may be different. For the convenience of description, in all embodiments of the present application, the device that provides wireless communication functions for the terminal device is collectively referred to as the access network device, and in the embodiments of the present application, the access network device can be replaced by an access network network element. It should be understood that the embodiments of the present application do not limit the specific types of the access network devices.

[0065] The data network DN 140, which can also be referred to as a packet data network (PDN), is usually a network located outside the operator's network, such as a third-party network. The DN may include one or more servers, and these one or more servers provide services for the terminal device by transmitting data with the terminal device. A part of the DN can be deployed in a location closer to the terminal device, and this part is called the local part of the DN. One or more EASs 141 are deployed in the local part of the DN. Since the transmission path between these EASs and the terminal device is shorter, the data transmission delay can be reduced.

[0066] Among them, the core network may include, but is not limited to, the following network elements: user plane function (UPF) network element, access and mobility management function (AMF) network element 132, session management function (SMF) network element 133, policy control function (PCF) network element 134, network exposure function (NEF) network element 135, network function repository function (NRF) network element 136, unified data management (UDM) network element 137, unified data repository (UDR) network element 138, edge application server discovery function (EASDF) network element 139. Among them, the network element can also be referred to as a network function (NF), and the embodiments of the present application do not limit this. Some of the network elements in the core network are further briefly described below.

[0067] 1. The UPF network element 131 is used to support the session of the terminal device, and this session is used for data transmission between the terminal device and the DN 140. That is to say, the UPF network element is used to forward service data between the terminal device and the DN. This session can be a protocol data unit (PDU) session. The UPF network element can be used to implement user plane-related functions such as packet routing and transmission, packet detection, service usage reporting, quality of service (QoS) processing, lawful interception, uplink packet detection, and downlink packet saving. For example, during the establishment of the session, the SMF network element selects the UPF network element for this session, and this UPF network element can be called the anchor point of the session, such as the PDU session anchor (PSA).

[0068] The network architecture 100 may also include a UPF network element 131-1, which is used to support data transmission between the terminal device and the local part of the DN (such as the EAS 141). It can also be said that it is used to support the terminal device to access the local part of the DN and support the local access of the terminal device. The UPF network element 131-1 can be called the local anchor point of the session, such as the local PSA (L-PSA). Compared with the UPF network element 131, the UPF network element 131-1 is usually closer to the terminal device, which helps to reduce the end-to-end delay of data transmission between the terminal device and the local part of the DN.

[0069] The network architecture 100 may also include a UPF network element 131-2, which is used to split the data transmitted in the session. That is, the UPF network element 131-2 can send the data transmitted in the session to different anchor points. For example, the UPF network element 131-2 can identify the data sent by the terminal device to the local part of the DN and send this data to the UPF network element 131-2. The UPF network element 131-2 is an uplink classifier (UL CL), which splits the data according to the destination address of the packet; or, the UPF network element 131-2 is a branching point (BP), which splits the data according to the source address of the packet. The UPF network element 131-2 can be denoted as UL CL / BP.

[0070] 2. The AMF network element 132 is responsible for the access control and mobility management of the terminal device accessing the operator network, such as mobile state management, allocating a temporary user identity, authenticating and authorizing the terminal device, etc.

[0071] 3. The SMF network element 133 is used to manage the sessions of the terminal device, such as the establishment, modification, and release of sessions, and is also used for the selection and reselection of the UPF network element, the allocation of the Internet Protocol (IP) address of the terminal device, the Quality of Service (QoS) control, etc. The SMF network element is also used to implement the discovery of the edge application server (EAS), including the selection of the EASDF network element, the configuration of the Domain Name System (DNS) processing rules for the EASDF network element, etc.

[0072] 4. The PCF 134 is used to support a unified policy framework to govern network behavior, provide policy rules, subscription information related to policy decisions, etc. to other control functions.

[0073] 5. The NEF network element 135 is used to enable third parties to use the services provided by the operator network, support the network to open its capabilities, event and data analysis, equip the PLMN security information from external applications, the conversion of information interaction inside and outside the PLMN, etc.

[0074] 6. The NRF network element 136 is a control plane function provided by the operator and can be used to maintain the real-time information of network functions and services in the network. For example, it supports network service discovery, maintains the services supported by the NF configuration data (NF profile) of the NF instance, supports the service discovery of the SCP, maintains the SCP configuration data (SCP profile) of the SCP instance, sends notifications about newly registered, deregistered, and updated NFs and SCPs, maintains the health status of the NFs and SCPs running, etc.

[0075] 7. The UDM network element 137 is a control plane function provided by the operator and is responsible for storing information such as the subscriber permanent identifier (SUPI) of the subscribed user in the operator network, the generic public subscription identifier (GPSI) of the subscribed user, and the credential.

[0076] 8. The UDR network element 138 is a control plane function provided by the operator and provides the function of storing and obtaining subscribed data for the UDM, storing and obtaining policy data for the PCF, storing and obtaining the NF group ID (group ID) information of the user, etc.

[0077] 9. The EASDF network element 139 is used to assist in the discovery of the edge application server (EAS). For example, the EASDF network element can receive DNS query messages from terminal devices, obtain the address of the EAS based on the DNS query messages, and send the address of the EAS to the terminal devices. The EASDF network element can also process DNS query messages and DNS response messages according to the processing rules configured by the SMF network element, such as DNS processing rules.

[0078] Optionally, the network architecture 100 further includes an application function (AF) network element for providing application layer services. The AF network element can belong to the operator network or can be a network element of a third party outside the operator network.

[0079] It should be understood that the above network elements can be physical entities in hardware devices, software instances running on dedicated hardware, or virtualized functions instantiated on a shared platform (such as a cloud platform). In terms of form, the above network elements can be independent devices or can be integrated into the same device to implement different functions.

[0080] The terminal device 110 is a device with wireless transceiver functions that provides voice and / or data connectivity to users and can communicate with one or more network elements in the core network via the (R)AN. The terminal device can also be referred to as a user equipment (UE), access terminal, terminal, user unit, user station, mobile station, mobile unit, remote station, remote terminal, mobile device, user terminal, user agent, or user device, etc. The terminal device can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; it can also be deployed on water (such as a ship, etc.); it can also be deployed in the air (such as an airplane, balloon, satellite, etc.). The terminal device can be a cellular phone, cordless phone, session initiation protocol (SIP) phone, smart phone, mobile phone, wireless local loop (WLL) station, personal digital assistant (PDA), etc. The terminal device can also be a handheld device with wireless communication functions, a computing device, or other devices connected to a wireless modem, a vehicle-mounted device, a wearable device, a drone device, or a terminal in the Internet of Things or the Internet of Vehicles, or a relay user equipment. Among them, the relay user equipment can be a 5G residential gateway (RG). The terminal device can also be a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in unmanned driving, a wireless terminal in remote medical care, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, etc. The embodiments of the present application do not limit the type or category of the terminal device.

[0081] It should be understood that the network architecture applicable to the embodiments of the present application is not limited to the network architecture 100, and any network architecture that can implement the functions of the above-mentioned network elements or devices is applicable to the embodiments of the present application. In addition, the above names are only defined for the convenience of distinguishing different functions and should not constitute any limitation to the embodiments of the present application. The present application does not exclude the possibility of using other names in 5G networks and future networks. For example, in a 6G network, some or all of the above-mentioned network elements or devices may continue to use the terms in 5G, or other names may also be used.

[0082] After the terminal device accesses the network, it can establish a session with the network. Then, through the anchor point of this session, it transmits the data of a certain service to the server providing the service in the data network, so as to use the service provided by the server. When the terminal device wants to use a new service, the network can select a server providing the new service for the terminal device, but the current anchor point of this session may not guarantee the quality of data transmission between the terminal device and the server selected by the network.

[0083] Figure 2 It is a schematic flowchart of a communication method 200 provided by an embodiment of the present application. As Figure 2 shown, the communication method 200 can be executed by a session management network element, a first network element, a first anchor point, and a traffic splitting point, or can be executed by modules and / or devices (such as chips or integrated circuits, etc.) with corresponding functions installed in the session management network element, the first network element, the first anchor point, and the traffic splitting point. The present application is not limited thereto. For the sake of description, the following will be described with the session management network element, the first network element, the first anchor point, and the traffic splitting point as the execution entities. The communication method 200 can be applied to Figure 1 the network architecture 100 shown. Exemplarily, the terminal device is the terminal device 110, the first network element is the EASDF network element 139 or AF, the first anchor point is the UPF network element 131, and the traffic splitting point is the UPF network element 131-3. Parts not elaborated in the embodiments of the present application can refer to existing protocols. As Figure 2 shown, the communication method 200 includes the following multiple steps.

[0084] S210. The session management network element selects a first anchor point for the session of the terminal device, and the first anchor point is used to transmit data between the terminal device and the data network.

[0085] Among them, the first anchor point can be considered as the anchor point configured by the session management network element for the session of the terminal device, and this session is used for data transmission between the terminal device and the data network. Exemplarily, the session of the terminal device can be a protocol data unit (PDU) session, and this anchor point can be a PDU session anchor (PSA).

[0086] For example, during the establishment process of this session, the session management network element selects an anchor point for this session. The specific implementation can refer to existing protocols and will not be elaborated here.

[0087] S220. The first network element receives a first query message from the first anchor point. Correspondingly, the first anchor point sends the first query message to the first network element.

[0088] Among them, the first query message includes a domain name (hereinafter referred to as the first domain name). The first query message is used to query the address of the server that provides services corresponding to the first domain name for the terminal device. In other words, the first query message is used to query the address of the server that provides services corresponding to the first domain name for the terminal device for the terminal device. The first query message may be a domain name system (DNS) query message, and the first domain name may be a fully qualified domain name (FQDN).

[0089] The data between the terminal device and the data network includes the first query message. That is, the terminal device sends the first query message through this session. After the first query message is sent from the terminal device, it reaches the first network element via the first anchor point. Correspondingly, the first network element receives the first query message from the terminal device via the first anchor point. The source address information of the first query message indicates the address of the terminal device, and this address corresponds to this session. Therefore, it can be considered that the first query message is related to this session.

[0090] In one implementation (Implementation 2-1), the first query message includes the address of the first network element. For example, the destination address information of the first query message indicates the address of the first network element. The first anchor point can send the first query message to the first network element according to the address of the first network element.

[0091] In this implementation, the communication method 200 further includes the following step S221.

[0092] S221. The session management network element sends the address of the first network element to the terminal device.

[0093] The session management network element may send the address of the first network element to the terminal device when at least one of the following conditions is met:

[0094] (1) The terminal device is outside the service range of the session management network element;

[0095] (2) The data network access identifier of the session is a data network access identifier not supported by the session management network element;

[0096] (3) The terminal device is within the service range of the first network element;

[0097] (4) The data network access identifier of the session corresponds to the first network element; or,

[0098] (5) The domain name from the second network element corresponds to the first network element, where the second network element is used to provide the address of the server.

[0099] The session management network element can determine whether the above conditions are met according to the following Implementations 2-1-1 to 2-1-7.

[0100] In Method 2-1-1, the session management network element receives a notification message from the mobility management network element. This notification message is used to notify the session management network element that the terminal device is outside the service range of this session management network element, that is, this notification message is used to indicate that the above condition (1) is satisfied. The session management network element determines that condition (1) is satisfied based on this notification message. The notification message may also include the location information of the terminal device, such as the user location information (URI) of the terminal device, the identification information of the tracking area (TA) where the terminal device is located, or the identification information of the cell where the terminal device is located.

[0101] In Method 2-1-2, the session management network element receives a notification message from the mobility management network element. This notification message is used to notify that the location of the terminal device has changed, and this notification message may include the updated location information of the terminal device. The session management network element determines that the terminal device is outside the service range of the session management network element based on the location information of the terminal device, that is, determines that the above condition (1) is satisfied.

[0102] In Method 2-1-3, the session management network element receives the location information of the terminal device from the mobility management network element. For example, the session management network element receives the notification message in Method 2-1-1 or Method 2-1-2, and this notification message includes the location information of the terminal device. The session management network element determines the corresponding data network access identifier (DNAI) based on the location information of the terminal device. Then, the session management network element determines that this DNAI is a DNAI not supported by this session management network element, that is, determines that this DNAI is a DNAI that this session management network element cannot serve, that is, the above condition (2) is satisfied.

[0103] For example, the session management network element determines the DNAI corresponding to the TA indicated by the location information of the terminal device according to the correspondence between the TA and the DNAI. Then, the session management network element determines whether the DNAI corresponding to this TA belongs to the list of DNAIs supported by this session management network element, or whether the DNAI corresponding to this TA belongs to the list of DNAIs not supported by this session management network element, so as to determine whether this DNAI is a DNAI that this session management network element cannot serve. Among them, the correspondence between the TA and the DNAI, the list of DNAIs supported by this session management network element, or the list of DNAIs not supported by this session management network element may be pre-configured in the session management network element.

[0104] In Method 2-1-4, the session management network element receives rule information from the policy control network element, such as a policy and charging control (PCC) rule. This rule information includes a DNAI. The session management network element determines that this DNAI is a DNAI not supported by this session management network element, that is, it determines that this DNAI is a DNAI that this session management network element cannot serve, i.e., condition (2) is satisfied.

[0105] For example, after receiving a DNAI from the policy control network element, the session management network element determines whether this DNAI belongs to the list of DNAIs supported by this session management network element, or whether this DNAI belongs to the list of DNAIs not supported by this session management network element. Among them, the list of DNAIs supported by this session management network element or the list of DNAIs not supported by this session management network element can be pre-configured in the session management network element.

[0106] In Method 2-1-5, the session management network element receives a notification message from the mobility management network element. This notification message is the same as the notification message in Method 2-1-1 or Method 2-1-2. The session management network element determines, based on the location information of the terminal device in the notification message, that the terminal device is within the service range of the first network element, i.e., condition (3) is satisfied.

[0107] For example, the location information of the terminal device indicates the TA where the terminal device is located. The session management network element determines that condition (3) is satisfied based on the fact that the service range of the first network element includes the TA where the terminal device is located. Exemplarily, the session management network element is locally configured with a list that includes one or more TAs covered by the service range of the first network element. When the TA where the terminal device is located belongs to this list, it means that the service range of the first network element includes the TA where the terminal device is located, i.e., the terminal device is within the service range of the first network element.

[0108] In Method 2-1-6, the session management network element determines that the first network element corresponds to this DNAI based on the DNAI corresponding to the location information of the terminal device (refer to Method 2-1-3), or the session management network element determines that the first network element corresponds to this DNAI based on the DNAI from the policy control network element (refer to Method 2-1-4), i.e., condition (4) is satisfied. For example, the session management network element is locally configured with a list that includes one or more DNAIs corresponding to the first network element. These one or more DNAIs include the DNAI corresponding to the location information of the terminal device or the DNAI from the policy control network element. If the first network element corresponds to this DNAI, it can be considered that the service range of the first network element includes the location represented by this DNAI.

[0109] Method 2-1-7: The session management network element receives the second domain name from the second network element, determines that the second domain name corresponds to the first network element, that is, condition (5) is satisfied. For example, the session management network element is locally configured with a list that includes one or more domain names corresponding to the first network element. When the list includes the second domain name, condition (5) is satisfied. If the first network element corresponds to the second domain name, it can be considered that the service scope of the first network element includes the address of the server that provides the service corresponding to the second domain name.

[0110] Based on Method 2-1-7, before step S221, the communication method further includes the following steps S222 and S223.

[0111] S222: The terminal device sends a third query message to the second network element. Correspondingly, the second network element receives the third query message from the terminal device.

[0112] Among them, the third query message includes the second domain name, and the third query message is used to query the address of the server that provides the service corresponding to the second domain name for the terminal device. The second network element can be the network element selected by the session management network element for the session of the terminal device to provide the address of the server. Before step S222, the session management network element can send the address of the second network element to the terminal device.

[0113] S223: The second network element sends the second domain name to the session management network element. Correspondingly, the session management network element receives the second domain name from the second network element.

[0114] For example, the second network element sends the second domain name to the session management network element according to the fourth processing rule, where the fourth processing rule corresponds to the session and matches the domain name, and the fourth processing rule instructs the second network element to send the second domain name to the session management network element. The fourth processing rule can be sent by the session management network element to the second network element before step S222. The processing rule in the embodiments of the present application can be a DNS processing rule.

[0115] Before step S221, the communication method 200 further includes: The session management network element obtains the address of the first network element. For example, when at least one of the above conditions (1) to (5) is satisfied, the session management network element obtains the address of the first network element, and then executes step S221.

[0116] Optionally, the session management network element obtains the address of the first network element by using the following steps S224 and S225.

[0117] S224: The session management network element sends a fourth query message to the third network element. Correspondingly, the third network element receives the fourth query message from the session management network element.

[0118] S225. The third network element sends the address of the first network element to the session management network element. Correspondingly, the session management network element receives the address of the first network element from the third network element.

[0119] For example, the third network element sends a fourth response to the fourth query message to the session management network element, and the fourth response includes the address of the first network element. The third network element can be any one of the NRF network element, UDR network element, NEF network element, PCF network element, BSF network element, and UDM network element.

[0120] In one example, the fourth query message includes a DNAI, and the fourth query message is used to query the address of the first network element corresponding to the DNAI.

[0121] For example, based on Mode 2-1-1 to Mode 2-1-6, the DNAI included in the fourth query message is the DNAI corresponding to the location information of the terminal device or the DNAI of the policy control network element. Based on Mode 2-1-7, the DNAI included in the fourth query message is the DNAI corresponding to the second domain name. For example, the session management network element stores the correspondence between one or more domain names and DNAIs, and the one or more domain names include the second domain name. The session management network element determines the DNAI corresponding to the second domain name according to the correspondence.

[0122] The third network element locally configures the correspondence between the DNAI and the address of the first network element. The third network element determines the address of the first network element according to the DNAI in the fourth query message and the correspondence.

[0123] In another example, the fourth query message includes the location information of the terminal device, and the fourth query message is used to query the address of the first network element corresponding to the location information of the terminal device.

[0124] For example, based on Mode 2-1-1 to Mode 2-1-3, or Mode 2-1-5, the session management network element receives the location information of the terminal device from the mobility management network element and carries the location information in the fourth query message and sends it to the third network element. The third network element locally configures the correspondence between the location information of the terminal device and the address of the first network element. The third network element determines the address of the first network element according to the correspondence and the location information of the terminal device in the fourth query message.

[0125] In yet another example, the fourth query message includes a second domain name, and the fourth query message is used to query the address of the first network element corresponding to the second domain name.

[0126] For example, based on Mode 2-1-7, the session management network element carries the second domain name received from the second network element in the fourth query message and sends it to the third network element. The third network element locally configures the correspondence between the domain name and the address of the first network element. The third network element determines the address of the first network element according to the correspondence and the second domain name.

[0127] Optionally, steps S224 and S225 may be replaced by step S224-a: The session management network element determines the address of the first network element.

[0128] For example, based on Modes 2-1-1 to 2-1-7, the session management network element is locally configured with the correspondence between one or more DNAIs and the address of the first network element. The one or more DNAIs include the DNAI corresponding to the location information of the terminal device, the DNAI from the policy control network element, or the DNAI corresponding to the second domain name. The session management network element determines the address of the first network element according to this correspondence.

[0129] Again, for example, based on Modes 2-1-1 to 2-1-3, or Mode 2-1-5, the session management network element is locally configured with the correspondence between the location information of the terminal device and the address of the first network element. The session management network element receives the location information of the terminal device from the mobility management network element and determines the address of the first network element corresponding to the location information of the terminal device according to this correspondence.

[0130] Also, for example, based on Mode 2-1-7, the session management network element is locally configured with the correspondence between the domain name and the address of the first network element. The session management network element determines the address of the first network element corresponding to the second domain name according to this correspondence and the second domain name received from the second network element.

[0131] In another implementation mode (Mode 2-2), the first network element receives a first query message from the first anchor point, including: The first network element receives the first query message from the first anchor point via the second network element.

[0132] For example, the first network element receiving the first query message from the first anchor point includes the following steps S226 to S229.

[0133] S226. The terminal device sends a first query message to the second network element. Correspondingly, the second network element receives the first query message from the terminal device.

[0134] Among them, the terminal device sends the first query message to the second network element through the first anchor point. Correspondingly, the second network element receives the first query message through the first anchor point.

[0135] For example, during the establishment process of the session of the terminal device, the session management network element sends the address of the second network element to the terminal device. The second network element is used to provide the address of the server for the terminal device. When the terminal device expects to access the service corresponding to the first domain name, the terminal device sends a first query message through this session. The destination address of the first query message is the address of the second network element. The first anchor point may send the first query message to the second network element according to the destination address.

[0136] S227. The second network element sends a first domain name to the session management network element. Correspondingly, the session management network element receives the first domain name from the second network element.

[0137] For example, the second network element sends the first domain name to the session management network element according to a fifth processing rule. The fifth processing rule corresponds to the session and matches the first domain name, and the fifth processing rule instructs the second network element to send the first domain name to the session management network element. Exemplarily, the action included in the fifth processing rule is reporting. The fifth processing rule may be sent by the session management network element to the second network element.

[0138] S228. The session management network element sends a second message to the second network element. Correspondingly, the second network element receives the second message from the session management network element.

[0139] Wherein, the second message is used to instruct the second network element to send a first query message to the first network element, and the second message may further include the address of the first network element. For example, the second message includes a sixth processing rule, and the sixth processing rule includes: sending a first query message to the first network element, and the sixth processing rule may further include the address of the first network element.

[0140] For example, when the first domain name corresponds to the first network element, the session management network element sends the second message to the second network element. Exemplarily, the session management network element is locally configured with the correspondence between one or more domain names and the first network element, and the one or more domain names include the first domain name. After receiving the first domain name, the session management network element determines that the first domain name corresponds to the first network element according to the correspondence, and then sends the second message to the second network element.

[0141] S229. The second network element sends a first query message to the first network element according to the second message. Correspondingly, the first network element receives the first query message from the second network element.

[0142] S230. The first network element obtains the address of the first server according to the first query message.

[0143] Wherein, the first server is the server in the above data network, and the first server may be an edge application server (EAS).

[0144] In one implementation (Mode 2-3), the first network element obtaining the address of the first server according to the first query message includes the following steps S221 and S222.

[0145] S221. The first network element sends a second query message to the first domain name server according to the first query message. Correspondingly, the first domain name server receives the second query message from the first network element.

[0146] Among them, the second query message includes the first domain name. The second query message is used to query the address of the server corresponding to the first domain name, and the second query message may be a DNS query message.

[0147] S222. The first domain name server sends the address of the first server to the first network element. Correspondingly, the first network element receives the address of the first server from the domain name server.

[0148] Among them, the first server is used to provide services corresponding to the first domain name for the terminal device. For example, the first domain name server sends a second response to the second query message to the first network element. The second response includes the address of the first server, and the second response may also include the first domain name.

[0149] Optionally, the second query message further includes option information. The option information is used to determine the address of the first server, and the option information is constructed based on the first domain name. For example, the second query message conforms to a certain message format, which may be specified by the protocol. According to this message format, the fixed field of the second query message is used to carry the option information, that is, the option information occupies the fixed field of the second query message, and the recipient of the second query message can obtain the option information from this fixed field.

[0150] For example, the first network element constructs option information according to the first domain name, and modifies the first query message to the second query message in the following manner: including the option information in the first query message, or replacing the option information in the first query message with the option information. Exemplarily, when the first query message and the second query message are DNS query messages, the option information may be the DNS extended mechanisms for DNS (EDNS) client subnet option (ECS option). Exemplarily, the option information may be used to indicate the location information of the terminal device, so that the first domain name server can select a server closer to the terminal device as the first server according to the option information, thereby shortening the transmission path between the terminal device and the first server and reducing the transmission delay. Exemplarily, the first network element may construct option information in the following manner 2-3-1 or manner 2-3-2.

[0151] Manner 2-3-1. When the first domain name meets the conditions, the first network element determines that the second query message includes option information.

[0152] For example, the conditions include: the first domain name belongs to the first list. Among them, the first list includes at least one domain name. When the first list includes a certain domain name, when the first network element sends a query message including the domain name to the domain name server, the option information needs to be included in the query message.

[0153] Exemplarily, the server deployment information includes a first list. The server deployment information indicates how each server (or each service) is deployed in the data network, that is, the server deployment information indicates the deployment situation of the servers (or services) in the data network. Among them, the servers in the data network include a first server, and the servers in the data network can provide services corresponding to the domain names in the first list.

[0154] The server deployment information can be pre-configured in the first network element, or the first network element can obtain it from other network elements. For example, the first network element obtains the server deployment information from the NEF network element. The server deployment information can be EAS deployment information (EDI). The specific implementation of the first network element obtaining the server deployment information from the NEF network element can refer to the implementation method of the SMF network element obtaining EDI from the NEF network element in the existing protocol, which will not be elaborated here.

[0155] Optionally, the option information is constructed based on at least one of the following: the data network name (DNN) corresponding to the session, the single network slice selection assistance information (S-NSSAI) corresponding to the session, or the data network access identifier (DNAI) corresponding to the first domain name (denoted as the first DNAI).

[0156] Exemplarily, the first network element locally stores information corresponding to each DNN or S-NSSAI for constructing option information. The first network element determines the information for constructing option information according to the DNN or S-NSSAI corresponding to the session, and then constructs the option information.

[0157] Exemplarily, the first network element locally stores a first correspondence between the domain name and the DNAI, and a second correspondence between each DNAI and the information for constructing option information. The first network element determines the first DNAI according to the first domain name and the second correspondence, and then determines the information for constructing option information according to the DNAI and the second correspondence, and then constructs the option information. Among them, the DNAI can be used to identify the connection for transmitting data between the core network and one or more data networks, or can be used to represent the location where the core network accesses the one or more data networks, that is, to represent the location of the servers in the one or more data networks. The first domain name and the first DNAI correspond to indicate that there is a server providing services corresponding to the first domain name at the location represented by the first DNAI. The first correspondence can be included in the server deployment information.

[0158] In Method 2-3-2, the first network element determines that the second query message includes option information according to a second processing rule. The second processing rule corresponds to the session and matches the first domain name. The second processing rule indicates that the query message sent to the domain name server needs to include option information.

[0159] Among them, the second processing rule corresponding to the session and matching the first domain name means that the second processing rule matches the first query message; the second processing rule corresponding to the session can be that the source address information included in the second processing rule indicates the address of the terminal device, and this address corresponds to the session. Exemplarily, the detection template of the second processing rule includes source address information and a domain name range, where the source address information indicates the address of the terminal device, and the domain name range includes the domain name in the first query message; the action of the second processing rule indicates that the query message sent to the domain name server needs to include option information; or, the action of the second processing rule indicates to construct option information. The second processing rule can adopt the following format:

[0160]

[0161] Exemplarily, after receiving the first query message, the first network element searches for a second processing rule that matches the first query message (i.e., corresponding to the session and matching the first domain name), such as searching for a second processing rule whose detection template matches the first query message, and then constructs option information according to the second processing rule, such as constructing option information according to the action included in the second processing rule.

[0162] Optionally, the second processing rule further includes first information for constructing option information, and the first network element can construct option information according to the first information.

[0163] In one example, the first information is related to the session. That is, for a processing rule whose source address information indicates the address of the terminal device, that is, a processing rule corresponding to the session, if this processing rule includes information for constructing option information, then this information is the same as the first information. The first information can be determined by the first network element according to the session-corresponding DNN or S-NSSAI when generating the second processing rule, and the specific implementation can refer to the description below.

[0164] In another example, if the first information is related to DNAI, the option information can be considered to be constructed based on the first DNAI. In this example, the second processing rule may further include the first DNAI. For example, after the first network element receives the first query message, it determines the first DNAI according to the first domain name and the first correspondence, and then searches for the second processing rule that matches the first query message, that is, searches for the second processing rule that corresponds to this session, matches the first domain name, and matches the first DNAI. Then, the option information is constructed according to the first information included in the second processing rule. Wherein, the second processing rule includes the first DNAI can be that the detection template of the second processing rule includes a DNAI range, and this DNAI range includes the first DNAI. The second processing rule includes the first information can be that the action of the second processing rule includes the first information. The second processing rule can adopt the following format:

[0165]

[0166] In yet another example, the first network element locally stores the first correspondence between the domain name and DNAI, and the second correspondence between each DNAI and the information used to construct the option information. After the first network element determines that the second query message includes option information according to the second processing rule, it determines the first DNAI according to the first domain name and the first correspondence, determines the first information according to the first DNAI and the second correspondence, and then constructs the option information according to the first information.

[0167] It should be noted that in the first correspondence between the domain name and DNAI, one domain name can correspond to one or more DNAIs. When the first domain name corresponds to multiple DNAIs, the embodiments of the present application do not limit the implementation manner of the first network element to select the first DNAI from these multiple DNAIs. Exemplarily, the first network element can randomly select the first DNAI from these multiple DNAIs; the first network element can also select the first DNAI from these multiple DNAIs according to a predefined mechanism, and this mechanism can be stipulated by the protocol or pre-configured in the first network element; the first network element can also select the first DNAI from these multiple DNAIs according to the location of the terminal device. For example, the first network element selects the DNAI that represents the location closest to the location of the terminal device among these multiple DNAIs as the first DNAI.

[0168] Optionally, the first domain name server is determined according to the first domain name. Exemplarily, the first network element can determine the first domain name server in the following manner 2-3-3 or manner 2-3-4.

[0169] In manner 2-3-3, the first network element determines the first domain name server according to the first DNAI corresponding to the first domain name.

[0170] For example, the server deployment information includes the addresses of the domain name servers corresponding to each of one or more DNAIs, the one or more DNAIs include a first DNAI, and the domain name servers include a first domain name server. Among them, the address of the domain name server may be the Internet protocol (IP) address and / or port of the domain name server. The first network element may determine the first domain name server according to the first DNAI and the server deployment information.

[0171] Exemplarily, the first network element determines the first DNAI corresponding to the first domain name according to the first correspondence relationship, and then determines the information of the first domain name server corresponding to the first DNAI according to the server deployment information. Then, according to the information of the first domain name server, the first network element sends a second query message to the first domain name server.

[0172] Method 2-3-4: The first network element determines the first domain name server according to a third processing rule, where the third processing rule matches the first domain name and corresponds to the session, and the third processing rule includes the address of the first domain name server.

[0173] Among them, the description of the "third processing rule matches the first domain name and corresponds to the session" can refer to the description of the second processing rule in Method 2-3-2. Exemplarily, after receiving the first query message, the first network element searches for the third processing rule that matches the first query message, and then sends a second query message to the first domain name server according to the address of the first domain name server in the third processing rule.

[0174] It should be understood that any one of Method 2-3-1 and Method 2-3-2 can be combined with any one of Method 2-3-3 and Method 2-3-4. When Method 2-3-2 and Method 2-3-4 are combined, the second processing rule and the third processing rule can be a single processing rule.

[0175] In one example (Method 2-3-5), the second processing rule and / or the third processing rule may be generated by the first network element. For example, the first network element generates the second processing rule and / or the third processing rule according to the server deployment information and / or the feature information. In the embodiments of the present application, generating a processing rule may also be referred to as creating or configuring a processing rule.

[0176] Among them, the server deployment information indicates how each server is deployed in the data network. For example, the server deployment information includes the domain names corresponding to the services provided by each server in the data network. The feature information is used to describe the features of the session or the terminal device, and may include one or more of the following: the DNN corresponding to the session, the S-NSSAI corresponding to the session, the location information of the terminal device, the group information of the terminal device, or the policy information of the terminal device.

[0177] The first network element may also generate information for constructing option information based on the server deployment information and / or the feature information, include the information for constructing option information in the second processing rule, or save the information for constructing option information locally. In step S230, this information may be used to construct option information to obtain the address of the server.

[0178] For example, if the first network element generates information for constructing option information based on the DNN corresponding to the session and / or the S-NSSAI corresponding to the session, then the information for constructing option information corresponds to the DNN and / or the S-NSSAI. Another example is that if the first network element generates information for constructing option information based on the DNAI, then the information for constructing option information corresponds to

[0179] In the case where the first network element generates the second processing rule and / or the third processing rule according to the feature information, the communication method 200 further includes: the session management network element sends the feature information to the first network element. Correspondingly, the first network element receives the feature information from the session management network element.

[0180] Optionally, before the first network element generates the second processing rule and / or the third processing rule, the communication method 200 further includes: the session management network element sends indication information (denoted as the first indication information) to the first network element, and the first indication information is used to indicate the first network element to generate a processing rule corresponding to the session. Correspondingly, the first network element receives the first indication information from the session management network element, and generates a processing rule corresponding to the session according to the first indication information, including the second processing rule and / or the third processing rule.

[0181] Among them, the processing rule corresponding to the session can be considered that the processing rule is used to process the query message related to the session and the response message to the query message. The query message related to the session may be a query message sent by the terminal device through the session. For example, the source address information of these processing rules indicates the address of the terminal device, and the address of the terminal device corresponds to the session.

[0182] For example, the session management network element sends the first indication information to the first network element when at least one of the above conditions (1) to (5) is satisfied.

[0183] In another example (Mode 2-3-6), the second processing rule and / or the third processing rule may be sent by the second session management network element to the first network element. The second processing rule and / or the third processing rule includes identification information of the baseline processing rule, and the identification information of the baseline processing rule is used to indicate the baseline processing rule, which is generated by the first network element. The baseline processing rule is not dedicated to a specific session.

[0184] Among them, it can also be considered that the second processing rule and / or the third processing rule includes the identification information of the baseline processing rule, that is, the second processing rule and / or the third processing rule refers to the baseline processing rule. For example, the baseline processing rule includes at least one of the following: a baseline detection template or baseline action information. The baseline detection template is used to determine whether the processing rule matches the query message and includes a domain name range. When the second processing rule and / or the third processing rule refers to a baseline processing rule including a baseline detection template, the first network element determines whether the second processing rule and / or the third processing rule matches the first query message according to the domain name range included in the baseline detection template, that is, determines whether the first domain name belongs to the domain name range included in the baseline detection template.

[0185] The baseline action information is used to indicate an action. When the second processing rule and / or the third processing rule refers to a baseline processing rule including baseline action information, after the first network element determines that the first query message matches the second processing rule and / or the third processing rule, it processes the second processing rule and / or the third processing rule according to the action indicated by the baseline action information. For example, the baseline action information referred to by the second processing rule is used to indicate that the query message sent to the domain name server needs to include option information; the baseline action information referred to by the third processing rule includes the address of the first domain name server.

[0186] The first network element may generate a baseline processing rule according to the server deployment information and / or feature information, and the server deployment information and feature information may refer to the description in Mode 2-3-5.

[0187] For example, when at least one of the above conditions (1) to (5) is satisfied, the second session management network element sends a processing rule corresponding to the session to the first network element, including the second processing rule and / or the third processing rule. In this example, before the second session management network element sends a processing rule corresponding to the session to the first network element, the communication method 200 further includes: the second session management network element obtains the identification information of the baseline processing rule. Exemplarily, the second session management network element may obtain the identification information of the baseline processing rule through the following steps S231 and S232.

[0188] S231. The second session management network element sends a fifth query message to the third network element. Correspondingly, the third network element receives the fifth query message from the session management network element.

[0189] Among them, the fifth query message is used to query the baseline processing rules of the first network element. The fifth query message and the fourth query message may be the same, that is, the session management network element queries the address of the first network element and the baseline processing rules of the first network element through the same query message. The fifth query message and the fourth query message may be different. For example, after the session management network element obtains the address of the first network element according to the fourth query message, it further queries the baseline processing rules of the first network element through the fifth query message. The fifth query message includes information of the first network element, such as the address of the first network element.

[0190] S232. The third network element sends the identification information of the baseline processing rules of the first network element to the session management network element. Correspondingly, the session management network element receives the identification information of the baseline processing rules from the third network element.

[0191] For example, after the first network element generates the baseline processing rules, it assigns identification information to each baseline processing rule and sends the identification information of each baseline processing rule to the third network element. Correspondingly, the third network element receives the identification information of each baseline processing rule and saves the correspondence between the information of the first network element (such as the address of the first network element) and the identification information of each baseline processing rule, or saves the correspondence among one or more DNAIs, the address of the first network element, and the identification information of each baseline processing rule.

[0192] After receiving the fifth query message, the third network element determines the identification information of each baseline processing rule of the first network element according to the above correspondence and the DNAI or the information of the first network element in the fifth query message, and sends the identification information of each baseline processing rule to the session management network element.

[0193] Optionally, steps S231 and S232 may be replaced with: The session management network element determines the identification information of the baseline processing rules of the first network element.

[0194] For example, the session management network element locally configures the correspondence between the information of the first network element (such as the address of the first network element) and the identification information of each baseline processing rule. After the session management network element obtains the address of the first network element based on steps S224 and S225, it determines the identification information of each baseline processing rule according to this correspondence.

[0195] For another example, in step S224-a, the correspondence between one or more DNAIs locally configured by the session management network element and the address of the first network element is the correspondence among one or more DNAIs, the address of the first network element, and the identification information of each baseline processing rule. In step S224-a, the session management network element determines the address of the first network element based on the DNAI, and also determines the identification information of the baseline processing rule of the first network element according to this correspondence.

[0196] In another implementation manner (manner 2-4), the first network element obtaining the address of the first server according to the first query message includes: the first network element determining the address of the first server according to the first query message.

[0197] For example, the first network element determines the address of the first server according to the first domain name in the first query message. Exemplarily, the first network element determines the address of the first server corresponding to the first domain name according to the third correspondence. Wherein, the third correspondence includes the correspondence between each domain name in one or more domain names and the address of the server, the one or more domain names include the first domain name, and the address of the server includes the address of the first server. Exemplarily, the server deployment information includes the third correspondence.

[0198] In this implementation manner, the first network element can be a network element in the core network or a third-party application function (AF).

[0199] S240. The first network element determines the DNAI corresponding to the address of the first server (denoted as the second DNAI).

[0200] For example, the first network element determines the second DNAI corresponding to the address of the first server according to the fourth correspondence. Wherein, the fourth correspondence includes the correspondence between each DNAI in one or more DNAIs and the address of the server, the one or more DNAIs include the second DNAI, and the address of the server includes the address of the first server. Exemplarily, when the first server is located at the position represented by the second DNAI, the fourth correspondence includes the correspondence between the first server and the second DNAI.

[0201] Exemplarily, if the server deployment information includes the above correspondence, the first network element determines the second DNAI corresponding to the address of the first server according to the server deployment information.

[0202] Optionally, the first network element determines a second DNAI corresponding to the address of the first server based on the server deployment information and the location information of the terminal device. For example, in the fourth correspondence relationship, the address of one server corresponds to one or more DNAIs. When the address of the first server corresponds to multiple DNAIs, the first network element may select a second DNAI from the multiple DNAIs according to the location information of the terminal device. Exemplarily, the first network element selects the DNAI that represents the location closest to the location of the terminal device from the multiple DNAIs as the second DNAI. The location information of the terminal device may be the DNAI corresponding to the location of the terminal device, or may be the identification information of the tracking area (TA) where the terminal device is located or the identification information of the cell.

[0203] In this implementation manner, before the first network element determines the DNAI corresponding to the address of the first server, the communication method 200 further includes: the first network element obtains the location information of the terminal device. For example, the first network element receives the address of the terminal device from the session management network element.

[0204] The first network element may also select the second DNAI from the multiple DNAIs in other ways, and the embodiments of the present application do not limit this.

[0205] S250. The first network element sends a first message to the session management network element. Correspondingly, the session management network element receives the first message from the first network element.

[0206] Wherein, the first message includes the address of the first server and the second DNAI. The first message is used to determine a shunt point, and the shunt point is used to send the data of the session to the first server via the second anchor point. The first message may also be used to determine a second anchor point, and the second anchor point is used to send the data of the session from the shunt point to the first server.

[0207] Optionally, the first network element directly sends the first message to the session management network element. For example, there is an interface between the first network element and the session management network element, and the first network element directly sends the first message to the session management network element through this interface, and this interface may be a service-based interface.

[0208] Optionally, the first network element sends the first message to the session management network element through other network elements. For example, in Method 2-4, when the first network element is an AF, the first network element may send the first message to the session management network element through one or more of the NEF network element, the PCF network element, and the UDR network element, and the first message may be an AF request.

[0209] In an implementation manner (Method 2-5), the first network element sends the first message to the session management network element when the first domain name and / or the address of the first server meet the conditions.

[0210] For example, the first network element sending a first message to the session management network element when the first domain name meets the conditions includes: the first network element sending a first message to the session management network element when the first domain name belongs to the second list. The second list includes at least one domain name. When the second list includes a certain domain name, after the first network element obtains the address of the server providing the service corresponding to the domain name, it sends the address of the server and the corresponding DNAI to the session management network element. That is, the second list includes one or more domain names for which the address of the server and the corresponding DNAI need to be sent to the session management network element, and the one or more domain names include the first domain name.

[0211] Similarly, the first network element sends a first message to the session management network element when the address of the first server meets the conditions, or the first network element sends a first message to the session management network element when the first domain name and the address of the first server meet the conditions. The specific implementation can refer to the description above and will not be elaborated here.

[0212] In another implementation (Method 2-6), the first network element sends a first message to the session management network element according to the first processing rule, where the first processing rule matches the first domain name and / or the address of the first server, and the first processing rule indicates that a first message needs to be sent to the session management network element, or the first processing rule indicates: there is a need (requirement) to send a first message to the session management network element.

[0213] Among them, the first processing rule matching the first domain name can be that the domain name range in the first processing rule includes the first domain name. For example, the domain name range in the detection template of the first processing rule includes the first domain name; the first processing rule matching the address of the first server can be that the server address range in the first processing rule includes the address of the first server. For example, the server address range in the detection template of the first processing rule includes the address of the first server. The first processing rule indicating that a first message needs to be sent to the session management network element can be that the action of the first processing rule includes: sending the address of the server and the corresponding DNAI to the session management network element. Exemplarily, the first processing rule can adopt the following format:

[0214]

[0215] For example, after the first network element obtains the address of the first server, it searches for the first processing rule that matches the first domain name and / or the address of the first server, and then determines the second DNAI according to the first processing rule in step S240, and then executes step S250 to send a first message to the session management network element.

[0216] The first processing rule is generated by the first network element; alternatively, the first processing rule is sent by the session management network element to the first network element, and the first processing rule includes the identification information of the baseline processing rule, which is generated by the first network element. For the specific implementation, reference can be made to Method 2-3-5 and Method 2-3-6, which will not be elaborated here.

[0217] It should be noted that when the first domain name and / or the address of the first server do not meet the conditions, or when the first network element fails to find the first processing rule, the first network element sends the address of the first server to the terminal device. For example, the first network element sends a first response to the first query message to the terminal device, and the first response includes the address of the first server, and subsequent steps S250 to S290 can be skipped.

[0218] S260. The session management network element determines a shunt point (denoted as the first shunt point) according to the first message.

[0219] Since the session management network element determines the first shunt point according to the first message, it can be considered that the first message is used to determine the first shunt point. Among them, the first shunt point is used to send the data of this session to the first server via the second anchor point, that is, the first shunt point is used to send the data sent by the terminal device to the first server to the second anchor point.

[0220] For example, the session management network element determines the first shunt point according to the second DNAI in the first message. Exemplarily, the session management network element determines the first shunt point corresponding to the second DNAI according to the fifth correspondence relationship, where the fifth correspondence relationship includes the correspondence relationship between each of one or more DNAIs and the shunt point, the one or more DNAIs include the second DNAI, and the shunt point includes the first shunt point.

[0221] Optionally, the session management network element also determines the second anchor point according to the first message, that is, the first message can also be used to determine the second anchor point, and the second anchor point is used to send the data of this session from the first shunt point to the first server.

[0222] For example, the session management network element determines the second anchor point according to the second DNAI in the first message. Exemplarily, the session management network element determines the second anchor point corresponding to the second DNAI according to the sixth correspondence relationship, where the sixth correspondence relationship includes the correspondence relationship between each of one or more DNAIs and the user plane network element, the one or more DNAIs include the second DNAI, and the user plane network element includes the second anchor point.

[0223] S270. The session management network element instructs the shunt point (i.e., the first shunt point) to send the data of the session to the first server via the second anchor point.

[0224] For example, the session management network element sends a third message to the first traffic splitting point. The third message is used to instruct the first traffic splitting point to send the data of the session to the first server via the second anchor point, that is, to forward the data sent by the terminal device to the first server to the second anchor point. The third message can be any one of the following: packet detection rules (PDR), forwarding action rules (FAR), multi-access rules (MAR), usage reporting rules (URR), quality of service (QoS) enforcement rules (QER), session reporting rules (SRR). The interface between the session management network element and the first traffic splitting point is called the N4 interface. The session management network element can configure the first traffic splitting point through the N4 session. For example, the session management network element can configure the first traffic splitting point by creating, or updating, or deleting the N4 session context in the first traffic splitting point.

[0225] In one implementation, the session management network element sends a third message to the first traffic splitting point. The third message includes the address of the server. The third message is used to instruct the first traffic splitting point to send the data packet with the destination address of the first server to the second anchor point. In this implementation, the first traffic splitting point can be an uplink classifier (ULCL). The session management network element also establishes a tunnel between the first traffic splitting point and the second anchor point for transmitting the data of the session between the first traffic splitting point and the second anchor point. This tunnel can be a general packet radio service (GPRS) user plane tunnel protocol (GPRS Tunnelling Protocol for the user plane, GTP-U) tunnel. The specific implementation can refer to the existing protocol.

[0226] In another implementation, the session management network element sends a third message to the first traffic splitting point. The third message includes the first address of the terminal device. The third message is used to instruct the first traffic splitting point to send the data packet with the source address of the first address to the second anchor point. Among them, the first address is the address assigned by the second anchor point to the terminal device. The first address corresponds to the first server, that is, the source address information of the data packet sent by the terminal device to the first server is the first address. The session management network element can also instruct the second anchor point to assign an address to the terminal device. In this implementation, the first traffic splitting point can be a branching point (BP).

[0227] In this implementation manner, the session management network element also sends a fourth message to the terminal device. The fourth message includes the address of the terminal device and a first address. The fourth message is used to instruct the terminal device to set the source address information of the data packet sent to the first server as the first address. Or rather, the fourth message is used to instruct the terminal device to use the first address as the source address of the data packet sent to the first server. The fourth message may be a routing rule.

[0228] Optionally, the communication method 200 further includes the following steps S280 and S290 (not shown in the figure).

[0229] S280: The session management network element sends second indication information to the first network element. Correspondingly, the first network element receives the second indication information from the session management network element.

[0230] Among them, the second indication information is used to indicate the address of the sending server.

[0231] Alternatively, the second indication information is used to indicate that the shunt point configuration is successful, or the second indication information is used to indicate that the connection configuration between the terminal device and the first server is successful. This connection is used to transmit the data of the service corresponding to the first domain name between the terminal device and the first server.

[0232] The session management network element may directly send the second indication information to the first network element, or may send the second indication information to the first network element through other network elements. For example, when the first network element is an EASDF network element and there is an interface (such as a service-based interface) between the session management network element and the first network element, the session management network element may directly send the second indication information to the first network element through this interface. Another example is that when the first network element is an AF network element or a DNS server, or the first network element may have some or all of the functions of an AF network element, a DNS server, or an SMF network element, the session management network element may send the second indication information to the first network element through a network open function network element (such as a NEF network element 135).

[0233] S290: The first network element sends a first response to the first query message. The first response includes the address of the first server.

[0234] For example, the first network element determines the address of the first server according to the second indication information.

[0235] Based on Method 2-1, the first network element sends the first response to the terminal device; based on Method 2-2, the first network element sends the first response to the second network element, and the second network element then sends the first response to the terminal device.

[0236] Optionally, the communication method 200 further includes the following steps S291 to S293 (not shown in the figure).

[0237] S291. The terminal device sends the data corresponding to the first domain name to the first shunt point. Correspondingly, the first shunt point receives the data from the terminal device.

[0238] S292. The first shunt point sends the data to the second anchor point. Correspondingly, the second anchor point receives the data from the first shunt point.

[0239] S293. The second anchor point sends the data to the first server.

[0240] For example, the terminal device sends a data packet to the first shunt point through the session, and the data packet is used to carry the data of the service.

[0241] Optionally, based on Method 2-5, the destination address of the data packet is the address of the first server. The first shunt point sends the data packet to the second anchor point according to the destination address of the data packet, and the second anchor point then sends the data packet to the first server.

[0242] Optionally, based on Method 2-6, the source address of the data packet is the address of the terminal device, and the address of the terminal device corresponds to the first server. The first shunt point sends the data packet to the second anchor point according to the source address of the data packet, and the second anchor point then sends the data packet to the first server.

[0243] Based on this method, the first network element can provide a first message for determining the shunt point to the session management network element according to the address of the first server that provides services for the terminal device. Under the processing of the shunt point, the data of the session, such as the data sent by the terminal device to the first server, can be sent to the first server via the second anchor point instead of the first anchor point, which helps the data transmission between the terminal device and the first server.

[0244] Figure 3 It is a schematic flowchart of a communication method 300 provided by an embodiment of the present application. Taking the first network element as the EASDF network element 139, the session management network element as the SMF network element 133, the first anchor point as the UPF network element 131, the shunt point as the UPF network element 131-2, and the second anchor point as the UPF network element 131-1 as an example to describe a possible implementation manner of the communication method 200. As Figure 3 shown, the communication method 300 can be executed by the EASDF network element, the SMF network element, and the UPF network element, or can be executed by modules and / or devices (such as chips or integrated circuits, etc.) with corresponding functions installed in the EASDF network element, the SMF network element, and the UPF network element. The present application is not limited. For the convenience of description, the EASDF network element, the SMF network element, and the UPF network element are used as the execution entities for description below. The parts not elaborated in detail can refer to the existing protocols and the above description of the communication method 200.

[0245] S301. The SMF network element selects the UPF network element 131 as the session anchor point for the terminal device.

[0246] For the specific implementation, reference can be made to existing protocols and will not be elaborated here.

[0247] S302. The SMF network element determines that the first condition is satisfied.

[0248] Among them, the first condition includes at least one of the following conditions:

[0249] (1) The terminal device is outside the service scope of the SMF network element;

[0250] (2) The data network access identifier of the session is a data network access identifier not supported by the SMF network element;

[0251] (3) The terminal device is within the service scope of the EASDF network element;

[0252] (4) The data network access identifier of the session corresponds to the EASDF network element; or,

[0253] (5) The domain name from the EASDF network element 2 corresponds to the EASDF network element, where the EASDF network element 2 is used to provide the address of the server.

[0254] For the specific implementation of the SMF network element to judge the above conditions, reference can be made to Method 2-1-1 to Method 2-1-7 and will not be elaborated here.

[0255] S303. The SMF network element obtains the address of the EASDF network element.

[0256] In one implementation, the SMF network element obtaining the address of the EASDF network element includes: The SMF network element receives the address of the EASDF network element from the NRF network element. For the specific implementation, reference can be made to steps S224 and S225. In another implementation, the SMF network element obtaining the address of the EASDF network element includes: The SMF network element locally determines the address of the EASDF network element. For the specific implementation, reference can be made to step S224-a.

[0257] Optionally, while obtaining the address of the EASDF network element, the SMF network element also obtains the identification information of the baseline DNS processing rule generated by the EASDF network element. For example, the EASDF network element generates a baseline DNS processing rule based on the edge application server deployment information (EDI). The baseline DNS processing rule includes at least one of a baseline DNS detection template or baseline DNS action information. Among them, the baseline DNS detection template is used to determine whether the DNS processing rule matches the DNS message. Exemplarily, when the DNS message type included in the baseline DNS detection template is a DNS query message, the baseline DNS detection template includes a domain name range. When the domain name in the DNS query message belongs to the domain name range included in the baseline DNS detection template, the baseline DNS detection template matches the DNS query message. Exemplarily, when the DNS message type included in the baseline DNS detection template is a DNS response message, the baseline DNS detection template includes a domain name range and / or a range of EAS server addresses. When the domain name in the DNS response message belongs to the domain name range included in the baseline DNS detection template, and / or the address of the EAS server in the DNS response message belongs to the range of EAS server addresses included in the baseline DNS detection template, the baseline DNS detection template matches the DNS response message. The baseline DNS action information is used to indicate the actions to be performed by the EASDF network element, which will be described in detail below.

[0258] Among them, the EDI indicates how the edge services in the DN local part are deployed. The EDI includes at least one FQDN, where each FQDN corresponds to a service provided by a server in the DN local part. The EDI may also include at least one of the following:

[0259] (1) At least one DNAI, where each DNAI can identify the location where the core network accesses the DN local part, or rather, each DNAI can represent the location where one or more servers in the DN local part are located. One DNAI can correspond to one or more FQDNs, and one FQDN can correspond to one or more DNAIs. The correspondence between the FQDN and the DNAI will be referred to as correspondence 1 below.

[0260] (2) At least one EAS address, which is the address of the EAS deployed in the DN local part. Each DNAI corresponds to one or more EAS addresses, and the address of each EAS can correspond to one or more DNAIs. The correspondence between the EAS address and the DNAI will be referred to as correspondence 2 below.

[0261] (3) Information of at least one DNS server, such as the IP address and port of the DNS server. Each DNAI corresponds to the information of one or more DNS servers. The correspondence between the DNAI and the DNS server is hereinafter referred to as correspondence 3.

[0262] EDI may also include other information, such as DNN, S-NSSAI, service identifier, etc. For a detailed introduction, reference can be made to existing protocols and will not be elaborated here. EDI can be pre-configured in the EASDF network element or obtained by the EASDF network element from other network elements (such as the NEF network element). The specific implementation can refer to the way the SMF network element obtains EDI in the existing protocol.

[0263] After the EASDF network element generates the baseline DNS processing rules, it assigns identification information to each baseline DNS processing rule and sends the identification information of each baseline DNS processing rule to the SMF network element or the NRF network element. Correspondingly, the SMF network element or the NRF network element saves the identification information of each baseline DNS processing rule. Thus, the SMF network element can locally determine the identification information of the baseline DNS processing rules generated by the EASDF network element, or the SMF network element can obtain the identification information of the baseline DNS processing rules generated by the EASDF network element from the NRF network element. The specific implementation can refer to steps S231 and S232 and will not be elaborated here.

[0264] S304. The SMF network element sends indication information 1 to the EASDF network element. Correspondingly, the EASDF network element receives the indication information 1 from the SMF network element.

[0265] Among them, the indication information 1 is used to indicate the EASDF network element to generate a DNS processing rule corresponding to the session with the terminal device. The DNS processing rule corresponding to the session with the terminal device can also be considered as a processing rule for processing DNS messages related to the terminal device. The DNS messages related to the terminal device include a DNS query message A whose source address information indicates the address of the terminal device, and the address of the terminal device corresponds to the session; the DNS messages related to the terminal device also include a DNS response message for the DNS query message A.

[0266] Optionally, the SMF network element also sends feature information to the EASDF network element, and the feature information is used to describe the features of the session or the terminal device. Among them, the feature information used to describe the features of the session may include the DNN or S-NSSAI corresponding to the session, etc. The feature information used to describe the features of the terminal device may include one or more of the location information of the terminal device, the group information of the terminal device, or the policy information of the terminal device. Among them, the location information of the terminal device may be the DNAI corresponding to the terminal device, or used to indicate the TA or cell where the terminal device is located.

[0267] S305. The EASDF network element generates a DNS processing rule corresponding to the session according to the indication information 1.

[0268] The EASDF network element may generate a DNS processing rule based on one or more of the server deployment information and the feature information.

[0269] For example, the EASDF network element generates a DNS processing rule 1, where the DNS processing rule 1 is used to process DNS response messages, and the DNS processing rule 1 includes an FQDN range and / or an address range of the EAS server. The DNS processing rule 1 indicates that the address of the EAS server and the DNAI corresponding to the address of the EAS server need to be sent to the SMF network element; for example, the action included in the DNS processing rule 1 is: sending the address of the EAS server and the DNAI corresponding to the address of the EAS server to the SMF network element.

[0270] For example, the EASDF network element generates a DNS processing rule 2, where the DNS processing rule 2 is used to process DNS query messages, the source address information included in the DNS processing rule 2 indicates the address of the terminal device, the DNS processing rule 2 includes an FQDN range, and the DNS processing rule 2 indicates that the query message sent to the domain name server needs to include an ECS option.

[0271] Optionally, the EASDF network element also generates information K for constructing the ECS option, and the information K may be included in the DNS processing rule 2. In one example, the information K corresponds to the session. For example, the information K is determined according to the DNN or S-NSSAI corresponding to the session. In another example, the information K corresponds to the DNAI. When the information K corresponds to the DNAI and the DNS processing rule 2 includes the information K, the DNS processing rule 2 also includes the DNAI, such as the detection template of the DNS processing rule 2 includes the DNAI.

[0272] For example, the EASDF network element generates DNS processing rule 3. Among them, DNS processing rule 3 is used to process DNS query messages. The source address information included in DNS processing rule 3 indicates the address of the terminal device. DNS processing rule 3 includes an FQDN range, and DNS processing rule 3 includes the address of the DNS server. Exemplarily, the EASDF network element can determine the address of the DNS server based on one or more of the following: the location information of the terminal device, DNN, S-NSSAI, the group information of the terminal device, and the policy information of the terminal device. For example, the EASDF network element selects a DNS server closer to the terminal device according to the location information of the terminal device (which can be called a local DNS server, and the local DNS server can provide the address of a server closer to the terminal device). The EASDF network element can also determine the DNS server according to different DNNs and / or S-NSSAIs. In this case, the DNS servers supporting different DNNs and / or S-NSSAIs can be different. The EASDF network element can also determine a DNS server that conforms to the group to which the terminal device belongs or the policy of the terminal device according to the group information of the terminal device and / or the policy information of the terminal device (for example, a DNS server dedicated to gold users). Based on this method, the EASDF network element can select a DNS server that conforms to the characteristics of the session or the terminal device, such as a server closer to the terminal device.

[0273] The EASDF network element can establish a DNS context corresponding to the session. The DNS context includes the DNS processing rule corresponding to the session generated by the EASDF network element.

[0274] S305a (not shown in the figure), the EASDF network element sends a message to the SMF network element to indicate the completion of the generation of the DNS processing rule. Correspondingly, the SMF network element receives this message from the EASDF network element.

[0275] Optionally, steps S304 to S305a can be replaced by steps S306 and S306a.

[0276] S306, the SMF network element sends at least one DNS processing rule to the EASDF network element. Correspondingly, the EASDF network element receives at least one DNS processing rule from the SMF network element.

[0277] Among them, the at least one DNS processing rule corresponds to the session. The at least one DNS processing rule includes the identification information of the baseline DNS processing rule generated by the EASDF network element, that is, the at least one DNS processing rule refers to the baseline DNS processing rule generated by the EASDF network element.

[0278] The at least one DNS processing rule may include DNS processing rule 1, which is used to process DNS response messages. DNS processing rule 1 may include the identification information of baseline DNS detection template 1 and the identification information of baseline DNS action information 1, where baseline DNS detection template 1 includes the FQDN range and / or the address range of the EAS server; baseline DNS action information 1 indicates that the address of the EAS server and the DNAI corresponding to the address of the EAS server need to be sent to the SMF network element. For example, the action included in baseline DNS action information 1 is: sending the address of the EAS server and the DNAI corresponding to the address of the EAS server to the SMF network element.

[0279] The at least one DNS processing rule may include DNS processing rule 2, which is used to process DNS query messages. DNS processing rule 2 may include the identification information of baseline DNS detection template 2 and the identification information of baseline DNS action information 2. Baseline DNS detection template 2 includes the FQDN range; baseline DNS action information 2 indicates that the query message sent to the domain name server needs to include the ECS option, and baseline DNS action information 2 may also include the information K used to construct the ECS option. DNS processing rule 2 further includes source address information indicating the address of the terminal device.

[0280] The at least one DNS processing rule may include DNS processing rule 3, where DNS processing rule 3 is used to process DNS query messages. DNS processing rule 3 may include the identification information of baseline DNS detection template 3 and the identification information of baseline DNS action information 3. Baseline DNS detection template 3 includes the FQDN range; baseline DNS action information 3 includes the address of the DNS server. DNS processing rule 2 further includes source address information indicating the address of the terminal device.

[0281] S306a (not shown in the figure), the EASDF network element sends a message to the SMF network element to indicate the successful reception of the DNS processing rule. Correspondingly, the SMF network element receives this message from the EASDF network element.

[0282] Steps S304 - S305a, steps S306 and S306a are optional.

[0283] S307, the SMF network element sends the address of the EASDF network element to the terminal device. Correspondingly, the terminal device receives the address of the EASDF network element from the SMF network element.

[0284] The terminal device uses the EASDF network element as the default DNS server for this session.

[0285] It should be noted that step S307 may be executed before or after steps S304a to S306a, and may be executed before or after steps S304b and S305b. The embodiments of the present application do not limit this.

[0286] S308. The terminal device sends a DNS query message 1 to the EASDF network element. Correspondingly, the EASDF network element receives the DNS query message 1 from the terminal device.

[0287] For example, the terminal device sends a DNS query message 1 to the EASDF network element through an access network device and a session anchor point.

[0288] Among them, the DNS query message 1 includes FQDN 1. The DNS query message 1 is used to query the address of the server that provides the service corresponding to FQDN 1 for the terminal device. The source address information of the DNS query message 1 indicates the address of the terminal device, and the destination address information indicates the address of the EASDF network element.

[0289] S309. The EASDF network element sends a DNS query message 2 to the domain name server according to the DNS query message 1. Correspondingly, the domain name server receives the DNS query message 2 from the EASDF network element.

[0290] Optionally, the DNS query message 2 includes an ECS option, and the ECS option is used to determine the address of the server.

[0291] In one example, when FQDN 1 meets the condition, the EASDF network element includes an ECS option in the DNS query message 2. The condition may be that the EDI includes the address of EAS1, or the address of EAS1 belongs to list 1, where list 1 includes one or more FQDNs. List 1 may be pre-configured in the EASDF network element.

[0292] For example, the EASDF network element locally stores the correspondence 4 between the address of the terminal device and the information K for constructing the ECS option. The EASDF network element determines the information K according to the correspondence 4 and the address of the terminal device indicated by the source address information in the DNS query message 1, and then constructs the ECS option according to the information K. Another example is that the EASDF network element locally stores the correspondence 5 between the DNAI and the information K. The EASDF network element determines the DNAI corresponding to FQDN 1 according to the correspondence 1, then determines the information K according to the correspondence 5, and then constructs the ECS option according to the information K.

[0293] In another example, the EASDF network element includes an ECS option in the DNS query message 2 according to the DNS processing rule 2. If the EASDF network element determines that the DNS processing rule 2 matches the DNS query message 1, that is, the source address information included in the DNS processing rule 2 or the baseline DNS detection template 2 indicates the address of the terminal device, the included FQDN range includes FQDN 1. Optionally, the DNAI range included in the DNS processing rule 2 or the baseline DNS detection template 2 includes the DNAI corresponding to FQDN 1. Then, the EASDF network element includes an ECS option in the DNS query message 2 according to the indication of the DNS processing rule 2 or the baseline DNS action information 2.

[0294] When the DNS processing rule 2 includes the information K, the EASDF network element constructs an ECS option according to the information K included in the DNS processing rule 2. Alternatively, the EASDF network element determines the information K according to the correspondence 4 or the correspondence 5, and the specific implementation can refer to the above description.

[0295] Optionally, before the EASDF network element sends the DNS query message 2 to the DNS server, the communication method 300 further includes: the EASDF network element determines the DNS server.

[0296] In one example, the EASDF network element determines the DNS server according to FQDN 1 and the correspondence 3. In another example, the EASDF network element determines the DNS server according to the DNS processing rule 3. If the EASDF network element determines that the DNS processing rule 3 matches the DNS query message 1, that is, the source address information included in the DNS processing rule 3 or the baseline DNS detection template 3 indicates the address of the terminal device, the included FQDN range includes FQDN 1. Then, the EASDF network element determines that the DNS server included in the DNS processing rule 3 or the baseline DNS action information 3 is the target DNS server for sending the DNS query message 2.

[0297] S310. The domain name server sends a DNS response message 2 to the EASDF network element. Correspondingly, the EASDF network element receives the DNS response message 2 from the domain name server.

[0298] Among them, the DNS response message 2 includes the address of EAS1.

[0299] S311. The EASDF network element determines the DNAI 1 corresponding to the address of EAS1.

[0300] For example, the EASDF network element determines, according to correspondence relationship 2, that the DNAI corresponding to the address of EAS1 is DNAI 1. When there are multiple DNAIs corresponding to the address of EAS1 in correspondence relationship 2, the EASDF network element may select DNAI 1 from the multiple DNAIs according to the location information of the terminal device. Exemplarily, the EASDF network element may select, from the multiple DNAIs, the DNAI whose indicated location is closest to the location indicated by the location information of the terminal device as DNAI 1. The EASDF network element may also select DNAI 1 from the multiple DNAIs corresponding to the address of EAS1 in other ways, and the embodiments of the present application do not limit this.

[0301] S312. The EASDF network element sends message 1 to the SMF network element. Correspondingly, the SMF network element receives message 1 from the EASDF network element.

[0302] Among them, message 1 includes the address of EAS1 and DNAI 1, and message 1 is used to determine the traffic splitting point.

[0303] In one example, when the address of EAS1 meets the conditions, the EASDF network element determines the DNAI 1 corresponding to the address of EAS1 and sends message 1 to the SMF network element. The conditions may be: the EDI includes the address of EAS1, or the address of EAS1 belongs to list 2, where list 2 includes one or more addresses of EASs. List 2 may be pre-configured in the EASDF network element.

[0304] In another example, the EASDF network element determines the DNAI 1 corresponding to the address of EAS1 according to DNS processing rule 1 and sends message 1 to the SMF network element. For example, the EASDF network element determines that DNS processing rule 1 matches DNS response message 2, that is, the FQDN range included in DNS processing rule 1 or baseline DNS detection template 1 includes FQDN 1, and / or the EAS address range included in DNS processing rule 1 or baseline DNS detection template 1 includes the address of EAS1. Then, the EASDF network element determines the DNAI 1 corresponding to the address of EAS1 according to the indication of DNS processing rule 1 or baseline DNS action information 1 and sends message 1 to the SMF network element.

[0305] Optionally, in step S311, the EASDF network element determining the DNAI 1 corresponding to the address of EAS1 may be replaced with the EASDF network element determining the traffic splitting point corresponding to the address of EAS1; and message 1 including DNAI 1 may be replaced with message 1 including the identification information of the traffic splitting point. The specific implementation manners are similar and will not be elaborated here.

[0306] S313. The SMF network element determines the traffic splitting point according to message 1.

[0307] For example, when message 1 includes DNAI 1, the SMF network element stores the correspondence 6 between DNAI and the UPF network element. The SMF network element selects a UPF network element corresponding to DNAI 1 as the traffic splitting point according to DNAI 1 and the correspondence 6. The specific selection method is not limited in the embodiments of the present application.

[0308] Optionally, the SMF network element also determines the local session anchor according to message 1. For example, the SMF network element selects another UPF network element corresponding to DNAI 1 as the local session anchor according to DNAI 1 and the correspondence 6. The specific selection method is not limited in the embodiments of the present application.

[0309] S314. The SMF network element instructs the traffic splitting point to send the session data to EAS1 via the local session anchor.

[0310] The implementation manner of step S314 can refer to the description in step S270 and will not be elaborated here.

[0311] Optionally, the communication method 300 further includes the following steps S315 and S316 (not shown in the figure).

[0312] S315. The SMF network element sends indication information 3 to the EASDF network element. Correspondingly, the EASDF network element receives the indication information 3 from the SMF network element.

[0313] The indication information 3 can be used to indicate that the traffic splitting point configuration is completed, or to indicate that the connection configuration between the terminal device and EAS1 is successful. This connection is used for transmitting data of the service corresponding to FQDN 1 between the terminal device and EAS1.

[0314] S316. The EASDF network element sends the address of EAS1 to the terminal device according to the indication information 3. Correspondingly, the terminal device receives the address of EAS1 from the EASDF network element.

[0315] For example, the EASDF network element sends a DNS response message 1 for the DNS query message 1 to the terminal device, and the DNS response message 1 includes the address of EAS1.

[0316] Optionally, the communication method 300 further includes the following steps S317 to S319 (not shown in the figure).

[0317] S317. The terminal device sends the data of the service corresponding to FQDN 1 to the traffic splitting point. Correspondingly, the traffic splitting point receives the data from the terminal device.

[0318] For example, the terminal device sends the data to the traffic splitting point through the access network device.

[0319] Among them, the source address information of the data packet carrying the data indicates the address of the terminal device, and the destination address information indicates the address of the EAS1. When the shunt point is BP, the address of the terminal device corresponds to the address of the EAS1.

[0320] S318. The shunt point sends the data to the local session anchor point. Correspondingly, the local session anchor point receives the data from the shunt point.

[0321] For example, when the shunt point is the UL CL, the shunt point forwards the data packet to the local session anchor point according to the destination address information of the data packet carrying the data. Another example is that when the shunt point is BP, the shunt point forwards the data packet to the local session anchor point according to the source address information of the data packet carrying the data.

[0322] S319. The local session anchor point sends the data to the EAS1. Correspondingly, the EAS1 receives the data from the local session anchor point.

[0323] Based on the above method, the data of the session of the terminal device was originally sent to the data network through the session anchor point. When the terminal device needs to use the service corresponding to FQDN 1, it queries the EASDF network element for the address of the server that can provide the service. After the EASDF network element obtains the address of the EAS1 according to the query of the terminal device, it determines the DNAI corresponding to the address of the EAS1, and sends message 1 including the DNAI to the session management network element. Thus, the session management network element can determine the shunt point according to message 1, and instruct the shunt point to send the data sent by the terminal device to the EAS1 via the local session anchor point instead of the session anchor point. The data transmitted between the terminal device and the EAS1 is forwarded through the local session anchor point, the transmission path of the data is short, the transmission delay and jitter are low, which is beneficial to the high-quality data transmission between the terminal device and the EAS1.

[0324] Figure 4 It is a schematic flow chart of a communication method 400 provided by an embodiment of the present application. Taking the session management network element as the SMF network element 133, the second network element as the EASDF network element, the first anchor point as the UPF network element 131, the shunt point as the UPF network element 131-2, and the second anchor point as the UPF network element 131-1 as an example to describe a possible implementation manner of the communication method 200. In the communication method 400, the first network element may have some or all of the functions of the AF network element, the DNS server, or the SMF network element. Such as Figure 4As shown, the communication method 400 may be executed by the first network element, the EASDF network element, the SMF network element, and the UPF network element, or may be executed by modules and / or devices (such as chips or integrated circuits, etc.) with corresponding functions installed in the first network element, the EASDF network element, the SMF network element, and the UPF network element. This application does not limit this. For ease of description, hereinafter, the first network element, the EASDF network element, the SMF network element, and the UPF network element are used as the execution entities for explanation. For parts not elaborated in detail, reference can be made to existing protocols and the above description of the communication method 200.

[0325] S401. The SMF network element selects the UPF network element 131 as the session anchor point for the session of the terminal device.

[0326] For the specific implementation, reference can be made to existing protocols and will not be elaborated here.

[0327] S402. The SMF network element sends the address of the EASDF network element to the terminal device. Correspondingly, the terminal device receives the address of the EASDF network element from the SMF network element.

[0328] For example, the SMF network element selects the EASDF network element for the session of the terminal device, and the terminal device may use the EASDF network element as the default DNS server for this session. For the specific implementation, reference can be made to existing protocols and will not be elaborated here.

[0329] S403. The terminal device sends a DNS query message 1 to the EASDF network element. Correspondingly, the EASDF network element receives the DNS query message 1 from the terminal device.

[0330] Among them, the DNS query message 1 includes FQDN 1. The DNS query message 1 is used to query the address of the server that provides the service corresponding to FQDN 1 for the terminal device. The source address information of the DNS query message 1 indicates the address of the terminal device, and the destination address information indicates the address of the EASDF network element.

[0331] S404. The EASDF network element sends FQDN 1 to the SMF network element. Correspondingly, the SMF network element receives FQDN 1 from the EASDF network element.

[0332] For example, the EASDF network element sends FQDN 1 to the SMF network element according to the DNS processing rule 4. The source address information of the DNS processing rule 4 indicates the address of the terminal device. The FQDN range of the DNS processing rule 4 includes FQDN 1. The DNS processing rule 4 indicates to send FQDN 1 to the SMF network element. For example, the action included in the DNS processing rule 4 is reporting.

[0333] Exemplarily, the EASDF network element sends a DNS context notification request message (such as Neasdf_DNSContext_Notify Request) to the SMF network element, and the DNS context notification request message includes FQDN 1.

[0334] S405. The SMF network element instructs the EASDF network element to forward the DNS query message 1 to the first network element.

[0335] For example, when FQDN 1 meets the condition, the SMF network element instructs the EASDF network element to forward the DNS query message 1 to the first network element. The condition may be that FQDN 1 corresponds to the first network element. For example, the SMF network element stores a list that includes at least one FQDN corresponding to the first network element. When FQDN 1 belongs to this list, the SMF network element instructs the EASDF network element to forward the DNS query message 1 to the first network element.

[0336] In one example, the SMF network element sends indication information 2 to the EASDF network element. The indication information 2 is used to instruct the EASDF network element to forward the DNS query message 1 to the first network element. The SMF network element may also send the address of the first network element to the EASDF network element. In another example, the SMF network element sends DNS processing rule 5 to the EASDF network element. DNS processing rule 5 includes: forwarding the DNS query message 1 to the first network element. For example, the action included in DNS processing rule 5 is to forward the DNS query message 1 to the first network element. Optionally, DNS processing rule 5 also includes the address of the first network element. For example, the SMF network element may send DNS processing rule 5 to the EASDF network element through a DNS context update request message (such as Neasdf_DNSContext_Update Request).

[0337] S406. The EASDF network element sends the DNS query message 1 to the first network element. Correspondingly, the first network element receives the DNS query message 1 from the EASDF network element.

[0338] For example, the EASDF network element sends the DNS query message 1 to the first network element according to the indication information 2 or DNS processing rule 5.

[0339] Optionally, the above steps S404 - S406 may be replaced by the following step S407.

[0340] S407. The EASDF network element sends the DNS query message 1 to the first network element according to DNS processing rule 6. Correspondingly, the first network element receives the DNS query message 1 from the EASDF network element.

[0341] Among them, DNS processing rule 6 matches DNS query message 1. If the source address information of DNS processing rule 6 indicates the address of the terminal device, the FQDN range included in DNS processing rule 6 includes FQDN 1. DNS processing rule 6 includes: sending a DNS query message including FQDN 1 to the first network element. DNS processing rule 6 may further include the address of the first network element.

[0342] After the EASDF network element receives DNS query message 1, it finds DNS processing rule 6 that matches DNS query message 1, and then sends DNS query message 1 to the first network element according to DNS processing rule 6.

[0343] In this implementation manner, before the EASDF network element sends DNS query message 1 to the first network element according to DNS processing rule 6, communication method 400 further includes: the SMF network element sends DNS processing rule 6 to the EASDF network element. For example, during the establishment of a session of the terminal device, the SMF network element selects the EASDF network element for this session and sends DNS processing rule 6 to the EASDF network element.

[0344] The EASDF network element may establish a DNS context corresponding to this session and save DNS processing rule 6 in the DNS context corresponding to this session. The DNS context may include the address of the terminal device. After the EASDF network element receives DNS query message 1, it first determines that the DNS context corresponding to this session matches DNS query message 1, that is, the address of the terminal device included in this DNS context is the address of the terminal device indicated by the source address information of DNS query message 1. Then, the EASDF network element searches for DNS processing rule 6 that matches DNS query message 1 from this DNS context.

[0345] The EASDF network element may directly send DNS query message 1 to the first network element, or send DNS query message 1 to the first network element through other network elements (such as the NEF network element). The embodiments of the present application do not limit this.

[0346] It should be noted that the DNS query message 1 sent by the above-mentioned EASDF network element to the first network element and the DNS query message 1 received by the EASDF network element may be the same or different. For example, the DNS query message 1 received by the EASDF network element includes or replaces the ECS option, and then the DNS query message 1 with the added ECS option is sent to the first network element. The DNS processing rule 6 may include the information K for constructing the ECS option. The EASDF network element constructs the ECS option according to the information K in the DNS processing rule 6, adds the ECS option to the DNS query message 1, or uses the ECS option to replace the original ECS option in the DNS query message 1.

[0347] S408. The first network element obtains the address of EAS1 according to the DNS query message 1, and then determines the DNAI 1 corresponding to the address of EAS1.

[0348] For example, the first network element resolves the FQDN 1 in the DNS query message 1 to obtain the address of EAS1. The specific implementation can refer to the implementation method of the DNS server in the prior art, and the embodiments of the present application do not limit this.

[0349] The first network element also includes the correspondence between one or more DNAIs and the addresses of EASs. Among them, one or more DNAIs include DNAI 1, and the addresses of EASs include the address of EAS1. The first network element determines DNAI 1 according to this correspondence and the address of EAS1. This correspondence can be stored in the EDI of the first network element.

[0350] S409. The first network element sends the address of EAS1 and DNAI 1 to the SMF network element. Correspondingly, the SMF network element receives the address of EAS1 and DNAI 1 from the first network element.

[0351] Among them, DNAI 1 is used to determine the shunt point, and DNAI 1 can also determine the local session anchor point. DNAI 1 can also be replaced with the identification information of the shunt point. The specific implementation can refer to step S312.

[0352] Optionally, the first network element directly sends the address of EAS1 and DNAI 1 to the SMF network element, or the first network element sends the address of EAS1 and DNAI 1 to the SMF network element through other network elements, such as one or more of the NEF network element, the PCF network element, or the UDR network element.

[0353] S410. The SMF network element determines the shunt point according to message 1.

[0354] For example, the SMF network element determines that the UPF network element 131-2 is a traffic splitting point based on Message 1. The SMF network element can also determine the local session anchor point according to Message 1, such as determining that the UPF network element 131-1 is the local session anchor point.

[0355] S411. The SMF network element instructs the traffic splitting point to send the session data to the EAS1 via the local session anchor point.

[0356] The implementation manners of steps S410 and S411 can refer to steps S313 and S314, which will not be elaborated here.

[0357] Optionally, the communication method 400 further includes steps S315 to S319.

[0358] Based on the above method, the session data of the terminal device was originally sent to the data network through the session anchor point. When the terminal device needs to use the service corresponding to FQDN 1 and queries the address of the server that can provide the service from the EASDF network element, the EASDF network element forwards the query message of the terminal device to the first network element. Thus, the first network element can resolve FQDN 1 in the query message, determine the address of the EAS1 and the corresponding DNAI, and provide the address of the EAS1 and the corresponding DNAI to the SMF network element. The SMF network element can determine and configure the splitting point according to the information provided by the first network element, so that the data sent by the terminal device to the EAS1 can be transmitted to the EAS1 via the local session anchor point instead of the session anchor point. The data transmitted between the terminal device and the EAS1 is forwarded via the local session anchor point, with a short transmission path, low transmission delay and jitter, and high data transmission quality.

[0359] In the communication method 300, the first condition may include: the domain name from the EASDF network element 2 corresponds to the EASDF network element, where the EASDF network element 2 is used to provide the address of the server. The following is combined with Figure 5 Further describe a possible implementation manner (denoted as the communication method 500).

[0360] S501. The SMF network element selects the UPF network element 131 as the session anchor point for the session of the terminal device.

[0361] S502. The SMF network element sends the address of the EASDF network element 2 to the terminal device. Correspondingly, the terminal device receives the address of the EASDF network element 2 from the SMF network element.

[0362] S503. The terminal device sends a DNS query message 3 to the EASDF network element 2. Correspondingly, the EASDF network element 2 receives the DNS query message 3 from the terminal device.

[0363] Among them, the DNS query message 3 includes the FQDN 2, and the DNS query message 3 is used to query the server that provides the service corresponding to the FQDN 2 for the terminal device.

[0364] S504. The EASDF network element 2 sends the FQDN 2 to the SMF network element. Correspondingly, the SMF network element receives the FQDN 2 from the EASDF network element 2.

[0365] The above steps S501 to S504 are similar to S401 to S404, and will not be elaborated here.

[0366] S505. The SMF network element determines that the FQDN 2 corresponds to the EASDF network element (that is, the first condition is satisfied).

[0367] For example, the SMF network element is locally configured with a list that includes one or more FQDNs corresponding to the EASDF network element. When the FQDN 2 belongs to this list, the SMF network element determines that the FQDN 2 corresponds to the EASDF network element. The correspondence between the FQDN 2 and the EASDF network element may indicate that within the service range of the EASDF network element, there is a server that can provide the service corresponding to the FQDN 2 deployed.

[0368] The communication method 500 further includes steps S303 to S317, and the specific implementation can refer to the description in the communication method 300.

[0369] Among them, in step S308, the DNS query message 1 and the DNS query message 3 sent by the terminal device may be the same, that is, the FQDN 1 and the FQDN 2 may be the same. Exemplarily, the terminal device receives the address of the EASDF network element in step S307, confirms that the default DNS server for this session has changed, and invalidates the DNS query message 3 that has been sent and has not received a response. Then the terminal device resends the DNS query message 3 to the EASDF network element in step S308.

[0370] Based on this method, the data of the session of the terminal device was originally sent to the data network through the session anchor point. When the terminal device needs to use the service corresponding to FQDN 2 and queries the EASDF network element 2 for the address of the server that can provide this service, the SMF network element determines, according to the FQDN 1 reported by the EASDF network element 2, that FQDN 1 corresponds to the EASDF network element, and then provides the address of the EASDF network element to the terminal device. The EASDF network element provides the server discovery service for the terminal device. Subsequently, when the terminal device needs to use the service corresponding to FQDN 1 and queries the EASDF network element for the address of the server that can provide this service, after the EASDF network element obtains the address of EAS1 according to the query of the terminal device, it determines the DNAI corresponding to the address of EAS1 and sends message 1 including this DNAI to the session management network element. Thus, the session management network element can determine the shunt point according to message 1 and instruct the shunt point to send the data sent by the terminal device to EAS1 via the local session anchor point instead of the session anchor point to EAS1. The data transmitted between the terminal device and EAS1 is forwarded via the local session anchor point. The transmission path of the data is short, the transmission delay and jitter are low, and the data transmission quality is high.

[0371] Figure 6 It is a schematic structural diagram of the communication device 1000 provided by an embodiment of the present application. As Figure 6 shown, the device 1000 may include a transceiver unit 1010 and a processing unit 1020. The transceiver unit 1010 can implement corresponding communication functions. The processing unit 1020 is used for data processing. Or rather, the transceiver unit 1010 is used to perform operations related to reception and transmission, and the processing unit 1020 is used to perform other operations except reception and transmission. The transceiver unit 1010 may also be referred to as a communication interface or a communication unit.

[0372] In a possible design, the communication device 1000 may correspond to the first network element in the above method embodiment, or be a component (such as a chip) of the first network element.

[0373] The communication device 1000 can implement the steps or processes executed by the first network element in the above method embodiment. Among them, the transceiver unit 1010 can be used to perform operations related to reception and transmission of the first network element in the above method embodiment, and the processing unit 1020 can be used to perform operations related to internal processing of the first network element in the above method embodiment.

[0374] Exemplarily, the transceiver unit 1010 is configured to receive a first query message of a first anchor point of a session from a terminal device, where the first query message includes a domain name, and the first query message is used to query an address of a server that provides a service corresponding to the domain name for the terminal device; the processing unit 1020 is configured to obtain an address of a first server according to the first query message, where the first server is used to provide the service corresponding to the domain name for the terminal device; the processing unit 1020 is further configured to determine a data network access identifier corresponding to the address of the first server; the transceiver unit 1010 is further configured to send a first message for determining a shunt point to a session management network element, where the first message includes the address of the first server and the data network access identifier, and the shunt point is used to send data of the session to the first server via a second anchor point.

[0375] Wherein, when the apparatus 1000 is used to execute Figure 2 the method in, the transceiver unit 1010 may be configured to execute the step of sending and receiving information in the method, such as step S220, or S250; the processing unit 1020 may be configured to execute the internal processing step in the method, such as step S230, or S240.

[0376] Wherein, when the apparatus 1000 is used to execute Figure 3 the method in, the transceiver unit 1010 may be configured to execute the step of sending and receiving information in the method, such as step S304a, S304b, S308, S309, S310, or S312; the processing unit 1020 may be configured to execute the internal processing step in the method, such as step S305a, or S311.

[0377] Wherein, when the apparatus 1000 is used to execute Figure 4 the method in, the transceiver unit 1010 may be configured to execute the step of sending and receiving information in the method, such as step S406, S407, S409, S411, S412, S414, or S415; the processing unit 1020 may be configured to execute the internal processing step in the method, such as step S408.

[0378] Wherein, when the apparatus 1000 is used to execute Figure 5 the method in, the transceiver unit 1010 may be configured to execute the step of sending and receiving information in the method, such as step S304a, S304b, S308, S309, S310, or S312; the processing unit 1020 may be configured to execute the internal processing step in the method, such as step S305a, or S311.

[0379] It should be understood that for the specific processes of each unit executing the above steps, reference may be made to the description of the above embodiments, which will not be elaborated herein.

[0380] In another possible design, the communication device 1000 may correspond to the session management network element in the above method embodiments, or be a component (such as a chip) of the session management network element.

[0381] The communication device 1000 can implement the steps or processes corresponding to those performed by the session management network element in the above method embodiments. Among them, the transceiver unit 1010 can be used to perform the operations related to the transceiver of the session management network element in the above method embodiments, and the processing unit 1020 can be used to perform the operations related to the internal processing of the session management network element in the above method embodiments.

[0382] Exemplarily, the processing unit 1020 is used to select a first anchor point for the session of the terminal device, where the first anchor point is used to transmit data between the terminal device and the data network. The data includes a first query message, and the first query message includes a domain name. The first query message is used to query the address of the server that provides the service corresponding to the domain name for the terminal device; the transceiver unit 1010 is used to receive a first message from a first network element, and the first message includes the address of the first server and a data network access identifier. The first server is a server in the data network; the processing unit 1020 is further used to determine a shunt point according to the first message; the processing unit 1020 is further used to instruct the shunt point to send the data of the session to the first server via a second anchor point through the transceiver unit 1010.

[0383] Among them, when the device 1000 is used to execute Figure 2 the method in, the transceiver unit 1010 can be used to execute the steps of sending and receiving information in the method, such as step S250 or S270; the processing unit 1020 can be used to execute the internal processing steps in the method, such as step S210, S260, or S270.

[0384] Among them, when the device 1000 is used to execute Figure 3 the method in, the transceiver unit 1010 can be used to execute the steps of sending and receiving information in the method, such as step S304a, S304b, S307, S312, or S314; the processing unit 1020 can be used to execute the internal processing steps in the method, such as step S301, S302, S303, S313, or S314.

[0385] Among them, when the device 1000 is used to execute Figure 4 the method in, the transceiver unit 1010 can be used to execute the steps of sending and receiving information in the method, such as step S402, S404, S405, S409, or S411; the processing unit 1020 can be used to execute the internal processing steps in the method, such as step S401, S410, or S411.

[0386] Among them, when the device 1000 is used to execute Figure 5 the method in, the transceiver unit 1010 can be used to execute the steps of sending and receiving information in the method, such as steps S502, S504, S304a, S304b, S307, S312, or S314; the processing unit 1020 can be used to execute the internal processing steps in the method, such as steps S501, S505, S303, S313, or S314.

[0387] It should be understood that for the specific processes of each unit executing the above steps, reference can be made to the descriptions in the above embodiments, and details will not be repeated here.

[0388] It should be understood that the device 1000 here is embodied in the form of functional units. The term "unit" here can refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (such as a shared processor, a dedicated processor, or a group of processors, etc.) for executing one or more software or firmware programs, and a memory, a combined logic circuit, and / or other suitable components that support the described functions. In an alternative example, the above transceiver unit 1010 can also be a transceiver circuit (for example, it can include a receiving circuit and a sending circuit), and the processing unit 1020 can be a processing circuit.

[0389] The device 1000 of each of the above solutions has the function of implementing the corresponding steps executed by the network element (such as the first network element or the session management network element) in the above method. This function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions; for example, the transceiver module can be replaced by a transceiver (for example, the sending unit in the transceiver module can be replaced by a transmitter, and the receiving unit in the transceiver module can be replaced by a receiver), and other units, such as the processing module, etc., can be replaced by a processor to respectively execute the sending and receiving operations and related processing operations in each method embodiment.

[0390] Figure 7 is a schematic diagram of another communication device 2000 provided by an embodiment of the present application. The device 2000 includes one or more processors 2010 and one or more memories 2020. The processor 2010 is used to execute the computer programs or instructions stored in the memory 2020, or read the data / signaling stored in the memory 2020 to execute the methods in the above method embodiments. The memory 2020 is used to store computer programs or instructions and / or data. The memory 2020 can be integrated with the processor 2010 or can be separately provided.

[0391] Optionally, as Figure 7As shown, the device 2000 further includes a transceiver 2030, which is used for receiving and / or transmitting signals. For example, the processor 2010 is used to control the transceiver 2030 to receive and / or transmit signals.

[0392] As a solution, the device 2000 is used to implement the operations performed by the first network element in the above method embodiments.

[0393] As another solution, the device 2000 is used to implement the operations performed by the session management network element in the above method embodiments.

[0394] It should be understood that the processor mentioned in the embodiments of the present application may be a central processing unit (CPU), or may also be other general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0395] It should also be understood that the memory mentioned in the embodiments of the present application may be a volatile memory and / or a non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable ROM (PROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM). For example, the RAM can be used as an external cache. By way of example and not limitation, the RAM includes the following various forms: static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchlink DRAM (SLDRAM), and direct rambus RAM (DR RAM).

[0396] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, the memory (storage module) can be integrated in the processor. It should also be noted that the memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0397] Figure 8 FIG. is a schematic diagram of a chip system 3000 provided by an embodiment of the present application. The chip system 3000 (or may also be referred to as a processing system) includes a logic circuit 3010 and an input / output interface 1002.

[0398] Among them, the logic circuit 3010 may be a processing circuit in the chip system 3000. The logic circuit 3010 may be coupled to a storage unit and call instructions in the storage unit, so that the chip system 3000 can implement the methods and functions of the embodiments of the present application. The input / output interface 3020 may be an input / output circuit in the chip system 3000, output the information processed by the chip system 3000, or input the data or signaling information to be processed into the chip system 3000 for processing.

[0399] As a solution, the chip system 3000 is used to implement the operations performed by the first network element or the session management network element in the above method embodiments. For example, the logic circuit 3010 is used to implement the operations related to internal processing performed by the first network element or the session management network element in the above method embodiments; the input / output interface 3020 is used to implement the operations related to sending and / or receiving performed by the first network element or the session management network element in the above method embodiments.

[0400] For the explanations and beneficial effects of the relevant content in any of the above-mentioned devices, reference can be made to the corresponding method embodiments provided above, which will not be elaborated here.

[0401] In several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the displayed or discussed couplings or direct couplings or communication connections to each other can be through some interfaces. The indirect couplings or communication connections of the devices or units can be in electrical, mechanical or other forms.

[0402] The embodiments of this application also provide a communication system, including a first network element and a session management network element. Among them, the first network element is used to implement the operations performed by the first network element in the above method embodiments, and the session management network element is used to implement the operations performed by the session management network element in the above method embodiments. Optionally, the communication system further includes one or more network elements among a traffic splitting point, a first anchor point or a second anchor point. Among them, the traffic splitting point is used to implement the operations performed by the traffic splitting point in the above method embodiments, the first anchor point is used to implement the operations performed by the first anchor point in the above method embodiments, and the second anchor point is used to implement the operations performed by the second anchor point in the above method embodiments.

[0403] The embodiments of this application also provide a communication system, including a session management network element, a traffic splitting point, a first anchor point and a second anchor point. Among them, the session management network element is used to implement the operations performed by the session management network element in the above method embodiments, the traffic splitting point is used to implement the operations performed by the traffic splitting point in the above method embodiments, the first anchor point is used to implement the operations performed by the first anchor point in the above method embodiments, and the second anchor point is used to implement the operations performed by the second anchor point in the above method embodiments. Optionally, the communication system further includes a first network element, where the first network element is used to implement the operations performed by the first network element in the above method embodiments.

[0404] The embodiments of the present application further provide a computer-readable storage medium, on which computer instructions for implementing the methods executed by the first network element or the session management network element in the above-mentioned method embodiments are stored. For example, when the computer program is executed by a computer, the computer can implement the methods executed by the first network element or the session management network element in the above-mentioned method embodiments.

[0405] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. For example, the computer can be a personal computer, a server, or a network device, etc. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or a data center that includes one or more integrated available media. The available medium can be a magnetic medium (such as a floppy disk, a hard disk, a magnetic tape), an optical medium (such as a DVD), or a semiconductor medium (such as a solid state disk (SSD), etc.). For example, the foregoing available media include, but are not limited to: USB flash drives, external hard drives, ROM, RAM, magnetic disks, or optical discs, etc., which can store program codes.

[0406] To facilitate understanding of the embodiments of the present application, the following points are explained.

[0407] First, in each embodiment of the present application, if there is no special description and logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced to each other. The technical features in different embodiments can be combined to form new embodiments according to their internal logical relationships.

[0408] Second, in the embodiments of the present application, "a plurality of" means two or more. "And / or" describes the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone, where A and B can be singular or plural. In the written description of the present application, the character " / " generally represents an "or" relationship between the associated objects before and after.

[0409] Third, in the embodiments of the present application, "first", "second", and various numerical numbers (for example, #1, #2, etc.) are used for distinction for the convenience of description and do not limit the scope of the embodiments of the present application. For example, to distinguish different messages, etc., rather than for describing a specific order or sequence. It should be understood that the objects described in this way can be interchanged under appropriate circumstances so as to be able to describe the solutions other than the embodiments of the present application.

[0410] Fourth, in the embodiments of the present application, descriptions such as "when...", "in the case of...", and "if" all refer to that the device will perform corresponding processing under a certain objective situation, which does not limit the time, and does not require the device to have a judgment action when implemented, nor does it mean that there are other limitations.

[0411] Fifth, in the embodiments of the present application, the terms "include" and "have" and any of their variations are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units does not have to be limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or are inherent to these processes, methods, products, or devices.

[0412] Sixth, in the embodiments of the present application, "for indicating" may include direct indication and indirect indication. When describing that a certain indication information is used to indicate A, it may include that the indication information directly indicates A or indirectly indicates A, and does not mean that A must be carried in the indication information.

[0413] The indication methods involved in the embodiments of the present application should be understood to cover various methods that can enable the party to be indicated to obtain the indication information. The indication information can be sent as a whole or divided into multiple sub-information and sent separately, and the sending periods and / or sending opportunities of these sub-information can be the same or different. The present application does not limit the specific sending method.

[0414] The "indication information" in the embodiments of the present application can be explicit indication, that is, directly indicated by signaling, or obtained according to the parameters indicated by the signaling, combined with other rules or combined with other parameters or through derivation. It can also be implicit indication, that is, obtained according to rules or relationships, or according to other parameters, or through derivation. The present application does not make specific limitations on this.

[0415] Seventh, in the embodiments of the present application, "storage" may refer to being stored in one or more memories. The one or more memories may be separately provided, or may be integrated in an encoder or a decoder, a processor, or a communication device. The one or more memories may also have a part separately provided and a part integrated in a decoder, a processor, or a communication device. The type of the memory may be any form of storage medium, and the present application does not limit this.

[0416] Eighth, in the embodiments of the present application, "communication" may also be described as "data transmission", "information transmission", "data processing", etc. "Transmission" includes "sending" and "receiving", and the present application does not limit this.

[0417] As mentioned above, the above are only specific embodiments of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art within the technical scope disclosed by the present application can easily think of changes or substitutions, which should all be covered by the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A communication method, characterized in that including: A first network element receives a first query message from a first anchor point of a session of a terminal device, where the first query message includes a domain name, and the first query message is used to query an address of a server that provides a service corresponding to the domain name for the terminal device; The first network element obtains an address of a first server according to the first query message, where the first server is used to provide a service corresponding to the domain name for the terminal device; The first network element determines a data network access identifier corresponding to the address of the first server; The first network element sends a first message for determining a splitting point to a session management network element, where the first message includes the address of the first server and the data network access identifier, and the splitting point is used to send data of the session to the first server via a second anchor point; 2. The method according to claim 1, wherein The first anchor point is an anchor point configured by the session management network element for data transmission between the terminal device and a data network, and the first server is a server in the data network; 3. The method according to claim 1 or 2, characterized in that, The first message is further used to determine the second anchor point; 4. The method according to claim 3, characterized in that, The data network access identifier is used to determine the splitting point and the second anchor point; 5. The method according to any one of claims 1-4, characterized in that, Server deployment information includes a correspondence between each of one or more data network access identifiers and an address of a server, the one or more data network access identifiers include the data network access identifier, and the address of the server includes the address of the first server; The first network element determines a data network access identifier corresponding to the address of the first server, including: The first network element determines a data network access identifier corresponding to the address of the first server according to the server deployment information; 6. The method according to claim 5, wherein The first network element determines a data network access identifier corresponding to the address of the first server according to the server deployment information, including: The first network element determines a data network access identifier corresponding to the address of the first server according to the server deployment information and location information of the terminal device; 7. The method according to any one of claims 1-6, characterized in that Before the first network element sends a first message for determining a splitting point to a session management network element, it further includes: The first network element determines to send the first message to the session management network element according to a processing rule, where the processing rule matches the domain name or the address of the first server, and the processing rule indicates that the first message needs to be sent to the session management network element; 8. The method according to any one of claims 1-7, characterized in that, The first network element obtains the address of the first server according to the first query message, including: The first network element determines that the second query message includes option information according to a processing rule, where the option information is used to determine the address of the first server, the processing rule matches the domain name and corresponds to the session, and the processing rule indicates that a query message sent to a domain name server needs to include option information; The first network element sends a second query message to a domain name server, where the second query message includes the domain name and the option information, and the second query message is used to query an address of a server corresponding to the domain name; The first network element receives the address of the first server from the domain name server.

9. The method according to any one of claims 1-8, characterized in that, The first network element obtains the address of the first server according to the first query message, including: The first network element sends a second query message to the domain name server according to a processing rule, where the processing rule matches the domain name and corresponds to the session, the processing rule includes the address of the domain name server, the second query message includes the domain name, and the second query message is used to query the address of the server corresponding to the domain name; The first network element receives the address of the first server from the domain name server.

10. The method according to any one of claims 7-9, characterized in that, The method further includes: The first network element generates the processing rule according to server deployment information and / or feature information, the server deployment information indicates how each server is deployed in the data network, the first server is a server in the data network, and the feature information is used to describe the features of the session or the terminal device.

11. The method according to claim 10, wherein Before the first network element generates the processing rule according to server deployment information and / or feature information, the method further includes: The first network element receives indication information from the session management network element, and the indication information is used to instruct the first network element to generate a processing rule corresponding to the session.

12. The method according to any one of claims 7-9, characterized in that, The method further includes: The first network element receives the processing rule from the session management network element, the processing rule includes identification information of a baseline processing rule, the baseline processing rule is generated by the first network element according to server deployment information and / or feature information, the server deployment information indicates how each server is deployed in the data network, the first server is a server in the data network, and the feature information is used to describe the features of the session or the terminal device.

13. A communication method, characterized in that, Including: The session management network element selects a first anchor point for the session of the terminal device, the first anchor point is used to transmit data between the terminal device and the data network, the data includes a first query message, the first query message includes a domain name, and the first query message is used to query the address of the server that provides the service corresponding to the domain name for the terminal device; The session management network element receives a first message from the first network element, the first message includes the address of the first server and a data network access identifier, and the first server is a server in the data network; The session management network element determines a shunt point according to the first message; The session management network element instructs the shunt point to send the data of the session to the first server via a second anchor point.

14. The method according to claim 13, wherein The method further includes: The session management network element determines the second anchor point according to the first message.

15. The method according to claim 14, wherein: The session management network element determines a shunt point according to the first message, including: the session management network element determines the shunt point according to the data network access identifier; The session management network element determines the second anchor point according to the first message, including: the session management network element determines the second anchor point according to the data network access identifier.

16. The method according to any one of claims 1-15, characterized in that, The first query message further includes the address of the first network element, and the method further includes: When at least one of the following conditions is satisfied, the session management network element sends the address of the first network element to the terminal device: The terminal device is outside the service range of the session management network element; The data network access identifier of the session is a data network access identifier not supported by the session management network element; The terminal device is within the service range of the first network element; The data network access identifier of the session corresponds to the first network element; or The domain name in the first query message corresponds to the first network element.

17. The method according to claim 16, wherein The method further includes: When the at least one condition is satisfied, the session management network element sends indication information to the first network element, and the indication information is used to instruct the first network element to generate a processing rule corresponding to the session, where the processing rule is used to obtain the address of the server, or the processing rule is used to indicate that the first message needs to be sent to the session management network element.

18. The method according to claim 17, wherein The method further includes: The session management network element sends feature information to the first network element, and the feature information is used to describe the features of the session or the terminal device, and the feature information is used to generate the processing rule.

19. The method according to claim 16, wherein The method further includes: When the at least one condition is satisfied, the session management network element sends a processing rule corresponding to the session to the first network element, where the processing rule is used to obtain the address of the server, or the processing rule is used to indicate that the first message needs to be sent to the session management network element; Wherein, the processing rule includes identification information of a baseline processing rule, and the baseline processing rule is generated by the first network element according to server deployment information and / or feature information, the server deployment information indicates how each server is deployed in the data network, the first server is a server in the data network, and the feature information is used to describe the features of the session or the terminal device.

20. The method according to claim 13, wherein Before the session management network element receives the first message from the first network element, the method further includes: The session management network element receives the domain name from the second network element, and the second network element is used to provide the address of the server for the terminal device; The session management network element sends a second message to the second network element according to the domain name, and the second message is used to instruct the second network element to send a query message including the domain name to the first network element.

21. The method according to claim 13, characterized in that, Before the session management network element receives the first message from the first network element, the method further includes: The session management network element sends a second processing rule to the second network element, and the second network element is used to provide the address of the server for the terminal device, the second processing rule corresponds to the session and matches the domain name, and the second processing rule further includes: sending a query message including the domain name to the first network element.

22. A communication device, characterized in that, Including a module for executing the method according to any one of claims 1-21.

23. A communication device, characterized in that, It includes a processor and a memory. The memory is used to store instructions. When the instructions are executed by the processor, the processor executes the method according to any one of claims 1-21.

24. A computer program product comprising instructions, characterized in that, When the instructions run on a computer, the computer executes the method according to any one of claims 1-21.

25. A communication system, characterized in that, It includes a first network element and a session management network element, where: The first network element is used to execute the method according to any one of claims 1-12. The session management network element is used to execute the method according to any one of claims 13-21.

26. The system according to claim 25, wherein The system further includes one or more of a shunt point, a first anchor point or a second anchor point, where: The shunt point is used to send the data of the session of the terminal device to the first server via the second anchor point. The first anchor point is used to transmit data between the terminal device and the data network, and the first server is a server in the data network. The second anchor point is used to send the data of the session from the shunt point to the first server.

27. A communication system, characterized in that, It includes a session management network element, a shunt point, a first anchor point and a second anchor point, where: The session management network element is used to execute the method according to any one of claims 13-21. The shunt point is used to send the data of the session of the terminal device to the first server via the second anchor point. The first anchor point is used to transmit data between the terminal device and the data network, and the first server is a server in the data network. The second anchor point is used to send the data of the session from the shunt point to the first server.

28. A communication method, characterized in that, It includes: The session management network element selects a first anchor point for the session of the terminal device. The first anchor point is used to transmit data between the terminal device and the data network. The data includes a first query message. The first query message includes a domain name. The first query message is used to query the address of the server that provides the service corresponding to the domain name for the terminal device. The first network element receives the first query message from the first anchor point. The first network element obtains the address of the first server according to the first query message. The first server is a server in the data network. The first network element determines the data network access identifier corresponding to the address of the first server. The first network element sends a first message to the session management network element. The first message includes the address of the first server and the data network access identifier. The session management network element determines the shunt point according to the first message. The session management network element instructs the shunt point to send the data of the session to the first server via the second anchor point.

29. The method according to claim 28, wherein The method further includes: The first anchor point sends the first query message to the first network element. The shunt point sends the data of the session to the second anchor point. The second anchor point receives the data of the session from the shunt point and sends the data of the session to the first server.

30. A communication method, characterized in that, It includes: The session management network element selects a first anchor point for the session of the terminal device. The first anchor point sends a first query message to the first network element. The first query message includes a domain name, and the first query message is used to query the address of the server that provides the service corresponding to the domain name for the terminal device; The session management network element receives a first message from the first network element. The first message includes the address of the first server and a data network access identifier, and the first server is a server in the data network; The session management network element determines a shunt point according to the first message; The session management network element instructs the shunt point to send the data of the session to the first server via the second anchor point; The shunt point sends the data of the session to the second anchor point; The second anchor point receives the data of the session from the shunt point and sends the data of the session to the first server.

Images