CN116866893A

CN116866893A - Communication method and device

Info

Publication number: CN116866893A
Application number: CN202210313165.9A
Authority: CN
Inventors: 王亚鑫; 李岩
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2022-03-28
Filing date: 2022-03-28
Publication date: 2023-10-10
Also published as: WO2023185620A1

Abstract

The embodiment of the application provides a communication method and device. The method may include: the session management network element obtains provider information, and the provider is a provider for providing edge computing service for the terminal equipment; the session management network element configures Domain Name Service (DNS) processing rules according to provider information and Edge Application Server (EAS) deployment information corresponding to the provider, wherein the DNS processing rules are used for processing DNS information of terminal equipment, and the EAS deployment information is the EAS deployment information of the provider in an access network of the terminal equipment; the session management network element sends DNS handling rules to the edge application server discovery network element. And searching the corresponding EAS deployment information of the provider in the access network of the terminal equipment by providing provider information of edge computing service for the terminal equipment, and further selecting the corresponding EAS of the provider in the access network of the terminal equipment for the terminal equipment.

Description

Communication method and device

Technical Field

The embodiment of the application relates to the field of communication, and more particularly relates to a communication method and device.

Background

An edge application server (edge application server, EAS) may be deployed in the network, which may provide edge services for terminal devices (UEs).

An Operator (OP) (e.g., OP 1) deploys EAS or a machine room in another operator (e.g., OP 2), and a terminal device accessing the network through OP2 may preferentially select EAS of a certain OP (e.g., OP 1) according to its home domain or subscription. How to prioritize EAS for a certain OP for a terminal device is a considerable issue.

Disclosure of Invention

The application provides a communication method and a communication device, which are used for searching the corresponding EAS deployment information of a provider by providing the provider information of edge calculation service for terminal equipment, so as to select the corresponding EAS of the provider in an access network of the terminal equipment for the terminal equipment.

In a first aspect, a method of communication is provided, which may be performed by a session management network element, or may also be performed by a component (e.g. a chip or a circuit) of the session management network element, which is not limited to this, and for convenience of description, will be described below with reference to the embodiment performed by the session management network element.

The method may include: the session management network element obtains provider information, and the provider is a provider for providing edge computing service for the terminal equipment; the session management network element configures Domain Name Service (DNS) processing rules according to provider information and Edge Application Server (EAS) deployment information corresponding to the provider, wherein the DNS processing rules are used for processing DNS information of terminal equipment, and the EAS deployment information is the EAS deployment information corresponding to the provider in an access network of the terminal equipment; the session management network element sends DNS handling rules to the edge application server discovery network element.

Illustratively, the EAS deployment information is deployment information of the EAS corresponding to the provider in the access network of the terminal device.

Based on the technical scheme, the session management network element configures DNS processing rules according to information of a provider providing edge computing service for the terminal equipment and EAS deployment information corresponding to the provider, and sends the DNS processing rules to the edge application server discovery network element, and the edge application server discovery network element processes DNS query information of the terminal equipment based on the DNS processing rules. The session management network element configures DNS processing rules according to the information of the provider and the EAS deployment information corresponding to the provider, and not only can directly obtain the EAS deployment information corresponding to the provider based on the information of the provider, but also can directly configure DNS processing rules based on the EAS deployment information corresponding to the provider, so that the DNS processing rules are related to the EAS deployment information corresponding to the provider, and thus, when the edge application server discovers that the network element processes a DNS query message of the terminal device based on the DNS processing rules, the edge application server can be implemented to select (or provide) the EAS corresponding to the provider in the access network for the terminal device. In addition, by associating the provider with EAS deployment information of the provider in the access network of the terminal device, not only can the terminal device be provided with corresponding EAS according to the requirement of the terminal device (such as using an edge computing service provided by a certain provider), but also the DNS processing rule is configured based on the EAS deployment information corresponding to the provider, so that the existing configuration flow of the DNS processing rule is utilized, and less protocol modification is performed.

With reference to the first aspect, in certain implementations of the first aspect, the method further includes: the session management network element obtains the EAS deployment information according to the provider information; or the session management network element acquires the EAS deployment information according to the provider information and the access network information.

Based on the above technical scheme, corresponding EAS deployment information may be determined according to provider information. For example, the EAS deployment information may include information about the provider (e.g., provider ID); for another example, the EAS deployment information is associated with information of the provider (e.g., provider ID). Alternatively, the corresponding EAS deployment information may be determined based on the provider information and the access network information. For example, the EAS deployment information includes information of the provider (such as a provider ID) and information of the access network (such as an ID of the access network); for another example, the EAS deployment information is associated with information of the provider (e.g., provider ID) and information of the access network (e.g., access network ID).

With reference to the first aspect, in certain implementations of the first aspect, the EAS deployment information includes a DNS server, and EAS registered on the DNS server is EAS corresponding to the provider in the access network.

Based on the above technical solution, EAS registered on the DNS server in the EAS deployment information corresponding to the provider is EAS corresponding to the provider in the access network, so that the DNS server can query EAS corresponding to the provider in the access network.

With reference to the first aspect, in certain implementations of the first aspect, the EAS deployment information includes ECS option, and EAS corresponding to the ECS option is EAS corresponding to a provider providing edge computing services for the terminal device in the access network.

Based on the above technical solution, the EAS corresponding to the ECS option in the EAS deployment information corresponding to the provider is the EAS corresponding to the provider in the access network, so that the EAS corresponding to the provider in the access network can be queried through the ECS option.

With reference to the first aspect, in certain implementations of the first aspect, the EAS deployment information includes an address of a corresponding EAS in the access network of a provider that provides edge computing services for the terminal device.

Based on the above technical solution, the EAS address in the EAS deployment information corresponding to the provider is the address of the EAS corresponding to the provider in the access network, so that filtering (or selecting) the address belonging to the EAS address in the inquiry response of the terminal device can be achieved through the EAS address, and the EAS corresponding to the provider in the access network is further provided for the terminal device.

With reference to the first aspect, in certain implementations of the first aspect, the DNS server is a server deployed in a home network, or the DNS server is a server deployed in an access network.

With reference to the first aspect, in certain implementations of the first aspect, the DNS processing rules include any of: DNS server, ECS option, address of the corresponding EAS in the access network for the provider.

Based on the technical scheme, the information is carried in the DNS processing rule, so that when the inquiry request of the terminal equipment is processed based on the DNS processing rule, the corresponding EAS of the provider in the access network can be provided for the terminal equipment.

With reference to the first aspect, in certain implementations of the first aspect, the access network of the terminal device is a visited network of the terminal device.

The provider providing the edge computing service to the terminal device may be, for example, a provider outside the visited network of the terminal device, such as the home network of the terminal device, and such as a third party edge computing service provider subscribed to by the terminal device.

With reference to the first aspect, in certain implementations of the first aspect, the session management network element obtains provider information including any one of: the session management network element determines provider information according to the home network of the terminal equipment; the session management network element determines provider information according to the subscription information of the terminal equipment, wherein the subscription information of the terminal equipment comprises the information of the provider; the session management network element determines provider information according to the terminal equipment included in the terminal equipment list provided by the provider; alternatively, the session management network element determines the provider information according to a protocol between the provider and the access network.

The agreement between the provider and the access network may be understood, for example, as a federation agreement between the provider and the access network. For example, if the access network of the terminal device has a cooperative relationship with the provider, such as allowing the terminal device of the access network to use the edge computing service of the provider, or allowing the terminal device of the provider to use the edge computing service of the access network, the provider may be determined for the terminal device.

Based on the above technical solution, the session management network element may be according to: determining a provider by any one of a home network of the terminal equipment, subscription information of the terminal equipment and a terminal equipment list provided by the provider, wherein the terminal equipment or a protocol between the provider and an access network, so as to acquire EAS deployment information corresponding to the provider; or determining the provider according to any item of home network of the terminal equipment, subscription information of the terminal equipment, terminal equipment list provided by the provider, or protocol between the provider and the access network, and combining the access network to obtain EAS deployment information corresponding to the provider. This is not limited.

With reference to the first aspect, in certain implementations of the first aspect, the provider is any one of: EAS provider, edge host environment EHE provider, edge data network EDN provider.

In a second aspect, a method of communication is provided, which may be performed by the edge application server discovery network element, or may also be performed by a component (e.g. a chip or a circuit) of the edge application server discovery network element, which is not limited, and for convenience of description, will be described below with reference to the embodiment performed by the edge application server discovery network element.

The method may include: the edge application server discovers that the network element receives Domain Name Service (DNS) query messages from the terminal equipment; the edge application server discovers that the network element processes the DNS query message according to the DNS processing rule; the DNS processing rule is determined according to EAS deployment information of an edge application server corresponding to a provider for providing edge computing service for the terminal equipment, wherein the EAS deployment information is EAS deployment information of the provider in an access network of the terminal equipment.

With reference to the second aspect, in certain implementations of the second aspect, the EAS deployment information is determined from provider information; alternatively, the EAS deployment information is determined based on the provider information and the access network information.

With reference to the second aspect, in certain implementations of the second aspect, the EAS deployment information includes at least one of: DNS server, ECS option, provider address of corresponding EAS in access network; wherein, the EAS registered on the DNS server is the EAS corresponding to the provider in the access network, and the EAS corresponding to the ECS option is the EAS corresponding to the provider in the access network.

With reference to the second aspect, in certain implementations of the second aspect, the DNS server is a server deployed in a home network, or the DNS server is a server deployed in an access network.

With reference to the second aspect, in some implementations of the second aspect, the EAS deployment information includes DNS server information, the DNS processing rule includes DNS server information, and the edge application server discovers that the network element processes the DNS query message according to the DNS processing rule, including: the edge application server discovers that the network element sends a DNS query message to the DNS server.

Based on the above technical solution, since the EAS registered on the DNS server is the EAS corresponding to the provider providing the edge computing service for the terminal device in the access network, the edge application server discovers that the network element sends the query message of the terminal device to the DNS server, and the DNS server processes the query request of the terminal device, so that the DNS server provides the corresponding EAS in the access network for the terminal device.

With reference to the second aspect, in some implementations of the second aspect, the DNS server is a server deployed in a home network, and the edge application server discovers that the network element processes the DNS query message according to a DNS processing rule, and further includes: the edge application server discovers that the network element adds ECS option in the DNS query message according to the DNS processing rule; the edge application server discovering that the network element sends a DNS query message to the DNS server includes: the edge application server discovers that the network element sends a DNS query message containing ECS options to the DNS server.

Based on the above technical solution, since the EAS corresponding to the ECS option is the EAS corresponding to the provider providing the edge computing service for the terminal device in the access network, after the edge application server discovers that the network element adds the ECS option in the DNS query message, the information of the EAS corresponding to the provider in the access network can be provided for the terminal device.

With reference to the second aspect, in some implementations of the second aspect, the EAS deployment information includes an address of an EAS corresponding to the provider in the access network, the DNS processing rule includes an address of an EAS corresponding to the provider in the access network, and the edge application server discovers that the network element processes the DNS query message according to the DNS processing rule, including: the edge application server discovers that the network element obtains at least one address of the EAS according to the DNS processing rule; the edge application server discovers that the network element generates a response message of the DNS query message, where the response message includes a part or all of the EAS addresses in the address of at least one EAS, where the part or all of the EAS addresses are determined according to the EAS corresponding to the provider in the access network.

Based on the above technical solution, after the edge application server finds that the network element receives the response of the DNS query message, the address belonging to the EAS address may be filtered (or selected) from the query response, so as to provide the terminal device with the EAS corresponding to the provider in the access network.

With reference to the second aspect, in some implementations of the second aspect, the EAS deployment information includes ECS option, the DNS processing rule includes information of ECS option, and the edge application server discovers that the network element processes the DNS query message according to the DNS processing rule, including: the edge application server finds that the network element adds ECS option in the DNS query message.

With reference to the second aspect, in certain implementations of the second aspect, the method further includes: the edge application server discovers that the network element receives DNS handling rules from the session management network element.

With reference to the second aspect, in certain implementations of the second aspect, the provider is any one of: EAS provider, edge host environment EHE provider, edge data network EDN provider.

The second aspect and the advantageous effects of each possible design may refer to the description related to the first aspect, and are not repeated here.

In a third aspect, a method of communication is provided, which may be performed by a data management network element, or may also be performed by a component (e.g. a chip or a circuit) of the data management network element, which is not limited to this, and for convenience of description, will be described below by taking the data management network element as an example.

The method may include: the data management network element receives the EAS deployment information of the edge application server corresponding to the provider for providing the edge computing service for the terminal equipment from the application network element, wherein the EAS deployment information is the EAS deployment information corresponding to the provider in the access network of the terminal equipment; the data management network element stores EAS deployment information.

Based on the technical scheme, the data management network element can store the EAS deployment information corresponding to the provider, so that when the session management needs the EAS deployment information corresponding to the provider, the session management network element can be provided with the EAS deployment information corresponding to the provider, and further the session management network element determines a corresponding DNS processing rule based on the EAS deployment information corresponding to the provider, so as to select (or provide) the EAS corresponding to the provider in the access network of the terminal device for the terminal device.

With reference to the third aspect, in certain implementations of the third aspect, the EAS deployment information is determined from provider information; alternatively, the EAS deployment information is determined based on the provider information and the access network information.

Illustratively, the EAS deployment information is determined based on the provider information, and it is understood that the EAS deployment information corresponding to the provider is queried based on the provider information.

Illustratively, the EAS deployment information is determined according to the provider information and the access network information, and it is understood that the EAS deployment information corresponding to the provider is queried according to the provider information and the access network information.

With reference to the third aspect, in certain implementations of the third aspect, the EAS deployment information includes at least one of: data network name, network slice information, data network access identifier, or application information.

The application information may be, for example, an application identification (application ID).

With reference to the third aspect, in certain implementations of the third aspect, the EAS deployment information includes at least one of: DNS server, ECS option, provider address of corresponding EAS in access network; wherein, the EAS registered on the DNS server is the EAS corresponding to the provider in the access network, and the EAS corresponding to the ECS option is the EAS corresponding to the provider in the access network.

With reference to the third aspect, in some implementations of the third aspect, the DNS server is a server deployed in a home network, or the DNS server is a server deployed in an access network.

With reference to the third aspect, in certain implementations of the third aspect, the method further includes: the data management network element receives information from at least one provider of the application network element and information of at least one terminal device for which the at least one provider is capable of providing edge computing services.

With reference to the third aspect, in certain implementations of the third aspect, the provider is any one of: EAS provider, edge host environment EHE provider, edge data network EDN provider.

The advantages of the third aspect and the various possible designs may be referred to in the description related to the first aspect, and are not repeated here.

In a fourth aspect, a method of communication is provided, which may be performed by an application network element, or may also be performed by a component (e.g. a chip or a circuit) of the application network element, which is not limited, and for convenience of description, will be described below by taking an example of the implementation by the application network element.

The method may include: the method comprises the steps that an application network element determines EAS deployment information of an edge application server corresponding to a provider for providing edge computing service for terminal equipment, wherein the EAS deployment information is corresponding EAS deployment information of the provider in an access network of the terminal equipment; the application network element transmits EAS deployment information.

Based on the technical scheme, the application network element can provide the EAS deployment information corresponding to the provider, so that when the session management needs the EAS deployment information corresponding to the provider, the application network element or other network elements (such as the application network element sends the EAS deployment information corresponding to the provider to other network elements) can provide the EAS deployment information corresponding to the provider for the session management network element, and further the session management network element determines a corresponding DNS processing rule based on the EAS deployment information corresponding to the provider, so as to realize selecting (or providing) the EAS corresponding to the provider in the access network of the terminal device for the terminal device.

With reference to the fourth aspect, in certain implementations of the fourth aspect, the EAS deployment information is determined from provider information; alternatively, the EAS deployment information is determined based on the provider information and the access network information.

With reference to the fourth aspect, in some implementations of the fourth aspect, the transmitting, by the application network element, EAS deployment information includes: the application network element transmits EAS deployment information to one or more of: a data management network element, a session management network element and a network opening network element.

With reference to the fourth aspect, in certain implementations of the fourth aspect, the EAS deployment information includes at least one of: data network name, network slice information, data network access identifier, or application information.

With reference to the fourth aspect, in certain implementations of the fourth aspect, the EAS deployment information includes at least one of: DNS server, ECS option, provider address of corresponding EAS in access network; wherein, the EAS registered on the DNS server is the EAS corresponding to the provider in the access network, and the EAS corresponding to the ECS option is the EAS corresponding to the provider in the access network.

With reference to the fourth aspect, in some implementations of the fourth aspect, the DNS server is a server deployed in the home network, or the DNS server is a server deployed in the access network.

With reference to the fourth aspect, in certain implementations of the fourth aspect, the method further includes: the application network element transmits information of at least one provider and information of at least one terminal device, the at least one provider being capable of providing edge computing services for the at least one terminal device.

