WO2023213305A1

WO2023213305A1 - Edi acquisition, routing reconfiguration, ecs address configuration information acquisition, dns processing method and apparatus, and device

Info

Publication number: WO2023213305A1
Application number: PCT/CN2023/092325
Authority: WO
Inventors: 吕华章
Original assignee: 维沃移动通信有限公司
Priority date: 2022-05-06
Filing date: 2023-05-05
Publication date: 2023-11-09
Also published as: CN117014907A

Abstract

The application discloses an EDI acquisition, routing reconfiguration, ECS address configuration information acquisition, DNS processing method and apparatus, and a device, belonging to the technical field of communications. The EDI acquisition method provided by an embodiment in the present application comprises: a first network element sending a query request to a second network element, the query request being used for requesting to query a third network element; the first network element receiving a query response sent by the second network element, the query response comprising address information of the third network element; and the first network element sending a target request to the third network element according to the address information, the target request being used for requesting to obtain the EDI of a roaming operator from a fourth network element; and the first network element receiving the EDI sent by the third network element.

Description

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

Cross-references to related applications

This application claims the priority of Chinese Patent Application No. 202210489834.8 filed in China on May 06, 2022, and the priority of Chinese Patent Application No. 202310106999.7 filed in China on February 9, 2023, and the priority of Chinese Patent Application No. 202310106999.7 filed in China on February 09, 2023. The priority of Chinese patent application number 202310140125.3 filed in China on the 17th, the entire content of which is incorporated herein by reference.

Technical field

This application belongs to the field of communication technology, and specifically relates to an EDI acquisition, route reconfiguration, ECS address configuration information acquisition, DNS processing method, device and equipment.

Background technique

In the roaming scenario, that is, after the terminal moves from the home place to the roaming place, the terminal needs to re-establish a protocol data unit (Protocol Data Unit, PDU) session to achieve data transmission. However, there is currently no corresponding solution for how to establish a PDU session for a terminal in a roaming location.

Contents of the invention

Embodiments of the present application provide an EDI acquisition, route reconfiguration, ECS address configuration information acquisition, DNS processing method, device and equipment, which can solve the problem of how to establish a PDU session for a terminal in a roaming location.

In a first aspect, an EDI acquisition method is provided. The EDI acquisition method includes: a first network element sends a query request to a second network element, and the query request is used to request to query a third network element; the first network element receives the second network element. The query response sent by the network element includes the address information of the third network element; the first network element sends a target request to the third network element based on the address information, and the target request is used to request the request from the fourth network element. Obtain the EDI of the roaming operator; the first network element receives the EDI sent by the third network element.

In a second aspect, an EDI acquisition device is provided, which is applied to the first network element. The EDI acquisition device includes: a sending module and a receiving module. The sending module 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. 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 also configured to send a target request to the third network element based on the address information. The target request is used to request to obtain the EDI of the roaming operator from the fourth network element. The receiving module is also used to receive EDI sent by the third network element.

In a third aspect, an EDI acquisition method is provided. The EDI acquisition method includes: the second network element receives a query request sent by the first network element, and the query request is used to request to query the third network element; the second network element sends a request to the third network element; A network element sends a query response, and the query response includes the address information of the third network element; wherein, the address information is used by the first network element to send a target request to the third network element, and the target request is used to request a request from the fourth network element. Obtain the EDI of the roaming operator.

In a fourth aspect, an EDI acquisition device is provided, which is applied to the second network element. The EDI acquisition device includes: a receiving module and a sending module. The receiving module is configured to receive a query request sent by the first network element, where the query request is used to request query of the third network element. The sending module is configured to send a query response to the first network element, where the query response includes the address information of the third network element. The address information is used by the first network element to send a target request to the third network element, and the target request is used to request to obtain the EDI of the roaming operator from the fourth network element.

In the fifth aspect, an EDI acquisition method is provided. The EDI acquisition method includes: a third network element receives a target request sent by the first network element, and the target request is used to request 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 acquisition device is provided, which is applied to a third network element. The EDI acquisition device includes: a receiving module and a sending module. The receiving module is configured to receive a target request sent by the first network element. The target request is used to request to obtain the EDI of the roaming operator from the fourth network element. The sending module is used to send EDI to the first network element.

In the embodiment of this application, the first network element can query the third network element by sending a query request to the second network element, and after finding the third network element, request the third network element to obtain the information from the fourth network element. Obtain the EDI of the roaming operator to obtain the EDI, thereby generating DNS message processing rules based on the EDI, thereby achieving the establishment of a PDU session in the roaming location.

In a seventh aspect, a route reconfiguration method is provided. The route reconfiguration method includes: a first target network element receiving a first target notification message sent by a fourth network element, and the first target notification message is used to notify the fourth network element. The changed AF route impact request information in Traffic routing reconfiguration.

In an eighth aspect, a route reconfiguration device is provided, which is applied to the first target network element. The route reconfiguration device includes: a receiving module and a sending module. The receiving module is configured to receive the first target notification message sent by the fourth network element. The first target notification message is used to notify the fourth network element of the changed AF route impact request information. The sending module 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 perform traffic routing reconfiguration.

In a ninth aspect, a route reconfiguration method is provided. The route reconfiguration method includes: the second target network element receives a second target notification message sent by the first target network element, and the second target notification message includes updated policy information. , the policy information is used for traffic routing reconfiguration by the second target network element; wherein, 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. The notification message is used to notify the changed AF route impact request information in the fourth network element.

In a tenth aspect, a route reconfiguration device is provided, which is applied to the second target network element. The route reconfiguration device includes: a receiving module. receiving mode block, used to receive a second target notification message sent by the first target network element, the second target notification message includes updated policy information, and the policy information is used for the second target network element to perform traffic routing reconfiguration; wherein, the second target network element The notification message is sent by the first target network element after receiving the first target notification message sent by the fourth network element. The first target notification message is used to notify the fourth network element of the changed AF route impact request information, thereby achieving Establishment of PDU session at roaming location.

In this embodiment of the present application, the first target network element can receive the first target notification message sent by the fourth network element, which is used to notify the fourth network element of the changed AF route impact request information, and then the first target network element can according to The AF route impact request information sends updated policy information to the second target network element for use in traffic routing reconfiguration by the second target network element, thereby applying the AF request route impact to the HR session.

In an eleventh aspect, a method for obtaining ECS address configuration information is provided. The method for obtaining ECS address configuration information includes: the fifth network element receives the ECS address configuration information sent by the first network element, and the ECS address configuration information includes a PLMN identifier. ; The fifth network element sends ECS address configuration information to the terminal. The ECS address configuration information is used by the terminal to establish a roaming PDU session with the ECS.

In a twelfth aspect, a device for obtaining ECS address configuration information is provided, which is applied to the fifth network element. The device for obtaining ECS address configuration information includes: a receiving module and a sending module. The receiving module is configured to receive the ECS address configuration information sent by the first network element, where the ECS address configuration information includes the PLMN identifier. The sending module is used to send ECS address configuration information to the terminal. The ECS address configuration information is used by the terminal to establish a roaming PDU session with the ECS.

In the embodiment of this 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 establishing a roaming location between the terminal and the ECS. PDU session, thereby realizing the establishment of PDU session in the roaming location.

In a thirteenth aspect, a DNS processing method is provided. The DNS processing method includes: when the terminal enters the roaming state, the terminal performs at least one of the following: clearing the DNS cache; sending a DNS requery request. The DNS requery request uses Request to reselect EAS in roaming location.

In a fourteenth aspect, a DNS processing device is provided, applied to a terminal, and the DNS processing device includes: an execution module. The execution module is configured to perform at least one of the following when the terminal enters the roaming state: clear the DNS cache; send a DNS requery request, and the DNS requery request is used to request EAS reselection in the roaming location.

In the embodiment of this application, after the terminal enters the roaming area, it can clear the DNS cache so that the terminal can find the EAS as soon as possible; and/or the terminal can initiate a DNS re-query request to reselect the optimal EAS in the roaming area; thereby realizing roaming The establishment of the PDU session in the roaming location; thereby realizing the establishment of the PDU session in the roaming location.

In a fifteenth aspect, a network element is provided. The network element includes a processor and a memory. The memory stores programs or instructions that can be run on the processor. When the program or instructions are executed by the processor, Implement the steps of the method described in the first aspect, or implement the steps of the method described in the third aspect, or implement the steps of the method described in the fifth aspect.

In a sixteenth aspect, a network element is provided, including a processor and a communication interface, wherein the communication interface is used to send a query request to the second network element, the query request is used to request to query the third network element; and receives the second The query response sent by the network element includes the address information of the third network element; and based on the address information, a target request is sent to the third network element, and the target request is used to request to obtain the roaming location from the fourth network element. The operator's EDI; and receiving the EDI sent by the third network element.

In a seventeenth aspect, a network element is provided, including a processor and a communication interface, wherein the communication interface is used to receive a query request sent by the first network element, and the query request is used to request to query the third network element; and to the third network element; A network element sends a query response, and the query response includes the address information of the third network element; wherein, the address information is used by the first network element to send a target request to the third network element, and the target request is used to request a request from the fourth network element. Obtain the EDI of the roaming operator.

In an eighteenth aspect, a network element is provided, including a processor and a communication interface, wherein the communication interface is used to receive a target request sent by the first network element, and the target request is used to request to obtain roaming operations from the fourth network element. The third network element sends EDI to the first network element.

In a nineteenth aspect, a network element is provided. The network element includes a processor and a memory. The memory stores programs or instructions that can be run on the processor. When the program or instructions are executed by the processor, Implement the steps of the method described in the seventh aspect, or implement the steps of the method described in the ninth aspect.

In a twentieth aspect, a network element is provided, including a processor and a communication interface, wherein the communication interface is used to receive a first target notification message sent by a fourth network element, and the first target notification message is used to notify the fourth network element The changed AF route impact request information is sent to the second target network element; and a second target notification message is sent to the second target network element. The second target notification message includes updated policy information, and the policy information is used for the second target network element to perform traffic routing reconfiguration. .

In a twenty-first aspect, a network element is provided, including a processor and a communication interface, wherein the communication interface is used to receive a second target notification message sent by the first target network element, and the second target notification message includes an updated policy. Information, policy information is used for traffic routing reconfiguration by the second target network element; wherein, 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. The target notification message is used to notify the fourth network element of the changed AF route impact request information.

In a twenty-second aspect, a network element is provided. The network element includes a processor and a memory. The memory stores programs or instructions that can be run on the processor. The program or instructions are executed by the processor. When implementing the steps of the method described in the eleventh aspect.

In a twenty-third aspect, a network element is provided, including a processor and a communication interface, wherein the communication interface is used to receive ECS address configuration information sent by the first network element, and the ECS address configuration information includes a PLMN identifier; and sends it to the terminal ECS address configuration information. The ECS address configuration information is used by the terminal to establish a roaming PDU session with the ECS.

In a twenty-fourth aspect, a terminal is provided. The terminal includes a processor and a memory. The memory stores programs or instructions that can be run on the processor. The program or instructions are implemented when executed by the processor. The steps of the method as described in the thirteenth aspect.

A twenty-fifth aspect provides a terminal, including a processor and a communication interface, wherein the processor is configured to perform at least one of the following when the terminal enters the roaming state: clearing the DNS cache; sending a DNS re-query request, DNS The requery request is used to request EAS reselection in the roaming location.

A twenty-sixth aspect provides a readable storage medium, the readable storage medium stores programs or instructions, and when the programs or instructions are executed by a processor, the steps of the method described in the first aspect are implemented, or Implement the steps of the method described in the third aspect, or implement the steps of the method described in the fifth aspect, or implement the steps of the method described in the seventh aspect, or implement the steps of the method described in the ninth aspect , or implemented as in the tenth The steps of the method described in one aspect, or the steps of implementing the method described in the thirteenth aspect.

In the twenty-seventh aspect, a chip is provided. The chip includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement as described in the first aspect. method, or implement the method as described in the third aspect, or implement the method as described in the fifth aspect, or implement the method as described in the seventh aspect, or implement the method as described in the ninth aspect, or implement as The method described in the eleventh aspect, or implementing the method described in the thirteenth aspect.

A twenty-eighth aspect, a computer program/program product is provided, the computer program/program product is stored in a storage medium, and the computer program/program product is executed by at least one processor to implement the first aspect The steps of the method described in the third aspect, or the steps of the method described in the fifth aspect, or the steps of the method described in the seventh aspect, or the steps of the method described in the ninth aspect The steps of the method described in the aspect, or the steps of implementing the method described in the eleventh aspect, or the steps of implementing the method described in the thirteenth aspect.

Description of the drawings

Figure 1 is a schematic architectural diagram of a wireless communication system provided by an embodiment of the present application;

Figure 2 is one of the flow charts of an EDI acquisition method provided by an embodiment of the present application;

Figure 3 is the second flow chart of an EDI acquisition method provided by an embodiment of the present application;

Figure 4 is one of the flow charts of a route reconfiguration method provided by an embodiment of the present application;

Figure 5 is the second flow chart of a route reconfiguration method provided by an embodiment of the present application;

Figure 6 is the third flow chart of a route reconfiguration method provided by an embodiment of the present application;

Figure 7 is the fourth flowchart of a route reconfiguration method provided by an embodiment of the present application;

Figure 8 is the fifth flowchart of a route reconfiguration method provided by an embodiment of the present application;

Figure 9 is a flow chart of a method for obtaining ECS address configuration information provided by an embodiment of the present application;

Figure 10 is a flow chart of a DNS processing method provided by an embodiment of the present application;

