Addressing methods, apparatus, electronic devices and computer-readable storage media
By obtaining the external identifier of the slice through EASDF and inserting a DNS request message, the problem of user equipment being unable to obtain an IP address under 5G slicing is solved, end-to-end service assurance is achieved, and service performance is improved.
Patent Information
- Application Number
- CN202210591968.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-05-27
- Publication Date
- 2026-11-17
- Estimated Expiration
- 2042-05-27
AI Technical Summary
Because user equipment under 5G slicing cannot obtain the IP address of the application instance under the corresponding slice, the service guarantee provided by 5G slicing is limited to the mobile network and cannot achieve end-to-end service guarantee.
The EASDF receives the DNS Context Generation Request message carrying the slice identifier sent by the SMF, obtains the external identifier of the slice, inserts it into the DNS request message, processes it using the DNS extension mechanism eDNS, and sends it to the DNS server so that the DNS server can determine the IP address applied under the slice.
This enables user equipment to directly obtain the IP address of application instances under a slice without the need for dedicated channels and channel mapping, avoiding continuous analysis and identification of slice services by user equipment during service access and improving end-to-end service performance.
Smart Images

Figure CN117176688B_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to the field of Internet communication technology, and in particular to an addressing method, apparatus, electronic device and computer-readable storage medium. Background Technology
[0002] With the development of Internet communication technology, users' needs for network resources are becoming more and more diverse. 5G (5th Generation Mobile Communication Technology) network slicing can provide different service guarantees for users with different needs, thus meeting users' diverse needs for network resources.
[0003] However, because the N6 (an interface type) interface at the mobile network's exit does not carry slice information, user devices under different slices cannot access instances of the same application under different slices. In other words, user devices under different slices cannot obtain the IP (Internet Protocol) address of the application instance under the corresponding slice. Consequently, the service guarantees provided by 5G slices are limited to within the mobile network, failing to provide end-to-end guarantees. Therefore, a method to find the IP address of the application instance corresponding to the slice is urgently needed.
[0004] It should be noted that the information disclosed in the background section above is only used to enhance the understanding of the background of this disclosure, and therefore may include information that does not constitute prior art known to those skilled in the art. Summary of the Invention
[0005] This disclosure provides an addressing method, apparatus, electronic device, and computer-readable storage medium, and at least provides a method for finding the IP address of an application instance corresponding to a slice.
[0006] Other features and advantages of this disclosure will become apparent from the following detailed description, or may be learned in part from practice of this disclosure.
[0007] According to one aspect of this disclosure, an addressing method is provided for use in Edge Application Server Discovery Function (EASDF), comprising:
[0008] Receive a DNS context generation request message sent by the Session Management Function (SMF), wherein the DNS context generation request message includes the slice identifier of the slice where the corresponding session is located;
[0009] Receive the DNS request message sent by the user equipment (UE) corresponding to the session;
[0010] Obtain the external identifier of the slice corresponding to the slice identifier;
[0011] Insert the external identifier of the slice into the DNS request message;
[0012] A DNS request message containing the external identifier of the slice is sent to a DNS server so that the DNS server can determine the Internet Protocol IP address of the application under the slice corresponding to the domain name included in the DNS request message based on the external identifier of the slice.
[0013] In one embodiment of this disclosure, the EASDF is configured with a DNS message detection template; obtaining the external segment identifier corresponding to the segment identifier includes: obtaining the external segment identifier corresponding to the segment identifier when the DNS request message matches the DNS message detection template.
[0014] In one embodiment of this disclosure, the EASDF is configured with an internal and external identifier mapping table for slices, and obtaining the external identifier of the slice corresponding to the slice identifier includes: querying the internal and external identifier mapping table based on the slice identifier to obtain the external identifier of the slice.
[0015] In one embodiment of this disclosure, inserting the slice external identifier into the DNS request message includes: performing DNS extension mechanism eDNS processing on the DNS request message so that the processed DNS request message includes a pseudo resource record (OPT), the OPT including a first variable part (RDATA) field; and inserting the slice external identifier into the first RDATA field.
[0016] In one embodiment of this disclosure, the DNS server is a central DNS server; before sending the DNS request message with the external identifier of the slice inserted to the DNS server, the method further includes: obtaining the location information of the UE through the network; mapping the location information of the UE to a location identifier corresponding to the edge network where the UE is located; inserting the location identifier into the first RDATA field; sending the DNS request message with the external identifier of the slice inserted to the DNS server includes: sending the DNS request message with the external identifier of the slice inserted and the location identifier inserted to the central DNS server.
[0017] In one embodiment of this disclosure, the OPT further includes a second RDATA field, and the DNS server is a central DNS server; before sending the DNS request message with the external identifier of the slice inserted to the DNS server, the method further includes: obtaining the location information of the UE through the network; mapping the location information of the UE to a location identifier corresponding to the edge network where the UE is located; inserting the location identifier into the second RDATA field; sending the DNS request message with the external identifier of the slice inserted to the DNS server includes: sending the DNS request message with the external identifier of the slice inserted and the location identifier inserted to the central DNS server.
[0018] According to another aspect of this disclosure, an addressing method is provided for use with a Domain Name System (DNS) server, comprising:
[0019] Receive a DNS request message sent by the Edge Application Server Discovery Function (EASDF), the DNS request message including the slice external identifier;
[0020] Based on the external identifier of the slice, determine the Internet Protocol (IP) address of the application under the slice corresponding to the domain name included in the DNS request message.
[0021] In one embodiment of this disclosure, the DNS server is a central DNS server configured with an enhanced resolution table. The enhanced resolution includes domain name information and a location identifier, a slice external identifier, and an IP address corresponding to the domain name information. The DNS request message also includes a location identifier. Determining the Internet Protocol (IP) address of the application under the slice corresponding to the domain name included in the DNS request message based on the slice external identifier includes: querying the enhanced resolution table based on the location identifier, slice external identifier, and domain name included in the DNS request message to obtain the IP address of the application under the slice corresponding to the domain name included in the DNS request message.
[0022] In one embodiment of this disclosure, the DNS server is a local DNS server configured with an enhanced resolution table, which includes domain name information and a slice external identifier and IP address corresponding to the domain name information. The step of determining the Internet Protocol (IP) address of the application under the slice corresponding to the domain name included in the DNS request message based on the slice external identifier includes: querying the enhanced resolution table based on the slice external identifier and domain name included in the DNS request message to obtain the IP address of the application under the slice corresponding to the domain name included in the DNS request message.
[0023] According to another aspect of this disclosure, an addressing apparatus is provided for use in Edge Application Server Discovery Function (EASDF), comprising:
[0024] The receiving module is used to receive a Domain Name System (DNS) Context Generation Request message sent by the Session Management Function (SMF), wherein the DNS Context Generation Request message includes the slice identifier of the slice where the corresponding session is located.
[0025] The receiving module is also used to receive a DNS request message sent by the user equipment (UE) corresponding to the session;
[0026] The acquisition module is used to acquire the external identifier of the slice corresponding to the slice identifier;
[0027] The processing module is used to insert the external identifier of the slice into the DNS request message;
[0028] The sending module is used to send a DNS request message containing the external identifier of the slice to the DNS server, so that the DNS server can determine the Internet Protocol IP address of the domain name included in the DNS request message under the slice based on the external identifier of the slice.
[0029] In one embodiment of this disclosure, the EASDF is configured with a DNS message detection template; the acquisition module is used to acquire the external identifier of the slice corresponding to the slice identifier when the DNS request message matches the DNS message detection template.
[0030] In one embodiment of this disclosure, the EASDF is configured with an internal and external identifier mapping table for slices, and the acquisition module is used to query the internal and external identifier mapping table according to the slice identifier to obtain the external identifier of the slice.
[0031] In one embodiment of this disclosure, the processing module is configured to perform DNS extension mechanism eDNS processing on the DNS request message, so that the processed DNS request message includes a pseudo resource record (OPT), the OPT including a first variable part (RDATA) field; and to insert the slice external identifier into the first RDATA field.
[0032] In one embodiment of this disclosure, the DNS server is a central DNS server; the processing module is further configured to obtain the location information of the UE through the network; map the location information of the UE to a location identifier corresponding to the edge network where the UE is located; insert the location identifier into the first RDATA field; and the sending module is configured to send a DNS request message containing the external identifier of the slice and the location identifier to the central DNS server.
[0033] In one embodiment of this disclosure, the OPT further includes a second RDATA field, and the DNS server is a central DNS server; the processing module is further configured to obtain the location information of the UE through the network; map the location information of the UE to a location identifier corresponding to the edge network where the UE is located; insert the location identifier into the second RDATA field; and the sending module is configured to send a DNS request message containing the external identifier of the slice and the location identifier to the central DNS server.
[0034] According to another aspect of this disclosure, an addressing apparatus is provided for use in a Domain Name System (DNS) server, comprising:
[0035] The receiving module is used to receive DNS request messages sent by the Edge Application Server Discovery Function (EASDF), wherein the DNS request message includes the slice external identifier;
[0036] The determining module is used to determine, based on the external identifier of the slice, the Internet Protocol IP address of the application under the slice corresponding to the domain name included in the DNS request message.
[0037] In one embodiment of this disclosure, the DNS server is a central DNS server, which is configured with an enhanced resolution table. The enhanced resolution includes domain name information and a location identifier, a slice external identifier, and an IP address corresponding to the domain name information. The DNS request message also includes a location identifier. The determining module is used to query the enhanced resolution table based on the location identifier, slice external identifier, and domain name included in the DNS request message to obtain the IP address of the domain name included in the DNS request message that is applied under the slice.
[0038] In one embodiment of this disclosure, the DNS server is a local DNS server configured with an enhanced resolution table, which includes domain name information and a slice external identifier and IP address corresponding to the domain name information. The determining module is used to query the enhanced resolution table based on the slice external identifier and domain name included in the DNS request message to obtain the IP address of the application under the slice corresponding to the domain name included in the DNS request message.
[0039] According to another aspect of this disclosure, an electronic device is provided, comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to perform the above-described addressing method by executing the executable instructions.
[0040] According to another aspect of this disclosure, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the addressing method described above.
[0041] The technical solution provided in this disclosure involves the EASDF receiving a DNS context generation request message carrying a slice identifier from the SMF. The EASDF then obtains the corresponding external slice identifier based on the slice identifier and inserts it into a DNS request message sent by the UE. This external slice identifier is then carried to the DNS server via the DNS request message, allowing the DNS server to determine the IP address of the application corresponding to the domain name included in the DNS request message within the slice. This method provides an addressing mechanism for finding the IP address of an application instance within a slice without requiring the construction of a dedicated channel or the configuration of channel mapping.
[0042] Furthermore, it enables user devices to directly obtain and access the IP address of the application instance under the slice, avoiding the need for continuous analysis and identification of slice services during user device access, improving end-to-end service performance, and enabling the slice to provide end-to-end service guarantee for users.
[0043] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description
[0044] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure. It is obvious that the drawings described below are merely some embodiments of this disclosure, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort.
[0045] Figure 1 This diagram illustrates an addressing system structure according to an embodiment of the present disclosure;
[0046] Figure 2 A flowchart illustrating an addressing method according to an embodiment of this disclosure is shown;
[0047] Figure 3 This diagram illustrates the structure of the first RDATA field before and after the insertion of the slice external identifier in one embodiment of this disclosure;
[0048] Figure 4 This diagram illustrates the structure after inserting the slice external identifier and position identifier into the first RDATA field in another embodiment of this disclosure;
[0049] Figure 5This diagram illustrates the structure of the first RDATA field and the second RDATA field after inserting the slice external identifier and the position identifier, respectively, in another embodiment of this disclosure.
[0050] Figure 6 A flowchart illustrating an addressing method according to another embodiment of this disclosure is shown;
[0051] Figure 7 The following is a signaling diagram illustrating an application instance accessed by a UE under a slice, according to one embodiment of this disclosure;
[0052] Figure 8 This diagram illustrates an addressing device according to an embodiment of the present disclosure;
[0053] Figure 9 A schematic diagram of an addressing device is shown in another embodiment of this disclosure;
[0054] Figure 10 A structural block diagram of an electronic device according to an embodiment of the present disclosure is shown. Detailed Implementation
[0055] Exemplary embodiments will now be described more fully with reference to the accompanying drawings. However, these exemplary embodiments can be implemented in many forms and should not be construed as limited to the examples set forth herein; rather, they are provided so that this disclosure will be more comprehensive and complete, and will fully convey the concept of the exemplary embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
[0056] Furthermore, the accompanying drawings are merely illustrative of this disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and therefore repeated descriptions of them will be omitted. Some block diagrams shown in the drawings are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities may be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.
[0057] To facilitate understanding, the following is an explanation of several terms used in this disclosure:
[0058] SMF: Session Management Function;
[0059] EASDF: Edge Application Server Discovery function;
[0060] gNB: 5G base station;
[0061] DNS: Domain Name System;
[0062] UPF: User Plane Function;
[0063] EDN: Edge Data Network;
[0064] MEC: Multi-access Computing;
[0065] EAS: Edge Application Server.
[0066] In the field of internet communication technology, the development and application of network slicing technology allows users with different network resource needs to obtain the service guarantees they require under the corresponding slice. In related technologies, when user devices under different slices access the same application, they will access the same instance of that application. That is, before accessing the application, the DNS server sends the same IP address to user devices under different slices, regardless of the slice. However, because the IP address obtained by the user device is a slice-insensitive IP address, the service guarantee provided by the slice for this access is limited to within the mobile network and cannot achieve end-to-end coverage.
[0067] To address this, this disclosure provides an addressing method that can locate the application instance IP address corresponding to the slice without needing to build a dedicated channel or configure channel mapping. Furthermore, it enables user devices to directly access application instances via the IP address of the application instance under the slice, avoiding the need for continuous analysis and identification of slice services during user device access, thus improving end-to-end service performance and ensuring that the slice can provide end-to-end service guarantees to users.
[0068] Figure 1 A schematic diagram of an exemplary system architecture that can be applied to the addressing method or addressing apparatus of the present disclosure is shown.
[0069] like Figure 1 As shown, the system architecture includes user equipment 101, user equipment 102, gNB base station 103, SMF network element 104, EASDF network element 105, DNS server 106, UPF network element 107, EDN / EMC node 108, application first instance 109, and application second instance 110.
[0070] Both user equipment 101 and user equipment 102 can initiate slice session establishment requests to SMF network element 104, and gNB base station 103 can forward these requests. SMF network element 104 can receive slice session establishment requests and, based on these requests, send corresponding DNS context generation requests to EASDF network element 105. These DNS context generation requests include the slice identifier (Single Network Slice Selection Assistance Information, S-NSSAI) of the slice corresponding to the session. EASDF network element 105 can generate the corresponding DNS context based on the information included in the DNS context generation request sent by SMF network element 104.
[0071] User equipment 101 and user equipment 102 can also send DNS request messages to EASDF network element 105 to resolve domain name IP addresses, and UPF network element 107 can forward these DNS request messages. EASDF network element 105 can receive DNS request messages and process them according to the DNS message processing rules in the DNS context, and then send the processed DNS request messages to DNS server 106. DNS server 106 can address the corresponding IP address based on the domain name in the DNS request message and can return the IP address to EASDF network element 105. EASDF network element 105 can forward the IP address sent by DNS server 106 to the corresponding user equipment.
[0072] Both user equipment 101 and user equipment 102 can send request messages to the corresponding application instances based on their IP addresses, and EDN / EMC node 108 can forward and process these request messages.
[0073] The application instance corresponding to the IP address can be either application instance 109 or application instance 110. Application instance 109 and application instance 110 are different instances of the same application under different slices, and each corresponds to a different IP address.
[0074] In one embodiment, when the slice where user device 101 is located is the same as the slice where the first instance of application 109 is located, user device 101 accesses the first instance of application 109 when accessing the application; when the slice where user device 102 is located is the same as the slice where the second instance of application 110 is located, user device 102 accesses the second instance of application 110 when accessing the application.
[0075] User equipment 101 or user equipment 102, gNB base station 103, SMF network element 104, EASDF network element 105, DNS server 106, UPF network element 107, EDN / EMC node 108, and application first instance 109 or application second instance 110 establish a communication connection based on a network, which can be a wired network or a wireless network.
[0076] In some embodiments, the aforementioned wireless or wired networks use standard communication technologies and / or protocols. The network is typically the Internet, but can be any network, including but not limited to Local Area Networks (LANs), Metropolitan Area Networks (MANs), Wide Area Networks (WANs), mobile, wired or wireless networks, private networks, or any combination of virtual private networks. In some embodiments, technologies and / or formats, including Hyper Text Markup Language (HTML), Extensible Markup Language (XML), etc., are used to represent data exchanged over the network. Furthermore, conventional encryption technologies such as Secure Socket Layer (SSL), Transport Layer Security (TLS), Virtual Private Networks (VPNs), and Internet Protocol Security (IPsec) can be used to encrypt all or some links. In other embodiments, custom and / or dedicated data communication technologies may be used to replace or supplement the aforementioned data communication technologies.
[0077] User equipment 101 and user equipment 102 can be various electronic devices, including but not limited to smartphones, tablets, laptops, desktop computers, wearable devices, augmented reality devices, virtual reality devices, etc. Application first instance 109 and application second instance 110 can be two instances of any application under different slices; this disclosure does not limit this.
[0078] The following detailed description of this exemplary implementation method is provided in conjunction with the accompanying drawings and embodiments.
[0079] This disclosure provides an addressing method that can be executed by any electronic device with computing capabilities, such as an EASDF network element.
[0080] Figure 2A flowchart of an addressing method according to an embodiment of this disclosure is shown, such as Figure 2 As shown, the addressing method provided in this embodiment includes steps S201 to S205.
[0081] In step S201, the EASDF network element receives a DNS context generation request message sent by the Session Management Function (SMF). The DNS context generation request message includes the slice identifier of the slice where the corresponding session is located.
[0082] Before explaining step S201, it's necessary to explain when the SMF network element sends a DNS context generation request message to the EASDF network element. In the 5G core network, a user equipment (UE) needs to establish a session before accessing an application instance. The session establishment process includes: the UE initiating a slice session establishment request to the SMF network element; this slice session establishment request is received by the 5G base station where the UE is located; after receiving the slice session establishment request, the 5G base station forwards the slice session establishment request to the SMF network element; after receiving the slice session establishment request, the SMF network element establishes the corresponding session and sends a response message indicating successful session establishment to the UE. Afterwards, the SMF network element sends the DNS context generation request message corresponding to this session to the EASDF network element. Upon receiving the DNS context generation request message from the SMF, the EASDF network element also completes step S201 accordingly.
[0083] The slice session establishment request sent by the user equipment to the SMF network element includes the slice identifier (S-NSSAI) of the slice where the user equipment is located, and the S-NSSAI is the same as the slice identifier included in the DNS context generation request message received by the EASDF network element. The response message sent by the SMF network element to the UE indicating successful session establishment carries the IP address of the EASDF network element, so that the UE can send the domain name resolution request (DNS) message to the EASDF network element indicated by the IP address.
[0084] In step S202, the EASDF network element receives a DNS request message sent by the user equipment (UE) corresponding to the session.
[0085] Continuing with the description of the session establishment process in step S201, the SMF network element sends a response message indicating successful session establishment to the UE. Upon receiving this response message, the UE generates a DNS request message with the destination IP address as the IP address of the EASDF network element included in the response message. This DNS request message includes the domain name that the UE needs to access.
[0086] Since the DNS destination address is the IP address of the EASDF network element, the DNS request message will be forwarded to the EASDF network element via the UPF network element, and the EASDF network element will then complete step S202.
[0087] Step S203: The EASDF network element obtains the external identifier of the slice corresponding to the slice identifier.
[0088] The slice identifier is the S-NSSAI carried in the DNS context generation request message. The external slice identifier can be a field uniquely identifying the slice, specified by the edge system; this disclosure does not limit this and can be determined according to the agreement between the EASDF network element and the DNS server. In some embodiments, the external slice identifier agreed upon by the EASDF network element and the DNS server is an enterprise code, or the DN (Delivery Network) environment number corresponding to the slice, or other readable fields.
[0089] In one embodiment, the EASDF network element is configured with a DNS message detection template for detecting whether a DNS request message needs to be processed. If the DNS request message matches the DNS message detection template, the DNS request message is processed; otherwise, the DNS request message is forwarded to the DNS server.
[0090] In one embodiment, the EASDF network element obtains the external identifier of the slice corresponding to the slice identifier, including: obtaining the external identifier of the slice corresponding to the slice identifier when the DNS request message matches the DNS message detection template. In some embodiments, the DNS message detection template can be a template for detecting domain names. In this case, matching the DNS request message with the DNS message detection template includes: the domain name included in the DNS request message belongs to the domain name in the DNS message detection template.
[0091] In one embodiment, the EASDF network element is configured with an internal and external identifier mapping table for slices. The internal and external identifier mapping table records slice identifiers and corresponding external identifiers of slices. The EASDF network element obtains the external identifier of the slice corresponding to the slice identifier by: querying the internal and external identifier mapping table based on the slice identifier to obtain the external identifier of the slice.
[0092] For example, part of the internal and external identifier mapping table is shown in Table 1. The external identifier corresponding to slice identifier 1 is the first enterprise code, and the external identifier corresponding to slice identifier 2 is the second enterprise code.
[0093] Table 1
[0094] Slice Identifier (S-NSSAI) External markings of the slice Slice Identifier 1 First Enterprise Code Slice identifier 2 Second Enterprise Code
[0095] If the slice identifier included in the DNS context generation request message is slice identifier 1, the EASDF network element queries the internal and external identifier mapping table to obtain the first enterprise code corresponding to slice identifier 1. It should be noted that the external slice identifier in Table 1 uses the enterprise code representation. Similarly, other representation methods can also be used to represent the external slice identifier. The embodiments of this disclosure do not limit this; the external slice identifier can be determined based on the agreement between the EASDF network element and the DNS server.
[0096] In step S204, the EASDF network element inserts the external identifier of the slice into the DNS request message.
[0097] In one embodiment, the EASDF network element inserts the slice external identifier into the DNS request message, including: performing eDNS (Extension mechanisms for DNS) processing on the DNS request message so that the processed DNS request message includes an OPT (pseudo-resource record), the OPT including a first variable part RDATA field; and inserting the slice external identifier into the first RDATA field. Exemplarily, the structure of the first RDATA field is as follows: Figure 3 As shown in (1), the structure after inserting the slice external identifier in the first RDATA field is as follows: Figure 3 As shown in (2) of the text.
[0098] EASDF network elements process DNS messages based on DNS message processing rules, which reside within the DNS context. Specifically, the information required to generate the DNS context is provided by the DNS context generation request message, which includes the DNS message processing rules.
[0099] Before proceeding to step S204, the EASDF network element further includes: generating a corresponding DNS context based on the DNS context generation request message received from the SMF network element. For example, some of the contents of the generated DNS context are shown in Table 2. Here, IPv4 (Internet Protocol version 4), IPv6 (Internet Protocol version 6), PDU (Protocol Data Unit), DNN (Data Network Name), C indicates optional, and M indicates mandatory.
[0100] Table 2
[0101] Feature name Data types necessity quantity describe ueIpv4Addr Ipv4Addr C 0..1 UE's IPv4 address ueIpv6Addr Ipv6Addr C 0..1 UE's IPv6 address dnn Dnn M 1 DNN of PDU Session S-NSSAI S-NSSAI M 1 PDU session slice identifier dnsRules map(DnsRule) M 1..N DNS message processing rules notifyUri Uri C 0..1 Callback address for subscribed messages supportedFeatures SupportedFeatures C 0..1 Capacity Negotiation
[0102] Table 2 lists `dnsRules` as DNS message processing rules. `dnsRules` specifies how an EASDF network element should process a DNS request message it receives. In one embodiment, the `EcsOptionInfo` field in `dnsRules` defines that the `eDNS` field carries an external slice identifier. For example, the `EcsOptionInfo` field defines that the external slice identifier is carried in the first `RDATA` field. In another embodiment, the `ForwardingParameter` field in `dnsRules` defines the operation of adding the external slice identifier to the `eDNS` field. For example, the `ForwardingParameter` field defines that the external slice identifier is inserted into the first `RDATA` field. In this case, inserting the external slice identifier into the first `RDATA` field includes: the EASDF network element inserts the external slice identifier into the first `RDATA` field according to the operations defined by the `EcsOptionInfo` and `ForwardingParameter` fields in `dnsRules`.
[0103] In step S205, the EASDF network element sends a DNS request message with an external slice identifier inserted to the DNS server, so that the DNS server can determine the Internet Protocol IP address of the application under the slice corresponding to the domain name included in the DNS request message based on the external slice identifier.
[0104] In one embodiment, the DNS server is a local DNS server. After receiving a DNS request message with an inserted external segment identifier, the local DNS server can determine the IP address of the application corresponding to the domain name to be resolved in the DNS request message within the segment based on the inserted external segment identifier. This IP address is the IP address mapped to the application corresponding to the domain name in the edge network where the UE is located. When the UE accesses the IP address mapped to the application in the local edge network, the UE can receive the response message packet more quickly.
[0105] In another embodiment, the DNS server receiving the DNS request message is a central DNS server. The central DNS server cannot directly resolve the IP address of the domain name in the UE's location based on the slice external identifier and the domain name. Therefore, before sending a DNS request message with the slice external identifier inserted to the DNS server, the EASDF network element further includes: obtaining the UE's location information through the network; mapping the UE's location information to a location identifier corresponding to the edge network where the UE is located; and inserting the location identifier into the first RDATA field.
[0106] This disclosure does not limit how the EASDF network element obtains the UE's location information through the network. For example, the UE's location information can be obtained from the SMF network element through a subscription. In one embodiment, the UE's location information is the base station identifier of the UE's location. The base station identifier can be any information that can represent the location of a base station; this disclosure does not limit this. For example, the base station identifier can be the base station number.
[0107] In one embodiment, mapping the UE's location information to a location identifier corresponding to the edge network where the UE is located includes: mapping the UE's location information to a location identifier of the edge network where the UE is located, as agreed upon by the EASDF network element and the central DNS server. This disclosure does not limit the type of location identifier agreed upon by the EASDF network element and the central DNS server. In some embodiments, the agreed location identifier may be an IP address, or it may be the UE's location information directly used as the location identifier of the edge network where the UE is located.
[0108] The method of inserting the location identifier into the first RDATA field is the same as the method of inserting the slice external identifier into the first RDATA field in step S204, and will not be repeated here. In one embodiment, the structure of the first RDATA field after inserting the slice external identifier and the location identifier is as follows: Figure 4 As shown.
[0109] In another embodiment, the DNS server receiving the DNS request message is the central DNS server, and the OPT field of the DNS request message after eDNS processing also includes a second RDATA field. Before the EASDF network element sends the DNS request message with the inserted slice external identifier to the DNS server, it also includes: obtaining the UE's location information through the network; mapping the UE's location information to a location identifier corresponding to the edge network where the UE is located; and inserting the location identifier into the second RDATA field.
[0110] The method of inserting the location identifier into the second RDATA field is the same as the method of inserting the slice external identifier into the first RDATA field in step S204, and will not be repeated here. For example, the structures of the first RDATA field and the second RDATA field after inserting the slice external identifier and the location identifier respectively are as follows: Figure 5 As shown.
[0111] It should be noted that, in the case where the DNS server is the central DNS server, the DNS message processing rules can support EASDF network elements to insert the location identifier into the first RDATA field or the second RDATA field.
[0112] In one embodiment, when the DNS server is the central DNS server, the EASDF network element sends a DNS request message with an inserted slice external identifier to the DNS server, including: sending a DNS request message with an inserted slice external identifier and a location identifier to the central DNS server, so that the central DNS server can determine the IP address of the application under the slice corresponding to the domain name to be resolved in the DNS request message based on the slice external identifier and the location identifier.
[0113] The technical solution provided in this disclosure involves the EASDF receiving a DNS context generation request message carrying a slice identifier from the SMF. The EASDF then obtains the corresponding external slice identifier based on the slice identifier and inserts it into a DNS request message sent by the UE. This external slice identifier is then carried to the DNS server via the DNS request message, allowing the DNS server to determine the IP address of the application corresponding to the domain name included in the DNS request message within the slice. This method provides an addressing mechanism for finding the IP address of the application instance corresponding to a slice without requiring the construction of a dedicated channel or the configuration of channel mapping.
[0114] Furthermore, it enables user devices to directly obtain and access the IP address of the application instance under the slice, avoiding the need for continuous analysis and identification of slice services during user device access, improving end-to-end service performance, and enabling the slice to provide end-to-end service guarantee for users.
[0115] This disclosure provides another addressing method that can be executed by any electronic device with computing capabilities, such as a DNS server.
[0116] Figure 6 A flowchart of another addressing method in an embodiment of this disclosure is shown, such as Figure 6 As shown, the addressing method provided in this embodiment includes steps S601 and S602.
[0117] In step S601, the DNS server receives a DNS request message sent by the Edge Application Server Discovery Function (EASDF). The DNS request message includes the external identifier of the slice.
[0118] After the EASDF network element inserts the external identifier of the slice into the DNS request message, it sends the DNS request message to the DNS server. Upon receiving the DNS request message, the DNS server completes step S601 accordingly.
[0119] In step S602, the DNS server determines the Internet Protocol IP address of the application corresponding to the domain name included in the DNS request message under the slice corresponding to the slice external identifier, based on the slice external identifier.
[0120] In one embodiment, the DNS server is a central DNS server configured with an enhanced resolution table. The enhanced resolution includes domain name information and a location identifier, a slice external identifier, and an IP address corresponding to the domain name information. The DNS request message also includes the location identifier. The DNS server determines the Internet Protocol IP address of the application corresponding to the domain name included in the DNS request message under the slice corresponding to the slice external identifier based on the slice external identifier. This includes: querying the enhanced resolution table based on the location identifier, slice external identifier, and domain name included in the DNS request message to obtain the IP address of the application corresponding to the domain name included in the DNS request message under the slice.
[0121] For example, some parts of the enhanced parsing table are shown in Table 3.
[0122] Table 3
[0123]
[0124]
[0125] As shown in Table 3, the same domain name can have different IP addresses under different slices in the same location. For example, if the DNS request message includes the domain name as domain name1, the location identifier as location identifier1, and the slice external identifier as identifier2, then the central DNS server will obtain the second IP address by querying the enhanced resolution table.
[0126] In another embodiment, the DNS server is a local DNS server configured with an enhanced resolution table. The enhanced resolution includes domain name information and the slice external identifier and IP address corresponding to the domain name information. The DNS server determines the Internet Protocol IP address of the application corresponding to the domain name included in the DNS request message under the slice corresponding to the slice external identifier based on the slice external identifier, including: querying the enhanced resolution table based on the slice external identifier and domain name included in the DNS request message to obtain the IP address of the application corresponding to the domain name included in the DNS request message under the slice.
[0127] For example, some parts of the enhanced parsing table are shown in Table 4.
[0128] Table 4
[0129] domain name External markings of the slice IP address Domain A Identifier A Fifth IP address Domain A Identifier B Sixth IP address Domain B Identifier A Seventh IP address Domain B Identifier B Eighth IP address
[0130] For example, if the DNS request message includes the domain name B and the external identifier of the slice A, the local DNS server will obtain the seventh IP address by querying the enhanced resolution table.
[0131] In one embodiment, after the DSN server determines the IP address of the application corresponding to the domain name included in the DNS request message under the slice, it sends the IP address to the UE so that the UE can access the corresponding application instance based on the IP address.
[0132] To facilitate understanding, the following will combine... Figure 2 Corresponding addressing methods and Figure 6 The corresponding addressing methods are used to illustrate the technical solutions of the embodiments of this disclosure.
[0133] like Figure 7 As shown, the process of UE accessing application instances under a slice includes S701 to S711.
[0134] S701: PDU slice session establishment;
[0135] S702: SMF network element selection: EASDF network element;
[0136] S703: The SMF network element sends a DNS context generation request containing the slice identifier to the EASDF network element;
[0137] S704: The EASDF network element sends a DNS context generation response message to the SMF network element;
[0138] S705: The UE sends a DNS request message to the EASDF network element;
[0139] S706: EASDF network elements perform eDNS processing on DNS request messages and add an external slice identifier to the eDNS field;
[0140] S707: The EASDF network element sends a processed DNS request message to the DNS server;
[0141] S708: The DNS server processes DNS request messages and obtains the IP address under the slice;
[0142] S709: The DNS server sends a response message, including the IP address, to the EASDF network element;
[0143] S710: The EASDF network element sends a response message including the IP address to the UE;
[0144] S711: The UE accesses the application instance corresponding to the IP address through a slice session.
[0145] Based on the same inventive concept, this disclosure also provides an addressing device, as described in the following embodiments. Since the principle by which this device embodiment solves the problem is similar to that of the above-described method embodiment, the implementation of this device embodiment can refer to the implementation of the above-described method embodiment, and repeated details will not be elaborated further.
[0146] Figure 8 This diagram illustrates an addressing device according to an embodiment of the present disclosure, which is applied to EASDF, such as... Figure 8 As shown, the device includes:
[0147] The receiving module 801 is used to receive a Domain Name System (DNS) Context Generation Request message sent by the Session Management Function (SMF). The DNS Context Generation Request message includes the slice identifier of the slice where the corresponding session is located.
[0148] The receiving module 801 is also used to receive DNS request messages sent by the user equipment (UE) corresponding to the session;
[0149] The acquisition module 802 is used to acquire the external identifier of the slice corresponding to the slice identifier;
[0150] Processing module 803 is used to insert the slice external identifier into the DNS request message;
[0151] The sending module 804 is used to send a DNS request message with an external slice identifier inserted to the DNS server, so that the DNS server can determine the Internet Protocol IP address of the application under the slice corresponding to the domain name included in the DNS request message based on the external slice identifier.
[0152] In one embodiment of this disclosure, EASDF is configured with a DNS message detection template; the acquisition module 802 is used to acquire the external identifier of the slice identifier corresponding to the slice identifier when the DNS request message matches the DNS message detection template.
[0153] In one embodiment of this disclosure, EASDF is configured with an internal and external identifier mapping table for slices. The acquisition module 802 is used to query the internal and external identifier mapping table based on the slice identifier to obtain the external identifier of the slice.
[0154] In one embodiment of this disclosure, the processing module 803 is configured to perform DNS extension mechanism eDNS processing on the DNS request message, so that the processed DNS request message includes a pseudo resource record OPT, the OPT including a first variable part RDATA field; and to insert the slice external identifier into the first RDATA field.
[0155] In one embodiment of this disclosure, the DNS server is a central DNS server; the processing module 803 is further configured to obtain the location information of the UE through the network; map the location information of the UE to a location identifier corresponding to the edge network where the UE is located; insert the location identifier into the first RDATA field; and the sending module 804 is configured to send a DNS request message with the inserted slice external identifier and location identifier to the central DNS server.
[0156] In one embodiment of this disclosure, OPT further includes a second RDATA field, and the DNS server is a central DNS server; the processing module 803 is further configured to obtain the location information of the UE through the network; map the location information of the UE to a location identifier corresponding to the edge network where the UE is located; insert the location identifier into the second RDATA field; and the sending module 804 is configured to send a DNS request message with the slice external identifier and the location identifier inserted to the central DNS server.
[0157] The technical solution provided in this disclosure involves the EASDF receiving a DNS context generation request message carrying a slice identifier from the SMF. The EASDF then obtains the corresponding external slice identifier based on the slice identifier and inserts it into a DNS request message sent by the UE. This external slice identifier is then carried to the DNS server via the DNS request message, allowing the DNS server to determine the IP address of the application corresponding to the domain name included in the DNS request message within the slice. This method provides an addressing mechanism for finding the IP address of an application instance within a slice without requiring the construction of a dedicated channel or the configuration of channel mapping.
[0158] Furthermore, it enables user devices to directly obtain and access the IP address of the application instance under the slice, avoiding the need for continuous analysis and identification of slice services during user device access, improving end-to-end service performance, and enabling the slice to provide end-to-end service guarantee for users.
[0159] Figure 9 This illustration shows another addressing device in an embodiment of the present disclosure, which is applied to a DNS server, such as... Figure 9 As shown, the device includes:
[0160] The receiving module 901 is used to receive DNS request messages sent by EASDF, the DNS request messages including the external identifier of the slice;
[0161] The determination module 902 is used to determine the IP address of the application corresponding to the domain name included in the DNS request message under the slice corresponding to the slice external identifier, based on the slice external identifier.
[0162] In one embodiment of this disclosure, the DNS server is a central DNS server, which is configured with an enhanced resolution table. The enhanced resolution includes domain name information and a location identifier, slice external identifier, and IP address corresponding to the domain name information. The DNS request message also includes a location identifier. The determining module 902 is used to query the enhanced resolution table based on the location identifier, slice external identifier, and domain name included in the DNS request message to obtain the IP address of the application under the slice corresponding to the domain name included in the DNS request message.
[0163] In one embodiment of this disclosure, the DNS server is a local DNS server, which is configured with an enhanced resolution table. The enhanced resolution table includes domain name information and the slice external identifier and IP address corresponding to the domain name information. The determination module 902 is used to query the enhanced resolution table based on the slice external identifier and domain name included in the DNS request message to obtain the IP address of the application under the slice corresponding to the domain name included in the DNS request message.
[0164] Those skilled in the art will understand that various aspects of this disclosure can be implemented as a system, method, or program product. Therefore, various aspects of this disclosure can be specifically implemented in the following forms: a completely hardware implementation, a completely software implementation (including firmware, microcode, etc.), or a combination of hardware and software aspects, collectively referred to herein as a "circuit," "module," or "system."
[0165] The following reference Figure 10 To describe an electronic device 1000 according to such an embodiment of the present disclosure. Figure 10 The electronic device 1000 shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments disclosed herein.
[0166] like Figure 10 As shown, the electronic device 1000 is presented in the form of a general-purpose computing device. The components of the electronic device 800 may include, but are not limited to: at least one processing unit 1010, at least one storage unit 1020, and a bus 1030 connecting different system components (including storage unit 1020 and processing unit 1010).
[0167] The storage unit stores program code, which can be executed by the processing unit 1010, causing the processing unit 1010 to perform the steps described in the "Detailed Description" section of this specification according to various exemplary embodiments of this disclosure.
[0168] Storage unit 1020 may include a readable medium in the form of a volatile storage unit, such as a random access memory unit (RAM) 1021 and / or a cache memory unit 1022, and may further include a read-only memory unit (ROM) 1023.
[0169] Storage unit 1020 may also include a program / utility 1024 having a set (at least one) program module 1025, such program module 1025 including but not limited to: operating system, one or more application programs, other program modules and program data, each or some combination of these examples may include an implementation of a network environment.
[0170] Bus 1030 can represent one or more of several types of bus structures, including a memory cell bus or memory cell controller, a peripheral bus, a graphics acceleration port, a processing unit, or a local bus using any of the multiple bus structures.
[0171] Electronic device 1000 can also communicate with one or more external devices 1040 (e.g., keyboard, pointing device, Bluetooth device, etc.), and with one or more devices that enable a user to interact with the electronic device 1000, and / or with any device that enables the electronic device 1000 to communicate with one or more other computing devices (e.g., router, modem, etc.). This communication can be performed via input / output (I / O) interface 1050. Furthermore, electronic device 1000 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public networks, such as the Internet) via network adapter 1060. Figure 10 As shown, network adapter 1060 communicates with other modules of electronic device 1000 via bus 1030. It should be understood that, although not shown in the figure, other hardware and / or software modules can be used in conjunction with electronic device 1000, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.
[0172] From the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solutions according to the embodiments of this disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, external hard drive, etc.) or on a network, including several instructions to cause a computing device (such as a personal computer, server, terminal device, or network device, etc.) to execute the methods according to the embodiments of this disclosure.
[0173] In exemplary embodiments of this disclosure, a computer-readable storage medium is also provided, which may be a readable signal medium or a readable storage medium. A program product capable of implementing the methods described above is stored thereon. In some possible implementations, various aspects of this disclosure may also be implemented as a program product including program code, which, when run on a terminal device, causes the terminal device to perform the steps of the various exemplary embodiments of this disclosure described in the "Detailed Description" section above.
[0174] More specific examples of computer-readable storage media in this disclosure may include, but are not limited to: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.
[0175] In this disclosure, a computer-readable storage medium may include a data signal propagated in baseband or as part of a carrier wave, carrying readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A readable signal medium may also be any readable medium other than a readable storage medium, capable of transmitting, propagating, or transmitting a program for use by or in connection with an instruction execution system, apparatus, or device.
[0176] Optionally, the program code contained on the computer-readable storage medium may be transmitted using any suitable medium, including but not limited to wireless, wired, optical fiber, RF, etc., or any suitable combination thereof.
[0177] In practical implementation, program code for performing the operations of this disclosure can be written in any combination of one or more programming languages, including object-oriented programming languages such as Java and C++, and conventional procedural programming languages such as C or similar languages. The program code can execute entirely on the user's computing device, partially on the user's device, as a standalone software package, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).
[0178] It should be noted that although several modules or units for the device used to perform actions have been mentioned in the detailed description above, this division is not mandatory. In fact, according to embodiments of this disclosure, the features and functions of two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided and embodied by multiple modules or units.
[0179] Furthermore, although the steps of the method in this disclosure are described in a specific order in the accompanying drawings, this does not require or imply that the steps must be performed in that specific order, or that all the steps shown must be performed to achieve the desired result. Additional or alternative steps may be omitted, multiple steps may be combined into one step, and / or a step may be broken down into multiple steps.
[0180] From the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solutions according to the embodiments of this disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, external hard drive, etc.) or on a network, including several instructions to cause a computing device (such as a personal computer, server, mobile terminal, or network device, etc.) to execute the methods according to the embodiments of this disclosure.
[0181] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope of this disclosure is indicated by the appended claims.
Claims
1. An addressing method, characterized by, The EASDF, used for edge application server discovery, includes: Receive a DNS context generation request message sent by the Session Management Function (SMF), wherein the DNS context generation request message includes the slice identifier of the slice where the corresponding session is located; Receive the DNS request message sent by the user equipment (UE) corresponding to the session; Obtain the external identifier of the slice corresponding to the slice identifier. The EASDF is configured with an internal and external identifier mapping table for slices. Obtaining the external identifier of the slice corresponding to the slice identifier includes: querying the internal and external identifier mapping table based on the slice identifier to obtain the external identifier of the slice; the internal and external identifier mapping table is configured with the mapping relationship between the slice identifier and the external identifier of the slice. Insert the external identifier of the slice into the DNS request message; A DNS request message containing the external identifier of the slice is sent to a DNS server so that the DNS server can determine the Internet Protocol IP address of the application under the slice corresponding to the domain name included in the DNS request message based on the external identifier of the slice.
2. The method of claim 1, wherein, The EASDF is configured with a DNS message detection template; obtaining the external identifier of the slice corresponding to the slice identifier includes: If the DNS request message matches the DNS message detection template, obtain the external identifier of the slice corresponding to the slice identifier.
3. The method of claim 1, wherein, The step of inserting the external identifier of the slice into the DNS request message includes: The DNS request message is processed by the DNS extension mechanism eDNS so that the processed DNS request message includes a pseudo resource record (OPT), the OPT including a first variable part RDATA field; Insert the external identifier of the slice into the first RDATA field.
4. The method of claim 3, wherein, The DNS server is a central DNS server; before sending the DNS request message with the external identifier of the slice inserted to the DNS server, the method further includes: The location information of the UE is obtained through the network; the location information of the UE is mapped to a location identifier corresponding to the edge network where the UE is located; Insert the location identifier into the first RDATA field; Sending a DNS request message to the DNS server with the external identifier of the slice inserted includes: Send a DNS request message containing the external identifier of the slice and the location identifier to the central DNS server.
5. The method of claim 3, wherein, The OPT further includes a second RDATA field, and the DNS server is a central DNS server; before sending the DNS request message with the external identifier of the slice inserted to the DNS server, the method further includes: The location information of the UE is obtained through the network; the location information of the UE is mapped to a location identifier corresponding to the edge network where the UE is located; Insert the location identifier into the second RDATA field; Sending a DNS request message to the DNS server with the external identifier of the slice inserted includes: Send a DNS request message containing the external identifier of the slice and the location identifier to the central DNS server.
6. An addressing method, characterized by, Used in Domain Name System (DNS) servers, including: Receive a DNS request message sent by the Edge Application Server Discovery Function (EASDF). The DNS request message includes a slice external identifier, wherein there is a mapping relationship between the slice external identifier and the slice identifier, and the mapping relationship is configured by the internal and external identifier mapping table. The slice identifier is the slice identifier of the slice where the corresponding session is located, which is included in the DNS context generation request message. Based on the external identifier of the slice, determine the Internet Protocol IP address of the application under the slice corresponding to the domain name included in the DNS request message; The DNS server is configured with an enhanced resolution table, which includes domain name information and the corresponding slice external identifier and IP address. Specifically, determining the Internet Protocol (IP) address corresponding to the domain name included in the DNS request message, based on the external slice identifier, and applying it under the slice corresponding to the external slice identifier, includes: Based on the DNS request message, the enhanced resolution table is queried to obtain the IP address of the application under the slice corresponding to the domain name included in the DNS request message.
7. The method of claim 6, wherein, The DNS server is a central DNS server, which is configured with an enhanced resolution table. The enhanced resolution table includes domain name information and a location identifier, slice external identifier, and IP address corresponding to the domain name information. The DNS request message also includes the location identifier. The step of determining the Internet Protocol (IP) address corresponding to the domain name included in the DNS request message, which is applied to the slice corresponding to the external slice identifier, based on the external slice identifier includes: Based on the location identifier, slice external identifier, and domain name included in the DNS request message, the enhanced resolution table is queried to obtain the IP address of the application under the slice corresponding to the domain name included in the DNS request message.
8. The method of claim 6, wherein, The DNS server is a local DNS server, which is configured with an enhanced resolution table. The enhanced resolution table includes domain name information and the slice external identifier and IP address corresponding to the domain name information. The step of determining the Internet Protocol (IP) address corresponding to the domain name included in the DNS request message, which is applied to the slice corresponding to the external slice identifier, based on the external slice identifier includes: Based on the external identifier and domain name of the slice included in the DNS request message, the enhanced resolution table is queried to obtain the IP address of the application under the slice corresponding to the domain name included in the DNS request message.
9. An addressing device, characterized by The EASDF, used for edge application server discovery, includes: The receiving module is used to receive a Domain Name System (DNS) Context Generation Request message sent by the Session Management Function (SMF), wherein the DNS Context Generation Request message includes the slice identifier of the slice where the corresponding session is located. The receiving module is also used to receive a DNS request message sent by the user equipment (UE) corresponding to the session; The acquisition module is used to acquire the external identifier of the slice corresponding to the slice identifier; the EASDF is configured with an internal and external identifier mapping table for slices, wherein the acquisition module is specifically used to: query the internal and external identifier mapping table according to the slice identifier to obtain the external identifier of the slice; the internal and external identifier mapping table is configured with a mapping relationship between the slice identifier and the external identifier of the slice; The processing module is used to insert the external identifier of the slice into the DNS request message; The sending module is used to send a DNS request message containing the external identifier of the slice to the DNS server, so that the DNS server can determine the Internet Protocol IP address of the domain name included in the DNS request message under the slice based on the external identifier of the slice.
10. An addressing device, characterized by Used in Domain Name System (DNS) servers, including: The receiving module is used to receive a DNS request message sent by the Edge Application Server Discovery Function (EASDF). The DNS request message includes a slice external identifier, wherein there is a mapping relationship between the slice external identifier and the slice identifier, and the mapping relationship is configured by an internal and external identifier mapping table. The slice identifier is the slice identifier of the slice where the corresponding session is located, which is included in the DNS context generation request message. The determining module is used to determine, based on the external identifier of the slice, the Internet Protocol IP address corresponding to the domain name included in the DNS request message, which is applied under the slice corresponding to the external identifier of the slice; The DNS server is configured with an enhanced resolution table, which includes domain name information and the corresponding slice external identifier and IP address. The determining module is specifically used to: query the enhanced resolution table according to the DNS request message to obtain the IP address of the application under the slice corresponding to the domain name included in the DNS request message.
11. An electronic device, comprising: include: processor; as well as Memory for storing the executable instructions of the processor; The processor is configured to execute the addressing method of any one of claims 1 to 5, or the addressing method of any one of claims 6 to 8, by executing the executable instructions.
12. A computer readable storage medium having stored thereon a computer program, characterized in that, When the computer program is executed by the processor, it implements the addressing method according to any one of claims 1 to 5, or the addressing method according to any one of claims 6 to 8.
Citation Information
Patent Citations
Address information sending method, address information obtaining method, address information sending device, address information obtaining device, equipment and medium
CN113115480A
Edge application server discovery method and device, block chain system and medium
CN114338603A
