A wireless communication method, platform, device and storage medium

Abstract

The application discloses a wireless communication method, a wireless communication platform, an electronic device and a computer readable storage medium, receiving first DNS configuration information associated with a first application network element sent by an edge computing server; the first DNS configuration information comprises at least one of a data network address, an application network element service identifier, a data network access identifier, a fully qualified domain name, a service filtering identifier and domain name system information; configuring the first DNS configuration information for a to-be-configured network element associated with the first application network element in a core network device, and sending DNS feedback information to the edge computing server; the DNS feedback information is used for indicating that the to-be-configured network element is successfully configured, or indicating that the to-be-configured network element fails to be configured. In this way, it is ensured that a terminal device can access services carried on the edge computing server through local DNS services.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of blockchains, and particularly relates to a wireless communication method, a wireless communication platform, an electronic device and a computer readable storage medium. BACKGROUND

[0002] As a new generation of broadband mobile communication technology, the 5th Generation Mobile Communication Technology (5G) has the advantages of large bandwidth, low latency, high speed, high reliability, high connectivity and ubiquitous network, and promotes the rapid development and change of vertical industries, such as the rise of smart medical care, smart education, smart agriculture and other directions. Mobile Edge Computing (MEC) as one of the key technologies of 5G evolution, is an Internet Technology (IT) general platform with wireless network information Application Programming Interface (API) interaction ability, and computing, storage, analysis functions; relying on MEC, traditional external applications can be pulled into mobile, closer to users, providing localized services, thereby improving user experience and bringing more value to edge networks. As a multi-access edge computing platform standard led by the European Telecommunications Standards Institute (ETSI), MEC provides more efficient business operation services through the application of MEC, platform, resource virtualization and service, to meet the differentiated needs of different businesses in processing capacity. Figure 1 is a MEC system framework diagram defined by ETSI standard. As shown in Figure 1As shown, the MEC system framework defined by the ETSI standard includes: a Customer-Facing Service Portal (CFS portal), a User Equipment Application (UE APP), a MEC system level management, a MEC host level management, a MEC host, and other MEC hosts. The MEC system level management includes an Operation Support System, a User app LCM proxy, and a MEC orchestrator (MEAO). The MEC host level management includes a MEC platform manager and a Virtualisation Infrastructure Manager. The MEC platform manager includes a MEC platform element mgmt, a MEC app rules & reqts mgmt, and a MEC app LCM. The MEC host includes a Virtualisation infrastructure, a MEC Application (MEC APP), and a MEC Platform (MEP). The MEP includes a MEC service, a Service Registry, a Domain Name System Handling (DNS Handling), and a Traffic rules Control. The Other MEC host includes Other MEC platform. The UE APP interacts with the User app LCM proxy through an Mx interface 2 (Mx2).The Operation Support System interacts with the User app LCM proxy through a mobile edge management (Mm) interface 8 (referred to as Mm8), interacts with the CFS protal through a Mx interface 1 (referred to as Mx1), interacts with the MEC platform element mgmt through a Mm interface 2 (referred to as Mm2), and interacts with the MEAO through a Mm interface 1 (referred to as Mm1). The MEAO interacts with the User app LCM proxy through a Mm interface 9 (referred to as Mm9), interacts with the MEC platform manager through a Mm interface 3 (referred to as Mm3), and interacts with the Virtualisation Infrastructure Manager through a Mm interface 4 (referred to as Mm4). The Virtualisation Infrastructure Manager interacts with the MEC platform manager through a Mm interface 6 (referred to as Mm6), and interacts with the Virtualisation Infrastructure through a Mm interface 7 (referred to as Mm7). The MEC platform manager interacts with the Data plane in the virtualization infrastructure through a mobile edge point (Mp) interface 2 (referred to as Mp2), interacts with the MEC APP through a Mp interface 1 (referred to as Mp1), and interacts with the Other MEC platform through a Mp interface 3 (referred to as Mp3).

[0003] Currently, the 3rd Generation Partnership Project (3GPP) gives a reference design for the combination of 5GC and MEC in the standards TS23.501 and TS23.502 as follows Figure 2 Figure 2 ​As shown, the MEC edge server includes a MEP (Mobile Application Program), a MEC APP (Multi-Application Component), and a Network Function Virtualized Infrastructure (NFVi). The MEP includes MEC Services and Application Functions (AFs). It's worth noting that AF functions are integrated into the MEC, providing better data flow control policies (coding policies, Quality of Service (QoS) policies, routing policies, etc.) for applications deployed on the MEC platform. The AF in the MEP connects to the ME APP via API. The 5G core network (5GC) includes Policy Control Function (PCF), Unified Data Management (UDM), Network Exposure Function (NEF), Access and Mobility Management Function (AMF), Session Management Function (SMF), and User Port Function (UPF). The AF in the MEP interacts with the NEF in the 5GC through Next Generation (NG) Interface 33 (N33). To enable low-latency, high-bandwidth, and high-reliability edge applications in vertical industries, the Uplink Filter (UPF) is deployed close to the MEC (Multi-access Edge Computing) within the campus. Data is forwarded to the MEC edge server via the UPF's local traffic offloading technology, specifically the Uplink Classifier / Internet Protocol Version 6 Branching Point (UL-CL / IPv6 BP). User Equipment (UE) interacts with the AMF (Advanced Feature Filter) in the 5GC (User Capacitor Center) through NG interface 1 (N1). The Radio Access Network (RAN) interacts with the AMF in the 5GC through NG interface 2 (N2). The RA (Radio Access Network) interacts with the UPF deployed in the campus through NG interface 3 (N3). The UPF deployed in the campus interacts with the SMF (Supervisory Feature Filter) in the 5GC through NG interface 4 (N4). The UPF deployed in the campus interacts with the UPF in the 5GC through NG interface 9 (N9). The UPF deployed in the campus interacts with the MEP (Multi-access Filter) in the 5GC through NG interface 6 (N6).

