CN114615270A - Method and device for migrating edge application server and refreshing or emptying DNS (domain name system) cache - Google Patents

Method and device for migrating edge application server and refreshing or emptying DNS (domain name system) cache Download PDF

Info

Publication number
CN114615270A
CN114615270A CN202011447141.XA CN202011447141A CN114615270A CN 114615270 A CN114615270 A CN 114615270A CN 202011447141 A CN202011447141 A CN 202011447141A CN 114615270 A CN114615270 A CN 114615270A
Authority
CN
China
Prior art keywords
information
application server
edge application
core network
dns cache
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202011447141.XA
Other languages
Chinese (zh)
Inventor
吕华章
柯小婉
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Vivo Mobile Communication Co Ltd
Original Assignee
Vivo Mobile Communication Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Vivo Mobile Communication Co Ltd filed Critical Vivo Mobile Communication Co Ltd
Priority to CN202011447141.XA priority Critical patent/CN114615270A/en
Priority to PCT/CN2021/136145 priority patent/WO2022121902A1/en
Publication of CN114615270A publication Critical patent/CN114615270A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10Architectures or entities
    • H04L65/1059End-user terminal functionalities specially adapted for real-time communication
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Computer And Data Communications (AREA)

Abstract

The application discloses a method and a device for migrating an edge application server and refreshing or emptying a DNS (domain name system) cache, belonging to the technical field of wireless communication. The method for migrating the edge application server is executed by a first core network device and comprises the following steps: after receiving first information, judging whether second information needs to be sent to a target terminal, wherein the first information is used for indicating that a source edge application server providing service support for the target terminal has been migrated to a target edge application server, and the second information is used for indicating the target terminal to refresh DNS cache records or empty part or all of the DNS cache records; and when the second information needs to be sent to the target terminal, sending the second information to the target terminal. In the application, after the migration of the edge application server is completed, the terminal can refresh or empty the DNS cache according to the indication of the core network device, so that a new edge application server can be found when the DNS query process is restarted.

Description