Figure 11 is one of the structural schematic diagrams of an EDI acquisition device provided by an embodiment of the present application;

Figure 12 is the second structural schematic diagram of an EDI acquisition device provided by an embodiment of the present application;

Figure 13 is the third structural schematic diagram of an EDI acquisition device provided by an embodiment of the present application;

Figure 14 is one of the structural schematic diagrams of a routing reconfiguration device provided by an embodiment of the present application;

Figure 15 is the second structural schematic diagram of a routing reconfiguration device provided by an embodiment of the present application;

Figure 16 is a schematic structural diagram of a device for obtaining ECS address configuration information provided by an embodiment of the present application;

Figure 17 is a schematic structural diagram of a DNS processing device provided by an embodiment of the present application;

Figure 18 is a schematic diagram of the hardware structure of a communication device provided by an embodiment of the present application;

Figure 19 is a schematic diagram of the hardware structure of a network element provided by an embodiment of the present application;

Figure 20 is a schematic diagram of the hardware structure of a terminal provided by an embodiment of the present application.

Figure 21 is flowchart 6 of a route reconfiguration method provided by an embodiment of the present application;

Figure 22 is flowchart 7 of a route reconfiguration method provided by an embodiment of the present application;

Figure 23 is the third structural schematic diagram of a routing reconfiguration device provided by an embodiment of the present application;

Figure 24 is a schematic structural diagram of an information sending device provided by an embodiment of the present application.

Figure 25 is the eighth flowchart of a route reconfiguration method provided by an embodiment of the present application.

Figure 26 is the fourth structural schematic diagram of a reconfiguration device provided by an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be clearly described below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, but not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art fall within the scope of protection of this application.

The terms "first", "second", etc. in the description and claims of this application are used to distinguish similar objects and are not used to describe a specific order or sequence. It is to be understood that the terms so used are interchangeable under appropriate circumstances so that the embodiments of the present application can be practiced in sequences other than those illustrated or described herein, and that "first" and "second" are distinguished objects It is usually one type, and the number of objects is not limited. For example, the first object can be one or multiple. In addition, "and/or" in the description and claims indicates at least one of the connected objects, and the character "/" generally indicates that the related objects are in an "or" relationship.

It is worth pointing out that the technology described in the embodiments of this application is not limited to Long Term Evolution (LTE)/LTE Evolution (LTE-Advanced, LTE-A) systems, and can also be used in other wireless communication systems, such as code Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access, OFDMA), Single-carrier Frequency Division Multiple Access (SC-FDMA) and other systems. The terms "system" and "network" in the embodiments of this application are often used interchangeably, and the described technology can be used not only for the above-mentioned systems and radio technologies, but also for other systems and radio technologies. The following description describes a New Radio (NR) system for example purposes, and NR terminology is used in much of the following description, but these techniques can also be applied to applications other than NR system applications, such as 6th ^generation Generation, 6G) communication system.

Figure 1 shows a block diagram of a wireless communication system to which embodiments of the present application are applicable. The wireless communication system includes a terminal 11 and a network side device 12. The terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), or a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a palmtop computer, a netbook, or a super mobile personal computer. (ultra-mobile personal computer, UMPC), mobile Internet device (Mobile Internet Device, MID), augmented reality (augmented reality, AR)/ Virtual reality (VR) equipment, robots, wearable devices (Wearable Devices), vehicle-mounted equipment (VUE), pedestrian terminals (PUE), smart home (home equipment with wireless communication functions, such as refrigerators, TVs, washing machines or furniture, etc.), game consoles, personal computers (PCs), teller machines or self-service machines and other terminal-side devices. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets) , smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. It should be noted that the embodiment of the present application does not limit the specific type of the terminal 11. The network side device 12 may include an access network device or a core network device, where the access network device 12 may also be called a radio access network device, a radio access network (Radio Access Network, RAN), a radio access network function or Wireless access network unit. The access network device 12 may include a base station, a WLAN access point or a WiFi node, etc. The base station may be called a Node B, an evolved Node B (eNB), an access point, a Base Transceiver Station (BTS), a radio Base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B, Home Evolved Node B, Transmitting Receiving Point (TRP) or all Some other appropriate terminology in the above field, as long as the same technical effect is achieved, the base station is not limited to specific technical terms. It should be noted that in the embodiment of this application, only the base station in the NR system is used as an example for introduction, and The specific type of base station is not limited. Core network equipment may include but is not limited to at least one of the following: 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 Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Service Discovery function (Edge Application Server Discovery Function, EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), centralized network configuration ( Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (Local NEF, or L-NEF), Binding Support Function (Binding Support Function, BSF), application function (Application Function, AF), etc. It should be noted that in the embodiment of this application, only the core network equipment in the NR system is used as an example for introduction, and the specific type of the core network equipment is not limited.

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

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

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

The second target network element, in this patent, may be an SMF, a home SMF, or a roaming SMF, or may be one or more other devices among 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 among the above core network devices.

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

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

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

The sixth network element, in this patent, is a PCF or a roaming PCF, and may also be one or more other devices among 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, are used for at least one of the following purposes:

Request influence SMF routing decisions for User Plane traffic of PDU Sessions;

Influence UPF(re)selection);

Allow routing of user traffic to a local access (identified by a DNAI) to a Data Network.

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;

Traffic influence request (request for traffic influence);

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

AF influenced Traffic Steering Enforcement Control (AF influenced Traffic Steering Enforcement Control);

AF request information;

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

policy information

Traffic influence parameters.

The above-mentioned AF request, traffic impact request, PCC rule, AF impact traffic diversion execution control, AF request information, AF traffic impact request information, or policy information, or traffic impact parameters, etc., contain at least one of the following content, as shown in Table 0 middle:

Table 0

The following explains some concepts and/or terms involved in the EDI acquisition, route reconfiguration, ECS address configuration information acquisition, DNS processing method, apparatus and equipment provided by the embodiments of this application.

The Edge Application Server Discovery Function (EASDF) network element is a newly proposed core network element used to process Domain Name System (Domain Name System, DNS) query requests sent from terminals.

The EASDF network element is a network element used to process the DNS query of the terminal. Specifically, the terminal sends the DNS query to the EASDF network element, and then the EASDF network element makes a judgment based on the DNS query and sends the DNS query to the Central DNS. C-DNS) or local DNS (Local DNS, L-DNS), and then send the fully qualified domain name (Fully Qualified Domain Name, FQDN) and other information in the DNS query to the SMF network element, and the SMF network element provides the corresponding DNS for EASDF The Internet Protocol (IP) address of the server, such as: C-DNS or L-DNS; then, after C-DNS or L-DNS finds the IP address corresponding to the FQDN, it sends it to the EASDF network element, and the EASDF network element will The query results are saved to the SMF network element and then sent to the terminal. In this way, the terminal obtains the server IP address of the requested FQDN.

The EDI acquisition method, routing reconfiguration method, ECS address configuration information acquisition method, and 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.

Question 1: Generation of DNS processing rules in roaming scenario

In a roaming scenario, Home EASDF (Home EASDF, H-EASDF) is responsible for using DNS processing rules, and H-SMF is responsible for generating DNS processing rules. However, since the terminal is in the roaming area, the terminal needs to access the DNS processing rules of the roaming area nearby, and needs to use the Edge Application Server Deployment Information (EDI) of the roaming area. However, under the Home Public Land Mobile Network (H-PLMN), there is currently no corresponding solution for how to obtain the EDI information of the roaming location.

In response to the above question 1, in the embodiment of this application, the home SMF (Home SMF, H-SMF) network element can obtain EDI from the visited UDR (Visited-UDR, V-UDR) network element to generate DNS message processing rules. Specifically, after H-SMF queries the visited NEF (Visited-NEF, V-NEF) network element, it requests the V-NEF network element to obtain the EDI of the roaming operator from the V-UDR network element to obtain the EDI. , thereby generating DNS message processing rules based on EDI.

Question 2: AF traffic routing impact (traffic influence)

Traffic influence is a method for AF to affect 5GC routing. The terminal establishes a connection with a business server. When the business server is replaced and the server IP address changes, the connection between the terminal and the business server will be affected. Therefore, AF needs to provide relevant information affecting routing to 5GC for user plane reconfiguration. However, under the Home Routed (HR) session, AF traffic influence is not currently supported. That is, for the HR session, AF cannot be used to request routing influence.

In response to the above question 2, in the embodiment of this application, the home PCF (Home PCF, H-PCF) network element or the visited PCF (Visited-PCF, V-PCF) network element can receive the notification message sent by the V-UDR network element. , this notification message is used to notify the changed AF route impact request information in the V-UDR network element, and then sends updated policy information to the H-SMF network element and/or V-SMF network element based on the AF route impact request information. , used for H-SMF network elements and/or V-SMF network elements to perform traffic routing reconfiguration, so as to apply the AF request routing impact to the HR session.

Question 3: How does the terminal establish the roaming protocol data unit (Protocol) with the Edge Configuration Server (ECS)? Data Unit (PDU) session, there is currently no corresponding solution.

In response to the above question 3, in the embodiment of this application, the H-SMF network element can send ECS address configuration information to the V-SMF network element, so that the V-SMF network element can send the ECS address configuration information to the terminal for use with the terminal. ECS establishes a PDU session in the roaming location.

Question 4: After the terminal enters the roaming area, the edge server visited may not be the optimal server according to the policy of the roaming area. At this time, there is no clear plan for the operation of the terminal.

In response to the above question 4, in the embodiment of the present application, after the terminal enters the roaming area, it can clear the DNS cache so that the terminal can find the EAS as soon as possible; and/or the terminal can initiate a DNS re-query request to reselect the optimal one in the roaming area. EAS.

An embodiment of the present application provides an EDI obtaining method. Figure 2 shows a flow chart of an EDI obtaining method provided by an embodiment of the present application. As shown in Figure 2, the EDI acquisition method provided by the embodiment of the present 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 this embodiment of the present application, the above query request is used to request to query the third network element.

Optionally, in this embodiment of the present application, the first network element may be an H-SMF network element. The above-mentioned second network element may be a V-NRF network element, and the above-mentioned third network element may be a V-NEF network element. It should be noted that the above-mentioned first network element, second network element, and third network element can also be other network elements, which are not limited by the embodiments of this application. Obtaining EDI from the roaming location requires passing through the third network element.

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

Optionally, in this embodiment of the present application, the above-mentioned PLMN identification includes at least one of the following: a visited PLMN (V-PLMN) identification and an H-PLMN identification.

Optionally, in this embodiment of the present application, the above step 201 can be specifically implemented through the following step 201a.

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

Optionally, in this embodiment of the present application, the above query request may be Nnrf_NFDiscovery_Request.

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

Optionally, in this embodiment of the present application, the above step 202 may be specifically implemented through the following step 202a.

Step 202a: The second network element receives the 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 this embodiment of the present application, the above query response includes the address information of the third network element. The address information is used by the first network element to send a target request to the third network element, and the target request is used to request to obtain the EDI of the roaming operator from the fourth network element.

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

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

Optionally, in this embodiment of the present application, after the second network element finds the third network element, it can send a query response to the H-NRF network element to send the address information of the third network element to the H-NRF network element. Then the H-NRF network element sends the address information of the third network element to the first network element.

Optionally, in this embodiment of the present application, the above 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 this embodiment of the present application, the above target request is used to request to obtain the EDI of the roaming operator from the fourth network element.

Optionally, in this embodiment of the present application, the above target request includes at least one of the following: PLMN identification, Single Network Slice Selection Assistance Information (S-NSSAI), Data Network Name, DNN).

Optionally, in this embodiment of the present application, the above target request may be Nnef_EASDeployment_Subscribe or Nnef_EASDeployment_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.

Embodiments of the present application provide an EDI acquisition method. The first network element can query the third network element by sending a query request to the second network element, and after finding the third network element, request the third network element from The fourth network element obtains the EDI of the operator in the roaming location to obtain the EDI, thereby generating DNS message processing rules based on the EDI, thereby establishing the PDU session in the roaming location.

Optionally, the EDI acquisition method provided by the embodiment of the present application also includes the following steps 209 and 210, and the above step 201 can be specifically implemented through the following step 201b.

Step 209: The first network element sends the first request to the UDM network element.

In the embodiment of this application, the above-mentioned first request is used to request to obtain the subscription information of the terminal. The terminal is a terminal in a roaming area that needs to establish a PDU session or update a PDU session. The subscription information is used to indicate whether the terminal is authorized to use the roaming area. For edge computing services, the first request includes the PLMN identifier.

Step 210: The first network element receives the first response sent by the UDM network element.

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

Step 201b: When the subscription information indicates that the terminal is authorized to use the roaming edge computing service, the first network element sends a query request to the second network element.

Optionally, in this embodiment of the present application, before the above-mentioned step 207, the EDI acquisition method provided by this embodiment of the present application further includes the following step 211, and the above-mentioned step 207 can be specifically implemented through the following step 207a.

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: After 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 acquisition method provided by the embodiment of the present application will be described below through a specific implementation mode (ie, implementation mode 1).

Implementation Mode 1: H-SMF network element restores EDI from V-NEF network element

As shown in Figure 3, the EDI acquisition method provided by the embodiment of the present 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_PDUSession_Create/Update request.

Step 22: The H-SMF network element restores the terminal's subscription information from the UDM network element.

In the embodiment of this application, the above-mentioned subscription information indicates whether the terminal can use edge computing services in roaming areas.

The signaling is: Nudm_SDM_Get or Nudm_SDM_Subscribe. The signaling needs to include the terminal's SUPI and PLMN ID. The PLMN ID may be the PLMN ID of the roaming location or the home location. In this way, the terminal subscription information of the terminal under a specific operator can be restored from the UDM.