[0004] The introduction of the User Plane Function (UPF) is crucial for enabling data transmitted on the 5GC to be offloaded or diverted to the MEC platform. The UPF primarily provides user plane functions, responding to SMF requests through the N4 and being directly controlled and managed by the SMF, executing service flow processing according to various policies issued by the SMF. As the interaction point connecting the RAN with the 5GC medical edge cloud and data network (DN), the UPF supports user service data routing and forwarding, data and service identification, and action and policy execution. Simultaneously, as the routing and local diversion of 5G Standalone (SA) packets, it plays a key role in the converged MEC architecture of 5G networks. Currently, the UPF diversion capabilities defined in the TS23.501 and TS23.502 standards mainly include three modes: UL-CL, IPv6 Multi-homing, and Local Area Data Network (LADN). The first mode, UL-CL, uses local traffic splitting based on destination address. According to edge computing service requirements, when the UE moves to a certain location, the SMF inserts a local UPF for traffic splitting. The UPF filters uplink packet IP addresses based on the splitting rules (Uplink Classifier) ​​issued by the SMF, and splits packets that meet the rules to the local DN. The second mode, IPv6 Multi-homing, uses local traffic splitting based on source address. This mechanism utilizes the multi-homing feature of IPv6, using one of the UE's IPv6 addresses for edge computing services. The SMF selects a common local Branching Point UPF for traffic splitting based on the UE's location. Different IP anchors are separated through this Branching Point UPF. The Branching Point UPF filters uplink packet source IP addresses according to the splitting rules issued by the SMF, and packets that meet the rules are split to the local DN. Under the IPv6 Multi-homing mechanism, the UE needs to support IPv6 Multi-homing. A Protocol Data Unit (PDU) session is assigned two IPv6 prefixes, and the UE can detect and control data offloading. The third mode, LADN, performs local offloading based on a specific Data Network Name (DNN). LADN mode requires the UE to establish a new PDU session to access the local DN for edge computing services. After the UE successfully registers in the 5G core network, the AMF informs the UE of its LADN information (e.g., service area, LADN DNN).When a UE moves to the LADN service area, it initiates a PDU session. The SMF selects a local UPF based on the UE's location and routes the session to LADN. After the UE leaves the area, the SMF initiates session release. Under the LADN mechanism, the UE needs to support LADN and be able to detect and control data offloading.

[0005] As the number of applications hosted on the MEC increases, the three IP address-based local data offloading modes mentioned above will encounter at least two problems. First, the uncertainty and timeliness of IP addresses lead to significant signaling overhead or signaling storms between the 5GC and MEAO. To ensure application security, especially in industries with high security requirements such as healthcare and education, IP addresses have a certain timeliness. Outside of this timeframe, IP addresses may change. In such cases, to ensure the application's data flow can be properly offloaded on the UPF side, the MEAO needs to update its routing policy on the UPF side. This results in a large amount of signaling for traffic offloading policy (IP address) updates between the MEAO and 5GC, which can lead to signaling storms and severe signaling overhead, especially when there are hundreds or thousands of applications. Second, the uncertainty of IP addresses leads to extremely high overall system maintenance costs and a poor user experience. When IP addresses change, in addition to causing the aforementioned signaling storm problem... Meanwhile, for the UE (User Equipment), the destination address needs to be updated again; otherwise, service access will be interrupted. More importantly, when a UE carries multiple different services, multiple IP addresses need to be updated to ensure the connectivity of all services, resulting in a poor user experience. Therefore, to solve the above problems, we need to adopt the mature DNS mechanism in the industry. DNS resolves domain names into IP addresses, linking domain names and IP addresses together for service. On the Internet, when one host accesses another host, it must first know its IP address. IP addresses consist of four segments of numbers separated by ".", which are difficult to remember. Therefore, the Domain Name System (DNS) is used to manage the mapping between hostnames and IP addresses. Domain names are managed by the Internet Corporation for Assigned Names and Numbers (ICANN), a non-profit organization established to undertake functions such as DNS management, IP address allocation, protocol parameter configuration, and main server system management. The Internet Corporation for Assigned Names and Numbers (ICANN) sets up corresponding top-level domains for different countries or regions. These domain names usually consist of two English letters. For example, .uk represents the United Kingdom, and .fr represents France. The Chinese domain name is .cn, and domain names under .cn are managed by the China Internet Network Information Center (CNNIC). Domain name servers typically come in two forms: DNS servers and caching DNS servers. DNS servers provide DNS information to the world and provide the corresponding IP addresses; caching DNS servers cache the mapping relationship between domain names and IP addresses locally, enabling fast domain name resolution.

[0006] However, in related technologies, when DNS technology is applied to the converged architecture of 5GC and MEC, the default DNS server of 5GC points to the Internet DNS server, and all service access initiated by UE using DNS domain names is controlled by the resolution process of the Internet DNS server. For example... Figure 3 As shown, when a UE initiates an access to www.app1.com, the UE's DNS request is directly sent to an Internet DNS server. If the Internet DNS server does not have a resolution address for this domain name, the response returns empty. This results in the UE being unable to access applications on the MEC via DNS domain names. Furthermore, there is no reachable path between the UE and the MEC's ​​DNS server; if DNS is used to access applications on the MEC, the returned address is inaccessible. In this situation, for example, if the DNS address of application APP2 on the MEC is www.app2.com, when the UE initiates an access to this domain name, the 5GC first submits the UE's access information to the Internet DNS server, instead of pointing to the MEC's ​​DNS server; this leads to the final DNS service resolution failing. Therefore, the relevant technology at least suffers from the problem that DNS information cannot penetrate from the 5GC to the MEC system. Summary of the Invention

[0007] In view of this, this application provides a wireless communication method, a wireless communication platform, an electronic device, and a computer-readable storage medium, which solves the problem in the related art that DNS information cannot be penetrated from 5GC to the MEC system.

[0008] To achieve the above objectives, the technical solution of this application is implemented as follows:

[0009] A wireless communication method, the method comprising:

[0010] The system receives first DNS configuration information associated with a first application network element sent by an edge computing server; the first DNS configuration information includes a data network address, and at least one of the following: application network element service identifier, data network access identifier, fully qualified domain name, service filtering identifier, and domain name system information.

[0011] Configure the first DNS configuration information for the network element to be configured in the core network device that is associated with the first application network element, and send DNS feedback information to the edge computing server; the DNS feedback information is used to indicate that the network element to be configured has been successfully configured, or to indicate that the network element to be configured has failed to be configured.

[0012] A wireless communication platform, the platform comprising:

[0013] The receiving module is used to receive first DNS configuration information associated with the first application network element sent by the edge computing server; the first DNS configuration information includes a data network address, and at least one of the following: application network element service identifier, data network access identifier, fully qualified domain name, service filtering identifier, and domain name system information;

[0014] The processing module is used to configure the first DNS configuration information for the network element to be configured in the core network device that is associated with the first application network element, and to send DNS feedback information to the edge computing server; the DNS feedback information is used to indicate that the network element to be configured has been successfully configured, or to indicate that the network element to be configured has failed to be configured.

[0015] An electronic device, the electronic device comprising:

[0016] A memory for storing executable instructions; a processor for executing the executable instructions stored in the memory to implement the steps of the wireless communication method described above.

[0017] A computer-readable storage medium storing one or more applications that can be executed by one or more processors to implement the steps of the wireless communication method described above.

[0018] The wireless communication method, wireless communication platform, electronic device, and computer-readable storage medium provided in this application receive first DNS configuration information associated with a first application network element sent by an edge computing server. The first DNS configuration information includes a data network address, and at least one of the following: application network element service identifier, data network access identifier, fully qualified domain name, service filtering identifier, and domain name system information. The method configures the first DNS configuration information for the network element to be configured in the core network device associated with the first application network element, and sends DNS feedback information to the edge computing server. The DNS feedback information indicates whether the network element to be configured has been successfully configured or has failed to be configured. In other words, this application provides a DNS domain name configuration and resolution method between a 5GC and an MEC server, solving the problem in related technologies where DNS information cannot penetrate from the 5GC to the MEC system. By pre-configuring DNS configuration information for the network element to be configured in the 5GC through the application network element, when a terminal device receives a DNS request, it can determine whether the server responding to the DNS request is the MEC DNS server or the Internet DNS server based on the configured DNS configuration information. This ensures that the terminal device accesses the services carried on the MEC through the local DNS service. Attached Figure Description

[0019] Figure 1 This is a diagram of the MEC system framework defined by the ETSI standard in related technologies;

[0020] Figure 2 This is a reference design diagram of the combination of 5GC and MEC provided by related technologies. Figure 1 ;

[0021] Figure 3 This is a reference design diagram of the combination of 5GC and MEC provided by related technologies. Figure 2 ;

[0022] Figure 4 This is a schematic structural diagram of the wireless communication system provided in the embodiments of this application;

[0023] Figure 5 This is an illustrative flowchart of the wireless communication method provided in the embodiments of this application. Figure 1 ;

[0024] Figure 6 This is an illustrative flowchart of the wireless communication method provided in the embodiments of this application. Figure 2 ;

[0025] Figure 7 This is an illustrative flowchart of the wireless communication method provided in the embodiments of this application. Figure 3 ;

[0026] Figure 8 This is a flowchart illustrating the communication between the UE and the DNS server at the service layer, as provided in an embodiment of this application.

[0027] Figure 9 This is a schematic block diagram of a wireless communication platform according to an embodiment of this application;

[0028] Figure 10 This is a schematic structural diagram of an electronic device provided in an embodiment of this application. Detailed Implementation

[0029] To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings. The described embodiments should not be regarded as limitations on this application. All other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0030] In the following description, references to "some embodiments" refer to a subset of all possible embodiments. However, it is understood that "some embodiments" may be the same or different subsets of all possible embodiments and may be combined with each other without conflict. Unless otherwise defined, all technical and scientific terms used in the embodiments of this application have the same meaning as commonly understood by one of ordinary skill in the art to which the embodiments of this application pertain. The terminology used in the embodiments of this application is for the purpose of describing the embodiments of this application only and is not intended to limit the application.

[0031] Figure 4 This is a schematic diagram of a wireless communication system according to an embodiment of this application.

[0032] like Figure 4 As shown, the communication system 400 may include a terminal device 410 and a network device 420. The network device 420 can communicate with the terminal device 410 via an air interface. Multi-service transmission is supported between the terminal device 410 and the network device 420.

[0033] It should be understood that the embodiments of this application are only illustrated by way of example, using communication system 400, but the embodiments of this application are not limited thereto. That is to say, the technical solutions of the embodiments of this application can be applied to various communication systems, such as: Long Term Evolution (LTE) system, LTE Time Division Duplex (TDD), Universal Mobile Telecommunication System (UMTS), Internet of Things (IoT) system, Narrow Band Internet of Things (NB-IoT) system, enhanced Machine-Type Communications (eMTC) system, 5G communication system, also known as New Radio (NR) communication system, or future communication systems, etc.

[0034] exist Figure 4 In the communication system 400 shown, network device 420 may be an access network device that communicates with terminal device 410. The access network device can provide communication coverage for a specific geographical area and can communicate with terminal device 410 (e.g., user equipment) located within that coverage area.

[0035] Network device 420 may be an MEC server, an evolved Node B (eNB or eNodeB) in a Long Term Evolution (LTE) system, a Next Generation Radio Access Network (NG RAN) device, a next generation Node B (gNB) in a 5G mobile communication system, a radio controller in a Cloud Radio Access Network (CRAN), or a relay station, access point, vehicle-mounted device, wearable device, hub, switch, bridge, router, or a network device in a future evolved Public Land Mobile Network (PLMN), or a base station in a future mobile communication system, an access node in a wireless fidelity (Wi-Fi) system, or one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G system.