Method and device for migrating edge application server and refreshing or emptying DNS (domain name system) cache
Technical Field
The application belongs to the technical field of wireless communication, and particularly relates to a method and a device for migrating an edge application server and refreshing or emptying a DNS cache.
Background
Edge Application Server (EAS) migration (relocation) is a phenomenon in which an Edge Application Server migrates when User Equipment (UE, also called a terminal) moves, or when a load balance (load balance) or failure (break down) occurs in the Edge Application Server.
In the process of edge application server migration, the most important thing is how to let the UE find a new edge application server again.
One method is to find a new edge application server by the UE triggering a Domain Name System (DNS) query process. The UE has its own technology, in which the Operating System (OS) of the UE can automatically refresh (refresh) or flush (flush) the old DNS cache when it senses a new Internet Protocol (IP) connection (link).
However, in the session break (session break) connected mode of edge application server migration, the UE does not perceive any change in the user plane at all, including the new IP link. Therefore, in this scenario, the UE cannot perceive the new IP link, and therefore the DNS cache is not refreshed or emptied. Even if the UE re-initiates the DNS process to find a new edge application server, the old DNS cache is still used, so that the old edge application server is still connected, and the new edge application server cannot be found.
Disclosure of Invention
An object of the embodiments of the present application is to provide a method and an apparatus for migrating an edge application server, refreshing or clearing a DNS cache, which can solve the problem that after the edge application server is migrated, if a UE still uses an old DNS cache, the UE still connects to the old edge application server and cannot find a new edge application server.
In order to solve the technical problem, the present application is implemented as follows:
in a first aspect, a method for migrating an edge application server is provided, where the method is performed by a first core network device, and includes:
after receiving first information, judging whether second information needs to be sent to a target terminal, wherein the first information is used for indicating that a source edge application server providing service support for the target terminal has been migrated to a target edge application server, and the second information is used for indicating the target terminal to refresh DNS cache records or empty part or all of the DNS cache records;
and when the second information needs to be sent to the target terminal, sending the second information to the target terminal.
In a second aspect, a DNS cache refreshing or clearing method is provided, which is executed by a terminal, and includes:
receiving second information sent by first core network equipment, wherein the second information is used for indicating the terminal to refresh DNS cache records or clear part or all of the DNS cache records;
and refreshing the DNS cache record according to the second information, or emptying all or part of the DNS cache record.
In a third aspect, an edge application server migration apparatus is provided, including:
the system comprises a judging module and a judging module, wherein the judging module is used for judging whether second information needs to be sent to a target terminal or not after first information is received, the first information is used for indicating that a source edge application server providing service support for the target terminal has been migrated to a target edge application server, and the second information is used for indicating the target terminal to refresh DNS cache records or empty all or part of the DNS cache records;
and the sending module is used for sending the second information to the target terminal when the second information needs to be sent to the target terminal.
In a fourth aspect, a DNS cache refreshing or flushing apparatus is provided, including:
a receiving module, configured to receive second information sent by a first core network device, where the second information is used to instruct a terminal to refresh a DNS cache record or to clear part or all of the DNS cache record;
and the processing module is used for refreshing the DNS cache record according to the second information, or emptying all or part of the DNS cache record.
In a fifth aspect, a core network device is provided, the terminal comprising a processor, a memory, and a program or instructions stored on the memory and executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method according to the first aspect.
In a sixth aspect, a terminal is provided, where the network-side device includes a processor, a memory, and a program or instructions stored on the memory and executable on the processor, and the program or instructions, when executed by the processor, implement the steps of the method according to the second aspect.
In a seventh aspect, there is provided a readable storage medium on which a program or instructions are stored, which program or instructions, when executed by a processor, implement the steps of the method according to the first aspect, or implement the steps of the method according to the third aspect.
In an eighth aspect, a chip is provided, where the chip includes a processor and a communication interface, where the communication interface is coupled to the processor, and the processor is configured to execute a network-side device program or instruction, implement the method according to the first aspect, or implement the method according to the second aspect.
In a ninth aspect, there is provided a program product stored on a non-volatile storage medium, the program product being executable by at least one processor to implement a method as in the first aspect, or to implement a method as in the second aspect.
In this embodiment of the present application, after the migration of the edge application server is completed, the core network device may determine, according to the determination, whether it is necessary to send, to the terminal, indication information for indicating that the terminal refreshes or clears the DNS cache, so that the terminal can refresh or clear the DNS cache according to the indication of the core network device, and thus can discover a new edge application server when the DNS query process is restarted.
Drawings
Fig. 1 is a schematic flowchart of an edge application server migration method according to an embodiment of the present application;
fig. 2 is a schematic diagram of a core network session connection mode;
fig. 3 is a schematic flowchart of a DNS cache refreshing or flushing method according to an embodiment of the present application;
fig. 4 is an interaction flow diagram of an edge application server migration method according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of an edge application server migration apparatus according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of a DNS cache refreshing or flushing apparatus according to an embodiment of the present application;
fig. 7 is a schematic structural diagram of a communication device according to an embodiment of the present application;
fig. 8 is a schematic diagram of a hardware structure of a terminal for implementing the embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, embodiments of the present application. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present application without making any creative effort belong to the protection scope of the present application.
The terms first, second and the like in the description and in the claims of the present application are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It should be understood that the data so used are interchangeable under appropriate circumstances such that embodiments of the application can be practiced in sequences other than those illustrated or described herein, and the terms "first" and "second" used herein generally do not denote any order, nor do they denote any order, for example, the first object may be one or more. In addition, "and/or" in the specification and the claims means at least one of connected objects, and a character "/" generally means that a preceding and succeeding related objects are in an "or" relationship.
It is worth pointing out that the technology described in the embodiments of the present applicationThe technique is not limited to Long Term Evolution (LTE)/LTE Evolution (LTE-Advanced) systems, but may also be used in other wireless communication systems, such as 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 the present application are often used interchangeably, and the described techniques can be used for both the above-mentioned systems and radio technologies, as well as for other systems and radio technologies. However, the following description describes a New Radio (NR) system for purposes of example, and NR terminology is used in much of the description below, although the techniques may also be applied to applications other than NR system applications, such as 6 th generation (6 th generation)thGeneration, 6G) communication system.
The terminal in the embodiment of the present application may be a Mobile phone, a Tablet Personal Computer (Tablet Personal Computer), a Laptop Computer (Laptop Computer) or a terminal side Device called a notebook Computer, a Personal Digital Assistant (PDA), a palmtop Computer, a netbook, a super Mobile Personal Computer (ultra-Mobile Personal Computer, UMPC), a Mobile Internet Device (MID), a Wearable Device (Wearable Device) or a vehicle mounted Device (VUE), a pedestrian terminal (PUE), and the Wearable Device includes: bracelets, earphones, glasses and the like. It should be noted that the embodiment of the present application does not limit the specific type of the terminal.
The edge application server migration method, the DNS cache refreshing or clearing method, and the DNS cache flushing or clearing device provided in the embodiments of the present application are described in detail below with reference to the accompanying drawings by specific embodiments and application scenarios thereof.
Referring to fig. 1, fig. 1 is a flowchart illustrating an edge application server migration method according to an embodiment of the present application, where the edge application server migration method is executed by a first core network device, and in the embodiment of the present application, the first core network device may be a Session Management Function (SMF), and certainly, in some other embodiments of the present application, other core network functions are not excluded, and the edge application server migration method includes:
step 11: after receiving first information, judging whether second information needs to be sent to a target terminal, wherein the first information is used for indicating that a source edge application server providing service support for the target terminal has been migrated to a target edge application server, and the second information is used for indicating the target terminal to refresh (refresh) DNS cache records or empty (clear or flush) part or all of the DNS cache records;
in this embodiment of the present Application, the first information may be sent by an Application Function (AF), and certainly, sending by using other core network functions is not excluded.
The first information is, for example, Nsmf _ EventExposure _ apprelocation info. In the migration process of the edge application server, the AF may need to send Nsmf _ EventExposure _ applocationinfo to the first core network device 2 times, where the first information in this application is Nsmf _ EventExposure _ applocationinfo sent by the AF for the second time, and in order to distinguish from Nsmf _ EventExposure _ applocationinfo sent for the first time, the Nsmf _ EventExposure _ applocationinfo sent for the second time may be added with an identifier to indicate as the first information, for example, a table notification identifier is added, and the Nsmf _ EventExposure _ appletationinfo sent for the first time may be added with an early notification identifier.
Step 12: and when the second information needs to be sent to the target terminal, sending the second information to the target terminal.
In the embodiment of the application, after the migration of the edge application server is completed, the core network device may determine, according to the determination, whether to send to the terminal indication information for indicating that the terminal refreshes or clears the DNS cache, so that the terminal can refresh or clear the DNS cache according to the indication of the core network device, and thus, a new edge application server can be found when the DNS query process is restarted.
In this embodiment, optionally, whether to send the second information to the target terminal may be determined according to a mode (also referred to as an EAS IP replacement method, EAS IP relocation) of whether to replace the IP address of the edge application server with the second core network device and a session connection mode of the core network.
In the manner that the second core network device replaces the IP address of the edge application server, the user cannot perceive the IP address of the edge application server.
Optionally, referring to fig. 2, the core network session connection modes include three types:
(1) distributed Anchor (Distributed Anchor). The PDU session anchor moves far away in the network, i.e. to the local site.
(2) Session breakout (session breakout). The PDU session has a PDU session anchor point in the central site and a PDU session anchor point in the local site. Only one of which provides an IP anchor. Edge computing application traffic is selectively transferred to a local PDU session anchor Point using an upstream classifier (UL CL) or a Branch Point (BP) technique. That is, session forking is to insert a UL CL/BP in the middle of the whole session, which can fork traffic to a User Plane Function (UPF) of the local station, but this procedure is not perceived by the UE, which is equivalent to that the UE does not know that the UL CL/BP is inserted.
(3) Multiple PDU Sessions (Multiple Sessions). The edge computing applications use a particular PDU session with a PDU session anchor in the local site, and the remaining applications use PDU sessions with a central PDU session anchor.
As can be seen from the above description, in the session offloading connection mode, the UE does not know that the UL CL/BP is inserted, and thus cannot sense the change of the IP address of the edge application server even when the edge application server migrates.
Based on this, optionally, determining whether it is necessary to send the second information to the target terminal according to a mode of whether the second core network device is used to replace the IP address of the edge application server and a session connection mode of the core network, where the mode includes at least one of the following:
1) if the mode that second core network equipment replaces the IP address of the edge application server is adopted, judging that second information does not need to be sent to the target terminal;
in a mode that the second core network device replaces the IP address of the edge application server, the user cannot perceive the IP address of the edge application server, and therefore, the user does not need to send the second information to the target terminal to refresh or empty the DNS cache.
2) If the mode that the IP address of the edge application server is not replaced by second core network equipment and the session connection mode of the core network is a session shunting mode, judging that second information needs to be sent to the target terminal;
in the session offloading mode, since the UE does not know that the UL CL/BP is inserted, it cannot sense the change of the IP address of the edge application server even when the edge application server migrates, and therefore, it is necessary to notify the UE to refresh or empty the DNS cache.
3) And if the mode that the IP address of the edge application server is not replaced by the second core network equipment and the session connection mode of the core network is the other mode of the non-session shunting mode, judging that the second information does not need to be sent to the target terminal.
In other modes than the session offload mode (distributed anchor or multi-PDU session mode), the UE may be aware of the change in IP address, so that the UE does not need to be informed to refresh or empty the DNS cache.
In this embodiment of the application, optionally, the second core network device may be a User Plane Function (UPF), and certainly, other core network devices are not excluded.
Referring to fig. 3, fig. 3 is a schematic flowchart of a DNS cache refreshing or clearing method according to an embodiment of the present application, where the DNS cache refreshing or clearing method is executed by a terminal, and the DNS cache refreshing or clearing method is executed by the terminal, and includes:
step 31: receiving second information sent by first core network equipment, wherein the second information is used for indicating the terminal to refresh DNS cache records or clear part or all of the DNS cache records;
step 32: and refreshing the DNS cache record according to the second information, or emptying all or part of the DNS cache record.
In the embodiment of the application, after the migration of the edge application server is completed, the terminal can refresh or empty the DNS cache according to the indication of the core network device, so that a new edge application server can be found when the DNS query process is restarted.
In this embodiment of the present application, optionally, the refreshing the DNS cache record includes: and refreshing an IP address corresponding to a Fully Qualified Domain Name (FQDN) of an edge application server in a DNS cache of the terminal. A fully qualified domain name is a name with both a host name and a domain name. For example: the host name is bigserver, the domain name is mycompany.
In this embodiment of the present application, optionally, clearing all or part of DNS cache records includes: and clearing all information in the DNS cache of the terminal, or clearing the FQDN of the edge application server in the DNS cache of the terminal and the IP address corresponding to the FQDN.
The following describes the above migration method of the edge application server with reference to a specific embodiment.
Referring to fig. 4, an edge application server migration method according to an embodiment of the present application includes:
step 1: the AF subscribes a Data Network Access Identifier (DNAI) change time notification to the 5G core Network;
step 2: a Policy Control Function (PCF) sends a Policy Charging Control (PCC) rule to the SMF;
and step 3: EAS needs to migrate to a new DANI;
and 4, step 4: the AF sends application control information to the affected UE;
and 5: PCF sends PCC rule to SMF;
step 6: SMF determines EAS migration;
and 7: the SMF sends Nsmf _ EventExposure _ Notify to the AF;
step 8, the AF sends a Nsmf _ EventExposure _ AppRescrocationInfo to the SMF.
And step 9: setting target BP/UL CL and PSA3, starting a timer, comprising:
step 9 a: the target UPF and the SMF are used for carrying out N4 session establishment;
and step 9 b: the source BP/UL CL carries out N4 session modification with PCF;
and step 9 c: the target BP/UL CL and PCF carry out N4 session establishment;
and step 9 d: the UE and the PCF carry out N4 session modification;
step 10: the SMF sends Nsmf _ EventExposure _ Notify to the AF;
step 11: the context migration is complete;
step 12: the AF sends Nsmf _ EventExposure _ AppReLocation Info to the SMF.
Here, the Nsmf _ EventExposure _ apprelocation info, i.e. the first information, may add an identifier to the Nsmf _ EventExposure _ apprelocation info in step 12 to indicate that the first information is the first information, e.g. add a late notification identifier, and the Nsmf _ EventExposure _ apprelocation info in step 8 may add an early notification identifier.
Step 13: the SMF judges whether second information needs to be sent to the target terminal;
the specific judgment process is as follows:
1) if the mode that second core network equipment replaces the IP address of the edge application server is adopted, judging that second information does not need to be sent to the target terminal;
2) if the mode that the IP address of the edge application server is not replaced by second core network equipment and the session connection mode of the core network is a session shunting mode, judging that second information needs to be sent to the target terminal;
3) and if the mode that the IP address of the edge application server is not replaced by the second core network equipment and the session connection mode of the core network is the other mode of the non-session shunting mode, judging that the second information does not need to be sent to the target terminal.
Step 14: and when the second information needs to be sent to the target terminal, sending the second information to the target terminal.
Step 15: the UE refreshes or empties the DNS cache and triggers a new DNS query.
Step 16: the source BP/UL CL and PSA2 are removed.
It should be noted that, in the edge application server migration method provided in the embodiment of the present application, the execution subject may be an edge application server migration apparatus, or a control module in the edge application server migration apparatus, configured to execute the edge application server migration method. In the embodiment of the present application, an edge application server migration apparatus performs an edge application server migration method as an example, and the edge application server migration apparatus provided in the embodiment of the present application is described.
Referring to fig. 5, an embodiment of the present application further provides an edge application server migration apparatus 50, including:
a determining module 51, configured to determine whether second information needs to be sent to a target terminal after receiving first information, where the first information is used to indicate that a source edge application server providing service support for the target terminal has migrated to a target edge application server, and the second information is used to indicate the target terminal to refresh a DNS cache record or to empty all or part of the DNS cache record;
a sending module 52, configured to send the second information to the target terminal when it is determined that the second information needs to be sent to the target terminal.
In the embodiment of the application, after the migration of the edge application server is completed, the core network device may determine, according to the determination, whether to send to the terminal indication information for indicating that the terminal refreshes or clears the DNS cache, so that the terminal can refresh or clear the DNS cache according to the indication of the core network device, and thus, a new edge application server can be found when the DNS query process is restarted.
In this embodiment, optionally, the determining module is configured to determine whether to send the second information to the target terminal according to a mode of whether to replace the IP address of the edge application server with the second core network device and a core network session connection mode.
In this embodiment of the application, optionally, the determining module includes at least one of the following:
the first judgment submodule is used for judging that second information does not need to be sent to the target terminal if a mode that second core network equipment replaces an IP address of an edge application server is adopted;
the second judgment submodule is used for judging that second information needs to be sent to the target terminal if a mode that second core network equipment replaces an IP address of the edge application server is not adopted and a core network session connection mode is a session shunting mode;
and the third judging submodule is used for judging that the second information does not need to be sent to the target terminal if the mode that the second core network equipment replaces the IP address of the edge application server is not adopted and the session connection mode of the core network is the other mode of the non-session shunting mode.
Optionally, the second core network device is a UPF.
Optionally, the other modes of the non-session offload mode include: distributed anchor mode and multi-PDU session mode.
In this embodiment of the present application, optionally, the edge application server migration apparatus further includes:
and the receiving module is used for receiving the first information sent by the AF.
The edge application server migration apparatus provided in the embodiment of the present application can implement each process implemented in the method embodiment of fig. 1, and achieve the same technical effect, and is not described here again to avoid repetition.
Referring to fig. 6, an embodiment of the present application further provides a DNS cache refreshing or flushing apparatus 60, including:
a receiving module 61, configured to receive second information sent by a first core network device, where the second information is used to instruct the terminal to refresh a DNS cache record or to empty part or all of the DNS cache records;
and the processing module 62 is configured to refresh the DNS cache record according to the second information, or empty all or part of the DNS cache record.
In the embodiment of the application, after the migration of the edge application server is completed, the terminal can refresh or empty the DNS cache according to the indication of the core network device, so that a new edge application server can be found when the DNS query process is restarted.
Optionally, the processing module 62 includes:
and the refreshing submodule is used for refreshing the IP address corresponding to the FQDN of the edge application server in the DNS cache of the terminal.
Optionally, the processing module 62 includes:
and the emptying submodule is used for emptying all information in the DNS cache of the terminal, or emptying the FQDN of the edge application server in the DNS cache of the terminal and the IP address corresponding to the FQDN.
The DNS cache refreshing or flushing apparatus in the embodiment of the present application may be an apparatus, or may be a component, an integrated circuit, or a chip in a terminal. The device can be a mobile terminal or a non-mobile terminal. By way of example, the mobile terminal may include, but is not limited to, the above-listed type of terminal 11, and the non-mobile terminal may be a server, a Network Attached Storage (NAS), a Personal Computer (PC), a Television (TV), a teller machine, a kiosk, or the like, and the embodiments of the present application are not limited in particular.
The DNS cache flushing or flushing device in the embodiment of the present application may be a device having an operating system. The operating system may be an Android (Android) operating system, an ios operating system, or other possible operating systems, and embodiments of the present application are not limited specifically.
The DNS cache refreshing or clearing device provided in the embodiment of the present application can implement each process implemented by the method embodiment of fig. 3, and achieve the same technical effect, and is not described here again to avoid repetition.
As shown in fig. 7, the embodiment of the present application further provides a communication device 70, which includes a processor 71, a memory 72, and a program or an instruction stored on the memory 72 and executable on the processor 71, for example, when the communication device 70 is a terminal, the program or the instruction is executed by the processor 71 to implement the processes of the above DNS cache refreshing or clearing method embodiment, and the same technical effect can be achieved. When the communication device 70 is a core network device, the program or the instruction is executed by the processor 71 to implement the processes of the above-mentioned embodiment of the edge application server migration method, and the same technical effect can be achieved, and for avoiding repetition, the details are not described here again.
Fig. 8 is a schematic diagram of a hardware structure of a terminal implementing the embodiment of the present application. The terminal 80 includes but is not limited to: radio frequency unit 81, network module 82, audio output unit 83, input unit 84, sensor 85, display unit 86, user input unit 87, interface unit 88, memory 89, and processor 810.
Those skilled in the art will appreciate that the terminal 80 may further include a power source (e.g., a battery) for supplying power to various components, and the power source may be logically connected to the processor 810 through a power management system, so as to implement functions of managing charging, discharging, and power consumption through the power management system. The terminal structure shown in fig. 8 does not constitute a limitation of the terminal, and the terminal may include more or less components than those shown, or combine some components, or have a different arrangement of components, and thus will not be described again.
It should be understood that in the embodiment of the present application, the input Unit 84 may include a Graphics Processing Unit (GPU) 841 and a microphone 842, and the Graphics Processing Unit 841 processes image data of still pictures or videos obtained by an image capturing device (such as a camera) in a video capturing mode or an image capturing mode. The display unit 86 may include a display panel 861, and the display panel 861 may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like. The user input unit 87 includes a touch panel 871 and other input devices 872. Touch panel 871, also referred to as a touch screen. The touch panel 871 may include two parts of a touch detection device and a touch controller. Other input devices 872 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which are not described in detail herein.
In the embodiment of the present application, the radio frequency unit 81 receives downlink data from a network side device and then processes the downlink data in the processor 810; in addition, the uplink data is sent to the network side equipment. In general, the radio frequency unit 81 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.
The memory 89 may be used to store software programs or instructions as well as various data. The memory 89 may mainly include a stored program or instruction area and a stored data area, wherein the stored program or instruction area may store an operating system, an application program or instruction (such as a sound playing function, an image playing function, etc.) required for at least one function, and the like. Further, the Memory 89 may include a high-speed random access Memory, and may further include a nonvolatile Memory, wherein the nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable Programmable PROM (EPROM), an Electrically Erasable Programmable ROM (EEPROM), or a flash Memory. Such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device.
Processor 810 may include one or more processing units; alternatively, the processor 810 may integrate an application processor, which primarily handles operating systems, user interfaces, and applications or instructions, etc., and a modem processor, which primarily handles wireless communications, such as a baseband processor. It will be appreciated that the modem processor described above may not be integrated into processor 810.
The radio frequency unit 81 is configured to receive second information sent by a first core network device, where the second information is used to instruct the terminal to refresh a DNS cache record or to empty part or all of the DNS cache records;
and the processor 810 is configured to refresh the DNS cache record according to the second information, or flush all or part of the DNS cache record.
In the embodiment of the application, after the migration of the edge application server is completed, the terminal can refresh or empty the DNS cache according to the indication of the core network device, so that a new edge application server can be found when the DNS query process is restarted.
Optionally, the processor 810 is configured to refresh an IP address corresponding to a fully qualified domain name FQDN of an edge application server in a DNS cache of the terminal.
Optionally, the processor 810 is configured to empty all information in the DNS cache of the terminal, or empty the FQDN of the edge application server in the DNS cache of the terminal and the IP address corresponding to the FQDN.
The embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or the instruction is executed by a processor, the program or the instruction implements each process of the foregoing edge application server migration method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.
The embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or the instruction is executed by a processor, the program or the instruction implements each process of the above DNS cache refreshing or clearing method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.
Wherein, the processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and so on.
The embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run a network-side device program or an instruction, so as to implement each process of the above-mentioned edge application server migration method embodiment, and achieve the same technical effect, and in order to avoid repetition, the description is omitted here.
The embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run a network-side device program or an instruction, to implement each process of the above DNS cache refreshing or clearing method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.
It should be understood that the chips mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip or a system-on-chip, etc.
The embodiment of the present application further provides a program product, where the program product is stored in a non-volatile storage medium, and the program product is executed by at least one processor to implement each process of the foregoing edge application server migration method embodiment, and the same technical effect can be achieved, and in order to avoid repetition, details are not repeated here.
The embodiment of the present application further provides a program product, where the program product is stored in a non-volatile storage medium, and the program product is executed by at least one processor to implement each process of the above DNS cache refreshing or clearing method embodiment, and the same technical effect can be achieved, and in order to avoid repetition, details are not repeated here.
An embodiment of the present application further provides a core network device configured to execute the above edge application server migration method.
An embodiment of the present application further provides a terminal configured to execute the above DNS cache refreshing or clearing method.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. Further, it should be noted that the scope of the methods and apparatus of the embodiments of the present application is not limited to performing the functions in the order illustrated or discussed, but may include performing the functions in a substantially simultaneous manner or in a reverse order based on the functions involved, e.g., the methods described may be performed in an order different than that described, and various steps may be added, omitted, or combined. In addition, 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 will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present application may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present application.
While the present embodiments have been described with reference to the accompanying drawings, it is to be understood that the invention is not limited to the precise embodiments described above, which are meant to be illustrative and not restrictive, and that various changes may be made therein by those skilled in the art without departing from the spirit and scope of the invention as defined by the appended claims.