The contract information that the H-SMF network element needs to obtain is as shown in the following Table 1: Another implementation manner is that the V-SMF obtains the contract information. V-SMF checks whether the terminal can use EASDF to perform EAS search under the roaming operator.

Table 1

Specifically, the session management subscription data may include at least one item in the following Table 2:

Table 2

The input content includes: NF ID=H-SMF; Subscription data type(s)=SUPI, Data Sub Key(s)=S-NSSAI, DNN, PLMN ID. Among them, the roaming location PLMN ID (VPLMN ID) in the PLMN ID is required.

It should be noted that if after verification of the contract information, it is found that the terminal cannot use edge computing services, then all the processes after step 23 will be skipped and not executed.

Step 23. Select the H-EASDF network element from the H-SMF network element.

Step 24: The H-SMF network element sends a query request to the H-NRF network element.

The signaling is: Nnrf_NFDiscovery_Request to request to find the V-NEF network element.

In the embodiment of this application, since the H-EASDF network element has been selected for the terminal in the roaming area, the H-SMF network element needs to be configured with basic DNS processing rules (Baseline DNS Pattern).

However, BaselineDNSPattern needs to be derived based on EDI, and the EDI information is stored in the V-UDR network element in the roaming location; therefore, the H-SMF network element needs to restore 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 to find the V-NEF network element.

The parameters in the query request may include at least one of the following: PLMN ID (such as the PLMN ID of the roaming location), SUPI.

Step 25: The H-NRF network element triggers a query to the V-NRF network element.

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

Step 26: The V-NRF network element finds the V-NEF network element and sends the IP address, FQDN, etc. of the V-NEF network element to the H-NRF network element.

The signaling is: Nnrf_NFDiscovery_Response.

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

Step 27: The H-NRF network element sends the found IP address, FQDN, etc. 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 EDI from the V-UDR network element.

The signaling is: Nnef_EASDeployment_Subscribe Request or Nnef_EASDeployment_Get Request.

The parameters in the signaling may include at least one of the following: PLMN ID (such as the roaming PLMN ID or the home PLMN ID), DNN, S-NSSAI, etc. For example, in this step, H-SMF can indicate the home PLMN ID, go to V-NEF, and request to obtain the roaming EDI stored in V-UDR.

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

The signaling is: Nnef_EASDeployment_Subscribe Response or Nnef_EASDeployment_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 where the H-SMF is located is not qualified to obtain EDI from the V-UDR, then the V-NEF rejects the H-SMF's request to obtain EDI.

Steps 30 and 32: If the verification passes, the V-NEF network element restores EDI from the V-UDR network element.

Step 33. The V-NEF network element sends EDI to the H-SMF network element.

The signaling is: Nnef_EASDeployment_Notify.

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

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

Step 301: The first target network element receives the first target notification message sent by the fourth network element.

In this embodiment of the present application, the above-mentioned first target notification message is used to notify the changed AF route impact request information in the fourth network element.

Optionally, in this 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 the embodiment of this application, the above AF traffic influence request information includes at least one of the following: traffic description information, identification of the terminal whose traffic will be affected, traffic routing information of the target interface, and data Network access identification, PLMN identification.

It should be noted that the above traffic description information (Traffic Description) defines the target traffic to be affected (represented by a combination of DNN and optional S-NSSAI), as well as application identifiers or traffic filtering information. The purpose of AF route impact request information is to affect the current route, so first you need to give which traffic is to be affected, and the traffic description is used to tell 5GC to identify the target traffic.

The identification of the terminal (Target UE Identifier(s)) that the above traffic will be affected refers to the traffic of which terminals will be affected.

Optionally, in this embodiment of the present application, the target interface may be an N6 interface. Traffic routing information of the N6 interface (N6Traffic Routing requirements): Servers are deployed in DN, and UPF and DN are connected through the N6 interface.

It should be noted that the above-mentioned Data Network Access Identifier (Data Network Access Identifier): the user plane identifier of one or more data networks (Data Network, DN) where the application is located.

Optionally, in this embodiment of the present application, the above-mentioned 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 this embodiment of the present application, the above-mentioned second target notification message includes updated policy information, and the policy information is used for the second target network element to perform traffic routing reconfiguration.

Optionally, in this 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 a V-SMF network element, or other network elements. Yuan.

Optionally, in an implementation manner of the embodiment of the present application, the above step 302 may be specifically implemented through the following step 302a.

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

In this embodiment of the present application, the above-mentioned first notification message is used to notify that the current HR session is affected by the AF request; wherein, the first notification message is used for the first network element to perform traffic routing reconfiguration and to send the first notification message to the fifth network element. Two notification messages, the second notification message is used to notify that the PDU session in the roaming location needs to be changed, and the second notification message is used for the fifth network element to perform traffic routing reconfiguration.

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

Optionally, in this implementation, the first target network element may be an H-PCF network element.

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

Step 302b: The first target network element sends the first notification message to the first network element.

In the embodiment of the present application, the above-mentioned 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 routing reconfiguration.

Step 302c: The first target network element sends the second notification message to the fifth network element.

In this embodiment of the present application, the above-mentioned second notification message is used to notify that the PDU session in the roaming location needs to be changed, and the second notification message is used for the fifth network element to perform traffic routing reconfiguration.

Optionally, in another implementation manner of the embodiment of the present application, the above step 301 can be specifically implemented through the following step 301a, and the above step 302 can be specifically implemented through the following steps 302d and 302e.

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

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

Step 302d: The first target network element sends the first notification message to the first network element.

Step 302e: The first target network element sends the second notification message to the fifth network element.

Optionally, in another implementation manner of the embodiment of the present application, the above step 302 can be specifically implemented through the following step 302f.

Step 302f: The first target network element sends the first notification message to the fifth network element.

In the embodiment of this application, the above-mentioned first notification message is used to notify that the current HR session is affected by the AF request; wherein, the first notification message is used for the fifth network element to perform traffic routing reconfiguration and send the first network element to the first notification message. Two notification messages. The second notification message is used to notify that the PDU session in the roaming location needs to be changed. The second notification message is used for the fifth network element to perform traffic routing reconfiguration when the first network element agrees to perform the PDU session change.

Optionally, in this 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 this embodiment of the present application, the above-mentioned 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. of.

Optionally, in an implementation manner of the embodiment of the present application, the above step 303 can be specifically implemented through the following steps 303a and 303b.

Step 303a: The second target network element receives the first notification message sent by the first target network element through the first 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.

Optionally, in another implementation manner of the embodiment of the present application, the above step 303 can be specifically implemented through the following steps 303c and 303d.

Step 303c: The second target network element receives the first notification message sent by the first target network element through the first 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 yet another implementation manner of the embodiment of the present application, the above-mentioned 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 implemented through the following steps 303e and 303f.

Step 303e: The second target network element receives the first notification message sent by the first target network element through the first 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.

Optionally, in another implementation manner of the embodiment of the present application, the above step 303 can be specifically implemented through the following steps 303g and 303h.

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 this embodiment of the present application, the above-mentioned 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 perform traffic routing reconfiguration.

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 above-mentioned second notification message is used to notify that the PDU session in the roaming location needs to be changed, and the second notification message is used for the fifth network element to perform traffic rerouting when the first network element agrees to perform the PDU session change. configuration.

Optionally, in this embodiment of the present application, the above-mentioned second notification message includes at least one of the following: data network access identifier, traffic routing information of the target interface, affected user plane function identifier, affected PDU session identifier, The identity of the affected terminal and the PLMN identity.

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

Reselect or change user interface;

Establish a PDU session to the visited EAS;

Instruct the user plane to replace the source and destination EAS address accessed by the terminal with the destination EAS address, and the destination EAS address is carried by the first target notification message.

Embodiments of the present application provide a route reconfiguration method. The first target network element can receive the first target notification message sent by the fourth network element to notify the fourth network element of the changed AF route impact request information, and then the third network element can receive the first target notification message sent by the fourth network element. A target network element can send updated policy information to the second target network element based on the AF route impact request information, so that the second target network element can perform traffic routing reconfiguration, thereby applying the AF request route impact to the HR session. middle.

The route reconfiguration method provided by the embodiments of the present application will be described below through specific implementation modes (ie, implementation mode two to implementation mode five).

Implementation Mode 2: The V-UDR network element notifies the H-PCF network element

As shown in Figure 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 process.

The AF network element provides traffic influence information to the V-UDR network element. Traffic routing affects the content of information that is state of the art.

Step 46: The V-UDR network element sends a notification message to the H-PCF network element to notify that the AF route impact request information stored in the V-UDR network element has changed, and sends the changed information to H-PCF.

The signaling is: Nudr_DN_Notify.

In the embodiment of this application, since the V-PCF network element does not play any role in the HR session (the V-PCF network element here is, to be precise, the V-SM-PCF network element, session management PCF), so the V- The UDR network element needs to notify the H-PCF network element that the information stored in the V-UDR network element changes. Here is the AF traffic influence request information stored in the V-UDR network element.

The content of the AF routing impact request information is as follows:

Traffic Description: Defines the target traffic to be affected (represented by a combination of DNN and optional S-NSSAI), as well as application identifiers or traffic filtering information. The purpose of the AF request is to affect the current route, so first it needs to be given which traffic is to be affected, and the traffic description is used to tell 5GC to identify the target traffic;

Identifier of the terminal whose traffic will be affected (Target UE Identifier(s)): Target terminal. Traffic to the target endpoint will be affected;

Traffic routing information of N6 interface (N6Traffic Routing requirements): Traffic routing information of N6 interface. The servers are all in the DN Deployment, and UPF and DN are connected through the N6 interface;

Data Network Access Identifier: The user plane identifier of one or more DNs where the application is located;

PLMN logo. The PLMN identifier is used to indicate which PLMN the traffic affects routing information and is effective under.

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

Steps 47-48: The H-PCF network element notifies the H-SMF network element that the current HR session may be affected by the AF request.

The signaling used in step 47 is: Npcf_SMPolicyControl_UpdateNotify.

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

For example, the PCC policy reflects that AF request affects traffic routing and has the following content:

Data Network Access Identifier;

Per DNAI: N6 traffic routing information (N6 traffic routing information): N6 traffic routing information with each DNAI as the granularity.

There can be other content, but the above content is the most important, because the AF we mentioned affects routing, which is ultimately reflected in the N6 traffic routing information. This information determines which DN the traffic on the terminal will eventually be routed to. , which application server.

Step 48 is optional: the traffic routing rules of the home part may be changed or the UPF may be reselected.

Step 48 may not happen, but steps 49-50 will definitely happen.

Step 49: The H-SMF network element notifies the V-SMF network element if the AF request affects user plane reselection or routing rule changes in the roaming location.

This signaling is used to notify the roaming location that the PDU session needs to be changed.

Signaling: Nsmf_PDUSession_Update. Through this signaling, PCC rules are sent to the roaming V-SMF, and then V-SMF performs relevant route reconfiguration according to the policy.

Parameters: PCC rules affected by AF request.

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

Data Network Access Identifier;

Per DNAI: N6 traffic routing information (N6 traffic routing information);

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

Affected PDU session ID: Which PDU session ID corresponds to the session for which the routing information should be changed;

UEID.

Step 50. After the V-SMF network element receives the update, the V-SMF network element needs to modify the PDU session in the roaming location, for example:

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

Perform EAS IP address replacement. According to the sent destination server IP address (target EAS IP address), indicate the roaming UPF (such as V-PSA), and generate a FAR; use the FAR to forward the data packet originally used by the terminal to access the roaming EAS 1 to EAS 2. FAR: Forwarding action rule, the configuration on the original UPF, that is, the data packet sent to EAS 1, will be forwarded to the new EAS, such as EAS 2, after using this FAR.

It can be understood that in the second embodiment, the V-UDR network element can send a notification message to the H-PCF network element to notify the V-UDR network element of the changed AF route impact request information, and the H-PCF network element subscribes to the V - The change of AF routing in the UDR network element affects the request information; the H-PCF network element can send a notification message to the H-SMF network element to notify the terminal that the current HR session will be affected by the AF request. The H-SMF network element Perform traffic routing reconfiguration; the H-SMF network element sends a notification message to the V-SMF network element to notify that the PDU session in the roaming location needs to be changed. The V-SMF network element modifies the PDU session in the roaming location to implement traffic routing reconfiguration. .

Implementation Mode 3: The H-PCF network element notifies the V-SMF network element

As shown in Figure 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-mentioned second embodiment.

Step 59: The H-PCF network element notifies the V-SMF network element if the AF request affects user plane reselection or routing rule changes in the roaming location.

Signaling: Npcf_SMPolicyControl_UpdateNotify

Parameters: PCC rules affected by AF request.

In this method, the updated PCC rules are not sent to H-SMF, but directly to 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 can send a notification message to the H-PCF network element to notify the V-UDR network element of the changed AF route impact request information, and the H-PCF network element subscribes to the V - The change of AF routing in the UDR network element affects the request information; the H-PCF network element sends a notification message to the H-SMF network element to notify the terminal that the current HR session will be affected by the AF request, and the H-SMF network element performs Data route reconfiguration: The H-PCF network element sends a notification message to the V-SMF network element to notify that the PDU session in the roaming location needs to be changed. The V-SMF network element modifies the PDU session in the roaming location to implement traffic routing reconfiguration.

Implementation Mode 4: The V-PSA network element notifies the H-PCF network element

As shown in Figure 7, the route reconfiguration method provided by 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-mentioned second embodiment.

