HK40048395B - Address information sending method, acquiring method, apparatus, device, and medium - Google Patents

Description

Address information sending methods, acquisition methods, devices, equipment and media

Technical Field

This application relates to the field of mobile communications, and in particular to a method, method, apparatus, device, and medium for sending and obtaining address information.

Background Technology

The 5G core network (5G Core, 5GC) supports edge computing using Protocol Data Unit (PDU) sessions.

In edge computing scenarios, Domain Name System (DNS) queries sent by User Equipment (UE) are handled by the Edge Application Server Discovery Function (EASDF).

However, how the UE obtains the EASDF address information before the DNS query is an unresolved technical problem.

Summary of the Invention

This application provides a method, method, apparatus, device, and medium for sending and obtaining address information, and provides an EASDF allocation mechanism based on UE-initiated activation. The technical solution is as follows:

According to one aspect of this application, a method for sending address information is provided, applied in a Session Management Function (SMF), the method comprising:

Receive the first identifier sent by the UE during the Protocol Data Unit (PDU) session establishment process;

Select a first EASDF for the UE based on the first identifier;

The address information of the first EASDF is sent to the UE.

According to one aspect of this application, an address information acquisition method is provided, applied in a UE, the method comprising:

During the PDU session establishment process, a first identifier is sent to the SMF, which is used to trigger the SMF to locate and select a first EASDF for the UE.

Receive the address information of the first EASDF.

According to another aspect of this application, an address information sending apparatus is provided, the apparatus comprising:

The receiving module is used to receive the first identifier sent by the UE during the PDU session establishment process;

The selection module is configured to select a first EASDF for the UE based on the first identifier;

The sending module is used to send the address information of the first EASDF to the UE.

According to another aspect of this application, an address information acquisition device is provided, the device comprising:

The sending module is used to send a first identifier to the SMF during the PDU session establishment process. The first identifier is used to trigger the SMF to locate and select a first EASDF for the terminal.

The receiving module is used to receive the address information of the first EASDF.

According to one aspect of this application, a network element device is provided, the network element device comprising: a processor and a memory, the memory storing a computer program, the computer program being loaded and executed by the processor to implement the address information transmission method as described above.

According to one aspect of this application, a terminal is provided, the terminal comprising: a processor and a memory, the memory storing a computer program, the computer program being loaded and executed by the processor to implement the address information acquisition method as described above.

According to another aspect of this application, a computer-readable storage medium is provided, the storage medium storing a computer program, the computer program being loaded and executed by a processor to implement the address information sending method or address information acquisition method as described above.

According to another aspect of this application, a computer program product is provided, the computer program product including computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, causing the computer device to perform the address information sending method or address information acquisition method provided in the above aspect.

According to another aspect of this application, a chip is provided, the chip being configured to perform the address information sending method or the address information acquisition method provided in the above aspects.

The beneficial effects of the technical solutions provided in this application include at least the following:

By having the UE send a first identifier to the SMF during the PDU session establishment process, triggering the SMF to select a first EASDF for the UE and send the address information of the first EASDF to the UE, the SMF can select a first EASDF for the UE in the scenario triggered by the UE. This avoids the problem of the SMF allocating EASDF to the UE in an unreasonable way, and achieves the effect of reasonably allocating EASDF when the UE has corresponding needs.

Attached Figure Description

To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

Figure 1 shows a structural block diagram of a communication system provided in an exemplary embodiment of this application;

Figure 2 shows a structural block diagram of a communication system provided in another exemplary embodiment of this application;

Figure 3 shows a flowchart of an address information sending method provided in an exemplary embodiment of this application;

Figure 4 shows a flowchart of an address information sending method provided in another exemplary embodiment of this application;

Figure 5 illustrates the signaling format diagram of a PDU session establishment request provided in an exemplary embodiment of this application;

Figure 6 shows a flowchart of an address information sending method provided in another exemplary embodiment of this application;

Figure 7 shows a flowchart of an address information acquisition method provided in another exemplary embodiment of this application;

Figure 8 shows a flowchart of an EASDF discovery method provided in an exemplary embodiment of this application;

Figure 9 shows a flowchart of a PDU session establishment method provided in another exemplary embodiment of this application;

Figure 10 shows a flowchart of a method for adding additional PDU session anchors and branch points or UL CL provided in another exemplary embodiment of this application;

Figure 11 shows a block diagram of an address information sending apparatus provided in an exemplary embodiment of this application;

Figure 12 shows a block diagram of an address information acquisition device provided in an exemplary embodiment of this application;

Figure 13 shows a block diagram of a network element device provided in an exemplary embodiment of this application.

Detailed Implementation

Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

It should be understood that "several" in this article refers to one or more, and "multiple" refers to two or more. "And/or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and/or B can represent: A alone, A and B simultaneously, or B alone. The character "/" generally indicates that the preceding and following related objects have an "or" relationship.

Edge computing provides cloud services and IT (Internet Technology) environment services at the edge of the network for application developers and service providers. The goal is to provide computing, storage, and network bandwidth close to data input or users. For example, if a user is using game A on their phone, the nearest edge computing server can be assigned to provide the game service, minimizing network latency.

Figure 1 illustrates a schematic diagram of the architecture of a communication system 100 provided in an exemplary embodiment of this application. As shown in Figure 1, the communication system 100 may include: a User Equipment (UE), a Radio Access Network (RAN), a Core Network, and a Data Network (DN). The UE, RAN, and Core are the main components of the architecture, logically divided into a user plane and a control plane. The control plane is responsible for the management of the mobile network, and the user plane is responsible for the transmission of service data. In Figure 1, the NG2 reference point is located between the RAN control plane and the Core control plane, the NG3 reference point is located between the RAN user plane and the Core user plane, and the NG6 reference point is located between the Core user plane and the data network.

UE (User Equipment): This is the entry point for mobile users to interact with the network. It provides basic computing and storage capabilities, displays service windows to the user, and accepts user input. The UE will use next-generation air interface technology to establish signal and data connections with the RAN (Radio Network Array), thereby transmitting control signals and service data to the mobile network.

RAN: Similar to a base station in a traditional network, it is deployed close to the UE (User Equipment) to provide network access for authorized users within the cell coverage area. It can transmit user data using transmission tunnels of different quality levels based on user level and service requirements. The RAN manages its own resources, utilizes them efficiently, and provides access services to the UE on demand, forwarding control signals and user data between the UE and the core network.