Claims (20)

1. An edge application server migration method executed by a first core network device, the method comprising:
after receiving first information, judging whether second information needs to be sent to a target terminal, wherein the first information is used for indicating that a source edge application server providing service support for the target terminal has been migrated to a target edge application server, and the second information is used for indicating the target terminal to refresh domain name system DNS cache records or empty part or all of the DNS cache records;
and when the second information needs to be sent to the target terminal, sending the second information to the target terminal.
2. The method of claim 1, wherein determining whether the second information needs to be sent to the target terminal comprises:
and judging whether second information needs to be sent to the target terminal according to the mode of whether the second core network equipment is adopted to replace the IP address of the edge application server and the core network session connection mode.
3. The method of claim 2, wherein determining whether the second information needs to be sent to the target terminal according to a mode of whether the second core network device is used to replace the IP address of the edge application server and a session connection mode of the core network comprises at least one of:
if the mode that second core network equipment replaces the IP address of the edge application server is adopted, judging that second information does not need to be sent to the target terminal;
if the mode that the IP address of the edge application server is not replaced by second core network equipment and the session connection mode of the core network is a session shunting mode, judging that second information needs to be sent to the target terminal;
and if the mode that the IP address of the edge application server is not replaced by the second core network equipment and the session connection mode of the core network is the other mode of the non-session shunting mode, judging that the second information does not need to be sent to the target terminal.
4. The method according to claim 2 or 3, wherein the second core network device is a User Plane Function (UPF).
5. The method of claim 3, wherein the other modes of the non-session offload mode comprise: distributed anchor mode and multi-PDU session mode.
6. The method of claim 1, further comprising:
and receiving the first information sent by an Application Function (AF).
7. The method of claim 1, wherein the first core network device is a Session Management Function (SMF).
8. A DNS cache refreshing or clearing method is executed by a terminal, and is characterized by comprising the following steps:
receiving second information sent by first core network equipment, wherein the second information is used for indicating the terminal to refresh DNS cache records or clear part or all of the DNS cache records;
and refreshing the DNS cache record according to the second information, or emptying all or part of the DNS cache record.
9. The method of claim 8, wherein refreshing the DNS cache record comprises:
and refreshing the IP address corresponding to the fully qualified domain name FQDN of the edge application server in the DNS cache of the terminal.
10. The method of claim 8, wherein flushing all or a portion of DNS cache records comprises:
and clearing all information in the DNS cache of the terminal, or clearing the FQDN of the edge application server in the DNS cache of the terminal and the IP address corresponding to the FQDN.
11. An edge application server migration apparatus, comprising:
the system comprises a judging module and a judging module, wherein the judging module is used for judging whether second information needs to be sent to a target terminal or not after first information is received, the first information is used for indicating that a source edge application server providing service support for the target terminal has been migrated to a target edge application server, and the second information is used for indicating the target terminal to refresh DNS cache records or empty all or part of the DNS cache records;
and the sending module is used for sending the second information to the target terminal when the second information needs to be sent to the target terminal.
12. The apparatus of claim 11, wherein the determining module is configured to determine whether the second information needs to be sent to the target terminal according to a mode of whether the second core network device replaces the IP address of the edge application server and a core network session connection mode.
13. The apparatus of claim 12, wherein the determining means comprises at least one of:
the first judgment submodule is used for judging that second information does not need to be sent to the target terminal if a mode that second core network equipment replaces an IP address of an edge application server is adopted;
the second judgment submodule is used for judging that second information needs to be sent to the target terminal if a mode that second core network equipment replaces an IP address of the edge application server is not adopted and a core network session connection mode is a session shunting mode;
and the third judging submodule is used for judging that the second information does not need to be sent to the target terminal if the mode that the second core network equipment replaces the IP address of the edge application server is not adopted and the session connection mode of the core network is the other mode of the non-session shunting mode.
14. The apparatus of claim 11, further comprising:
and the receiving module is used for receiving the first information sent by the AF.
15. A DNS cache refreshing or emptying device is characterized by comprising:
a receiving module, configured to receive second information sent by a first core network device, where the second information is used to instruct a terminal to refresh a DNS cache record or to clear part or all of the DNS cache record;
and the processing module is used for refreshing the DNS cache record according to the second information, or clearing all or part of the DNS cache record.
16. The apparatus of claim 15, wherein the processing module comprises:
and the refreshing submodule is used for refreshing the IP address corresponding to the FQDN of the edge application server in the DNS cache.
17. The apparatus of claim 15, wherein the processing module comprises:
and the emptying submodule is used for emptying all information in the DNS cache, or emptying the FQDN of the edge application server in the DNS cache and the IP address corresponding to the FQDN.
18. A core network device comprising a processor, a memory and a program or instructions stored on the memory and executable on the processor, the program or instructions when executed by the processor implementing the steps of the edge application server migration method according to any one of claims 1 to 7.
19. A terminal comprising a processor, a memory, and a program or instructions stored on the memory and executable on the processor, the program or instructions when executed by the processor implementing the steps of the DNS cache flushing or purging method according to any of claims 8 to 10.
20. A readable storage medium, on which a program or instructions are stored, which program or instructions, when executed by a processor, implement the edge application server migration method according to any one of claims 1 to 7, or the steps of the DNS cache flushing or flushing method according to any one of claims 8 to 10.
CN202011447141.XA 2020-12-09 2020-12-09 Method and device for migrating edge application server and refreshing or emptying DNS (domain name system) cache Pending CN114615270A (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202011447141.XA CN114615270A (en) 2020-12-09 2020-12-09 Method and device for migrating edge application server and refreshing or emptying DNS (domain name system) cache
PCT/CN2021/136145 WO2022121902A1 (en) 2020-12-09 2021-12-07 Edge application server migration and dns cache flushing or clearing method and apparatus

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202011447141.XA CN114615270A (en) 2020-12-09 2020-12-09 Method and device for migrating edge application server and refreshing or emptying DNS (domain name system) cache

Publications (1)

Publication Number Publication Date
CN114615270A true CN114615270A (en) 2022-06-10

Family

ID=81856391

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202011447141.XA Pending CN114615270A (en) 2020-12-09 2020-12-09 Method and device for migrating edge application server and refreshing or emptying DNS (domain name system) cache

Country Status (2)

Country Link
CN (1) CN114615270A (en)
WO (1) WO2022121902A1 (en)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110078229A1 (en) * 2009-09-25 2011-03-31 At&T Intellectual Property I, L.P. Method and apparatus for managing user endpoint devices in a communication network
CN106997306A (en) * 2016-01-26 2017-08-01 阿里巴巴集团控股有限公司 Physical machine Data Migration to high in the clouds methods, devices and systems
WO2018214638A1 (en) * 2017-05-25 2018-11-29 中兴通讯股份有限公司 Policy control method and device for user-plane function entity reselection, and storage medium
CN109788078A (en) * 2017-11-13 2019-05-21 华为技术有限公司 Application server switching method, equipment and system

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109547585A (en) * 2019-01-14 2019-03-29 中国雄安集团数字城市科技有限公司 A method of based on being switched fast for edge calculations cloud
CN110830606A (en) * 2019-10-31 2020-02-21 瑞斯康达科技发展股份有限公司 Method and device for solving abnormal DNS cache and computer readable storage medium

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110078229A1 (en) * 2009-09-25 2011-03-31 At&T Intellectual Property I, L.P. Method and apparatus for managing user endpoint devices in a communication network
CN106997306A (en) * 2016-01-26 2017-08-01 阿里巴巴集团控股有限公司 Physical machine Data Migration to high in the clouds methods, devices and systems
WO2017128992A1 (en) * 2016-01-26 2017-08-03 阿里巴巴集团控股有限公司 Method, device and system for migrating physical machine data to cloud
WO2018214638A1 (en) * 2017-05-25 2018-11-29 中兴通讯股份有限公司 Policy control method and device for user-plane function entity reselection, and storage medium
CN109788078A (en) * 2017-11-13 2019-05-21 华为技术有限公司 Application server switching method, equipment and system

Non-Patent Citations (8)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "S2-2000196 "Edge Application Server Discovery and selection using DNS"", 《3GPP TSG_SA\WG2_ARCH》 *
ERICSSON: "S2-2009165 "KI#2, sol#24 update."", 《3GPP TSG_SA\WG2_ARCH》 *
HUAWEI等: "S2-2008730 "KI#2, Update to Conclusions on UE DNS cache."", 《3GPP TSG_SA\WG2_ARCH》 *
INTEL等: "S2-2004314 "KI#2, New Solution: UE Agnostic EAS IP address replacement for traffic subject to edge computing."", 《3GPP TSG_SA\WG2_ARCH》 *
LENOVO等: "S2-2008919 "KI#2, Conclusion update on UE DNS cache."", 《3GPP TSG_SA\WG2_ARCH》 *
VIVO: "S2-2007251 "KI#2: Evaluation and Conclusion of Edge relocation."", 《3GPP TSG_SA\WG2_ARCH》 *
VIVO: "S2-2008671 "Evaluation and conclusion update to UE DNS cache renewal"", 《3GPP TSG_SA\WG2_ARCH》 *
ZTE: "S2-1903799 "Clarification on Nsmf_EventExposure_AppRelocationInfo"", 《3GPP TSG_SA\WG2_ARCH》 *

Also Published As

Publication number Publication date
WO2022121902A1 (en) 2022-06-16

Similar Documents

Publication Publication Date Title
US11025963B2 (en) Data processing method, apparatus, and system for live streaming page
EP3389300B1 (en) Method and apparatus for identifying pseudo base-station, and terminal
US10958459B2 (en) Method and apparatus for processing group chat message
US11425604B2 (en) User plane resource management method, user plane network element, and control plane network element
US10491535B2 (en) Adaptive data synchronization
JP6511541B2 (en) Message updating method, apparatus and terminal
US11627486B2 (en) Data sending method and apparatus, and device
US11096177B2 (en) Operation mode switching method and user equipment
WO2017107852A1 (en) Method and device for transmitting heartbeat packet
CN114339811A (en) Method and device for executing target operation and terminal equipment
US9838313B2 (en) Method, system, control device and node device for data transmission
CN114615270A (en) Method and device for migrating edge application server and refreshing or emptying DNS (domain name system) cache
EP3420750B1 (en) Using a single packet data network for data transfers to manage network resources
CN113923613B (en) Call processing method and device, electronic equipment and storage medium
CN110121216B (en) Session recovery method and device and computer storage medium
CN115150357B (en) Information processing method, device, terminal and network side equipment
EP3518513A1 (en) Streaming data acquisition method, device, and system
CN104615623A (en) Network resource obtaining method and device
CN103796289B (en) Method and terminal for achieving data traffic dial
WO2024037439A1 (en) Computing power task migration method and apparatus, and device
WO2023246756A1 (en) Computing power service method and apparatus, terminal, and core network device
CN113051103A (en) Data processing method and device and electronic equipment
JP2024522015A (en) RESOURCE PROCESSING METHOD, DEVICE, ELECTRONIC DEVICE, AND STORAGE MEDIUM
CN117835287A (en) Network function management method and device, electronic equipment and storage medium
CN105989039A (en) Picture processing method and device in mobile terminal

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
WD01 Invention patent application deemed withdrawn after publication

Application publication date: 20220610

WD01 Invention patent application deemed withdrawn after publication