Step 66: The V-UDR network element notifies the V-PCF network element.

Step 67: The V-PCF network element notifies the H-PCF network element.

V-PCF network elements and H-PCF network elements have interfaces for interoperability. Therefore, use the V-PCF network element to forward the notification message in step 66 to the H-PCF network element.

The signaling in step 67 is used to transmit the changes in the information stored in the V-UDR network element. Here is the information about the changes in the AF traffic influence request information stored in the V-UDR network element (that is, the changed information in the V-UDR network element) The application function AF routing affects the request information).

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

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

It can be understood that in the fourth embodiment, the V-UDR network element can send a notification message to the V-PCF network element to notify the V-UDR network element of the changed AF route impact request information, and the V-PCF network element subscribes to the V -The AF routing in the UDR network element affects the change of request information; 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 to notify the terminal of the current The HR session will be affected by the AF request. The H-SMF network element performs data routing reconfiguration; the H-PCF network element sends a notification message to the V-SMF network element to notify that the PDU session in the roaming location needs to be changed and V-SMF is modified. PDU sessions in roaming locations to implement traffic routing reconfiguration.

Implementation mode five: V-SMF network element notifies H-SMF network element

As shown in Figure 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.

When the V-SMF network element modifies the roaming user plane according to the AF request, it needs to update the PDU session to the H-SMF network element.

Step 79: Since the V-SMF network element has received the updated PCC rule, the V-SMF network element requests to change the PDU session.

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

Data Network Access Identifier;

Per DNAI: N6 traffic routing information (N6 traffic routing information);

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

UEID.

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 changes 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 can send a notification message to the V-PCF network element to notify the V-UDR network element of the changed AF route impact request information, and the V-PCF network element subscribes to the V -The AF routing in the UDR network element affects the change of the request information; the V-PCF network element sends a notification message to the V-SMF network element to notify the terminal that the current HR session will be affected by the AF request, and V-SMF performs data routing Reconfiguration: The V-SMF network element sends a notification message to the H-SMF network element to notify that the PDU session in the roaming location needs to be changed, and the V-SMF network element modifies the PDU session in the roaming location.

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

The embodiment of this application also provides another route reconfiguration method, including:

The fifth network element receives the second information sent by the first network element, and the second information is used for the fifth network element to perform traffic routing reconfiguration; wherein the second information is determined based on the first information; The first information is used to influence SMF routing decisions for User Plane traffic of PDU Sessions, or to influence UPF selection or reselection, Or, used to allow routing of user traffic to a local access (identified by a DNAI) to a Data Network through a local portal.

The second information is information sent by the home operator HPLMN (such as VPLMN SMF) to the roaming operator VPLMN (such as VPLMN SMF), or the second information is the communication between the home operator HPLMN (such as HPLMN SMF) and the roaming operator Some information that the operator VPLMN (such as VPLMN SMF) needs to exchange. The second information includes at least one of the following:

QoS requirements associated with a PDU Session;

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

QoS Rule(s);

QoS flow level QoS parameters (QoS Flow level QoS parameters);

QoS flow identifier (QFI(s));

QoS profile(s);

Session aggregate bit rate (Session-AMBR (Aggregate Bit Rates));

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

In one implementation, the fifth network element is a communication device at the visited place, which may be a device with a session management function at the visited place (for example, V-SMF), or may be a device with a unified data warehousing function at the visited place (for example, V-SMF). V-UDR), or other core network equipment at the visited location.

In one implementation, the first network element is a home communication device, which may be a home device with a session management function (for example, H-SMF), or may be a home device with a policy control function (such as H-SMF). -PCF), or other core network equipment at home.

In one implementation, the method further includes: the fifth network element performing traffic routing reconfiguration.

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

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

The fifth network element reconfigures the routing information of the UPF;

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

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

The fifth network element configures the user plane UPF and requests the user plane to buffer the uplink traffic to be sent to the target DNAI (buffering of uplink traffic to the target DNAI);

The fifth network element triggers the N4 Session Modification procedure (N4Session Modification procedure) to the roaming UPF;

The fifth network element may apply a VPLMN policy related to the SLA negotiated by the HPLMN;

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

In one implementation, the fifth network element performs user plane reconfiguration by triggering the N4 Session Modification procedure (N4Session Modification procedure) or triggering the N4 Session Establishment procedure (N4Session Establishment procedure) to the UPF.

In one implementation, the fifth network element requests the user plane to cache the uplink traffic to be sent to the target DNAI by triggering the N4 Session Modification procedure (N4Session Modification procedure) or triggering the N4 Session Establishment procedure (N4Session Establishment procedure) to the UPF. Request routing information to be reconfigured.

In one implementation, the fifth network element carries the first information or the second information to the UPF to request routing by triggering the N4 Session Modification procedure (N4Session Modification procedure) or triggering the N4 Session Establishment procedure (N4Session Establishment procedure). Reconfigure.

In one implementation, the fifth network element receives the second information through Nsmf_PDUSession_Create response or Nsmf_PDUSession_Update response.

In one implementation, the first information includes traffic influence information.

In one implementation, the first information includes at least one of the following:

Target DNAI (target DNAI);

First indication information, the first indication information is used to instruct caching of uplink traffic to be sent to the target DNAI.

It can be understood that the first indication information is used to instruct the user plane of the roaming location to cache the uplink traffic to be sent to the target DNAI.

In one implementation, the second information includes updated policy information.

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

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

TargetDNAI;

In one implementation, the method further includes: the fifth network element sending the first information to the first network element. Optionally, the fifth network element sends the first information to the first network element through Nsmf_PDUSession_Create request or Nsmf_PDUSession_Update request.

In one implementation, after the first network element receives 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 to the first target network element. , or policy update request.

Optionally, the policy update request can be Npcf_SMPolicyControl_Update request. The first information is included in the policy update request. Optionally, the policy creation request can be Npcf_SMPolicyControl_Create request. The first information is included in the policy creation request.

In one implementation, after receiving the first information sent by the fifth network element, the first network element may also perform at least one of the following:

Establish or modify session policy association (SM policy association);

Establish or modify session policy association (SM policy association) to the first target network element;

Request to obtain PCC rules, or request to obtain 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 implementation, the second information is determined by the first target network element based on the first information. The first target network element may be a home network device, may be a home device with a policy control function (for example, H-PCF), or may be another home core network device. It can be understood that after receiving the first information sent by the fifth network element, the first target network element determines the second information based on the first information, and sends the second information to the first network element.

In an implementation manner, the first target network element may send the second information to the first network element through a policy update response. Among them, the policy update response can be Npcf_SMPolicyControl_Update response.

In an implementation manner, the first target network element may send the second information to the first network element through a policy creation response. Among them, policy update creation can be Npcf_SMPolicyControl_Create response.

In an implementation manner, 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 implementation, the method further includes: the fifth network element receiving the first information sent by the third network element.

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

Optionally, the third notification may be Nnef_TrafficInfluence_Notify, or may be other communication messages.

In one implementation, the third network element is a communication device at the visited place, which may be a device with a network opening function at the visited place (for example, V-NEF), or may be a device with a unified warehousing function at the visited place (for example, V-NEF). V-UDR), or other core network equipment at the visited location.

In one implementation, the method further includes: the fifth network element sending a first subscription request to the third network element, where the first subscription request is used to subscribe to at least one of the following:

Subscribe to the first information (for example, update of the first information, deletion of the first information, or addition of the first information);

Subscribe to the request for traffic influence; it can be understood that when the third network element receives the traffic influence request, the third network element can notify the fifth network element.

Optionally, the first subscription request may be a Nnef_TrafficInfluence_Subscribe request, 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 implementation, when the first subscription request includes the first identifier, it indicates 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 indicates that the fifth network element requests to subscribe 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 implementation, when the first condition is met, the third network element sends the first information or the third notification to the fifth network element, wherein the first condition includes at least one of the following:

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

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

The third network element receives a traffic impact request (request for traffic influence or AF request).

For the convenience of understanding, the following takes 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 for detailed explanation.

The route reconfiguration method shown in Figure 21.

Step 0: V-SMF sends the first subscription request to V-NEF. The first subscription request is used to subscribe to at least one of the following:

Subscribe to the first information (for example, update of the first information, deletion of the first information, or addition of the first information).

Subscribing to the request for traffic influence, that is, when the third network element receives the traffic influence request, the third network element can notify the fifth network element.

The first subscription request may be a Nnef_TrafficInfluence_Subscribe request, and 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 indicates 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, it indicates that the fifth network element only requests to subscribe to the first information provided by the AF corresponding to the AF ID.

Step 1 - Step 3: Existing process. AF triggers AF request, which is used to request traffic impact. The traffic impact information is stored in the roaming UDR through the third network element (step 3).

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

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

For example, the fifth network element sends the first information to the first network element through Nsmf_PDUSession_Create request or Nsmf_PDUSession_Update request.

The fifth network element also sends 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 receiving the first information, H-SMF determines the policy for updating the PDU session.

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

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

The session policy association establishment signaling may be: Npcf_SMPolicyControl_Create request;

The second information includes: PCC rules or policy information.

The second information may also include:

QoS requirements associated with a PDU Session;

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

QoS Rule(s);

QoS flow level QoS parameters (QoS Flow level QoS parameters);

QoS flow identifier (QFI(s));

QoS profile(s);

Session aggregate bit rate (Session-AMBR (Aggregate Bit Rates));

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

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

The response includes at least one of the following:

The session policy association modification response signaling may be: Npcf_SMPolicyControl_Update response;

The session policy association establishment signaling may be: Npcf_SMPolicyControl_Create response;

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

The first network element sends the second information to the V-SMF through Nsmf_PDUSession_Create response or Nsmf_PDUSession_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:

Reconfigure the user plane of the PDU session;

Reconfigure UPF routing information;

Update UPF target DNAI;

Determine the target DNAI and add, replace or delete UPF in the data path;

Configure the user plane UPF and request the user plane to cache the uplink traffic to be sent to the target DNAI.

The user plane is a roaming user plane.

The embodiment of the present application also provides another route reconfiguration method, including: the third network element sends the first information to the seventh network element.

In one implementation, the seventh network element is a home communication device, which may be a home device with network opening function (for example, H-NEF), or may be a home device with unified warehousing function (for example, H-NEF). UDR), or other core network equipment at 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 can directly send the first information to the seventh network element through the service interface to facilitate the home location. The network performs policy updates.

In this embodiment of the present application, the first network element may send the second information or the updated policy information to the fifth network element, so that the fifth network element can perform routing reconfiguration, where the second information is determined based on the first information. of. Optionally, the first network element sends the second information or updated policy information to the fifth network element through Nsmf_PDUSession_Create response or Nsmf_PDUSession_Update response.

Target DNAI (target DNAI);

It can be understood that the first indication information is used to instruct the roaming user plane to cache the uplink traffic to be sent to the target DNAI.

TargetDNAI;

In one implementation, 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 implementation, the eighth network element is a home network device, which may be a home device with a unified warehousing function (for example, H-UDR).

In one implementation, when the second condition is met, the eighth network element sends the first information to the first target network element, wherein the second condition includes at least one of the following:

The first target network element subscribes to the first information (for example, the update of the first information, the deletion of the first information, or the addition of the first information);

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

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

In an implementation manner, the eighth network element sends the first information to the first target network element through the fourth notification. Among them, the fourth notification can be Nudr_DM_Notify.

In one implementation, the first target network element may be a home network device, may be a home device with a policy control function (for example, H-PCF), or may be another home core network device.

In one implementation, after receiving the first information, the first target network element determines the second information based on the first information, and sends the second information to the first network element.

For the convenience of understanding, the following takes 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 for explanation:

A routing reconfiguration method is shown in Figure 22.

Step 1-2: In the existing technology, the roaming AF sends the first information to the V-NEF.

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

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

Step 4 is to provide the first information in the roaming location, and the first information is sent to the home PLMN through the H-NEF. The first information is used to generate second information. The H-PCF receives the first information from the H-UDR through step 6, and generates the second information.

Step 5: H-UDR stores the first information.

Step 6: H-UDR sends the first information to H-PCF. H-PCF generates second information based on the first information.

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

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

Embodiments of this application also provide a route reconfiguration method, including:

The fifth network element sends third information to the ninth network element, where the third information is used to instruct or request the home operator (HPLMN) to authenticate or authorize the visited operator (VPLMN) to perform the first An operation, the first operation includes at least one of the following:

Use the first information directly;

Execute or complete the AF traffic influence procedure;

Use AF traffic influence request information.

or,

The fifth network element obtains fourth information. The fourth information is used to indicate that the visiting operator can perform a first operation. The first operation includes at least one of the following:

Use the first information directly;

Execute or complete the AF traffic influence procedure;

Use AF traffic influence request information.

It should be noted that the fourth information may be sent to the fifth network element by the home network device, or may be agreed upon in the agreement.

In one implementation, "the operator of the visited location can perform the first operation" can be understood as "the operator of the visited location has the authority to perform the first operation."

Target DNAI (target DNAI);

In one implementation, the ninth network element is a home communication device, which may be a home device with a session management function (for example, H-SMF), or may be a home device with a unified data management function (for example, H-SMF) UDM), or other core network equipment at home.

In one implementation, "directly using the first information" can be understood as meaning that there is no need to send the first information to the home operator or the home operator to generate corresponding PCC rules, or it can be used directly without authorization from the home operator. use.

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

Directly use the first information to reconfigure the user plane of the PDU session;

Directly use the first information to reconfigure the UPF routing information;

Directly use the first information to update the target DNAI of UPF;

