WO2023207637A1 - 通信方法及装置 - Google Patents

通信方法及装置 Download PDF

Info

Publication number
WO2023207637A1
WO2023207637A1 PCT/CN2023/088475 CN2023088475W WO2023207637A1 WO 2023207637 A1 WO2023207637 A1 WO 2023207637A1 CN 2023088475 W CN2023088475 W CN 2023088475W WO 2023207637 A1 WO2023207637 A1 WO 2023207637A1
Authority
WO
WIPO (PCT)
Prior art keywords
network element
dns
address
user plane
message
Prior art date
Application number
PCT/CN2023/088475
Other languages
English (en)
French (fr)
Inventor
魏鑫鹏
朱奋勤
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2023207637A1 publication Critical patent/WO2023207637A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H04W40/04—Communication route or path selection, e.g. power-based or shortest path routing based on wireless node resources

Definitions

  • the present application relates to the field of communication, and in particular, to a communication method and device.
  • Edge computing is a new network architecture that is used to optimize the user's resource access process by deploying computing resources at the edge of the network close to the user, such as reducing the network transmission delay between the user and the computing resource.
  • EAS edge application servers
  • the terminal can initiate access to the edge application server discovery function (EASDF).
  • EASDF can interact with the session management function (SMF) network element based on the terminal's access to discover available EAS and provide the terminal with the IP address of the EAS.
  • SMF session management function
  • the terminal can access the EAS according to the IP address of the EAS to obtain edge services.
  • Edge computing services can support roaming terminal access, but how to route data from roaming terminals is an issue worth considering.
  • Embodiments of the present application provide a communication method and device to solve the data routing problem of roaming terminals in edge computing.
  • the first aspect is to provide a communication method.
  • the method includes: a user plane network element receives a first domain name system DNS query message from a terminal, and sends the first DNS query message and a first identifier to an edge application service function.
  • the first DNS query message is used to query the address of the application service, and the first identifier is an identifier allocated by the VPLMN to the terminal.
  • the first identification is used by the edge application service function to determine whether there is a DNS rule matching the first identification.
  • the edge application service function can identify the terminal through the first identification assigned by the VPLMN, or it can be understood that the edge application service function can determine that the first DNS query message corresponds to the terminal through the first identification, so that in the case of possible address conflicts , the edge application service function can still identify the terminal, thereby correctly processing the DNS query message of the terminal, achieving correct data routing, and facilitating the terminal to obtain application services, such as edge services.
  • the first identification can be used to identify the terminal within the VPLMN.
  • the first identifier may be the VPLMN, such as a network element within the VPLMN, an identifier assigned to the protocol data unit PDU session of the terminal, or the first identifier may be mapped to the PDU session of the terminal within the VPLMN.
  • the terminal's PDU session may be the terminal's home routing HR PDU session.
  • the user plane network element receives the first domain name system DNS query message from the terminal through the terminal's PDU session.
  • the user plane network element is configured with a first user plane processing rule.
  • the first user plane processing rule indicates: for the first DNS query message, the user plane network element sends the first DNS to the edge application service function. Query message and first identifier. In this way, the user plane network element can process the first DNS query message according to the configured first user plane processing rule, thereby avoiding misoperation or mishandling of the user plane network element.
  • the user plane network element sends the first DNS query message and the first identifier to the edge application service function, including: the user plane network element sends the first DNS query message and the first identifier to the edge application service function through the communication tunnel.
  • the first identifier; the first identifier is carried in the header of the communication tunnel, so that the edge application service function can identify that the received information element is the first identifier through the communication tunnel.
  • the first identification is an identification of the communication tunnel, that is, the first identification can be implemented by reusing existing information elements to reduce implementation difficulty.
  • the first identifier may also be carried in the first DNS query message, such as in a reserved field of the first DNS query message.
  • the method described in the first aspect may further include: the user plane network element receives the first DNS query message from the edge application service function.
  • the first DNS response message and the second identifier of the function and sends the first DNS response message to the terminal according to the second identifier.
  • the second identifier is an identifier assigned by the VPLMN to the terminal, and the first DNS response message carries the address of the application service.
  • the second identification can be used to identify the terminal within the VPLMN.
  • the second identifier may be a VPLMN, such as a network element within the VPLMN, an identifier assigned to the terminal's PDU session, or the second identifier may be mapped to the terminal's PDU session within the VPLMN, that is, the user plane network element may be based on the second identifier. Identification, mapping the terminal's message (such as the first DNS response message) to the terminal's PDU session, thereby sending the first DNS response message to the terminal so that the terminal can obtain application services, such as edge services.
  • the user plane network element is configured with a second user plane processing rule, and the second user plane processing rule indicates that: for the first DNS response message and the second identification, the user plane network element sends the first DNS response message to the terminal.
  • the user plane network element can process the first DNS response message according to the configured second user plane processing rule, thereby avoiding misoperation or mishandling of the user plane network element.
  • the user plane network element receives the first DNS response message and the second identification from the edge application service function, including: the user plane network element receives the first DNS response message and the second identity from the edge application service function through the communication tunnel.
  • Identity the second identification is carried in the header of the communication tunnel, so that the user plane network element can identify that the received cell is the second identification through the communication tunnel.
  • the second identification is an identification of the communication tunnel, that is, the second identification can be implemented by reusing existing information elements to reduce implementation difficulty.
  • the second identifier may be the same as the first identifier, or may be different, without limitation.
  • the second identifier may also be carried in the first DNS response message, such as in a reserved field of the first DNS response message.
  • the method described in the first aspect may further include: the user plane network element receives the first DNS query message from the edge application service function. function, and sends a third DNS query message to the HPLMN of the terminal according to the second DNS query message and the second identifier.
  • the second identifier is the identifier assigned by VPLMN to the terminal, and the second DNS The query message is used to obtain the address of the application service, and the third DNS query message is used to request the address of the application service.
  • the second identification can be used to identify the terminal within the VPLMN.
  • the second identifier may be a VPLMN, such as a network element within the VPLMN, an identifier assigned to the terminal's PDU session, or the second identifier may be mapped to the terminal's PDU session within the VPLMN, that is, the user plane network element may be based on the second identifier. Identification, mapping the terminal's message (such as the third DNS query message) to the terminal's PDU session, thereby sending the third DNS query message to the terminal's HPLMN, so that the terminal can obtain the corresponding application service.
  • the terminal's message such as the third DNS query message
  • the user plane network element is configured with a third user plane processing rule.
  • the third user plane processing rule indicates that: for the second DNS query message and the second identification from the edge application service function, the user plane network element sends a request to the terminal to the user plane network element.
  • the HPLMN sends a third DNS query message.
  • the user plane network element can process the second DNS query message according to the configured third user plane processing rule, thereby avoiding misoperation or mishandling of the user plane network element.
  • the user plane network element receives the second DNS query message and the second identification from the edge application service function, including: the user plane network element receives the second DNS query message and the second identity from the edge application service function through the communication tunnel.
  • Identity the second identification is carried in the header of the communication tunnel, so that the user plane network element can identify that the received cell is the second identification through the communication tunnel.
  • the second identification is an identification of the communication tunnel, that is, the second identification can be implemented by reusing existing information elements to reduce implementation difficulty.
  • the second identifier may also be carried in the second DNS query message, such as in a reserved field of the second DNS query message.
  • the method described in the first aspect may further include: the user plane network element determines the first identifier and sends it to the session management network element.
  • the first identifier is so that the VPLMN network element, such as the edge application service function, can obtain the first identifier from the session management network element, thereby identifying the terminal's message based on the first identifier and achieving correct data routing.
  • the user plane network element can determine the first identifier by itself, or determine the first identifier according to instructions from the session management network element, without limitation.
  • the user plane network element receives the first identifier from the session management network element, that is, obtains the first identifier from the session management network element, so that when sending the terminal's message, the first identifier can be sent at the same time to facilitate edge application service functions.
  • the terminal's message can be identified according to the first identifier, and correct data routing can be achieved.
  • the method described in the first aspect may further include: the user plane network element determines the second identifier and sends it to the session management network element.
  • the second identifier is so that the VPLMN network element, such as the edge application service function, can obtain the second identifier from the session management network element, so that the second identifier can be sent at the same time when sending the terminal message, so that the user plane network element can be based on the second identifier.
  • the identifier identifies the terminal's message and enables correct data routing.
  • the user plane network element can determine the second identity by itself, or determine the second identity according to the instruction of the user plane network element, without limitation.
  • the user plane network element receives the second identity from the session management network element, that is, the user plane network element obtains the second identity from the session management network element, so that it can receive the second DNS query message or the first DNS response message. , identifying the received message as a terminal message through the second identifier, thereby achieving correct data routing.
  • the second aspect is to provide a communication method.
  • the method includes: an edge application service function receiving a first domain name system DNS query message and a first identifier from a user plane network element, and determining whether there is a DNS message processing rule matching the first DNS query message and the first identifier.
  • the first identifier is an identifier assigned to the terminal by the visiting public land mobile network VPLMN. The terminal roams into the VPLMN, and the first DNS query message is used to query the address of the application service.
  • the edge application service function receives the first DNS query message and the first identification from the user plane network element, including: the edge application service function receives the first DNS query from the user plane network element through the communication tunnel. message and a first identifier; the first identifier is carried in the header of the communication tunnel.
  • the first identifier is an identifier of the communication tunnel.
  • the method described in the second aspect may further include: in the case where there is a DNS message processing rule that matches the first DNS query message and the first identification, the edge application service function reports to the user plane network element Send the first DNS response message and the second identification.
  • the second identifier is an identifier assigned by the VPLMN to the terminal, and the first DNS response message carries the address of the application service.
  • the DNS message processing rules may be stored in the DNS context, and the DNS context may also include the first identifier.
  • the edge application service function may determine a DNS context matching the first identifier based on the first identifier, such as a context containing the first identifier.
  • the edge application service function may determine whether there is a DNS message processing rule in the DNS context that matches the first DNS query message. At this time, if the full address domain name FQDN in the first DNS query message matches the FQDN in a DNS message processing rule in the DNS context, it means that there is a DNS message processing rule matching the first DNS query message, that is, there is a DNS message processing rule matching the first DNS query message.
  • DNS message processing rules matching the first DNS query message and the first identifier are examples of the DNS query message.
  • the FQDN in the first DNS query message does not match the FQDN in any DNS message processing rule in the DNS context, it means that there is no DNS message processing rule matching the first DNS query message, that is, there is no DNS message processing rule matching the first DNS query message.
  • DNS message processing rules that match the DNS query message and the first identifier.
  • the edge application service function can provide the terminal with the address of the edge application service through the first DNS response message, so that the terminal can obtain the edge service.
  • the edge application service function is configured with a DNS message processing rule, and the DNS message processing rule indicates that the edge application service function sends the first DNS response message and the second identification to the user plane network element.
  • the edge application service function can process the first DNS response message according to the configured DNS message processing rules, thereby avoiding misoperation or mishandling of the edge application service function.
  • the edge application service function sends the first DNS response message and the second identification to the user plane network element, including: the edge application service function sends the first DNS response message and the second identification to the user plane network element through the communication tunnel;
  • the second identification is carried in the header of the communication tunnel.
  • the second identifier is an identifier of the communication tunnel.
  • the method described in the second aspect may further include: in the case where there is no DNS message processing rule matching the first DNS query message and the first identification, the edge application service function provides the user with access to the network.
  • the second DNS query message and the second identifier are sent by the terminal; the second identifier is an identifier assigned by the VPLMN to the terminal, and the second DNS query message is used to obtain the address of the application service.
  • the edge application service function can send a second DNS query message to the HPLMN of the terminal through the user plane network element, so that the terminal can finally obtain the corresponding application service.
  • the edge application service function sends the second DNS query message and the second identification to the user plane network element, including: the edge application service function sends the second DNS query message and the second identification to the user plane network element through the communication tunnel.
  • the second identifier is carried in the header of the communication tunnel.
  • the second identification is an identification of the communication tunnel.
  • the method in the second aspect may further include: the edge application service function determines the first identification, and sends the first identification to the session management network element.
  • the edge application service function can determine the first identifier by itself, or determine the first identifier according to instructions from the session management network element, without limitation. Alternatively, the edge application service function receives the first identification from the session management network element.
  • the method in the second aspect may further include: the edge application service function determines the second identification, and sends the second identification to the session management network element.
  • the edge application service function can determine the second identity by itself, or determine the second identity according to the instructions of the session management network element, without limitation.
  • the edge application service function receives the second identification from the session management network element.
  • the third aspect is to provide a communication method.
  • the method includes: the session management network element determines the first identifier, and sends the first identifier to the user plane network element.
  • the first identifier is the identifier in the visited public land mobile network VPLMN corresponding to the terminal, and the terminal roams into the VPLMN.
  • the method described in the third aspect may further include: the session management network element sending the first identifier to the edge application service function.
  • the session management network element determines the first identifier during the session establishment process of the protocol data unit PDU of the terminal.
  • the terminal's PDU session is the terminal's home routing HR PDU session.
  • the method described in the third aspect may further include: the session management network element determines the second identifier, and sends the second identifier to the user plane network element.
  • the method described in the third aspect may further include: the session management network element sending the second identification to the edge application service function.
  • the session management network element determines the second identifier during the establishment process of the terminal's PDU session.
  • the PDU session of the terminal is the HR PDU session of the terminal.
  • the fourth aspect is to provide a communication method.
  • the method includes: a user plane network element receives a first domain name system DNS query message from a terminal, and replaces the source address of the first DNS query message from the terminal's address to the first address to obtain a second DNS query message, thereby sending the message to the edge.
  • the application service function sends a second DNS query message.
  • the terminal roams to the visited public land mobile network VPLMN, and the first DNS query message is used to query the address of the application service, and the first address is the address allocated by the VPLMN to the terminal.
  • the edge application service function can use the first address assigned by the VPLMN to the terminal to identify the terminal's DNS query message to avoid address conflicts, achieve correct data routing, and facilitate the terminal to obtain application services, such as edge services.
  • the first address may specifically be a VPLMN, such as a network element within the VPLMN, and the protocol number for the terminal.
  • the identifier assigned to the PDU session of the data unit, or the first address, can be mapped to the PDU session of the terminal.
  • the user plane network element receives the first domain name system DNS query message from the terminal through the terminal's PDU session.
  • the terminal's PDU session can be the terminal's home routing HR PDU session.
  • the user plane network element is configured with a first user plane processing rule.
  • the first user plane processing rule indicates that: for the first DNS query message, the user plane network element changes the source address of the first DNS query message. Replace the terminal's address with the first address to obtain a second DNS query message, and send the second DNS query message to the edge application service function.
  • the user plane network element can process the first DNS query message according to the configured first user plane processing rule, thereby avoiding misoperation or misprocessing of the user plane network element.
  • the method of the fourth aspect may also include: the user plane network element receives the first DNS response from the edge application service function.
  • the first DNS response message carries the address of the application service.
  • the user plane network element replaces the destination address of the first DNS response message with the address of the terminal from the first address to obtain the second DNS response message, thereby sending the second DNS response message to the terminal so that the terminal can obtain application services.
  • the user plane network element is configured with a second user plane processing rule.
  • the second user plane processing rule indicates that: for the first DNS response message, the user plane network element changes the destination address of the first DNS response message to the first address. Replace with the address of the terminal to obtain a second DNS response message, and send the second DNS response message to the edge application service function.
  • the method of the fourth aspect may also include: the user plane network element receives the third DNS query from the edge application service function. message, replace the destination address of the third DNS query message from the second address to the address of the DNS server in the HPLMN to obtain the fourth DNS query message, thereby sending the fourth DNS query message to the HPLMN.
  • the second address is an address assigned by the VPLMN to the terminal.
  • the second address may be an identifier assigned by the VPLMN to the terminal's protocol data unit PDU session, or the second address may be mapped to the terminal's PDU session, that is, the user plane network element may map the terminal's message to the terminal based on the second address.
  • the second address and the first address may be different.
  • the user plane network element is configured with a third user plane processing rule.
  • the third user plane processing rule indicates that: for the third DNS query message, the user plane network element changes the destination address of the third DNS query message from the second address. Replace with the address of the DNS server in HPLMN to obtain the fourth DNS query message, and send the fourth DNS query message to the edge application service function.
  • the method described in the fourth aspect may further include: the user plane network element determines the first address and sends it to the session management network element.
  • First address The user plane network element can determine the first address by itself, or determine the first address according to instructions from the session management network element, without limitation. Alternatively, the user plane network element receives the first address from the session management network element.
  • the method described in the fourth aspect may further include: the user plane network element determines the second address and sends the second address to the session management network element. Two addresses.
  • the user plane network element can determine the second address by itself, or determine the second address according to the instructions of the session management network element, without limitation. Alternatively, the user plane network element receives the second address from the session management network element.
  • the fifth aspect provides a communication method.
  • the method includes: the session management network element determines the first address, and responds to the edge Send the first address using the service function.
  • the first address is the address assigned to the terminal by the visiting public land mobile network VPLMN, and the terminal roams into the VPLMN.
  • the method described in the fifth aspect may further include: the session management network element sending the first address to the user plane network element.
  • the session management network element determines the first address during the establishment process of the protocol data unit PDU session of the terminal.
  • the terminal's PDU session is the terminal's home routing HR PDU session.
  • the method described in the fifth aspect may further include: the session management network element determines the second address, and sends the second address to the edge application service function.
  • the second address is an address assigned by the VPLMN to the terminal, and the second address is different from the first address.
  • the method described in the fifth aspect may further include: the session management network element sending the second address to the user plane network element.
  • the session management network element determines the second address during the establishment process of the terminal's PDU session.
  • the PDU session of the terminal is the HR PDU session of the terminal.
  • a sixth aspect provides a communication device.
  • the device includes: receiving module and sending module.
  • the receiving module is used to receive the first domain name system DNS query message from the terminal, and the sending module is used to send the first DNS query message and the first identification to the edge application service function.
  • the first DNS query message is used to query the address of the application service, and the first identifier is an identifier allocated by the VPLMN to the terminal.
  • the first identification is used by the edge application service function to determine whether there is a DNS rule matching the first identification.
  • the first identification can be used to identify the terminal within the VPLMN.
  • the first identifier may be the VPLMN, such as a network element within the VPLMN, an identifier assigned to the protocol data unit PDU session of the terminal, or the first identifier may be mapped to the PDU session of the terminal within the VPLMN.
  • the terminal's PDU session can be the terminal's home routing HR PDU session.
  • the receiving module is configured to receive a first domain name system DNS query message from the terminal through a PDU session of the terminal.
  • the communication device described in the sixth aspect is configured with a first user plane processing rule, and the first user plane processing rule indicates that: for the first DNS query message, the device sends the first DNS query message to the edge application service function. a DNS query message and the first identifier.
  • the sending module is configured to send a first DNS query message and a first identifier to the edge application service function through the communication tunnel; the first identifier is carried in the header of the communication tunnel.
  • the first identifier is an identifier of the communication tunnel.
  • the first identifier may also be carried in the first DNS query message, such as in a reserved field of the first DNS query message.
  • the receiving module is also configured to receive the first DNS response message and the second identification from the edge application service function after the sending module sends the first DNS query message and the first identification to the edge application service function.
  • the communication device further includes: a processing module; a processing module configured to control the sending module to send the first DNS response message to the terminal according to the second identification.
  • the second identifier is an identifier assigned by the VPLMN to the terminal, and the first DNS response message carries the address of the application service.
  • the second identification can be used to identify the terminal within the VPLMN.
  • the second identifier may be VPLMN,
  • the network element in the VPLMN, the identifier assigned to the terminal's PDU session, or the second identifier can be mapped to the terminal's PDU session in the VPLMN.
  • the communication device described in the sixth aspect is configured with a second user plane processing rule, the second user plane processing rule indicates: for the first DNS response message and the second identification, the device sends the first DNS response to the terminal information.
  • the receiving module is configured to receive the first DNS response message and the second identification from the edge application service function through the communication tunnel; the second identification is carried in the header of the communication tunnel.
  • the second identifier is an identifier of the communication tunnel.
  • the second identifier may be the same as the first identifier, or may be different, without limitation.
  • the second identifier may also be carried in the first DNS response message, such as in a reserved field of the first DNS response message.
  • the receiving module is also configured to receive a second DNS query message and a second identification from the edge application service function after the sending module sends the first DNS query message and the first identification to the edge application service function.
  • the communication device further includes: a processing module; the processing module is configured to control the sending module to send a third DNS query message to the HPLMN of the terminal according to the second DNS query message and the second identification.
  • the second identifier is an identifier assigned by the VPLMN to the terminal, the second DNS query message is used to obtain the address of the application service, and the third DNS query message is used to request the address of the application service.
  • the second identification can be used to identify the terminal within the VPLMN.
  • the second identifier may be the VPLMN, such as a network element within the VPLMN, an identifier assigned to the terminal's PDU session, or the second identifier may be mapped to the terminal's PDU session within the VPLMN.
  • the communication device described in the sixth aspect is configured with a third user plane processing rule, the third user plane processing rule indicates: for the second DNS query message and the second identification from the edge application service function, the device The terminal's HPLMN sends a third DNS query message.
  • the receiving module is configured to receive the second DNS query message and the second identification from the edge application service function through the communication tunnel; the second identification is carried in the header of the communication tunnel.
  • the second identifier is an identifier of the communication tunnel.
  • the second identifier may be the same as the first identifier, or may be different, without limitation.
  • the second identifier may also be carried in the second DNS query message, such as in a reserved field of the second DNS query message.
  • the communication device further includes: a processing module; the processing module is configured to determine the first identifier and control the sending module before the receiving module receives the first DNS message from the terminal. Send the first identifier to the session management network element.
  • the receiving module is configured to receive the first identification from the session management network element.
  • the communication device further includes: a processing module; the processing module is configured to determine the second identity and control the sending module before the receiving module receives the first DNS message from the terminal. Send the second identification to the session management network element.
  • the receiving module is configured to receive the second identification from the session management network element.
  • the sending module and the receiving module can also be integrated into a sending and receiving module to implement the sending and receiving functions of the communication device described in the sixth aspect.
  • the communication device may further include a storage module that stores programs or instructions.
  • the processing module executes the program or instruction, the communication device can execute the communication method described in the first aspect.
  • the communication device described in the sixth aspect may be a network device, such as a user plane network element, or may be a chip (system) or other component or component that can be disposed in the network device, or may include a network device. device, this application does not limit this.
  • a communication device in a seventh aspect, includes: transceiver module and processing module.
  • the transceiver module is used to receive the first domain name system DNS query message and the first identifier from the user plane network element, and the processing module is used to determine whether there is a DNS message processing rule matching the first DNS query message and the first identifier.
  • the first identifier is an identifier assigned to the terminal by the visiting public land mobile network VPLMN. The terminal roams into the VPLMN, and the first DNS query message is used to query the address of the application service.
  • the transceiver module is configured to receive the first DNS query message and the first identifier from the user plane network element through the communication tunnel; the first identifier is carried in the header of the communication tunnel.
  • the first identifier is an identifier of the communication tunnel.
  • the transceiver module when there is a DNS message processing rule matching the first DNS query message and the first identifier, the transceiver module is configured to send the first DNS response message and the second identifier to the user plane network element.
  • the second identifier is an identifier assigned by the VPLMN to the terminal, and the first DNS response message carries the address of the application service.
  • the communication device described in the seventh aspect is configured with a DNS message processing rule, and the DNS message processing rule indicates that the device sends the first DNS response message and the second identification to the user plane network element.
  • the transceiver module is configured to send the first DNS response message and the second identifier to the user plane network element through the communication tunnel; the second identifier is carried in the header of the communication tunnel.
  • the second identifier is an identifier of the communication tunnel.
  • the transceiver module when there is no DNS message processing rule matching the first DNS query message and the first identifier, the transceiver module is configured to send the second DNS query message and the second DNS query message to the user plane network element.
  • Identity the second identification is an identification assigned by VPLMN to the terminal, and the second DNS query message is used to obtain the address of the application service.
  • the transceiver module is configured to send the second DNS query message and the second identification to the user plane network element through the communication tunnel.
  • the second identification is carried in the header of the communication tunnel.
  • the second identification is an identification of the communication tunnel.
  • the processing module is also configured to determine the first identifier before the transceiver module receives the first DNS query message and the first identifier from the user plane network element, and control the transceiver module to send the message to the session management network element. Send the first identification.
  • the transceiver module is configured to receive the first identifier from the session management network element.
  • the processing module is also configured to determine the second identifier before the transceiver module receives the first DNS query message and the first identifier from the user plane network element, and control the transceiver module to send the message to the session management network element. Send the second identification.
  • the transceiver module is configured to receive the second identification from the session management network element.
  • the transceiver module may also include a sending module and a receiving module.
  • the sending module is used to implement the sending function of the communication device described in the seventh aspect
  • the receiving module is used to implement the receiving function of the communication device described in the seventh aspect.
  • the communication device may further include a storage module that stores programs or instructions.
  • the processing module executes the program or instruction, the communication device can execute the communication method described in the second aspect.
  • the communication device described in the seventh aspect may be a network device, such as an edge application service function, or It may be a chip (system) or other component or assembly that can be installed in a network device, or it may be a device including a network device, which is not limited in this application.
  • a communication device in an eighth aspect, includes: transceiver module and processing module.
  • the processing module is used to determine the first identifier; the transceiver module is used to send the first identifier to the user plane network element.
  • the first identifier is the identifier in the visited public land mobile network VPLMN corresponding to the terminal, and the terminal roams into the VPLMN.
  • the transceiver module is used to send the first identification to the edge application service function.
  • the processing module is configured to determine the first identifier during the establishment of a protocol data unit PDU session of the terminal.
  • the terminal's PDU session is the terminal's home routing HR PDU session.
  • the processing module is used to determine the second identifier; the transceiver module is used to send the second identifier to the user plane network element.
  • the transceiver module is used for the edge application service function to send the second identification.
  • the transceiving module may also include a sending module and a receiving module.
  • the sending module is used to implement the sending function of the communication device described in the eighth aspect
  • the receiving module is used to implement the receiving function of the communication device described in the eighth aspect.
  • the communication device may further include a storage module that stores programs or instructions.
  • the processing module executes the program or instruction, the communication device can perform the communication method described in the third aspect.
  • the communication device described in the eighth aspect may be a network device, such as a session management network element, or may be a chip (system) or other components or components that can be installed in the network device, or may include a network device. device, this application does not limit this.
  • a communication device in a ninth aspect, includes: a transceiver module and a processing module.
  • the transceiver module is used to receive the first domain name system DNS query message from the terminal, and the processing module is used to replace the source address of the first DNS query message from the address of the terminal to the first address to obtain the second DNS query message, thereby
  • the transceiver module is controlled to send a second DNS query message to the edge application service function.
  • the terminal roams to the visited public land mobile network VPLMN, and the first DNS query message is used to query the address of the application service, and the first address is the address allocated by the VPLMN to the terminal.
  • the first address may specifically be a VPLMN, such as a network element within the VPLMN, an identifier assigned to the protocol data unit PDU session of the terminal, or the first address may be mapped to the PDU session of the terminal.
  • VPLMN such as a network element within the VPLMN, an identifier assigned to the protocol data unit PDU session of the terminal, or the first address may be mapped to the PDU session of the terminal.
  • the transceiver module is configured to receive a first domain name system DNS query message from the terminal through a PDU session of the terminal.
  • the terminal's PDU session can be the terminal's home routing HR PDU session.
  • the communication device described in the ninth aspect is configured with a first user plane processing rule, and the first user plane processing rule indicates that: for the first DNS query message, the device converts the first DNS query message into The source address is replaced with the first address by the terminal's address to obtain a second DNS query message, and the second DNS query message is sent to the edge application service function.
  • the transceiver module is used to send a second DNS query to the edge application service function. After the message, a first DNS response message from the edge application service function is received, where the first DNS response message carries the address of the application service.
  • the processing module is configured to replace the destination address of the first DNS response message from the first address to the address of the terminal to obtain the second DNS response message, thereby controlling the sending and receiving of the second DNS response message to the terminal.
  • the communication device is configured with a second user plane processing rule, and the second user plane processing rule indicates that: for the first DNS response message, the device changes the destination address of the first DNS response message to the first DNS response message. An address is replaced with the address of the terminal to obtain a second DNS response message, and the second DNS response message is sent to the edge application service function.
  • the transceiver module is configured to receive a third DNS query message from the edge application service function after sending the second DNS query message to the edge application service function.
  • the processing module is used to replace the destination address of the third DNS query message from the second address to the address of the DNS server in the HPLMN to obtain the fourth DNS query message, thereby controlling the transceiver module to send the fourth DNS query message to the HPLMN.
  • the second address is an address assigned by the VPLMN to the terminal.
  • the second address may be an identifier assigned by the VPLMN to the terminal's protocol data unit PDU session, or the second address may be mapped to the terminal's PDU session, that is, the user plane network element may map the terminal's message to the terminal based on the second address.
  • the second address and the first address may be different.
  • the communication device is configured with a third user plane processing rule, and the third user plane processing rule indicates that: for the third DNS query message, the device changes the destination address of the third DNS query message to The second address is replaced with the address of the DNS server in the HPLMN to obtain the fourth DNS query message, and the fourth DNS query message is sent to the edge application service function.
  • the processing module is configured to determine the first address for the user plane network element before the transceiver module receives the first DNS message from the terminal, and control the transceiver module to send the first address to the session management network element.
  • the transceiving module is configured to receive the first address from the session management network element.
  • the processing module is configured to determine the second address before the transceiver module receives the first DNS message from the terminal, and control the transceiver module to send the second address to the session management network element.
  • the transceiver module is configured to receive the second address from the session management network element.
  • the transceiving module may also include a sending module and a receiving module.
  • the sending module is used to implement the sending function of the communication device described in the ninth aspect
  • the receiving module is used to implement the receiving function of the communication device described in the ninth aspect.
  • the communication device may further include a storage module that stores programs or instructions.
  • the processing module executes the program or instruction, the communication device can perform the communication method described in the fourth aspect.
  • the communication device described in the ninth aspect may be a network device, such as a user plane network element, or may be a chip (system) or other component or component that can be disposed in the network device, or may include a network device. device, this application does not limit this.
  • a communication device in a tenth aspect, includes: transceiver module and processing module.
  • the processing module is used to determine the first address, and the transceiving module is used to send the first address to the edge application service function.
  • the first address is the address assigned to the terminal by the visiting public land mobile network VPLMN, and the terminal roams into the VPLMN.
  • the transceiver module is used to send the first address to the user plane network element.
  • the processing module is used in the protocol data unit PDU session establishment process of the terminal. , determine the first address.
  • the terminal's PDU session is the terminal's home routing HR PDU session.
  • the processing module is used to determine the second address, and the transceiver module is used to send the second address to the edge application service function.
  • the second address is an address assigned by the VPLMN to the terminal, and the second address is different from the first address.
  • the transceiver module is configured to send the second address to the user plane network element.
  • the processing module is used to determine the second address during the establishment of a PDU session of the terminal.
  • the PDU session of the terminal is the HR PDU session of the terminal.
  • the transceiver module may also include a sending module and a receiving module.
  • the sending module is used to implement the sending function of the communication device described in the tenth aspect
  • the receiving module is used to implement the receiving function of the communication device described in the tenth aspect.
  • the communication device may further include a storage module that stores programs or instructions.
  • the processing module executes the program or instruction, the communication device can perform the communication method described in the fifth aspect.
  • the communication device described in the tenth aspect may be a network device, such as a session management network element, or may be a chip (system) or other components or components that can be installed in the network device, or may include a network device. device, this application does not limit this.
  • a communication device in an eleventh aspect, includes: a processor configured to execute the communication method described in any one of the possible implementations of the first to fifth aspects.
  • the communication device described in the eleventh aspect may further include a transceiver.
  • the transceiver can be a transceiver circuit or an interface circuit.
  • the transceiver can be used for the communication device described in the seventh aspect to communicate with other communication devices.
  • the communication device described in the eleventh aspect may further include a memory.
  • This memory can be integrated with the processor or provided separately.
  • the memory may be used to store computer programs and/or data involved in the communication method described in any one of the first to fifth aspects.
  • the communication device described in the eleventh aspect may be the device described in any one of the first to fifth aspects, or a chip (system) or other components or components that may be disposed in the device, or a device containing such device.
  • a communication device in a twelfth aspect, includes: a processor, the processor is coupled to a memory, and the processor is used to execute a computer program stored in the memory, so that the communication device executes any one of the possible implementation methods of the first to fifth aspects. communication method.
  • the communication device described in the twelfth aspect may further include a transceiver.
  • the transceiver can be a transceiver circuit or an interface circuit.
  • the transceiver can be used for the communication device described in the twelfth aspect to communicate with other communication devices.
  • the communication device described in the twelfth aspect may be the device described in any one of the first to fifth aspects, or a chip (system) or other components or components that may be disposed in the device, or a device containing such device.
  • a communication device including: a processor and a memory; the memory is used to store a computer program, and when the processor executes the computer program, the communication device executes the first to fifth aspects.
  • the communication device described in the thirteenth aspect may further include a transceiver.
  • the transceiver can be a transceiver circuit or an interface circuit.
  • the transceiver can be used for the communication device described in the thirteenth aspect to communicate with other communication devices.
  • the communication device described in the thirteenth aspect may be the device described in any one of the first to fifth aspects, or a chip (system) or other components or components that may be disposed in the device, or a device containing such device.
  • a communication device including: a processor; the processor is configured to be coupled to a memory, and after reading the computer program in the memory, execute the steps in the first to fifth aspects according to the computer program. Any communication method described in the implementation method.
  • the communication device described in the fourteenth aspect may further include a transceiver.
  • the transceiver can be a transceiver circuit or an interface circuit.
  • the transceiver can be used for the communication device described in the fourteenth aspect to communicate with other communication devices.
  • the communication device described in the fourteenth aspect may be the device described in any one of the first to fifth aspects, or a chip (system) or other components or components that may be disposed in the device, or a device containing such device.
  • a communication system includes: the user plane network element described in the first aspect, the edge application service function described in the second aspect, and the session management network element described in the third aspect; or, the communication system includes: the fourth aspect The user plane network element described in the fifth aspect, and the session management network element described in the fifth aspect.
  • a computer-readable storage medium including: a computer program or instructions; when the computer program or instructions are run on a computer, the computer is caused to execute any one of the possible methods of the first to fifth aspects. Implement the communication method described in the manner.
  • a computer program product including a computer program or instructions.
  • the computer program or instructions When the computer program or instructions are run on a computer, the computer is caused to execute any one of the possible implementation methods of the first to fifth aspects. the communication method described above.
  • Figure 1 is a schematic diagram of the non-roaming architecture of 5GS
  • Figure 2 is a schematic diagram of the architecture of edge computing
  • Figure 3 is a schematic process diagram of edge computing service discovery
  • Figure 4 is a schematic diagram of the roaming architecture of 5GS
  • Figure 5 is a schematic diagram of the architecture of edge computing in the 5GS roaming architecture
  • Figure 6 is an architectural schematic diagram of a communication system provided by an embodiment of the present application.
  • Figure 7 is a schematic flowchart 1 of a communication method provided by an embodiment of the present application.
  • Figure 8 is a schematic diagram of an application scenario of a communication method provided by an embodiment of the present application.
  • Figure 9 is a schematic flow chart 2 of a communication method provided by an embodiment of the present application.
  • Figure 10 is a schematic flow chart 3 of a communication method provided by an embodiment of the present application.
  • Figure 11 is a schematic diagram 2 of an application scenario of a communication method provided by an embodiment of the present application.
  • Figure 12 is a schematic flow chart 4 of a communication method provided by an embodiment of the present application.
  • Figure 13 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • Figure 14 is a schematic structural diagram 2 of a communication device provided by an embodiment of the present application.
  • Figure 15 is a schematic structural diagram three of a communication device provided by an embodiment of the present application.
  • 5G system 5G system, 5GS
  • FIG. 1 is a schematic diagram of the non-roaming architecture of 5GS.
  • 5GS includes: access network (AN) and core network (core network, CN), and can also include: terminals.
  • the above-mentioned terminal may be a terminal with a transceiver function, or a chip or chip system that can be installed on the terminal.
  • the terminal can also be called user equipment (UE), access terminal, subscriber unit (subscriber unit), user station, mobile station (MS), mobile station, remote station, remote terminal, mobile device, User terminal, terminal, wireless communication device, user agent or user device.
  • UE user equipment
  • MS subscriber unit
  • MS mobile station
  • remote station remote terminal
  • mobile device User terminal, terminal, wireless communication device, user agent or user device.
  • the terminal in the embodiment of the present application may be a mobile phone (mobile phone), cellular phone (cellular phone), smart phone (smart phone), tablet computer (Pad), wireless data card, personal digital assistant computer (personal digital assistant, PDA) ), wireless modems, handheld devices, laptop computers, machine type communication (MTC) terminals, computers with wireless transceiver functions, virtual reality (VR) Terminals, augmented reality (AR) terminals, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical, smart grids Wireless terminals in grid, wireless terminals in transportation safety, wireless terminals in smart city, wireless terminals in smart home, vehicle-mounted terminals, roadside units with terminal functions (road side unit, RSU) etc.
  • the terminal of this application may also be a vehicle-mounted module, vehicle-mounted module, vehicle-mounted component, vehicle-mounted chip, or vehicle-mounted unit built into the vehicle as one or more components or units.
  • the above-mentioned AN is used to implement access-related functions. It can provide network access functions for authorized users in specific areas, and can determine transmission links of different qualities to transmit user data according to user levels, business needs, etc.
  • the AN forwards control signals and user data between the terminal and the CN.
  • AN may include: access network equipment, which may also be called radio access network equipment (radio access network, RAN) equipment.
  • RAN radio access network equipment
  • CN is mainly responsible for maintaining mobile network subscription data and providing terminals with functions such as session management, mobility management, policy management, and security authentication.
  • CN mainly includes the following network elements: user plane function (UPF) network element, authentication server function (AUSF) network element, access and mobility management function (AMF) network element Element, session management function (SMF) network element, network slice selection function (NSSF) network element, network exposure function (NEF) network element, network function repository function (NF repository) function, NRF) network element, policy control function (policy control) function (PCF) network element, unified data management (UDM) network element, unified data repository (UDR), and application function (AF).
  • UPF user plane function
  • AUSF authentication server function
  • AMF access and mobility management function
  • SMF session management function
  • NSSF network slice selection function
  • NEF network exposure function
  • NRF network exposure function
  • PCF policy control function
  • UDM unified data management
  • UDR unified data repository
  • AF application function
  • the UE accesses the 5G network through RAN equipment.
  • the UE communicates with the AMF network element through the N1 interface (referred to as N1); the RAN network element communicates with the AMF network element through the N2 interface (referred to as N2); the RAN network element communicates with the AMF network element through the N3 interface.
  • the interface, referred to as N3, communicates with the UPF network element; SMF communicates with the UPF network element through the N4 interface (referred to as N4), and the UPF network element accesses the data network (DN) through the N6 interface (referred to as N6).
  • control plane functions such as AUSF network element, AMF network element, SMF network element, NSSF network element, NEF network element, NRF network element, PCF network element, UDM network element, UDR network element or AF shown in Figure 1 adopt services interface to interact.
  • the external service interface provided by the AUSF network element is Nausf; the external service interface provided by the AMF network element is Namf; the external service interface provided by the SMF network element is Nsmf; the external service interface provided by the NSSF is Nnssf; the NEF network
  • the external service interface provided by the NRF network element is Nnef; the external service interface provided by the NRF network element is Nnrf; the external service interface provided by the PCF network element is Npcf; the external service interface provided by the UDM network element is Nudm; the external service interface provided by the UDR network element is Nudm;
  • the service-oriented interface provided is Nudr; the service-oriented interface provided by AF to the outside world is Naf.
  • network elements such as NSSF network elements, AUSF network elements, UDM network elements, UE, RAN network elements, PCF network elements, and SMF network elements can also communicate with AMF network elements.
  • AUSF network elements can also communicate with UDM network elements, and UDM can also communicate with SMF network elements.
  • SMF network elements can also communicate with UPF network elements and PCF network elements.
  • PCF network elements can also communicate with AF and NEF network elements.
  • NEF network elements can also communicate with AF.
  • UPF network elements can communicate with RAN equipment and DN.
  • "Nxx" between two network elements indicates the interface between the two network elements.
  • N22 represents the interface between NSSF network element and AMF network element
  • N12 represents the interface between AUSF network element and AMF network element
  • N8 represents the interface between UDM network element and AMF network element. We will not list them one by one here. List etc.
  • RAN equipment may be equipment that provides access to terminals.
  • RAN equipment may include: next-generation mobile communication systems, such as 6G access network equipment, such as 6G base stations, or in the next-generation mobile communication system, the network equipment may also have other naming methods, which are all covered by this application Within the protection scope of the embodiments, this application does not impose any limitations on this.
  • the RAN equipment may also include 5G, such as gNB in the new radio (NR) system, or one or a group (including multiple antenna panels) antenna panels of the base station in 5G, or may also be composed of gNB, transmission point (transmission and reception point, TRP or transmission point, TP) or transmission measurement function (TMF) network node, such as baseband unit (building base band unit, BBU), or centralized unit (centralized unit (CU) or distributed unit (DU), RSU with base station function, or wired access gateway, or 5G core network element.
  • 5G such as gNB in the new radio (NR) system, or one or a group (including multiple antenna panels) antenna panels of the base station in 5G, or may also be composed of gNB, transmission point (transmission and reception point, TRP or transmission point, TP) or transmission measurement function (TMF) network node, such as baseband unit (building base band unit, BBU), or centralized unit (centralized unit (CU) or distributed unit (DU), RSU with base station function, or
  • RAN equipment can also include access points (APs) in wireless fidelity (WiFi) systems, wireless relay nodes, wireless backhaul nodes, various forms of macro base stations, micro base stations (also (called small stations), relay stations, access points, wearable devices, vehicle-mounted devices, etc.
  • APs access points
  • WiFi wireless fidelity
  • wireless relay nodes wireless backhaul nodes
  • various forms of macro base stations such as, but not limited to, WiFi
  • micro base stations also (called small stations)
  • relay stations such as access points, wearable devices, vehicle-mounted devices, etc.
  • the UPF network element is mainly responsible for user data processing (forwarding, receiving, accounting, etc.).
  • the UPF network element can receive user data from the data network (DN) and forward the user data to the terminal through the access network device.
  • the UPF network element can also receive user data from the terminal through the access network equipment and forward the user data to the DN.
  • DN network element refers to the operator network that provides data transmission services to users. For example, Internet protocol (IP), multimedia service (IP multi-media service, IMS), Internet, etc.
  • IP Internet protocol
  • multimedia service IP multi-media service
  • IMS Internet multi-media service
  • the DN can be an operator's external network or a network controlled by the operator, used to provide business services to terminal devices.
  • the AUSF network element is mainly used to perform terminal security authentication.
  • AMF network elements are mainly used for mobility management in mobile networks. For example, user location update, user registration network, user switching, etc.
  • SMF network elements are mainly used for session management in mobile networks. For example, session establishment, modification, and release. Specific functions include assigning Internet Protocol (IP) addresses to users, selecting UPF network elements that provide data packet forwarding functions, etc.
  • IP Internet Protocol
  • the PCF network element mainly supports providing a unified policy framework to control network behavior, provides policy rules to the control layer network functions, and is also responsible for obtaining user subscription information related to policy decisions.
  • PCF network elements can provide policies to AMF network elements and SMF network elements, such as quality of service (QoS) policies, slice selection policies, etc.
  • QoS quality of service
  • NSSF network elements are mainly used to select network slices for terminals.
  • NEF network elements are mainly used to support the opening of capabilities and events.
  • UDM network elements are mainly used to store user data, such as contract data, authentication/authorization data, etc.
  • UDR network elements are mainly used to store structured data.
  • the stored content includes contract data and policy data, externally exposed structured data and application-related data.
  • AF mainly supports interaction with CN to provide services, such as affecting data routing decisions, policy control functions, or providing some third-party services to the network side.
  • Edge computing is a new network architecture that is used to optimize the user's resource access process by deploying computing resources at the edge of the network close to the user, such as reducing the network transmission delay between the user and the computing resource.
  • 5GS also introduces edge computing.
  • the edge application server (EAS) is usually deployed in the local part of the DN (LDN), which can also be called the edge part of the DN.
  • LDN local part of the DN
  • the edge part also belongs to this DN, but the edge part may be located close to the UE.
  • Each LDN can be identified by a corresponding data network access identifier (DNAI). If the UE wants to obtain edge services, it usually needs to first obtain the IP address of the corresponding EAS through the edge computing service discovery process. In this way, the operator network can select the UPF network element that is far away from the LDN based on the IP address of the EAS to establish a transmission path for the UE to ensure that the UE can access the EAS of the LDN and obtain edge services.
  • FIG. 3 shows the edge computing service discovery process defined by TS23.548. As shown in Figure 3, the process includes:
  • the UE initiates the PDU session establishment process.
  • the UE After the UE is registered, it can request the SMF network element to establish a PDU session for it.
  • the SMF network element For details, please refer to the relevant introduction of PDU sessions in TS23.502, which will not be described again.
  • the SMF network element selects the edge application server discovery function (EASDF).
  • EASDF edge application server discovery function
  • the SMF network element can select an EASDF for the UE's PDU session, and the selected EASDF can be used as the domain name system (DNS) corresponding to the PDU session for subsequent use by the UE in discovering the EAS.
  • DNS domain name system
  • the SMF network element sends a DNS context creation request (Neasdf_DNSContext_Create Request) message to EASDF.
  • EASDF receives the DNS context creation request message from the SMF network element.
  • the DNS context creation request message can be used to request EASDF to create the DNS context corresponding to the PDU session.
  • the DNS context creation request message may include: the UE's IP address, the UE's PDU session identifier, and DNS message processing rules.
  • DNS message processing rules include: DNS handling rule identity, DNS message detection template (optional), and actions (action(s)).
  • the IP address of the UE may be the IP address assigned to the UE by the HPLMN.
  • the DNS message detection template may include at least one of the following: DNS message type (DNS message type) is DNS query or DNS response (DNS response). If the DNS message type is DNS query, EASDF needs to check the source IP address (UE’s IP address) ) and full qualified domain name (FQDN) range array (optional). If the DNS message type is DNS response, EASDF needs to view the FQDN range array and/or EAS IP address range array (optional). For ease of understanding, the "FQDN” mentioned below is usually understood as the "FQDN of the edge service” unless otherwise specified.
  • the operation may include at least one of the following: reporting action, forwarding action, or control action.
  • the reporting operation means that EASDF can report the content of the DNS message to the SMF network element. For example, if the UE's IP address and FQDN are available, the EASDF may report the FQDN in the DNS query message to the SMF network element (see 308). For another example, if the IP address and FQDN provided by the DNS server are available, the EASDF may report the FQDN and the IP address in the DNS response message to the SMF (see S314).
  • the reporting operation means that EASDF can send DNS messages to the DNS server.
  • EASDF can construct the DNS extended mechanism (extended-DNS, EDNS) client subnet option (EDNS client subnet option, ECS option) in the DNS message, and then send the DNS message to the DNS server (see S312).
  • the control operation may include at least one of the following: EASDF caches the DNS message, EASDF sends the cached DNS response message to the UE, or EASDF discards the cached DNS response message.
  • EASDF sends a DNS context creation response (Neasdf_DNSContext_Create Response) message to the SMF network element.
  • the SMF network element receives the DNS context creation response message from EASDF.
  • the DNS context creation response message can be used to indicate that EASDF has created a DNS context.
  • the SMF network element can create a DNS context corresponding to the PDU session of the UE according to the DNS context creation request message, and store the IP address of the UE and the DNS message processing rules into the DNS context.
  • the SMF network element sends a DNS context update request (Neasdf_DNSContext_Update Request) message to EASDF.
  • EASDF receives the DNS context creation update message from the SMF network element.
  • EASDF sends a DNS context update response (Neasdf_DNSContext_Update Response) message to the SMF network element.
  • the SMF network element receives the DNS context update response message from EASDF.
  • the DNS context update request message can be used to request EASDF to update the DNS context.
  • EASDF update DNS context can be triggered by the mobility of the UE, such as the UE moving to a new location.
  • the DNS context update response message is a response message to the DNS context update request message and can be used to indicate that EASDF has received the DNS context update request message.
  • S305-S306 are similar to the above-mentioned S303-S304, which can be understood by reference and will not be described again. S305-S306 are optional steps, and the SMF network element does not need to update the DNS context.
  • S307 The UE sends a DNS query message to EASDF.
  • EASDF receives the DNS query message from the UE.
  • DNS query messages can be used to query the IP address of the EAS.
  • the DNS query message may carry the FQDN corresponding to the edge service that the UE wants to obtain, and is used to query the IP address of the EAS corresponding to the edge service through the FQDN.
  • the UE is pre-configured with the IP address of EASDF. At this time, if the UE wants to obtain the edge service, the UE can send a DNS query message to the EASDF according to the IP address of the EASDF.
  • EASDF For EASDF, if the DNS query message matches the DNS message detection template in the DNS message processing rule, EASDF executes S308. For example, EASDF can obtain the UE's IP address and FQDN from the DNS query message, and determine whether the UE's IP address and FQDN are available based on the DNS message processing rules. At this point, if the DNS query If the IP address of the UE in the message is the same as the IP address of the UE in the DNS context, and the IFQDN in the DNS query message is the same as the FQDN in the DNS context, it means that the IP address and FQDN of the UE are available, that is, DNS query message and DNS message detection Template matching.
  • EASDF sends a DNS context notification request (Neasdf_DNSContext_Notify Request) message to the SMF network element.
  • the SMF network element receives the DNS context notification request message from EASDF.
  • the DNS context notification request message may be used to request the SMF network element to provide information for EAS addressing.
  • the DNS context notification request message may carry the above-mentioned FQDN to request the SMF network element to provide information for EAS addressing through the FQDN.
  • the SMF network element sends a DNS context notification response (Neasdf_DNSContext_Notify Response) message to EASDF.
  • EASDF receives the DNS context notification response message from the SMF network element.
  • the DNS context notification response message may be a response message to the DNS context notification request message, and is used to indicate that the SMF network element has received the DNS context notification request message.
  • S310 The SMF network element sends a DNS context update request message to EASDF.
  • EASDF receives the DNS context creation update message from the SMF network element.
  • the DNS context update request message is used to request updates to DNS message processing rules.
  • the DNS context update request message can carry new DNS message processing rules, and the new DNS message processing rules can carry ECS option information to represent an IP address that can reflect the area where the UE is located. That is to say, the SMF network element can provide EASDF with information for EAS addressing by updating DNS message processing rules.
  • EASDF sends a DNS context update response message to the SMF network element.
  • the SMF network element receives the DNS context update response message from EASDF.
  • the DNS context update response message is a response message to the DNS context update request message and can be used to indicate that EASDF has received the DNS context update request message.
  • EASDF sends a DNS query message to the DNS server.
  • the DNS server receives DNS query messages from EASDF.
  • DNS query messages can be used to request the DNS server to provide the IP address of the EAS.
  • the DNS query message may carry ECS options (including ECS option information) to request the DNS server to provide the IP address of the EAS through the ECS options.
  • EASDF can obtain the ECS option information from the DNS context update request message and use the ECS option information to generate ECS options according to the DNS message processing rules.
  • EASDF can encapsulate ECS options into DNS query messages to obtain DNS query messages.
  • the DNS server sends a DNS response message to EASDF.
  • EASDF receives DNS response messages from DNS servers.
  • the DNS response message can carry the FQDN and the IP address of the EAS.
  • the DNS server can determine the area where the UE is located based on the ECS option in the DNS query message.
  • the DNS server can determine an EAS located in the area where the UE is located, or the EAS closest to the area where the UE is located, and thereby obtain the IP address of the EAS.
  • S308-S313 are optional steps. If the IP address of the UE is available, S308-S313 will be executed. Otherwise, S308-S313 will not be executed.
  • EASDF sends a DNS context notification request message to SMF.
  • the SMF network element receives the DNS context notification request message from EASDF.
  • the DNS context notification request message can be used to request the SMF network element to establish data plane transmission between the UE and the EAS. path.
  • the DNS context notification request message can carry the FQDN and the IP address of the EAS, so that the SMF network element can establish a data plane transmission path between the UE and the EAS based on the IP address of the EAS.
  • the DNS response message matches the DNS message detection template of the DNS message processing rule in the DNS context, EASDF sends a DNS context notification request message to the SMF.
  • matching the DNS response message with the DNS message detection template may mean that the FQDN and the IP address of the EAS in the DNS response message are the same as the FQDN and the IP address of the EAS in the DNS message detection template.
  • EASDF sends a DNS context notification response message to SMF.
  • the SMF network element receives the DNS context notification response message from EASDF.
  • the DNS context notification response message may be a response message to the DNS context notification request message, and is used to indicate that the SMF network element has received the DNS context notification request message.
  • the SMF network element sends a DNS context update request message to EASDF.
  • EASDF receives the DNS context creation update message from the SMF network element.
  • the DNS context update request message is used to indicate that the data plane transmission path between the UE and the EAS has been established.
  • the DNS context update request message may carry an information element, which is used to indicate that the data plane transmission path between the UE and the EAS has been established.
  • EASDF sends a DNS context update response message to the SMF network element.
  • the SMF network element receives the DNS context update response message from EASDF.
  • the DNS context update response message is a response message to the DNS context update request message and can be used to indicate that EASDF has received the DNS context update request message.
  • EASDF sends a DNS response message to the UE.
  • the UE receives the DNS response message from the EASDF.
  • the DNS response message may be used to indicate the IP address of the EAS.
  • the DNS response message may carry the FQDN and the IP address of the EAS.
  • the FQDN in the DNS response message is the same as the FQDN requested by the UE (see S307).
  • the UE can learn that the IP address of the EAS in the DNS response message is the IP address of the EAS corresponding to the edge service requested by the UE according to the FQDN in the DNS response message.
  • the IP address of the UE is usually a private IP address assigned to the UE by the UE's home public land mobile network (HPLMN). Private IP addresses of different private networks may conflict. To avoid this problem, operators can properly deploy EASDF to ensure that the IP addresses of UEs connected to the same EASDF do not overlap, thereby ensuring that EASDF can distinguish DNS query messages from different UEs based on the UE's IP address.
  • HPLMN home public land mobile network
  • FIG 4 is a schematic diagram of the roaming architecture of 5GS, such as the 5G network in the home routed (HR) roaming scenario.
  • the 5G network includes HPLMN and VPLMN.
  • HPLMN is the home network of the UE, also called the home network.
  • the visited public land mobile network (VPLMN) is the roaming network of the UE, also known as the roaming network.
  • VPLMN and HPLMN communicate through vSEPP and hSEPP.
  • the service needs to be carried in HPLMN, that is, the DN is in HPLMN.
  • the UE accesses the 5G network through the RAN device, and the UE communicates with the AMF network element through the N1 interface (referred to as N1); the RAN device communicates with the AMF network element through the N2 interface (referred to as N2); the RAN device It communicates with the UPF network element through the N3 interface (referred to as N3); the SMF network element communicates with the UPF network element through the N4 interface (referred to as N4).
  • N1 interface referred to as N1
  • N2 interface referred to as N2
  • N3 the SMF network element
  • N4 interface referred to as N4 interface
  • Network element communication In HPLMN, the UPF network element accesses the DN through the N6 interface (referred to as N6); the UPF network element communicates with the SMF network element through the N4 interface (referred to as N4).
  • control plane functions such as the NSSF network element, NEF network element, AMF network element, SMF network element, NRF network element, or PCF network element of the VPLMN shown in Figure 4 use service-based interfaces for interaction.
  • the external service interface provided by the AMF network element is Namf; the external service interface provided by the SMF network element is Nsmf; the external service interface provided by the NSSF network element is Nnssf; the external service interface provided by the NEF network element is Nnef; The external service interface provided by the NRF network element is Nnrf; the external service interface provided by the PCF network element is Npcf.
  • HPLMN such as UDM network element, AUSF network element, PCF network element, NRF network element, NSSF network element, AF, or NEF network element shown in Figure 4 also use service-oriented interfaces for interaction.
  • the service-oriented interface provided by the AUSF network element to the outside world is Nausf
  • the service-oriented interface provided by the UDM network element to the outside world is Nudm
  • the service-oriented interface provided by the AF to the outside world is Naf.
  • “Nxx” between the two network elements shown in Figure 4 indicates the interface between the two network elements, and specific examples will not be given one by one.
  • the UE can trigger the V-SMF network element to establish a home routing protocol data unit (protocol data unit) session (HR PDU session), that is, the PDU session in which the UE connects to the H-UPF network element through the V-UPF network element.
  • HR PDU session home routing protocol data unit
  • the DN's data can be forwarded to the UE through the H-UPF network element and the V-UPF network element in sequence, or the UE's data can be forwarded to the DN through the V-UPF network element and the H-UPF network element in sequence.
  • the V-SMF network element can establish a local offload point (such as the V-UPF network element) in the VPLMN for the HR PDU session and use edge services.
  • the UE can send a DNS query message to V-EASDF through the V-UPF network element. If the DNS query message matches the DNS message detection template in the DNS message processing rule, the V-EASDF can obtain the IP address of the EAS located in the VPLMN from the DNS server through the V-SMF network element.
  • V-EASDF can send a DNS response message to the UE through the V-UPF network element, so that the UE can access the EAS according to the DNS response message, thereby obtaining edge services located in the VPLMN.
  • the specific implementation principle of Figure 5 can also be referred to the relevant introduction in Figure 3 above, and will not be described again.
  • the private IP address allocated by HPLMN to UE may be the same as the IP address of a UE in VPLMN (denoted as UE2).
  • UE1 roams to When using this VPLMN, the addresses of UE1 and UE2 may conflict, resulting in UE1 being unable to obtain edge services.
  • V-EASDF may not be able to distinguish whether the DNS query message comes from UE1 or UE2, resulting in the inability to correctly match the DNS context and the inability to provide the correct IP address of the EAS to UE1, resulting in UE1 being unable to obtain edge services.
  • the DNS response message returned by V-EASDF may be sent to UE2 through the anchor UPF network element of UE2 and cannot be correctly routed back to UE1, which also results in UE1 being unable to obtain edge services.
  • the UE initiating the access may be located in a different network, such as VPLMN or HPLMN, EASDF may not be able to identify and process it, causing the process to fail and the UE to be unable to obtain edge services.
  • V-EASDF may choose to send a DNS query message to the H-DNS server (the DNS server corresponding to the HR PDU session)/H-EASDF through the V-UPF network element.
  • the DNS query message may not carry ECS options related to the edge service, so it can be called a non-EC DNS query message.
  • the V-UPF network element recognizes the non-EC DNS query message and cannot forward the non-EC DNS query message to the H-DNS server. interest. That is to say, in the roaming scenario, UE1 cannot access the H-DNS server and cannot obtain corresponding application services.
  • edge computing services can support roaming terminal access, but how to route data from roaming terminals is an issue worth considering. Therefore, embodiments of this application propose the following technical solutions to solve the problem of data routing of roaming terminals in edge computing.
  • WiFi wireless fidelity
  • V2X vehicle to everything
  • D2D device-to-device
  • 4G fourth generation mobile communication systems, such as long term evolution (LTE) systems, global interoperability for microwave access (WiMAX) communication systems
  • 5G such as new radio (NR) system
  • future communication systems such as WiFi, WiFi, WiMAX, 5G, such as new radio (NR) system, and future communication systems.
  • WiFi wireless fidelity
  • V2X vehicle to everything
  • D2D device-to-device
  • 4G fourth generation
  • LTE long term evolution
  • WiMAX global interoperability for microwave access
  • 5G such as new radio (NR) system
  • NR new radio
  • FIG. 6 is an architectural schematic diagram of a communication system to which the communication method provided by the embodiment of the present application is applicable.
  • this communication system can be applied to the HR roaming scenario of the above-mentioned 5G system, and mainly includes at least one of the following: UE, V-UPF network element, V-EASDF, V-SMF network element, H-UPF network element , H-SMF network element, LDN, H-DNS server.
  • a UE may refer to a UE that roams to a VPLMN, and the home public land mobile network of the UE is the HPLMN.
  • the UE mentioned below can also be understood similarly unless otherwise introduced.
  • the VPLMN can additionally identify the UE to distinguish other UEs that have IP address conflicts with the UE and ensure that the UE can obtain corresponding edge services. For example, in one possible scenario, the VPLMN can allocate an identifier to the UE to additionally identify the UE through the identifier, so that in the event of an IP address conflict, V-EASDF can still identify the UE and correctly handle the DNS of the UE. Query messages to achieve correct data routing so that UE can obtain edge services. Or, in another possible scenario, the V-UPF network element can use the address assigned by the VPLMN to identify the UE's DNS query message to avoid address conflicts and achieve correct data routing so that the UE can obtain the edge. Serve.
  • the VPLMN can also configure processing rules for non-EC DNS query messages for the V-UPF network element, so that the V-UPF network element can forward non-EC DNS query messages to the H-DNS server or H-EASDF. DNS query message, so that the UE can access the H-DNS server to obtain corresponding application services.
  • the communication method provided by the embodiment of the present application can be applied to the above-mentioned communication system, and is specifically applied to various scenarios mentioned in the above-mentioned communication system, which will be introduced in detail below.
  • FIG. 7 is a schematic flowchart 1 of the communication method provided by the embodiment of the present application.
  • This communication method is suitable for interactions between terminals, user plane network elements, and edge application service functions.
  • the terminal may be a UE in the above communication system
  • the user plane network element may be specifically a V-UPF network element in the above communication system
  • the edge application service function may be specifically a V-EASDF in the above communication system.
  • the VPLMN may allocate a first identity to the terminal to additionally identify the terminal through the first identity.
  • the user plane network element receives the first DNS query message from the terminal.
  • the terminal roams into the VPLMN.
  • the first DNS query message is used to query the address of the application service.
  • the first DNS query message carries the FQDN of the application service.
  • the first DNS query message carries the IP address of the terminal in the HPLMN.
  • a PDU session is pre-established between the user plane network element and the terminal, such as the HR PDU session of the terminal.
  • the user plane network element can receive the first DNS query message through the PDU session.
  • the user plane network element sends the first DNS query message and the first identifier to the edge application service function.
  • the edge application service function receives the first DNS query message and the first identification from the user plane network element.
  • the first identifier may be an identifier assigned by the VPLMN to the terminal, and is used to identify the terminal within the VPLMN. Specifically, the first identifier may be an identifier assigned by the VPLMN to the terminal's PDU session, or the first identifier may be mapped to the terminal's PDU session in the VPLMN. For example, VPLMN can establish a communication tunnel between the user plane network element and the edge application service function for the terminal, or for the PDU session of the terminal.
  • the communication tunnel can be a communication tunnel corresponding to any of the following tunnel protocols, such as general packet radio system (GPRS) tunneling protocol (GPRS tunneling protocol, GTP), or general routing encapsulation protocol (generic routing encapsulation, GRE) ), or any other possible communication tunnel.
  • GPRS general packet radio system
  • GTP general packet radio system tunneling protocol
  • GRE general routing encapsulation protocol
  • the first identifier can be the identifier of the communication tunnel, specifically the endpoint identifier of the communication tunnel at the edge application service function. That is, the first identifier can be implemented by reusing existing cells to reduce the difficulty of implementation. .
  • the first identifier may be a tunnel endpoint identifier (tunnel endpoint identifier, TEID) or a fully qualified tunnel endpoint identifier (F-TEID).
  • the first identifier may be a sequence number.
  • the first identifier can also be any other possible identifier, or a newly defined identifier, without limitation.
  • the first identifier may also be used by the edge application service function to determine whether there is a DNS rule matching the first identifier. Specifically, S703 may be performed, which will not be described again.
  • the first identifier may be allocated by a network element within the VPLMN, such as a user plane network element, a session management network element or an edge Application service functions.
  • the first identifier may be determined by a user plane network element.
  • the user plane network element can determine the first identifier and send the first identifier to the session management network element, so that the network element of the VPLMN, such as the edge application service function, can obtain the first identifier from the session management network element, and thereby use the first identifier according to the first identifier. Identify the terminal's messages and implement correct data routing.
  • the user plane network element can determine the first identifier by itself, or determine the first identifier according to instructions from the session management network element, without limitation.
  • the first identifier may be determined by the session management network element. For example, during the process of creating a PDU session of the terminal, the session management network element may determine the first identifier and send the first identifier to the user plane network element. And, optionally, the session management network element may also send the first identification to the edge application service function. In this way, the user plane network element can receive the first identifier from the session management network element, so that when sending the terminal's message, the first identifier can be sent at the same time, so that the edge application service function can identify the terminal's message according to the first identifier, achieving Correct data routing.
  • the first identification may be determined by the edge application service function.
  • the edge application service function can determine the first identifier and send the first identifier to the session management network element, so that the user plane network element can obtain the first identifier from the session management network element, so that it can send the terminal's message at the same time.
  • the first identifier is so that the edge application service function can identify the terminal's message based on the first identifier and implement correct data routing.
  • the edge application service function can determine the first identifier by itself, or determine the first identifier according to instructions from the session management network element, without limitation.
  • the user plane network element may send the first DNS query message and the first identifier to the edge application service function by default or according to the first user plane processing rule, such as sending the first DNS query message and the first identifier to the edge application service function through a communication tunnel.
  • the first user plane processing rule may be pre-configured or provided by the session management network element in advance.
  • the session management network element provides the first user plane processing rule to the user plane network element through the PDU session establishment process.
  • the first user plane processing rule may correspond to the PDU session of the terminal, or the first user plane processing rule may be mapped to the PDU session of the terminal, so that the user plane network element identifies and processes signaling related to the PDU session of the terminal. .
  • the first user plane processing rule may indicate that: for the first DNS query message, the user plane network element sends the first DNS query message and the first identifier to the edge application service function.
  • the first user plane processing rule may indicate: for the first DNS query message from the terminal, the user plane network element sends the first DNS query message and the first identifier to the edge application service function through the communication tunnel. In this way, the user plane network element can process the first DNS query message according to the configured first user plane processing rule, thereby avoiding misoperation or misprocessing of the user plane network element.
  • the first user plane processing rule may not be limited to the first DNS query message, but may also be applicable to the DNS query message from the terminal.
  • the first user plane processing rule may indicate that: for a DNS query message from the terminal, the user plane network element sends the DNS query message and the first identifier to the edge application service function.
  • the first DNS query message is one of the DNS query messages from the terminal.
  • the way in which the user plane network element sends the first DNS query message and the first identifier may be different when the communication tunnel is established or when the communication tunnel is not established.
  • the user plane network element can reuse the first DNS query message and send the first DNS query message and the first identifier.
  • the user plane network element may carry the first identifier in the first DNS query message, such as in a reserved field of the first DNS query message, and then send the first DNS query message to the edge application service function.
  • the user plane network element may encapsulate the first DNS query message and the first identifier into a tunnel message, and then send the tunnel message to the edge application service function.
  • user plane network elements can be in the first The outer layer of the DNS query message encapsulates a header carrying the first identifier, that is, the header of the communication tunnel, to obtain the tunnel message.
  • the tunnel header is a GTP-formatted tunnel header.
  • the tunnel header is a GRE-formatted tunnel header.
  • the outer tunnel header can allow the tunnel message to directly pass through the entity/function between the user plane network element and the edge application service function, or the entity between the user plane network element and the edge application service function. / function directly transparently transmits the tunnel message, which realizes so-called tunnel transmission. It can be understood that since the first identifier is carried in the header of the communication tunnel, the edge application service function can identify that the received information element is the first identifier through the communication tunnel.
  • the edge application service determines whether there is a DNS message processing rule matching the first DNS query message and the first identifier.
  • the DNS message processing rule may include FQDN.
  • the DNS message detection template of the DNS message processing rule may include the FQDN.
  • the DNS message processing rules may be carried in a DNS context, and the DNS context may also include the first identifier.
  • the DNS context can be pre-configured on the edge application service; or the edge application service can obtain the DNS context from the session management network element in advance, or generate the DNS context in advance based on the information provided by the session management network element.
  • the existence of a DNS message processing rule matching the first DNS query message and the first identifier may mean: there is a DNS context matching the first identifier, and there is a DNS message processing rule matching the first DNS query message in the DNS context. Similarly, the absence of a DNS message processing rule matching the first DNS query message and the first identifier may mean: there is a DNS context matching the first identifier, but there is no DNS matching the first DNS query message in the DNS context. Message processing rules.
  • the edge application service function may determine, based on the first identifier, whether there is a DNS context matching the first identifier, such as a DNS context containing the first identifier. If there is no DNS context matching the first identifier, it means that the identity of the terminal cannot be determined, and the process ends. If there is a DNS context matching the first identification, the edge application service function may determine whether there is a DNS message processing rule matching the first DNS query message in the DNS context. At this time, if the FQDN in the first DNS query message matches the FQDN in a DNS message processing rule in the DNS context, it means that there is a DNS message processing rule matching the first DNS query message. However, if the FQDN in the first DNS query message does not match the FQDN in any DNS message processing rule in the DNS context, it means that there is no DNS message processing rule matching the first DNS query message.
  • a DNS context matching the first identifier such as a DNS context containing the first identifier. If there is no DNS context matching the first identifier, it
  • the communication method may also include: in the case where there is a DNS message processing rule matching the first DNS query message and the first identification, the edge application service function reports the network to the user The element sends a first DNS response message and a second identification.
  • the user plane network element receives the first DNS response message and the second identification from the edge application service function, and sends the first DNS response message to the terminal according to the second identification.
  • the first DNS response message may be a response message to the first DNS query message.
  • the first DNS response message may carry an address of an application service, such as an address of an edge application service, so that the terminal can obtain the edge service.
  • the second identifier may be an identifier assigned by the VPLMN to the terminal, and is used to identify the terminal within the VPLMN.
  • the second identifier may be an identifier assigned by the VPLMN to the terminal's PDU session.
  • the second identifier may be mapped to the terminal's PDU session in the VPLMN. That is, the user plane network element may, based on the second identifier, transfer the terminal's message (such as the first DNS response message) is mapped to the PDU session of the terminal, thereby sending the first DNS response message to the terminal so that the terminal can obtain application services, such as edge services. For details, see below and will not be described again.
  • the second logo is the same as the first
  • the logos may be the same, or they may be different, without limitation.
  • the second identifier may also be the identifier of the communication tunnel, specifically, it may be the endpoint identifier of the communication tunnel at the user plane network element. That is, the second identifier may be implemented by reusing existing information elements to reduce implementation difficulty.
  • the second identifier can also be any other possible identifier, or a newly defined identifier, without limitation.
  • the determination method of the second identification is similar to the above-mentioned first identification, which can be understood by reference and will not be described again.
  • the edge application service function since the FQDN carried in the first DNS query message matches the FQDN in the above DNS message processing rule, it means that the address of the application service requested by the terminal is the address of the edge application service. At this time, the edge application service function may provide the terminal with the address of the edge application service through the first DNS response message. The edge application service function may send the first DNS response message and the second identifier to the user plane network element by default or according to the above DNS message processing rules, such as sending the first DNS response message and the second identifier to the user plane network element through a communication tunnel.
  • the DNS message processing rules may include DNS message detection templates and operations.
  • the DNS message detection template may include: FQDN, which may be used to match the FQDN carried in the first DNS query message.
  • the operation may instruct: the edge application service function sends the first DNS response message and the second identification to the user plane network element. Specifically, it may instruct: the edge application service function sends the first DNS response message and the second identification to the user plane network element through the communication tunnel. logo. That is to say, if the FQDN carried in the first DNS query message matches the FQDN in the DNS message detection template, that is, the DNS message detection template matches the DNS message detection template. At this time, the edge application service function can send the first DNS response message and the second identification to the user plane network element according to the operation instructions.
  • the DNS message processing rules may not be limited to the first DNS query message and the first DNS response message, but may also be applicable to DNS query messages from the user plane network element and DNS query messages sent to the user plane network element.
  • the DNS message detection template includes: FQDN, which can be used to match the FQDN carried in the DNS query message from the user plane network element.
  • the operation may instruct: the edge application service function sends the DNS response message and the second identification to the user plane network element.
  • the first DNS query message is one of the DNS query messages from the terminal
  • the first DNS response message is one of the DNS query messages sent to the user plane network element.
  • the specific implementation of DNS message processing rules can also refer to the relevant introduction in S303 above, and will not be described again.
  • the specific implementation of the edge application service function sending the first DNS response message and the second identifier is similar to the above-mentioned user plane network element sending the first DNS query message and the first identifier, which can be understood by reference and will not be described again.
  • the user plane network element can identify that the received information element is the second identifier through the communication tunnel.
  • the user plane network element After receiving the first DNS response message and the second identifier, the user plane network element can determine based on the second identifier that the first DNS response message is the message corresponding to the terminal, or the PDU of the terminal. The message corresponding to the session. Therefore, the user plane network element sends the first DNS response message to the terminal, for example, sending the first DNS response message to the terminal through the PDU session of the terminal.
  • the user plane network element may be configured with a second user plane processing rule.
  • the configuration method of the second user plane processing rules is similar to the above-mentioned first user plane processing rules and can be understood by reference and will not be described again.
  • the second user plane processing rule may indicate: for the first DNS response message and the second identification, the user plane network element sends the first DNS response message to the terminal.
  • the second user plane processing rule may specifically indicate that: for the first DNS response message and the second identification in the communication tunnel, the user plane network element sends the first DNS response message to the terminal.
  • the user plane network element can execute the above processing logic for the first DNS response message according to the configured second user plane processing rule, thereby avoiding misoperation or mishandling of the user plane network element.
  • the user plane network element does not configure the second user plane processing rule, the user plane network element can process the first DNS response message according to the above processing logic by default.
  • the second user plane processing rule may not be limited to the first DNS response message, but may also be applicable to the DNS response message from the edge application service function.
  • the second user plane processing rule may indicate that: for the DNS response message and the second identification from the edge application service function, the user plane network element sends the DNS response message to the terminal.
  • the first DNS response message is one of the DNS response messages from the edge application service function.
  • the communication method may also include: in the case where there is no DNS message processing rule matching the first DNS query message and the first identification, the edge application service function sends a message to the user plane.
  • the network element sends the second DNS query message and the second identifier.
  • the user plane network element receives the second DNS query message and the second identifier from the edge application service function, and sends a third DNS query message to the HPLMN based on the second DNS query message and the second identifier.
  • the second DNS query message can be used to request the addresses of other application services, so that the terminal can finally obtain the corresponding application services.
  • the second identifier please refer to the relevant introduction in the above-mentioned first possible design solution, and will not be described again.
  • the edge application service function can send the second DNS query message and the second identifier to the HPLMN of the terminal through the user plane network element.
  • edge application service function sending the second DNS query message and the second identifier is similar to the above-mentioned edge application service function sending the first DNS response message and the second identifier, which can be understood by reference and will not be described again.
  • the third DNS query message can also be used to request the addresses of other application services.
  • the third DNS query message may be a message determined by the user plane network element based on the second DNS query message. For example, after receiving the second DNS query message and the second identifier, the user plane network element can determine based on the second identifier that the second DNS query message is a message corresponding to the terminal, or a message corresponding to the PDU session of the terminal. Therefore, the user plane network element can replace the source address of the second DNS query message from the address of the edge application service function to the address of the terminal to obtain the third DNS query message, and map the third DNS query message to the PDU of the terminal. session, thereby sending a third DNS query message to the HPLMN of the terminal so that the terminal can obtain the corresponding application service.
  • the user plane network element can be configured with a third user plane processing rule.
  • the configuration method of the third user plane processing rules is similar to the above-mentioned first user plane processing rules, which can be understood by reference and will not be described again.
  • the third user plane processing rule may indicate: for the second DNS query message and the second identification, the user plane network element sends the third DNS query message to the HPLMN; specifically, it may indicate: for the second DNS query message and the second identity in the communication tunnel identification, the user plane network element sends a third DNS query message to HPLMN.
  • the user plane network element can execute the above processing logic for the second DNS query message according to the configured third user plane processing rule, thereby avoiding misoperation or mishandling of the user plane network element.
  • the user plane network element can process the second DNS query message according to the above processing logic by default.
  • the third user plane processing rules may not be limited to the second DNS query message and the third DNS query message, but may also be applicable to DNS query messages from the edge application service function and DNS query messages sent to the HPLMN.
  • the third user plane processing rule may indicate that: for the DNS query message and the second identification from the edge application service function, the user plane network element sends a DNS query message to the HPLMN.
  • the second DNS query message is one of the DNS query messages from the edge application service function
  • the third DNS query message is one of the DNS query messages sent to the HPLMN.
  • the communication method may also include: the user plane network element receives the The second DNS response message of the DNS server in the HPLMN; the user plane network element sends the third DNS response message and the first identifier to the edge application service function according to the second DNS response message; the edge application service function receives the second DNS response message from the user plane network element.
  • the edge application service function sends the fourth DNS response message and the second identifier to the user plane network element according to the third DNS response message and the first identifier;
  • the user plane network element receives the message from the edge application service The fourth DNS response message and the second identifier of the function; the user plane network element sends the fourth DNS response message to the terminal according to the second identifier.
  • the second DNS response message may be a response message to the third DNS query message.
  • the second DNS response message may carry addresses of other application services for the terminal to obtain corresponding application services.
  • the third DNS response message may be a response message to the second DNS query message.
  • the third DNS response message may be determined based on the second DNS response message.
  • the user plane network element may receive the second DNS response message through the PDU session of the terminal.
  • the user plane network element can determine to replace the destination address of the second DNS response message from the address of the terminal to the address of the edge application service function to obtain the third DNS response message, and then sends a third DNS response message and the first identifier to the edge application service function, for example, sending the third DNS response message and the first identifier to the edge application service function through a communication tunnel.
  • the user plane network element may be configured with a fourth user plane processing rule.
  • the configuration method of the fourth user plane processing rules is similar to that of the first user plane processing rules and can be understood by reference without going into details.
  • the fourth user plane processing rule may indicate: for the second DNS response message, the user plane network element sends the third DNS response message and the first identifier to the edge application service function; specifically, it may indicate: for the second DNS response message, the user plane network The element sends the third DNS response message and the first identification to the edge application service function through the communication tunnel.
  • the user plane network element can execute the above processing logic for the second DNS response message according to the configured fourth user plane processing rule, thereby avoiding misoperation or mishandling of the user plane network element.
  • the user plane network element can process the second DNS response message according to the above processing logic by default.
  • the fourth user plane processing rule may not be limited to the second DNS response message and the third DNS response message, and may also be applicable to the DNS response message from the DNS server in the HPLMN, as well as the DNS response message sent to the edge application service function.
  • the fourth user plane processing rule may indicate: a DNS response message from the DNS server in the HPLMN, a DNS response message and the first identifier sent by the user plane network element to the edge application service function.
  • the second DNS response message is one of the DNS response messages from the DNS server in the HPLMN
  • the third DNS response message is one of the DNS response messages sent to the edge application service function.
  • the specific implementation of the user plane network element sending the third DNS response message and the first identifier is similar to the above user plane network element sending the first DNS response message and the first identifier, which can be understood by reference and will not be described again.
  • the fourth DNS response message may be a response message to the first DNS query message.
  • the fourth DNS response message may be determined based on the third DNS response message. For example, after receiving the third DNS response message, the edge application service function can replace the destination address of the third DNS response message from the address of the edge application service function to the terminal according to the matching of the third DNS response message with the corresponding DNS message processing rule. address to get the fourth DNS response message. In this way, the edge application service function can send the fourth DNS response message and the second identifier to the user plane network element according to the DNS message processing rule, such as sending the fourth DNS response message and the second identifier to the user plane network element through the communication tunnel.
  • edge application service function sending the fourth DNS response message and the second identifier is similar to the above-mentioned edge application service function sending the first DNS response message and the second identifier, which can be understood by reference and will not be described again.
  • the processing of the fourth DNS response message by the user plane network element is similar to the above-mentioned first DNS response message. It can be understood by reference and will not be repeated. narrate.
  • the edge application service function user plane network element can additionally identify the terminal through the first identifier allocated by the VPLMN, or it can be understood that the edge application service function can determine that the first DNS query message corresponds to the terminal through the first identifier, so that the address In the case of possible conflicts, the edge application service function can still identify the terminal, thereby correctly processing the DNS query message of the terminal, ensuring correct data routing, so that the terminal can obtain application services, such as edge services.
  • FIG. 8 is a schematic architectural diagram of Embodiment 1 in a specific scenario.
  • This scenario involves UE, V-UPF network element, V-SMF network element, V-EASDF, and H-DNS server.
  • the UE may be the terminal in the above method
  • the V-UPF network element may be the user plane network element in the above method
  • the V-SMF network element may be the session management network element in the above method
  • the V-EASDF may be the user plane network element in the above method.
  • the edge application service function and H-DNS server can be the above-mentioned DNS server in HPLMN.
  • the IP address of the UE is IP address 1
  • IP address 1 is also the address assigned by HPLMN to the UE.
  • the IP address of V-EASDF is IP address 2.
  • the IP address of the H-DNS server is IP address 3.
  • VPLMN can establish a communication tunnel between V-UPF and V-EASDF for the UE's HR PDU session, that is, the communication tunnel corresponds to the UE's HR PDU session.
  • the TID1 of the communication tunnel and the TID2 of the communication tunnel can be used to identify the UE, or the TID1 of the communication tunnel and the TID2 of the communication tunnel can also be replaced with other identifiers that may be used to identify the UE in the VPLMN, without limitation.
  • the TID1 of the communication tunnel and the TID2 of the communication tunnel can be saved in the DNS context corresponding to the HR PDU session.
  • the UPF processing rules can include: 1) For the DNS query message from the UE, the V-UPF network element sends it to V-EASDF through the communication tunnel.
  • the DNS query message and the TID1 of the communication tunnel 2) For the DNS response message received in the communication tunnel and the TID2 of the communication tunnel, the V-UPF network element sends the DNS response message to the UE; 3) For the DNS response message received in the communication tunnel DNS query message and TID2 of the communication tunnel, the V-UPF network element sends the DNS query message to the H-DNS server; 4) For the DNS response message from the H-DNS server, the V-UPF network element sends it to the V-EASDF through the communication tunnel DNS response message and TID1 of the communication tunnel.
  • the behavior of V-EASDF is mainly dictated by DNS message processing rules: DNS message detection templates and operations.
  • the DNS message detection template includes: FQDN, which can be used to match the FQDN in the DNS query message from the UE.
  • the operation can be used to instruct: V-EASDF sends a DNS response message and the TID2 of the communication tunnel to the V-UPF network element through the communication tunnel.
  • FIG. 9 is a schematic flowchart 2 of the communication method provided by the embodiment of the present application. This communication method is suitable for the scenario shown in Figure 8. As shown in Figure 9, a specific example process is provided for the embodiment shown in Figure 7. The details of the communication method are as follows:
  • the H-SMF network element sends a PDU session creation response (Nsmf_PDUSession_Create Response) message to the V-SMF network element.
  • the V-SMF network element receives the PDU session creation response message from the H-SMF network element.
  • the PDU session creation response message may be a response message of the PDU session creation request (Nsmf_PDUSession_Create Request) message.
  • the PDU session creation request message can be used by the V-SMF network element to request the H-SMF network element to provide creation Information required for the UE's HR PDU session. Accordingly, the PDU session creation response message can be used to provide the information required to create the HR PDU session of the UE.
  • the PDU session creation response message may carry IP address 1, and IP address 3 of the H-DNS server.
  • the V-SMF network element sends an N4 session modification request (N4Sseesion Modification Request) message to the V-UPF network element.
  • N4Sseesion Modification Request N4Sseesion Modification Request
  • the V-UPF network element receives the N4 session modification request message from the V-SMF network element.
  • the N4 session modification request message may carry the first indication information.
  • the first indication information may be used to instruct the V-UPF network element to allocate TID1 of the communication tunnel and/or TID2 of the communication tunnel for the HR PDU session of the UE.
  • the N4 session modification request message may not carry the first indication information.
  • the V-UPF network element receives the N4 session modification request message, the V-UPF network element allocates the TID1 and/or communication tunnel of the communication tunnel to the UE's HR PDU session by default. TID2.
  • the TID1 of the communication tunnel can refer to the relevant introduction of the above-mentioned first identifier.
  • the embodiment of the present application takes the TID1 of the communication tunnel as an example.
  • the TID1 of the communication tunnel in the embodiment of the present application can be replaced. as the first identifier. That is, when the first identifier is information in other forms other than TID1 of the communication tunnel, similar processing is performed.
  • the TID 2 of the communication tunnel please refer to the related introduction of the second identifier mentioned above.
  • the embodiment of the present application takes the TID2 of the communication tunnel as an example.
  • the TID2 of the communication tunnel in the embodiment of the present application can be replaced by the second identifier. logo. That is, when the second identifier is information in other forms other than TID2 of the communication tunnel, similar processing is performed.
  • the V-UPF network element allocates TID1 of the communication tunnel and/or TID2 of the communication tunnel to the HR PDU session of the UE.
  • the V-UPF network element sends an N4 session modification response (N4Sseesion Modification Response) message to the V-SMF network element.
  • N4Sseesion Modification Response N4Sseesion Modification Response
  • the V-SMF network element receives the N4 session modification response message from the V-UPF network element.
  • the N4 session modification request message may carry the TID1 of the communication tunnel and/or the TID2 of the communication tunnel.
  • steps S902-S904 are optional steps.
  • the TID1 of the communication tunnel and/or the TID2 of the communication tunnel may be determined by the V-SMF network element itself. In this case, S902-S904 may not be executed.
  • the TID1 of the communication tunnel and/or the TID2 of the communication tunnel can be determined by V-EASDF.
  • V-EASDF sends the generated communication tunnel TID to the V-SMF network element, or the V-SMF network element instructs V-EASDF to determine TID1 of the communication tunnel and/or TID2 of the communication tunnel.
  • V-EASDF can provide the TID1 of the communication tunnel and/or the TID2 of the communication tunnel to the V-UPF network element through the V-SMF network element.
  • S902-S904 can also refer to the relevant introduction in S702 above, which will not be described again.
  • V-SMF network element sends a DNS context creation request message to V-EASDF.
  • V-EASDF receives the DNS context creation request message from the V-SMF network element.
  • the DNS context creation request message can be used to request EASDF to create the DNS context corresponding to the UE's HR PDU session.
  • the DNS context creation request message may include at least one of the following: IP address 1, IP address 3, TID1 of the communication tunnel, TID2 of the communication tunnel, or DNS message processing rules.
  • IP address 1, IP address 3, TID1 of the communication tunnel, TID2 of the communication tunnel, or DNS message processing rules For the specific implementation of DNS message processing rules, please refer to Figure 8 and the relevant introduction in S303 above, and will not be described again.
  • DNS message processing rules can be pre-configured or protocols pre-defined on V-EASDF.
  • the DNS context creation request message may carry at least one of the following: IP address 1, IP address 3, TID1 of the communication tunnel, or TID2 of the communication tunnel, without carrying DNS message processing rules.
  • information such as IP address 1, IP address 3, TID1 of the communication tunnel, or TID2 of the communication tunnel can be used to trigger V-EASDF to activate local DNS message processing rules.
  • the DNS context creation request message can also carry an additional information element, which can be used to trigger V-EASDF to activate local DNS message processing rules.
  • DNS message processing rules can be determined by V-EASDF Determine it yourself based on some necessary parameters.
  • the DNS context creation request message can only carry these necessary parameters, such as including at least one of the following: IP address 1 (the address assigned by HPLMN to the UE), IP address 3 (the IP address assigned by HPLMN to the H-DNS server) ), TID1 of the communication tunnel, or TID2 of the communication tunnel, etc.
  • V-EASDF can create a request message based on the DNS context, create a DNS context corresponding to the UE's HR PDU session, and store at least one of the following: IP address 1, TID1 of the communication tunnel, TID2 of the communication tunnel, and DNS message processing rules. into that DNS context.
  • V-SMF network element sends the N4 rule to the V-UPF network element.
  • the V-UPF network element receives the N4 rule from the V-SMF network element.
  • N4 rules can be carried in the N4 session, such as the N4 session modification response message.
  • the N4 session corresponds to the UE's HR PDU session.
  • the N4 rule may include at least one of the following: IP address 1, IP address 2, IP address 3, TID1 of the communication tunnel, TID2 of the communication tunnel, and UPF processing rules.
  • IP address 1, IP address 2, IP address 3, TID1 of the communication tunnel, TID2 of the communication tunnel, and UPF processing rules For the specific implementation of UPF processing rules, please refer to the relevant introduction in Figure 8 above, and will not be described again.
  • UPF processing rules can also refer to the relevant introduction of the user plane processing rules mentioned above.
  • the embodiment of the present application takes the UPF processing rule as an example to illustrate. Those skilled in the art can understand that the UPF processing rules in the embodiment of the present application can be replaced by user plane processing rules. . That is to say, when the user plane processing rules are information in other forms other than UPF processing rules, similar processing is performed.
  • N4 rules carrying UPF processing rules are an optional implementation method.
  • UPF processing rules can be pre-configured or the protocol can be pre-defined on the V-UPF network element.
  • the N4 rule can carry at least one of the following: IP address 1, IP address 2, IP address 3, TID1 of the communication tunnel, or TID2 of the communication tunnel, without carrying the UPF processing rule.
  • information such as IP address 1, IP address 2, IP address 3, TID1 of the communication tunnel, or TID2 of the communication tunnel can be used to trigger the V-UPF network element to activate local UPF processing rules.
  • the N4 rule can also carry an additional information element, which can be used to trigger the V-UPF network element to activate local UPF processing rules.
  • the DNS message processing rules can be determined by the V-UPF network element itself based on some necessary parameters.
  • the N4 rule can only carry these necessary parameters, such as at least one of the following: IP address 1, IP address 2, IP address 3, TID1 of the communication tunnel, or TID2 of the communication tunnel, etc.
  • the V-UPF network element obtains the UPF processing rules through the UE's HR PDU session corresponding to the N4 session, this acquisition method can implicitly indicate that the UPF processing rules correspond to the HR PDU session, so that the V-UPF network element can According to the UPF processing rules, the corresponding messages (such as DNS response message #1 and DNS query message #3 mentioned below) are mapped to the HR PDU session to send these messages through the HR PDU session.
  • the UPF processing rules can also directly define that these messages need to be mapped to the HR PDU session.
  • UPF processing rule is only an exemplary naming, which can also be replaced by any possible naming, such as UPF behavior, UPF operation, UPF operation rule, etc., which is not specifically limited.
  • execution order between S906 and S905 is not limited.
  • S901-S906 are steps in the HR PDU session creation process in the HR scenario, that is, the embodiments of this application are applicable to this process.
  • the embodiments of this application are applicable to this process.
  • TSXXXX please refer to TSXXX, which will not be described again.
  • S907 The UE sends DNS query message #1 to the V-UPF network element.
  • the V-UPF network element receives the DNS query message #1 from the UE.
  • DNS query message #1 can be used to request application services, for example, DNS query message #1 carries There is the FQDN of the application service.
  • the source address of DNS query message #1 is IP address 1
  • the destination address of DNS query message #1 is IP address 2 or IP address 3.
  • the UE is pre-configured with IP address 2 and/or IP address 3.
  • the V-SMF network element can provide IP address 2 and/or IP address 3 to the UE through the H-SMF network element.
  • DNS query message #1 may also contain other parameters.
  • S307 please refer to the relevant introduction in S307 above.
  • S907 please refer to the relevant introduction in S701 above, which will not be described again.
  • V-UPF network element sends the DNS query message #1 and the TID1 of the communication tunnel to the V-EASDF through the communication tunnel.
  • V-EASDF receives the DNS query message #1 from the V-UPF network element and the TID1 of the communication tunnel through the communication tunnel.
  • the V-UPF network element After receiving the DNS query message #1, the V-UPF network element can send the DNS query message #1 and the TID1 of the communication tunnel to the V-EASDF through the communication tunnel according to the UPF processing rules.
  • V-EASDF determines whether there is a DNS message processing rule matching the DNS query message #1 and the TID1 of the communication tunnel.
  • V-EASDF can match the DNS context that stores the TID1 of the communication tunnel according to the TID1 of the communication tunnel of the DNS query message #1. At this time, V-EASDF can determine whether there is a DNS message processing rule matching DNS query message #1 in the DNS context.
  • DNS query message #1 matches the FQDN of the DNS message processing rule, that is, DNS query message #1 matches the DNS message detection template, it indicates DNS Query message #1 is used to request the application service to be an edge service, or DNS query message #1 is used to request a certain EAS to provide services, or to query a certain EAS, thereby triggering the execution of S910-S911 to provide edge services for the UE.
  • DNS query message #1 is used to request the application service to be an edge service, or DNS query message #1 is used to request a certain EAS to provide services, or to query a certain EAS, thereby triggering the execution of S910-S911 to provide edge services for the UE.
  • the FQDN in the DNS query message #1 does not match the FQDN in the DNS message processing rule, that is, the DNS query message #1 and the DNS If the message detection template does not match, it means that the application service requested by DNS query message #1 is not an edge application service, but other application services, or that DNS query message #1 is used to request the H-DNS server to provide the address of other application services.
  • V-EASDF can trigger execution of S912-S916 to provide corresponding application services for the UE.
  • S909 can also refer to the relevant introduction in S703 above, and will not be described again.
  • V-EASDF sends DNS response message #1 and TID2 of the communication tunnel to the V-UPF network element through the communication tunnel.
  • the V-UPF network element receives the DNS response message #1 from V-EASDF and the TID2 of the communication tunnel through the communication tunnel.
  • DNS response message #1 may be used in response to DNS query message #1.
  • DNS response message #1 may carry the IP address of the EAS queried by DNS query message #1.
  • the source address of DNS response message #1 is IP address 2, and the destination address is IP address 1.
  • V-EASDF can obtain the IP address of the EAS by interacting with the V-SMF network element and the DNS server.
  • S308-S318 please refer to the relevant introduction of S308-S318 above, which will not be described again.
  • V-EASDF can encapsulate the IP address of the EAS corresponding to the edge service into DNS response message #1 according to the instructions of the operation in the DNS message processing rule, and send DNS response message #1 and
  • TID2 of the communication tunnel please refer to the relevant introduction in S703 above, and will not be described again.
  • the V-UPF network element sends DNS response message #1 to the UE.
  • the UE receives DNS response message #1 from the V-UPF network element.
  • the V-UPF network element After receiving the DNS response message #1 and the TID2 of the communication tunnel, the V-UPF network element can determine that the communication tunnel The DNS response message #1 corresponding to TID2 is mapped to the HR PDU session of the UE, so that the DNS response message #1 is sent to the UE through the HR PDU session. For example, the V-UPF network element can replace the source address in DNS response message #1 from IP address 2 to IP address 3, and then send the DNS response message #1 to the UE. In this way, the UE can obtain the IP address of the EAS from the DNS response message #1, and then access the EAS according to the IP address of the EAS to obtain the corresponding edge service.
  • the V-UPF network element can also execute the processing logic in S911 according to the UPF processing rules without limitation.
  • S910-S911 can also refer to the relevant introduction in the first possible design solution mentioned above, and will not be described again.
  • V-EASDF sends DNS query message #2 and TID2 of the communication tunnel to the V-UPF network element through the communication tunnel.
  • the V-UPF network element receives the DNS query message #2 from V-EASDF and the TID2 of the communication tunnel through the communication tunnel.
  • DNS query message #2 can be used to request the IP address of other application services.
  • the source address of DNS query message #2 is IP address 2, and the destination address is IP address 3. That is to say, in the case of determining the IP address requesting other application services, V-EASDF can replace the source address of DNS query message #1 from IP address 1 to IP address 2, and change the destination address of DNS query message #1 Replace IP address 2 with IP address 3 to get DNS query message #2.
  • V-EASDF can also directly generate DNS query message #2. Thereafter, V-EASDF can send DNS query message #2 and TID2 of the communication tunnel to the V-UPF network element through the communication tunnel.
  • V-EASDF sending DNS query message #2 and TID2 of the communication tunnel to the V-UPF network element through the communication tunnel, please refer to the relevant introduction in S908 and S910 above, and will not be described again.
  • the V-UPF network element sends DNS query message #3 to the H-DNS server.
  • the H-DNS server receives DNS query message #3 from the V-UPF network element.
  • DNS query message #3 can be used to request the H-DNS server to provide services.
  • the source address of DNS query message #3 is IP address 1, and the destination address is IP address 3. That is to say, after receiving the DNS query message #2 and the TID2 of the communication tunnel, the V-UPF network element can determine to map the DNS query message #2 corresponding to the TID2 of the communication tunnel to the HR PDU session of the UE. For example, the V-UPF network element can replace the source address of DNS query message #2 from IP address 2 to IP address 1 to obtain DNS query message #3, or directly generate DNS query message #3 and then send DNS query message #3 Map to the HR PDU session of the UE to send DNS query message #3 to the H-DNS server through the HR PDU session (i.e. through the H-UPF network element (not shown in Figure 8)).
  • the V-UPF network element can also execute the processing logic in S912 according to the UPF processing rules without limitation.
  • S912-S913 can also refer to the relevant introduction in the second possible design solution mentioned above, and will not be described again.
  • the H-DNS server sends DNS response message #2 to the V-UPF network element through the H-UPF network element.
  • the V-UPF network element receives the DNS response message #2 from the H-DNS server through the H-UPF network element.
  • DNS response message #2 may be a response message to DNS query message #3.
  • DNS response message #2 may carry the IP address of other application services.
  • the source address of DNS response message #2 is IP address 3, and the destination address is IP address 1.
  • V-UPF network element sends the DNS response message #3 and the TID1 of the communication tunnel to the V-EASDF through the communication tunnel.
  • V-EASDF receives the DNS response message #3 from the V-UPF network element and the TID1 of the communication tunnel through the communication tunnel.
  • DNS response message #3 may be a response message to DNS query message #2.
  • DNS response message #3 may carry the IP address of other application services.
  • the source address of DNS response message #3 is IP address 3, and the destination address is IP address 2. That is to say, for the DNS response message #2 from the H-DNS server, the V-UPF network element can determine to send the DNS response message #3 and the TID1 of the communication tunnel to the V-EASDF.
  • the V-UPF network element can replace the destination address of DNS response message #2 from IP address 1 to IP address 2 to obtain DNS response message #3, or directly generate DNS response message #3 and then send it to V through the communication tunnel.
  • -EASDF sends DNS response message #3 and TID1 of the communication tunnel.
  • the V-UPF network element can also execute the processing logic in S915 according to the UPF processing rules without limitation.
  • the specific implementation of S915 can refer to the relevant introduction in S703 above, and will not be described again.
  • V-EASDF sends DNS response message #4 and TID1 of the communication tunnel to the V-UPF network element through the communication tunnel.
  • the V-UPF network element receives the DNS response message #4 from V-EASDF and the TID1 of the communication tunnel through the communication tunnel.
  • DNS response message #4 may be a response message to DNS query message #1.
  • DNS response message #4 may carry the IP address of other application services.
  • the source address of DNS response message #4 is IP address 2, and the destination address is IP address 1. That is to say, after V-EASDF receives the DNS response message #3, it can match the DNS response message #3 to the corresponding DNS message processing rule. In this way, V-EASDF can replace the source address of DNS response message #3 from IP address 3 to IP address 2 according to the DNS message processing rules matched by DNS response message #3, and change the destination address of DNS response message #3 from IP address 2 is replaced with IP address 1 to get DNS response message #4.
  • V-EASDF can directly generate DNS response message #4 based on the DNS message processing rules matched by the DNS response message #3. Thereafter, V-EASDF may send the DNS response message #4 and the communication tunnel TID2 to the V-UPF network element through the communication tunnel according to the DNS message processing rules matched by the DNS response message #3.
  • V-EASDF sends DNS response message #4 to the V-UPF network element.
  • the V-UPF network element accepts DNS response message #4 from V-EASDF.
  • the V-UPF network element's processing logic for DNS response message #4 is similar to the above-mentioned DNS response message #1, which can be understood by reference and will not be described again.
  • S914-S917 can also refer to the relevant introduction in the third possible design solution mentioned above, and will not be described again.
  • V-UPF network element and V-EASDF as an example, but it is not limited to this.
  • V-UPF network element can also be replaced with other V-UPF network element
  • V-EASDF can also be replaced. for other V-EASDF.
  • the UE can be identified not only by the IP address assigned by HPLMN, but also by the TID1 of the communication tunnel assigned by VPLMN, in the case of possible IP address conflicts, the UE can still be identified by the TID1 of the communication tunnel. Identification is performed so that roaming UEs can obtain edge services. Furthermore, the VPLMN can configure UPF processing rules for non-EC DNS query messages for the V-UPF network element to ensure that the V-UPF network element can forward non-EC DNS query messages to the H-DNS server so that the roaming UE can also Corresponding application services can be obtained.
  • FIG. 10 is a schematic flowchart 3 of the communication method provided by the embodiment of the present application.
  • This communication method is suitable for interactions between terminals, user plane network elements, and edge application service functions.
  • the terminal may be a UE in the above communication system
  • the user plane network element may be specifically a V-UPF network element in the above communication system
  • the edge application service function may be specifically a V-EASDF in the above communication system.
  • the VPLMN can allocate a first address to the terminal to avoid address conflicts.
  • the user plane network element receives the first DNS query message from the terminal.
  • S1001 can refer to the relevant introduction in S701 above, and will not be described again.
  • the user plane network element replaces the source address of the first DNS query message from the terminal address to the first address to obtain the second DNS query message, and sends the second DNS query message to the edge application service function.
  • the address of the terminal may be an address assigned by HPLMN to the terminal, for example, it may be an IP address or any other possible address, without limitation.
  • the first address may be an address assigned by the VPLMN to the terminal, specifically, it may be an address assigned by the VPLMN to the terminal's PDU session, or the first address may be mapped to the terminal's PDU session in the VPLMN, for example, the first address may point to the terminal.
  • the first address may be determined by a network element within the VPLMN, such as a user plane network element, session management network element or edge application service function within the VPLMN.
  • the first address may be an IP address, such as an IPv4 address or an IPv6 address, or it may be any other possible address.
  • the first address may be determined by the user plane network element.
  • the user plane network element can determine the first address and send the first address to the session management network element, so that the network element of the VPLMN, such as the edge application service function, can obtain the first address from the session management network element, so as to obtain the first address according to the first address. Identify the terminal's messages and implement correct data routing.
  • the user plane network element can determine the first address by itself, or determine the first address according to the instructions of the session management network element, without limitation.
  • the first address may be determined by the session management network element.
  • the session management network element may determine the first address and send the first address to the user plane network element.
  • the session management network element may also send the first address to the edge application service function.
  • the user plane network element can receive the first address from the session management network element, so that it can carry the first address when sending the terminal's message, so that the edge application service function can identify the terminal's message based on the first address and achieve correct data routing. .
  • the first address may be determined by the edge application service function.
  • the edge application service function can determine the first address and send the first address to the session management network element, so that the user plane network element can obtain the first address from the session management network element, so that it can carry the first address when sending the terminal's message. address, so that the edge application service function can identify the terminal's message based on the first address and achieve correct data routing.
  • the edge application service function can determine the first address by itself, or determine the first address according to the instructions of the session management network element, without limitation.
  • the user plane network element When the user plane network element receives the first DNS query message, such as receiving the first DNS query message through the PDU session of the terminal, it can be based on whether the first DNS query message is from the terminal, or according to the source address of the first DNS query message is that of the terminal. address, and determine to send the second DNS query message to the edge application service function. For example, the user plane network element can replace the source address of the first DNS query message from the terminal's address to the first address to obtain the second DNS query message, and send the second DNS query message to the edge application service function.
  • the user plane network element may be configured with a first user plane processing rule.
  • the first user plane processing rule may indicate that: for the first DNS query message, the user plane network element replaces the source address of the first DNS query message from the terminal's address to the first address to obtain the second DNS query message, and sends the first DNS query message to the first DNS query message.
  • the edge application service function sends a second DNS query message; specifically, it can be indicated that: for the first DNS query message, if the destination address of the first DNS query message is the address of the edge application service function or the address of the DNS server in the HPLMN, then the user faces the network The source address of the first DNS query message is replaced by the terminal address with the first address to obtain the second DNS query message, and the second DNS query message is sent to the edge application service function. That is to say, the user plane network element can execute the The above processing logic for the first DNS query message can avoid misoperation or mishandling of user plane network elements. Of course, if the user plane network element is not configured with the first user plane processing rule, the user plane network element can process the first DNS query message according to the above processing logic by default.
  • the first user plane processing rule may not be limited to the first DNS query message and the second DNS query message, but may also be applicable to DNS query messages from the terminal and DNS query messages sent to the edge application service function.
  • the first user plane processing rule may indicate that for a DNS query message from the terminal, the user plane network element replaces the source address of the DNS query message from the terminal's address to the first address to obtain the DNS query message and apply it to the edge.
  • the service function sends DNS query messages.
  • the first DNS query message is one of the DNS query messages from the terminal
  • the second DNS query message is one of the DNS query messages sent to the edge application service function.
  • the edge application service function saves a DNS context.
  • the DNS context can be pre-configured by the edge application service function, or provided by the session management network element in advance, or the edge application service function can be pre-configured according to the session management network element.
  • the information provided is self-generated and is not limited.
  • the DNS context may include: the first address and DNS message processing rules.
  • the DNS message processing rules may include DNS message detection templates and operations.
  • the DNS message detection template may include: FQDN, which may be used to match the FQDN carried in the second DNS query message.
  • the operation may instruct the edge application service function to send the first DNS response message.
  • the edge application service function can match the corresponding DNS context according to the second DNS query message, thereby executing the corresponding processing, such as sending the first DNS response message to the user plane network element to achieve correct data routing.
  • the specific implementation of the DNS context can also refer to the relevant introduction in S303 above, and will not be described again.
  • the communication method may also include: the user plane network element receives the first DNS response message from the edge application service function; the user plane network element sends the destination address of the first DNS response message Replace the first address with the address of the terminal to obtain a second DNS response message, thereby sending the second DNS response message to the terminal.
  • the first DNS response message may be a response message to the second DNS query message.
  • the first DNS response message may carry an address of an application service, such as an address of an edge application service.
  • the edge application service function can determine whether the second DNS query message matches the DNS message processing rules in the DNS context, such as whether the FQDN in the second DNS query message matches Matches the FQDN in this DNS message processing rule.
  • the edge application service will process the DNS message according to the FQDN in the DNS message processing rule.
  • the operation is to send the first DNS response message to the user plane network element.
  • the user plane network element may determine that the first DNS response message is a message from the edge application service function, and may further determine whether the destination address of the first DNS response message is the first address.
  • the first DNS response message is mapped to the terminal's PDU session.
  • the user plane network element can replace the destination address of the first DNS response message from the first address to the address of the terminal to obtain the second DNS response message, and send the second DNS response message to the terminal through the terminal's PDU session. So that the terminal can obtain edge services.
  • the user plane network element may be configured with a second user plane processing rule.
  • the configuration method of the second user plane processing rules is similar to the first user plane processing rules and can be understood by reference and will not be described again.
  • the second user plane processing rule may indicate: for the first DNS response message, the user plane network element replaces the destination address of the first DNS response message from the first address to the terminal. address to obtain the second DNS response message, and send the second DNS response message to the terminal.
  • the second user plane processing rule may specifically indicate: for the first DNS response message, if the destination address of the first DNS response message is the first address, the user plane network element changes the destination address of the first DNS response message to the first address.
  • the address is replaced with the address of the terminal to obtain a second DNS response message, and the second DNS response message is sent to the terminal. That is to say, the user plane network element can execute the above-mentioned processing logic for the first DNS response message according to the second user plane processing rule, thereby avoiding misoperation or mishandling of the user plane network element.
  • the user plane network element can process the first DNS response message according to the above processing logic by default.
  • the second user plane processing rule may not be limited to the first DNS response message and the second DNS response message, but may also be applicable to the DNS response message from the edge application service function and the DNS response message sent to the terminal.
  • the second user plane processing rule may indicate that: for a DNS response message from the edge application service function, the user plane network element replaces the destination address of the DNS response message from the first address to the address of the terminal, and sends the DNS response message to the terminal.
  • the first DNS response message is one of the DNS response messages from the edge application service function
  • the second DNS response message is one of the DNS response messages sent to the terminal.
  • the communication method may also include: the user plane network element receives a third DNS query message from the edge application service function, and changes the destination address of the third DNS query message to the second address Replace with the address of the DNS server in HPLMN to obtain the fourth DNS query message, thereby sending the fourth DNS query message to HPLMN.
  • the third DNS query message can be used to request the addresses of other application services.
  • the destination address of the third DNS query message may be the second address.
  • the second address may be an address assigned by the VPLMN to the terminal.
  • the second address may be an identifier assigned by the VPLMN to the terminal's PDU session, or the second address may be mapped to the terminal's PDU session within the VPLMN.
  • the second address can indicate the DNS server in the HPLMN, that is, the user plane network element can map the terminal's message to the PDU session based on the second address, so as to send the message to the DNS server in the HPLMN.
  • the edge application service function can determine whether the second DNS query message matches the DNS message processing rules in the DNS context, such as whether the FQDN in the second DNS query message matches Matches the FQDN in this DNS message processing rule. At this time, if the FQDN in the second DNS query message does not match the FQDN in the DNS message processing rule, that is, there is no DNS message processing rule matching the second DNS query message, the edge application service will be sent to the user plane network element. Send a third DNS query message. For example, the edge application service can generate a third DNS query message based on the second address in the DNS context, and send the third DNS query message to the user plane network element.
  • the edge application service function can use the second address as the destination when determining the address to request other application services.
  • the address is carried to the third DNS query message, so that the user plane network element can identify the second address and send a corresponding message, such as a fourth DNS query message, to the HPLMN.
  • the fourth DNS query message can also be used to request the addresses of other application services.
  • the user plane network element may determine that the third DNS query message is a message from the edge application service function, and may further determine whether the third DNS query message is the second address based on the destination address of the third DNS query message.
  • Three DNS query messages are mapped to the terminal's PDU session.
  • the user plane network element can replace the destination address of the third DNS query message from the second address to the address of the DNS server within the HPLMN to obtain the fourth DNS query message, thereby sending the fourth DNS to the HPLMN.
  • Query message such as sending a fourth DNS query message to HPLMN through the terminal's PDU session.
  • the address of the DNS server in HPLMN may be an address in HPLMN, for example, the address assigned by HPLMN to the DNS server, which may be an IP address or any other possible address without limitation.
  • the user plane network element can be configured with a third user plane processing rule.
  • the configuration method of the third user plane processing rules is similar to the first user plane processing rules and can be understood by reference and will not be described again.
  • the third user plane processing rule may indicate that: for the third DNS query message, the user plane network element replaces the destination address of the third DNS query message from the second address to the address of the DNS server within the HPLMN to obtain the fourth DNS query message, and sends a fourth DNS query message to the edge application service function.
  • the third user plane processing rule may specifically indicate: for the third DNS query message, if the destination address of the third DNS query message is the second address, the user plane network element replaces the destination address of the third DNS query message with the second address.
  • the user plane network element can execute the above processing logic for the third DNS query message according to the configured third user plane processing rules, thereby avoiding misoperation or mishandling of the user plane network element.
  • the user plane network element can process the third DNS query message according to the above processing logic by default.
  • the third user plane processing rules may not be limited to the third DNS query message and the fourth DNS query message, but may also be applicable to DNS query messages from the edge application service function and DNS query messages sent to the HPLMN.
  • the third user plane processing rule may indicate that: for a DNS query message from the edge application service function, the user plane network element sends a DNS query message to the HPLMN.
  • the third DNS query message is one of the DNS query messages from the edge application service function
  • the fourth DNS query message is one of the DNS query messages sent to the HPLMN.
  • the communication method may also include: the user plane network element receives the third DNS response message from the HPLMN; the user plane network element applies the service function to the edge according to the third DNS response message. Send a fourth DNS response message; the edge application service function receives the fourth DNS response message from the user plane network element; the edge application service function sends a fifth DNS response message to the user plane network element according to the fourth DNS response message; the user plane network The user plane network element receives the fifth DNS response message from the edge application service function; the user plane network element sends the sixth DNS response message to the terminal according to the fifth DNS response message.
  • the third DNS response message may be a response message to the fourth DNS query message, and the third DNS response message may carry addresses of other application services for the terminal to obtain corresponding application services.
  • the source address of the third DNS response message may be the address of the DNS server in the HPLMN, and the destination address of the third DNS response message may be the address of the terminal.
  • the user plane network element can receive the third DNS response message through the PDU session of the terminal.
  • the fourth DNS response message may be a response message to the third DNS query message.
  • the fourth DNS response message may be determined based on the third DNS response message.
  • the user plane network element can determine the direction to the edge based on the fact that the third DNS response message comes from the DNS server in the HPLMN, and further based on the fact that the destination address of the third DNS response message is the address of the terminal.
  • the application service function sends a fourth DNS response message.
  • the user plane network element can replace the source address of the third DNS response message from the address of the DNS server in the HPLMN to the second address, and replace the destination address of the third DNS response message from the address of the terminal to the address of the edge application service function. address to obtain the fourth DNS response message, and then send the fourth DNS response message to the edge application service function.
  • the user plane network element may be configured with a fourth user plane processing rule.
  • the configuration method of the fourth user plane processing rules is similar to that of the first user plane processing rules and can be understood by reference without going into details.
  • the fourth user plane processing rule may indicate: for In the third DNS response message, the user plane network element replaces the source address of the third DNS response message from the address of the DNS server in the HPLMN to the second address, and replaces the destination address of the third DNS response message from the address of the terminal to the edge application.
  • the address of the service function is used to obtain the fourth DNS response message, and then the fourth DNS response message is sent to the edge application service function.
  • the fourth user plane processing rule may specifically indicate: for the third DNS response message, if the destination address of the third DNS response message is the address of the terminal, the user plane network element will use the DNS server in the HPLMN to transfer the source address of the third DNS response message. The address is replaced with the second address, and the destination address of the third DNS response message is replaced by the address of the terminal with the address of the edge application service function to obtain the fourth DNS response message, and then the fourth DNS response is sent to the edge application service function information.
  • the user plane network element can execute the above processing logic for the third DNS response message according to the configured fourth user plane processing rule, thereby avoiding misoperation or mishandling of the user plane network element.
  • the user plane network element can process the third DNS response message according to the above processing logic by default.
  • the fourth user plane processing rule may not be limited to the third DNS response message and the fourth DNS response message, but may also be applicable to the DNS response message from the HPLMN and the DNS response message sent to the edge application service function.
  • the fourth user plane processing rule may indicate that: for a DNS response message from the HPLMN, the user plane network element replaces the source address of the DNS response message with the address of the DNS server within the HPLMN to the second address, and changes the destination of the DNS response message. The address is replaced by the address of the terminal with the address of the edge application service function, and then a DNS response message is sent to the edge application service function.
  • the third DNS response message is one of the DNS response messages from the HPLMN
  • the fourth DNS response message is one of the DNS response messages sent to the edge application service function.
  • the fifth DNS response message is a response message to the second DNS query message.
  • the fifth DNS response message may be determined based on the fourth DNS response message.
  • the edge application service function can replace the source address of the fourth DNS response message from the second address to the edge application service function based on the matching of the fourth DNS response message with the corresponding DNS message processing rule. address, and replaces the destination address of the fourth DNS response message with the address of the edge application service function with the first address to obtain the fifth DNS response message, and then sends the fifth DNS response message to the user plane network element.
  • the sixth DNS response message may be a response message to the first DNS query message.
  • the sixth DNS response message can be determined based on the fifth DNS response message.
  • the specific implementation is similar to the above-mentioned second DNS response message, which can be understood by reference and will not be described again.
  • the edge application service function can use the first address assigned by the VPLMN to the terminal to identify the terminal's DNS query message to avoid address conflicts, achieve correct data routing, and facilitate the terminal to obtain application services, such as edge services.
  • FIG 11 is a schematic architectural diagram of Embodiment 2 in a specific scenario.
  • This scenario involves UE, V-UPF network element, V-SMF network element, V-EASDF, and H-DNS server.
  • the UE may be the terminal in the above method
  • the V-UPF network element may be the user plane network element in the above method
  • the V-SMF network element may be the session management network element in the above method
  • the V-EASDF may be the user plane network element in the above method.
  • the edge application service function and H-DNS server can be the above-mentioned DNS server in HPLMN.
  • the IP address of the UE is IP address 1
  • IP address 1 is also HPLMN for the UE. assigned address.
  • the IP address of V-EASDF is IP address 2.
  • the IP address of the H-DNS server is IP address 3, which is also the address assigned by HPLMN to the H-DNS server.
  • the VPLMN may allocate an IP address 4 (the above-mentioned first address) to the UE, and allocate an IP address 5 (the above-mentioned second address) to the H-DNS server.
  • IP address 4 and IP address 5 can be mapped to the HR PDU session of the UE. For example, IP address 4 can point to the UE within the HR PDU session, and IP address 5 can point to the H-DNS server within the HR PDU session. IP address 4 and IP address 5 can be saved in the DNS context corresponding to this HR PDU session.
  • the UPF processing rules can include: 1) For the DNS query message from the UE, the V-UPF network element changes the source address of the DNS query message from the IP address Replace 1 with IP address 4 and send a DNS query message to V-EASDF. 2) For the DNS response message from V-EASDF, the V-UPF network element replaces the destination address of the DNS response message from IP address 4 to IP address 1, and sends the DNS response message to the UE. 3) For the DNS query message from V-EASDF, the V-UPF network element replaces the destination address of the DNS query message from IP address 5 to IP address 3, and sends the DNS query message to the H-DNS server.
  • the V-UPF network element For the DNS response message from the H-DNS server, the V-UPF network element replaces the source address of the DNS response message from IP address 3 to IP address 5, and replaces the destination address of the DNS response message from IP address 1 to IP Address 2, sends a DNS response message to V-EASDF.
  • the behavior of V-EASDF is mainly dictated by DNS message processing rules: DNS message detection templates and operations.
  • the DNS message detection template includes: FQDN, which can be used to match the FQDN in the DNS query message from the UE.
  • Actions can be used to instruct: V-EASDF to send a DNS response message.
  • FIG 12 is a schematic flowchart 4 of the communication method provided by the embodiment of the present application. This communication method is suitable for the scenario shown in Figure 10. As shown in Figure 12, the specific process of this communication method is as follows:
  • the H-SMF network element sends a PDU session creation response message to the V-SMF network element.
  • the V-SMF network element receives the PDU session creation response message from the H-SMF network element.
  • S1201 the specific implementation principle of S1201 is similar to the above-mentioned S901, which can be understood by reference and will not be described again.
  • the V-SMF network element sends an N4 session modification request message to the V-UPF network element.
  • the V-UPF network element receives the N4 session modification request message from the V-SMF network element.
  • the N4 session modification request message may carry second indication information.
  • the second indication information may be used to instruct the V-UPF network element to allocate IP address 4 and/or IP address 5.
  • the N4 session modification request message may not carry the second indication information.
  • the V-UPF network element receives the N4 session modification request message, the UE will be assigned IP address 4 and/or IP address 5 by default.
  • the V-UPF network element allocates IP address 4 and/or IP address 5.
  • the V-UPF network element can allocate IP address 4 and IP address 5 in any possible way.
  • the V-UPF network element can randomly select two unused IP addresses in the address pool as IP address 4 and IP address 5 respectively.
  • the V-UPF network element can sequentially select two unused IP addresses as IP address 4 and IP address 5 in the address pool.
  • the V-UPF network element sends an N4 session modification response (N4Sseesion Modification Response) message to the V-SMF network element.
  • N4Sseesion Modification Response N4Sseesion Modification Response
  • the V-SMF network element receives the N4 session modification response message from the V-UPF network element.
  • the N4 session modification request message may carry IP address 4 and/or IP address 5.
  • S1202-S1204 are optional steps.
  • IP address 4 and/or IP address 5 may be determined by the V-SMF network element.
  • S1202-S1204 may not be executed.
  • S1202-S1204 can also refer to the above The relevant introduction in S1002 will not be repeated again.
  • V-SMF network element sends a DNS context creation request message to V-EASDF.
  • V-EASDF receives the DNS context creation request message from the V-SMF network element.
  • the DNS context creation request message can be used to request EASDF to create the DNS context corresponding to the UE's HR PDU session.
  • the DNS context creation request message may include at least one of the following: IP address 4, IP address 5, and DNS message processing rules.
  • IP address 4, IP address 5, and DNS message processing rules For the specific implementation of DNS message processing rules, please refer to Figure 10 and the relevant introduction in S303 above, and will not be described again.
  • DNS message processing rules can be pre-configured or protocols pre-defined on V-EASDF.
  • the DNS context creation request message can carry IP address 4 and IP address 5 without carrying DNS message processing rules.
  • information such as IP address 4 and IP address 5 can be used to trigger V-EASDF to activate local DNS message processing rules.
  • the DNS context creation request message can also carry an additional information element, which can be used to trigger V-EASDF to activate local DNS message processing rules.
  • DNS message processing rules can be determined by V-EASDF based on some necessary parameters. In this case, the DNS context creation request message can only carry these necessary parameters, such as at least one of the following: IP address 4, IP address 5, and so on.
  • V-EASDF can create a request message based on the DNS context, create a DNS context corresponding to the UE's HR PDU session, and store at least one of the following: IP address 5, IP address 4, and DNS message processing rules into the DNS context.
  • S1205 can also refer to the relevant introduction in S303-S304 above, and will not be described again.
  • the V-SMF network element sends the N4 rule to the V-UPF network element.
  • the V-UPF network element receives the N4 rule from the V-SMF network element.
  • N4 rules can be carried in the N4 session, such as the N4 session modification response message.
  • the N4 session corresponds to the UE's HR PDU session.
  • the N4 rule may include at least one of the following: IP address 1, IP address 2, IP address 3, IP address 4, IP address 5, and UPF processing rules.
  • IP address 1, IP address 2, IP address 3, IP address 4, IP address 5, and UPF processing rules For the specific implementation of UPF processing rules, please refer to the relevant introduction in Figure 10 and will not be described again.
  • UPF processing rules can also refer to the relevant introduction of the user plane processing rules mentioned above.
  • the embodiment of the present application takes the UPF processing rule as an example to illustrate. Those skilled in the art can understand that the UPF processing rules in the embodiment of the present application can be replaced by user plane processing rules. . That is to say, when the user plane processing rules are information in other forms other than UPF processing rules, similar processing is performed.
  • N4 rules carrying UPF processing rules are an optional implementation method.
  • UPF processing rules can be pre-configured or the protocol can be pre-defined on the V-UPF network element.
  • the N4 rule can carry at least one of the following: IP address 1, IP address 2, IP address 3, IP address 4, IP address 5, without carrying the UPF processing rule.
  • information such as IP address 1, IP address 2, IP address 3, IP address 4, and IP address 5 can be used to trigger the V-UPF network element to activate local UPF processing rules.
  • the N4 rule can also carry an additional information element, which can be used to trigger the V-UPF network element to activate local UPF processing rules.
  • the DNS message processing rules can be determined by the V-UPF network element itself based on some necessary parameters.
  • the N4 rule can only carry these necessary parameters, such as at least one of the following: IP address 1, IP address 2, IP address 3, IP address 4, IP address 5, etc.
  • the V-UPF network element obtains the UPF processing rules through the UE's HR PDU session corresponding to the N4 session, this acquisition method can implicitly indicate that the UPF processing rules correspond to the HR PDU session, so that the V-UPF network element can According to the UPF processing rules, the corresponding messages (such as DNS response message #1 and DNS query mentioned below Message #3) is mapped to the HR PDU session to send these messages through the HR PDU session.
  • the UPF processing rules can also directly define that these messages need to be mapped to the HR PDU session.
  • S1201-S1206 are steps in the HR PDU session creation process in the HR scenario, that is, the embodiment of the present application is applicable to this process.
  • the execution order between S1206 and S1205 is not limited.
  • the UE sends DNS query message #1 to the V-UPF network element.
  • the V-UPF network element receives the DNS query message #1 from the UE.
  • V-UPF network element sends DNS query message #2 to V-EASDF.
  • V-EASDF receives DNS query message #2 from the V-UPF network element.
  • the source address of DNS query message #2 can be IP address 4, and the destination address can be IP address 2 or IP address 3.
  • the V-UPF network element can determine DNS query message #2 based on DNS query message #1. For example, after receiving the DNS query message #1, according to the UPF processing rules, the source address of the DNS query message #1 is replaced from IP address 1 to IP address 4 to obtain DNS query message #2. Then, the V-UPF network element can send the DNS query message #2 to the V-EASDF according to the UPF processing rules.
  • the relevant introduction in S1002 above please refer to the relevant introduction in S1002 above, which will not be described again.
  • V-EASDF determines whether there is a DNS message processing rule matching DNS query message #2.
  • V-EASDF can match the DNS context storing IP address 4 according to the source address of DNS query message #2, which is IP address 4. At this time, V-EASDF can determine whether there is a DNS message processing rule matching DNS query message #2 in the DNS context. If there is a DNS message processing rule that matches DNS query message #1, for example, the FQDN in DNS query message #1 matches the FQDN in the DNS message processing rule, that is, DNS query message #2 matches the DNS message detection template, then it represents DNS query message #1 is used to request an application service that is an edge service, thereby triggering execution of S1210-S1211 to provide edge services for the UE.
  • V-EASDF can trigger execution of S1212-S1216 to provide corresponding application services for the UE.
  • S1209 can also refer to the relevant introductions in the above-mentioned S1002, the fourth possible design solution, and the fifth possible design solution, and will not be described again.
  • V-EASDF sends DNS response message #1 to the V-UPF network element.
  • the V-UPF network element receives DNS response message #1 from V-EASDF.
  • DNS response message #1 may be used in response to DNS query message #1.
  • DNS response message #1 may carry the IP address of an EAS queried by DNS query message #1.
  • the source address of DNS response message #1 is IP address 2, and the destination address is IP address 4.
  • DNS response message #1 may carry the IP address of the EAS corresponding to the edge service.
  • V-EASDF can obtain the IP address of the EAS by interacting with the V-SMF network element and the DNS server. For details, please refer to the relevant introduction of S308-S318 above, which will not be described again. Then, V-EASDF can encapsulate the IP address of the EAS corresponding to the edge service into DNS response message #1 according to the instructions in the DNS message processing rule, thereby sending DNS response message #1 to the V-UPF network element.
  • the V-UPF network element sends DNS response message #2 to the UE.
  • the UE receives DNS response message #2 from the V-UPF network element.
  • the source address of DNS response message #2 is IP address 2 or IP address 3, and the destination address is IP address 1. That is to say, the V-UPF network element can determine the DNS response message #2 based on the DNS response message #1. For example, after receiving the DNS response message #1, the V-UPF network element can determine to map the DNS response message #1 to the UE's HR PDU session based on the destination address of the DNS response message #1 from IP address 4. For example, the V-UPF network element can replace the destination address of DNS response message #1 from IP address 4 to IP address 1 to obtain DNS response message #2. Alternatively, if the destination address of DNS query message #1 is IP address 3, the V-UPF network element can also replace the source address in DNS response message #1 from IP address 2 to IP address 3 to obtain DNS response message # 2.
  • the V-UPF network element maps the DNS response message #2 to the UE's HR PDU session to send the DNS response message #2 to the UE through the HR PDU session. In this way, the UE can obtain the IP address of the EAS from the DNS response message #2, and then access the EAS according to the IP address of the EAS to obtain the corresponding edge service.
  • the V-UPF network element determines that the destination address of DNS response message #1 is not IP address 4, the V-UPF network element can discard the DNS response message #1. It can be understood that the V-UPF network element can also execute the processing logic in S1211 according to the UPF processing rules, without limitation.
  • S1210-S1211 can also refer to the relevant introduction in the fourth possible design solution mentioned above, and will not be described again.
  • V-EASDF sends DNS query message #3 to the V-UPF network element.
  • the V-UPF network element receives DNS query message #3 from V-EASDF.
  • DNS query message #3 can be used to request the H-DNS server to provide services.
  • the source address of DNS query message #3 is IP address 2, and the destination address is IP address 5. That is to say, after determining the IP address for requesting other application services, V-EASDF determines that it can send DNS query message #3 to the V-UPF network element. For example, V-EASDF can replace the source address of DNS query message #2 from IP address 4 to IP address 2, and replace the destination address of DNS query message #2 from IP address 2 to IP address 5, to obtain DNS query message # 2. Alternatively, V-EASDF can also directly generate DNS query message #2. Then, V-EASDF can send DNS query message #3 to the V-UPF network element according to the DNS message processing rules.
  • the V-UPF network element sends DNS query message #4 to the H-DNS server.
  • the H-DNS server receives DNS query message #4 from the V-UPF network element.
  • DNS query message #4 can be used to request the H-DNS server to provide services.
  • the source address of DNS query message #4 is IP address 1 and the destination address is IP address 3. That is to say, the V-UPF network element can determine DNS query message #4 based on DNS query message #3. For example, the V-UPF network element can determine to map the DNS query message #3 to the UE's HR PDU session based on the fact that the destination address of the DNS query message #3 is IP address 5. For example, the V-UPF network element can replace the source address of DNS query message #3 from IP address 2 to IP address 1, and replace the destination address of DNS query message #3 from IP address 5 to IP address 3 to obtain the DNS Query message #4.
  • the V-UPF network element can map the DNS query message #4 to the UE's HR PDU session to send the DNS query message #4 to the H-DNS server through the HR PDU session.
  • the V-UPF network element determines that the destination address of DNS query message #3 is not IP address 5 according to the UPF processing rules, the V-UPF network element can discard the DNS query message #3. It can be understood that the V-UPF network element can also execute the processing logic in S1213 according to the UPF processing rules, without limitation.
  • S1212-S1213 can also refer to the relevant introduction in the fifth possible design solution mentioned above, and will not be described again.
  • the H-DNS server sends DNS response message #3 to the V-UPF network element through the H-UPF network element.
  • the V-UPF network element receives the DNS response message #3 from the H-DNS server through the H-UPF network element.
  • V-UPF network element sends DNS response message #4 to V-EASDF.
  • V-EASDF receives DNS response message #4 from the V-UPF network element.
  • DNS response message #4 may be a response message to DNS query message #3.
  • the source address of DNS response message #4 is IP address 5 and the destination address is IP address 2. That is to say, the V-UPF network element can determine DNS response message #4 based on DNS response message #3. For example, after receiving DNS response message #3, the V-UPF network element can determine that the destination address is IP address 1 according to the UPF processing rules.
  • DNS response message #3 is a message that needs to be sent to V-EASDF. In this way, the V-UPF network element can replace the source address of DNS response message #3 from IP address 3 to IP address 5 and replace the destination address of DNS response message #3 from IP address 1 to IP address according to the UPF processing rules. 2, to get DNS response message #4.
  • the V-UPF network element can send DNS response message #4 to V-EASDF according to the UPF processing rules.
  • the V-UPF network element determines that the destination address of DNS response message #3 is not IP address 1 according to the UPF processing rules, the V-UPF network element can discard the DNS response message #3. It can be understood that the V-UPF network element can also execute the processing logic in S1215 according to the UPF processing rules, without limitation.
  • V-EASDF sends DNS response message #5 to the V-UPF network element.
  • the V-UPF network element receives DNS response message #5 from V-EASDF.
  • DNS response message #5 may be a response message to DNS query message #2.
  • the source address of DNS response message #5 is IP address 2 and the destination address is IP address 4.
  • V-EASDF may determine DNS response message #5 based on DNS response message #4. For example, after V-EASDF receives DNS response message #4, it can match DNS response message #4 to the corresponding DNS message processing rule. In this way, V-EASDF can replace the source address of DNS response message #4 from IP address 5 to IP address 2 according to the DNS message processing rules corresponding to DNS response message #4, and change the destination address of DNS response message #4 from IP address 2 is replaced with IP address 4, thereby obtaining DNS response message #5, and returning the DNS response message #5 to the V-UPF network element.
  • V-EASDF sends DNS response message #6 to the UE.
  • the UE receives DNS response message #6 from V-EASDF.
  • DNS response message #6 may be a response message to DNS query message #1.
  • the source address of DNS response message #6 is IP address 2 or IP address 3, and the destination address is IP address 1. That is to say, the V-UPF network element can determine the DNS response message #6 based on the DNS response message #5.
  • the relevant introduction of the above DNS response message #2 please refer to the relevant introduction of the above DNS response message #2, which will not be described again.
  • S1214-S1217 can also refer to the relevant introduction in the sixth possible design solution mentioned above, and will not be described again.
  • V-UPF network element and V-EASDF as an example, but it is not limited to this.
  • V-UPF network element can also be replaced with other V-UPF network element
  • V-EASDF can also be replaced. for other V-EASDF.
  • identifying the UE's DNS message with the IP address assigned by the VPLMN can avoid IP address conflicts so that the UE can obtain edge services.
  • VPLMN can also configure processing rules for non-EC DNS query messages for the V-UPF network element to ensure that the V-UPF network element can forward non-EC DNS query messages to the H-DNS server or H-EASDF, Ensure that the UE can access the H-DNS server and obtain corresponding application services.
  • FIG. 13 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • the communication device 1300 includes: a receiving module 1301 and a sending module 1302.
  • FIG. 13 only shows the main components of the communication device.
  • the communication device 1300 can be applied to the communication system shown in Figure 6 to perform the functions of the user plane network element in the method shown in Figure 7, or to perform the functions of the V-UPF network element in the method shown in Figure 9.
  • the receiving module 1301 is used to receive the first domain name system DNS query message from the terminal, and the sending module 1302 is used to send the first DNS query message and the first identification to the edge application service function.
  • the first DNS query message is used to query the address of the application service, and the first identifier is an identifier allocated by the VPLMN to the terminal.
  • the first identification is used by the edge application service function to determine whether there is a DNS rule matching the first identification.
  • the first identification can be used to identify the terminal within the VPLMN.
  • the first identifier may be the VPLMN, such as a network element within the VPLMN, an identifier assigned to the protocol data unit PDU session of the terminal, or the first identifier may be mapped to the PDU session of the terminal within the VPLMN.
  • the terminal's PDU session can be the terminal's home routing HR PDU session.
  • the receiving module 1301 is configured to receive a first domain name system DNS query message from the terminal through a PDU session of the terminal.
  • the communication device 1300 is configured with a first user plane processing rule.
  • the first user plane processing rule indicates: for the first DNS query message, the communication device 1300 sends the first DNS query message to the edge application service function. and first logo.
  • the sending module 1302 is configured to send the first DNS query message and the first identifier to the edge application service function through the communication tunnel; the first identifier is carried in the header of the communication tunnel.
  • the first identifier is an identifier of the communication tunnel.
  • the first identifier may also be carried in the first DNS query message, such as in a reserved field of the first DNS query message.
  • the receiving module 1301 is also configured to receive the first DNS response message and the first DNS response message from the edge application service function after the sending module 1302 sends the first DNS query message and the first identification to the edge application service function.
  • the communication device 1300 also includes: a processing module (not shown in Figure 13); a processing module configured to control the sending module 1302 to send the first DNS response message to the terminal according to the second identification.
  • the second identifier is an identifier assigned by the VPLMN to the terminal, and the first DNS response message carries the address of the application service.
  • the second identification can be used to identify the terminal within the VPLMN.
  • the second identifier may be the VPLMN, such as a network element within the VPLMN, an identifier assigned to the terminal's PDU session, or the second identifier may be mapped to the terminal's PDU session within the VPLMN.
  • the communication device 1300 is configured with a second user plane processing rule, which indicates that: for the first DNS response message and the second identification, the communication device 1300 sends the first DNS response message to the terminal.
  • the receiving module 1301 is configured to receive the first DNS response message and the second identification from the edge application service function through the communication tunnel; the second identification is carried in the header of the communication tunnel.
  • the second identifier is an identifier of the communication tunnel.
  • the second identifier may be the same as the first identifier, or may be different, without limitation.
  • the second identification may also be carried in the first DNS response message, such as in the reserved fields.
  • the receiving module 1301 is also configured to receive the second DNS query message and the first identification from the edge application service function after the sending module 1302 sends the first DNS query message and the first identification to the edge application service function.
  • the communication device 1300 also includes: a processing module (not shown in Figure 13); the processing module is configured to control the sending module 1302 to send a third DNS query message to the HPLMN of the terminal according to the second DNS query message and the second identification.
  • the second identifier is an identifier assigned by the VPLMN to the terminal, the second DNS query message is used to obtain the address of the application service, and the third DNS query message is used to request the address of the application service.
  • the second identification can be used to identify the terminal within the VPLMN.
  • the second identifier may be the VPLMN, such as a network element within the VPLMN, an identifier assigned to the terminal's PDU session, or the second identifier may be mapped to the terminal's PDU session within the VPLMN.
  • the communication device 1300 is configured with a third user plane processing rule, the third user plane processing rule indicates: for the second DNS query message and the second identification from the edge application service function, the communication device 1300 sends to the HPLMN of the terminal Third DNS query message.
  • the receiving module 1301 is configured to receive the second DNS query message and the second identification from the edge application service function through the communication tunnel; the second identification is carried in the header of the communication tunnel.
  • the second identifier is an identifier of the communication tunnel.
  • the second identifier may be the same as the first identifier, or may be different, without limitation.
  • the second identifier may also be carried in the second DNS query message, such as in a reserved field of the second DNS query message.
  • the communication device 1300 further includes: a processing module (not shown in Figure 13); the processing module is configured to determine the first identity before the receiving module 1301 receives the first DNS message from the terminal, And control the sending module 1302 to send the first identifier to the session management network element.
  • the receiving module 1301 is configured to receive the first identification from the session management network element.
  • the communication device 1300 further includes: a processing module (not shown in Figure 13); the processing module is configured to determine the second identity before the receiving module 1301 receives the first DNS message from the terminal, And control the sending module 1302 to send the second identifier to the session management network element.
  • the receiving module 1301 is configured to receive the second identification from the session management network element.
  • the sending module 1302 and the receiving module 1301 can also be integrated into a sending and receiving module to implement the sending and receiving functions of the communication device 1300 .
  • the communication device 1300 may also include a storage module that stores programs or instructions.
  • the processing module executes the program or instruction, the communication device 1300 can execute the method described in FIG. 7 or FIG. 9 .
  • the communication device 1300 may be a network device, such as a user plane network element or a V-UPF network element, or it may be a chip (system) or other component or component that can be installed in the network device, or it may include a network device.
  • the device of the equipment is not limited in this application.
  • the technical effects of the communication device 1300 can be referred to the technical effects of the above communication method, which will not be described again here.
  • FIG. 14 is a second structural schematic diagram of a communication device provided by an embodiment of the present application.
  • the communication device 1400 includes: a transceiver module 1401 and a processing module 1402.
  • FIG. 14 shows only the main components of the communication device.
  • the communication device 1400 may be adapted to the communication system shown in FIG. 6 and perform the steps shown in FIG. 7 The function of the edge application service function in the method, or the function of V-EASDF in the method shown in Figure 9.
  • the transceiver module 1401 is used to receive the first domain name system DNS query message and the first identifier from the user plane network element.
  • the processing module 1402 is used to determine whether there is a DNS message processing rule that matches the first DNS query message and the first identifier. .
  • the first identifier is an identifier assigned to the terminal by the visiting public land mobile network VPLMN. The terminal roams into the VPLMN, and the first DNS query message is used to query the address of the application service.
  • the transceiver module 1401 is configured to receive the first DNS query message and the first identifier from the user plane network element through the communication tunnel; the first identifier is carried in the header of the communication tunnel.
  • the first identifier is an identifier of the communication tunnel.
  • the transceiver module 1401 when there is a DNS message processing rule matching the first DNS query message and the first identifier, the transceiver module 1401 is configured to send the first DNS response message and the second DNS response message to the user plane network element. logo.
  • the second identifier is an identifier assigned by the VPLMN to the terminal, and the first DNS response message carries the address of the application service.
  • the communication device 1400 is configured with a DNS message processing rule, which indicates that the device 1400 sends the first DNS response message and the second identification to the user plane network element.
  • the transceiver module 1401 is configured to send the first DNS response message and the second identifier to the user plane network element through the communication tunnel; the second identifier is carried in the header of the communication tunnel.
  • the second identifier is an identifier of the communication tunnel.
  • the transceiver module 1401 when there is no DNS message processing rule matching the first DNS query message and the first identifier, the transceiver module 1401 is configured to send the second DNS query message and the third DNS query message to the user plane network element.
  • the transceiving module 1401 is configured to send the second DNS query message and the second identification to the user plane network element through the communication tunnel.
  • the second identification is carried in the header of the communication tunnel.
  • the second identification is an identification of the communication tunnel.
  • the processing module 1402 is also configured to determine the first identifier before the transceiver module 1401 receives the first DNS query message and the first identifier from the user plane network element, and control the transceiver module 1401 to send the first identifier to the session.
  • the management network element sends the first identifier.
  • the transceiver module 1401 is configured to receive the first identifier from the session management network element.
  • the processing module 1402 is also configured to determine the second identifier before the transceiver module 1401 receives the first DNS query message and the first identifier from the user plane network element, and control the transceiver module 1401 to send the message to the session.
  • the management network element sends the second identifier.
  • the transceiving module 1401 is configured to receive the second identification from the session management network element.
  • the transceiver module 1401 may also include a sending module and a receiving module.
  • the sending module is used to implement the sending function of the communication device 1400
  • the receiving module is used to implement the receiving function of the communication device 1400 .
  • the communication device 1400 may also include a storage module that stores programs or instructions.
  • the processing module 1402 executes the program or instruction
  • the communication device 1400 can execute the method shown in FIG. 7 or FIG. 9 .
  • the communication device 1400 may be a network device, such as an edge application service function or V-EASDF, or may be a chip (system) or other component or component that can be disposed in the network device, or may include a network device. device, this application does not limit this.
  • the communication device 1400 may be adapted to the communication system shown in FIG. 6 to perform the function of the session management network in the method shown in FIG. 7, or to perform the V-SMF network in the method shown in FIG. 9. Yuan function.
  • the processing module 1402 is used to determine the first identification; the transceiving module 1401 is used to send the first identification to the user plane network element.
  • the first identifier is the identifier in the visited public land mobile network VPLMN corresponding to the terminal, and the terminal roams into the VPLMN.
  • the transceiver module 1401 is configured to send the first identification to the edge application service function.
  • the processing module 1402 is configured to determine the first identifier during the establishment process of the protocol data unit PDU session of the terminal.
  • the terminal's PDU session is the terminal's home routing HR PDU session.
  • the processing module 1402 is used to determine the second identifier; the transceiver module 1401 is used to send the second identifier to the user plane network element.
  • the transceiving module 1401 is used for the edge application service function to send the second identification.
  • the transceiver module 1401 may also include a sending module and a receiving module.
  • the sending module is used for the sending function of the communication device 1400
  • the receiving module is used for realizing the receiving function of the communication device 1400 .
  • the communication device 1400 may also include a storage module that stores programs or instructions.
  • the processing module 1402 executes the program or instruction
  • the communication device 1400 can execute the method described in FIG. 7 or FIG. 9 .
  • the communication device 1400 may be a network device, such as a session management network element or a V-SMF network element, or a chip (system) or other components or components that can be installed in the network device, or may include a network device.
  • the device of the equipment is not limited in this application.
  • the communication device 1400 may be adapted to the communication system shown in Figure 6 to perform the functions of the user plane network element in the method shown in Figure 10, or to perform the V-UPF in the method shown in Figure 12 Network element functions.
  • the transceiving module 1401 is used to receive the first domain name system DNS query message from the terminal, and the processing module 1402 is used to replace the source address of the first DNS query message from the terminal's address to the first address to obtain the second DNS query message, thereby controlling the transceiver module 1401 to send a second DNS query message to the edge application service function.
  • the terminal roams to the visited public land mobile network VPLMN, and the first DNS query message is used to query the address of the application service, and the first address is the address allocated by the VPLMN to the terminal.
  • the first address may specifically be a VPLMN, such as a network element within the VPLMN, an identifier assigned to the protocol data unit PDU session of the terminal, or the first address may be mapped to the PDU session of the terminal.
  • VPLMN such as a network element within the VPLMN, an identifier assigned to the protocol data unit PDU session of the terminal, or the first address may be mapped to the PDU session of the terminal.
  • the transceiver module 1401 is configured to receive a first domain name system DNS query message from the terminal through a PDU session of the terminal.
  • the terminal's PDU session can be the terminal's home routing HR PDU session.
  • the communication device 1400 is configured with a first user plane processing rule, which indicates: for the first DNS query message, the device changes the source address of the first DNS query message from the terminal's The address is replaced with the first address to obtain a second DNS query message, and the second DNS query message is sent to the edge application service function.
  • the transceiver module 1401 is configured to receive a first DNS response message from the edge application service function after sending the second DNS query message to the edge application service function.
  • the first DNS response message carries the application The address of the service.
  • the processing module 1402 is used to replace the destination address of the first DNS response message from the first address to the address of the terminal to obtain the second DNS response message, thereby controlling the sending and receiving of the second DNS response to the terminal. Respond to the message.
  • the communication device 1400 is configured with a second user plane processing rule, which indicates that: for the first DNS response message, the device replaces the destination address of the first DNS response message from the first address to the terminal. address to obtain the second DNS response message, and send the second DNS response message to the edge application service function.
  • the transceiver module 1401 is configured to receive a third DNS query message from the edge application service function after sending the second DNS query message to the edge application service function.
  • the processing module 1402 is used to replace the destination address of the third DNS query message from the second address to the address of the DNS server in the HPLMN to obtain the fourth DNS query message, thereby controlling the transceiver module 1401 to send the fourth DNS query message to the HPLMN.
  • the second address is an address assigned by the VPLMN to the terminal.
  • the second address may be an identifier assigned by the VPLMN to the terminal's protocol data unit PDU session, or the second address may be mapped to the terminal's PDU session, that is, the user plane network element may map the terminal's message to the terminal based on the second address.
  • the second address and the first address may be different.
  • the communication device is configured with a third user plane processing rule, and the third user plane processing rule indicates that: for the third DNS query message, the device changes the destination address of the third DNS query message to The second address is replaced with the address of the DNS server in the HPLMN to obtain the fourth DNS query message, and the fourth DNS query message is sent to the edge application service function.
  • the processing module 1402 is configured to determine the first address for the user plane network element before the transceiver module 1401 receives the first DNS message from the terminal, and control the transceiver module 1401 to send the first DNS message to the session management network element. address.
  • the transceiving module 1401 is configured to receive the first address from the session management network element.
  • the processing module 1402 is configured to determine the second address before the transceiver module 1401 receives the first DNS message from the terminal, and control the transceiver module 1401 to send the second address to the session management network element.
  • the transceiving module 1401 is configured to receive the second address from the session management network element.
  • the transceiver module 1401 may also include a sending module and a receiving module.
  • the sending module is used to implement the sending function of the communication device 1400
  • the receiving module is used to implement the receiving function of the communication device 1400 .
  • the communication device 1400 may also include a storage module that stores programs or instructions.
  • the processing module 1402 executes the program or instruction, the communication device 1400 can perform the communication method described in FIG. 10 or FIG. 12 .
  • the communication device 1400 may be a network device, such as a user plane network element or a V-SMF network element, or it may be a chip (system) or other component or component that can be installed in the network device, or it may include a network device.
  • the device of the equipment is not limited in this application.
  • the communication device 1400 may be adapted to the communication system shown in FIG. 6 to perform the function of the session management network element in the method shown in FIG. 10, or to perform V-SMF in the method shown in FIG. 12. Network element functions.
  • the processing module 1402 is used to determine the first address, and the transceiving module 1401 is used to send the first address to the edge application service function.
  • the first address is the address assigned to the terminal by the visiting public land mobile network VPLMN, and the terminal roams into the VPLMN.
  • the transceiver module 1401 is used to send the first address to the user plane network element.
  • the processing module 1402 is configured to determine the first address during the establishment process of the protocol data unit PDU session of the terminal.
  • the terminal's PDU session is the terminal's home routing HR PDU session.
  • the processing module 1402 is used to determine the second address, and the transceiver module 1401 is used to Send the second address to the edge application service function.
  • the second address is an address assigned by the VPLMN to the terminal, and the second address is different from the first address.
  • the transceiving module 1401 is configured to send the second address to the user plane network element.
  • the processing module 1402 is configured to determine the second address during the establishment of a PDU session of the terminal.
  • the PDU session of the terminal is the HR PDU session of the terminal.
  • the transceiver module 1401 may also include a sending module and a receiving module.
  • the sending module is used to implement the sending function of the communication device 1400
  • the receiving module is used to implement the receiving function of the communication device 1400 .
  • the communication device 1400 may also include a storage module that stores programs or instructions.
  • the processing module 1402 executes the program or instruction
  • the communication device 1400 can execute the method described in FIG. 10 or FIG. 12 .
  • the communication device 1400 may be a network device, such as a session management network element or a V-SMF network element, or a chip (system) or other components or components that can be installed in the network device, or may include a network device.
  • the device of the equipment is not limited in this application.
  • FIG. 15 is a schematic structural diagram three of a communication device provided by an embodiment of the present application.
  • the communication device may be a terminal, or a chip (system) or other components or components that can be installed in the terminal.
  • communication device 1500 may include processor 1501 .
  • the communication device 1500 may also include a memory 1502 and/or a transceiver 1503.
  • the processor 1501 is coupled to the memory 1502 and the transceiver 1503, for example, through a communication bus.
  • the processor 1501 is the control center of the communication device 1500, and may be a processor or a collective name for multiple processing elements.
  • the processor 1501 is one or more central processing units (CPUs), may also be an application specific integrated circuit (ASIC), or may be configured to implement one or more embodiments of the present application.
  • An integrated circuit such as one or more microprocessors (digital signal processor, DSP), or one or more field programmable gate arrays (field programmable gate array, FPGA).
  • the processor 1501 can perform various functions of the communication device 1500 by running or executing software programs stored in the memory 1502 and calling data stored in the memory 1502, such as performing the above-mentioned functions shown in FIGS. 8-10. communication method.
  • the processor 1501 may include one or more CPUs, such as CPU0 and CPU1 shown in FIG. 15 .
  • the communication device 1500 may also include multiple processors, such as the processor 1501 and the processor 1504 shown in FIG. 15 .
  • processors can be a single-core processor (single-CPU) or a multi-core processor (multi-CPU).
  • a processor here may refer to one or more devices, circuits, and/or processing cores for processing data (eg, computer program instructions).
  • the memory 1502 is used to store the software program for executing the solution of the present application, and is controlled by the processor 1501 for execution.
  • the memory 1502 is used to store the software program for executing the solution of the present application, and is controlled by the processor 1501 for execution.
  • the memory 1502 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (random access memory, RAM) or a random access memory (RAM) that can store information and instructions.
  • ROM read-only memory
  • RAM random access memory
  • RAM random access memory
  • RAM random access memory
  • RAM random access memory
  • RAM random access memory
  • RAM random access memory
  • RAM random access memory
  • RAM random access memory
  • RAM random access memory
  • RAM random access memory
  • RAM random access memory
  • RAM random access memory
  • RAM random access memory
  • RAM random access memory
  • RAM random access memory
  • RAM random access memory
  • RAM random access memory
  • RAM random access memory
  • Transceiver 1503 used for communication with other communication devices.
  • the communication device 1500 is a terminal, and the transceiver 1503 can be used to communicate with a network device or with another terminal device.
  • the communication device 1500 is a network device, and the transceiver 1503 can be used to communicate with a terminal or another network device.
  • the transceiver 1503 may include a receiver and a transmitter (not shown separately in Figure 15). Among them, the receiver is used to implement the receiving function, and the transmitter is used to implement the sending function.
  • the transceiver 1503 can be integrated with the processor 1501, or can exist independently and be coupled to the processor 1501 through the interface circuit (not shown in Figure 15) of the communication device 1500. This is not the case in the embodiment of this application. Specific limitations.
  • the structure of the communication device 1500 shown in Figure 15 does not constitute a limitation on the communication device.
  • the actual communication device may include more or less components than shown in the figure, or some components may be combined, or Different component arrangements.
  • the technical effects of the communication device 1500 can be referred to the technical effects of the communication method described in the above method embodiments, which will not be described again here.
  • the processor in the embodiment of the present application can be a central processing unit (CPU).
  • the processor can also be other general-purpose processors, digital signal processors (DSP), special-purpose integrated processors, etc.
  • Circuit application specific integrated circuit, ASIC), off-the-shelf programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
  • a general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.
  • non-volatile memory may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory.
  • non-volatile memory can be read-only memory (ROM), programmable ROM (PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically removable memory. Erase electrically programmable read-only memory (EPROM, EEPROM) or flash memory.
  • Volatile memory can be random access memory (RAM), which is used as an external cache.
  • RAM random access memory
  • static random access memory static random access memory
  • DRAM dynamic random access memory
  • RAM synchronous dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • double data rate SDRAM double data rate SDRAM
  • DDR SDRAM double data rate SDRAM
  • enhanced SDRAM enhanced synchronous dynamic random access memory
  • SLDRAM synchronous connection dynamic random access memory access memory
  • direct rambus RAM direct rambus RAM, DR RAM
  • the above embodiments may be implemented in whole or in part by software, hardware (such as circuits), firmware, or any other combination.
  • the above-described embodiments may 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 or computer programs. When the computer instructions or computer programs are loaded or executed on the computer, the processes or functions described in the embodiments of the present application are generated in whole or in part.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another, e.g., the computer instructions may be transferred from a website, computer, server, or data center Transmit to another website, computer, server or data center through wired (such as infrared, wireless, microwave, etc.) means.
  • the computer-readable storage medium may be any available medium that a computer can access, or a data storage device such as a server or a data center that contains one or more sets of available media.
  • the usable media may be magnetic media (eg, floppy disk, hard disk, tape), optical media (eg, DVD), or semiconductor media.
  • the semiconductor medium may be a solid state drive.
  • At least one refers to one or more, and “plurality” refers to two or more.
  • At least one of the following” or similar expressions thereof refers to any combination of these items, including any combination of a single item (items) or a plurality of items (items).
  • at least one of a, b, or c can mean: a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, c can be single or multiple .
  • the size of the sequence numbers of the above-mentioned processes does not mean the order of execution.
  • the execution order of each process should be determined by its functions and internal logic, and should not be used in the embodiments of the present application.
  • the implementation process constitutes any limitation.
  • the disclosed systems, devices and methods can be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or can be integrated into another system, or some features can be ignored, or not implemented.
  • the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the devices or units may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or they may be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application can be integrated into one processing unit, each unit can exist physically alone, or two or more units can be integrated into one unit.
  • the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium.
  • the technical solution of the present application is essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product.
  • the computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of this application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program code. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请提供一种通信方法及装置，属于通信技术领域，用以解决边缘计算中漫游终端的数据路由问题。在终端漫游至VPLMN时，该终端的HPLMN分配的地址可能与VPLMN的其他终端的地址冲突。因此，边缘应用服务功能可通过VPLMN分配的第一标识来标识该终端，或者可以理解为边缘应用服务功能可通过第一标识确定第一DNS查询消息对应该终端，以便在地址可能冲突的情况下，边缘应用服务功能仍能够识别该终端，从而正确处理该终端的DNS查询消息，实现正确的数据路由，便于终端获得应用服务，如边缘服务。

Description

通信方法及装置
本申请要求于2022年04月29日提交国家知识产权局、申请号为202210469042.4、申请名称为“通信方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，尤其涉及一种通信方法及装置。
背景技术
边缘计算是一种新的网络架构，用于通过将计算资源部署在距离用户近网络边缘，以达到对用户的资源访问过程进行优化的目的，如降低用户与计算资源之间的网络传输时延。如果用户想要获得边缘服务，则需要通过边缘计算服务发现流程来发现可用的边缘应用服务器(edge application server，EAS)，如位于用户附近的EAS。例如，终端可以向边缘应用服务器发现功能(edge application server discovery function，EASDF)发起访问。EASDF可根据终端的访问，与会话管理功能(session management function，SMF)网元交互，以发现可用的EAS，并为终端提供该EAS的IP地址。终端可根据该EAS的IP地址访问该EAS，以获得边缘服务。
边缘计算业务能够支持漫游终端访问，但对于漫游终端的数据如何进行路由，是值得考虑的问题。
发明内容
本申请实施例提供一种通信方法及装置，用以解决边缘计算中漫游终端的数据路由问题。
为达到上述目的，本申请采用如下技术方案：
第一方面，提供一种通信方法。该方法包括：用户面网元接收来自终端的第一域名系统DNS查询消息，向边缘应用服务功能发送第一DNS查询消息和第一标识。终端漫游至拜访公共陆地移动网VPLMN内，第一DNS查询消息用于查询应用服务的地址，第一标识是VPLMN针对终端分配的标识。第一标识用于边缘应用服务功能确定是否存在与第一标识匹配的DNS规则。
基于第一方面所述的方法可知，在终端漫游至VPLMN时，该终端的归属公共陆地移动网络HPLMN分配的地址可能与VPLMN的其他终端的地址冲突。因此，边缘应用服务功能可通过VPLMN分配的第一标识来标识该终端，或者可以理解为边缘应用服务功能可通过第一标识确定第一DNS查询消息对应该终端，以便在地址可能冲突的情况下，边缘应用服务功能仍能够识别该终端，从而正确处理该终端的DNS查询消息，实现正确的数据路由，便于终端获得应用服务，如边缘服务。
可以理解，第一标识可用于在VPLMN内标识终端。第一标识具体可以是VPLMN，如VPLMN内的网元，针对终端的协议数据单元PDU会话分配的标识，或者说第一标识可以在VPLMN内映射到终端的PDU会话。
一种可能的设计方案中，终端的PDU会话可以为终端的家乡路由HR PDU会话。
一种可能的设计方案中，用户面网元通过终端的PDU会话，接收来自终端的第一域名系统DNS查询消息。
一种可能的设计方案中，用户面网元配置有第一用户面处理规则，该第一用户面处理规则指示：对于第一DNS查询消息，用户面网元向边缘应用服务功能发送第一DNS查询消息和第一标识。如此，用户面网元可以根据配置的第一用户面处理规则处理第一DNS查询消息，从而可避免用户面网元误操作或误处理。
一种可能的设计方案中，用户面网元向边缘应用服务功能发送第一DNS查询消息和第一标识，包括：用户面网元通过通信隧道，向边缘应用服务功能发送第一DNS查询消息和第一标识；第一标识携带在通信隧道的头部中，以便边缘应用服务功能能够通过通信隧道识别接收到的信元是第一标识。
可选地，第一标识为通信隧道的标识，即第一标识可通过复用已有信元实现，以降低实现难度。
一种可能的设计方案中，第一标识还可以携带在第一DNS查询消息中，如携带在第一DNS查询消息的预留字段中。
一种可能的设计方案中，在用户面网元向边缘应用服务功能发送第一DNS查询消息和第一标识之后，第一方面所述的方法还可以包括：用户面网元接收来自边缘应用服务功能的第一DNS响应消息和第二标识，并根据第二标识，向终端发送第一DNS响应消息。第二标识是VPLMN针对终端分配的标识，第一DNS响应消息携带有应用服务的地址。
可以理解，第二标识可用于在VPLMN内标识终端。第二标识具体可以是VPLMN，如VPLMN内的网元，针对终端的PDU会话分配的标识，或者说第二标识可以在VPLMN内映射到终端的PDU会话，也即用户面网元可以基于第二标识，将终端的消息(如第一DNS响应消息)映射到终端的PDU会话，从而向终端发送该第一DNS响应消息，以便终端能够获得应用服务，如边缘服务。
可选地，用户面网元配置有第二用户面处理规则，该第二用户面处理规则指示：对于第一DNS响应消息和第二标识，用户面网元向终端发送第一DNS响应消息。如此，用户面网元可以根据配置的第二用户面处理规则处理第一DNS响应消息，从而可避免用户面网元误操作或误处理。
可选地，用户面网元接收来自边缘应用服务功能的第一DNS响应消息和第二标识，包括：用户面网元通过通信隧道，接收来自边缘应用服务功能的第一DNS响应消息和第二标识；第二标识携带在通信隧道的头部中，以便用户面网元能够通过通信隧道识别接收到的信元是第二标识。
进一步的，第二标识为通信隧道的标识，即第二标识可通过复用已有信元实现，以降低实现难度。第二标识与第一标识可能相同，或者也可能不同，不做限定。
可选地，第二标识还可以携带在第一DNS响应消息中，如携带在第一DNS响应消息的预留字段中。
一种可能的设计方案中，在用户面网元向边缘应用服务功能发送第一DNS查询消息和第一标识之后，第一方面所述的方法还可以包括：用户面网元接收来自边缘应用服务功能的第二DNS查询消息和第二标识，并根据第二DNS查询消息和第二标识，向终端的HPLMN发送第三DNS查询消息。第二标识是VPLMN针对终端分配的标识，第二DNS 查询消息用于获取应用服务的地址，第三DNS查询消息用于请求应用服务的地址。
可以理解，第二标识可用于在VPLMN内标识终端。第二标识具体可以是VPLMN，如VPLMN内的网元，针对终端的PDU会话分配的标识，或者说第二标识可以在VPLMN内映射到终端的PDU会话，也即用户面网元可以基于第二标识，将终端的消息(如第三DNS查询消息)映射到终端的PDU会话，从而向终端的HPLMN发送第三DNS查询消息，以便终端能够获得相应的应用服务。
可选地，用户面网元配置有第三用户面处理规则，该第三用户面处理规则指示：对于来自边缘应用服务功能的第二DNS查询消息和第二标识，用户面网元向终端的HPLMN发送第三DNS查询消息。如此，用户面网元可以根据配置的第三用户面处理规则处理第二DNS查询消息，从而可避免用户面网元误操作或误处理。
可选地，用户面网元接收来自边缘应用服务功能的第二DNS查询消息和第二标识，包括：用户面网元通过通信隧道，接收来自边缘应用服务功能的第二DNS查询消息和第二标识；第二标识携带在通信隧道的头部中，以便用户面网元能够通过通信隧道识别接收到的信元是第二标识。
进一步的，第二标识为通信隧道的标识，即第二标识可通过复用已有信元实现，以降低实现难度。
可选地，第二标识还可以携带在第二DNS查询消息中，如携带在第二DNS查询消息的预留字段中。
一种可能的设计方案中，在用户面网元接收来自终端的第一DNS消息之前，第一方面所述的方法还可以包括：用户面网元确定第一标识，并向会话管理网元发送第一标识，以便VPLMN的网元，例如边缘应用服务功能能够从会话管理网元获得第一标识，从而根据第一标识识别该终端的消息，实现正确的数据路由。用户面网元可自行确定第一标识，或者根据会话管理网元的指示确定第一标识，不做限定。或者，用户面网元接收来自会话管理网元的第一标识，也即是从会话管理网元获得第一标识，从而能够在发送终端的消息时，同时发送第一标识，以便边缘应用服务功能能够根据第一标识识别该终端的消息，实现正确的数据路由。
一种可能的设计方案中，在用户面网元接收来自终端的第一DNS消息之前，第一方面所述的方法还可以包括：用户面网元确定第二标识，并向会话管理网元发送第二标识，以便VPLMN的网元，例如边缘应用服务功能能够从会话管理网元获得第二标识，从而够在发送终端的消息时，同时发送第二标识，以便用户面网元能够根据第二标识识别该终端的消息，实现正确的数据路由。用户面网元可自行确定第二标识，或者根据用户面网元的指示确定第二标识，不做限定。或者，用户面网元接收来自会话管理网元的第二标识，也即是用户面网元从会话管理网元获得第二标识，从而能够在接收第二DNS查询消息或者第一DNS响应消息时，通过第二标识识别接收到的消息为终端的消息，实现正确的数据路由。
第二方面，提供一种通信方法。该方法包括：边缘应用服务功能接收来自用户面网元的第一域名系统DNS查询消息和第一标识，并确定是否存在与第一DNS查询消息和第一标识匹配的DNS消息处理规则。第一标识是拜访公共陆地移动网VPLMN针对终端分配的标识，终端漫游至VPLMN内，第一DNS查询消息用于查询应用服务的地址。
一种可能的设计方案中，边缘应用服务功能接收来自用户面网元的第一DNS查询消息和第一标识，包括：边缘应用服务功能通过通信隧道，接收来自用户面网元的第一DNS查询消息和第一标识；第一标识携带在通信隧道的头部中。
可选地，第一标识为通信隧道的标识。
一种可能的设计方案中，第二方面所述的方法还可以包括：在存在与第一DNS查询消息和第一标识匹配的DNS消息处理规则的情况下，边缘应用服务功能向用户面网元发送第一DNS响应消息和第二标识。第二标识是VPLMN针对终端分配的标识，第一DNS响应消息携带有应用服务的地址。
其中，DNS消息处理规则可保存在DNS上下文中，DNS上下文还可以包括第一标识。这种情况下，边缘应用服务功能可以根据第一标识，确定与该第一标识匹配的DNS上下文，如包含第一标识的上下文。边缘应用服务功能可以确定该DNS上下文中是否存在与第一DNS查询消息匹配的DNS消息处理规则。此时，如果第一DNS查询消息中的全地址域名FQDN与DNS上下文中某个DNS消息处理规则中的FQDN匹配，则表示存在与第一DNS查询消息匹配的DNS消息处理规则，也即存在与第一DNS查询消息和第一标识匹配的DNS消息处理规则。如果第一DNS查询消息中的FQDN与DNS上下文中任一个DNS消息处理规则中的FQDN都不匹配，则表示不存在与第一DNS查询消息匹配的DNS消息处理规则，也即不存在与第一DNS查询消息和第一标识匹配的DNS消息处理规则。
可以理解，由于第一DNS查询消息中的FQDN与该DNS消息处理规则中的FQDN匹配匹配，表示终端请求的应用服务的地址为边缘应用服务的地址。因此，边缘应用服务功能可通过第一DNS响应消息为终端提供边缘应用服务的地址，以便终端能够获得边缘服务。
可选地，边缘应用服务功能配置有DNS消息处理规则，该DNS消息处理规则指示：边缘应用服务功能向用户面网元发送第一DNS响应消息和第二标识。如此，边缘应用服务功能可以根据配置的DNS消息处理规则处理第一DNS响应消息，从而可避免边缘应用服务功能误操作或误处理。
可选地，边缘应用服务功能向用户面网元发送第一DNS响应消息和第二标识，包括：边缘应用服务功能通过通信隧道，向用户面网元发送第一DNS响应消息和第二标识；第二标识携带在通信隧道的头部中。
进一步的，第二标识为通信隧道的标识。
一种可能的设计方案中，第二方面所述的方法还可以包括：在不存在与第一DNS查询消息和第一标识匹配的DNS消息处理规则的情况下，边缘应用服务功能向用户面网元发送第二DNS查询消息和第二标识；第二标识是VPLMN针对终端分配的标识，第二DNS查询消息用于获取应用服务的地址。
可以理解，由于第一DNS查询消息中的FQDN与任一个DNS消息处理规则中的FQDN都不匹配，表示终端请求的应用服务的地址并不是边缘应用服务的地址，而可能是其他应用服务的地址。此时，边缘应用服务功能可通过用户面网元向终端的HPLMN发送第二DNS查询消息，以便终端最终能够获得相应的应用服务。
可选地，边缘应用服务功能向用户面网元发送第二DNS查询消息和第二标识，包括：边缘应用服务功能通过通信隧道，向用户面网元发送第二DNS查询消息和第二标识。第 二标识携带在通信隧道的头部中。
可选地，第二标识为通信隧道的标识。
一种可能的设计方案中，在边缘应用服务功能接收来自用户面网元向的第一DNS查询消息和第一标识之前，第二方面所述的方法还可以包括：边缘应用服务功能确定第一标识，并向会话管理网元发送第一标识。边缘应用服务功能可自行确定第一标识，或者根据会话管理网元的指示确定第一标识，不做限定。或者，边缘应用服务功能接收来自会话管理网元的第一标识。
一种可能的设计方案中，在边缘应用服务功能接收来自用户面网元向的第一DNS查询消息和第一标识之前，第二方面所述的方法还可以包括：边缘应用服务功能确定第二标识，并向会话管理网元发送第二标识。边缘应用服务功能可自行确定第二标识，或者根据会话管理网元的指示确定第二标识，不做限定。或者，边缘应用服务功能接收来自会话管理网元的第二标识。
此外，第二方面所述的通信方法的其他技术效果可以参考第一方面所述的通信方法的技术效果，此处不再赘述。
第三方面，提供一种通信方法。该方法包括：会话管理网元确定第一标识，向用户面网元发送第一标识。第一标识是终端对应的拜访公共陆地移动网VPLMN内的标识，终端漫游至VPLMN内。
一种可能的设计方案中，第三方面所述的方法还可以包括：会话管理网元向边缘应用服务功能发送第一标识。
一种可能的设计方案中，会话管理网元在终端的协议数据单元PDU会话建立过程中，确定第一标识。可选地，终端的PDU会话为终端的家乡路由HR PDU会话。
一种可能的设计方案中，第三方面所述的方法还可以包括：会话管理网元确定第二标识，向用户面网元发送第二标识。
可选地，第三方面所述的方法还可以包括：会话管理网元向边缘应用服务功能发送第二标识。
一种可能的设计方案中，会话管理网元在终端的PDU会话建立过程中，确定第二标识。可选地，终端的PDU会话为终端的HR PDU会话。
此外，第三方面所述的通信方法的其他技术效果可以参考第一方面所述的通信方法的技术效果，此处不再赘述。
第四方面，提供一种通信方法。该方法包括：用户面网元接收来自终端的第一域名系统DNS查询消息，将第一DNS查询消息的源地址由终端的地址替换为第一地址，以得到第二DNS查询消息，从而向边缘应用服务功能发送第二DNS查询消息。其中，终端漫游至拜访公共陆地移动网VPLMN内，第一DNS查询消息用于查询应用服务的地址，第一地址是VPLMN针对终端分配的地址。
基于第四方面所述的方法可知，在终端漫游至VPLMN时，该终端的归属公共陆地移动网络HPLMN分配的地址可能与VPLMN的其他终端的地址冲突。因此，边缘应用服务功能可使用VPLMN针对该终端分配的第一地址来标识该终端的DNS查询消息，以避免出现地址冲突，实现正确的数据路由，便于终端获得应用服务，如边缘服务。
可以理解，第一地址具体可以是VPLMN，如VPLMN内的网元，针对终端的协议数 据单元PDU会话分配的标识，或者说第一地址可以映射到终端的PDU会话。
一种可能的设计方案中，用户面网元通过终端的PDU会话，接收来自终端的第一域名系统DNS查询消息。
一种可能的设计方案中，终端的PDU会话可以为终端的家乡路由HR PDU会话。
一种可能的设计方案中，用户面网元配置有第一用户面处理规则，该第一用户面处理规则指示：对于第一DNS查询消息，用户面网元将第一DNS查询消息的源地址由终端的地址替换为第一地址，以得到第二DNS查询消息，并向边缘应用服务功能发送第二DNS查询消息。如此，用户面网元可根据配置的第一用户面处理规则处理第一DNS查询消息，从而可避免用户面网元误操作或误处理。一种可能的设计方案中，在用户面网元向边缘应用服务功能发送第二DNS查询消息之后，第四方面的方法还可以包括：用户面网元接收来自边缘应用服务功能的第一DNS响应消息，该第一DNS响应消息携带有应用服务的地址。用户面网元将第一DNS响应消息的目的地址由第一地址替换为终端的地址，以得到第二DNS响应消息，从而向终端发送第二DNS响应消息，以便终端能够获得应用服务。
可选地，用户面网元配置有第二用户面处理规则，该第二用户面处理规则指示：对于第一DNS响应消息，用户面网元将第一DNS响应消息的目的地址由第一地址替换为终端的地址，以得到第二DNS响应消息，并向边缘应用服务功能发送第二DNS响应消息。
一种可能的设计方案中，在用户面网元向边缘应用服务功能发送第二DNS查询消息之后，第四方面的方法还可以包括：用户面网元接收来自边缘应用服务功能的第三DNS查询消息，将第三DNS查询消息的目的地址由第二地址替换为HPLMN内DNS服务器的地址，以得到第四DNS查询消息，从而向HPLMN发送第四DNS查询消息。其中，第二地址是VPLMN针对终端分配的地址。第二地址具体可以是VPLMN针对终端的协议数据单元PDU会话分配的标识，或者说第二地址可以映射到终端的PDU会话，也即用户面网元可以基于第二地址，将终端的消息映射到终端的PDU会话。第二地址与第一地址可以不同。
可选地，用户面网元配置有第三用户面处理规则，该第三用户面处理规则指示：对于第三DNS查询消息，用户面网元将第三DNS查询消息的目的地址由第二地址替换为HPLMN内DNS服务器的地址，以得到第四DNS查询消息，并向边缘应用服务功能发送第四DNS查询消息。
一种可能的设计方案中，在用户面网元接收来自终端的第一DNS消息之前，第四方面所述的方法还可以包括：用户面网元确定第一地址，并向会话管理网元发送第一地址。用户面网元可自行确定第一地址，或者根据会话管理网元的指示确定第一地址，不做限定。或者，用户面网元接收来自会话管理网元的第一地址。
一种可能的设计方案中在用户面网元接收来自终端的第一DNS消息之前，第四方面所述的方法还可以包括：用户面网元确定第二地址，并向会话管理网元发送第二地址。用户面网元可自行确定第二地址，或者根据会话管理网元的指示确定第二地址，不做限定。或者，用户面网元接收来自会话管理网元的第二地址。
此外，第四方面所述的通信方法的其他技术效果可以参考第一方面所述的通信方法的技术效果，此处不再赘述。
第五方面，提供一种通信方法。该方法包括：会话管理网元确定第一地址，向边缘应 用服务功能发送第一地址。第一地址是拜访公共陆地移动网VPLMN针对终端分配的地址，终端漫游至VPLMN内。
一种可能的设计方案中，第五方面所述的方法还可以包括：会话管理网元向用户面网元发送第一地址。
一种可能的设计方案中，会话管理网元在终端的协议数据单元PDU会话建立过程中，确定第一地址。可选地，终端的PDU会话为终端的家乡路由HR PDU会话。
一种可能的设计方案中，第五方面所述的方法还可以包括：会话管理网元确定第二地址，向边缘应用服务功能发送第二地址。第二地址是VPLMN针对终端分配的地址，第二地址与第一地址不同。
可选地，第五方面所述的方法还可以包括：会话管理网元向用户面网元发送第二地址。
一种可能的设计方案中，会话管理网元在终端的PDU会话建立过程中，确定第二地址。可选地，终端的PDU会话为终端的HR PDU会话。
此外，第五方面所述的通信方法的其他技术效果可以参考第四方面所述的通信方法的技术效果，此处不再赘述。
第六方面，提供一种通信装置。该装置包括：接收模块和发送模块。其中，接收模块，用于接收来自终端的第一域名系统DNS查询消息，发送模块，用于向边缘应用服务功能发送第一DNS查询消息和第一标识。终端漫游至拜访公共陆地移动网VPLMN内，第一DNS查询消息用于查询应用服务的地址，第一标识是VPLMN针对终端分配的标识。第一标识用于边缘应用服务功能确定是否存在与第一标识匹配的DNS规则。
可以理解，第一标识可用于在VPLMN内标识终端。第一标识具体可以是VPLMN，如VPLMN内的网元，针对终端的协议数据单元PDU会话分配的标识，或者说第一标识可以在VPLMN内映射到终端的PDU会话。
一种可能的设计方案中，终端的PDU会话可以为终端的家乡路由HR PDU会话。
一种可能的设计方案中，接收模块，用于通过终端的PDU会话，接收来自终端的第一域名系统DNS查询消息。
一种可能的设计方案中，第六方面所述的通信装置配置有第一用户面处理规则，该第一用户面处理规则指示：对于第一DNS查询消息，该装置向边缘应用服务功能发送第一DNS查询消息和第一标识。
一种可能的设计方案中，发送模块，用于通过通信隧道，向边缘应用服务功能发送第一DNS查询消息和第一标识；第一标识携带在通信隧道的头部中。
可选地，第一标识为通信隧道的标识。
一种可能的设计方案中，第一标识还可以携带在第一DNS查询消息中，如携带在第一DNS查询消息的预留字段中。
一种可能的设计方案中，接收模块，还用于在发送模块向边缘应用服务功能发送第一DNS查询消息和第一标识之后，接收来自边缘应用服务功能的第一DNS响应消息和第二标识。第六方面所述的通信装置还包括：处理模块；处理模块，用于根据第二标识，控制发送模块向终端发送第一DNS响应消息。第二标识是VPLMN针对终端分配的标识，第一DNS响应消息携带有应用服务的地址。
可以理解，第二标识可用于在VPLMN内标识终端。第二标识具体可以是VPLMN， 如VPLMN内的网元，针对终端的PDU会话分配的标识，或者说第二标识可以在VPLMN内映射到终端的PDU会话。
可选地，第六方面所述的通信装置配置有第二用户面处理规则，该第二用户面处理规则指示：对于第一DNS响应消息和第二标识，该装置向终端发送第一DNS响应消息。
可选地，接收模块，用于通过通信隧道，接收来自边缘应用服务功能的第一DNS响应消息和第二标识；第二标识携带在通信隧道的头部中。
进一步的，第二标识为通信隧道的标识。第二标识与第一标识可能相同，或者也可能不同，不做限定。
可选地，第二标识还可以携带在第一DNS响应消息中，如携带在第一DNS响应消息的预留字段中。
一种可能的设计方案中，接收模块，还用于在发送模块向边缘应用服务功能发送第一DNS查询消息和第一标识之后，接收来自边缘应用服务功能的第二DNS查询消息和第二标识。第六方面所述的通信装置还包括：处理模块；该处理模块，用于根据第二DNS查询消息和第二标识，控制发送模块向终端的HPLMN发送第三DNS查询消息。第二标识是VPLMN针对终端分配的标识，第二DNS查询消息用于获取应用服务的地址，第三DNS查询消息用于请求应用服务的地址。
可以理解，第二标识可用于在VPLMN内标识终端。第二标识具体可以是VPLMN，如VPLMN内的网元，针对终端的PDU会话分配的标识，或者说第二标识可以在VPLMN内映射到终端的PDU会话。
可选地，第六方面所述的通信装置配置有第三用户面处理规则，该第三用户面处理规则指示：对于来自边缘应用服务功能的第二DNS查询消息和第二标识，该装置向终端的HPLMN发送第三DNS查询消息。
可选地，接收模块，用于通过通信隧道，接收来自边缘应用服务功能的第二DNS查询消息和第二标识；第二标识携带在通信隧道的头部中。
进一步的，第二标识为通信隧道的标识。第二标识与第一标识可能相同，或者也可能不同，不做限定。
可选地，第二标识还可以携带在第二DNS查询消息中，如携带在第二DNS查询消息的预留字段中。
一种可能的设计方案中，第六方面所述的通信装置还包括：处理模块；该处理模块，用于在接收模块接收来自终端的第一DNS消息之前，确定第一标识，并控制发送模块向会话管理网元发送第一标识。或者，接收模块，用于接收来自会话管理网元的第一标识。
一种可能的设计方案中，第六方面所述的通信装置还包括：处理模块；该处理模块，用于在接收模块接收来自终端的第一DNS消息之前，确定第二标识，并控制发送模块向会话管理网元发送第二标识。或者，接收模块，用于接收来自会话管理网元的第二标识。
可选地，发送模块和接收模块也可以集成为收发模块，用于实现第六方面所述的通信装置的收发功能。
可选地，第六方面所述的通信装置还可以包括存储模块，该存储模块存储有程序或指令。当该处理模块执行该程序或指令时，使得该通信装置可以执行第一方面所述的通信方法。
需要说明的是，第六方面所述的通信装置可以是网络设备，如用户面网元，也可以是可设置于网络设备中的芯片(系统)或其他部件或组件，还可以是包含网络设备的装置，本申请对此不做限定。
此外，第六方面所述的通信装置的技术效果可以参考第一方面所述的通信方法的技术效果，此处不再赘述。
第七方面，提供一种通信装置。该装置包括：收发模块和处理模块。其中，收发模块，用于接收来自用户面网元的第一域名系统DNS查询消息和第一标识，处理模块，用于确定是否存在与第一DNS查询消息和第一标识匹配的DNS消息处理规则。第一标识是拜访公共陆地移动网VPLMN针对终端分配的标识，终端漫游至VPLMN内，第一DNS查询消息用于查询应用服务的地址。
一种可能的设计方案中，收发模块，用于通过通信隧道，接收来自用户面网元的第一DNS查询消息和第一标识；第一标识携带在通信隧道的头部中。
可选地，第一标识为通信隧道的标识。
一种可能的设计方案中，在存在与第一DNS查询消息和第一标识匹配的DNS消息处理规则的情况下，收发模块，用于向用户面网元发送第一DNS响应消息和第二标识。第二标识是VPLMN针对终端分配的标识，第一DNS响应消息携带有应用服务的地址。
可选地，第七方面所述的通信装置配置有DNS消息处理规则，该DNS消息处理规则指示：该装置向用户面网元发送第一DNS响应消息和第二标识。
可选地，收发模块，用于通过通信隧道，向用户面网元发送第一DNS响应消息和第二标识；第二标识携带在通信隧道的头部中。
进一步的，第二标识为通信隧道的标识。
一种可能的设计方案中，在不存在与第一DNS查询消息和第一标识匹配的DNS消息处理规则的情况下，收发模块，用于向用户面网元发送第二DNS查询消息和第二标识；第二标识是VPLMN针对终端分配的标识，第二DNS查询消息用于获取应用服务的地址。
可选地，收发模块，用于通过通信隧道，向用户面网元发送第二DNS查询消息和第二标识。第二标识携带在通信隧道的头部中。
可选地，第二标识为通信隧道的标识。
一种可能的设计方案中，处理模块，还用于在收发模块接收来自用户面网元向的第一DNS查询消息和第一标识之前，确定第一标识，并控制收发模块向会话管理网元发送第一标识。或者，收发模块，用于接收来自会话管理网元的第一标识。
一种可能的设计方案中，处理模块，还用于在收发模块接收来自用户面网元向的第一DNS查询消息和第一标识之前，确定第二标识，并控制收发模块向会话管理网元发送第二标识。或者，收发模块，用于接收来自会话管理网元的第二标识。
可选地，收发模块也可以包括发送模块和接收模块，发送模块用于实现第七方面所述的通信装置的发送功能，接收模块用于实现第七方面所述的通信装置的接收功能。
可选地，第七方面所述的通信装置还可以包括存储模块，该存储模块存储有程序或指令。当该处理模块执行该程序或指令时，使得该通信装置可以执行第二方面所述的通信方法。
需要说明的是，第七方面所述的通信装置可以是网络设备，如边缘应用服务功能，也 可以是可设置于网络设备中的芯片(系统)或其他部件或组件，还可以是包含网络设备的装置，本申请对此不做限定。
此外，第七方面所述的通信装置的其他技术效果可以参考第二方面所述的通信方法的技术效果，此处不再赘述。
第八方面，提供一种通信装置。该装置包括：收发模块和处理模块。其中，处理模块，用于确定第一标识；收发模块，用于向用户面网元发送第一标识。第一标识是终端对应的拜访公共陆地移动网VPLMN内的标识，终端漫游至VPLMN内。
一种可能的设计方案中，收发模块，用于向边缘应用服务功能发送第一标识。
一种可能的设计方案中，处理模块，用于在终端的协议数据单元PDU会话建立过程中，确定第一标识。可选地，终端的PDU会话为终端的家乡路由HR PDU会话。
一种可能的设计方案中，处理模块，用于确定第二标识；收发模块，用于向用户面网元发送第二标识。
可选地，收发模块，用于边缘应用服务功能发送第二标识。
可选地，收发模块也可以包括发送模块和接收模块，发送模块用于实现第八方面所述的通信装置的发送功能，接收模块用于实现第八方面所述的通信装置的接收功能。
可选地，第八方面所述的通信装置还可以包括存储模块，该存储模块存储有程序或指令。当该处理模块执行该程序或指令时，使得该通信装置可以执行第三方面所述的通信方法。
需要说明的是，第八方面所述的通信装置可以是网络设备，如会话管理网元，也可以是可设置于网络设备中的芯片(系统)或其他部件或组件，还可以是包含网络设备的装置，本申请对此不做限定。
此外，第八方面所述的通信方法的其他技术效果可以参考第三方面所述的通信方法的技术效果，此处不再赘述。
第九方面，提供一种通信装置。该方法包括：收发模块和处理模块。收发模块，用于接收来自终端的第一域名系统DNS查询消息，处理模块，用于将第一DNS查询消息的源地址由终端的地址替换为第一地址，以得到第二DNS查询消息，从而控制收发模块向边缘应用服务功能发送第二DNS查询消息。其中，终端漫游至拜访公共陆地移动网VPLMN内，第一DNS查询消息用于查询应用服务的地址，第一地址是VPLMN针对终端分配的地址。
可以理解，第一地址具体可以是VPLMN，如VPLMN内的网元，针对终端的协议数据单元PDU会话分配的标识，或者说第一地址可以映射到终端的PDU会话。
一种可能的设计方案中，收发模块，用于通过终端的PDU会话，接收来自终端的第一域名系统DNS查询消息。
一种可能的设计方案中，终端的PDU会话可以为终端的家乡路由HR PDU会话。
一种可能的设计方案中，第九方面所述的通信装置配置有第一用户面处理规则，该第一用户面处理规则指示：对于第一DNS查询消息，该装置将第一DNS查询消息的源地址由终端的地址替换为第一地址，以得到第二DNS查询消息，并向边缘应用服务功能发送第二DNS查询消息。
一种可能的设计方案中，收发模块，用于在向边缘应用服务功能发送第二DNS查询 消息之后，接收来自边缘应用服务功能的第一DNS响应消息，该第一DNS响应消息携带有应用服务的地址。处理模块，用于将第一DNS响应消息的目的地址由第一地址替换为终端的地址，以得到第二DNS响应消息，从而控制收发向终端发送第二DNS响应消息。
可选地，第九方面所述的通信装置配置有第二用户面处理规则，该第二用户面处理规则指示：对于第一DNS响应消息，该装置将第一DNS响应消息的目的地址由第一地址替换为终端的地址，以得到第二DNS响应消息，并向边缘应用服务功能发送第二DNS响应消息。
一种可能的设计方案中，收发模块，用于在向边缘应用服务功能发送第二DNS查询消息之后，接收来自边缘应用服务功能的第三DNS查询消息。处理模块，用于将第三DNS查询消息的目的地址由第二地址替换为HPLMN内DNS服务器的地址，以得到第四DNS查询消息，从而控制收发模块向HPLMN发送第四DNS查询消息。其中，第二地址是VPLMN针对终端分配的地址。第二地址具体可以是VPLMN针对终端的协议数据单元PDU会话分配的标识，或者说第二地址可以映射到终端的PDU会话，也即用户面网元可以基于第二地址，将终端的消息映射到终端的PDU会话。第二地址与第一地址可以不同。
可选地，第九方面所述的通信装置配置有第三用户面处理规则，该第三用户面处理规则指示：对于第三DNS查询消息，该装置将第三DNS查询消息的目的地址由第二地址替换为HPLMN内DNS服务器的地址，以得到第四DNS查询消息，并向边缘应用服务功能发送第四DNS查询消息。
一种可能的设计方案中，处理模块，用于在收发模块接收来自终端的第一DNS消息之前，用户面网元确定第一地址，并控制收发模块向会话管理网元发送第一地址。或者，收发模块，用于接收来自会话管理网元的第一地址。
一种可能的设计方案中，处理模块，用于在收发模块接收来自终端的第一DNS消息之前，确定第二地址，并控制收发模块向会话管理网元发送第二地址。或者，收发模块，用于接收来自会话管理网元的第二地址。
可选地，收发模块也可以包括发送模块和接收模块，发送模块用于实现第九方面所述的通信装置的发送功能，接收模块用于实现第九方面所述的通信装置的接收功能。
可选地，第九方面所述的通信装置还可以包括存储模块，该存储模块存储有程序或指令。当该处理模块执行该程序或指令时，使得该通信装置可以执行第四方面所述的通信方法。
需要说明的是，第九方面所述的通信装置可以是网络设备，如用户面网元，也可以是可设置于网络设备中的芯片(系统)或其他部件或组件，还可以是包含网络设备的装置，本申请对此不做限定。
此外，第九方面所述的通信装置的其他技术效果可以参考第四方面所述的通信方法的技术效果，此处不再赘述。
第十方面，提供一种通信装置。该装置包括：收发模块和处理模块。其中，处理模块，用于确定第一地址，收发模块，用于向边缘应用服务功能发送第一地址。第一地址是拜访公共陆地移动网VPLMN针对终端分配的地址，终端漫游至VPLMN内。
一种可能的设计方案中，收发模块，用于向用户面网元发送第一地址。
一种可能的设计方案中，处理模块，用于在终端的协议数据单元PDU会话建立过程 中，确定第一地址。可选地，终端的PDU会话为终端的家乡路由HR PDU会话。
一种可能的设计方案中，处理模块，用于确定第二地址，收发模块，用于向边缘应用服务功能发送第二地址。第二地址是VPLMN针对终端分配的地址，第二地址与第一地址不同。
可选地，收发模块，用于向用户面网元发送第二地址。
一种可能的设计方案中，处理模块，用于在终端的PDU会话建立过程中，确定第二地址。可选地，终端的PDU会话为终端的HR PDU会话。
可选地，收发模块也可以包括发送模块和接收模块，发送模块用于实现第十方面所述的通信装置的发送功能，接收模块用于实现第十方面所述的通信装置的接收功能。
可选地，第十方面所述的通信装置还可以包括存储模块，该存储模块存储有程序或指令。当该处理模块执行该程序或指令时，使得该通信装置可以执行第五方面所述的通信方法。
需要说明的是，第十方面所述的通信装置可以是网络设备，如会话管理网元，也可以是可设置于网络设备中的芯片(系统)或其他部件或组件，还可以是包含网络设备的装置，本申请对此不做限定。
此外，第十方面所述的通信方法的其他技术效果可以参考第五方面所述的通信方法的技术效果，此处不再赘述。
第十一方面，提供一种通信装置。该通信装置包括：处理器，该处理器用于执行第一方面至第五方面中任意一种可能的实现方式所述的通信方法。
在一种可能的设计方案中，第十一方面所述的通信装置还可以包括收发器。该收发器可以为收发电路或接口电路。该收发器可以用于第七方面所述的通信装置与其他通信装置通信。
在一种可能的设计方案中，第十一方面所述的通信装置还可以包括存储器。该存储器可以与处理器集成在一起，也可以分开设置。该存储器可以用于存储第一方面至第五方面中任一方面所述的通信方法所涉及的计算机程序和/或数据。
在本申请中，第十一方面所述的通信装置可以为第一方面至第五方面中任一方面所述的装置，或者可设置于该装置中的芯片(系统)或其他部件或组件，或者包含该装置的装置。
此外，第十一方面所述的通信装置的技术效果可以参考第一方面至第五方面中任意一种实现方式所述的通信方法的技术效果，此处不再赘述。
第十二方面，提供一种通信装置。该通信装置包括：处理器，该处理器与存储器耦合，该处理器用于执行存储器中存储的计算机程序，以使得该通信装置执行第一方面至第五方面中任意一种可能的实现方式所述的通信方法。
在一种可能的设计方案中，第十二方面所述的通信装置还可以包括收发器。该收发器可以为收发电路或接口电路。该收发器可以用于第十二方面所述的通信装置与其他通信装置通信。
在本申请中，第十二方面所述的通信装置可以为第一方面至第五方面中任一方面所述的装置，或者可设置于该装置中的芯片(系统)或其他部件或组件，或者包含该装置的装置。
此外，第十二方面所述的通信装置的技术效果可以参考第一方面至第五方面中任意一种实现方式所述的通信方法的技术效果，此处不再赘述。
第十三方面，提供了一种通信装置，包括：处理器和存储器；该存储器用于存储计算机程序，当该处理器执行该计算机程序时，以使该通信装置执行第一方面至第五方面中的任意一种实现方式所述的通信方法。
在一种可能的设计方案中，第十三方面所述的通信装置还可以包括收发器。该收发器可以为收发电路或接口电路。该收发器可以用于第十三方面所述的通信装置与其他通信装置通信。
在本申请中，第十三方面所述的通信装置可以为第一方面至第五方面中任一方面所述的装置，或者可设置于该装置中的芯片(系统)或其他部件或组件，或者包含该装置的装置。
此外，第十三方面所述的通信装置的技术效果可以参考第一方面至第五方面中任意一种实现方式所述的通信方法的技术效果，此处不再赘述。
第十四方面，提供了一种通信装置，包括：处理器；该处理器用于与存储器耦合，并读取存储器中的计算机程序之后，根据该计算机程序执行如第一方面至第五方面中的任意一种实现方式所述的通信方法。
在一种可能的设计方案中，第十四方面所述的通信装置还可以包括收发器。该收发器可以为收发电路或接口电路。该收发器可以用于第十四方面所述的通信装置与其他通信装置通信。
在本申请中，第十四方面所述的通信装置可以为第一方面至第五方面中任一方面所述的装置，或者可设置于该装置中的芯片(系统)或其他部件或组件，或者包含该装置的装置。
此外，第十四方面所述的通信装置的技术效果可以参考第一方面至第五方面中任意一种实现方式所述的通信方法的技术效果，此处不再赘述。
第十五方面，提供一种通信系统。该通信系统包括：第一方面所述的用户面网元、第二方面所述的边缘应用服务功能、以及第三方面所述的会话管理网元；或者，该通信系统包括：第四方面所述的用户面网元、以及第五方面所述的会话管理网元。
第十六方面，提供一种计算机可读存储介质，包括：计算机程序或指令；当该计算机程序或指令在计算机上运行时，使得该计算机执行第一方面至第五方面中任意一种可能的实现方式所述的通信方法。
第十七方面，提供一种计算机程序产品，包括计算机程序或指令，当该计算机程序或指令在计算机上运行时，使得该计算机执行第一方面至第五方面中任意一种可能的实现方式所述的通信方法。
附图说明
图1为5GS的非漫游架构示意图；
图2为边缘计算的架构示意图；
图3为边缘计算服务发现的流程示意图；
图4为5GS的漫游架构示意图；
图5为5GS的漫游架构中边缘计算的架构示意图；
图6为本申请实施例提供的一种通信系统的架构示意图；
图7为本申请实施例提供的一种通信方法的流程示意图一；
图8为本申请实施例提供的一种通信方法的应用场景示意图一；
图9为本申请实施例提供的一种通信方法的流程示意图二；
图10为本申请实施例提供的一种通信方法的流程示意图三；
图11为本申请实施例提供的一种通信方法的应用场景示意图二；
图12为本申请实施例提供的一种通信方法的流程示意图四；
图13为本申请实施例提供的一种通信装置的结构示意图一；
图14为本申请实施例提供的一种通信装置的结构示意图二；
图15为本申请实施例提供的一种通信装置的结构示意图三。
具体实施方式
方便理解，下面先介绍本申请实施例所涉及的技术术语。
1、第五代(5th generation，5G)移动通信系统(简称5G系统(5G system，5GS))：
图1为5GS的非漫游架构示意图。如图1所示，5GS包括：接入网(access network，AN)和核心网(core network，CN)，还可以包括：终端。
上述终端可以为具有收发功能的终端，或为可设置于该终端的芯片或芯片系统。该终端也可以称为用户装置(uesr equipment，UE)、接入终端、用户单元(subscriber unit)、用户站、移动站(mobile station，MS)、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。本申请的实施例中的终端可以是手机(mobile phone)、蜂窝电话(cellular phone)、智能电话(smart phone)、平板电脑(Pad)、无线数据卡、个人数字助理电脑(personal digital assistant，PDA)、无线调制解调器(modem)、手持设备(handset)、膝上型电脑(laptop computer)、机器类型通信(machine type communication，MTC)终端、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端、增强现实(augmented reality，AR)终端、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端、车载终端、具有终端功能的路边单元(road side unit，RSU)等。本申请的终端还可以是作为一个或多个部件或者单元而内置于车辆的车载模块、车载模组、车载部件、车载芯片或者车载单元。
上述AN用于实现接入有关的功能，可以为特定区域的授权用户提供入网功能，并能够根据用户的级别，业务的需求等确定不同质量的传输链路以传输用户数据。AN在终端与CN之间转发控制信号和用户数据。AN可以包括：接入网设备，也可以称为无线接入网设备(radio access network，RAN)设备。CN主要负责维护移动网络的签约数据，为终端提供会话管理、移动性管理、策略管理以及安全认证等功能。CN主要包括如下网元：用户面功能(user plane function，UPF)网元、认证服务功能(authentication server function，AUSF)网元、接入和移动性管理功能(access and mobility management function，AMF)网元、会话管理功能(session management function，SMF)网元、网络切片选择功能(network slice selection function，NSSF)网元、网络开放功能(network exposure function，NEF)网元、网络功能仓储功能(NF repository function，NRF)网元、策略控制功能(policy control  function，PCF)网元、统一数据管理(unified data management，UDM)网元、统一数据存储(unified data repository，UDR)、以及应用功能(application function，AF)。
如图1所示，UE通过RAN设备接入5G网络，UE通过N1接口(简称N1)与AMF网元通信；RAN网元通过N2接口(简称N2)与AMF网元通信；RAN网元通过N3接口简称N3与UPF网元通信；SMF通过N4接口(简称N4)与UPF网元通信，UPF网元通过N6接口(简称N6)接入数据网络(data network，DN)。此外，图1所示的AUSF网元、AMF网元、SMF网元、NSSF网元、NEF网元、NRF网元、PCF网元、UDM网元、UDR网元或者AF等控制面功能采用服务化接口进行交互。比如，AUSF网元对外提供的服务化接口为Nausf；AMF网元对外提供的服务化接口为Namf；SMF网元对外提供的服务化接口为Nsmf；NSSF对外提供的服务化接口为Nnssf；NEF网元对外提供的服务化接口为Nnef；NRF网元对外提供的服务化接口为Nnrf；PCF网元对外提供的服务化接口为Npcf；UDM网元对外提供的服务化接口为Nudm；UDR网元对外提供的服务化接口为Nudr；AF对外提供的服务化接口为Naf。此外，如图1所示，NSSF网元、AUSF网元、UDM网元、UE、RAN网元、PCF网元以及SMF网元等网元，还都能够与AMF网元通信。AUSF网元还能与UDM网元通信，UDM还能与SMF网元通信，SMF网元除了能够与AMF网元和UDM网元通信外，还能与UPF网元和PCF网元通信。PCF网元还能与AF和NEF网元通信。NEF网元还能与AF通信。UPF网元能够与RAN设备以及DN通信。如图1所示，两个网元之间的“Nxx”表示这两个网元之间的接口。例如，N22表示NSSF网元与AMF网元之间的接口，N12表示AUSF网元与AMF网元之间的接口，N8表示UDM网元与AMF网元之间的接口，在此不再一一列举等。
RAN设备可以是为终端提供接入的设备。例如，RAN设备可以包括：下一代移动通信系统，例如6G的接入网设备，例如6G基站，或者在下一代移动通信系统中，该网络设备也可以有其他命名方式，其均涵盖在本申请实施例的保护范围以内，本申请对此不做任何限定。或者，RAN设备也可以包括5G，如新空口(new radio，NR)系统中的gNB，或，5G中的基站的一个或一组(包括多个天线面板)天线面板，或者，还可以为构成gNB、传输点(transmission and reception point，TRP或者transmission point，TP)或传输测量功能(transmission measurement function，TMF)的网络节点，如基带单元(building base band unit，BBU)，或，集中单元(centralized unit，CU)或分布单元(distributed unit，DU)、具有基站功能的RSU，或者有线接入网关，或者5G的核心网网元。或者，RAN设备还可以包括无线保真(wireless fidelity，WiFi)系统中的接入点(access point，AP)，无线中继节点、无线回传节点、各种形式的宏基站、微基站(也称为小站)、中继站、接入点、可穿戴设备、车载设备等等。
UPF网元主要负责用户数据处理(转发、接收、计费等)。例如，UPF网元可以接收来自数据网络(data network，DN)的用户数据，通过接入网设备向终端转发该用户数据。UPF网元也可以通过接入网设备接收来自终端的用户数据，并向DN转发该用户数据。DN网元指的是为用户提供数据传输服务的运营商网络。例如互联网协议(internet protocol，IP)多媒体业务(IP multi-media srvice，IMS)、互联网(internet)等。DN可以为运营商外部网络，也可以为运营商控制的网络，用于向终端设备提供业务服务。
AUSF网元主要用于执行终端的安全认证。
AMF网元主要用于移动网络中的移动性管理。例如用户位置更新、用户注册网络、用户切换等。
SMF网元主要用于移动网络中的会话管理。例如会话建立、修改、释放。具体功能例如为用户分配互联网协议(internet protocol，IP)地址，选择提供数据包转发功能的UPF网元等。
PCF网元主要支持提供统一的策略框架来控制网络行为，提供策略规则给控制层网络功能，同时负责获取与策略决策相关的用户签约信息。PCF网元可以向AMF网元、SMF网元提供策略，例如服务质量(quality of service，QoS)策略、切片选择策略等。
NSSF网元主要用于为终端选择网络切片。
NEF网元主要用于支持能力和事件的开放。
UDM网元主要用于存储用户数据，例如签约数据、鉴权/授权数据等。
UDR网元主要用于存储结构化数据，存储的内容包括签约数据和策略数据、对外暴露的结构化数据和应用相关的数据。
AF主要支持与CN交互来提供服务，例如影响数据路由决策、策略控制功能或者向网络侧提供第三方的一些服务。
2、边缘计算(edge omputing)：
边缘计算是一种新的网络架构，用于通过将计算资源部署在距离用户近网络边缘，以达到对用户的资源访问过程进行优化的目的，如降低用户与计算资源之间的网络传输时延。如图2所示，5GS也引入了边缘计算。边缘应用服务器(edge application server，EAS)通常部署在DN本地部分(local part of the DN，LDN)，也可以称为该DN的边缘部分。边缘部分也属于这一个DN，只是边缘部分可能位于靠近UE的位置。每个LDN可以由相应的数据网络访问标识符(data network access identifier，DNAI)进行标识。如果UE要获得边缘服务，则通常需要先通过边缘计算服务发现流程来获得相应的EAS的IP地址。如此，运营商网络可以根据EAS的IP地址，选择距离LDN的UPF网元来为UE建立传输路径，以确保UE可以访问该LDN的EAS，获得边缘服务。
图3为TS23.548定义的边缘计算服务发现流程，如图3所示，该流程包括：
S301，UE发起PDU会话建立流程。
UE在注册完成后，可以请求SMF网元为其建立PDU会话，具体可以参考TS23.502中PDU会话的相关介绍，不再赘述。
S302，SMF网元选择边缘应用服务器发现功能(edge application server discovery function，EASDF)。
SMF网元可以为UE的PDU会话选择EASDF，该被选择的EASDF可以作为该PDU会话对应的域名系统(domain name system，DNS)，用于后续UE发现EAS使用。
S303，SMF网元向EASDF发送DNS上下文创建请求(Neasdf_DNSContext_Create Request)消息。EASDF接收来自SMF网元的DNS上下文创建请求消息。
DNS上下文创建请求消息可以用于请求EASDF创建PDU会话对应的DNS上下文。DNS上下文创建请求消息可以包括：UE的IP地址、UE的PDU会话标识、以及DNS消息处理规则。DNS消息处理规则包括：DNS消息处理规则标识(DNS handling rule identity)、以及DNS消息检测模板(DNS message detection template)(可选)、以及操作(action(s))。 UE的IP地址可以是HPLMN为UE分配的IP地址。
DNS消息检测模板可以包括如下至少一项：DNS消息类型(DNS message type)为DNS查询或DNS响应(DNS response)、如果DNS消息类型为DNS查询，则EASDF需要查看源IP地址(UE的IP地址)和全地址域名(full qualified domain name，FQDN)范围数组(可选)、如果DNS消息类型为DNS响应，则EASDF需要查看FQDN范围数组和/或EAS IP地址范围数组(可选)。为方便理解，下文提到的“FQDN”，在没有特别说明的情况下，通常理解为“边缘服务的FQDN”。
操作可以包括如下至少一项：报告操作(reporting action)、转发操作(forwarding action)、或控制操作(control action)。报告操作是指EASDF可以向SMF网元报告DNS消息的内容。例如，如果UE的IP地址和FQDN可用，则EASDF可以向SMF网元报告DNS查询消息中的FQDN(参见308)。又例如，如果DNS服务器提供的IP地址和FQDN可用，则EASDF可以向SMF报告DNS响应消息中的FQDN和该IP地址(参见S314)。报告操作是指EASDF可以向DNS服务器发送DNS消息。EASDF可在DNS消息中构建DNS扩展机制(extended-DNS，EDNS)客户端子网选项(EDNS client subnet option，ECS option)，然后向该DNS服务器送该DNS消息(参见S312)。控制操作可以包括如下至少一项：EASDF缓存DNS消息、EASDF向UE发送缓存的DNS响应消息、或EASDF丢弃缓存的DNS响应消息。
S304，EASDF向SMF网元发送DNS上下文创建响应(Neasdf_DNSContext_Create Response)消息。SMF网元接收来自EASDF的DNS上下文创建响应消息。
DNS上下文创建响应消息可以用于指示EASDF已创建DNS上下文。其中，SMF网元可以根据DNS上下文创建请求消息，创建该UE的PDU会话对应的DNS上下文，并将上述UE的IP地址以及DNS消息处理规则存储到该DNS上下文中。
S305，SMF网元向EASDF发送DNS上下文更新请求(Neasdf_DNSContext_Update Request)消息。EASDF接收来自SMF网元的DNS上下文创建更新消息。
S306，EASDF向SMF网元发送DNS上下文更新响应(Neasdf_DNSContext_Update Response)消息。SMF网元接收来自EASDF的DNS上下文更新响应消息。
DNS上下文更新请求消息可以用于请求EASDF更新DNS上下文。EASDF更新DNS上下文可以由UE的移动性触发，例如UE移动到新的位置。DNS上下文更新响应消息为DNS上下文更新请求消息的响应消息，可以用于指示EASDF接收到DNS上下文更新请求消息。S305-S306的具体原理与上述S303-S304类似，可参考理解，不再赘述。S305-S306为可选步骤，SMF网元也可以不更新DNS上下文。
S307，UE向EASDF发送DNS查询消息。EASDF接收来自UE的DNS查询消息。
DNS查询消息可以用于查询EAS的IP地址。DNS查询消息可以携带UE想要获得的边缘服务对应的FQDN，用于通过该FQDN查询到该边缘服务对应的EAS的IP地址。UE预先配置有EASDF的IP地址。此时，如果UE想要获得该边缘服务，UE可以根据该EASDF的IP地址，向EASDF发送DNS查询消息。
对于EASDF而言，如果DNS查询消息与DNS消息处理规则中的DNS消息检测模板匹配，则EASDF执行S308。例如，EASDF可以从DNS查询消息获取UE的IP地址和FQDN，并根据DNS消息处理规则，判断UE的IP地址和FQDN是否可用。此时，如果DNS查询 消息中UE的IP地址与DNS上下文中UE的IP地址相同，以及DNS查询消息中的IFQDN与DNS上下文中的FQDN相同，则表示UE的IP地址和FQDN可用，也即DNS查询消息与DNS消息检测模板匹配。
S308，EASDF向SMF网元发送DNS上下文通知请求(Neasdf_DNSContext_Notify Request)消息。SMF网元接收来自EASDF的DNS上下文通知请求消息。
DNS上下文通知请求消息可以用于请求SMF网元提供用于EAS寻址的信息。例如，DNS上下文通知请求消息可以携带上述FQDN，用以通过该FQDN请求SMF网元提供用于EAS寻址的信息。
S309，SMF网元向EASDF发送DNS上下文通知响应(Neasdf_DNSContext_Notify Response)消息。EASDF接收来自SMF网元的DNS上下文通知响应消息。
DNS上下文通知响应消息可以为DNS上下文通知请求消息的响应消息，用以指示SMF网元已接收到该DNS上下文通知请求消息。
S310，SMF网元向EASDF发送DNS上下文更新请求消息。EASDF接收来自SMF网元的DNS上下文创建更新消息。
DNS上下文更新请求消息用于请求更新DNS消息处理规则。例如，DNS上下文更新请求消息可以携带新的DNS消息处理规则，新的DNS消息处理规则可以携带ECS选项信息，用以表征一个可以反映UE所在区域的IP地址。也就是说，SMF网元可以通过更新DNS消息处理规则来为EASDF提供用于EAS寻址的信息。
S311，EASDF向SMF网元发送DNS上下文更新响应消息。SMF网元接收来自EASDF的DNS上下文更新响应消息。
DNS上下文更新响应消息为DNS上下文更新请求消息的响应消息，可以用于指示EASDF接收到DNS上下文更新请求消息。
S312，EASDF向DNS服务器发送DNS查询消息。DNS服务器接收来自EASDF的DNS查询消息。
DNS查询消息可以用于请求DNS服务器提供EAS的IP地址。例如，DNS查询消息可以携带ECS选项(包含ECS选项信息)，用以通过ECS选项请求DNS服务器提供EAS的IP地址。EASDF可以从DNS上下文更新请求消息中获得ECS选项信息，并根据DNS消息处理规则，使用该ECS选项信息生成ECS选项。EASDF可以将ECS选项封装到DNS查询消息中，得到DNS查询消息。
S313，DNS服务器向EASDF发送DNS响应消息。EASDF接收来自DNS服务器的DNS响应消息。
DNS响应消息可以携带FQDN和EAS的IP地址。DNS服务器可以根据DNS查询消息中的ECS选项，确定UE所在区域。DNS服务器可以确定一个位于UE所在区域，或者与UE所在区域距离最近的EAS，从而获得该EAS的IP地址。
可以理解，S308-S313为可选步骤，在UE的IP地址可用的情况下，执行S308-S313，否则，不执行。
S314，EASDF向SMF发送DNS上下文通知请求消息。SMF网元接收来自EASDF的DNS上下文通知请求消息。
DNS上下文通知请求消息可以用于请求SMF网元建立UE与EAS之间的数据面传输 路径。例如，DNS上下文通知请求消息可以携带FQDN以及EAS的IP地址，用以SMF网元根据EAS的IP地址，建立UE与EAS之间的数据面传输路径，具体可以参考TS23.548中的相关介绍，不再赘述。EASDF在接收到DNS响应消息后，如果DNS响应消息与DNS上下文中DNS消息处理规则的DNS消息检测模板匹配，则EASDF向SMF发送DNS上下文通知请求消息。其中，DNS响应消息与DNS消息检测模板匹配可以指：DNS响应消息中的FQDN和EAS的IP地址，与DNS消息检测模板中的FQDN和EAS的IP地址相同。
S315，EASDF向SMF发送DNS上下文通知响应消息。SMF网元接收来自EASDF的DNS上下文通知响应消息。
DNS上下文通知响应消息可以为DNS上下文通知请求消息的响应消息，用以指示SMF网元已接收到该DNS上下文通知请求消息。
S316，SMF网元向EASDF发送DNS上下文更新请求消息。EASDF接收来自SMF网元的DNS上下文创建更新消息。
DNS上下文更新请求消息用于指示UE与EAS之间的数据面传输路径已建立完成。例如，DNS上下文更新请求消息可以携带一个信元，该信元用于指示UE与EAS之间的数据面传输路径已建立完成。
S317，EASDF向SMF网元发送DNS上下文更新响应消息。SMF网元接收来自EASDF的DNS上下文更新响应消息。
DNS上下文更新响应消息为DNS上下文更新请求消息的响应消息，可以用于指示EASDF接收到DNS上下文更新请求消息。
S318，EASDF向UE发送DNS响应消息。UE接收来自EASDF的DNS响应消息。
DNS响应消可以用于指示EAS的IP地址。例如，DNS响应消息可以携带FQDN以及EAS的IP地址。该DNS响应消息中的FQDN与UE请求的FQDN(参见S307)相同。UE可以根据该DNS响应消息中的FQDN，获知DNS响应消息中的EAS的IP地址为UE请求的边缘服务对应的EAS的IP地址。
可以理解，UE的IP地址通常由UE的归属公共陆地移动网(home public land mobile network，HPLMN)为UE分配的私网IP地址。不同私网的私网IP地址可以会出现冲突。为避免这一问题，运营商可以通过合理部署EASDF来确保连接到同一个EASDF的UE的IP地址不发生重叠，从而确保EASDF可以基于UE的IP地址区分来自不同UE的DNS查询消息。
3、5GS漫游：
图4为5GS的漫游架构示意图，例如归属路由(home routed，HR)的漫游场景下的5G网络。如图4所示，该5G网络包括HPLMN和VPLMN。HPLMN为UE的归属地网络，也称为家乡网络。受访的公用陆地移动网(visited public land mobile network，VPLMN)为UE的漫游地网络，也称为漫游网络。VPLMN和HPLMN通过vSEPP和hSEPP通信。在图4所示的场景下，业务需要在HPLMN承载，即，DN在HPLMN。
如图4所示，在VPLMN中，UE通过RAN设备接入5G网络，UE通过N1接口(简称N1)与AMF网元通信；RAN设备通过N2接口(简称N2)与AMF网元通信；RAN设备通过N3接口(简称N3)与UPF网元通信；SMF网元通过N4接口(简称N4)与UPF 网元通信。在HPLMN，UPF网元通过N6接口(简称N6)接入DN；UPF网元通过N4接口(简称N4)与SMF网元通信。且VPLMN内的UPF网元与HPLMN内的UPF网元通过N9接口(简称N2)通信。此外，图4所示的VPLMN的NSSF网元、NEF网元、AMF网元、SMF网元、NRF网元、或者PCF网元等控制面功能采用服务化接口进行交互。比如，AMF网元对外提供的服务化接口为Namf；SMF网元对外提供的服务化接口为Nsmf；NSSF网元对外提供的服务化接口为Nnssf；NEF网元对外提供的服务化接口为Nnef；NRF网元对外提供的服务化接口为Nnrf；PCF网元对外提供的服务化接口为Npcf。图4所示的HPLMN的UDM网元、AUSF网元、PCF网元、NRF网元、NSSF网元、AF、或者NEF网元等控制面功能也采用服务化接口进行交互。比如，AUSF网元对外提供的服务化接口为Nausf；UDM网元对外提供的服务化接口为Nudm；AF对外提供的服务化接口为Naf。图4所示的两个网元之间的“Nxx”表示这两个网元之间的接口，具体不再一一例举。
在漫游场景下，UE可以触发V-SMF网元建立归属路由协议数据单元(protocol data unit)会话(HR PDU session)，即UE通过V-UPF网元连接到H-UPF网元的PDU会话，具体可以参考TS23.502中PDU会话的相关介绍，不再赘述。这种情况下，DN的数据可以依次通过H-UPF网元和V-UPF网元转发到UE，或者，UE的数据可以依次通过V-UPF网元和H-UPF网元转发到DN。
上述边缘计算也同样适用于漫游场景。如图5所示，在已建立HR PDU会话的情况下，V-SMF网元可以在VPLMN为HR PDU会话建立本地分流点(如V-UPF网元)，并使用边缘服务。这样，UE可以通过V-UPF网元向V-EASDF发送DNS查询消息。如果DNS查询消息与DNS消息处理规则中的DNS消息检测模板匹配，则V-EASDF可以通过V-SMF网元从DNS服务器获取位于在VPLMN的EAS的IP地址。V-EASDF可以通过V-UPF网元向UE发送DNS响应消息，以便UE根据该DNS响应消息访问该EAS，从而获得位于VPLMN的边缘服务。当然，图5的具体实现原理也可以参考上述图3中的相关介绍，不再赘述。
可以理解，由于VPLMN与HPLMN通常属于不同的运营商，HPLMN为UE(记为UE1)分配的私网IP地址可能与VPLMN中某个UE(记为UE2)的IP地址相同，则当UE1漫游至该VPLMN时，可能出现UE1与UE2的地址冲突的情况，导致UE1可能无法获得边缘服务。例如，V-EASDF可能无法区分DNS查询消息是来自UE1还是UE2，导致其无法正确匹配DNS上下文，也无法为UE1提供正确的EAS的IP地址，从而导致UE1无法获得边缘服务。又例如，即使V-EASDF正确匹配DNS上下文，但V-EASDF返回的DNS响应消息可能通过UE2的锚点UPF网元发往UE2，而无法正确路由回UE1，也导致UE1无法获得边缘服务。总而言之，由于发起访问的UE可能位于不同的网络，如VPLMN或HPLMN，EASDF可能无法识别和处理，导致流程失败，UE无法获得边缘服务。
进一步的，如图5所示，如果DNS查询消息与DNS消息处理规则中的DNS消息检测模板不匹配，则可能表示UE1不请求边缘服务。这种情况下，V-EASDF可能会选择通过V-UPF网元向H-DNS服务器(HR PDU会话对应的DNS服务器)/H-EASDF发送DNS查询消息。该DNS查询消息可能不携带与边缘服务相关的ECS选项，因此可称为非EC的DNS查询消息。但由于该非EC的DNS查询消息并不属于HR PDU会话，导致V-UPF网元识别该非EC的DNS查询消息，也无法向H-DNS服务器转发该非EC的DNS查询消 息。也即，在漫游场景下，UE1无法访问H-DNS服务器，无法获得相应的应用服务。
通过上述分析可以看出，边缘计算业务能够支持漫游终端访问，但对于漫游终端的数据如何进行路由，是值得考虑的问题。因此，本申请实施例提出了如下技术方案，用以解决边缘计算中漫游终端的数据路由的问题。
下面将结合附图，对本申请中的技术方案进行描述。
本申请实施例的技术方案可以应用于各种通信系统，例如无线保真(wireless fidelity，WiFi)系统，车到任意物体(vehicle to everything，V2X)通信系统、设备间(device-todevie，D2D)通信系统、车联网通信系统、第四代(4th generation，4G)移动通信系统，如长期演进(long term evolution，LTE)系统、全球互联微波接入(worldwide interoperability for microwave access，WiMAX)通信系统、5G，如新空口(new radio，NR)系统，以及未来的通信系统等。
本申请将围绕可包括多个设备、组件、模块等的系统来呈现各个方面、实施例或特征。应当理解和明白的是，各个系统可以包括另外的设备、组件、模块等，并且/或者可以并不包括结合附图讨论的所有设备、组件、模块等。此外，还可以使用这些方案的组合。
另外，在本申请实施例中，“示例的”、“例如”等词用于表示作例子、例证或说明。本申请中被描述为“示例”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言，使用示例的一词旨在以具体方式呈现概念。
本申请实施例中，“信息(information)”，“信号(signal)”，“消息(message)”，“信道(channel)”、“信令(singaling)”有时可以混用，应当指出的是，在不强调其区别时，其所要表达的含义是匹配的。“的(of)”，“相应的(corresponding，relevant)”和“对应的(corresponding)”有时可以混用，应当指出的是，在不强调其区别时，其所要表达的含义是匹配的。此外，本申请实施例提到的“/”可以用于表示“或”的关系。本申请实施例提到的“#1”、“#2”、“#3”、…“#x”等等，仅用于描述上的区分，其含义应当不做特殊理解。
本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
为便于理解本申请实施例，首先以图6中示出的通信系统为例详细说明适用于本申请实施例的通信系统。示例性的，图6为本申请实施例提供的通信方法所适用的一种通信系统的架构示意图。
如图6所示，该通信系统可以适用于上述5G系统的HR漫游场景，主要包括如下至少一项：UE、V-UPF网元、V-EASDF、V-SMF网元、H-UPF网元、H-SMF网元、LDN、H-DNS服务器。UE可以指漫游至VPLMN的UE，且该UE的归属公共陆地移动网络为HPLMN，并且，下文提到的UE，在没有特别介绍的情况下，也可以做类似理解。
本申请实施例中，由于UE的IP地址可能会出现冲突，因此VPLMN可以对UE进行额外标识，以区分与UE存在IP地址冲突的其他UE，确保UE能够获得相应的边缘服务。例如，一种可能的场景中，VPLMN可以针对UE分配标识，以通过该标识来额外标识UE，以便在IP地址冲突的情况下，V-EASDF仍能够识别该UE，从而正确处理该UE的DNS 查询消息，实现正确的数据路由，便于UE获得边缘服务。或者，另一种可能的场景中，V-UPF网元可使用VPLMN针对该UE分配的地址来标识该UE的DNS查询消息，以避免出现地址冲突，实现正确的数据路由，便于UE能够获得边缘服务。
另外，本申请实施例中，VPLMN还可以为V-UPF网元配置针对非EC的DNS查询消息的处理规则，以便于V-UPF网元能够向H-DNS服务器或H-EASDF转发非EC的DNS查询消息，从而UE能够访问H-DNS服务器，以获得相应的应用服务。
为方便理解，下面将结合图7-图12，通过方法实施例具体介绍上述通信系统中各网元之间的交互流程。
本申请实施例提供的通信方法可以适用于上述通信系统，并具体应用到上述通信系统中提到的各种场景，下面具体介绍。
实施例1：
示例性的，图7为本申请实施例提供的通信方法的流程示意图一。该通信方法适用于终端、用户面网元、边缘应用服务功能之间的交互。终端具体可以是上述通信系统中的UE、用户面网元具体可以是上述通信系统中的V-UPF网元、边缘应用服务功能具体可以是上述通信系统中的V-EASDF。该通信方法中，VPLMN可以针对终端分配第一标识，以通过该第一标识来额外标识该终端。
如图7所示，该通信方法的流程具体如下：
S701，用户面网元接收来自终端的第一DNS查询消息。
终端漫游至VPLMN内。第一DNS查询消息用于查询应用服务的地址，例如第一DNS查询消息携带有该应用服务的FQDN。第一DNS查询消息携带有HPLMN内的终端的IP地址。用户面网元与终端预先建立有PDU会话，如终端的HR PDU会话。用户面网元可通过该PDU会话，接收第一DNS查询消息。
S702，用户面网元向边缘应用服务功能发送第一DNS查询消息和第一标识。边缘应用服务功能接收来自用户面网元的第一DNS查询消息和第一标识。
第一标识可以是VPLMN针对终端分配的标识，用于在VPLMN内标识该终端。第一标识具体可以是VPLMN针对终端的PDU会话分配的标识，或者说第一标识可以在VPLMN内映射到终端的PDU会话。例如，VPLMN可以针对该终端，或者说针对该终端的PDU会话，建立用户面网元与边缘应用服务功能之间的通信隧道。该通信隧道可以为如下任一项隧道协议对应的通信隧道，如通用分组无线系统(general packet radio system，GPRS)隧道协议(GPRS tunneling protocol，GTP)、或通用路由封装协议(generic routing encapsulation，GRE)，或者其他任何可能的通信隧道。在此基础上，第一标识可以是该通信隧道的标识，具体可以是该通信隧道在边缘应用服务功能处的端点标识，即第一标识可通过复用已有信元实现，以降低实现难度。具体的，如果通信隧道为GTP，则第一标识可以为隧道端点标识(tunnel endpoint identifier，TEID)或者全称隧道端点标识符(fully qualified tunnel endpoint identifier，F-TEID)。如果通信隧道为GRE，则第一标识可以为序列号。或者，第一标识也可以其他任何可能的标识，或者新定义的标识，不做限定。第一标识也可以用于边缘应用服务功能确定是否存在与第一标识匹配的DNS规则，具体可以参加S703，不再赘述。
第一标识具体可以由VPLMN内的网元分配，例如用户面网元、会话管理网元或边缘 应用服务功能。
一种可能的方式中，第一标识可由用户面网元确定。例如，用户面网元可确定第一标识，并向会话管理网元发送第一标识，以便VPLMN的网元，例如边缘应用服务功能能够从会话管理网元获得第一标识，从而根据第一标识识别该终端的消息，实现正确的数据路由。其中，用户面网元可自行确定第一标识，或者根据会话管理网元的指示确定第一标识，不做限定。
或者，另一种可能的方式中，第一标识可由会话管理网元确定。例如，在创建终端的PDU会话的过程，会话管理网元可确定第一标识，并向用户面网元发送第一标识。以及，可选地，会话管理网元还可向边缘应用服务功能发送第一标识。如此，用户面网元可接收来自会话管理网元的第一标识，从而能够在发送终端的消息时，同时发送第一标识，以便边缘应用服务功能能够根据第一标识识别该终端的消息，实现正确的数据路由。
或者，又一种可能的方式中，第一标识可由边缘应用服务功能确定。例如，边缘应用服务功能可确定第一标识，并向会话管理网元发送第一标识，以便用户面网元能够从会话管理网元获得第一标识，从而能够在发送终端的消息时，同时发送第一标识，以便边缘应用服务功能能够根据第一标识识别该终端的消息，实现正确的数据路由。其中，边缘应用服务功能可自行确定第一标识，或者根据会话管理网元的指示确定第一标识，不做限定。
用户面网元可默认或根据第一用户面处理规则，向边缘应用服务功能发送第一DNS查询消息和第一标识，如通过通信隧道向边缘应用服务功能发送第一DNS查询消息和第一标识。例如，第一用户面处理规则可预先配置或者预先由会话管理网元提供，例如会话管理网元通过PDU会话建立流程向用户面网元提供第一用户面处理规则。第一用户面处理规则可以与终端的PDU会话对应，或者说第一用户面处理规则可以映射到该终端的PDU会话，用以用户面网元识别和处理与该终端的PDU会话相关的信令。第一用户面处理规则可以指示：对于第一DNS查询消息，用户面网元向边缘应用服务功能发送第一DNS查询消息和第一标识。第一用户面处理规则具体可以指示：对于来自终端的第一DNS查询消息，用户面网元通过通信隧道，向边缘应用服务功能发送第一DNS查询消息和第一标识。如此，用户面网元可根据配置的第一用户面处理规则处理第一DNS查询消息，从而可避免用户面网元误操作或误处理。
可以理解，第一用户面处理规则可以不限于第一DNS查询消息，也可以适用于来自终端的DNS查询消息。例如，第一用户面处理规则可以指示：对于来自终端的DNS查询消息，用户面网元向边缘应用服务功能发送该DNS查询消息和第一标识。这种情况下，该第一DNS查询消息为来自终端的DNS查询消息中的其中一条消息。
其中，在建立通信隧道或者未建立通信隧道的情况下，用户面网元发送第一DNS查询消息和第一标识的方式可能有所不同。
在未建立通信隧道的情况下，用户面网元可复用第一DNS查询消息，发送第一DNS查询消息和第一标识。例如，用户面网元可以将第一标识携带在第一DNS查询消息中，如携带在第一DNS查询消息的预留字段中，然后向边缘应用服务功能发送第一DNS查询消息。
或者，在建立通信隧道的情况下，用户面网元可以将第一DNS查询消息和第一标识封装为隧道消息，然后向边缘应用服务功能发送隧道消息。例如，用户面网元可以在第一 DNS查询消息的外层封装一个携带有第一标识的头部，也即通信隧道的头部，以得到隧道消息。如果通信隧道是GTP，则隧道头部是GTP格式的隧道头部。如果通信隧道是GRE，则隧道头部是GRE格式的隧道头部。这种情况下，外层的隧道头部可以使得该隧道消息直接穿越位于用户面网元与边缘应用服务功能之间的实体/功能，或者说用户面网元与边缘应用服务功能之间的实体/功能直接透传该隧道消息，即实现所谓的隧道传输。可以理解，由于第一标识携带在通信隧道的头部中，边缘应用服务功能能够通过通信隧道识别接收到的信元是第一标识。
S703，边缘应用服务确定是否存在与第一DNS查询消息和第一标识匹配的DNS消息处理规则。
DNS消息处理规则中可以包括FQDN，例如DNS消息处理规则的DNS消息检测模板中可以包括FQDN。DNS消息处理规则可以携带在DNS上下文中，该DNS上下文中还可以包括第一标识。该DNS上下文可预先配置在边缘应用服务上；或者边缘应用服务可预先从会话管理网元获取该DNS上下文，或者预先根据会话管理网元提供的信息生成该DNS上下文。
其中，存在与第一DNS查询消息和第一标识匹配的DNS消息处理规则可以指：存在与第一标识匹配的DNS上下文，且该DNS上下文中存在与第一DNS查询消息匹配的DNS消息处理规则。同理，不存在与第一DNS查询消息和第一标识匹配的DNS消息处理规则可以指：存在与第一标识匹配的DNS上下文，但该DNS上下文中不存在与第一DNS查询消息匹配的DNS消息处理规则。
在此基础上，边缘应用服务功能可以根据第一标识，确定是否存在与该第一标识匹配的DNS上下文，如包含第一标识的DNS上下文。如果不存在与该第一标识匹配的DNS上下文，则表示终端的身份无法确定，流程结束。如果存在与该第一标识匹配的DNS上下文，则边缘应用服务功能可以确定该DNS上下文中是否存在与第一DNS查询消息匹配的DNS消息处理规则。此时，如果第一DNS查询消息中的FQDN与DNS上下文中某个DNS消息处理规则中的FQDN匹配，则表示存在与第一DNS查询消息匹配的DNS消息处理规则。但是，如果第一DNS查询消息中的FQDN与DNS上下文中任一个DNS消息处理规则中的FQDN都不匹配，则表示不存在与第一DNS查询消息匹配的DNS消息处理规则。
可选地，第一种可能的设计方案中，该通信方法还可以包括：在存在与第一DNS查询消息和第一标识匹配的DNS消息处理规则的情况下，边缘应用服务功能向用户面网元发送第一DNS响应消息和第二标识。相应的，用户面网元接收来自边缘应用服务功能的第一DNS响应消息和第二标识，并根据第二标识向终端发送第一DNS响应消息。
其中，第一DNS响应消息可以是第一DNS查询消息的响应消息，例如，第一DNS响应消息可携带应用服务的地址，如边缘应用服务的地址，以便终端能够获得边缘服务。
第二标识可以是VPLMN针对终端分配的标识，用于在VPLMN内标识该终端。第二标识具体可以是VPLMN针对终端的PDU会话分配的标识，第二标识可以在VPLMN内映射到终端的PDU会话，也即用户面网元可以基于第二标识，将终端的消息(如第一DNS响应消息)映射到终端的PDU会话，从而向该终端发送该第一DNS响应消息，以便终端获得应用服务，如边缘服务，具体可以参见下文，不再赘述。可以理解，第二标识与第一 标识可能相同，或者也可能不同，不做限定。例如，第二标识也可以是通信隧道的标识，具体可以是该通信隧道在用户面网元处的端点标识，即第二标识可通过复用已有信元实现，以降低实现难度。或者，第二标识也可以其他任何可能的标识，或者新定义的标识，不做限定。第二标识的确定方式与上述第一标识类似，可参考理解，不再赘述。
对于边缘应用服务功能而言，由于第一DNS查询消息携带中的FQDN与上述DNS消息处理规则中的FQDN匹配，表示终端请求的应用服务的地址为边缘应用服务的地址。此时，边缘应用服务功能可通过第一DNS响应消息为终端提供边缘应用服务的地址。边缘应用服务功能可默认或根据上述DNS消息处理规则，向用户面网元发送第一DNS响应消息和第二标识，如通过通信隧道向用户面网元发送第一DNS响应消息和第二标识。
其中，DNS消息处理规则可以包括DNS消息检测模版和操作。DNS消息检测模版可以包括：FQDN，该FQDN可用于与第一DNS查询消息携带的FQDN匹配。操作可以指示：边缘应用服务功能向用户面网元发送第一DNS响应消息和第二标识，具体可以指示：边缘应用服务功能通过通信隧道，向用户面网元发送第一DNS响应消息和第二标识。也就是说，如果第一DNS查询消息携带中的FQDN与DNS消息检测模版中的FQDN匹配，也即DNS消息检测模版与DNS消息检测模版匹配。此时，边缘应用服务功能可以根据操作的指示，向用户面网元发送第一DNS响应消息和第二标识。
可以理解，DNS消息处理规则可不限于第一DNS查询消息和第一DNS响应消息，也可以适用于来自用户面网元的DNS查询消息，以及向用户面网元发送的DNS查询消息。例如，DNS消息检测模版包括：FQDN，该FQDN可用于与来自用户面网元的DNS查询消息携带的FQDN匹配。操作可以指示：边缘应用服务功能向用户面网元发送DNS响应消息和第二标识。这种情况下，该第一DNS查询消息为来自终端的DNS查询消息中的其中一条消息，该第一DNS响应消息为向用户面网元发送的DNS查询消息中的一条消息。此外，DNS消息处理规则的具体实现也可以参考上述S303中的相关介绍，不再赘述。
可以理解，边缘应用服务功能发送第一DNS响应消息和第二标识的具体实现，与上述用户面网元发送第一DNS查询消息和第一标识类似，可参考理解，不再赘述。此外，在建立通信隧道的情况下，由于第二标识可以携带在通信隧道的头部中，使得用户面网元能够通过通信隧道识别接收到的信元是第二标识。
对于用户面网元而言，用户面网元在接收到第一DNS响应消息和第二标识后，可根据第二标识，确定第一DNS响应消息是终端对应的消息，或者说该终端的PDU会话对应的消息。因此，用户面网元向终端发送第一DNS响应消息，如通过终端的PDU会话向终端发送第一DNS响应消息。
其中，用户面网元可配置有第二用户面处理规则。第二用户面处理规则的配置方式与上述第一用户面处理规则类似，可参考理解，不再赘述。第二用户面处理规则可以指示：对于第一DNS响应消息和第二标识，用户面网元向终端发送第一DNS响应消息。第二用户面处理规则具体可以指示：对于通信隧道内的第一DNS响应消息和第二标识，用户面网元向终端发送第一DNS响应消息。如此，用户面网元可以根据配置的第二用户面处理规则，执行上述针对第一DNS响应消息的处理逻辑，从而可避免用户面网元误操作或误处理。当然，如果用户面网元没有配置第二用户面处理规则，则用户面网元可以默认按照上述处理逻辑处理第一DNS响应消息。
可以理解，第二用户面处理规则可以不限于第一DNS响应消息，也可以适用于来自边缘应用服务功能的DNS响应消息。例如，第二用户面处理规则可以指示：对于来自边缘应用服务功能的DNS响应消息和第二标识，用户面网元向终端发送该DNS响应消息。这种情况下，第一DNS响应消息为来自边缘应用服务功能的DNS响应消息中的一条消息。
可选地，第二种可能的设计方案中，该通信方法还可以包括：在不存在与第一DNS查询消息和第一标识匹配的DNS消息处理规则的情况下，边缘应用服务功能向用户面网元发送第二DNS查询消息和第二标识。用户面网元接收来自边缘应用服务功能的第二DNS查询消息和第二标识，并根据第二DNS查询消息和第二标识，向HPLMN发送第三DNS查询消息。
其中，第二DNS查询消息可以用于请求其他应用服务的地址，以便终端最终能够获得相应的应用服务。第二标识的具体实现可参考上述第一种可能的设计方案中的相关介绍，不再赘述。例如，由于第一DNS查询消息中的FQDN与边缘应用服务功能上配置的任一个DNS消息处理规则中的FQDN都不匹配，表示终端请求的应用服务的地址并不是边缘应用服务的地址，而可能是其他应用服务的地址。此时，边缘应用服务功能可通过用户面网元向终端的HPLMN发送第二DNS查询消息和第二标识。此外，边缘应用服务功能发送第二DNS查询消息和第二标识的具体实现，与上述边缘应用服务功能发送第一DNS响应消息和第二标识类似，可参考理解，不再赘述。
第三DNS查询消息也可以用于请求其他应用服务的地址。第三DNS查询消息可以是用户面网元根据第二DNS查询消息确定的消息。例如，用户面网元在接收到第二DNS查询消息和第二标识后，可根据第二标识，确定第二DNS查询消息是终端对应的消息，或者说该终端的PDU会话对应的消息。因此，用户面网元可以将第二DNS查询消息的源地址由边缘应用服务功能的地址替换为终端的地址，以得到消息第三DNS查询消息，并将第三DNS查询消息映射到终端的PDU会话，从而向终端的HPLMN发送第三DNS查询消息，以便终端能够获得相应的应用服务。
其中，用户面网元可配置有第三用户面处理规则。第三用户面处理规则的配置方式与上述第一用户面处理规则类似，可参考理解，不再赘述。第三用户面处理规则可以指示：对于第二DNS查询消息和第二标识，用户面网元向HPLMN发送第三DNS查询消息；具体可以指示：对于通信隧道内的第二DNS查询消息和第二标识，用户面网元向HPLMN发送第三DNS查询消息。如此，用户面网元可以根据配置的第三用户面处理规则，执行上述针对第二DNS查询消息的处理逻辑，从而可避免用户面网元误操作或误处理。当然，如果用户面网元没有配置第三用户面处理规则，则用户面网元可以默认按照上述处理逻辑处理第二DNS查询消息。
可以理解，第三用户面处理规则可以不限于第二DNS查询消息和第三DNS查询消息，也可以适用于来自边缘应用服务功能的DNS查询消息，以及向HPLMN发送的DNS查询消息。例如，第三用户面处理规则可以指示：对于来自边缘应用服务功能的DNS查询消息和第二标识，用户面网元向HPLMN发送DNS查询消息。这种情况下，第二DNS查询消息为来自边缘应用服务功能的DNS查询消息中的一条消息，第三DNS查询消息为向HPLMN发送的DNS查询消息中的一条消息。
可选地，第三种可能的设计方案，该通信方法还可以包括：用户面网元接收来自 HPLMN内的DNS服务器的第二DNS响应消息；用户面网元根据第二DNS响应消息，向边缘应用服务功能发送第三DNS响应消息和第一标识；边缘应用服务功能接收来自用户面网元的第三DNS响应消息和第一标识；边缘应用服务功能根据第三DNS响应消息和第一标识，向用户面网元发送第四DNS响应消息和第二标识；用户面网元接收来自边缘应用服务功能的第四DNS响应消息和第二标识；用户面网元根据第二标识，向终端发送第四DNS响应消息。
第二DNS响应消息可以为第三DNS查询消息的响应消息。第二DNS响应消息可携带其他应用服务的地址，用于终端获得相应的应用服务。第三DNS响应消息可以为第二DNS查询消息的响应消息。第三DNS响应消息可根据第二DNS响应消息确定。例如，用户面网元可以通过终端的PDU会话接收第二DNS响应消息。此时，由于该第二DNS响应消息来自HPLMN内的DNS服务器，用户面网元可以确定将第二DNS响应消息的目的地址由终端的地址替换为边缘应用服务功能的地址，以得到第三DNS响应消息，然后向边缘应用服务功能发送第三DNS响应消息和第一标识，如通过通信隧道向边缘应用服务功能发送第三DNS响应消息和第一标识。
其中，用户面网元可配置有第四用户面处理规则。第四用户面处理规则的配置方式与第一用户面处理规则类似，可参考理解，不再赘述。第四用户面处理规则可以指示：对于第二DNS响应消息，用户面网元向边缘应用服务功能发送第三DNS响应消息和第一标识；具体可以指示：对于第二DNS响应消息，用户面网元通过通信隧道向边缘应用服务功能发送第三DNS响应消息和第一标识。如此，用户面网元可以根据配置的第四用户面处理规则，执行上述针对第二DNS响应消息的处理逻辑，从而可避免用户面网元误操作或误处理。当然，如果用户面网元没有配置第四用户面处理规则，则用户面网元可默认按照上述处理逻辑处理第二DNS响应消息。
可以理解，第四用户面处理规则可以不限于第二DNS响应消息和第三DNS响应消息，也可以适用于来自HPLMN内的DNS服务器的DNS响应消息，以及向边缘应用服务功能发送的DNS响应消息。例如，第四用户面处理规则可以指示：来自HPLMN内的DNS服务器的DNS响应消息，用户面网元向边缘应用服务功能发送的DNS响应消息和第一标识。这种情况下，第二DNS响应消息为来自HPLMN内的DNS服务器的DNS响应消息中的一条消息，第三DNS响应消息为向边缘应用服务功能发送的DNS响应消息中的一条消息。此外，用户面网元发送第三DNS响应消息和第一标识的具体实现，与上述用户面网元发送第一DNS响应消息和第一标识类似，可参考理解，不再赘述。
第四DNS响应消息可以为第一DNS查询消息的响应消息。第四DNS响应消息可根据第三DNS响应消息确定。例如，边缘应用服务功能在接收到第三DNS响应消息，可根据第三DNS响应消息与对应的DNS消息处理规则匹配，将第三DNS响应消息的目的地址由边缘应用服务功能的地址替换为终端的地址，以得到第四DNS响应消息。如此，边缘应用服务功能可根据该DNS消息处理规则，向用户面网元发送第四DNS响应消息和第二标识，如通过通信隧道向用户面网元发送第四DNS响应消息和第二标识。
此外，边缘应用服务功能发送第四DNS响应消息和第二标识的具体实现，与上述边缘应用服务功能发送第一DNS响应消息和第二标识类似，可参考理解，不再赘述。用户面网元对第四DNS响应消息的处理与上述第一DNS响应消息类似，可参考理解，不再赘 述。
可以理解，上述第二种可能的设计方案和第三种可能的设计方案可以组合实施例。
综上，根据上述通信方法可知，在终端漫游至位于VPLMN时，该终端的归属公共陆地移动网络HPLMN分配的地址可能与VPLMN的其他终端的地址冲突，导致边缘应用服务功能无法识别和处理。因此，边缘应用服务功能用户面网元可通过VPLMN分配的第一标识来额外标识该终端，或者可以理解为边缘应用服务功能可通过第一标识确定第一DNS查询消息对应该终端，以便在地址可能冲突的情况下，边缘应用服务功能仍能够识别该终端，从而正确处理该终端的DNS查询消息，确保实现正确的数据路由，从而便于终端能够获得应用服务，如边缘服务。
可以理解，以上介绍了该通信方法在实施例1中的整体流程，下面介绍该通信方法在实施例1中的具体流程。
示例性的，图8为实施例1在具体场景中的架构示意图。该场景涉及UE、V-UPF网元、V-SMF网元、V-EASDF、H-DNS服务器。UE可以是上述方法中的终端、V-UPF网元可以是上述方法中的用户面网元、V-SMF网元可以是上述方法中的会话管理网元、V-EASDF可以是上述方法中的边缘应用服务功能、H-DNS服务器可以是上述HPLMN内的DNS服务器。定义该场景中：UE的IP地址为IP地址1，IP地址1也是HPLMN为UE分配的地址。V-EASDF的IP地址为IP地址2。H-DNS服务器的IP地址为IP地址3。VPLMN可以针对UE的HR PDU会话，建立V-UPF与V-EASDF之间的通信隧道，也即该通信隧道与UE的HR PDU会话对应。通信隧道的TID1以及通信隧道的TID2可用于标识UE，或者通信隧道的TID1和通信隧道的TID2也可以替换为其他VPLMN内可能用于标识UE的标识，不做限定。通信隧道的TID1和通信隧道的TID2可以保存在该HR PDU会话对应的DNS上下文中。
在此基础上，V-UPF网元的行为主要通过UPF处理规则指示，该UPF处理规则可以包括：1)对于来自UE的DNS查询消息，V-UPF网元通过通信隧道，向V-EASDF发送该DNS查询消息和通信隧道的TID1；2)对于通信隧道内接收到的DNS响应消息和通信隧道的TID2，V-UPF网元向UE发送该DNS响应消息；3)对于通信隧道内接收到的DNS查询消息和通信隧道的TID2，V-UPF网元向H-DNS服务器发送DNS查询消息；4)对于来自H-DNS服务器的DNS响应消息，V-UPF网元通过通信隧道向V-EASDF发送DNS响应消息和通信隧道的TID1。
V-EASDF的行为主要通过DNS消息处理规则指示，该DNS消息处理规则：DNS消息检测模板和操作。DNS消息检测模板包括：FQDN，该FQDN可用于与来自UE的DNS查询消息中的FQDN匹配。操作可用于指示：V-EASDF通过通信隧道向V-UPF网元发送DNS响应消息和通信隧道的TID2。
图9为本申请实施例提供的通信方法的流程示意图二。该通信方法适用于图8所示的场景，如图9所示，为图7所示实施例提供了具体的示例流程，该通信方法的具体如下：
S901，H-SMF网元向V-SMF网元发送PDU会话创建响应(Nsmf_PDUSession_Create Response)消息。相应的，V-SMF网元接收来自H-SMF网元的PDU会话创建响应消息。
PDU会话创建响应消息可以是PDU会话创建请求(Nsmf_PDUSession_Create Request)消息的响应消息。PDU会话创建请求消息可以用于V-SMF网元请求H-SMF网元提供创建 UE的HR PDU会话所需的信息。相应的，PDU会话创建响应消息可以用于提供创建UE的HR PDU会话所需的信息。例如，PDU会话创建响应消息可以携带IP地址1，以及H-DNS服务器的IP地址3。
S902，V-SMF网元向V-UPF网元发送N4会话修改请求(N4Sseesion Modification Request)消息。相应的，V-UPF网元接收来自V-SMF网元的N4会话修改请求消息。
N4会话修改请求消息可以携带第一指示信息。第一指示信息可以用于指示V-UPF网元为UE的HR PDU会话分配通信隧道的TID1和/或通信隧道的TID2。当然，N4会话修改请求消息也可以不携带第一指示信息，V-UPF网元在接收到N4会话修改请求消息的情况下，默认为UE的HR PDU会话分配通信隧道的TID1和/或通信隧道的TID2。
应理解，通信隧道的TID1可以参考上述第一标识的相关介绍，本申请实施例以通信隧道的TID1为例进行说明，本领域技术人员能够理解，本申请实施例中通信隧道的TID 1可以替换为第一标识。也即是当第一标识为除通信隧道的TID1以外的其他形式的信息时，也是类似处理。通信隧道的TID 2可以参考上述第二标识的相关介绍，本申请实施例以通信隧道的TID2为例进行说明，本领域技术人员能够理解，本申请实施例中通信隧道的TID2可以替换为第二标识。也即是当第二标识为除通信隧道的TID2以外的其他形式的信息时，也是类似处理。
S903，V-UPF网元为UE的HR PDU会话分配通信隧道的TID1和/或通信隧道的TID2。
S904，V-UPF网元向V-SMF网元发送N4会话修改响应(N4Sseesion Modification Response)消息。相应的，V-SMF网元接收来自V-UPF网元的N4会话修改响应消息。
N4会话修改请求消息可以携带通信隧道的TID1和/或通信隧道的TID2。
可以理解，S902-S904为可选步骤。例如，通信隧道的TID1和/或通信隧道的TID2可以由V-SMF网元自行确定，这种情况下，S902-S904可以不执行。又例如，通信隧道的TID1和/或通信隧道的TID2可以由V-EASDF确定，例如V-EASDF将生成的通信隧道TID发送给V-SMF网元，或者V-SMF网元指示V-EASDF确定通信隧道的TID1和/或通信隧道的TID2。之后，V-EASDF可以通过V-SMF网元向V-UPF网元提供通信隧道的TID1和/或通信隧道的TID2。此外，S902-S904也可以参考上述S702中的相关介绍，不再赘述。
S905，V-SMF网元向V-EASDF发送DNS上下文创建请求消息。相应的，V-EASDF接收来自V-SMF网元的DNS上下文创建请求消息。
DNS上下文创建请求消息可以用于请求EASDF创建UE的HR PDU会话对应的DNS上下文。该DNS上下文创建请求消息可以包括如下至少一项：IP地址1、IP地址3、通信隧道的TID1、通信隧道的TID2、或DNS消息处理规则。DNS消息处理规则的具体实现可参考图8以及上述S303中的相关介绍，不再赘述。
可以理解，DNS上下文创建请求消息携带DNS消息处理规则为一种可选实现方式。例如，DNS消息处理规则可以预先配置或者协议预定义在V-EASDF上。这种情况下，DNS上下文创建请求消息可以携带如下至少一项：IP地址1、IP地址3、通信隧道的TID1、或通信隧道的TID2，而不携带DNS消息处理规则。此时，IP地址1、IP地址3、通信隧道的TID1、或通信隧道的TID2等信息可以用于触发V-EASDF激活本地的DNS消息处理规则。或者，DNS上下文创建请求消息还可以携带一个额外的信元，该信元可以用于触发V-EASDF激活本地的DNS消息处理规则。又例如，DNS消息处理规则可以由V-EASDF 根据一些必要参数自行确定。这种情况下，DNS上下文创建请求消息可以仅携带这些必要参数，如包括如下至少一项：IP地址1(HPLMN为UE分配的地址)、IP地址3(HPLMN为H-DNS服务器分配的IP地址)、通信隧道的TID1、或通信隧道的TID2等等。
V-EASDF可以根据DNS上下文创建请求消息，创建该UE的HR PDU会话对应的DNS上下文，并将如下至少一项：IP地址1、通信隧道的TID1、通信隧道的TID2、以及DNS消息处理规则存储到该DNS上下文中。
此外，S905的具体实现也可以参考上述S303-S304中的相关介绍，不再赘述。
S906，V-SMF网元向V-UPF网元发送N4规则。相应的，V-UPF网元接收来自V-SMF网元的N4规则。
N4规则可以承载在N4会话中，如N4会话修改响应消息，该N4会话与UE的HR PDU会话对应。N4规则可以包括如下至少一项：IP地址1、IP地址2、IP地址3、通信隧道的TID1、通信隧道的TID2、以及UPF处理规则。UPF处理规则的具体实现可参考上述图8的相关介绍，不再赘述。UPF处理规则也可以参考上述用户面处理规则的相关介绍，本申请实施例以UPF处理规则为例进行说明，本领域技术人员能够理解，本申请实施例中UPF处理规则可以替换为用户面处理规则。也即是当用户面处理规则为除UPF处理规则以外的其他形式的信息时，也是类似处理。
可以理解，N4规则携带UPF处理规则为一种可选实现方式。例如，UPF处理规则可以预先配置或者协议预定义在V-UPF网元上。这种情况下，N4规则可以携带如下至少一项：IP地址1、IP地址2、IP地址3、通信隧道的TID1、或通信隧道的TID2，而不携带UPF处理规则。此时，IP地址1、IP地址2、IP地址3、通信隧道的TID1、或通信隧道的TID2等信息可以用于触发V-UPF网元激活本地的UPF处理规则。或者，N4规则还可以携带一个额外的信元，该信元可以用于触发V-UPF网元激活本地的UPF处理规则。又例如，DNS消息处理规则可以由V-UPF网元根据一些必要参数自行确定。这种情况下，N4规则可以仅携带这些必要参数，如包括如下至少一项：IP地址1、IP地址2、IP地址3、通信隧道的TID1、或通信隧道的TID2等等。
可以理解，由于V-UPF网元是通过UE的HR PDU会话对应N4会话获得UPF处理规则，这种获得方式可以隐式指示该UPF处理规则与该HR PDU会话对应，以便V-UPF网元可以根据UPF处理规则，将对应的消息(如下文提到的DNS响应消息#1和DNS查询消息#3)映射到该HR PDU会话，以通过该HR PDU会话发送这些消息。当然，也可以由UPF处理规则直接定义这些消息需要被映射到该HR PDU会话。
还可以理解，UPF处理规则仅为一种示例性的命名，其也可以替换为任何可能的命名，例如UPF行为、UPF操作、UPF操作规则等等，对此不做具体限定。此外，S906与S905之间的执行顺序不限定。
此外，S901-S906为HR场景下的HR PDU会话创建流程中的步骤，也即本申请实施例适用该于流程，该流程具体可以参考TSXXXX，不再赘述。
S907，UE向V-UPF网元发送DNS查询消息#1。相应的，V-UPF网元接收来自UE的DNS查询消息#1。
在UE的HR PDU会话建立完成后，UE可以通过HR PDU会话，向V-UPF网元发送DNS查询消息#1。DNS查询消息#1可以用于请求应用服务，例如DNS查询消息#1携带 有该应用服务的FQDN。DNS查询消息#1的源地址为IP地址1，DNS查询消息#1的目的地址为IP地址2或IP地址3。其中，UE预先配置有IP地址2和/或IP地址3。例如，在UE的HR PDU会话建立流程中，V-SMF网元可以通过H-SMF网元向UE提供IP地址2和/或IP地址3。此外，DNS查询消息#1还可以包含其他参数，具体可以参考上述S307中的相关介绍，S907的具体实现也可以参考上述S701中的相关介绍，不再赘述。
S908，V-UPF网元通过通信隧道，向V-EASDF发送DNS查询消息#1和通信隧道的TID1。相应的，V-EASDF通过通信隧道，接收来自V-UPF网元的DNS查询消息#1和通信隧道的TID1。
V-UPF网元在接收到DNS查询消息#1后，可根据UPF处理规则，通过通信隧道向V-EASDF向发送DNS查询消息#1和通信隧道的TID1，具体实现可参考上述S702中的相关介绍，不再赘述。
S909，V-EASDF确定是否存在与DNS查询消息#1和通信隧道的TID1匹配的DNS消息处理规则。
其中，V-EASDF可以根据DNS查询消息#1的通信隧道的TID1，匹配到保存有通信隧道的TID1的DNS上下文。此时，V-EASDF可以确定该DNS上下文中是否存在与DNS查询消息#1匹配的DNS消息处理规则。如果存在与DNS查询消息#1匹配的DNS消息处理规则，如DNS查询消息#1中的FQDN与DNS消息处理规则的FQDN匹配，也即DNS查询消息#1与DNS消息检测模板匹配，则表征DNS查询消息#1用于请求的应用服务为边缘服务，或者说DNS查询消息#1用于请求某个EAS提供服务，或用于查询某个EAS，从而触发执行S910-S911，用以为UE提供边缘服务。如果不存在与DNS查询消息#1和通信隧道的TID1匹配的DNS消息处理规则，如DNS查询消息#1中的FQDN与DNS消息处理规则中的FQDN不匹配，也即DNS查询消息#1与DNS消息检测模板不匹配，则表征DNS查询消息#1请求的应用服务并非边缘应用服务，而是其他应用服务，或者说DNS查询消息#1用于请求H-DNS服务器提供其他应用服务的地址。如此，V-EASDF可以触发执行S912-S916，用以为UE提供相应的应用服务。
此外，S909的具体实现也可以参考上述S703中的相关介绍，不再赘述。
S910，V-EASDF通过通信隧道，向V-UPF网元发送DNS响应消息#1和通信隧道的TID2。相应的，V-UPF网元通过通信隧道，接收来自V-EASDF的DNS响应消息#1和通信隧道的TID2。
DNS响应消息#1可以用于响应DNS查询消息#1。例如，DNS响应消息#1可以携带DNS查询消息#1查询的EAS的IP地址。DNS响应消息#1的源地址为IP地址2，目的地址为IP地址1。也就是说，V-EASDF可以通过与V-SMF网元以及DNS服务器交互，获得EAS的IP地址，具体可以参考上述S308-S318的相关介绍，不再赘述。然后，V-EASDF可以根据DNS消息处理规则中操作的指示，将边缘服务对应的EAS的IP地址封装到DNS响应消息#1中，通过通信隧道向V-UPF网元发送DNS响应消息#1和通信隧道的TID2，具体实现可参考上述S703中的相关介绍，不再赘述。
S911，V-UPF网元向UE发送DNS响应消息#1。相应的，UE接收来自V-UPF网元的DNS响应消息#1。
V-UPF网元在接收到DNS响应消息#1和通信隧道的TID2后，可以确定将通信隧道 的TID2对应的DNS响应消息#1映射到UE的HR PDU会话，以通过该HR PDU会话向UE发送DNS响应消息#1。例如，V-UPF网元可以将DNS响应消息#1中的源地址由IP地址2替换为IP地址3，然后向UE发送该DNS响应消息#1。这样，UE可以从DNS响应消息#1中获得EAS的IP地址，然后根据EAS的IP地址访问该EAS，以获得相应的边缘服务。当然，V-UPF网元也可以根据UPF处理规则执行S911中的处理逻辑，不做限定。
此外，S910-S911的具体实现也可以参考上述第一种可能的设计方案中的相关介绍，不再赘述。
S912，V-EASDF通过通信隧道，向V-UPF网元发送DNS查询消息#2和通信隧道的TID2。相应的，V-UPF网元通过通信隧道，接收来自V-EASDF的DNS查询消息#2和通信隧道的TID2。
DNS查询消息#2可以用于请求其他应用服务的IP地址。DNS查询消息#2的源地址为IP地址2，目的地址为IP地址3。也就是说，在确定请求其他应用服务的IP地址的情况下，V-EASDF可以将DNS查询消息#1的源地址从IP地址1替换为IP地址2，并将DNS查询消息#1的目的地址从IP地址2替换为IP地址3，得到DNS查询消息#2。或者，V-EASDF也可以直接生成DNS查询消息#2。此后，V-EASDF可以通过通信隧道向V-UPF网元发送DNS查询消息#2和通信隧道的TID2。
其中，V-EASDF通过通信隧道向V-UPF网元发送DNS查询消息#2和通信隧道的TID2的具体实现，可以参考上述S908和S910中的相关介绍，不再赘述。
S913，V-UPF网元向H-DNS服务器发送DNS查询消息#3。相应的，H-DNS服务器接收来自V-UPF网元的DNS查询消息#3。
DNS查询消息#3可以用于请求H-DNS服务器提供服务。DNS查询消息#3的源地址为IP地址1，目的地址为IP地址3。也就是说，V-UPF网元在接收到DNS查询消息#2和通信隧道的TID2后，可确定将通信隧道的TID2对应的DNS查询消息#2映射到UE的HR PDU会话。例如，V-UPF网元可以将DNS查询消息#2的源地址从IP地址2替换为IP地址1，得到DNS查询消息#3，或者直接生成DNS查询消息#3，然后将DNS查询消息#3映射到UE的HR PDU会话，以通过HR PDU会话(即通过H-UPF网元(图8未示出))向H-DNS服务器发送DNS查询消息#3。当然，V-UPF网元也可以根据UPF处理规则执行S912中的处理逻辑，不做限定。
此外，S912-S913的具体实现也可以参考上述第二种可能的设计方案中的相关介绍，不再赘述。
S914，H-DNS服务器通过H-UPF网元向V-UPF网元发送DNS响应消息#2。相应的，V-UPF网元通过H-UPF网元接收来自H-DNS服务器的DNS响应消息#2。
DNS响应消息#2可以为DNS查询消息#3的响应消息，例如DNS响应消息#2可以携带其他应用服务的IP地址。DNS响应消息#2的源地址为IP地址3，目的地址为IP地址1。
S915，V-UPF网元通过通信隧道，向V-EASDF发送DNS响应消息#3和通信隧道的TID1。相应的，V-EASDF通过通信隧道，接收来自V-UPF网元的DNS响应消息#3和通信隧道的TID1。
DNS响应消息#3可以为DNS查询消息#2的响应消息，例如DNS响应消息#3可以携带其他应用服务的IP地址。DNS响应消息#3的源地址为IP地址3，目的地址为IP地址2。 也就是说，对于来自H-DNS服务器的DNS响应消息#2，V-UPF网元可确定向V-EASDF发送DNS响应消息#3和通信隧道的TID1。例如，V-UPF网元可以将DNS响应消息#2的目的地址从IP地址1替换为IP地址2，以得到DNS响应消息#3，或直接生成DNS响应消息#3，然后通过通信隧道向V-EASDF发送DNS响应消息#3和通信隧道的TID1。当然，V-UPF网元也可以根据UPF处理规则执行S915中的处理逻辑，不做限定。此外，S915的具体实现可参考上述S703中的相关介绍，不再赘述。
S916，V-EASDF通过通信隧道，向V-UPF网元发送DNS响应消息#4和通信隧道的TID1。相应的，V-UPF网元通过通信隧道，接收来自V-EASDF的DNS响应消息#4和通信隧道的TID1。
DNS响应消息#4可以为DNS查询消息#1的响应消息，例如DNS响应消息#4可以携带其他应用服务的IP地址。DNS响应消息#4的源地址为IP地址2，目的地址为IP地址1。也就是说，V-EASDF接收到DNS响应消息#3后，可将DNS响应消息#3匹配到对应的DNS消息处理规则。如此，V-EASDF可根据该DNS响应消息#3匹配的DNS消息处理规则，将DNS响应消息#3的源地址从IP地址3替换为IP地址2，并将DNS响应消息#3的目的地址从IP地址2替换为IP地址1，以得到DNS响应消息#4。或者，V-EASDF可根据该DNS响应消息#3匹配的DNS消息处理规则，直接生成DNS响应消息#4。此后，V-EASDF可以根据该DNS响应消息#3匹配的DNS消息处理规则，通过通信隧道向V-UPF网元发送该DNS响应消息#4和通信隧道TID2。
S917，V-EASDF向V-UPF网元发送DNS响应消息#4。相应的，V-UPF网元接受来自V-EASDF的DNS响应消息#4。
V-UPF网元对DNS响应消息#4处理逻辑与上述DNS响应消息#1类似，可参考理解，不再赘述。
此外，S914-S917的具体实现也可以参考上述第三种可能的设计方案中的相关介绍，不再赘述。
可以理解，上述场景是以V-UPF网元和V-EASDF为例，但并不限定于此，例如V-UPF网元也可以替换为其他的V-UPF网元，V-EASDF也可以替换为其他的V-EASDF。
综上，由于UE不仅可以通过HPLMN分配的IP地址进行标识，还可通过VPLMN分配的通信隧道的TID1进行标识，如此，在IP地址可能冲突的情况下，仍可以通过通信隧道的TID1来对UE进行识别，以便于漫游UE能够获得边缘服务。进一步的，由于VPLMN可以为V-UPF网元配置针对非EC的DNS查询消息的UPF处理规则，以确保V-UPF网元能够向H-DNS服务器转发非EC的DNS查询消息，以便漫游UE还能够获得相应的应用服务。
实施例2：
示例性的，图10为本申请实施例提供的通信方法的流程示意图三。该通信方法适用于终端、用户面网元、边缘应用服务功能之间的交互。终端具体可以是上述通信系统中的UE、用户面网元具体可以是上述通信系统中的V-UPF网元、边缘应用服务功能具体可以是上述通信系统中的V-EASDF。该通信方法中，VPLMN可以针对终端分配第一地址，以避免出现地址冲突的情况。
如图10所示，该通信方法的流程具体如下：
S1001，用户面网元接收来自终端的第一DNS查询消息。
其中，S1001的具体实现可以参考上述S701中的相关介绍，不再赘述。
S1002，用户面网元将第一DNS查询消息的源地址由终端的地址替换为第一地址，以得到第二DNS查询消息，并向边缘应用服务功能发送第二DNS查询消息。
其中，终端的地址可以是HPLMN为终端分配的地址，如可以是IP地址或者其他任何可能的地址，不做限定。
第一地址可以是VPLMN针对终端分配的地址，具体可以是VPLMN针对终端的PDU会话分配的地址，或者说第一地址可以在VPLMN内映射到终端的PDU会话，例如第一地址可以指向该终端。第一地址可以由VPLMN内的网元确定，例如VPLMN内的用户面网元、会话管理网元或边缘应用服务功能。
一种可能实现中，第一地址可以是IP地址，例如IPv4地址或者IPv6地址，或者也可以是其他任何可能的地址。第一地址可由用户面网元确定。例如，用户面网元可确定第一地址，并向会话管理网元发送第一地址，以便VPLMN的网元，例如边缘应用服务功能能够从会话管理网元获得第一地址，从而根据第一地址识别该终端的消息，实现正确的数据路由。其中，用户面网元可自行确定第一地址，或者根据会话管理网元的指示确定第一地址，不做限定。
或者，另一种可能的方式中，第一地址可由会话管理网元确定。例如，在创建终端的PDU会话的过程，会话管理网元可确定第一地址，并向用户面网元发送第一地址。以及，可选地，会话管理网元还可向边缘应用服务功能发送第一地址。用户面网元可接收来自会话管理网元的第一地址，从而能够在发送终端的消息时携带第一地址，以便边缘应用服务功能能够根据第一地址识别该终端的消息，实现正确的数据路由。
或者，又一种可能的方式中，第一地址可由边缘应用服务功能确定。例如，边缘应用服务功能可确定第一地址，并向会话管理网元发送第一地址，以便用户面网元能够从会话管理网元获得第一地址，从而能够在发送终端的消息时携带第一地址，以便边缘应用服务功能能够根据第一地址识别该终端的消息，实现正确的数据路由。其中，边缘应用服务功能可自行确定第一地址，或者根据会话管理网元的指示确定第一地址，不做限定。
用户面网元接收到第一DNS查询消息，如通过终端的PDU会话接收到第一DNS查询消息，可根据第一DNS查询消息是来自终端，或根据第一DNS查询消息的源地址是终端的地址，确定向边缘应用服务功能发送第二DNS查询消息。例如，用户面网元可以将第一DNS查询消息的源地址由终端的地址替换为第一地址，以得到第二DNS查询消息，并向边缘应用服务功能发送第二DNS查询消息。
其中，用户面网元可配置有第一用户面处理规则，第一用户面处理规则的配置方式可参考上述第一用户面处理规则的相关介绍，不再赘述。该第一用户面处理规则可以指示：对于第一DNS查询消息，用户面网元将第一DNS查询消息的源地址由终端的地址替换为第一地址，以得到第二DNS查询消息，并向边缘应用服务功能发送第二DNS查询消息；具体可以指示：对于第一DNS查询消息，如果第一DNS查询消息的目的地址为边缘应用服务功能的地址或者HPLMN内DNS服务器的地址，则用户面网元将第一DNS查询消息的源地址由终端的地址替换为第一地址，以得到第二DNS查询消息，并向边缘应用服务功能发送第二DNS查询消息。也就是说，用户面网元可根据第一用户面处理规则，执行 上述针对第一DNS查询消息的处理逻辑，从而可避免用户面网元误操作或误处理。当然，如果用户面网元没有配置第一用户面处理规则，则用户面网元可以默认按照上述处理逻辑处理第一DNS查询消息。
可以理解，第一用户面处理规则可以不限于第一DNS查询消息和第二DNS查询消息，也可以适用于来自终端的DNS查询消息，以及向边缘应用服务功能发送的DNS查询消息。例如，第一用户面处理规则可以指示：对于来自终端的DNS查询消息，用户面网元将DNS查询消息的源地址由终端的地址替换为第一地址，以得到DNS查询消息，并向边缘应用服务功能发送DNS查询消息。这种情况下，第一DNS查询消息为来自终端的DNS查询消息中的一条消息，第二DNS查询消息为向边缘应用服务功能发送的DNS查询消息中的一条消息。
对于边缘应用服务功能而言，边缘应用服务功能保存有DNS上下文，该DNS上下文可以是边缘应用服务功能预先配置的，或者预先由会话管理网元提供，或者边缘应用服务功能预先根据会话管理网元提供的信息自行生成的，不做限定。该DNS上下文可以包括：第一地址以及DNS消息处理规则。该DNS消息处理规则可以包括DNS消息检测模版和操作。DNS消息检测模版可以包括：FQDN，该FQDN可用于与第二DNS查询消息携带的FQDN匹配。操作可以指示：边缘应用服务功能发送第一DNS响应消息。可以看出，由于DNS上下文中的地址是第一地址，而不是HPLMN的地址，如终端的IP地址，使得边缘应用服务功能能够根据第二DNS查询消息，匹配到对应的DNS上下文，从而执行相应的处理，如向用户面网元发送第一DNS响应消息，以实现正确的数据路由。此外，DNS上下文的具体实现也可以参考上述S303中的相关介绍，不再赘述。
可选地，第四种可能的设计方案中，该通信方法还可以包括：用户面网元接收来自边缘应用服务功能的第一DNS响应消息；用户面网元将第一DNS响应消息的目的地址由第一地址替换为终端的地址，以得到第二DNS响应消息，从而向终端发送第二DNS响应消息。
其中，第一DNS响应消息可以是第二DNS查询消息的响应消息，例如第一DNS响应消息可以携带应用服务的地址，如边缘应用服务的地址。边缘应用服务功能在将第二DNS查询消息匹配到对应的DNS上下文后，可确定该第二DNS查询消息是否与该DNS上下文中的DNS消息处理规则匹配，如第二DNS查询消息中的FQDN是否与该DNS消息处理规则中的FQDN匹配。此时，如果第二DNS查询消息中的FQDN与该DNS消息处理规则中的FQDN匹配，也即存在与第二DNS查询消息匹配的DNS消息处理规则，则边缘应用服务根据该DNS消息处理规则中的操作，向用户面网元发送第一DNS响应消息。
用户面网元在接收到第一DNS响应消息后，可根据第一DNS响应消息是来自边缘应用服务功能的消息，以及还可以进一步根据第一DNS响应消息的目的地址是第一地址，确定将第一DNS响应消息映射到终端的PDU会话。例如，用户面网元可以将第一DNS响应消息的目的地址由第一地址替换为终端的地址，以得到第二DNS响应消息，并通过终端的PDU会话，向终端发送第二DNS响应消息，以便终端能够获得边缘服务。
其中，用户面网元可配置有第二用户面处理规则。第二用户面处理规则的配置方式与第一用户面处理规则类似，可参考理解，不再赘述。第二用户面处理规则可以指示：对于第一DNS响应消息，用户面网元将第一DNS响应消息的目的地址由第一地址替换为终端 的地址，以得到第二DNS响应消息，并向终端发送第二DNS响应消息。以及，第二用户面处理规则具体可以指示：对于第一DNS响应消息，如果第一DNS响应消息的目的地址为第一地址，则用户面网元将第一DNS响应消息的目的地址由第一地址替换为终端的地址，以得到第二DNS响应消息，并向终端发送第二DNS响应消息。也就是说，用户面网元可根据第二用户面处理规则，执行上述针对第一DNS响应消息的处理逻辑，从而可避免用户面网元误操作或误处理。当然，如果用户面网元没有配置第二用户面处理规则，则用户面网元可以默认按照上述处理逻辑处理第一DNS响应消息。
可以理解，第二用户面处理规则可以不限于第一DNS响应消息和第二DNS响应消息，也可以适用于来自边缘应用服务功能的DNS响应消息，以及向终端发送的DNS响应消息。例如，第二用户面处理规则可以指示：对于来自边缘应用服务功能的DNS响应消息，用户面网元将DNS响应消息的目的地址由第一地址替换为终端的地址，并向终端发送DNS响应消息。这种情况下，第一DNS响应消息为来自边缘应用服务功能的DNS响应消息中的一条消息，第二DNS响应消息为向终端发送的DNS响应消息中的一条消息。
可选地，第五种可能的设计方案中，该通信方法还可以包括：用户面网元接收来自边缘应用服务功能的第三DNS查询消息，将第三DNS查询消息的目的地址由第二地址替换为HPLMN内DNS服务器的地址，以得到第四DNS查询消息，从而向HPLMN发送第四DNS查询消息。
其中，第三DNS查询消息可以用于请求其他应用服务的地址。第三DNS查询消息的目的地址可以是第二地址。第二地址可以是VPLMN针对终端分配的地址。第二地址具体可以是VPLMN针对终端的PDU会话分配的标识，或者说第二地址可以在VPLMN内映射到终端的PDU会话。例如，第二地址可以指示该HPLMN内的DNS服务器，也即用户面网元可以基于第二地址，将终端的消息映射到该PDU会话，以便向HPLMN内的DNS服务器发送该消息。
边缘应用服务功能在将第二DNS查询消息匹配到对应的DNS上下文后，可确定该第二DNS查询消息是否与该DNS上下文中的DNS消息处理规则匹配，如第二DNS查询消息中的FQDN是否与该DNS消息处理规则中的FQDN匹配。此时，如果第二DNS查询消息中的FQDN与该DNS消息处理规则中的FQDN不匹配，也即不存在与第二DNS查询消息匹配的DNS消息处理规则，则边缘应用服务向用户面网元发送第三DNS查询消息。例如，边缘应用服务可根据该DNS上下文中的第二地址，生成第三DNS查询消息，并向用户面网元发送第三DNS查询消息。可以理解，由于DNS上下文中保存的是第二地址，而不是HPLMN的地址，如HPLMN内DNS服务器的地址，那么边缘应用服务功能在确定请求其他应用服务的地址时，可将第二地址作为目的地址携带到第三DNS查询消息，以便用户面网元能够识别该第二地址，从而向HPLMN发送相应的消息，如第四DNS查询消息。
第四DNS查询消息也可用于请求其他应用服务的地址。用户面网元在接收到第三DNS查询消息，可根据第三DNS查询消息是来自边缘应用服务功能的消息，以及还可以进一步根据第三DNS查询消息的目的地址是第二地址，确定将第三DNS查询消息映射到终端的PDU会话。例如，用户面网元可以将第三DNS查询消息的目的地址由第二地址替换为HPLMN内DNS服务器的地址，以得到第四DNS查询消息，从而向HPLMN发送第四DNS 查询消息，如通过终端的PDU会话向HPLMN发送第四DNS查询消息。其中，HPLMN内DNS服务器的地址可以是HPLMN内的地址，例如HPLMN为该DNS服务器分配的地址，如可以是IP地址或者其他任何可能的地址，不做限定。
其中，用户面网元可配置有第三用户面处理规则。第三用户面处理规则的配置方式与第一用户面处理规则类似，可参考理解，不再赘述。第三用户面处理规则可以指示：对于第三DNS查询消息，用户面网元将第三DNS查询消息的目的地址由第二地址替换为HPLMN内DNS服务器的地址，以得到第四DNS查询消息，并向边缘应用服务功能发送第四DNS查询消息。第三用户面处理规则具体可以指示：对于第三DNS查询消息，如果第三DNS查询消息的目的地址是第二地址，则用户面网元将第三DNS查询消息的目的地址由第二地址替换为HPLMN内DNS服务器的地址，以得到第四DNS查询消息，并向边缘应用服务功能发送第四DNS查询消息。如此，用户面网元可以根据配置的第三用户面处理规则，执行上述针对第三DNS查询消息的处理逻辑，从而可避免用户面网元误操作或误处理。当然，如果用户面网元没有配置第三用户面处理规则，则用户面网元可以默认按照上述处理逻辑处理第三DNS查询消息。
可以理解，第三用户面处理规则可以不限于第三DNS查询消息和第四DNS查询消息，也可以适用于来自边缘应用服务功能的DNS查询消息，以及向HPLMN发送的DNS查询消息。例如，第三用户面处理规则可以指示：对于来自边缘应用服务功能的DNS查询消息，用户面网元向HPLMN发送DNS查询消息。这种情况下，第三DNS查询消息为来自边缘应用服务功能的DNS查询消息中的一条消息，第四DNS查询消息为向HPLMN发送的DNS查询消息中的一条消息。
可选地，第六种可能的设计方案中，该通信方法还可以包括：用户面网元接收来自HPLMN的第三DNS响应消息；用户面网元根据第三DNS响应消息，向边缘应用服务功能发送第四DNS响应消息；边缘应用服务功能接收来自用户面网元的第四DNS响应消息；边缘应用服务功能根据第四DNS响应消息，向用户面网元发送第五DNS响应消息；用户面网元接收来自边缘应用服务功能的第五DNS响应消息；用户面网元根据第五DNS响应消息，向终端发送第六DNS响应消息。
第三DNS响应消息可以为第四DNS查询消息的响应消息，第三DNS响应消息可携带其他应用服务的地址，用于终端获得相应的应用服务。第三DNS响应消息的源地址可以为HPLMN内DNS服务器的地址，第三DNS响应消息的目的地址可以终端的地址。用户面网元可以通过终端的PDU会话接收第三DNS响应消息。
第四DNS响应消息可以为第三DNS查询消息的响应消息。第四DNS响应消息可根据第三DNS响应消息确定。例如，用户面网元在接收到第三DNS响应消息后，可根据第三DNS响应消息来自HPLMN内的DNS服务器，以及可以进一步根据第三DNS响应消息的目的地址是终端的地址，确定向边缘应用服务功能发送第四DNS响应消息。例如，用户面网元可以将第三DNS响应消息的源地址由HPLMN内DNS服务器的地址替换为第二地址，并将第三DNS响应消息的目的地址由终端的地址替换为边缘应用服务功能的地址，以得到第四DNS响应消息，然后向边缘应用服务功能发送第四DNS响应消息。
其中，用户面网元可配置有第四用户面处理规则。第四用户面处理规则的配置方式与第一用户面处理规则类似，可参考理解，不再赘述。第四用户面处理规则可以指示：对于 第三DNS响应消息，用户面网元将第三DNS响应消息的源地址由HPLMN内DNS服务器的地址替换为第二地址，并将第三DNS响应消息的目的地址由终端的地址替换为边缘应用服务功能的地址，以得到第四DNS响应消息，然后向边缘应用服务功能发送第四DNS响应消息。第四用户面处理规则具体可以指示：对于第三DNS响应消息，如果第三DNS响应消息的目的地址是终端的地址，则用户面网元将第三DNS响应消息的源地址由HPLMN内DNS服务器的地址替换为第二地址，并将第三DNS响应消息的目的地址由终端的地址替换为边缘应用服务功能的地址，以得到第四DNS响应消息，然后向边缘应用服务功能发送第四DNS响应消息。如此，用户面网元可以根据配置的第四用户面处理规则，执行上述针对第三DNS响应消息的处理逻辑，从而可避免用户面网元误操作或误处理。当然，如果用户面网元没有配置第四用户面处理规则，则用户面网元可默认按照上述处理逻辑处理第三DNS响应消息。
可以理解，第四用户面处理规则可以不限于第三DNS响应消息和第四DNS响应消息，也可以适用于来自HPLMN的DNS响应消息，以及向边缘应用服务功能发送的DNS响应消息。例如，第四用户面处理规则可以指示：对于来自HPLMN的DNS响应消息，用户面网元将DNS响应消息的源地址由HPLMN内DNS服务器的地址替换为第二地址，并将DNS响应消息的目的地址由终端的地址替换为边缘应用服务功能的地址，然后向边缘应用服务功能发送DNS响应消息。这种情况下，第三DNS响应消息为来自HPLMN的DNS响应消息中的一条消息，第四DNS响应消息为向边缘应用服务功能发送的DNS响应消息中的一条消息。
第五DNS响应消息为第二DNS查询消息的响应消息。第五DNS响应消息可根据第四DNS响应消息确定。例如，边缘应用服务功能在接收到第四DNS响应消息，可根据第四DNS响应消息与对应的DNS消息处理规则匹配，将第四DNS响应消息的源地址由第二地址替换为边缘应用服务功能的地址，并将第四DNS响应消息的目的地址由边缘应用服务功能的地址替换为第一地址，以得到第五DNS响应消息，然后向用户面网元发送第五DNS响应消息。
第六DNS响应消息可以为第一DNS查询消息的响应消息。第六DNS响应消息可根据第五DNS响应消息确定，具体实现与上述第二DNS响应消息类似，可参考理解，不再赘述。
综上，根据上述通信方法可知，在终端漫游至VPLMN时，该终端的HPLMN分配的地址可能与VPLMN的其他终端的地址冲突。因此，边缘应用服务功能可使用VPLMN针对该终端分配的第一地址来标识该终端的DNS查询消息，以避免出现地址冲突，实现正确的数据路由，便于终端获得应用服务，如边缘服务。
可以理解，以上介绍了该通信方法在实施例2中的整体流程，下面介绍该通信方法在实施例2中的具体流程。
示例性的，图11为实施例2在具体场景中的架构示意图。该场景涉及UE、V-UPF网元、V-SMF网元、V-EASDF、H-DNS服务器。UE可以是上述方法中的终端、V-UPF网元可以是上述方法中的用户面网元、V-SMF网元可以是上述方法中的会话管理网元、V-EASDF可以是上述方法中的边缘应用服务功能、H-DNS服务器可以是上述HPLMN内的DNS服务器。定义该场景中：UE的IP地址为IP地址1，IP地址1也是HPLMN为UE 分配的地址。V-EASDF的IP地址为IP地址2。H-DNS服务器的IP地址为IP地址3，IP地址3也是HPLMN为H-DNS服务器分配的地址。这种情况下，VPLMN可以针对UE分配一个IP地址4(上述第一地址)，以及针对H-DNS服务器分配一个IP地址5(上述第二地址)。IP地址4和IP地址5可以映射到UE的HR PDU会话，例如，IP地址4可以指向该HR PDU会话内的UE，IP地址5可以指向该HR PDU会话内的H-DNS服务器。IP地址4和IP地址5可以保存在该HR PDU会话对应的DNS上下文中。
在此基础上，V-UPF网元的行为主要通过UPF处理规则指示，该UPF处理规则可以包括：1)对于来自UE的DNS查询消息V-UPF网元将DNS查询消息的源地址由IP地址1替换为IP地址4，向V-EASDF发送DNS查询消息。2)对于来自V-EASDF的DNS响应消息，V-UPF网元将DNS响应消息的目的地址由IP地址4替换为IP地址1，向UE发送DNS响应消息。3)对于来自V-EASDF的DNS查询消息，V-UPF网元将DNS查询消息的目的地址由IP地址5替换为IP地址3，向H-DNS服务器发送DNS查询消息。4)对于来自H-DNS服务器的DNS响应消息，V-UPF网元将DNS响应消息的源地址从IP地址3替换为IP地址5，以及将DNS响应消息的目的地址从IP地址1替换为IP地址2，向V-EASDF发送DNS响应消息。
V-EASDF的行为主要通过DNS消息处理规则指示，该DNS消息处理规则：DNS消息检测模板和操作。DNS消息检测模板包括：FQDN，该FQDN可用于与来自UE的DNS查询消息中的FQDN匹配。操作可用于指示：V-EASDF发送DNS响应消息。
图12为本申请实施例提供的通信方法的流程示意图四。该通信方法适用于图10所示的场景，如图12所示，该通信方法的具体流程如下：
S1201，H-SMF网元向V-SMF网元发送PDU会话创建响应消息。相应的，V-SMF网元接收来自H-SMF网元的PDU会话创建响应消息。
其中，S1201的具体实现原理与上述S901类似，可以参考理解，不再赘述。
S1202，V-SMF网元向V-UPF网元发送N4会话修改请求消息。相应的，V-UPF网元接收来自V-SMF网元的N4会话修改请求消息。
N4会话修改请求消息可以携带第二指示信息。第二指示信息可以用于指示V-UPF网元分配IP地址4和/或IP地址5。当然，N4会话修改请求消息也可以不携带第二指示信息，V-UPF网元在接收到N4会话修改请求消息的情况下，默认UE分配IP地址4和/或IP地址5。
S1203，V-UPF网元分配IP地址4和/或IP地址5。
其中，V-UPF网元可以采用任何可能的方式分配IP地址4和IP地址5。例如，V-UPF网元可以在地址池中随机选择2个未使用的IP地址分别作为IP地址4和IP地址5。又例如，V-UPF网元可以在地址池中按顺序选择2个未使用的IP地址作为IP地址4和IP地址5。
S1204，V-UPF网元向V-SMF网元发送N4会话修改响应(N4Sseesion Modification Response)消息。相应的，V-SMF网元接收来自V-UPF网元的N4会话修改响应消息。
N4会话修改请求消息可以携带IP地址4和/或IP地址5。
可以理解，S1202-S1204为可选步骤。例如，IP地址4和/或IP地址5可以由V-SMF网元确定，这种情况下，S1202-S1204可以不执行。此外，S1202-S1204也可以参考上述 S1002中的相关介绍，不再赘述。
S1205，V-SMF网元向V-EASDF发送DNS上下文创建请求消息。相应的，V-EASDF接收来自V-SMF网元的DNS上下文创建请求消息。
DNS上下文创建请求消息可以用于请求EASDF创建UE的HR PDU会话对应的DNS上下文。该DNS上下文创建请求消息可以包括如下至少一项：IP地址4、IP地址5、以及DNS消息处理规则。DNS消息处理规则的具体实现可参考图10以及上述S303中的相关介绍，不再赘述。
可以理解，DNS上下文创建请求消息携带DNS消息处理规则为一种可选实现方式。例如，DNS消息处理规则可以预先配置或者协议预定义在V-EASDF上。这种情况下，DNS上下文创建请求消息可以携带IP地址4和IP地址5，而不携带DNS消息处理规则。此时IP地址4和IP地址5等信息可以用于触发V-EASDF激活本地的DNS消息处理规则。或者，DNS上下文创建请求消息还可以携带一个额外的信元，该信元可以用于触发V-EASDF激活本地的DNS消息处理规则。又例如，DNS消息处理规则可以由V-EASDF根据一些必要参数自行确定。这种情况下，DNS上下文创建请求消息可以仅携带这些必要参数，如包括如下至少一项：IP地址4和IP地址5等等。
V-EASDF可以根据DNS上下文创建请求消息，创建该UE的HR PDU会话对应的DNS上下文，并将如下至少一项：IP地址5、IP地址4、以及DNS消息处理规则存储到该DNS上下文中。
此外，S1205的具体实现也可以参考上述S303-S304中的相关介绍，不再赘述。
S1206，V-SMF网元向V-UPF网元发送N4规则。相应的，V-UPF网元接收来自V-SMF网元的N4规则。
N4规则可以承载在N4会话中，如N4会话修改响应消息，该N4会话与UE的HR PDU会话对应。N4规则可以包括如下至少一项：IP地址1、IP地址2、IP地址3、IP地址4、IP地址5、以及UPF处理规则。UPF处理规则的具体实现可参考图10中的相关介绍，不再赘述。UPF处理规则也可以参考上述用户面处理规则的相关介绍，本申请实施例以UPF处理规则为例进行说明，本领域技术人员能够理解，本申请实施例中UPF处理规则可以替换为用户面处理规则。也即是当用户面处理规则为除UPF处理规则以外的其他形式的信息时，也是类似处理。
可以理解，N4规则携带UPF处理规则为一种可选实现方式。例如，UPF处理规则可以预先配置或者协议预定义在V-UPF网元上。这种情况下，N4规则可以携带如下至少一项：IP地址1、IP地址2、IP地址3、IP地址4、IP地址5，而不携带UPF处理规则。此时，IP地址1、IP地址2、IP地址3、IP地址4、IP地址5等信息可以用于触发V-UPF网元激活本地的UPF处理规则。或者，N4规则还可以携带一个额外的信元，该信元可以用于触发V-UPF网元激活本地的UPF处理规则。又例如，DNS消息处理规则可以由V-UPF网元根据一些必要参数自行确定。这种情况下，N4规则可以仅携带这些必要参数，如包括如下至少一项：IP地址1、IP地址2、IP地址3、IP地址4、IP地址5等等。
可以理解，由于V-UPF网元是通过UE的HR PDU会话对应N4会话获得UPF处理规则，这种获得方式可以隐式指示该UPF处理规则与该HR PDU会话对应，以便V-UPF网元可以根据UPF处理规则，将对应的消息(如下文提到的DNS响应消息#1和DNS查询 消息#3)映射到该HR PDU会话，以通过该HR PDU会话发送这些消息。当然，也可以由UPF处理规则直接定义这些消息需要被映射到该HR PDU会话。
可以理解，S1201-S1206为HR场景下的HR PDU会话创建流程中的步骤，也即本申请实施例适用该于流程，该流程具体可以参考TSXXXX，不再赘述。此外，S1206与S1205之间的执行顺序不限定。
S1207，UE向V-UPF网元发送DNS查询消息#1。相应的，V-UPF网元接收来自UE的DNS查询消息#1。
其中，S1207的具体实现原理与上述S907类似，可参考理解，不再赘述。
S1208，V-UPF网元向V-EASDF发送DNS查询消息#2。相应的，V-EASDF接收来自V-UPF网元的DNS查询消息#2。
DNS查询消息#2的源地址可以为IP地址4，目的地址可以为IP地址2或IP地址3。也就是说，V-UPF网元可以根据DNS查询消息#1，确定DNS查询消息#2。例如，在接收到DNS查询消息#1后，根据UPF处理规则，将DNS查询消息#1的源地址从IP地址1替换为IP地址4，得到DNS查询消息#2。然后，V-UPF网元可以根据UPF处理规则，向V-EASDF向发送DNS查询消息#2，具体实现可参考上述S1002中的相关介绍，不再赘述。
S1209，V-EASDF确定是否存在与DNS查询消息#2匹配的DNS消息处理规则。
其中，V-EASDF可以根据DNS查询消息#2的源地址为IP地址4，匹配到保存有IP地址4的DNS上下文。此时，V-EASDF可以确定该DNS上下文中是否存在与DNS查询消息#2匹配的DNS消息处理规则。如果存在与DNS查询消息#1匹配的DNS消息处理规则，如DNS查询消息#1中的FQDN与DNS消息处理规则中的FQDN匹配，也即DNS查询消息#2与DNS消息检测模板匹配，则表征DNS查询消息#1用于请求的应用服务为边缘服务，从而触发执行S1210-S1211，用以为UE提供边缘服务。如果不存在与DNS查询消息#1配的DNS消息处理规则，如DNS查询消息#1中的FQDN与DNS消息处理规则中的FQDN不匹配，也即DNS查询消息#2与DNS消息检测模板不匹配，则表征DNS查询消息#1请求的应用服务并非边缘应用服务，而是其他应用服务。如此，V-EASDF可以触发执行S1212-S1216，用以为UE提供相应的应用服务。
此外，S1209的具体实现也可以参考上述S1002、第四种可能的设计方案以及第五种可能的设计方案中的相关介绍，不再赘述。
S1210，V-EASDF向V-UPF网元发送DNS响应消息#1。相应的，V-UPF网元接收来自V-EASDF的DNS响应消息#1。
DNS响应消息#1可以用于响应DNS查询消息#1。例如，DNS响应消息#1可以携带DNS查询消息#1查询的某个EAS的IP地址。DNS响应消息#1的源地址为IP地址2，目的地址为IP地址4。DNS响应消息#1可以携带边缘服务对应的EAS的IP地址。也就是说，V-EASDF可以通过与V-SMF网元以及DNS服务器交互，获得EAS的IP地址，具体可以参考上述S308-S318的相关介绍，不再赘述。然后，V-EASDF可以根据DNS消息处理规则中操作的指示，将边缘服务对应的EAS的IP地址封装到DNS响应消息#1中，从而向V-UPF网元发送DNS响应消息#1。
S1211，V-UPF网元向UE发送DNS响应消息#2。相应的，UE接收来自V-UPF网元的DNS响应消息#2。
DNS响应消息#2的源地址为IP地址2或IP地址3，目的地址为IP地址1。也就是说，V-UPF网元可以根据到DNS响应消息#1，确定DNS响应消息#2。例如，V-UPF网元在接收到DNS响应消息#1后，可以根据DNS响应消息#1的目的地址从IP地址4，确定将DNS响应消息#1映射到UE的HR PDU会话。例如，V-UPF网元可以将DNS响应消息#1的目的地址从IP地址4替换为IP地址1，以得到DNS响应消息#2。或者，如果DNS查询消息#1的目的地址是IP地址3，则V-UPF网元还可将DNS响应消息#1中的源地址由IP地址2替换为IP地址3，以得到DNS响应消息#2。然后，V-UPF网元将DNS响应消息#2映射到UE的HR PDU会话，以通过HR PDU会话向UE发送DNS响应消息#2。这样，UE可以从DNS响应消息#2中获得EAS的IP地址，然后根据EAS的IP地址访问该EAS，以获得相应的边缘服务。当然，如果V-UPF网元确定DNS响应消息#1的目的地址不为IP地址4，则V-UPF网元可以丢弃该DNS响应消息#1。可以理解，V-UPF网元也可以根据UPF处理规则执行S1211中的处理逻辑，不做限定。
此外，S1210-S1211的具体实现也可以参考上述第四种可能的设计方案中的相关介绍，不再赘述。
S1212，V-EASDF向V-UPF网元发送DNS查询消息#3。相应的，V-UPF网元接收来自V-EASDF的DNS查询消息#3。
DNS查询消息#3可以用于请求H-DNS服务器提供服务。DNS查询消息#3的源地址为IP地址2，目的地址为IP地址5。也就是说，在确定请求其他应用服务的IP地址的情况下，V-EASDF确定可以向V-UPF网元发送DNS查询消息#3。例如，V-EASDF可以将DNS查询消息#2的源地址从IP地址4替换为IP地址2，并将DNS查询消息#2的目的地址从IP地址2替换为IP地址5，得到DNS查询消息#2。或者，V-EASDF也可以直接生成DNS查询消息#2。然后，V-EASDF可以根据DNS消息处理规则，向V-UPF网元发送DNS查询消息#3。
S1213，V-UPF网元向H-DNS服务器发送DNS查询消息#4。相应的，H-DNS服务器接收来自V-UPF网元的DNS查询消息#4。
DNS查询消息#4可以用于请求H-DNS服务器提供服务。DNS查询消息#4的源地址为IP地址1，目的地址为IP地址3。也就是说，V-UPF网元可以根据DNS查询消息#3，确定DNS查询消息#4。例如，V-UPF网元可以根据DNS查询消息#3的目的地址为IP地址5，确定将DNS查询消息#3映射到UE的HR PDU会话。例如，V-UPF网元可以将DNS查询消息#3的源地址从IP地址2替换为IP地址1，并将DNS查询消息#3的目的地址从IP地址5替换为IP地址3，以得到DNS查询消息#4。然后，V-UPF网元可以将DNS查询消息#4映射到UE的HR PDU会话，以通过HR PDU会话向H-DNS服务器发送DNS查询消息#4。当然，如果V-UPF网元根据UPF处理规则，确定DNS查询消息#3的目的地址不为IP地址5，则V-UPF网元可以丢弃该DNS查询消息#3。可以理解，V-UPF网元也可以根据UPF处理规则执行S1213中的处理逻辑，不做限定。
此外，S1212-S1213的具体实现也可以参考上述第五种可能的设计方案中的相关介绍，不再赘述。
S1214，H-DNS服务器通过H-UPF网元向V-UPF网元发送DNS响应消息#3。相应的，V-UPF网元通过H-UPF网元接收来自H-DNS服务器的DNS响应消息#3。
其中，S1214的具体实现原理与上述S914类似，可参考理解，不再赘述。
S1215，V-UPF网元向V-EASDF发送DNS响应消息#4。相应的，V-EASDF接收来自V-UPF网元的DNS响应消息#4。
DNS响应消息#4可以为DNS查询消息#3的响应消息。DNS响应消息#4的源地址为IP地址5，目的地址为IP地址2。也就是说，V-UPF网元可以根据DNS响应消息#3，确定DNS响应消息#4。例如，V-UPF网元在接收到DNS响应消息#3后，可根据UPF处理规则，确定目的地址为IP地址1DNS响应消息#3是需要向V-EASDF发送的消息。如此，V-UPF网元可以根据UPF处理规则，将DNS响应消息#3的源地址从IP地址3替换为IP地址5，并将DNS响应消息#3的目的地址从IP地址1替换为IP地址2，以得到DNS响应消息#4。然后，V-UPF网元可以根据UPF处理规则，向V-EASDF发送DNS响应消息#4。当然，如果V-UPF网元根据UPF处理规则，确定DNS响应消息#3的目的地址不为IP地址1，则V-UPF网元可以丢弃该DNS响应消息#3。可以理解，V-UPF网元也可以根据UPF处理规则执行S1215中的处理逻辑，不做限定。
S1216，V-EASDF向V-UPF网元发送DNS响应消息#5。相应的，V-UPF网元接收来自V-EASDF的DNS响应消息#5。
DNS响应消息#5可以为DNS查询消息#2的响应消息。DNS响应消息#5的源地址为IP地址2，目的地址为IP地址4。V-EASDF可以根据DNS响应消息#4，确定DNS响应消息#5。例如，V-EASDF接收到DNS响应消息#4后，可将DNS响应消息#4匹配到对应的DNS消息处理规则。如此，V-EASDF可根据该DNS响应消息#4对应的DNS消息处理规则，DNS响应消息#4的源地址从IP地址5替换为IP地址2，将DNS响应消息#4的目的地址从IP地址2替换为IP地址4，从而得到DNS响应消息#5，并向V-UPF网元返回该DNS响应消息#5，
S1217，V-EASDF向UE发送DNS响应消息#6。相应的，UE接收来自V-EASDF的DNS响应消息#6。
DNS响应消息#6可以为DNS查询消息#1的响应消息。DNS响应消息#6的源地址为IP地址2或IP地址3，目的地址为IP地址1。也就是说，V-UPF网元可以根据到DNS响应消息#5，确定DNS响应消息#6，具体实现可以参考上述DNS响应消息#2的相关介绍，不再赘述。
此外，S1214-S1217的具体实现也可以参考上述第六种可能的设计方案中的相关介绍，不再赘述。
可以理解，上述场景是以V-UPF网元和V-EASDF为例，但并不限定于此，例如V-UPF网元也可以替换为其他的V-UPF网元，V-EASDF也可以替换为其他的V-EASDF。
综上，在HPLMN为UE分配的IP地址可能与VPLMN分配的IP地址冲突的情况下，通过VPLMN分配的IP地址来标识该UE的DNS消息，可避免出现IP地址冲突，以便UE能够获得边缘服务。进一步的，由于VPLMN还可以为V-UPF网元配置针对非EC的DNS查询消息的处理规则，以确保V-UPF网元能够向H-DNS服务器或H-EASDF转发非EC的DNS查询消息，确保UE能够访问H-DNS服务器，获得相应的应用服务。
以上结合图7-图12详细说明了本申请实施例提供的通信方法。以下结合图13-图15详细说明用于执行本申请实施例提供的通信方法的通信装置。
示例性的，图13是本申请实施例提供的通信装置的结构示意图一。如图13所示，通信装置1300包括：接收模块1301和发送模块1302。为了便于说明，图13仅示出了该通信装置的主要部件。
该通信装置1300可适用于图6中所示出的通信系统中，执行图7所示的方法中用户面网元的功能，或者执行图9所示的方法中V-UPF网元的功能。
其中，接收模块1301，用于接收来自终端的第一域名系统DNS查询消息，发送模块1302，用于向边缘应用服务功能发送第一DNS查询消息和第一标识。终端漫游至拜访公共陆地移动网VPLMN内，第一DNS查询消息用于查询应用服务的地址，第一标识是VPLMN针对终端分配的标识。第一标识用于边缘应用服务功能确定是否存在与第一标识匹配的DNS规则。
可以理解，第一标识可用于在VPLMN内标识终端。第一标识具体可以是VPLMN，如VPLMN内的网元，针对终端的协议数据单元PDU会话分配的标识，或者说第一标识可以在VPLMN内映射到终端的PDU会话。
一种可能的设计方案中，终端的PDU会话可以为终端的家乡路由HR PDU会话。
一种可能的设计方案中，接收模块1301，用于通过终端的PDU会话，接收来自终端的第一域名系统DNS查询消息。
一种可能的设计方案中，通信装置1300配置有第一用户面处理规则，该第一用户面处理规则指示：对于第一DNS查询消息，通信装置1300向边缘应用服务功能发送第一DNS查询消息和第一标识。
一种可能的设计方案中，发送模块1302，用于通过通信隧道，向边缘应用服务功能发送第一DNS查询消息和第一标识；第一标识携带在通信隧道的头部中。
可选地，第一标识为通信隧道的标识。
一种可能的设计方案中，第一标识还可以携带在第一DNS查询消息中，如携带在第一DNS查询消息的预留字段中。
一种可能的设计方案中，接收模块1301，还用于在发送模块1302向边缘应用服务功能发送第一DNS查询消息和第一标识之后，接收来自边缘应用服务功能的第一DNS响应消息和第二标识。通信装置1300还包括：处理模块(图13中未示出)；处理模块，用于根据第二标识，控制发送模块1302向终端发送第一DNS响应消息。第二标识是VPLMN针对终端分配的标识，第一DNS响应消息携带有应用服务的地址。
可以理解，第二标识可用于在VPLMN内标识终端。第二标识具体可以是VPLMN，如VPLMN内的网元，针对终端的PDU会话分配的标识，或者说第二标识可以在VPLMN内映射到终端的PDU会话。
可选地，通信装置1300配置有第二用户面处理规则，该第二用户面处理规则指示：对于第一DNS响应消息和第二标识，通信装置1300向终端发送第一DNS响应消息。
可选地，接收模块1301，用于通过通信隧道，接收来自边缘应用服务功能的第一DNS响应消息和第二标识；第二标识携带在通信隧道的头部中。
进一步的，第二标识为通信隧道的标识。第二标识与第一标识可能相同，或者也可能不同，不做限定。
可选地，第二标识还可以携带在第一DNS响应消息中，如携带在第一DNS响应消息 的预留字段中。
一种可能的设计方案中，接收模块1301，还用于在发送模块1302向边缘应用服务功能发送第一DNS查询消息和第一标识之后，接收来自边缘应用服务功能的第二DNS查询消息和第二标识。通信装置1300还包括：处理模块(图13中未示出)；该处理模块，用于根据第二DNS查询消息和第二标识，控制发送模块1302向终端的HPLMN发送第三DNS查询消息。第二标识是VPLMN针对终端分配的标识，第二DNS查询消息用于获取应用服务的地址，第三DNS查询消息用于请求应用服务的地址。
可以理解，第二标识可用于在VPLMN内标识终端。第二标识具体可以是VPLMN，如VPLMN内的网元，针对终端的PDU会话分配的标识，或者说第二标识可以在VPLMN内映射到终端的PDU会话。
可选地，通信装置1300配置有第三用户面处理规则，该第三用户面处理规则指示：对于来自边缘应用服务功能的第二DNS查询消息和第二标识，通信装置1300向终端的HPLMN发送第三DNS查询消息。
可选地，接收模块1301，用于通过通信隧道，接收来自边缘应用服务功能的第二DNS查询消息和第二标识；第二标识携带在通信隧道的头部中。
进一步的，第二标识为通信隧道的标识。第二标识与第一标识可能相同，或者也可能不同，不做限定。
可选地，第二标识还可以携带在第二DNS查询消息中，如携带在第二DNS查询消息的预留字段中。
一种可能的设计方案中，通信装置1300还包括：处理模块(图13中未示出)；该处理模块，用于在接收模块1301接收来自终端的第一DNS消息之前，确定第一标识，并控制发送模块1302向会话管理网元发送第一标识。或者，接收模块1301，用于接收来自会话管理网元的第一标识。
一种可能的设计方案中，通信装置1300还包括：处理模块(图13中未示出)；该处理模块，用于在接收模块1301接收来自终端的第一DNS消息之前，确定第二标识，并控制发送模块1302向会话管理网元发送第二标识。或者，接收模块1301，用于接收来自会话管理网元的第二标识。
可选地，发送模块1302和接收模块1301也可以集成为收发模块，用于实现通信装置1300的收发功能。
可选地，通信装置1300还可以包括存储模块，该存储模块存储有程序或指令。当该处理模块执行该程序或指令时，使得该通信装置1300可以执行图7或图9所述的方法。
需要说明的是，通信装置1300可以是网络设备，如用户面网元或者V-UPF网元，也可以是可设置于网络设备中的芯片(系统)或其他部件或组件，还可以是包含网络设备的装置，本申请对此不做限定。
此外，通信装置1300的技术效果可以参考上述通信方法的技术效果，此处不再赘述。
示例性的，图14是本申请实施例提供的通信装置的结构示意图二。如图14所示，通信装置1400包括：收发模块1401和处理模块1402。为了便于说明，图14仅示出了该通信装置的主要部件。
一些实施例中，通信装置1400可适用于图6中所示出的通信系统中，执行图7所示 的方法中边缘应用服务功能的功能，或者执行图9所示的方法中V-EASDF的功能。
收发模块1401，用于接收来自用户面网元的第一域名系统DNS查询消息和第一标识，处理模块1402，用于确定是否存在与第一DNS查询消息和第一标识匹配的DNS消息处理规则。第一标识是拜访公共陆地移动网VPLMN针对终端分配的标识，终端漫游至VPLMN内，第一DNS查询消息用于查询应用服务的地址。
一种可能的设计方案中，收发模块1401，用于通过通信隧道，接收来自用户面网元的第一DNS查询消息和第一标识；第一标识携带在通信隧道的头部中。
可选地，第一标识为通信隧道的标识。
一种可能的设计方案中，在存在与第一DNS查询消息和第一标识匹配的DNS消息处理规则的情况下，收发模块1401，用于向用户面网元发送第一DNS响应消息和第二标识。第二标识是VPLMN针对终端分配的标识，第一DNS响应消息携带有应用服务的地址。
可选地，通信装置1400配置有DNS消息处理规则，该DNS消息处理规则指示：该装置1400向用户面网元发送第一DNS响应消息和第二标识。
可选地，收发模块1401，用于通过通信隧道，向用户面网元发送第一DNS响应消息和第二标识；第二标识携带在通信隧道的头部中。
进一步的，第二标识为通信隧道的标识。
一种可能的设计方案中，在不存在与第一DNS查询消息和第一标识匹配的DNS消息处理规则的情况下，收发模块1401，用于向用户面网元发送第二DNS查询消息和第二标识；第二标识是VPLMN针对终端分配的标识，第二DNS查询消息用于获取应用服务的地址。
可选地，收发模块1401，用于通过通信隧道，向用户面网元发送第二DNS查询消息和第二标识。第二标识携带在通信隧道的头部中。
可选地，第二标识为通信隧道的标识。
一种可能的设计方案中，处理模块1402，还用于在收发模块1401接收来自用户面网元向的第一DNS查询消息和第一标识之前，确定第一标识，并控制收发模块1401向会话管理网元发送第一标识。或者，收发模块1401，用于接收来自会话管理网元的第一标识。
一种可能的设计方案中，处理模块1402，还用于在收发模块1401接收来自用户面网元向的第一DNS查询消息和第一标识之前，确定第二标识，并控制收发模块1401向会话管理网元发送第二标识。或者，收发模块1401，用于接收来自会话管理网元的第二标识。
可选地，收发模块1401也可以包括发送模块和接收模块，发送模块用于实现通信装置1400的发送功能，接收模块用于实现通信装置1400的接收功能。
可选地，通信装置1400还可以包括存储模块，该存储模块存储有程序或指令。当该处理模块1402执行该程序或指令时，使得该通信装置1400可以执行图7或图9所示的方法。
需要说明的是，通信装置1400可以是网络设备，如边缘应用服务功能或者V-EASDF，也可以是可设置于网络设备中的芯片(系统)或其他部件或组件，还可以是包含网络设备的装置，本申请对此不做限定。
此外，通信装置1400的其他技术效果可以参考上述通信方法的技术效果，此处不再赘述。
另一些实施例中，通信装置1400可适用于图6中所示出的通信系统中，执行图7所示的方法中会话管理网络的功能，或者执行图9所示的方法中V-SMF网元的功能。
其中，处理模块1402，用于确定第一标识；收发模块1401，用于向用户面网元发送第一标识。第一标识是终端对应的拜访公共陆地移动网VPLMN内的标识，终端漫游至VPLMN内。
一种可能的设计方案中，收发模块1401，用于向边缘应用服务功能发送第一标识。
一种可能的设计方案中，处理模块1402，用于在终端的协议数据单元PDU会话建立过程中，确定第一标识。可选地，终端的PDU会话为终端的家乡路由HR PDU会话。
一种可能的设计方案中，处理模块1402，用于确定第二标识；收发模块1401，用于向用户面网元发送第二标识。
可选地，收发模块1401，用于边缘应用服务功能发送第二标识。
可选地，收发模块1401也可以包括发送模块和接收模块，发送模块用于通信装置1400的发送功能，接收模块用于实现通信装置1400的接收功能。
可选地，通信装置1400还可以包括存储模块，该存储模块存储有程序或指令。当该处理模块1402执行该程序或指令时，使得该通信装置1400可以执行图7或图9所述的方法。
需要说明的是，通信装置1400可以是网络设备，如会话管理网元或者V-SMF网元，也可以是可设置于网络设备中的芯片(系统)或其他部件或组件，还可以是包含网络设备的装置，本申请对此不做限定。
再一些实施例中，通信装置1400可适用于图6中所示出的通信系统中，执行图10所示的方法中用户面网元的功能，或者执行图12所示的方法中V-UPF网元的功能。
其中，收发模块1401，用于接收来自终端的第一域名系统DNS查询消息，处理模块1402，用于将第一DNS查询消息的源地址由终端的地址替换为第一地址，以得到第二DNS查询消息，从而控制收发模块1401向边缘应用服务功能发送第二DNS查询消息。其中，终端漫游至拜访公共陆地移动网VPLMN内，第一DNS查询消息用于查询应用服务的地址，第一地址是VPLMN针对终端分配的地址。
可以理解，第一地址具体可以是VPLMN，如VPLMN内的网元，针对终端的协议数据单元PDU会话分配的标识，或者说第一地址可以映射到终端的PDU会话。
一种可能的设计方案中，收发模块1401，用于通过终端的PDU会话，接收来自终端的第一域名系统DNS查询消息。
一种可能的设计方案中，终端的PDU会话可以为终端的家乡路由HR PDU会话。
一种可能的设计方案中，通信装置1400配置有第一用户面处理规则，该第一用户面处理规则指示：对于第一DNS查询消息，该装置将第一DNS查询消息的源地址由终端的地址替换为第一地址，以得到第二DNS查询消息，并向边缘应用服务功能发送第二DNS查询消息。
一种可能的设计方案中，收发模块1401，用于在向边缘应用服务功能发送第二DNS查询消息之后，接收来自边缘应用服务功能的第一DNS响应消息，该第一DNS响应消息携带有应用服务的地址。处理模块1402，用于将第一DNS响应消息的目的地址由第一地址替换为终端的地址，以得到第二DNS响应消息，从而控制收发向终端发送第二DNS响 应消息。
可选地，通信装置1400配置有第二用户面处理规则，该第二用户面处理规则指示：对于第一DNS响应消息，该装置将第一DNS响应消息的目的地址由第一地址替换为终端的地址，以得到第二DNS响应消息，并向边缘应用服务功能发送第二DNS响应消息。
一种可能的设计方案中，收发模块1401，用于在向边缘应用服务功能发送第二DNS查询消息之后，接收来自边缘应用服务功能的第三DNS查询消息。处理模块1402，用于将第三DNS查询消息的目的地址由第二地址替换为HPLMN内DNS服务器的地址，以得到第四DNS查询消息，从而控制收发模块1401向HPLMN发送第四DNS查询消息。其中，第二地址是VPLMN针对终端分配的地址。第二地址具体可以是VPLMN针对终端的协议数据单元PDU会话分配的标识，或者说第二地址可以映射到终端的PDU会话，也即用户面网元可以基于第二地址，将终端的消息映射到终端的PDU会话。第二地址与第一地址可以不同。
可选地，第九方面所述的通信装置配置有第三用户面处理规则，该第三用户面处理规则指示：对于第三DNS查询消息，该装置将第三DNS查询消息的目的地址由第二地址替换为HPLMN内DNS服务器的地址，以得到第四DNS查询消息，并向边缘应用服务功能发送第四DNS查询消息。
一种可能的设计方案中，处理模块1402，用于在收发模块1401接收来自终端的第一DNS消息之前，用户面网元确定第一地址，并控制收发模块1401向会话管理网元发送第一地址。或者，收发模块1401，用于接收来自会话管理网元的第一地址。
一种可能的设计方案中，处理模块1402，用于在收发模块1401接收来自终端的第一DNS消息之前，确定第二地址，并控制收发模块1401向会话管理网元发送第二地址。或者，收发模块1401，用于接收来自会话管理网元的第二地址。
可选地，收发模块1401也可以包括发送模块和接收模块，发送模块用于实现通信装置1400的发送功能，接收模块用于通信装置1400的接收功能。
可选地，通信装置1400还可以包括存储模块，该存储模块存储有程序或指令。当该处理模块1402执行该程序或指令时，使得该通信装置1400可以执行图10或图12所述的通信方法。
需要说明的是，通信装置1400可以是网络设备，如用户面网元或者V-SMF网元，也可以是可设置于网络设备中的芯片(系统)或其他部件或组件，还可以是包含网络设备的装置，本申请对此不做限定。
还一些实施例中，通信装置1400可适用于图6中所示出的通信系统中，执行图10所示的方法中会话管理网元的功能，或者执行图12所示的方法中V-SMF网元的功能。
处理模块1402，用于确定第一地址，收发模块1401，用于向边缘应用服务功能发送第一地址。第一地址是拜访公共陆地移动网VPLMN针对终端分配的地址，终端漫游至VPLMN内。
一种可能的设计方案中，收发模块1401，用于向用户面网元发送第一地址。
一种可能的设计方案中，处理模块1402，用于在终端的协议数据单元PDU会话建立过程中，确定第一地址。可选地，终端的PDU会话为终端的家乡路由HR PDU会话。
一种可能的设计方案中，处理模块1402，用于确定第二地址，收发模块1401，用于 向边缘应用服务功能发送第二地址。第二地址是VPLMN针对终端分配的地址，第二地址与第一地址不同。
可选地，收发模块1401，用于向用户面网元发送第二地址。
一种可能的设计方案中，处理模块1402，用于在终端的PDU会话建立过程中，确定第二地址。可选地，终端的PDU会话为终端的HR PDU会话。
可选地，收发模块1401也可以包括发送模块和接收模块，发送模块用于实现通信装置1400的发送功能，接收模块用于通信装置1400的接收功能。
可选地，通信装置1400还可以包括存储模块，该存储模块存储有程序或指令。当该处理模块1402执行该程序或指令时，使得该通信装置1400可以执行图10或图12所述的方法。
需要说明的是，通信装置1400可以是网络设备，如会话管理网元或者V-SMF网元，也可以是可设置于网络设备中的芯片(系统)或其他部件或组件，还可以是包含网络设备的装置，本申请对此不做限定。
示例性地，图15为本申请实施例提供的通信装置的结构示意图三。该通信装置可以是终端，也可以是可设置于终端的芯片(系统)或其他部件或组件。如图15所示，通信装置1500可以包括处理器1501。可选地，通信装置1500还可以包括存储器1502和/或收发器1503。其中，处理器1501与存储器1502和收发器1503耦合，如可以通过通信总线连接。
下面结合图15对通信装置1500的各个构成部件进行具体的介绍：
其中，处理器1501是通信装置1500的控制中心，可以是一个处理器，也可以是多个处理元件的统称。例如，处理器1501是一个或多个中央处理器(central processing unit，CPU)，也可以是特定集成电路(application specific integrated circuit，ASIC)，或者是被配置成实施本申请实施例的一个或多个集成电路，例如：一个或多个微处理器(digital signal processor，DSP)，或，一个或者多个现场可编程门阵列(field programmable gate array，FPGA)。
可选地，处理器1501可以通过运行或执行存储在存储器1502内的软件程序，以及调用存储在存储器1502内的数据，执行通信装置1500的各种功能，例如执行上述图8-图10所示的通信方法。
在具体的实现中，作为一种实施例，处理器1501可以包括一个或多个CPU，例如图15中所示出的CPU0和CPU1。
在具体实现中，作为一种实施例，通信装置1500也可以包括多个处理器，例如图15中所示的处理器1501和处理器1504。这些处理器中的每一个可以是一个单核处理器(single-CPU)，也可以是一个多核处理器(multi-CPU)。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
其中，所述存储器1502用于存储执行本申请方案的软件程序，并由处理器1501来控制执行，具体实现方式可以参考上述方法实施例，此处不再赘述。
可选地，存储器1502可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器 (electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器1502可以和处理器1501集成在一起，也可以独立存在，并通过通信装置1500的接口电路(图15中未示出)与处理器1501耦合，本申请实施例对此不作具体限定。
收发器1503，用于与其他通信装置之间的通信。例如，通信装置1500为终端，收发器1503可以用于与网络设备通信，或者与另一个终端设备通信。又例如，通信装置1500为网络设备，收发器1503可以用于与终端通信，或者与另一个网络设备通信。
可选地，收发器1503可以包括接收器和发送器(图15中未单独示出)。其中，接收器用于实现接收功能，发送器用于实现发送功能。
可选地，收发器1503可以和处理器1501集成在一起，也可以独立存在，并通过通信装置1500的接口电路(图15中未示出)与处理器1501耦合，本申请实施例对此不作具体限定。
需要说明的是，图15中示出的通信装置1500的结构并不构成对该通信装置的限定，实际的通信装置可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。
此外，通信装置1500的技术效果可以参考上述方法实施例所述的通信方法的技术效果，此处不再赘述。
应理解，在本申请实施例中的处理器可以是中央处理单元(central processing unit，CPU)，该处理器还可以是其他通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
还应理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的随机存取存储器(random access memory，RAM)可用，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。
上述实施例，可以全部或部分地通过软件、硬件(如电路)、固件或其他任意组合来实现。当使用软件实现时，上述实施例可以全部或部分地以计算机程序产品的形式实现。 所述计算机程序产品包括一个或多个计算机指令或计算机程序。在计算机上加载或执行所述计算机指令或计算机程序时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以为通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集合的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质。半导体介质可以是固态硬盘。
应理解，本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况，其中A,B可以是单数或者复数。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系，但也可能表示的是一种“和/或”的关系，具体可参考前后文进行理解。
本申请中，“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a,b,或c中的至少一项(个)，可以表示：a,b,c,a-b,a-c,b-c,或a-b-c，其中a,b,c可以是单个，也可以是多个。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (30)

  1. 一种通信方法，其特征在于，所述方法包括：
    用户面网元接收来自终端的第一域名系统DNS查询消息；所述终端漫游至拜访公共陆地移动网VPLMN，所述第一DNS查询消息用于查询应用服务的地址；
    所述用户面网元向边缘应用服务功能发送所述第一DNS查询消息和第一标识；所述第一标识是所述VPLMN针对所述终端分配的标识。
  2. 根据权利要求1所述的方法，其特征在于，所述用户面网元配置有第一用户面处理规则，所述第一用户面处理规则指示：对于所述第一DNS查询消息，所述用户面网元向所述边缘应用服务功能发送所述第一DNS查询消息和所述第一标识。
  3. 根据权利要求1或2所述的方法，其特征在于，所述用户面网元向边缘应用服务功能发送所述第一DNS查询消息和所述第一标识，包括：
    所述用户面网元通过通信隧道，向所述边缘应用服务功能发送所述第一DNS查询消息和所述第一标识；所述第一标识携带在所述通信隧道的头部中。
  4. 根据权利要求1-3中任一项所述的方法，其特征在于，在所述用户面网元向边缘应用服务功能发送所述第一DNS查询消息和所述第一标识之后，所述方法还包括：
    所述用户面网元接收来自所述边缘应用服务功能的第一DNS响应消息和第二标识；所述第二标识是所述VPLMN针对所述终端分配的标识，所述第一DNS响应消息携带有所述应用服务的地址；
    所述用户面网元根据所述第二标识，向所述终端发送所述第一DNS响应消息。
  5. 根据权利要求4所述的方法，其特征在于，所述用户面网元配置有第二用户面处理规则，所述第二用户面处理规则指示：对于所述第一DNS响应消息和所述第二标识，所述用户面网元向终端发送所述第一DNS响应消息。
  6. 根据权利要求4或5所述的方法，其特征在于，所述用户面网元接收来自所述边缘应用服务功能的所述第一DNS响应消息和第二标识，包括：
    所述用户面网元通过所述通信隧道，接收来自所述边缘应用服务功能的所述第一DNS响应消息和所述第二标识；所述第二标识携带在所述通信隧道的头部中。
  7. 根据权利要求1-3中任一项所述的方法，其特征在于，在所述用户面网元向边缘应用服务功能发送所述第一DNS查询消息和所述第一标识之后，所述方法还包括：
    所述用户面网元接收来自所述边缘应用服务功能的第二DNS查询消息和第二标识；所述第二标识是所述VPLMN针对所述终端分配的标识，所述第二DNS查询消息用于获取所述应用服务的地址；
    所述用户面网元根据所述第二DNS查询消息和所述第二标识，向所述终端的归属公共陆地移动网络HPLMN发送所述第三DNS查询消息；所述第三DNS查询消息用于请求所述应用服务的地址。
  8. 根据权利要求7所述的方法，其特征在于，所述用户面网元配置有第三用户面处理规则，所述第三用户面处理规则指示：对于所述第二DNS查询消息和所述第二标识，所述用户面网元向所述HPLMN发送所述第三DNS查询消息。
  9. 根据权利要求7或8所述的方法，其特征在于，所述用户面网元接收来自所述边缘应用服务功能的所述第二DNS查询消息和第二标识，包括：
    所述用户面网元通过所述通信隧道，接收来自所述边缘应用服务功能的所述第二DNS查询消息和所述第二标识；所述第二标识携带在所述通信隧道的头部中。
  10. 根据权利要求1-9中任一项所述的方法，其特征在于，所述方法还包括：
    所述用户面网元确定所述第一标识，并向会话管理网元发送所述第一标识；或者，
    所述用户面网元接收来自所述会话管理网元的所述第一标识。
  11. 一种通信方法，其特征在于，所述方法包括：
    边缘应用服务功能接收来自用户面网元的第一域名系统DNS查询消息和第一标识；所述第一标识是拜访公共陆地移动网VPLMN针对终端的标识，所述终端漫游至所述VPLMN，所述第一DNS查询消息用于查询应用服务的地址；
    所述边缘应用服务功能确定是否存在与所述第一DNS查询消息和所述第一标识匹配的DNS消息处理规则。
  12. 根据权利要求11所述的方法，其特征在于，所述边缘应用服务功能接收来自用户面网元的第一DNS查询消息和第一标识，包括：
    所述边缘应用服务功能通过通信隧道，接收来自所述用户面网元的所述第一DNS查询消息和所述第一标识；所述第一标识携带在所述通信隧道的头部中。
  13. 根据权利要求11或12所述的方法，其特征在于，所述方法还包括：
    在存在与所述第一DNS查询消息和所述第一标识匹配的所述DNS消息处理规则的情况下，所述边缘应用服务功能向所述用户面网元发送第一DNS响应消息和第二标识；所述第二标识是所述VPLMN针对所述终端分配的标识，所述第一DNS响应消息携带有所述应用服务的地址。
  14. 根据权利要求13所述的方法，其特征在于，所述DNS消息处理规则指示：所述边缘应用服务功能向所述用户面网元发送所述第一DNS响应消息和所述第二标识。
  15. 根据权利要求13或14所述的方法，其特征在于，所述边缘应用服务功能向所述用户面网元发送第一DNS响应消息和第二标识，包括：
    所述边缘应用服务功能通过通信隧道，向所述用户面网元发送所述第一DNS响应消息和所述第二标识；所述第二标识携带在所述通信隧道的头部中。
  16. 根据权利要求11或12所述的方法，其特征在于，所述方法还包括：
    在不存在与所述第一DNS查询消息和所述第一标识匹配的所述DNS消息处理规则的情况下，所述边缘应用服务功能向所述用户面网元发送第二DNS查询消息和第二标识；所述第二标识是所述VPLMN针对所述终端分配的标识，所述第二DNS查询消息用于获取所述应用服务的地址。
  17. 根据权利要求16所述的方法，其特征在于，所述边缘应用服务功能向所述用户面网元发送第二DNS查询消息和第二标识，包括：
    所述边缘应用服务功能通过通信隧道，向所述用户面网元发送所述第二DNS查询消息和所述第二标识；所述第二标识携带在所述通信隧道的头部中。
  18. 根据权利要求11-17中任一项所述的方法，其特征在于，在所述边缘应用服务功能接收来自用户面网元向的第一DNS查询消息和第一标识之前，所述方法还包括：
    所述边缘应用服务功能确定所述第一标识，并向会话管理网元发送所述第一标识； 或者，
    所述边缘应用服务功能接收来自所述会话管理网元的所述第一标识。
  19. 根据权利要求13-16中任一项所述的方法，其特征在于，在所述边缘应用服务功能接收来自用户面网元向的第一DNS查询消息和第一标识之前，所述方法还包括：
    所述边缘应用服务功能确定所述第二标识，并向会话管理网元发送所述第二标识；或者，
    所述边缘应用服务功能接收来自所述会话管理网元的所述第二标识。
  20. 一种通信方法，其特征在于，所述方法包括：
    用户面网元接收来自终端的第一域名系统DNS查询消息；所述终端漫游至拜访公共陆地移动网VPLMN，所述第一DNS查询消息用于查询应用服务的地址；
    所述用户面网元将第一DNS查询消息的源地址由所述终端的地址替换为第一地址，以得到第二DNS查询消息；所述第一地址是所述VPLMN针对所述终端分配的地址；
    所述用户面网元向边缘应用服务功能发送所述第二DNS查询消息。
  21. 根据权利要求20所述的方法，其特征在于，所述用户面网元配置有第一用户面处理规则，所述第一用户面处理规则指示：对于所述第一DNS查询消息，所述用户面网元将所述第一DNS查询消息的源地址由所述终端的地址替换为所述第一地址，以得到所述第二DNS查询消息，并向所述边缘应用服务功能发送所述第二DNS查询消息。
  22. 根据权利要求20或21所述的方法，其特征在于，在所述用户面网元向边缘应用服务功能发送所述第二DNS查询消息之后，所述方法还包括：
    所述用户面网元接收来自所述边缘应用服务功能的第一DNS响应消息；所述第一DNS响应消息携带所述应用服务的地址；
    所述用户面网元将所述第一DNS响应消息的目的地址由所述第一地址替换为所述终端的地址，以得到第二DNS响应消息；
    所述用户面网元向所述终端发送所述第二DNS响应消息。
  23. 根据权利要求22所述的方法，其特征在于，所述用户面网元配置有第二用户面处理规则，所述第二用户面处理规则指示：对于所述第一DNS响应消息，所述用户面网元将所述第一DNS响应消息的目的地址由所述第一地址替换为所述终端的地址，以得到所述第二DNS响应消息，并向所述边缘应用服务功能发送所述第二DNS响应消息。
  24. 根据权利要求20或21所述的方法，其特征在于，在所述用户面网元向边缘应用服务功能发送所述第二DNS查询消息之后，所述方法还包括：
    所述用户面网元接收来自所述边缘应用服务功能的所述第三DNS查询消息；
    所述用户面网元将所述第三DNS查询消息的目的地址由第二地址替换为所述HPLMN内DNS服务器的地址，以得到第四DNS查询消息；所述第二地址是所述VPLMN针对所述终端分配的地址；
    所述用户面网元向所述HPLMN发送所述第四DNS查询消息。
  25. 根据权利要求24所述的方法，其特征在于，所述用户面网元配置有第三用户 面处理规则，所述第三用户面处理规则指示：对于所述第三DNS查询消息，所述用户面网元将所述第三DNS查询消息的目的地址由所述第二地址替换为所述HPLMN内DNS服务器的地址，以得到所述第四DNS查询消息，并向所述边缘应用服务功能发送所述第四DNS查询消息。
  26. 根据权利要求20-25中任一项所述的方法，其特征在于，在所述用户面网元接收来自终端的第一DNS消息之前，所述方法还包括：
    所述用户面网元确定所述第一地址，并向会话管理网元发送所述第一地址；或者，
    所述用户面网元接收来自所述会话管理网元的所述第一地址。
  27. 根据权利要求24或25所述的方法，其特征在于，在所述用户面网元接收来自终端的第一DNS消息之前，所述方法还包括：
    所述用户面网元确定所述第二地址，并向会话管理网元发送所述第二地址；或者，
    所述用户面网元接收来自所述会话管理网元的所述第二地址。
  28. 一种通信装置，其特征在于，所述装置包括：用于执行如权利要求1-10中任一项所述的方法的模块、或者用于执行如权利要求11-19中任一项所述的方法的模块、或者用于执行如权利要求20-27中任一项所述的方法的模块。
  29. 一种通信装置，其特征在于，所述通信装置包括：处理器和存储器；所述存储器用于存储计算机指令，当所述处理器执行该指令时，以使所述通信装置执行如权利要求1-27中任一项所述的通信方法。
  30. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质包括计算机程序或指令，当所述计算机程序或指令在计算机上运行时，使得所述计算机执行如权利要求1-27中任一项所述的通信方法。
PCT/CN2023/088475 2022-04-29 2023-04-14 通信方法及装置 WO2023207637A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210469042.4A CN117014987A (zh) 2022-04-29 2022-04-29 通信方法及装置
CN202210469042.4 2022-04-29

Publications (1)

Publication Number Publication Date
WO2023207637A1 true WO2023207637A1 (zh) 2023-11-02

Family

ID=88517498

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/088475 WO2023207637A1 (zh) 2022-04-29 2023-04-14 通信方法及装置

Country Status (2)

Country Link
CN (1) CN117014987A (zh)
WO (1) WO2023207637A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20200032665A (ko) * 2018-09-18 2020-03-26 주식회사 케이티 저지연 엣지 로밍 서비스를 제공하기 위한 데이터 패킷의 처리 방법 및 그 시스템
CN113596191A (zh) * 2021-07-23 2021-11-02 腾讯科技（深圳）有限公司 一种数据处理方法、网元设备以及可读存储介质
WO2021218595A1 (zh) * 2020-04-28 2021-11-04 华为技术有限公司 一种地址获取方法及装置
CN114338603A (zh) * 2021-12-31 2022-04-12 中国电信股份有限公司 边缘应用服务器的发现方法、设备、区块链系统及介质

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20200032665A (ko) * 2018-09-18 2020-03-26 주식회사 케이티 저지연 엣지 로밍 서비스를 제공하기 위한 데이터 패킷의 처리 방법 및 그 시스템
WO2021218595A1 (zh) * 2020-04-28 2021-11-04 华为技术有限公司 一种地址获取方法及装置
CN113596191A (zh) * 2021-07-23 2021-11-02 腾讯科技（深圳）有限公司 一种数据处理方法、网元设备以及可读存储介质
CN114338603A (zh) * 2021-12-31 2022-04-12 中国电信股份有限公司 边缘应用服务器的发现方法、设备、区块链系统及介质

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
CHINA UNICOM: "Corrections on the procedure of EAS discovery with EASDF", SA WG2 MEETING #147E S2-2107265, 9 October 2021 (2021-10-09), XP052060131 *

Also Published As

Publication number Publication date
CN117014987A (zh) 2023-11-07

Similar Documents

Publication Publication Date Title
US10980084B2 (en) Supporting multiple QOS flows for unstructured PDU sessions in wireless system using non-standardized application information
JP7252305B2 (ja) データ伝送方法、デバイス、およびシステム
US20220191100A1 (en) Method and device for providing connectivity to terminal in order to use edge computing service
WO2022152238A1 (zh) 一种通信方法及通信装置
CN111615844B (zh) 用于选择服务无线通信设备的会话管理实体的方法和装置
WO2017147772A1 (zh) 一种消息传输方法及核心网接口设备
CN114651477A (zh) 用于用户面处理的系统和方法
KR20210024160A (ko) 통신 방법 및 장치
WO2022017285A1 (zh) 报文转发方法、装置及系统
WO2023051287A1 (zh) 一种通信方法及装置
WO2021197175A1 (zh) 应用服务器的发现方法及相关装置
WO2022199451A1 (zh) 会话切换的方法和装置
WO2022012176A1 (zh) 临近服务通信方法、管理网元、终端设备和通信系统
WO2022022322A1 (zh) 访问本地网络的方法和装置
CN114301788B (zh) 一种切片管理方法、装置及通信设备
EP4207828A1 (en) Data communication method and communication apparatus
WO2022253137A1 (zh) 接入业务的方法、装置和系统
KR20210023299A (ko) 무선통신 시스템에서 네트워크 서비스를 노출하는 방법 및 장치
WO2023207637A1 (zh) 通信方法及装置
CN114423074A (zh) 一种通信方法及装置
WO2024027299A1 (zh) 消息路由方法和装置
WO2024012230A1 (zh) 通信方法及装置
WO2024051313A1 (zh) 通信资源管理方法、装置、系统及存储介质
US20240155418A1 (en) Method and apparatus for connecting qos flow based terminal in wireless communication system
WO2023197737A1 (zh) 报文发送方法、pin管理方法、通信装置及通信系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23795070

Country of ref document: EP

Kind code of ref document: A1