WO2022206260A1 - 地址信息发送方法、获取方法、装置、设备及介质 - Google Patents

地址信息发送方法、获取方法、装置、设备及介质 Download PDF

Info

Publication number
WO2022206260A1
WO2022206260A1 PCT/CN2022/078589 CN2022078589W WO2022206260A1 WO 2022206260 A1 WO2022206260 A1 WO 2022206260A1 CN 2022078589 W CN2022078589 W CN 2022078589W WO 2022206260 A1 WO2022206260 A1 WO 2022206260A1
Authority
WO
WIPO (PCT)
Prior art keywords
easdf
pdu session
address information
smf
identifier
Prior art date
Application number
PCT/CN2022/078589
Other languages
English (en)
French (fr)
Inventor
熊春山
Original Assignee
腾讯科技（深圳）有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 腾讯科技（深圳）有限公司 filed Critical 腾讯科技（深圳）有限公司
Priority to EP22778445.1A priority Critical patent/EP4213577A4/en
Publication of WO2022206260A1 publication Critical patent/WO2022206260A1/zh
Priority to US17/993,865 priority patent/US20230086304A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5007—Internet protocol [IP] addresses
    • H04L61/5014—Internet protocol [IP] addresses using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/16—Discovering, processing access restriction or access information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2101/00—Indexing scheme associated with group H04L61/00
    • H04L2101/60—Types of network addresses
    • H04L2101/668—Internet protocol [IP] address subnets

