CN117014907A

CN117014907A - EDI acquisition, route reconfiguration, ECS address configuration information acquisition and DNS processing methods, devices and equipment

Info

Publication number: CN117014907A
Application number: CN202310140125.3A
Authority: CN
Inventors: 吕华章
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2022-05-06
Filing date: 2023-02-17
Publication date: 2023-11-07
Also published as: WO2023213305A1

Abstract

The application discloses an EDI acquisition method, a route reconfiguration method, an ECS address configuration information acquisition method, a DNS processing method, a device and equipment, belonging to the technical field of communication, wherein the EDI acquisition method comprises the following steps: the first network element sends a query request to the second network element, wherein the query request is used for requesting to query the third network element; the first network element receives a query response sent by the second network element, wherein the query response comprises address information of the third network element; the first network element sends a target request to the third network element according to the address information, wherein the target request is used for requesting to obtain the EDI of the roaming place operator from the fourth network element; the first network element receives the EDI sent by the third network element.

Description

EDI acquisition, route reconfiguration, ECS address configuration information acquisition and DNS processing methods, devices and equipment

Technical Field

The application belongs to the technical field of communication, and particularly relates to an EDI acquisition method, a routing reconfiguration method, an ECS address configuration information acquisition method, a DNS processing device and DNS processing equipment.

Background

In roaming scenarios, i.e. after the terminal has moved from home to roaming, the terminal needs to re-establish protocol data unit (Protocol Data Unit, PDU) sessions to enable data transfer. However, how to establish a PDU session for a roaming terminal, no corresponding solution exists at present.

Disclosure of Invention

The embodiment of the application provides an EDI acquisition method, a routing reconfiguration method, an ECS address configuration information acquisition method, a DNS processing device and DNS processing equipment, which can solve the problem of how to establish PDU session for a terminal in a roaming place.

In a first aspect, an EDI obtaining method is provided, where the EDI obtaining method includes: the first network element sends a query request to the second network element, wherein the query request is used for requesting to query the third network element; the first network element receives a query response sent by the second network element, wherein the query response comprises address information of the third network element; the first network element sends a target request to the third network element according to the address information, wherein the target request is used for requesting to obtain the EDI of the roaming place operator from the fourth network element; the first network element receives the EDI sent by the third network element.

In a second aspect, an EDI obtaining apparatus is provided and applied to a first network element, where the EDI obtaining apparatus includes: a transmitting module and a receiving module. And the sending module is used for sending a query request to the second network element, wherein the query request is used for requesting to query the third network element. And the receiving module is used for receiving a query response sent by the second network element, wherein the query response comprises the address information of the third network element. And the sending module is further used for sending a target request to the third network element according to the address information, wherein the target request is used for requesting to obtain the EDI of the roaming place operator from the fourth network element. The receiving module is further configured to receive EDI sent by the third network element.

In a third aspect, an EDI obtaining method is provided, where the EDI obtaining method includes: the second network element receives a query request sent by the first network element, wherein the query request is used for requesting to query the third network element; the second network element sends a query response to the first network element, wherein the query response comprises the address information of the third network element; the address information is used for the first network element to send a target request to the third network element, wherein the target request is used for requesting to obtain the EDI of the roaming place operator from the fourth network element.

In a fourth aspect, an EDI obtaining apparatus is provided and applied to a second network element, where the EDI obtaining apparatus includes: a receiving module and a transmitting module. And the receiving module is used for receiving a query request sent by the first network element, wherein the query request is used for requesting to query the third network element. And the sending module is used for sending a query response to the first network element, wherein the query response comprises the address information of the third network element. The address information is used for the first network element to send a target request to the third network element, wherein the target request is used for requesting to obtain the EDI of the roaming place operator from the fourth network element.

In a fifth aspect, there is provided an EDI obtaining method, including: the third network element receives a target request sent by the first network element, wherein the target request is used for requesting to obtain the EDI of the roaming operator from the fourth network element; the third network element sends EDI to the first network element.

In a sixth aspect, an EDI obtaining apparatus is provided and applied to a third network element, where the EDI obtaining apparatus includes: a receiving module and a transmitting module. The receiving module is used for receiving a target request sent by the first network element, wherein the target request is used for requesting to obtain the EDI of the roaming operator from the fourth network element. And the sending module is used for sending the EDI to the first network element.

In the embodiment of the application, the first network element can inquire the third network element by sending an inquiry request to the second network element, and after the third network element is found, the first network element requests the third network element to acquire the EDI of the roaming place operator from the fourth network element so as to acquire the EDI, so that a DNS message processing rule is generated according to the EDI, and the establishment of the PDU session of the roaming place is realized.

In a seventh aspect, a route reconfiguration method is provided, the route reconfiguration method including: the first target network element receives a first target notification message sent by the fourth network element, wherein the first target notification message is used for notifying the changed AF route influence request information in the fourth network element; the first target network element sends a second target notification message to the second target network element, wherein the second target notification message comprises updated policy information, and the policy information is used for the second target network element to reconfigure the flow route.

An eighth aspect provides a route reconfiguration device applied to a first target network element, the route reconfiguration device comprising: a receiving module and a transmitting module. The receiving module is used for receiving a first target notification message sent by the fourth network element, wherein the first target notification message is used for notifying the changed AF route influence request information in the fourth network element. The sending module is used for sending a second target notification message to the second target network element, wherein the second target notification message comprises updated strategy information, and the strategy information is used for the second target network element to reconfigure the flow route.

A ninth aspect provides a route reconfiguration method, the route reconfiguration method including: the second target network element receives a second target notification message sent by the first target network element, wherein the second target notification message comprises updated strategy information, and the strategy information is used for reconfiguring the flow route by the second target network element; the second target notification message is sent by the first target network element after receiving the first target notification message sent by the fourth network element, where the first target notification message is used to notify the fourth network element of the changed AF route influence request information.

In a tenth aspect, a route reconfiguration device is provided, applied to a second target network element, where the route reconfiguration device includes: and a receiving module. The receiving module is used for receiving a second target notification message sent by the first target network element, wherein the second target notification message comprises updated strategy information, and the strategy information is used for reconfiguring the flow route by the second target network element; the second target notification message is sent by the first target network element after receiving the first target notification message sent by the fourth network element, where the first target notification message is used to notify the fourth network element of the changed AF route influence request information, so as to implement establishment of the PDU session in the roaming place.

In the embodiment of the application, the first target network element can receive the first target notification message sent by the fourth network element and is used for notifying the changed AF route influence request information in the fourth network element, and then the first target network element can send updated strategy information to the second target network element according to the AF route influence request information so as to be used for the second target network element to reconfigure the flow route, thereby realizing the application of AF route influence to the HR session.

In an eleventh aspect, there is provided an ECS address configuration information acquiring method, including: the fifth network element receives ECS address configuration information sent by the first network element, wherein the ECS address configuration information comprises PLMN identifications; the fifth network element sends ECS address configuration information to the terminal, the ECS address configuration information being used by the terminal to establish a PDU session with the ECS in the roaming place.

In a twelfth aspect, there is provided an ECS address configuration information acquiring apparatus applied to a fifth network element, the ECS address configuration information acquiring apparatus including: a receiving module and a transmitting module. And the receiving module is used for receiving the ECS address configuration information sent by the first network element, wherein the ECS address configuration information comprises PLMN identifications. And the sending module is used for sending the ECS address configuration information to the terminal, wherein the ECS address configuration information is used for establishing a PDU session of the roaming place between the terminal and the ECS.

In the embodiment of the application, the first network element can send the ECS address configuration information under the HR session to the fifth network element, so that the fifth network element can send the ECS address configuration information to the terminal for the terminal to establish the PDU session of the roaming place with the ECS, thereby realizing the establishment of the PDU session of the roaming place.

In a thirteenth aspect, there is provided a DNS processing method including: in case the terminal enters a roaming state, the terminal performs at least one of: clearing the DNS cache; a DNS re-query request is sent requesting a reselection of EAS in roaming.

In a fourteenth aspect, there is provided a DNS processing device applied to a terminal, the DNS processing device including: and executing the module. An execution module, configured to execute at least one of the following in case that the terminal enters a roaming state: clearing the DNS cache; a DNS re-query request is sent requesting a reselection of EAS in roaming.

In the embodiment of the application, after the terminal enters the roaming place, the DNS cache can be emptied so that the terminal can find the EAS as soon as possible; and/or the terminal may initiate a DNS re-query request to reselect the optimal EAS at roaming; thereby realizing the establishment of PDU session of roaming place; thereby enabling establishment of a PDU session at the roaming place.

In a fifteenth aspect, there is provided a network element comprising a processor and a memory storing a program or instructions executable on the processor, the program or instructions implementing the steps of the method according to the first aspect, or implementing the steps of the method according to the third aspect, or implementing the steps of the method according to the fifth aspect.

In a sixteenth aspect, there is provided a network element comprising a processor and a communication interface, wherein the communication interface is configured to send a query request to a second network element, the query request being configured to request a query of a third network element; receiving a query response sent by the second network element, wherein the query response comprises address information of the third network element; according to the address information, a target request is sent to a third network element, wherein the target request is used for requesting to obtain the EDI of the roaming place operator from a fourth network element; and receiving the EDI sent by the third network element.

A seventeenth aspect provides a network element, including a processor and a communication interface, where the communication interface is configured to receive a query request sent by a first network element, where the query request is configured to request to query a third network element; sending a query response to the first network element, wherein the query response comprises the address information of the third network element; the address information is used for the first network element to send a target request to the third network element, wherein the target request is used for requesting to obtain the EDI of the roaming place operator from the fourth network element.

An eighteenth aspect provides a network element, including a processor and a communication interface, where the communication interface is configured to receive a target request sent by a first network element, where the target request is configured to request obtaining EDI of a roaming operator from a fourth network element; the third network element sends EDI to the first network element.

In a nineteenth aspect, there is provided a network element comprising a processor and a memory storing a program or instructions executable on the processor, the program or instructions implementing the steps of the method according to the seventh aspect or the steps of the method according to the ninth aspect when executed by the processor.

In a twentieth aspect, there is provided a network element, including a processor and a communication interface, where the communication interface is configured to receive a first target notification message sent by a fourth network element, where the first target notification message is configured to notify an AF route impact request information that has been changed in the fourth network element; and sending a second target notification message to the second target network element, wherein the second target notification message comprises updated policy information, and the policy information is used for the second target network element to reconfigure the traffic route.

In a twenty-first aspect, a network element is provided, including a processor and a communication interface, where the communication interface is configured to receive a second target notification message sent by a first target network element, where the second target notification message includes updated policy information, and the policy information is used for traffic route reconfiguration by the second target network element; the second target notification message is sent by the first target network element after receiving the first target notification message sent by the fourth network element, where the first target notification message is used to notify the fourth network element of the changed AF route influence request information.

In a twenty-second aspect, there is provided a network element comprising a processor and a memory storing a program or instructions executable on said processor, said program or instructions implementing the steps of the method according to the eleventh aspect when executed by said processor.

In a twenty-third aspect, a network element is provided, including a processor and a communication interface, where the communication interface is configured to receive ECS address configuration information sent by a first network element, where the ECS address configuration information includes a PLMN identity; and transmitting ECS address configuration information to the terminal, wherein the ECS address configuration information is used for establishing PDU session of roaming place between the terminal and the ECS.

In a twenty-fourth aspect, there is provided a terminal comprising a processor and a memory storing a program or instructions executable on the processor, which when executed by the processor, implement the steps of the method according to the thirteenth aspect.

In a twenty-fifth aspect, a terminal is provided, comprising a processor and a communication interface, wherein the processor is configured to perform at least one of the following in case the terminal enters a roaming state: clearing the DNS cache; a DNS re-query request is sent requesting a reselection of EAS in roaming.

A twenty-sixth aspect provides a readable storage medium having stored thereon a program or instructions which when executed by a processor, performs the steps of the method as described in the first aspect, or performs the steps of the method as described in the third aspect, or performs the steps of the method as described in the fifth aspect, or performs the steps of the method as described in the seventh aspect, or performs the steps of the method as described in the ninth aspect, or performs the steps of the method as described in the eleventh aspect, or performs the steps of the method as described in the thirteenth aspect.

In a twenty-seventh aspect, there is provided a chip comprising a processor and a communication interface, the communication interface and the processor being coupled, the processor being adapted to run a program or instructions, to implement the method according to the first aspect, or to implement the method according to the third aspect, or to implement the method according to the fifth aspect, or to implement the method according to the seventh aspect, or to implement the method according to the ninth aspect, or to implement the method according to the eleventh aspect, or to implement the method according to the thirteenth aspect.

A twenty-eighth aspect provides a computer program/program product stored in a storage medium, the computer program/program product being executable by at least one processor to perform the steps of the method as described in the first aspect, or to perform the steps of the method as described in the third aspect, or to perform the steps of the method as described in the fifth aspect, or to perform the steps of the method as described in the seventh aspect, or to perform the steps of the method as described in the ninth aspect, or to perform the steps of the method as described in the eleventh aspect.

Drawings

Fig. 1 is a schematic diagram of a wireless communication system according to an embodiment of the present application;

fig. 2 is one of flowcharts of an EDI obtaining method according to an embodiment of the present application;

FIG. 3 is a second flowchart of an EDI acquisition method according to an embodiment of the present application;

fig. 4 is one of flowcharts of a route reconfiguration method according to an embodiment of the present application;

FIG. 5 is a second flowchart of a route reconfiguration method according to an embodiment of the present application;

FIG. 6 is a third flowchart of a route reconfiguration method according to an embodiment of the present application;

FIG. 7 is a flowchart of a route reconfiguration method according to an embodiment of the present application;

FIG. 8 is a flowchart of a route reconfiguration method according to an embodiment of the present application;

fig. 9 is a flowchart of a method for acquiring ECS address configuration information according to an embodiment of the present application;

fig. 10 is a flowchart of a DNS processing method provided in an embodiment of the present application;

fig. 11 is a schematic structural diagram of an EDI obtaining device according to an embodiment of the present application;

fig. 12 is a second schematic structural diagram of an EDI obtaining device according to an embodiment of the application;

fig. 13 is a third schematic structural diagram of an EDI obtaining device according to an embodiment of the application;

fig. 14 is a schematic structural diagram of a route reconfiguration device according to an embodiment of the present application;

FIG. 15 is a second schematic diagram of a route reconfiguration device according to an embodiment of the present application;

fig. 16 is a schematic structural diagram of an ECS address configuration information acquiring apparatus according to an embodiment of the present application;

fig. 17 is a schematic structural diagram of a DNS processing device according to an embodiment of the present application;

fig. 18 is a schematic hardware structure of a communication device according to an embodiment of the present application;

fig. 19 is a schematic hardware structure of a network element according to an embodiment of the present application;

Fig. 20 is a schematic hardware structure of a terminal according to an embodiment of the present application.

FIG. 21 is a flowchart of a route reconfiguration method according to an embodiment of the present application;

FIG. 22 is a flow chart of a route reconfiguration method according to an embodiment of the present application;

fig. 23 is a third schematic structural diagram of a route reconfiguration device according to an embodiment of the present application;

fig. 24 is a schematic structural diagram of an information sending device according to an embodiment of the present application.

Fig. 25 is a flowchart of a route reconfiguration method according to an embodiment of the present application.

Fig. 26 is a schematic structural diagram of a reconfiguration device according to an embodiment of the present application.

Detailed Description

The technical solutions of the embodiments of the present application will be clearly described below with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which are derived by a person skilled in the art based on the embodiments of the application, fall within the scope of protection of the application.

The terms first, second and the like in the description and in the claims, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the terms so used are interchangeable under appropriate circumstances such that the embodiments of the application are capable of operation in sequences other than those illustrated or otherwise described herein, and that the "first" and "second" distinguishing between objects generally are not limited in number to the extent that the first object may, for example, be one or more. Furthermore, in the description and claims, "and/or" means at least one of the connected objects, and the character "/" generally means a relationship in which the associated object is an "or" before and after.