Core: Responsible for maintaining the subscription data of the mobile network, managing the network elements of the mobile network, and providing UE with functions such as session management, mobility management, policy management, and security authentication. When the UE attaches, it provides network access authentication; when the UE has a service request, it allocates network resources for the UE; when the UE moves, it updates network resources for the UE; when the UE is idle, it provides a fast recovery mechanism for the UE; when the UE detaches, it releases network resources for the UE; when the UE has service data, it provides data routing functions, such as forwarding uplink data to the DN; or receiving downlink data from the UE from the DN, forwarding it to the RAN, and then sending it to the UE.

DN: This is the data network that provides services to users. Generally, the client is located at the UE (User Equipment), and the server is located in the data network. The data network can be a private network, such as a local area network (LAN), an external network not controlled by the operator, such as the Internet, or a dedicated network jointly deployed by the operator, such as for configuring IP Multimedia Core Network Subsystem (IMS) services.

Figure 2 shows the detailed architecture based on Figure 1. The core network user plane includes the User Plane Function (UPF); the core network control plane includes the Authentication Server Function (AUSF), Access and Mobility Management Function (AMF), Session Management Function (SMF), Network Slice Selection Function (NSSF), Network Exposure Function (NEF), Network Function Repository Function (NRF), Unified Data Management (UDM), Policy Control Function (PCF), and Application Function (AF). The functions of these entities are as follows:

UPF: Performs user packet forwarding according to the routing rules of SMF;

AUSF: Performs security authentication for the UE;

AMF: UE Access and Mobility Management;

SMF: UE Session Management;

NSSF: Select network slices for the UE;

NEF: To expose network functions to third parties via API interfaces;

NRF: Provides storage and selection functions for network function entity information for other network elements;

UDM: User Subscription Context Management;

PCF: User Policy Management;

AF: User Application Management.

In the architecture shown in Figure 2, the N1 interface serves as the reference point between the UE and the AMF; the N2 interface serves as the reference point between the RAN and the AMF, used for sending NAS messages, etc.; the N3 interface serves as the reference point between the RAN and the UPF, used for transmitting user plane data, etc.; the N4 interface serves as the reference point between the SMF and the UPF, used for transmitting information such as tunnel identification information for N3 connections, data buffer indication information, and downlink data notification messages, etc.; the N6 interface serves as the reference point between the UPF and the DN, used for transmitting user plane data, etc. NG interface: The interface between the radio access network and the 5G core network.

It should be noted that the interface names between the network elements in Figures 1 and 2 are merely examples, and the interface names in actual implementations may be different. This application embodiment does not impose specific limitations on these names. Similarly, the names of the network elements (such as SMF, AF, UPF, etc.) included in Figures 1 and 2 are also merely examples and do not limit the functionality of the network elements themselves. In 5GS and other future networks, the aforementioned network elements may also have other names, and this application embodiment does not impose specific limitations on these names. For example, in 6G networks, some or all of the aforementioned network elements may use the terminology from 5G, or they may use other names, etc. This is explained uniformly here and will not be elaborated further below. Furthermore, it should be understood that the names of the messages (or signaling) transmitted between the aforementioned network elements are also merely examples and do not limit the functionality of the messages themselves.

Figure 3 shows a flowchart of an address information sending method provided in an exemplary embodiment of this application. This embodiment illustrates the method by applying it to an SMF (Software-Defined Fund). The method includes:

Step 320: The SMF receives the first identifier sent by the UE during the PDU session establishment process;

If the PDU session established this time belongs to the edge connection of edge computing, the UE sends the first identifier to the SMF. For example, if the PDU session established this time does not belong to the edge connection of edge computing, the UE does not send the first identifier to the SMF.

For example, the first identifier is used to indicate that the PDU session established this time is an edge connection for edge computing. For instance, when a user starts using a service application that supports edge computing in the UE, the UE establishes a PDU session for that service application.

For example, the first identifier includes an Edge Computing (EC) identifier, or an EASDF identifier.

Step 340: The SMF selects the first EASDF for the UE based on the first identifier;

During the PDU session establishment process, if the SMF receives the first identifier sent by the UE, it considers that the UE needs to allocate, locate, or select an EASDF.

The SMF selects a first EASDF for the UE according to a predetermined allocation principle. For example, the SMF is located at the EASDF closest to the UE in terms of geographical or network location, and is selected as the first EASDF. This embodiment does not limit how the SMF is located and how the first EASDF is selected.

Step 360: The SMF sends the address information of the first EASDF to the UE.

After the SMF selects a first EASDF for the UE, the SMF sends the address information of the first EASDF to the UE. Optionally, this address information refers to the Internet Protocol (IP) address of the first EASDF.

After obtaining the IP address of the first EASDF, the UE uses the DNS-related services provided by the first EASDF, such as the DNS query service.

In summary, the method provided in this embodiment, by having the UE send a first identifier to the SMF during the PDU session establishment process, triggering the SMF to select a first EASDF for the UE and send the address information of the first EASDF to the UE, enables the SMF to select a first EASDF for the UE in the scenario triggered by the UE. This avoids the problems of the SMF always assigning an EASDF that does not match the UE's location, or never assigning an EASDF to the UE, or using an unreasonable allocation method to assign an EASDF to the UE (such as selecting the lightest EASDF based on the EASDF load; or assigning a generic DNS Server). Instead, it achieves the effect of reasonably allocating an EASDF based on the UE's current location when the UE has corresponding needs.

In an optional embodiment based on Figure 3, the first identifier is carried in the PDU session establishment request, which is a signaling message sent by the UE to the SMF; the address information of the first EASDF is carried in the PDU session establishment accept, which is a signaling message sent by the SMF to the UE.

Figure 4 shows a flowchart of an address information sending method provided in an exemplary embodiment of this application. This embodiment illustrates the method by applying it to an SMF (Software-Defined Fund). The method includes:

Step 420: The SMF receives the PDU session establishment request sent by the UE. The first cell in the PDU session establishment request carries the first identifier.

If the PDU session established this time belongs to the edge connection of edge computing, the UE sends the first identifier to the SMF. For example, if the PDU session established this time does not belong to the edge connection of edge computing, the UE does not send the first identifier to the SMF.

For example, the first identifier is used to indicate that the PDU session established this time is an edge connection for edge computing. For instance, when a user starts using a service application that supports edge computing in the UE, the UE establishes a PDU session for that service application.