Directly use the first information to determine the target DNAI and add, replace or delete UPF in the data path;

Directly use the first information to configure the user plane UPF, and request the user plane to cache the uplink traffic to be sent to the target DNAI, where the user plane is the visited user plane.

In one implementation, the AF traffic impact process includes: V-AF (or AF) provides the first information to the third network element (for example, V-NEF); the third network element sends the first information to the fifth network element (for example, V-SMF), the fifth network element directly uses the first information to complete at least one of the following:

Reconfigure the user plane of the PDU session;

Reconfigure UPF routing information;

Update UPF target DNAI;

Determine the target DNAI and add, replace or delete UPF in the data path;

Configure the user plane UPF and request the user plane to cache the uplink traffic to be sent to the target DNAI, where the user plane is the visited user plane.

In one implementation, the third information may be a message used to request the home operator (HPLMN) to authenticate or authorize the visited operator (VPLMN) to perform the first operation. For example, the third information may be home routing session offload authorization request (HR-SBO authorization request), AF traffic influence request in VPLMN authorization request (AF traffic influence request in VPLMN authorization request), home routing session offload authorization indication (HR- SBO authorization indication), or AF traffic influence in VPLMN authorization indication, home routing session offload allowed indication (HR-SBO allowed indication), AF traffic influence in VPLMN in VPLMN allowed indication), etc., or it can be another name.

In one implementation, the third information may be instruction information indicating that the home operator (HPLMN) authenticates or authorizes the visited operator (VPLMN) to perform the first operation. Optionally, the third information may be indication information carried in the Nsmf_PDUSession_Create request or Nsmf_PDUSession_Update request message.

In an implementation manner, after the ninth network element receives the third information, the ninth network element first restores the contract from UDR or UDM. information. Then, the ninth network element verifies, authorizes or approves the third information based on the contract information. When the third information is verified, authorized or approved, it means that the home operator (HPLMN) has verified, authorized or approved that the visited operator (VPLMN) can perform the first operation.

In one implementation, the method further includes: the fifth network element receiving the verification result or authorization result sent by the ninth network element. The verification result or the authorization result includes at least one of the following:

Pass the verification, authorize or approve the roaming operator to directly use the first information;

Pass the verification, authorize or approve the roaming operator to perform or complete the AF traffic influence procedure;

Pass the verification, authorize or approve the roaming operator to use AF traffic influence request information;

The verification fails, and the roaming operator is not authorized or approved to directly use the first information;

The verification fails, the roaming operator is not authorized or approved to perform or complete the AF traffic influence procedure;

The verification fails, the roaming operator is not authorized or approved to use AF traffic influence request information;

In one implementation, when the verification result or authorization result is "verification passed, authorized or approved", the fifth network element executes or completes the AF traffic influence procedure (AF traffic influence procedure) or the fifth network element directly uses The first information, or the fifth network element uses AF traffic influence request information (AF traffic influence request information).

The fourth information includes at least one of the following:

Home routing session offload allowed indication (HR-SBO allowed indication), AF traffic impact in VPMN allowed indication (AF traffic influence in VPLMN allowed indication).

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

Network elements with mobility management functions (such as AMF), network elements with unified data management functions (such as UDM), network elements with unified data warehousing functions (such as UDR), ninth network elements, or other core network elements One or more of them (the core network elements include visiting core network elements or home core network elements).

The fourth information obtained by the fifth network element includes at least one of the following:

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

The fifth network element obtains the fourth information from a network element with access management function (such as AMF) through Nsmf_PDUSession_CreateSMContext Request, where the fourth information is that the network element with access management function obtains the fourth information from a network element with unified data management function. Obtained from the functional network element (such as UDM).

In an implementation manner, 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 the ninth network element. (such as H-SMF), or the fifth network element directly performs at least one of the first operations.

In an implementation manner, 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 sends the third information without sending the first information, which can save the message capacity carried in the signaling.

In another implementation manner, in addition to sending the third information to the ninth network element, the fifth network element can also send the first information to the ninth network element, so that the verification result or authorization result of the ninth network element is "verification". "Not passed, not authorized, not approved", the ninth network element can use the first information to obtain the second information, and send the second information to the fifth network element. Among them, the method for the ninth network element to use the first information to obtain the second information and send the second information to the fifth network element can refer to the operation of the first network element in the corresponding embodiment of Figure 21, which will not be described in detail in this embodiment. .

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 implementation, the fifth network element obtains the fourth information, either 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. after.

For ease of understanding, the following takes the fifth network element as V-SMF, the third network element as V-NEF, and the ninth network element as H-SMF as examples for detailed explanation. If the description of this example is not complete, reference may also be made to the above embodiment.

The route reconfiguration method shown in Figure 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: V-SMF sends the third information to H-SMF.

For example, V-SMF sends the third information to H-SMF through Nsmf_PDUSession_Create request or Nsmf_PDUSession_Update request.

The third information is used to instruct or request the home operator (HPLMN) to authenticate or authorize the visited operator (VPLMN) to perform the first operation, where the first operation includes at least one of the following:

Use the first information directly;

Execute or complete the AF traffic influence procedure;

Use AF traffic influence request information.

In one implementation, the V-SMF may not send the first information to the H-SMF, but only send the third information. The third information is used to indicate the request or indicate the home operator (H-PLMN). Authentication or authorization allows the roaming operator to use the first information (i.e., allowing the roaming operator to directly use AF traffic influence information, allowing direct use of the first information, or allowing execution or completion of the AF traffic influence process) at least one of them).

In an implementation manner, when the V-SMF carries the third information, it does not carry the first information or does not send the first information to the H-SMF.

Step 6: After receiving the third information, H-SMF performs the verification or authorization process. The verification or authorization process includes: H-SMF recovers the contract information from UDM or UDR, and verifies, authorizes or approves the third information based on the contract information.

H-SMF restores contract information through at least one of the following:

Nudm_SDM_Get

Nudm_SDM_Subscribe

Nudm_UECM_Get and so on.

The type of the subscription information may be SM subscription data, and its content may be as follows:

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

Step 8. When the verification result or authorization result is "verification passed, authorized or approved", the V-SMF performs the first operation, and the first operation includes at least one of the following:

Use the first information directly;

Execute or complete the AF traffic influence procedure;

Use AF traffic influence request information.

An embodiment of the present application provides a method for obtaining ECS address configuration information. Figure 9 shows a flow chart of a method of obtaining ECS address configuration information provided by an embodiment of the present application. As shown in Figure 9, the method for obtaining ECS address configuration information provided by the embodiment of the present application may include the following steps 401 to 404.

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

Optionally, in this embodiment of the present application, the first network element can send the ECS Address Configuration Information (ECS Address Configuration Information) to the fifth network element through signaling such as Nsmf_PDUSession_Create Response or Nsmf_PDUSession_Update Response.

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

In this embodiment of the present application, the above ECS address configuration information includes a PLMN identifier. The PLMN identification is used to indicate which operator the ECS address applies to.

Optionally, in the embodiment of this application, the structure of the above ECS address configuration information is as shown in the following Table 3:

Form 3

Optionally, in the embodiment of this application, the above-mentioned PLMN ID can also be placed outside the ECS address configuration information, as shown in the following Table 4:

Form 4

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

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

The AF network element first sends the ECS address configuration information, PLMN ID, etc. to the NEF network element through Nnef_ParameterProvision_Update or Nnef_ParameterProvision_Create; the PLMN ID is used to indicate the operator to which the ECS address configuration information belongs; it can also be included in the ECS address configuration information. , carrying PLMN ID;

Then the NEF network element sends the ECS address configuration information, PLMN ID, etc. to the UDM network element through Nudm_ParameterProvision_Update or Nudm_ParameterProvision_Create; the PLMN ID is used to indicate the operator to which the ECS address configuration information belongs; it can also be included in the ECS address configuration information. , carries the PLMN ID.

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

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

In the embodiment of this application, the above-mentioned ECS address configuration information is used for the terminal to establish a protocol data unit PDU session in the roaming location with the ECS.

Step 404: The terminal receives the ECS address configuration information sent by the fifth network element.

Optionally, in this embodiment of the present application, the above 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 this application, the ECS address configuration information can be stored in the UDM network element or UDR network element in the form of a PLMN identifier; ECS: edge configuration server edge configuration server.

For example, in UDR, as shown in Table 5 below, save the ECS address configuration information.

Form 5

That is to say, the ECS address can be saved in the form of PLMN ID in the UDR contract data.

Data key or data sub key can have PLMN ID.

In UDM, save the ECS address configuration information as shown in Table 6 below.

Form 6

Since the ECS configuration information stored in UDM is also stored in the session management subscription data, you can also consider adding a PLMN ID to distinguish different ECS addresses.

The embodiment of this application provides a method for obtaining ECS address configuration information. 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. Used for the terminal to establish a roaming PDU session with the ECS.

It should be noted that the embodiment of the present application provides a method for obtaining ECS address configuration information. The execution subject may also be a device for obtaining ECS address configuration information, or the device for obtaining ECS address configuration information may be used to execute the ECS address configuration information. Control module for obtaining configuration information.

An embodiment of the present application provides a DNS processing method. Figure 10 shows a flow chart of a DNS processing method provided by an embodiment of the present application. As shown in Figure 10, the DNS processing method provided by the embodiment of the present application may include the following step 501.

Step 501: When the terminal enters the roaming state, the terminal performs at least one of the following:

Clear DNS cache;

Send a DNS requery request, which is used to request EAS reselection in the roaming location.

In the embodiment of the present application, after the terminal enters the roaming area from the home area, the connected edge server may become a sub-optimal server. Therefore, the terminal can clear the DNS cache and/or re-initiate DNS query to re-find the EAS.

It should be noted that roaming means that the terminal is not in H-PLMN but in V-PLMN.

Optionally, in this embodiment of the present application, after the terminal enters the roaming state, the application on the terminal can trigger the terminal to perform a DNS query. At this time, the application on the terminal can sense that the EAS at home is not the optimal EAS, so it can initiate DNS requery request to request EAS reselection in the roaming location.

Optionally, in this embodiment of the present application, the terminal clearing the DNS cache may be implemented through the following step 501a.

Step 501a: When the terminal receives the instruction information, the terminal clears the DNS cache.

In this embodiment of the present application, the above instruction information is used to instruct the terminal to clear the DNS cache.

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

Optionally, in this embodiment of the present application, the terminal enters the roaming state when the terminal meets target conditions, and the target conditions include at least one of the following:

The terminal completes registration with V-PLMN;

The terminal is configured with new DNS address information (i.e., new DNS server IP address) in the roaming area; for example, the new DNS server IP address can be the H-EASDF IP address, or the local DNS server IP address in the roaming area;

The terminal completes establishing a local breakout (LBO) session or HR session in the roaming location.

The embodiment of the present application provides a DNS processing method. After the terminal enters the roaming area, it can clear the DNS cache so that the terminal can find the EAS as soon as possible; and/or the terminal can initiate a DNS re-query request to reselect the optimal one in the roaming area. EAS; thereby achieving the establishment of PDU sessions in roaming locations.

It should be noted that, for the DNS processing method provided by the embodiment of the present application, the execution subject 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 various embodiments of the present application can be common. In order to avoid redundant descriptions, descriptions in some embodiments are not repeated, and the content in various embodiments can be combined.

Figure 11 shows a possible structural diagram of the EDI acquisition device involved in the embodiment of the present application. The EDI acquisition device is applied to the first network element. As shown in Figure 11, the EDI acquisition device 90 may include: a sending module 91 and a receiving module 92.

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

The embodiment of the present application provides an EDI acquisition device. The EDI acquisition device can query the third network element by sending a query request to the second network element. After finding the third network element, it requests the third network element to obtain the EDI of the roaming operator from the fourth network element to obtain the EDI, thereby generating DNS message processing rules based on the EDI, thereby realizing the PDU of the roaming area. Session establishment.

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

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

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

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

In a possible implementation, the above-mentioned sending module 91 is also used to send a first request to the UDM network element. The first request is used to request to obtain the subscription information of the terminal. The terminal establishes a PDU session or updates for needs in the roaming area. For the terminal of the PDU session, the subscription information is used to indicate whether the terminal is authorized to use the roaming edge computing service. The first request includes a PLMN identity. The above-mentioned receiving module 92 is also used to receive the first response sent by the UDM network element, where the first response includes the terminal's subscription information. The above-mentioned 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 edge computing service.

The EDI acquisition device provided by the embodiment of the present application can implement each process implemented by the first network element in the above method embodiment, and achieve the same technical effect. To avoid duplication, the details will not be described here.

Figure 12 shows a possible structural diagram of the EDI acquisition device involved in the embodiment of the present application. The EDI acquisition device is applied to the second network element. As shown in Figure 12, the EDI acquisition device 100 may include: a receiving module 101 and a sending module 102.

Among them, the receiving module 101 is used to receive a query request sent by the first network element, and the query request is used to request to query the third network element. 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 by the first network element to send a target request to the third network element, and the target request is used to request to obtain the EDI of the roaming operator from the fourth network element.

Embodiments of the present application provide an EDI acquisition device. The EDI acquisition device can receive a query request sent by the first network element to query the third network element, and after finding the third network element, send the third network element to the first network element. The address information of the network element, so that the first network element can request the third network element to obtain the EDI of the roaming operator from the fourth network element to obtain the EDI, thereby generating DNS message processing rules based on the EDI, thereby realizing roaming Establishment of local PDU session.

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

The EDI acquisition device provided by the embodiment of the present application can implement each process implemented by the second network element in the above method embodiment, and achieve the same technical effect. To avoid duplication, the details will not be described here.