[0036] Terminal device 410 includes, but is not limited to, any terminal device that is connected to network device 420 or other terminal devices via wired or wireless connection.

[0037] For example, the terminal device 410 can refer to an access terminal, UE, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user equipment. The access terminal can be a cellular phone, cordless phone, Session Initiation Protocol (SIP) phone, IoT device, satellite handheld terminal, Wireless Local Loop (WLL) station, Personal Digital Assistant (PDA), handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, in-vehicle device, wearable device, terminal device in a 5G network, or terminal device in a future evolved network, etc.

[0038] Terminal device 410 can be used for device-to-device (D2D) communication.

[0039] The wireless communication system 400 may further include a core network device 430 that communicates with the base station. This core network device 430 may be a 5GC device, such as an Access and Mobility Management Function (AMF) device, an Authentication Server Function (AUSF) device, a User Plane Function (UPF) device, or a Session Management Function (SMF) device. Optionally, the core network device 430 may also be an Evolved Packet Core (EPC) device for an LTE network, such as a Session Management Function + Core Packet Gateway (SMF+PGW-C) device. It should be understood that SMF+PGW-C can simultaneously implement the functions of both SMF and PGW-C. During network evolution, the names of the aforementioned core network devices may change, or new network entities may be formed by dividing the core network functions; this embodiment does not limit this.

[0040] The various functional units in the communication system 400 can also communicate with each other through a next-generation (NG) network interface.

[0041] For example, terminal equipment establishes an air interface connection with access network equipment through the NR interface for transmitting user plane data and control plane signaling; terminal equipment can establish a control plane signaling connection with AMF through N1; access network equipment, such as next-generation radio access base station (gNB), can establish a user plane data connection with UPF through N3; access network equipment can establish a control plane signaling connection with AMF through N2; UPF can establish a control plane signaling connection with SMF through N4; UPF can interact with the data network to exchange user plane data through N6; AMF can establish a control plane signaling connection with SMF through N11; and SMF can establish a control plane signaling connection with PCF through N7.

[0042] Figure 4 An exemplary embodiment shows a base station, a core network device, and two terminal devices. Optionally, the wireless communication system 400 may include multiple base station devices, and each base station may include other numbers of terminal devices within its coverage area. This application embodiment does not limit this.

[0043] It should be noted that, Figure 4This application merely illustrates the system to which this application applies; of course, the methods shown in the embodiments of this application can also be applied to other systems. Furthermore, the terms "system" and "network" are often used interchangeably herein. The term "and / or" in this application merely describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this application generally indicates that the preceding and following related objects have an "or" relationship. It should also be understood that "instruction" mentioned in the embodiments of this application can be a direct instruction, an indirect instruction, or an indication of a related relationship. For example, A instructing B can mean that A directly instructs B, for example, B can be obtained through A; it can also mean that A indirectly instructs B, for example, A instructs C, B can be obtained through C; or it can mean that there is a related relationship between A and B. It should also be understood that "correspondence" mentioned in the embodiments of this application can indicate a direct or indirect correspondence between two things, or an related relationship between two things, or a relationship of instruction and being instructed, configuration and being configured, etc. It should also be understood that the "predefined" or "predefined rules" mentioned in the embodiments of this application can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including terminal devices and network devices), and this application does not limit the specific implementation method. For example, predefined can refer to those defined in a protocol. It should also be understood that in the embodiments of this application, the "protocol" can refer to standard protocols in the field of communication, such as LTE protocol, NR protocol, and related protocols applied to future communication systems, and this application does not limit this.

[0044] To facilitate understanding of the technical solutions of the embodiments of this application, the relevant technologies of the embodiments of this application are described below. The following relevant technologies are optional solutions and can be combined with the technical solutions of the embodiments of this application in any way, and they all fall within the protection scope of the embodiments of this application.

[0045] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of this application only and is not intended to limit this application.

[0046] Figure 5 This is a flowchart illustrating a wireless communication method provided in an embodiment of this application, as shown below. Figure 5 As shown, this method is applied to Figure 4 The wireless communication system 400 shown includes a method comprising:

[0047] Step 501: Receive the first DNS configuration information associated with the first application network element sent by the edge computing server;

[0048] The first DNS configuration information includes the data network address, and at least one of the following: application network element service identifier, data network access identifier, fully qualified domain name, service filtering identifier, and domain name system information.

[0049] In this embodiment, AF is an application network element used to convey the application side's requirements to the network side, such as QoS requirements. AF can be a third-party functional entity or an application service deployed by the operator, such as the IP Multimedia Subsystem (IMS) voice call service.

[0050] In some embodiments, the data network address includes a data network name (DNN) and single network slice selection assistance information (S-NSSAI). The DNN has the same meaning and carries the same information as the access point name (APN). The DNN is a parameter that a terminal device must configure when accessing the network, determining the access method used. The S-NSSAI identifies different slices of the network the terminal device wants to access, including the slice / service type (SST) and the slice differentialist (SD). S-NSSAI is divided into standard S-NSSAI, which consists of SSTs with standardized SST values ​​and no SD, and non-standard S-NSSAI, which consists of SSTs and SDs, or only SSTs without standardization and no SD. The non-standard S-NSSAI identifies a single network slice within its associated Public Land Mobile Network (PLMN). Except for PLMNs associated with S-NSSAI, UEs must not use S-NSSAI with non-standard values ​​during access stratum procedures in any PLMN.

[0051] In some embodiments, the application network element service identifier (AF-Service-Identifier, AF ID) is used to characterize the service identifier for the request issued by the AF. The 5G Core maps this identifier to the target DNN and slice information (S-NSSAI).

[0052] In some embodiments, a Data Network Access Identifier (DNAI) is an identifier used by the user plane to access one or more DNs where applications are deployed. It should be noted that one DNAI can correspond to multiple DNNs, and one DNN can only correspond to one DNAI, to ensure the correctness of routing.

[0053] In some embodiments, a fully qualified domain name (FQDN) refers to a hostname plus a full path that lists all domain members in the sequence.