Definitions

  • the embodiments of the present application relate to the field of mobile communications, and in particular, to a method for sending address information, a method for obtaining address information, an apparatus, a device, and a medium.
  • the 5G core network (5G Core, 5GC) supports the use of Protocol Data Unit (PDU) sessions to support edge computing.
  • PDU Protocol Data Unit
  • the Domain Name System (DNS) query sent by the User Equipment (UE) is processed by the Edge Application Server Discovery Function (EASDF).
  • EASDF Edge Application Server Discovery Function
  • the present application provides an address information sending method, obtaining method, apparatus, device and medium, and provides an EASDF allocation mechanism based on the active triggering of the UE.
  • the technical solution is as follows:
  • a method for sending address information is provided, which is applied in a session management function (Session Management Function, SMF), and the method includes:
  • Protocol Data Unit Protocol Data Unit
  • a method for obtaining address information is provided, which is applied to a UE, and the method includes:
  • an apparatus for sending address information comprising:
  • a receiving module configured to receive the first identifier sent by the UE in the PDU session establishment process
  • a selection module configured to select a first EASDF for the UE according to the first identifier
  • a sending module configured to send the address information of the first EASDF to the UE.
  • an apparatus for acquiring address information comprising:
  • a sending module configured to send a first identifier to the SMF during the establishment of the PDU session, where the first identifier is used to trigger the SMF to locate and select the first EASDF for the terminal;
  • a receiving module configured to receive the address information of the first EASDF.
  • a network element device includes: a processor and a memory, the memory stores a computer program, and the computer program is loaded and executed by the processor to achieve the above The address information sending method.
  • a terminal includes: a processor and a memory, the memory stores a computer program, the computer program is loaded and executed by the processor to realize the address as described above Information acquisition method.
  • a computer-readable storage medium stores a computer program, and the computer program is loaded and executed by a processor to implement the above-mentioned method for sending address information, or an address Information acquisition method.
  • a computer program product comprising computer instructions stored in a computer-readable storage medium.
  • the processor of the computer device reads the computer instruction from the computer-readable storage medium, and the processor executes the computer instruction, so that the computer device executes the address information sending method or the address information obtaining method provided in the above aspects.
  • a chip is provided, and the chip is configured to execute the method for sending address information or the method for obtaining address information provided by the above aspects.
  • the SMF can select the first EASDF for the UE in the scenario triggered by the UE. , to avoid the problem that the SMF allocates EASDF to the UE in an unreasonable allocation manner, but to reasonably allocate the EASDF when the UE has corresponding requirements.
  • FIG. 1 shows a structural block diagram of a communication system provided by an exemplary embodiment of the present application
  • FIG. 2 shows a structural block diagram of a communication system provided by another exemplary embodiment of the present application
  • FIG. 3 shows a flowchart of a method for sending address information provided by an exemplary embodiment of the present application
  • FIG. 4 shows a flowchart of a method for sending address information provided by another exemplary embodiment of the present application
  • FIG. 5 shows a signaling format diagram of a PDU session establishment request provided by an exemplary embodiment of the present application
  • FIG. 6 shows a flowchart of a method for sending address information provided by another exemplary embodiment of the present application.
  • FIG. 7 shows a flowchart of a method for acquiring address information provided by another exemplary embodiment of the present application.
  • FIG. 8 shows a flowchart of an EASDF discovery method provided by an exemplary embodiment of the present application
  • FIG. 9 shows a flowchart of a method for establishing a PDU session provided by another exemplary embodiment of the present application.
  • FIG. 10 shows a flowchart of a method for adding additional PDU session anchors and branch points or UL CLs provided by another exemplary embodiment of the present application
  • FIG. 11 shows a block diagram of an apparatus for sending address information provided by an exemplary embodiment of the present application
  • FIG. 12 shows a block diagram of an apparatus for obtaining address information provided by an exemplary embodiment of the present application
  • FIG. 13 shows a block diagram of a network element device provided by an exemplary embodiment of the present application.
  • Edge computing It is to provide cloud services and IT (Internet Technology, Internet technology) environmental services for application developers and service providers on the edge side of the network; the goal is to provide computing, storage and network bandwidth close to data input or users. For example, if game program A is used on the user's mobile phone, the edge computing server closest to the user's mobile phone can be allocated to provide the background game service of game program A, so as to provide the user with game services with minimal network delay.
  • IT Internet Technology, Internet technology
  • FIG. 1 shows a schematic diagram of the architecture of a communication system 100 provided by an exemplary embodiment of the present application.
  • the communication system 100 may include: a user equipment (User Equipment, UE), a radio access network (Radio Access Network, RAN), a core network (Core), and a data network (Data Network, DN).
  • UE, RAN, and Core are the main components of the architecture. Logically, they can be divided into two parts: the user plane and the 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.
  • 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
  • the NG6 reference point is located between the Core user plane and the data network.
  • the UE It is the portal for mobile users to interact with the network. It can provide basic computing capabilities and storage capabilities, display service windows to users, and accept user operation input. The UE will use the next-generation air interface technology to establish a signal connection and a data connection with the RAN, thereby transmitting control signals and service data to the mobile network.
  • RAN Similar to the base station in the traditional network, it is deployed close to the UE to provide network access functions for authorized users within the cell coverage area, and can use transmission tunnels of different quality to transmit user data according to user levels and service requirements.
  • the RAN can manage its own resources, utilize them rationally, provide access services for the UE on demand, and forward 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 functions such as session management, mobility management, policy management, and security authentication for the UE.
  • the UE When the UE is attached, it provides network access authentication for the UE; when the UE has a service request, it allocates network resources for the UE; when the UE moves, it updates the network resources for the UE; when the UE is idle, it provides a fast recovery mechanism for the UE;
  • the DN It is a data network that provides business services for users.
  • the client is located in the UE, and the server is located in the data network.
  • the data network can be a private network, such as a local area network, or an external network that is not controlled by operators, such as the Internet, or a private network jointly deployed by operators, such as in order to configure the IP Multimedia Core Network. Subsystem, IMS) service.
  • IMS IP Multimedia Core Network. Subsystem
  • Figure 2 is a detailed architecture determined on the basis of Figure 1, wherein the core network user plane includes a user plane function (User Plane Function, UPF); the core network control plane includes an authentication server function (Authentication Server Function, AUSF), access and Access and Mobility Management Function (AMF), Session Management (Session Management Function, SMF), Network Slice Selection Function (NSSF), Network Exposure Function (NEF), Network Function Storage Function (Network Repository Function, NRF), Unified Data Management (Unified Data Management, UDM), Policy Control Function (Policy Control Function, PCF), Application Function (Application Function, AF).
  • the functions of these functional entities are as follows:
  • UPF perform user data packet forwarding according to the routing rules of SMF
  • AUSF perform security authentication of the UE
  • AMF UE access and mobility management
  • SMF UE session management
  • NSSF select network slice for UE
  • NEF Open network functions to third parties in the form of API interfaces
  • NRF Provides the storage function and selection function of network function entity information for other network elements
  • UDM user subscription context management
  • PCF User Policy Management
  • the N1 interface is the reference point between the UE and the AMF
  • the N2 interface is the reference point between the RAN and the AMF, used for sending NAS messages, etc.
  • the N3 interface is the reference point between the RAN and the UPF, It is used to transmit data on the user plane, etc.
  • the N4 interface is the reference point between the SMF and the UPF, and is used to transmit information such as the tunnel identification information of the N3 connection, the data buffer indication information, and the downlink data notification message
  • the N6 interface is the UPF and the UPF.
  • NG interface The interface between the radio access network and the 5G core network.
  • each network element in FIG. 1 and FIG. 2 is just an example, and the name of the interface in the specific implementation may be other names, which are not specifically limited in this embodiment of the present application.
  • the names of each network element (such as SMF, AF, UPF, etc.) included in FIG. 1 and FIG. 2 are only an example, and the functions of the network elements themselves are not limited. In 5GS and other future networks, the above-mentioned network elements may also have other names, which are not specifically limited in this embodiment of the present application.
  • FIG. 3 shows a flowchart of a method for sending address information provided by an exemplary embodiment of the present application.
  • the method is applied to SMF as an example for illustration.
  • the method includes:
  • Step 320 the SMF receives the first identifier sent by the UE during the PDU session establishment process
  • the UE sends the first identifier to the SMF.
  • the first identifier is not sent to the SMF.
  • the first identifier is used to indicate that the PDU session established this time is an edge connection of edge computing.
  • the PDU session established this time is an edge connection of edge computing.
  • a user starts to use a service application supporting edge computing in the UE, and the UE establishes a PDU session for the service application.
  • the first identifier includes an edge computing (Edge Computing, EC) identifier, or an EASDF identifier.
  • Step 340 the SMF selects the first EASDF for the UE according to the first identifier
  • the SMF receives the first identifier sent by the UE, it is considered that the UE needs to allocate or locate or select the EASDF.
  • the SMF selects the first EASDF for the UE according to a predetermined allocation principle.
  • the SMF locates the EASDF closest to the UE in geographic location or network location, and selects it as the first EASDF. This embodiment does not limit how the SMF locates and selects the first EASDF.
  • Step 360 The SMF sends the address information of the first EASDF to the UE.
  • the SMF After the SMF selects the first EASDF for the UE, the SMF sends the address information of the first EASDF to the UE.
  • the address information refers to an Internet Protocol (Internet Protocol, IP) address of the first EASDF.
  • IP Internet Protocol
  • the UE After obtaining the IP address of the first EASDF, the UE uses the DNS-related service provided by the first EASDF. For example, DNS query service.
  • the UE sends the first identifier to the SMF during the establishment of the PDU session, triggers the SMF to select the first EASDF for the UE and sends the address information of the first EASDF to the UE, so that the SMF can
  • select the first EASDF for the UE to avoid that the SMF always allocates an EASDF that does not match its location to the UE, or always does not allocate an EASDF to the UE, or allocates an EASDF to the UE using an unreasonable allocation method (such as EASDF according to EASDF).
  • an EASDF with the lightest load is selected; or a general DNS Server is allocated), but the effect of rationally allocating EASDF based on the current location of the UE when the UE has corresponding requirements.
  • the first identifier is carried in a PDU session establishment request (PDU session establishment request), and the PDU session establishment request is a signaling message sent by the UE to the SMF; the address information of the first EASDF is carried in the In the PDU session establishment acknowledgment (PDU session establishment accept), the PDU session establishment acknowledgment is a signaling message sent by the SMF to the UE.
  • FIG. 4 shows a flowchart of a method for sending address information provided by an exemplary embodiment of the present application.
  • the method is applied to SMF as an example for illustration.
  • the method includes:
  • Step 420 the SMF receives the PDU session establishment request sent by the UE, and the first information element in the PDU session establishment request carries the first identifier;
  • the UE sends the first identifier to the SMF.
  • the first identifier is not sent to the SMF.
  • the first identifier is used to indicate that the PDU session established this time is an edge connection of edge computing.
  • the PDU session established this time is an edge connection of edge computing.
  • a user starts to use a service application supporting edge computing in the UE, and the UE establishes a PDU session for the service application.
  • the first identifier includes an EC identifier, or an EASDF identifier.
  • the first identifier is carried in the first cell.
  • FIG. 5 shows a signaling format of a PDU session establishment request in the related art.
  • a first cell is added to the signaling format of the PDU session establishment request, and the first cell is used to carry the first identifier.
  • the first cell is an edge computing connection indicator cell (Edge Computing Connection Indicator).
  • the first information element can be added to any column in the signaling format shown in FIG. 5 .
  • the type of the first cell is optional.
  • TLV in FIG. 5 is: Type, Length, Value.
  • Type is the message type; Length is the length of the value, and Value is the actual value.
  • the lengths of T and L are fixed, and the length of V is specified by Length.
  • TLV-E refers to the extended TLV format, TV is the message type and actual value, and V is the actual value.
  • Step 440 the SMF selects the first EASDF for the UE according to the first identifier
  • the SMF receives the PDU session establishment request sent by the UE, and the first information element in 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 is considered that the UE needs to allocate or locate or select the EASDF.
  • the SMF selects the first EASDF for the UE from among the multiple candidate EASDFs according to a predetermined allocation principle.
  • the SMF locates the EASDF closest to the UE in geographic location or network location, and selects it as the first EASDF. This embodiment does not limit how the SMF locates and selects the first EASDF.
  • the SMF when the UE acquires its own IP address, it needs to request the SMF to allocate the first UPF from the multiple UPFs.
  • An IP address is allocated to the UE by the first UPF.
  • the SMF may select the EASDF connected to the first UPF as the EASDF closest to the UE.
  • the SMF knows all or part of the network topology information of the core network in advance, and the network topology information includes each UPF and the EASDF connected to each UPF; or, based on the IP address of the UE, the SMF selects the EASDF closest to the UE in the network location, such as EASDF in the same network segment is selected according to the gateway address or network segment address to which the IP address belongs.
  • Step 460 The SMF sends a PDU session establishment confirmation to the UE, and the PDU session establishment confirmation carries the address information of the first EASDF.
  • the SMF After the SMF selects the first EASDF for the UE, the SMF sends the address information of the first EASDF to the UE.
  • the address information refers to the IP address of the first EASDF.
  • the UE After obtaining the IP address of the first EASDF, the UE uses the DNS-related service provided by the first EASDF.
  • the SMF sends a PDU session establishment confirmation to the UE, where the PDU session establishment confirmation carries the address information of the first EASDF.
  • the PDU session establishment confirmation includes an Extended Protocol Configuration Options (Extended Protocol Configuration Options, EPCO) information element.
  • the address information of the first EASDF is carried in the third cell in the EPCO cell.
  • the third cell is a 0003 cell.
  • Step 482 After the PDU session is established, the SMF receives a Dynamic Host Configuration Protocol (DHCP) request sent by the terminal;
  • DHCP Dynamic Host Configuration Protocol
  • the UE may initiate a DHCP request to the SMF to obtain the address of a DNS Server.
  • the SMF also needs to send a DHCP response to the UE.
  • the DHCP response contains the address information of the first EASDF, that is, the first EASDF.
  • An IP address of the EASDF is the first EASDF.
  • Step 484 The SMF sends a DHCP response to the terminal, and the DHCP response carries the address information of the first EASDF.
  • the fourth information element of the EPCO information element of the DHCP response carries the address information of the first EASDF.
  • the SMF also needs to include the same address information of the first EASDF in the DHCP response.
  • the address information of the first EASDF in the PDU session establishment request is triggered by the OS operating system of the UE.
  • the UE obtains the address information (DNS Server address) of the first EASDF through DHCP through the user plane, which is usually triggered by an application (Application, APP) running in the UE.
  • the UE sends the first identifier by adding the first information element to the SMF in the PDU session establishment request, so that the SMF can obtain the first identifier as early as possible during the PDU session establishment process, Therefore, when the UE has a demand, the SMF reasonably allocates the first EASDF to the UE.
  • FIG. 6 shows a flowchart of a method for acquiring address information provided by an exemplary embodiment of the present application.
  • the method is applied to SMF as an example for illustration.
  • the method includes:
  • Step 620 the SMF receives the PDU session establishment request sent by the UE, and the second information element of the extended protocol configuration option in the PDU session establishment request carries the first identifier;
  • the UE sends the first identifier to the SMF.
  • the first identifier is not sent to the SMF.
  • the first identifier is used to indicate that the PDU session established this time is an edge connection of edge computing. For example, a user starts to use a service application supporting edge computing in the UE, and the UE establishes a PDU session for the service application.
  • the first identifier includes an EC identifier, or an EASDF identifier.
  • the first identifier is carried in the first cell.
  • the first cell is an edge computing connection indication cell.
  • FIG. 5 shows a signaling format of a PDU session establishment request in the related art.
  • the information element (Information Element, IE) of the PDU session establishment request includes: an EPCO information element, and a second information element newly added in the EPCO is used to carry the first identifier.
  • the EPCO includes at least the following information elements:
  • Terminal to network direction ie UE to SMF direction:
  • the second cell is an IP address request cell for EASDF.
  • the second cell is as follows:
  • Step 640 the SMF selects the first EASDF for the UE according to the first identifier
  • the SMF receives the PDU session establishment request sent by the UE, and the second information element in the EPCO information element in the PDU session establishment request carries the first identifier.
  • the SMF resolves the first identifier sent by the UE in the PDU session establishment request, it is considered that the UE needs to allocate or locate or select the EASDF.
  • the SMF selects the first EASDF for the UE according to a predetermined allocation principle.
  • the SMF locates the EASDF closest to the UE in geographic location or network location, and selects it as the first EASDF. This embodiment does not limit how the SMF locates and selects the first EASDF.
  • Step 660 The SMF sends a PDU session establishment confirmation to the UE, and the PDU session establishment confirmation carries the address information of the first EASDF.
  • the SMF After the SMF selects the first EASDF for the UE, the SMF sends the address information of the first EASDF to the UE.
  • the address information refers to the IP address of the first EASDF.
  • the UE After obtaining the IP address of the first EASDF, the UE uses the DNS-related service provided by the first EASDF.
  • the PDU session establishment confirmation includes an EPCO cell.
  • the 0003H cell in the EPCO cell carries the address information of the first EASDF.
  • Step 682 After the PDU session is established, the SMF receives the DHCP request sent by the terminal;
  • the UE may initiate a DHCP request to the SMF to obtain the address of a DNS Server.
  • the SMF also needs to send a DHCP response to the UE.
  • the DHCP response contains the address information of the first EASDF, that is, the first EASDF.
  • An IP address of the EASDF is the first EASDF.
  • Step 684 The SMF sends a DHCP response to the terminal, and the DHCP response carries the address information of the first EASDF.
  • the fourth information element of the EPCO information element of the DHCP response carries the address information of the first EASDF.
  • the SMF also needs to include the same address information of the first EASDF in the DHCP response.
  • the address information of the first EASDF in the PDU session establishment request is triggered by the OS operating system of the UE.
  • the UE obtains the address information of the first EASDF through the DHCP of the user plane, which is usually triggered by an APP running in the UE. That is, the SMF sends the address information twice in the PDU session establishment request process and the DHCP process, so that different program modules (OS and APP) in the UE can obtain the address information of the first EASDF.
  • the UE sends the first identifier by adding a second information element to the EPCO information element in the PDU session establishment request by the UE, and keeps the first level information element of the PDU session establishment request. Under the condition that the number remains unchanged, only the content of the information element in the EPCO information element is modified, and the modification of the communication protocol is less, which can also enable the SMF to obtain the first identifier as soon as possible during the establishment of the PDU session, so that the UE has a demand.
  • the SMF reasonably allocates the first EASDF to the UE.
  • FIG. 7 shows a flowchart of a method for acquiring address information provided by an exemplary embodiment of the present application.
  • the method is applied to the UE as an example for illustration.
  • the method includes:
  • Step 720 The UE sends a first identifier to the SMF during the PDU session establishment process, where the first identifier is used to trigger the SMF to locate and select the first EASDF for the terminal;
  • the UE sends a PDU session establishment request to the SMF, where the PDU session establishment request carries the first identifier.
  • the first identifier is used to indicate that the PDU session requested to be established this time belongs to an edge connection of edge computing.
  • the first identifier includes an EC identifier or an EASDF identifier.
  • the first identifier is carried in the first information element of the PDU session establishment request.
  • the first cell is an edge computing connection indication cell.
  • FIG. 5 shows a signaling format of a PDU session establishment request in the related art. A first cell is added to the signaling format of the PDU session establishment request, and the first cell is used to carry the first identifier.
  • the first information element can be added to any column in the signaling format shown in FIG. 5 .
  • the type of the first cell is optional.
  • the first identifier is carried in the second information element of the EPCO information element of the PDU session establishment request. That is, the information element of the PDU session establishment request includes the EPCO information element, and the second information element newly added in the EPCO is used to carry the first identifier.
  • the EPCO includes at least the following information elements:
  • Terminal to network direction ie UE to SMF direction:
  • the second cell is an IP address request cell for EASDF.
  • the second cell is as follows:
  • the SMF After the UE sends a PDU session establishment request carrying the first identifier to the SMF, the SMF allocates or locates or selects the first EASDF for the UE.
  • the SMF sends a PDU session establishment confirmation to the UE, and the PDU session establishment confirmation carries the address information of the first EASDF.
  • the PDU session establishment confirmation includes an EPCO cell.
  • the 0003H cell in the EPCO cell carries the address information of the first EASDF.
  • Step 740 The UE receives the address information of the first EASDF.
  • the UE receives the PDU session establishment confirmation sent by the SMF, where the PDU session establishment confirmation carries the address information of the first EASDF.
  • the address information refers to the IP address of the first EASDF;
  • the address information of the first EASDF is carried in the third information element of the EPCO of the PDU session establishment confirmation.
  • the UE After obtaining the IP address of the first EASDF, the UE uses the DNS-related service provided by the first EASDF. For example, DNS query service.
  • Step 760 After the PDU session is established, send a DHCP request to the SMF;
  • the UE may initiate a DHCP request to the SMF to obtain the address of a DNS Server.
  • the SMF also needs to send a DHCP response to the UE.
  • the DHCP response contains the address information of the first EASDF, that is, the first EASDF.
  • An IP address of the EASDF is the first EASDF.
  • Step 780 Receive a DHCP response sent by the SMF, where the DHCP response carries the address information of the first EASDF.
  • the address information of the first EASDF is carried in the fourth information element of the EPCO in the DHCP response.
  • the fourth information element of the EPCO information element of the DHCP response carries the address information of the first EASDF.
  • the SMF also needs to include the same address information of the first EASDF in the DHCP response.
  • the address information of the first EASDF in the PDU session establishment request is triggered by the OS operating system of the UE.
  • the UE obtains the address information of the first EASDF through DHCP through the user plane, which is usually triggered by an APP running in the UE. That is, the SMF sends the address information twice in the PDU session establishment request process and the DHCP process, so that different program modules (OS and APP) in the UE can obtain the address information of the first EASDF.
  • step 760 and step 780 are optional steps in this embodiment, and these two steps may not be performed in some embodiments.
  • the UE sends the first identifier by adding the first information element to the SMF in the PDU session establishment request, so that the SMF can obtain the first identifier as soon as possible during the PDU session establishment process. Therefore, when the UE has a demand, the SMF reasonably allocates the first EASDF to the UE.
  • FIG. 8 shows a flowchart of an EASDF discovery method provided by an exemplary embodiment of the present application.
  • the method is performed by UE, SMF, UPF, EASDF and DNS server.
  • the method includes:
  • Step 1 UE sends a PDU session establishment request to SMF;
  • the PDU session establishment request carries the first identifier, as shown in step 720 or step 1 in FIG. 9 .
  • Step 2 SMF selects EASDF
  • the SMF finds that the PDU session establishment request contains the first identifier, and selects the first EASDF for the UE, where the first EASDF refers to the EASDF selected by the SMF for the UE.
  • Step 3 SMF sends a Neasdf_DNS context creation request to EASDF;
  • Neasdf refers to the interface or reference point between SMF and EASDF.
  • the SMF calls the Neasdf_DNS context creation request to the selected EASDF.
  • the Neasdf_DNS context creation request carries (UE IP address, callback Uniform Resource Identifier (URI), rules for processing DNS messages from UE).
  • the rules for processing DNS messages from the terminal ie, DNS message processing rules
  • DNS message processing rules include DNS message forwarding rules and/or DNS message reporting rules.
  • the DNS message forwarding rule includes the DNS server address that needs to be forwarded and/or the extended DNS-Client-Subnet ECS (EDNS-Client-Subnet) option that needs 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 reporting conditions for the EASDF to report DNS information (including EAS-related information) to the SMF when it receives a DNS query or DNS response.
  • EASDF handles DNS query ECS options or local DNS server address processing
  • SMF can provide reporting rules to guide EASDF to send the fully qualified domain name (s) (Fully Qualified Domain Name, FQDN) of the Edge Application Server (EAS) to SMF, If the EAS FQDN in the DNS query message matches the FQDN(s) filter's rules for DNS information reporting.
  • s Fully Qualified Domain Name
  • FQDN Edge Application Server
  • EASDF handles DNS responses for specific IP address or FQDN ranges, and SMF provides reporting rules to direct EASDF to report EAS IP addresses/FQDN SMF if the EAS DNS response message matches the IP address range(s) reporting rules for an IP address, or FQDN DNS Responses to matching FQDN DNS message reporting rules.
  • EASDF Before EASDF receives DNS query message or after DNS query report, EASDF provides forwarding rules, namely ECS option for FQDN(s) and Data Network Access Identifier(s) (DNAI) or Local DNS server.
  • ECS option for FQDN(s) and Data Network Access Identifier(s) (DNAI) or Local DNS server.
  • Step 4 EASDF sends a Neasdf_DNS context creation response to SMF;
  • EASDF calls the service operation Neasdf_DNSContext_Create in response (IP address of EASDF) with 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 EASDF as a PDU session.
  • Step 5 SMF sends PDU session establishment confirmation to 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 call Neasdf_DNS Context Update Request (PDU Session Context ID, rules for handling DNS queries on UE) to EASDF.
  • Updates may cause liquidity problems, such as when the problem is moved to a new location, or reported by EASDF DNS queries with certain FQDNs, or updates may cause insert/delete local PSAs, such as updating rules to handle DNS information problems or New PCC rule information.
  • Step 7 EASDF sends Neasdf_DNS context update response to SMF;
  • Step 8 UE sends DNS query to EASDF
  • EASDF sends a Neasdf_DNS context creation request.
  • Step 9 EASDF sends a Neasdf_DNS context notification request to SMF;
  • EASDF reports the DNS message to the SMF by calling Neasdf_DNSContext_Notify request.
  • Step 10 SMF sends a Neasdf_DNS context notification response to EASDF;
  • the notification response in the Neasdf_DNS context contains the following possible options:
  • the SMF may include the corresponding ECS option in the response message.
  • the SMF may include the corresponding local DNS server IP address in the response message.
  • EASDF can also be instructed to simply forward DNS queries to pre-configured DNS servers/resolvers.
  • Step 11 EASDF sends DNS query to DNS server
  • EASDF adds the ECS option to the DNS query message specified in RFC 7871 and sends it to the central DNS C-DNS server; either C-DNS is configured locally on EASDF or via SMF.
  • EASDF sends a DNS query message to the local DNS server.
  • This local DNS server is provided by SMF in step 10.
  • 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
  • the EASDF receives the DNS response 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;
  • the EASDF can send the DNS message reporting information, including the EAS information, to the SMF by calling the Neasdf_DNS context notification request.
  • EASDF does not send DNS response message to UE, but waits for SMF instruction.
  • Step 14 SMF sends a Neasdf_DNS context notification response to EASDF;
  • SMF calls Neasdf_DNSContext_Notify in response to the service operation.
  • Step 15 Uplink Classifier (UL CL)/Branching Point (Branching Point, BP) insertion;
  • SMF can perform UL CL/BP and partial PSA selection and insert UL CL/BP and partial PSA.
  • the SMF may perform UL CL/BP and partial 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;
  • Forward DNS response means that EASDF forwards the cached DNS response 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.
  • FIG. 9 shows a flowchart of a method for establishing a PDU session provided by an exemplary embodiment of the present application.
  • the method is performed by UE, RAN, AMF, SMF, UPF, PCF, UDM and DN.
  • the method includes:
  • Step 1 UE sends a PDU session establishment request to AMF;
  • Step 2 AMF performs SMF selection
  • Step 3 AMF sends Nsmf_PDU session creation SM context request to SMF;
  • Step 4 SMF and UDM perform subscription retrieval/subscription update
  • Step 5 SMF sends Nsmf_PDU session to AMF to create SM context response;
  • Step 6 PDU session authentication/authorization
  • Step 7a PCF selection
  • Step 7b SM policy association is established or SMF initiates SM policy association modification
  • Step 8 UPF selection
  • Step 9 SMF starts SM policy association modification
  • Step 10a SMF sends N4 session establishment/modification request to UPF;
  • Step 10b UPF sends N4 session establishment/modification request to SMF;
  • Step 11 SMF sends Namf_CommunicationN1N2 message conversion to AMF;
  • Step 12 AMF sends N2PDU session request (NAS message) to (R)AN;
  • Step 13 UE and (R)AN perform (R)AN specific resource setting
  • Step 14 (R)AN sends N2PDU session response to AMF;
  • Step 15 AMF sends Nsmf_PDU session update SM context request to SMF;
  • Step 16a SMF sends N4 session modification request to UPF;
  • Step 16b UPF sends N4 session modification response to SMF;
  • Step 16c SMF and UDM perform the registration process
  • Step 17 SMF sends Nsmf_PDU session update SM context response to AMF;
  • Step 18 SMF sends Nsmf_PDU session SM context notification to AMF;
  • Step 19 SMF performs IPv6 address configuration to UE
  • Step 20 SMF starts SM policy association modification
  • Step 21 SMF and PCF unsubscribe.
  • Steps 2 to 4 in Figure 8 should be completed before Step 11 in Figure 9.
  • Step 5 in Figure 8 corresponds to Steps 11 to 16 shown in Figure 9.
  • Steps 6 to 18 in Figure 8 may be after Step 21 in Figure 9, or Step 8 in Figure 8 corresponds to the first uplink data (First UL data) before Step 15 in Figure 9.
  • FIG. 10 shows a flowchart of a method for adding additional PDU session anchors and branch points or UL CLs provided by an exemplary embodiment of the present application.
  • the method is performed by the UE, the RAN, the SMF and the UPF, and the method includes:
  • Step 1 UE establishes a PDU session with PSA1;
  • the UE has an established PDU session whose UPF includes PDU Session Anchor 1 (ie PSA1).
  • PDU session user plane involves at least the (R)AN and the PDU session anchor 1 .
  • Step 2 SMF establishes PSA2;
  • the SMF decides to establish a new PDU session anchor, eg due to UE mobility, new flow detection.
  • the SMF selects the UPF and uses N4 to establish a new PDU Session Anchor 2 (ie PSA2) for the PDU Session.
  • PSA2 PDU Session Anchor 2
  • 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 procedure to provide the PCF with the newly allocated IPv6 prefix.
  • SMF waits for a notification response from AF based on the indication that "Expected AF Acknowledgement" is included in the AF subscription to SMF events. If the SMF receives a negative notification response from the AF, the SMF can stop the process.
  • Step 3 SMF establishes branch point or UL CL
  • SMF selects UPF and uses N4 to establish branch point (in case of IPv6 multi-homing) or PDU CL for PDU session. It provides necessary uplink forwarding rules for PSA1 and PSA2, including PSA1CN channel information and PSA2CN channel information. Additionally, AN channel information is provided for downlink forwarding.
  • SMF also provides traffic filters for the IPv6 prefixes corresponding to PSA1 and PSA2, indicating which traffic will be forwarded to PSA1 and PSA2, respectively.
  • UL CL the SMF provides traffic filters indicating which traffic should be forwarded to PSA1 and PSA2 respectively.
  • 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, SMF will send delay notification to AF and wait for notification according to the indication of "Expected AF Acknowledgement" included in AF subscription to SMF event. AF responds before configuring the UL CL. If the SMF receives a negative notification response from the AF, the SMF can stop the process.
  • Steps 2 and 3 can be combined if the branch point or UL CL and PSA2 are co-located in a single UPF. If a 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.
  • Steps 3 and 4 can be combined if the branch point or UL CL and PSA1 are co-located in a single UPF.
  • Step 5 SMF updates PSA2;
  • SMF updates PSA2 via N4. It provides branch point or UL CL CN channel information for downlink traffic.
  • Step 5 is not required if the branch point or UL CL and PSA2 are co-located in a single UPF.
  • Step 6 SMF updates (R)AN for uplink traffic
  • SMF updates (R)AN with N2SM information on N11. It provides new CN channel information corresponding to UPF (Branch Point or UL CL).
  • UPF Brain Point or UL CL
  • the SMF updates the existing UPF via N4 instead of updating the (R)AN.
  • Step 7 SMF notifies UE of new IP prefix @PSA2;
  • the SMF informs the UE of the availability of the new IP prefix @PSA2. This is performed using IPv6 Router Advertisement messages (RFC 4861). Furthermore, the SMF sends routing rules to the UE along with the IPv6 prefix using IPv6 Router Advertisement messages (RFC 4191), as described for example in the communication protocol TS 23.501 section 5.8.1.2.
  • SMF will send delayed notification to AF and wait for notification response to send new IP prefix from AF to UE. If the SMF receives a negative notification response from the AF, the SMF can stop the process.
  • Step 8 SMF reconfigures the UE for the original IP prefix @PSA1;
  • the SMF may reconfigure the UE for the original IP prefix @PSA1; i.e. the SMF sends routing rules to the UE along with the IPv6 prefix using IPv6 Router Advertisement messages, (RFC 4191) e.g. Communication Protocol TS 23.501 Section 5.8. as described in Article 1.2.
  • RRC 4191 IPv6 Router Advertisement messages
  • the Request For Comments is a series of memorandums issued by The Internet Engineering Task Force (IETF).
  • the document collects information about the Internet, as well as software documents for UNIX and the Internet community, arranged by number.
  • RFC documents are issued under the sponsorship of the Internet Society (ISOC).
  • FIG. 11 shows a block diagram of an apparatus for sending address information provided by an exemplary embodiment of the present application.
  • the apparatus can be applied in SMF, or implemented as part of SMF, and the apparatus includes:
  • a receiving module 1120 configured to receive the first identifier sent by the terminal in the PDU session establishment process
  • a selection module 1140 configured to select a first EASDF for the terminal according to the first identifier
  • the sending module 1160 is configured to send the address information of the first EASDF to the terminal.
  • the receiving module 1120 is configured to receive a PDU session establishment request sent by the terminal, where the PDU session establishment request carries the first identifier.
  • the first identifier is used to indicate that the PDU session requested to be established this time belongs to an edge connection of edge computing.
  • the first identifier includes at least one of an EC identifier and an EASDF identifier.
  • the first identifier is carried in a first information element of the PDU session establishment request.
  • the first cell is an edge computing connection indication cell.
  • the first identifier is carried in the second information element of the extended protocol configuration option of the PDU session establishment request.
  • the second information element is an IP address request information element of EASDF.
  • the sending module 1160 is configured to send a PDU session establishment confirmation to the terminal, where the PDU session establishment confirmation carries the address information of the first EASDF.
  • the address information of the first EASDF is carried in the third information element of the extended protocol configuration option of the PDU session establishment confirmation.
  • 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 The DHCP response carries the address information of the first EASDF.
  • the address information of the first EASDF is carried in the fourth information element of the extended protocol configuration option of the DHCP response.
  • FIG. 12 shows a block diagram of an apparatus for acquiring address information provided by an exemplary embodiment of the present application.
  • the apparatus can be applied to a terminal, or implemented as a part of a terminal, and the apparatus includes:
  • a sending module 1220 configured to send a first identifier to the SMF during the PDU session establishment process, where the first identifier is used to trigger the SMF to select the first EASDF for the terminal;
  • the receiving module 1240 is configured to receive the address information of the first EASDF.
  • the sending module 1220 is configured to send a PDU session establishment request to the SMF, where the PDU session establishment request carries the first identifier.
  • the first identifier is used to indicate that the PDU session requested to be established this time belongs to an edge connection of edge computing.
  • the first identifier includes an EC identifier or an EASDF identifier.
  • the first identifier is carried in a first information element of the PDU session establishment request.
  • the first cell is an edge computing connection indication cell.
  • the first identifier is carried in the second information element of the extended protocol configuration option of the PDU session establishment request.
  • the second information element is an IP address request information element of EASDF.
  • the receiving module 1240 is configured to receive a PDU session establishment confirmation sent by the SMF, where the PDU session establishment confirmation carries address information of the first EASDF.
  • the address information of the first EASDF is carried in the third information element of the extended protocol configuration option of the PDU session establishment confirmation.
  • 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 The response carries the address information of the first EASDF.
  • the address information of the first EASDF is carried in the fourth information element of the extended protocol configuration option of the DHCP response.
  • FIG. 13 shows a schematic structural diagram of a communication device (network element device or terminal) provided by an embodiment of the present application.
  • the communication device may be used to execute the above method for sending address information or obtaining method for address information.
  • 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, and the processor 1301 executes various functional applications and information processing by running software programs and modules.
  • the receiver 1302 and the transmitter 1303 may be implemented as a transceiver 1306, which may be a communication chip.
  • the memory 1304 is connected to the processor 1301 through the bus 1305 .
  • the memory 1304 may be used to store a computer program, and the processor 1301 is used to execute the computer program to implement 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 steps related to sending in the above embodiments; the receiver 1302 is used to perform the steps related to receiving in the above embodiments; the processor 1301 is used to perform the steps except sending and receiving in the above embodiments. Steps other than the receiving step.
  • the memory 1304 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, and the volatile or non-volatile storage device includes but is not limited to: RAM (Random-Access Memory, random access memory) and ROM (Read-Only Memory), EPROM (Erasable Programmable Read-Only Memory, Erasable Programmable Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory, Electrically Erasable Programmable Read-Only Memory) memory), flash memory or other solid-state storage technology, CD-ROM (Compact Disc Read-Only Memory), DVD (Digital Video Disc, high-density digital video disc) or other optical storage, tape cassettes, magnetic tapes, magnetic disks storage or other magnetic storage devices.
  • RAM Random-Access Memory, random access memory
  • ROM Read-Only Memory
  • EPROM Erasable Programmable Read-Only Memory
  • EEPROM Electrically Erasable Programmable Read-Only Memory
  • flash memory or other solid-
  • a network element device includes: a processor and a memory, the memory stores a computer program, and the computer program is loaded and executed by the processor to implement The address information transmission method as described above.
  • a terminal in an exemplary embodiment, includes: a processor and a memory, the memory stores a computer program, the computer program is loaded and executed by the processor to implement the above-mentioned How to obtain address information.
  • the present application further provides a computer-readable storage medium, where at least one instruction, at least one piece of program, code set or instruction set is stored in the storage medium, the at least one instruction, the at least one piece of program, the code set or The instruction set is loaded and executed by the processor to implement the method for sending address information or the method for obtaining address information provided by the above method embodiments.
  • the present application also provides a computer program product, wherein the computer program product includes computer instructions, and the computer instructions are stored in a computer-readable storage medium.
  • the processor of the computer device reads the computer instruction from the computer-readable storage medium, and the processor executes the computer instruction, so that the computer device executes the address information sending method or the address information acquiring method provided in the above aspects.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请公开了一种地址信息发送方法、获取方法、装置、设备及介质，属于移动通信领域。所述方法包括：SMF接收UE在PDU会话建立过程发送的第一标识(320)；根据所述第一标识为所述UE选择第一EASDF(340)；向所述UE发送所述第一EASDF的地址信息(360)。