It should be noted that the techniques described in the embodiments of the present application are not limited to long term evolution (Long Term Evolution, LTE)/LTE evolution (LTE-Advanced, LTE-a) systems, but may also be used in other wireless communication systems, such as code division multiple access (Code Division Multiple Access, CDMA), time division multiple access (Time Division Multiple Access, TDMA), frequency division multiple access (Frequency Division Multiple Access, FDMA), orthogonal frequency division multiple access (Orthogonal Frequency Division Multiple Access, OFDMA), single carrier frequency division multiple access (Single-carrier Frequency Division Multiple Access, SC-FDMA), and other systems. The terms "system" and "network" in embodiments of the application are often used interchangeably, and the techniques described may be used for both the above-mentioned systems and radio technologies, as well as other systems and radio technologies. The following description describes a New air interface (NR) system for purposes of example and uses NR terminology in much of the description that follows, but these techniques are also applicable to applications other than NR system applications, such as generation 6 (6) ^th Generation, 6G) communication system.

Fig. 1 shows a block diagram of a wireless communication system to which an embodiment of the present application is applicable. The wireless communication system includes a terminal 11 and a network device 12. The terminal 11 may be a mobile phone, a tablet (Tablet Personal Computer), a Laptop (Laptop Computer) or a terminal-side Device called a notebook, a personal digital assistant (Personal Digital Assistant, PDA), a palm top, a netbook, an ultra-mobile personal Computer (ultra-mobile personal Computer, UMPC), a mobile internet appliance (Mobile Internet Device, MID), an augmented reality (augmented reality, AR)/Virtual Reality (VR) Device, a robot, a Wearable Device (weather Device), a vehicle-mounted Device (VUE), a pedestrian terminal (PUE), a smart home (home Device with a wireless communication function, such as a refrigerator, a television, a washing machine, or a furniture), a game machine, a personal Computer (personal Computer, PC), a teller machine, or a self-service machine, and the Wearable Device includes: intelligent wrist-watch, intelligent bracelet, intelligent earphone, intelligent glasses, intelligent ornament (intelligent bracelet, intelligent ring, intelligent necklace, intelligent anklet, intelligent foot chain etc.), intelligent wrist strap, intelligent clothing etc.. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network-side device 12 may comprise an access network device or a core network device, wherein the access network device 12 may also be referred to as a radio access network device, a radio access network (Radio Access Network, RAN), a radio access network function or a radio access network element. Access network device 12 may include a base station, a WLAN access point, a WiFi node, or the like, which may be referred to as a node B, an evolved node B (eNB), an access point, a base transceiver station (Base Transceiver Station, BTS), a radio base station, a radio transceiver, a basic service set (Basic Service Set, BSS), an extended service set (Extended Service Set, ESS), a home node B, a home evolved node B, a transmission and reception point (Transmitting Receiving Point, TRP), or some other suitable terminology in the art, and the base station is not limited to a particular technical vocabulary so long as the same technical effect is achieved, and it should be noted that in the embodiment of the present application, only a base station in the NR system is described as an example, and the specific type of the base station is not limited. The core network device may include, but is not limited to, at least one of: core network nodes, core network functions, mobility management entities (Mobility Management Entity, MME), access mobility management functions (Access and Mobility Management Function, AMF), session management functions (Session Management Function, SMF), user plane functions (User Plane Function, UPF), policy control functions (Policy Control Function, PCF), policy and charging rules function units (Policy and Charging Rules Function, PCRF), edge application service discovery functions (Edge Application Server Discovery Function, EASDF), unified data management (Unified Data Management, UDM), unified data repository (Unified Data Repository, UDR), home subscriber server (Home Subscriber Server, HSS), centralized network configuration (Centralized network configuration, CNC), network storage functions (Network Repository Function, NRF), network opening functions (Network Exposure Function, NEF), local NEF (or L-NEF), binding support functions (Binding Support Function, BSF), application functions (Application Function, AF), and the like. It should be noted that, in the embodiment of the present application, only the core network device in the NR system is described as an example, and the specific type of the core network device is not limited.

In this patent, the first network element, the first target network element, the second network element, the third network element, the fourth network element, the fifth network element, and the sixth network element may be one or more of the above core network devices.

The first network element, in this patent, is an SMF or a home SMF, or may be one or more other devices in the above core network devices.

The first target network element, in this patent, is a PCF or a home PCF, or may be one or more other devices in the above core network devices.

The second target network element may be an SMF, a home SMF, or a roaming SMF, or may be one or more other devices in the above core network devices.

The second network element, in this patent, is an NRF or a roaming NRF, or may be one or more other devices in the above core network devices.

The third network element, in this patent, may be a NEF or a roaming NEF, or may be one or more other devices in the above core network devices.

The fourth network element, in this patent, may be UDR or roaming UDR, or may be one or more other devices in the above core network devices.

The fifth network element, in this patent, may be an SMF or a roaming SMF, or may be one or more other devices in the above core network devices.

The sixth network element, in this patent, is a PCF or a roaming PCF, or may be one or more other devices in the above core network devices.

In this patent, the first information or the second information, or the first notification message, the second notification message, or the first target notification message, or the second target notification message is used for at least one of the following items:

requesting SMF routing decisions (influence SMF routeing decisions for User Plane traffic of PDU Sessions) that affect user plane traffic in the PDU session;

influence the UPF selection or reselection (refluence UPF (re) selection);

the user plane is allowed to route traffic to the data network (allow routeing of user traffic to alocal access (identified by a DNAI) to a Data Network) through a local ingress.

In this patent, the first information or the second information, or the first notification message, the second notification message, or the first target notification message, or the second target notification message may include at least one of the following:

AF (application function) request;

A traffic influencing request (request for traffic influence);

PCC (Policy and Charging Control) rule (PCC rule);

AF affects flow split execution control (AF influenced Traffic Steering Enforcement Control);

AF request information (AF request information);

AF flow effect request information (AF traffic influence request information);

policy information (policy information)

Flow influencing parameters (traffic influence parameters).

The above AF request, the flow influencing request, the PCC rule, the AF influencing flow splitting execution control, the AF request information, the AF flow influencing request information, or the policy information, or the flow influencing parameter, etc. include at least one of the following contents, which are shown in table 0:

TABLE 0

The following explains some concepts and/or terms related to EDI acquisition, route reconfiguration, ECS address configuration information acquisition, DNS processing methods, devices and equipment provided in the embodiments of the present application.

The edge application server discovery function (Edge Application Server Discovery Function, EASDF) network element is a newly proposed core network element for handling domain name system (Domain Name System, DNS) query requests sent by the terminal.

The EASDF network element is a network element for processing DNS query of a terminal, specifically, the terminal sends the DNS query to the EASDF network element, then the EASDF network element determines according to the DNS query, whether to send the DNS query to a Central DNS (C-DNS) or a Local DNS (L-DNS), and then sends information such as a fully defined domain name (Fully Qualified Domain Name, FQDN) in the DNS query to the SMF network element, where the SMF network element provides a network protocol (Internet Protocol, IP) address of a corresponding DNS server for the EASDF, for example: C-DNS or L-DNS; then, after the C-DNS or the L-DNS detects the IP address corresponding to the FQDN, the IP address is sent to the EASDF network element, and the EASDF network element stores the query result to the SMF network element and then sends the query result to the terminal. The terminal thus obtains the server IP address of the requested FQDN.

The EDI obtaining method, the route reconfiguration method, the ECS address configuration information obtaining method and the DNS processing method provided by the embodiments of the present application are described in detail below with reference to the accompanying drawings through some embodiments and application scenarios thereof.

Problem 1: generation of DNS processing rules in roaming scenarios

In roaming scenarios, home EASDF (H-EASDF) is responsible for using DNS processing rules and H-SMF is responsible for generating DNS processing rules. But because the terminal is roaming, the terminal needs to visit DNS processing rules of the roaming nearby, and needs to use edge application server deployment information (Edge Application Server Deployment Information, EDI) of the roaming. However, under the home public land mobile network (Home Public Land Mobile Network, H-PLMN), there is no corresponding solution at present how to obtain EDI information of roaming sites.

In view of the above problem 1, in the embodiment of the present application, a Home SMF (H-SMF) network element may generate a DNS message processing rule by acquiring EDI from a Visited UDR (virtual-UDR, V-UDR) network element, specifically, after the H-SMF queries a Visited NEF (virtual-NEF, V-NEF) network element, the H-SMF requests the V-NEF network element to acquire EDI of a roaming operator from the V-UDR network element, so as to acquire EDI, thereby generating the DNS message processing rule according to EDI.

Problem 2: AF traffic routing impact (traffic influence)

Traffic influence A method for AF to influence 5GC route is that a terminal establishes connection with a certain service server, when the service server is changed, the connection between the terminal and the service server is influenced after the IP address of the server is changed. The AF needs to provide information about the affected routes to the 5GC for reconfiguration of the user plane. However, under Home Routed (HR) session (session), currently AF traffic influence is not supported, i.e., currently AF request routing impact cannot be used for HR session.

In view of the above problem 2, in the embodiment of the present application, a Home PCF (H-PCF) network element or a Visited PCF (V-PCF) network element may receive a notification message sent by a V-UDR network element, where the notification message is used to notify an AF route impact request information that has been changed in the V-UDR network element, and then send updated policy information to an H-SMF network element and/or a V-SMF network element according to the AF route impact request information, so as to be used for traffic route reconfiguration by the H-SMF network element and/or the V-SMF network element, thereby implementing application of an AF route impact to an HR session.

Problem 3: how the terminal establishes a protocol data unit (Protocol Data Unit, PDU) session with the edge configuration server (Edge Configuration Server, ECS) for roaming locations, no corresponding solution exists at present.

In view of the above problem 3, in the embodiment of the present application, the H-SMF network element may send ECS address configuration information to the V-SMF network element, so that the V-SMF network element may send the ECS address configuration information to the terminal, so as to be used for the terminal to establish a PDU session with the ECS in a roaming place.

Problem 4: after the terminal enters the roaming place, the visited edge server may not be the optimal server according to the policy of the roaming place, and there is no clear scheme for the operation of the terminal.

Aiming at the problem 4, in the embodiment of the application, after the terminal enters the roaming place, the DNS cache can be emptied so that the terminal can find the EAS as soon as possible; and/or the terminal may initiate a DNS re-query request to reselect the optimal EAS roaming.

The embodiment of the application provides an EDI acquisition method, and fig. 2 shows a flow chart of the EDI acquisition method provided by the embodiment of the application. As shown in fig. 2, the EDI obtaining method provided by the embodiment of the application may include the following steps 201 to 208.

Step 201, the first network element sends a query request to the second network element.

In the embodiment of the present application, the query request is used to request to query the third network element.

Optionally, in an embodiment of the present application, the first network element may be an H-SMF network element. The second network element may be a V-NRF network element, and the third network element may be a V-NEF network element. It should be noted that, the first network element, the second network element, and the third network element may be other network elements, which is not limited by the embodiment of the present application. EDI is acquired from the roaming place and is acquired through a third network element.

Optionally, in an embodiment of the present application, the query request includes at least one of the following: PLMN identity, subscriber permanent identity (Subscription Permanent Identifier, SUPI).

Optionally, in an embodiment of the present application, the PLMN identifier includes at least one of the following: visited PLMN (V-PLMN) identity, H-PLMN identity.

Alternatively, in the embodiment of the present application, the above step 201 may be specifically implemented by the following step 201 a.

Step 201a, the first network element sends a query request to the second network element via a Home NRF (H-NRF) network element.

Optionally, in an embodiment of the present application, the query Request may be an nrf_nfdiscovery_request.

Step 202, the second network element receives the query request sent by the first network element.

Alternatively, in the embodiment of the present application, the above step 202 may be specifically implemented by the following step 202 a.

Step 202a, the second network element receives a query request sent by the first network element via the home network storage function H-NRF network element.

Step 203, the second network element sends a query response to the first network element.

In the embodiment of the present application, the query response includes address information of the third network element. The address information is used for the first network element to send a target request to the third network element, wherein the target request is used for requesting to obtain the EDI of the roaming place operator from the fourth network element.

Optionally, in an embodiment of the present application, the fourth network element may be a V-UDR network element.

Optionally, in an embodiment of the present application, the address information of the third network element includes at least one of the following: IP address, FQDN of the third network element.

Optionally, in the embodiment of the present application, after the second network element finds the third network element, a query response may be sent to the H-NRF network element, so as to send the address information of the third network element to the H-NRF network element, and then the H-NRF network element sends the address information of the third network element to the first network element.

Alternatively, in the embodiment of the present application, the query Response may be nnrf_nfdiscovery_response.

Step 204, the first network element receives the query response sent by the second network element.

Step 205, the first network element sends a target request to the third network element according to the address information of the third network element.

In the embodiment of the present application, the target request is used to request to obtain the EDI of the roaming operator from the fourth network element.

Optionally, in an embodiment of the present application, the target request includes at least one of the following: PLMN identification, single network slice selection assistance information (Single Network Slice Selection Assistance Information, S-nsai), data network name (Data Network Name, DNN).

Optionally, in an embodiment of the present application, the target request may be nnef_easliployment_subscnibe or nnef_easliployment_get.

Step 206, the third network element receives the target request sent by the first network element.

Step 207, the third network element sends EDI to the first network element.

Step 208, the first network element receives the EDI sent by the third network element.

The embodiment of the application provides an EDI acquisition method, a first network element can inquire a third network element by sending an inquiry request to a second network element, and after the third network element is found, the first network element requests the third network element to acquire EDI of a roaming place operator from a fourth network element so as to acquire the EDI, so that DNS message processing rules are generated according to the EDI, and the establishment of PDU session of the roaming place is realized.

Optionally, the EDI obtaining method provided by the embodiment of the present application further includes the following step 209 and step 210, and the above step 201 may be specifically implemented through the following step 201 b.

Step 209, the first network element sends a first request to the UDM network element.

In the embodiment of the present application, the first request is used for requesting to obtain subscription information of a terminal, where the terminal is in a roaming place and needs to establish a PDU session or update the PDU session, and the subscription information is used for indicating whether the terminal is authorized to use a roaming place edge computing service, and the first request includes a PLMN identifier.

Step 210, the first network element receives a first response sent by the UDM network element.

In the embodiment of the present application, the first response includes subscription information of the terminal.

Step 201b, in case the subscription information indicates that the terminal is authorized to use the roaming place edge calculation service, the first network element sends a query request to the second network element.

Optionally, in the embodiment of the present application, before the step 207, the EDI obtaining method provided in the embodiment of the present application further includes a step 211 described below, and the step 207 may be specifically implemented by a step 207a described below.

Step 211, the third network element verifies the first network element according to the target request to determine whether the first network element is authorized to obtain data from the roaming operator to which the EDI belongs.

Step 207a, in the case of verifying that the first network element is authorized to obtain data from the roaming operator to which the EDI belongs, the third network element obtains the EDI from the fourth network element and sends the EDI to the first network element.

The EDI obtaining method provided by the embodiment of the application is described below through a specific embodiment (i.e., embodiment one).

Embodiment one: H-SMF network element recovers EDI from V-NEF network element

As shown in fig. 3, the EDI obtaining method provided by the embodiment of the application may include the following steps 21 to 33.

Step 21, the V-SMF network element sends a session establishment or update request to the H-SMF network element.

The signaling is: nsmf_pduse_create/Update request.

And step 22, the H-SMF network element recovers the subscription information of the terminal from the UDM network element.

In the embodiment of the present application, the subscription information indicates whether the terminal can use the edge computing service in roaming.

The signaling is: nudm_sdm_get or nudm_sdm_subscnibe. The signaling needs to include the SUPI, PLMN ID of the terminal. The PLMN ID may be a roaming PLMN ID or a home PLMN ID. In this way, the terminal subscription information under a specific operator can be recovered from the UDM.

The subscription information that the H-SMF network element needs to obtain is shown in table 1 below: in another embodiment, the V-SMF obtains the subscription information. The V-SMF checks whether the terminal is able to use EASDF for EAS lookup under roaming operators.

Table 1

Specifically, the session management subscription data may include at least one of the following table 2:

table 2

The input content includes: nfid=h-SMF; subscription Data type (S) =supi, data Sub Key (S) =s-NSSAI, DNN, PLMN ID. Wherein a roaming PLMN ID (VPLMN ID) among PLMN IDs is necessary.