With reference to the fourth aspect, in certain implementations of the fourth aspect, the provider is any one of: the provider of EAS, the provider of edge hosting environment EHE, or the provider of edge data network EDN.

The advantages of the fourth aspect and the various possible designs may be referred to in the description related to the first aspect, and will not be repeated here.

In a fifth aspect, there is provided a communication apparatus for performing the method of any one of the possible implementations of the first to fourth aspects. In particular, the apparatus may comprise means and/or modules, such as a processing unit and/or a communication unit, for performing the method in any of the possible implementations of the first to fourth aspects.

In one implementation, the apparatus is a core network element (e.g., a session management element, a data management element, a network deployment element, and a policy control element). When the device is a core network element, the communication unit may be a transceiver, or an input/output interface; the processing unit may be at least one processor. Alternatively, the transceiver may be a transceiver circuit. Alternatively, the input/output interface may be an input/output circuit.

In another implementation, the apparatus is a chip, a system-on-chip, or a circuit for a core network element (e.g., a session management element, a data management element, a network deployment element, a policy control element). When the device is a chip, a system-on-chip or a circuit for a core network element, the communication unit may be an input/output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit on the chip, the system-on-chip or the circuit; the processing unit may be at least one processor, processing circuit or logic circuit, etc.

In a sixth aspect, there is provided an apparatus for communication, the apparatus comprising: at least one processor configured to execute a computer program or instructions stored in a memory to perform a method according to any one of the possible implementations of the first to fourth aspects. Optionally, the apparatus further comprises a memory for storing a computer program or instructions. Optionally, the apparatus further comprises a communication interface through which the processor reads the computer program or instructions stored in the memory.

In one implementation, the apparatus is a core network element (e.g., a session management element, a data management element, a network deployment element, and a policy control element).

In another implementation, the apparatus is a chip, a system-on-chip, or a circuit for a core network element (e.g., a session management element, a data management element, a network deployment element, a policy control element).

In a seventh aspect, the present application provides a processor configured to perform the method provided in the above aspects.

The operations such as transmitting and acquiring/receiving, etc. related to the processor may be understood as operations such as outputting and receiving, inputting, etc. by the processor, or may be understood as operations such as transmitting and receiving by the radio frequency circuit and the antenna, if not specifically stated, or if not contradicted by actual function or inherent logic in the related description, which is not limited by the present application.

In an eighth aspect, a computer readable storage medium is provided, the computer readable storage medium storing program code for execution by a device, the program code comprising instructions for performing the method of any one of the possible implementations of the first to fourth aspects.

In a ninth aspect, there is provided a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of any one of the possible implementations of the first to fourth aspects.

In a tenth aspect, a communication system is provided, comprising one or more of the aforementioned session management network element, edge application server discovery network element, data management network element, or application network element.

With reference to the tenth aspect, in certain implementations of the tenth aspect, the communication system includes the aforementioned session management network element and a network element/device in communication with the aforementioned session management network element.

With reference to the tenth aspect, in certain implementations of the tenth aspect, the communication system includes the aforementioned edge application server discovery network element and a network element/device in communication with the aforementioned edge application server discovery network element.

With reference to the tenth aspect, in certain implementations of the tenth aspect, the communication system includes the aforementioned data management network element and a network element/device in communication with the aforementioned data management network element.

With reference to the tenth aspect, in certain implementations of the tenth aspect, the communication system includes the aforementioned application network element and a network element/device that communicates with the aforementioned application network element.

Drawings

Fig. 1 is a schematic diagram of a network architecture suitable for use with embodiments of the present application.

Fig. 2 is a schematic diagram of another network architecture suitable for use with embodiments of the present application.

Fig. 3 is a schematic diagram of another network architecture suitable for use with embodiments of the present application.

Fig. 4 is a schematic diagram of another network architecture suitable for use with embodiments of the present application.

Fig. 5 is a schematic diagram of a method 500 for communication according to an embodiment of the present application.

Fig. 6 is a schematic diagram of a network architecture according to an embodiment of the present application.

Fig. 7 is a schematic diagram of a network architecture according to another embodiment of the present application.

Fig. 8 is a schematic diagram of a network architecture according to another embodiment of the present application.

Fig. 9 is a schematic flow chart diagram of a method 900 of communication provided by an embodiment of the present application.

Fig. 10 is a schematic flow chart diagram of a method 1000 of communication provided by an embodiment of the present application.

Fig. 11 is a schematic flow chart diagram of a method 1100 of communication provided by an embodiment of the application.

Fig. 12 is a schematic flow chart diagram of a method 1200 of communication provided by an embodiment of the present application.

Fig. 13 is a schematic flow chart diagram of a method 1300 of communication provided by an embodiment of the present application.

Fig. 14 is a schematic diagram of a communication apparatus 1400 provided in an embodiment of the application.

Fig. 15 is a schematic diagram of an apparatus 1500 for providing another communication in accordance with an embodiment of the present application.

Fig. 16 is a schematic diagram of a chip system 1600 according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings.

The technical scheme provided by the application can be applied to various communication systems, such as: fifth generation (5th generation,5G) or New Radio (NR) systems, long term evolution (long term evolution, LTE) systems, LTE frequency division duplex (frequency division duplex, FDD) systems, LTE time division duplex (time division duplex, TDD) systems, and the like. The technical scheme provided by the application can also be applied to future communication systems, such as a sixth generation mobile communication system. The technical solution provided by the present application may also be applied to device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine (machine to machine, M2M) communication, machine type communication (machine type communication, MTC), and internet of things (internet of things, ioT) communication systems or other communication systems.

For ease of understanding, a brief description of mobile network roaming (roaming) will be presented first.

Taking operator a and operator B as examples, roaming refers to the situation where a mobile user belonging to operator a has access to the network of operator B. For this user, the network of operator a may be considered the home network (or home network), and the network of operator B may be considered the visited network.

A cellular mobile communication network of a certain standard of a certain operator may be referred to as public land mobile network (public land mobile network, PLMN). A PLMN subscribed to a User Equipment (UE) may be referred to as a home public land mobile network (public land mobile network, PLMN) (home PLMN, HPLMN) that characterizes a subscriber's home operator. When the UE leaves the coverage of the HPLMN for mobile or other reasons, the following conditions are met if a certain PLMN is present: 1) May cover the current location of the UE, 2) its operator has signed a roaming agreement with the operator of the HPLMN of the UE (roaming agreement, meaning some agreement between operators, content may include, for example: service and billing methods provided for subscribers of the opposite operator network, without limitation), the UE may access the PLMN, and the PLMN may be referred to as a Visited Public Land Mobile Network (VPLMN). The behavior of the UE to access the VPLMN may be referred to as roaming. Generally, roaming scenarios can be classified into local break-through (LBO) roaming and Home Routed (HR) roaming, which differ mainly in whether a session is to be connected to a user plane function (user plane function, UPF) of the home network. These two scenarios are described below in conjunction with fig. 1 and 2.

Fig. 1 is a schematic diagram of a network architecture suitable for use with embodiments of the present application. The network architecture shown in fig. 1 is exemplified by HR roaming.

As shown in fig. 1, the network architecture may include, but is not limited to: based on network slice specific authentication and authorization functions (network slice specific authentication and authorization function, NSSAAF), network slice selection functions (network slice selection function, NSSF), authentication server functions (authentication server function, AUSF), unified data management (unified data management, UDM), policy control functions (policy control function, PCF), application functions (application function, AF), access and mobility management functions (access and mobility management function, AMF), session management functions (session management function, SMF), UE, radio access network devices, UPF, data Network (DN), etc.

The following briefly describes the network elements shown in fig. 1.

1. UE: a terminal device, access terminal, subscriber unit, subscriber station, mobile station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or user equipment may be referred to as a terminal device.

The terminal device may be a device that provides voice/data to a user, e.g., a handheld device with wireless connection, an in-vehicle device, etc. Currently, some examples of terminals are: a mobile phone, tablet, laptop, palmtop, mobile internet device (mobile internet device, MID), wearable device, virtual Reality (VR) device, augmented reality (augmented reality, AR) device, wireless terminal in industrial control (industrial control), wireless terminal in unmanned (self driving), wireless terminal in teleoperation (remote medical surgery), wireless terminal in smart grid (smart grid), wireless terminal in transportation security (transportation safety), wireless terminal in smart city (smart city), wireless terminal in smart home (smart home), cellular phone, cordless phone, session initiation protocol (session initiation protocol, SIP) phone, wireless local loop (wireless local loop, WLL) station, personal digital assistant (personal digital assistant, PDA), handheld device with wireless communication function, computing device or other processing device connected to wireless modem, wearable device, terminal device in 5G network or terminal in future evolved land mobile communication network (public land mobile network), and the like, without limiting the application.

By way of example, and not limitation, in embodiments of the present application, the terminal device may also be a wearable device. The wearable device can also be called as a wearable intelligent device, and is a generic name for intelligently designing daily wear by applying wearable technology and developing wearable devices, such as glasses, gloves, watches, clothes, shoes and the like. The wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also can realize a powerful function through software support, data interaction and cloud interaction. The generalized wearable intelligent device includes full functionality, large size, and may not rely on the smart phone to implement complete or partial functionality, such as: smart watches or smart glasses, etc., and focus on only certain types of application functions, and need to be used in combination with other devices, such as smart phones, for example, various smart bracelets, smart jewelry, etc. for physical sign monitoring.

In addition, in the embodiment of the application, the terminal equipment can also be terminal equipment in an IoT system, and the IoT is an important component of the development of future information technology, and the main technical characteristics of the terminal equipment are that the articles are connected with a network through a communication technology, so that the man-machine interconnection and the intelligent network for the interconnection of the articles are realized.

It should be noted that, some air interface technology (such as NR or LTE technology) may be used to communicate between the terminal device and the access network device. The terminal equipment and the terminal equipment can also communicate with each other by adopting a certain air interface technology (such as NR or LTE technology).

In the embodiment of the present application, the device for implementing the function of the terminal device may be the terminal device, or may be a device capable of supporting the terminal device to implement the function, for example, a chip system or a chip, and the device may be installed in the terminal device. In the embodiment of the application, the chip system can be composed of chips, and can also comprise chips and other discrete devices.

2. (radio) access network (R) AN) device: the authorized users of the specific area may be provided with the functionality to access the communication network, which may specifically include wireless network devices in a third generation partnership project (3rd generation partnership project,3GPP) network or may include access points in a non-3GPP (non-3 GPP) network. The following description will be presented using AN apparatus for convenience of description.

AN device may employ different radio access technologies. There are two types of current radio access technologies: 3GPP access technologies (e.g., third generation (3rd generation,3G), fourth generation (4th generation,4G), or wireless access technologies employed in 5G systems) and non-3GPP (non-3 GPP) access technologies. The 3GPP access technology refers to an access technology conforming to the 3GPP standard specification, for example, access network devices in a 5G system are referred to as next generation base station nodes (next generation Node Base station, gNB) or RAN devices. Non-3GPP access technologies can include air interface technologies typified by an Access Point (AP) in Wireless Fidelity (wireless fidelity, wiFi), worldwide interoperability for microwave Access (worldwide interoperability for microwave access, wiMAX), code division multiple Access (code division multiple access, CDMA), and so forth. The AN device may allow interworking between the terminal device and the 3GPP core network using non-3GPP technology.

The AN device can be responsible for radio resource management, quality of service (quality of service, qoS) management, data compression, encryption, and other functions on the air interface side. The AN equipment provides access service for the terminal equipment, and further, the forwarding of control signals and user data between the terminal equipment and the core network is completed.

AN devices may include, for example, but are not limited to: macro base stations, micro base stations (also called small stations), radio network controllers (radio network controller, RNC), node bs (Node bs, NB), base station controllers (base station controller, BSC), base transceiver stations (base transceiver station, BTS), home base stations (e.g., home evolved NodeB, or home Node bs, HNB), base Band Units (BBU), APs in WiFi systems, wireless relay nodes, wireless backhaul nodes, transmission points (transmission point, TP), or transmission reception points (transmission and reception point, TRP), etc., as well as a gNB or transmission points (TRP or TP) in 5G (e.g., NR) systems, an antenna panel of one or a group (including multiple antenna panels) of base stations in 5G systems, or as well as network nodes constituting a gNB or transmission point, such as a Distributed Unit (DU), or a base station in next generation communication 6G systems, etc. The embodiment of the application does not limit the specific technology and the specific equipment form adopted by the AN equipment.

3. AMF: the method is mainly used for the functions of access control, mobility management, attachment and detachment and the like.

4. SMF: the method is mainly used for user plane network element selection, user plane network element redirection, internet protocol (internet protocol, IP) address allocation of terminal equipment and session management in a mobile network, such as session establishment, modification and release and quality of service (quality of service, qoS) control.

In the present application, for distinction, the SMF in the HPLMN is denoted as home SMF (H-SMF), and the SMF in the VPLMN is denoted as visited SMF (V-SMF).

5. UPF: the method is mainly used for receiving and forwarding the user plane data. For example, the UPF may receive user plane data from the DN and send the user plane data to the terminal device through the AN device. The UPF may also receive user plane data from the terminal device through the AN device and forward to the DN. The UPF in the session directly connected to the DN through the N6 interface may be referred to as a protocol data unit (protocol data unit, PDU) session anchor (PDU session anchor, PSA).

In the present application, for distinction, the UPF in the HPLMN is denoted as the home UPF (H-UPF) and the UPF in the VPLMN is denoted as the visited UPF (V-UPF). In addition, for distinction, the PSA in the HPLMN is referred to as home PSA (H-PSA), and the PSA in the VPLMN is referred to as visited PSA (V-PSA) (or as local PSA (L-PSA)).

6. PCF: the unified policy framework is mainly used for guiding network behaviors, and provides policy rule information and the like for control plane network elements (such as AMF, SMF and the like).

In the present application, for distinction, the PCF in the HPLMN is referred to as the home PCF (H-PCF) and the PCF in the VPLMN is referred to as the visited PCF (V-PCF).

7. AF: the method is mainly used for providing services to the 3GPP network, such as interaction with PCF for policy control and the like.

8. Network slice selection function (network slice selection function, NSSF): the method is mainly used for network slice selection.

9. UDM: the method is mainly used for subscription data management of the UE, and comprises storage and management of the UE identification, access authorization of the UE and the like.

10. DN: the method is mainly used for an operator network for providing data services for the UE. Such as the Internet, a third party's service network, an IP Multimedia Services (IMS) network, etc.

11. AUSF: the method is mainly used for user authentication and the like.

In the HR roaming scenario, a session (e.g., referred to as HR session) is connected to the UPF of the home network. HR session refers to a session of a UPF established when a user is located in a visited network and connected to a home network, in which traffic flow (traffic) carried in the HR session is sent from a UE to the UPF of the home network and then to a receiving end.

For example, in the HR roaming scenario, the UE initiates a session establishment request at the VPLMN through the V-SMF; the V-SMF forwards the session establishment request to the H-SMF; the H-SMF connects the H-PCF and performs configuration of session management (session management, SM) policy (policy) and session establishment of the session; V-SMF may configure V-UPF according to the N4 context generated by H-SMF. In the HR roaming scenario, the anchor point of the session is at the H-UPF, the main control network element of the session comprises the H-SMF and the H-PCF, and the V-UPF is mainly responsible for forwarding the data packet between the H-UPF and the RAN.

Fig. 2 is a schematic diagram of another network architecture suitable for use with embodiments of the present application. The network architecture shown in fig. 2 is exemplified by LBO roaming.

As shown in fig. 2, the network architecture may include, but is not limited to: NSSAAF, NSSF, AUSF, UDM, PCF, AF, AMF, SMF, UE radio access network devices, UPF, DN, etc. For the description of each network element, reference may be made to the above description, and details are not repeated here.

In the LBO roaming scenario, a session (e.g., referred to as an LBO session) is not connected to the UPF (i.e., H-UPF) of the home network. LBO session refers to a session established when a user is located in a visited network and connected to a V-UPF, and traffic carried in the LBO session is directly sent out locally in the visited network (i.e., VPLMN), without wrapping around to the UPF (i.e., H-UPF) of the home network (i.e., HPLMN).

For example, in an LBO roaming scenario, the UE initiates a session establishment request at the VPLMN through the V-SMF, which connects the V-PCF and performs configuration of SM policy for the session and session establishment. In LBO roaming scenarios, the anchor point of the session is at the V-UPF, the primary control network elements of the session include the V-SMF and the V-PCF, the V-UPF may offload packets using local multi-access edge computing (multi-access edge computing, MEC) traffic, and forward from the V-UPF to an edge application server (edge application server, EAS) deployed locally.