For example, the first identifier includes an EC identifier or an EASDF identifier. In this embodiment, the first identifier is carried in the first cell.

Figure 5 illustrates the signaling format of a PDU session establishment request in related technologies. A first information element is added to this signaling format to carry a first identifier. For example, this first information element is an Edge Computing Connection Indicator.

This first information cell can be added to any column in the signaling format shown in Figure 5. The type of this first information cell is optional.

It should be noted that the TLV format in Figure 5 consists of Type, Length, and Value. Type represents the message type; Length is the length of the value, and Value is the actual value. The lengths of T and L are fixed, while the length of V is specified by Length. TLV-E refers to the extended TLV format, where TV represents the message type and the actual value, and V is the actual value.

Step 440: The SMF selects the first EASDF for the UE based on the first identifier;

During the PDU session establishment process, the SMF receives a PDU session establishment request sent by the UE. The first cell in the PDU session establishment request carries a first identifier. If the SMF parses the first identifier sent by the UE in the PDU session establishment request, it considers that the UE needs to allocate, locate, or select an EASDF.

The SMF selects the first EASDF for the UE from multiple candidate EASDFs according to a predetermined allocation principle. For example, the SMF locates the EASDF that is geographically or network-wise closest to the UE and selects it as the first EASDF. This embodiment does not limit how the SMF locates and selects the first EASDF.

Step 460: The SMF sends a PDU session establishment confirmation to the UE, which carries the address information of the first EASDF.

After the SMF selects a first EASDF for the UE, the SMF sends the address information of the first EASDF to the UE. Optionally, this address information refers to the IP address of the first EASDF. After obtaining the IP address of the first EASDF, the UE uses the DNS-related services provided by the first EASDF.

Optionally, the SMF sends a PDU session establishment confirmation to the UE, which carries the address information of the first EASDF.

Optionally, the PDU session establishment confirmation includes an Extended Protocol Configuration Options (EPCO) cell. The address information of the first EASDF is carried in a third cell within this EPCO cell. For example, this third cell is cell 0003.

Step 482: After the PDU session is established, receive the Dynamic Host Configuration Protocol (DHCP) request sent by the terminal;

After the PDU session is established, the UE may obtain the address of a DNS server by initiating a DHCP request to the SMF through the user. At this time, the SMF also needs to send a DHCP response to the UE, which contains the address information of the first EASDF, that is, the IP address of the first EASDF.

Step 484: Send a DHCP response to the terminal, which carries the address information of the first EASDF.

For example, the fourth cell of the EPCO cell in the DHCP response carries the address information of the first EASDF.

That is, if the SMF provides the address information of the first EASDF in the EPCO cell of the PDU session establishment request, then the SMF also needs to include the same address information of the first EASDF in the DHCP response.

It should be noted that the address information of the first EASDF in the PDU session establishment request is triggered by the UE's operating system. However, the UE obtains the address information of the first EASDF (DNS Server address) via DHCP through the user plane, which is usually triggered by the application (APP) running on the UE.

In summary, the method provided in this embodiment, by having the UE send a first identifier to the SMF by adding a first information element in the PDU session establishment request, enables the SMF to obtain the first identifier as early as possible during the PDU session establishment process, thereby allowing the SMF to reasonably allocate the first EASDF to the UE when there is a demand from the UE.

Figure 6 shows a flowchart of an address information acquisition method provided in an exemplary embodiment of this application. This embodiment illustrates the method by applying it to an SMF (Software-Defined Fund). The method includes:

Step 620: The SMF receives the PDU session establishment request sent by the UE. The second cell of the extended protocol configuration option in the PDU session establishment request carries the first identifier.

If the PDU session established this time belongs to the edge connection of edge computing, the UE sends the first identifier to the SMF. For example, if the PDU session established this time does not belong to the edge connection of edge computing, the UE does not send the first identifier to the SMF.

The first identifier indicates that the PDU session established is an edge connection for edge computing. For example, when a user starts using a service application that supports edge computing in the UE, the UE establishes a PDU session for that service application.

For example, the first identifier includes an EC identifier or an EASDF identifier. In this embodiment, the first identifier is carried in the first cell.

For example, the first cell is an edge computing connectivity indication cell.

Figure 5 illustrates the signaling format of a PDU session establishment request in the related art. The information element (IE) of this PDU session establishment request includes: an EPCO information element, which uses a second information element added in the EPCO to carry the first identifier.

In an exemplary example, EPCO includes at least the following information elements:

Terminal-to-network direction (i.e., UE-to-SMF direction):

0001H (P-CSCF IPv6 address request);

0002H (IM CN subsystem signal tag);

0003H (DNS service IPv6 address request);

Network to terminal direction (i.e., SMF to UE direction):

0001H (P-CSCF IPv6 address request);

0002H (IM CN subsystem signal tag);

0003H (DNS service IPv6 address request);

Add an extended second element to the above EPCO element. This second element is an EASDF IP address request element. For example, the second element is as follows:

0013H (EASDF IP address request).

Step 640: The SMF selects the first EASDF for the UE based on the first identifier;

During the PDU session establishment process, the SMF receives the PDU session establishment request sent by the UE. The second element in the EPCO element of the PDU session establishment request carries the first identifier.

If the SMF parses the first identifier sent by the UE in the PDU session establishment request, it considers that the UE needs to allocate, locate, or select an EASDF.

The SMF selects a first EASDF for the UE according to a predetermined allocation principle. For example, the SMF is located at the EASDF closest to the UE in terms of geographical or network location, and is selected as the first EASDF. This embodiment does not limit how the SMF is located and how the first EASDF is selected.

Step 660: The SMF sends a PDU session establishment confirmation to the UE, which carries the address information of the first EASDF.

After the SMF selects a first EASDF for the UE, the SMF sends the address information of the first EASDF to the UE. Optionally, this address information refers to the IP address of the first EASDF.

After obtaining the IP address of the first EASDF, the UE uses the DNS-related services provided by the first EASDF.

Optionally, the PDU session establishment confirmation includes an EPCO cell. Within this EPCO cell, the 0003H cell carries the address information of the first EASDF.

Step 682: After the PDU session is established, receive the DHCP request sent by the terminal;

After the PDU session is established, the UE may obtain the address of a DNS server by initiating a DHCP request to the SMF through the user. At this time, the SMF also needs to send a DHCP response to the UE, which contains the address information of the first EASDF, that is, the IP address of the first EASDF.