It should be noted that, if the terminal is found to be unable to use the service of edge calculation after subscription information verification, the process after step 23 is skipped entirely and not performed.

Step 23, the H-SMF network element selects the H-EASDF network element.

And step 24, the H-SMF network element sends a query request to the H-NRF network element.

The signaling is: the nrrf_nfdiscovery_request requests to find V-NEF network elements.

In the embodiment of the application, since the H-EASDF network element is already selected for the roaming terminal, the H-SMF network element needs to configure basic DNS processing rules (Baseline DNS Pattern) for the H-EASDF network element.

However, baselineDNSPattern needs to be derived according to EDI, and the EDI information is stored in the V-UDR network element of the roaming place; thus, the H-SMF network element needs to recover this information from the V-UDR network element. Then the H-SMF network element needs to send a query request to the H-NRF network element to request a search for V-NEF network elements.

The parameters in the query request may include at least one of: PLMN ID (e.g., PLMN ID of roaming), SUPI.

Step 25, the H-NRF network element triggers the inquiry to the V-NRF network element.

It should be noted that the signaling and parameters of step 25 are the same as those of step 24.

And 26, the V-NRF network element finds the V-NEF network element and sends the IP address, FQDN and the like of the V-NEF network element to the H-NRF network element.

The signaling is: nnrf_NFdiscovery_response.

The parameters in the signaling may include at least one of: V-NEF IP address, FQDN.

Step 27, the H-NRF network element sends the found IP address, FQDN and the like of the V-NEF network element to the H-SMF network element.

Step 28, the H-SMF network element requests the V-NEF network element to obtain the EDI from the V-UDR network element.

The signaling is: nnef_easliployment_ Subscribe Request or nnef_easliployment_get Request.

The parameters in the signaling may include at least one of: PLMN IDs (e.g., roaming PLMN IDs or home PLMN IDs), DNNs, S-nsais, etc. For example, in this step, the H-SMF may indicate the home PLMN ID, to the V-NEF, requesting access to the roaming location EDI stored in the V-UDR.

Step 29, the V-NEF network element requests to send a response to the H-SMF network element.

The signaling is: nnef_easliployment_ Subscribe Response or nnef_easliployment_get Response.

Step 30, the V-NEF network element needs to verify whether the H-SMF network element can obtain EDI from the V-UDR network element. If the HPLMN in which the H-SMF is located does not qualify to obtain EDI from the V-UDR, then the V-NEF denies the H-SMF request to obtain EDI.

And step 30 and 32, if the verification is passed, the V-NEF network element recovers EDI from the V-UDR network element.

And step 33, the V-NEF network element transmits the EDI to the H-SMF network element.

The signaling is: nnef_easidoyment_notify.

It should be noted that, in the EDI obtaining method provided by the embodiment of the present application, the execution body may also be an EDI obtaining device, or a control module in the EDI obtaining device for executing the EDI obtaining method.

The embodiment of the application provides a route reconfiguration method, and fig. 4 shows a flow chart of the route reconfiguration method provided by the embodiment of the application. As shown in fig. 4, the route reconfiguration method provided by the embodiment of the present application may include the following steps 301 to 303.

Step 301, a first target network element receives a first target notification message sent by a fourth network element.

In the embodiment of the present application, the first target notification message is used to notify the modified AF route influence request information in the fourth network element.

Optionally, in the embodiment of the present application, the first target network element may be an H-PCF network element, a V-PCF network element, or other network elements.

Optionally, in an embodiment of the present application, the AF routing impact request information (AF traffic influence request information) includes at least one of the following: traffic description information, identification of the terminal to which traffic will be affected, traffic routing information of the target interface, data network access identification, PLMN identification.

It should be noted that, the traffic description information (Traffic Description) defines the target traffic to be affected (represented by the DNN and optional S-nsai combination), and the application identifier or traffic filtering information. The purpose of the AF route influencing request information is to influence the current route, then it is first necessary to give which traffic is to be influenced, and the traffic description is to tell the 5GC to identify the target traffic.

The identity (Target UE Identifier (s)) of the terminals to which the traffic is to be affected refers to which terminals the traffic is to be affected.

Optionally, in an embodiment of the present application, the target interface may be an N6 interface. Traffic routing information for N6 interface (N6 Traffic Routing requirements): servers are all deployed in DNs, and UPFs and DNs are connected through an N6 interface.

The data network access identifier (Data Network Access Identifier): user plane identifiers of one or more Data Networks (DNs) in which the application is located.

Optionally, in an embodiment of the present application, the PLMN identifier may include at least one of the following: V-PLMN, H-PLMN.

Step 302, the first target network element sends a second target notification message to the second target network element.

In the embodiment of the present application, the second target notification message includes updated policy information, where the policy information is used for the second target network element to reconfigure the traffic route.

Optionally, in the embodiment of the present application, the second target network element may be an H-SMF network element, or an H-SMF network element and a V-SMF network element, or other network elements.

Alternatively, in one implementation manner of the embodiment of the present application, the above step 302 may be specifically implemented by the following step 302 a.

Step 302a, the first target network element sends a first notification message to the first network element.

In the embodiment of the present application, the first notification message is used to notify that the current HR session is affected by the AF request; the first notification message is used for the first network element to perform traffic route reconfiguration and sends a second notification message to the fifth network element, the second notification message is used for notifying the PDU session of the roaming place that needs to be changed, and the second notification message is used for the fifth network element to perform traffic route reconfiguration.

Optionally, in the embodiment of the present application, the fifth network element may be a V-SMF network element or other network elements.

Alternatively, in such an implementation, the first target network element may be an H-PCF network element.

Alternatively, in another implementation manner of the embodiment of the present application, the above step 302 may be specifically implemented by the following steps 302b and 302 c.

Step 302b, the first target network element sends a first notification message to the first network element.

In the embodiment of the present application, the first notification message is used to notify that the current HR session is affected by the AF request, and the first notification message is used to reconfigure the traffic route by the first network element.

Step 302c, the first target network element sends a second notification message to the fifth network element.

In the embodiment of the present application, the second notification message is used to notify that the PDU session in the roaming place needs to be changed, and the second notification message is used for the fifth network element to reconfigure the flow route.

Alternatively, in yet another implementation manner of the embodiment of the present application, the above step 301 may be specifically implemented by the following step 301a, and the above step 302 may be specifically implemented by the following steps 302d and 302 e.

Step 301a, the first target network element receives a first target notification message sent by the fourth network element via the sixth network element.

Optionally, in an embodiment of the present application, the sixth network element may be a V-PCF network element.

Step 302d, the first target network element sends a first notification message to the first network element.

Step 302e, the first target network element sends a second notification message to the fifth network element.

Alternatively, in yet another implementation manner of the embodiment of the present application, the above step 302 may be specifically implemented by the following step 302 f.

Step 302f, the first target network element sends a first notification message to the fifth network element.

In the embodiment of the present application, the first notification message is used to notify that the current HR session is affected by the AF request; the first notification message is used for the fifth network element to perform traffic route reconfiguration, and sends a second notification message to the first network element, wherein the second notification message is used for notifying that the PDU session of the roaming place needs to be changed, and the second notification message is used for the fifth network element to perform traffic route reconfiguration under the condition that the first network element agrees to execute the PDU session change.

Alternatively, in such an implementation, the first target network element may be a V-PCF network element.

Step 303, the second target network element receives the second target notification message sent by the first target network element.

In the embodiment of the present application, the second target notification message is sent by the first target network element after receiving the first target notification message sent by the fourth network element.

Alternatively, in an implementation manner of the embodiment of the present application, the above step 303 may be specifically implemented by the following steps 303a and 303 b.

Step 303a, the second target network element receives, through the first network element, the first notification message sent by the first target network element.

Step 303b, the second target network element receives the second notification message sent by the first network element through the fifth network element.

Alternatively, in another implementation manner of the embodiment of the present application, the above step 303 may be specifically implemented by the following steps 303c and 303 d.

Step 303c, the second target network element receives, through the first network element, the first notification message sent by the first target network element.

Step 303d, the second target network element receives the second notification message sent by the first target network element through the fifth network element.

Optionally, in another implementation manner of the embodiment of the present application, the first target notification message is sent by the fourth network element to the first target network element via the sixth network element. The above step 303 can be specifically realized by the following steps 303e and 303 f.

Step 303e, the second target network element receives, through the first network element, the first notification message sent by the first target network element.

Step 303f, the second target network element receives the second notification message sent by the first target network element through the fifth network element.

Alternatively, in yet another implementation manner of the embodiment of the present application, the above step 303 may be specifically implemented by the following steps 303g and 303 h.

Step 303g, the second target network element receives the first notification message sent by the first target network element through the fifth network element.

In the embodiment of the present application, the first notification message is used to notify that the current HR session is affected by the AF request, and the first notification message is used for the fifth network element to reconfigure the traffic route.

Step 303h, the second target network element receives the second notification message sent by the fifth network element through the first network element.

In the embodiment of the present application, the second notification message is used to notify that the PDU session in the roaming place needs to be changed, and the second notification message is used to reconfigure the flow route by the fifth network element when the first network element agrees to execute the PDU session change.

Optionally, in an embodiment of the present application, the second notification message includes at least one of the following: data network access identification, traffic routing information of a target interface, affected user plane function identification, affected PDU session identification, affected terminal identification, PLMN identification.

Optionally, in the embodiment of the present application, a manner in which the fifth network element performs traffic routing reconfiguration includes at least one of the following:

reselecting or replacing the user plane;

establishing a PDU session to a visitor location EAS;

the user plane is instructed to replace the source destination EAS address accessed by the terminal with a destination EAS address carried by the first destination announcement message.

The embodiment of the application provides a route reconfiguration method, wherein a first target network element can receive a first target notification message sent by a fourth network element and is used for notifying the fourth network element of changed AF route influence request information, and then the first target network element can send updated strategy information to a second target network element according to the AF route influence request information so as to be used for traffic route reconfiguration of the second target network element, thereby realizing application of AF route influence to an HR session.

The route reconfiguration method provided by the embodiment of the present application is described below by means of specific embodiments (i.e., embodiment two to embodiment five).

Embodiment two: V-UDR network element informing H-PCF network element

As shown in fig. 5, the route reconfiguration method provided by the embodiment of the present application may include the following steps 41 to 50.

Step 41 to step 45: existing processes.

The AF network element provides traffic routing impact (traffic influence) information to the V-UDR network element. The content of the traffic routing impact information is prior art.

Step 46, the V-UDR network element sends a notification message to the H-PCF network element to notify the change of the AF route influence request information stored in the V-UDR network element, and sends the changed information to the H-PCF.

The signaling is: nudr_dn_notify.

In the embodiment of the application, since the V-PCF network element does not play any role in the HR session (the V-PCF network element herein is, to be precise, the V-SM-PCF network element, the session management PCF), the V-UDR network element needs to notify the H-PCF network element of the change of information stored in the V-UDR network element, which is herein the AF route influence request information stored in the V-UDR network element (AF traffic influence request information).

The AF route influence request information contains the following contents:

flow description information (Traffic Description): define the target traffic to be affected (represented by the DNN and optional S-NSSAI combination), and application identifier or traffic filtering information. The purpose of the AF request is to influence the current route, then it needs to be given first which traffic is to be affected, and the traffic description is to tell the 5GC to identify the target traffic;

Identification of the terminal (Target UE Identifier (s)) to which traffic will be affected: and the target terminal. The traffic of the target terminal will be affected;

traffic routing information for N6 interface (N6 Traffic Routing requirements): traffic routing information for the N6 interface. The server is deployed in DN, and UPF and DN are connected through N6 interface;

data network access identification (Data Network Access Identifier): user plane identifiers of one or more DNs where the application is located;

PLMN identification. The PLMN identity is information indicating under which PLMN the traffic affects routing is in effect.

The H-PCF network element may subscribe to changes in AF traffic influence request information information in the V-UDR network element.

The H-PCF network element informs the H-SMF network element of the current HR session, possibly affected by an AF request (request), steps 47-48.

The signaling used in step 47 is: npcf_smpolicycontrol_updatenotify.

The purpose of this signaling is that if the H-PCF network element receives a modification of the AF request stored in the UDR network element, at this time the existing PDU session is affected, then the H-PCF network element needs to issue a new policy and charging control (Policy and Charging Control, PCC) policy to the V-SMF network element.

For example, in the PCC policy, the AF request is reflected to affect the traffic route, which includes the following:

a data network access identification (Data Network Access Identifier);

per DNAI: traffic routing information for N6 interface (N6 traffic routing information): n6 traffic routing information with each DNAI as granularity.

There may be other content but the above is most important because our AF affects routing, which ultimately manifests itself in this N6 traffic routing information, which determines which DN traffic on the terminal will ultimately be routed to which application server.

Step 48 is optional: traffic routing rules of the possible home part change or the UPF reselects.

Step 48 may not occur, but steps 49-50 must occur.

Step 49, the H-SMF network element informs the V-SMF network element if the AF request affects the user plane reselection or the change of the routing rules of the roaming place.

This signaling is used to inform the roaming place that the PDU session needs to be changed.

Signaling: nsmf_pduse_update. Through the signaling, PCC rule is sent to roaming place V-SMF, and then V-SMF carries out relevant route reconfiguration according to strategy.

Parameters: PCC rule affected by AF request.

In this signaling, the H-SMF network element indicates to the V-SMF network element the following information:

a data network access identification (Data Network Access Identifier);

per DNAI: traffic routing information (N6 traffic routing information) for the N6 interface;

affected UPF network elements: the UPF ID, that is, the H-SMF network element should indicate to the V-SMF network element to which UPF the routing information should be applied;

affected PDU session ID: which PDU session ID corresponds to the session, the routing information should be changed;

UE ID。

after receiving the update, the V-SMF network element modifies the PDU session in the roaming place, for example:

reselecting the user plane, V-PSA, for routing terminal traffic to the roaming EAS;

EAS IP address replacement is performed. Generating FAR according to the IP address of the destination server (target EAS IP address), indicating roaming place UPF (such as V-PSA); the terminal would otherwise access the data packet of the roaming EAS 1 and use this FAR to forward to EAS 2.FAR: forwarding action rule, the configuration on the original UPF, i.e., the packet destined for EAS 1, is forwarded to a new EAS, e.g., EAS 2, after using the FAR.

It can be understood that in the second embodiment, the V-UDR network element may send a notification message to the H-PCF network element, for notifying the changed AF route impact request information in the V-UDR network element, and the H-PCF network element subscribes to the change of the AF route impact request information in the V-UDR network element; the H-PCF network element can send a notification message to the H-SMF network element, and is used for notifying that the current HR session of the terminal can be influenced by the AF request, and the H-SMF network element carries out flow route reconfiguration; the H-SMF network element sends a notification message to the V-SMF network element, and the notification message is used for notifying the PDU session of the roaming place to be changed, and the V-SMF network element modifies the PDU session of the roaming place to realize the reconfiguration of the flow route.

Embodiment III: H-PCF network element notification V-SMF network element

As shown in fig. 6, the route reconfiguration method provided by the embodiment of the present application may include the following steps 51 to 60.

Steps 51 to 58 refer to steps 41 to 48 in the above-described second embodiment.

Step 59, the H-PCF network element informs the V-SMF network element if the AF request affects the user plane reselection or the change of the routing rules of the roaming place.

Signaling: npcf_smpolicycontrol_updatenotify

Parameters: PCC rule affected by AF request.

In this manner, the updated PCC rule is not issued to the H-SMF, but directly to the V-SMF.

Step 60 may refer to step 50 in the second embodiment.

It can be understood that in the third embodiment, the V-UDR network element may send a notification message to the H-PCF network element, for notifying the changed AF route impact request information in the V-UDR network element, and the H-PCF network element subscribes to the change of the AF route impact request information in the V-UDR network element; the H-PCF network element sends a notification message to the H-SMF network element, and is used for notifying that the current HR session of the terminal can be influenced by the AF request, and the H-SMF network element performs data routing reconfiguration; the H-PCF network element sends a notification message to the V-SMF network element, and the notification message is used for notifying the PDU session of the roaming place to be changed, and the V-SMF network element modifies the PDU session of the roaming place to realize the reconfiguration of the flow route.