Description

地址信息发送方法、获取方法、装置、设备及介质
本申请要求于2021年04月02日提交的申请号为202110362381.8、发明名称为“地址信息发送方法、获取方法、装置、设备及介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及移动通信领域，特别涉及一种地址信息发送方法、获取方法、装置、设备及介质。
背景技术
5G核心网(5G Core，5GC)支持采用协议数据单元(Protocol Data Unit，PDU)会话来支持边缘计算。
在边缘计算场景下，用户设备(User Equipment，UE)发送的域名系统(Domain Name System，DNS)查询由边缘应用服务器发现功能(Edge Application Server Discovery Function，EASDF)来处理。
但是在DNS查询前，UE如何获知EASDF的地址信息是尚未解决的技术问题。
发明内容
本申请提供了一种地址信息发送方法、获取方法、装置、设备及介质，提供了一种基于UE主动触发的EASDF分配机制。所述技术方案如下：
根据本申请的一方面，提供了一种地址信息发送方法，应用于会话管理功能(Session Management Function，SMF)中，所述方法包括：
接收UE在协议数据单元(Protocol Data Unit，PDU)会话建立过程发送的第一标识；
根据所述第一标识为所述UE选择第一EASDF；
向所述UE发送所述第一EASDF的地址信息。
根据本申请的一方面，提供了一种地址信息获取方法，应用于UE中，所述方法包括：
在PDU会话建立过程中向SMF发送第一标识，所述第一标识用于触发所述SMF为所述UE定位和选择第一EASDF；
接收所述第一EASDF的地址信息。
根据本申请的另一方面，提供了一种地址信息发送装置，所述装置包括：
接收模块，用于接收UE在PDU会话建立过程发送的第一标识；
选择模块，用于根据所述第一标识为所述UE选择第一EASDF；
发送模块，用于向所述UE发送所述第一EASDF的地址信息。
根据本申请的另一方面，提供了一种地址信息获取装置，所述装置包括：
发送模块，用于在PDU会话建立过程中向SMF发送第一标识，所述第一标识用于触发所述SMF为所述终端定位和选择第一EASDF；
接收模块，用于接收所述第一EASDF的地址信息。
根据本申请的一个方面，提供了一种网元设备，所述网元设备包括：处理器和存储器，所述存储器存储有计算机程序，所述计算机程序由所述处理器加载并执行以实现如上所述的地址信息发送方法。
根据本申请的一个方面，提供了一种终端，所述终端包括：处理器和存储器，所述存储器存储有计算机程序，所述计算机程序由所述处理器加载并执行以实现如上所述的地址信息获取方法。
根据本申请的另一方面，提供了一种计算机可读存储介质，所述存储介质存储有计算机程序，所述计算机程序由处理器加载并执行以实现如上所述的地址信息发送方法，或地址信息获取方法。
根据本申请的另一方面，提供了一种计算机程序产品，所述计算机程序产品包括计算机指令，该计算机指令存储在计算机可读存储介质中。计算机设备的处理器从计算机可读存储介质读取该计算机指令，处理器执行该计算机指令，使得该计算机设备执行上述方面提供的地址信息发送方法，或地址信息获取方法。
根据本申请的另一方面，提供了一种芯片，所述芯片被配置为执行上述方面提供的地址信息发送方法，或地址信息获取方法。
本申请实施例提供的技术方案带来的有益效果至少包括：
通过UE向SMF在PDU会话建立过程中发送第一标识，触发SMF为UE选择第一EASDF以及向UE发送第一EASDF的地址信息，能够使得SMF在UE触发的场景下，为UE选择第一EASDF，避免SMF采用不合理的分配方式向UE分配EASDF的问题，而是在UE存在相应需求的情况下，合理分配EASDF的效果。
附图说明
图1示出了本申请一个示例性实施例提供的通信系统的结构框图；
图2示出了本申请另一个示例性实施例提供的通信系统的结构框图；
图3示出了本申请一个示例性实施例提供的地址信息发送方法的流程图；
图4示出了本申请另一个示例性实施例提供的地址信息发送方法的流程图；
图5示出了本申请一个示例性实施例提供的PDU会话建立请求的信令格式图；
图6示出了本申请另一个示例性实施例提供的地址信息发送方法的流程图；
图7示出了本申请另一个示例性实施例提供的地址信息获取方法的流程图；
图8示出了本申请一个示例性实施例提供的EASDF的发现方法的流程图；
图9示出了本申请另一个示例性实施例提供的PDU会话建立方法的流程图；
图10示出了本申请另一个示例性实施例提供的增加额外的PDU会话锚和分支点或UL CL方法的流程图；
图11示出了本申请一个示例性实施例提供的地址信息发送装置的框图；
图12示出了本申请一个示例性实施例提供的地址信息获取装置的框图；
图13示出了本申请一个示例性实施例提供的网元设备的框图。
具体实施方式
边缘计算：是为应用开发者和服务提供商在网络的边缘侧提供云服务和IT(Internet Technology，互联网技术)环境服务；目标是在靠近数据输入或用户的地方提供计算、存储和网络带宽。比如，用户手机上使用游戏程序A，则可以分配离用户手机最近的边缘计算服务器来提供游戏程序A的后台游戏服务，以便给用户提供网络延迟最小的游戏服务。
图1示出了本申请一个示例性实施例提供的通信系统100的架构示意图。如图1所示，该通信系统100可以包括：用户设备(User Equipment，UE)、无线接入网(Radio Access Network，RAN)、核心网(Core)和数据网络(Data Network，DN)构成。其中，UE、RAN、Core是构成架构的主要成分，逻辑上它们可以分为用户面和控制面两部分，控制面负责移动网络的管理，用户面负责业务数据的传输。在图1中，NG2参考点位于RAN控制面和Core控制面之间，NG3参考点位于RAN用户面和Core用户面之间，NG6参考点位于Core用户面和数据网络之间。
UE：是移动用户与网络交互的入口，能够提供基本的计算能力、存储能力，向用户显示业务窗口，接受用户操作输入。UE会采用下一代空口技术，与RAN建立信号连接、数据连接，从而传输控制信号和业务数据到移动网络。
RAN：类似于传统网络里面的基站，部署在靠近UE的位置，为小区覆盖范围的授权用户提供入网功能，并能够根据用户的级别，业务的需求等使用不同质量的传输隧道传输用户数据。RAN能够管理自身的资源，合理利用，按需为UE提供接入服务，把控制信号和用户数据在UE和核心网之间转发。
Core：负责维护移动网络的签约数据，管理移动网络的网元，为UE提供会话管理、移动性管理、策略管理、安全认证等功能。在UE附着的时候，为UE提供入网认证；在UE有业务请求时，为UE分配网络资源；在UE移动的时候，为UE更新网络资源；在UE空闲的时候，为UE提供快恢复机制；在UE去附着的时候，为UE释放网络资源；在UE有业务数据时，为UE提供数据路由功能，如转发上行数据到DN；或者从DN接收UE下行数据，转发到RAN，从而发送给UE。
DN：是为用户提供业务服务的数据网络，一般客户端位于UE，服务端位于数据网络。数据网络可以是私有网络，如局域网，也可以是不受运营商管控的外部网络，如Internet，还可以是运营商共同部署的专有网络，如为了配置IP多媒体网络子系统(IP Multimedia Core Network Subsystem，IMS)服务。
图2是在图1的基础上确定的详细架构，其中核心网用户面包括用户面功能(User Plane Function，UPF)；核心网控制面包括认证服务器功能(Authentication Server Function，AUSF)、接入和移动管理(Access and Mobility Management Function，AMF)、会话管理(Session Management Function，SMF)、网络切片选择功能(Network Slice Selection Function，NSSF)、网络开放功能(Network Exposure Function，NEF)、网络功能仓储功能(Network Repository Function，NRF)、统一数据管理(Unified Data Management，UDM)、策略控制功能(Policy Control Function，PCF)、应用功能(Application Function，AF)。这些功能实体的功能如下：
UPF：根据SMF的路由规则执行用户数据包转发；
AUSF：执行UE的安全认证；
AMF：UE接入和移动性管理；
SMF：UE会话管理；
NSSF：为UE选择网络切片；
NEF：以API接口的方式向第三方开放网络功能；
NRF：为其他网元提供网络功能实体信息的存储功能和选择功能；
UDM：用户签约上下文管理；
PCF：用户策略管理；
AF：用户应用管理。
在图2所示架构中，N1接口为UE与AMF之间的参考点；N2接口为RAN和AMF的参考点，用于NAS消息的发送等；N3接口为RAN和UPF之间的参考点，用于传输用户面的数据等；N4接口为SMF和UPF之间的参考点，用于传输例如N3连接的隧道标识信息、数据缓存指示信息，以及下行数据通知消息等信息；N6接口为UPF和DN之间的参考点，用于传输用户面的数据等。NG接口：无线接入网和5G核心网之间的接口。
需要说明的是，图1和图2中的各个网元之间的接口名称只是一个示例，具体实现中接口的名称可能为其他的名称，本申请实施例对此不作具体限定。图1和图2中包括的各个网元(比如SMF、AF、UPF等)的名称也仅是一个示例，对网元本身的功能不构成限定。在5GS以及未来其它的网络中，上述各个网元也可以是其他的名称，本申请实施例对此不作具体限定。例如，在6G网络中，上述各个网元中的部分或全部可以沿用5G中的术语，也可能采用其他名称，等等，在此进行统一说明，以下不再赘述。此外，应理解，上述各个网元之间的所传输的消息(或信令)的名称也仅仅是一个示例，对消息本身的功能不构成任何限定。
图3示出了本申请一个示例性实施例提供的地址信息发送方法的流程图。本实施例以该方法应用于SMF中来举例说明。该方法包括：
步骤320：SMF接收UE在PDU会话建立过程发送的第一标识；
UE在本次建立的PDU会话属于边缘计算的边缘连接的情况下，向SMF发送第一标识。示例性的，在本次建立的PDU会话不属于边缘计算的边缘连接的情况下，不向SMF发送第一标识。
示例性的，第一标识用于指示本次建立的PDU会话是边缘计算的边缘连接。比如，用户在UE中开始使用支持边缘计算的业务应用程序，UE为该业务应用程序建立PDU会话。
示例性的，第一标识包括边缘计算(Edge Computing，EC)标识，或者，EASDF标识。
步骤340：SMF根据第一标识为UE选择第一EASDF；
在PDU会话建立过程中，若SMF接收到UE发送的第一标识，则认为UE需要分配或定位或选择EASDF。
SMF按照预定分配原则，为UE选择第一EASDF。示例性的，SMF定位在地理位置或网络位置上离UE最近的EASDF，选择成为第一EASDF。本实施例对SMF如何定位和选择第一EASDF不做限定。
步骤360：SMF向UE发送第一EASDF的地址信息。
在SMF为UE选择第一EASDF之后，SMF向UE发送第一EASDF的地址信息。可选地，该地址信息是指第一EASDF的网际互连协议(Internet Protocol，IP)地址。
UE在获得第一EASDF的IP地址后，使用第一EASDF提供的DNS相关服务。比如，DNS查询服务。
综上所述，本实施例提供的方法，通过UE向SMF在PDU会话建立过程中发送第一标识，触发SMF为UE选择第一EASDF以及向UE发送第一EASDF的地址信息，能够使得SMF在UE触发的场景下，为UE选择第一EASDF，避免SMF总是向UE分配与其位置不匹配的EASDF或总是不向UE分配EASDF或采用不合理的分配方式向UE分配EASDF(如根据EASDF的负载情况，选择了一个负载最轻的EASDF；或分配一个通用的DNS Server)的问题，而是在UE存在相应需求的情况下，基于UE的当前位置合理分配EASDF的效果。
在基于图3的可选实施例中，第一标识携带在PDU会话建立请求(PDU session establishment request)中，PDU会话建立请求是UE向SMF发送的信令消息；第一EASDF的地址信息携带在PDU会话建立确认(PDU session establishment accept)中，PDU会话建立确认是SMF向UE发送的信令消息。
图4示出了本申请一个示例性实施例提供的地址信息发送方法的流程图。本实施例以该方法应用于SMF中来举例说明。该方法包括：
步骤420：SMF接收UE发送的PDU会话建立请求，PDU会话建立请求中的第一信元携带有第一标识；
UE在本次建立的PDU会话属于边缘计算的边缘连接的情况下，向SMF发送第一标识。示例性的，在本次建立的PDU会话不属于边缘计算的边缘连接的情况下，不向SMF发送第一标识。
示例性的，第一标识用于指示本次建立的PDU会话是边缘计算的边缘连接。比如，用户在UE中开始使用支持边缘计算的业务应用程序，UE为该业务应用程序建立PDU会话。
示例性的，第一标识包括EC标识，或者，EASDF标识。在本实施例中，第一标识携带在第一信元中。
图5示出了相关技术中的PDU会话建立请求的信令格式。在该PDU会话建立请求的信令格式中增加第一信元，使用第一信元来携带第一标识。示例性的，该第一信元是边缘计算连接指示信元(Edge Computing Connection Indicator)。
该第一信元可以增加在图5所示的信令格式中的任意一列。该第一信元的类型为可选项。
需要说明的是，图5中的格式TLV：Type，Length，Value。Type为报文类型；Length是数值的长度，Value是实际的数值。T和L的长度固定，V的长度由Length指定。TLV-E是指扩展的TLV格式，TV是报文类型和实际的数值，V为实际的数值。
步骤440：SMF根据第一标识为UE选择第一EASDF；
在PDU会话建立过程中，SMF接收UE发送的PDU会话建立请求，该PDU会话建立请求中的第一信元携带有第一标识。若SMF在PDU会话建立请求中解析到UE发送的第一标 识，则认为UE需要分配或定位或选择EASDF。
SMF按照预定分配原则，在多个候选的EASDF中为UE选择第一EASDF。示例性的，SMF定位在地理位置或网络位置上离UE最近的EASDF，选择成为第一EASDF。本实施例对SMF如何定位和选择第一EASDF不做限定。
在一个示意性的例子中，UE在获取自身的IP地址时，需要请求SMF从多个UPF中分配第一UPF。由该第一UPF为UE分配IP地址。SMF可以将与该第一UPF相连的EASDF选择为离UE最近的EASDF。其中，SMF预先知晓核心网的全部或部分网络拓扑信息，该网络拓扑信息包括各个UPF以及与各个UPF相连的EASDF；或者，SMF基于UE的IP地址，选择网络位置上离UE最近的EASDF，比如根据IP地址所属的网关地址或网段地址来选择同一网段内的EASDF。
步骤460：SMF向UE发送PDU会话建立确认，该PDU会话建立确认携带有第一EASDF的地址信息。
在SMF为UE选择第一EASDF之后，SMF向UE发送第一EASDF的地址信息。可选地，该地址信息是指第一EASDF的IP地址。UE在获得第一EASDF的IP地址后，使用第一EASDF提供的DNS相关服务。
可选地，SMF向UE发送PDU会话建立确认，该PDU会话建立确认携带有第一EASDF的地址信息。
可选地，该PDU会话建立确认包括扩展协议配置选项(Extended Protocol Configuration Options，EPCO)信元。在该EPCO信元内的第三信元中携带有第一EASDF的地址信息。示例性的，该第三信元是0003信元。
步骤482：在PDU会话建立之后，SMF接收终端发送的动态主机配置协议(Dynamic Host Configuration Protocol，DHCP)请求；
在PDU会话建立之后，UE可能通过用户面向SMF发起DHCP请求获取一个DNS Server的地址，此时，SMF也需要在发送给UE的DHCP响应，该DHCP响应包含第一EASDF的地址信息，也即第一EASDF的IP地址。
步骤484：SMF向终端发送DHCP响应，DHCP响应携带有第一EASDF的地址信息。
示例性的，DHCP响应的EPCO信元的第四信元中，携带有第一EASDF的地址信息。
也即，若在PDU会话建立请求的EPCO信元中SMF提供了第一EASDF的地址信息，则在DHCP响应中，SMF也需要包含同样的第一EASDF的地址信息。
需要说明的是，在PDU会话建立请求中的第一EASDF的地址信息是UE的OS操作系统所触发的。而UE通过用户面通过DHCP来获取第一EASDF的地址信息(DNS Server地址)，通常是由UE中运行的应用程序(Application，APP)所触发的。
综上所述，本实施例提供的方法，通过UE向SMF在PDU会话建立请求中新增第一信元来发送第一标识，能够使得SMF在PDU会话建立过程中尽早获取到第一标识，从而在UE存在需求的情况下，由SMF向UE合理分配第一EASDF。
图6示出了本申请一个示例性实施例提供的地址信息获取方法的流程图。本实施例以该方法应用于SMF中来举例说明。该方法包括：
步骤620：SMF接收UE发送的PDU会话建立请求，PDU会话建立请求中的扩展协议配置选项的第二信元中携带有第一标识；
UE在本次建立的PDU会话属于边缘计算的边缘连接的情况下，向SMF发送第一标识。示例性的，在本次建立的PDU会话不属于边缘计算的边缘连接的情况下，不向SMF发送第一标识。
其中，第一标识用于指示本次建立的PDU会话是边缘计算的边缘连接。比如，用户在UE中开始使用支持边缘计算的业务应用程序，UE为该业务应用程序建立PDU会话。
示例性的，第一标识包括EC标识，或者，EASDF标识。在本实施例中，第一标识携带 在第一信元中。
示例性的，该第一信元是边缘计算连接指示信元。
图5示出了相关技术中的PDU会话建立请求的信令格式。在该PDU会话建立请求的信元(Information Element，IE)中包括：EPCO信元，使用EPCO中新增的第二信元来携带第一标识。
在一个示例性的例子中，EPCO至少包括如下信元：
终端到网络方向(即UE到SMF方向)：
0001H(P-CSCF IPv6地址请求)；
0002H(IM CN子系统信号标签)；
0003H(DNS服务IPv6地址请求)；
网络到终端方向(即SMF到UE方向)：
0001H(P-CSCF IPv6地址请求)；
0002H(IM CN子系统信号标签)；
0003H(DNS服务IPv6地址请求)；
在上述EPCO信元中新增一个扩展的第二信元。该第二信元是求EASDF的IP地址请求信元。比如，第二信元如下：
0013H(EASDF IP地址请求)。
步骤640：SMF根据第一标识为UE选择第一EASDF；
在PDU会话建立过程中，SMF接收UE发送的PDU会话建立请求，该PDU会话建立请求中的EPCO信元中的第二信元中携带有第一标识。
若SMF在PDU会话建立请求中解析到UE发送的第一标识，则认为UE需要分配或定位或选择EASDF。
SMF按照预定分配原则，为UE选择第一EASDF。示例性的，SMF定位在地理位置或网络位置上离UE最近的EASDF，选择成为第一EASDF。本实施例对SMF如何定位和选择第一EASDF不做限定。
步骤660：SMF向UE发送PDU会话建立确认，该PDU会话建立确认携带有第一EASDF的地址信息。
在SMF为UE选择第一EASDF之后，SMF向UE发送第一EASDF的地址信息。可选地，该地址信息是指第一EASDF的IP地址。
UE在获得第一EASDF的IP地址后，使用第一EASDF提供的DNS相关服务。
可选地，该PDU会话建立确认包括EPCO信元。在该EPCO信元内的0003H信元中携带有第一EASDF的地址信息。
步骤682：在PDU会话建立之后，SMF接收终端发送的DHCP请求；
在PDU会话建立之后，UE可能通过用户面向SMF发起DHCP请求获取一个DNS Server的地址，此时，SMF也需要在发送给UE的DHCP响应，该DHCP响应包含第一EASDF的地址信息，也即第一EASDF的IP地址。
步骤684：SMF向终端发送DHCP响应，DHCP响应携带有第一EASDF的地址信息。
示例性的，DHCP响应的EPCO信元的第四信元中，携带有第一EASDF的地址信息。
也即，若在PDU会话建立请求的EPCO信元中SMF提供了第一EASDF的地址信息，则在DHCP响应中，SMF也需要包含同样的第一EASDF的地址信息。
需要说明的是，在PDU会话建立请求中的第一EASDF的地址信息是UE的OS操作系统所触发的。而UE通过用户面的DHCP来获取第一EASDF的地址信息，通常是由UE中运行的APP所触发的。也即，SMF在PDU会话建立请求过程和DHCP过程下发两次地址信息，是为了让UE中不同程序模块(OS和APP)均获取到第一EASDF的地址信息。
综上所述，本实施例提供的方法，通过UE向SMF在PDU会话建立请求中的EPCO信 元中新增第二信元来发送第一标识，在保持PDU会话建立请求的一级信元数量不变的情况下，只修改EPCO信元中的信元内容，对通信协议的修改较少，也能够使得SMF在PDU会话建立过程中尽早获取到第一标识，从而在UE存在需求的情况下，由SMF向UE合理分配第一EASDF。
图7示出了本申请一个示例性实施例提供的地址信息获取方法的流程图。本实施例以该方法应用于UE中来举例说明。该方法包括：
步骤720：UE在PDU会话建立过程中向SMF发送第一标识，第一标识用于触发SMF为终端定位和选择第一EASDF；
可选地，UE向SMF发送PDU会话建立请求，该PDU会话建立请求中携带有第一标识。第一标识用于指示本次请求建立的PDU会话属于边缘计算的边缘连接。
示例性的，第一标识包括EC标识或EASDF标识。
在一个实施例中，第一标识携带在PDU会话建立请求的第一信元中。第一信元是边缘计算连接指示信元。图5示出了相关技术中的PDU会话建立请求的信令格式。在该PDU会话建立请求的信令格式中增加第一信元，使用第一信元来携带第一标识。该第一信元可以增加在图5所示的信令格式中的任意一列。该第一信元的类型为可选项。
在一个实施例中，第一标识携带在PDU会话建立请求的EPCO信元的第二信元中。也即，PDU会话建立请求的信元中包括EPCO信元，使用EPCO中新增的第二信元来携带第一标识。示例性的，EPCO至少包括如下信元：
终端到网络方向(即UE到SMF方向)：
0001H(P-CSCF IPv6地址请求)；
0002H(IM CN子系统信号标签)；
0003H(DNS服务IPv6地址请求)；
网络到终端方向(即SMF到UE方向)：
0001H(P-CSCF IPv6地址请求)；
0002H(IM CN子系统信号标签)；
0003H(DNS服务IPv6地址请求)；
在上述EPCO信元中新增一个扩展的第二信元。该第二信元是求EASDF的IP地址请求信元。比如，第二信元如下：
0013H(EASDF IP地址请求)。
在UE向SMF发送携带有第一标识的PDU会话建立请求后，SMF为UE分配或定位或选择第一EASDF。
SMF向UE发送PDU会话建立确认，该PDU会话建立确认携带有第一EASDF的地址信息。可选地，该PDU会话建立确认包括EPCO信元。在该EPCO信元内的0003H信元中携带有第一EASDF的地址信息。
步骤740：UE接收第一EASDF的地址信息。
UE接收SMF发送的PDU会话建立确认，该PDU会话建立确认携带有第一EASDF的地址信息。可选地，该地址信息是指第一EASDF的IP地址；
示例性的，第一EASDF的地址信息携带在PDU会话建立确认的EPCO的第三信元中。
UE在获得第一EASDF的IP地址后，使用第一EASDF提供的DNS相关服务。比如，DNS查询服务。
步骤760：在PDU会话建立之后，向SMF发送DHCP请求；
在PDU会话建立之后，UE可能通过用户面向SMF发起DHCP请求获取一个DNS Server的地址，此时，SMF也需要在发送给UE的DHCP响应，该DHCP响应包含第一EASDF的地址信息，也即第一EASDF的IP地址。
步骤780：接收SMF发送的DHCP响应，DHCP响应携带有第一EASDF的地址信息。
其中，第一EASDF的地址信息携带在DHCP响应的EPCO的第四信元中。
示例性的，DHCP响应的EPCO信元的第四信元中，携带有第一EASDF的地址信息。
也即，若在PDU会话建立请求的EPCO信元中SMF提供了第一EASDF的地址信息，则在DHCP响应中，SMF也需要包含同样的第一EASDF的地址信息。
需要说明的是，在PDU会话建立请求中的第一EASDF的地址信息是UE的OS操作系统所触发的。而UE通过用户面通过DHCP来获取第一EASDF的地址信息，通常是由UE中运行的APP所触发的。也即，SMF在PDU会话建立请求过程和DHCP过程下发两次地址信息，是为了让UE中不同程序模块(OS和APP)均获取到第一EASDF的地址信息。
需要说明的是，步骤760和步骤780为本实施例中的可选步骤，在一些实施例中可以不执行这2个步骤。
综上所述，本实施例提供的方法，通过UE向SMF在PDU会话建立请求中新增第一信元来发送第一标识，能够使得SMF在PDU会话建立过程中尽早获取到第一标识，从而在UE存在需求的情况下，由SMF向UE合理分配第一EASDF。
图8示出了本申请一个示例性实施例提供的EASDF的发现方法的流程图。该方法由UE、SMF、UPF、EASDF和DNS服务器来执行。该方法包括：
步骤1：UE向SMF发送PDU会话建立请求；
该PDU会话建立请求携带有第一标识，参考步骤720所示或图9的步骤1所示。
步骤2：SMF选择EASDF；
SMF发现PDU会话建立请求中包含有第一标识，为UE选择第一EASDF，第一EASDF是指SMF为UE选择的EASDF。
SMF选择EASDF的过程可以参考通信协议TS23.501的第6.3条的相关描述，此选择过程可以使用网络存储功能(NF Repository Function，NRF)发现，也可以基于SMF本地配置。EASDF可能已经在NRF注册。
步骤3：SMF向EASDF发送Neasdf_DNS上下文创建请求；
其中，Neasdf是指SMF和EASDF之间的接口或参考点。
SMF调用Neasdf_DNS上下文创建请求到选择的EASDF。Neasdf_DNS上下文创建请求携带有(UE IP地址，回调统一资源标识符(Uniform Resource Identifier，URI)，处理来自UE的DNS消息的规则)。其中，处理来自终端的DNS消息的规则(即DNS消息处理规则)包括DNS消息转发规则和/或DNS消息上报规则。DNS消息转发规则包括需要转发的DNS服务器地址和/或需要添加的扩展的DNS-客户端-子网ECS(EDNS-Client-Subnet)选项。
EASDF为PDU会话创建一个DNS上下文，并存储UE的IP地址，回调URI和处理从UE到上下文的DNS消息的规则。
DNS消息上报规则包括EASDF在收到DNS查询或DNS响应时，向SMF上报DNS信息(包括EAS相关信息)的上报条件。
EASDF处理DNS查询ECS选项或本地DNS服务器地址处理、SMF可以提供报告规则指导EASDF将边缘应用服务器(Edge Application Server，EAS)的全限定域名(s)(Fully Qualified Domain Name，FQDN)发送到SMF，如果DNS查询消息中的EAS FQDN匹配FQDN(s)过滤器的DNS信息报告的规则。
EASDF处理DNS响应特定的IP地址或FQDN范围，SMF提供报告的规则来指导EASDF报告EAS IP地址/FQDN SMF如果EAS的DNS响应消息匹配一个IP地址的IP地址范围(s)报告规则，或FQDN DNS响应匹配的FQDN DNS消息报道规则。
在EASDF收到DNS查询消息之前或在DNS查询报告之后，EASDF提供了转发规则，即用于FQDN(s)和数据网络接入标识符(s)(Data Network Access Identifier，DNAI)的ECS选项或本地DNS服务器。
步骤4：EASDF向SMF发送Neasdf_DNS上下文创建响应；
EASDF调用服务操作Neasdf_DNSContext_Create响应(EASDF的IP地址)，并使用允许SMF稍后更新或删除上下文的信息。
EASDF的IP地址是终端连接到EASDF作为PDU会话的DNS服务器的地址。
步骤5：SMF向UE发送PDU会话建立确认；
该PDU会话建立请求携带有第一EASDF的地址信息，参考步骤460或660所示。
步骤6：SMF向EASDF发送Neasdf_DNS上下文更新请求；
SMF可能会调用Neasdf_DNS上下文更新请求(PDU会话上下文ID，处理UE上DNS查询的规则)到EASDF。更新可能会引发的流动性问题，例如当问题转移到一个新的位置，或者报告通过与某些FQDN EASDF DNS查询，或者更新可能引发的插入/删除本地PSA，例如更新规则来处理DNS信息问题或新的PCC规则信息。
步骤7：EASDF向SMF发送Neasdf_DNS上下文更新响应；
步骤8：UE向EASDF发送DNS查询；
EASDF发送Neasdf_DNS上下文创建请求。
步骤9：EASDF向SMF发送Neasdf_DNS上下文通知请求；
如果匹配UE的DNS报文上报条件，则EASDF通过调用Neasdf_DNSContext_Notify请求将DNS报文上报给SMF。
步骤10：SMF向EASDF发送Neasdf_DNS上下文通知响应；
在Neasdf_DNS上下文通知响应包含如下的几个可能选项：
对于选项A，SMF可能在响应消息中包含相应的ECS选项。
对于选项B，SMF可能在响应消息中包含相应的本地DNS服务器IP地址。还可以指示EASDF简单地将DNS查询转发到预先配置的DNS服务器/解析器。
步骤11：EASDF向DNS服务器发送DNS查询；
对于选项A，EASDF将ECS选项添加到RFC 7871中指定的DNS查询消息中，并发送给中央DNS C-DNS服务器；在EASDF上本地配置有C-DNS或通过SMF所配置。
对于选项B，EASDF向本地DNS服务器发送DNS查询消息。此本地DNS服务器是在步骤10中由SMF所提供。
如果SMF提供的报告规则和转发规则都不匹配DNS查询中请求的FQDN，那么EASDF可以简单地将DNS查询转发到预先配置的DNS服务器/解析器。
步骤12：DNS服务器向EASDF发送DNS响应；
EASDF接收DNS系统的DNS响应，判断是否可以将DNS响应发送到终端。
步骤13：EASDF向SMF发送Neasdf_DNS上下文通知请求；
如果DNS响应报文中的EAS IP地址或FQDN与SMF提供的上报条件匹配，则EASDF可以通过调用Neasdf_DNS上下文通知请求向SMF发送DNS消息上报信息，包括EAS信息。
EASDF不向UE发送DNS响应消息，而是等待SMF指令。
步骤14：SMF向EASDF发送Neasdf_DNS上下文通知响应；
SMF调用Neasdf_DNSContext_Notify响应服务操作。
步骤15：上行分类器(Uplink Classifier，UL CL)/分支点(Branching Point，BP)插入；
SMF可以进行UL CL/BP和局部PSA选择，并插入UL CL/BP和局部PSA。
根据从EASDF接收到的EAS信息和通信协议TS 23.501第6.3.3条规定的其他UPF选择标准，SMF可以执行通信协议TS 23.502中描述的UL CL/BP和局部PSA选择和插入。
步骤16：SMF向EASDF发送Neasdf_DNS上下文更新请求；
SMF调用Neasdf_DNSContext_Update请求(正向DNS响应指示)。
“正向DNS响应”表示EASDF将步骤12中缓存的DNS响应转发到UE。
步骤17：EASDF向SMF发送Neasdf_DNS上下文更新响应；
步骤18：EASDF向UE发送DNS响应。
图9示出了本申请一个示例性实施例提供的PDU会话建立方法的流程图。该方法由UE、RAN、AMF、SMF、UPF、PCF、UDM和DN来执行。该方法包括：
步骤1：UE向AMF发送PDU会话建立请求；
步骤2：AMF进行SMF选择；
步骤3：AMF向SMF发送Nsmf_PDU会话创建SM上下文请求；
步骤4：SMF与UDM执行订阅检索/订阅更新；
步骤5：SMF向AMF发送Nsmf_PDU会话创建SM上下文响应；
步骤6：PDU会话身份验证/授权；
步骤7a：PCF选择；
步骤7b：SM策略关联建立或SMF发起SM策略关联修改；
步骤8：UPF选择；
步骤9：SMF启动SM策略关联修改；
步骤10a：SMF向UPF发送N4会话建立/修改请求；
步骤10b：UPF向SMF发送N4会话建立/修改请求；
步骤11：SMF向AMF发送Namf_CommunicationN1N2消息转换；
步骤12：AMF向(R)AN发送N2PDU会话请求(NAS消息)；
步骤13：UE与(R)AN执行(R)AN特定资源设置；
步骤14：(R)AN向AMF发送N2PDU会话响应；
步骤15：AMF向SMF发送Nsmf_PDU会话更新SM上下文请求；
步骤16a：SMF向UPF发送N4会话修改请求；
步骤16b：UPF向SMF发送N4会话修改响应；
步骤16c：SMF与UDM执行注册流程；
步骤17：SMF向AMF发送Nsmf_PDU会话更新SM上下文响应；
步骤18：SMF向AMF发送Nsmf_PDU会话SM上下文通知；
步骤19：SMF向UE进行IPv6地址配置；
步骤20：SMF启动SM策略关联修改；
步骤21：SMF与PCF取消订阅。
注1：在图8中的步骤2至4应当在图9所示的步骤11之前完成。
注2：在图8中的步骤5，对应图9所示的步骤11至16。
注3：图8中的步骤6至18，可以是在图9的步骤21之后，或图8中的步骤8对应于图9的步骤15前的第一次上行数据(First UL data)。
图8所示的步骤15的UL CL/分支点插入过程，如下图10所示出的步骤2至8。图10示出了本申请一个示例性实施例提供的增加额外的PDU会话锚和分支点或UL CL方法的流程图。该方法由UE、RAN、SMF和UPF来执行，该方法包括：
步骤1：UE与PSA1建立PDU会话；
UE具有已建立的PDU会话，其UPF包括PDU会话锚1(也即PSA1)。PDU会话用户平面至少涉及(R)AN和PDU会话锚1。
步骤2：SMF建立PSA2；
在某些时候，SMF决定建立新的PDU会话锚，例如由于UE移动性，新的流检测。SMF选择UPF并使用N4建立PDU会话的新PDU会话锚2(也即PSA2)。在IPv6多宿主PDU会话的情况下，SMF还分配对应于PSA2的新IPv6前缀，并且如果PCF已用户IP分配/释放事件，则SMF执行会话管理策略修改过程，为PCF提供新分配的IPv6前缀。
如果基于本地配置启用了5GC和AF之间的运行时协调，则根据对SMF事件的AF订阅中包含“预期的AF确认”的指示，SMF等待来自AF的通知响应。如果SMF从AF接 收到否定通知响应，则SMF可以停止该过程。
步骤3：SMF建立分支点或UL CL；
SMF选择UPF并使用N4建立分支点(在IPv6多归属的情况下)或PDU CL用于PDU会话。它为PSA1和PSA2提供必要的上行链路转发规则，包括PSA1CN通道信息和PSA2CN通道信息。另外，AN通道信息被提供用于下行链路转发。在IPv6多归属的情况下，SMF还为与PSA1和PSA2相对应的IPv6前缀提供流量过滤器，指示哪些流量将分别转发到PSA1和PSA2。在UL CL的情况下，SMF提供流量过滤器，指示应分别向PSA1和PSA2转发哪些流量。
在UL CL的情况下，SMF提供流量过滤器，指示应分别将哪些流量转发到PSA1和PSA2。如果基于本地配置启用了5GC和AF之间的运行时协调，则根据对SMF事件的AF订阅中包含“预期的AF确认”的指示，SMF将向AF发送延迟通知并等待通知。在配置UL CL之前，AF会做出响应。如果SMF从AF接收到否定通知响应，则SMF可以停止该过程。
注1：如果分支点或UL CL和PSA2共同位于单个UPF中，则可以合并步骤2和3。如果已经分配了分支点，则跳过步骤3。
步骤4：SMF为下行链路流量更新PSA1；
SMF通过N4为下行链路流量更新PSA1。它为下行链路流量提供分支点或UL CL CN通道信息。
注2：如果分支点或UL CL和PSA1共同位于单个UPF中，则可以合并步骤3和4。
步骤5：SMF更新PSA2；
SMF通过N4更新PSA2。它为下行链路流量提供分支点或UL CL CN通道信息。
注3：如果分支点或UL CL和PSA2共同位于单个UPF中，则不需要步骤5。
步骤6：SMF为上行链路流量更新(R)AN；
SMF通过N11上的N2SM信息更新(R)AN。它提供与UPF(分支点或UL CL)对应的新CN通道信息。在UL CL的情况下，如果在(R)AN和新插入的UL CL之间存在现有UPF，则SMF经由N4更新现有UPF而不是更新(R)AN。
步骤7：SMF通知UE新的IP前缀@PSA2；
在IPv6多宿主的情况下，SMF通知UE新IP前缀@PSA2的可用性。这是使用IPv6路由器通告消息(RFC 4861)执行的。此外，SMF使用IPv6路由器通告消息(RFC 4191)将路由规则连同IPv6前缀一起发送到UE，例如通信协议TS 23.501第5.8.1.2节中所述。
如果基于本地配置启用了5GC和AF之间的运行时协调，则根据AF订阅SMF事件中包含的“预期AF确认”指示，SMF将向AF发送延迟通知并等待通知响应从AF发送新IP前缀到UE。如果SMF从AF接收到否定通知响应，则SMF可以停止该过程。
步骤8：SMF为原始IP前缀@PSA1重新配置UE；
在IPv6多归属的情况下，SMF可以为原始IP前缀@PSA1重新配置UE；即SMF使用IPv6路由器通告消息将路由规则连同IPv6前缀一起发送到UE，(RFC 4191)例如通信协议TS 23.501第5.8.1.2条所述。
注：征求意见稿(Request For Comments，RFC)，是由互联网工程任务组(The Internet Engineering Task Force，IETF)发布的一系列备忘录。文件收集了有关互联网相关信息，以及UNIX和互联网社群的软件文件，以编号排定。目前RFC文件是由互联网协会(Internet Society，ISOC)赞助发行。
图11示出了本申请一个示例性实施例提供的地址信息发送装置的框图。该装置可以应用于SMF中，或者实现成为SMF的一部分，所述装置包括：
接收模块1120，用于接收终端在PDU会话建立过程发送的第一标识；
选择模块1140，用于根据所述第一标识为所述终端选择第一EASDF；
发送模块1160，用于向所述终端发送所述第一EASDF的地址信息。
可选地，所述接收模块1120，用于接收所述终端发送的PDU会话建立请求，所述PDU会话建立请求中携带有所述第一标识。所述第一标识用于指示本次请求建立的PDU会话属于边缘计算的边缘连接。
可选地，所述第一标识包括EC标识和EASDF标识中的至少一种。
在一种设计中，所述第一标识携带在所述PDU会话建立请求的第一信元中。所述第一信元是边缘计算连接指示信元。
在一个设计中，所述第一标识携带在所述PDU会话建立请求的扩展协议配置选项的第二信元中。所述第二信元是EASDF的IP地址请求信元。
可选地，所述发送模块1160，用于向所述终端发送PDU会话建立确认，所述PDU会话建立确认携带有所述第一EASDF的地址信息。
可选地，所述第一EASDF的地址信息携带在所述PDU会话建立确认的扩展协议配置选项的第三信元中。
可选地，所述接收模块1120，用于在所述PDU会话建立之后，接收所述终端发送的动态主机配置协议DHCP请求；所述发送模块1160，用于向所述终端发送DHCP响应，所述DHCP响应携带有所述第一EASDF的地址信息。
可选地，所述第一EASDF的地址信息携带在所述DHCP响应的扩展协议配置选项的第四信元中。
图12示出了本申请一个示例性实施例提供的地址信息获取装置的框图。该装置可以应用于终端中，或者实现成为终端的一部分，所述装置包括：
发送模块1220，用于在PDU会话建立过程中向SMF发送第一标识，所述第一标识用于触发所述SMF为所述终端选择第一EASDF；
接收模块1240，用于接收所述第一EASDF的地址信息。
可选地，所述发送模块1220，用于向SMF发送PDU会话建立请求，所述PDU会话建立请求中携带有所述第一标识。
可选地，所述第一标识用于指示本次请求建立的PDU会话属于边缘计算的边缘连接。
可选地，所述第一标识包括EC标识或EASDF标识。
在一个设计中，所述第一标识携带在所述PDU会话建立请求的第一信元中。可选地，所述第一信元是边缘计算连接指示信元。
在一个设计中，所述第一标识携带在所述PDU会话建立请求的扩展协议配置选项的第二信元中。
可选地，所述第二信元是EASDF的IP地址请求信元。
可选地，所述接收模块1240，用于接收所述SMF发送的PDU会话建立确认，所述PDU会话建立确认携带有所述第一EASDF的地址信息。所述第一EASDF的地址信息携带在所述PDU会话建立确认的扩展协议配置选项的第三信元中。
可选地，所述发送模块1220，用于在所述PDU会话建立之后，向所述SMF发送动态主机配置协议DHCP请求；接收模块1240，用于接收所述SMF发送的DHCP响应，所述DHCP响应携带有第一EASDF的地址信息。可选地，所述第一EASDF的地址信息携带在所述DHCP响应的扩展协议配置选项的第四信元中。
图13示出了本申请一个实施例提供的通信设备(网元设备或终端)的结构示意图，例如，该通信设备可以用于执行上述地址信息发送方法或地址信息获取方法。具体来讲：该通信设备1300可以包括：处理器1301、接收器1302、发射器1303、存储器1304和总线1305。
处理器1301包括一个或者一个以上处理核心，处理器1301通过运行软件程序以及模块，从而执行各种功能应用以及信息处理。
接收器1302和发射器1303可以实现为一个收发器1306，该收发器1306可以是一块通 信芯片。
存储器1304通过总线1305与处理器1301相连。
存储器1304可用于存储计算机程序，处理器1301用于执行该计算机程序，以实现上述方法实施例中的网元设备、接入网实体、核心网网元或核心网实体执行的各个步骤。
其中，发射器1303用于执行上述各个实施例中与发送相关的步骤；接收器1302用于执行上述各个实施例中与接收相关的步骤；处理器1301用于执行上述各个实施例中除发送和接收步骤之外的其它步骤。
此外，存储器1304可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，易失性或非易失性存储设备包括但不限于：RAM(Random-Access Memory，随机存储器)和ROM(Read-Only Memory，只读存储器)、EPROM(Erasable Programmable Read-Only Memory，可擦写可编程只读存储器)、EEPROM(Electrically Erasable Programmable Read-Only Memory，电可擦写可编程只读存储器)、闪存或其他固态存储其技术，CD-ROM(Compact Disc Read-Only Memory，只读光盘)、DVD(Digital Video Disc，高密度数字视频光盘)或其他光学存储、磁带盒、磁带、磁盘存储或其他磁性存储设备。
在示例性实施例中，还提供了一种网元设备，所述网元设备包括：处理器和存储器，所述存储器存储有计算机程序，所述计算机程序由所述处理器加载并执行以实现如上所述的地址信息发送方法。
在示例性实施例中，还提供了一种终端，所述终端包括：处理器和存储器，所述存储器存储有计算机程序，所述计算机程序由所述处理器加载并执行以实现如上所述的地址信息获取方法。
本申请还提供一种计算机可读存储介质，所述存储介质中存储有至少一条指令、至少一段程序、代码集或指令集，所述至少一条指令、所述至少一段程序、所述代码集或指令集由处理器加载并执行以实现上述方法实施例提供的地址信息发送方法或地址信息获取方法。
可选地，本申请还提供了一种计算机程序产品，所述计算机程序产品包括计算机指令，该计算机指令存储在计算机可读存储介质中。计算机设备的处理器从计算机可读存储介质读取该计算机指令，处理器执行该计算机指令，使得该计算机设备执行上述方面提供的地址信息发送方法或地址信息获取方法。