Step 684: Send a DHCP response to the terminal, which carries the address information of the first EASDF.

For example, the fourth cell of the EPCO cell in the DHCP response carries the address information of the first EASDF.

That is, if the SMF provides the address information of the first EASDF in the EPCO cell of the PDU session establishment request, then the SMF also needs to include the same address information of the first EASDF in the DHCP response.

It should be noted that the address information of the first EASDF in the PDU session establishment request is triggered by the UE's operating system. However, the UE obtains the address information of the first EASDF via DHCP through the user plane, which is usually triggered by the application running on the UE.

In summary, the method provided in this embodiment sends the first identifier by adding a second information element to the EPCO information element in the PDU session establishment request by the UE. While keeping the number of first-level information elements in the PDU session establishment request unchanged, it only modifies the information element content in the EPCO information element, which requires less modification to the communication protocol. It also enables the SMF to obtain the first identifier as early as possible during the PDU session establishment process, so that the SMF can reasonably allocate the first EASDF to the UE when there is a demand from the UE.

Figure 7 shows a flowchart of an address information acquisition method provided in an exemplary embodiment of this application. This embodiment illustrates the method by applying it to a UE. The method includes:

Step 720: During the PDU session establishment process, the UE sends a first identifier to the SMF. The first identifier is used to trigger the SMF to locate the terminal and select the first EASDF.

Optionally, the UE sends a PDU session establishment request to the SMF, which carries a first identifier. The first identifier is used to indicate that the PDU session to be established belongs to the edge connection of edge computing.

For example, the first identifier may include an EC identifier or an EASDF identifier.

In one embodiment, the first identifier is carried in the first cell of the PDU session establishment request. The first cell is an edge computing connection indication cell. Figure 5 illustrates the signaling format of a PDU session establishment request in the related art. A first cell is added to the signaling format of this PDU session establishment request to carry the first identifier. This first cell can be added to any column in the signaling format shown in Figure 5. The type of the first cell is optional.

In one embodiment, the first identifier is carried in the second element of the EPCO element in the PDU session establishment request. That is, the PDU session establishment request element includes the EPCO element, and the first identifier is carried using the newly added second element in the EPCO. For example, the EPCO includes at least the following elements:

Terminal-to-network direction (i.e., UE-to-SMF direction):

0001H (P-CSCF IPv6 address request);

0002H (IM CN subsystem signal tag);

0003H (DNS service IPv6 address request);

Network to terminal direction (i.e., SMF to UE direction):

0001H (P-CSCF IPv6 address request);

0002H (IM CN subsystem signal tag);

0003H (DNS service IPv6 address request);

Add an extended second element to the above EPCO element. This second element is an EASDF IP address request element. For example, the second element is as follows:

0013H (EASDF IP address request).

After the UE sends a PDU session establishment request carrying the first identifier to the SMF, the SMF allocates, locates, or selects the first EASDF for the UE.

The SMF sends a PDU session establishment confirmation to the UE, which carries the address information of the first EASDF. Optionally, the PDU session establishment confirmation includes an EPCO cell. The address information of the first EASDF is carried in the 0003H cell within the EPCO cell.

Step 740: The UE receives the address information of the first EASDF.

The UE receives a PDU session establishment confirmation sent by the SMF, which carries the address information of the first EASDF. Optionally, this address information refers to the IP address of the first EASDF.

For example, the address information of the first EASDF is carried in the third cell of the EPCO that confirms the establishment of the PDU session.

After obtaining the IP address of the first EASDF, the UE uses the DNS-related services provided by the first EASDF, such as the DNS query service.

Step 760: After the PDU session is established, send a DHCP request to the SMF;

After the PDU session is established, the UE may obtain the address of a DNS server by initiating a DHCP request to the SMF through the user. At this time, the SMF also needs to send a DHCP response to the UE, which contains the address information of the first EASDF, that is, the IP address of the first EASDF.

Step 780: Receive the DHCP response sent by the SMF, which carries the address information of the first EASDF.

The address information of the first EASDF is carried in the fourth cell of the EPCO in the DHCP response.

For example, the fourth cell of the EPCO cell in the DHCP response carries the address information of the first EASDF.

That is, if the SMF provides the address information of the first EASDF in the EPCO cell of the PDU session establishment request, then the SMF also needs to include the same address information of the first EASDF in the DHCP response.

It should be noted that the address information of the first EASDF in the PDU session establishment request is triggered by the UE's operating system. However, the UE obtains the address information of the first EASDF via DHCP through the user plane, which is usually triggered by the application running on the UE.

It should be noted that steps 760 and 780 are optional steps in this embodiment, and these two steps may not be performed in some embodiments.

In summary, the method provided in this embodiment, by having the UE send a first identifier to the SMF by adding a first information element in the PDU session establishment request, enables the SMF to obtain the first identifier as early as possible during the PDU session establishment process, thereby allowing the SMF to reasonably allocate the first EASDF to the UE when there is a demand from the UE.

Figure 8 illustrates a flowchart of an EASDF discovery method provided in an exemplary embodiment of this application. The method is performed by the UE, SMF, UPF, EASDF, and DNS server. The method includes:

Step 1: The UE sends a PDU session establishment request to the SMF;

The PDU session establishment request carries a first identifier, as shown in step 720 or step 1 of Figure 9.

Step 2: Select EASDF for SMF;

The SMF discovers that the PDU session establishment request contains a first identifier and selects the first EASDF for the UE. The first EASDF refers to the EASDF selected by the SMF for the UE.

The process of SMF selecting EASDF can be found in Clause 6.3 of the communication protocol TS23.501. This selection process can be discovered using the Network Storage Function (NRF) or based on SMF local configuration. EASDF may already be registered with the NRF.

Step 3: SMF sends a Neasdf_DNS context creation request to EASDF;

Neasdf refers to the interface or reference point between SMF and EASDF.

SMF invokes a Neasdf_DNS context creation request to the selected EASDF. The Neasdf_DNS context creation request carries (UE IP address, callback Uniform Resource Identifier (URI), and rules for processing DNS messages from the UE). The rules for processing DNS messages from the terminal (i.e., DNS message processing rules) include DNS message forwarding rules and/or DNS message reporting rules. The DNS message forwarding rules include the DNS server addresses to be forwarded and/or any extended DNS-Client-Subnet (EDNS-Client-Subnet) options to be added.