Embodiment four: V-PSA network element notification H-PCF network element

As shown in fig. 7, the route reconfiguration method provided in the embodiment of the present application may include the following steps 61 to 71.

Steps 61 to 65 refer to steps 41 to 45 in the above-described second embodiment.

Step 66, the V-UDR network element informs the V-PCF network element.

Step 67, the V-PCF network element informs the H-PCF network element.

The V-PCF network element and the H-PCF network element are provided with interfaces which can be communicated. Thus, the notification message in step 66 is forwarded to the H-PCF network element using the V-PCF network element.

Signaling in step 67 is used to transfer the information change stored in the V-UDR network element, here, the change information of AF traffic influence request information stored in the V-UDR network element (i.e., the changed application function AF route impact request information in the V-UDR network element).

Signaling: the signaling carries the changed application function AF route influence request information notified by the V-UDR network element.

Steps 68 to 71 may refer to steps 57 to 60 in the third embodiment described above.

It can be understood that in the fourth embodiment, the V-UDR network element may send a notification message to the V-PCF network element, for notifying the V-UDR network element of the changed AF route impact request information, where the V-PCF network element subscribes to the change of the AF route impact request information in the V-UDR network element; the V-PCF network element forwards the notification message to the H-PCF network element; the H-PCF network element sends a notification message to the H-SMF network element, and is used for notifying that the current HR session of the terminal can be influenced by the AF request, and the H-SMF network element performs data routing reconfiguration; the H-PCF network element sends a notification message to the V-SMF network element for notifying the PDU session of the roaming place that needs to be changed, and the V-SMF modifies the PDU session of the roaming place to realize the reconfiguration of the flow route.

Fifth embodiment: V-SMF network element notification H-SMF network element

As shown in fig. 8, the route reconfiguration method provided by the embodiment of the present application may include the following steps 72 to 81.

Steps 72 to 78 refer to steps 61 to 67 in the fourth embodiment.

After the V-SMF network element modifies the roaming user plane according to the AF request, the PDU session needs to be updated to the H-SMF network element.

Step 79, the V-SMF network element requests to change PDU session due to receiving updated PCC rules.

In this signaling, the V-SMF network element indicates to the H-SMF network element the following information:

a data network access identification (Data Network Access Identifier);

affected UPF: the UPF ID, that is, the H-SMF network element should indicate to the V-SMF network element to which UPF the routing information should be applied;

UE ID。

step 80, the H-SMF network element agrees to perform PDU session change.

Step 81, the V-SMF network element uses the routing information for the UPF ID and then alters the target PDU session, which is the session indicated by the PDU session ID.

It can be understood that in the fifth embodiment, the V-UDR network element may send a notification message to the V-PCF network element, for notifying the V-UDR network element of the changed AF route impact request information, where the V-PCF network element subscribes to the change of the AF route impact request information in the V-UDR network element; the V-PCF network element sends a notification message to the V-SMF network element, and the notification message is used for notifying that the current HR session of the terminal can be influenced by the AF request, and the V-SMF performs data route reconfiguration; the V-SMF network element sends a notification message to the H-SMF network element for notifying the PDU session of the roaming place that the PDU session needs to be changed, and the V-SMF network element modifies the PDU session of the roaming place.

It should be noted that, in the route reconfiguration method provided by the embodiment of the present application, the execution body may also be a route reconfiguration device, or a control module used for executing the route reconfiguration method in the route reconfiguration device.

The embodiment of the application also provides another route reconfiguration method, which comprises the following steps:

the fifth network element receives second information sent by the first network element, wherein the second information is used for the fifth network element to reconfigure the flow route; wherein the second information is determined from the first information; the first information is used to influence SMF routing decisions (influence SMF routeing decisions for User Plane traffic of PDU Sessions) of user plane traffic in PDU sessions, or to influence UPF selection or reselection (infunence UPF (re) selection), or to allow the user plane to route traffic to the data network (allow routeing of user traffic to alocal access (identified by a DNAI) to a Data Network) through a local portal.

The second information is information that the home operator HPLMN (e.g., VPLMN SMF) sends to the roaming operator VPLMN (e.g., VPLMN SMF), or the second information is some information that the home operator HPLMN (e.g., HPLMN SMF) needs to exchange with the roaming operator VPLMN (e.g., VPLMN SMF). The second information includes at least one of:

QoS requirements associated with PDU Session (QoS requirements associated with a PDU Session);

(N9) user plane forwarding information ((N9) User Plane forwarding information);

QoS rules (QoS Rule (s));

QoS traffic class QoS parameters (QoS Flow level QoS parameters);

QoS flow identifier (QFI (s));

QoS profile(s);

session aggregation bit rate (Session-AMBR (Aggregate Bit Rates));

home core network Tunnel information (H-CN Tunnel Info).

In one embodiment, the fifth network element is a communication device of the visiting place, which may be a device (for example, V-SMF) having a session management function of the visiting place, or may be a device (for example, V-UDR) having a unified data repository function of the visiting place, or may be other core network devices of the visiting place.

In one embodiment, the first network element is a communication device in the home location, which may be a device with a session management function in the home location (e.g., H-SMF), or may be a device with a policy control function in the home location (e.g., H-PCF), or may be another core network device in the home location.

In one embodiment, the method further comprises: and the fifth network element performs traffic route reconfiguration.

In one embodiment, the traffic routing reconfiguration performed by the fifth network element includes at least one of:

the fifth network element reconfigures the user plane of the PDU session;

the fifth network element reconfigures the route information of UPF;

the fifth network element updates the target DNAI of the UPF;

the fifth network element determines a target DNAI and adds, replaces or deletes UPF in the data path;

the fifth network element configures a user plane UPF, requesting the user plane to buffer uplink traffic to be sent to a target DNAI (buffering of uplink traffic to the target DNAI);

the fifth network element triggers an N4 session modification procedure (N4 Session Modification procedure) to the roaming place UPF;

the fifth network element may apply VPLMN policies related to SLAs negotiated by the HPLMN;

the fifth network element may apply the VPLMN supported QoS values to evaluate QoS parameters received from the H-SMF.

In one embodiment, the fifth network element performs the user plane reconfiguration by triggering an N4 session modification procedure (N4 Session Modification procedure) or triggering an N4 session establishment procedure (N4 Session Establishment procedure) to the UPF.

In one embodiment, the fifth network element requests the user plane to buffer uplink traffic to be sent to the target DNAI or to reconfigure routing information by triggering an N4 session modification procedure (N4 Session Modification procedure) or triggering an N4 session establishment procedure (N4 Session Establishment procedure) to the UPF.

In one embodiment, the fifth network element requests route reconfiguration by triggering an N4 session modification procedure (N4 Session Modification procedure) or triggering an N4 session establishment procedure (N4 Session Establishment procedure), carrying the first information or the second information, to the UPF.

In one embodiment, the fifth network element receives the second information through nsmf_pdustion_create response, or nsmf_pdustion_update response.

In one embodiment, the first information includes traffic impact information (traffic influence information).

In one embodiment, the first information includes at least one of:

target DNAI (target DNAI);

and the first indication information is used for indicating the uplink traffic to be sent to the target DNAI by the cache.

It will be appreciated that the first indication information is used to indicate that the user plane of the roaming place buffers the uplink traffic to be sent to the target DNAI.

In one embodiment, the second information includes updated policy information (updated policy information).

In one embodiment, the second information includes updated PCC rules (updated PCC rules).

In one embodiment, the second information includes at least one of the following:

a target DNAI;

In one embodiment, the method further comprises: the fifth network element sends the first information to the first network element. Optionally, the fifth network element sends the first information to the first network element through nsmf_pduse_create request or nsmf_pduse_update request.

In one embodiment, after receiving the first information sent by the fifth network element, the first network element triggers policy creation or policy update, or the first network element sends a policy creation request or a policy update request to the first target network element.

Alternatively, the policy Update request may be an npcf_smplicycontrol_update request. The policy update request includes first information. Alternatively, the policy creation request may be an npcf_smplicycorol_create request. The policy creation request includes first information.

In one embodiment, after the first network element receives the first information sent by the fifth network element, at least one of the following may be further executed:

establishing or modifying a session policy association (SM policy association);

establishing or modifying a session policy association (SM policy association) to the first target network element;

requesting to acquire PCC rules or requesting to acquire second information;

requesting to obtain the PCC rule from the first target network element, or requesting to obtain the second information from the first target network element.

In one embodiment, the second information is determined by the first target network element based on the first information. The first target network element may be a network device of a home location, a device (e.g., H-PCF) of the home location with a policy control function, or another core network device of the home location. It can be understood that after the first target network element receives the first information sent by the fifth network element, the second information is determined according to the first information, and the second information is sent to the first network element.

In one embodiment, the first target network element may send the second information to the first network element via a policy update response. The policy Update response may be npcf_smplicycorol_update response.

In one embodiment, the first target network element may send the second information to the first network element via a policy creation response. The policy update creation may be npcf_smplicycorol_create response.

In one embodiment, the first target network element may send updated policy information (updated policy information) or policy information (policy information) to the first network element.

In one embodiment, the method further comprises: the fifth network element receives the first information sent by the third network element.

Optionally, the fifth network element receives a third notification sent by a third network element, where the third notification includes the first information.

Optionally, the third notification may be nnef_trafficinfluence_notify, or may be another communication message.

In an implementation manner, the third network element is a communication device of the visited place, which may be a device (for example, V-NEF) having a network opening function of the visited place, a device (for example, V-UDR) having a unified storage function of the visited place, or other core network devices of the visited place.

In one embodiment, the method further comprises: the fifth network element sends a first subscription request to the third network element, wherein the first subscription request is used for subscribing at least one of the following:

Subscribing to the first information (e.g., updating of the first information, deleting of the first information, or adding of the first information);

subscribing to a traffic-influencing request (request for traffic influence); it will be appreciated that the third network element may notify the fifth network element after the third network element receives the traffic influencing request.

Optionally, the first subscription request may be an nnef_trafficinfluence_subscriber request, where the first subscription request includes a first identifier, and the first identifier includes at least one of the following:

one or more PLMN IDs;

one or more UE identifiers;

one or more AF IDs;

one or more DNNs;

one or more S-NSSAI;

one or more IP addresses or port numbers.

In one embodiment, when the first identifier is included in the first subscription request, it is indicated that the fifth network element requests to subscribe to the first information associated with the first identifier.

As an example, when the first subscription request carries one or more PLMN IDs, it is indicated that the fifth network element requests subscription to the first information associated with the PLMN ID.

As another example, when the first subscription request carries one or more AF IDs, it indicates that the fifth network element requests to subscribe to the first information provided by the AF corresponding to the AF ID.

In one embodiment, the third network element sends the first information or the third notification to the fifth network element if the first condition is met, where the first condition includes at least one of:

the third network element receives a first subscription request sent by a fifth network element;

the third network element determines that the first information is updated, deleted or added;

the third network element receives a traffic influencing request (request for traffic influence or AF request).

For convenience of understanding, the following specific description will be given by taking the fifth network element as V-SMF, the third network element as V-NEF, the first network element as H-SMF, and the first target network element as H-PCF as an example.

A route reconfiguration method as shown in fig. 21.

Step 0: the V-SMF sends a first subscription request to the V-NEF. The first subscription request is for subscribing to at least one of:

the first information (e.g., update of the first information, deletion of the first information, or addition of the first information) is subscribed to.

The traffic influencing request (request for traffic influence) is subscribed to, i.e. after the third network element receives the traffic influencing request, the third network element may inform the fifth network element.

The first subscription request may be an nnef_trafficinfluence_subscribe request, where the first subscription request may carry at least one of the following:

One or more PLMN IDs;

one or more UE identifiers;

one or more AF IDs;

one or more DNNs;

one or more S-NSSAI;

one or more IP addresses or port numbers.

For example, when the first subscription request carries one or more PLMN IDs, it is indicated that the fifth network element only requests to subscribe to the first information associated with the PLMN ID.

When the first subscription request carries one or more AF IDs, the fifth network element only requests to subscribe the first information provided by the AF corresponding to the AF ID.

Step 1-step 3: existing processes. The AF triggers an AF request for requesting traffic effects. The information of the traffic impact is stored in the roaming place UDR by the third network element (step 3).

Step 4: the V-NEF sends a third notification to the V-SMF. The third notification includes the first information.

Step 5: the V-SMF sends the first information to the H-SMF.

For example, the fifth network element sends the first information to the first network element through nsmf_pdustion_create request or nsmf_pdustion_update request.

The fifth network element also transmits at least one of the following to the first network element:

target DNAI (target DNAI);

In one embodiment, the first information includes the target DNAI or the first indication information.

Step 6: after the H-SMF receives the first information, the strategy for updating the PDU session is decided.

Step 7: the H-SMF sends the first information to the H-PCF. The first information is used to generate second information. The H-SMF sends the first information to the H-PCF by triggering a session policy association establishment (SM policy association establishment) or modification (SM policy association modification) procedure.

The session policy association modification signaling may be: npcf_smpolicycontrol_update request;

the session policy association establishment signaling may be: npcf_smpolicicontrol_create request;

the second information includes: PCC rules or policy information (policy information).

The second information may further include:

QoS rules (QoS Rule (s));

QoS traffic class QoS parameters (QoS Flow level QoS parameters);

QoS flow identifier (QFI (s));

QoS profile(s);

session aggregation bit rate (Session-AMBR (Aggregate Bit Rates));

Home core network Tunnel information (H-CN Tunnel Info).

Step 8: the H-PCF sends a response to the H-SMF. The response includes second information. The PCC rule is generated according to the first information.

The response includes at least one of:

the session policy association modification response signaling may be: npcf_smpolicycontrol_update response;

the session policy association establishment signaling may be: npcf_smpolicicontrol_create response;

step 9: the H-SMF sends the second information to the V-SMF.

The first network element sends the second information to the V-SMF through the Nsmf_PDUSion_Create response or the Nsmf_PDUSion_update response.

The H-SMF also sends at least one of the following information to the V-SMF:

target DNAI (target DNAI);

Step 10: the V-SMF performs at least one of the following according to the second information:

reconfiguring a user plane of the PDU session;

reconfiguring route information of UPF;

updating target DNAI of UPF;

determining a target DNAI, and adding, replacing or deleting UPF in the data path;

And configuring a user plane UPF, and requesting the user plane to buffer the uplink flow to be sent to the target DNAI.

The user plane is a roaming user plane.

The embodiment of the application also provides another route reconfiguration method, which comprises the following steps: the third network element sends the first information to the seventh network element.

In one embodiment, the seventh network element is a communication device of the home location, which may be a device of the home location having a network opening function (for example, H-NEF), which may be a device of the home location having a unified repository function (for example, H-UDR), or which may be another core network device of the visited location.

It can be understood that, when the third network element is V-NEF and the seventh network element is H-NEF, the third network element may directly send the first information to the seventh network element through the service interface, so as to facilitate policy update by the home network.

In the embodiment of the present application, the first network element may send second information or updated policy information to the fifth network element, so that the fifth network element performs route reconfiguration, where the second information is determined according to the first information. Optionally, the first network element sends the second information or the updated policy information to the fifth network element through nsmf_pdustion_create response or nsmf_pdustion_update response.

In one embodiment, the first information includes at least one of:

target DNAI (target DNAI);

It will be appreciated that the first indication information is used to indicate that the roaming ue caches uplink traffic to be sent to the target DNAI.

a target DNAI;

In one embodiment, after the seventh network element receives the first information sent by the third network element, the seventh network element stores the first information in the eighth network element.

In one embodiment, the eighth network element is a home network device, which may be a device (e.g., H-UDR) with unified warehousing functionality in the home.

In one embodiment, the eighth network element sends the first information to the first target network element if the second condition is met, wherein the second condition comprises at least one of:

the first target network element subscribes to the first information (e.g., update of the first information, deletion of the first information, or addition of the first information);

the first target network element subscribes to a traffic influencing request (request for traffic influence or AF request);