Claims (34)

  1. 一种地址信息发送方法，应用于会话管理功能SMF中，所述方法包括：
    接收终端在协议数据单元PDU会话建立过程发送的第一标识；
    根据所述第一标识为所述终端选择第一边缘应用服务器发现功能EASDF；
    向所述终端发送所述第一EASDF的地址信息。
  2. 根据权利要求1所述的方法，其中，所述接收终端在PDU会话建立过程发送的第一标识，包括：
    接收所述终端发送的PDU会话建立请求，所述PDU会话建立请求中携带有所述第一标识。
  3. 根据权利要求1所述的方法，其中，所述第一标识用于指示本次请求建立的PDU会话属于边缘计算的边缘连接。
  4. 根据权利要求1所述的方法，其中，所述第一标识包括边缘计算EC标识和EASDF标识中的至少一种。
  5. 根据权利要求2所述的方法，其中，所述第一标识携带在所述PDU会话建立请求的第一信元中。
  6. 根据权利要求5所述的方法，其中，
    所述第一信元是边缘计算连接指示信元。
  7. 根据权利要求2所述的方法，其中，所述第一标识携带在所述PDU会话建立请求的扩展协议配置选项的第二信元中。
  8. 根据权利要求2所述的方法，其中，
    所述第二信元是EASDF的网际互连协议IP地址请求信元。
  9. 根据权利要求1至4任一所述的方法，其中，所述向所述终端发送所述第一EASDF的地址信息，包括：
    向所述终端发送PDU会话建立确认，所述PDU会话建立确认携带有所述第一EASDF的地址信息。
  10. 根据权利要求9所述的方法，其中，所述第一EASDF的地址信息携带在所述PDU会话建立确认的扩展协议配置选项的第三信元中。
  11. 根据权利要求1至4任一所述的方法，其中，所述方法还包括：
    在所述PDU会话建立之后，接收所述终端发送的动态主机配置协议DHCP请求；
    向所述终端发送DHCP响应，所述DHCP响应携带有所述第一EASDF的地址信息。
  12. 根据权利要求11所述的方法，其中，所述第一EASDF的地址信息携带在所述DHCP响应的扩展协议配置选项的第四信元中。
  13. 一种地址信息获取方法，应用于终端中，所述方法包括：
    在协议数据单元PDU会话建立过程中向会话管理功能SMF发送第一标识，所述第一标识用于触发所述SMF为所述终端选择第一边缘应用服务器发现功能EASDF；
    接收所述第一EASDF的地址信息。
  14. 根据权利要求13所述的方法，其中，所述在PDU会话建立过程向SMF发送第一标识，包括：
    向所述SMF发送PDU会话建立请求，所述PDU会话建立请求中携带有所述第一标识。
  15. 根据权利要求13所述的方法，其中，所述第一标识用于指示本次请求建立的PDU会话属于边缘计算的边缘连接。
  16. 根据权利要求13所述的方法，其中，所述第一标识包括边缘计算EC标识或EASDF标识。
  17. 根据权利要求14所述的方法，其中，所述第一标识携带在所述PDU会话建立请求的第一信元中。
  18. 根据权利要求17所述的方法，其中，
    所述第一信元是边缘计算连接指示信元。
  19. 根据权利要求14所述的方法，其中，所述第一标识携带在所述PDU会话建立请求的扩展协议配置选项的第二信元中。
  20. 根据权利要求19所述的方法，其中，
    所述第二信元是EASDF的网际互连协议IP地址请求信元。
  21. 根据权利要求11至16任一所述的方法，其中，所述接收所述第一EASDF的地址信息，包括：
    接收所述SMF发送的PDU会话建立确认，所述PDU会话建立确认携带有所述第一EASDF的地址信息。
  22. 根据权利要求21所述的方法，其中，所述第一EASDF的地址信息携带在所述PDU会话建立确认的扩展协议配置选项的第三信元中。
  23. 根据权利要求11至16任一所述的方法，其中，所述方法还包括：
    在所述PDU会话建立之后，向所述SMF发送动态主机配置协议DHCP请求；
    接收所述SMF发送的DHCP响应，所述DHCP响应携带有第一EASDF的地址信息。
  24. 根据权利要求23所述的方法，其中，所述第一EASDF的地址信息携带在所述DHCP响应的扩展协议配置选项的第四信元中。
  25. 一种地址信息发送装置，所述装置包括：
    发送模块，用于接收终端在PDU会话建立过程发送的第一标识；
    处理模块，用于根据所述第一标识为所述终端选择第一EASDF；
    发送模块，用于向所述终端发送所述第一EASDF的地址信息。
  26. 一种地址信息获取装置，所述装置包括：
    发送模块，用于在PDU会话建立过程中向SMF发送第一标识，所述第一标识用于触发所述SMF为所述终端定位和选择第一EASDF；
    接收模块，用于接收所述第一EASDF的地址信息。
  27. 一种网元设备，所述网元设备包括：处理器和存储器，所述存储器存储有计算机程序，所述计算机程序由所述处理器加载并执行以实现如权利要求1至12任一所述的地址信息发送方法。
  28. 一种终端，所述终端包括：处理器和存储器，所述存储器存储有计算机程序，所述计算机程序由所述处理器加载并执行以实现如权利要求13至24任一所述的地址信息获取方法。
  29. 一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，所述计算机程序由处理器加载并执行以实现如权利要求1至12任一所述的地址信息发送方法。
  30. 一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，所述计算机程序由处理器加载并执行以实现如权利要求13至24任一所述的地址信息获取方法。
  31. 一种计算机程序产品，所述计算机程序产品存储有计算机程序，所述计算机程序由处理器加载并执行以实现如权利要求1至12任一所述的地址信息发送方法。
  32. 一种计算机程序产品，所述计算机程序产品存储有计算机程序，所述计算机程序由处理器加载并执行以实现如权利要求13至24任一所述的地址信息获取方法。
  33. 一种芯片，所述芯片被配置为执行如权利要求1至12任一所述的地址信息发送方法。
  34. 一种芯片，所述芯片被配置为执行如权利要求13至24任一所述的地址信息获取方法。