EASDF creates a DNS context for the PDU session and stores the UE's IP address, callback URI, and rules for handling DNS messages from the UE to the context.

The DNS message reporting rules include the reporting conditions under which EASDF reports DNS information (including EAS-related information) to SMF when it receives a DNS query or DNS response.

EASDF handles DNS queries for ECS options or local DNS server addresses. SMF can provide reporting rules to guide EASDF to send the fully qualified domain name(s) (FQDN) of the Edge Application Server (EAS) to SMF. If the EAS FQDN in the DNS query message matches the rules of the DNS information report of the FQDN(s) filter, EASDF will send the fully qualified domain name(s) of the Edge Application Server (EAS) to SMF.

EASDF processes DNS responses for specific IP addresses or FQDN ranges. SMF provides reporting rules to guide EASDF in reporting EAS IP addresses/FQDNs. SMF reports if an EAS DNS response message matches an IP address range(s) rule, or if an FQDN DNS response matches an FQDN DNS message reporting rule.

Before or after EASDF receives a DNS query message, EASDF provides forwarding rules, either for FQDN(s) and Data Network Access Identifier(s) (DNAI), through the ECS option or the local DNS server.

Step 4: EASDF sends a Neasdf_DNS context creation response to SMF;

EASDF invokes the service operation Neasdf_DNSContext_Create response(EASDF IP address) and uses information that allows SMF to update or delete the context later.

The IP address of EASDF is the address of the DNS server that the terminal connects to as a PDU session with EASDF.

Step 5: The SMF sends a PDU session establishment confirmation to the UE;

The PDU session establishment request carries the address information of the first EASDF, as shown in step 460 or 660.

Step 6: SMF sends a Neasdf_DNS context update request to EASDF;

SMF may invoke Neasdf_DNS Context Update Request (PDU Session Context ID, rules that handle DNS queries on the UE) to EASDF. Updates may cause mobility issues, such as when a problem moves to a new location, or when reports are made via certain FQDN EASDF DNS queries, or updates may cause insertion/deletion of local PSAs, such as updating rules to handle DNS information issues or new PCC rule information.

Step 7: EASDF sends a Neasdf_DNS context update response to SMF;

Step 8: The UE sends a DNS query to the EASDF;

EASDF sends a Neasdf_DNS context creation request;

Step 9: EASDF sends a Neasdf_DNS context notification request to SMF;

If the UE's DNS message reporting conditions are met, EASDF will report the DNS message to SMF by calling the Neasdf_DNSContext_Notify request.

Step 10: SMF sends a Neasdf_DNS context notification response to EASDF;

The Neasdf_DNS context notification response includes several possible options, including:

For option A, SMF may include the corresponding ECS option in the response message.

For option B, SMF may include the corresponding local DNS server IP address in the response message. It can also instruct EASDF to simply forward DNS queries to a pre-configured DNS server/resolver.

Step 11: EASDF sends a DNS query to the DNS server;

For option A, EASDF adds the ECS option to the DNS query message specified in RFC 7871 and sends it to the central DNS C-DNS server; C-DNS is either locally configured on EASDF or configured via SMF.

For option B, EASDF sends a DNS query message to the local DNS server. This local DNS server is provided by SMF in step 10.

If neither the reporting rules nor the forwarding rules provided by SMF match the FQDN requested in the DNS query, then EASDF can simply forward the DNS query to a pre-configured DNS server/resolver.

Step 12: The DNS server sends a DNS response to EASDF;

EASDF receives DNS responses from the DNS system and determines whether the DNS response can be sent to the terminal.

Step 13: EASDF sends a Neasdf_DNS context notification request to SMF;

If the EAS IP address or FQDN in the DNS response message matches the reporting conditions provided by the SMF, the EASDF can send a DNS message to the SMF to report information, including EAS information, by calling the Neasdf_DNS Context Notification Request.

EASDF does not send DNS response messages to the UE, but instead waits for SMF instructions.

Step 14: SMF sends a Neasdf_DNS context notification response to EASDF;

SMF calls Neasdf_DNSContext_Notify to respond to service operations.

Step 15: Insert Uplink Classifier (ULCL)/Branching Point (BP);

SMF can select UL CL/BP and local PSA, and insert UL CL/BP and local PSA.

Based on the EAS information received from the EAS and other UPF selection criteria specified in Clause 6.3.3 of the communication protocol TS 23.501, the SMF can perform the UL CL/BP and local PSA selection and insertion as described in the communication protocol TS 23.502.

Step 16: SMF sends a Neasdf_DNS context update request to EASDF;

SMF invokes the Neasdf_DNSContext_Update request (forward DNS response indication).

A “forward DNS response” means that EASDF forwards the DNS response cached in step 12 to the UE.

Step 17: EASDF sends a Neasdf_DNS context update response to SMF;

Step 18: EASDF sends a DNS response to the UE.

Figure 9 illustrates a flowchart of a PDU session establishment method provided in an exemplary embodiment of this application. This method is performed by the UE, RAN, AMF, SMF, UPF, PCF, UDM, and DN. The method includes:

Step 1: The UE sends a PDU session establishment request to the AMF;

Step 2: AMF performs SMF selection;

Step 3: The AMF sends an Nsmf_PDU session creation SM context request to the SMF;

Step 4: SMF and UDM perform subscription retrieval/subscription update;

Step 5: The SMF sends an Nsmf_PDU session creation SM context response to the AMF;

Step 6: PDU session authentication/authorization;

Step 7a: PCF selection;

Step 7b: Establish SM policy association or SMF initiates SM policy association modification;

Step 8: UPF selection;

Step 9: SMF initiates SM policy association modification;

Step 10a: The SMF sends an N4 session establishment/modification request to the UPF;

Step 10b: The UPF sends an N4 session establishment/modification request to the SMF;

Step 11: SMF sends Namf_CommunicationN1N2 message to AMF for conversion;

Step 12: AMF sends an N2 PDU session request (NAS message) to (R)AN;

Step 13: The UE and (R)AN perform (R)AN-specific resource settings;

Step 14: (R)AN sends an N2 PDU session response to AMF;

Step 15: The AMF sends an Nsmf_PDU session update SM context request to the SMF;

Step 16a: The SMF sends an N4 session modification request to the UPF;

Step 16b: The UPF sends an N4 session modification response to the SMF;

Step 16c: SMF and UDM perform the registration process;