[0054] In some embodiments, the service filtering identifier is used to identify the filtering information of the target service. The filtering information of the target service includes, but is not limited to, the IP 5-tuple or the Media Access Control Address (MAC address); wherein, the IP 5-tuple includes the IP address, source port, destination IP address, destination port and transport layer protocol.

[0055] In some embodiments, Domain Name System (DNS) information is used to describe the DNS domain name information corresponding to the AF ID information. For example, consider two application network elements, APP1 and APP2, deployed separately. The DNS server can provide services to all applications with the same DNN / S-NSSAI in the same area, as it is now configured for each PDU session; therefore, the example deployment shows the normal situation. In the example, L-DNS1 serves the applications deployed within DNAI1 / EDN1 and DNAI2 / EDN2, and L-DNS2 serves the applications deployed within DNAI3 / EDN3 and DNAI4 / EDN4. Table 1 shows the service routing information for each application in related technologies and the DNS configuration information required for locally deployed applications; Table 2 shows the first DNS configuration information associated with the first application network element sent by the edge computing server received by the 5GC in this application.

[0056] Table 1

[0057]

[0058] Table 2

[0059]

[0060] By comparing Table 1 and Table 2, the first DNS configuration information received by 5GC in this application is richer than the DNS configuration information in related technologies.

[0061] Step 502: Configure the first DNS configuration information for the network element to be configured in the core network device that is associated with the first application network element, and send DNS feedback information to the edge computing server.

[0062] The DNS feedback information is used to indicate whether the network element to be configured has been successfully configured or has failed to be configured.

[0063] In this embodiment, the edge computing server sends first DNS configuration information associated with the first application network element to the core network device, and the core network device receives the first DNS configuration information. The core network device configures the first DNS configuration information for the network element to be configured, that is, it sequentially sends the first DNS configuration information to each network element in the core network device associated with the first application network element.

[0064] Here, the network elements to be configured include, but are not limited to, user plane network elements (UPF), access management network elements (AMF), network open network elements (NEF), policy control network elements (PCF), and data management network elements (UDM).

[0065] It should be noted that the UPF is used for packet routing and forwarding, QoS processing of user plane data, and packet probing and policy rule enforcement. The AMF is used for session management, UE IP address allocation and management, selection of manageable UPF network elements, interaction of session information related to the access network via the AMF, endpoints for policy control and charging function interfaces, and downlink data notification. The NEF is used to securely expose services and capabilities provided by 3GPP network functions to the outside world. The PCF is a unified policy framework guiding network behavior, providing policy rule information to control plane function network elements (such as AMF, SMF, etc.). The UDM is used to implement functions such as user identification, access authentication, registration, and mobility management.

[0066] This application discloses a wireless communication method, comprising: receiving first DNS configuration information associated with a first application network element sent by an edge computing server; the first DNS configuration information includes a data network address, and at least one of an application network element service identifier, a data network access identifier, a fully qualified domain name, a service filtering identifier, and domain name system information; configuring DNS configuration information for a network element to be configured in the core network device associated with the first application network element, and sending DNS feedback information to the edge computing server; the DNS feedback information is used to indicate that the network element to be configured has been successfully configured, or to indicate that the network element to be configured has failed to be configured. In other words, this application provides a DNS domain name configuration and resolution method between a 5GC and an MEC server, solving the problem in related technologies where DNS information cannot penetrate from the 5GC to the MEC system. By pre-configuring DNS configuration information for the network element to be configured in the 5GC by the application network element, when a terminal device receives a DNS request, it can determine whether the server responding to the DNS request is the MEC DNS server or the Internet DNS server based on the configured DNS configuration information. This ensures that the terminal device accesses the services carried on the MEC through the local DNS service.

[0067] Figure 6 This is a flowchart illustrating a wireless communication method provided in an embodiment of this application, as shown below. Figure 6 As shown, this method is applied to Figure 4 The wireless communication system 400 shown includes a method comprising:

[0068] Step 601: Receive the first DNS configuration information sent by the edge computing server through the first application network element via the network open network element in the core network device, and store the first DNS configuration information in the data storage network element in the core network device.

[0069] In this embodiment, the AF (Area Function) in the edge computing server sends the first DNS configuration information to the network open element. This first DNS configuration information passes through the data storage element (UDR), the policy control element (PCF), and the waiting configuration element, and is finally sent to the SMF (Site Management Element). The SMF uses the first DNS configuration information to determine the data network access identifier or data network address. When a terminal device initiates a DNS request message, the SMF can determine the DNS server that the terminal device wants to access based on the data network access identifier or data network address determined by the first DNS configuration information.

[0070] In this embodiment, the first DNS configuration information is carried by a message on the interface of the mobile edge platform via the Internet Protocol (IP) data stream. For example, taking the interface (Mp)2 of the mobile edge platform (Mp2 for short) as an example, the 5GC receives the first DNS configuration information associated with the first application network element carried by the edge computing server through the MP2 interface of the N6 tunnel. Table 3 shows the specific content of the first DNS configuration information carried by the MP2 interface message, and Table 4 shows the DNS Information parameter list corresponding to the MP2 interface.

[0071] Table 3

[0072]

[0073] Table 4

[0074]

[0075] In this embodiment, the first DNS configuration information is carried through an Application Function Request (AF Request) message. The first DNS configuration information is carried based on the AF Request. Based on the AF Request standard interface defined by 3GPP, the AF Request interface is used to configure DNS parameters in order to carry the first DNS configuration information. Table 5 shows the specific content of the first DNS configuration information carried based on the AF Request, and Table 6 shows the list of DNS Information parameters corresponding to the AF Request.

[0076] Table 5

[0077]

[0078] Table 6

[0079]

[0080] Step 602: Check whether the data network address and / or data network access identifier in the first DNS configuration information are valid.

[0081] Step 603: If the data network address and / or data network access identifier are valid, configure the first DNS configuration information for the network element to be configured, and generate DNS feedback information indicating whether the first DNS configuration information has been successfully configured.

