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 only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Please refer to fig. 1, which is a schematic diagram of a system architecture according to an embodiment of the present application. The system architecture can be applied to business scenarios supporting edge computing. The edge computing means that a platform for integrating network, computing storage and application core capabilities is arranged on the edge side of a network close to an object or a data source, so that edge intelligent services are provided nearby, and the key requirements of industry digitization on agile connection, real-time service, data optimization, application intelligent safety, privacy protection and the like are met. Edge computing enables operators and third party services to be hosted close to the access point of the end device, thereby enabling efficient service delivery by reducing end-to-end delay and load on the transport network.
The fifth generation mobile communication technology (5G for short) is a new generation broadband mobile communication technology with the characteristics of high speed, low time delay and large connection, and is a network infrastructure for realizing man-machine-object interconnection. The International Telecommunications Union (ITU) defines a more typical scenario in 5G applications, including: enhanced Mobile Broadband (eMBB), Ultra-reliable and Low Latency Communication (URLLC), Ultra-reliable Low Latency Communication and mass Machine Communication (mMTC), vehicle networking (V2X), and the like. On one hand, the above-mentioned eMBB scenario provides a large-traffic mobile broadband service, such as high-speed downloading, high-definition video, Virtual Reality (VR)/Augmented Reality (AR), etc., the peak rate of these services usually exceeds 10Gbps, and the bandwidth requirement is as high as several tens of Gbps, so that it will cause a huge pressure on wireless transmission and return mobile networks. These traffic demands therefore require that the traffic be sunk as far as possible to the edge of the network in order to achieve local offloading of the traffic. On the other hand, URLLC scenario and V2X scenario can provide ultra-high reliable ultra-low delay communication, such as automatic driving, industrial control, remote medical treatment, etc., which require high reliability of 99.999% from end to end and ultra-low delay of less than 1ms from end to end, so these service demands also require that services be sunk to the edge of the network to reduce network delay caused by network transmission and multi-level service forwarding.
It can be seen from the above that the popularization of 5G increases the demand for edge computation, and in addition, the use of edge computation in combination with 5G can help the network that encounters sudden and continuous traffic surge to solve bandwidth, speed and security problems.
As shown in fig. 1, the system architecture may include an edge data center 100 and a terminal cluster, where the terminal cluster may include: the edge data center 100 may include a plurality of Edge Application Servers (EAS) such as edge application server 100a, edge application servers 100b, …, edge application server 100m, terminal device 200a, terminal device 200b, terminal device 200c, …, terminal device 200 n. Communication connection may exist between the terminal clusters, for example, communication connection exists between the terminal device 200a and the terminal device 200b, and communication connection exists between the terminal device 200a and the terminal device 200 n. There may be a communication connection between the edge application servers, for example, a communication connection between the edge application server 100a and the edge application server 100 b. Meanwhile, any terminal device in the terminal cluster may have a communication connection with any edge application server in the edge data center 100, for example, a communication connection exists between the terminal device 200a and the edge application server 100 a. The communication connection is not limited to a connection method, and may be a 4G wireless access method, a 5G wireless access method, or the like, and the present application is not limited thereto.
It should be noted that, in mobile communication, the system architecture shown in fig. 1 may further include an access network, a bearer network (transport network), and a core network, where the access network may be configured with a plurality of base stations (e.g., a 5G base station gNB) and is mainly responsible for access and management of terminal devices on a wireless side; the bearer network may be composed of a series of operator's switching and routing devices, and is mainly used for transmitting control signaling and user data between the base station and the core network; the core network may deploy a series of core network elements ("network elements" may also be referred to as "network functions"), which cooperate to perform authentication, charging, mobility management, and the like on the terminal device, and the description of the access network and the bearer network is not provided herein.
For the understanding and description of the following embodiments, a brief description is first made of the main core network elements involved in the embodiments of the present application, specifically as follows:
(1) SMF (Session Management Function): the method is mainly responsible for session establishment and deletion, User plane selection and control, UE IP (User Equipment, namely terminal Equipment or User Equipment; IP, Internet Protocol, namely Internet Protocol) address allocation and the like. In the embodiment of the present application, the SMF may also be referred to as a session management network element.
(2) UPF (User Plane Function): the Data routing and forwarding method is mainly responsible for Data routing and forwarding of a user plane of a mobile core Network, and is interconnected with an external Data Network (such as an operator service, the internet or a third-party service, etc.). The UPF is a module that processes data in the 5G core network.
(3) PCF (Policy Control Function): it is mainly responsible for managing network behavior using a unified policy framework and executing relevant policies in cooperation with user information in udr (unified Data replication). In the embodiment of the present application, the PCF may also be referred to as a policy control network element.
(4) UDR (Unified Data Repository ): the method is mainly responsible for storage and retrieval of structured services, supports UDM (Unified Data Management) to store and retrieve subscription Data, supports PCF to store and retrieve policy Data and the like. In this embodiment of the present application, the UDR may also be referred to as a unified data storage network element.
(5) EASDF (Edge Application Server Discovery Function): in this embodiment of the present application, the EASDF may also be referred to as an edge application server discovery network element, and its main functions are as follows:
(a) register with NRF (Network Repository Function) for discovery and selection of EASDF;
(b) processing a DNS (Domain Name System) message according to the indication of the SMF, comprising:
(b1) receiving DNS message processing rules from the SMF;
(b2) exchanging DNS messages from the UE;
(b3) forwarding the DNS message to a C-DNS server (Central DNS server) or an L-DNS server (Local DNS server) for DNS query;
(b4) adding an ECS (EDNS Client Subnet, EDNS i.e. Extension Mechanisms for DNS, which is an extended DNS mechanism) option to a DNS query for an FQDN (Fully Qualified Domain Name/Fully Qualified Domain Name);
(b5) informing the SMF of EASDF related information;
(b6) DNS Security is terminated if DoT (DNS over TLS, DNS protocol is transmitted using TLS protocol), DoH (DNS over HTTPS, DNS protocol is transmitted using HTTPS protocol), or DNS over DTLS (DNS protocol is transmitted using packet Transport Layer Security protocol, DTLS).
It should be noted that the EASDF may be connected to a PSA (PDU Session Anchor) UPF through a data plane interface, and may be used to transmit DNS messages exchanged with the UE. Furthermore, multiple EASDF instances may be deployed within one PLMN (Public Land Mobile Network), and the interaction between the Network functions of the 5G core Network and the EASDF occurs within one PLMN.
In the 5G Network, assuming that a certain terminal device (e.g., any one of the terminal device 200a, the terminal device 200b, the terminal device 200c, and the terminal device 200 n) desires to access a Data Network (DN) outside a mobile communication Network, such as the Internet, a WAP, an intranet, and the like, the terminal device may initiate an access request, the base station may forward a service flow requested by the base station to a Core Network element (UPF) in a 5G Core Network (5G Core, which may be abbreviated as 5 upgc), and forward the service flow to the external Data Network through the Core Network element UPF, and other Core Network elements in the 5G Core Network are responsible for processing signaling and controlling the whole flow.
Further, to achieve more efficient service delivery, edge calculations may be employed to meet different traffic demands. It should be noted that in the edge computing scenario, one application service may be served by multiple edge application servers (e.g., edge application server 100a, edge application server 100b, and edge application server 100m in fig. 1) typically deployed at different sites, and these multiple edge application servers carrying the service may use a single IP address or different IP addresses. In general, an application server of an application may be deployed in a central application server or may be deployed in an edge application server. To route traffic of the Application to an Edge Application Server (Edge Application Server), the terminal device needs to know the IP address of the Edge Application Server serving the Application, and the terminal device may perform discovery to obtain the IP address of the appropriate Edge Application Server (e.g., the closest Edge Application Server) so that traffic may be routed locally to the Edge Application Server and service delay, traffic routing path, and user service experience may be optimized. Based on this, edge application server discovery is the process by which the terminal device uses the domain name system to find the appropriate edge application server's IP address. Among them, a Domain Name System (DNS) is a service of the internet, which serves as a distributed database mapping domain names and IP addresses to each other, enabling users to more conveniently access the internet.
The 5G core network supports a PDU connection service between the terminal device and the data network, the PDU connection service is embodied in a form of a PDU session (i.e., a protocol data unit session), and one PDU session refers to a process of performing communication between the terminal device and the data network, that is, after the PDU session is established, a data transmission channel between the terminal device and the data network is established. Taking the terminal device 200a as an example, assuming that the terminal device 200a desires to obtain a certain edge application service, the terminal device 200a may initiate a PDU session establishment request to a core network element SMF in the 5G core network, and in the PDU session establishment process, the core network element SMF may obtain deployment information of the edge application server through PDU session related policy information provided by the core network element PCF, and then the core network element SMF may select the core network element EASDF according to a related rule, and provide the terminal device 200a with an address of the core network element EASDF as an address of a DNS server of the PDU session. Further, the terminal device 200a may send a DNS query request message to a core network element EASDF. It should be noted that the core network element SMF may configure the DNS message processing rule on the core network element EASDF, so that the core network element EASDF forwards the DNS message of the terminal device 200a to the relevant DNS server when detecting the DNS message, and/or reports when detecting the DNS message. It is to be understood that the DNS message handling rules include information for DNS message detection and related operations. It should be noted that, in the PDU session process, the core network element SMF and the core network element EASDF may interact for multiple times, so that the core network element EASDF may correctly process the DNS request and the DNS response message, and so that the core network element SMF may correctly establish a offloading path and set an offloading rule, and further may return the IP address of the edge application server to the terminal device 200a, and after receiving the IP address, the terminal device 200a may use the IP address as a service access address to access the edge application server corresponding to the IP address. Assuming that it is the edge application server 100a finally found through the above procedure, the edge application server 100a may provide the corresponding edge application service to the terminal device 200 a.
It can be understood that, for the service with the ultra-large bandwidth, the ultra-large bandwidth traffic is processed nearby by deploying the mobile edge computing (such as the edge application server shown in fig. 1) nearby, and the impact of the large bandwidth on the backbone network can be greatly reduced, and typical scenes such as the live broadcast of a sports stadium match, the live broadcast of a concert, the distribution of mobile contents and the like can be greatly reduced.
It should be noted that, in the embodiment of the present application, the core network element SMF may generate a message processing rule set at a node level, where the message processing rule set may include one or more DNS message processing rules, and when the core network element SMF and the core network element EASDF establish a connection, the core network element SMF may issue the message processing rule set to the core network element EASDF, it should be noted that a sending condition of the message processing rule set at the node level does not depend on creation of a PDU session, that is, after the core network element EASDF receives the message processing rule set, if no rule update is involved, the received DNS message may be processed according to the message processing rule set in all subsequent PDU sessions, that is, the message processing rule set may be applied to processing all DNS messages sent to the core network element EASDF, and the core network element SMF is not required to frequently issue the rules.
It can be understood that the above-mentioned terminal device that can be used for edge computing may include terminal application products in the fields of civil use, business use, industry, military industry, etc., such as smart phones, tablet computers, notebook computers, palm computers, Mobile Internet Devices (MID), wearable devices (e.g., smart watches, smart bracelets, etc.), smart computers, smart vehicles, smart homes, unmanned aerial vehicles, ATMs, cameras, traffic lights, generators, or various types of sensors, etc. The edge application server may be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, or a cloud server providing basic cloud computing services such as a cloud database, a cloud service, cloud computing, a cloud function, cloud storage, a network service, cloud communication, middleware service, domain name service, security service, a CDN, a big data and artificial intelligence platform, and the like. The terminal device and the edge application server may be directly or indirectly connected in a wired or wireless manner, which is not limited in this embodiment of the present application.
Please refer to fig. 2 a-2 b together, which are schematic views of a data processing scenario provided in the embodiment of the present application. The implementation process of the data processing scenario is mainly performed in a 5G core network. As shown in fig. 2a, in the core network 300, the session management network element 300a (i.e., the SMF) may generate one or more message processing rules in advance according to a request of an Application Function (AF, which refers to various services of an Application layer) or a configuration of an operator, where the one or more message processing rules may form a message processing rule set 300b, and a specific number of the message processing rules is not limited in the embodiment of the present Application. When the session management network element 300a and the edge application server discover that the network element 300c (i.e., the EASDF) establishes a connection, both parties may perform data interaction, such as request and issue of rules. In an alternative embodiment, the session management network element 300a may issue the message processing rule set 300b to the edge application server discovery network element 300 c.
It should be noted that other manners may also be used to generate and issue the message processing rule, which is not limited in the embodiment of the present application, and some optional manners (for example, policy control network element generation and message processing rule issue) may refer to the subsequent embodiments. Of course, the present application may also be extended to other related or similar scenarios.
Further, after the edge application server discovery network element 300c receives the message processing rule set 300b, the message processing rule set 300b may be used to process a subsequent received domain name system message (i.e., DNS message), and the message processing rule set 300b is applicable to any protocol data unit session of any terminal device. Referring to fig. 2b together, the embodiment of the present application is described by taking AN example that a terminal device initiates a pdu session, as shown in fig. 2b, assuming that the terminal device 400 initiates a pdu session establishment request, such as pdu session a, to the core network 300, during the pdu session a, a plurality of dns messages, such as dns message a1, dns messages a2, …, and dns message AN (N is AN integer greater than 1), are generated, and the dns messages may include a query request message type and a query response message type, for example, dns message a1 may be a dns query request message sent by the terminal device 400. Further, if the message processing rule set 300b includes a plurality of message processing rules, the edge application server discovery network element 300c may respectively obtain a target message processing rule applicable to each domain name system message in the plurality of message processing rules included in the message processing rule set 300b, and then the edge application server discovery network element 300c may respectively process each domain name system message according to the corresponding target message processing rule.
Taking domain name system message A1 as an example, assume that message processing rule set 300b includes M message processing rules, respectively message processing rule X1Message processing rule X2… message processing rule XMIf M is an integer greater than 1, the edge application server finds that the network element 300c receives the domain name system message a1, matches the domain name system message a1 with M message processing rules in the message processing rule set 300b, and determines the matched message processing rule as a candidate message processing rule corresponding to the domain name system message a1, and if the candidate message processing rule is one, may directly determine the candidate message processing rule as a target message processing rule corresponding to the domain name system message a 1; if there are multiple candidate message processing rules, the target message processing rule corresponding to the domain name system message a1 may be obtained from the candidate message processing rules, for example, it is assumed that the candidate message processing rules include the message processing rule X1Medicine for curing diabetesInformation processing rule X2Then the edge application server discovery network element 300c may be configured according to message processing rule X1Message processing rule X2And sorting the corresponding rule priorities, and selecting the message processing rule with the highest rule priority from the two message processing rules as a target message processing rule corresponding to the domain name system message A1. It should be noted that, other ways may also be used to determine the target message processing rule among the multiple candidate message processing rules, which is not limited in the embodiment of the present application. Assuming that the target message processing rule determined through the above steps is message processing rule X1Then the edge application server discovery network element 300c may be configured according to message processing rule X1The message processing operation in (1) processes the domain name system message a 1. It can be understood that the processing procedure of the edge application server discovery network element 300c for other received domain name system messages (e.g., domain name system message a2, domain name system message AN, etc.) is consistent with the processing procedure for domain name system message a1, and is not described herein again.
As shown in fig. 2b, finally, the edge application server discovery network element 300c may send a domain name system query response message to the terminal device 400, which in one embodiment may contain the IP addresses of one or more edge application servers. It can be understood that, for other protocol data unit sessions established by the terminal device 400 or protocol data unit sessions established by other terminal devices, the processing procedure thereof is consistent with the processing procedure for the protocol data unit session a described above, and details are not described here.
It should be noted that, the data processing scenarios shown in fig. 2a to fig. 2b only represent core network elements (including SMF and EASDF) that have an affinity with the embodiment of the present application, and other core network elements, such as AMF (Access and Mobility Management Function), base station, UDM, and the like, may also be involved in an actual service scenario, which is not expanded in the embodiment of the present application.
As can be seen from the above, the message processing rule set provided in the embodiment of the present application has a node level, and the sending condition of the message processing rule set does not depend on the creation of the protocol data unit session, that is, after the session management network element successfully issues the message processing rule set to the edge application server to discover the network element, if there is no rule update involved, then no matter how many protocol data unit sessions are established, the request and issue of the message processing rule do not need to be triggered any more, i.e. the session management element does not need to issue message handling rules frequently for each pdu session of each terminal device, and, in addition, when the edge application server finds that the network element receives the dns message, the domain name system message can be directly processed in a relevant way according to the received message processing rule set, so that the domain name system message processing efficiency can be improved.
Please refer to fig. 3, which is a flowchart illustrating a data processing method according to an embodiment of the present application. The data processing method may be performed by a session management network element (SMF). As shown in fig. 3, the data processing method may include at least the following steps S101 to S102:
step S101, a session management network element generates a message processing rule set with a node level; the message processing rule set comprises one or more message processing rules;
specifically, the session management network element may obtain the rule generating information, and further may generate one or more message handling rules (DNS message handling rules) with priorities according to the rule generating information, and may determine the one or more message handling rules as the message handling rule set. The rule generation information may specifically include request information of an Application Function (AF) or configuration information of an operator. It should be noted that the message processing rule set in the embodiment of the present application is at a node level, that is, the sending condition of the message processing rule set does not depend on the creation of the protocol data unit session, and the message processing rule set can be sent when the network element is enabled.
Wherein each message processing rule in the set of message processing rules includes a message detection template and a message processing operation. The message detection template may specifically include one or more of a query request message detection template and a query response message detection template; message processing operations include, but are not limited to, one or more of content reporting operations, forwarding operations, cache waiting operations, sending operations; the forwarding operation may further include an option construction operation or an address replacement operation. In addition, each message processing rule may further include a rule identifier and a rule priority, and may further include at least one of the following: rule level and lifecycle. Wherein, the rule identifier is an identifier for distinguishing and marking each message processing rule; the rule priority may characterize the order in which each message processing rule is executed; rule level refers to node level; the lifecycle may characterize the validity time range of each message processing rule.
More specifically, each message processing rule may include the following:
(1) a rule identifier (rule ID);
(2) rule level: node level, i.e., the message handling rule is valid for all domain name system messages (i.e., DNS messages) on the node;
(3) rule priority (Precedence of the DNS message handling rule);
(4) a message detection template (DNS message detection template) comprising at least one of:
(a) if the message type of the domain name system message is the Query request message type (i.e. DNS message type ═ DNS Query): an array comprising a range of Fully Qualified Domain Names (FQDNs), which may comprise one or more fully qualified domain names, wherein one or more fully qualified domain names in the array may be used to match domain name system messages, i.e. as a query request message detection template;
(b) if the message type of the domain name system message is the query Response message type (i.e., dnmessage type ═ DNS Response):
may include at least one of: an array characterizing a fully qualified domain name range and an array (which may include one or more edge application server addresses) characterizing a range of edge application server addresses (EAS IP addresses, i.e., IP addresses of edge application servers), wherein one or more fully qualified domain names in the array, or alternatively, one or more edge application server addresses, may be used to match domain name system messages, i.e., as a query response message detection template;
(5) performing at least one possible message processing operation may include:
(a) content reporting operation: reporting the content of the domain name system message to the session management network element, such as may include at least one of: the IP address, FQDN and the like of the edge application server resolved from the domain name system message;
(b) and forwarding operation: sending the domain name system message to a preconfigured DNS server/resolver (DNS server/resolver) or a designated DNS server (indexed DNS server), which may also include the following operations (the designated DNS server is included in the message processing rule):
(b1) and (3) option construction operation: the domain name system message contains information for constructing an optional ECS option (ECS option) (the information for discovering the network element by the edge application server to construct the ECS option is contained in the message processing rule);
(b2) and (3) address replacement operation: replacing the domain name system message target address with a specified DNS server address (DNS ServerAddress); and replacing the source address of the domain name system message with the particular IP address. If the session management network element does not provide a DNS server address, the edge application server discovers that the network element will forward the domain name system message to a locally preconfigured DNS server/resolver;
(c) and (3) cache waiting operation: caching the domain name system message, reporting the content of the domain name system message to a session management network element and waiting for an instruction of the session management network element;
(d) and (3) sending operation: and sending the specified domain name system response message to the UE.
(6) Lifecycle, also known as Time Window (Time Window): the validity time of the message handling rule is defined. Outside the time window, the message processing rule is invalid.
As can be seen from the above, the query request message detection template provided in the embodiment of the present application does not include a Source IP address (e.g., an IP address of a terminal device), because the scheme provided in the present application does not relate to rule configuration of a session level, but is applicable to all sessions.
It can be understood that the specific content of the message processing rule may be adjusted according to actual requirements, which is not limited in the embodiment of the present application.
Step S102, when the session management network element and the edge application server find the network element to establish connection, the message processing rule set is issued to the edge application server to find the network element, so that the edge application server finds the network element to process the received domain name system message according to the message processing rule set in the subsequent protocol data unit session process.
Specifically, when the Session management network element and the edge application server discovery network Element (EASDF) establish a connection (at a node level), the Session management network element may issue the generated message processing rule set to the edge application server discovery network element, and during a subsequent protocol data unit Session (PDU Session), when the edge application server discovery network element receives a domain name system message, the Session management network element may perform detection and execution according to the message processing rule at the node level in the message processing rule set, so in this application embodiment, when the message processing rule set is configured on the edge application server discovery network element, all the protocol data unit sessions of all the terminal devices are applicable, and it is not necessary to require the Session management network element and the edge application server discovery network element to perform an interaction of the message processing rule each time a protocol data unit Session is established, that is, the session management network element does not need to frequently issue message processing rules to the edge application server discovery network element for each protocol data unit session of each terminal device.
It will be appreciated that the session management network element may also store the generated set of message handling rules to a unified data storage network element (UDR).
In addition, the session management network element may further obtain rule update information, and further may perform rule update on the message processing rule set according to the rule update information, and send the updated message processing rule set to the unified data storage network element and the edge application server discovery network element, so that the edge application server discovery network element may process a subsequent received domain name system message according to the updated message processing rule set. The rule updating information can be obtained according to the request of the application function or the configuration of an operator, and the rule updating can be realized in a full updating mode, namely, a full message processing rule set is issued and comprises an updating rule and a rule which is kept unchanged; and the updated content can be sent only by incremental updating, and the content which is not updated does not need to be sent repeatedly. The updated content may include modification or deletion of the content of a particular one or more message handling rules, or addition of one or more new message handling rules to a set of message handling rules, or deletion of one or more existing message handling rules.
Please refer to fig. 4, which is a schematic view of a data processing scenario provided in the embodiment of the present application. As shown in fig. 4, the message processing rule set with the node level is generated by the session management network element, when the session management network element and the edge application server discovery network element establish a connection, the session management network element will issue the generated message processing rule set with the node level to the edge application server discovery network element, and after receiving the message processing rule set, the edge application server discovery network element may send a response message for confirming the reception to the session management network element. It should be noted that the flow issued by the rule may be defined as a service for the edge application server to discover the network element, or may be defined as a service for the session management network element, and the specific service definition for implementing the function is not limited in the embodiment of the present application.
It should be noted that, when the session management network element generates the message processing rule with the session level (session level) and the message processing rule with the node level at the same time, the message processing rule with the session level may be continuously issued when the pdu session is established. When the edge application server finds that the network element receives the message processing rule with the session level, the message processing rule with the session level can be preferentially executed, and then the message processing rule with the node level provided by the embodiment of the application is executed; when the edge application server finds that the network element does not receive the message processing rule with the session level, the message processing rule with the node level is executed. For example, for a scenario where the edge application server discovery network element has configured message processing rules with a node level, but some special processing is desired for some pdu sessions, the session management network element may issue the message processing rules with a session level to the edge application server discovery network element, and at this time, the edge application server discovery network element may select to preferentially execute the message processing rules with a session level.
The embodiment of the application can support the session management network element to generate the message processing rule set with the node level, and further can issue the message processing rule set to the edge application server discovery network element when the session management network element and the edge application server discovery network element establish connection, and after the edge application server discovery network element receives the message processing rule set, the received domain name system message can be processed according to the message processing rule set in the subsequent protocol data unit session process. Therefore, it can be seen that the sending condition of the message processing rule set with the node level provided in the embodiment of the present application does not depend on the creation of the protocol data unit session, that is, after the session management network element successfully issues the message processing rule set to the edge application server discovery network element, if the rule is not updated, no matter how many protocol data unit sessions are established subsequently, the request and the issuance of the message processing rule need not to be triggered, that is, the session management network element does not need to issue the message processing rule frequently for each protocol data unit session of each terminal device, so that the interaction amount between the session management network element and the edge application server discovery network element can be greatly reduced. In addition, when the edge application server finds that the network element receives the domain name system message, the edge application server can directly perform related processing on the domain name system message according to the received message processing rule set, so that the domain name system message processing efficiency can be improved.
Please refer to fig. 5, which is a flowchart illustrating a data processing method according to an embodiment of the present application. The data processing method may be performed by a policy control network element (PCF). As shown in fig. 5, the data processing method may include at least the following steps S201 to S202:
step S201, a strategy control network element generates a message processing rule set with a node level; the message processing rule set comprises one or more message processing rules;
specifically, the policy control network element may obtain the rule generating information, and further may generate one or more message processing rules with priorities according to the rule generating information, and may determine the one or more message processing rules as a message processing rule set. The rule generation information may specifically include request information of an application function or configuration information of an operator. It should be noted that the message processing rule set in the embodiment of the present application is at a node level, that is, the sending condition of the message processing rule set does not depend on the creation of the protocol data unit session, and the message processing rule set can be sent when the network element is enabled.
Each message processing rule in the message processing rule set comprises a message detection template and a message processing operation. The message detection template may specifically include one or more of a query request message detection template and a query response message detection template; message processing operations include, but are not limited to, one or more of content reporting operations, forwarding operations, cache waiting operations, sending operations; the forwarding operation may further include an option construction operation or an address replacement operation. In addition, each message processing rule may further include a rule identifier and a rule priority, and may further include at least one of the following: rule level and lifecycle. Wherein, the rule identifier is an identifier for distinguishing and marking each message processing rule; the rule priority may characterize the order in which each message processing rule is executed; rule level refers to node level; the lifecycle may characterize the valid time range of each message processing rule; more specific rule contents may refer to the description in step S101 in the embodiment corresponding to fig. 3, and are not described again here. It can be understood that the specific content of the message processing rule may be adjusted according to actual requirements, which is not limited in the embodiment of the present application.
Step S202, the message processing rule set is issued to the edge application server to discover the network element, so that the edge application server discovers the network element and processes the received domain name system message according to the message processing rule set in the subsequent protocol data unit session process.
Specifically, the policy control network element may issue the generated message processing rule set to the edge application server discovery network element, and in a subsequent protocol data unit Session (PDU Session), when the edge application server discovery network element receives a domain name system message, the edge application server discovery network element may perform detection and execution operations according to a node-level message processing rule in the message processing rule set.
The policy control network element may issue the message processing rule set to the edge application server in a plurality of different manners to discover the network element, which is specifically as follows:
optionally, when the session management network element and the edge application server discovery network element establish a connection, the policy control network element may respond to the rule obtaining request sent by the session management network element, and forward the message processing rule set to the edge application server discovery network element through the session management network element. Please refer to fig. 6, which is a schematic view of a data processing scenario provided in the embodiment of the present application. As shown in fig. 6, a set of message processing rules having a node level is generated by a policy control network element, when the session management network element and the edge application server discover that the network element establishes a connection, the session management network element may request a set of message processing rules at a node level from the policy control network element, the policy control network element may respond to the rule acquisition request, sending the message processing rule set to the session management network element in the relevant response message, after receiving the message processing rule set, the session management network element may send the message processing rule set to the edge application server discovery network element, and after receiving the message processing rule set, the edge application server discovery network element may send a response message for confirming receipt to the session management network element.
Optionally, the policy control network element may respond to the rule obtaining request sent by the edge application server discovery network element, and issue the message processing rule set to the edge application server discovery network element. Please refer to fig. 7, which is a schematic view of a data processing scenario provided in the embodiment of the present application. As shown in fig. 7, the message processing rule set with the node level is generated by the policy control network element, when the edge application server discovers that the network element is enabled, the edge application server may actively request the message processing rule set with the node level from the policy control network element, the policy control network element may respond to the rule obtaining request and send the message processing rule set to the edge application server discovery network element in the relevant response message, and after receiving the message processing rule set, the edge application server discovery network element may send a response message for confirming the reception to the policy control network element.
Optionally, the policy control network element may store the message processing rule set in a unified data storage network element (UDR), so that the unified data storage network element issues the message processing rule set to the session management network element when the session management network element and the edge application server discover that the network element establishes a connection, where the session management network element refers to a network element that forwards the message processing rule set to the edge application server discovery network element. Please refer to fig. 8, which is a schematic view of a data processing scenario provided in the embodiment of the present application. As shown in fig. 8, the message processing rule set with the node level is generated by the policy control network element, the policy control network element may store the message processing rule set with the node level to the unified data storage network element first, when the session management network element and the edge application server discover that the network element establishes connection, the unified data storage network element may issue the message processing rule set to the session management network element, after receiving the message processing rule set, the session management network element may send a response message for confirming reception to the unified data storage network element, further, the session management network element may issue the message processing rule set to the edge application server discover network element, and after receiving the message processing rule set, the edge application server discover network element may send a response message for confirming reception to the session management network element.
In addition, the embodiment of the present application further supports the policy control network element to perform rule update on the message processing rule set, and the following description is respectively provided for different rule issuing paths.
Optionally, the policy control network element may obtain rule update information, further perform rule update on the message processing rule set according to the rule update information, and send the updated message processing rule set to the session management network element, so that the session management network element may send the updated message processing rule set to the edge application server to discover the network element, where a specific process may refer to the related description in the embodiment corresponding to fig. 6.
Optionally, the policy control network element may obtain rule update information, further perform rule update on the message processing rule set according to the rule update information, and send the updated message processing rule set to the edge application server to discover the network element, where a specific process may refer to the related description in the embodiment corresponding to fig. 7.
Optionally, the policy control network element may obtain rule update information, further perform rule update on the message processing rule set according to the rule update information, and store the updated message processing rule set to the unified data storage network element, so that the unified data storage network element may issue the updated message processing rule set to the session management network element, where the session management network element refers to a network element that forwards the updated message processing rule set to the edge application server discovery network element, and the specific process may refer to the relevant description in the embodiment corresponding to fig. 8.
It can be understood that, after the edge application server finds that the network element is successfully received, further, the edge application server may process the subsequent received domain name system message according to the updated message processing rule set.
The rule updating information can be obtained according to the request of the application function or the configuration of an operator, and the rule updating can be realized in a full updating mode, namely, a full message processing rule set is issued and comprises an updating rule and a rule which is kept unchanged; and the updated content can be sent only by incremental updating, and the content which is not updated does not need to be sent repeatedly. The updated content may include modification or deletion of the content of a particular one or more message handling rules, or addition of one or more new message handling rules to a set of message handling rules, or deletion of one or more existing message handling rules.
The embodiment of the application can support the policy control network element to generate a message processing rule set with a node level, and further can issue the message processing rule set to the edge application server to discover the network element, and after the edge application server discovers that the network element receives the message processing rule set, the edge application server can process the received domain name system message according to the message processing rule set in the subsequent protocol data unit session process. Therefore, it can be seen that the sending condition of the message processing rule set with the node level provided in the embodiment of the present application does not depend on the creation of the pdu session, that is, after the policy control element successfully issues the pdu set to the edge application server to find the element, if there is no rule update involved, no matter how many pdu sessions are subsequently established, there is no need to trigger the request and issue of the pdu processing rule, that is, there is no need to frequently issue the pdu processing rule for each pdu session of each terminal device.
Please refer to fig. 9, which is a flowchart illustrating a data processing method according to an embodiment of the present application. The data processing method may be performed by an edge application server discovery network Element (EASDF). As shown in fig. 9, the data processing method may include at least the following steps S301 to S302:
s301, when the session management network element and the edge application server find the network element to establish connection, the edge application server finds the network element to obtain a message processing rule set with a node level; the message processing rule set comprises one or more message processing rules;
specifically, when the session management network element and the edge application server discovery network element establish a connection, the edge application server discovery network element may obtain a message processing rule set having a node level, where a sending condition of the message processing rule set having the node level does not depend on creation of a protocol data unit session, and the message processing rule set may include one or more message processing rules in this embodiment. With reference to the embodiments corresponding to fig. 3 and fig. 5, the message processing rule set may be generated by the session management network element or may be generated by the policy control network element, which is not limited in this embodiment of the present application.
S302, when the edge application server finds that the network element receives the domain name system message, a target message processing rule is obtained from one or more message processing rules contained in the message processing rule set, and the domain name system message is processed according to the target message processing rule.
It should be noted that each message processing rule in the message processing rule set includes a message detection template and a message processing operation. The message detection template may specifically include one or more of a query request message detection template and a query response message detection template; message processing operations include, but are not limited to, one or more of content reporting operations, forwarding operations, cache waiting operations, sending operations; the forwarding operation may further include an option construction operation or an address replacement operation. In addition, each message processing rule may further include a rule identifier and a rule priority, and may further include at least one of the following: rule level and lifecycle. Wherein, the rule identifier is an identifier for distinguishing and marking each message processing rule; the rule priority may characterize the order in which each message processing rule is executed; rule level refers to node level; the lifecycle may characterize the validity time range of each message processing rule. More specific rule contents may refer to the description in step S101 in the embodiment corresponding to fig. 3, and are not described again here.
In an alternative embodiment, it is assumed that each message processing rule in the set of message processing rules includes a rule priority, a lifecycle, a message detection template, and a message processing operation. When the edge application server finds that the network element receives the domain name system message, the edge application server may obtain a target message processing rule from one or more message processing rules included in the message processing rule set, and may further process the received domain name system message according to the target message processing rule, where the specific process may be: when the edge application server finds that the network element receives the domain name system message, the domain name system message may be respectively matched with the message detection templates in one or more message processing rules included in the message processing rule set, and the matched message processing rule may be determined as a candidate message processing rule. According to the definition of the message detection template, the specific process of respectively matching the domain name system message with the message detection template in the one or more message processing rules may be as follows: firstly, an edge application server finds that a network element can acquire a message type of a domain name system message, if the message type is a query request message type, a Fully Qualified Domain Name (FQDN) in the domain name system message can be acquired, the fully qualified domain name can be respectively matched with a query request message detection template in one or more message processing rules, and then the message processing rules meeting matching conditions (such as matching with the fully qualified domain name) can be determined as candidate message processing rules; optionally, if the message type of the domain name system message is a query response message type, a fully qualified domain name in the domain name system message may be obtained, and then the fully qualified domain name may be respectively matched with a query response message detection template in one or more message processing rules, and then a message processing rule that satisfies a matching condition (e.g., matches with the fully qualified domain name) may be determined as a candidate message processing rule; or, if the message type is an inquiry response message type, an edge application server address (EAS IP address) in the domain name system message may be acquired, and then the edge application server address may be respectively matched with an inquiry response message detection template in one or more message processing rules, and then a message processing rule that satisfies a matching condition (e.g., matches with the edge application server address) may be determined as a candidate message processing rule.
Further, according to the rule priority corresponding to the candidate message processing rule, the edge application server finds that the network element can obtain the target message processing rule from the candidate message processing rule. It will be appreciated that the number of candidate message processing rules may be one or more. In one embodiment, when the number of candidate message processing rules is one, the candidate message processing rule may be determined as the target message processing rule. In one embodiment, when the number of candidate message processing rules is plural, a candidate message processing rule having the highest rule priority among the plural candidate message processing rules may be determined as the target message processing rule. Optionally, when the number of the candidate message processing rules is multiple, the multiple candidate message processing rules may be subjected to rule sorting and sorting according to rule priorities and life cycles corresponding to the multiple candidate message processing rules, that is, the rule priorities and life cycles may be considered comprehensively, so that the target message processing rule having the highest rule priority in the target time period may be obtained.
Finally, in the life cycle corresponding to the target message processing rule, the edge application server finds that the network element can process the domain name system message according to the message processing operation in the target message processing rule. It should be noted that, when there are multiple message processing operations in the target message processing rule, the edge application server discovers that the network element can perform the multiple message processing operations in a set order. It will be appreciated that the lifecycle actually relates to scheduling issues of edge computing, for example, when an edge computing platform is very loaded, the lifecycle by setting certain message processing rules may produce some beneficial changes so that subsequent edge application services do not squeeze the edge computing platform all over the time period. The relevant scenarios of the embodiments of the present application can be referred to the descriptions in the embodiments corresponding to fig. 2a to fig. 2 b.
In addition, when the message processing rule set is updated, the edge application server finds that the network element can acquire the updated message processing rule set, and then processes the subsequent received domain name system message according to the updated message processing rule set.
The embodiment of the application can support the edge application server discovery network element to acquire the message processing rule set with the node level when the session management network element and the edge application server discovery network element establish connection, and further can acquire the target message processing rule from one or more message processing rules contained in the message processing rule set when the domain name system message is received, and process the domain name system message according to the target message processing rule. Therefore, it can be seen that the sending condition of the message processing rule set with the node level provided in the embodiment of the present application does not depend on the creation of the protocol data unit session, that is, after the edge application server finds that the network element successfully acquires the message processing rule set, if the rule is not updated, no matter how many protocol data unit sessions are subsequently established, the request and the issue of the message processing rule need not to be triggered, that is, the message processing rule need not be frequently requested for each protocol data unit session of each terminal device.
Please refer to fig. 10, which is a schematic structural diagram of a network element apparatus according to an embodiment of the present application. The network element means may be a computer program (comprising program code) running on the network element device, e.g. the network element means is an application software; the device can be used for executing corresponding steps in the data processing method provided by the embodiment of the application. As shown in fig. 10, the network element apparatus 1 may include: the system comprises a rule generating module 11 and a rule issuing module 12;
a rule generating module 11, configured to generate, by a session management network element, a message processing rule set having a node level; the message processing rule set comprises one or more message processing rules;
the rule issuing module 12 is configured to issue the message processing rule set to the edge application server discovery network element when the session management network element and the edge application server discovery network element establish a connection, so that the edge application server discovery network element processes the received domain name system message according to the message processing rule set in a subsequent protocol data unit session;
in one embodiment, each message processing rule of the set of message processing rules includes a message detection template and a message processing operation.
In one embodiment, the message detection templates include one or more of a query request message detection template, a query response message detection template; the message processing operation comprises one or more of a content reporting operation, a forwarding operation, a cache waiting operation and a sending operation; the forwarding operation includes an option build operation and an address replacement operation.
In one embodiment, each of the message processing rules further includes a rule priority; the rule priority characterizes the order in which each message processing rule is executed.
In one embodiment, each of the message processing rules further includes a rule identifier; the rule identifier refers to an identifier that discriminates the marking of each message processing rule.
In one embodiment, each of the message processing rules further includes a life cycle and a rule level; the life cycle represents the effective time range of each message processing rule; rule level refers to node level.
The specific functional implementation manner of the rule generating module 11 may refer to step S101 in the embodiment corresponding to fig. 3, and the specific functional implementation manner of the rule issuing module 12 may refer to step S102 in the embodiment corresponding to fig. 3, which is not described herein again.
The embodiment of the application can support the session management network element to generate a message processing rule set with a node level, and further can issue the message processing rule set to the edge application server discovery network element when the session management network element and the edge application server discovery network element establish connection, and after the edge application server discovery network element receives the message processing rule set, the edge application server discovery network element can process the received domain name system message according to the message processing rule set in the subsequent protocol data unit session process. Therefore, it can be seen that the sending condition of the message processing rule set with the node level provided in the embodiment of the present application does not depend on the creation of the protocol data unit session, that is, after the session management network element successfully issues the message processing rule set to the edge application server discovery network element, if the rule is not updated, no matter how many protocol data unit sessions are established subsequently, the request and the issuance of the message processing rule need not to be triggered, that is, the session management network element does not need to issue the message processing rule frequently for each protocol data unit session of each terminal device, so that the interaction amount between the session management network element and the edge application server discovery network element can be greatly reduced. In addition, when the edge application server finds that the network element receives the domain name system message, the edge application server can directly perform related processing on the domain name system message according to the received message processing rule set, so that the domain name system message processing efficiency can be improved.
Please refer to fig. 11, which is a schematic structural diagram of a network element apparatus according to an embodiment of the present application. The network element means may be a computer program (comprising program code) running on the network element device, e.g. the network element means is an application software; the device can be used for executing corresponding steps in the data processing method provided by the embodiment of the application. As shown in fig. 11, the network element apparatus 2 may include: a rule generating module 21 and a rule issuing module 22;
a rule generating module 21, configured to generate, by a policy control network element, a message processing rule set having a node level; the message processing rule set comprises one or more message processing rules;
the rule issuing module 22 is configured to issue the message processing rule set to the edge application server to discover the network element, so that the edge application server discovers the network element and processes the received domain name system message according to the message processing rule set in a subsequent protocol data unit session process.
The specific functional implementation manner of the rule generating module 21 may refer to step S201 in the embodiment corresponding to fig. 5, and the specific functional implementation manner of the rule issuing module 22 may refer to step S202 in the embodiment corresponding to fig. 5, which is not described herein again.
Referring to fig. 11, the network element apparatus 2 may further include: a first update module 23, a second update module 24, a third update module 25;
the first updating module 23 is configured to obtain rule update information, perform rule update on the message processing rule set according to the rule update information, and send the updated message processing rule set to the session management network element, so that the session management network element sends the updated message processing rule set to the edge application server discovery network element;
the second updating module 24 is configured to obtain rule update information, perform rule update on the message processing rule set according to the rule update information, and send the updated message processing rule set to the edge application server discovery network element;
and a third updating module 25, configured to obtain rule update information, perform rule update on the message processing rule set according to the rule update information, and store the updated message processing rule set to the unified data storage network element, so that the unified data storage network element issues the updated message processing rule set to the session management network element, where the session management network element is a network element that forwards the updated message processing rule set to the edge application server discovery network element.
For specific functional implementation manners of the first updating module 23, the second updating module 24, and the third updating module 25, reference may be made to step S202 in the embodiment corresponding to fig. 5, which is not described herein again.
Referring to fig. 11, the rule issuing module 22 may include: a first issuing unit 221, a second issuing unit 222, and a third issuing unit 223;
the first issuing unit 221 is configured to, when the session management network element and the edge application server discover the network element and establish a connection, respond to the rule acquisition request sent by the session management network element, and forward the message processing rule set to the edge application server discover the network element through the session management network element;
a second issuing unit 222, configured to respond to a rule obtaining request sent by the edge application server to discover the network element, and issue the message processing rule set to the edge application server to discover the network element;
a third issuing unit 223, configured to store the message processing rule set to the unified data storage network element, so that the unified data storage network element issues the message processing rule set to the session management network element when the session management network element and the edge application server discover the network element to establish a connection, where the session management network element refers to a network element that forwards the message processing rule set to the edge application server discover the network element.
The specific functional implementation manners of the first issuing unit 221, the second issuing unit 222, and the third issuing unit 223 may refer to step S202 in the embodiment corresponding to fig. 5, and are not described herein again.
The embodiment of the application can support the policy control network element to generate a message processing rule set with a node level, and further can issue the message processing rule set to the edge application server to discover the network element, and after receiving the message processing rule set, the edge application server discovers that the network element can process the received domain name system message according to the message processing rule set in the subsequent protocol data unit session process. Therefore, it can be seen that the sending condition of the message processing rule set with the node level provided in the embodiment of the present application does not depend on the creation of the pdu session, that is, after the policy control element successfully issues the pdu set to the edge application server to find the element, if there is no rule update involved, no matter how many pdu sessions are subsequently established, there is no need to trigger the request and issue of the pdu processing rule, that is, there is no need to frequently issue the pdu processing rule for each pdu session of each terminal device.
Please refer to fig. 12, which is a schematic structural diagram of a network element apparatus according to an embodiment of the present application. The network element means may be a computer program (comprising program code) running on the network element device, e.g. the network element means is an application software; the device can be used for executing corresponding steps in the data processing method provided by the embodiment of the application. As shown in fig. 12, the network element apparatus 3 may include: a rule acquisition module 31 and a message processing module 32;
a rule obtaining module 31, configured to, when the session management network element and the edge application server discover the network element to establish a connection, the edge application server discovers the network element and obtains a message processing rule set at a node level; the message processing rule set comprises one or more message processing rules;
the message processing module 32 is configured to, when the edge application server finds that the network element receives the domain name system message, obtain a target message processing rule from the message processing rule set that includes one or more message processing rules, and process the domain name system message according to the target message processing rule.
The specific functional implementation manner of the rule obtaining module 31 may refer to step S301 in the embodiment corresponding to fig. 9, and the specific functional implementation manner of the message processing module 32 may refer to step S302 in the embodiment corresponding to fig. 9, which is not described herein again.
In one embodiment, each message processing rule in the set of message processing rules includes a rule priority, a lifecycle, a message detection template, and a message processing operation;
referring to fig. 12, the message processing module 32 may include: a matching unit 321, an obtaining unit 322, a processing unit 323;
a matching unit 321, configured to match, when the edge application server finds that the network element receives the domain name system message, the domain name system message with a message detection template in one or more message processing rules included in the message processing rule set, respectively, and determine the matched message processing rule as a candidate message processing rule;
in one embodiment, the message detection template includes one or more of a query request message detection template and a query response message detection template;
the matching unit 321 is specifically configured to obtain a message type of a domain name system message; if the message type is the query request message type, acquiring a fully qualified domain name in the domain name system message, matching the fully qualified domain name with a query request message detection template in one or more message processing rules, and determining the message processing rule meeting the matching condition as a candidate message processing rule; and is specifically configured to, if the message type is a query response message type, obtain a fully qualified domain name in the domain name system message, match the fully qualified domain name with a query response message detection template in the one or more message processing rules, and determine a message processing rule that satisfies the matching condition as a candidate message processing rule; or if the message type is the query response message type, acquiring an edge application service protocol address in the domain name system message, matching the edge application service protocol address with a query response message detection template in one or more message processing rules, and determining the message processing rule meeting the matching condition as a candidate message processing rule;
an obtaining unit 322, configured to obtain a target message processing rule from the candidate message processing rules according to the rule priority corresponding to the candidate message processing rule;
the processing unit 323 is configured to process the domain name system message according to the message processing operation in the target message processing rule in the life cycle corresponding to the target message processing rule.
For specific functional implementation manners of the matching unit 321, the obtaining unit 322, and the processing unit 323, reference may be made to step S302 in the embodiment corresponding to fig. 9, which is not described herein again.
The embodiment of the application can support the edge application server discovery network element to acquire the message processing rule set with the node level when the session management network element and the edge application server discovery network element establish connection, and further can acquire the target message processing rule from one or more message processing rules contained in the message processing rule set when the domain name system message is received, and process the domain name system message according to the target message processing rule. Therefore, it can be seen that the sending condition of the message processing rule set with the node level provided in the embodiment of the present application does not depend on the creation of the protocol data unit session, that is, after the edge application server finds that the network element successfully acquires the message processing rule set, if the rule is not updated, no matter how many protocol data unit sessions are subsequently established, the request and the issue of the message processing rule need not to be triggered, that is, the message processing rule need not be frequently requested for each protocol data unit session of each terminal device.
Please refer to fig. 13, which is a schematic structural diagram of a network element device according to an embodiment of the present application. As shown in fig. 13, the network element apparatus 1000 may include: the processor 1001, the network interface 1003 and the memory 1004, and the network element device 1000 may further include: at least one communication bus 1002. Wherein a communication bus 1002 is used to enable connective communication between these components. The network interface 1003 may optionally include a standard wired interface or a wireless interface (e.g., WI-FI interface). The memory 1004 may be a high-speed RAM memory or a non-volatile memory (e.g., at least one disk memory). The memory 1004 may optionally be at least one storage device located remotely from the processor 1001. As shown in fig. 13, the memory 1004, which is a kind of computer-readable storage medium, may include therein an operating system, a network communication module, and a device control application program. In this embodiment, the network element device 1000 may be a session management network element.
In the network element apparatus 1000 shown in fig. 13, the network interface 1003 may provide a network communication network element; and the processor 1001 may be configured to invoke a device control application stored in the memory 1004 to cause the network element device 1000 to perform:
generating a set of message processing rules having a node level; the message processing rule set comprises one or more message processing rules;
when the connection with the edge application server discovery network element is established, the message processing rule set is issued to the edge application server discovery network element, so that the edge application server discovery network element processes the received domain name system message according to the message processing rule set in the subsequent protocol data unit session process.
It should be understood that the network element device 1000 described in this embodiment of the present application may perform the description on the data processing method in the embodiment corresponding to fig. 3, which is not described herein again. In addition, the beneficial effects of the same method are not described in detail.
Further, here, it is to be noted that: an embodiment of the present application further provides a computer-readable storage medium, where the computer-readable storage medium stores the aforementioned computer program executed by the network element apparatus 1, and the computer program includes program instructions, and when the processor executes the program instructions, the description of the data processing method in the embodiment corresponding to fig. 3 can be performed, so that details are not repeated here. In addition, the beneficial effects of the same method are not described in detail. For technical details not disclosed in embodiments of the computer-readable storage medium referred to in the present application, reference is made to the description of embodiments of the method of the present application.
Please refer to fig. 14, which is a schematic structural diagram of a network element device according to an embodiment of the present application. As shown in fig. 14, the network element device 2000 may include: the processor 2001, the network interface 2003 and the memory 2004, and the network element apparatus 2000 may further include: at least one communication bus 2002. The communication bus 2002 is used to implement connection communication between these components. The network interface 2003 may optionally include a standard wired interface, a wireless interface (e.g., WI-FI interface), among others. The memory 2004 may be a high-speed RAM memory or a non-volatile memory, such as at least one disk memory. The memory 2004 may alternatively be at least one memory device located remotely from the aforementioned processor 2001. As shown in fig. 14, the memory 2004, which is a kind of computer-readable storage medium, may include therein an operating system, a network communication module, and a device control application program. In this embodiment, the network element device 2000 may be a policy control network element.
In the network element apparatus 2000 shown in fig. 14, the network interface 2003 may provide a network communication network element; and the processor 2001 may be configured to invoke a device control application stored in the memory 2004 to cause the network element device 2000 to perform:
generating a set of message processing rules having a node level; the message processing rule set comprises one or more message processing rules;
and sending the message processing rule set to the edge application server to discover the network element so that the edge application server discovers the network element and processes the received domain name system message according to the message processing rule set in the subsequent protocol data unit session process.
It should be understood that the network element device 2000 described in this embodiment of the present application may perform the description of the data processing method in the embodiment corresponding to fig. 5, which is not described herein again. In addition, the beneficial effects of the same method are not described in detail.
Further, here, it is to be noted that: an embodiment of the present application further provides a computer-readable storage medium, where the computer-readable storage medium stores the aforementioned computer program executed by the network element device 2, and the computer program includes program instructions, and when the processor executes the program instructions, the description of the data processing method in the embodiment corresponding to fig. 5 can be performed, so that details are not repeated here. In addition, the beneficial effects of the same method are not described in detail. For technical details not disclosed in embodiments of the computer-readable storage medium referred to in the present application, reference is made to the description of embodiments of the method of the present application.
Please refer to fig. 15, which is a schematic structural diagram of a network element device according to an embodiment of the present application. As shown in fig. 15, the network element device 3000 may include: the processor 3001, the network interface 3003 and the memory 3004, wherein the network element device 3000 further includes: at least one communication bus 3002. The communication bus 3002 is used to realize connection communication between these components. The network interface 3003 may optionally include a standard wired interface, a wireless interface (e.g., WI-FI interface). The memory 3004 may be a high-speed RAM memory or a non-volatile memory (e.g., at least one disk memory). The memory 3004 may alternatively be at least one memory device located remotely from the processor 3001. As shown in fig. 15, the memory 3004, which is a kind of computer-readable storage medium, may include therein an operating system, a network communication module, and a device control application program. In this embodiment, the network element device 3000 may discover a network element for an edge application server.
In the network element device 3000 shown in fig. 15, the network interface 3003 may provide a network communication network element; and the processor 3001 may be configured to invoke a device control application stored in the memory 3004 to cause the network element device 3000 to perform:
when establishing connection with a session management network element, acquiring a message processing rule set with a node level; the message processing rule set comprises one or more message processing rules;
when receiving the domain name system message, obtaining a target message processing rule from one or more message processing rules contained in the message processing rule set, and processing the domain name system message according to the target message processing rule.
It should be understood that the network element device 3000 described in this embodiment of the present application may perform the description on the data processing method in the embodiment corresponding to fig. 9, which is not described herein again. In addition, the beneficial effects of the same method are not described in detail.
Further, here, it is to be noted that: an embodiment of the present application further provides a computer-readable storage medium, where the computer-readable storage medium stores the aforementioned computer program executed by the network element device 3, and the computer program includes program instructions, and when the processor executes the program instructions, the description of the data processing method in the embodiment corresponding to fig. 9 can be performed, so that details are not repeated here. In addition, the beneficial effects of the same method are not described in detail. For technical details not disclosed in embodiments of the computer-readable storage medium referred to in the present application, reference is made to the description of embodiments of the method of the present application.
The computer readable storage medium may be the network element apparatus provided in any of the foregoing embodiments or an internal storage unit of the network element device, such as a hard disk or a memory of the network element device. The computer readable storage medium may also be an external storage device of the network element device, such as a plug-in hard disk, a Smart Memory Card (SMC), a Secure Digital (SD) card, a flash memory card (flash card), and the like, which are provided on the network element device. Further, the computer readable storage medium may also include both an internal storage unit and an external storage device of the network element device. The computer-readable storage medium is used for storing the computer program and other programs and data required by the network element device. The computer readable storage medium may also be used to temporarily store data that has been output or is to be output.
Further, here, it is to be noted that: embodiments of the present application also provide a computer program product or computer program comprising computer instructions stored in a computer-readable storage medium. The processor of the network element device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the network element device performs the method provided by any one of the embodiments corresponding to fig. 3, fig. 5, and fig. 9.
The terms "first," "second," and the like in the description and in the claims and drawings of the embodiments of the present application are used for distinguishing between different objects and not for describing a particular order. Furthermore, the terms "comprises" and any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, apparatus, product, or apparatus that comprises a list of steps or elements is not limited to the listed steps or modules, but may alternatively include other steps or modules not listed or inherent to such process, method, apparatus, product, or apparatus.
Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the examples described in connection with the embodiments disclosed herein may be embodied in electronic hardware, computer software, or combinations of both, and that the components and steps of the examples have been described in general terms of network elements in the foregoing description for the purpose of illustrating clearly the interchangeability of hardware and software. Whether these network elements are implemented in hardware or software depends on the specific application of the solution and design constraints. A person skilled in the art may use different methods for implementing the described network elements for each specific application, but such an implementation should not be considered as being beyond the scope of the present application.
The method and the related apparatus provided by the embodiments of the present application are described with reference to the flowchart and/or the structural diagram of the method provided by the embodiments of the present application, and each flow and/or block of the flowchart and/or the structural diagram of the method, and the combination of the flow and/or block in the flowchart and/or the block diagram can be specifically implemented by computer program instructions. These computer program instructions may 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, create means for implementing the functions specified in the flowchart flow or flows and/or block or blocks of the block diagram. These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block or blocks of the block diagram. These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block or blocks.
The above disclosure is only for the purpose of illustrating the preferred embodiments of the present application and is not to be construed as limiting the scope of the present application, so that the present application is not limited thereto, and all equivalent variations and modifications can be made to the present application.