Step 17: The SMF sends an Nsmf_PDU session update SM context response to the AMF;

Step 18: The SMF sends the Nsmf_PDU session SM context notification to the AMF;

Step 19: The SMF configures the IPv6 address for the UE;

Step 20: SMF initiates SM policy association modification;

Step 21: Unsubscribe from SMF and PCF.

Note 1: Steps 2 to 4 in Figure 8 should be completed before step 11 shown in Figure 9.

Note 2: Step 5 in Figure 8 corresponds to steps 11 to 16 shown in Figure 9.

Note 3: Steps 6 to 18 in Figure 8 may be after step 21 in Figure 9, or step 8 in Figure 8 may correspond to the first uplink data (First UL data) before step 15 in Figure 9.

The UL CL/branch point insertion process in step 15 shown in Figure 8 is equivalent to steps 2 to 8 shown in Figure 10. Figure 10 illustrates a flowchart of a method for adding additional PDU session anchors and branch points or UL CL according to an exemplary embodiment of this application. This method is performed by the UE, RAN, SMF, and UPF, and includes:

Step 1: The UE establishes a PDU session with PSA1;

The UE has an established PDU session, and its UPF includes PDU session anchor 1 (i.e., PSA1). The PDU session user plane involves at least (R)AN and PDU session anchor 1.

Step 2: SMF establishes PSA2;

At certain times, the SMF decides to establish a new PDU session anchor, for example, due to UE mobility or new flow detection. The SMF selects the UPF and uses N4 to establish a new PDU session anchor 2 (i.e., PSA2) for the PDU session. In the case of an IPv6 multihomed PDU session, the SMF also allocates a new IPv6 prefix corresponding to PSA2, and if the PCF has a user IP allocation/release event, the SMF performs a session management policy modification process to provide the PCF with the newly allocated IPv6 prefix.

If runtime coordination between 5GC and AF is enabled based on local configuration, the SMF awaits a notification response from the AF, according to the "Expected AF Acknowledgment" instruction included in the AF subscription to SMF events. If the SMF receives a negative notification response from the AF, the SMF can halt the process.

Step 3: SMF establishes branch points or UL CL;

The SMF selects the UPF and uses N4 to establish the branch point (in the case of IPv6 multihoming) or PDU CL for PDU sessions. It provides the necessary uplink forwarding rules for PSA1 and PSA2, including PSA1 CN channel information and PSA2 CN channel information. Additionally, AN channel information is provided for downlink forwarding. In the case of IPv6 multihoming, the SMF also provides traffic filters for the IPv6 prefixes corresponding to PSA1 and PSA2, indicating which traffic should be forwarded to PSA1 and PSA2 respectively. In the case of ULCL, the SMF provides traffic filters indicating which traffic should be forwarded to PSA1 and PSA2 respectively.

In the case of UL CL, the SMF provides traffic filters, indicating which traffic should be forwarded to PSA1 and PSA2 respectively. If runtime coordination between 5GC and AF is enabled based on local configuration, the SMF will send a delayed notification to the AF and wait for notification, based on the "expected AF acknowledgment" indication included in the AF subscription to the SMF event. The AF will respond before UL CL is configured. If the SMF receives a negative notification response from the AF, the SMF can stop the process.

Note 1: If the branch point or UL CL and PSA2 are both located in a single UPF, steps 2 and 3 can be combined. If the branch point has already been assigned, skip step 3.

Step 4: SMF updates PSA1 for downlink traffic;

SMF updates PSA1 for downlink traffic via N4. It provides branch point or UL CL CN channel information for downlink traffic.

Note 2: If the branch point or UL CL and PSA1 are both located in a single UPF, steps 3 and 4 can be combined.

Step 5: SMF updates PSA2;

SMF updates PSA2 via N4. It provides branch point or UL CL CN channel information for downlink traffic.

Note 3: If the branch point or UL CL and PSA2 are both located in a single UPF, then step 5 is not required.

Step 6: SMF updates (R)AN for uplink traffic;

The SMF updates the (R)AN via the N2 SM information on N11. It provides new CN channel information corresponding to the UPF (branch point or UL CL). In the case of UL CL, if there is an existing UPF between the (R)AN and the newly inserted UL CL, the SMF updates the existing UPF via N4 instead of updating the (R)AN.

Step 7: SMF notifies UE of the new IP prefix @PSA2;

In the context of IPv6 multihomed operation, the SMF notifies the UE of the availability of the new IP prefix @PSA2. This is performed using the IPv6 Router Advertisement Message (RFC 4861). Additionally, the SMF sends the routing rules along with the IPv6 prefix to the UE using the IPv6 Router Advertisement Message (RFC 4191), as described in Section 5.8.1.2 of the Communication Protocol TS 23.501, for example.

If runtime coordination between 5GC and AF is enabled based on local configuration, the SMF will send a delayed notification to the AF and wait for a notification response from the AF to send the new IP prefix to the UE, according to the "Expected AF Confirmation" indication included in the AF subscription SMF event. If the SMF receives a negative notification response from the AF, the SMF can stop the process.

Step 8: SMF reconfigures the UE with the original IP prefix @PSA1;

In the case of IPv6 multihoming, the SMF can reconfigure the UE for the original IP prefix @PSA1; that is, the SMF uses IPv6 router advertisement messages to send the routing rules along with the IPv6 prefix to the UE (RFC 4191), as described in Section 5.8.1.2 of the communication protocol TS23.501.

Note: Request for Comments (RFCs) are a series of memos issued by the Internet Engineering Task Force (IETF). These documents compile information related to the Internet, as well as software documentation from the UNIX and Internet communities, arranged in numbered blocks. Currently, RFCs are sponsored and published by the Internet Society (ISOC).

Figure 11 shows a block diagram of an address information sending apparatus provided in an exemplary embodiment of this application. This apparatus can be applied in an SMF (Software-Defined Network) or implemented as part of an SMF, and the apparatus includes:

The receiving module 1120 is used to receive the first identifier sent by the terminal during the PDU session establishment process;

Selection module 1140 is configured to select a first EASDF for the terminal based on the first identifier;

The sending module 1160 is used to send the address information of the first EASDF to the terminal.

Optionally, the receiving module 1120 is configured to receive a PDU session establishment request sent by the terminal, wherein the PDU session establishment request carries the first identifier. The first identifier is used to indicate that the PDU session to be established in this request belongs to the edge connection of edge computing.