[0082] The DNS feedback information is used to indicate whether the network element to be configured has been successfully configured or has failed to be configured.

[0083] In this embodiment, when the core network device receives a first DNS configuration message from the AF in the edge computing server, it verifies the elements in the first DNS configuration message as follows and provides feedback on whether the configuration was successful. First, it verifies the data network address. If the data network address in the first DNS configuration message does not exist, it returns "data network address does not exist" to the AF in the edge computing server and terminates the configuration process for the corresponding network element (such as UPF, NEF, etc.) in the 5GC. Otherwise, the Data Network Access Identifier (DNAI) is verified. If the DNAI in the service routing information of the first DNS configuration message does not exist, the AF function is notified that "the DNAI in the service routing information does not exist," and the configuration process for the corresponding network element (such as UPF, NEF, etc.) in the 5GC is terminated. Otherwise, the 5GC network element function is verified. That is, after the 5GC receives the first DNS configuration information sent by the AF, it sends the first DNS configuration information to the UPF or NEF network element through the relevant interface. If one of them fails, the 5GC reports the reason for the configuration execution failure to the AF. For example, if the UPF reports execution failure, the 5GC reports "UPF execution failure" to the AF; if the NEF reports execution failure, the 5GC reports "NEF execution failure" to the AF; if multiple network elements report execution failure at the same time, the 5GC reports the multiple network elements that failed to execute to the AF; otherwise, the 5GC reports that the first DNS configuration information was executed successfully to the AF.

[0084] Step 604: If the terminal device successfully connects to the core network device, obtain the first domain name address of the DNS server corresponding to the user plane network element.

[0085] In this embodiment of the application, after the terminal device (e.g., UE) connects to 5GC, it obtains the DNS server address on the UPF side.

[0086] Step 605: Receive a DNS request message sent by the terminal device. The DNS request message includes the second domain name address of the second application network element that the terminal device wants to access.

[0087] The second application network element and the first application network element may be the same or different.

[0088] In this embodiment, the second domain name address is the address of the DNS server that the terminal device wants to access. The DNS server to be accessed includes the application network element corresponding to the application that the terminal device wants to access, i.e., the second application network element. The terminal device can send a DNS request message to the DNS server to be accessed. If the DNS server to be accessed has a resolution address corresponding to the second domain name address, it will return the IP address corresponding to the second domain name address.

[0089] Step 606: Based on the first domain name address, the second domain name address, and the second DNS configuration information of the second application network element, determine the IP address corresponding to the second domain name address of the second application network element that the terminal device wants to access.

[0090] In this embodiment of the application, step 606, based on the first domain name address, the second domain name address, and the second DNS configuration information of the second application network element, determines the IP address corresponding to the second domain name address of the second application network element to be accessed by the terminal device. This can be achieved through steps A1 to A3, or through steps A1 and A4, or through step A5.

[0091] Step A1: If the first domain name address is different from the second domain name address, determine whether there is DNS configuration information corresponding to the second application network element in the edge computing server.

[0092] In this embodiment, if the first domain name address corresponding to the DNS server on the UPF side is different from the second domain name address of the second application network element in the DNS request message, the matching fails. The terminal determines the distribution strategy based on the DNN subscription channel. If it has subscribed to the local MEC, it is directly transferred to the DNS server of the local MEC; if it has not subscribed to the local MEC, it is distributed to the Internet DNS server. Here, "subscription" refers to whether the configuration information corresponding to the second application network element has been successfully configured in advance in the network element to be configured in the core network device.

[0093] Step A2: If the edge computing server has DNS configuration information corresponding to the second application network element, obtain the second DNS configuration information corresponding to the second application network element from the data storage network element UDR in the core network device.

[0094] In this embodiment of the application, if the edge computing server has DNS configuration information corresponding to the second application network element, that is, the second DNS configuration information is successfully configured in the network element to be configured in the core network device, the second DNS configuration information corresponding to the second application network element is obtained from the data storage network element UDR in the core network device.

[0095] Step A3: Based on the second DNS configuration information, determine the edge computing DNS server that the terminal device wants to access, and resolve the IP address corresponding to the second domain name address of the second application network element that the terminal device wants to access based on the edge computing DNS server.

[0096] In this embodiment of the application, whether it is a DNS server distributed to the local MEC or a DNS server on the Internet, it will eventually return a matching result. If the match is successful, the IP address is obtained for business access; if the match is unsuccessful, the resolution failure is returned.

[0097] Step A4: If the core network device does not have DNS configuration information corresponding to the second application network element, send a DNS request message to the Internet DNS server, and resolve the IP address corresponding to the second domain name address of the second application network element that the terminal device wants to access based on the Internet DNS server.

[0098] In this embodiment of the application, if the edge computing server does not have DNS configuration information corresponding to the second application network element, that is, if the configuration of the second DNS configuration information in the network element to be configured in the core network device fails or the second DNS configuration information is not configured in the network element to be configured in the core network device, the DNS request message is sent to the Internet DNS server, and the IP address corresponding to the second domain name address of the second application network element to be accessed by the terminal device is resolved based on the Internet DNS server.

[0099] Step A5: If the first domain name address is the same as the second domain name address, send a DNS response message to the terminal device. The DNS response message includes the IP address corresponding to the second domain name address.

[0100] In this embodiment, if the first domain name address and the second domain name address are the same, the match is successful, and the DNS server on the UPF is used to determine the IP address corresponding to the second domain name address.

[0101] Figure 7 This is a schematic flowchart of the wireless communication method provided in the embodiments of this application.

[0102] Step 701: The AF functional entity sends DNS configuration information to the 5GC. The sender of this information is the AF functional entity (deployed above the MEC), and the receiver is the 5GC. The network elements within the 5GC include the UPF, NEF, and SMF. The DNS configuration information can be carried via the IP data stream N6 interface or via an AF request message.

[0103] Step 702: 5GC receives DNS configuration information, verifies whether the DNS configuration information is valid, and configures the DNS configuration information for the network element to be configured; if valid, it completes the configuration work for UPF, SMF and other related networks according to the transmitted configuration information.