the eighth network element determines that the first information is updated, deleted or added.

In one embodiment, the eighth network element sends the first information to the first target network element through a fourth notification. The fourth notification may be nudr_dm_notify.

In one embodiment, the first target network element may be a network device of a home location, a device (e.g., an H-PCF) with policy control function of the home location, or another core network device of the home location.

In one embodiment, after receiving the first information, the first target network element determines second information according to the first information, and sends the second information to the first network element.

For easy understanding, the following description will be given by taking the third network element as V-NEF, the seventh network element as H-NEF, and the eighth network element as H-UDR as an example:

a route reconfiguration method as shown in fig. 22.

Step 1-2: in the prior art, the roaming AF sends a first message to the V-NEF.

Step 3: optionally, the V-NEF saves the first information to the V-UDR.

Step 4: the V-NEF sends the first information to the H-NEF.

Step 4 is providing the first information roaming, said first information being sent to the home PLMN via the H-NEF. The first information is used to generate second information. The H-PCF receives the first information from the H-UDR and generates the second information, via step 6.

Step 5: the H-UDR stores the first information.

Step 6: the H-UDR sends the first information to the H-PCF. The H-PCF generates second information according to the first information.

Step 7: the H-PCF sends the second information to the H-SMF.

Step 8: the H-SMF transmits the second information to the V-SMF.

The embodiment of the application also provides a route reconfiguration method, which comprises the following steps:

the fifth network element sends third information to the ninth network element, wherein the third information is used to indicate or request that a home operator (HPLMN) authentication (authentication) or authorization (authorization) visitor operator (VPLMN) can perform a first operation, the first operation comprising at least one of:

directly using the first information;

performing or completing an AF flow affecting procedure (AF traffic influence procedure);

the request information is affected using AF traffic (AF traffic influence request information).

Or,

the fifth network element obtains fourth information, where the fourth information is used to indicate that the visited place operator can perform a first operation, and the first operation includes at least one of the following:

directly using the first information;

It should be noted that, the fourth information may be sent by the network device of the home location to the fifth network element, or may be agreed by a protocol.

In one embodiment, the "visited place operator may perform the first operation" may be understood as "the visited place operator has authority to perform the first operation".

In one embodiment, the first information includes at least one of:

target DNAI (target DNAI);

In one embodiment, the ninth network element is a communication device in the home location, which may be a device having a session management function in the home location (for example, H-SMF), or may be a device having a unified data management function in the home location (for example, UDM), or may be another core network device in the home location.

In one embodiment, "directly using the first information" may be understood as directly using without sending the first information to the home operator or without generating corresponding PCC rules by the home operator or without authorization by the home operator.

In one embodiment, "directly using the first information" includes at least one of:

directly using the first information to reconfigure the user plane of the PDU session;

directly reconfiguring the route information of the UPF by using the first information;

directly updating target DNAI of the UPF by using the first information;

directly using the first information to determine a target DNAI, and adding, replacing or deleting UPF in the data path;

and directly using the first information to configure a user plane UPF, and requesting the user plane to buffer the uplink flow to be sent to the target DNAI, wherein the user plane is a visiting place user plane.

In one embodiment, the AF flow affecting procedure includes: the V-AF (or AF) provides the first information to a third network element (e.g., V-NEF); the third network element sends the first information to a fifth network element (e.g., V-SMF), the fifth network element directly using the first information to perform at least one of:

reconfiguring a user plane of the PDU session;

reconfiguring route information of UPF;

Updating target DNAI of UPF;

and configuring a user plane UPF, and requesting the user plane to cache the uplink flow to be sent to the target DNAI, wherein the user plane is a visiting place user plane.

In one embodiment, the third information may be a message requesting that a home operator (HPLMN) authentication (authorization) or authorization (authorization) visited operator (VPLMN) may perform the first operation. For example, the third information may be a home routed session offload authorization request (HR-SBO authorization request), an AF traffic influencing request authorization request (AF traffic influence request in VPLMN authorization request) in the VPLMN, a home routed session offload authorization indication (HR-SBO authorization indication), or an AF traffic influencing authorization indication (AF traffic influence in VPLMN authorization indication) in the VPLMN, a home routed session offload allow indication (HR-SBO allowed indication), an AF traffic influencing allow indication (AF traffic influence in VPLMN allowed indication) in the VPLMN, etc., or may be other names as well.

In one embodiment, the third information may be indication information indicating that a home operator (HPLMN) authentication (authorization) or authorization (authorization) visited operator (VPLMN) may perform the first operation. Alternatively, the third information may be indication information carried in an nsmf_pduse_create request message or an nsmf_pduse_update request message.

In one embodiment, after the ninth network element receives the third information, the ninth network element recovers the subscription information from the UDR or the UDM. And then, the ninth network element verifies, authorizes or approves the third information according to the subscription information. After verifying, authorizing or approving said third information, it is also meant that the home operator (HPLMN) verifies that the visited operator (VPLMN) can perform the first operation.

In one embodiment, the method further comprises: and the fifth network element receives the verification result or the authorization result sent by the ninth network element. The verification result or the authorization result includes at least one of:

verifying that the first information is directly used by the roaming place operator by, authorizing or approving;

verifying that the AF traffic influencing procedure is performed or completed by, authorised or authorised to the roaming place operator (AF traffic influence procedure);

verify pass, authorize or approve roaming operator use AF traffic influence request information;

verifying that the first information is not directly used by the operator at roaming locations, unauthorized or not approved;

verifying that the AF traffic influencing procedure is not performed or completed by the roaming operator (AF traffic influence procedure), unauthorized or not approved;

Verify that roaming operator usage is not passed, authorized or approved AF traffic influence request information;

in one embodiment, in the case that the authentication result or the authorization result is "authentication pass, authorization or approval", the fifth network element performs or completes the AF traffic influencing procedure (AF traffic influence procedure) or the fifth network element directly uses the first information or the fifth network element uses the AF traffic influencing request information (AF traffic influence request information).

The fourth information includes at least one of:

home routing session offload allowed indication (HR-SBO allowed indication), AF traffic in VPMN affects the allowed indication (AF traffic influence in VPLMN allowed indication).

The fifth network element may obtain fourth information from at least one of:

one or more of a network element with mobility management function (e.g., AMF), a network element with unified data management function (e.g., UDM), a network element with unified data repository function (e.g., UDR), a ninth network element, or other core network elements (the core network elements include visited core network elements or home core network elements).

The fifth network element obtaining fourth information includes at least one of:

The fifth network element obtains the fourth information from the ninth network element or the HPLMN through Nsmf_PDUSion_Create/Update response;

the fifth network element obtains the fourth information from the network element (for example, AMF) with the access management function through nsmf_pduse_ CreateSMContext Request, where the fourth information is obtained from the network element (for example, UDM) with the unified data management function by the network element with the access management function.

In an embodiment, after the fifth network element obtains the fourth information, if the fifth network element receives the first information, the fifth network element may not send the first information to a ninth network element (such as H-SMF), or the fifth network element directly performs at least one of the first operations.

In one embodiment, when the fifth network element sends the third information to the ninth network element, the fifth network element may not send the first information to the ninth network element. That is, the fifth network element only transmits the third information, and does not need to transmit the first information, so that the message capacity carried in the signaling can be saved.

In another embodiment, when the fifth network element sends the third information to the ninth network element, the first information may also be sent to the ninth network element, so that the ninth network element may acquire the second information by using the first information and send the second information to the fifth network element when the verification result or the authorization result of the ninth network element is "verification failed, unauthorized, and not approved". The method for the ninth network element to acquire the second information by using the first information and send the second information to the fifth network element may refer to the operation of the first network element in the embodiment corresponding to fig. 21, which is not described in detail herein.

One or more PLMN IDs;

one or more UE identifiers;

one or more AF IDs;

one or more DNNs;

one or more S-NSSAI;

one or more IP addresses or port numbers.

In an embodiment, the fifth network element may acquire the fourth information before the fifth network element receives the first information sent by the third network element, or after the fifth network element receives the first information sent by the third network element.

For convenience of understanding, the following will specifically describe an example in which the fifth network element is V-SMF, the third network element is V-NEF, and the ninth network element is H-SMF. This example is not illustrated and reference may be made to the above embodiments.

A route reconfiguration method as shown in fig. 25.

one or more PLMN IDs;

one or more UE identifiers;

one or more AF IDs;

one or more DNNs;

One or more S-NSSAI;

one or more IP addresses or port numbers.

Step 5: the V-SMF transmits third information to the H-SMF.

For example, the V-SMF sends the third information to the H-SMF via the Nsmf_PDUSion_Create request, or the Nsmf_PDUSion_Update request.

The third information is used to indicate or request that a home operator (HPLMN) authentication or authorization (authorization) visited operator (VPLMN) can perform a first operation comprising at least one of:

directly using the first information;

In one embodiment, the V-SMF may not send the first information to the H-SMF, but only send third information indicating that the roaming operator (H-PLMN) may use the first information (i.e., at least one of allowing the roaming operator to directly use AF traffic influence information, allowing the first information to be directly used, or allowing the AF traffic influencing procedure to be performed or completed) to request or indicate authentication or authorization (authorization) of the home operator.

In one embodiment, the V-SMF does not carry the first information or send the first information to the H-SMF when carrying the third information.

Step 6: after the H-SMF receives the third information, a verification or authorization process is performed. Wherein the verification or authorization process includes: the H-SMF recovers the subscription information from the UDM or UDR and verifies, authorizes or approves the third information according to the subscription information.

The H-SMF recovers the subscription information by at least one of:

Nudm_SDM_Get

Nudm_SDM_Subscribe

nudm_uecm_get, etc.

The subscription information may be SM subscription data (SM subscription data), and the content thereof may be as follows:

step 7: the H-SMF sends the verification result or the authorization result to the V-SMF.

Step 8, in the case that the verification result or the authorization result is "verification pass, authorization or approval", the V-SMF performs a first operation, where the first operation includes at least one of the following:

directly using the first information;

An embodiment of the present application provides a method for acquiring ECS address configuration information, and fig. 9 shows a flowchart of a method for acquiring ECS address configuration information provided by the embodiment of the present application. As shown in fig. 9, the method for obtaining ECS address configuration information according to the embodiment of the present application may include the following steps 401 to 404.

Step 401, the first network element sends ECS address configuration information to the fifth network element.

Optionally, in the embodiment of the present application, the first network element may send the ECS address configuration information (ECS Address Configuration Information) to the fifth network element through signaling such as nsmf_pduse_create Response or nsmf_pduse_update Response.

Step 402, the fifth network element receives ECS address configuration information sent by the first network element.

In the embodiment of the present application, the ECS address configuration information includes PLMN identifiers. PLMN identities are used to give which operator the ECS address is applicable to.

Optionally, in an embodiment of the present application, the structure of the ECS address configuration information is as follows table 3:

TABLE 3

Alternatively, in the embodiment of the present application, the PLMN ID may be located outside the ECS address configuration information, as shown in the following table 4:

table 4

Since the AF network element may send the ECS address to the home operator instead of the roaming operator, the AF network element must indicate which operator this ECS address or ECS address configuration information provides at this time.

In addition, the AF network element sends ECS address configuration information to the NEF network element first, and then the NEF network element sends the ECS address configuration information to the UDM network element, as follows:

the AF network element sends the ECS address configuration information, PLMN ID and the like to the NEF network element through the Nnef_ParameterProvision_update or the Nnef_ParameterProvision_Create; the PLMN ID is used to indicate the operator to which the ECS address configuration information belongs; the PLMN ID may also be carried in the ECS address configuration information;

Then the NEF network element sends the ECS address configuration information, PLMN ID and the like to the UDM network element through Nudm_ParameterProvisions_update or Nudm_ParameterProvisions_Create; the PLMN ID is used to indicate the operator to which the ECS address configuration information belongs; the PLMN ID may also be carried in the ECS address configuration information.

Then the UDM network element stores the information in the UDR network element through the following signaling: nudr_dm_update or nudr_dm_query. In these two signaling, the input content includes: data Subset is ECS address configuration information (AF provided), data Key is UE SUPI, and Data Sub Key is PLMN ID.

Step 403, the fifth network element sends ECS address configuration information to the terminal.

In the embodiment of the present application, the ECS address configuration information is used for establishing a protocol data unit PDU session of the roaming place between the terminal and the ECS.

And step 404, the terminal receives the ECS address configuration information sent by the fifth network element.

Optionally, in an embodiment of the present application, the ECS address configuration information is stored by a unified data storage network element or a unified data management network element.

Optionally, in the embodiment of the present application, the ECS address configuration information may be stored in a UDM network element or a UDR network element in a PLMN identifier form; ECS: edge configuration server edge configuration server.

For example, in UDR, ECS address configuration information is stored as shown in table 5 below.

Table 5

Here, the ECS address may be stored in the form of PLMN ID in the subscription data of the UDR.

Either the Data key or the Data sub key may have a PLMN ID.

In the UDM, ECS address configuration information is stored as shown in table 6 below.

Table 6

Since the storage ECS configuration information in the UDM is also stored in the session management subscription data, it is also conceivable to add a PLMN ID to distinguish between different ECS addresses.

The embodiment of the application provides a method for acquiring ECS address configuration information, wherein a first network element can send ECS address configuration information under an HR session to a fifth network element, so that the fifth network element can send the ECS address configuration information to a terminal, and the ECS address configuration information is used for establishing a PDU session of a roaming place between the terminal and an ECS.

It should be noted that, in the method for acquiring ECS address configuration information provided in the embodiment of the present application, the executing body may also be an ECS address configuration information acquiring device, or a control module in the ECS address configuration information acquiring device for executing the method for acquiring ECS address configuration information.

An embodiment of the present application provides a DNS processing method, and fig. 10 shows a flowchart of the DNS processing method provided by the embodiment of the present application. As shown in fig. 10, the DNS processing method provided by the embodiment of the present application may include the following step 501.

Step 501, in the case that the terminal enters a roaming state, the terminal performs at least one of the following:

clearing the DNS cache;

a DNS re-query request is sent requesting that EAS be reselected while roaming.

In the embodiment of the application, the connected edge server may become a suboptimal server after the terminal enters the roaming place from the home location. Thus, the terminal may empty the DNS cache and/or reinitiate DNS queries to enable the re-search for EAS.

Roaming means that the terminal is not in the H-PLMN but in the V-PLMN.

Optionally, in the embodiment of the present application, after the terminal enters the roaming state, the application on the terminal may trigger the terminal to perform DNS query, where the application on the terminal may perceive that the EAS of the home location is not the optimal EAS, so that a DNS re-query request may be initiated to request to reselect the EAS in the roaming location.

Optionally, in the embodiment of the present application, the terminal may specifically empty the DNS cache through the following step 501 a.

In step 501a, when the terminal receives the indication information, the terminal clears the DNS cache.

In the embodiment of the present application, the indication information is used to instruct the terminal to empty the DNS cache.

Optionally, in the embodiment of the present application, the indication information may be indication information in a 5G NAS message.

Optionally, in the embodiment of the present application, the terminal enters the roaming state to enable the terminal to meet a target condition, where the target condition includes at least one of the following:

the terminal finishes registering in the V-PLMN;

the terminal is configured with new DNS address information (i.e., new DNS server IP address) at roaming; for example, the new DNS server IP address may be an H-EASDF IP address, or a local DNS server IP address of the roaming site;

the terminal completes the establishment of a Local Break (LBO) session or HR session at roaming place.

The embodiment of the application provides a DNS processing method, which can empty a DNS cache after a terminal enters a roaming place so as to facilitate the terminal to find an EAS as soon as possible; and/or the terminal may initiate a DNS re-query request to reselect the optimal EAS at roaming; thereby enabling establishment of a PDU session at the roaming place.

It should be noted that, in the DNS processing method provided by the embodiment of the present application, the execution body may also be a DNS processing device, or a control module in the DNS processing device for executing the DNS processing method.

It should be noted that, the relevant descriptions in the various embodiments of the present application may be general, and in order to avoid redundancy, the descriptions in some embodiments are not repeated, and the contents in the various embodiments may be combined.