Figure 13 shows a possible structural diagram of the EDI acquisition device involved in the embodiment of the present application. The EDI acquisition device is applied to the third network element. As shown in Figure 13, the EDI acquisition device 110 may include: a receiving module 111 and a sending module 112.

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

Embodiments of the present application provide an EDI acquisition device. After the first network element sends a query request to the second network element to find the third network element, the first network element requests the third network element to obtain the information from the fourth network element. To obtain the EDI of the roaming operator, the third network element can send the EDI of the roaming operator to the first network element, so that the first network element can obtain the EDI and generate DNS message processing rules based on the EDI to realize roaming. Establishment of local PDU session.

In a possible implementation, the EDI acquisition device provided by the embodiment of the present application further includes: a verification module. A verification module, 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 to determine whether the first network element is authorized to obtain the EDI from the roaming operator to which it belongs. data. The above-mentioned sending module 112 is specifically used to obtain EDI from the fourth network element and send EDI to the first network element when verifying that the first network element is authorized to obtain data from the roaming operator to which the EDI belongs.

The EDI acquisition device provided by the embodiment of the present application can implement each process implemented by the third network element in the above method embodiment, and achieve the same technical effect. To avoid duplication, the details will not be described here.

Figure 14 shows a possible structural diagram of the route reconfiguration device involved in the embodiment of the present application. The route reconfiguration device is applied to the first target network element. As shown in Figure 14, the route reconfiguration device 120 may include: a receiving module 121 and a sending module 122.

The receiving module 121 is configured to receive the first target notification message sent by the fourth network element. 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 traffic routing reconfiguration by the second target network element.

Embodiments of the present application provide a route reconfiguration device. The route reconfiguration device can receive a first target notification message sent by the fourth network element to notify the fourth network element of the changed AF route impact request information, and then the route reconfiguration The configuration device can send updated policy information to the second target network element according to the AF route impact request information, so that the second target network element can perform traffic routing reconfiguration, thereby applying the AF request route impact to the HR session.

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

In a possible implementation, the above-mentioned sending module 122 is specifically configured to send a first notification message to the first network element. The first notification message is used to notify that the current HR session is affected by the AF request; wherein, the first notification message The message is used for the first network element to reconfigure the traffic route and send the second notification message to the fifth network element. The second notification message is used to notify that the PDU session in the roaming location needs to be changed. The second notification message is used for the fifth network element. Perform traffic routing reconfiguration.

In a possible implementation, the above-mentioned sending module 122 is specifically used to send a first notification message to the first network element. The first notification message is used to notify that the current HR session is affected by the AF request. The first notification message is Perform traffic routing reconfiguration on the first network element; and send a second notification message to the fifth network element. The second notification message is used to notify that the PDU session in the roaming location needs to be changed, and the second notification message is used for the fifth network element to conduct traffic flow. Route reconfiguration.

In a possible implementation manner, the above-mentioned receiving module 121 is specifically configured to receive the first target notification message sent by the fourth network element via the sixth network element. The above-mentioned sending module 122 is specifically used to send a first notification message to the first network element. 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 reroute traffic. configure; and send a second notification message to the fifth network element, the second notification message is used to notify that the PDU session in the roaming location needs to be changed, and the second notification message is used for the fifth network element to perform traffic routing reconfiguration.

In a possible implementation, the above-mentioned sending module 122 is specifically configured to send a first notification message to the fifth network element. The first notification message is used to notify that the current HR session is affected by the AF request; wherein, the first notification message The message is used for the fifth network element to perform traffic routing reconfiguration and send a second notification message to the first network element. The second notification message is used to notify that the PDU session in the roaming location needs to be changed. The second notification message is used for connecting to the first network element. If the fifth network element agrees to perform PDU session changes, the fifth network element performs traffic routing reconfiguration.

In a possible implementation, the above-mentioned second notification message includes at least one of the following: data network access identifier, traffic routing information of the target interface, affected user plane function identifier, affected PDU session identifier, affected The identity of the affected terminal and the PLMN identity.

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

Reselect or change user interface;

Establish a PDU session to the visited EAS;

Instructs the user plane to replace the source and destination EAS address accessed by the terminal with the destination EAS address, and the destination EAS address is carried by the first target notification message.

The route reconfiguration device provided by the embodiments of the present application can implement each process implemented by the first target network element in the above method embodiment, and achieve the same technical effect. To avoid duplication, details will not be described here.

Figure 15 shows a possible structural diagram of the route reconfiguration device involved in the embodiment of the present application. The route reconfiguration device is applied to the second target network element. As shown in Figure 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. The second target notification message includes updated policy information, and the policy information is used for the second target network element to perform traffic routing reconfiguration; wherein , 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. The first target notification message is used to notify the fourth network element of the changed AF route impact request. information.

Embodiments of the present application provide a route reconfiguration device. The route reconfiguration device can receive updated policy information sent by the first target network element based on the changed AF route impact request information in the fourth network element, and perform operations based on the policy information. Traffic routing is reconfigured to apply the AF request routing impact to the HR session to establish the PDU session in the roaming location.

In a possible implementation, the above-mentioned receiving module 131 is specifically configured to receive the first notification message sent by the first target network element through the first network element. The first notification message is used to notify that the current HR session is subject to an AF request. Impact, the first notification message is used for the first network element to reconfigure the traffic route; and the second notification message sent by the first network element is received through the fifth network element, and the second notification message is used to notify that the PDU session in the roaming location needs to be changed. , the second notification message is used for the fifth network element to perform traffic routing reconfiguration.

In a possible implementation, the above-mentioned receiving module 131 is specifically configured to receive the first notification message sent by the first target network element through the first network element. The first notification message is used to notify that the current HR session is subject to an AF request. Impact, the first notification message is used for the first network element to perform traffic routing reconfiguration; and the second notification message sent by the first target network element is received through the fifth network element, and the second notification message is used to notify the PDU session needs of the roaming location Change, the second notification message is used for the fifth network element to perform traffic routing reconfiguration.

In a 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 above-mentioned receiving module 131 is specifically used to receive the first notification message sent by the first target network element through the first network element. 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 notification message. A network element performs traffic routing reconfiguration; and receives a second notification message sent by the first target network element through the fifth network element. The second notification message is used to notify that the PDU session in the roaming location needs to be changed, and the second notification message is used to notify the roaming location that the PDU session needs to be changed. Five network elements perform traffic routing reconfiguration.

In a possible implementation, the above-mentioned receiving module 131 is specifically configured to receive the first notification message sent by the first target network element through the fifth network element. The first notification message is used to notify that the current HR session is subject to an AF request. Impact, the first notification message is used for the fifth network element to perform traffic routing reconfiguration; and the second notification message sent by the fifth network element is received through the first network element, and the second notification message is used to notify that the PDU session in the roaming location needs to be changed. , the second notification message is used for the fifth network element to perform traffic routing reconfiguration when the first network element agrees to perform PDU session change.

The routing reconfiguration device provided by the embodiments of the present application can implement each process implemented by the second target network element in the above method embodiment, and achieve the same technical effect. To avoid duplication, details will not be described here.

Figure 16 shows a possible structural diagram of a device for obtaining ECS address configuration information involved in the embodiment of the present application. The device for obtaining ECS address configuration information is applied to the fifth network element. As shown in Figure 16, the device 140 for obtaining ECS address configuration information may include: a receiving module 141 and a sending module 142.

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

Embodiments of the present application provide a device for obtaining ECS address configuration information. The device for obtaining ECS address configuration information can receive the ECS address configuration information under the HR session sent by the first network element, and then send the ECS address configuration information to the terminal for use. Establish a roaming PDU session between the terminal and the ECS.

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

The device for obtaining 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. To avoid duplication, the details will not be described here.

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

The receiving module 2301 is used to receive the second information sent by the first network element. Wherein, the second information is used for traffic routing reconfiguration by the fifth network element; wherein the second information is determined based on the first information; the first information is used to affect user plane traffic in the PDU session SMF Road Influence SMF routing decisions for User Plane traffic of PDU Sessions, or to influence UPF(re)selection, or to allow user plane traffic to be routed through a local ingress. to a Data Network (allow routing of user traffic to a local access (identified by a DNAI) to a Data Network).

QoS requirements associated with a PDU Session;

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

QoS Rule(s);

QoS flow level QoS parameters (QoS Flow level QoS parameters);

QoS flow identifier (QFI(s));

QoS profile(s);

Session aggregate 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 the visited place, or may be a device at the visited place with a session management function (for example, V-SMF), or may be a device at the visited place with a unified data warehousing function (for example, V-SMF). UDR), can also be installed for other core networks at the visited destination.

The route reconfiguration device 2300 also includes: a reconfiguration module for reconfiguring traffic routes.

The routing reconfiguration by the reconfiguration module includes at least one of the following:

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

The reconfiguration module reconfigures the routing information of the UPF;

The reconfiguration module updates the target DNAI of UPF;

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

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

The reconfiguration module triggers the N4 Session Modification procedure (N4 Session Modification procedure) to the roaming UPF;

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

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

In one implementation, the reconfiguration module performs user plane reconfiguration by triggering the N4 Session Modification procedure (N4 Session Modification procedure) or triggering the N4 Session Establishment procedure (N4 Session Establishment procedure) to the UPF.

In one implementation, the reconfiguration module carries the first information or the second information to the UPF by triggering the N4 Session Modification procedure (N4 Session Modification procedure) or triggering the N4 Session Establishment procedure (N4 Session Establishment procedure), and requests the process to proceed. Route reconfiguration.

In one implementation, the receiving module 2301 receives the second information through Nsmf_PDUSession_Create response or Nsmf_PDUSession_Update response.

Target DNAI (target DNAI);

TargetDNAI;

In one implementation, 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_PDUSession_Create request or Nsmf_PDUSession_Update request.

In one implementation, the second information is determined by the first target network element based on the first information. The first target network element may be a home network device, may be a home device with a policy control function (for example, H-PCF), or may be another home core network device. It can be understood that after receiving the first information sent by the route reconfiguration device 2300, the first target network element determines the second information based on the first information, and sends the second information to the first network element.

In one implementation, the receiving module 2301 is also 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 implementation, the sending module is further configured to send a first subscription request to the third network element, where the first subscription request is used to subscribe to at least one of the following:

Subscribe to the request for traffic influence; it can be understood that when the third network element receives the request for traffic influence, the third network element can notify the fifth network element.

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 implementation, when the first condition is met, the receiving module receives the first information or the third notification sent by the third network element, wherein the first condition includes at least one of the following:

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

In one implementation, the information sending device 2400 is a device in the visited place, which may be a device with a network opening function in the visited place (for example, V-NEF), or may be a device with a unified warehousing function in the visited place (for example, V-NEF). -UDR), can also be installed for other core networks at the visited location.

It can be understood that the information sending device 2400 can directly send the first information to the seventh network element through the service interface, so as to facilitate policy updating in the home network.

Target DNAI (target DNAI);

TargetDNAI;

First indication information, the first indication information is used to instruct caching of uplink traffic to be sent to the target DNAI. .

Figure 17 shows a possible structural diagram of the DNS processing device involved in the embodiment of the present application. The DNS processing device is applied to a terminal. As shown in Figure 17, the DNS processing device 150 may include: an execution module 151.

Among them, the execution module 151 is used to execute at least one of the following when the terminal enters the roaming state: clear the DNS cache; send DNS Requery request, DNS requery request is used to request to reselect EAS in the roaming location. .

Embodiments of the present application provide a DNS processing device. After the terminal enters the roaming area, the DNS processing device can clear the DNS cache so that the terminal can find the EAS as soon as possible; and/or the DNS processing device can initiate a DNS re-query request to facilitate the roaming. The optimal EAS is reselected locally; thereby establishing the PDU session in the roaming location.

In a possible implementation, the above execution module 151 is specifically configured to clear the DNS cache when the terminal receives indication information, and the indication information is used to instruct the terminal to clear the DNS cache.

In a possible implementation, the terminal enters the roaming state when the terminal meets the target conditions, and the target conditions include at least one of the following:

The terminal completes registration with V-PLMN;

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

The terminal completes establishing an LBO session or HR session in the roaming location.

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. To avoid duplication, the details will not be described here.

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

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

Sending module 2601, the sending module 2601 is configured to send third information to the ninth network element, where the third information is used to instruct or request the home operator (HPLMN) to verify (authentication) or authorize (authorize) the visited operation The merchant (VPLMN) can perform a first operation, and the first operation includes at least one of the following:

Use the first information directly;

Execute or complete the AF traffic influence procedure;

Use AF traffic influence request information.

or,

Acquisition module, the receiving module is used to acquire fourth information, the fourth information is used to indicate that the visited operator can perform a first operation, and the first operation includes at least one of the following:

Use the first information directly;

Execute or complete the AF traffic influence procedure;

Use AF traffic influence request information.

Target DNAI (target DNAI);

In one implementation, the route reconfiguration device 2600 is a device at the visited location, which may be a device with a session management function at the visited location (for example, V-SMF), or may be a device with a unified data warehousing function at the visited location (for example, V-SMF). V-UDR), can also be installed for other core networks at the visited destination.

Directly use the first information to reconfigure the UPF routing information;

Directly use the first information to update the target DNAI of UPF;

In one implementation, the AF traffic impact process includes: V-AF (or AF) provides the first information to the third network element (for example, V-NEF); the third network element sends the first information to the fifth network element (for example, V-SMF), the route reconfiguration device 2600 directly uses the first information to complete at least one of the following:

Reconfigure the user plane of the PDU session;