As shown in fig. 3, the network architecture may include, but is not limited to: SMF, UE, UPF (e.g., V-UPF and H-UPF), PSA (e.g., L-PSA and remote PAS (remote PSA)), upstream classifier (uplink classifier, UL CL), domain name service (domain name service, DNS) server (e.g., L-DNS and C-DNS in fig. 3), edge application server discovers network elements (edge application server discovery function, EASDF). The edge application server discovery network element may also be called, for example, an edge application (service) discovery function, an application instance discovery function, an edge application instance discovery function, an MEC application (server) discovery function, and the like, and is not limited. The following description of some network elements shown in fig. 3 will be briefly described, and for the description of the remaining network elements, reference may be made to the above description, which is not repeated here.

1. UL CL: for forwarding packets that meet traffic filtering rules to a designated path, UL CL functionality may be provided by the UPF. When a UL CL is inserted into a PDU session data channel, the PDU session may have multiple PDU session anchors providing multiple different paths to access the same DN.

2. EASDF, mainly used to assist EAS discovery, has main roles including: the DNS message is processed according to the indication of the SMF. EASDF may be considered a centralized processing network element that may be configured by the SMF at session establishment. The DNS query message for the UE may be sent to the EASDF by the remote PSA. The EASDF may process DNS messages according to SMF configured processing rules (handling rule).

As an example, EASDF processes DNS messages according to processing rules, which may include the following three scenarios.

1) The UE sends a DNS query request to the EASDF, the EASDF queries the SMF for EDNS client subnet options (Edns-client-subnet options, ECS options), or the EASDF locally queries the ECS options (e.g., the SMF pre-configures the ECS options on the EASDF), and sends the UE's DNS query to the C-DNS server. Among them, EDNS is a DNS extension mechanism (extended mechanisms for DNS, EDNS).

In the present application, for distinction, a centralized DNS server deployed in the HPLMN is denoted as a C-DNS server (centralize DNS server), and a local DNS server deployed in the VPLMN is denoted as an L-DNS server (local DNS server). In FIG. 3, C-DNS and L-DNS are used for simplicity, respectively.

2) The UE sends a DNS query request to the EASDF, the EASDF queries the SMF for information of the L-DNS server (such as an address of the L-DNS server), or the EASDF locally queries the L-DNS server (such as the SMF pre-configures the information of the L-DNS server on the EASDF), and sends a DNS query of the UE to the corresponding L-DNS server.

3) The SMF configures forwarding rules for the ULCL, and the UE sends a DNS query request to the L-DNS server through the L-PSA.

The foregoing is merely a simple exemplary illustration and is not intended to be limiting. For example, the UE may send directly to the EASDF through the PSA, and the EASDF may pick a DNS server for forwarding.

As shown in fig. 4, the network architecture may include, but is not limited to: UE, RAN, PSA (e.g., L-PSA and remote PAS), UL CL, DNS (e.g., C-DNS and L-DNS), EASDF, edge data network (edge data network, EDN). Wherein the EDN may comprise a plurality of EAS. It is generally understood that EDN, which corresponds to a data network, is a special local data network (local DN) comprising edge enabled servers (edge enabler server, EES), can be identified using data network access identifiers (DN Access Identifier, DNAI) and data network names (data network name, DNN), and is a network logic concept. Another understanding of EDN: EDNs are peer-to-peer concepts of a central cloud, which can be understood as a local data center (geographical location concept), can be identified using DNAI, and can contain multiple local data networks (local DNs). With respect to the specific definition of EDN, embodiments of the present application are not limited. For the description of the remaining network elements, reference may be made to the above description, which is not repeated here.

OP1 in fig. 4 represents an Operator (OP), and accordingly EDN1 represents an edge data network in the OP 1; alternatively, OP1 may also represent a third party edge computing service provider (edge computing service provider, ECSP), and accordingly EDN1 represents an edge data network in the third party ECSP. OP2 in fig. 4 represents another operator, and EDN2 represents an edge data network in the OP 2. As shown in fig. 4, OP1 may deploy a separate MEC machine room (such as EDN1 in fig. 4) at OP 2; or OP1 may also deploy its own server (e.g., EAS OP1 in EDN2 in fig. 4) in the MEC room of the VPLMN (e.g., EDN2 in fig. 4). For example, if the UE is the UE of OP1, it may be considered that the HPLMN deploys EAS at the VPLMN; as another example, if the UE is an OP2 UE, it may be regarded as an edge service that the local user needs to use other provider.

It is understood that in embodiments of the present application, the MEC room may also be an edge hosting environment (edge hosting environment, EHE).

In the network architecture shown in fig. 1 to 4, the network elements may communicate with each other through AN interface, for example, the UE connects to the AN device through a radio resource control (radio resource control, RRC) protocol, and the UE and the AN device communicate with each other through a Uu interface. Or may refer to the interface shown in fig. 1, and will not be described again here.

It should be understood that the network architecture shown above is merely illustrative, and the network architecture to which the embodiments of the present application are applied is not limited, and any network architecture capable of implementing the functions of the respective network elements described above is applicable to the embodiments of the present application. In addition, other network elements, such as network opening functions (network exposure function, NEF), may be included in the network architecture shown above, and the unified data storage network element (unified data repository, UDR) is not limited thereto. Among them, the NEF is mainly used to safely open services and capabilities provided by 3GPP network functions, etc., to the outside. In the present application, for distinction, the NEF in the HPLMN is designated as home NEF (H-NEF), and the NEF in the VPLMN is designated as visited NEF (V-NEF). In the present application, for distinction, the UDR in the HPLMN is denoted home UDR (H-UDR) and the UDR in the VPLMN is denoted visited UDR (V-UDR).

It should also be understood that the functions or network elements AMF, SMF, UPF, PCF, UDM, NSSF, AUSF shown in fig. 1 to 4 may be understood as network elements for implementing different functions, for example, may be combined into network slices as required. The network elements may be independent devices, may be integrated in the same device to implement different functions, or may be network elements in hardware devices, or may be software functions running on dedicated hardware, or may be virtualized functions instantiated on a platform (for example, a cloud platform), where the specific form of the network elements is not limited by the present application.

It should also be understood that the above designations are merely intended to facilitate distinguishing between different functions and should not be construed as limiting the application in any way. The application does not exclude the possibility of using other designations in 6G networks as well as other networks in the future. For example, in a 6G network, some or all of the individual network elements may follow the terminology in 5G, possibly by other names, etc.

As described above, the UE may access the VPLMN by roaming. The HPLMN operator may deploy its own EAS at the VPLMN or the third party ECSP may deploy its own EAS at the VPLMN. According to existing DNS query techniques, it is not possible to distinguish to which operator the EAS belongs. Or if the UE subscribes to the edge calculation service of the third party ECSP, according to the existing DNS query technology, the EAS corresponding to the third party ECSP in the VPLMN cannot be preferentially provided for the UE. Therefore, how to select the EAS in the VPLMN for a roaming UE that corresponds to a particular network (e.g., a third party ECSP or HPLMN) is a considerable issue.

The application provides a scheme, according to the information of the provider providing the edge computing service for the terminal equipment, the corresponding EAS deployment information of the provider, namely the corresponding EAS deployment information of the provider in the access network of the terminal equipment is determined, and then the session management network element configures DNS processing rules based on the corresponding EAS deployment information of the provider, so that when the edge application server finds that the network element processes the DNS inquiry information of the terminal equipment based on the DNS processing rules, the edge application server can provide the EAS of the provider for the terminal equipment, namely the corresponding EAS of the provider in the access network of the terminal equipment.