Optionally, the first identifier includes at least one of the EC identifier and the EASDF identifier.

In one design, the first identifier is carried in a first cell of the PDU session establishment request. The first cell is an edge computing connection indication cell.

In one design, the first identifier is carried in a second element of the extended protocol configuration options in the PDU session establishment request. The second element is an EASDF IP address request element.

Optionally, the sending module 1160 is configured to send a PDU session establishment confirmation to the terminal, the PDU session establishment confirmation carrying the address information of the first EASDF.

Optionally, the address information of the first EASDF is carried in the third cell of the extended protocol configuration option of the PDU session establishment confirmation.

Optionally, the receiving module 1120 is configured to receive a Dynamic Host Configuration Protocol (DHCP) request sent by the terminal after the PDU session is established; the sending module 1160 is configured to send a DHCP response to the terminal, the DHCP response carrying the address information of the first EASDF.

Optionally, the address information of the first EASDF is carried in the fourth cell of the extended protocol configuration option in the DHCP response.

Figure 12 shows a block diagram of an address information acquisition device provided in an exemplary embodiment of this application. This device can be applied to a terminal or implemented as part of a terminal, and the device includes:

The sending module 1220 is used to send a first identifier to the SMF during the PDU session establishment process. The first identifier is used to trigger the SMF to select a first EASDF for the terminal.

The receiving module 1240 is used to receive the address information of the first EASDF.

Optionally, the sending module 1220 is configured to send a PDU session establishment request to the SMF, wherein the PDU session establishment request carries the first identifier.

Optionally, the first identifier is used to indicate that the PDU session established in this request belongs to the edge connection of edge computing.

Optionally, the first identifier may include an EC identifier or an EASDF identifier.

In one design, the first identifier is carried in a first cell of the PDU session establishment request. Optionally, the first cell is an edge computing connection indication cell.

In one design, the first identifier is carried in a second cell of the extended protocol configuration options of the PDU session establishment request.

Optionally, the second information element is an EASDF IP address request information element.

Optionally, the receiving module 1240 is configured to receive a PDU session establishment confirmation sent by the SMF, the PDU session establishment confirmation carrying the address information of the first EASDF. The address information of the first EASDF is carried in the third cell of the extended protocol configuration option of the PDU session establishment confirmation.

Optionally, the sending module 1220 is configured to send a Dynamic Host Configuration Protocol (DHCP) request to the SMF after the PDU session is established; the receiving module 1240 is configured to receive a DHCP response sent by the SMF, the DHCP response carrying the address information of the first EASDF. Optionally, the address information of the first EASDF is carried in the fourth cell of the extended protocol configuration options of the DHCP response.

Figure 13 shows a schematic diagram of the structure of a communication device (network element device or terminal) provided in an embodiment of this application. For example, the communication device can be used to execute the above-described address information sending method or address information acquisition method. Specifically, the communication device 1300 may include: a processor 1301, a receiver 1302, a transmitter 1303, a memory 1304, and a bus 1305.

The processor 1301 includes one or more processing cores. The processor 1301 executes various functional applications and information processing by running software programs and modules.

The receiver 1302 and the transmitter 1303 can be implemented as a transceiver 1306, which can be a communication chip.

The memory 1304 is connected to the processor 1301 via the bus 1305.

The memory 1304 can be used to store computer programs, and the processor 1301 is used to execute the computer programs to implement the various steps performed by the network element device, access network entity, core network element or core network entity in the above method embodiments.

The transmitter 1303 is used to perform the transmission-related steps in the above embodiments; the receiver 1302 is used to perform the reception-related steps in the above embodiments; and the processor 1301 is used to perform other steps in the above embodiments besides the transmission and reception steps.

Furthermore, the memory 1304 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, including but not limited to: RAM (Random-Access Memory) and ROM (Read-Only Memory), EPROM (Erasable Programmable Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), flash memory or other solid-state storage technologies, CD-ROM (Compact Disc Read-Only Memory), DVD (Digital Video Disc) or other optical storage, magnetic tape cassettes, magnetic tape, disk storage or other magnetic storage devices.

In an exemplary embodiment, a network element device is also provided, the network element device including: a processor and a memory, the memory storing a computer program, the computer program being loaded and executed by the processor to implement the address information transmission method as described above.

In an exemplary embodiment, a terminal is also provided, the terminal including: a processor and a memory, the memory storing a computer program, the computer program being loaded and executed by the processor to implement the address information acquisition method as described above.

This application also provides a computer-readable storage medium storing at least one instruction, at least one program, code set, or instruction set, wherein the at least one instruction, the at least one program, the code set, or the instruction set is loaded and executed by a processor to implement the address information sending method or address information acquisition method provided in the above method embodiments.

Optionally, this application also provides a computer program product comprising computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the address information sending method or address information acquisition method provided above.

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

Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware or by a program instructing related hardware. The program can be stored in a computer-readable storage medium, such as a read-only memory, a disk, or an optical disk.

The above description is merely an optional embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims (27)