Reconfigure UPF routing information;

Update UPF target DNAI;

Determine the target DNAI and add, replace or delete UPF in the data path;

In one implementation, the third information may be used to request authentication or authorization from the home operator (HPLMN). (authorization) A message that the visited operator (VPLMN) can perform the first operation. For example, it can 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 it could be another name.

In an implementation manner, after the ninth network element receives the third information, the ninth network element first restores the contract information from UDR or UDM. Then, the ninth network element verifies, authorizes or approves the third information based on the contract information. When the third information is verified, authorized or approved, it means that the home operator (HPLMN) has verified, authorized or approved that the visited operator (VPLMN) can perform the first operation.

In one implementation, the route reconfiguration device 2600 further includes: a receiving module, the receiving module is configured to receive the verification result or authorization result sent by the ninth network element. The verification result or the authorization result includes at least one of the following:

In one implementation, the fourth information includes at least one of the following:

HR-SBO allowed indication, AF traffic influence in VPLMN allowed indication.

The acquisition module may acquire the fourth information from at least one of the following:

The fourth information obtained by the acquisition module includes at least one of the following:

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

The acquisition module obtains the fourth information from a network element with access management function (such as AMF) through Nsmf_PDUSession_CreateSMContext Request, where the fourth information is that the network element with access management function obtains the fourth information from a network element with unified data management function. Obtained from the functional network element (such as UDM).

In one implementation, after the obtaining module obtains the fourth information, if the receiving module in the route reconfiguration device 2600 receives the first information, the sending module in the route reconfiguration device 2600 may not send The first information is sent to the ninth network element (such as H-SMF), or the execution module in the route reconfiguration device 2600 directly performs at least one of the first operations.

In one implementation, the route reconfiguration device 2600 further includes an execution module, which is configured to execute or complete the AF traffic impact process (AF) when the verification result or authorization result is "verification passed, authorized or approved". traffic influence procedure), or use the first information directly, or use AF traffic influence request information (AF traffic influence request information).

In one implementation, 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, the route reconfiguration device 2600 only sends the third information without sending the first information, which can save the message capacity carried in the signaling.

In another implementation, in addition to sending the third information to the ninth network element, the route reconfiguration device 2600 can also send the first information to the ninth network element, so that the verification result or authorization result of the ninth network element is " In the case of "failed verification, not authorized, not approved", the ninth network element can use the first information to obtain the second information, and send the second information to the route reconfiguration device 2600. Among them, the ninth network element uses the first information to obtain the second information and sends the second information to the route reconfiguration device 2600. You can refer to the operation of the first network element in the corresponding embodiment of Figure 21, and this embodiment is no longer specific. Repeat.

In one implementation, 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 one implementation, the obtaining module may obtain the fourth information before the receiving module receives the first information sent by the third network element, or after the receiving module receives the first information sent by the third network element.

Optionally, as shown in Figure 18, this embodiment of the present application also provides a communication device 5000, which includes a processor 5001 and a memory 5002. The memory 5002 stores programs or instructions that can be run on the processor 5001, such as , when the communication device 5000 is a network element, when the program or instruction is executed by the processor 5001, the above-mentioned first network element side, second network element side, third network element side, first target network element side, and second target are achieved. Each step of the method embodiment on the network element side or the fifth network element side can achieve the same technical effect. To avoid duplication, it will not be described again here. When the communication device 5000 is a terminal, when the program or instruction is executed by the processor 5001, each step of the above terminal-side method embodiment is implemented, and the same technical effect can be achieved. To avoid duplication, the details are not repeated here.

Embodiments of the present application also provide a network element, including a processor and a communication interface. The communication interface is used to send a query request to the second network element. The query request is used to request to query the third network element; and receives the query sent by the second network element. The query response includes the address information of the third network element; and sends a target request to the third network element based on the address information. The target request is used to request to obtain the EDI of the roaming operator from the fourth network element. ; and receive the EDI sent by the third network element. This network element embodiment corresponds to the above-mentioned first network element side method embodiment. Each implementation process and implementation manner of the above-mentioned method embodiment can be applied to this network element embodiment, and can achieve the same technical effect.

Embodiments of the present application also provide a network element, including a processor and a communication interface. The communication interface is used to receive a query request sent by the first network element, where the query request is used to request the query of the third network element; and to the first network element. Send a query response, which includes the address information of the third network element; wherein the address information is used by the first network element to send a target request to the third network element, and the target request is used to request to obtain roaming information from the fourth network element. EDI of the local operator. This network element embodiment corresponds to the above-mentioned second network element side method embodiment. Each implementation process and implementation method of the above-mentioned method embodiment can be applied to this network element embodiment, and can achieve the same technical effect.

An embodiment of the present application also provides a network element, including a processor and a communication interface. The communication interface is used to receive a target request sent by the first network element. The target request is used to request to obtain the EDI of the roaming operator from the fourth network element. ;The third network element sends EDI to the first network element. This network element embodiment corresponds to the above-mentioned third network element side method embodiment. Each implementation process and implementation manner of the above-mentioned method embodiment can be applied to this network element embodiment, and can achieve the same technical effect.

An embodiment of the present application also provides a network element, including a processor and a communication interface. The communication interface is used to receive a first target notification message sent by the fourth network element. The first target notification message is used to notify the fourth network element that a change has been made. AF route impact request information; and sends a second target notification message to the second target network element. The second target notification message includes updated policy information, and the policy information is used for the second target network element to perform traffic routing reconfiguration. This network element embodiment corresponds to the above-mentioned first target network element side method embodiment. Each implementation process and implementation manner of the above-mentioned method embodiment can be applied to this network element embodiment, and can achieve the same technical effect.

Embodiments of the present application also provide a network element, including a processor and a communication interface. The communication interface is used to receive a second target notification message sent by the first target network element. The second target notification message includes updated policy information. The policy information It is used for the second target network element to perform traffic routing reconfiguration; wherein, 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, and the first target notification message is To notify the fourth network element of the changed AF route impact request information. This network element embodiment corresponds to the above-mentioned second target network element side method embodiment. Each implementation process and implementation manner of the above-mentioned method embodiment can be applied to this network element embodiment, and can achieve the same technical effect.

Embodiments of the present application also provide a network element, including a processor and a communication interface. The communication interface is used to receive ECS address configuration information sent by the first network element. The ECS address configuration information includes a PLMN identifier; and sends the ECS address configuration information to the terminal. , the ECS address configuration information is used by the terminal to establish a roaming PDU session with the ECS. This network element embodiment corresponds to the above-mentioned fifth network element side method embodiment. Each implementation process and implementation method of the above-mentioned method embodiment can be applied to this network element embodiment, and can achieve the same technical effect.

This embodiment of the present application also provides a network element. As shown in Figure 19, the network element 1200 includes: a processor 1201, a network interface 1202, and a memory 1203. Among them, the network interface 1202 is, for example, a Common Public Radio Interface (CPRI).

Specifically, the network element 1200 in the embodiment of the present application also includes: instructions or programs stored in the memory 1203 and executable on the processor 1201. The processor 1201 calls the instructions or programs in the memory 1203 to execute the above-mentioned Figures 11 to 16 The method of executing each module in the module, or the method of the processor 1201 calling instructions or programs in the memory 1203 to execute the method of executing each module corresponding to Figure 23 or Figure 24, and achieving the same technical effect, will not be described again here to avoid duplication.

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 above embodiment. Network elements, etc.

The network element provided by the embodiment of the present application can realize each process implemented by 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 above method embodiment. , and achieve the same technical effect. To avoid repetition, we will not repeat them here.

Embodiments of the present application also provide a terminal, including a processor and a communication interface. The processor is configured to perform at least one of the following when the terminal enters the roaming state: clear the DNS cache; send a DNS re-query request. The DNS re-query request uses Request to reselect EAS in roaming location. This terminal embodiment corresponds to the above-mentioned terminal-side method embodiment. Each implementation process and implementation manner of the above-mentioned method embodiment can be applied to this terminal embodiment, and can achieve the same technical effect. Specifically, FIG. 20 is a schematic diagram of the hardware structure of a terminal that implements an embodiment of the present application.

The terminal 7000 includes but is not limited to: a radio frequency unit 7001, a network module 7002, an audio output unit 7003, an input unit 7004, a sensor 7005, a display unit 7006, a user input unit 7007, an interface unit 7008, a memory 7009, a processor 7010, etc. At least some parts.

Those skilled in the art can understand that the terminal 7000 may also include a power supply (such as a battery) that supplies power to various components. The power supply may be logically connected to the processor 7010 through a power management system, thereby managing charging, discharging, and power consumption through the power management system. Management and other functions. The terminal structure shown in Figure 20 does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown in the figure, or some components may be combined or arranged differently, which will not be described again here.

It should be understood that in the embodiment of the present application, the input unit 7004 may include a graphics processing unit (Graphics Processing Unit, GPU) 7041 and a microphone 7042. The graphics processor 7041 is responsible for the image capture device (GPU) in the video capture mode or the image capture mode. Process the image data of still pictures or videos obtained by cameras (such as cameras). The display unit 7006 may include a display panel 7061, which 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 a touch panel 7071 and at least one of other input devices 7072 . Touch panel 7071, also called 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 physical keyboards, function keys (such as volume control keys, switch keys, etc.), trackballs, mice, and joysticks, which will not be described again here.

In this embodiment of the present application, after receiving downlink data from the network side device, the radio frequency unit 7001 can transmit it to the processor 7010 for processing; in addition, the radio frequency unit 7001 can send uplink data to the network side device. Generally, the radio frequency unit 7001 includes, but is not limited to, an antenna, amplifier, transceiver, coupler, low noise amplifier, duplexer, etc.

Memory 7009 may be used to store software programs or instructions as well as various data. The memory 7009 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, an application program or instructions required for at least one function (such as a sound playback function, Image playback function, etc.) etc. Additionally, memory 7009 may include volatile memory or nonvolatile memory, or memory 7009 may include both volatile and nonvolatile memory. Among them, non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electrically removable memory. Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory. Volatile memory can be random access memory (Random Access Memory, RAM), static random access memory (Static RAM, SRAM), dynamic random access memory (Dynamic RAM, DRAM), synchronous dynamic random access memory (Synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDRSDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (Synch link DRAM) , SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DRRAM). Memory 709 in embodiments of the present 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; optionally, the processor 7010 integrates an application processor and a modem processor, where the application processor mainly handles operations related to the operating system, user interface, application programs, etc., Modem processors mainly process wireless communication signals, such as baseband processors. It can be understood that the above modem processor may not be integrated into the processor 7010.

The processor 7010 is configured to perform at least one of the following when the terminal enters the roaming state: clear the DNS cache; send a DNS requery request, and the DNS requery request is used to request EAS reselection in the roaming location.

Embodiments of the present application provide a terminal. After the terminal enters the roaming area, it can clear the DNS cache so that the terminal can find the EAS as soon as possible; and/or the terminal can initiate a DNS re-query request to reselect the optimal EAS in the roaming area; This enables the establishment of a PDU session in the roaming location.

The terminal provided by the embodiments of this application can implement each process implemented by the terminal in the above method embodiments and achieve the same technical effect. To avoid duplication, details will not be described here.

Embodiments of the present application also provide a readable storage medium. Programs or instructions are stored on the readable storage medium. When the program or instructions are executed by a processor, each process of the above method embodiments is implemented and the same technology can be achieved. The effect will not be described here to avoid repetition.

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

An embodiment of the present application further provides a chip. The chip includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement various processes of the above method embodiments. , and can achieve the same technical effect, so to avoid repetition, they will not be described again here.

It should be understood that the chips mentioned in the embodiments of this application may also be called system-on-chip, system-on-a-chip, system-on-chip or system-on-chip, etc.

Embodiments of the present application further provide a computer program/program product. The computer program/program product is stored in a storage medium. The computer program/program product is executed by at least one processor to implement each of the above method embodiments. The process can achieve the same technical effect. To avoid repetition, it will not be described again here.

An embodiment of the present application also provides a communication system, including: a first network element, a second network element, and a third network element. The first network element can be used to perform the steps of the EDI acquisition method as described above. The second network element may be used to perform the steps of the EDI obtaining method as described above, and the third network element may be used to perform the steps of the EDI obtaining method as described above.

An embodiment of the present application also provides a communication system, including: a first target network element and a second target network element. The first target network element can be used to perform the steps of the route reconfiguration method as described above. The third target network element The second target network element may be used to perform the steps of the route reconfiguration method as described above.

Embodiments of the present application also provide a communication system, including: 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. The first network element may be used to perform the steps of the EDI obtaining method as described above, the second network element may be used to perform the steps of the EDI obtaining method as described above, and the third network element may be used to perform the EDI obtaining method as described above. In the steps of the acquisition method, the first target network element may The second target network element may be used to perform the steps of the route reconfiguration method as described above. The fifth network element may be used to perform the ECS address as described above. In the steps of the configuration information obtaining method, the terminal may be used to perform the steps of the DNS processing method as described above.