Fig. 11 is a schematic diagram of a possible structure of an EDI obtaining apparatus according to an embodiment of the application, where the EDI obtaining apparatus is applied to a first network element. As shown in fig. 11, the EDI obtaining apparatus 90 may include: a transmitting module 91 and a receiving module 92.

The sending module 91 is configured to send a query request to the second network element, where the query request is used to request to query the third network element. And a receiving module 92, configured to receive a query response sent by the second network element, where the query response includes address information of the third network element. The sending module 91 is further configured to send, to the third network element, a target request according to address information of the third network element, where the target request is used to request obtaining EDI of the roaming operator from the fourth network element. The receiving module 92 is further configured to receive EDI sent by the third network element.

The embodiment of the application provides an EDI acquisition device, which can inquire a third network element by sending an inquiry request to a second network element, and after the third network element is found, request the third network element to acquire EDI of a roaming place operator from a fourth network element so as to acquire the EDI, thereby generating a DNS message processing rule according to the EDI and realizing establishment of PDU session of the roaming place.

In one possible implementation manner, the query request includes at least one of the following: PLMN identification, SUPI; wherein the PLMN identification comprises at least one of: V-PLMN identity, H-PLMN identity.

In one possible implementation manner, the address information of the third network element includes at least one of the following: IP address, FQDN of the third network element.

In one possible implementation manner, the target request includes at least one of the following: PLMN identity, S-NSSAI, DNN.

In a possible implementation manner, the sending module 91 is specifically configured to send the query request to the second network element via the H-NRF network element.

In a possible implementation manner, the sending module 91 is further configured to send a first request to the UDM network element, where the first request is used to request to obtain subscription information of a terminal, where the terminal is a terminal that is in a roaming location and needs to establish a PDU session or update the PDU session, and the subscription information is used to indicate whether the terminal is authorized to use a roaming location edge computing service, and the first request includes a PLMN identifier. The receiving module 92 is further configured to receive a first response sent by the UDM network element, where the first response includes subscription information of the terminal. The sending module 91 is specifically configured to send a query request to the second network element when the subscription information indicates that the terminal is authorized to use the roaming place edge computing service.

The EDI obtaining device provided by the embodiment of the application can realize each process realized by the first network element in the embodiment of the method and achieve the same technical effect, and in order to avoid repetition, the description is omitted.

Fig. 12 is a schematic diagram of a possible structure of an EDI obtaining apparatus according to an embodiment of the application, where the EDI obtaining apparatus is applied to a second network element. As shown in fig. 12, the EDI obtaining apparatus 100 may include: a receiving module 101 and a transmitting module 102.

The receiving module 101 is configured to receive a query request sent by the first network element, where the query request is used to request to query the third network element. And the sending module 102 is configured to send a query response to the first network element, where the query response includes address information of the third network element. The address information is used for sending a target request to the third network element by the first network element, wherein the target request is used for requesting to obtain the EDI of the roaming place operator from the fourth network element.

The embodiment of the application provides an EDI acquisition device, which can receive a query request sent by a first network element to query a third network element, and after the third network element is found, send address information of the third network element to the first network element, so that the first network element can request the third network element to acquire EDI of a roaming place operator from a fourth network element to acquire the EDI, and generate a DNS message processing rule according to the EDI, thereby realizing establishment of PDU session of the roaming place.

In a possible implementation manner, the receiving module 101 is specifically configured to receive a query request sent by a first network element via an H-NRF network element.

The EDI obtaining device provided by the embodiment of the application can realize each process realized by the second network element in the embodiment of the method and achieve the same technical effect, and in order to avoid repetition, the description is omitted.

Fig. 13 is a schematic diagram of a possible structure of an EDI obtaining apparatus according to an embodiment of the application, where the EDI obtaining apparatus is applied to a third network element. As shown in fig. 13, the EDI obtaining apparatus 110 may include: a receiving module 111 and a transmitting module 112.

The receiving module 111 is configured to receive a target request sent by the first network element, where the target request is used to request obtaining EDI of the roaming operator from the fourth network element. A sending module 112, configured to send EDI to the first network element.

The embodiment of the application provides an EDI acquisition device, after a first network element sends a query request to a second network element to find a third network element, the first network element requests the third network element to acquire the EDI of a roaming operator from a fourth network element, and the third network element can send the EDI of the roaming operator to the first network element so that the first network element can acquire the EDI, and a DNS message processing rule is generated according to the EDI, thereby realizing establishment of PDU session of the roaming.

In a possible implementation manner, the EDI obtaining device provided by the embodiment of the application further includes: and a verification module. The verification module is configured to verify the first network element according to the target request before the sending module 112 sends the EDI to the first network element, so as to determine whether the first network element is authorized to obtain data from the roaming operator to which the EDI belongs. The sending module 112 is specifically configured to obtain the EDI from the fourth network element and send the EDI to the first network element when it is verified that the first network element is authorized to obtain the data from the roaming operator to which the EDI belongs.

The EDI obtaining device provided by the embodiment of the application can realize each process realized by the third network element in the embodiment of the method and achieve the same technical effect, and in order to avoid repetition, the description is omitted.

Fig. 14 is a schematic diagram of a possible configuration of a route reconfiguration device according to an embodiment of the present application, where the route reconfiguration device is applied to a first target network element. As shown in fig. 14, the route reconfiguration device 120 may include: a receiving module 121 and a transmitting module 122.

The receiving module 121 is configured to receive a first target notification message sent by the fourth network element, where the first target notification message is used to notify the fourth network element of the changed AF route impact request information. The sending module 122 is configured to send a second target notification message to the second target network element, where the second target notification message includes updated policy information, and the policy information is used for the second target network element to reconfigure the traffic route.

The embodiment of the application provides a route reconfiguration device, which can receive a first target notification message sent by a fourth network element and is used for notifying the changed AF route influence request information in the fourth network element, and then the route reconfiguration device can send updated strategy information to a second target network element according to the AF route influence request information so as to be used for traffic route reconfiguration of the second target network element, thereby realizing the application of AF route influence to an HR session.

In one possible implementation manner, the AF route impact request information includes at least one of the following: traffic description information, identification of the terminal to which traffic will be affected, traffic routing information of the target interface, data network access identification, PLMN identification.

In one possible implementation manner, the sending module 122 is specifically configured to send a first notification message to the first network element, where the first notification message is used to notify that the current HR session is affected by the AF request; the first notification message is used for the first network element to perform traffic route reconfiguration and sends a second notification message to the fifth network element, the second notification message is used for notifying the PDU session of the roaming place that needs to be changed, and the second notification message is used for the fifth network element to perform traffic route reconfiguration.

In a possible implementation manner, the sending module 122 is specifically configured to send a first notification message to the first network element, where the first notification message is used to notify that the current HR session is affected by the AF request, and the first notification message is used for the first network element to perform traffic route reconfiguration; and sending a second notification message to the fifth network element, wherein the second notification message is used for notifying the PDU session of the roaming place needs to be changed, and the second notification message is used for the fifth network element to reconfigure the traffic route.

In a possible implementation manner, the receiving module 121 is specifically configured to receive a first target notification message sent by the fourth network element via the sixth network element. The sending module 122 is specifically configured to send a first notification message to a first network element, where the first notification message is used to notify that the current HR session is affected by the AF request, and the first notification message is used to reconfigure the traffic route by the first network element; and sending a second notification message to the fifth network element, wherein the second notification message is used for notifying the PDU session of the roaming place needs to be changed, and the second notification message is used for the fifth network element to reconfigure the traffic route.

In a possible implementation manner, the sending module 122 is specifically configured to send a first notification message to the fifth network element, where the first notification message is used to notify that the current HR session is affected by the AF request; the first notification message is used for the fifth network element to perform traffic route reconfiguration, and sends a second notification message to the first network element, wherein the second notification message is used for notifying that the PDU session of the roaming place needs to be changed, and the second notification message is used for the fifth network element to perform traffic route reconfiguration under the condition that the first network element agrees to execute the PDU session change.

In one possible implementation manner, the second notification message includes at least one of the following: data network access identification, traffic routing information of a target interface, affected user plane function identification, affected PDU session identification, affected terminal identification, PLMN identification.

In one possible implementation manner, the manner in which the fifth network element performs traffic routing reconfiguration includes at least one of the following:

reselecting or replacing the user plane;

establishing a PDU session to a visitor location EAS;

The route reconfiguration device provided by the embodiment of the application can realize each process realized by the first target network element in the embodiment of the method and achieve the same technical effect, and is not repeated here for avoiding repetition.

Fig. 15 shows a schematic diagram of a possible configuration of a route reconfiguration device according to an embodiment of the present application, where the route reconfiguration device is applied to a second target network element. As shown in fig. 15, the route reconfiguration device 130 may include: a receiving module 131.

The receiving module 131 is configured to receive a second target notification message sent by the first target network element, where the second target notification message includes updated policy information, and the policy information is used for reconfiguring a traffic route by the second target network element; the second target notification message is sent by the first target network element after receiving the first target notification message sent by the fourth network element, where the first target notification message is used to notify the fourth network element of the changed AF route influence request information.

The embodiment of the application provides a route reconfiguration device, which can receive updated strategy information sent by a first target network element according to changed AF route influence request information in a fourth network element, and carry out traffic route reconfiguration according to the strategy information, thereby realizing that AF route influence is applied to an HR session so as to realize the establishment of a PDU session in a roaming place.

In a possible implementation manner, the receiving module 131 is specifically configured to receive, by using a first network element, a first notification message sent by a first target network element, where the first notification message is used to notify that a current HR session is affected by an AF request, and the first notification message is used by the first network element to perform traffic route reconfiguration; and receiving, by the fifth network element, a second notification message sent by the first network element, where the second notification message is used to notify that a PDU session in the roaming place needs to be changed, and the second notification message is used by the fifth network element to perform traffic route reconfiguration.

In a possible implementation manner, the receiving module 131 is specifically configured to receive, by using a first network element, a first notification message sent by a first target network element, where the first notification message is used to notify that a current HR session is affected by an AF request, and the first notification message is used by the first network element to perform traffic route reconfiguration; and receiving, by the fifth network element, a second notification message sent by the first target network element, where the second notification message is used to notify that the PDU session in the roaming place needs to be changed, and the second notification message is used by the fifth network element to perform traffic route reconfiguration.

In one possible implementation manner, the first target notification message is sent by the fourth network element to the first target network element via the sixth network element. The receiving module 131 is specifically configured to receive, by using a first network element, a first notification message sent by a first target network element, where the first notification message is used to notify that a current HR session is affected by an AF request, and the first notification message is used to reconfigure a traffic route by using the first network element; and receiving, by the fifth network element, a second notification message sent by the first target network element, where the second notification message is used to notify that the PDU session in the roaming place needs to be changed, and the second notification message is used by the fifth network element to perform traffic route reconfiguration.

In a possible implementation manner, the receiving module 131 is specifically configured to receive, by using a fifth network element, a first notification message sent by a first target network element, where the first notification message is used to notify that a current HR session is affected by an AF request, and the first notification message is used by the fifth network element to perform traffic route reconfiguration; and receiving, by the first network element, a second notification message sent by the fifth network element, where the second notification message is used to notify that the PDU session in the roaming place needs to be changed, and the second notification message is used to reconfigure the flow route by the fifth network element when the first network element agrees to execute the PDU session change.

The route reconfiguration device provided by the embodiment of the application can realize each process realized by the second target network element in the embodiment of the method and achieve the same technical effect, and is not repeated here for avoiding repetition.

Fig. 16 is a schematic diagram showing a possible configuration of an ECS address configuration information acquiring apparatus according to an embodiment of the present application, where the ECS address configuration information acquiring apparatus is applied to a fifth network element. As shown in fig. 16, the ECS address configuration information acquiring device 140 may include: a receiving module 141 and a transmitting module 142.

The receiving module 141 is configured to receive ECS address configuration information sent by the first network element, where the ECS address configuration information includes a PLMN identifier. A transmitting module 142 for transmitting ECS address configuration information to the terminal, the ECS address configuration information being used for the terminal to establish PDU session of roaming place with ECS

The embodiment of the application provides an ECS address configuration information acquisition device, which can receive ECS address configuration information under an HR session sent by a first network element, and then send the ECS address configuration information to a terminal for establishing a PDU session of a roaming place between the terminal and an ECS.

In one possible implementation, the ECS address configuration information is stored by a unified data storage network element or a unified data management network element.

The device for acquiring the ECS address configuration information provided by the embodiment of the present application can implement each process implemented by the fifth network element in the above method embodiment, and achieve the same technical effect, so that repetition is avoided, and no description is repeated here.

Fig. 23 shows a schematic structural diagram of one possible route reconfiguration device, which may be applied to the fifth network element. As shown in fig. 23, the route reconfiguration device 2300 may include:

a receiving module 2301, configured to receive second information sent by the first network element. The second information is used for the fifth network element to reconfigure the traffic route; wherein the second information is determined from the first information; the first information is used to influence SMF routing decisions (influence SMF routeing decisions for User Plane traffic of PDU Sessions) of user plane traffic in PDU sessions, or to influence UPF selection or reselection (infunence UPF (re) selection), or to allow the user plane to route traffic to the data network (allow routeing of user traffic to a local access (identified by a DNAI) to a Data Network) through a local portal.

QoS rules (QoS Rule (s));

QoS traffic class QoS parameters (QoS Flow level QoS parameters);

QoS flow identifier (QFI (s));

QoS profile(s);

session aggregation bit rate (Session-AMBR (Aggregate Bit Rates));

home core network Tunnel information (H-CN Tunnel Info).

The route reconfiguration device 2300 may be a device at a visited place, a device with a session management function at the visited place (for example, V-SMF), or a device with a unified data storage function at the visited place (for example, V-UDR), or other core network devices at the visited place.

The route reconfiguration device 2300 further includes: and the reconfiguration module is used for carrying out traffic route reconfiguration.

The reconfiguration module performs route reconfiguration including at least one of:

the reconfiguration module reconfigures the user plane of the PDU session;

the reconfiguration module reconfigures the route information of the UPF;

the reconfiguration module updates a target DNAI of the UPF;

the reconfiguration module determines a target DNAI and adds, replaces or deletes a UPF in the data path;

The reconfiguration module configures a user plane UPF, and requests the user plane to cache the uplink flow to be sent to the target DNAI;

the reconfiguration module triggers an N4 session modification procedure (N4 Session Modification procedure) to the roaming place UPF;

the reconfiguration module may apply VPLMN policies related to SLAs negotiated by the HPLMN;

the reconfiguration module may apply the VPLMN supported QoS values to evaluate QoS parameters received from the H-SMF.

In one embodiment, the reconfiguration module performs user plane reconfiguration by triggering an N4 session modification procedure (N4 Session Modification procedure) or triggering an N4 session establishment procedure (N4 Session Establishment procedure) to the UPF.

In one embodiment, the reconfiguration module requests route reconfiguration by triggering an N4 session modification procedure (N4 Session Modification procedure) or triggering an N4 session establishment procedure (N4 Session Establishment procedure), carrying either the first information or the second information, to the UPF.

In one embodiment, the receiving module 2301 receives the second information through nsmf_pdustion_create response or nsmf_pdustion_update response.

In one embodiment, the first information includes at least one of:

target DNAI (target DNAI);

It may be appreciated that the first indication information is used to indicate that the roaming ue caches uplink traffic to be sent to the target DNAI.

a target DNAI;

In one embodiment, the route reconfiguration device 2300 further includes a sending module configured to send the first information to the first network element. Optionally, the sending module sends the first information to the first network element through nsmf_pduse_create request or nsmf_pduse_update request.

In one embodiment, the second information is determined by the first target network element based on the first information. The first target network element may be a network device of a home location, a device (e.g., H-PCF) of the home location with a policy control function, or another core network device of the home location. It may be appreciated that after the first target network element receives the first information sent by the route reconfiguration device 2300, second information is determined according to the first information, and the second information is sent to the first network element.

In one embodiment, the receiving module 2301 is further configured to receive the first information sent by the third network element.

Optionally, the receiving module 2301 is configured to receive a third notification sent by a third network element, where the third notification includes the first information.

In one embodiment, the sending module is further configured to send a first subscription request to a third network element, where the first subscription request is used to subscribe to at least one of:

One or more PLMN IDs;

one or more UE identifiers;

one or more AF IDs;

one or more DNNs;

one or more S-NSSAI;

one or more IP addresses or port numbers.

In one embodiment, the receiving module receives the first information or the third notification sent by the third network element if the first condition is met, where the first condition includes at least one of:

Fig. 24 shows a schematic diagram of a possible information transmission device that can be applied to a third network element. As shown in fig. 24, the information transmission apparatus 2400 may include: a sending module 2401, configured to send the first information to the seventh network element.

In one embodiment, the information sending device 2400 is a device at a visiting place, which may be a device with a network opening function (for example, V-NEF) at the visiting place, which may be a device with a unified storage function (for example, V-UDR) at the visiting place, or which may be another core network device at the visiting place.

It can be appreciated that the information sending apparatus 2400 may send the first information directly to the seventh network element through the server interface, so as to facilitate policy update of the home network.

In one embodiment, the first information includes at least one of:

target DNAI (target DNAI);

A target DNAI;

and the first indication information is used for indicating the uplink traffic to be sent to the target DNAI by the cache. .

Fig. 17 shows a schematic diagram of a possible configuration of a DNS processing device involved in an embodiment of the present application, where the DNS processing device is applied to a terminal. As shown in fig. 17, the DNS processing means 150 may include: and an execution module 151.

Wherein, the executing module 151 is configured to execute at least one of the following when the terminal enters a roaming state: clearing the DNS cache; a DNS re-query request is sent requesting a reselection of EAS in roaming. .

The embodiment of the application provides a DNS processing device, which can empty a DNS cache after a terminal enters a roaming place so as to facilitate the terminal to find an EAS as soon as possible; and/or the DNS processing means may initiate a DNS re-query request to reselect the optimal EAS at the roaming location; thereby enabling establishment of a PDU session at the roaming place.

In one possible implementation manner, the executing module 151 is specifically configured to empty the DNS cache when the terminal receives the indication information, where the indication information is used to instruct the terminal to empty the DNS cache.

In one possible implementation, the terminal enters the roaming state such that the terminal satisfies a target condition, where the target condition includes at least one of:

the terminal finishes registering in the V-PLMN;

the terminal is configured with new DNS address information in roaming place;

the terminal completes the establishment of the LBO session or HR session at roaming.

The DNS processing device provided by the embodiment of the present application can implement each process implemented by the terminal in the above method embodiment, and achieve the same technical effect, so that repetition is avoided, and no description is repeated here.

The DNS processing device in the embodiment of the present application may be a terminal, for example, a terminal with an operating system, or may be a component in the terminal, for example, an integrated circuit or a chip. The terminal may be a UE or may be another device other than the UE. By way of example, terminals may include, but are not limited to, the types of terminals 11 listed above, other devices may be servers, network attached storage (Network Attached Storage, NAS), etc., and embodiments of the application are not specifically limited.

Fig. 26 shows a schematic structural diagram of another route reconfiguration 2600, and the route reconfiguration 2600 can be applied to a fifth network element. As shown in fig. 26, the route reconfiguration device 2600 may include:

A sending module 2601, where the sending module 2601 is configured to send third information to a ninth network element, where the third information is configured to indicate or request that a home operator (HPLMN) authentication (authentication) or authorization (authorization) visited operator (VPLMN) can perform a first operation, and the first operation includes at least one of:

directly using the first information;

Or,

the system comprises an acquisition module, a receiving module and a processing module, wherein the acquisition module is used for acquiring fourth information, the fourth information is used for indicating that a visiting place operator can execute a first operation, and the first operation comprises at least one of the following steps:

directly using the first information;

In one embodiment, the first information includes at least one of:

target DNAI (target DNAI);

In one embodiment, the route reconfiguration device 2600 is a device of the visited place, which may be a device of the visited place having a session management function (for example, V-SMF), or may be a device of the visited place having a unified data storage function (for example, V-UDR), or may be another core network device of the visited place.

directly updating target DNAI of the UPF by using the first information;

In one embodiment, the AF flow affecting procedure includes: the V-AF (or AF) provides the first information to a third network element (e.g., V-NEF); the third network element sends the first information to the fifth network element (e.g., V-SMF), and the route reconfiguration device 2600 directly uses the first information to perform at least one of:

reconfiguring a user plane of the PDU session;

reconfiguring route information of UPF;

updating target DNAI of UPF;

In one embodiment, the third information may be a message requesting that a home operator (HPLMN) authentication (authorization) or authorization (authorization) visited operator (VPLMN) may perform the first operation. For example, it may be HR-SBO authorization request, AF traffic influence request in VPLMN authorization request, HR-SBO authorization indication, or AF traffic influence in VPLMN authorization indication, HR-SBO allowed indication, AF traffic influence in VPLMN allowed indication, etc., or other names may be used.

In one embodiment, the route reconfiguration device 2600 further includes: and the receiving module is used for receiving the verification result or the authorization result sent by the ninth network element. The verification result or the authorization result includes at least one of:

in one embodiment, the fourth information includes at least one of:

HR-SBO allowed indication，AF traffic influence in VPLMN allowed indication。

the obtaining module may obtain fourth information from at least one of:

The obtaining the fourth information includes at least one of:

the acquisition module acquires the fourth information from a ninth network element or HPLMN through Nsmf_PDUSion_Create/Update response;

the obtaining module obtains the fourth information from a network element (for example, AMF) with an access management function through nsmf_pduse_ CreateSMContext Request, where the fourth information is obtained from a network element (for example, UDM) with a unified data management function by the network element with an access management function.

In one embodiment, after the obtaining module obtains the fourth information, if the receiving module in the routing reconfiguration device 2600 receives the first information, the sending module in the routing reconfiguration device 2600 may not send the first information to the ninth network element (such as H-SMF), or the executing module in the routing reconfiguration device 2600 directly executes at least one of the first operations.

In one embodiment, the route reconfiguration device 2600 further includes an execution module, where the execution module is configured to execute or complete the AF traffic influencing procedure (AF traffic influence procedure) or directly use the first information or use the AF traffic influencing request information (AF traffic influence request information) if the verification result or the authorization result is "verification pass, authorization or approval".

In one embodiment, when the route reconfiguration device 2600 sends the third information to the ninth network element, the route reconfiguration device may not send the first information to the ninth network element. That is, routing reconfiguration device 2600 only transmits the third information, and does not need to transmit the first information, which can save the message capacity carried in the signaling.

In another embodiment, when the route reconfiguration device 2600 sends the third information to the ninth network element, the first information may also be sent to the ninth network element, so that the ninth network element may obtain the second information by using the first information and send the second information to the route reconfiguration device 2600 when the verification result or the authorization result of the ninth network element is "verification is failed, unauthorized, and not approved". The method for the ninth network element to obtain the second information by using the first information and send the second information to the routing reconfiguration device 2600 may refer to the operation of the first network element in the embodiment corresponding to fig. 21, which is not described in detail in this embodiment.

In one embodiment, the receiving module is further configured to receive the first information sent by the third network element.

Optionally, the receiving module is configured to receive a third notification sent by a third network element, where the third notification includes the first information.

one or more PLMN IDs;

one or more UE identifiers;

One or more AF IDs;

one or more DNNs;

one or more S-NSSAI;

one or more IP addresses or port numbers.

In an embodiment, the obtaining module obtains the fourth information, which may be before the receiving module receives the first information sent by the third network element, or may be after the receiving module receives the first information sent by the third network element.

Optionally, as shown in fig. 18, the embodiment of the present application further provides a communication device 5000, including a processor 5001 and a memory 5002, where the memory 5002 stores a program or an instruction that can be executed on the processor 5001, for example, when the communication device 5000 is a network element, the program or the instruction is executed by the processor 5001 to implement the steps of the method embodiments of the first network element side, the second network element side, the third network element side, the first target network element side, the second target network element side, or the fifth network element side, and the like, and the same technical effects can be achieved, and will not be repeated herein. When the communication device 5000 is a terminal, the program or the instruction when executed by the processor 5001 implements the steps of the method embodiment on the terminal side, and the same technical effects can be achieved, so that repetition is avoided, and no further description is given here.

The embodiment of the application also provides a network element, which comprises a processor and a communication interface, wherein the communication interface is used for sending a query request to the second network element, and the query request is used for requesting to query the third network element; receiving a query response sent by the second network element, wherein the query response comprises address information of the third network element; sending a target request to a third network element according to the address information, wherein the target request is used for requesting to obtain the EDI of the roaming operator from a fourth network element; and receiving the EDI sent by the third network element. The network element embodiment corresponds to the first network element side method embodiment, and each implementation process and implementation manner of the method embodiment can be applied to the network element embodiment, and the same technical effect can be achieved.

The embodiment of the application also provides a network element, which comprises a processor and a communication interface, wherein the communication interface is used for receiving a query request sent by the first network element, and the query request is used for requesting to query the third network element; sending a query response to the first network element, wherein the query response comprises the address information of the third network element; the address information is used for the first network element to send a target request to the third network element, wherein the target request is used for requesting to obtain the EDI of the roaming place operator from the fourth network element. The network element embodiment corresponds to the second network element side method embodiment, and each implementation process and implementation manner of the method embodiment can be applied to the network element embodiment, and the same technical effect can be achieved.

The embodiment of the application also provides a network element, which comprises a processor and a communication interface, wherein the communication interface is used for receiving a target request sent by the first network element, and the target request is used for requesting to obtain the EDI of the roaming place operator from the fourth network element; the third network element sends EDI to the first network element. The network element embodiment corresponds to the third network element side method embodiment, and each implementation process and implementation manner of the method embodiment can be applied to the network element embodiment, and the same technical effect can be achieved.

The embodiment of the application also provides a network element, which comprises a processor and a communication interface, wherein the communication interface is used for receiving a first target notification message sent by the fourth network element, and the first target notification message is used for notifying the changed AF route influence request information in the fourth network element; and sending a second target notification message to the second target network element, wherein the second target notification message comprises updated policy information, and the policy information is used for the second target network element to reconfigure the traffic route. The network element embodiment corresponds to the first target network element side method embodiment, and each implementation process and implementation manner of the method embodiment can be applied to the network element embodiment, and the same technical effects can be achieved.

The embodiment of the application also provides a network element, which comprises a processor and a communication interface, wherein the communication interface is used for receiving a second target notification message sent by the first target network element, the second target notification message comprises updated strategy information, and the strategy information is used for the second target network element to reconfigure the flow route; the second target notification message is sent by the first target network element after receiving the first target notification message sent by the fourth network element, where the first target notification message is used to notify the fourth network element of the changed AF route influence request information. The network element embodiment corresponds to the second target network element side method embodiment, and each implementation process and implementation manner of the method embodiment can be applied to the network element embodiment, and the same technical effect can be achieved.

The embodiment of the application also provides a network element, which comprises a processor and a communication interface, wherein the communication interface is used for receiving ECS address configuration information sent by the first network element, and the ECS address configuration information comprises PLMN identifications; and transmitting ECS address configuration information to the terminal, wherein the ECS address configuration information is used for establishing PDU session of roaming place between the terminal and the ECS. The network element embodiment corresponds to the fifth network element side method embodiment, and each implementation process and implementation manner of the method embodiment can be applied to the network element embodiment, and the same technical effect can be achieved.

The embodiment of the present application further provides a network element, as shown in fig. 19, where the network element 1200 includes: a processor 1201, a network interface 1202, and a memory 1203. The network interface 1202 is, for example, a common public radio interface (Common Public Radio Interface, CPRI).

Specifically, the network element 1200 of the embodiment of the present application further includes: instructions or programs stored in the memory 1203 and capable of being executed by the processor 1201, the processor 1201 calls the instructions or programs in the memory 1203 to execute the methods executed by the modules in fig. 11 to 16, or the processor 1201 calls the instructions or programs in the memory 1203 to execute the methods executed by the modules corresponding to fig. 23 or 24, and achieve the same technical effects, so that repetition is avoided and no further description is given here.

It should be noted that, the network element in the embodiment of the present application may be the first network element, the second network element, the third network element, the first target network element, the second target network element, or the fifth network element described in the foregoing embodiment.

The network element provided by the embodiment of the application can realize each process of the first network element, the second network element, the third network element, the first target network element, the second target network element and the fifth network element in the embodiment of the method, and achieve the same technical effect, and in order to avoid repetition, the description is omitted.

The embodiment of the application also provides a terminal, which comprises a processor and a communication interface, wherein the processor is used for executing at least one of the following under the condition that the terminal enters a roaming state: clearing the DNS cache; a DNS re-query request is sent requesting a reselection of EAS in roaming. The terminal embodiment corresponds to the terminal-side method embodiment, and each implementation process and implementation manner of the method embodiment can be applied to the terminal embodiment, and the same technical effects can be achieved. Specifically, fig. 20 is a schematic diagram of a hardware structure of a terminal for implementing an embodiment of the present application.

The terminal 7000 includes, but is not limited to: at least some of the components of the radio frequency unit 7001, the network module 7002, the audio output unit 7003, the input unit 7004, the sensor 7005, the display unit 7006, the user input unit 7007, the interface unit 7008, the memory 7009, the processor 7010, and the like.

Those skilled in the art will appreciate that the terminal 7000 may further include a power source (e.g., a battery) for powering the various components, which may be logically connected to the processor 7010 via a power management system to perform functions such as managing charging, discharging, and power consumption via the power management system. The terminal structure shown in fig. 20 does not constitute a limitation of the terminal, and the terminal may include more or less components than those shown in the drawings, or may combine some components, or may be arranged in different components, which will not be described herein.

It should be appreciated that in embodiments of the present application, the input unit 7004 may include a graphics processing unit (Graphics Processing Unit, GPU) 7041 and a microphone 7042, with the graphics processor 7041 processing image data of still pictures or video obtained by an image capture device (e.g., a camera) in a video capture mode or an image capture mode. The display unit 7006 may include a display panel 7061, and the display panel 7061 may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like. The user input unit 7007 includes at least one of a touch panel 7071 and other input devices 7072. The touch panel 7071 is also referred to as a touch screen. The touch panel 7071 may include two parts, a touch detection device and a touch controller. Other input devices 7072 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and so forth, which are not described in detail herein.

In the embodiment of the present application, after receiving downlink data from the network side device, the radio frequency unit 7001 may transmit the downlink data to the processor 7010 for processing; in addition, the radio frequency unit 7001 may send uplink data to the network side device. In general, radio frequency units 7001 include, but are not limited to, antennas, amplifiers, transceivers, couplers, low noise amplifiers, diplexers, and the like.

The memory 7009 may be used to store software programs or instructions and various data. The memory 7009 may mainly include a first memory area storing programs or instructions and a second memory area storing data, wherein the first memory area may store an operating system, application programs or instructions (such as a sound playing function, an image playing function, etc.) required for at least one function, and the like. Further, the memory 7009 may include volatile memory or nonvolatile memory, or the memory 7009 may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM), static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (ddr SDRAM), enhanced SDRAM (Enhanced SDRAM), synchronous DRAM (SLDRAM), and Direct RAM (DRRAM). Memory 709 in embodiments of the application includes, but is not limited to, these and any other suitable types of memory.

The processor 7010 may include one or more processing units; the processor 7010 optionally integrates an application processor that primarily handles operations involving an operating system, user interfaces, applications, etc., and a modem processor that primarily handles wireless communication signals, such as a baseband processor. It will be appreciated that the modem processor described above may not be integrated into the processor 7010.

Wherein the processor 7010 is configured to perform at least one of the following in a case that the terminal enters a roaming state: clearing the DNS cache; a DNS re-query request is sent requesting a reselection of EAS in roaming.

The embodiment of the application provides a terminal, which can empty a DNS cache after entering a roaming place so as to facilitate the terminal to find an EAS as soon as possible; and/or the terminal may initiate a DNS re-query request to reselect the optimal EAS at roaming; thereby enabling establishment of a PDU session at the roaming place.

The terminal provided by the embodiment of the application can realize each process realized by the terminal in the embodiment of the method and achieve the same technical effect, and in order to avoid repetition, the description is omitted here.