[0104] Step 703: 5GC sends DNS configuration feedback information to the AF functional entity. The sender of this information is any functional entity involved with 5GC, including UPF, NEF, and even SMF; the receiving entity is AF. This information allows determination of whether DNS configuration was successful, and if so, the reason for failure.

[0105] Step 704: The UE performs service communication.

[0106] Figure 8This is a flowchart of the communication between the UE and the DNS server at the service layer, as provided in this application.

[0107] Step 801: Connect the terminal device to 5GC and proceed to step 802.

[0108] Step 802: Return the DNS server address of UPF and proceed to step 803.

[0109] Step 803: The terminal device initiates a DNS request, proceeding to step 804. It should be noted that the DNS request includes the address of the application network element that the terminal device wants to access.

[0110] Step 804: Determine whether the DNS server address of the UPF is the same as the address corresponding to the application network element that the terminal device wants to access. If they are the same, proceed to step 805; if they are not the same, proceed to step 806.

[0111] Step 805: Return the IP address of the application network element that the terminal device wants to access.

[0112] Step 806: Determine the distribution strategy based on the DNN channel subscribed by the terminal device, and proceed to step 807. Specifically, determining the distribution strategy based on the DNN channel subscribed by the terminal device involves checking if the DNS configuration information corresponding to the application network element that the terminal device wants to access exists in the 5GC.

[0113] Step 807: Whether to sign up for a MEC DNS server. If you have signed up for a MEC DNS server, proceed to step 808; if you have not signed up for a MEC DNS server, proceed to step 810.

[0114] Step 808: Distribute the DNS request to the MEC DNS server, and proceed to step 809.

[0115] Step 809: The MEC DNS server returns the IP address of the application network element that the terminal device wants to access.

[0116] Step 810: Distribute the DNS request to the Internet DNS server, and proceed to step 811.

[0117] Step 811: The Internet DNS server returns the IP address of the application network element that the terminal device wants to access.

[0118] Embodiments of this application provide a wireless communication platform, the terminal device of which can be used to implement... Figure 5 , Figure 6 A corresponding embodiment provides a wireless communication method, referring to... Figure 9 As shown, the wireless communication platform 9 includes:

[0119] The receiving module 901 is used to receive first DNS configuration information associated with the first application network element sent by the edge computing server; the first DNS configuration information includes a data network address, and at least one of the following: application network element service identifier, data network access identifier, fully qualified domain name, service filtering identifier, and domain name system information;

[0120] The processing module 902 is used to configure the first DNS configuration information for the network element to be configured in the core network device that is associated with the first application network element, and to send DNS feedback information to the edge computing server; the DNS feedback information is used to indicate that the network element to be configured has been configured successfully, or to indicate that the network element to be configured has failed to be configured.

[0121] In other embodiments of this application, the processing module 902 is used to receive first DNS configuration information sent by the edge computing server through the first application network element through the network open network element in the core network device, and store the first DNS configuration information in the data storage network element in the core network device.

[0122] In other embodiments of this application, the processing module 902 is used to detect whether the data network address and / or data network access identifier in the first DNS configuration information are valid;

[0123] The processing module 902 is also used to configure first DNS configuration information for the network element to be configured when the data network address and / or data network access identifier are valid, and to generate DNS feedback information indicating whether the first DNS configuration information has been successfully configured.

[0124] In other embodiments of this application, the first DNS configuration information is carried by a message on the interface of the mobile edge platform of the Internet Protocol data stream; or, the first DNS configuration information is carried by an application function request message.

[0125] In other embodiments of this application, the processing module 902 is used to obtain the first domain name address of the DNS server corresponding to the user plane network element when the terminal device successfully connects to the core network device.

[0126] The receiving module 901 is used to receive a DNS request message sent by the terminal device. The DNS request message includes the second domain name address of the second application network element that the terminal device wants to access.

[0127] The processing module 902 is also used to determine the IP address corresponding to the second domain name address of the second application network element to be accessed by the terminal device based on the first domain name address, the second domain name address, and the second DNS configuration information of the second application network element.

[0128] In other embodiments of this application, the processing module 902 is configured to, if the edge computing server has DNS configuration information corresponding to the second application network element, obtain the second DNS configuration information corresponding to the second application network element from the data storage network element UDR in the core network device; based on the second DNS configuration information, determine the edge computing DNS server to be accessed by the terminal device, and resolve the IP address corresponding to the second domain name address of the second application network element to be accessed by the terminal device based on the edge computing DNS server.

[0129] In other embodiments of this application, the processing module 902 is used to send a DNS request message to an Internet DNS server if there is no DNS configuration information corresponding to the second application network element in the core network device, and resolve the IP address corresponding to the second domain name address of the second application network element to be accessed by the terminal device based on the Internet DNS server.

[0130] In other embodiments of this application, the processing module 902 is used to send a DNS response message to the terminal device if the first domain name address is the same as the second domain name address. The DNS response message includes the IP address corresponding to the second domain name address.

[0131] The descriptions of the above device embodiments are similar to those of the above method embodiments, and have similar beneficial effects. For technical details not disclosed in the device embodiments of this application, please refer to the descriptions of the method embodiments of this application for understanding.

[0132] It should be noted that, in the embodiments of this application, if the above-described test data generation method is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiments of this application, or the part that contributes to the related technology, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a terminal device to execute all or part of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, mobile hard drives, read-only memory (ROM), magnetic disks, or optical disks. Thus, the embodiments of this application are not limited to any specific hardware and software combination.

[0133] This application provides an electronic device that can be applied to... Figure 5 , Figure 6 In one information processing method provided in the corresponding embodiment, referring to Figure 10 As shown, the electronic device 10 includes: a processor 1001, a memory 1002, and a communication bus 1003, wherein:

[0134] The communication bus 1003 is used to realize the communication connection between the processor 1001 and the memory 1002.