It should be noted that, in this document, the terms "comprising", "comprises" or any other variations thereof are intended to cover a non-exclusive inclusion, such that a process, method, article or device that includes a series of elements not only includes those elements, It also includes other elements not expressly listed or inherent in the process, method, article or apparatus. Without further limitation, an element defined by the statement "comprises a..." does not exclude the presence of additional identical elements in a process, method, article or apparatus that includes that element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, but may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved. Functions may be performed, for example, the methods described 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.

Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus the necessary general hardware platform. Of course, it can also be implemented by hardware, but in many cases the former is better. implementation. Based on this understanding, the technical solution of the present application can be embodied in the form of a computer software product that is essentially or contributes to the existing technology. The computer software product is stored in a storage medium (such as ROM/RAM, disk , CD), including several instructions to cause a terminal (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in various embodiments of this application.

The embodiments of the present application have been described above in conjunction with the accompanying drawings. However, the present application is not limited to the above-mentioned specific implementations. The above-mentioned specific implementations are only illustrative and not restrictive. Those of ordinary skill in the art will Inspired by this application, many forms can be made without departing from the purpose of this application and the scope protected by the claims, all of which fall within the protection of this application.

Claims

A method for obtaining edge application server deployment information EDI, the method includes:

The first network element sends a query request to the second network element, where the query request is used to request to query the third network element;

The first network element receives a query response sent by the second network element, where the query response includes address information of the third network element;

The first network element sends a target request to the third network element based on the address information, where the target request is used to request to obtain the EDI of the roaming operator from the fourth network element;

The first network element receives the EDI sent by the third network element.
The method according to claim 1, wherein the query request includes at least one of the following: a public land mobile network PLMN identity and a user permanent identity SUPI;

Wherein, the PLMN identifier includes at least one of the following: a visited V-PLMN identifier and a home H-PLMN identifier.
The method according to claim 1, wherein the address information includes at least one of the following: a network protocol IP address and a fully qualified domain name (FQDN) of the third network element.
The method according to claim 1, wherein the target request includes at least one of the following: PLMN identification, single network slice selection assistance information S-NSSAI, and data network name DNN.
The method according to any one of claims 1 to 4, wherein the first network element sends a query request to the second network element, including:

The first network element sends the query request to the second network element via the home network storage function H-NRF network element.
The method according to any one of claims 1 to 4, wherein the method further includes:

The first network element sends a first request to the unified data management UDM network element. The first request is used to request to obtain the subscription information of the terminal. The terminal needs to establish a protocol data unit PDU session or update a PDU for a roaming location. The terminal of the session, the subscription information is used to indicate whether the terminal is authorized to use the roaming edge computing service, and the first request includes a PLMN identity;

The first network element receives a first response sent by the UDM network element, where the first response includes the subscription information of the terminal;

The first network element sends a query request to the second network element, including:

If the subscription information indicates that the terminal is authorized to use the roaming edge computing service, the first network element sends the query request to the second network element.
A method for obtaining edge application server deployment information EDI, the method includes:

The second network element receives the query request sent by the first network element, where the query request is used to request the query of the third network element;

The second network element sends a query response to the first network element, where the query response includes 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, and the target request is used to request to obtain the EDI of the roaming operator from the fourth network element.
The method according to claim 7, wherein the second network element receives the query request sent by the first network element, including:

The second network element receives the query request sent by the first network element via the home network storage function H-NRF network element.
A method for obtaining edge application server deployment information EDI, the method includes:

The third network element receives the target request sent by the first network element, where the target request is used to request to obtain the EDI of the roaming operator from the fourth network element;

The third network element sends the EDI to the first network element.
The method according to claim 9, wherein before the third network element sends the EDI to the first network element, the method further includes:

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;

The third network element sends the EDI to the first network element, including:

After 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 it to the The first network element sends the EDI.
A route reconfiguration method, the method includes:

The first target network element receives the first target notification message sent by the fourth network element, where the first target notification message is used to notify the changed application function AF route impact request information in the fourth network element;

The first target network element sends a second target notification message to the second target network element. The second target notification message includes updated policy information, and the policy information is used for traffic routing by the second target network element. Reconfigure.
The method according to claim 11, wherein the AF route impact request information includes at least one of the following: traffic description information, identification of the terminal whose traffic will be affected, traffic routing information of the target interface, data network access identification, Public land mobile network PLMN logo.
The method according to claim 11, wherein the first target network element sends a second target notification message to the second target network element, including:

The first target network element sends a first notification message to the first network element, where the first notification message is used to notify that the current home routing HR session is affected by the AF request;

Wherein, the first notification message is used for the first network element to perform traffic routing reconfiguration and send a second notification message to the fifth network element. The second notification message is used to notify the protocol data unit PDU of the roaming location. The session needs to be changed, and the second notification message is used for the fifth network element to perform traffic routing reconfiguration.
The method according to claim 11, wherein the first target network element sends a second target notification message to the second target network element, including:

The first target network element sends a first notification message to the first network element. The first notification message is used to notify that the current home routing HR session is affected by the AF request. The first notification message is used for the third One network element performs traffic routing reconfiguration;

The first target network element sends a second notification message to the fifth network element, where the second notification message is used to notify that the PDU session in the roaming location needs to be changed, The second notification message is used for the fifth network element to perform traffic routing reconfiguration.
The method according to claim 11, wherein the first target network element receives the first target notification message sent by the fourth network element, including:

The first target network element receives the first target notification message sent by the fourth network element via the sixth network element;

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

The first target network element sends a first notification message to the first network element. The first notification message is used to notify that the current home routing HR session is affected by the AF request. The first notification message is used for the third One network element performs traffic routing reconfiguration;

The first target network element sends a second notification message to the fifth network element. The second notification message is used to notify that the PDU session in the roaming location needs to be changed. The second notification message is used for the fifth network element to perform Traffic routing reconfiguration.
The method according to claim 11, wherein the first target network element sends a second target notification message to the second target network element, including:

The first target network element sends a first notification message to the fifth network element, where the first notification message is used to notify that the current home routing HR session is affected by the AF request;

Wherein, the first notification message is used for the fifth network element to perform traffic routing reconfiguration and send a second notification message to the first network element. The second notification message is used to notify that the PDU session in the roaming location needs to be changed. , the second notification message is used for the fifth network element to perform traffic routing reconfiguration when the first network element agrees to perform PDU session change.
The method according to any one of claims 13 to 16, wherein the second notification message includes at least one of the following: a data network access identifier, traffic routing information of the target interface, and an affected user plane function identifier. , the affected PDU session identifier, the affected terminal identifier, and the PLMN identifier.
The method according to any one of claims 13 to 16, wherein the manner in which the fifth network element performs traffic routing reconfiguration includes at least one of the following:

Reselect or change user interface;

Establish a PDU session to the visited edge application server EAS;

Instruct the user plane to replace the source and destination EAS address accessed by the terminal with the destination EAS address, and the destination EAS address is carried by the first target notification message.
A route reconfiguration method, the method includes:

The second target network element receives the second target notification message sent by the first target network element. The second target notification message includes updated policy information. The policy information is used for the second target network element to reroute traffic. configuration;

Wherein, 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, and the first target notification message is used to notify the fourth network element Changed application functionality in the meta affects AF routing request information.
The method according to claim 19, wherein the second target network element receives the second target notification message sent by the first target network element, including:

The second target network element receives the first notification message sent by the first target network element through the first network element. The first notification message is used to notify that the current home routing HR session is affected by the AF request. The first notification message is used for the first network element to perform traffic routing reconfiguration;

The second target network element receives the second notification message sent by the first network element through the fifth network element. The second notification message is used to notify the protocol data unit PDU session in the roaming location that the session needs to be changed. The notification message is used for the fifth network element to perform traffic routing reconfiguration.
The method according to claim 19, wherein the second target network element receives the second target notification message sent by the first target network element, including:

The second target network element receives the first notification message sent by the first target network element through the first network element. The first notification message is used to notify that the current home routing HR session is affected by the AF request. The first notification message is used for the first network element to perform traffic routing reconfiguration;

The second target network element receives the second notification message sent by the first target network element through the fifth network element. The second notification message is used to notify that the PDU session in the roaming location needs to be changed. The second notification message Used for the fifth network element to perform traffic routing reconfiguration.
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 the second target notification message sent by the first target network element, including:

The second target network element receives the first notification message sent by the first target network element through the first network element. The first notification message is used to notify that the current home routing HR session is affected by the AF request. The first notification message is used for the first network element to perform traffic routing reconfiguration;

The second target network element receives the second notification message sent by the first target network element through the fifth network element. The second notification message is used to notify that the PDU session in the roaming location needs to be changed. The second notification message Used for the fifth network element to perform traffic routing reconfiguration.
The method according to claim 19, wherein the second target network element receives the second target notification message sent by the first target network element, including:

The second target network element receives the first notification message sent by the first target network element through the fifth network element. The first notification message is used to notify that the current home routing HR session is affected by the AF request. The first notification message is used for the fifth network element to perform traffic routing reconfiguration;

The second target network element receives the second notification message sent by the fifth network element through the first network element. The second notification message is used to notify that the PDU session in the roaming location needs to be changed. The second notification message is used When the first network element agrees to perform PDU session change, the fifth network element performs traffic routing reconfiguration.
A method for obtaining ECS address configuration information of an edge configuration server, the method includes:

The fifth network element receives the 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 fifth network element sends the ECS address configuration information to the terminal, and the ECS address configuration information is used for the terminal to establish a protocol data unit PDU session in the roaming location with the ECS.
The method according to claim 24, wherein the ECS address configuration information is stored by a unified data storage network element or a unified data management network element.
A domain name system DNS processing method, the method includes:

When the terminal enters the roaming state, the terminal performs at least one of the following:

Clear DNS cache;

Send a DNS requery request, where the DNS requery request is used to request reselection of the edge application server EAS in the roaming location.
The method according to claim 26, wherein the terminal clears the DNS cache, including:

When the terminal receives the indication information, the terminal clears the DNS cache, and the indication information is used to instruct the terminal to clear the DNS cache.
The method according to claim 26 or 27, wherein the terminal enters the roaming state when the terminal meets target conditions, and the target conditions include at least one of the following:

The terminal completes registration with the visited public land mobile network V-PLMN;

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

The terminal completes establishing a local offload LBO session or a home routing HR session in the roaming location.
An edge application server deployment information EDI acquisition device is applied to the first network element. The device includes: a sending module and a receiving module;

The sending module is used to send a query request to the second network element, and the query request is used to request 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 the 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 to obtain the EDI of the roaming operator from the fourth network element;

The receiving module is also configured to receive the EDI sent by the third network element.
An edge application server deployment information EDI acquisition device is applied to the second network element, and the device includes: a receiving module and a sending module;

The receiving module is used to receive a query request sent by the first network element, and the query request is used to request 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 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, and the target request is used to request to obtain the EDI of the roaming operator from the fourth network element.
An edge application server deployment information EDI acquisition device is applied to a third network element. The device includes: a receiving module and a sending module;

The receiving module is configured to receive a target request sent by the first network element, where the target request is used to request to obtain the EDI of the roaming operator from the fourth network element;

The sending module is configured to send the EDI to the first network element.
A route reconfiguration device, applied to a first target network element, the device includes: a receiving module and a sending 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 changed application function AF route impact request information in the fourth network element;

The sending module is configured to send a second target notification message to a second target network element. The second target notification message includes updated policy information. The policy information is used for traffic routing by the second target network element. Reconfigure.
A route reconfiguration device, applied to a second target network element, the device includes: a receiving module;

The receiving module is configured to receive a second target notification message sent by the first target network element. The second target notification message includes updated policy information. The policy information is used for the second target network element to conduct traffic. Route reconfiguration;

Wherein, 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, and the first target notification message is used to notify the fourth network element Changed application functionality in the meta affects AF routing request information.
A device for obtaining ECS address configuration information of an edge configuration server, applied to the fifth network element, the device includes: a receiving module and a sending module;

The receiving module is configured to receive the 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 the terminal. The ECS address configuration information is used for the terminal to establish a roaming protocol data unit PDU session with the ECS.
A domain name system DNS processing device, applied to a terminal, the device includes: an execution module;

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

Clear DNS cache;

Send a DNS requery request, where the DNS requery request is used to request reselection of the edge application server EAS in the roaming location.
A network element, including a processor, a memory, and a program or instruction stored on the memory and executable on the processor. When the program or instruction is executed by the processor, the implementation of claims 1 to 6 is achieved. The steps of the edge application server deployment information EDI acquisition method described in any one of the above, or the steps of implementing the EDI acquisition method as claimed in claim 7 or 8, or the steps of implementing the EDI acquisition method as claimed in claim 9 or 10 step.
A network element, including a processor, a memory and a program or instructions stored on the memory and executable on the processor. When the program or instructions are executed by the processor, the implementation of claims 11 to 18 is achieved. The steps of the route reconfiguration method described in any one of claims 19 to 23, or the steps of implementing the route reconfiguration method described in any one of claims 19 to 23.
A network element, including a processor, a memory and a program or instructions stored in the memory and executable on the processor. When the program or instructions are executed by the processor, the implementation of claim 24 or 25 is achieved. The steps of the method for obtaining the ECS address configuration information of the edge configuration server.
A terminal, including a processor, a memory and a program or instructions stored on the memory and executable on the processor. When the program or instructions are executed by the processor, the implementation of claims 26 to 28 is achieved. The steps of the domain name system DNS processing method described in any one of the above.
A readable storage medium on which programs or instructions are stored. When the programs or instructions are executed by a processor, the EDI acquisition of edge application server deployment information according to any one of claims 1 to 6 is implemented. The steps of the method, or the steps of realizing the EDI acquisition method as claimed in claim 7 or 8, or the steps of realizing the EDI acquisition method as claimed in claim 9 or 10, or any one of claims 11 to 18 The steps of the route reconfiguration method, or the steps of implementing the route reconfiguration method as described in any one of claims 19 to 23, or the steps of implementing the edge configuration server ECS address configuration information as claimed in claim 24 or 25 The steps of the acquisition method, or the steps of implementing the domain name system DNS processing method as described in any one of claims 26 to 28.