For example, if the UE subscribes to an edge computing service of a third party ECSP, and the access network of the UE is a PLMN (e.g., referred to as plmn#a), EAS deployment information corresponding to the third party ECSP may be found according to the identity of the third party ECSP, that is, EAS deployment information of the third party ECSP in plmn#a; thus, the SMF configures DNS processing rules according to the EAS deployment information of the third party ECSP in the PLMN#A; after the EASDF receives the DNS processing rule, the DNS query request of the UE may be processed based on the DNS processing rule, so as to find EAS corresponding to the third party ECSP in the plmn#a for the UE, so that the UE may preferentially use EAS corresponding to the third party ECSP in the plmn#a.

For another example, if the UE is to use the edge computing service of the HPLMN, and the access network of the UE is a VPLMN, the EAS deployment information corresponding to the HPLMN may be found according to the identity of the HPLMN, that is, the EAS deployment information of the HPLMN in the VPLMN; so that the SMF configures DNS processing rules according to the EAS deployment information of the HPLMN in the VPLMN; after the EASDF receives the DNS processing rule, the DNS query request of the UE may be processed based on the DNS processing rule, so as to find an EAS corresponding to the HPLMN in the VPLMN for the UE, so that the UE may preferentially use the EAS corresponding to the HPLMN in the VPLMN.

It will be appreciated that the term "and/or" is merely one association relationship describing the associated object, and means that three relationships may exist, for example, a and/or B may mean: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.

The method of communication provided by the embodiment of the present application will be described in detail below with reference to the accompanying drawings. The embodiments provided in the present application may be applied to the network architecture shown in fig. 1 to 4, and are not limited thereto.

Fig. 5 is a schematic diagram of a method 500 for communication according to an embodiment of the present application. The method 500 may include the following steps.

501, the session management network element obtains provider information, and the provider is a provider for providing edge computing service for terminal equipment;

502, configuring DNS processing rules by the session management network element according to provider information and EAS deployment information corresponding to the provider, wherein the DNS processing rules are used for processing DNS information of terminal equipment, and the EAS deployment information is the corresponding EAS deployment information of the provider in an access network of the terminal equipment;

503, the session management network element sends DNS handling rules to the edge application server discovery network element.

Accordingly, the edge application server sending network element receives the DNS handling rules. The edge application server sends DNS query messages of the terminal equipment according to the DNS processing rules.

Provider (provider) information, which indicates information of a provider providing an edge computing service for the terminal device. As an example, the information of the provider may be, for example, a provider ID (provider ID). It will be appreciated that the provider may represent a provider of EAS, or may represent a provider of EHE, without limitation.

Optionally, the provider comprises one or more of the following: a visited network (e.g., VPLMN of UE), a home network (e.g., HPLMN of UE), a third party edge computing service provider (edge computing service provider, ECSP). The third ECSP may be an ECSP subscribed (or requested) by the terminal device, or may also be a corresponding third party ECSP in plmn#a, which is not limited.

The access network of the terminal device, or the service network of the terminal device, represents the network currently providing services for the terminal device. The access network may be, for example, a representation of the access network, such as an identification of the access PLMN (access PLMN ID).

Hereinafter, for brevity and distinction, an access network of the terminal device is denoted as plmn#a, and a provider providing an edge computing service for the terminal device is denoted as provider#b. It will be appreciated that the naming of PLMN #a and provider #b does not limit the scope of the embodiments of the present application.

The EAS deployment information corresponding to provider #b indicates the EAS deployment information corresponding to provider #b in PLMN #a. EAS deployment information corresponding to provider #b includes the following forms: for example, the EAS deployment information includes provider #b information (e.g., provider #b ID); for another example, the EAS deployment information is associated with provider #b information (e.g., provider #b ID); for another example, the EAS deployment information includes provider #b information (e.g., provider #b ID) and PLMN #a information (e.g., PLMN #a ID); for another example, the EAS deployment information is associated with provider #b information (e.g., provider #b ID) and PLMN #a information (e.g., PLMN #a ID).

Optionally, in step 502, the session management network element configures DNS processing rules according to provider information and EAS deployment information corresponding to the provider, including: the session management network element determines EAS deployment information corresponding to the provider according to the provider information, and configures DNS processing rules according to the EAS deployment information corresponding to the provider.

In one possible implementation manner, the session management network element requests EAS deployment information corresponding to the provider #b from the network deployment network element, so as to obtain the EAS deployment information corresponding to the provider #b. In another possible implementation manner, the session management network element requests a plurality of EAS deployment information from the network deployment network element, and the session management network element determines EAS deployment information corresponding to provider#b from the plurality of EAS deployment information. It will be appreciated that the two modes described above are exemplary illustrations and are not limiting. As an example, EAS deployment information may also include one or more of the following: DNN, single-network-slice selection assistance information (single-network slice selection assistance information, S-nsai), external group identifier (external group identifier)/internal group identifier (internal group identifier), application information (e.g., application ID), full domain name (full qualified domain name, FQDN).

Two ways of determining EAS deployment information corresponding to provider #b are described below.

One possible way is to determine EAS deployment information corresponding to provider #b based on the provider #b information (e.g., provider #bid). Based on this approach, EAS deployment information corresponding to provider #b may be queried through the information of provider #b (e.g., provider #b ID).

For example, the EAS deployment information corresponding to provider #b may include provider #bid, so that EAS deployment information including the provider #bid may be determined according to provider #bid.

For another example, EAS deployment information corresponding to provider #b is associated with provider #bid, and thus EAS deployment information associated with the provider #bid may be determined from the provider #bid.

In another possible manner, EAS deployment information corresponding to provider #b is determined according to the provider #b and PLMN #a information. In this case, the EAS deployment information corresponding to provider #b may be described as EAS deployment information corresponding to provider #b and PLMN #a, or EAS deployment information corresponding to provider #b in PLMN #a. Based on this approach, EAS deployment information corresponding to provider #b may be queried through information of provider #b and PLMN #a (e.g., provider #b ID and PLMN #a ID).

For example, the EAS deployment information corresponding to provider #b (or the EAS deployment information corresponding to provider #b and PLMN #a, or the EAS deployment information corresponding to provider #b in PLMN #a) may include provider #bid and PLMN #aid, and thus the EAS deployment information including the provider #bid and PLMN #aid may be determined according to provider #bid.

For another example, EAS deployment information corresponding to provider #b (or EAS deployment information corresponding to provider #b and PLMN #a, or EAS deployment information corresponding to provider #b in PLMN #a) is associated with provider #bid and PLMN #aid, so EAS deployment information associated with the provider #bid and PLMN #aid can be determined from the provider #bid and PLMN #aid.

Optionally, the EAS deployment information corresponding to provider #b may include one or more of the following: DNS server, ECS option, EAS address. EAS registered on DNS server is EAS corresponding to provider #b in PLMN #a. As an example, DNS servers may be C-DNS servers (e.g., DNS servers deployed in HPLMN) or L-DNS servers (e.g., DNS servers deployed in PLMN #a). The EAS corresponding to ECS option is the EAS corresponding to provider #b in PLMN #a. The EAS address is the address of the EAS corresponding to provider #b in PLMN #a. As an example, the EAS address is an EAS IP address. Several examples are listed below.

Example 1, the EAS deployment information corresponding to provider#b includes a C-DNS server.

The SMF configures DNS processing rules for the terminal device according to the EAS deployment information corresponding to provider #b, and in this example, the DNS processing rules configured by the SMF for EASDF include the C-DNS server.

Optionally, the method 500 further comprises: the EASDF sends a query message of the DNS of the terminal device to the C-DNS server (i.e., the C-DNS server included in the EAS deployment information corresponding to provider #b), and the C-DNS server processes the query message of the DNS of the terminal device. Since the EAS registered on the C-DNS server is the EAS corresponding to provider #b in PLMN #a, the C-DNS server returns to the EASDF the address of the EAS corresponding to provider #b in PLMN #a. Thus, the EASDF may provide the terminal device with the EAS corresponding to provider #b in PLMN #a.

As an example, a structure suitable for example 1 is described below with reference to fig. 6.

Fig. 6 is a schematic diagram of a network architecture according to an embodiment of the present application. Assuming that plmn#a is VPLMN and provider#b is HPLMN, under the architecture, after receiving a DNS query message of a roaming UE, the EASDF may send a DNS query of the UE to a C-DNS server corresponding to the HPLMN (i.e., a C-DNS server included in EAS deployment information corresponding to provider#b) according to a DNS processing rule obtained from the SMF. After the EASDF receives a DNS query message from a UE (i.e., a normal UE, or a non-roaming UE), the EASDF may send the DNS query of the UE to the C-DNS server according to DNS processing rules obtained from the SMF. The specific flow is described below in connection with method 900.

Example 2, the EAS deployment information corresponding to provider#b includes ECS option.

The SMF configures DNS processing rules for the terminal device according to the EAS deployment information corresponding to provider #b, and in this example, the DNS processing rules configured by the SMF for EASDF include the ECS option.

Optionally, the method 500 further comprises: the EASDF adds the ECS option (i.e., the ECS option included in the EAS deployment information corresponding to provider #b) to the DNS query message of the terminal device. Further, the EASDF may send a DNS query message to a DNS server (e.g., a C-DNS server) that adds the ECS option, which is processed by the DNS server. Since the EAS corresponding to the ECS option is the EAS corresponding to the provider #b in the PLMN #a, the DNS response returned by the DNS server to the EASDF carries the address of the EAS corresponding to the ECS option (i.e., the address of the EAS corresponding to the provider #b in the PLMN #a). Thus, the EASDF may provide the terminal device with the EAS corresponding to provider #b in PLMN #a.

As an example, the architecture shown in fig. 6 may also be used for the implementation of example 2. Assuming that plmn#a is VPLMN and provider#b is HPLMN, under the architecture shown in fig. 6, after the EASDF receives the DNS query message of the roaming UE, ECS option corresponding to HPLMN (i.e., ECS option included in EAS deployment information corresponding to provider#b) may be added to the DNS query message according to a DNS processing rule obtained from the SMF. After the EASDF receives the DNS query message of the UE (i.e., a normal UE or a non-roaming UE), the EASDF may add an ECS option to the DNS query message according to the DNS processing rule obtained from the SMF, and send the ECS option to the C-DNS server, or may directly forward the DNS query message of the UE to the L-DNS server. The specific flow is described below in connection with method 1000.

Example 3, the EAS deployment information corresponding to provider#b includes an L-DNS server.

The SMF configures DNS processing rules for the terminal device according to the EAS deployment information corresponding to provider #b, and in this example, the L-DNS server is included in the DNS processing rules configured by the SMF for EASDF.

Optionally, the method 500 further comprises: the EASDF sends a query message of the DNS of the terminal device to the L-DNS server (i.e., the L-DNS server included in the EAS deployment information corresponding to provider #b), and the L-DNS server processes the query message of the DNS of the terminal device. Since the EAS registered on the L-DNS server is the EAS corresponding to provider #b in PLMN #a, the L-DNS server returns to the EASDF an address of the EAS corresponding to provider #b in PLMN #a. Thus, the EASDF may provide the terminal device with the EAS corresponding to provider #b in PLMN #a.

As an example, a structure suitable for example 3 is described below in connection with fig. 7.

Fig. 7 is a schematic diagram of a network architecture according to another embodiment of the present application. Assuming that plmn#a is VPLMN and provider#b is HPLMN, under the architecture, after receiving a DNS query message of a roaming UE, the EASDF may send a DNS query of the UE to an L-DNS server corresponding to the HPLMN (i.e., an L-DNS server included in EAS deployment information corresponding to provider#b) according to a DNS processing rule obtained from the SMF. After the EASDF receives a DNS query message from a UE (i.e., a normal UE, or a non-roaming UE), the EASDF may send the DNS query of the UE to the L-DNS server according to DNS processing rules obtained from the SMF. With respect to the specific flow, the description of the method 1100 is provided below.

Example 4, the EAS deployment information corresponding to provider#b includes an EAS address.

The SMF configures DNS processing rules for the terminal device according to the EAS deployment information corresponding to provider #b, and in this example, the DNS processing rules configured by the SMF for EASDF include the EAS address.

Optionally, the method 500 further comprises: the EASDF selects an address belonging to the EAS address (i.e., the EAS address included in the EAS deployment information corresponding to provider #b) in response to the inquiry of the DNS of the terminal device. The EASDF obtains the address of at least one EAS from a DNS server; the EASDF may select a part or all of the EAS addresses from the addresses of at least one EAS according to the EAS address, the part or all of the EAS addresses belonging to the EAS address. Thus, the EASDF may provide the terminal device with the EAS corresponding to provider #b in PLMN #a.

As an example, a structure suitable for example 4 is described below with reference to fig. 8.

Fig. 8 is a schematic diagram of a network architecture according to another embodiment of the present application. Assuming plmn#a is VPLMN and provider#b is HPLMN information, under the architecture, after the EASDF receives a DNS query message of the roaming UE, the EASDF may query an EAS IP address (e.g., including an EAS IP address corresponding to the HPLMN and an EAS IP address corresponding to the VPLMN) from the L-DNS server, and filter (or select) the EAS IP address corresponding to the HPLMN from the queried EAS IP addresses according to DNS processing rules obtained from the SMF. After the EASDF receives the DNS query message of the UE (i.e., a normal UE, or a non-roaming UE), the EASDF may query the L-DNS server for the EAS IP address according to DNS processing rules obtained from the SMF, and return the queried EAS IP address to the UE. The specific flow is described below in connection with method 1200.

In addition, each of the above information is described separately, and it is understood that each of the above information may be used alone or in combination. One possible example of a combination is described below.

Example 5 the EAS deployment information corresponding to provider#b includes a C-DNS server and ECS option.

The SMF configures DNS processing rules for the terminal device according to EAS deployment information corresponding to provider #b, and in this example, the DNS processing rules configured by the SMF for EASDF include the C-DNS server and ECS option.

Optionally, the method 500 further comprises: the EASDF adds the ECS option (i.e., the ECS option included in the EAS deployment information corresponding to provider #b) to a DNS query message of the DNS of the terminal device, and further, the EASDF may send a DNS query message for adding the ECS option to the C-DNS server (i.e., the C-DNS server included in the EAS deployment information corresponding to provider #b), where the DNS query message for adding the ECS option is processed by the C-DNS server.

The foregoing is a simple exemplary illustration, which is described in detail below in connection with methods 900-1300.

Optionally, in step 501, the session management network element acquires information of provider#b, including: the session management network element determines the information of provider#b according to the terminal device.

The session management network element may determine the information of provider#b according to any one of the following information: the home network of the terminal device, subscription information of the terminal device or the terminal device, and the terminal device list provided by provider #b include protocols between the terminal device, provider #b and PLMN #a. In other words, the session management network element may determine EAS deployment information corresponding to provider #b according to any one of the above information, i.e., the session management network element may determine provider #b according to any one of the above information, and may further query the EAS deployment information corresponding to provider #b.

Several examples are presented below.

Example 1, smf determines provider#b information from UE or subscription information of UE.

The subscription information of the UE may include provider #b information (e.g., provider #b ID). For example, the subscription information of the UE includes information of services that can use the provider #b, and thus the provider #b can be determined based on the information. For another example, the subscription information of the UE includes that plmn#a has a cooperative relationship (or alliance relationship) with provider#b, and the UE of plmn#a is allowed to use EAS of provider#b, so provider#b can be determined based on the information.

In one possible implementation, the SMF determines the provider #b information according to the UE ID. As an example, the UE ID may be: a user permanent identity (subscription permanent identifier, SUPI) or permanent device identity (permanent equipment identifier, PEI) of the UE.

Take provider#b as HPLMN or VPLMN as an example. For example, the SMF may obtain the provider #bid (e.g., HPLMN ID, also VPLMN ID) of the UE by querying the AMF. For example, the AMF may obtain the SUPI of the UE in the UE registration procedure, the AMF may determine the provider #b ID of the UE according to the SUPI of the UE, and the AMF may send the provider #b ID of the UE to the SMF based on the request of the SMF; or in the session establishment procedure, the AMF sends the provider #b ID of the UE to the SMF. For another example, the SMF analyzes the SUPI of the UE, and may further obtain the provider #b ID of the UE.

Take provider #B as ECSP for example. For example, the SMF may get the ECSP ID to which the UE subscribes by querying UDR or NEF. For example, the AF corresponding to the ECSP sends EAS subscription information to the UDR through the NEF, and the UDR stores the EAS subscription information, where the EAS subscription information includes: ECSP ID corresponding to EAS, and UE ID subscribing to ECSP; the SMF determines the UE ID and queries the UDR for the ECSP subscribed by the UE through the NEF; the UDR determines ECSP IDs subscribed to by the UE based on locally stored EAS subscription information and sends the ECSP IDs subscribed to by the UE to the SMF via the NEF. Optionally, DNN and/or S-NSSAI are also included in the EAS subscription information. Alternatively, the EAS subscription information may be carried in an AF request (AF request) message.

It will be appreciated that if there are multiple ECSPs subscribed to by the UE, the SMF may also determine the ECSP ID to provide edge computing services to the UE according to any of the following ways.

In mode 1, the smf determines ECSP IDs for providing an edge computing service for the UE from among a plurality of ECSP IDs subscribed to by the UE, according to the ECSP IDs and priorities of the ECSPs. Among them, priority with respect to a plurality of ECSPs is not limited. For example, the priorities of the plurality of ECSPs may be determined according to the ID sizes of the plurality of ECSPs; for another example, the priority of the plurality of ECSPs may be determined according to the frequency of use of the plurality of ECSPs.

In mode 2, the smf selects one ECSP from a plurality of ECSPs (either according to a protocol convention or according to a predetermined convention) according to the ECSP IDs subscribed to by the UE as the ECSP providing the edge computing service to the UE.

The above two ways are exemplary illustrations, and embodiments of the present application are not limited thereto.

Example 2, the smf includes information of the UE determining provider #b in the UE list provided according to provider #b.

If the UE list provided by provider #b includes a UE, information of provider #b may be determined.

For example, if the UE is a provider #b UE, the provider #b may provide edge computing services for the UE, and may determine provider #b for the UE. Specific examples may refer to the foregoing example 1, and will not be described herein.

Example 3, the smf determines provider #b information according to the protocol between provider #b and PLMN #a.

The protocol between provider #b and PLMN #a may indicate that provider #b and PLMN #a have a cooperative relationship or a federation relationship. If there is a cooperative relationship between the provider#b and the plmn#a, such as allowing the UE of plmn#a to use the EAS of provider#b or allowing the UE of provider#b to use the EAS of plmn#a, the provider#b may be determined for the UE.

For example, if the UE is a plmn#a UE, if the provider#b has a cooperative relationship with plmn#a, the provider#b may provide edge computing services for the UE, and may further determine provider#b for the UE. Specific examples may refer to the foregoing example 1, and will not be described herein.

Example 4, SMF determines provider#B information from HPLMN.

If there is a cooperative relationship between HPLMN and provider#B, such as allowing the HPLMN's UE to use the EAS of provider#B or allowing the provider#B's UE to use the EAS of HPLMN, provider#B may be determined for the HPLMN's UE. Specific examples may refer to the foregoing example 1, and will not be described herein.

Under different roaming scenes, the adaptive adjustment can be performed according to the roaming scene, and the method is not limited. The following is a brief description in connection with two scenarios.

Scene 1, lbo roaming scene.

Example 1, assume provider#b is the HPLMN of the UE and plmn#a is the VPLMN of the UE.

For example, V-SMF of PLMN #a may determine to use EAS corresponding to provider #b according to HPLMN ID of UE, and thus V-SMF may configure DNS processing rule according to EAS deployment information corresponding to HPLMN ID (i.e., provider #b=hplmn ID).

For another example, the V-SMF determines from the VPLMN ID and the HPLMN ID that EAS corresponding in the VPLMN is to be used with the HPLMN ID, and thus the V-SMF may configure DNS processing rules according to EAS deployment information corresponding to the VPLMN ID and the HPLMN ID (i.e., PLMN #a=vplmn ID, and provider #b=hplmn ID).

Example 2, suppose provider #b is VPLMN of UE and PLMN #a is VPLMN of UE.

For example, if the V-SMF determines that the UE can use (or needs to use) EAS of the VPLMN according to the UE subscription, the V-SMF configures DNS processing rules according to EAS deployment information corresponding to the VPLMN ID (i.e., provider #b=vplmn ID).

Example 3, suppose provider #b is a third party ECSP and PLMN #a is a VPLMN of the UE.

For example, if the V-SMF determines that the UE can use (or needs to use) EAS of the third party ECSP according to the UE subscription, the V-SMF configures DNS processing rules according to EAS deployment information corresponding to the third party ECSP ID (i.e., provider #b=third party ECSP ID).

For another example, the V-SMF determines, from the VPLMN ID and the third party ECSP ID, EAS that corresponds in the VPLMN to use the third party ECSP ID, and thus the V-SMF may configure DNS processing rules according to EAS deployment information that corresponds to the VPLMN ID and the third party ECSP ID (i.e., PLMN #a=vplmn ID, and provider #b=third party ECSP ID).

It will be appreciated that the three examples above are illustrative, and provider#b may be other PLMNs, without limitation.

Scene 2, hr roaming scene.

For example, the H-SMF of provider #b may determine to use EAS corresponding to provider #b according to the HPLMN ID of the UE, and thus, the H-SMF may configure DNS processing rules according to EAS deployment information corresponding to the HPLMN ID (i.e., provider #b=hplmn ID).

For another example, the H-SMF determines from the VPLMN ID and the HPLMN ID that EAS corresponding in the VPLMN is to be used with the HPLMN ID, and thus, the H-SMF may configure DNS processing rules according to EAS deployment information corresponding to the VPLMN ID and the HPLMN ID (i.e., PLMN #a=vplmn ID, and provider #b=hplmn ID).

Example 2, suppose provider #b is VPLMN of UE and PLMN #a is VPLMN of UE.

For example, if the H-SMF determines that the UE can use (or needs to use) EAS of the VPLMN according to the UE subscription, the H-SMF configures DNS processing rules according to EAS deployment information corresponding to the VPLMN ID (i.e., provider #b=vplmn ID).

For example, if the H-SMF determines that the UE can use (or needs to use) EAS of the third party ECSP according to the UE subscription, the H-SMF configures DNS processing rules according to EAS deployment information corresponding to the third party ECSP ID (i.e., provider #b=third party ECSP ID).

For another example, the H-SMF determines, from the VPLMN ID and the third party ECSP ID, EAS that are to be corresponding in the VPLMN using the third party ECSP ID, and thus the H-SMF may configure DNS processing rules according to EAS deployment information that is corresponding to the VPLMN ID and the third party ECSP ID (i.e., PLMN #a=vplmn ID, and provider #b=third party ECSP ID).

While the foregoing has been briefly described in connection with two roaming scenarios, it will be appreciated that the solution of the embodiments of the present application is not limited to the foregoing scenarios.

For ease of understanding, embodiments of the present application are described below with reference to fig. 9-13, wherein reference is made specifically to the steps described above.

Fig. 9 is a schematic flow chart diagram of a method 900 of communication provided by an embodiment of the present application. The method 900 may be used to implement a scheme such as method 500 (e.g., example 1 in method 500), for example, the method 900 may be used for PLMN # A, provider #b, and C-DNS servers have associated scenarios. By way of example, method 900 may be implemented by the architecture shown in fig. 6. The method 900 may include the following steps.

901, the af sends EAS deployment information to the NEF.

For example, the AF sends an Nnef interface EAS deployment setup Request (Nnef_EASDepsilon_Create Request) to the NEF, which includes EAS deployment information. For another example, the AF sends an Nnef interface EAS deployment Update Request (Nnef_EASDepsilon_update Request) to the NEF, which includes the EAS deployment information.

The EAS deployment information is EAS deployment information corresponding to provider #B, and the EAS deployment information comprises provider #B ID and C-DNS server #B, wherein the EAS registered on the C-DNS server #B is the EAS corresponding to provider #B in PLMN #A. It will be appreciated that the C-DNS server #b is a name for distinction, and the name does not limit the scope of protection of the embodiment of the present application. Optionally, the EAS deployment information further includes a PLMN #a ID.

As an example, provider #bid may be any one of the following: HPLMN ID, VPLMN ID, ECSP ID. It will be appreciated that provider #bid may also be carried in the ID (e.g., the ID of the SMF) of a certain network element in the PLMN (e.g., HPLMN, also e.g., VPLMN), by which the PLMN may also be determined, i.e., the PLMN ID may also be determined. Reference may be made to the relevant description in method 500 for provider #b, which is not repeated here.

Optionally, the EAS deployment information further includes at least one of: DNN, S-NSSAI, or ECS option corresponding to DNAI. For example, if the EAS deployment information includes dnn#1, the EAS deployment information is EAS deployment information corresponding to dnn#1. For another example, if the EAS deployment information includes S-nsai#1, the EAS deployment information is indicated as EAS deployment information corresponding to S-nsai#1.

The NEF processes 902 the EAS deployment information.

Optionally, the NEF processes the EAS deployment information, including: the NEF performs authorization verification on the EAS deployment information. If the NEF successfully authenticates the EAS deployment information authorization, the NEF can send the EAS deployment information to the UDR. If the NEF fails the authorization verification of the EAS deployment information, one possible implementation may inform the AF of the failure of the authorization verification of the EAS deployment information. In the embodiment of the application, it is assumed that NEF successfully authenticates the EAS deployment information authorization.

903, the nef sends EAS deployment information to the UDR.

For example, the NEF sends a Nudr interface Data Management (DM) setup Request (nudr_dm_create Request) to the UDR, which includes EAS deployment information therein. For another example, the NEF sends a Nudr interface DM Update Request (Nudr_DM_update Request) to the UDR, the Nudr_DM_update Request including the EAS deployment information.

After receiving the EAS deployment information, the UDR may store the EAS deployment information. If the UDR successfully stores the EAS deployment information, a store response may be returned to the NEF informing the NEF of: UDR has successfully stored EAS deployment information.

904, the udr sends a store response to the NEF.

For example, if the NEF sends a nudr_dm_create Request to the UDR in step 903, the UDR returns a Nudr interface DM setup response (nudr_dm_createresponse) to the NEF in step 904. For another example, if the NEF sends a nudr_dm_update Request to the UDR in step 903, the UDR returns a Nudr interface DM Update response (nudr_dm_updateresponse) to the NEF in step 904.

905, the nef sends an EAS deployment information response to the AF.

For example, if in step 901 the AF sends an nnef_eastern_create Request to the NEF, then in step 905 the NEF returns an Nnef interface EAS deployment setup response (nnef_eastern_createresponse) to the AF. For another example, if in step 901 the AF sends an nnef_easliptionupdate Request to the NEF, then in step 905 the NEF returns an Nnef interface EAS deployment Update response (nnef_easliptionupdate response) to the AF.

The ue initiates a session establishment procedure 906.

The present application is not limited to a specific session establishment procedure, and may be, for example, as follows: after receiving a session establishment request of the UE, the AMF selects SMF serving the session; after receiving the session establishment request, the SMF selects a UPF serving the session, creates an N4 session, and sends user plane tunnel information. If the session establishment is successful, the network side returns a session establishment response to the UE, and then the message can be transmitted through the session.

In particular, the present application is not limited by reference to 4.3.2.2.2 in 3GPP standard TS 23.503 or the like, or by the manner in which a session is established later.

It will be appreciated that in step 906, the UE may initiate the establishment procedure of the HR session or may initiate the establishment procedure of the LBO session, without limitation.

It is further understood that step 906 is not limited to performing a complete session establishment procedure, and that steps following step 906 may be multiplexed (or reused, or continue to perform) the session establishment procedure, or that steps following step 906 may be performed in the session establishment procedure.

907, the smf requests EAS deployment information from the NEF.

For example, the SMF receives a session establishment request message from the UE, where the session establishment request message includes: S-NSSAI, DNN, PDU session ID; the SMF sends a request message to the NEF, the request message including DNN and/or S-nsai, the request message being used to request (or query, or subscribe to) EAS deployment information corresponding to the DNN and/or S-nsai.

A possible implementation, the SMF requesting EAS deployment information from the NEF, comprising: the SMF sends an Nnef interface EAS deployment subscription request (Nnef_EASDepiment_ Subscribe Request) to the NEF, wherein the Nnef_EASDepiment_ Subscribe Request comprises DNN and/or S-NSSAI, and the Nnef_EASDepiment_ Subscribe Request is used for requesting the EAS deployment information corresponding to the DNN and/or S-NSSAI.

Optionally, when the SMF requests EAS deployment information from the NEF, the SMF may also carry a provider #b ID, where the request is for requesting EAS deployment information corresponding to provider #b. Alternatively, when the SMF requests EAS deployment information from the NEF, the SMF may also carry a provider #b ID and a PLMN #a ID, where the request is for requesting the deployment information of EAS corresponding to the provider #b in the PLMN #a. The manner in which the SMF determines provider #b ID refers to the description in method 500, and is not described here.

908, the NEF obtains the EAS deployment information from the UDR.

For example, upon receiving a request from an SMF, the NEF requests (or subscribes to, or queries) the corresponding EAS deployment information of DNN and/or S-NSSAI from the UDR. In step 903, the UDR stores the EAS deployment information, and thus, in step 908, upon receiving the request for the NEF, the UDR may query the stored EAS deployment information for EAS deployment information corresponding to the DNN and/or S-nsai.

Optionally, if the SMF further carries a provider #b ID when requesting EAS deployment information from the NEF, or if the SMF further carries a provider #b ID and a PLMN #a ID when requesting EAS deployment information from the NEF, the UDR may query the stored EAS deployment information for the EAS deployment information corresponding to the provider #b after receiving the request from the NEF.

909, the nef sends EAS deployment information to the SMF.

After the NEF obtains the EAS deployment information corresponding to DNN and/or S-NSSAI from UDR, the EAS deployment information is sent to SMF.

At 910, the SMF selects EASDF.

The application is not limited to the particular manner in which the SMF selects EASDF.

As an example, when the SMF selects EASDF, one or more of the following information may be referenced: S-NSSAI, location of EASDF, DNAI. It will be appreciated that the SMF may refer to one or more of the above information when selecting EASDF, or may refer to other information not listed, and the application is not limited.

As an example, the SMF selects EASDF, which may be implemented at least in any of the following ways.

In one manner, the SMF may select EASDF according to the local configuration.

In yet another approach, the SMF obtains EASDF from a network registration function (network repository function, NRF). For example, the SMF sends a request message to the NRF, which returns information (e.g., including address, identification, etc.) of one or more EASDF to the SMF. If the NRF returns multiple EASDF to the SMF, the SMF may select one from them.

It will be appreciated that the method of SMF selecting EASDF may be the method of SMF selecting EASDF in a non-roaming scenario, or the later-occurring SMF selecting EASDF, without limitation.

911, the SMF configures DNS processing rules for the EASDF based on the EAS deployment information, the DNS processing rules including C-DNS server #B.

In one possible scenario, the EAS deployment information received by the SMF from the NEF is the EAS deployment information corresponding to provider #b, and then the SMF may configure DNS processing rules for the EASDF directly according to the EAS deployment information corresponding to provider #b.

In another possible scenario, if the EAS deployment information received by the SMF from the NEF is EAS deployment information corresponding to the DNN and/or the S-nsai, the SMF may determine the EAS deployment information corresponding to the provider #b according to the provider #b ID, or the SMF may determine the EAS deployment information corresponding to the provider #b according to the provider #bid and the PLMN #aid, and configure DNS processing rules for the EASDF according to the EAS deployment information corresponding to the provider #b.

For the manner in which the SMF determines the EAS deployment information corresponding to provider #b, reference may be made to the description in method 500, which is not repeated herein.

As an example, step 911 includes: and the SMF generates a DNS processing rule according to the EAS deployment information corresponding to the provider#B, and sends the DNS processing rule to the EASDF. For example, the SMF sends a neosdf interface context creation request (neosdf_context_create request) to the EASDF, the neosdf_context_create request including DNS processing rules; the EASDF returns a Neasdf interface context creation response (neasdf_context_create response) to the SMF.

Among other things, DNS processing rules may be used to process DNS messages, such as DNS messages related to a UE. For example, DNS processing rules may be used to process DNS query messages.

As an example, DNS processing rules may include one or more of the following information: FQDN range, ECS option, C-DNS server #b address, DNS forwarding rules.

Wherein ECS option can be used to characterize the location information of the UE.

The DNS forwarding rule may also be referred to as a forwarding rule, or a data plane forwarding rule, may be used by the EASDF to perform corresponding processing on a DNS message from the UE. For example, when the FQDN contained in the DNS query sent by the UE matches the FQDN range in the DNS processing rule, the EASDF adds ECS option to the DNS query based on the DNS forwarding rule. For another example, when the FQDN included in the DNS query sent by the UE matches the FQDN range in the DNS processing rule, the EASDF forwards the DNS query (e.g., the DNS query after adding the ECS option) to the DNS server based on the DNS forwarding rule.

Wherein, C-DNS server #B represents the C-DNS server in the EAS deployment information that provider #B corresponds.

Through the above steps and other steps (refer specifically to the existing session establishment procedure), the UE may complete session establishment.

The ue sends 912 a DNS query to the EASDF.

For example, the UE sends a DNS query message to the H-EASDF via the RAN and UPF via the user plane.

The DNS query may include an FQDN corresponding to an application that the UE wants to access.

913, the easdf processes DNS queries according to DNS processing rules.

After the EASDF receives the DNS query, the DNS query may be processed according to DNS processing rules received from the SMF. The EASDF processes DNS queries according to DNS processing rules, which may include: the EASDF sends the DNS query of the UE to the C-DNS server #b included in the DNS processing rules.

For example, if the EASDF detects according to the DNS processing rule that the FQDN included in the DNS query of the UE may be matched with the FQDN included in the DNS processing rule, the EASDF sends the DNS query after adding the ECS option to the DNS query to the C-DNS server #b according to the DNS processing rule.

914, the EASDF sends a DNS query containing ECS option to C-DNS server #B.

For example, after adding the ECS option in the DNS query, the EASDF sends a DNS query message (i.e., a DNS query message to which the ECS option has been added) to the C-DNS server #B.

It should be noted that, in the embodiment of the present application, the embodiment is mainly exemplified by adding the ECS option to the DNS query by using the EASDF, which is not limited thereto. That is, how the EASDF handles DNS queries of the UE is not limited, so long as the EASDF can send DNS queries to the C-DNS server #b included in the DNS handling rule, so that the C-DNS server #b provides information of EAS corresponding to provider #b, which is suitable for the embodiment of the present application.

915, C-DNS server #B returns a DNS response (DNS response) to the EASDF.

The C-DNS server may send a DNS response to the EASDF, which may contain information (e.g., an EAS IP address) of the EAS corresponding to provider #B. The description is made in connection with three cases.

Case 1, provider#B is HPLMN ID. In this case, EAS corresponding to provider #b indicates EAS corresponding to HPLMN.

Case 2, provider#B is VPLMN ID. In this case, EAS corresponding to provider #b indicates EAS corresponding to VPLMN.

Case 3, provider#B is ECSP ID. In this case, EAS corresponding to provider #b indicates EAS corresponding to ECSP.

916, the easdf returns information of EAS corresponding to provider #b to the UE.

Through the steps, the UE can obtain the information of the EAS corresponding to the provider#B.

It is to be appreciated that the method 900 may be used for HR roaming (e.g., the session of the UE in step 906 is an HR session) or LBO roaming (e.g., the session of the UE in step 906 is an LBO session), and in different roaming modes, adaptation may be performed according to the roaming modes, which is not limited.

Scenario 1, the session of the ue is an LBO session.

In this scenario, it is assumed that the UE roams from provider #B to PLMN #A by LBO, where PLMN #A may be regarded as the VPLMN of the UE and provider #B may be regarded as the HPLMN of the UE. After the UE roams from provider#b to plmn#a by LBO, the UE may access the MEC service through the UPF (i.e., V-UPF) corresponding to plmn#a, and the SMF (i.e., V-SMF) in plmn#a configures DNS processing rules for the UE. When the SMF in PLMN #a (i.e., V-SMF) configures DNS processing rules for the UE, the following may be used: the access network of the UE is plmn#a (i.e. VPLMN), the PLMN providing the edge computing service for the UE is provider#b (i.e. HPLMN), corresponding EAS deployment information is searched, and thus a C-DNS server #b corresponding to provider#b (i.e. HPLMN) in plmn#a (i.e. VPLMN) can be found, and thus EAS corresponding to provider#b (i.e. HPLMN) in plmn#a (i.e. VPLMN) can be found for the UE.

Scenario 2, session of ue is HR session.

In this scenario, it is assumed that the UE roams from provider #b to PLMN #a in HR, where PLMN #a may be regarded as VPLMN of the UE and provider #b may be regarded as HPLMN of the UE. After the UE roams from provider #b to PLMN #a in HR, SMF (i.e., H-SMF) in provider #b configures DNS processing rules for the UE. When the SMF in provider #b (i.e., H-SMF) configures DNS processing rules for the UE, the following may be used: the access network of the UE is plmn#a (i.e. VPLMN), the PLMN providing the edge computing service for the UE is provider#b (i.e. HPLMN), corresponding EAS deployment information is searched, and thus a C-DNS server #b corresponding to provider#b (i.e. HPLMN) in plmn#a (i.e. VPLMN) can be found, and thus EAS corresponding to provider#b (i.e. HPLMN) in plmn#a (i.e. VPLMN) can be found for the UE.

It will be appreciated that the two scenarios described above are simple exemplary illustrations, and embodiments of the present application are not limited thereto. For example, in both of the above scenarios, the SMF (e.g., V-SMF in scenario 1, and H-SMF in scenario 2) may be based on: the home network of the UE, the subscription information of the UE, and the UE list provided by provider #b include any one of the protocols between the UE or provider #b and PLMN #a to determine provider #b, so as to obtain EAS deployment information corresponding to the provider #b. For another example, in the above two scenarios, the SMF (e.g. V-SMF in scenario 1 and H-SMF in scenario 2) may also determine provider #b according to any one of the home network of the UE, subscription information of the UE or UE, a protocol between provider #b and PLMN #a included in the UE list provided by provider #b, and combine with PLMN #a to obtain EAS deployment information corresponding to the provider #b. Specific reference may be made to the description of method 500, which is not repeated here.

Based on the method 900, the EAS deployment information provided by the af may include C-DNS servers corresponding to different PLMNs or different ECSPs in PLMN #a, and the EAS corresponding to the corresponding PLMN or ECSP in PLMN #a may be registered on the C-DNS servers. When configuring a DNS processing rule for the EASDF in the session establishment procedure, the SMF may carry information of the C-DNS server corresponding to provider #b in the DNS processing rule, so that the EASDF may send the DNS query of the UE to the C-DNS server for processing. Thus, if provider#b is HPLMN ID, UE may be enabled to preferentially use EAS corresponding to HPLMN in plmn#a; if provider#b is VPLMN ID, the UE may be enabled to preferentially use EAS corresponding to VPLMN in plmn#a; if provider#b is ECSP ID, the UE may be caused to preferentially use EAS corresponding to ECSP in plmn#a.

Fig. 10 is a schematic flow chart diagram of a method 1000 of communication provided by an embodiment of the present application. The method 1000 may be used to implement a scheme such as method 500 (e.g., example 2 in method 500), for example, the method 1000 may be used for PLMN # A, provider #b, and ECS option with associated scenarios. As an example, method 1000 may be implemented by the architecture shown in fig. 6. The method 1000 may include the following steps.

1001, the af sends EAS deployment information to the NEF.

Step 1001 is similar to step 901, except that in step 1001, the EAS deployment information includes a provider #b ID and an ECS option #b, where EAS corresponding to the ECS option #b is EAS corresponding to the provider #b in the PLMN #a. It will be appreciated that ECS option#b is a name given for distinction, and the name does not limit the scope of the embodiments of the present application. Optionally, the EAS deployment information further includes a PLMN #a ID.

1002, the NEF processes the EAS deployment information.

1003, the NEF sends the EAS deployment information to the UDR.

1004, the udr sends a store response to the NEF.

1005, the NEF sends an EAS deployment information response to the AF.

At 1006, the ue initiates a session establishment procedure.

1007, the smf requests EAS deployment information from the NEF.

1008, the nef obtains EAS deployment information from the UDR.

1009, the nef sends EAS deployment information to the SMF.

At 1010, the SMF selects EASDF.

Steps 1002 to 1010 are similar to steps 902 to 910, and are not described herein.

1011, the smf configures DNS processing rules for the EASDF according to the EAS deployment information, the DNS processing rules including ECS option #b.

The SMF may configure DNS processing rules for the selected EASDF according to the EAS deployment information corresponding to provider #b. As an example, step 1011 includes: the SMF generates DNS processing rules according to the EAS deployment information and sends the DNS processing rules to the EASDF. For example, the SMF sends a neosdf_context_create_create_request to the EASDF, the neosdf_context_create_request including DNS processing rules; the easdf_context_create response is returned by EASDF to the SMF.

As an example, DNS processing rules may include one or more of the following information: FQDN range, ECS option # B, L-DNS server address, DNS forwarding rules. Regarding the meaning of each information, reference may be made to the description in step 911, and the ECS option #b is mainly described herein.

Wherein, the EAS corresponding to ECS option#b is the EAS corresponding to provider#b in plmn#a.

1012, the ue sends a DNS query to the EASDF.

Step 1012 is similar to step 912 and will not be described again here.

1013, the EASDF processes the DNS query according to the DNS processing rules.

After the EASDF receives the DNS query, the DNS query may be processed according to DNS processing rules received from the SMF. The EASDF processes DNS queries according to DNS processing rules, which may include: EASDF adds ECS option#B in DNS query. EAS provided by provider #b can be queried by adding the ECS option #b to DNS query.

For example, if the EASDF detects according to the DNS processing rule that the FQDN included in the DNS query of the UE may be matched with the FQDN included in the DNS processing rule, the EASDF sends the DNS query after adding the ECS option #b to the DNS query to the C-DNS server according to the DNS processing rule.

1014, the EASDF sends a DNS query containing ECS option #B to the C-DNS server.

1015, the C-DNS server returns a DNS response to the EASDF.

1016, the easdf returns information of the EAS corresponding to provider #b to the UE.

It is appreciated that the method 1000 may be used for HR roaming (e.g., the session of the UE in step 1006 is an HR session) or LBO roaming (e.g., the session of the UE in step 1006 is an LBO session), and in different roaming modes, the adaptation may be performed according to the roaming modes, which is not limited.

Scenario 1, the session of the ue is an LBO session.

In this scenario, it is assumed that the UE roams from provider #B to PLMN #A by LBO, where PLMN #A may be regarded as the VPLMN of the UE and provider #B may be regarded as the HPLMN of the UE. After the UE roams from provider #b to PLMN #a through LBO, the UE may access the MEC service through the UPF (i.e., V-UPF) corresponding to PLMN #a. When the SMF in PLMN #a (i.e., V-SMF) configures DNS processing rules for the UE, the following may be used: the access network of the UE is plmn#a (i.e. VPLMN), the PLMN providing the edge computing service for the UE is provider#b (i.e. HPLMN), corresponding EAS deployment information is searched, and thus ECS option#b corresponding to provider#b (i.e. HPLMN) in plmn#a (i.e. VPLMN) can be found, and thus EAS corresponding to provider#b (i.e. HPLMN) in plmn#a (i.e. VPLMN) can be found for the UE.

Scenario 2, session of ue is HR session.

In this scenario, it is assumed that the UE roams from provider #b to PLMN #a in HR, where PLMN #a may be regarded as VPLMN of the UE and provider #b may be regarded as HPLMN of the UE. After the UE roams from provider #b to PLMN #a in HR, the UE may access MEC service through UPF (i.e., H-UPF) corresponding to provider #b. When the SMF in provider #b (i.e., H-SMF) configures DNS processing rules for the UE, the following may be used: the access network of the UE is plmn#a (i.e. VPLMN), the PLMN providing the edge computing service for the UE is provider#b (i.e. HPLMN), corresponding EAS deployment information is searched, and thus ECS option#b corresponding to provider#b (i.e. HPLMN) in plmn#a (i.e. VPLMN) can be found, and thus EAS corresponding to provider#b (i.e. HPLMN) in plmn#a (i.e. VPLMN) can be found for the UE.

Based on the above method 1000, the EAS deployment information provided by the af may include ECS options corresponding to different PLMNs or different ECSPs in PLMN #a. When configuring a DNS processing rule for the EASDF in the session establishment procedure, the SMF may carry information of the ECS option corresponding to provider #b in the DNS processing rule, so that the EASDF may add the ECS option in the DNS query of the UE. Thus, if provider#b is HPLMN ID, UE may be enabled to preferentially use EAS corresponding to HPLMN in plmn#a; if provider#b is VPLMN ID, the UE may be enabled to preferentially use EAS corresponding to VPLMN in plmn#a; if provider#b is ECSP ID, the UE may be caused to preferentially use EAS corresponding to ECSP in plmn#a.

Fig. 11 is a schematic flow chart diagram of a method 1100 of communication provided by an embodiment of the application. The method 1100 may be used to implement a scheme such as method 500 (e.g., example 3 in method 500), e.g., the method 1100 may be used for PLMN # A, provider #b, and L-DNS servers have associated scenarios. As an example, the method 1100 may be implemented by the architecture shown in fig. 7. The method 1100 may include the following steps.

1101, the AF sends the EAS deployment information to the NEF.

Step 1101 is similar to step 901, except that in step 1101, the EAS deployment information includes provider #b ID and L-DNS server #b, where EAS registered on L-DNS server #b is EAS corresponding to provider #b in PLMN #a. It will be appreciated that the L-DNS server #b is a name for distinction, and the name does not limit the scope of protection of the embodiment of the present application. Optionally, the EAS deployment information further includes a PLMN #a ID.

1102, the NEF processes the EAS deployment information.

1103, the NEF sends the EAS deployment information to the UDR.

1104, the udr sends a store response to the NEF.

1105, the nef sends an EAS deployment information response to the AF.

1106, the ue initiates a session establishment procedure.

1107, the smf requests EAS deployment information from the NEF.

1108, the nef obtains EAS deployment information from the UDR.

1109, the nef sends EAS deployment information to the SMF.

1110, the smf selects EASDF.

Steps 1102-1110 are similar to steps 902-910, and are not repeated here.

1111, the smf configures DNS handling rules for the EASDF according to the EAS deployment information, the DNS handling rules including L-DNS server #b.

The SMF may configure DNS processing rules for the selected EASDF according to the EAS deployment information corresponding to provider #b. As an example, step 1111 includes: the SMF generates DNS processing rules according to the EAS deployment information and sends the DNS processing rules to the EASDF. For example, the SMF sends a neosdf_context_create_create_request to the EASDF, the neosdf_context_create_request including DNS processing rules; the easdf_context_create response is returned by EASDF to the SMF.

As an example, DNS processing rules may include one or more of the following information: FQDN range, ECS option, L-DNS server #b address, DNS forwarding rules. Regarding the meaning of each information, reference may be made to the description in step 911, and the description of the L-DNS server #b is mainly described herein.

The EAS registered on the L-DNS server #b is EAS corresponding to the provider #b in the PLMN #a.

1112, the UE sends a DNS query to the EASDF.

Step 1112 is similar to step 912 and will not be described again here.

1113, the easdf processes DNS queries according to DNS processing rules.

After the EASDF receives the DNS query, the DNS query may be processed according to DNS processing rules received from the SMF. The EASDF processes DNS queries according to DNS processing rules, which may include: the EASDF sends the UE's DNS query to the processing rules including L-DNS server #b.

For example, if the EASDF detects according to the DNS processing rule that the FQDN included in the DNS query of the UE may match the FQDN included in the DNS processing rule, the EASDF determines the address of the L-DNS server #b according to the DNS processing rule, and sends the DNS query of the UE to the L-DNS server #b.

1114, the easdf sends a DNS query to L-DNS server #b.

1115, l-DNS server #b returns DNS response to EASDF.

The L-DNS server may send a DNS response to the EASDF, which may contain information (e.g., an EAS IP address) of the EAS corresponding to provider #B. The description is made in connection with three cases.

1116, the easdf returns information of the EAS corresponding to provider #b to the UE.

It is to be appreciated that the method 1100 may be used for HR roaming (e.g., the session of the UE in step 1106 is an HR session) or LBO roaming (e.g., the session of the UE in step 1106 is an LBO session), and in different roaming modes, adaptation may be performed according to the roaming modes, which is not limited.

Scenario 1, the session of the ue is an LBO session.

In this scenario, it is assumed that the UE roams from provider #B to PLMN #A by LBO, where PLMN #A may be regarded as the VPLMN of the UE and provider #B may be regarded as the HPLMN of the UE. After the UE roams from provider #b to PLMN #a through LBO, the UE may access the MEC service through the UPF (i.e., V-UPF) corresponding to PLMN #a. When the SMF in PLMN #a (i.e., V-SMF) configures DNS processing rules for the UE, the following may be used: the access network of the UE is plmn#a (i.e. VPLMN), the PLMN providing the edge computing service for the UE is provider#b (i.e. HPLMN), corresponding EAS deployment information is searched, and thus, an L-DNS server #b corresponding to provider#b (i.e. HPLMN) in plmn#a (i.e. VPLMN) can be found, and thus, EAS corresponding to provider#b (i.e. HPLMN) in plmn#a (i.e. VPLMN) can be found for the UE.

Scenario 2, session of ue is HR session.

In this scenario, it is assumed that the UE roams from provider #b to PLMN #a in HR, where PLMN #a may be regarded as VPLMN of the UE and provider #b may be regarded as HPLMN of the UE. After the UE roams from provider #b to PLMN #a in HR, the UE may access MEC service through UPF (i.e., H-UPF) corresponding to provider #b. When the SMF in provider #b (i.e., H-SMF) configures DNS processing rules for the UE, the following may be used: the access network of the UE is plmn#a (i.e. VPLMN), the PLMN providing the edge computing service for the UE is provider#b (i.e. HPLMN), corresponding EAS deployment information is searched, and thus, an L-DNS server #b corresponding to provider#b (i.e. HPLMN) in plmn#a (i.e. VPLMN) can be found, and thus, EAS corresponding to provider#b (i.e. HPLMN) in plmn#a (i.e. VPLMN) can be found for the UE.

Based on the above method 1100, the EAS deployment information provided by the af may include L-DNS servers corresponding to different PLMNs or different ECSPs in the PLMN #a, and EAS corresponding to the corresponding PLMN or ECSP may be registered on the L-DNS servers. When configuring a DNS processing rule for the EASDF in the session establishment procedure, the SMF may carry information of the L-DNS server corresponding to provider#b in the DNS processing rule, so that the EASDF may send a DNS query of the UE to the L-DNS server for processing. Thus, if provider#b is HPLMN ID, UE may be enabled to preferentially use EAS corresponding to HPLMN in plmn#a; if provider#b is VPLMN ID, the UE may be enabled to preferentially use EAS corresponding to VPLMN in plmn#a; if provider#b is ECSP ID, the UE may be caused to preferentially use EAS corresponding to ECSP in plmn#a.

Fig. 12 is a schematic flow chart diagram of a method 1200 of communication provided by an embodiment of the present application. The method 1200 may be used to implement a scheme such as method 500 (e.g., example 4 in method 500), for example, the method 1200 may be used in scenarios where PLMN # A, provider #b, and EAS IP addresses have an association. As an example, the method 1200 may be implemented by the architecture shown in fig. 8. The method 1200 may include the following steps.

1201, the af sends EAS deployment information to the NEF.

Step 1201 is similar to step 901, except that in step 1201, the EAS deployment information includes a provider #b ID and an EAS address #b, where the EAS address #b is an address (e.g., EAS IP address) of the EAS corresponding to the provider #b in the PLMN #a. It will be appreciated that EAS address #b is a name given for distinction, and the naming thereof does not limit the scope of the embodiments of the present application. Optionally, the EAS deployment information further includes a PLMN #a ID.

1202, NEF processes the EAS deployment information.

1203, the NEF sends the EAS deployment information to the UDR.

1204, udr sends a store response to NEF.

1205, the nef sends an EAS deployment information response to the AF.

The ue initiates a session establishment procedure 1206.

1207, the smf requests EAS deployment information from the NEF.

1208, the nef obtains EAS deployment information from the UDR.

1209, the nef sends EAS deployment information to the SMF.

1210, SMF selects EASDF.

Steps 1202-1210 are similar to steps 902-910 and are not repeated here.

1211, the smf configures DNS processing rules for the EASDF according to the EAS deployment information, the DNS processing rules including EAS address #b.

The SMF may configure DNS processing rules for the selected EASDF according to the EAS deployment information corresponding to provider #b. As an example, step 1211 includes: the SMF generates DNS processing rules according to the EAS deployment information and sends the DNS processing rules to the EASDF. For example, the SMF sends a neosdf_context_create_create_request to the EASDF, the neosdf_context_create_request including DNS processing rules; the easdf_context_create response is returned by EASDF to the SMF.

As an example, DNS processing rules may include one or more of the following information: FQDN range, ECS option, L-DNS server address, EAS address # B, DNS forwarding rules. Regarding the meaning of each information, reference may be made to the description in step 911, and EAS address #b is mainly described herein.

Wherein, EAS address #b is the address (e.g., EAS IP address) of EAS corresponding to provider #b in PLMN #a.

The ue sends 1212 a DNS query to the EASDF.

Step 1212 is similar to step 912 and will not be described again.

1213, the easdf processes DNS queries according to DNS processing rules.

After the EASDF receives the DNS query, the DNS query may be processed according to DNS processing rules received from the SMF. The EASDF processes DNS queries according to DNS processing rules, which may include the following two processing manners.

Treatment mode 1: if the EASDF detects that the domain name (such as FQDN) contained in the DNS query of the UE can be matched with the domain name contained in the DNS processing rule according to the DNS processing rule, the EASDF sends the DNS query added with the ECS option to the C-DNS server after the ECS option is added in the DNS query according to the DNS processing rule.

Treatment mode 2: if the EASDF detects that the domain name (such as FQDN) contained in the DNS query of the UE can be matched with the domain name contained in the DNS processing rule according to the DNS processing rule, the EASDF determines the address of the L-DNS server according to the DNS processing rule and sends the DNS query of the UE to the L-DNS server.

1214, the easdf queries the DNS server for N EAS IP addresses.

Wherein, the N EAS IP addresses may include at least one of: the EAS IP address corresponding to the HPLMN of the UE, the EAS IP address corresponding to the VPLMN of the UE, and the EAS IP address corresponding to a third party ECSP (e.g., ECSP subscribed to by the UE).

Wherein, the DNS server comprises at least one of the following: the EAS IP address corresponding to the HPLMN of the UE, the EAS IP address corresponding to the VPLMN of the UE, and the EAS IP address corresponding to a third party ECSP (e.g., ECSP subscribed to by the UE), and further the N EAS IP addresses may be provided to the EASDF. The DNS server may be an L-DNS server or a C-DNS server. The following description will be made in connection with the two processing manners in the above-described step 1213.

For example, consider processing mode 1 in step 1213, in which case it is assumed that the C-DNS server includes the N EAS IP addresses described above. After receiving the DNS request containing the ECS option from the EASDF, the C-DNS server sends a DNS response to the EASDF, where the DNS response contains N EAS IP addresses, and the EASDF obtains the N EAS IP addresses.

As another example, consider processing mode 2 in step 1213, in which case it is assumed that the L-DNS server includes the N EAS IP addresses described above. After receiving the DNS query from the EASDF, the L-DNS server sends a DNS response to the EASDF, where the DNS response includes N EAS IP addresses, and the EASDF obtains the N EAS IP addresses.

1215, the easdf selects M EAS IP addresses from the N EAS IP addresses according to EAS address #b.

Wherein M is an integer greater than or equal to 1, and M is less than or equal to N.

The EASDF selects M EAS IP addresses from the N EAS IP addresses according to EAS address #b, including: the EASDF is based on selecting (or filtering) the EAS IP address belonging to the EAS address #b (i.e., M EAS IP addresses) from the N EAS IP addresses. In other words, the M EAS IP addresses are the intersection of N EAS IP addresses and EAS address #B.

1216, the easdf returns information of the EAS corresponding to provider #b to the UE.

After selecting M EAS IP addresses from the N EAS IP addresses according to EAS address #b, the EASDF may return the M EAS IP addresses (i.e., information of EAS corresponding to provider #b) to the UE.

It is to be appreciated that the method 1200 may be used for HR roaming (e.g., the session of the UE in step 1206 is an HR session) or LBO roaming (e.g., the session of the UE in step 1206 is an LBO session), and in different roaming modes, adaptation may be performed according to the roaming modes, which is not limited.

Scenario 1, the session of the ue is an LBO session.

In this scenario, it is assumed that the UE roams from provider #B to PLMN #A by LBO, where PLMN #A may be regarded as the VPLMN of the UE and provider #B may be regarded as the HPLMN of the UE. After the UE roams from provider #b to PLMN #a through LBO, the UE may access the MEC service through the UPF (i.e., V-UPF) corresponding to PLMN #a. When the SMF in PLMN #a (i.e., V-SMF) configures DNS processing rules for the UE, the following may be used: the access network of the UE is plmn#a (i.e. VPLMN), the PLMN providing the edge computing service for the UE is provider#b (i.e. HPLMN), and corresponding EAS deployment information is searched for, so that an EAS address #b corresponding to provider#b (i.e. HPLMN) in plmn#a (i.e. VPLMN) can be found, and further, EAS corresponding to provider#b (i.e. HPLMN) in plmn#a (i.e. VPLMN) can be found for the UE.

Scenario 2, session of ue is HR session.

In this scenario, it is assumed that the UE roams from provider #b to PLMN #a in HR, where PLMN #a may be regarded as VPLMN of the UE and provider #b may be regarded as HPLMN of the UE. After the UE roams from provider #b to PLMN #a in HR, the UE may access MEC service through UPF (i.e., H-UPF) corresponding to provider #b. When the SMF in provider #b (i.e., H-SMF) configures DNS processing rules for the UE, the following may be used: the access network of the UE is plmn#a (i.e. VPLMN), the PLMN providing the edge computing service for the UE is provider#b (i.e. HPLMN), and corresponding EAS deployment information is searched for, so that an EAS address #b corresponding to provider#b (i.e. HPLMN) in plmn#a (i.e. VPLMN) can be found, and further, EAS corresponding to provider#b (i.e. HPLMN) in plmn#a (i.e. VPLMN) can be found for the UE.

Based on the method 1200, the EAS deployment information provided by the af may include EAS IP addresses corresponding to different PLMNs or different ECSPs in PLMN #a. When configuring a DNS processing rule for the EASDF in the session establishment procedure, the SMF may carry the EAS address corresponding to provider #b in the DNS processing rule, so that the EASDF may filter (or select) the EAS address corresponding to provider #b in the DNS response. Thus, if provider#b is HPLMN ID, UE may be enabled to preferentially use EAS corresponding to HPLMN in plmn#a; if provider#b is VPLMN ID, the UE may be enabled to preferentially use EAS corresponding to VPLMN in plmn#a; if provider#b is ECSP ID, the UE may be caused to preferentially use EAS corresponding to ECSP in plmn#a.

The applications of the respective examples are described above separately, and it is understood that examples 1 to 4 may be used alone or in combination. The following is an exemplary description taking the use of example 1 and example 2 in combination as an example.

Fig. 13 is a schematic flow chart diagram of a method 1300 of communication provided by an embodiment of the present application. The method 1300 may be used to implement a scheme such as method 500 (e.g., example 5 in method 500), for example, the method 1300 may be used for PLMN # A, provider # B, C-DNS servers, and ECS option with associated scenarios. As an example, the method 1300 may be implemented by the architecture shown in fig. 6. The method 1300 may include the following steps.

1301, the af sends EAS deployment information to the NEF.

Step 1301 is similar to step 901, except that in step 1301, the EAS deployment information includes provider #b ID, C-DNS server #b, and ECS option #b. Optionally, the EAS deployment information further includes a PLMN #a ID. In the following, a provider#b is taken as an example of a PLMN, and several possible cases are described.

For example, one PLMN corresponds to one C-DNS server #b, and the PLMN corresponds to a set of mapping relationships between DNAI and ECS option. For example, a dedicated C-DNS server #b may be configured for a PLMN, and a set of mapping relationships between dedicated DNAI and ECS options may be configured for the PLMN.

For another example, one PLMN corresponds to one C-DNS server #b, and all PLMNs correspond to the same set of mapping relationships of DNAI and ECS option. For example, a dedicated C-DNS server #b may be configured for one PLMN, and the same mapping relationship between DNAI and ECS option may be configured for all PLMNs.

For another example, all PLMNs correspond to one C-DNS server #B, and each PLMN corresponds to a set of mapping relationships of DNAI and ECS option. For example, the same C-DNS server #b may be configured for all PLMNs, and each PLMN corresponds to a set of mapping relationships between dedicated DNAI and ECS option.

It will be appreciated that the foregoing is illustrative and that any variations, which fall within the above-described examples, are suitable for use with embodiments of the present application.

It will also be appreciated that provider #B is ECSP similarly, and will not be described here again.

1303, NEF processes the EAS deployment information.

1303, NEF sends EAS deployment information to UDR.

1304, the udr sends a store response to the NEF.

1305, the nef sends an EAS deployment information response to the AF.

1306, the UE initiates a session establishment procedure.

1307, the smf requests EAS deployment information from the NEF.

1308, the NEF obtains the EAS deployment information from the UDR.

1309, the nef sends EAS deployment information to the SMF.

1310, SMF selects EASDF.

Steps 1303 to 1310 are similar to steps 902 to 910, and are not described herein.

1311, the smf configures DNS processing rules for the EASDF according to the EAS deployment information, the DNS processing rules including ECS option #b and C-DNS server #b.

The SMF may configure DNS processing rules for the selected EASDF according to the EAS deployment information corresponding to provider #b. As an example, step 1311 includes: the SMF generates DNS processing rules according to the EAS deployment information and sends the DNS processing rules to the EASDF. For example, the SMF sends a neosdf_context_create_create_request to the EASDF, the neosdf_context_create_request including DNS processing rules; the easdf_context_create response is returned by EASDF to the SMF.

As an example, DNS processing rules may include one or more of the following information: FQDN range, ECS option # B, C-DNS server #b address, DNS forwarding rules. For each piece of information, reference may be made to the descriptions in step 911 and step 211, and a detailed description is omitted here.

The ECS option #b and the C-DNS server #b address may be included in the DNS processing rule determined by the SMF, so that the EASDF may add the ECS option #b to the DNS query of the UE according to the DNS processing rule, and send the DNS query containing the ECS option #b to the C-DNS server #b address. Thus, selection of a particular EAS (i.e., EAS corresponding to provider #b) for the UE may be implemented.

1312, the ue sends a DNS query to the EASDF.

Step 1312 is similar to step 912 and will not be described again here.

1313, processing the DNS query by the easdf according to DNS processing rules.

After the EASDF receives the DNS query, the DNS query may be processed according to DNS processing rules received from the SMF. The EASDF processes DNS queries according to DNS processing rules, which may include: the EASDF adds ECS option #b in the DNS query and sends the DNS query containing ECS option #b to the C-DNS server #b.

For example, if the EASDF detects according to the DNS processing rule that the FQDN included in the DNS query of the UE may be matched with the FQDN included in the DNS processing rule, the EASDF sends the DNS query with the ECS option #b added to the C-DNS server #b after adding the ECS option #b to the DNS query according to the DNS processing rule.

1314, the EASDF sends a DNS query containing ECS option #B to C-DNS server #B.

1315, C-DNS Server #B returns a DNS response to the EASDF.

The C-DNS server #B may send a DNS response to the EASDF, where the DNS response may contain information (e.g., an EAS IP address) of the EAS corresponding to provider #B. The description is made in connection with three cases.

1316, the easdf returns information of EAS corresponding to provider #b to the UE.

It is to be appreciated that the method 1300 may be used for HR roaming (e.g., the session of the UE in step 1306 is an HR session) or LBO roaming (e.g., the session of the UE in step 1306 is an LBO session), and in different roaming modes, adaptation may be performed according to the roaming modes, which is not limited.

Scenario 1, the session of the ue is an LBO session.

In this scenario, it is assumed that the UE roams from provider #B to PLMN #A by LBO, where PLMN #A may be regarded as the VPLMN of the UE and provider #B may be regarded as the HPLMN of the UE. After the UE roams from provider #b to PLMN #a through LBO, the UE may access the MEC service through the UPF (i.e., V-UPF) corresponding to PLMN #a. When the SMF in PLMN #a (i.e., V-SMF) configures DNS processing rules for the UE, the following may be used: the access network of the UE is plmn#a (i.e. VPLMN), the PLMN providing the edge computing service for the UE is provider#b (i.e. HPLMN), corresponding EAS deployment information is searched, and thus, a C-DNS server #b and ECS option #b corresponding to provider#b (i.e. HPLMN) in plmn#a (i.e. VPLMN) can be found, and thus, EAS corresponding to provider#b (i.e. HPLMN) in plmn#a (i.e. VPLMN) can be searched for the UE.

Scenario 2, session of ue is HR session.

In this scenario, it is assumed that the UE roams from provider #b to PLMN #a in HR, where PLMN #a may be regarded as VPLMN of the UE and provider #b may be regarded as HPLMN of the UE. After the UE roams from provider #b to PLMN #a in HR, the UE may access MEC service through UPF (i.e., H-UPF) corresponding to provider #b. When the SMF in provider #b (i.e., H-SMF) configures DNS processing rules for the UE, the following may be used: the access network of the UE is plmn#a (i.e. VPLMN), the PLMN providing the edge computing service for the UE is provider#b (i.e. HPLMN), corresponding EAS deployment information is searched, and thus, a C-DNS server #b and ECS option #b corresponding to provider#b (i.e. HPLMN) in plmn#a (i.e. VPLMN) can be found, and thus, EAS corresponding to provider#b (i.e. HPLMN) in plmn#a (i.e. VPLMN) can be searched for the UE.

Based on the method 1300 described above, the EAS deployment information provided by the af may include: a C-DNS server corresponding to a different PLMN or a different ECSP in PLMN#A, and an ECS option corresponding to a different PLMN or a different ECSP in PLMN#A. When the SMF configures a DNS processing rule for the EASDF in the session establishment procedure, the DNS processing rule may carry a C-DNS server and an ECS option corresponding to provider #b, so that the EASDF may send a DNS query to which the ECS option is added to the C-DNS server for processing. Thus, if provider#b is HPLMN ID, UE may be enabled to preferentially use EAS corresponding to HPLMN in plmn#a; if provider#b is VPLMN ID, the UE may be enabled to preferentially use EAS corresponding to VPLMN in plmn#a; if provider#b is ECSP ID, the UE may be caused to preferentially use EAS corresponding to ECSP in plmn#a.

It will be appreciated that the examples of fig. 9 to 13 in the embodiments of the present application are merely for facilitating understanding of the embodiments of the present application by those skilled in the art, and are not intended to limit the embodiments of the present application to the specific scenarios illustrated. It will be apparent to those skilled in the art from the examples of fig. 9-13 that various equivalent modifications or variations can be made, and such modifications or variations are intended to be within the scope of the embodiments of the present application. For example, the session establishment procedure in fig. 9 to 13 described above may be replaced with a session modification procedure.

It should also be understood that, in some embodiments described above, the message names, such as nsmf_pdustion_update Request message, nsmf_pdustion_create Request, query message, etc., are only examples, and do not limit the protection scope of the embodiments of the present application. For example, the query message may be replaced with the request message.

It will also be appreciated that in some of the above embodiments, the SMF is mainly exemplified by querying corresponding EAS deployment information according to provider #b (or PLMN #a and provider #b), which is not limited. For example, when the SMF requests EAS deployment information from the NEF, the NEF may carry provider #b (or PLMN #a and provider #b), and further send the deployment information of EAS corresponding to the provider #b in PLMN #a to the SMF.

It is further understood that in embodiments of the present application, SMF may be based on: the home network of the UE, the subscription information of the UE or the UE, and any one of protocols between the provider#B and the PLMN#A are included in a UE list provided by the provider#B to determine the provider#B, so as to acquire the EAS deployment information corresponding to the provider#B; or determining provider#b according to any one of a home network of the UE, subscription information of the UE or the UE, and a protocol between the provider#b and the plmn#a included in a UE list provided by the provider#b, and combining with the plmn#a to further obtain EAS deployment information corresponding to the provider#b. This is not limited.

It will also be appreciated that in some of the above embodiments, the SMF is mainly exemplified by determining DNS processing rules according to EAS deployment information corresponding to a provider, which is not limited. For example, the SMF may determine DNS processing rules according to existing means and send to the EASDF; the EASDF may process DNS query requests of the UE according to the DNS processing rule and EAS deployment information corresponding to the provider.

It will also be appreciated that in some of the embodiments described above, the message is sent multiple times. Taking the example of sending the message from a to B, the message from a to B may include sending the message from a directly to B, or may include sending the message from a to B through other devices or network elements, which is not limited.

It will also be appreciated that in some of the embodiments described above, reference is made to EAS IP or FQDN, which may be replaced by EAS IP range (EAS IP range), and FQDN may be replaced by FQDN range.

It will also be appreciated that in some of the above embodiments, ECSPs subscribed to by the UE are exemplified, and this is not limiting. For example, ECSPs subscribed to by the UE may also be replaced with corresponding all or part of the third party ECSPs in the VPLMN.

It will also be appreciated that in some of the embodiments described above, various network elements (e.g., SMF, AMF, NEF, etc.) are illustrated primarily by way of example in a 5G system. The application does not exclude the possibility of using other designations in 6G networks as well as other networks in the future. For example, in a 6G network, some or all of the individual network elements may follow the terminology in 5G, possibly by other names, etc.

It will also be appreciated that some optional features of the various embodiments of the application may, in some circumstances, be independent of other features or may, in some circumstances, be combined with other features, without limitation.

It is also to be understood that the aspects of the embodiments of the application may be used in any reasonable combination, and that the explanation or illustration of the various terms presented in the embodiments may be referred to or explained in the various embodiments without limitation.

It should be further understood that the magnitude of the various numerical numbers in the embodiments of the present application does not mean the order of execution, but merely serves to distinguish between the convenience of description and the implementation of the embodiments of the present application, and should not constitute any limitation.

It is also to be understood that in the foregoing embodiments of the method and operations performed by the apparatus may also be performed by component parts (e.g., chips or circuits) of the apparatus.

Corresponding to the methods given by the above method embodiments, the embodiments of the present application also provide corresponding apparatuses, where the apparatuses include corresponding modules for executing the above method embodiments. The module may be software, hardware, or a combination of software and hardware. It will be appreciated that the technical features described in the method embodiments described above are equally applicable to the device embodiments described below.

Fig. 14 is a schematic diagram of a communication apparatus 1400 provided in an embodiment of the application. The apparatus 1400 includes a transceiver unit 1410 and a processing unit 1420. The transceiving unit 1410 may be used to implement a corresponding communication function. The transceiver unit 1410 may also be referred to as a communication interface or a communication unit. Processing unit 1420 may be configured to implement corresponding processing functions, such as determining DNS processing rules.

Optionally, the apparatus 1400 further includes a storage unit, where the storage unit may be configured to store instructions and/or data, and the processing unit 1420 may read the instructions and/or data in the storage unit, so that the apparatus implements the actions of the device or network element in the foregoing method embodiments.

In a first design, the apparatus 1400 may be a session management network element (e.g., SMF) in the foregoing embodiment, or may be a component (e.g., a chip) of the session management network element. The apparatus 1400 may implement steps or procedures performed by a session management network element in the above method embodiment, where the transceiving unit 1410 may be configured to perform transceiving related operations of the session management network element in the above method embodiment, and the processing unit 1420 may be configured to perform processing related operations of the session management network element in the above method embodiment.

A possible implementation manner, the processing unit 1420 is configured to obtain provider information, where a provider is a provider that provides an edge computing service for a terminal device; a processing unit 1420, configured to configure a DNS processing rule for a domain name service according to provider information and EAS deployment information of an edge application server corresponding to the provider, where the DNS processing rule is used to process a DNS message of the terminal device, and the EAS deployment information is EAS deployment information corresponding to the provider in an access network of the terminal device; a transceiving unit 1410, configured to send DNS processing rules to the edge application server discovery network element.

Optionally, a processing unit 1420, configured to obtain EAS deployment information according to provider information; or acquiring the EAS deployment information according to the provider information and the access network information.

Illustratively, the EAS deployment information includes any of the following: DNS server, ECS option, provider address of corresponding EAS in access network; wherein, the EAS registered on the DNS server is the EAS corresponding to the provider in the access network, and the EAS corresponding to the ECS option is the EAS corresponding to the provider in the access network.

Illustratively, the DNS server is a server deployed in the home network, or the DNS server is a server deployed in the access network.

Illustratively, the DNS handling rules include any of the following: DNS server, ECS option, address of the corresponding EAS in the access network for the provider.

Optionally, the processing unit 1420 is configured to perform any one of the following: determining provider information according to a home network of the terminal equipment; determining provider information according to the subscription information of the terminal equipment, wherein the subscription information of the terminal equipment comprises the information of the provider; determining provider information according to terminal equipment included in a terminal equipment list provided by a provider; alternatively, the provider information is determined according to an agreement between the provider and the access network.

Illustratively, the access network is a visited network of the terminal device and the provider is a home network of the terminal device.

Illustratively, the provider is any one of: the provider of EAS, the provider of edge hosting environment EHE, or the provider of edge data network EDN.

In a second design, the apparatus 1400 may be an edge application server discovery network element (e.g., EASDF) in the foregoing embodiment, or may be a component (e.g., a chip) of the edge application server discovery network element. The apparatus 1400 may implement steps or processes performed by the edge application server discovery network element in the above method embodiment, where the transceiving unit 1410 may be configured to perform transceiving related operations of the edge application server discovery network element in the above method embodiment, and the processing unit 1420 may be configured to perform processing related operations of the edge application server discovery network element in the above method embodiment.

A possible implementation manner, the transceiver unit 1410 is configured to receive a domain name service DNS query message from a terminal device; a processing unit 1420, configured to process the DNS query message according to a DNS processing rule; the DNS processing rule is determined according to EAS deployment information of an edge application server corresponding to a provider for providing edge computing service for the terminal equipment, wherein the EAS deployment information is EAS deployment information of the provider in an access network of the terminal equipment.

Illustratively, the EAS deployment information is determined from the provider information; alternatively, the EAS deployment information is determined based on the provider information and the access network information.

Illustratively, the EAS deployment information includes at least one of: DNS server, ECS option, provider address of corresponding EAS in access network; wherein, the EAS registered on the DNS server is the EAS corresponding to the provider in the access network, and the EAS corresponding to the ECS option is the EAS corresponding to the provider in the access network.

Optionally, the EAS deployment information includes information of a DNS server, and the DNS processing rule includes information of the DNS server, and the transceiver unit 1410 is configured to send a DNS query message to the DNS server.

Optionally, the DNS server is a server deployed in the home network, and the processing unit 1420 is configured to add ECS option to the DNS query message according to a DNS processing rule; a transceiver unit 1410, configured to send a DNS query message including the ECS option to the DNS server.

Optionally, the EAS deployment information includes an address of an EAS corresponding to the provider in the access network, the DNS processing rule includes an address of an EAS corresponding to the provider in the access network, and the processing unit 1420 is configured to obtain, according to the DNS processing rule, the address of at least one EAS; and generating a response message of the DNS inquiry message, wherein the response message comprises part or all of the addresses of at least one EAS, and the part or all of the EAS addresses are determined according to the corresponding EAS of the provider in the access network.

Optionally, the EAS deployment information includes ECS option, and the DNS processing rule includes information of ECS option, and the processing unit 1420 is configured to add ECS option in the DNS query message.

Optionally, the transceiver unit 1410 is configured to receive DNS processing rules from the session management network element.

Illustratively, the provider is any one of: EAS provider, edge host environment EHE provider, edge data network EDN provider.

It should be understood that the specific process of each unit performing the corresponding steps has been described in detail in the above method embodiments, and is not described herein for brevity.

It should also be appreciated that the apparatus 1400 herein is embodied in the form of functional units. The term "unit" herein may refer to an application specific integrated circuit (application specific integrated circuit, ASIC), an electronic circuit, a processor (e.g., a shared, dedicated, or group processor, etc.) and memory that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable components that support the described functionality. In an alternative example, it will be understood by those skilled in the art that the apparatus 1400 may be specifically configured as a session management network element in the foregoing embodiments, and may be configured to perform each flow and/or step corresponding to the session management network element in the foregoing method embodiments; alternatively, the apparatus 1400 may be specifically configured as a data management network element in the foregoing embodiments, and may be configured to perform each flow and/or step corresponding to the data management network element in the foregoing method embodiments; alternatively, the apparatus 1400 may be specifically an application network element in the foregoing embodiments, and may be configured to perform each flow and/or step corresponding to the application network element in the foregoing method embodiments; alternatively, the apparatus 1400 may be specifically configured to discover a network element by an edge application server in the above embodiments, and may be configured to execute each flow and/or step corresponding to the discovery network element by the edge application server in the above method embodiments, which are not described herein for avoiding repetition.

The apparatus 1400 of each of the above embodiments has a function of implementing the corresponding steps performed by the network element (such as a session management network element, or a data management network element, or an application network element, or an edge application server discovery network element) in the above method. The functions may be implemented by hardware, or may be implemented by hardware executing corresponding software. The hardware or software comprises one or more modules corresponding to the functions; for example, the transceiver unit may be replaced by a transceiver (e.g., a transmitting unit in the transceiver unit may be replaced by a transmitter, a receiving unit in the transceiver unit may be replaced by a receiver), and other units, such as a processing unit, etc., may be replaced by a processor, to perform the transceiver operations and related processing operations in the various method embodiments, respectively.

The transceiver 1410 may be a transceiver circuit (e.g., may include a receiving circuit and a transmitting circuit), and the processing unit may be a processing circuit.

It should be noted that the apparatus in fig. 14 may be a network element or a device in the foregoing embodiment, or may be a chip or a chip system, for example: system on chip (SoC). The receiving and transmitting unit can be an input and output circuit and a communication interface; the processing unit is an integrated processor or microprocessor or integrated circuit on the chip. And are not limited herein.

Fig. 15 is a schematic diagram of an apparatus 1500 for providing another communication in accordance with an embodiment of the present application. The apparatus 1500 includes a processor 1510, the processor 1510 being configured to execute computer programs or instructions stored in a memory 1520 or to read data/signaling stored in the memory 1520 to perform the methods in the method embodiments above. Optionally, the processor 1510 is one or more.

Optionally, as shown in fig. 15, the apparatus 1500 further comprises a memory 1520, the memory 1520 for storing computer programs or instructions and/or data. The memory 1520 may be integrated with the processor 1510 or may be provided separately. Optionally, memory 1520 is one or more.

Optionally, as shown in fig. 15, the apparatus 1500 further comprises a transceiver 1530, the transceiver 1530 being for receiving and/or transmitting signals. For example, the processor 1510 is configured to control the transceiver 1530 to receive and/or transmit signals.

As an option, the apparatus 1500 is configured to implement the operations performed by the session management network element in the above method embodiments.

For example, processor 1510 is configured to execute computer programs or instructions stored in memory 1520 to perform the operations associated with session management network elements in the various method embodiments above. For example, the method performed by the session management network element in the embodiment shown in fig. 5, or the method performed by the SMF in the embodiment shown in any one of fig. 9 to 13.

Alternatively, the apparatus 1500 is configured to implement the operations performed by the application network element in the method embodiments above.

For example, the processor 1510 is configured to execute computer programs or instructions stored in the memory 1520 to implement the relevant operations of the application network element in the method embodiments above. For example, the method performed by the application network element in the embodiment shown in fig. 5, or the method performed by the AF in any one of the embodiments shown in fig. 9 to 13.

Alternatively, the apparatus 1500 is configured to implement the operations performed by the data management network element in the method embodiments above.

For example, the processor 1510 is configured to execute computer programs or instructions stored in the memory 1520 to implement the relevant operations of the data management network element in the method embodiments above. For example, the method performed by the data management network element in the embodiment shown in fig. 5, or the method performed by the UDR in the embodiment shown in any one of fig. 9 to 13.

Alternatively, the apparatus 1500 is configured to implement the operations performed by the edge application server discovery network element in the method embodiments above.

For example, the processor 1510 is configured to execute computer programs or instructions stored in the memory 1520 to implement the operations associated with the discovery of network elements by the edge application server in the method embodiments above. For example, the edge application server in the embodiment shown in fig. 5 discovers the method performed by the network element, or the EASDF in any of the embodiments shown in fig. 9-13.

It should be appreciated that the processors referred to in embodiments of the present application may be central processing units (central processing unit, CPU), but may also be other general purpose processors, digital signal processors (digital signal processor, DSP), application specific integrated circuits (application specific integrated circuit, ASIC), off-the-shelf programmable gate arrays (field programmable gate array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

It should also be understood that the memory referred to in embodiments of the present application may be volatile memory and/or nonvolatile memory. The nonvolatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. The volatile memory may be random access memory (random access memory, RAM). For example, RAM may be used as an external cache. By way of example, and not limitation, RAM includes the following forms: static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous DRAM (SLDRAM), and direct memory bus RAM (DR RAM).

It should be noted that when the processor is a general purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, the memory (storage module) may be integrated into the processor.

It should also be noted that the memory described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

Fig. 16 is a schematic diagram of a chip system 1600 according to an embodiment of the present application. The system-on-chip 1600 (or may also be referred to as a processing system) includes logic 1610 and input/output interface 1620.

Logic 1610 may be a processing circuit in system-on-chip 1600. Logic 1610 may be coupled to the memory unit to invoke instructions in the memory unit so that system-on-chip 1600 may implement the methods and functions of embodiments of the present application. The input/output interface 1620 may be an input/output circuit in the chip system 1600, and outputs information processed by the chip system 1600, or inputs data or signaling information to be processed into the chip system 1600 for processing.

Specifically, for example, if the SMF is installed with the chip system 1600, the logic 1610 is coupled to the input/output interface 1620, the logic 1610 may send DNS processing rules through the input/output interface 1620, which may be generated for the logic 1610; or the input/output interface 1620 may input EAS deployment information from the NEF to the logic 1610 for processing.

As an option, the chip system 1600 is used to implement the operations performed by the session management network element in the method embodiments above.

For example, the logic 1610 is configured to implement the operations related to the processing performed by the session management network element in the above method embodiment, for example, the operations related to the processing performed by the session management network element in the embodiment shown in fig. 5, or the operations related to the processing performed by the SMF in the embodiment shown in any of fig. 9 to 13; the input/output interface 1620 is configured to implement the above operations related to transmission and/or reception performed by the session management network element in the method embodiment, for example, the operations related to transmission and/or reception performed by the session management network element in the embodiment shown in fig. 5, or the operations related to transmission and/or reception performed by the SMF in the embodiment shown in any one of fig. 9 to 13.

Alternatively, the system on a chip 1600 is configured to implement the operations performed by the application network element in the method embodiments above.

For example, the logic 1610 is configured to implement operations related to processing performed by an application network element in the above method embodiment, for example, operations related to processing performed by an application network element in the embodiment shown in fig. 5, or operations related to processing performed by AF in any one of the embodiments shown in fig. 9 to 13; the input/output interface 1620 is configured to implement the operations related to transmission and/or reception performed by the application network element in the above method embodiment, for example, the operations related to transmission and/or reception performed by the application network element in the embodiment shown in fig. 5, or the operations related to transmission and/or reception performed by the AF in the embodiment shown in any one of fig. 9 to 13.

Alternatively, the system on a chip 1600 is configured to implement the operations performed by the data management network element in the various method embodiments above.

For example, the logic 1610 is configured to implement the operations related to the processing performed by the data management network element in the above method embodiment, for example, the operations related to the processing performed by the data management network element in the embodiment shown in fig. 5, or the operations related to the processing performed by the UDR in the embodiment shown in any one of fig. 9 to 13; the input/output interface 1620 is configured to implement the above operations related to transmission and/or reception performed by the data management network element in the method embodiment, for example, the operations related to transmission and/or reception performed by the data management network element in the embodiment shown in fig. 5, or the operations related to transmission and/or reception performed by the UDR in the embodiment shown in any one of fig. 9 to 13.

Alternatively, the system on a chip 1600 is configured to implement the operations performed by the edge application server discovery network element in the method embodiments above.

For example, the logic 1610 is configured to implement operations related to processing performed by the edge application server discovery network element in the above method embodiment, for example, operations related to processing performed by the edge application server discovery network element in the embodiment shown in fig. 5, or operations related to processing performed by the EASDF in any of the embodiments shown in fig. 9 to 13; the input/output interface 1620 is configured to implement the operations related to transmission and/or reception performed by the edge application server discovery network element in the above method embodiment, for example, the operations related to transmission and/or reception performed by the edge application server discovery network element in the embodiment shown in fig. 5, or the operations related to transmission and/or reception performed by the EASDF in the embodiment shown in any one of fig. 9 to 13.

The embodiments of the present application further provide a computer readable storage medium having stored thereon computer instructions for implementing the method performed by the network element in the above method embodiments.

For example, the computer program, when executed by a computer, enables the computer to implement the method performed by the session management network element in the embodiments of the method described above.

As another example, the computer program when executed by a computer may enable the computer to implement the method performed by the application network element in the embodiments of the method described above.

As another example, the computer program when executed by a computer may enable the computer to implement the method performed by the data management network element in the embodiments of the method described above.

As another example, the computer program when executed by a computer may enable the computer to implement the method performed by the edge application server discovery network element in the embodiments of the method described above.

The embodiments of the present application also provide a computer program product comprising instructions that when executed by a computer implement the method performed by a network element (e.g., a session management network element, or an application network element, or a data management network element, or an edge application server discovery network element) in the above method embodiments.

The embodiment of the application also provides a communication system which comprises one or more of the session management network element, the application network element, the data management network element or the edge application server discovery network element. Optionally, the system further includes a device that communicates with one or more network elements. For example, at least one of the following may be included in the system: terminal equipment, NEF, etc.

The explanation and beneficial effects of the related content in any of the above-mentioned devices can refer to the corresponding method embodiments provided above, and are not repeated here.

In the several embodiments provided by the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Furthermore, the coupling or direct coupling or communication connection shown or discussed with each other may be through some interface, device or unit indirect coupling or communication connection, which may be in electrical, mechanical or other form.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, 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. When loaded and executed on a computer, produces a flow or function in accordance with embodiments of the present application, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. For example, the computer may be a personal computer, a server, or a network device, etc. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another, for example, by wired (e.g., coaxial cable, optical fiber, digital Subscriber Line (DSL)), or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. For example, the aforementioned usable media include, but are not limited to, U disk, removable hard disk, read-only memory (ROM), random access memory (random access memory, RAM), magnetic disk or optical disk and other various media that can store program code.

The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method of communication, comprising:

the session management network element obtains provider information, wherein the provider is a provider for providing edge computing service for terminal equipment;

the session management network element configures Domain Name Service (DNS) processing rules according to the provider information and the corresponding Edge Application Server (EAS) deployment information of the provider, wherein the DNS processing rules are used for processing DNS information of the terminal equipment, and the EAS deployment information is corresponding EAS deployment information of the provider in an access network of the terminal equipment;

and the session management network element sends the DNS processing rule to an edge application server discovery network element.

2. The method according to claim 1, wherein the method further comprises:

the session management network element obtains the EAS deployment information according to the provider information; or alternatively, the process may be performed,

And the session management network element acquires the EAS deployment information according to the provider information and the information of the access network.

3. The method according to claim 1 or 2, wherein the EAS deployment information comprises any one of the following: DNS server, ECS option, address of corresponding EAS in the said access network of the said provider;

wherein, the EAS registered on the DNS server is the EAS corresponding to the provider in the access network, and the EAS corresponding to the ECS option is the EAS corresponding to the provider in the access network.

4. A method according to claim 3, characterized in that the DNS server is a server deployed in the home network or the DNS server is a server deployed in the access network.

5. The method of claim 3 or 4, wherein the DNS processing rules include any of: DNS server, ECS option, address of the EAS corresponding to the provider in the access network.

6. The method according to any of claims 1 to 5, wherein the session management network element obtains provider information comprising any of:

The session management network element determines the provider information according to the home network of the terminal equipment;

the session management network element determines the provider information according to the subscription information of the terminal equipment, wherein the subscription information of the terminal equipment comprises the information of the provider;

the session management network element determines the provider information according to the terminal equipment included in the terminal equipment list provided by the provider; or alternatively, the process may be performed,

the session management network element determines the provider information according to a protocol between the provider and the access network.

7. The method according to any of claims 1 to 6, wherein the access network is a visited network of the terminal equipment and the provider is a home network of the terminal equipment.

8. The method according to any one of claims 1 to 7, wherein the provider is any one of the following: the provider of EAS, the provider of edge hosting environment EHE, or the provider of edge data network EDN.

9. A method of communication, comprising:

the edge application server discovers that the network element receives Domain Name Service (DNS) query messages from the terminal equipment;

The edge application server discovers that the network element processes the DNS query message according to a DNS processing rule;

the DNS processing rule is determined according to EAS deployment information of an edge application server corresponding to a provider for providing edge computing service for the terminal equipment, wherein the EAS deployment information is EAS deployment information of the provider in an access network of the terminal equipment.

10. The method of claim 9, wherein the EAS deployment information is determined from the provider information; alternatively, the EAS deployment information is determined based on the provider information and information of the access network.

11. The method of claim 9 or 10, wherein the EAS deployment information includes at least one of:

DNS server, ECS option, address of corresponding EAS in the said access network of the said provider;

12. The method of claim 10, wherein the DNS server is a server deployed in a home network or the DNS server is a server deployed in the access network.

13. The method of claim 11 or 12, wherein the EAS deployment information includes information of the DNS server, wherein the DNS processing rules include information of the DNS server,

the edge application server discovers that the network element processes the DNS query message according to a DNS processing rule, and the method comprises the following steps:

the edge application server discovers that a network element sends the DNS query message to the DNS server.

14. The method of claim 13, wherein the DNS server is a server deployed in the home network,

the edge application server discovers that the network element processes the DNS query message according to a DNS processing rule, and further includes:

the edge application server discovers that the network element adds ECS option in the DNS query message according to the DNS processing rule;

the edge application server discovery network element sending the DNS query message to the DNS server, including:

the edge application server discovers that a network element sends a DNS query message containing the ECS option to the DNS server.

15. The method of claim 11, wherein the EAS deployment information includes an address of the corresponding EAS in the access network for the provider, wherein the DNS processing rules include an address of the corresponding EAS in the access network for the provider,

the edge application server discovers that the network element obtains the address of at least one EAS according to the DNS processing rule;

the edge application server discovers that the network element generates a response message to the DNS query message, the response message including some or all of the at least one EAS address,

wherein the partial or full EAS address is determined based on the EAS corresponding to the provider in the access network.

16. The method according to any one of claims 11 to 15, wherein the ECS option is included in the EAS deployment information, wherein the DNS processing rules include information of the ECS option,

the edge application server discovers that the network element adds the ECS option in the DNS query message.

17. The method according to any one of claims 9 to 16, further comprising:

the edge application server discovers that the network element receives the DNS handling rules from a session management network element.

18. The method of any one of claims 9 to 17, wherein the provider is any one of: EAS provider, edge host environment EHE provider, edge data network EDN provider.

19. An apparatus for communication, comprising:

a processor for executing a computer program stored in a memory to cause the apparatus to perform the method of any one of claims 1 to 8 or to cause the apparatus to perform the method of any one of claims 9 to 18.

20. The apparatus of claim 19, further comprising the memory.

21. A computer readable storage medium, characterized in that the computer readable storage medium has stored thereon a computer program which, when run on a computer, causes the computer to perform the method according to any of claims 1 to 8 or to cause the computer to perform the method according to any of claims 9 to 18.

22. A computer program product, characterized in that the computer program product comprises instructions for performing the method of any one of claims 1 to 8 or the computer program product comprises instructions for performing the method of any one of claims 9 to 18.

23. A communication system is characterized by comprising a session management network element and an edge application server discovery network element,

wherein the session management network element is configured to perform the method according to any of claims 1 to 8, and the edge application server discovery network element is configured to perform the method according to any of claims 9 to 18.