PCT/CN2022/078589 2021-04-02 2022-03-01 地址信息发送方法、获取方法、装置、设备及介质 WO2022206260A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP22778445.1A EP4213577A4 (en) 2021-04-02 2022-03-01 METHOD AND DEVICE FOR SENDING ADDRESS INFORMATION, METHOD AND DEVICE FOR RECEIVING ADDRESS INFORMATION, DEVICE AND MEDIUM
US17/993,865 US20230086304A1 (en) 2021-04-02 2022-11-23 Method and apparatus for transmitting address information, method and apparatus for obtaining address information, device, and medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110362381.8 2021-04-02
CN202110362381.8A CN113115480A (zh) 2021-04-02 2021-04-02 地址信息发送方法、获取方法、装置、设备及介质

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/993,865 Continuation US20230086304A1 (en) 2021-04-02 2022-11-23 Method and apparatus for transmitting address information, method and apparatus for obtaining address information, device, and medium

Publications (1)

Publication Number Publication Date
WO2022206260A1 true WO2022206260A1 (zh) 2022-10-06

Family

ID=76713591

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/078589 WO2022206260A1 (zh) 2021-04-02 2022-03-01 地址信息发送方法、获取方法、装置、设备及介质

Country Status (4)

Country Link
US (1) US20230086304A1 (zh)
EP (1) EP4213577A4 (zh)
CN (1) CN113115480A (zh)
WO (1) WO2022206260A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4354828A1 (en) * 2022-10-10 2024-04-17 Nokia Solutions and Networks Oy V-easdf in home routed roaming