1. A method for sending address information, characterized in that it is applied in a Session Management Function (SMF), the method comprising: The receiving terminal sends a PDU session establishment request, in which the second information element of the Extended Protocol Configuration Option (EPCO) in the PDU session establishment request carries a first identifier. The information element in the PDU session establishment request includes an EPCO information element, and the second information element is a newly added information element in the EPCO information element used to request the IP address of the Edge Application Server Discovery Function (EASDF). Based on the first identifier, the EASDF that is geographically or network-based closest to the terminal is selected as the first EASDF for the terminal; Send a PDU session establishment confirmation to the terminal. The PDU session establishment confirmation includes the EPCO cell. The third cell of the EPCO cell carries the address information of the first EASDF. After the PDU session is established, a Dynamic Host Configuration Protocol (DHCP) request sent by the terminal is received. The DHCP request is used to obtain the address information of the Domain Name System (DNS) server. A DHCP response is sent to the terminal, and the fourth cell of the EPCO cell in the DHCP response carries the address information of the first EASDF. 2. The method according to claim 1, wherein the first identifier is used to indicate that the PDU session requested in this request belongs to the edge connection of edge computing. 3. The method according to claim 1, wherein the first identifier includes at least one of an edge computing EC identifier and an EASDF identifier. 4. The method according to any one of claims 1 to 3, wherein the first identifier is carried in the first information element of the PDU session establishment request. 5. The method according to claim 4, characterized in that, The first cell is an edge computing connection indication cell. 6. A method for obtaining address information, characterized in that it is applied in a terminal, the method comprising: During the Protocol Data Unit (PDU) session establishment process, a PDU session establishment request is sent to the Session Management Function (SMF). The second information element of the Extended Protocol Configuration Option (EPCO) in the PDU session establishment request carries a first identifier. The first identifier is used to trigger the SMF to select the First Edge Application Server Discovery Function (EASDF) for the terminal. The information element of the PDU session establishment request includes an EPCO information element. The second information element is a newly added information element in the EPCO information element used to request the IP address of the Edge Application Server Discovery Function (EASDF). Receive the address information of the first EASDF, wherein the first EASDF is the EASDF that is closest to the terminal in terms of geographical or network location located by the SMF based on the first identifier; Receive the PDU session establishment confirmation sent by the SMF, the PDU session establishment confirmation includes the EPCO cell, and the third cell of the EPCO cell carries the address information of the first EASDF; After the PDU session is established, a Dynamic Host Configuration Protocol (DHCP) request is sent to the SMF. The DHCP request is used to obtain the address information of the Domain Name System (DNS) server. The system receives a DHCP response sent by the SMF, wherein the fourth cell of the EPCO cell in the DHCP response carries the address information of the first EASDF. 7. The method according to claim 6, wherein the first identifier is used to indicate that the PDU session requested in this request belongs to the edge connection of edge computing. 8. The method according to claim 7, wherein the first identifier includes an edge computing EC identifier or an EASDF identifier. 9. The method according to any one of claims 6 to 8, wherein the first identifier is carried in the first element of the PDU session establishment request. 10. The method according to claim 9, characterized in that, The first cell is an edge computing connection indication cell. 11. The method according to any one of claims 6 to 8, wherein the first identifier is carried in a second element of the extended protocol configuration option of the PDU session establishment request. 12. An address information transmitting device, characterized in that the device comprises: The receiving module is used to receive a PDU session establishment request sent by the terminal. The second information element of the Extended Protocol Configuration Option (EPCO) in the PDU session establishment request carries a first identifier. The information element of the PDU session establishment request includes an EPCO information element. The second information element is a newly added information element in the EPCO information element for requesting the IP address of the Edge Application Server Discovery Function (EASDF). The processing module is configured to locate the EASDF that is geographically or network-wise closest to the terminal based on the first identifier, and select it as the first EASDF for the terminal; The sending module is used to send a PDU session establishment confirmation to the terminal. The PDU session establishment confirmation includes the EPCO cell, and the third cell of the EPCO cell carries the address information of the first EASDF. The receiving module is further configured to receive a Dynamic Host Configuration Protocol (DHCP) request sent by the terminal after the PDU session is established, wherein the DHCP request is used to obtain the address information of the Domain Name System (DNS) server. The sending module is further configured to send a DHCP response to the terminal, wherein the fourth cell of the EPCO cell in the DHCP response carries the address information of the first EASDF. 13. The apparatus according to claim 12, wherein the first identifier is used to indicate that the PDU session requested to be established belongs to the edge connection of edge computing. 14. The apparatus according to claim 12, wherein the first identifier comprises at least one of an edge computing EC identifier and an EASDF identifier. 15. The apparatus according to any one of claims 12 to 14, wherein the first identifier is carried in the first cell of the PDU session establishment request. 16. The apparatus according to claim 15, characterized in that, The first cell is an edge computing connection indication cell. 17. An address information acquisition device, characterized in that the device comprises: The sending module is used to send a PDU session establishment request to the Session Management Function (SMF) during the establishment of a Protocol Data Unit (PDU) session. The second information element of the Extended Protocol Configuration Option (EPCO) in the PDU session establishment request carries a first identifier. The first identifier is used to trigger the SMF to locate and select the First Edge Application Server Discovery Function (EASDF) for the terminal. The information element of the PDU session establishment request includes an EPCO information element. The second information element is a newly added information element in the EPCO information element used to request the IP address of the Edge Application Server Discovery Function (EASDF). The receiving module is used to receive the address information of the first EASDF, wherein the first EASDF is the EASDF that is closest to the terminal in terms of geographical location or network location located by the SMF according to the first identifier; The receiving module is further configured to receive a PDU session establishment confirmation sent by the SMF, wherein the PDU session establishment confirmation includes the EPCO cell, and the third cell of the EPCO cell carries the address information of the first EASDF; The sending module is further configured to send a Dynamic Host Configuration Protocol (DHCP) request to the SMF after the PDU session is established, the DHCP request being used to obtain the address information of the Domain Name System (DNS) server; The receiving module is further configured to receive a DHCP response sent by the SMF, wherein the fourth cell of the EPCO cell in the DHCP response carries the address information of the first EASDF. 18. The apparatus according to claim 17, wherein the first identifier is used to indicate that the PDU session requested to be established belongs to the edge connection of edge computing. 19. The apparatus according to claim 18, wherein the first identifier comprises an edge computing EC identifier or an EASDF identifier. 20. The apparatus according to any one of claims 17 to 19, wherein the first identifier is carried in the first cell of the PDU session establishment request. 21. The apparatus according to claim 20, characterized in that, The first cell is an edge computing connection indication cell. 22. The apparatus according to any one of claims 17 to 19, wherein the first identifier is carried in a second element of the extended protocol configuration option of the PDU session establishment request. 23. A network element device, characterized in that the network element device comprises: a processor and a memory, the memory storing a computer program, the computer program being loaded and executed by the processor to implement the address information transmission method as described in any one of claims 1 to 5. 24. A terminal, characterized in that the terminal comprises: a processor and a memory, the memory storing a computer program, the computer program being loaded and executed by the processor to implement the address information acquisition method as described in any one of claims 6 to 11. 25. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program, the computer program being loaded and executed by a processor to implement the address information transmission method as described in any one of claims 1 to 5, or the address information acquisition method as described in any one of claims 6 to 11. 26. A computer program product, characterized in that the computer program product includes computer instructions stored in a computer-readable storage medium, the computer instructions being read from and executed by a processor of a computer device to cause the computer device to perform an address information sending method as described in any one of claims 1 to 5, or an address information acquisition method as described in any one of claims 6 to 11. 27. A chip, characterized in that the chip is configured to perform an address information transmission method as described in any one of claims 1 to 5, or an address information acquisition method as described in any one of claims 6 to 11.