The embodiment of the application also provides a readable storage medium, on which a program or an instruction is stored, which when executed by a processor, implements each process of the above method embodiment, and can achieve the same technical effects, and in order to avoid repetition, the description is omitted here.

Wherein the processor is a processor in the communication device described in the above embodiment. The readable storage medium includes computer readable storage medium such as computer readable memory ROM, random access memory RAM, magnetic or optical disk, etc.

The embodiment of the application further provides a chip, which comprises a processor and a communication interface, wherein the communication interface is coupled with the processor, and the processor is used for running programs or instructions to realize the processes of the embodiment of the method, and can achieve the same technical effects, so that repetition is avoided, and the description is omitted here.

It should be understood that the chips referred to in the embodiments of the present application may also be referred to as system-on-chip chips, or the like.

The embodiments of the present application further provide a computer program/program product stored in a storage medium, where the computer program/program product is executed by at least one processor to implement each process of the above method embodiments, and achieve the same technical effects, and are not repeated herein.

The embodiment of the application also provides a communication system, which comprises: a first network element, a second network element and a third network element, wherein the first network element is operable to perform the steps of the EDI obtaining method as described above, the second network element is operable to perform the steps of the EDI obtaining method as described above, and the third network element is operable to perform the steps of the EDI obtaining method as described above.

The embodiment of the application also provides a communication system, which comprises: a first target network element operable to perform the steps of the route reconfiguration method as described above, and a second target network element operable to perform the steps of the route reconfiguration method as described above.

The embodiment of the application also provides a communication system, which comprises: the method comprises the steps of a first network element, a second network element, a third network element, a first target network element, a second target network element, a fifth network element and a terminal, wherein the first network element can be used for executing the steps of the EDI acquisition method, the second network element can be used for executing the steps of the EDI acquisition method, the third network element can be used for executing the steps of the EDI acquisition method, the first target network element can be used for executing the steps of the route reconfiguration method, the second target network element can be used for executing the steps of the route reconfiguration method, the fifth network element can be used for executing the steps of the ECS address configuration information, and the terminal can be used for executing the steps of the DNS processing method.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. Furthermore, it should be noted that the scope of the methods and apparatus in the embodiments of the present application is not limited to performing the functions in the order shown or discussed, but may also include performing the functions in a substantially simultaneous manner or in an opposite order depending on the functions involved, e.g., the described methods may be performed in an order different from that described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art in the form of a computer software product stored in a storage medium (e.g. ROM/RAM, magnetic disk, optical disk) comprising instructions for causing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the method according to the embodiments of the present application.

The embodiments of the present application have been described above with reference to the accompanying drawings, but the present application is not limited to the above-described embodiments, which are merely illustrative and not restrictive, and many forms may be made by those having ordinary skill in the art without departing from the spirit of the present application and the scope of the claims, which are to be protected by the present application.

Claims

1. The method for acquiring the edge application server deployment information EDI is characterized by comprising the following steps:

the first network element sends a query request to the second network element, wherein the query request is used for requesting to query the third network element;

the first network element receives a query response sent by the second network element, wherein the query response comprises address information of the third network element;

the first network element sends a target request to the third network element according to the address information, wherein the target request is used for requesting to obtain EDI of a roaming place operator from a fourth network element;

the first network element receives the EDI sent by the third network element.

2. The method of claim 1, wherein the query request includes at least one of: public Land Mobile Network (PLMN) identity and user permanent identity (SUPI);

wherein the PLMN identity comprises at least one of: visited V-PLMN identity, home H-PLMN identity.

3. The method of claim 1, wherein the address information comprises at least one of: and the network protocol IP address of the third network element completely limits the domain name FQDN.

4. The method of claim 1, wherein the target request includes at least one of: PLMN identification, single network slice selection assistance information S-NSSAI, data network name DNN.

5. The method according to any of claims 1 to 4, wherein the first network element sending a query request to a second network element comprises:

the first network element sends the query request to the second network element via a home network storage function H-NRF network element.

6. The method according to any one of claims 1 to 4, further comprising:

the first network element sends a first request to a Unified Data Management (UDM) network element, wherein the first request is used for requesting to acquire subscription information of a terminal, the terminal is a terminal which is in a roaming place and needs to establish a Protocol Data Unit (PDU) session or update the PDU session, the subscription information is used for indicating whether the terminal is authorized to use a roaming place edge computing service, and the first request comprises a PLMN identifier;

the first network element receives a first response sent by the UDM network element, wherein the first response comprises subscription information of the terminal;

the first network element sending a query request to a second network element, comprising:

the first network element sends the query request to a second network element in case the subscription information indicates that the terminal is authorized to use roaming place edge computing services.

7. The method for acquiring the edge application server deployment information EDI is characterized by comprising the following steps:

the second network element receives a query request sent by the first network element, wherein the query request is used for requesting to query the third network element;

the second network element sends a query response to the first network element, wherein the query response comprises the address information of the third network element;

the address information is used for sending a target request to the third network element by the first network element, wherein the target request is used for requesting to obtain the EDI of the roaming place operator from the fourth network element.

8. The method of claim 7, wherein the second network element receiving the query request sent by the first network element comprises:

the second network element receives the query request sent by the first network element through a home network storage function H-NRF network element.

9. The method for acquiring the edge application server deployment information EDI is characterized by comprising the following steps:

the third network element receives a target request sent by the first network element, wherein the target request is used for requesting to obtain the EDI of the roaming place operator from the fourth network element;

and the third network element sends the EDI to the first network element.

10. The method of claim 9, wherein prior to the third network element sending the EDI to the first network element, the method further comprises:

the third network element verifies the first network element according to the target request to determine whether the first network element is authorized to acquire data from a roaming place operator to which the EDI belongs;

the third network element sending the EDI to the first network element, including:

and under the condition of verifying that the first network element is authorized to acquire data from a roaming place operator to which the EDI belongs, the third network element acquires the EDI from the fourth network element and sends the EDI to the first network element.

11. A method of route reconfiguration, the method comprising:

the method comprises the steps that a first target network element receives a first target notification message sent by a fourth network element, wherein the first target notification message is used for notifying the changed application function AF route influence request information in the fourth network element;

the first target network element sends a second target notification message to a second target network element, wherein the second target notification message comprises updated policy information, and the policy information is used for the second target network element to reconfigure the flow route.

12. The method of claim 11, wherein the AF routing impact request information includes at least one of: traffic description information, identification of the terminal to which traffic will be affected, traffic routing information of the target interface, data network access identification, public land mobile network PLMN identification.

13. The method of claim 11, wherein the first target network element sending a second target notification message to a second target network element comprises:

the first target network element sends a first notification message to the first network element, wherein the first notification message is used for notifying that the current home routing HR session is influenced by an AF request;

the first notification message is used for the first network element to perform traffic route reconfiguration, and sends a second notification message to a fifth network element, wherein the second notification message is used for notifying a Protocol Data Unit (PDU) session of a roaming place to need to be changed, and the second notification message is used for the fifth network element to perform traffic route reconfiguration.

14. The method of claim 11, wherein the first target network element sending a second target notification message to a second target network element comprises:

The first target network element sends a first notification message to a first network element, wherein the first notification message is used for notifying that the current home routing HR session is affected by an AF request, and the first notification message is used for the first network element to reconfigure a flow route;

the first target network element sends a second notification message to a fifth network element, wherein the second notification message is used for notifying the PDU session of the roaming place to need to be changed, and the second notification message is used for the fifth network element to reconfigure the flow route.

15. The method of claim 11, wherein the first target network element receiving the first target notification message sent by the fourth network element comprises:

the first target network element receives the first target notification message sent by the fourth network element through a sixth network element;

the first target network element sending a second target notification message to a second target network element, including:

16. The method of claim 11, wherein the first target network element sending a second target notification message to a second target network element comprises:

the first target network element sends a first notification message to a fifth network element, wherein the first notification message is used for notifying that the current home routing HR session is influenced by an AF request;

the first notification message is used for performing traffic route reconfiguration by the fifth network element, and sending a second notification message to the first network element, where the second notification message is used for notifying that a PDU session of a roaming place needs to be changed, and the second notification message is used for performing traffic route reconfiguration by the fifth network element when the first network element agrees to perform PDU session change.

17. The method according to any one of claims 13 to 16, wherein the second notification message comprises at least one of: data network access identification, traffic routing information of a target interface, affected user plane function identification, affected PDU session identification, affected terminal identification, PLMN identification.

18. The method according to any of claims 13 to 16, wherein the manner in which the fifth network element performs traffic routing reconfiguration comprises at least one of:

reselecting or replacing the user plane;

establishing a PDU session to a visitor edge application server, EAS;

instructing the user plane to replace the source destination EAS address accessed by the terminal with a destination EAS address carried by said first destination announcement message.

19. A method of route reconfiguration, the method comprising:

the method comprises the steps that a second target network element receives a second target notification message sent by a first target network element, wherein the second target notification message comprises updated strategy information, and the strategy information is used for reconfiguring flow routes by the second target network element;

the second target notification message is sent by the first target network element after receiving a first target notification message sent by a fourth network element, where the first target notification message is used to notify the fourth network element of the changed application function AF route influence request information.

20. The method of claim 19, wherein the second target network element receiving the second target notification message sent by the first target network element comprises:

The second target network element receives a first notification message sent by a first target network element through the first network element, wherein the first notification message is used for notifying that the current home routing HR session is affected by an AF request, and the first notification message is used for carrying out flow routing reconfiguration by the first network element;

the second target network element receives a second notification message sent by the first network element through a fifth network element, wherein the second notification message is used for notifying the protocol data unit PDU session of the roaming place that the PDU session needs to be changed, and the second notification message is used for the fifth network element to reconfigure the flow route.

21. The method of claim 19, wherein the second target network element receiving the second target notification message sent by the first target network element comprises:

the second target network element receives a second notification message sent by the first target network element through a fifth network element, wherein the second notification message is used for notifying the PDU session of the roaming place that needs to be changed, and the second notification message is used for the fifth network element to reconfigure the flow route.

22. The method according to claim 19, wherein the first target notification message is sent by the fourth network element to the first target network element via a sixth network element;

the second target network element receives a second target notification message sent by the first target network element, including:

23. The method of claim 19, wherein the second target network element receiving the second target notification message sent by the first target network element comprises:

the second target network element receives a first notification message sent by the first target network element through a fifth network element, wherein the first notification message is used for notifying that the current home routing HR session is affected by an AF request, and the first notification message is used for the fifth network element to reconfigure the flow routing;

The second target network element receives a second notification message sent by the fifth network element through the first network element, wherein the second notification message is used for notifying that the PDU session of the roaming place needs to be changed, and the second notification message is used for carrying out flow route reconfiguration by the fifth network element under the condition that the first network element agrees to execute the PDU session change.

24. A method for obtaining ECS address configuration information of an edge configuration server, the method comprising:

the method comprises the steps that a fifth network element receives ECS address configuration information sent by a first network element, wherein the ECS address configuration information comprises Public Land Mobile Network (PLMN) identifications;

and the fifth network element sends the ECS address configuration information to the terminal, wherein the ECS address configuration information is used for establishing a protocol data unit PDU session of the roaming place between the terminal and the ECS.

25. The method of claim 24, wherein the ECS address configuration information is stored by a unified data storage network element or a unified data management network element.

26. A domain name system, DNS, processing method, the method comprising:

in case the terminal enters a roaming state, the terminal performs at least one of:

Clearing the DNS cache;

a DNS re-query request is sent requesting a reselection of the edge application server EAS at roaming.

27. The method of claim 26, wherein the terminal empties the DNS cache, comprising:

and under the condition that the terminal receives the indication information, the terminal empties the DNS cache, wherein the indication information is used for indicating the terminal to empty the DNS cache.

28. The method according to claim 26 or 27, wherein the terminal entering a roaming state satisfies a target condition for the terminal, the target condition comprising at least one of:

the terminal finishes registering in the visiting public land mobile network V-PLMN;

the terminal is configured with new DNS address information in a roaming place;

the terminal completes the establishment of a local breakout LBO session or a home routing HR session in a roaming place.

29. An edge application server deployment information EDI obtaining device applied to a first network element, wherein the device includes: a transmitting module and a receiving module;

the sending module is used for sending a query request to the second network element, wherein the query request is used for requesting to query the third network element;

The receiving module is configured to receive a query response sent by the second network element, where the query response includes address information of the third network element;

the sending module is further configured to send a target request to the third network element according to the address information, where the target request is used to request obtaining EDI of the roaming operator from the fourth network element;

the receiving module is further configured to receive the EDI sent by the third network element.

30. An edge application server deployment information EDI obtaining device applied to a second network element, wherein the device includes: a receiving module and a transmitting module;

the receiving module is used for receiving a query request sent by the first network element, wherein the query request is used for requesting to query the third network element;

the sending module is configured to send a query response to the first network element, where the query response includes address information of the third network element;

31. An edge application server deployment information EDI obtaining device applied to a third network element, wherein the device includes: a receiving module and a transmitting module;

The receiving module is used for receiving a target request sent by the first network element, wherein the target request is used for requesting to obtain the EDI of the roaming place operator from the fourth network element;

the sending module is configured to send the EDI to the first network element.

32. A route reconfiguration device for use with a first target network element, the device comprising: a receiving module and a transmitting module;

the receiving module is configured to receive a first target notification message sent by a fourth network element, where the first target notification message is used to notify the fourth network element of changed application function AF route impact request information;

the sending module is configured to send a second target notification message to a second target network element, where the second target notification message includes updated policy information, and the policy information is used for the second target network element to reconfigure a traffic route.

33. A route reconfiguration device for use with a second target network element, the device comprising: a receiving module;

the receiving module is configured to receive a second target notification message sent by the first target network element, where the second target notification message includes updated policy information, and the policy information is used for the second target network element to reconfigure a traffic route;

34. An apparatus for acquiring ECS address configuration information of an edge configuration server, applied to a fifth network element, characterized in that the apparatus includes: a receiving module and a transmitting module;

the receiving module is configured to receive ECS address configuration information sent by the first network element, where the ECS address configuration information includes a public land mobile network PLMN identifier;

the sending module is configured to send the ECS address configuration information to a terminal, where the ECS address configuration information is used for the terminal to establish a protocol data unit PDU session with an ECS in a roaming place.

35. A domain name system, DNS, processing device, applied to a terminal, the device comprising: an execution module;

the execution module is configured to execute at least one of the following when the terminal enters a roaming state:

clearing the DNS cache;

36. A network element comprising a processor, a memory and a program or instruction stored on the memory and executable on the processor, the program or instruction when executed by the processor implementing the steps of the edge application server deployment information EDI acquisition method according to any one of claims 1 to 6, or implementing the steps of the EDI acquisition method according to claim 7 or 8, or implementing the steps of the EDI acquisition method according to claim 9 or 10.

37. A network element comprising a processor, a memory and a program or instruction stored on the memory and executable on the processor, which program or instruction when executed by the processor implements the steps of the route reconfiguration method according to any one of claims 11 to 18 or the steps of the route reconfiguration method according to any one of claims 19 to 23.

38. A network element comprising a processor, a memory and a program or instruction stored on the memory and executable on the processor, which program or instruction when executed by the processor performs the steps of the method for obtaining ECS address configuration information of an edge configuration server according to claim 24 or 25.

39. A terminal comprising a processor, a memory and a program or instruction stored on the memory and executable on the processor, which when executed by the processor implements the steps of the domain name system DNS processing method according to any of claims 26 to 28.

40. A readable storage medium, wherein a program or an instruction is stored on the readable storage medium, which when executed by a processor, implements the steps of the edge application server deployment information EDI acquisition method according to any one of claims 1 to 6, or implements the steps of the EDI acquisition method according to claim 7 or 8, or implements the steps of the EDI acquisition method according to claim 9 or 10, or implements the steps of the route reconfiguration method according to any one of claims 11 to 18, or implements the steps of the route reconfiguration method according to any one of claims 19 to 23, or implements the steps of the edge configuration server ECS address configuration information acquisition method according to any one of claims 24 or 25, or implements the steps of the domain name system DNS processing method according to any one of claims 26 to 28.