Families Citing this family (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113115480A (zh) * 2021-04-02 2021-07-13 腾讯科技（深圳）有限公司 地址信息发送方法、获取方法、装置、设备及介质
CN113691969B (zh) * 2021-07-16 2022-10-18 华为技术有限公司 通信方法和装置
CN113573303B (zh) * 2021-07-20 2022-08-26 中国联合网络通信集团有限公司 一种边缘应用服务器确定方法及装置
CN116668511A (zh) * 2021-07-21 2023-08-29 腾讯科技（深圳）有限公司 一种数据处理方法、网元设备以及可读存储介质
CN118018517A (zh) * 2021-07-21 2024-05-10 腾讯科技（深圳）有限公司 一种数据处理方法、网元设备以及可读存储介质
CN113630272B (zh) * 2021-08-06 2022-12-06 华为技术有限公司 一种通信方法及装置
CN113794784B (zh) * 2021-08-06 2022-11-11 华为技术有限公司 一种获取边缘服务的方法和装置
CN115884152A (zh) * 2021-09-30 2023-03-31 华为技术有限公司 通信的方法和装置
WO2023057800A1 (en) * 2021-10-08 2023-04-13 Nokia Technologies Oy Method, apparatus, and computer program
CN116267035A (zh) * 2021-10-18 2023-06-20 北京小米移动软件有限公司 边缘服务器的路由选择方法、装置、通信设备及存储介质
CN116267034A (zh) * 2021-10-18 2023-06-20 北京小米移动软件有限公司 边缘应用服务器的选择方法及装置、网元设备、终端及存储介质
CN116074383A (zh) * 2021-11-04 2023-05-05 维沃移动通信有限公司 Dns消息的发送方法、终端及网络侧设备
CN116866892A (zh) * 2022-03-28 2023-10-10 华为技术有限公司 通信方法和通信装置
WO2023184118A1 (en) * 2022-03-28 2023-10-05 Nokia Shanghai Bell Co., Ltd. Location service enhancement based on usage of an user plane interface with a terminal device
WO2023184130A1 (en) * 2022-03-29 2023-10-05 Nokia Shanghai Bell Co., Ltd. Location service user plane function address information obtainment

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20200115155A (ko) * 2019-03-28 2020-10-07 삼성전자주식회사 Edge Computing 서비스를 이용하기 위하여 단말에 연결성을 제공하는 방법 및 장치
CN111918279A (zh) * 2019-05-07 2020-11-10 华为技术有限公司 一种寻址方法、通信装置及系统
CN113115480A (zh) * 2021-04-02 2021-07-13 腾讯科技（深圳）有限公司 地址信息发送方法、获取方法、装置、设备及介质

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108934007B (zh) * 2017-05-25 2022-03-25 中兴通讯股份有限公司 一种upf重选的策略控制方法、pcf及smf
CN108684073B (zh) * 2017-06-19 2019-08-27 华为技术有限公司 一种注册及会话建立的方法、终端和amf实体

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20200115155A (ko) * 2019-03-28 2020-10-07 삼성전자주식회사 Edge Computing 서비스를 이용하기 위하여 단말에 연결성을 제공하는 방법 및 장치
CN111918279A (zh) * 2019-05-07 2020-11-10 华为技术有限公司 一种寻址方法、通信装置及系统
CN113115480A (zh) * 2021-04-02 2021-07-13 腾讯科技（深圳）有限公司 地址信息发送方法、获取方法、装置、设备及介质

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on enhancement of support for Edge Computing in 5G Core network (5GC) (Release 17)", 3GPP STANDARD; TECHNICAL REPORT; 3GPP TR 23.748, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. V17.0.0, 17 December 2020 (2020-12-17), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , pages 1 - 250, XP051975180 *
HUAWEI, NOKIA, NOKIA SHANGHAI BELL, CHINA MOBILE, ZTE, FUTUREWEI, NTT DOCOMO, LENOVO, INTERDIGITAL INC.: "EAS Discovery for Session Breakout connectivity model", 3GPP DRAFT; S2-2100116, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. e-meeting; 20210224 - 20210309, 18 February 2021 (2021-02-18), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052172463 *
See also references of EP4213577A4

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4354828A1 (en) * 2022-10-10 2024-04-17 Nokia Solutions and Networks Oy V-easdf in home routed roaming

Also Published As

Publication number Publication date
EP4213577A4 (en) 2024-03-27
CN113115480A (zh) 2021-07-13
US20230086304A1 (en) 2023-03-23
EP4213577A1 (en) 2023-07-19

Similar Documents

Publication Publication Date Title
WO2022206260A1 (zh) 地址信息发送方法、获取方法、装置、设备及介质
EP3821622B1 (en) Systems and methods for enabling private communication within a user equipment group
US20210112379A1 (en) Communication method and communications apparatus
WO2021043191A1 (zh) 域名系统服务器的确定方法、请求处理方法和装置、系统
US11729137B2 (en) Method and device for edge application server discovery
US11463935B2 (en) Methods and functions for handling local breakout
US11855957B2 (en) Discovery method and apparatus for DNS server, computer device, computer-readable storage medium and computer program product
WO2022033345A1 (zh) 一种pdu会话建立方法、终端设备和芯片系统
WO2021051420A1 (zh) 一种dns缓存记录的确定方法及装置
CN113114650B (zh) 网络攻击的解决方法、装置、设备及介质
US20230156577A1 (en) Exposure and Discovery of Distributed Network Functions Serving a User Equipment or PPDU Session
US20220345532A1 (en) Apparatus, method, and computer program
US20230224792A1 (en) Dynamic activation of local breakout with coordination between application domain and mobile network
EP4113943A1 (en) System and method for subscriber awareness in a 5g network
WO2021233196A1 (zh) 加入组播广播业务mbs会话的方法及装置
CN114071649B (zh) 访问本地网络的方法和装置
US20230247524A1 (en) Support for data forwarding
WO2022067538A1 (zh) 网元发现方法、装置、设备及存储介质
WO2022001972A1 (zh) Dns请求的解析方法、通信装置及通信系统
US20240187374A1 (en) Method and apparatus for improving a server discovery handling procedure
WO2022217376A1 (en) Method and apparatus for improving a server discovery handling procedure
US20230025344A1 (en) Application Discovery Method, Apparatus, and System, and Computer Storage Medium
US11653334B2 (en) Systems and methods for reducing transcoding resource allocation during call setup to multiple terminations
US11870601B2 (en) Policy control function fallback
WO2022213486A1 (zh) 网络功能注册方法、发现方法、装置、设备及介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22778445

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2022778445

Country of ref document: EP

Effective date: 20230315

NENP Non-entry into the national phase

Ref country code: DE