WO2023185620A1 - Procédé et appareil de communication - Google Patents

Procédé et appareil de communication Download PDF

Info

Publication number
WO2023185620A1
WO2023185620A1 PCT/CN2023/083362 CN2023083362W WO2023185620A1 WO 2023185620 A1 WO2023185620 A1 WO 2023185620A1 CN 2023083362 W CN2023083362 W CN 2023083362W WO 2023185620 A1 WO2023185620 A1 WO 2023185620A1
Authority
WO
WIPO (PCT)
Prior art keywords
provider
eas
dns
information
network element
Prior art date
Application number
PCT/CN2023/083362
Other languages
English (en)
Chinese (zh)
Inventor
王亚鑫
李岩
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2023185620A1 publication Critical patent/WO2023185620A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/26—Network addressing or numbering for mobility support

Definitions

  • the embodiments of the present application relate to the field of communications, and more specifically, to a communication method and device.
  • An edge application server can be deployed in the network, and EAS can provide edge services for terminal equipment (user equipment (UE)).
  • UE user equipment
  • One operator (for example, called OP1) deploys an EAS or computer room in another operator (for example, called OP2).
  • Terminal devices that access the network through OP2 can preferentially select a certain operator based on their home domain or contract status.
  • EAS of an OP (such as OP1). How to prioritize a certain OP's EAS for terminal equipment is an issue worth considering.
  • This application provides a communication method and device. By providing provider information of edge computing services for terminal equipment, it searches for the EAS deployment information corresponding to the provider, and then selects the access network of the provider in the terminal equipment for the terminal equipment. The corresponding EAS in .
  • the first aspect provides a communication method, which can be executed by the session management network element, or can also be executed by components (such as chips or circuits) of the session management network element. There is no limitation on this. For the convenience of description, , the following description takes execution by the session management network element as an example.
  • the method may include: the session management network element obtains provider information, and the provider is a provider that provides edge computing services for terminal devices; the session management network element configures a domain name based on the provider information and the provider's corresponding edge application server EAS deployment information Service DNS processing rules. DNS processing rules are used to process DNS messages of terminal devices.
  • the EAS deployment information is the corresponding EAS deployment information of the provider in the access network of the terminal device; the session management network element sends DNS to the edge application server discovery network element. Processing rules.
  • the EAS deployment information is the deployment information of the provider's corresponding EAS in the access network of the terminal device.
  • the session management network element configures DNS processing rules based on the information of the provider that provides edge computing services for terminal devices and the EAS deployment information corresponding to the provider, and sends them to the edge application server to discover the network element, and the edge application server It is found that the network element processes the DNS query message of the terminal device based on the DNS processing rule.
  • the session management network element configures DNS processing rules based on the provider's information and the provider's corresponding EAS deployment information. It can not only obtain the provider's corresponding EAS deployment information directly based on the provider's information, but also directly obtain the provider's corresponding EAS deployment information based on the provider's information.
  • the edge application server discovers that the network element is processing the DNS of the terminal device based on the DNS processing rules.
  • the terminal device can be selected (or provided) with the EAS corresponding to the provider in the access network.
  • the provider by associating the provider with the provider's EAS deployment information in the access network of the terminal device, it is not only possible to provide corresponding terminal devices according to the needs of the terminal device (such as using edge computing services provided by a certain provider).
  • EAS and by configuring DNS processing rules based on the provider's corresponding EAS deployment information, the existing DNS processing rule configuration process is used, with minimal changes to the protocol.
  • the method further includes: the session management network element obtains the EAS deployment information based on the provider information; or, the session management network element obtains the EAS deployment information based on the provider information and access network information. , obtain EAS deployment information.
  • the corresponding EAS deployment information can be determined based on the provider information.
  • the EAS deployment information may include the provider's information (such as the provider ID); for another example, the EAS deployment information is associated with the provider's information (such as the provider ID).
  • the corresponding EAS deployment information can also be determined based on the provider information and access network information.
  • the EAS deployment information includes provider information (such as provider ID) and access network information (such as access network ID); for another example, the EAS deployment information and provider information (such as provider ID ) and access network information (such as access network ID).
  • the EAS deployment information includes a DNS server, and the EAS registered on the DNS server is the corresponding EAS of the provider in the access network.
  • the EAS registered on the DNS server in the provider's corresponding EAS deployment information is the provider's corresponding EAS in the access network. Therefore, the provider's information on the access network can be queried through the DNS server. The corresponding EAS in .
  • the EAS deployment information includes the ECS option
  • the EAS corresponding to the ECS option is the EAS corresponding to the access network of the provider that provides edge computing services for terminal devices.
  • 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. Therefore, the ECS option can be used to query the provider in the access network. Corresponding EAS.
  • the EAS deployment information includes the address of the EAS corresponding to the provider that provides edge computing services for the terminal device in the access network.
  • 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. Therefore, through this EAS address, it is possible to filter out (or Select) an address belonging to the above-mentioned EAS address, and then provide the terminal device with the EAS corresponding to the provider in the access network.
  • the DNS server is a server deployed in the home network, or the DNS server is a server deployed in the access network.
  • the DNS processing rules include any of the following: DNS server, ECS option, and the address of the provider's corresponding EAS in the access network.
  • the above information is carried in the DNS processing rule, so that when processing the query request of the terminal device based on the DNS processing rule, the EAS corresponding to the provider in the access network can be provided for the terminal device.
  • the access network of the terminal device is a visited network of the terminal device.
  • the provider that provides edge computing services for the terminal device may be a provider outside the visited network of the terminal device.
  • Provider such as the home network of the terminal device, or the third-party edge computing service provider subscribed by the terminal device.
  • the session management network element obtains provider information, including any of the following: the session management network element determines the provider information according to the home network of the terminal device; the session management network element determines the provider information according to the home network of the terminal device; The session management network element determines the provider information based on the contract information of the terminal device, where the contract information of the terminal device includes the provider's information; the session management network element determines the provider information based on the terminal device included in the terminal device list provided by the provider; or , the session management network element determines the provider information according to the agreement between the provider and the access network.
  • the agreement between the provider and the access network can also be understood as an alliance agreement between the provider and the access network.
  • the provider can be determined for the terminal device.
  • the session management network element can be based on: the home network of the terminal device, the contract information of the terminal device, the terminal device included in the terminal device list provided by the provider, or any of the agreements between the provider and the access network.
  • One step determines the provider, and then obtains the EAS deployment information corresponding to the provider; or it can also be based on the home network of the terminal device, the contract information of the terminal device, the terminal device included in the terminal device list provided by the provider, or the provider and the interface.
  • Any one of the protocols between access networks determines the provider, and combines the access network to obtain the EAS deployment information corresponding to the provider. There are no restrictions on this.
  • the provider is any one of the following: a provider of EAS, a provider of edge host environment EHE, or a provider of edge data network EDN.
  • the second aspect provides a communication method, which can be executed by the edge application server discovering the network element, or it can also be executed by the edge application server discovering the component parts (such as chips or circuits) of the network element, which is not limited. , for the convenience of description, the following takes the discovery of network elements by the edge application server as an example for explanation.
  • the method may include: the edge application server discovers the network element and receives the domain name service DNS query message from the terminal device; the edge application server discovers the network element and processes the DNS query message according to the DNS processing rule; wherein the DNS processing rule is based on providing the edge for the terminal device.
  • the EAS deployment information of the edge application server corresponding to the computing service provider is determined, and the EAS deployment information is the EAS deployment information of the provider in the access network of the terminal device.
  • the EAS deployment information is determined based on provider information; or, the EAS deployment information is determined based on provider information and access network information.
  • the EAS deployment information includes at least one of the following: DNS server, ECS option, and the address of the EAS corresponding to the provider in the access network; wherein, on the DNS server The registered EAS 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.
  • the DNS server is a server deployed in the home network, or the DNS server is a server deployed in the access network.
  • the EAS deployment information includes DNS server information
  • the DNS processing rules include DNS server information
  • the edge application server discovers the network element and processes the DNS query message according to the DNS processing rules. , including: the edge application server discovers the network element and sends a DNS query message to the DNS server.
  • the edge application server discovers that the network element sends a message to the DNS server.
  • a query message is sent to the terminal device, and the DNS server processes the query request of the terminal device, so that the DNS server provides the terminal device with the EAS corresponding to the provider in the access network.
  • the DNS server is a server deployed in the home network
  • the edge application server discovers network elements and processes DNS query messages according to DNS processing rules, which also includes: edge application server discovery
  • the network element adds the ECS option to the DNS query message according to the DNS processing rules
  • the edge application server discovers the network element and sends a DNS query message to the DNS server, including: the edge application server discovers the network element and sends a DNS query message containing the ECS option to the DNS server.
  • the EAS corresponding to the ECS option is the EAS corresponding to the access network of the provider that provides edge computing services for terminal devices, therefore, after the edge application server discovers that the network element adds the ECS option in the DNS query message, it can It is implemented to provide the terminal device with the information of the EAS corresponding to the provider in the access network.
  • the EAS deployment information includes the address of the provider's corresponding EAS in the access network
  • the DNS processing rules include the address of the provider's corresponding EAS in the access network.
  • the edge application server discovers the network element and processes the DNS query message according to the DNS processing rules, including: the edge application server discovers the network element and obtains the address of at least one EAS according to the DNS processing rules; the edge application server discovers the network element and generates a response message for the DNS query message , the response message includes part or all of the EAS addresses of at least one EAS, where part or all of the EAS addresses are determined based on the provider's corresponding EAS in the access network.
  • the edge application server After the edge application server discovers that the network element has received a response to the DNS query message, it can filter out (or select) the address belonging to the above-mentioned EAS address from the query response, and then provide the provider with the information for the terminal device.
  • the corresponding EAS in the access network After the edge application server discovers that the network element has received a response to the DNS query message, it can filter out (or select) the address belonging to the above-mentioned EAS address from the query response, and then provide the provider with the information for the terminal device.
  • the corresponding EAS in the access network After the edge application server discovers that the network element has received a response to the DNS query message, it can filter out (or select) the address belonging to the above-mentioned EAS address from the query response, and then provide the provider with the information for the terminal device.
  • the corresponding EAS in the access network After the edge application server discovers that the network element has received a response to the DNS query message, it can filter out (or select) the
  • the EAS deployment information includes the ECS option
  • the DNS processing rules include the information of the ECS option
  • the edge application server discovers that the network element processes the DNS query message according to the DNS processing rules, including : The edge application server discovers that the network element adds the ECS option in the DNS query message.
  • the method further includes: the edge application server discovers the network element and receives the DNS processing rule from the session management network element.
  • the provider is any one of the following: a provider of EAS, a provider of edge host environment EHE, or a provider of edge data network EDN.
  • a communication method is provided.
  • This method can be executed by the data management network element, or can also be executed by the component (such as a chip or circuit) of the data management network element.
  • the component such as a chip or circuit
  • the following description takes the execution by the data management network element as an example.
  • the method may include: the data management network element receives from the application network element edge application server EAS deployment information corresponding to a provider that provides edge computing services for terminal devices, and the EAS deployment information is corresponding to the provider in the access network of the terminal device. EAS deployment information; the data management network element stores EAS deployment information.
  • the data management network element can store the EAS deployment information corresponding to the provider.
  • the session management network element can be provided with the EAS deployment information corresponding to the above provider.
  • the session management network element determines the corresponding DNS processing rules based on the EAS deployment information corresponding to the above provider, so as to select (or provide) the EAS corresponding to the above provider in the access network of the terminal device for the terminal device.
  • the EAS deployment information is determined based on provider information; or, the EAS deployment information is determined based on provider information and access network information.
  • the EAS deployment information is determined based on the provider information, which can be understood as querying the EAS deployment information corresponding to the provider based on the provider information.
  • the EAS deployment information is determined based on the provider information and the access network information, which can be understood as querying the EAS deployment information corresponding to the provider based on the provider information and the access network information.
  • the EAS deployment information includes at least one of the following information: data network name, network slice information, data network access identifier, or application information.
  • the application information may be an application ID.
  • the EAS deployment information includes at least one of the following: DNS server, ECS option, and the address of the EAS corresponding to the provider in the access network; wherein, on the DNS server The registered EAS 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.
  • the DNS server is a server deployed in the home network, or the DNS server is a server deployed in the access network.
  • the method further includes: the data management network element receives information from at least one provider of the application network element and information from at least one terminal device, and the at least one provider can provide At least one terminal device provides edge computing services.
  • the provider is any of the following: a provider of EAS, a provider of edge host environment EHE, or a provider of edge data network EDN.
  • the fourth aspect provides a communication method, which can be executed by the application network element, or can also be executed by the component (such as a chip or circuit) of the application network element.
  • the component such as a chip or circuit
  • the method may include: the application network element determines the EAS deployment information of the edge application server corresponding to the provider that provides edge computing services for the terminal device, where the EAS deployment information is the EAS deployment information corresponding to the provider in the access network of the terminal device; the application network Yuan sends EAS deployment information.
  • the application network element can provide the EAS deployment information corresponding to the above-mentioned providers.
  • the application network element or other network elements can provide the above-mentioned EAS deployment information.
  • the EAS deployment information corresponding to the provider is sent to other network elements) to provide the session management network element with the EAS deployment information corresponding to the above provider, thereby enabling the session management network element to determine the corresponding DNS processing rules based on the EAS deployment information corresponding to the above provider, Implementation of selecting (or providing) the EAS corresponding to the above provider in the access network of the terminal device for the terminal device.
  • the EAS deployment information is determined based on provider information; or, the EAS deployment information is determined based on provider information and access network information.
  • the application network element sends EAS deployment information, including: the application network element sends EAS deployment information to one or more of the following: data management network element, session management network element , network open network elements.
  • the EAS deployment information includes at least one of the following information: Information: data network name, network slice information, data network access identifier, or application information.
  • the EAS deployment information includes at least one of the following: DNS server, ECS option, and the address of the EAS corresponding to the provider in the access network; wherein, registered on the DNS server
  • the EAS is the EAS corresponding to the provider in the access network
  • the EAS corresponding to the ECS option is the EAS corresponding to the provider in the access network.
  • the DNS server is a server deployed in the home network, or the DNS server is a server deployed in the access network.
  • the method further includes: applying the network element to send information of at least one provider and information of at least one terminal device, and at least one provider can provide an edge for at least one terminal device. Computing services.
  • the provider is any of the following: a provider of EAS, a provider of edge host environment EHE, or a provider of edge data network EDN.
  • a fifth aspect provides a communication device, which is used to perform the method in any of the possible implementations of the first to fourth aspects.
  • the device may include units and/or modules for performing the method in any possible implementation of the first to fourth aspects, such as a processing unit and/or a communication unit.
  • the device is a core network element (such as a session management network element, a data management network element, a network opening network element, or a policy control network element).
  • the communication unit may be a transceiver or an input/output interface; the processing unit may be at least one processor.
  • the transceiver may be a transceiver circuit.
  • the input/output interface may be an input/output circuit.
  • the device is a chip or chip system used for a core network element (such as a session management network element, a data management network element, a network opening network element, or a policy control network element). or circuit.
  • a core network element such as a session management network element, a data management network element, a network opening network element, or a policy control network element.
  • the communication unit may be an input/output interface, interface circuit, output circuit, input circuit, pin or related information on the chip, chip system or circuit. circuit, etc.; the processing unit may be at least one processor, processing circuit or logic circuit, etc.
  • a sixth aspect provides a communication device.
  • the device includes: at least one processor for executing computer programs or instructions stored in a memory to execute the method in any of the possible implementations of the first to fourth aspects.
  • the device further includes a memory for storing computer programs or instructions.
  • the device further includes a communication interface, through which the processor reads the computer program or instructions stored in the memory.
  • the device is a core network element (such as a session management network element, a data management network element, a network opening network element, or a policy control network element).
  • a core network element such as a session management network element, a data management network element, a network opening network element, or a policy control network element.
  • the device is a chip or chip system used for a core network element (such as a session management network element, a data management network element, a network opening network element, or a policy control network element). or circuit.
  • a core network element such as a session management network element, a data management network element, a network opening network element, or a policy control network element.
  • this application provides a processor for executing the methods provided in the above aspects.
  • processor output, reception, input and other operations can be understood as processor output, reception, input and other operations.
  • transmitting and receiving operations performed by the radio frequency circuit and the antenna, which is not limited in this application.
  • a computer-readable storage medium stores a program code for device execution.
  • the program code includes a method for executing any of the possible implementations of the above-mentioned first to fourth aspects. method.
  • a ninth aspect provides a computer program product containing instructions, which when the computer program product is run on a computer, causes the computer to execute the method in any of the possible implementations of the first to fourth aspects.
  • a tenth aspect provides a communication system, including one or more of the aforementioned session management network element, edge application server discovery network element, data management network element, or application network element.
  • the communication system includes the aforementioned session management network element and a network element/device that communicates with the aforementioned session management network element.
  • the communication system includes the aforementioned edge application server discovery network element and a network element/device that communicates with the aforementioned edge application server discovery network element.
  • the communication system includes the aforementioned data management network element and network elements/devices that communicate with the aforementioned data management network element.
  • the communication system includes the aforementioned application network element and a network element/device that communicates with the aforementioned application network element.
  • Figure 1 is a schematic diagram of a network architecture suitable for embodiments of the present application.
  • Figure 2 is a schematic diagram of another network architecture suitable for embodiments of the present application.
  • Figure 3 is a schematic diagram of another network architecture suitable for embodiments of the present application.
  • Figure 4 is a schematic diagram of another network architecture suitable for embodiments of the present application.
  • Figure 5 is a schematic diagram of a communication method 500 provided by an embodiment of the present application.
  • Figure 6 is a schematic diagram of a network architecture provided by an embodiment of the present application.
  • Figure 7 is a schematic diagram of a network architecture provided by another embodiment of the present application.
  • Figure 8 is a schematic diagram of a network architecture provided by another embodiment of the present application.
  • Figure 9 is a schematic flow chart of a communication method 900 provided by an embodiment of the present application.
  • Figure 10 is a schematic flow chart of a communication method 1000 provided by an embodiment of the present application.
  • Figure 11 is a schematic flow chart of a communication method 1100 provided by an embodiment of the present application.
  • Figure 12 is a schematic flow chart of a communication method 1200 provided by an embodiment of the present application.
  • Figure 13 is a schematic flow chart of a communication method 1300 provided by an embodiment of the present application.
  • Figure 14 is a schematic diagram of a communication device 1400 provided by an embodiment of the present application.
  • Figure 15 is a schematic diagram of a device 1500 that provides another type of communication according to an embodiment of the present application.
  • FIG. 16 is a schematic diagram of a chip system 1600 provided by an embodiment of the present application.
  • the technical solutions provided by this application can be applied to various communication systems, such as: fifth generation (5th generation, 5G) or new radio (NR) systems, long term evolution (LTE) systems, LTE frequency division Duplex (frequency division duplex, FDD) system, LTE time division duplex (TDD) system, etc.
  • the technical solution provided by this application can also be applied to future communication systems, such as the sixth generation mobile communication system.
  • the technical solution provided by this application can also be applied to device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine (M2M) communication, Machine type communication (MTC), and Internet of things (IoT) communication systems or other communication systems.
  • D2D device-to-device
  • V2X vehicle-to-everything
  • M2M machine-to-machine
  • MTC Machine type communication
  • IoT Internet of things
  • roaming refers to the situation where a mobile user belonging to operator A accesses the network of operator B.
  • the network of operator A can be considered as the home network (or home network)
  • the network of operator B can be considered as the visited network.
  • a certain standard of cellular mobile communication network of a certain operator can be called a public land mobile network (PLMN).
  • PLMN public land mobile network
  • the PLMN subscribed by the user equipment (UE) can be called the home public land mobile network (PLMN) (home PLMN, HPLMN), which represents the home operator of the subscriber.
  • PLMN home public land mobile network
  • HPLMN home public land mobile network
  • the content may include, for example: services and billing methods for contracted users of the other operator's network.
  • this PLMN may be called a visited public land mobile network (visited PLMN, VPLMN).
  • the behavior of the UE accessing the VPLMN can be called roaming.
  • roaming scenarios can be divided into local breakout (LBO) roaming and home routed (HR) roaming. The main difference between the two is whether the session needs to be connected to the user plane function (UPF) of the home network. ).
  • LBO local breakout
  • HR home routed
  • UPF user plane function
  • Figure 1 is a schematic diagram of a network architecture suitable for embodiments of the present application.
  • the network architecture shown in Figure 1 takes HR roaming as an example.
  • the network architecture can include but is not limited to: network slice specific authentication and authorization function (NSSAAF), network slice selection function (NSSF), authentication server Function (authentication server function, AUSF), unified data management (UDM), policy control function (PCF), application function (AF), access and mobility management function (access and mobility management function (AMF), session management function (SMF), UE, wireless access network equipment, UPF, data network (DN), etc.
  • NSSAAF network slice specific authentication and authorization function
  • NSSF network slice selection function
  • authentication server Function authentication server function
  • UDM unified data management
  • PCF policy control function
  • AF application function
  • access and mobility management function access and mobility management function
  • SMF session management function
  • UE wireless access network equipment
  • UPF data network
  • DN data network
  • UE It can be called terminal equipment, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent or user device.
  • the terminal device may be a device that provides voice/data to users, for example, a handheld device with wireless connection function, a vehicle-mounted device, etc.
  • terminals are: mobile phones, tablets, laptops, PDAs, mobile internet devices (MID), wearable devices, virtual reality (VR) devices, augmented reality (augmented reality, AR) equipment, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, and smart grids wireless terminals, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol , SIP) telephone, wireless local loop (WLL) station, personal digital assistant (personal digital assistant (PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a wearable device, a terminal device in a 5G network or a future evolved public land mobile network (public land mobile network, PLMN), etc.
  • the embodiments of the present application are not limited to this
  • the terminal device may also be a wearable device.
  • Wearable devices can also be called wearable smart devices. It is a general term for applying wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes, etc.
  • a wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not just hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction.
  • wearable smart devices include full-featured, large-sized devices that can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, and those that only focus on a certain type of application function and need to cooperate with other devices such as smartphones.
  • the terminal device may also be a terminal device in the IoT system.
  • IoT is an important part of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing human-machine Interconnection, an intelligent network that interconnects things.
  • terminal equipment and access network equipment can communicate with each other using certain air interface technology (such as NR or LTE technology, etc.).
  • Terminal devices can also communicate with each other using some air interface technology (such as NR or LTE technology, etc.).
  • the device used to implement the functions of the terminal device may be a terminal device, or may be a device capable of supporting the terminal device to implement the function, such as a chip system or a chip, and the device may be installed in the terminal device.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • (Radio) access network (R)AN) equipment It can provide authorized users in a specific area with the function of accessing the communication network. Specifically, it can include the 3rd generation partnership program (3rd generation partnership) Wireless network devices in project, 3GPP) networks may also include access points in non-3GPP (non-3GPP) networks. The following uses AN equipment representation for convenience of description.
  • AN equipment can use different wireless access technologies.
  • 3GPP access technologies for example, wireless access technologies used in third generation (3G), fourth generation (4G) or 5G systems
  • non-3GPP non- 3GPP (non-3GPP) access technology.
  • 3GPP access technology refers to access technology that complies with 3GPP standard specifications.
  • the access network equipment in the 5G system is called next generation Node Base station (gNB) or RAN equipment.
  • Non-3GPP access technologies can include air interface technology represented by access point (AP) in wireless fidelity (WiFi), global interoperability for microwave access (WiMAX), code Code division multiple access (CDMA), etc.
  • AP access point
  • WiFi wireless fidelity
  • WiMAX global interoperability for microwave access
  • CDMA code Code division multiple access
  • AN equipment can allow interconnection and interworking between terminal equipment and the 3GPP core network using non-3GPP technologies.
  • AN equipment can be responsible for wireless resource management, quality of service (QoS) management, data compression and encryption on the air interface side.
  • AN equipment provides access services to terminal equipment, thereby completing the forwarding of control signals and user data between the terminal equipment and the core network.
  • QoS quality of service
  • AN equipment may include, for example, but is not limited to: macro base station, micro base station (also called small station), radio network controller (RNC), Node B (Node B, NB), base station controller (base station controller) , BSC), base transceiver station (BTS), home base station (e.g., home evolved NodeB, Or home Node B (HNB), baseband unit (BBU), AP, wireless relay node, wireless backhaul node, transmission point (TP) or transmission and reception point (transmission and reception point) in the WiFi system , TRP), etc., can also be a gNB or transmission point (TRP or TP) in a 5G (such as NR) system, one or a group (including multiple antenna panels) antenna panels of a base station in a 5G system, or, also It can be a network node that constitutes a gNB or a transmission point, such as a distributed unit (DU), or a base station in the next-generation communication 6G system.
  • RNC radio
  • AMF Mainly used for functions such as access control, mobility management, attachment and detachment.
  • SMF Mainly used for user plane network element selection, user plane network element redirection, Internet protocol (IP) address allocation for terminal equipment, and session management in mobile networks, such as session establishment, modification and release. and quality of service (QoS) control.
  • IP Internet protocol
  • QoS quality of service
  • the SMF in the HPLMN is recorded as the home SMF (home SMF, H-SMF)
  • the SMF in the VPLMN is recorded as the visited SMF (visited SMF, V-SMF).
  • UPF Mainly used for receiving and forwarding user plane data.
  • the UPF can receive user plane data from the DN and send the user plane data to the terminal device through the AN device.
  • UPF can also receive user plane data from the terminal device through the AN device and forward it to the DN.
  • the UPF directly connected to the DN through the N6 interface in the session can be called the protocol data unit (PDU) session anchor (PDU session anchor, PSA).
  • PDU protocol data unit
  • PSA protocol data unit
  • the UPF in HPLMN is recorded as home UPF (homeUPF, H-UPF), and the UPF in VPLMN is recorded as visited UPF (visited UPF, V-UPF).
  • the PSA in HPLMN is recorded as home PSA (home PSA, H-PSA)
  • the PSA in VPLMN is recorded as visited PSA (V-PSA) (or local PSA, L-PSA)).
  • PCF A unified policy framework mainly used to guide network behavior and provide policy rule information for control plane network elements (such as AMF, SMF, etc.).
  • the PCF in the HPLMN is recorded as the home PCF (homePCF, H-PCF), and the PCF in the VPLMN is recorded as the visited PCF (visited PCF, V-PCF).
  • AF Mainly used to provide services to the 3GPP network, such as interacting with PCF for policy control, etc.
  • NSSF Network slice selection function
  • UDM Mainly used for UE subscription data management, including storage and management of UE identification, UE access authorization, etc.
  • DN Operator network mainly used to provide data services to UE.
  • UE For example, the Internet, third-party business networks, IP multimedia service (IMS) networks, etc.
  • IMS IP multimedia service
  • AUSF Mainly used for user authentication, etc.
  • the session (eg called HR session) is connected to the UPF of the home network.
  • An HR session refers to a session established when the user is in the visited network and connected to the UPF of the home network.
  • the traffic carried in the HR session is sent from the UE to the UPF of the home network and then to the receiving end. .
  • the UE initiates a session establishment request in the VPLMN through V-SMF; V-SMF forwards the session establishment request to H-SMF; H-SMF connects to H-PCF and performs session management ( session management, SM policy (policy) configuration and session establishment; V-SMF can be generated based on H-SMF N4 context configures V-UPF.
  • the anchor point of the session is H-UPF.
  • the main control network elements of the session include H-SMF and H-PCF.
  • V-UPF is mainly responsible for forwarding data packets between H-UPF and RAN.
  • Figure 2 is a schematic diagram of another network architecture suitable for embodiments of the present application.
  • the network architecture shown in Figure 2 takes LBO roaming as an example.
  • the network architecture may include but is not limited to: NSSAAF, NSSF, AUSF, UDM, PCF, AF, AMF, SMF, UE, radio access network equipment, UPF, DN, etc.
  • LBO session In LBO roaming scenario, the session (eg called LBO session) is not connected to the UPF of the home network (ie H-UPF).
  • An LBO session refers to a session established when the user is in the visited network and connected to the V-UPF.
  • the service flow carried in this LBO session is sent directly locally on the visited network (i.e. VPLMN) without going back to the home network.
  • VPLMN visited network
  • UPF ie H-UPF
  • the UE initiates a session establishment request in the VPLMN through V-SMF.
  • the V-SMF connects to the V-PCF and configures the SM policy of the session and establishes the session.
  • the anchor point of the session is V-UPF
  • the main control network elements of the session include V-SMF and V-PCF.
  • V-UPF can use local multi-access edge computing (MEC) ) business data packets are diverted and forwarded from V-UPF to the local edge application server (edge application server, EAS).
  • MEC multi-access edge computing
  • Figure 3 is a schematic diagram of another network architecture suitable for embodiments of the present application.
  • the network architecture can include but is not limited to: SMF, UE, UPF (such as V-UPF and H-UPF), PSA (such as L-PSA and remote PAS (remote PSA)), uplink classifier (uplink classifier, UL CL), domain name service (domain name service, DNS) server (L-DNS and C-DNS in Figure 3), edge application server discovery network element (edge application server discovery function, EASDF).
  • the edge application server discovers network elements, which may also be called edge application (service) discovery function, application instance discovery function, edge application instance discovery function, MEC application (server) discovery function, etc., and is not limited.
  • the following is a brief introduction to some of the network elements shown in Figure 3. For the introduction of the remaining network elements, please refer to the above description and will not be repeated here.
  • UL CL used to forward data packets that meet business filtering rules to a specified path.
  • the UL CL function can be provided by UPF.
  • UPF User Plane Function
  • EASDF is mainly used to assist EAS discovery. Its main functions include: processing DNS messages according to the instructions of SMF. EASDF can be considered as a centralized processing network element that can be configured by SMF during session establishment. The UE's DNS query message can be sent to EASDF through remote PSA. EASDF can process DNS messages according to the handling rules configured by SMF.
  • EASDF processes DNS messages according to processing rules, which can include the following three situations.
  • the UE sends a DNS query (DNS query) request to EASDF, and EASDF queries SMF for the EDNS client subnet option (Edns-client-subnet option, ECS option), or EASDF locally queries the ECS option (such as SMF pre-configuring the ECS option). configured on EASDF), and sends the UE’s DNS query to the C-DNS server.
  • DNS query DNS query
  • the centralized DNS server deployed in HPLMN will be recorded as C-DNS server (centralize DNS server), and the local DNS server deployed in VPLMN will be recorded as L-DNS server (local DNS server).
  • Figure 3 is simple, represented by C-DNS and L-DNS respectively.
  • the UE sends the DNS query request to EASDF, and the EASDF queries the SMF for the information of the L-DNS server (such as the address of the L-DNS server), or the EASDF locally queries the information of the L-DNS server (such as the SMF sends the L-DNS server information is preconfigured on EASDF), and the UE’s DNS query is sent to the corresponding L-DNS server.
  • the EASDF queries the SMF for the information of the L-DNS server (such as the address of the L-DNS server), or the EASDF locally queries the information of the L-DNS server (such as the SMF sends the L-DNS server information is preconfigured on EASDF), and the UE’s DNS query is sent to the corresponding L-DNS server.
  • SMF configures forwarding rules for ULCL, and the UE sends the DNS query request to the L-DNS server through L-PSA.
  • the UE can directly send the PSA to EASDF, and EASDF selects a DNS server for forwarding.
  • Figure 4 is a schematic diagram of another network architecture suitable for embodiments of the present application.
  • the network architecture can include but is not limited to: UE, RAN, PSA (such as L-PSA and remote PAS), UL CL, DNS (such as C-DNS and L-DNS), EASDF, edge data Network (edge data network, EDN).
  • EDN can contain multiple EAS.
  • a common understanding is that EDN corresponds to a data network, which is a special local data network (local DN), including an edge enabler server (EES), which can use the data network access identifier (DN Access Identifier, DNAI). ) and the data network name (DNN) identifier are network logical concepts.
  • EDN is the peer-to-peer concept of the central cloud.
  • OP1 in Figure 4 represents an operator (operator, OP).
  • EDN1 represents the edge data network in OP1; alternatively, OP1 can also represent a third-party edge computing service provider (edge computing service provider, ECSP).
  • EDN1 represents edge data network in third-party ECSP.
  • OP2 in Figure 4 represents another operator, and EDN2 represents the edge data network in OP2.
  • OP1 can deploy an independent MEC computer room in OP2 (EDN1 in Figure 4); or OP1 can also deploy its own server in the MEC computer room of VPLMN (EDN2 in Figure 4) (as shown in Figure 4) EAS in EDN2 OP1).
  • the UE is the UE of OP1, it can be regarded as the HPLMN deploying EAS on the VPLMN; for another example, if the UE is the UE of OP2, it can be regarded as the local user needs to use edge services provided by other providers.
  • the MEC computer room may also be an edge hosting environment (EHE).
  • EHE edge hosting environment
  • each network element can communicate through interfaces.
  • the UE is connected to the AN device through the radio resource control (RRC) protocol, and Uu is used between the UE and the AN device. interface for communication.
  • RRC radio resource control
  • the network architecture shown above is only an illustrative description, and the network architecture applicable to the embodiments of the present application is not limited thereto. Any network architecture that can realize the functions of each of the above network elements is applicable to the embodiments of the present application.
  • the network architecture shown above can also include other more network elements, such as network exposure function (NEF), and unified data storage network element (unified data repository, UDR) is not limited to this.
  • NEF network exposure function
  • UDR unified data storage network element
  • the NEF in HPLMN is recorded as home NEF (homeNEF, H-NEF), and the NEF in VPLMN is recorded as visited NEF (visited NEF, V-NEF).
  • the UDR in HPLMN is recorded as home UDR (homeUDR, H-UDR), and the UDR in VPLMN is recorded as visited UDR (visited UDR, V-UDR).
  • functions or network elements such as AMF, SMF, UPF, PCF, UDM, NSSF, and AUSF shown in Figures 1 to 4 can be understood as network elements used to implement different functions, and can, for example, be combined as needed.
  • Network slicing These network elements can be independent devices, or they can be integrated into the same device to implement different functions, or they can be network elements in hardware devices, software functions running on dedicated hardware, or platforms (for example, cloud The virtualization function instantiated on the platform), this application does not limit the specific form of the above network elements.
  • the UE may access the VPLMN through roaming.
  • HPLMN operators may deploy their own EAS at VPLMN, or third-party ECSPs may deploy their own EAS at VPLMN.
  • the existing DNS query technology it is impossible to distinguish which operator EAS belongs to.
  • the UE subscribes to the edge computing service of a third-party ECSP according to the existing DNS query technology, the EAS corresponding to the third-party ECSP in the VPLMN cannot be provided to the UE first. Therefore, how to select the EAS corresponding to a specific network (such as a third-party ECSP or HPLMN) in the VPLMN for roaming UEs is an issue worth considering.
  • This application proposes a solution to determine the EAS deployment information corresponding to the provider based on the information of the provider that provides edge computing services for the terminal device, that is, the EAS deployment information corresponding to the provider in the access network of the terminal device. Then, the session management network element configures DNS processing rules based on the EAS deployment information corresponding to the provider. In this way, when the edge application server discovers that the network element processes the DNS query message of the terminal device based on the DNS processing rules, it can provide the terminal device with the EAS of the provider. , that is, the provider's corresponding EAS in the access network of the terminal device.
  • the EAS deployment corresponding to the third-party ECSP can be found based on the identifier of the third-party ECSP.
  • SMF configures DNS processing rules based on the EAS deployment information of the third-party ECSP in PLMN#A; after EASDF receives the DNS processing rules, it can
  • the DNS processing rules process the UE's DNS query request, thereby finding the EAS corresponding to the third-party ECSP in PLMN#A for the UE, so that the UE can preferentially use the EAS corresponding to the third-party ECSP in PLMN#A.
  • the EAS deployment information corresponding to the HPLMN can be found according to the HPLMN identifier, that is, the EAS deployment information of the HPLMN in the VPLMN; thus SMF configures DNS processing rules based on the EAS deployment information of HPLMN in VPLMN; after EASDF receives the DNS processing rules, it can process the UE's DNS query request based on the DNS processing rules, thereby finding the corresponding HPLMN in VPLMN for the UE. EAS, so that the UE can preferentially use the EAS corresponding to the HPLMN in the VPLMN.
  • Figure 5 is a schematic diagram of a communication method 500 provided by an embodiment of the present application.
  • Method 500 may include the following steps.
  • the session management network element obtains provider information.
  • the provider is a provider that provides edge computing services for terminal devices;
  • the session management network element configures DNS processing rules based on the provider information and the provider's corresponding EAS deployment information.
  • the DNS processing rules are used to process DNS messages of the terminal device.
  • the EAS deployment information is provided by the provider in the access network of the terminal device. Corresponding EAS deployment information;
  • the session management network element sends DNS processing rules to the edge application server discovery network element.
  • the edge application server sends the network element to receive the DNS processing rule.
  • the edge application server sends the network element to process the DNS query message of the terminal device according to the DNS processing rules.
  • Provider information represents the information of the provider that provides edge computing services for terminal devices.
  • the provider's information may be, for example, a provider ID. It can be understood that the provider may represent the provider of EAS, or may also represent the provider of EHE, without limitation.
  • the provider includes one or more of the following: visited network (such as the UE's VPLMN), home network (such as the UE's HPLMN), and 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 be a corresponding third-party ECSP in PLMN#A, without limitation.
  • the access network of the terminal device indicates the network that currently provides services to the terminal device.
  • the access network may be a representation of the access network, such as an access PLMN ID (access PLMN ID).
  • the access network of the terminal device is denoted as PLMN#A
  • the provider that provides edge computing services for the terminal device is denoted as provider#B. It can be understood that the naming of PLMN#A and provider#B does not limit the scope of protection of the embodiments of this application.
  • the EAS deployment information corresponding to provider#B indicates the EAS deployment information corresponding to provider#B in PLMN#A.
  • the EAS deployment information corresponding to provider#B includes the following forms: for example, the EAS deployment information includes the information of provider#B (such as provider#B ID); for another example, the EAS deployment information and the information of provider#B ( For example, the EAS deployment information includes the information of provider#B (such as provider#B ID) and the information of PLMN#A (such as PLMN#A ID); for another example, the EAS deployment information Associated with provider#B's information (such as provider#B ID) and PLMN#A's information (such as PLMN#A ID).
  • the session management network element configures DNS processing rules based on the provider information and the EAS deployment information corresponding to the provider, including: the session management network element determines the EAS deployment information corresponding to the provider based on the provider information. , configure DNS processing rules based on the EAS deployment information corresponding to the provider.
  • One possible implementation method is that the session management network element requests the EAS deployment information corresponding to the provider #B from the network open network element, and then obtains the EAS deployment information corresponding to the provider #B.
  • Another possible implementation manner is that the session management network element requests multiple EAS deployment information from the network open network element, and the session management network element determines the EAS deployment information corresponding to provider #B from the multiple EAS deployment information. It can be understood that the above two methods are exemplary descriptions and are not limited thereto.
  • EAS deployment information may also include one or more of the following information: DNN, single-network slice selection assistance information (S-NSSAI), external group identifier (external group identifier)/internal Group identifier (internal group identifier), application information (such as application ID (AppID)), fully qualified domain name (full qualified domain name, FQDN).
  • the following describes two ways to determine the EAS deployment information corresponding to provider#B.
  • One possible way is to determine the EAS deployment information corresponding to provider#B based on provider#B's information (such as provider#BID). Based on this method, the EAS deployment information corresponding to provider#B can be queried through provider#B's information (such as provider#B ID).
  • the EAS deployment information corresponding to provider#B may include provider#BID, so the EAS deployment information containing the provider#BID can be determined based on provider#BID.
  • the EAS deployment information corresponding to provider#B is associated with provider#BID, so the EAS deployment information associated with provider#BID can be determined based on provider#BID.
  • Another possible way is to determine the EAS deployment information corresponding to provider #B based on the information of provider #B and PLMN #A.
  • the EAS deployment information corresponding to provider #B can also be described as the EAS deployment information corresponding to provider #B and PLMN #A, or the EAS deployment information corresponding to provider #B in PLMN #A.
  • the EAS deployment information corresponding to provider#B can be queried through the information of provider#B and PLMN#A (such as provider#B ID and PLMN#A ID).
  • the EAS deployment information corresponding to provider#B may include provider#BID and PLMN# AID, so the EAS deployment information containing the provider#BID and PLMN#AID can be determined based on the provider#BID.
  • 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) and provider#BID and PLMN#AID Association, so the EAS deployment information associated with provider#BID and PLMN#AID can be determined based on provider#BID and PLMN#AID.
  • the EAS deployment information corresponding to provider#B can include one or more of the following information: DNS server, ECS option, and EAS address.
  • the EAS registered on the DNS server is the EAS corresponding to provider#B in PLMN#A.
  • the DNS server may be a C-DNS server (such as the DNS server deployed in HPLMN) or an L-DNS server (such as the DNS server deployed in PLMN#A).
  • the EAS corresponding to the ECS option is the EAS corresponding to provider#B in PLMN#A.
  • the EAS address is the EAS address corresponding to provider#B in PLMN#A.
  • the EAS address is the EAS IP address.
  • the EAS IP address is a few examples.
  • Example 1 the EAS deployment information corresponding to provider#B includes the C-DNS server.
  • SMF configures DNS processing rules for the terminal device based on the EAS deployment information corresponding to provider#B.
  • the DNS processing rules configured by SMF for EASDF include the C-DNS server.
  • method 500 also includes: EASDF sending a query message of the DNS of the terminal device to the C-DNS server (that is, the C-DNS server included in the EAS deployment information corresponding to provider #B), and the C-DNS server Process the DNS query message 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 EASDF the address of the EAS corresponding to provider#B in PLMN#A. In this way, EASDF can provide the terminal device with the EAS corresponding to provider #B in PLMN #A.
  • Example 1 As an example, the structure applicable to Example 1 is introduced below in conjunction with Figure 6.
  • FIG. 6 is a schematic diagram of a network architecture provided by an embodiment of the present application.
  • PLMN#A is VPLMN and provider#B is HPLMN information.
  • EASDF receives the DNS query message from the roaming UE, it can send a request to the C-DNS server corresponding to HPLMN according to the DNS processing rules obtained from SMF. (i.e. provider#B The C-DNS server included in the corresponding EAS deployment information) sends the UE's DNS query.
  • EASDF receives the DNS query message of the UE (ie, ordinary UE, or non-roaming UE), it can send the DNS query of the UE to the C-DNS server according to the DNS processing rules obtained from the SMF.
  • the specific process will be introduced later in conjunction with method 900.
  • Example 2 the EAS deployment information corresponding to provider#B includes ECS option.
  • SMF configures DNS processing rules for the terminal device based on the EAS deployment information corresponding to provider#B.
  • the DNS processing rules configured by SMF for EASDF include the ECS option.
  • method 500 also includes: EASDF adding the ECS option (that is, the ECS option included in the EAS deployment information corresponding to provider #B) in the DNS query message of the terminal device.
  • EASDF can send a DNS query message for adding the ECS option to a DNS server (such as a C-DNS server), and the DNS server processes the DNS query message for adding the ECS option. Since the EAS corresponding to the ECS option is the EAS corresponding to provider#B in PLMN#A, the DNS response returned by the DNS server to EASDF carries the address of the EAS corresponding to the ECS option (that is, provider#B is in PLMN# The address of the corresponding EAS in A). In this way, EASDF can provide the terminal device with the EAS corresponding to provider #B in PLMN #A.
  • the architecture shown in Figure 6 can also be used for the implementation of Example 2. Assume that PLMN#A is VPLMN and provider#B is HPLMN information. Under the architecture shown in Figure 6, after EASDF receives the DNS query message from the roaming UE, it can process the DNS query message in the DNS query message based on the DNS processing rules obtained from SMF. Add the ECS option corresponding to HPLMN (that is, the ECS option included in the EAS deployment information corresponding to provider#B).
  • EASDF After EASDF receives the DNS query message from the UE (that is, ordinary UE, or non-roaming UE), it can add the ECS option to the DNS query message and send it to the C-DNS server according to the DNS processing rules obtained from the SMF, or it can also directly Forward the UE's DNS query message to the L-DNS server.
  • the specific process will be introduced later in conjunction with method 1000.
  • Example 3 the EAS deployment information corresponding to provider#B includes L-DNS server.
  • SMF configures DNS processing rules for the terminal device based on the EAS deployment information corresponding to provider#B.
  • the DNS processing rules configured by SMF for EASDF include the L-DNS server.
  • method 500 also includes: EASDF sending a query message of the DNS of the terminal device to the L-DNS server (that is, the L-DNS server included in the EAS deployment information corresponding to provider #B), and the L-DNS server Process the DNS query message 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 EASDF the address of the EAS corresponding to provider#B in PLMN#A. In this way, EASDF can provide the terminal device with the EAS corresponding to provider #B in PLMN #A.
  • the L-DNS server that is, the L-DNS server included in the EAS deployment information corresponding to provider #B
  • the L-DNS server Process the DNS query message 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 EASDF the address of the EAS corresponding to provider
  • Example 3 As an example, the structure applicable to Example 3 is introduced below in conjunction with Figure 7.
  • FIG. 7 is a schematic diagram of a network architecture provided by another embodiment of the present application.
  • PLMN#A is VPLMN and provider#B is HPLMN information.
  • EASDF receives the DNS query message from the roaming UE, it can send a request to the L-DNS server corresponding to HPLMN according to the DNS processing rules obtained from SMF. (that is, the L-DNS server included in the EAS deployment information corresponding to provider #B) sends the DNS query of the UE.
  • EASDF receives the DNS query message of the UE (ie, ordinary UE, or non-roaming UE), it can send the DNS query of the UE to the L-DNS server according to the DNS processing rules obtained from the SMF.
  • the specific process will be introduced later in conjunction with method 1100.
  • Example 4 the EAS deployment information corresponding to provider#B includes the EAS address.
  • SMF configures DNS processing rules for the terminal device based on the EAS deployment information corresponding to provider#B.
  • the DNS processing rules configured by SMF for EASDF include the EAS address.
  • the method 500 further includes: EASDF selects an address belonging to the EAS address (ie, the EAS address included in the EAS deployment information corresponding to provider #B) in response to a query of the DNS of the terminal device.
  • EASDF obtains the address of at least one EAS from the DNS server;
  • EASDF can select part or all of the EAS addresses from the addresses of at least one EAS based on the EAS address, and the part or all of the EAS addresses belong to the EAS address.
  • EASDF can provide the terminal device with the EAS corresponding to provider #B in PLMN #A.
  • Example 4 As an example, the structure applicable to Example 4 is introduced below in conjunction with Figure 8.
  • FIG 8 is a schematic diagram of a network architecture provided by another embodiment of the present application.
  • PLMN#A is VPLMN and provider#B is HPLMN information.
  • EASDF receives the DNS query message from the roaming UE, it can query the EAS IP address from the L-DNS server (for example, including the EAS IP address corresponding to HPLMN and the EAS IP address corresponding to the VPLMN), and based on the DNS processing rules obtained from the SMF, filter (or select) the EAS IP address corresponding to the HPLMN from the queried EAS IP address.
  • L-DNS server for example, including the EAS IP address corresponding to HPLMN and the EAS IP address corresponding to the VPLMN
  • filter or select
  • EASDF After EASDF receives the DNS query message from the UE (that is, ordinary UE, or non-roaming UE), it can query the L-DNS server for the EAS IP address according to the DNS processing rules obtained from the SMF, and return the queried EAS IP to the UE. address.
  • the specific process will be introduced later in conjunction with method 1200.
  • each piece of information is introduced separately above, and it can be understood that each piece of the above information can be used alone or in combination. An example of a possible combination is described below.
  • Example 5 the EAS deployment information corresponding to provider#B includes C-DNS server and ECS option.
  • SMF configures DNS processing rules for the terminal device based on the EAS deployment information corresponding to provider#B.
  • the DNS processing rules configured by SMF for EASDF include the C-DNS server and ECS option.
  • method 500 also includes: EASDF adding the ECS option (that is, the ECS option included in the EAS deployment information corresponding to provider #B) in the DNS query message of the terminal device. Further, EASDF can send a request to the C-DNS server (That is, the C-DNS server included in the EAS deployment information corresponding to provider#B) sends a DNS query message to add the ECS option, and the C-DNS server processes the DNS query message to add the ECS option.
  • EASDF can send a request to the C-DNS server (That is, the C-DNS server included in the EAS deployment information corresponding to provider#B) sends a DNS query message to add the ECS option, and the C-DNS server processes the DNS query message to add the ECS option.
  • the session management network element obtains the 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 can determine the information of provider #B based on any of the following information: the home network of the terminal device, the terminal device or the subscription information of the terminal device, the terminal device list provided by provider #B including the terminal device, provider #B and Agreement between PLMN#A.
  • the session management network element can determine the EAS deployment information corresponding to provider #B based on any of the above information. That is, the session management network element can determine provider #B based on any of the above information, and then query the corresponding EAS deployment information of provider #B. EAS deployment information.
  • Example 1 SMF determines the information of provider #B based on the UE or the UE's subscription information.
  • the subscription information of the UE may include provider#B information (such as provider#B ID).
  • provider#B information such as provider#B ID
  • the subscription information of the UE includes information that the service of provider #B can be used, so provider #B can be determined based on this information.
  • the UE's subscription information includes that PLMN#A has a cooperative relationship with provider#B (or alliance relationship), allowing the UE of PLMN #A to use the EAS of provider #B, so provider #B can be determined based on this information.
  • SMF determines the information of provider#B based on the UE ID.
  • the UE ID may be: the UE's user permanent identifier (subscription permanent identifier, SUPI) or permanent equipment identifier (permanent equipment identifier, PEI).
  • SMF can obtain the UE's provider#B ID (such as HPLMN ID, or VPLMN ID) by querying AMF.
  • AMF can obtain the UE's SUPI during the UE registration process.
  • AMF can determine the UE's provider#B ID based on the UE's SUPI.
  • AMF can send the UE's provider#B ID to SMF based on the SMF's request; or during session establishment During the process, AMF sends the UE's provider#B ID to SMF.
  • SMF parses the UE's SUPI and then obtains the UE's provider#B ID.
  • SMF can obtain the ECSP ID subscribed by the UE by querying UDR or NEF.
  • the AF corresponding to ECSP sends EAS subscription information to UDR through NEF, and UDR stores the EAS subscription information.
  • the EAS subscription information includes: the ECSP ID corresponding to EAS, and the UE ID subscribing to ECSP; SMF determines the UE ID, and Query the ECSP subscribed by the UE to the UDR through NEF; UDR determines the ECSP ID subscribed by the UE based on the locally stored EAS subscription information, and sends the ECSP ID subscribed by the UE to SMF through NEF.
  • the EAS subscription information also includes DNN and/or S-NSSAI.
  • the EAS subscription information can be carried in the AF request (AF request) message.
  • the SMF can also determine the ECSP ID that provides edge computing services to the UE according to any of the following methods.
  • Method 1 SMF determines the ECSP ID that provides edge computing services to the UE from the multiple ECSP IDs based on the multiple ECSP IDs subscribed by the UE and the priorities of the multiple ECSPs.
  • the priorities of multiple ECSPs may be determined based on the ID sizes of the multiple ECSPs; for another example, the priorities of multiple ECSPs may be determined based on the frequency of use of the multiple ECSPs.
  • Method 2 Based on the multiple ECSP IDs subscribed by the UE, the SMF selects an ECSP from any of the multiple ECSPs (either according to the agreement or according to the pre-agreement) as the ECSP that provides edge computing services to the UE.
  • Example 2 SMF determines provider #B based on the information that the UE includes in the UE list provided by provider #B.
  • the information of provider#B can be determined.
  • the UE is a UE of provider #B
  • the provider #B can provide edge computing services for the UE, and then the provider #B can be determined for the UE.
  • the provider #B can be determined for the UE.
  • Example 3 SMF determines the information of provider #B based on the agreement between provider #B and PLMN #A.
  • the agreement between provider #B and PLMN #A can indicate that provider #B and PLMN #A have a cooperative relationship or alliance relationship. If there is a cooperative relationship between provider #B and 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, then provider #B can be determined for the UE. .
  • provider#B can provide edge computing services for the UE, and then provider#B can be determined for the UE. . specific For examples, please refer to the previous example 1 and will not be repeated here.
  • Example 4 SMF determines the information of provider #B based on HPLMN.
  • provider #B can be determined for the UE of HPLMN. For specific examples, please refer to the previous example 1 and will not be described again here.
  • Example 1 assume that provider#B is the HPLMN of the UE and PLMN#A is the VPLMN of the UE.
  • Example 2 assume that provider#B is the VPLMN of the UE and PLMN#A is the VPLMN of the UE.
  • Example 3 assuming provider#B is a third-party ECSP and PLMN#A is the VPLMN of the UE.
  • provider #B can also be other PLMN, which is not limited.
  • Example 1 assume that provider#B is the HPLMN of the UE and PLMN#A is the VPLMN of the UE.
  • Example 2 assume that provider#B is the VPLMN of the UE and PLMN#A is the VPLMN of the UE.
  • Example 3 assuming provider#B is a third-party ECSP and PLMN#A is the VPLMN of the UE.
  • provider #B can also be other PLMN, which is not limited.
  • Figure 9 is a schematic flow chart of a communication method 900 provided by an embodiment of the present application.
  • the method 900 can be used to implement a solution such as the method 500 (such as Example 1 in the method 500).
  • the method 900 can be used in a scenario where PLMN#A, provider#B, and the C-DNS server are associated.
  • method 900 may be implemented through the architecture shown in FIG. 6 .
  • Method 900 may include the following steps.
  • AF sends EAS deployment information to NEF.
  • AF sends a Nnef interface EAS deployment establishment request (Nnef_EASDeployment_Create Request) to NEF, and the Nudr_EASDeployment_Create Request includes EAS deployment information.
  • AF sends an Nnef interface EAS deployment update request (Nnef_EASDeployment_Update Request) to NEF, and the Nnef_EASDeployment_Update Request includes EAS deployment information.
  • the EAS deployment information is the EAS deployment information corresponding to provider #B.
  • the EAS deployment information includes provider #B ID and C-DNS server #B. Among them, the EAS registered on C-DNS server #B is provider #B in PLMN #A. The corresponding EAS in . It can be understood that C-DNS server #B is named for differentiation, and its naming does not limit the protection scope of the embodiments of the present application.
  • the EAS deployment information also includes the PLMN#A ID.
  • provider#B ID can be any of the following: HPLMN ID, VPLMN ID, ECSP ID. It can be understood that provider#BID can also be carried in the ID of a certain network element in the PLMN (such as HPLMN, or VPLMN) (such as the ID of the SMF). Through the ID of a certain network element, the PLMN can also be determined, that is, determined PLMNID. Regarding provider #B, please refer to the relevant description in method 500, which will not be described again here.
  • the EAS deployment information also includes at least one of the following: DNN, S-NSSAI, or the ECS option corresponding to DNAI.
  • DNN#1 it means that the EAS deployment information is the EAS deployment information corresponding to DNN#1.
  • S-NSSAI#1 it means that the EAS deployment information is the EAS deployment information corresponding to S-NSSAI#1.
  • NEF processes EAS deployment information.
  • NEF processes EAS deployment information, including: NEF performs authorization verification on EAS deployment information. If NEF successfully authenticates the EAS deployment information, NEF can send the EAS deployment information to the UDR. If NEF fails to authorize the EAS deployment information to verify, a possible implementation method is that NEF can notify the AF that the EAS deployment information authorization verification fails. In the embodiment of this application, it is assumed that NEF successfully authenticates the EAS deployment information.
  • NEF sends EAS deployment information to UDR.
  • NEF sends a Nudr interface data management (DM) establishment request (Nudr_DM_Create Request) to UDR.
  • the Nudr_DM_Create Request includes EAS deployment information.
  • NEF sends a Nudr interface DM update request (Nudr_DM_Update Request) to UDR.
  • the Nudr_DM_Update Request includes EAS deployment information.
  • UDR After UDR receives the EAS deployment information, it can store the EAS deployment information. If UDR successfully stores EAS deployment information, it can return a storage response to NEF to notify NEF that UDR has successfully stored EAS deployment information.
  • UDR sends storage response to NEF.
  • step 903 NEF sends a Nudr_DM_Create Request to UDR, then in step 904, UDR returns a Nudr interface DM establishment response (Nudr_DM_CreateResponse) to NEF.
  • step 903 NEF sends a Nudr_DM_Update Request to UDR, then in step 904, UDR returns a Nudr interface DM update response (Nudr_DM_UpdateResponse) to NEF.
  • NEF sends an EAS deployment information response to AF.
  • NEF returns the Nnef interface EAS deployment establishment response (Nnef_EASDeployment_CreateResponse) to AF.
  • NEF returns the Nnef interface EAS deployment update response (Nnef_EASDeployment_UpdateResponse) to AF.
  • the UE initiates the session establishment process.
  • This application does not limit the specific session establishment process. For example, it can be as follows: after receiving the session establishment request from the UE, the AMF selects the SMF that serves the session; after the SMF receives the session establishment request, it selects the UPF that serves the session and creates an N4 session. , and send user plane tunnel information. If the session is successfully established, the network returns a session establishment response to the UE, and then messages can be transmitted through the session.
  • step 906 the UE can initiate the establishment process of the HR session or the establishment process of the LBO session without limitation.
  • step 906 is not limited to executing the complete session establishment process. Multiple steps after step 906 can reuse (or reuse, or continue to execute) the session establishment process, or in other words, multiple steps after step 906 can be Executed during the session establishment process.
  • SMF requests EAS deployment information from NEF.
  • SMF receives a session establishment request message from the UE, and the session establishment request message includes: S-NSSAI, DNN, and PDU session ID; SMF sends a request message to NEF, and the request message includes DNN and/or S- NSSAI, this request message is used to request (or query, or subscribe) EAS deployment information corresponding to DNN and/or S-NSSAI.
  • a possible implementation method is for SMF to request EAS deployment information from NEF, including: SMF sends an Nnef interface EAS deployment subscription request (Nnef_EASDeployment_Subscribe Request) to NEF.
  • the Nnef_EASDeployment_Subscribe Request includes DNN and/or S-NSSAI.
  • the Nnef_EASDeployment_Subscribe Request is used to Request EAS deployment information corresponding to DNN and/or S-NSSAI.
  • SMF when SMF requests EAS deployment information from NEF, it can also carry provider#B ID. This request is used to request EAS deployment information corresponding to provider#B.
  • SMF when SMF requests EAS deployment information from NEF, it can also carry provider#B ID and PLMN#A ID. This request is used to request the EAS deployment information corresponding to provider#B in PLMN#A.
  • provider#B ID refer to the description in method 500 and will not be repeated here.
  • NEF obtains EAS deployment information from UDR.
  • NEF requests (or subscribes to, or queries) the EAS deployment information corresponding to DNN and/or S-NSSAI from UDR.
  • UDR stores the EAS deployment information. Therefore, in step 908, after receiving the request from NEF, the UDR can query the EAS deployment information corresponding to DNN and/or S-NSSAI from the stored EAS deployment information.
  • NEF sends EAS deployment information to SMF.
  • NEF After NEF obtains the EAS deployment information corresponding to DNN and/or S-NSSAI from UDR, it sends the EAS deployment information to SMF.
  • SMF selects EASDF.
  • SMF selects EASDF it can refer to one or more of the following information: S-NSSAI, the location of EASDF, and DNAI. It can be understood that when SMF selects EASDF, it can refer to one or more of the above information, or it can also refer to other information not listed, which is not limited by this application.
  • SMF selects EASDF, which can be achieved in at least one of the following ways.
  • SMF can select EASDF based on local configuration.
  • SMF obtains EASDF from the network repository function (NRF). For example, SMF sends a request message to NRF, and NRF returns one or more EASDF information (including address, identification, etc.) to SMF. If NRF returns multiple EASDFs to SMF, SMF can select one from them.
  • NRF network repository function
  • the method for SMF to select EASDF can be the method for SMF to select EASDF in non-roaming scenarios, or the method for SMF to select EASDF that will appear in the future, and there is no restriction on this.
  • SMF configures DNS processing rules for EASDF based on the EAS deployment information.
  • the DNS processing rules include C-DNS server #B.
  • EAS deployment information received by SMF from NEF is the EAS deployment information corresponding to provider #B
  • SMF can directly configure DNS processing rules for EASDF based on the EAS deployment information corresponding to provider #B.
  • the EAS deployment information received by SMF from NEF is DNN and/or S-NSSAI pairs.
  • the EAS deployment information corresponding to the corresponding EAS deployment information then SMF can determine the EAS deployment information corresponding to provider#B based on provider#B ID, or SMF can determine the EAS deployment information corresponding to provider#B based on provider#BID and PLMN#AID , and configure DNS processing rules for EASDF based on the EAS deployment information corresponding to provider#B.
  • step 911 includes: SMF generates DNS processing rules based on the EAS deployment information corresponding to provider #B, and sends the DNS processing rules to EASDF.
  • SMF sends a Neasdf interface context creation request (Neasdf_context_createrequest) to EASDF, which Neasdf_context_createrequest includes DNS processing rules;
  • EASDF returns a Neasdf interface context creation response (Neasdf_context_create response) to SMF.
  • DNS processing rules can be used to process DNS messages, such as DNS messages related to the UE.
  • DNS processing rules can be used to process DNS query messages.
  • DNS processing rules may include one or more of the following information: FQDN range, ECS option, C-DNS server #B address, DNS forwarding rules.
  • ECS option can be used to characterize the location information of the UE.
  • DNS forwarding rules which may also be called forwarding rules or data plane forwarding rules, can be used by EASDF to process DNS messages from the UE accordingly. For example, when the FQDN contained in the DNS query sent by the UE matches the FQDN range in the DNS processing rule, based on the DNS forwarding rule, EASDF adds an ECS option to the DNS query. For another example, when the FQDN contained in the DNS query sent by the UE matches the FQDN range in the DNS processing rules, based on the DNS forwarding rules, EASDF forwards the DNS query (such as the DNS query after adding the ECS option) to the DNS server.
  • the DNS forwarding rules such as the DNS query after adding the ECS option
  • C-DNS server #B represents the C-DNS server in the EAS deployment information corresponding to provider #B.
  • the UE can complete the session establishment.
  • UE sends DNS query to EASDF.
  • the UE sends the DNS query message to H-EASDF through the user plane, RAN and UPF.
  • the DNS query may include the FQDN corresponding to the application that the UE wants to access.
  • EASDF processes DNS query according to DNS processing rules.
  • EASDF After EASDF receives the DNS query, it can process the DNS query according to the DNS processing rules received from SMF. EASDF processes the DNS query according to the DNS processing rules, which may include: EASDF sends the UE's DNS query to the C-DNS server #B included in the DNS processing rules.
  • EASDF detects that the FQDN contained in the UE's DNS query matches the FQDN contained in the DNS processing rules based on the DNS processing rules, then EASDF adds the ECS option to the DNS query based on the DNS processing rules and sends it to C-DNS.
  • Server #B sends the DNS query with the ECS option added.
  • EASDF sends a DNS query containing the ECS option to C-DNS server #B.
  • EASDF adds the ECS option in the DNS query
  • the embodiment of this application mainly takes EASDF adding ECS option in DNS query as an example.
  • EASDF processes the UE's DNS query
  • C-DNS server #B included in the DNS processing rules
  • C-DNS server #B provides provider #B
  • the corresponding EAS information is applicable to the embodiments of this application.
  • C-DNS server #B returns a DNS response (DNS response) to EASDF.
  • the C-DNS server can send a DNS response to EASDF, which can contain the EAS information (such as EAS IP address) corresponding to provider#B. Combine the three scenarios.
  • provider#B is HPLMN ID.
  • the EAS corresponding to provider#B indicates the EAS corresponding to HPLMN.
  • provider#B is VPLMN ID.
  • the EAS corresponding to provider#B indicates the EAS corresponding to VPLMN.
  • provider#B is the ECSP ID.
  • the EAS corresponding to provider#B indicates the EAS corresponding to ECSP.
  • EASDF returns the EAS information corresponding to provider #B to the UE.
  • the UE can obtain the EAS information corresponding to provider#B.
  • method 900 can be used for HR roaming (for example, the UE's session in step 906 is an HR session), or for LBO roaming (for example, the UE's session in step 906 is an LBO session).
  • HR roaming for example, the UE's session in step 906 is an HR session
  • LBO roaming for example, the UE's session in step 906 is an LBO session.
  • it can Adaptive adjustments are made based on different roaming methods, and there are no restrictions on this.
  • the UE's session is an LBO session.
  • PLMN #A can be considered as the VPLMN of the UE
  • provider #B can be considered as the HPLMN of the UE.
  • the UE can access the MEC service through the UPF (i.e. V-UPF) corresponding to PLMN#A.
  • the SMF (i.e. V-SMF) in PLMN#A is configured for the UE. DNS processing rules.
  • V-SMF in PLMN#A configures DNS processing rules for the UE, it can be based on: the UE's access network is PLMN#A (i.e. VPLMN), and the PLMN that provides edge computing services for the UE is provider#B (i.e. HPLMN), search for the corresponding EAS deployment information, and then you can find the C-DNS server #B corresponding to provider#B (i.e. HPLMN) in PLMN#A (i.e. VPLMN), and then you can find provider#B for the UE. (i.e. HPLMN) corresponding EAS in PLMN#A (i.e. VPLMN).
  • PLMN#A i.e. VPLMN
  • provider#B i.e. HPLMN
  • the UE's session is an HR session.
  • PLMN #A can be considered as the VPLMN of the UE
  • provider #B can be considered as the HPLMN of the UE.
  • the SMF (ie H-SMF) in provider #B configures DNS processing rules for the UE.
  • the SMF (i.e. H-SMF) in provider#B configures DNS processing rules for the UE, it can be based on: the UE's access network is PLMN#A (i.e. VPLMN), and the PLMN that provides edge computing services for the UE is provider#B (i.e.
  • HPLMN search for the corresponding EAS deployment information, and then you can find the C-DNS server #B corresponding to provider#B (i.e. HPLMN) in PLMN#A (i.e. VPLMN), and then you can find provider#B for the UE. (i.e. HPLMN) corresponding EAS in PLMN#A (i.e. VPLMN).
  • SMF (such as V-SMF in scenario 1, and H-SMF in scenario 2) can be based on: UE Determine provider #B by any one of the home network, UE or UE's subscription information, the UE list provided by provider #B including the UE, or the agreement between provider #B and PLMN #A, and then obtain the provider #B Corresponding EAS deployment information.
  • SMF (such as V-SMF in scenario 1, and H-SMF in scenario 2) can also be provided based on the UE's home network, the UE or the UE's subscription information, and provider #B
  • the UE list includes any one of the UEs or the agreement between provider #B and PLMN #A to determine provider #B, and combine it with PLMN #A to obtain the EAS deployment information corresponding to provider #B.
  • PLMN #A to obtain the EAS deployment information corresponding to provider #B.
  • the EAS deployment information provided by the AF may include C-DNS servers corresponding to different PLMNs or different ECSPs in PLMN#A.
  • the C-DNS servers registered on the C-DNS servers may be corresponding to the corresponding PLMN or ECSP in PLMN#A.
  • EAS When SMF configures DNS processing rules for EASDF during the session establishment process, it can carry the information of the C-DNS server corresponding to provider#B in the DNS processing rules, which in turn allows EASDF to send the UE's DNS query to the C-DNS server. deal with.
  • provider#B is the HPLMN ID
  • the UE can be made to preferentially use the EAS corresponding to the HPLMN in PLMN#A
  • provider#B is the VPLMN ID
  • the UE can be made to preferentially use the EAS corresponding to the VPLMN in PLMN#A
  • provider#B is an ECSP ID
  • the UE can be made to preferentially use the EAS corresponding to ECSP in PLMN#A.
  • Figure 10 is a schematic flow chart of a communication method 1000 provided by an embodiment of the present application.
  • This method 1000 can be used to implement a solution such as method 500 (such as Example 2 in method 500).
  • method 1000 can be used in a scenario where PLMN#A, provider#B, and ECS option are associated.
  • method 1000 may be implemented through the architecture shown in FIG. 6 .
  • Method 1000 may include the following steps.
  • AF sends EAS deployment information to NEF.
  • Step 1001 is similar to step 901, except that in step 1001, the EAS deployment information includes provider#B ID and ECS option#B, where the EAS corresponding to ECS option#B is provider#B in PLMN#A Corresponding EAS. It can be understood that ECS option#B is named for differentiation, and its naming does not limit the protection scope of the embodiments of this application. Optionally, the EAS deployment information also includes the PLMN#A ID.
  • NEF processes EAS deployment information.
  • NEF sends EAS deployment information to UDR.
  • UDR sends storage response to NEF.
  • NEF sends an EAS deployment information response to AF.
  • the UE initiates the session establishment process.
  • SMF requests EAS deployment information from NEF.
  • NEF obtains EAS deployment information from UDR.
  • NEF sends EAS deployment information to SMF.
  • SMF selects EASDF.
  • steps 1002 to 1010 are similar to steps 902 to 910, and will not be described again here.
  • SMF configures DNS processing rules for EASDF based on the EAS deployment information.
  • the DNS processing rules include ECS option#B.
  • step 1011 includes: SMF generates DNS processing rules based on EAS deployment information, and sends the DNS processing rules to EASDF. For example, SMF sends Neasdf_context_createrequest to EASDF, which Neasdf_context_createrrequest includes DNS processing rules; EASDF returns Neasdf_context_create response to SMF.
  • DNS processing rules can be used to process DNS messages, such as DNS messages related to the UE.
  • DNS processing rules can be used to process DNS query messages.
  • DNS processing rules can include one or more of the following information: FQDN range, ECS option#B, L-DNS server address, DNS forwarding rules.
  • FQDN range FQDN range
  • ECS option#B L-DNS server address
  • DNS forwarding rules For the meaning of each information, you can refer to the description in step 911. Here we mainly introduce ECS option #B.
  • the EAS corresponding to ECS option#B is the EAS corresponding to provider#B in PLMN#A.
  • UE sends DNS query to EASDF.
  • Step 1012 is similar to step 912 and will not be described again here.
  • EASDF processes DNS query according to DNS processing rules.
  • EASDF After EASDF receives the DNS query, it can process the DNS query according to the DNS processing rules received from SMF. EASDF processes DNS query according to DNS processing rules, which can include: EASDF adds ECS option#B to DNS query. By adding the ECS option#B to the DNS query, you can query the EAS provided by provider#B.
  • EASDF detects that the FQDN contained in the UE's DNS query matches the FQDN contained in the DNS processing rules based on the DNS processing rules, then EASDF adds ECS option #B to the DNS query based on the DNS processing rules, and then adds ECS option #B to the DNS query.
  • the DNS server sends the DNS query after adding ECS option#B.
  • EASDF sends a DNS query containing ECS option#B to the C-DNS server.
  • the C-DNS server returns a DNS response to EASDF.
  • the C-DNS server can send a DNS response to EASDF, which can contain the EAS information (such as EAS IP address) corresponding to provider#B. Combine the three scenarios.
  • provider#B is HPLMN ID.
  • the EAS corresponding to provider#B indicates the EAS corresponding to HPLMN.
  • provider#B is VPLMN ID.
  • the EAS corresponding to provider#B indicates the EAS corresponding to VPLMN.
  • provider#B is the ECSP ID.
  • the EAS corresponding to provider#B indicates the EAS corresponding to ECSP.
  • EASDF returns the EAS information corresponding to provider #B to the UE.
  • the UE can obtain the EAS information corresponding to provider#B.
  • method 1000 can be used for HR roaming (for example, the UE's session in step 1006 is an HR session), or for LBO roaming (for example, the UE's session in step 1006 is an LBO session).
  • HR roaming for example, the UE's session in step 1006 is an HR session
  • LBO roaming for example, the UE's session in step 1006 is an LBO session.
  • it can Adaptive adjustments are made based on different roaming methods, and there are no restrictions on this.
  • the UE's session is an LBO session.
  • PLMN #A can be considered as the VPLMN of the UE
  • provider #B can be considered as the HPLMN of the UE.
  • the UE can access the MEC service through the UPF (ie V-UPF) corresponding to PLMN #A.
  • the SMF i.e. V-SMF
  • the SMF configures DNS processing rules for the UE, it can be based on: the UE's access network is PLMN#A (i.e.
  • VPLMN PLMN that provides edge computing services for the UE
  • provider#B i.e. HPLMN
  • Find the corresponding EAS deployment information and then you can find the ECS option#B corresponding to provider#B (that is, HPLMN) in PLMN#A (that is, VPLMN), and then you can find the provider#B (that is, HPLMN) in PLMN# for the UE.
  • the corresponding EAS in A that is, VPLMN).
  • the UE's session is an HR session.
  • PLMN #A can be considered as the VPLMN of the UE
  • provider #B can be considered as the HPLMN of the UE.
  • the UE can access the MEC service through the UPF (ie H-UPF) corresponding to provider #B.
  • the SMF i.e. H-SMF
  • provider#B configures DNS processing rules for the UE, it can be based on: the UE's access network is PLMN#A (i.e. VPLMN), and the PLMN that provides edge computing services for the UE is provider#B (i.e.
  • HPLMN HPLMN
  • HPLMN HPLMN
  • PLMN#A i.e. VPLMN
  • provider#B i.e. provider#B
  • EAS EAS in PLMN#A (i.e. VPLMN).
  • the SMF (such as V-SMF in scenario 1, and H-SMF in scenario 2) can be based on: the home network of the UE, the UE or the UE's subscription information, and the information provided by provider #B.
  • the UE list includes any one of the UE or the agreement between provider #B and PLMN #A to determine the provider #B, and then obtain the EAS deployment information corresponding to the provider #B.
  • SMF (such as V-SMF in scenario 1, and H-SMF in scenario 2) can also be provided based on the UE's home network, the UE or the UE's subscription information, and provider #B
  • the UE list includes any one of the UEs or the agreement between provider #B and PLMN #A to determine provider #B, and combine it with PLMN #A to obtain the EAS deployment information corresponding to provider #B.
  • PLMN #A to obtain the EAS deployment information corresponding to provider #B.
  • the EAS deployment information provided by the AF may include ECS options corresponding to different PLMNs or different ECSPs in PLMN#A.
  • SMF configures DNS processing rules for EASDF during the session establishment process, it can carry the ECS option information corresponding to provider#B in the DNS processing rules, which in turn allows EASDF to add the ECS option in the UE's DNS query.
  • provider#B is the HPLMN ID
  • the UE can be made to preferentially use the EAS corresponding to the HPLMN in PLMN#A
  • provider#B is the VPLMN ID
  • the UE can be made to preferentially use the EAS corresponding to the VPLMN in PLMN#A
  • provider#B is an ECSP ID
  • the UE can be made to preferentially use the EAS corresponding to ECSP in PLMN#A.
  • Figure 11 is a schematic flow chart of a communication method 1100 provided by an embodiment of the present application.
  • the method 1100 can be used to implement a solution such as the method 500 (such as Example 3 in the method 500).
  • the method 1100 can be used in a scenario where PLMN#A, provider#B, and the L-DNS server are associated.
  • method 1100 may be implemented through the architecture shown in FIG. 7 .
  • Method 1100 may include the following steps.
  • AF sends EAS deployment information to 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 the EAS registered on L-DNS server #B is provider#B Corresponding EAS in PLMN#A. It can be understood that L-DNS server #B is named for differentiation, and its naming does not limit the protection scope of the embodiments of the present application.
  • the EAS deployment information also includes the PLMN#A ID.
  • NEF processes EAS deployment information.
  • NEF sends EAS deployment information to UDR.
  • UDR sends storage response to NEF.
  • NEF sends an EAS deployment information response to AF.
  • the UE initiates the session establishment process.
  • SMF requests EAS deployment information from NEF.
  • NEF obtains EAS deployment information from UDR.
  • NEF sends EAS deployment information to SMF.
  • SMF selects EASDF.
  • steps 1102 to 1110 are similar to steps 902 to 910, and will not be described again here.
  • SMF configures DNS processing rules for EASDF based on the EAS deployment information.
  • the DNS processing rules include L-DNS server #B.
  • step 1111 includes: SMF generates DNS processing rules based on EAS deployment information, and sends the DNS processing rules to EASDF. For example, SMF sends Neasdf_context_createrequest to EASDF, which Neasdf_context_createrequest includes DNS processing rules; EASDF returns Neasdf_context_create response to SMF.
  • DNS processing rules can be used to process DNS messages, such as DNS messages related to the UE.
  • DNS processing rules can be used to process DNS query messages.
  • DNS processing rules may include one or more of the following information: FQDN range, ECS option, L-DNS server #B address, DNS forwarding rules.
  • FQDN range FQDN range
  • ECS option ECS option
  • L-DNS server #B address e.g., SMTP address
  • DNS forwarding rules
  • the EAS registered on L-DNS server #B is the EAS corresponding to provider #B in PLMN #A.
  • UE sends DNS query to EASDF.
  • Step 1112 is similar to step 912 and will not be described again here.
  • EASDF processes DNS query according to DNS processing rules.
  • EASDF After EASDF receives the DNS query, it can process the DNS query according to the DNS processing rules received from SMF. EASDF processes DNS query according to DNS processing rules, which may include: EASDF sends UE's DNS query to L-DNS server #B included in the processing rules.
  • EASDF determines the address of L-DNS server #B based on the DNS processing rules and sets the UE's DNS query is sent to the L-DNS server #B.
  • EASDF sends DNS query to L-DNS server #B.
  • L-DNS server #B returns a DNS response to EASDF.
  • the L-DNS server can send a DNS response to EASDF, which can contain the EAS information (such as EAS IP address) corresponding to provider#B. Combine the three scenarios.
  • provider#B is HPLMN ID.
  • the EAS corresponding to provider#B indicates the EAS corresponding to HPLMN.
  • provider#B is VPLMN ID.
  • the EAS corresponding to provider#B indicates the EAS corresponding to VPLMN.
  • provider#B is the ECSP ID.
  • the EAS corresponding to provider#B represents ECSP Corresponding EAS.
  • EASDF returns the EAS information corresponding to provider #B to the UE.
  • the UE can obtain the EAS information corresponding to provider#B.
  • method 1100 can be used for HR roaming (for example, the UE's session in step 1106 is an HR session), or for LBO roaming (for example, the UE's session in step 1106 is an LBO session).
  • HR roaming for example, the UE's session in step 1106 is an HR session
  • LBO roaming for example, the UE's session in step 1106 is an LBO session.
  • it can Adaptive adjustments are made based on different roaming methods, and there are no restrictions on this.
  • the UE's session is an LBO session.
  • PLMN #A can be considered as the VPLMN of the UE
  • provider #B can be considered as the HPLMN of the UE.
  • the UE can access the MEC service through the UPF (ie V-UPF) corresponding to PLMN #A.
  • the SMF i.e. V-SMF
  • the SMF configures DNS processing rules for the UE, it can be based on: the UE's access network is PLMN#A (i.e.
  • VPLMN the PLMN that provides edge computing services for the UE is provider#B (i.e. HPLMN), search for the corresponding EAS deployment information, and then you can find the L-DNS server #B corresponding to provider #B (i.e. HPLMN) in PLMN #A (i.e. VPLMN), and then you can find provider #B for the UE. (i.e. HPLMN) corresponding EAS in PLMN#A (i.e. VPLMN).
  • the UE's session is an HR session.
  • PLMN #A can be considered as the VPLMN of the UE
  • provider #B can be considered as the HPLMN of the UE.
  • the UE can access the MEC service through the UPF (ie H-UPF) corresponding to provider #B.
  • the SMF i.e. H-SMF
  • provider#B configures DNS processing rules for the UE, it can be based on: the UE's access network is PLMN#A (i.e. VPLMN), and the PLMN that provides edge computing services for the UE is provider#B (i.e.
  • HPLMN HPLMN
  • HPLMN HPLMN
  • PLMN #A i.e. VPLMN
  • provider #B for the UE.
  • HPLMN corresponding EAS in PLMN#A (i.e. VPLMN).
  • the SMF (such as V-SMF in scenario 1, and H-SMF in scenario 2) can be based on: the home network of the UE, the UE or the UE's subscription information, and the information provided by provider #B.
  • the UE list includes any one of the UE or the agreement between provider #B and PLMN #A to determine the provider #B, and then obtain the EAS deployment information corresponding to the provider #B.
  • SMF (such as V-SMF in scenario 1, and H-SMF in scenario 2) can also be provided based on the UE's home network, the UE or the UE's subscription information, and provider #B
  • the UE list includes any one of the UEs or the agreement between provider #B and PLMN #A to determine provider #B, and combine it with PLMN #A to obtain the EAS deployment information corresponding to provider #B.
  • PLMN #A to obtain the EAS deployment information corresponding to provider #B.
  • the EAS deployment information provided by the AF may include L-DNS servers corresponding to different PLMNs or different ECSPs in PLMN#A, and what is registered on the L-DNS server may be the EAS corresponding to the corresponding PLMN or ECSP.
  • SMF configures DNS processing rules for EASDF during the session establishment process, it can carry the information of the L-DNS server corresponding to provider#B in the DNS processing rules, which in turn allows EASDF to send the UE's DNS query to the L-DNS server. for processing.
  • provider#B is the HPLMN ID
  • the UE can preferentially use the EAS corresponding to HPLMN in PLMN#A
  • provider#B is the VPLMN ID
  • the UE can be made to preferentially use the EAS corresponding to the VPLMN in PLMN#A
  • provider#B is an ECSP ID
  • the UE can be made to give priority to the EAS corresponding to the ECSP in PLMN#A.
  • Figure 12 is a schematic flow chart of a communication method 1200 provided by an embodiment of the present application.
  • This method 1200 can be used to implement a solution such as method 500 (such as Example 4 in method 500).
  • method 1200 can be used in a scenario where PLMN#A, provider#B, and EAS IP addresses are associated.
  • method 1200 may be implemented through the architecture shown in Figure 8.
  • Method 1200 may include the following steps.
  • AF sends EAS deployment information to NEF.
  • Step 1201 is similar to step 901, except that in step 1201, the EAS deployment information includes provider #B ID and EAS address #B, where EAS address #B is the EAS corresponding to provider #B in PLMN #A. address (such as EAS IP address). It can be understood that EAS address #B is named for differentiation, and its naming does not limit the protection scope of the embodiments of the present application.
  • the EAS deployment information also includes the PLMN#A ID.
  • NEF processes EAS deployment information.
  • NEF sends EAS deployment information to UDR.
  • UDR sends storage response to NEF.
  • NEF sends an EAS deployment information response to AF.
  • the UE initiates the session establishment process.
  • SMF requests EAS deployment information from NEF.
  • NEF obtains EAS deployment information from UDR.
  • NEF sends EAS deployment information to SMF.
  • SMF selects EASDF.
  • steps 1202 to 1210 are similar to steps 902 to 910, and will not be described again here.
  • SMF configures DNS processing rules for EASDF based on the EAS deployment information.
  • the DNS processing rules include EAS address #B.
  • step 1211 includes: SMF generates DNS processing rules based on EAS deployment information, and sends the DNS processing rules to EASDF. For example, SMF sends Neasdf_context_createrequest to EASDF, which Neasdf_context_createrequest includes DNS processing rules; EASDF returns Neasdf_context_create response to SMF.
  • DNS processing rules can be used to process DNS messages, such as DNS messages related to the UE.
  • DNS processing rules can be used to process DNS query messages.
  • DNS processing rules can include one or more of the following information: FQDN range, ECS option, L-DNS server address, EAS address #B, DNS forwarding rules.
  • FQDN range FQDN range
  • ECS option ECS option
  • L-DNS server address L-DNS server address
  • EAS address #B DNS forwarding rules.
  • EAS address #B is the address of EAS corresponding to provider #B in PLMN #A (such as EAS IP address).
  • UE sends DNS query to EASDF.
  • Step 1212 is similar to step 912 and will not be described again here.
  • EASDF processes DNS query according to DNS processing rules.
  • EASDF After EASDF receives the DNS query, it can process the DNS query according to the DNS processing rules received from SMF. EASDF processes DNS queries according to DNS processing rules, which can include the following two processing methods.
  • EASDF detects that the domain name (such as FQDN) contained in the UE's DNS query according to the DNS processing rules can match the domain name contained in the DNS processing rules, then EASDF adds the ECS option to the DNS query according to the DNS processing rules. Send the DNS query with the ECS option added to the C-DNS server.
  • domain name such as FQDN
  • EASDF detects that the domain name (such as FQDN) contained in the UE's DNS query according to the DNS processing rules can match the domain name contained in the DNS processing rules, then EASDF determines the address of the L-DNS server according to the DNS processing rules and sends The UE's DNS query is sent to the L-DNS server.
  • domain name such as FQDN
  • EASDF queries the DNS server for N EAS IP addresses.
  • the N EAS IP addresses may include at least one of the following: the EAS IP address corresponding to the UE's HPLMN, the EAS IP address corresponding to the UE's VPLMN, and the EAS IP address corresponding to the third-party ECSP (such as the ECSP subscribed by the UE).
  • the DNS server includes at least one of the following: the EAS IP address corresponding to the UE's HPLMN, the EAS IP address corresponding to the UE's VPLMN, and the EAS IP address corresponding to the third-party ECSP (such as the ECSP subscribed by the UE), which can then be provided to EASDF
  • the above N EAS IP addresses can be an L-DNS server or a C-DNS server. The following describes the two processing methods in the above step 1213.
  • the C-DNS server includes the above N EAS IP addresses.
  • the C-DNS server After receiving the DNS query containing the ECS option from EASDF, the C-DNS server sends a DNS response to EASDF.
  • the DNS response contains N EAS IP addresses, and EASDF obtains the N EAS IP addresses.
  • the L-DNS server includes the above N EAS IP addresses.
  • the L-DNS server After receiving the DNS query from EASDF, the L-DNS server sends a DNS response to EASDF.
  • the DNS response contains N EAS IP addresses, and EASDF obtains the N EAS IP addresses.
  • EASDF selects M EAS IP addresses from N EAS IP addresses based on EAS address #B.
  • M is an integer greater than or equal to 1, and M is less than or equal to N.
  • EASDF selects M EAS IP addresses from N EAS IP addresses based on EAS address #B, including: EASDF selects (or filters) the EAS IP address belonging to EAS address #B from N EAS IP addresses (i.e. M EAS IP addresses). In other words, the M EAS IP addresses are the intersection of N EAS IP addresses and EAS address #B.
  • EASDF returns the EAS information corresponding to provider #B to the UE.
  • EASDF After EASDF selects M EAS IP addresses from N EAS IP addresses based on EAS address #B, it can return the M EAS IP addresses to the UE (that is, the EAS information corresponding to provider #B).
  • the UE can obtain the EAS information corresponding to provider#B.
  • method 1200 can be used for HR roaming (for example, the UE's session in step 1206 is an HR session), or for LBO roaming (for example, the UE's session in step 1206 is an LBO session).
  • HR roaming for example, the UE's session in step 1206 is an HR session
  • LBO roaming for example, the UE's session in step 1206 is an LBO session.
  • it can Adaptive adjustments are made based on different roaming methods, and there are no restrictions on this.
  • the UE's session is an LBO session.
  • PLMN #A can be considered as the VPLMN of the UE
  • provider #B can be considered as the HPLMN of the UE.
  • the UE can access the MEC service through the UPF (ie V-UPF) corresponding to PLMN #A.
  • the SMF i.e. V-SMF
  • the SMF configures DNS processing rules for the UE, it can be based on: the UE's access network is PLMN#A (i.e.
  • VPLMN the PLMN that provides edge computing services for the UE is provider#B (i.e. HPLMN), search for the corresponding EAS deployment information, and then you can find the EAS address #B corresponding to provider #B (i.e. HPLMN) in PLMN #A (i.e. VPLMN), and then you can find provider #B (i.e. VPLMN) for the UE HPLMN) corresponding EAS in PLMN#A (i.e. VPLMN).
  • provider #B i.e. HPLMN
  • PLMN #A i.e. VPLMN
  • provider #B i.e. VPLMN
  • the UE's session is an HR session.
  • PLMN #A can be considered as the VPLMN of the UE
  • provider #B can be considered as the HPLMN of the UE.
  • the UE can access the MEC service through the UPF (ie H-UPF) corresponding to provider #B.
  • the SMF i.e. H-SMF
  • provider#B configures DNS processing rules for the UE, it can be based on: the UE's access network is PLMN#A (i.e. VPLMN), and the PLMN that provides edge computing services for the UE is provider#B (i.e.
  • HPLMN HPLMN
  • HPLMN HPLMN
  • PLMN #A i.e. VPLMN
  • provider #B i.e. VPLMN
  • PLMN #A i.e. VPLMN
  • PLMN#A i.e. VPLMN
  • the SMF (such as V-SMF in scenario 1, and H-SMF in scenario 2) can be based on: the home network of the UE, the UE or the UE's subscription information, and the information provided by provider #B.
  • the UE list includes any one of the UE or the agreement between provider #B and PLMN #A to determine the provider #B, and then obtain the EAS deployment information corresponding to the provider #B.
  • SMF (such as V-SMF in scenario 1, and H-SMF in scenario 2) can also be provided based on the UE's home network, the UE or the UE's subscription information, and provider #B
  • the UE list includes any one of the UEs or the agreement between provider #B and PLMN #A to determine provider #B, and combine it with PLMN #A to obtain the EAS deployment information corresponding to provider #B.
  • PLMN #A to obtain the EAS deployment information corresponding to provider #B.
  • the EAS deployment information provided by the AF may include the EAS IP addresses corresponding to different PLMNs or different ECSPs in PLMN#A.
  • SMF configures DNS processing rules for EASDF during the session establishment process, it can carry the EAS address corresponding to provider#B in the DNS processing rules, which in turn allows EASDF to filter (or select) the EAS address corresponding to provider#B in the DNS response. .
  • provider#B is the HPLMN ID
  • the UE can be made to preferentially use the EAS corresponding to the HPLMN in PLMN#A
  • provider#B is the VPLMN ID
  • the UE can be made to preferentially use the EAS corresponding to the VPLMN in PLMN#A
  • provider#B is an ECSP ID
  • the UE can be made to preferentially use the EAS corresponding to ECSP in PLMN#A.
  • Figure 13 is a schematic flow chart of a communication method 1300 provided by an embodiment of the present application.
  • This method 1300 can be used to implement a solution such as method 500 (such as Example 5 in method 500).
  • method 1300 can be used in a scenario where PLMN#A, provider#B, C-DNS server, and ECS option are associated.
  • method 1300 may be implemented through the architecture shown in FIG. 6 .
  • Method 1300 may include the following steps.
  • AF sends EAS deployment information to 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.
  • EAS deployment information also includes PLMN#A ID. The following takes provider#B as PLMN as an example to introduce several possible situations.
  • a PLMN corresponds to a C-DNS server #B
  • the PLMN corresponds to a set of mapping relationships between DNAI and ECS options.
  • a PLMN corresponds to a C-DNS server #B
  • all PLMNs correspond to the same set of mapping relationships between DNAI and ECS options.
  • all PLMNs correspond to one C-DNS server #B, and each PLMN corresponds to a set of mapping relationships between DNAI and ECS options.
  • the same C-DNS server #B can be configured for all PLMNs, and each PLMN corresponds to a unique set of mapping relationships between DNAI and ECS options.
  • provider#B is ECSP and will not be described again here.
  • NEF processes EAS deployment information.
  • NEF sends EAS deployment information to UDR.
  • UDR sends storage response to NEF.
  • NEF sends an EAS deployment information response to AF.
  • the UE initiates the session establishment process.
  • SMF requests EAS deployment information from NEF.
  • NEF obtains EAS deployment information from UDR.
  • NEF sends EAS deployment information to SMF.
  • SMF selects EASDF.
  • steps 1303 to 1310 are similar to steps 902 to 910, and will not be described again here.
  • SMF configures DNS processing rules for EASDF based on the EAS deployment information.
  • the DNS processing rules include ECS option #B and C-DNS server #B.
  • step 1311 includes: SMF generates DNS processing rules based on EAS deployment information, and sends the DNS processing rules to EASDF. For example, SMF sends Neasdf_context_createrequest to EASDF, which Neasdf_context_createrequest includes DNS processing rules; EASDF returns Neasdf_context_create response to SMF.
  • DNS processing rules can be used to process DNS messages, such as DNS messages related to the UE.
  • DNS processing rules can be used to process DNS query messages.
  • 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.
  • FQDN range FQDN range
  • ECS option#B ECS option#B
  • C-DNS server#B address DNS forwarding rules.
  • the DNS processing rules determined by SMF can include the ECS option#B and C-DNS server#B addresses, so that EASDF can add the ECS option#B to the UE's DNS query based on the DNS processing rules and send it to the C-DNS server.
  • Address #B sends a DNS query containing ECS option #B. Therefore, it is possible to select a specific EAS for the UE (that is, the EAS corresponding to provider #B).
  • the UE can complete the session Establish.
  • UE sends DNS query to EASDF.
  • Step 1312 is similar to step 912 and will not be described again here.
  • EASDF processes DNS query according to DNS processing rules.
  • EASDF After EASDF receives the DNS query, it can process the DNS query according to the DNS processing rules received from SMF. EASDF processes DNS query according to DNS processing rules, which can include: EASDF adds ECS option#B to DNS query, and sends a DNS query containing ECS option#B to C-DNS server #B.
  • EASDF detects that the FQDN contained in the UE's DNS query matches the FQDN contained in the DNS processing rules based on the DNS processing rules, then EASDF adds ECS option #B to the DNS query based on the DNS processing rules, and then adds ECS option #B to the DNS query.
  • -DNS server #B sends the DNS query after adding ECS option#B.
  • EASDF sends a DNS query containing ECS option#B to C-DNS server #B.
  • C-DNS server #B returns a DNS response to EASDF.
  • C-DNS server #B can send a DNS response to EASDF, and the DNS response can contain the EAS information (such as EAS IP address) corresponding to provider #B. Combine the three scenarios.
  • provider#B is HPLMN ID.
  • the EAS corresponding to provider#B indicates the EAS corresponding to HPLMN.
  • provider#B is VPLMN ID.
  • the EAS corresponding to provider#B indicates the EAS corresponding to VPLMN.
  • provider#B is the ECSP ID.
  • the EAS corresponding to provider#B indicates the EAS corresponding to ECSP.
  • EASDF returns the EAS information corresponding to provider #B to the UE.
  • the UE can obtain the EAS information corresponding to provider#B.
  • method 1300 can be used for HR roaming (for example, the UE's session in step 1306 is an HR session), or for LBO roaming (for example, the UE's session in step 1306 is an LBO session).
  • HR roaming for example, the UE's session in step 1306 is an HR session
  • LBO roaming for example, the UE's session in step 1306 is an LBO session.
  • it can Adaptive adjustments are made based on different roaming methods, and there are no restrictions on this.
  • the UE's session is an LBO session.
  • PLMN #A can be considered as the VPLMN of the UE
  • provider #B can be considered as the HPLMN of the UE.
  • the UE can access the MEC service through the UPF (ie V-UPF) corresponding to PLMN #A.
  • the SMF i.e. V-SMF
  • the SMF configures DNS processing rules for the UE, it can be based on: the UE's access network is PLMN#A (i.e.
  • VPLMN the PLMN that provides edge computing services for the UE is provider#B (i.e. HPLMN), search for the corresponding EAS deployment information, and then you can find the C-DNS server #B and ECS option #B corresponding to provider #B (i.e. HPLMN) in PLMN #A (i.e. VPLMN), and then you can find the UE Find the EAS corresponding to provider#B (ie HPLMN) in PLMN#A (ie VPLMN).
  • provider#B i.e. HPLMN
  • PLMN #A i.e. VPLMN
  • the UE's session is an HR session.
  • PLMN #A can be considered as the VPLMN of the UE
  • provider #B can be considered as the HPLMN of the UE.
  • the UE can access the MEC service through the UPF (ie H-UPF) corresponding to provider #B.
  • the SMF i.e. H-SMF
  • provider#B configures DNS processing rules for the UE, it can be based on: UE access
  • PLMN#A i.e. VPLMN
  • provider#B i.e.
  • HPLMN HPLMN
  • PLMN#A i.e. The corresponding C-DNS server #B and ECS option #B in VPLMN
  • EAS corresponding to provider #B ie HPLMN
  • PLMN #A ie VPLMN
  • the SMF (such as V-SMF in scenario 1, and H-SMF in scenario 2) can be based on: the home network of the UE, the UE or the UE's subscription information, and the information provided by provider #B.
  • the UE list includes any one of the UE or the agreement between provider #B and PLMN #A to determine the provider #B, and then obtain the EAS deployment information corresponding to the provider #B.
  • SMF (such as V-SMF in scenario 1, and H-SMF in scenario 2) can also be provided based on the UE's home network, the UE or the UE's subscription information, and provider #B
  • the UE list includes any one of the UEs or the agreement between provider #B and PLMN #A to determine provider #B, and combine it with PLMN #A to obtain the EAS deployment information corresponding to provider #B.
  • PLMN #A to obtain the EAS deployment information corresponding to provider #B.
  • the EAS deployment information provided by the AF may include: C-DNS servers corresponding to different PLMNs or different ECSPs in PLMN#A, and ECS options corresponding to different PLMNs or different ECSPs in PLMN#A.
  • SMF configures DNS processing rules for EASDF during the session establishment process, it can carry the C-DNS server and ECS option corresponding to provider#B in the DNS processing rules, which in turn allows EASDF to send the DNS query adding the ECS option to the C -DNS server handles it.
  • provider#B is the HPLMN ID
  • the UE can be made to preferentially use the EAS corresponding to the HPLMN in PLMN#A
  • provider#B is the VPLMN ID
  • the UE can be made to preferentially use the EAS corresponding to the VPLMN in PLMN#A
  • provider#B is an ECSP ID
  • the UE can be made to preferentially use the EAS corresponding to ECSP in PLMN#A.
  • the message names involved are only examples and do not limit the scope of protection of the embodiments of this application.
  • query messages can also be replaced with request messages.
  • the SMF querying the corresponding EAS deployment information according to provider #B is mainly used as an example for illustrative explanation, and this is not limited.
  • SMF requests EAS deployment information from NEF, it can carry provider #B (or PLMN #A and provider #B), and then NEF sends the EAS deployment information corresponding to provider #B in PLMN #A to SMF.
  • the SMF can be based on: the home network of the UE, the UE or the UE's subscription information, the UE included in the UE list provided by provider #B, or the agreement between provider #B and PLMN #A. Determine provider #B by any one of them, and then obtain the EAS deployment information corresponding to provider #B; or you can also include the UE according to the UE's home network, the UE or the UE's subscription information, the UE list provided by provider #B, or Any item in the agreement between provider #B and PLMN #A determines provider #B, and combines it with PLMN #A to obtain the EAS deployment information corresponding to provider #B. There are no restrictions on this.
  • the SMF determines the DNS processing rules based on the EAS deployment information corresponding to the provider as an example for illustrative explanation, and this is not limited.
  • SMF can determine DNS processing rules based on existing methods and send them to EASDF;
  • EASDF can process the UE's DNS query request based on the DNS processing rules and the provider's corresponding EAS deployment information.
  • sending messages is mentioned multiple times. Take A sending a message to B as an example.
  • a sending a message to B can include A sending a message directly to B, or it can include A sending a message to B through other devices or network elements. There is no restriction on this.
  • EAS IP or FQDN are mentioned multiple times, EAS IP can be replaced by EAS IP range (EAS IP range), and FQDN can be replaced by FQDN range.
  • the ECSP subscribed by the UE is used as an example for illustrative description, and this is not limited.
  • the ECSP subscribed by the UE can also be replaced with all or part of the corresponding third-party ECSP in the VPLMN.
  • each network element (such as SMF, AMF, NEF, etc.) is mainly explained by taking the naming in the 5G system as an example. This application does not rule out the possibility of using other naming in 6G networks and other networks in the future. For example, in a 6G network, some or all of the above network elements may use the terminology used in 5G, or may adopt other names.
  • the methods and operations implemented by the device can also be implemented by components of the device (such as chips or circuits).
  • embodiments of the present application also provide corresponding devices, and the devices include modules for executing corresponding modules in each of the above method embodiments.
  • the module can be software, hardware, or a combination of software and hardware. It can be understood that the technical features described in the above method embodiments are also applicable to the following device embodiments.
  • FIG 14 is a schematic diagram of a communication device 1400 provided by an embodiment of the present application.
  • the device 1400 includes a transceiver unit 1410 and a processing unit 1420.
  • the transceiver unit 1410 may be used to implement corresponding communication functions.
  • the transceiver unit 1410 may also be called a communication interface or communication unit.
  • the processing unit 1420 may be used to implement corresponding processing functions, such as determining DNS processing rules.
  • the device 1400 also includes a storage unit, which can be used to store instructions and/or data, and the processing unit 1420 can read the instructions and/or data in the storage unit, so that the device implements each of the foregoing method embodiments.
  • the actions of the equipment or network elements in the network can be used to store instructions and/or data, and the processing unit 1420 can read the instructions and/or data in the storage unit, so that the device implements each of the foregoing method embodiments.
  • the actions of the equipment or network elements in the network can be used to store instructions and/or data, and the processing unit 1420 can read the instructions and/or data in the storage unit, so that the device implements each of the foregoing method embodiments.
  • the actions of the equipment or network elements in the network can be used to store instructions and/or data, and the processing unit 1420 can read the instructions and/or data in the storage unit, so that the device implements each of the foregoing method embodiments.
  • the actions of the equipment or network elements in the network can be used to store instructions
  • the device 1400 may be the session management network element (such as SMF) in the previous embodiment, or may be a component of the session management network element (such as a chip).
  • the device 1400 can implement steps or processes corresponding to the execution of the session management network element in the above method embodiment, wherein the transceiver unit 1410 can be used to perform operations related to the transceiver of the session management network element in the above method embodiment, and the processing unit 1420 may be used to perform operations related to processing of the session management network element in the above method embodiment.
  • the processing unit 1420 is used to obtain provider information.
  • the provider is a provider that provides edge computing services for terminal devices; the processing unit 1420 is used to obtain provider information and the edge application server corresponding to the provider.
  • EAS deployment information configures domain name service DNS processing rules. DNS processing rules are used to process DNS messages of terminal devices.
  • EAS deployment information is the corresponding EAS deployment information of the provider in the access network of the terminal device; the transceiver unit 1410 is used to send The edge application server discovers the network element and sends DNS processing rules.
  • the processing unit 1420 is configured to obtain EAS deployment information based on provider information; or obtain EAS deployment information based on provider information and access network information.
  • the EAS deployment information includes any of the following: DNS server, ECS option, and the address of the EAS corresponding to the provider in the access network; among them, the EAS registered on the DNS server is the address corresponding to the provider in the access network.
  • the EAS corresponding to the ECS option is the EAS corresponding to the provider in the access network.
  • the DNS server is a server deployed in the home network, or the DNS server is a server deployed in the access network.
  • the DNS processing rules include any of the following: DNS server, ECS option, and the address of the provider's corresponding EAS in the access network.
  • the processing unit 1420 is configured to perform any of the following: determine provider information according to the home network of the terminal device; determine provider information according to the contract information of the terminal device, wherein the contract information of the terminal device includes providing Provider information; determine provider information based on the terminal equipment included in the terminal equipment list provided by the provider; or determine provider information based on the agreement between the provider and the access network.
  • the access network is the visited network of the terminal device
  • the provider is the home network of the terminal device.
  • the provider is any one of the following: a provider of EAS, a provider of edge host environment EHE, or a provider of edge data network EDN.
  • the device 1400 may be the edge application server discovery network element (such as EASDF) in the previous embodiment, or may be a component (such as a chip) of the edge application server discovery network element.
  • the device 1400 can implement steps or processes corresponding to the execution of the edge application server discovering the network element in the above method embodiment, wherein the transceiver unit 1410 can be used to perform the transceiver related to the edge application server discovering the network element in the above method embodiment.
  • the processing unit 1420 may be configured to perform operations related to the processing of the edge application server discovering network elements in the above method embodiment.
  • the transceiver unit 1410 is used to receive the domain name service DNS query message from the terminal device; the processing unit 1420 is used to process the DNS query message according to the DNS processing rules; wherein the DNS processing rules are based on the terminal device.
  • the EAS deployment information of the edge application server corresponding to the provider that provides edge computing services is determined.
  • the EAS deployment information is the EAS deployment information of the provider in the access network of the terminal device.
  • the EAS deployment information is determined based on provider information; or, the EAS deployment information is determined based on provider information and access network information.
  • the EAS deployment information includes at least one of the following: DNS server, ECS option, and the address of the EAS corresponding to the provider in the access network; wherein, the EAS registered on the DNS server is the address corresponding to the provider in the access network.
  • EAS, the EAS corresponding to the ECS option is the EAS corresponding to the provider in the access network.
  • the DNS server is a server deployed in the home network, or the DNS server is a server deployed in the access network.
  • the EAS deployment information includes DNS server information
  • the DNS processing rules include DNS server information
  • the transceiver unit 1410 is configured to send a DNS query message to the DNS server.
  • the DNS server is a server deployed in the home network.
  • the processing unit 1420 is used to add the ECS option to the DNS query message according to the DNS processing rules; the transceiver unit 1410 is used to send the DNS containing the ECS option to the DNS server. Query message.
  • the EAS deployment information includes the address of the provider's corresponding EAS in the access network
  • the DNS processing rules include the address of the provider's corresponding EAS in the access network.
  • the processing unit 1420 is configured to, according to the DNS processing rules, Obtain the address of at least one EAS; generate a response message of the DNS query message, the response message includes part or all of the EAS address in the address of at least one EAS, wherein part or all of the EAS address is corresponding to the provider in the access network EAS determined.
  • the EAS deployment information includes the ECS option
  • the DNS processing rules include the ECS option information
  • the processing unit 1420 is used to add the ECS option in the DNS query message.
  • the transceiving unit 1410 is configured to receive DNS processing rules from the session management network element.
  • the provider is any one of the following: a provider of EAS, a provider of edge host environment EHE, or a provider of edge data network EDN.
  • the device 1400 here is embodied in the form of a functional unit.
  • the term "unit” as used herein may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (such as a shared processor, a proprietary processor, or a group of processors) used to execute one or more software or firmware programs. processor, etc.) and memory, merged logic circuitry, and/or other suitable components to support the described functionality.
  • ASIC application specific integrated circuit
  • processor such as a shared processor, a proprietary processor, or a group of processors
  • memory merged logic circuitry, and/or other suitable components to support the described functionality.
  • the device 1400 can be specifically the session management network element in the above embodiments, and can be used to execute various processes corresponding to the session management network element in the above method embodiments and/or or steps; or, the device 1400 can be specifically the data management network element in the above embodiments, and can be used to execute various processes and/or steps corresponding to the data management network element in the above method embodiments; or the device 1400 can be specifically It is the application network element in the above embodiment, and can be used to execute various processes and/or steps corresponding to the application network element in the above method embodiments; or, the device 1400 can be specifically the edge application server discovery network in the above embodiment. The element can be used to execute each process and/or step corresponding to the edge application server discovering the network element in each of the above method embodiments. To avoid duplication, the details are not repeated here.
  • the device 1400 of each of the above solutions has the function of implementing corresponding steps performed by network elements (such as session management network elements, or data management network elements, or application network elements, or edge application server discovery network elements) in the above methods.
  • the functions described can be implemented by hardware, or can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions; for example, the transceiver unit can be replaced by a transceiver (for example, the sending unit in the transceiver unit can be replaced by a transmitter, and the receiving unit in the transceiver unit can be replaced by a receiving unit. (machine replacement), other units, such as processing units, etc., can be replaced by processors to respectively perform the sending and receiving operations and related processing operations in each method embodiment.
  • transceiver unit 1410 may also be a transceiver circuit (for example, it may include a receiving circuit and a transmitting circuit), and the processing unit may be a processing circuit.
  • the device in Figure 14 may be the network element or device in the aforementioned embodiment, or it may be a chip or a chip system, such as a system on chip (SoC).
  • the transceiver unit may be an input-output circuit or a communication interface; the processing unit may be a processor, microprocessor, or integrated circuit integrated on the chip. No limitation is made here.
  • Figure 15 is a schematic diagram of a device 1500 that provides another type of communication according to an embodiment of the present application.
  • the apparatus 1500 includes processing
  • the processor 1510 is configured to execute the computer program or instructions stored in the memory 1520, or read the data/signaling stored in the memory 1520, to execute the methods in the above method embodiments.
  • the device 1500 further includes a memory 1520, which is used to store computer programs or instructions and/or data.
  • the memory 1520 may be integrated with the processor 1510, or may be provided separately.
  • the device 1500 also includes a transceiver 1530, which is used for receiving and/or transmitting signals.
  • the processor 1510 is used to control the transceiver 1530 to receive and/or transmit signals.
  • the device 1500 is used to implement the operations performed by the session management network element in each of the above method embodiments.
  • the processor 1510 is configured to execute computer programs or instructions stored in the memory 1520 to implement related operations of the session management network element in each of the above method embodiments. For example, the method executed by the session management network element in the embodiment shown in FIG. 5, or the method executed by the SMF in any one of the embodiments shown in FIGS. 9 to 13.
  • the device 1500 is used to implement the operations performed by the application network element in each of the above method embodiments.
  • the processor 1510 is used to execute computer programs or instructions stored in the memory 1520 to implement related operations of the application network elements in each of the above method embodiments. For example, the method executed by the application network element in the embodiment shown in FIG. 5, or the method executed by AF in any one of the embodiments shown in FIGS. 9 to 13.
  • the device 1500 is used to implement the operations performed by the data management network element in each of the above method embodiments.
  • the processor 1510 is used to execute computer programs or instructions stored in the memory 1520 to implement related operations of the data management network element in each of the above method embodiments. For example, the method performed by the data management network element in the embodiment shown in Figure 5, or the method performed by the UDR in any of the embodiments shown in Figures 9 to 13.
  • the device 1500 is used to implement the operations performed by the edge application server to discover network elements in each of the above method embodiments.
  • the processor 1510 is used to execute computer programs or instructions stored in the memory 1520 to implement related operations of the edge application server discovering network elements in each of the above method embodiments. For example, the method executed by the edge application server in the embodiment shown in FIG. 5 to discover network elements, or the method executed by the EASDF in any one of the embodiments shown in FIGS. 9 to 13 .
  • processors mentioned in the embodiments of this application may be a central processing unit (CPU), or other general-purpose processor, digital signal processor (DSP), or application-specific integrated circuit (ASIC).
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • a general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.
  • the memory mentioned in the embodiments of the present application may be a volatile memory and/or a non-volatile memory.
  • the non-volatile memory can be read-only memory (ROM), programmable ROM (PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically removable memory.
  • ROM read-only memory
  • PROM programmable ROM
  • EPROM erasable programmable read-only memory
  • EPROM erasable PROM
  • EPROM erasable programmable read-only memory
  • Erase programmable read-only memory electrically EPROM, EEPROM
  • Volatile memory may be random access memory (RAM).
  • RAM can be used as an external cache live.
  • RAM includes the following forms: static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), Double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synchlink DRAM, SLDRAM) and direct Memory bus random access memory (direct rambus RAM, DR RAM).
  • the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component
  • the memory storage module
  • memories described herein are intended to include, but are not limited to, these and any other suitable types of memories.
  • FIG. 16 is a schematic diagram of a chip system 1600 provided by an embodiment of the present application.
  • the chip system 1600 (or can also be called a processing system) includes a logic circuit 1610 and an input/output interface 1620.
  • the logic circuit 1610 may be a processing circuit in the chip system 1600 .
  • the logic circuit 1610 can be coupled to the memory unit and call instructions in the memory unit, so that the chip system 1600 can implement the methods and functions of various embodiments of the present application.
  • the input/output interface 1620 can be an input/output circuit in the chip system 1600, which outputs information processed by the chip system 1600, or inputs data or signaling information to be processed into the chip system 1600 for processing.
  • the logic circuit 1610 can send a DNS processing rule through the input/output interface 1620, and the DNS processing rule can be generated for the logic circuit 1610 ; Or the input/output interface 1620 can input the EAS deployment information from the NEF to the logic circuit 1610 for processing.
  • the chip system 1600 is used to implement the operations performed by the session management network element in each of the above method embodiments.
  • the logic circuit 1610 is used to implement processing-related operations performed by the session management network element in the above method embodiment, such as processing-related operations performed by the session management network element in the embodiment shown in Figure 5, or Figure 9
  • the input/output interface 1620 is used to implement the sending and/or receiving related operations performed by the session management network element in the above method embodiment, For example, the sending and/or receiving related operations performed by the session management network element in the embodiment shown in Figure 5, or the sending and/or receiving related operations performed by the SMF in any of the embodiments shown in Figures 9 to 13. operate.
  • the chip system 1600 is used to implement the operations performed by the application network element in each of the above method embodiments.
  • the logic circuit 1610 is used to implement the processing-related operations performed by the application network element in the above method embodiment, such as the processing-related operations performed by the application network element in the embodiment shown in FIG. 5, or FIG. 9 to FIG. Processing-related operations performed by the AF in any of the embodiments shown in 13;
  • the input/output interface 1620 is used to implement sending and/or reception-related operations performed by the application network element in the above method embodiments, such as, Figure The sending and/or receiving related operations performed by the application network element in the embodiment shown in Figure 5, or the sending and/or receiving related operations performed by the AF in any one of the embodiments shown in Figures 9 to 13.
  • the chip system 1600 is used to implement the operations performed by the data management network element in each of the above method embodiments.
  • the logic circuit 1610 is used to implement processing-related operations performed by the data management network element in the above method embodiment, such as processing-related operations performed by the data management network element in the embodiment shown in Figure 5, or Figure 9 to the processing related operations performed by the UDR in any embodiment shown in Figure 13;
  • the input/output interface 1620 is used to implement the sending and/or receiving related operations performed by the data management network element in the above method embodiment, For example, the sending and/or receiving related operations performed by the data management network element in the embodiment shown in Figure 5, or the sending and/or receiving related operations performed by the UDR in any of the embodiments shown in Figures 9 to 13. operate.
  • the chip system 1600 is used to implement the operations performed by the edge application server to discover network elements in each of the above method embodiments.
  • the logic circuit 1610 is used to implement the processing-related operations performed by the edge application server to discover the network element in the above method embodiment, such as the processing-related operations performed by the edge application server to discover the network element in the embodiment shown in Figure 5 , or processing-related operations performed by the EASDF in any of the embodiments shown in Figures 9 to 13;
  • the input/output interface 1620 is used to implement the sending and/or execution of the discovery network element by the edge application server in the above method embodiment.
  • receive related operations such as the sending and/or receiving related operations performed by the edge application server in the embodiment shown in Figure 5 to discover the network element, or the EASDF performed in any of the embodiments shown in Figures 9 to 13 Send and/or receive related operations.
  • Embodiments of the present application also provide a computer-readable storage medium on which are stored computer instructions for implementing the methods executed by network elements in each of the above method embodiments.
  • the computer when the computer program is executed by a computer, the computer can implement the method executed by the session management network element in each embodiment of the above method.
  • the computer when the computer program is executed by a computer, the computer can implement the method executed by the application network element in each embodiment of the above method.
  • the computer when the computer program is executed by a computer, the computer can implement the method executed by the data management network element in each embodiment of the above method.
  • the computer when the computer program is executed by a computer, the computer can implement the method executed by the edge application server to discover network elements in each embodiment of the above method.
  • Embodiments of the present application also provide a computer program product, which includes instructions.
  • the instructions When the instructions are executed by a computer, the instructions are implemented by a network element (such as a session management network element, or an application network element, or a data management network element, Or the edge application server discovers the network element) execution method.
  • a network element such as a session management network element, or an application network element, or a data management network element, Or the edge application server discovers the network element
  • An embodiment of the present application also provides a communication system, including one or more of the aforementioned session management network elements, application network elements, data management network elements, or edge application server discovery network elements.
  • the system also includes a device that communicates with one or more of the above network elements.
  • the system may also include at least one of the following: terminal equipment, NEF, etc.
  • the disclosed devices and methods can be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or can be integrated into another system, or some features can be ignored, or not implemented.
  • the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the devices or units may be in electrical, mechanical or other forms.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device.
  • the computer may be a personal computer, a server, or a network device.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another, e.g., the computer instructions may be transferred from a website, computer, server, or data center Transmission to another website, computer, server or data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) means.
  • 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 one or more available media integrated.
  • the available media may be magnetic media (such as floppy disks, hard disks, magnetic tapes), optical media (such as DVDs), or semiconductor media (such as solid state disks (SSD)), etc.
  • the aforementioned available media include but Not limited to: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program code.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Computer And Data Communications (AREA)

Abstract

Des modes de réalisation de la présente demande concernent un procédé et un appareil de communication. Le procédé peut comprendre les étapes suivantes : un élément réseau de gestion de session acquiert des informations d'un fournisseur, le fournisseur étant un fournisseur fournissant un service informatique périphérique pour un dispositif terminal ; l'élément réseau de gestion de session configure une règle de traitement DNS de service de nom de domaine selon les informations du fournisseur et les informations de déploiement du serveur d'application périphérique (EAS) correspondant au fournisseur, la règle de traitement DNS servant à traiter un message DNS du dispositif terminal, et les informations de déploiement EAS étant des informations de déploiement EAS du fournisseur dans un réseau d'accès du dispositif terminal ; et l'élément réseau de gestion de session envoie la règle de traitement DNS à un élément réseau de découverte EAS. Au moyen des informations du fournisseur fournissant le service informatique périphérique pour le dispositif terminal, les informations de déploiement EAS correspondantes du fournisseur dans le réseau d'accès du dispositif terminal sont recherchées, de façon à ce qu'un EAS correspondant du fournisseur dans le réseau d'accès du dispositif terminal soit sélectionné pour le dispositif terminal.
PCT/CN2023/083362 2022-03-28 2023-03-23 Procédé et appareil de communication WO2023185620A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210313165.9A CN116866893A (zh) 2022-03-28 2022-03-28 通信的方法和装置
CN202210313165.9 2022-03-28

Publications (1)

Publication Number Publication Date
WO2023185620A1 true WO2023185620A1 (fr) 2023-10-05

Family

ID=88199220

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/083362 WO2023185620A1 (fr) 2022-03-28 2023-03-23 Procédé et appareil de communication

Country Status (2)

Country Link
CN (1) CN116866893A (fr)
WO (1) WO2023185620A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021091232A1 (fr) * 2019-11-05 2021-05-14 삼성전자 주식회사 Dispositif et procédé de fourniture d'informations de serveur d'application dans un système de communication mobile
CN113572835A (zh) * 2021-07-21 2021-10-29 腾讯科技（深圳）有限公司 一种数据处理方法、网元设备以及可读存储介质
CN113795014A (zh) * 2021-08-05 2021-12-14 华为技术有限公司 发现边缘应用服务器的方法及装置
CN114125808A (zh) * 2021-11-29 2022-03-01 中国联合网络通信集团有限公司 一种边缘应用服务器的发现方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021091232A1 (fr) * 2019-11-05 2021-05-14 삼성전자 주식회사 Dispositif et procédé de fourniture d'informations de serveur d'application dans un système de communication mobile
CN113572835A (zh) * 2021-07-21 2021-10-29 腾讯科技（深圳）有限公司 一种数据处理方法、网元设备以及可读存储介质
CN113795014A (zh) * 2021-08-05 2021-12-14 华为技术有限公司 发现边缘应用服务器的方法及装置
CN114125808A (zh) * 2021-11-29 2022-03-01 中国联合网络通信集团有限公司 一种边缘应用服务器的发现方法及装置

Also Published As

Publication number Publication date
CN116866893A (zh) 2023-10-10

Similar Documents

Publication Publication Date Title
WO2023280121A1 (fr) Procédé et appareil d'obtention de service de périphérie
WO2021057794A1 (fr) Procédé de configuration de service, dispositif de communication et système de communication
WO2020151584A1 (fr) Procédé de configuration de réseau et appareil de communication
WO2023124457A1 (fr) Procédé et appareil de sélection de réseau
WO2021063164A1 (fr) Procédé de communication, appareil de communication et support de stockage
WO2022199451A1 (fr) Procédé et appareil de commutation de session
WO2023051430A1 (fr) Procédé et appareil de communication
WO2022194262A1 (fr) Procédé et appareil de communication de sécurité
WO2022170798A1 (fr) Procédé de détermination de stratégie et appareil de communication
WO2023185620A1 (fr) Procédé et appareil de communication
WO2023160394A1 (fr) Procédé et appareil de communication
WO2023185561A1 (fr) Procédé de communication et appareil de communication
WO2023051428A1 (fr) Procédé et appareil de transmission d'informations
WO2023051427A1 (fr) Procédé et appareil de communication
WO2023051431A1 (fr) Procédé et appareil de communication
WO2023207958A1 (fr) Procédé de transmission de politique, et appareil et système de communication
WO2023116556A1 (fr) Procédé et appareil de commutation de session
WO2023103575A1 (fr) Procédé de communication de diffusion/multidiffusion et appareil associé
WO2023142717A1 (fr) Procédé et appareil pour déterminer une politique de sélection d'itinéraire d'équipement utilisateur
WO2023143212A1 (fr) Procédé et appareil de communication
WO2023133871A1 (fr) Procédé et appareil de communication
WO2023185657A1 (fr) Procédé de communication et appareil de communication
US20240244031A1 (en) Communication method and apparatus
JP7473001B2 (ja) コアネットワークノード、端末、及びこれらの方法
US20240244032A1 (en) Communication method and apparatus

Legal Events

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

Ref document number: 23777990

Country of ref document: EP

Kind code of ref document: A1