[0135] The processor 1001 is used to execute the information processing program stored in the memory 1002 to achieve, for example... Figure 5 , Figure 5 The corresponding embodiment provides a wireless communication method.

[0136] Based on the foregoing embodiments, embodiments of this application provide a computer-readable storage medium that stores one or more applications, which can be executed by one or more processors to achieve, as Figure 5 , Figure 6 The corresponding embodiment provides a wireless communication method.

[0137] It should be noted that the aforementioned computer-readable storage media can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic random access memory (FRAM), flash memory, magnetic surface memory, optical disc, or compact disc read-only memory (CD-ROM), etc.; or it can be various electronic devices that include one or any combination of the above-mentioned memories, such as mobile phones, computers, tablet devices, personal digital assistants, etc.

[0138] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0139] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0140] 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 necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0141] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer application products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer application instructions. These computer application instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0142] These computer application instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0143] These computer application instructions can also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0144] The above are merely preferred embodiments of this application and do not limit the patent scope of this application. Any equivalent structural or procedural transformations made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of this application.

Claims

1. A wireless communication method, characterized in that, The method includes: The edge computing server receives first DNS configuration information associated with the first application network element, sent by the first application network element; the first DNS configuration information includes a data network address, and at least one of the following: application network element service identifier, data network access identifier, fully qualified domain name, service filtering identifier, and domain name system information. Configure the first DNS configuration information for the network element to be configured in the core network device that is associated with the first application network element, and send DNS feedback information to the edge computing server; the DNS feedback information is used to indicate that the network element to be configured is configured successfully, or to indicate that the network element to be configured is configured unsuccessfully; the network element to be configured includes user plane network element, access management network element, network open network element, and data management network element; If the terminal device successfully connects to the core network device, obtain the first domain name address of the DNS server corresponding to the user plane network element; Receive a DNS request message sent by the terminal device, the DNS request message including the second domain name address of the second application network element that the terminal device wants to access; Based on the first domain name address, the second domain name address, and the second DNS configuration information of the second application network element, the first server to be accessed by the terminal device is determined, and based on the first server, the IP address corresponding to the second domain name address of the second application network element to be accessed by the terminal device is determined; wherein, the first server includes an edge computing DNS server or an Internet DNS server.

2. The method according to claim 1, characterized in that, The first DNS configuration information associated with the first application network element, sent by the edge computing server through the first application network element, includes: The core network device receives the first DNS configuration information sent by the edge computing server through the first application network element via the network open network element, and stores the first DNS configuration information in the data storage network element of the core network device.

3. The method according to claim 1, characterized in that, The process of configuring the DNS configuration information for the network element to be configured in the core network device that is associated with the first application network element includes: Detect whether the data network address and / or the data network access identifier in the first DNS configuration information are valid; If the data network address and / or the data network access identifier are valid, configure the first DNS configuration information for the network element to be configured, and generate DNS feedback information indicating whether the first DNS configuration information has been successfully configured.

4. The method according to any one of claims 1 to 3, characterized in that, The first DNS configuration information is carried in a message via the interface of the mobile edge platform of the Internet Protocol data stream; or, the first DNS configuration information is carried in an application function request message.

5. The method according to claim 1, characterized in that, The step of determining the first server to be accessed by the terminal device based on the first domain name address, the second domain name address, and the second DNS configuration information of the second application network element, and determining the IP address corresponding to the second domain name address of the second application network element to be accessed by the terminal device based on the first server, includes: If the first domain name address is different from the second domain name address, determine whether there is DNS configuration information corresponding to the second application network element in the edge computing server; If DNS configuration information corresponding to the second application network element exists in the edge computing server, the second DNS configuration information corresponding to the second application network element is obtained from the data storage network element in the core network device. Based on the second DNS configuration information, the edge computing DNS server that the terminal device wants to access is determined, and the IP address corresponding to the second domain name address of the second application network element that the terminal device wants to access is resolved based on the edge computing DNS server.

6. The method according to claim 5, characterized in that, The method further includes: If the core network device does not have DNS configuration information corresponding to the second application network element, the DNS request message is sent to the Internet DNS server, and the IP address corresponding to the second domain name address of the second application network element to be accessed by the terminal device is resolved based on the Internet DNS server.

7. The method according to claim 1, characterized in that, The method further includes: If the first domain name address is the same as the second domain name address, a DNS response message is sent to the terminal device, and the DNS response message includes the IP address corresponding to the second domain name address.

8. A wireless communication platform, characterized in that, The wireless communication platform includes: The receiving module is used to receive first DNS configuration information associated with the first application network element sent by the edge computing server through the first application network element; the first DNS configuration information includes a data network address, and at least one of the following: application network element service identifier, data network access identifier, fully qualified domain name, service filtering identifier, and domain name system information; The processing module is used to configure the first DNS configuration information for the network element to be configured in the core network device that is associated with the first application network element, and to send DNS feedback information to the edge computing server; the DNS feedback information is used to indicate that the network element to be configured is configured successfully, or to indicate that the network element to be configured is configured unsuccessfully, and the network element to be configured includes user plane network element, access management network element, network open network element and data management network element; The processing module is used to obtain the first domain name address of the DNS server corresponding to the user plane network element when the terminal device successfully connects to the core network device. The receiving module is configured to receive a DNS request message sent by the terminal device, wherein the DNS request message includes the second domain name address of the second application network element that the terminal device wants to access; The processing module is configured to determine the first server to be accessed by the terminal device based on the first domain name address, the second domain name address, and the second DNS configuration information of the second application network element, and to determine the IP address corresponding to the second domain name address of the second application network element to be accessed by the terminal device based on the first server; wherein, the first server includes an edge computing DNS server or an Internet DNS server.

9. An electronic device, characterized in that, The electronic device includes: Memory, used to store executable instructions; A processor, when executing executable instructions stored in the memory, implements the wireless communication method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores one or more programs, which can be executed by one or more processors to implement the wireless communication method as described in any one of claims 1 to 7.

Images