[go: up one dir, main page]
More Web Proxy on the site http://driver.im/

WO2022100197A1 - 获取边缘服务的方法和装置 - Google Patents

获取边缘服务的方法和装置 Download PDF

Info

Publication number
WO2022100197A1
WO2022100197A1 PCT/CN2021/114172 CN2021114172W WO2022100197A1 WO 2022100197 A1 WO2022100197 A1 WO 2022100197A1 CN 2021114172 W CN2021114172 W CN 2021114172W WO 2022100197 A1 WO2022100197 A1 WO 2022100197A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
message
network element
core network
edge
Prior art date
Application number
PCT/CN2021/114172
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 华为技术有限公司
Publication of WO2022100197A1 publication Critical patent/WO2022100197A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H04W8/14—Mobility data transfer between corresponding nodes

Definitions

  • the present application relates to the field of communication technologies, and more particularly, to a method and apparatus for acquiring edge services.
  • the user equipment generally adopts the following scheme to send information to the edge server: the edge enabler client (EEC), as a part of the UE, will first configure the edge configuration server on the EEC, Then, the EEC sends a service provisioning request (service provisioning request) or a service subscription update request (service subscription update request) to the ECS to obtain the address information of the edge enabler server (EES), UE or EEC After obtaining the address information of the EES, the EEC sends an EAS discovery request (EAS discovery request) to the EES to obtain the address information of the edge application server (EAS).
  • EAS edge enabler client
  • both the service provisioning request and the EAS discovery request are sent through the HTTP protocol, they are only applicable to the request-response model, and the UE needs to maintain a long connection. UE pushes information.
  • edge services there is a need for a method for obtaining edge services, so that the ECS or EES can also push or send information to the UE without maintaining a persistent connection, so as to obtain edge services.
  • the present application provides a method and apparatus for obtaining edge services.
  • the UE does not need to maintain a persistent connection, and the ECS or EES can also push or send information to the UE to obtain the edge service.
  • the method may be executed by a terminal device, or may also be executed by a component (eg, a chip or a chip system, etc.) configured in the terminal device.
  • a component eg, a chip or a chip system, etc.
  • This application does not limit this.
  • This application takes the user equipment UE as an example for description.
  • a first aspect provides a method for obtaining an edge service, the method comprising: a first control plane core network element receiving first information of a user equipment UE; the first control plane core network element sending the first information to a first edge configuration server.
  • a message, the first message includes the first information and the first notification information, and the first notification information includes the notification address information of the first control plane core network element and/or the context information of the UE ;
  • the first control plane core network element receives a second message from the first edge configuration server, the second message includes the first notification information and second information, and the second information includes the first edge configuring the information sent by the server to the UE; the first control plane core network element sends the second information to the UE according to the first notification information.
  • the user equipment may send the first information to the first control plane core network element, and the first control plane core network element forwards the first information of the UE and carries the first notification address information to the first edge configuration server, In order to facilitate the first edge configuration server to determine which core network element to send the information to.
  • the first edge configuration server determines the second information sent to the UE and sends it to the first control plane core network element and carries the first notification address information, and the first control plane core network element can send the information according to the first notification address information. sent to the UE.
  • the UE sends relevant information through the core network element of the control plane, which can realize that when the ECS or EES belongs to the 5GC network element, the UE does not need to maintain a long connection, and can also send information to the edge server, thereby Get edge services.
  • the first information in this embodiment of the present application includes information sent by the UE to the edge configuration server, for example, the first information may be used to request identification information of the edge enabling server.
  • the first notification information is used to indicate a sending direction of the second information.
  • the first edge configuration server may determine the object to send the second information through the first notification information.
  • the first control plane core network element receiving the first information of the user equipment UE includes: the first control plane core network element receiving the user equipment through a session establishment request message the first information of the equipment UE; or, the first control plane core network element receives the first information of the user equipment UE through a session modification request message; or, the first control plane core network element passes the non-access stratum
  • the container NAS Container message receives the first information of the user equipment UE.
  • the UE can send the first information to the core network element of the first control plane through a session establishment request message or a session modification request message or a non-access stratum container NAS Container message, so as to realize sending the information to the edge server.
  • a session establishment request message or a session modification request message or a non-access stratum container NAS Container message so as to realize sending the information to the edge server.
  • the above messages are only exemplary and should not have any limitations on the embodiments of the present application, and the present application does not exclude that the UE may use other messages to send the first information to the first control plane core network element.
  • the first information includes at least one of the following: a service configuration request, a service configuration subscription request, a service configuration subscription update request, and a service configuration cancellation subscription request.
  • the UE can also send a subscription request, so that when the address information of the edge enabling server or the edge application server changes, the UE can also obtain the updated address information in real time.
  • the first control plane core network element sends the second information to the UE according to the first notification information, including: the first control plane The core network element sends the second information to the UE through a session establishment reception message according to the first notification information; or, the first control plane core network element sends a session modification command according to the first notification information message to send the second information to the UE; or, the first control plane core network element sends the second information to the UE through a non-access stratum container NAS Container message according to the first notification information .
  • the first control plane core network element sending the first message to the first edge configuration server includes: the first control plane core network element passing the second The core network element sends a first message to the first edge configuration server.
  • the first message may be sent to the first edge configuration server through the PCF network element.
  • the first control plane core network element receiving the second message from the first edge configuration server includes: the first control plane core network element passing the The second core network element receives the second message from the first edge configuration server.
  • the second message of the first edge configuration server may be received through the PCF network element.
  • the method further includes: the first control plane core network element sends a third message to a third core network element, where the third message is used to request an acquisition Identification information of the edge configuration server, the identification information includes the uniform resource identifier of the edge configuration server and/or the Internet Protocol IP address information of the edge configuration server; the first control plane core network element receives the third The fourth message of the network element of the core network, where the fourth message includes the identification information of the first edge configuration server.
  • the first control plane core network element may first determine the edge configuration server, and at this time, may query the third core network element to determine the edge configuration server, for example, the first edge configuration server. Therefore, when the edge configuration server is a core network element, information can be sent to it, so as to obtain edge services.
  • the edge configuration server can be configured on the network side, which improves the flexibility of the address configuration of the edge server and ensures service experience.
  • the third message includes location information of the UE, and the location information of the UE is used by the third core network element to determine the first edge configuration
  • the location information of the UE includes at least one of the following: a tracking area identity of the UE, a cell identity of the UE, or a data network access identity of the UE.
  • the network element of the third core network may determine the first edge configuration server according to the location information of the UE and the service scope of the edge configuration server.
  • the first information further includes identification information of the first edge configuration server, and the first control plane core network element sends the first edge configuration server to the first edge configuration server.
  • a message includes: the first control plane core network network element sends a first message to the first edge configuration server according to the identification information of the first edge configuration server.
  • the UE may also send the identification information of the first edge configuration server to the first control plane core network element, so that the first control plane core network element can directly determine which edge configuration server to send the information to through the identification information.
  • the second information when the first information includes an identification message of the UE requesting to acquire an edge-enabled server, the second information further includes an identification of the first edge-enabled server message, the identification information includes at least one of the following: uniform resource identifier information, instance identifier information or Internet Protocol IP address information.
  • the first edge configuration server may determine the edge-enabled server, for example, the first edge-enabled server. In this way, the UE can send information to the edge configuration server to obtain the edge service.
  • the second information includes an identification message of the first edge-enabled server
  • the method further includes: the first control plane core network element receives the UE's identification message.
  • third information where the third information includes information sent by the UE to the first edge-enabled server; the first control plane core network element sends a fifth message to the first edge-enabled server, the fifth message includes the third information and first notification information, where the first notification information includes notification address information of the first control plane core network element and/or context information of the UE;
  • the The first control plane core network element receives a sixth message from the first edge-enabled server, where the sixth message includes the first notification information and fourth information, and the fourth information includes the first edge application server and the first control plane core network element sends the fourth information to the UE according to the first notification information.
  • the first control plane core network element may first determine the edge enabling server, and then request the first edge enabling server to obtain the identification information of the edge application server, and then send to the UE. In this way, the UE can send information to the edge configuration server to obtain the edge service.
  • the first control plane core network element receives a second message from the first edge configuration server, where the second message includes the first notification information and second information, where the second information includes information sent by the first edge configuration server to the UE, and the method further includes: the first control plane core network element saves the second information.
  • the first control plane core network element can store the identification information of the edge-enabling server, so that when the UE sends a message to the edge-enabling server subsequently, the first control plane core network element can verify the identification information specified by the UE. Whether the edge-enabled server is legal.
  • the first control plane core network element includes: a session management function network element, an access and mobility management function network element, or a policy control network element.
  • the UE sends relevant information through the core network element of the control plane, so that when the ECS is the core network element or the AF, the UE sends information to the ECS through the core network element.
  • the ECS sends the information to the ECS through the core network element.
  • the network element sends information to the UE to obtain the edge service, and the changes to the existing mechanism (including the UE and the network element on the network side) are small.
  • the technical solution provided by the present application can realize the configuration of the address information of the ECS on the network side, improve the flexibility of the address configuration of the edge server, and ensure the service experience.
  • the embodiment of the present application can also realize that when the address information of the EES or the EAS changes, the UE can also obtain the updated address information of the EES or the EAS in real time.
  • a method for obtaining an edge service comprising: a first edge configuration server receiving a first message of a first control plane core network element, where the first message includes first information and a first notification information, the first notification information includes notification address information of the first control plane core network element and/or context information of the UE; the first edge configuration server determines the first edge configuration server according to the first information two messages, the second message includes the first notification information and second information, the second information includes the information sent by the first edge configuration server to the UE; the first edge configuration server sends the information to the UE.
  • the first control plane core network element sends the second message.
  • the first edge configuration server may determine information to be acquired by the UE according to the first information, and send the second information to the first control plane core network element. It can be implemented that when the edge configuration server or the edge enabling server is a core network element, the UE sends information to the edge server, so as to obtain the edge service.
  • the first notification information is used to indicate a sending direction of the second information.
  • the first information includes at least one of the following: a service configuration request, a service configuration subscription request, a service configuration subscription update request, and a service configuration cancellation subscription request.
  • the first edge configuration server receiving the first message of the core network element of the first control plane includes: the first edge configuration server receives the first message through the second core network element The first message of the core network element of the first control plane.
  • the first edge configuration server sends a second message to the first control plane core network element, including: the first edge configuration server sends a second message through the second core network element.
  • the network element sends a second message to the first control plane core network element.
  • the second information when the first information is the UE requesting to obtain the identification message of the edge-enabled server, the second information further includes the identification of the first edge-enabled server message, the identification information includes at least one of the following information: uniform resource identifier information, instance identifier information or Internet Protocol IP address information.
  • the first control plane core network element includes: a session management function network element, an access and mobility management function network element, or a policy control network element.
  • the UE sends the relevant information through the core network element of the control plane, so that when the ECS is the core network element or the AF, the UE sends the information to the ECS through the core network element.
  • the ECS sends the information to the ECS through the core network element.
  • the network element sends information to the UE to obtain edge services, and the changes to the existing mechanism (including the UE and the network element on the network side) are small.
  • the technical solution provided by the present application can realize the configuration of the address information of the ECS on the network side, improve the flexibility of the address configuration of the edge server, and ensure the service experience.
  • the embodiment of the present application can also realize that when the address information of the EES or the EAS changes, the UE can also obtain the updated address information of the EES or the EAS in real time.
  • a third aspect provides a method for acquiring an edge service, the method comprising: a third core network element receiving a third message of the first control plane core network element, where the third message is used to request to acquire an edge configuration server
  • the identification information includes the uniform resource identifier of the edge configuration server and/or the Internet Protocol IP address information of the edge configuration server; the third core network element determines the first Four messages, where the fourth message includes identification information of the first edge configuration server; the third core network element sends the fourth information to the first control plane core network element.
  • the first edge configuration server may determine the edge-enabled server, for example, the first edge-enabled server. In this way, the UE can send information to the edge configuration server to obtain the edge service.
  • the third message includes location information of the UE, and the location information of the UE is used by the third core network element to determine the first edge configuration
  • the location information of the UE includes at least one of the following: a tracking area identity of the UE, a cell identity of the UE, or a data network access identity of the UE.
  • the first control plane core network element includes: a session management function network element, an access and mobility management function network element, or a policy control network element.
  • the UE sends the relevant information through the core network element of the control plane, so that when the ECS is the core network element or the AF, the UE sends the information to the ECS through the core network element.
  • the ECS sends the information to the ECS through the core network element.
  • the network element sends information to the UE, and the changes to the existing mechanism (including the UE and the network element on the network side) are relatively small.
  • the technical solution provided by the present application can realize the configuration of the address information of the ECS on the network side, improve the flexibility of the address configuration of the edge server, and ensure the service experience.
  • the embodiment of the present application can also realize that when the address information of the EES or the EAS changes, the UE can also obtain the updated address information of the EES or the EAS in real time.
  • a method for obtaining an edge service comprising: a first edge application server receiving a fifth message of the first control plane core network element, the fifth message including first information and a first notification information, the first notification information includes the notification address information of the first control plane core network element and/or the context information of the UE; the first edge application server determines the sixth message according to the first information , the sixth message includes the first notification information and third information, and the third information includes the identification information of the first edge application server; the first edge application server reports to the first control plane core network network The element sends the sixth message.
  • the first control plane core network element may first determine the edge enabling server, and then request the first edge enabling server to obtain the edge application server's identifier. The identification information is then sent to the UE. In this way, the UE can send information to the edge configuration server to obtain the edge service.
  • the first control plane core network element includes: a session management function network element, an access and mobility management function network element, or a policy control network element.
  • the UE sends the relevant information through the core network element of the control plane, so that when the ECS is the core network element or the AF, the UE sends the information to the ECS through the core network element.
  • the ECS sends the information to the ECS through the core network element.
  • the network element sends information to the UE to obtain edge services, and the changes to the existing mechanism (including the UE and the network element on the network side) are small.
  • the technical solution provided by the present application can realize the configuration of the address information of the ECS on the network side, improve the flexibility of the address configuration of the edge server, and ensure the service experience.
  • the embodiment of the present application can also realize that when the address information of the EES or the EAS changes, the UE can also obtain the updated address information of the EES or the EAS in real time.
  • an apparatus for obtaining an edge service including each module or unit for performing the method in any one of the possible implementations of the first aspect, the second aspect, the third aspect, and the fourth aspect.
  • a device for acquiring edge services including a processor and a memory, where the memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that the communication apparatus executes the first to The communication method in any possible implementation manner of the fourth aspect.
  • the processor is one or more, and the memory is one or more.
  • the memory may be integrated with the processor, or the memory may be provided separately from the processor.
  • the communication device also includes a transmitter (transmitter) and a receiver (receiver).
  • a communication device in one possible design, includes a transceiver, a processor, and a memory.
  • the processor is used to control the transceiver to send and receive signals
  • the memory is used to store a computer program
  • the processor is used to call and run the computer program from the memory, so that the communication device performs the first to fourth aspects or the first to fourth aspects method in any of the possible implementations.
  • a computer program product comprising: a computer program (also referred to as code, or instructions), which, when the computer program is executed, causes the computer to execute the above-mentioned first to sixth aspects The method in any of the four possible implementations.
  • a computer-readable medium stores a computer program (also referred to as code, or instruction), when it runs on a computer, causing the computer to execute the above-mentioned first aspect to sixth The method in any of the four possible implementations.
  • a computer program also referred to as code, or instruction
  • a chip system including a memory and a processor, the memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that the communication device installed with the chip system executes the above-mentioned The method in any one possible implementation manner of the first aspect to the fourth aspect.
  • a tenth aspect provides a chip, the chip includes a processor and a communication interface, the communication interface is used to communicate with an external device or an internal device, and the processor is used to implement any one of the first to fourth aspects above. method in the implementation.
  • the chip may further include a memory in which instructions are stored, and the processor is configured to execute the instructions stored in the memory or derived from other instructions. When the instruction is executed, the processor is configured to implement the method in any of the possible implementation manners of the first aspect to the fourth aspect.
  • the chip may be integrated on an access network device.
  • a system comprising a first control plane core network element and a first edge configuration server for communicating with the first control plane core network element.
  • the system may further include a third core network element.
  • a twelfth aspect provides a method for obtaining an edge service, the method comprising: a first control plane core network element receiving fifth information of a user equipment UE; and the first control plane core network element reporting to a second edge
  • the configuration server sends a seventh message, where the seventh message includes the seventh and fifth information and session information of the UE, where the session information of the UE is used by the second edge configuration server to establish an AF session for an application function network element ; the first control plane core network element receives the eighth message through the AF session, and the eighth message includes the information sent by the second edge configuration server to the UE; the first control plane The core network element sends the eighth message to the UE.
  • the user equipment may send fifth information to the first control plane core network element, and the first control plane core network element forwards the fifth information of the UE to the second edge configuration server and carries the session information of the UE,
  • the first edge configuration server In order to associate the first edge configuration server with the first control plane core network element and the UE, it can directly determine which core network element and which UE to send information to.
  • the second edge configuration server determines the information sent to the UE and sends it to the first control plane core network element, and the first control plane core network element may send the information to the UE.
  • the UE sends relevant information through the core network element of the control plane, so that when the ECS or EES belongs to the 5GC network element, the UE can also send information to the edge server to obtain edge services.
  • the fifth information includes information that the UE requests from the edge configuration server, for example, the fifth information may be information for the UE to request to obtain ECS identification information.
  • the session information of the UE includes at least one of the following items: the Internet Protocol IP address of the UE, the data network name DNN corresponding to the session of the UE, and a single Network slice selection auxiliary information S-NSSAI.
  • the method further includes: the first control plane core network element determines the second edge configuration server according to the location information of the UE.
  • the first control plane core network element receiving the fifth information of the user equipment UE includes: the first control plane core network element requests a session establishment through a session message receiving the first information of the user equipment UE; or, the first control plane core network element receives the first information of the user equipment UE through a session modification request message; or, the first control plane core network element
  • the access layer container NAS Container message receives the first information of the user equipment UE.
  • the fifth information includes at least one of the following: a service configuration request, a service configuration subscription request, a service configuration subscription update request, and a service configuration cancellation subscription request.
  • the first control plane core network element sends a seventh message to the second edge configuration server, including: the first control plane core network element The network element of the second core network sends a seventh message to the second edge configuration server.
  • the first control plane core network element receives the eighth message of the second edge configuration server, including: the first control plane core network element The eighth message of the second edge configuration server is received through the second core network element.
  • the first control plane core network element includes: a session management function network element, an access and mobility management function network element, or a policy control network element.
  • a thirteenth aspect provides a method for obtaining an edge service, the method comprising: a second edge configuration server receiving a seventh message of the first control plane core network element, where the seventh message includes fifth information and Session information of the user equipment UE, the fifth information includes information that the UE requests an edge configuration server; the session information of the UE is used by the second edge configuration server to establish an AF session of an application function network element; the second edge configuration server The edge configuration server determines an eighth message according to the fifth information, where the eighth message includes information sent by the second edge configuration server to the UE; the second edge configuration server sends the information to the UE through the AF session.
  • the first control plane core network element sends the eighth message.
  • the session information of the UE includes at least one of the following items: the Internet Protocol IP address of the UE, the data network name DNN corresponding to the session of the UE, and Single network slice selection auxiliary information S-NSSAI.
  • the second edge configuration server is determined according to the location information of the UE.
  • the first control plane core network element includes: a session management function network element or an access and mobility management function network element or a policy control network element.
  • the UE when the ECS is a core network element or an AF, the UE sends information to the ECS through the core network element, and correspondingly, the ECS sends information to the UE through the core network element, thereby obtaining edge services , the changes to the existing mechanism (including the UE and the network element on the network side) are small.
  • the technical solution provided by the present application can realize the configuration of the address information of the ECS on the network side, improve the flexibility of the address configuration of the edge server, and ensure the service experience.
  • the embodiment of the present application can also realize that when the address information of the EES or the EAS changes, the UE can also obtain the updated address information of the EES or the EAS in real time.
  • a fourteenth aspect provides an apparatus for obtaining an edge service, including each module or unit for performing the method in any possible implementation manner of the eleventh aspect and the twelfth aspect.
  • a fifteenth aspect provides a device for obtaining an edge service, including a processor and a memory, where the memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that the communication apparatus executes the first
  • the communication method in any one of the possible implementations of the eleventh and twelfth aspects.
  • the processor is one or more, and the memory is one or more.
  • the memory may be integrated with the processor, or the memory may be provided separately from the processor.
  • the communication device also includes a transmitter (transmitter) and a receiver (receiver).
  • a communication device in one possible design, includes a transceiver, a processor, and a memory.
  • the processor is used to control the transceiver to send and receive signals
  • the memory is used to store a computer program
  • the processor is used to call and run the computer program from the memory, so that the communication device performs the first to fourth aspects or the first to fourth aspects method in any of the possible implementations.
  • a sixteenth aspect provides a computer program product, the computer program product comprising: a computer program (also referred to as code, or instructions), which, when the computer program is executed, causes a computer to execute the above eleventh aspect and the method in any of the possible implementations of the twelfth aspect.
  • a computer program also referred to as code, or instructions
  • a computer-readable medium stores a computer program (also referred to as code, or instruction), when it runs on a computer, causing the computer to execute the above eleventh aspect and the method in any of the possible implementations of the twelfth aspect.
  • a computer program also referred to as code, or instruction
  • a chip system including a memory and a processor, where the memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that a communication device installed with the chip system executes the The method in any possible implementation manner of the eleventh aspect to the twelfth aspect.
  • a nineteenth aspect provides a chip, where the chip includes a processor and a communication interface, where the communication interface is used to communicate with an external device or an internal device, and the processor is configured to implement any of the above eleventh to twelfth aspects A method in a possible implementation.
  • the chip may further include a memory in which instructions are stored, and the processor is configured to execute the instructions stored in the memory or derived from other instructions. When the instruction is executed, the processor is configured to implement the method in any of the possible implementation manners of the first aspect to the fourth aspect.
  • the chip may be integrated on an access network device.
  • a twentieth aspect provides a system including a first control plane core network element and a second edge configuration server for communicating with the first control plane core network element.
  • the present application provides a method and device for obtaining edge services.
  • the UE sends relevant information through the core network element of the control plane, so that when the ECS is the core network element or the AF, the UE sends information to the ECS through the core network element,
  • the ECS sends information to the UE through the core network element, so as to obtain the edge service, and the changes to the existing mechanism (including the UE and the network element on the network side) are relatively small.
  • FIG. 1 is an architecture diagram of a system applicable to an embodiment of the present application.
  • FIG. 2 is a schematic diagram of an edge service architecture according to an embodiment of the present application.
  • FIG. 3 is a schematic diagram of another edge service architecture according to an embodiment of the present application.
  • FIG. 4 is a schematic diagram of another edge service architecture applicable to the embodiment of the present application.
  • FIG. 5 is a schematic flowchart of a method for acquiring an edge service provided by another embodiment of the present application.
  • FIG. 6 is a schematic flowchart of a method for acquiring an edge service provided by another embodiment of the present application.
  • FIG. 7 is a schematic flowchart of a method for acquiring an edge service provided by another embodiment of the present application.
  • FIG. 8 is a schematic flowchart of a method for acquiring an edge service provided by another embodiment of the present application.
  • FIG. 9 is a schematic flowchart of a method for acquiring an edge service provided by another embodiment of the present application.
  • FIG. 10 is a schematic flowchart of a method for acquiring an edge service provided by another embodiment of the present application.
  • FIG. 11 is a schematic flowchart of a method for acquiring an edge service provided by another embodiment of the present application.
  • FIG. 12 is a schematic block diagram of an apparatus for obtaining an edge service provided by an embodiment of the present application.
  • FIG. 13 is a schematic block diagram of an apparatus for obtaining an edge service provided by an embodiment of the present application.
  • FIG. 14 is a schematic block diagram of a device for acquiring an edge service provided by an embodiment of the present application.
  • the wireless communication systems mentioned in the embodiments of the present application include but are not limited to: a global system of mobile communication (GSM) system, a long term evolution (long term evolution, LTE) frequency division duplex (frequency division duplex, FDD) system , LTE time division duplex (TDD), LTE system, long-term evolution advanced (LTE-Advanced, LTE-A) system, next-generation communication system (for example, 6G communication system), convergence of multiple access systems system, or evolving system.
  • GSM global system of mobile communication
  • LTE long term evolution
  • FDD frequency division duplex
  • TDD LTE time division duplex
  • LTE system long-term evolution advanced
  • next-generation communication system for example, 6G communication system
  • convergence of multiple access systems system or evolving system.
  • the technical solutions provided in this application can also be applied to machine type communication (MTC), Long Term Evolution-machine (LTE-M), device to device (device to device, D2D) networks , Machine to Machine (M2M) network, Internet of Things (IoT) network or other network.
  • the IoT network may include, for example, the Internet of Vehicles.
  • vehicle to X, V2X, X can represent anything
  • the V2X may include: vehicle to vehicle (vehicle to vehicle, V2V) communication, vehicle and vehicle Infrastructure (V2I) communication, vehicle to pedestrian (V2P) or vehicle to network (V2N) communication, etc.
  • the terminal devices involved in the embodiments of the present application may include various access terminals, mobile devices, user terminals, or user equipment with wireless communication functions.
  • the terminal device may be a user equipment (UE), such as a mobile phone (mobile phone), a tablet computer (Pad), a computer with a wireless transceiver function, a virtual reality (virtual reality, VR) terminal device, an augmented reality (augmented reality, AR) terminal equipment, etc.
  • the terminal equipment can also be a wireless terminal in industrial control (industrial control), a machine type communication (MTC) terminal, a customer terminal equipment (customer premise equipment, CPE), and a wireless terminal in self-driving (self-driving).
  • industrial control industrial control
  • MTC machine type communication
  • CPE customer premise equipment
  • self-driving self-driving
  • wireless terminal in remote medical wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, smart home ), cellular telephones, cordless telephones, session initiation protocol (SIP) telephones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld Equipment, computing equipment or other processing equipment connected to a wireless modem, in-vehicle equipment, wearable equipment, terminal equipment in a 5G network or terminal equipment in a future evolved public land mobile network (PLMN), etc.
  • SIP session initiation protocol
  • WLL wireless local loop
  • PDAs personal digital assistants
  • handheld Equipment computing equipment or other processing equipment connected to a wireless modem
  • in-vehicle equipment wearable equipment
  • terminal equipment in a 5G network or terminal equipment in a future evolved public land mobile network (PLMN) etc.
  • FIG. 1 is a system architecture diagram to which an embodiment of the present application is applicable.
  • the network architecture may specifically include the following network elements:
  • Radio access network An access network that implements access network functions based on wireless communication technology can be called a radio access network.
  • the radio access network can manage radio resources, provide access services for terminals, and then complete the forwarding of control signals and user data between the terminal and the core network.
  • the wireless access network can be, for example, a base station (base transceiver station, BTS) in the global system of mobile communication (GSM) system or code division multiple access (CDMA), or a broadband code division A base station (nodeB, NB) in a wideband code division multiple access (WCDMA) system, an evolved base station (evolutional nodeB, eNB or eNodeB) in an LTE system, or a cloud radio access network (cloud radio access network (CRAN) scenario, or the network device can be a relay station, an access point, an in-vehicle device, a wearable device, and a network device in a future 5G network or a network device in a future evolved PLMN network, etc. , the embodiments of the present application are not limited.
  • AUSF Authentication server function
  • Access and mobility management function network element (access and mobility management function, AMF): mainly used for mobility management and access management, etc., and can be used to implement mobility management entity (mobility management entity, MME) functions Other functions than session management, such as lawful interception, or access authorization (or authentication) functions.
  • AMF access and mobility management function
  • MME mobility management entity
  • the functions of the access and mobility management network elements can be implemented.
  • Session management function (session management function, SMF): mainly used for session management, IP address allocation and management of terminal equipment, selection and management of user plane functions, policy control, or the termination point of charging function interface and downlink data notice etc. In this embodiment of the present application, it can be used to implement the function of the session management network element.
  • PCF Policy control function
  • Application function network element used to perform data routing affected by applications, access network open function network elements, or interact with the policy framework to perform policy control, etc.
  • Unified data management used for unified data management, 5G user data management, processing user identification, access authentication, registration, or mobility management, etc.
  • User plane function It can be used for packet routing and forwarding, or quality of service (QoS) processing of user plane data.
  • User data can be accessed to a data network (DN) through this network element.
  • DN data network
  • it can be used to implement the function of the user plane network element.
  • Network slice selection function Network element (network slice selection function, NSSF): used to manage information related to network slices.
  • Digital network A network used to provide data transmission.
  • DN Digital network
  • An operator's service network For example, an operator's service network, an Internet (Internet) network, a third-party service network, and the like.
  • the above-mentioned network architecture also includes a network storage function (network function (NF) repository function, NRF): used to store the description information of the network function entity and the services it provides, and support service discovery, network element entity discovery, etc.; Network Exposure Function (NEF): used to securely open to the outside the services and capabilities provided by the 3rd Generation Partnership Project (3GPP) network function.
  • NF network function
  • NRF Network Exposure Function
  • UDR Unified Data Repository
  • the network system architecture in this application may also include an edge configuration server (ECS) network element, and the ECS network element may be a global management network element that maintains the network elements of each edge data network (EDN).
  • Information including the service range of the edge data network and the address of the edge enabler server (EES) in the edge data network.
  • the service range of the edge data network can be topological address information (such as Cell ID, TAI (Trach area id), etc.) or geometric address information (such as province, city, district, or latitude and longitude), and the service range can be address information. collection.
  • the ECS network elements are deployed in a distributed manner, that is, each ECS can manage edge data networks in different regions.
  • the ECS network element may be co-located with other network elements or may be an independent network element, and this application does not make any limitation on the deployment of the ECS network element in the network architecture.
  • the network system architecture in this application may also include an edge enabler server (EES) network element
  • EES edge enabler server
  • the EES network element may be a mobile edge computing (mobile edge computing, MEC) node (MEC may also be referred to as
  • MEC mobile edge computing
  • the control network element or management network element in multi access edge computing (multi access edge computing) is responsible for managing each EAS deployed in the EDN, such as registration, domain name system (domain name system, DNS) resolution content routing, Basic functions such as upper-layer application registration management and wireless information exchange.
  • the EES can invoke the capability opening function network elements in the 3GPP network.
  • the EES network element may be co-located with other network elements or may be an independent network element, and this application does not make any limitation on the deployment of the EES network element in the network architecture.
  • the N2 interface is the interface between the RAN and the AMF network element, which is used for sending non-access stratum (NAS) messages, etc.
  • the N3 interface is the interface between the RAN and the UPF network element, using It is used to transmit user plane data, etc.
  • the N4 interface is the interface between the SMF network element and the UPF network element, which 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 above-mentioned network architecture applied to the embodiments of the present application is only a network architecture described from the perspective of a traditional point-to-point architecture and a service-oriented architecture, and the network architecture applicable to the embodiments of the present application is not limited thereto. Any network architecture capable of implementing the functions of the foregoing network elements is applicable to the embodiments of the present application.
  • the name of the interface between each network element in FIG. 1 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 application.
  • the names of the messages (or signaling) transmitted between the above network elements are only an example, and do not constitute any limitation on the functions of the messages themselves.
  • FIG. 2 is a schematic diagram of an edge service architecture according to an embodiment of the present application.
  • the network architecture may specifically include: an edge data network (EDN) may be a local data center, and the EDN includes an edge enabler server (edge enabler server). , EES) and multiple edge application servers (EAS), each EDN has a specific service scope.
  • the EES may be a control network element or a management network element in a mobile edge computing (mobile edge computing, MEC) node (MEC may also be referred to as multi access edge computing (multi access edge computing)), responsible for managing the deployment in the EDN
  • MEC mobile edge computing
  • MEC mobile edge computing node
  • multi access edge computing multi access edge computing
  • EES can invoke the capability opening function network elements in the 3GPP network.
  • An edge data network configuration server (EDNCS) or an edge configuration server (ECS) can be a global management network element that maintains information about each EDN, including service scope and EES addresses. It should be noted that in some standard protocols, such as technical specification (TS) 23.501, TS23.502, etc., the above EES, EAS, ECS, etc. can all be called AF (application function), which will not be repeated below. .
  • a user equipment may include: an edge enabler client (EEC) and an application client, wherein the EEC provides necessary support for the application client on the terminal, and the functions of the EEC include: EDGE-4 retrieves EDN information, UE registers to EES, retrieves available EAS, EAS availability changes, EAS migration notification to EEC.
  • EEC edge enabler client
  • EES edge enabler client
  • the EDGE-8 reference point in Figure 2 supports the interaction between the edge configuration server and the core network, which supports: (1) access to core network functions and application programming interfaces (APIs) for retrieving network capability information; (2) Provide service issuance notification to the core network (for example: SMF).
  • EDGE-1 The interface between EES and EEC, supports EEC registration/de-registration in EES; edge application server discovery in edge data network.
  • EDGE-2 The interface between the EES and the 3GPP core network, used by the EES to obtain the 3GPP network capabilities.
  • EDGE-3 The interface between EES and EAS, which supports EES registration/deregistration of EAS, including EAS availability information, service scope information, address information, etc.; EES provides 3GPP network capability information (such as location information) to EAS.
  • EDGE-4 The interface between the EEC and the ECS, which supports the ECS to provide/push configuration information to the EEC.
  • EDGE-5 The interface between the AC and the EEC, which supports the AC to obtain access EAS information from the EEC.
  • EDGE-6 The interface between ECS and EES, which supports configuring EES information on ECS.
  • EDGE-7 The interface between EAS and 3GPP core network, supports EAS to obtain 3GPP network capabilities.
  • EDGE-8 The interface between the ECS and the 3GPP core network, which supports the ECS to obtain 3GPP network capabilities.
  • EDGE-9 The interface between different EESs across MEC nodes/in the same MEC node, supports application migration.
  • FIG. 3 is a schematic diagram of another edge service architecture according to an embodiment of the present application.
  • the operator or service provider will lower the deployment of the application server to the prefecture and city level (the application server was originally deployed by province or region).
  • the application server may be deployed in multiple networks (including edge data network and central data network) or MEC nodes. Each MEC node or edge data network has a corresponding service area, and there may be crossover between the service areas of different edge data networks. If the location moves when the UE accesses an application, the application server accessed by the UE usually also needs to be switched accordingly, so that the application can be accessed with a lower delay.
  • FIG. 4 is a schematic diagram of another system architecture to which the embodiment of the present application is applied.
  • the network architecture may specifically include: an edge data network EDN, each EDN has a specific service range, and each edge network includes one or more Multiple Edge Enable Server EES and Edge Application Server EAS.
  • the service scope of EDN#1 includes an EES#1, EAS#1 and EAS#2; the service scope of EDN#2 includes an EES#2, EAS#3 and EAS#4.
  • the edge configuration server ECS is a global management network element, and maintains the information of each EDN, including service scope and EES address.
  • the user equipment UE can access the edge server through the core network element.
  • the UE may obtain the address information of the EES and the EAS through network elements such as UPF, AMF, SMF, or PCF.
  • the EEC is first configured on the EEC, that is, the address information of the ECS is configured on the user equipment UE.
  • Step 1 the EEC sends a request to the ECS, for example, a service provisioning request (service provisioning request) or a service provisioning subscription request (service provisioningrequest) to obtain the address information of the EES;
  • Step 2 the ECS sends a response to the EEC, such as a service provisioning response ( service provision response), send EES address information to EEC.
  • the EEC sends a request to the EES, for example, an EAS discovery request (EAS discovery request), to obtain the address information of the EAS.
  • the EES sends a response to the EEC, for example, an EAS discovery response (EAS discovery response), and sends the EAS address information to the EEC.
  • EAS discovery request an EAS discovery request
  • EAS discovery response an EAS discovery response
  • the above technical solution is to configure the ECS address on the UE, the configuration is inflexible and the ECS has a risk of a single point of failure.
  • the communication between the UE and the ECS or the EES adopts the HTTP protocol. If the address information of the EES changes, the ECS needs to dynamically deliver the location information of the EES to the UE. At this time, the UE needs to allocate ports and resources for monitoring the notification information of the ECS in real time. Considering the power consumption and security of the UE, the UE does not currently support this function. Therefore, using the HTTP protocol for communication in the above technical solution cannot solve the problem of notifying the UE in real time in a scenario where the EES address information changes. To support the above scenarios, the changes to the UE are very large.
  • This application provides a method for obtaining edge services.
  • the UE sends relevant information through the core network element of the control plane, so that when the ECS or EES belongs to the 5GC network element or AF (application function), the UE can also send information to the edge server, Changes to existing mechanisms (including UE and network elements on the network side) are minor.
  • the technical solution provided by the present application can realize the configuration of the address information of the ECS on the network side, improve the flexibility of the address configuration of the edge server, and ensure the service experience.
  • the embodiment of the present application can also realize that when the address information of the EES or the EAS changes, the UE can also obtain the updated address information of the EES or the EAS in real time.
  • the ECS may be a global management network element that maintains the information of each edge data network EDN, including the service scope and the address of the edge enabling server EES. That is to say, the EES address information is configured or saved on the ECS. Therefore, in a possible implementation manner in the embodiment of the present application, when the UE sends a request message to the core network to request the EES address information, the core network may first determine the ECS, and then the core network sends a request to the target ECS, using After requesting the address information of the EES, the ECS determines the address information of the EES and sends it to the UE.
  • the core network may send a request to the target EES, and the EES determines the EAS address information, this is because the address information of the EAS is configured or saved on the EES.
  • the core network may directly determine the address information of the EES or EAS that can currently serve the UE through other means such as configuration.
  • the identification message in the embodiment of the present application may refer to address information, that is, the identification information in the embodiment of the present application may include address information of the edge server.
  • the identification information of the edge server may also include, for example, the uniform resource identifier (URI) of the edge server and/or the Internet Protocol IP address information of the edge server, and the identification information may also include the instance identifier of the edge server ( instance ID), and the identification information may also include the fully qualified domain name (FQDN) of the edge server.
  • URI uniform resource identifier
  • FQDN fully qualified domain name
  • the address information of the edge server can be obtained according to the identification message.
  • the edge server may be ECS, EES or EAS.
  • identification information may also be any other information that can obtain the address information of the edge server.
  • FIG. 5 is a schematic flowchart of a method for obtaining an edge service provided by an embodiment of the present application.
  • UE#1 is taken as an example.
  • UE#1 can send information to a 5G core network element (5G Core, 5GC) (in this embodiment, SMF is used as an example) through messages such as non-access stratum NAS messages.
  • the network element can forward the information sent by UE#1 to the edge server, so that the UE sends information to the edge server (ECS or EES) through the core network element.
  • EES edge server
  • the edge server sends the EES to the UE through the core network element. or EAS identification information to obtain edge services.
  • the technical solutions provided by the embodiments of the present application can realize the configuration of the address information of the ECS on the network side, improve the flexibility of the address configuration of the edge server, and ensure the service experience.
  • the network element of the 5GC core network in this embodiment may also be other network elements such as AMF or PCF, that is to say, the following steps may also be performed by replacing SMF with other network elements such as AMF or PCF in this embodiment, which is not limited.
  • the 5G core network element in the embodiment is the SMF or the PCF
  • the information sent by the UE may be forwarded to the SMF or the PCF through the AMF network element.
  • FIG. 5 is a schematic flowchart of a method 100 for sending information to an edge server provided by the present application.
  • the first control plane core network element in FIG. 5 may be an AMF network element, an SMF network element, or a PCF network element.
  • Step S101 a first control plane core network element receives first information of a user equipment UE, where the first information includes information sent by the UE to an edge configuration server.
  • the user equipment UE may send the first information to the SMF through a session establishment request message, a session modification request message, a non-access stratum container NAS Container message, and the like.
  • the first information sent by UE#1 to the SMF may include: a service provisioning request (service provisioning request), a service provisioning subscription request (service provisioning subscription request), a service provisioning subscription update request (service provisioning subscription update request), Service provisioning unsubscribe request.
  • a service provisioning request service provisioning request
  • a service provisioning subscription request service provisioning subscription request
  • a service provisioning subscription update request service provisioning subscription update request
  • Service provisioning unsubscribe request Service provisioning unsubscribe request.
  • a service provisioning request, a service provisioning subscription request, a service provisioning subscription update request, and a service provisioning unsubscribe request may include in the session establishment request message or the session modification request message.
  • the above request may be a single NAS request.
  • a “service configuration request message” and the like may also be referred to as a “service configuration request”, which will not be described in detail below.
  • the first information sent by the UE to the network element of the core network of the first control plane may be information sent by the UE to the edge configuration server.
  • the first information may be a service configuration request for requesting to acquire the identification information of the EES.
  • the first information may further include indication information, where the indication information is used to instruct UE#1 to acquire the identification information of the EES.
  • the first information may also include application information, for example, application ID (for example, information of the service to be connected by UE#1) or application client profile.
  • the first information may further include identification information of UE#1, and the identification information of UE#1 may be used for 5GC and/or ECS to authenticate UE#1.
  • the first information may further include location information of UE#1, and the location information of UE#1 may be determined for the ECS and EES determined by the network side to serve the UE.
  • the location information of UE#1 may include: tracking area identity (TAI) and/or cell identity (cell identity, Cell ID) where UE#1 is located, or data corresponding to the current (PDU session) of UE#1 Network access identity (date network access identity, DNAI) and other information.
  • TAI tracking area identity
  • cell identity Cell ID
  • DNAI Network access identity
  • the first information can also carry a subscription indication, which is used to instruct the 5GC and/or ECS UE#1 to subscribe to the EES change notification, that is, when the available EES information changes, the changed EES information is notified to UE#1.
  • the changed EES information may be one or more of the following information: new EES information, old EES information, and changed EES information sent compared to the EES information previously sent to UE#1.
  • the subscription indication information may be used to indicate the change information of the edge server that can serve the UE when the location of the UE changes. That is to say, the subscription indication information can enable the UE to dynamically obtain the current real-time updated information of the server that can serve the UE.
  • the subscription indication information may be embodied by a service provisioning request or a service subscription update request.
  • Step S102 the first control plane core network element sends a first message to the first edge configuration server, where the first message includes first information and first notification information, and the first notification information includes a notification from the first control plane core network element address information and/or context information of the UE.
  • the first control plane core network element may send the first message to the first edge configuration server through the second core network element.
  • the core network element of the first control plane is the SMF
  • the first message may be sent to the first edge configuration server through the PCF network element.
  • the network element of the core network of the first control plane may determine that the message needs to be sent to the ECS. Specifically, the network element of the core network of the first control plane may be based on local configuration or based on the message name or The subscription information and the like determine that the message needs to be forwarded and sent to the ECS.
  • the core network element of the first control plane may query a third core network element (for example, an NRF network element) to determine the first edge configuration server, and then send the first information to the first edge configuration server.
  • the first message; or, the first control plane core network element receives the first information sent by the UE, and determines the first edge configuration server according to the historical storage information. It can be seen from this that the embodiment of the present application configures the address information of the ECS on the network side, which improves the flexibility of the edge server address configuration and ensures service experience.
  • the first control plane core network element when the first control plane core network element sends the first message to the first edge configuration server, it may be that the first control plane core network element directly forwards the first information of the user equipment UE, that is, the first message
  • the content can completely include the first information, and the first information also includes the first notification information.
  • the first notification information may include notification address information of the core network element of the first control plane and/or context information of the UE. According to the first notification information, it is convenient for the first edge configuration server to determine the address of the first control plane core network element, and can also be used for the first edge configuration server or the first control plane core network element to determine the UE.
  • the first edge configuration server may determine the information sent to the UE according to the first information, that is, the second information; may determine the address of the core network element of the first control plane according to the first notification address information, and then send the information to the first notification address information.
  • a control plane core network element sends the second message.
  • the first notification information in this embodiment of the present application is used to indicate the sending direction of the second information, for example:
  • the first notification information may be used to instruct the first edge configuration server to send information to the first control plane core network element.
  • the first notification information may be used to instruct the first edge configuration server to send information to the UE.
  • the first notification information may also be used to instruct the first edge configuration server to send information to the UE through a core network element (eg, SMF).
  • a core network element eg, SMF
  • the second information in this application may be information sent by the first edge configuration server to the UE. It should be noted that the information sent by the first edge configuration server to the UE may be determined according to the first information. As an example, if the first information in the first message is used for the UE to request to obtain the identification information of the EES, at this time, the first edge configuration server can be based on information such as the location information of the UE or the load information or application information of the edge enabling server. The identification information of the target EES is acquired, and then the identification information of the EES (ie, the second message) is sent to the first control plane core network element.
  • the first edge configuration server may determine, according to the location information of the UE, the identification information of the edge-enabled server currently serving the UE (ie, The second message) is sent to the first control plane core network element.
  • the second information may include: service provisioning request response (service provisioning response), service provisioning subscription request response (service provisioning subscription response), service provisioning subscription update request response (service provisioning subscription update response), service provisioning subscription cancellation request response (service provisioning subscription update response) provisioning unsubscribe response).
  • Step S103 the first control plane core network element receives a second message from the first edge configuration server, where the second message includes first notification information and second information, and the second information includes information sent by the first edge configuration server to the UE.
  • the first control plane core network element receives the second message of the first edge configuration server through the second core network element.
  • the core network element of the first control plane is an SMF
  • the second message of the first edge configuration server may be received through the PCF network element.
  • the first notification information is included in the destination address of the second message data packet.
  • the second message may be a response message to the first message. If the first message is a subscription message or includes subscription information, the second message may be a notification message corresponding to the first message, and the notification message may be sent multiple times. For example, the notification message is sent when the edge configuration server determines that the updated EES identification information needs to be sent to the UE.
  • the request message, notification message and response message are collectively referred to as "message" in this application, but based on the specific steps of each embodiment, those skilled in the art should understand and understand that the "message" is a request message, a notification message It is still a response message, which will not be repeated below.
  • the first control plane core network element receives a second message sent by the first edge configuration server according to the first message, where the second message includes the first notification information and the second information.
  • the first edge configuration server determines the second information according to the first information in the first message, for example, the first information is a service configuration request, the second information is a service configuration response, and the response information includes the determined EES identification information or connection information.
  • the first information is a service configuration subscription request
  • the second information is a service configuration notification
  • the response information includes the determined identification information or connection information of the EES.
  • the connection information may be URI and/or the Internet Protocol IP address information of the edge server
  • the connection information may also include the instance identifier (instance ID) of the edge server
  • the connection information may also include the fully qualified domain name (fully qualified domain name) of the edge server.
  • FQDN FQDN
  • Step S104 the first control plane core network element sends the second information to the UE according to the first notification information.
  • the first control plane core network network element may determine to which UE to send the second information according to the first notification information.
  • the first control plane core network element may send the second information to the UE through a session establishment reception message; or, the first control plane core network element may send the second information to the UE through a session modification command message,
  • the second information may be included in the session establishment reception message or the session modification command message as a NAS container; or, the first control plane core network element may send the second information to the UE through other non-access stratum container NAS messages.
  • the UE sends relevant information through the core network element of the control plane, so that when the ECS or EES belongs to the 5GC network element or AF (application function), the UE can pass the core network element or AF (application function).
  • the network element sends information to the edge server (ECS or EES).
  • the edge server sends the identification information of the EES or EAS to the UE through the core network element, so as to obtain the edge service.
  • FIG. 6 is a schematic flowchart of a method 200 for sending information to an edge server according to the first specific embodiment of the present application.
  • the method 200 shown in FIG. 6 may be performed by network elements such as AMF, SMF, NRF, and ECS in the system shown in FIG. 1 .
  • the method includes S201 to S211. This embodiment is described by taking UE#1 as an example, and each step is described in detail below.
  • Step S201 the ECS may register its own configuration information with the NRF.
  • the configuration information may include information such as the service scope of the ECS and the ID of the ECS.
  • each ECS has a corresponding service scope, and this embodiment includes multiple edge configuration servers, for example, ECS#1, ECS#2...ECS#n. That is to say, multiple ECSs can register their own configuration files with the NRF. In fact, multiple edge configuration servers can register their configuration information with the NRF.
  • Step S202 UE#1 may send first information to the SMF, where the first information includes information sent by UE#1 to the edge configuration server.
  • UE#1 may send the first information to the SMF through a session establishment request message, a session modification request message, a non-access stratum container NAS Container message, and the like.
  • the first information sent by UE#1 to the SMF may include: a service provisioning request (service provisioning request), a service configuration subscription request (service subscription request), a service configuration subscription update request (service subscription update request), Service configuration unsubscribe request (service unsubscribe request).
  • a service provisioning request service provisioning request
  • a service configuration subscription request service subscription request
  • a service configuration subscription update request service subscription update request
  • Service configuration unsubscribe request service unsubscribe request
  • a service provisioning request, a service configuration subscription request, a service configuration subscription update request, and a service configuration unsubscribe request may include in the session establishment request message or the session modification request message.
  • the first information may further include indication information, where the indication information is used to instruct UE#1 to acquire the identification information of the EES.
  • the first information may also include application information, for example, application ID (for example, information of the service to be connected by UE#1) or application client profile.
  • the first information may further include identification information of UE#1, and the identification information of UE#1 may be used for 5GC and/or ECS to authenticate UE#1.
  • the first information may further include location information of UE#1, and the location information of UE#1 may be determined for the ECS and EES determined by the network side to serve the UE.
  • the location information of UE#1 may include: tracking area identity (TAI) and/or cell identity (cell identity, Cell ID) where UE#1 is located, or data corresponding to the current (PDU session) of UE#1 Network access identity (date network access identity, DNAI) and other information.
  • TAI tracking area identity
  • cell identity Cell ID
  • DNAI Network access identity
  • the first information can also carry a subscription indication, which is used to instruct the 5GC and/or ECS UE#1 to subscribe to the EES change notification, that is, when the available EES information changes, the changed EES information is notified to UE#1.
  • the changed EES information may be one or more of the following information: new EES information, old EES information, and changed EES information sent compared to the EES information previously sent to UE#1.
  • the subscription indication information may be used to indicate the change information of the edge server that can serve the UE when the location of the UE changes. That is to say, the subscription indication information can enable the UE to dynamically obtain the current real-time updated information of the server that can serve the UE.
  • the subscription indication information may be embodied through a service provisioning request (service provisioning request) or a service configuration subscription update request (service subscription update request).
  • Step S203 after receiving the first information, the SMF determines that the first information needs to be sent to the ECS.
  • the SMF may determine that it needs to send the information to the ECS based on the local configuration or the message name of the first information or the subscription information or the like.
  • the SMF may also check whether the UE#1 is allowed to send information to the edge server. That is to say, SMF can check whether the information sent by UE#1 to the edge configuration server is valid. For example, the SMF may determine whether UE#1 is allowed to send information to the edge server according to the subscription information of UE#1.
  • the SMF may first determine to which ECS the information (the first information) should be sent, that is, the SMF may first obtain the identification information of the ECS (taking ECS #1 as an example).
  • Step S204 the SMF obtains the identification information of the ECS (taking ECS#1 as an example).
  • this application takes ECS#1 as an example, that is, the SMF obtains the identification message of ECS#1.
  • the address information and service range information of the ECS are stored or configured on the NRF, so the SMF can query the NRF to determine the ECS#1 that can serve the UE#1.
  • the SMF may send a message #1 to the NRF for requesting to query the information of the ECS.
  • message #1 may include location information of UE#1.
  • Step S204b the NRF determines the identification information of ECS#1.
  • the NRF may determine a target ECS, ie, ECS#1, based on the current location information of UE#1 and the service range of the ECS.
  • the service range of ECS#1 includes area 1 and area 2, and the current location of UE#1 is in area 1, the NRF can determine that ECS#1 is the ECS serving UE#1.
  • the location information of UE#1 may be reported by the SMF to the NRF, and the NFR may also send a request to the AMF to query the location information of UE#1.
  • the NRF may send a message #2 to the SMF, and the message #2 includes the identification information of the ECS #1. Specifically, if the NRF determines the target ECS#1, the NRF sends the identification information of ECS#1 (for example, the uniform resource identifier (URI) of ECS#1 and/or the Internet Protocol of ECS#1 to the SMF
  • the IP address information may also be the instance identifier (instance ID) of ECS#1, etc.).
  • step S205 may be further included, and the SMF may also save the received identification information of ECS#1 for subsequent SMF to check whether the request of the UE is legal after receiving the first information of the UE.
  • step S206 may also be included, where ECS#1 authenticates and authorizes UE#1.
  • UE#1 can be authenticated and authorized in a manner similar to protocol data unit (protocol data unit, PDU) session authentication in the prior art, that is, SMF provides authentication or authorization-related messages between UE#1 and ECS#1.
  • PDU protocol data unit
  • the SMF can send message #3 (an example of the first message) to the target ECS (for example, ECS #1, an example of the first edge configuration server), and the message #3 includes the first information and first notification information, where the first notification information includes notification address information of the SMF and/or context information of the UE.
  • the target ECS for example, ECS #1, an example of the first edge configuration server
  • Step S207 the SMF may send a message #3 to the ECS #1, where the message #3 includes first information and first notification information, where the first notification information includes notification address information of the SMF and/or context information of the UE.
  • the notification address information of the SMF may be, for example, the URI of the SMF.
  • the first notification information in this embodiment of the present application is used to indicate the sending direction of the second information, for example:
  • the first notification information may be used to instruct the first edge configuration server to send information to the first control plane core network element.
  • the first notification information may be used to instruct the first edge configuration server to send information to the UE.
  • the first notification information may also be used to instruct the first edge configuration server to send information to the UE through a core network element (eg, SMF), which will not be described in detail below.
  • a core network element eg, SMF
  • the SMF may forward the received first information to ECS#1 and carry the first notification information.
  • the first notification information may be used to determine address information of core network elements and/or UE information.
  • ECS#1 may determine which SMF or which UE to send the response message to according to the first notification address information.
  • the SMF may send the first information to the corresponding ECS according to the identification information of ECS#1 received in step S204c.
  • the SMF may invoke the service provisioning request of ECS#1, for example, the SMF sends a service provisioning request message to ECS#1, where the message includes: first information and first notification information.
  • the content of the first information may be the content of the first information in step S202.
  • the content of the message #3 may include indication information, where the indication information is used to instruct the UE #1 to acquire the identification information of the EES.
  • the identification information and application information of UE#1 may also be included.
  • the content of message #3 may also include location information of UE#1, which may be used by ECS#1 to determine EES#1.
  • the location information of UE#1 may include: tracking area identity (TAI) and/or cell identity (cell identity, Cell ID) where UE#1 is located, or data corresponding to the current (PDU session) of UE#1 Network access identity (date network access identity, DNAI) and other information. It should be understood that request #3 can also carry subscription indication information for subscribing to the EES#1 change notification.
  • the SMF can also carry subscription indication information in this step. It should be understood that if the SMF carries the subscription request, the SMF may also carry the notification address (for example, notification URI) of the SMF itself, for the subsequent ECS#1 to send the EES#1 change notification to the SMF.
  • the network element of the 5GC core network may not be SMF, but other network elements such as AMF or PCF. Then, AMF or PCF can carry the notification address of AMF or PCF itself, which is used for subsequent ECS#1 Send EES#1 change notification to AMF or PCF.
  • the SMF can send the message #3 to the ECS#2 through the PCF, and the ECS#2 can also receive the message #3 through the PCF.
  • Step S208 ECS #1 receives message #3 and determines message #4.
  • ECS#1 receives message #3, and may determine that UE#1 wants to acquire information according to the first information.
  • the first information includes indication information, that is, indicating that UE#1 wants to acquire the identification information of EES
  • ECS#1 needs to determine the identification information of EES#1 (an example of the second information).
  • ECS#1 can use the following methods to determine the target EES:
  • ECS#1 determines EES#1 according to the location information of UE#1;
  • ECS#1 may determine the EES closest to the location of UE#1 as the target EES, ie, EES#1, according to the location of UE#1. If the service range of EES#1 includes area 1 and area 2, and the current location of UE#1 is in area 1, ECS#1 can determine that EES#1 is the EES serving UE#1.
  • ECS#1 can determine EES#1 according to the application identifier
  • ECS#1 may determine the EES with this service as the target EES, ie, EES#1, according to the application identification information requested by UE#1, for example, the information of the service to be connected by UE#1. If the applications managed by EES#1 (ie EAS) include application 1 and application 2, and the application identifier requested by UE#1 corresponds to application 1, ECS#1 can determine that EES#1 is the EES serving UE#1.
  • ECS#1 can determine EES#1 according to the load information.
  • ECS#1 may determine the EES with the smallest load or the smaller load as the target EES, that is, EES#1, according to the load information of each managed EES.
  • step S206 that is, ECS#1 authenticates and authorizes UE#1. If ECS#1 authenticates UE#1, message #3 may be carried in the authentication message, that is, step S207 may be included in S206.
  • Step S209 ECS#1 sends a message #4 to the SMF, the message #4 includes the first notification information and the second information, and the second information includes the information sent by the ECS#1 to the UE#1. It should be understood that ECS #1 may send message #4 to SMF through the PCF.
  • the message #4 carries the first notification address information, so that the subsequent SMF can determine which UE to send the second information to.
  • the second information may be identification information of EES#1.
  • the identification information of EES#1 may include the URI of EES#1 and/or the Internet Protocol IP address information of EES#1, and may also include the instance ID of EES#1.
  • ECS#1 needs to monitor the location change of UE#1 in order to dynamically select EES#1 that is most suitable for the current location of UE#1.
  • ECS#1 may send a subscription request to the SMF for subscribing to UE#1 session's user plane path management events. It should be understood that when the 5GC is the AMF, the ECS#1 may also send a subscription request to the AMF for subscribing to the location change event of the UE#1.
  • EES#1 may be one or more EESs.
  • the ECS#1 may send the identification information (an example of the second information) of the new (or changed) EES#1 to the SMF.
  • the identification information of the changed or new EES may be one or more of the following information: the identification information of the new EES, the identification information of the old EES, and the EES sent to UE#1 compared to the previous one.
  • the identification information transmits the identification information of the changed EES.
  • step S210 may be further included, where the SMF saves the received identification information of EES#1, which is used by the SMF to check whether the request is legal when the UE#1 requests the EES#1 information from the SMF subsequently.
  • the ECS#1 can send the message #4 to the SMF through the PCF, and the SMF can receive the message #4 through the PCF, which will not be repeated below.
  • Step S211 the SMF receives the message #4, and sends the second information to the UE #1 according to the first notification address information.
  • the SMF may send the second information to the UE through a session establishment reception message; or the SMF may send the second information to the UE through a session modification command message; or the SMF may send the second information to the UE through a non-access stratum container NAS Container message The UE sends the second information.
  • the SMF sends the identification information of EES#1 to UE#1 through a NAS message.
  • the SMF may send a message #5 to UE#1, and the message #5 includes the identification information of EES#1.
  • the message name of the message #5 may include, but is not limited to, a session establishment reception message, a session modification command message, or a non-access stratum container NAS Container message, and the like.
  • the SMF can send the identification information (an example of the second information) of the new EES#1 to the UE through a UCU command (UE configuration update command) message, a PDU session modification request message and other messages. #1. If the identification information of EES#1 is sent through a message related to the PDU session, the identification information of EES#1 may be carried in a protocol configuration option (protocol configuration option, PCO) and sent to UE#1.
  • PCO protocol configuration option
  • the core network may also send the identification information of the edge server to the base station first, and then the base station sends it to UE#1.
  • the UE sends relevant information through the core network element of the control plane, so that when the ECS is the core network element or the AF, the UE sends information to the ECS through the core network element.
  • the ECS sends the information to the ECS through the core network element.
  • the network element sends information to the UE to obtain edge services, and the changes to the existing mechanism (including the UE and the network element on the network side) are small.
  • the technical solution provided by the present application can realize the configuration of the address information of the ECS on the network side, improve the flexibility of the address configuration of the edge server, and ensure the service experience.
  • the embodiment of the present application can also realize that when the address information of the EES or the EAS changes, the UE can also obtain the updated address information of the EES or the EAS in real time.
  • FIG. 7 is a schematic flowchart of a method 300 for acquiring an edge service according to a second specific embodiment of the present application.
  • the 5GC core in this embodiment can also be other 5GC network elements such as AMF or PCF, that is to say, the following steps can also be performed by replacing the SMF with other 5GC network elements in this embodiment.
  • the method 300 shown in FIG. 7 may be performed by network elements such as AMF, SMF, NRF, and ECS in the system shown in FIG. 1 .
  • the method includes steps S301 to S313. This embodiment is described by taking UE#2 as an example, and each step is described in detail below.
  • Step S301 ECS#2 may register its own configuration information with the NRF.
  • the configuration information may include information such as the service scope of the ECS and the ID of the ECS.
  • each ECS has a corresponding service scope
  • the ECS in this embodiment may include multiple edge configuration servers, for example, ECS#1, ECS#2...ECS#n. That is, multiple ECSs can register their configuration files with the NRF, and in fact, multiple edge configuration servers can have their configuration files registered with the NRF.
  • Step S302 UE#2 may send third information to the SMF, where the third information includes the identification information that UE#1 requests to acquire the ECS.
  • UE#2 may send the third information to the SMF through a session establishment request message, a session modification request message, a non-access stratum container NAS Container message, and the like.
  • the first information sent by UE#1 to the SMF may include: service provisioning request (service provisioning request), service provisioning subscription request (service provisioning subscription request), service provisioning subscription update request (service provisioning subscription update request) ), service provisioning unsubscribe request.
  • service provisioning request service provisioning request
  • service provisioning subscription request service provisioning subscription request
  • service provisioning subscription update request service provisioning subscription update request
  • service provisioning request, service provisioning subscription request, service provisioning subscription update request, service provisioning unsubscribe request may be included in a session establishment request message or a session modification request message.
  • the third information may further include indication information, which is used to instruct UE#2 to obtain the information of the ECS; the third information may further include the default notification address of the ECS.
  • the third information may further include identification information of UE#2, and the identification information of UE#2 is used for the ECS to perform identity verification on UE#2.
  • the third information may also include the default notification address of the requesting ECS.
  • Step S303 after receiving the third information, the SMF determines that the third information needs to be sent to the ECS.
  • the SMF determines that UE#2 needs to send the information to the ECS based on the local configuration, the message name of the third information, or the subscription information.
  • the SME may first determine to which ECS the information (third information) should be sent, that is, the SMF may first obtain the identification information of the ECS (taking ECS #2 as an example).
  • Step S304 the SMF obtains the identification information of the ECS (taking ECS#2 as an example).
  • the SMF may send a message #6 to the NRF for requesting to query ECS information.
  • message #6 includes location information of UE#2.
  • Step S304b the NRF determines the identification information of ECS#2.
  • the NRF may determine the target ECS, ie, ECS#2, based on the current location information of UE#2 and the service range of ECS#2.
  • the service range of ECS#2 includes area 3 and area 4, and the current location of UE#2 is in area 4, the NRF may determine that ECS#2 is the ECS serving UE#2.
  • the location information of UE#2 may be reported by the SMF to the NRF, and the NFR may also send a request to the AMF to query the location information of UE#2.
  • the NRF may also send the default notification address of the ECS to the SMF in this step.
  • Step S304c the NRF may send a message #7 to the SMF, and the message #7 includes the identification information of the ECS #2. Specifically, if the NRF determines a suitable ECS#2, the NRF sends the ECS#2 identification information (for example, the URI of ECS#2 and/or the Internet Protocol IP address information of ECS#1, or ECS#2) to the SMF instance ID, etc.).
  • ECS#2 identification information for example, the URI of ECS#2 and/or the Internet Protocol IP address information of ECS#1, or ECS#2
  • step S305 may be further included, and the SMF may also save the received identification information of ECS#2, for subsequent SMF to check whether the request of the UE is legal after the SMF receives the third information of the UE.
  • Step S306 the SMF sends fourth information to UE#2, where the fourth information includes the identification information of ECS#2. Specifically, when multiple UEs send the fourth information to the SMF at the same time, the SMF may determine to which UE the fourth information should be sent by using the identification information of the UE or the context information of the UE.
  • the SMF sends the identification information of ECS#2 to UE#2 through a NAS message. It should be understood that if the third message sent by UE#2 in step S302 includes a request for the default notification address of ECS#2, the SMF may also send the default notification address of ECS#2 to UE#2 in this step. That is, the fourth information may include the default notification address of ECS#2.
  • the SMF element may send the fourth information to the UE through a session establishment reception message; alternatively, the SMF may send the fourth information to the UE through a session modification command message; or the SMF may send the fourth information through a non-access stratum container NAS Container message Send fourth information to the UE.
  • Step S307 the UE sends fifth information to the SMF, where the fifth information includes the information sent by UE#1 to the ECS.
  • the content of the fifth information in this embodiment may be the same as the content included in the first information in the method 100 or the method 200 .
  • the fifth information may include identification information of ECS#2, for example, the instance ID of ECS#2, etc.; the fifth information may also include indication information, which is used to indicate that UE#2 wants to obtain EES information; The fifth information may also include a message sent by UE#2 to ECS#2, for example, a service provisioning request or a service provisioning subscription request sent by UE#2 to ECS#2. The fifth information may also include the information required when UE#2 obtains the EES identification information. It should be understood that at this time, the SMF needs to generate a service provisioning request message or a service provisioning subscription request message according to the above-mentioned information, and then send it to ECS#2. The fifth information may further include the default notification address of ECS#2.
  • UE#2 sends fifth information, and the fifth information does not contain the identification information of ECS #2.
  • the SMF can use the previously saved identification information of ECS #2 (see step S305) Send a message to the corresponding ECS#2, thereby acquiring the identification information of the EES.
  • the fifth information may further include subscription indication information for subscribing to the EES change notification.
  • the fifth information may also be encapsulated in a NAS container, that is, the content of the fifth information is used as an outer NAS message. It should be understood that the request message between UE#2 and ECS#2 may also adopt other formats, which is not limited in this embodiment.
  • step S308 is further included, in which the SMF performs an authorization check to determine whether to forward the message that UE#2 sends to ECS#2, that is, the fifth information is forwarded to ECS#2. Specifically, a comparison can be made based on the identification information of ECS#2 stored in step S305. If the identification information of the ECS in the fifth information is inconsistent with the identification information of the stored ECS, the SMF determines that the request of UE#2 is illegal or invalid. , the SMF may refuse to send the fifth message to ECS#2.
  • the SMF can send the message #8 to the target ECS (for example, ECS #2), where the message #8 includes the fifth information and the first notification information, and the first notification information includes the SMF’s Notify address information and/or context information of the UE.
  • ECS ECS #2
  • Step S309 SMF may send message #8 to ECS #2, message #8 (an example of the first message) includes fifth information and first notification information, and the first notification information includes the notification address information of the SMF and/or the UE’s notification address. contextual information.
  • message #8 may be a service provisioning request message or a service provisioning subscription request message generated by SMF according to the fifth information, or may be the fifth information itself contains a NAS request message (service provisioning request message or service provisioning request message or service provisioning request message). provisioning subscription request message).
  • SMF can send message #8 to ECS #2 in the following ways:
  • Mode 1 SMF uses the default notification address of ECS#2 or sends message #8 to ECS#2.
  • the SMF sends the message to ECS#2 using ECS#2's default notification address. It should be understood that when the request #4 sent by UE#2 in step S302 includes the request for the default notification address of ECS#2, the SMF can also obtain the default notification address of ECS#2 in step S304. At this point, in this step, the SMF can use the default notification address of ECS#2 to send the message to ECS#2. That is, after receiving request #4, the SMF sends request #7 to the default notification address of the ECS to obtain the identification information of the EES.
  • the SMF can obtain the default notification address of ECS#2 according to other identification messages of ECS#2. For example, the SMF obtains the ECS from the configuration file of ECS#2 saved locally or from the configuration file of ECS#2 obtained from the NRF. The default notification address of #2.
  • Mode 2 The SMF invokes the service configuration request of ECS#2 to send message #8 to ECS#2.
  • the SMF invokes the service configuration request of ECS#2 to send message #8 to ECS#2.
  • ECS#2 defines the EES provisioning service
  • SMF calls the EES provisioning service, and sends the message (fifth information) sent by UE#2 to ECS#2 to ECS#2.
  • ECS#2 sends the message to ECS#2.
  • SMF sends available EES information.
  • the SMF may obtain the service address information of ECS#2 according to the identifier of ECS#2, for example, the SMF obtains the service address information of ECS#2 from the locally saved configuration file of ECS#2 or the configuration file of ECS#2 obtained from NRF Address information of ECS#2.
  • Method 3 Send message #8 using the service provisioning request message or the service provisioning subscription request message.
  • the SMF may generate a service provisioning subscriptionrequest message to send message #8.
  • the SMF may generate a service provisioning request message or generate a service provisioning subscription request message according to the information sent by UE#2, so as to send it to ECS#2.
  • the SMF can simulate the EEC to generate a service provisioning request message or a service provisioning subscription request message.
  • message #8 may further include location information of UE#2, so that ECS#2 can determine the target EES, ie, EES#2 according to the location information of UE#2, for example, the TAI and/or the TAI where UE#1 is located.
  • Cell ID or information such as DNAI corresponding to the current PDU session of UE#1.
  • Request #7 may also include application information.
  • the SMF may carry the context identification information of the UE#2 in the message #8, so that when the ECS#2 sends the EES change notification
  • the context identification ie, the SMF, can be used to associate the EES change notification with the UE#2, so that the EES change notification can be sent to the corresponding UE, ie, UE#2.
  • Step S310 ECS #2 receives message #8 and determines message #9.
  • ECS#2 receives message #8, and may determine that UE#2 wants to acquire information according to the fifth information.
  • the ECS#2 needs to determine the identification information of the EES#2.
  • ECS#2 can determine the target EES (eg, EES#2) in the following ways:
  • ECS#2 determines EES#2 according to the location information of UE#2;
  • ECS#2 may determine the EES closest to the location of UE#2 as the target EES, ie, EES#2, according to the location of UE#2. If the service range of EES#2 includes area 3 and area 4, and the current location of UE#2 is in area 3, ECS#2 can determine that EES#2 is the EES serving UE#2.
  • ECS#2 can determine EES#2 according to the application identifier
  • ECS#2 may determine the EES with this service as the target EES, that is, EES#2, according to the application identifier requested by UE#2, for example, information about the service to be connected by UE#2. If the applications managed by EES#2 (ie EAS) include application 3 and application 4, and the application identifier requested by UE#2 corresponds to application 4, ECS#2 can determine that EES#2 is the EES serving UE#2.
  • ECS#2 can determine EES#2 according to the load information.
  • ECS#2 may determine the EES with the smallest load or the smaller load as the target EES, that is, EES#2, according to the managed load information of each EES.
  • Step S311, ECS#2 sends a message #10 (an example of the second message) to the SMF, the message #10 includes the first notification information and the sixth information, and the sixth information includes the information sent by the ECS#2 to the UE#2.
  • the message #10 includes the first notification information and the sixth information
  • the sixth information includes the information sent by the ECS#2 to the UE#2.
  • the message #10 carries the first notification address information, so that the subsequent SMF can determine which UE to send the sixth information to.
  • the sixth information may be identification information of EES#2.
  • the identification information of EES#2 may include the URI of EES#2 and/or the Internet Protocol IP address information of EES#2, and may also include the instance ID of EES#2.
  • ECS #2 sends message #10 to SMF, which may be a NAS Container or a NAS message. If the message is an EES change notification message, the notification message also carries the context identifier of UE#2, and then the SMF can associate with UE#2 according to the context identifier of UE#2, thereby sending the notification message to UE#2.
  • SMF may be a NAS Container or a NAS message. If the message is an EES change notification message, the notification message also carries the context identifier of UE#2, and then the SMF can associate with UE#2 according to the context identifier of UE#2, thereby sending the notification message to UE#2.
  • the message #10 sent by ECS#2 to SMF may also be a service provisioning response.
  • SMF needs to obtain the identification information of EES#2 from the response message, and then SMF will use the identification information of EES#2
  • the information is sent to UE#2 through NAS messages.
  • ECS#2 needs to monitor the location change of UE#2.
  • ECS#2 sends a subscription request to the SMF for subscribing to UE#2 session user plane path management events. It should be understood that when the 5GC is the AMF, the ECS#2 may also send a subscription request to the AMF for subscribing to the location change event of the UE#2.
  • EES#2 may be one or more EESs.
  • the SMF can associate the context of UE#2 according to the context identifier of UE#2, so that the EES#2 change notification can be sent to UE#2.
  • step S312 may also be included, in which the SMF saves the received identification information of EES#2, which is used by the SMF to check whether the request is legal when the UE#2 requests the EES#2 information from the SMF subsequently.
  • Step S313 the SMF receives the message 10, and sends the sixth information to UE#2 according to the first notification address information. .
  • the SMF element may send the sixth information to the UE through a session establishment reception message; alternatively, the SMF may send the sixth information to the UE through a session modification command message; or the SMF may send the sixth information through a non-access stratum container NAS Container message The sixth information is sent to the UE.
  • the SMF can directly send the NAS container to UE#2; if in step S209c, the SMF receives a service provisioning response, the SMF can send the identifier of EES#2 The information is encapsulated in other NAS messages and sent to UE#2.
  • the core network may also send the identification information of the edge server to the base station first, and then the base station sends it to UE#2.
  • the UE sends relevant information through the core network element of the control plane, so that when the ECS is the core network element or the AF, the UE sends information to the ECS through the core network element.
  • the ECS sends the information to the ECS through the core network element.
  • the network element sends information to the UE to obtain edge services, and the changes to the existing mechanism (including the UE and the network element on the network side) are small.
  • the technical solution provided by the present application can realize the configuration of the address information of the ECS on the network side, improve the flexibility of the address configuration of the edge server, and ensure the service experience.
  • the embodiment of the present application can also realize that when the address information of the EES or the EAS changes, the UE can also obtain the updated address information of the EES or the EAS in real time.
  • the involved 5GC core network element can also be AMF, that is to say, it is also possible to replace SMF with AMF in the method of the previous embodiment.
  • This embodiment specifically describes the process by taking the 5GC core as AMF as an example. It should be understood that although AMF is not specifically described as an example in the methods described in the foregoing embodiments, the execution steps of AMF are basically similar to those of SMF, and the subtle differences in individual steps are only those skilled in the art according to existing It is within the protection scope of the present application that the technology can understand or know how to change.
  • FIG. 8 is a schematic flowchart of a method 400 for obtaining an edge service according to a third specific embodiment of the present application.
  • the method 400 shown in FIG. 8 may be performed by network elements such as AMF, PCF, NRF, and ECS in the system shown in FIG. 1 .
  • the method includes steps S401 to S411 .
  • This embodiment takes UE#3 as an example for description.
  • the method 400 in this embodiment is similar to the method 100 in FIG. 6 , and each step is described in detail below.
  • Step S401 the ECS may register its own configuration information with the NRF.
  • the configuration information may include information such as the service scope of the ECS and the ID of the ECS.
  • each ECS has a corresponding service scope, and the ECS in this embodiment may include multiple edge configuration servers, for example, ECS#1, ECS#2...ECS#n. That is, multiple ECSs can register configuration information with the NRF, and in fact, multiple edge configuration servers can register their configuration files with the NRF.
  • Step S402 UE#3 may send seventh information (an example of the first information) to the AMF, where the seventh information includes the information sent by UE#3 to the edge configuration server.
  • UE#3 may send the seventh information to the AMF through a session establishment request message, a session modification request message, a non-access stratum container NAS Container message, and the like.
  • the seventh information sent by UE#3 to the AMF may include: a service provisioning request (service provisioning request), a service configuration subscription request (service subscription request), a service configuration subscription update request (service subscription update request), Service configuration unsubscribe request (service unsubscribe request).
  • a service provisioning request service provisioning request
  • a service configuration subscription request service subscription request
  • a service configuration subscription update request service subscription update request
  • Service configuration unsubscribe request service unsubscribe request
  • a service provisioning request, a service configuration subscription request, a service configuration subscription update request, and a service configuration unsubscribe request may include in the session establishment request message or the session modification request message.
  • the seventh information may include indication information, where the indication information is used to instruct UE#3 to acquire the identification information of the EES.
  • the seventh information may also include application information, such as application ID (for example, information of the service to be connected by UE#3) or application client profile.
  • the seventh information may further include identification information of UE#3, and the identification information of UE#3 may be used for 5GC and/or ECS to authenticate UE#3.
  • Request #8 may also include the default notification address of the requesting ECS.
  • the seventh information may also carry a subscription indication for instructing the 5GC and/or ECS UE#1 to subscribe to the EES change notification.
  • the seventh information may also carry the default notification address of the ECS.
  • Step S403 after receiving the seventh information, the AMF determines that the seventh information needs to be sent to the ECS.
  • the AMF determines that UE#3 needs to send the information to the ECS based on the local configuration, the message name of the seventh information, or the subscription information.
  • the AMF may also check whether the UE#3 is allowed to send information to the edge server. That is to say, AMF can check whether the information sent by UE#3 to the edge configuration server is valid. For example, the AMF may determine whether UE#3 is allowed to send information to the edge server according to the subscription information of UE#3.
  • the AMF may first determine to which ECS the information (the seventh information) should be sent, that is, the AMF may first obtain the identification information of the ECS (taking ECS #3 as an example).
  • Step S404 the AMF obtains the identification information of the ECS (taking ECS#3 as an example).
  • the AMF may obtain the identification information of the ECS #3 from the NRF. Specifically, in step S404a, the AMF may send a message #11 to the NRF for requesting to query the information of the ECS.
  • Step S404b the NRF determines the identification information of ECS#3.
  • the NRF may determine a suitable ECS#3 based on the current location information of the UE#3 and the service range of the ECS#3. It should be understood that the location information of UE#3 may be reported by the AMF to the NRF, and the NFR may also send a request to the AMF to query the location information of UE#3.
  • the NRF may send a message #12 to the AMF, where the message #12 includes the identification information of the ECS #3. Specifically, if the NRF determines the target ECS, that is, ECS#3, the NRF sends the identification information of ECS#3 to the AMF (for example, the URI of ECS#3 and/or the Internet Protocol IP address information of ECS#1, which may also be instance ID of ECS#3, etc.).
  • the NRF may send a message #12 to the AMF, where the message #12 includes the identification information of the ECS #3.
  • the NRF determines the target ECS, that is, ECS#3
  • the NRF sends the identification information of ECS#3 to the AMF (for example, the URI of ECS#3 and/or the Internet Protocol IP address information of ECS#1, which may also be instance ID of ECS#3, etc.).
  • the AMF may also obtain the identification information of ECS#3 in other ways.
  • the seventh information includes the default notification address of the requesting ECS.
  • the AMF can obtain the default notification address of the ECS, thereby obtaining the ECS. identification information.
  • the seventh information does not include the default notification address of the ECS, but includes other identification information of the ECS, for example, the Instance ID of the ECS.
  • the AMF can obtain the ECS# according to other identifiers of the ECS. 3 notification address, for example, the AMF obtains the notification address of ECS#3 from the ECS configuration file saved locally.
  • step S405 may also be included, and the AMF may also save the received identification information of ECS#3 for subsequent AMF to check whether the request of the UE is legal after receiving the seventh information of the UE.
  • step S406 may also be included, where ECS#3 authenticates and authorizes UE#3.
  • UE#3 can be authenticated and authorized in a manner similar to PDU session authentication in the prior art, that is, AMF provides a delivery service for messages related to authentication or authorization between UE#3 and ECS#3. For details, refer to the prior art. The method for third-party authentication of the PDU session is not repeated here.
  • the AMF can send the message #13 to the target ECS (for example, ECS #3), where the message #13 includes the seventh information and the first notification information, and the first notification information includes the AMF’s Notify address information and/or context information of the UE.
  • ECS target ECS
  • the message #13 includes the seventh information and the first notification information
  • the first notification information includes the AMF’s Notify address information and/or context information of the UE.
  • the AMF may send a message #13 to the ECS#3, the message #13 includes seventh information and first notification information, and the first notification information includes the notification address information of the AMF and/or the context information of the UE.
  • the notification address information of the AMF may be, for example, the URI of the AMF.
  • the AMF may forward the received seventh information to ECS#3 and carry the first notification information.
  • the first notification information may be used to determine the address information of the core network element and the UE information.
  • ECS#3 may determine which AMF or which UE to send the response message to according to the first notification address information.
  • the AMF may invoke the service provisioning request of the ECS, for example, the service provisioning request message sent by the AMF to the ECS, the message includes: seventh information and first notification information.
  • the content of the seventh information may be the content of the seventh information in step S402.
  • message #13 may include the identification information of UE #3 and application information.
  • Message #13 may also include location information of UE#3, which may be used by ECS#3 to determine the target EES, ie, EES#3.
  • the location information of UE#3, for example, the TAI and/or Cell ID where UE#3 is located, or information such as DNAI corresponding to the current PDU session of UE#3.
  • message #13 may also carry subscription indication information for subscribing to the EES change notification. For example, if UE#3 carries subscription indication in step S302, the AMF may also carry subscription indication information in this step. If the change notification of EES#3 is subscribed, the message can also carry the context identifier of UE#3. ECS#3 can use the context identifier when sending the EES change notification, so that the AMF and PCF can associate the EES change notification with the EES change notification. UE#3 associates so that an EES change notification can be sent to UE#3.
  • the AMF can send the message #13 to the ECS#3 through the PCF and/or the SMF, and the ECS#3 can also receive the message #13 through the PCF and/or the SMF.
  • Step S408, ECS #3 receives message #13 and determines message #14.
  • ECS#3 receives message #13, and may determine, according to the seventh information, that UE#3 wants to acquire the information.
  • the ECS#3 needs to determine the identification message of the EES#3.
  • ECS#3 can use the following methods to determine the target EES (for example, EES#3):
  • ECS#3 determines EES#3 according to the location information of UE#3;
  • ECS#3 may determine the EES closest to the location of UE#3 as the target EES, ie, EES#3, according to the location of UE#3. If the service range of EES#3 includes area 5 and area 6, and the current location of UE#3 is in area 5, ECS#3 can determine that EES#3 is the EES serving UE#3.
  • ECS#3 can determine EES#3 according to the application identifier
  • ECS#3 may determine the EES with this service as the target EES, ie, EES#3, according to the application identifier of UE#3, for example, information about the service to be connected by UE#3. If the applications managed by EES#3 (ie EAS) include application 5 and application 6, and the application identifier requested by UE#1 corresponds to application 6, ECS#3 can determine that EES#3 is the EES serving UE#3.
  • ECS#3 can determine EES#3 according to the load information.
  • ECS#3 may determine the EES with the smallest load or the smaller load as the target EES, that is, EES#3, according to the load information of each managed EES.
  • step S206 that is, ECS#3 authenticates and authorizes UE#3. If ECS#3 authenticates UE#3, message #13 may be carried in the authentication message, that is, step S307 may be included in S406.
  • Step S409 ECS#3 sends a message #14 to the AMF, the message #14 includes the first notification information and the eighth information, and the eighth information includes the information sent by the ECS#1 to the UE#1.
  • the message #14 carries the first notification address information, so that the subsequent AMF can determine which UE to send the second information to.
  • the eighth information may be identification information of EES#3.
  • the identification information of EES#3 may include the URI of EES#3 or the instance ID of EES#3.
  • ECS#3 needs to monitor the location change of UE#3 in order to dynamically select the EES#3 most suitable for the current location of UE#3.
  • the ECS#3 sends a subscription request to the AMF for subscribing to the UE#3 session's user plane path management events, ie, sends a subscription request to the AMF for subscribing to the UE#3 location change event.
  • EES#3 may be one or more EESs.
  • the ECS#3 may transmit the identification information (an example of the second information) of the new (or changed) EES#3 to the AMF.
  • the identification information of the changed or new EES may be one or more of the following information: the identification information of the new EES, the identification information of the old EES, and the EES sent to UE#3 compared to the previous one.
  • the identification information transmits the identification information of the changed EES.
  • step S410 may also be included, in which the AMF saves the received EES#3 identification information, which is used by the AMF to check whether the request is legal when the UE#3 requests the AMF for the EES#3 information subsequently.
  • Step S411 the AMF receives the message #14, and sends the eighth information to the UE#3 according to the first notification address information.
  • the AMF may send the second information to the UE through a session establishment reception message; alternatively, the AMF may send the second information to the UE through a session modification command message; or the AMF may send the second information to the UE through a non-access stratum container NAS Container message The UE sends the second information.
  • the UE sends relevant information through the core network element of the control plane, so that when the ECS is the core network element or the AF, the UE sends information to the ECS through the core network element, and the ECS sends the information to the ECS through the core network element.
  • the technical solution provided by the present application can realize the configuration of the address information of the ECS on the network side, improve the flexibility of the address configuration of the edge server, and ensure the service experience.
  • the embodiment of the present application can also realize that when the address information of the EES or the EAS changes, the UE can also obtain the updated address information of the EES or the EAS in real time.
  • the application scenario of this embodiment may be performed after the previous embodiment, that is, after the UE obtains the identification information of the EES, the UE further sends a request to the target EES (taking EES#4 as an example) to request the identification information of the application server EAS .
  • the method for the UE to obtain the EES identification information may adopt the method of the present application or the method in the prior art, and the method for the UE to obtain the EES identification information is not limited in this embodiment.
  • FIG. 9 is a schematic flowchart of a method 500 for obtaining an edge service according to a fourth specific embodiment of the present application.
  • the 5GC core in this embodiment may also be an AMF, that is to say, the following steps may also be performed by replacing the SMF with AMF in this embodiment, which will not be repeated.
  • the method 500 shown in FIG. 9 may be performed by network elements such as AMF, SMF, NRF, and EES in the system shown in FIG. 1 . As shown in FIG. 9, the method includes steps S501 to S507, and each step is described in detail below.
  • Step S501 UE#4 obtains the identification information of EES#4.
  • the method for UE#4 to obtain the identification information of EES#4 may adopt the method of the present application or the method according to the prior art.
  • the method for UE#4 to obtain the address information of EES#4 Does not make any restrictions.
  • Step S502 UE#4 sends ninth information to the SMF, where the ninth information includes the information sent by UE#4 to the edge enabling server.
  • UE#4 may send the ninth information to the AMF through a session establishment request message, a session modification request message, a non-access stratum container NAS Container message, and the like.
  • the ninth information may include indication information, and the indication information is used to indicate that UE#4 wants to obtain the identification information of EAS; the ninth information may also include EES#4 identification information; the ninth information may also include application information, For example, at least one of the identification of the application to be discovered, the similar applications to be discovered, the configuration file of the application client, and the like.
  • the ninth information also includes subscription indication information, which is used to instruct the SMF or EES#4 to subscribe UE#4 for the EAS change notification.
  • the ninth information may also include identification information of EES#4.
  • UE#4 may also encapsulate the information to be sent to EES#4 into the NAS container, so that the SMF forwards the information in the NAS container to EES#4.
  • Step S503 the SMF receives the ninth information, and determines that the ninth information needs to be sent to the EES.
  • the SMF determines that UE#4 needs to send the information to the EES based on the local configuration or the message name of the ninth information or the subscription information.
  • step S504 is also included, in which the SMF performs an authorization check.
  • a comparison can be made based on the historically stored identification information of EES#4. If the identification information of EES#4 in the ninth information is inconsistent with the stored identification information of EES#4, the SMF determines that the request of UE#4 is illegal or invalid, the SMF may refuse to send the ninth message to EES#4.
  • the SMF may first determine to which EES the information (the ninth information) should be sent, that is, the SMF may first obtain the identification information of the EES (taking ECS#3 as an example).
  • Step S505 the SMF sends a message #15 to the EES#4, the message #15 includes ninth information and first notification information, and the first notification information includes the notification address information of the SMF and/or the context information of the UE.
  • the notification address information of the SMF may be, for example, the URI of the SMF.
  • the SMF may forward the received ninth information to EES#4 and carry the first notification information.
  • the first notification information may be used to determine the address information of the core network element and the UE information.
  • EES#4 may determine which SMF or which UE to send the response message to according to the first notification address information.
  • the SMF may send the EAS discovery request to EES#4 based on the identification information of EES#4 received in step S502;
  • the identification information of EES#4 the SMF can also send the EAS discovery request to EES#4 according to the identification information of EES#4 stored in history.
  • SMF sends message #15 to EES#4, and the sending of message #15 can also be done in the following ways:
  • Mode 1 SMF sends message #15 to EES#4 using the default notification address of EES#4.
  • the SMF sends the message to EES#4 using EES#4's default notification address. It should be understood that when the ninth information sent by UE#4 in step S502 includes a request for the default notification address of EES#4, the SMF can also obtain the default notification address of EES#4. At this point, in this step, the SMF can send the message to ECS#4 using the default notification address of ECS#4.
  • step S502 when the ninth information sent by UE#4 in step S502 does not include the default notification address of EES#4, but includes other identification information of EES#4, for example, the instance ID of EES#4 .
  • SMF can obtain the notification address of EES#4 according to other identification messages of EES#4. For example, SMF obtains EES#4 from the configuration file of EES#4 saved locally or from the configuration file of EES#4 obtained from NRF , SMF can send the message to ECS#4 using the notification address of ECS#4.
  • Mode 2 The SMF invokes the service of EES#4 to send message #14 to EES#4.
  • the SMF invokes the services of EES#4 to send message #14 to EES#4.
  • EES#4 defines an application discovery service (EAS discovery service), and the SMF invokes the application discovery service to send the message sent by UE#4 to EES#4 to EES#4.
  • EAS discovery service application discovery service
  • the SMF can obtain the service address information of the EES#4 according to the identifier of the EES#4, for example, the SMF obtains from the configuration file of the EES#4 saved locally or the configuration file of the ECS#2 obtained from the NRF Address information of EES#4.
  • Method 3 Send message #14 by using the service provisioning request message or the service provisioning subscription request message.
  • the ninth information may further include identification information of EES#4, and the SMF sends the message to EES#4 by using the identification information of EES#4.
  • the SMF may generate an EAS discovery request message to send message #15.
  • the SMF may generate an EAS discovery request message based on the information sent by UE#2 to send it to EES#4. At this point, SMF can simulate EEC to generate EAS discoveryrequest message.
  • message #15 may further include location information of UE#4, so that EES determines the target EAS, ie, EAS#1, according to the location information of UE#4.
  • the location information of UE#4 may include, for example, the TAI and/or Cell ID where UE#4 is located, or information such as DNAI corresponding to UE#4 currently (in the PDU session).
  • Message #15 may also include application information.
  • step S502 the UE sends the SMF the change notification of the EAS subscription in the ninth information
  • the SMF may also carry the subscription request, and if the SMF carries the subscription request, the SMF may also carry the notification address, Used for EES#4 to send EAS change notifications.
  • Step S506 EES#4 receives message #15 and determines message #16.
  • EES#4 receives message #15, and may determine that UE#4 wants to acquire information according to the ninth information.
  • the ninth information contains indication information, that is, indicating that UE#4 is to acquire the identification information of EAS
  • EES#4 needs to determine the identification message of EAS#1.
  • EES#4 can determine the target EAS (for example, EAS#1) in the following ways:
  • EES#4 determines EAS#1 according to the location information of UE#4;
  • EES#4 may determine the EAS closest to the location of UE#4 as the target EAS, ie, EAS#1, according to the location of UE#4. If the service range of EAS#1 includes area 7 and area 8, and the current location of UE#4 is in area 7, EES#4 can determine that EAS#1 is the EAS serving UE#4.
  • EES#4 can determine EAS#1 according to the application identifier
  • EES#4 may determine the EAS with this service as the target EAS, ie, EAS#1, according to the application identifier requested by UE#4, for example, the information of the service to be connected by UE#4. If the applications managed by EAS#1 include application 7 and application 8, and the application identifier requested by UE#4 corresponds to application 8, EES#4 can determine that EAS#1 is the EAS serving UE#4.
  • EES#4 can determine EAS#1 according to the load information.
  • EES#4 may determine the EAS with the smallest load or the smaller load as the target EAS, that is, EAS#1, according to the load information of each managed EAS.
  • Step S507 EES#4 sends response #16 to SMF, message #16 includes the first notification information and tenth information, and the tenth information includes the information sent by EES#1 to UE#4.
  • the message #16 carries the first notification address information, so that the subsequent AMF can determine which UE to send the tenth information to.
  • the tenth information may be identification information of EAS#1.
  • the identification information of EAS#1 may include the URI of EAS#1 or the instance ID of EAS#1.
  • EES#4 needs to monitor the location change of UE#4 in order to dynamically select EAS#1 that is most suitable for the current location of UE#4.
  • EES#4 sends a subscription request to the SMF for subscribing to UE#4 session user plane path management events. It should be understood that when the 5GC is the AMF, the EES#4 may also send a subscription request to the AMF for subscribing to the location change event of the UE#4.
  • EES#4 can be based on the new location of UE#4 or new DNAI to determine new EAS#1.
  • EAS#1 may be one or more EASs.
  • the EES#4 may transmit the identification information (an example of the second information) of the new (or changed) EAS#1 to the AMF.
  • the identification information of the changed or new EAS may be one or more of the following information: the identification information of the new EAS, the identification information of the old EAS, and the EAS sent to UE#4 compared to the previous one.
  • the identification information transmits the identification information of the changed EAS.
  • Step S507 the SMF receives the message #16, and sends the tenth message to the EAS#1 according to the first notification address information.
  • the SMF may send the tenth information to the UE through a session establishment reception message; alternatively, the SMF may send the tenth information to the UE through a session modification command message; or the SMF may send the tenth information to the UE through a non-access stratum container NAS Container message The UE sends tenth information.
  • the 5GC core may also be AMF, that is to say, it is also possible to replace SMF with AMF in the method of this embodiment.
  • AMF is not specifically used as an example in the method described in this embodiment, the execution steps of AMF are basically similar to those of SMF, and the subtle differences in individual steps are as long as those in the art are based on existing It is within the protection scope of the present application that the technology can understand or know how to change.
  • the UE sends relevant information through the core network element of the control plane, so that when the ECS is the core network element or the AF, the UE sends information to the ECS through the core network element to obtain edge services.
  • the ECS sends information to the UE through the core network element, and the changes to the existing mechanism (including the UE and the network element on the network side) are small.
  • the technical solution provided by the present application can realize the configuration of the address information of the ECS on the network side, improve the flexibility of the address configuration of the edge server, and ensure the service experience.
  • the embodiment of the present application can also realize that when the address information of the EES or the EAS changes, the UE can also obtain the updated address information of the EES or the EAS in real time.
  • the application scenario of this embodiment may be that after obtaining the identification information of the target ECS, the UE sends a subscription request to the target ECS, where the subscription request is used to subscribe to the EES change notification.
  • the subscription notification message sent by the ECS to the UE may be a NAS message.
  • the method for the UE to obtain the ECS identification information may adopt the method of the present application or the method in the prior art, and the method for the UE to obtain the ECS identification information is not limited in this embodiment.
  • the method for the UE to send the subscription request to the target ECS may adopt the method in the prior art, or may adopt the method in the implementation of this application. That is, the subscription request may be sent through the HTTP protocol or the NAS protocol may be used to send the subscription request. In this embodiment, the method for sending the subscription request from the UE to the ECS is not limited in any way.
  • the UE may send a subscription request to the core network or to an edge server (taking ECS as an example) when the location changes, and the UE may also include a subscription request in the information when sending information to the core network.
  • FIG. 10 is a schematic flowchart of a method 600 for obtaining an edge service provided by an embodiment of the present application.
  • UE#5 is taken as an example, UE#5 sends a subscription EES address change request to a 5G core network (5G Core, 5GC).
  • 5G Core 5G Core
  • the corresponding ECS#5 detects that the address of the EES currently serving UE#5 (taking EES#5 as an example) has changed, it sends a subscription change notification to the 5GC, and then the 5GC sends the new EES#5 identification information to UE#5.
  • EES#5 in the embodiment of the present application may also refer to the changed EES, which will not be repeated below.
  • the UE obtains the change information of the EES as an example, and the process and steps for the UE to obtain the address change notification of the EAS are basically similar to those in this embodiment. It is enough to replace it with the change of EAS, and I will not repeat it.
  • the UE may also obtain the EES change notification according to the methods of this embodiment.
  • the 5GC core in this embodiment may be SMF, AMF, PCF or NEF.
  • the method 600 shown in FIG. 10 may be performed by network elements such as AMF, SMF, PCF, NEF, and ECS in the system shown in FIG. 1 .
  • the method includes steps S601 to S605, and each step is described in detail below.
  • step S601 may be included, where UE#5 acquires the identification information of ECS#5.
  • the identification information of ECS#5 may include the URI of ECS#5 or the Instance ID of ECS#5; and may also include address information of ECS#5.
  • step S602 may also be included, where UE#5 obtains the notification URI of the AMF, SMF or PCF.
  • the AMF or SMF sends the notification URI of the AMF or SMF or PCF to UE#5 in a message such as a session establishment response or a session modification request.
  • the notification URI of AMF or SMF or PCF and the identification information of ECS#5 may be sent to UE#5 in the same message.
  • UE#5 can also obtain a token for subsequent SMF verification.
  • Step S603, UE#5 sends an EES change subscription request to ECS#5.
  • UE#5 may send an EES change subscription request to ECS#5 through the core network element.
  • UE#5 may also directly send an EES change subscription request to ECS#5.
  • the change subscription request message may also be called service provisioning subscribe request, which is used to subscribe ECS#5 for the change information of the EES.
  • the request message may include indication information, which is used to instruct ECS#5 to send a notification to UE#5 through 5GC; the request message may also include the notification URI of AMF, SMF or PCF, and then ECS#5 detects the address information of EES When there is a change, ECS#5 sends a notification to SMF or AMF or PCF through the notification URI.
  • the request message may also include the IP address of UE#5.
  • the request message may also include token information.
  • AMF or SMF or PCF encapsulates its own notification URI after receiving the request message.
  • the UE includes the notification URI of AMF, SMF or PCF when sending the request.
  • Step S604, ECS#5 detects an event.
  • event here may be an EES#5 address change event, which satisfies the trigger condition for EES#5 update.
  • ECS#5 In order to dynamically select the EES most suitable for the current location of UE#5, ECS#5 needs to monitor the location change of UE#5.
  • ECS#5 (possibly via PCF) sends a subscription request to SMF for subscribing to UE#5 session's user plane path management events. It should be understood that ECS#5 may also send a subscription request to AMF for subscribing to UE#5's location change event.
  • EES#5 may be one or more EESs.
  • Step S605 ECS#5 sends the changed information of EES#5 to UE#5.
  • the address information of the changed EES#5 may be included in the service provisioning notification message.
  • ECS#5 may also send the token information received in step S503.
  • ECS#5 sends the changed EES#5 information (such as new EES#5 information, old EES#5 information, etc.) to UE#5, including the following three ways.
  • Step S605a1 ECS#5 determines the PCF serving UE#5 according to the IP address of UE#5, and ECS#5 sends the changed information of EES#5 to the PCF.
  • the ECS#5 may be sent to the PCF through the NEF; in another implementation manner, the ECS#5 may directly send the changed identification information of the EES#5 to the PCF. In another implementation, ECS#5 may be sent to the PCF via the NEF.
  • Step S605b1 the PCF may determine the SMF serving the UE#5 through the IP address, and the PCF sends the changed identification information of the EES#5 to the SMF.
  • Step S605c1 the SMF then sends the changed identification information of EES#5 to UE#5; or, the PCF sends the changed identification information of EES#5 to UE#5 through AMF. Sent to UE#5.
  • step S605a2 if the request message in step S503 also includes an AMF/SMF/PCF notification URI, ECS#5 can send the changed identification information of EES#5 to AMF/SMF/PCF based on the notification URI. Wherein, the changed identification information of EES#5 may be included in the service provisioning notification message.
  • Step S605b2 the AMF/SMF/PCF may associate with UE#5 according to the notification URI, and then send the changed identification information of EES#5 to UE#5.
  • the identification information of the changed EES#5 may be sent by the SMF to the UE#5 through messages such as PDU session establishment accept or PDU session modification request.
  • the SMF can also calculate a check code according to the notification URI and the ECS#5 address, and then the SMF checks whether it is legal. If it is not legal, the SMF refuses to send the changed identification information of the EES#5 to the UE# 5.
  • Step S605a3 ECS#5 invokes the service of NEF, and sends the updated identification information of EES#5 to NEF, and also includes the identification of UE#5 (for example, UE#5's Internet Protocol (IP) address or general generic public subscription identifier, GPSI)).
  • IP Internet Protocol
  • GPSI general generic public subscription identifier
  • Step S605b3 in an implementation manner, if the identifier of UE#5 is GPSI, the NEF can determine the PCF serving UE#5 according to the GPSI. Specifically, the NEF can notify the PCF of the new identifier information of EES#5 through UDR. In another implementation manner, if the identifier of the UE is an IP address, the NEF determines the PCF serving UE#5, which is the same as the first manner, and will not be repeated here.
  • Step S605c3 the PCF (through the AMF) sends the identification information of the new EES#5 to the UE#5.
  • the PCF sends the changed identification information of EES#5 to the UE,
  • ECS#5 may determine to send the changed identification information of EES#5 to 5GC based on the indication information in step S603, the indication information is used to instruct ECS#5 to send a notification to UE#5 through 5GC
  • the network element (NEF or PCF or SMF or AMF mentioned in the above manner) is then sent to UE#5 by the 5GC network element.
  • the UE when the identification information of the EES or EAS changes, the UE can also obtain the updated identification information of the EES or EAS in real time, which improves the flexibility of the UE to send information to the edge server and ensures the business experience.
  • FIG. 11 is a schematic flowchart of a method 700 for obtaining an edge server according to the sixth specific embodiment provided in this application.
  • the method 700 shown in FIG. 11 may be performed by network elements such as AMF, SMF, NEF, PCF, UDR, and ECS in the system shown in FIG. 1 .
  • the method includes steps S701 to S710. This embodiment is described by taking UE#6 as an example, and each step is described in detail below.
  • step 701 the ECS provides its own configuration information to the 5GC (eg PCF and/or SMF).
  • the 5GC eg PCF and/or SMF.
  • the configuration information may be sent to the NEF through request #1, for example, request #1 may be a Nnef_TrafficInfluence_Create/udpate request.
  • the configuration information may include one or more of the following information: service scope of ECS, data network name (DNN), single network slice selection assistance information (single network slice selection assistance information, S-NSSAI), DNAI and addresses of ECS.
  • DNN data network name
  • S-NSSAI single network slice selection assistance information
  • DNAI addresses of ECS.
  • each ECS may have a corresponding service scope, and this embodiment may include multiple edge configuration servers, for example, ECS#1, ECS#2...ECS#n.
  • the ECS may also subscribe the notification message to the core network, for example, the ECS provides the notification address to the core network, so that the core network sends the notification message to the ECS.
  • the configuration information of the ECS may also be pre-configured in the 5GC network element (for example, in PCF, SMF, or UDR), which is not limited.
  • Step 702 the NEF saves the configuration information of the ECS to the UDR.
  • step 703 may also be included, in which the UDR sends the ECS configuration information to the PCF.
  • the PCF may subscribe the ECS change information to the UDR in advance.
  • the UDR receives or saves the new ECS configuration information
  • the UDR will notify the PCF and/or the SMF of the new ECS configuration information,
  • the configuration information of the new ECS is saved or configured on the PCF and/or the SMF.
  • the UDR when the UDR receives the new ECS configuration information, the UDR actively notifies the PCF of the ECS configuration information.
  • the PCF may send the ECS configuration information to the SMF.
  • the ECS configuration information can be configured on the PCF, or on the SMF, or on both the SMF and the PCF, which is not limited in this application.
  • the ECS subscribes the notification message to the core network, the PCF can determine which SMF to send the subscription request to according to the service scope of the DNN, S-NSSAI, DNA or ECS, so that the SMF can directly send the subscription request to the UE upon receiving the information from the UE.
  • the ECS sends the notification, or sends the notification to the ECS through the PCF.
  • Step S704 UE#6 sends eleventh information to the 5GC (taking SMF as an example), where the eleventh information includes the information sent by UE#6 to the edge configuration server.
  • UE#6 may send the eleventh information to the SMF through a session establishment request message, a session modification request message, a non-access stratum container NAS Container message, and the like.
  • the eleventh information sent by UE#6 to the SMF may include: service provisioning request, service provisioning subscription request, service provisioning subscription update request request), service provisioning unsubscribe request.
  • service provisioning request, service provisioning subscription request, service provisioning subscription update request, service provisioning unsubscribe request may be included in a session establishment request message or a session modification request message.
  • service provisioning request can be used as a new NAS message.
  • the eleventh information may further include indication information, where the indication information is used to instruct UE#6 to acquire the identification information of the EES.
  • the eleventh information may further include application information, such as application ID (for example, information of the service to be connected by UE#1) or application client profile.
  • the eleventh information may further include identification information of UE#6, and the identification information of UE#6 may be used for 5GC and/or ECS to authenticate UE#6.
  • the eleventh information may further include location information of UE#6, and the location information of UE#1 may be determined for the ECS and EES determined by the network side to serve the UE.
  • the location information of UE#6 may include: tracking area identity (TAI) and/or cell identity (cell ID) where UE#6 is located, or data corresponding to UE#6 currently (in the PDU session) Network access identity (date network access identity, DNAI) and other information.
  • TAI tracking area identity
  • cell ID cell ID
  • DNAI network access identity
  • the eleventh information can also carry a subscription indication, which is used to instruct the 5GC and/or ECS UE#6 to subscribe to the EES change notification, that is, when the available EES information changes, the changed EES information is notified to UE#1.
  • the changed EES information may be one or more of the following information: new EES information, old EES information, and changed EES information sent compared to the EES information previously sent to UE#1.
  • the subscription indication information may be used to indicate the change information of the edge server that can serve the UE when the location of the UE changes. That is to say, the subscription indication information can enable the UE to dynamically obtain the current real-time updated information of the server that can serve the UE.
  • the subscription indication information may be embodied by a service provisioning request or a service subscription update request.
  • the eleventh information may further include DNN, S-NSSAI and other information.
  • Step S705 the SMF receives the eleventh information, and determines that the eleventh information needs to be sent to the ECS.
  • the SMF may determine that it needs to send the information to the ECS based on the local configuration, the message name of the eleventh information, or the subscription information.
  • the SMF may first determine to which ECS the information (the first information) should be sent, that is, the SMF may first obtain the identification information of the ECS (taking ECS #1 as an example).
  • Step S706 the SMF obtains the identification information of the ECS (taking ECS#6 as an example).
  • the SMF can determine an ECS according to the location of the UE and the service range of the ECS, for example, ECS #6 .
  • the SMF may send the eleventh information to the PCF, and when the PCF is configured with the ECS configuration information, the PCF may determine an ECS according to the UE location and the service range of the ECS, for example, ECS# 6.
  • the SMF or the PCF or the AMF can determine the target ECS, for example, ECS#6.
  • the SMF may send a message #17 to the ECS #6, and the message #17 includes eleventh information.
  • the PCF may send message #17 to ECS#6 in this step.
  • the SMF can also send the message #17 to the ECS #6 through the PCF.
  • Message #17 may also include the UE's IP address, DNN, and S-NSSAI.
  • the message may be an Npcf_PolicyAuthorization_Notify request.
  • Step S708, ECS #6 receives message #17 and determines message #18.
  • ECS#6 receives message #17, and may determine that UE#6 wants to obtain information according to the eleventh information.
  • the eleventh information contains indication information, that is, indicating that UE#6 is to acquire the identification information of EES
  • ECS#6 needs to determine the identification information of EES#6.
  • the identification message of the ECS to determine the EES#6 reference may be made to the method 200, the method 300 or the method 400, which will not be repeated.
  • the ECS may also establish an AF session of the application function network element according to the IP address, DNN, and S-NSSAI of the UE, and the AF session is bound to the PDU session corresponding to the IP address and/or DNN and S-NSSAI of the UE.
  • the ECS may send an Npcf_PolicyAuthorization_Create message to the PCF in order to establish the AF session.
  • Step S709 ECS#6 sends a message #18 to the PCF, the message #18 includes twelfth information, and the twelfth information includes the information sent by ECS#6 to UE#6.
  • the twelfth information may be the identification information of EES#6.
  • the identification information of EES#6 may include URI, FQDN and/or Internet Protocol IP address information of EES#6, and may also include instance ID of EES#6.
  • ECS#6 may send an Npcf_PolicyAuthorization_Create request message to the PCF, where the message includes the twelfth information.
  • ECS#6 may send message #18 to PCF through the AF session established in step S708, for example, ECS sends Npcf_PolicyAuthorization_update message to PCF, and the message includes the twelfth information.
  • ECS#6 needs to monitor the location change or session path change of UE#6.
  • ECS#6 sends a subscription request to the SMF for subscribing to UE#6 session user plane path management events.
  • the ECS#6 may also send a subscription request to the AMF for subscribing to the location change event of the UE#6.
  • EES#6 may be one or more EESs.
  • Step S710 the PCF receives the message #18, and sends the twelfth information to the UE#6.
  • step S708 the ECS establishes an AF session according to the UE's IP address, DNN, and S-NSSAI, and the AF session is bound to the UE's IP address and/or the PDU session corresponding to the DNN and S-NSSAI. , therefore, in this step, the PCF can determine which UE to send the twelfth information to.
  • the PCF can also send the twelfth information to the UE#6 through the SMF.
  • the method 700 in this embodiment may also be used in combination with the steps of the methods in the foregoing embodiments.
  • the method 700 in this embodiment may also enable the UE to obtain the identification information of the EAS.
  • the UE sends relevant information through the core network element of the control plane, so that when the ECS is the core network element or the AF, the UE sends information to the ECS through the core network element to obtain edge services.
  • the ECS sends information to the UE through the core network element, and the changes to the existing mechanism (including the UE and the network element on the network side) are small.
  • the technical solution provided by the present application can realize the configuration of the address information of the ECS on the network side, improve the flexibility of the address configuration of the edge server, and ensure the service experience.
  • the embodiment of the present application can also realize that when the address information of the EES or the EAS changes, the UE can also obtain the updated address information of the EES or the EAS in real time.
  • the network elements of the first control plane core network in the embodiments of the present application only take SMF, AMF, PCF, and related network elements involved as examples, and should not constitute any limitation to the present application.
  • This application does not exclude the possibility of using one or more of them to achieve the same or similar functions in other application scenarios, nor does this application exclude the use of one or more other network elements to achieve the same or similar functions in other application scenarios. possible.
  • the communication method provided by the embodiment of the present application.
  • the following describes the apparatus for acquiring edge services provided by the embodiments of the present application with reference to FIG. 12 to FIG. 14 . It should be understood that the description of the apparatus embodiment corresponds to the description of the method embodiment. Therefore, for the content not described in detail, reference may be made to the above method embodiment, which is not repeated here for brevity.
  • each network element includes corresponding hardware structures and/or software modules for performing each function.
  • each network element includes corresponding hardware structures and/or software modules for performing each function.
  • the present application can be implemented in hardware or a combination of hardware and computer software with the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein. Whether a function is performed by hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of this application.
  • the transmitting-end device or the receiving-end device may be divided into functional modules according to the foregoing method examples.
  • each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. middle.
  • the above-mentioned integrated modules can be implemented in the form of hardware, and can also be implemented in the form of software function modules. It should be noted that, the division of modules in the embodiments of the present application is schematic, and is only a logical function division, and there may be other division manners in actual implementation. The following description will be given by taking as an example that each function module is divided corresponding to each function.
  • FIG. 12 is a schematic block diagram of an apparatus 100 for obtaining an edge service provided by an embodiment of the present application.
  • the apparatus 100 may include: a transceiver unit 110 and a processing unit 120 .
  • the apparatus 100 may be the first control plane core network element in the above method embodiment, or may be a network element for implementing the first control plane core network element in the above method embodiment functional chip.
  • the apparatus 100 may correspond to the first control plane core network element in the method 100 according to the embodiment of the present application, the SMF network element in the method 200, the SMF network element in the method 300, and the AMF network in the method 400.
  • element, the SMF network element in the method 500, the SMF network element in the method 600, and the SMF network element in the method 700 the apparatus 100 may include a first control plane core network network element for performing the method 100 in FIG. unit of the method of FIG. 6 , unit of the method performed by SMF of method 200 in FIG. 6 , unit of the method performed by SMF of method 300 in FIG.
  • each unit in the apparatus 100 and the above-mentioned other operations and/or functions are for implementing the method 100 in FIG. 5 , the method 200 in FIG. 6 , the method 300 in FIG. 7 , the method 400 in FIG. 8 , and the method in FIG. Corresponding processes of the method 500, the method 600 in FIG. 10, and the method 700 in FIG. 11. It should be understood that the specific process of each unit performing the above-mentioned corresponding steps has been described in detail in the above-mentioned method embodiments, and for the sake of brevity, it will not be repeated here.
  • FIG. 13 is a schematic block diagram of an apparatus 200 for obtaining an edge service provided by an embodiment of the present application.
  • the apparatus 200 may include: a transceiver unit 210 and a processing unit 220.
  • the apparatus 200 may be the first edge configuration server network element in the above method embodiment, or may be used to implement the function of the first edge configuration server network element in the above method embodiment chip.
  • the apparatus 200 may correspond to the first edge configuration server in the method 100 according to the embodiment of the present application, the ECS#1 network element in the method 200, the ECS#2 network element in the method 300, and the ECS in the method 400.
  • Network element #3, the ECS#5 network element in method 600, and the ECS#6 network element in method 700 the apparatus 200 may include means for performing the method performed by the first edge configuration server of the method 100 in FIG. 5 , the unit of the method performed by ECS #1 of the method 200 in FIG. 6 , the unit of the method performed by ECS #2 of the method 300 in FIG. 7 , the unit of the method performed by ECS #3 of the method 400 in FIG. 8 , FIG.
  • each unit in the apparatus 200 and the above-mentioned other operations and/or functions are for implementing the method 100 in FIG. 5 , the method 200 in FIG. 6 , the method 300 in FIG. 7 , the method 400 in FIG. 8 , and the method in FIG. The method 600 and the corresponding flow of the method 700 in FIG. 11 . It should be understood that the specific process of each unit performing the above-mentioned corresponding steps has been described in detail in the above-mentioned method embodiments, and for the sake of brevity, it will not be repeated here.
  • the apparatus 200 may be the network storage function network element in the above method embodiment, or may be a chip for implementing the function of the network storage function network element in the above method embodiment.
  • the apparatus 200 may correspond to the NRF network element in the method 200, the NRF network element in the method 300, the NRF network element in the method 400, and the NRF network element in the method 500 according to the embodiment of the present application.
  • the apparatus 200 May include means for performing the NRF-implemented method of method 200 in FIG. 6 , the NRF-implemented method of method 300 in FIG. 7 , the NRF-implemented method of method 400 in FIG. Elements of the method performed by the NRF of method 500 .
  • the units in the apparatus 200 and the above other operations and/or functions are respectively to implement the corresponding processes of the method 200 in FIG. 6 , the method 300 in FIG. 7 , the method 400 in FIG. 8 , and the method 500 in FIG. It should be understood that the specific process of each unit performing the above-mentioned corresponding steps has been described in detail in the above-mentioned method embodiments, and for the sake of brevity, it will not be repeated here.
  • FIG. 14 is a structural block diagram of a device 300 for obtaining an edge service provided by an embodiment of the present application.
  • the device 300 shown in FIG. 14 includes: a processor 310 , a memory 320 and a transceiver 330 .
  • the processor 310 is coupled to the memory for executing instructions stored in the memory to control the transceiver 330 to transmit and/or receive signals.
  • the transceiver 330 in the device 300 may correspond to the transceiver unit 110 shown in FIG. 12 and the transceiver unit 210 shown in FIG. 13 ; the processor 310 in the device 300 may correspond to the process shown in FIG. 12 . unit 120 and processing unit 220 shown in FIG. 13 .
  • processor 310 and the memory 320 may be combined into a processing device, and the processor 310 is configured to execute the program codes stored in the memory 320 to realize the above-mentioned functions.
  • the memory 320 may also be integrated in the processor 310 or independent of the processor 310 .
  • the processor 310 may also correspond to each processing unit in the foregoing apparatus, and the transceiver 330 may correspond to each receiving unit and each transmitting unit in the foregoing apparatus.
  • transceiver 330 may include a receiver (or, receiver) and a transmitter (or, transmitter). The transceiver may further include antennas, and the number of the antennas may be one or more. Transceiver 330 may also be a communication interface or interface circuit.
  • the device 300 may be the first control plane core network element in the above method embodiment, or may be a network element for implementing the first control plane core network element in the above method embodiment functional chip.
  • the device 300 may correspond to the first control plane core network element in the method 100 according to the embodiment of the present application, the SMF network element in the method 200, the SMF network element in the method 300, and the AMF network in the method 400.
  • element, the SMF network element in the method 500, the SMF network element in the method 600, and the SMF network element in the method 700 the device 300 may include a first control plane core network network element for performing the method 100 in FIG. unit of the method of FIG. 6 , unit of the method performed by SMF of method 200 in FIG. 6 , unit of the method performed by SMF of method 300 in FIG. 7 , unit of method performed by AMF of method 400 in FIG.
  • each unit in the device 300 and the above-mentioned other operations and/or functions are respectively for implementing the method 100 in FIG. 5 , the method 200 in FIG. 6 , the method 300 in FIG. 7 , the method 400 in FIG. 8 , and the method in FIG. Corresponding processes of the method 500, the method 600 in FIG. 10, and the method 700 in FIG. 11. It should be understood that the specific process of each unit performing the above-mentioned corresponding steps has been described in detail in the above-mentioned method embodiments, and for the sake of brevity, it will not be repeated here.
  • the device 300 may be the first edge configuration server network element in the above method embodiment, or may be used to implement the function of the first edge configuration server network element in the above method embodiment chip.
  • the device 300 may correspond to the first edge configuration server in the method 100 according to the embodiment of the present application, the ECS#1 network element in the method 200, the ECS#2 network element in the method 300, and the ECS in the method 400.
  • #3 network element, ECS #5 network element in method 600, and ECS #6 network element in method 700 the apparatus 300 may include means for performing the method performed by the first edge configuration server of method 100 in FIG. 5 , the unit of the method performed by ECS #1 of the method 200 in FIG. 6 , the unit of the method performed by ECS #2 of the method 300 in FIG. 7 , the unit of the method performed by ECS #3 of the method 400 in FIG. 8 , FIG. 10 Elements of the method performed by ECS #5 of method 600 in FIG.
  • each unit in the device 300 and the above-mentioned other operations and/or functions are for implementing the method 100 in FIG. 5 , the method 200 in FIG. 6 , the method 300 in FIG. 7 , the method 400 in FIG. 8 , and the method in FIG. The method 600 and the corresponding flow of the method 700 in FIG. 11 . It should be understood that the specific process of each unit performing the above-mentioned corresponding steps has been described in detail in the above-mentioned method embodiments, and for the sake of brevity, it will not be repeated here.
  • the device 300 may be the network storage function network element in the above method embodiment, or may be a chip for implementing the function of the network storage function network element in the above method embodiment.
  • the device 300 may correspond to the NRF network element in the method 200 according to the embodiment of the present application, the NRF network element in the method 300, the NRF network element in the method 400, and the NRF network element in the method 500, the device 300 may include means for performing the NRF-performed method of method 200 in FIG. 6 , means for performing the NRF-performed method of method 300 in FIG. 7 , means for performing the NRF-performed method of method 400 in FIG. Elements of the method performed by the NRF of method 500.
  • each unit in the device 300 and the above other operations and/or functions are to implement the corresponding processes of the method 200 in FIG. 6 , the method 300 in FIG. 7 , the method 400 in FIG. 8 , and the method 500 in FIG. It should be understood that the specific process of each unit performing the above-mentioned corresponding steps has been described in detail in the above-mentioned method embodiments, and for the sake of brevity, it will not be repeated here.
  • the present application also provides a computer program product, the computer program product includes: computer program code, when the computer program code is run on a computer, the computer is made to execute the The method of any one of the embodiments shown in FIG. 7 , FIG. 8 , FIG. 9 , FIG. 10 , and FIG. 11 .
  • the present application further provides a computer-readable medium, where the computer-readable medium stores program codes, and when the program codes are executed on a computer, the computer is made to execute FIG. 5 , FIG. 6 , The method of any one of the embodiments shown in FIG. 7 , FIG. 8 , FIG. 9 , FIG. 10 , and FIG. 11 .
  • the present application further provides a system, which includes the aforementioned first control plane core network network element and a first edge configuration server.
  • the system may also include a third core network element.
  • the present application further provides a system, which includes the aforementioned first control plane core network network element and a second edge configuration server.
  • the above-mentioned embodiments it may be implemented in whole or in part by software, hardware, firmware or any combination thereof.
  • software it can be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated.
  • the computer may be a general purpose computer, special purpose computer, computer network, or other programmable device.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be downloaded from a website site, computer, server, or data center Transmission to another website site, computer, server, or data center by wire (eg, coaxial cable, optical fiber, digital subscriber line, DSL) or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, a data center, or the like that includes an integration of one or more available media.
  • the available media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, high-density digital video discs (DVDs)), or semiconductor media (eg, solid state discs, SSD)) etc.
  • the network-side equipment in each of the above apparatus embodiments corresponds to the terminal equipment and the network-side equipment or terminal equipment in the method embodiments, and corresponding steps are performed by corresponding modules or units. Or the step of sending, other steps except sending and receiving may be performed by a processing unit (processor). For functions of specific units, reference may be made to corresponding method embodiments.
  • the number of processors may be one or more.
  • a component may be, but is not limited to, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer.
  • an application running on a computing device and the computing device may be components.
  • One or more components may reside within a process and/or thread of execution, and a component may be localized on one computer and/or distributed between two or more computers.
  • these components can execute from various computer readable media having various data structures stored thereon.
  • a component may, for example, be based on a signal having one or more data packets (eg, data from two components interacting with another component between a local system, a distributed system, and/or a network, such as the Internet interacting with other systems via signals) Communicate through local and/or remote processes.
  • data packets eg, data from two components interacting with another component between a local system, a distributed system, and/or a network, such as the Internet interacting with other systems via signals
  • the disclosed system, apparatus and method may be implemented in other manners.
  • the apparatus embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the functions, if implemented in the form of software functional units and sold or used as independent products, may be stored in a computer-readable storage medium.
  • the technical solution of the present application can be embodied in the form of a software product in essence, or the part that contributes to the prior art or the part of the technical solution, and the computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program codes.

Landscapes

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

Abstract

本申请提供了一种获取边缘服务的方法和装置，该方法包括：第一控制面核心网网元接收用户设备UE的第一信息；第一控制面核心网网元向第一边缘配置服务器发送第一消息，第一消息包括第一信息和第一通知信息，第一通知信息包括第一控制面核心网网元的通知地址信息和/或UE的上下文信息；第一控制面核心网网元接收第一边缘配置服务器的第二消息，第二消息包括第一通知信息和第二信息，第二信息包括所述第一边缘配置服务器发送给UE的信息；第一控制面核心网网元根据第一通知信息向UE发送所述第二信息，可以实现UE通过核心网网元向边缘服务器发送信息，从而获取边缘服务。

Description

获取边缘服务的方法和装置
本申请要求于2020年11月10日提交中国专利局、申请号为202011250645.2、发明名称为“一种获取边缘服务的方法、装置和系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
本申请要求于2021年1月18日提交中国专利局、申请号为202110065138.X、发明名称为“获取边缘服务的方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，并且更具体地，涉及一种获取边缘服务的方法和装置。
背景技术
用户设备(user equipment，UE)要向边缘服务器发送信息一般采用如下方案：边缘使能客户端(edge enabler client，EEC)作为UE的一部分，会先在EEC上配置边缘配置服务器(edge configuration server，ECS)的地址信息，然后，EEC向ECS发送服务配置请求(service provisioning request)或服务订阅请求(service subscription update request)以获取边缘使能服务器(edge enabler server，EES)的地址信息，UE或EEC获取到EES的地址信息后，EEC向EES发送EAS发现请求(EAS discovery request)以获取边缘应用服务器(edge application server，EAS)的地址信息。
由于服务配置请求(service provisioning request)和EAS发现请求(EAS discovery request)都是通过HTTP协议发送，只适用于请求-响应模型，并且UE需要维持一个长连接，采用上述技术的方案边缘服务器无法向UE推送信息。
因此，需要一种获取边缘服务的方法，使得UE不用维持一个长连接，ECS或EES也可以向UE推送或发送信息，从而获取边缘服务。
发明内容
本申请提供了一种获取边缘服务的方法和装置，UE不用维持一个长连接，ECS或EES也可以向UE推送或发送信息，从而获取边缘服务。
该方法例如可以由终端设备执行，或者，也可以由配置在终端设备中的部件(如芯片或芯片系统等)执行。本申请对此不作限定。本申请以用户设备UE为例进行说明。
第一方面提供了一种获取边缘服务的方法，该方法包括：第一控制面核心网网元接收用户设备UE的第一信息；第一控制面核心网网元向第一边缘配置服务器发送第一消息，所述第一消息包括所述第一信息和第一通知信息，所述第一通知信息包括所述第一控制面核心网网元的通知地址信息和/或所述UE的上下文信息；第一控制面核心网网元接收所述第一边缘配置服务器的第二消息，所述第二消息包括所述第一通知信息和第二信息，所述 第二信息包括所述第一边缘配置服务器发送给所述UE的信息；第一控制面核心网网元根据所述第一通知信息向所述UE发送所述第二信息。
基于上述技术方案，用户设备可以向第一控制面核心网网元发送第一信息，第一控制面核心网网元向第一边缘配置服务器转发UE的第一信息并且携带第一通知地址信息，以便于第一边缘配置服务器确定向哪个核心网网元发送信息。第一边缘配置服务器确定发送给UE的第二信息并发送给第一控制面核心网网元并且携带第一通知地址信息，第一控制面核心网网元可以根据第一通知地址信息将该信息发送给UE。因此，本申请实施例所提供方法UE是通过控制面核心网网元发送相关信息，可以实现当ECS或EES属于5GC网元时，UE不用维持一个长连接，也可以向边缘服务器发送信息，从而获取边缘服务。
需要说明的是，本申请实施例中的第一信息包括所述UE向边缘配置服务器发送的信息，例如，第一信息可以是用于请求边缘使能服务器标识信息的。
结合第一方面，在某些可能的实现方式中，所述第一通知信息用于指示所述第二信息的发送方向。
也就是说，第一边缘配置服务器可以通过第一通知信息确定发送第二信息的对象。
结合第一方面，在某些可能的实现方式中，第一控制面核心网网元接收用户设备UE的第一信息，包括：所述第一控制面核心网网元通过会话建立请求消息接收用户设备UE的第一信息；或者，所述第一控制面核心网网元通过会话修改请求消息接收用户设备UE的第一信息；或者，所述第一控制面核心网网元通过非接入层容器NAS Container消息接收用户设备UE的第一信息。
也就是说UE可以通过会话建立请求消息或者会话修改请求消息或者非接入层容器NAS Container消息向第一控制面核心网网元发送第一信息，以此可以实现向边缘服务器发送信息。当然，上述消息仅仅是示例性的不应对本申请实施例有任何限定，本申请并未排除UE可以采用其他的消息向第一控制面核心网网元发送第一信息。
结合第一方面，在某些可能的实现方式中，所述第一信息包括至少以下一项：服务配置请求、服务配置订阅请求、服务配置订阅更新请求、服务配置取消订阅请求。
也就是说，在本申请中UE还可以发送订阅请求，可以实现当边缘使能服务器或边缘应用服务器的地址信息有变化时，UE也可以实时获取更新后的地址信息。
结合第一方面，在某些可能的实现方式中，所述第一控制面核心网网元根据所述第一通知信息向所述UE发送所述第二信息，包括：所述第一控制面核心网网元根据所述第一通知信息通过会话建立接收消息向所述UE发送所述第二信息；或者，所述第一控制面核心网网元根据所述第一通知信息通过会话修改命令消息向所述UE发送所述第二信息；或者，所述第一控制面核心网网元根据所述第一通知信息通过非接入层容器NAS Container消息向所述UE发送所述第二信息。
结合第一方面，在某些可能的实现方式中，所述第一控制面核心网网元向第一边缘配置服务器发送第一消息，包括：所述第一控制面核心网网元通过第二核心网网元向所述第一边缘配置服务器发送第一消息。
例如，当第一控制面核心网网元为SMF网元时，可以通过PCF网元向第一边缘配置服务器发送第一消息。
结合第一方面，在某些可能的实现方式中，所述第一控制面核心网网元接收所述第一 边缘配置服务器的第二消息，包括：所述第一控制面核心网网元通过第二核心网网元接收所述第一边缘配置服务器的第二消息。
例如，当第一控制面核心网网元为SMF网元时，可以通过PCF网元接收第一边缘配置服务器的第二消息。
结合第一方面，在某些可能的实现方式中，该方法还包括：所述第一控制面核心网网元向第三核心网网元发送第三消息，所述第三消息用于请求获取边缘配置服务器的标识信息，所述标识信息包括所述边缘配置服务器的统一资源标识符和/或所述边缘配置服务器的互联网协议IP地址信息；所述第一控制面核心网网元接收第三核心网网元的第四消息，所述第四消息包括第一边缘配置服务器的标识信息。
也就是说，第一控制面核心网网元可以先确定边缘配置服务器，此时，可以向第三核心网网元查询，确定边缘配置服务器，例如，第一边缘配置服务器。从而可以实现当边缘配置服务器为核心网网元时向其发送信息，从而获取边缘服务。另外，本申请中可以实现在网络侧配置边缘配置服务器，提高了边缘服务器地址配置的灵活性，保障业务体验。
结合第一方面，在某些可能的实现方式中，所述第三消息包括所述UE的位置信息，所述UE的位置信息用于所述第三核心网网元确定所述第一边缘配置服务器，所述UE的位置信息包括至少以下一项：所述UE的跟踪区标识、所述UE的小区标识或所述UE的数据网络接入标识。
也就是说第三核心网网元可以根据UE的位置信息以及边缘配置服务器的服务范围确定第一边缘配置服务器。
结合第一方面，在某些可能的实现方式中，所述第一信息还包括所述第一边缘配置服务器的标识信息，所述第一控制面核心网网元向第一边缘配置服务器发送第一消息，包括：所述第一控制面核心网网元根据所述第一边缘配置服务器的标识信息向所述第一边缘配置服务器发送第一消息。
也就是说，UE也可以向第一控制面核心网网元发送第一边缘配置服务器的标识信息，这样第一控制面核心网网元就直接可以通过标识信息确定向哪个边缘配置服务器发送信息。
结合第一方面，在某些可能的实现方式中，当所述第一信息包括所述UE请求获取边缘使能服务器的标识消息时，所述第二信息还包括第一边缘使能服务器的标识消息，所述标识信息包括至少以下一项：统一资源标识符信息、实例标识符信息或互联网协议IP地址信息。
也就是说，UE发送第一信息中为请求获取边缘使能服务器的标识消息时，此时第一边缘配置服务器可以确定边缘使能服务器，例如，第一边缘使能服务器。以此可以实现UE向边缘配置服务器发送信息，从而获取边缘服务。
结合第一方面，在某些可能的实现方式中，所述第二信息包括第一边缘使能服务器的标识消息，该方法还包括：所述第一控制面核心网网元接收所述UE的第三信息，所述第三信息包括所述UE向所述第一边缘使能服务器发送的信息；所述第一控制面核心网网元向所述第一边缘使能服务器发送第五消息，所述第五消息包括所述第三信息和第一通知信息，所述第一通知信息包括所述第一控制面核心网网元的通知地址信息和/或所述UE的上下文信息；所述第一控制面核心网网元接收所述第一边缘使能服务器的第六消息，所述第 六消息包括所述第一通知信息和第四信息，所述第四信息包括第一边缘应用服务器的标识信息；所述第一控制面核心网网元根据所述第一通知信息向所述UE发送所述第四信息。
也就是说，UE请求获取边缘应用服务器的标识消息时，第一控制面核心网网元可以先确定边缘使能服务器，然后向第一边缘使能服务器请求获取边缘应用服务器的标识信息，再发送给UE。以此可以UE实现向边缘配置服务器发送信息，从而获取边缘服务。
结合第一方面，在某些可能的实现方式中，所述第一控制面核心网网元接收所述第一边缘配置服务器的第二消息，所述第二消息包括所述第一通知信息和第二信息，所述第二信息包括所述第一边缘配置服务器发送给所述UE的信息，所述方法还包括：所述第一控制面核心网网元保存所述第二信息。
也就是说，例如，第一控制面核心网网元可以保存边使能服务器的标识信息，以便后续UE发送消息给边使能服务器时，第一控制面核心网网元可以校验UE指定的边使能服务器是否合法。
结合第一方面，在某些可能的实现方式中，所述第一控制面核心网网元包括：会话管理功能网元或接入和移动性管理功能网元或策略控制网元。
根据本实施例提供的方法，UE通过控制面核心网网元发送相关信息可以实现当ECS为核心网网元或AF时，UE通过核心网网元向ECS发送信息，对应的，ECS通过核心网网元向UE发送信息从而获取边缘服务，对现有机制(包括UE、网络侧网元)的改动较小。另外，本申请提供的技术方案可以实现在网络侧配置ECS的地址信息，提高了边缘服务器地址配置的灵活性，保障业务体验。而且本申请实施例还可以实现当EES或EAS的地址信息有变化时，UE也可以实时获取更新后的EES或EAS的地址信息。
第二方面，提供了一种获取边缘服务的方法，该方法包括：第一边缘配置服务器接收第一控制面核心网网元的第一消息，所述第一消息包括第一信息和第一通知信息，所述第一通知信息包括所述第一控制面核心网网元的通知地址信息和/或所述UE的上下文信息；所述第一边缘配置服务器根据所述第一信息确定所述第二消息，所述第二消息包括所述第一通知信息和第二信息，所述第二信息包括所述第一边缘配置服务器发送给所述UE的信息；所述第一边缘配置服务器向所述第一控制面核心网网元发送第二消息。
也就是说，第一边缘配置服务器可以根据第一信息确定UE要获取的信息，并将第二信息发送给第一控制面核心网网元。可以实现当边缘配置服务器或边缘使能服务器为核心网网元时，UE向边缘服务器发送信息，从而获取边缘服务。
结合第二方面，在某些可能的实现方式中，所述第一通知信息用于指示所述第二信息的发送方向。
结合第二方面，在某些可能的实现方式中，所述第一信息包括至少以下一项：服务配置请求、服务配置订阅请求、服务配置订阅更新请求、服务配置取消订阅请求。
结合第二方面，在某些可能的实现方式中，第一边缘配置服务器接收第一控制面核心网网元的第一消息，包括：所述第一边缘配置服务器通过第二核心网网元接收第一控制面核心网网元的第一消息。
结合第二方面，在某些可能的实现方式中，所述第一边缘配置服务器向所述第一控制面核心网网元发送第二消息，包括：所述第一边缘配置服务器通过第二核心网网元向所述第一控制面核心网网元发送第二消息。
结合第二方面，在某些可能的实现方式中，当所述第一信息为所述UE请求获取边缘使能服务器的标识消息时，所述第二信息还包括第一边缘使能服务器的标识消息，所述标识信息包括至少以下一项信息：统一资源标识符信息、实例标识符信息或互联网协议IP地址信息。
结合第二方面，在某些可能的实现方式中，所述第一控制面核心网网元包括：会话管理功能网元或接入和移动性管理功能网元或策略控制网元。
根据本实施例提供的方法是UE通过控制面核心网网元发送相关信息，可以实现当ECS为核心网网元或AF时，UE通过核心网网元向ECS发送信息，对应的，ECS通过核心网网元向UE发送信息，从而获取边缘服务，对现有机制(包括UE、网络侧网元)的改动较小。另外，本申请提供的技术方案可以实现在网络侧配置ECS的地址信息，提高了边缘服务器地址配置的灵活性，保障业务体验。而且本申请实施例还可以实现当EES或EAS的地址信息有变化时，UE也可以实时获取更新后的EES或EAS的地址信息。
第三方面，提供了一种获取边缘服务的方法，该方法包括：第三核心网网元接收第一控制面核心网网元的第三消息，所述第三消息用于请求获取边缘配置服务器的标识信息，所述标识信息包括所述边缘配置服务器的统一资源标识符和/或所述边缘配置服务器的互联网协议IP地址信息；所述第三核心网网元根据所述第三消息确定第四消息，所述第四消息包括第一边缘配置服务器的标识信息；所述第三核心网网元向所述第一控制面核心网网元发送所述第四信息。
也就是说，UE发送第一信息中为请求获取边缘使能服务器的标识消息时，此时第一边缘配置服务器可以确定边缘使能服务器，例如，第一边缘使能服务器。以此可以实现UE向边缘配置服务器发送信息，从而获取边缘服务。
结合第三方面，在某些可能的实现方式中，所述第三消息包括所述UE的位置信息，所述UE的位置信息用于所述第三核心网网元确定所述第一边缘配置服务器，所述UE的位置信息包括至少以下一项：所述UE的跟踪区标识、所述UE的小区标识或所述UE的数据网络接入标识。
结合第三方面，在某些可能的实现方式中，所述第一控制面核心网网元包括：会话管理功能网元或接入和移动性管理功能网元或策略控制网元。
根据本实施例提供的方法UE通过控制面核心网网元发送相关信息，可以实现当ECS为核心网网元或AF时，UE通过核心网网元向ECS发送信息，对应的，ECS通过核心网网元向UE发送信息，对现有机制(包括UE、网络侧网元)的改动较小。另外，本申请提供的技术方案可以实现在网络侧配置ECS的地址信息，提高了边缘服务器地址配置的灵活性，保障业务体验。而且本申请实施例还可以实现当EES或EAS的地址信息有变化时，UE也可以实时获取更新后的EES或EAS的地址信息。
第四方面，提供了获取边缘服务的方法，该方法包括：第一边缘应用服务器接收所述第一控制面核心网网元的第五消息，所述第五消息包括第一信息和第一通知信息，所述第一通知信息包括所述第一控制面核心网网元的通知地址信息和/或所述UE的上下文信息；所述第一边缘应用服务器根据所述第一信息确定第六消息，所述第六消息包括所述第一通知信息和第三信息，所述第三信息包括第一边缘应用服务器的标识信息；所述第一边缘应用服务器向所述第一控制面核心网网元发送所述第六消息。
也就是说，当第一信息为UE请求获取边缘应用服务器的标识消息时，第一控制面核心网网元可以先确定边缘使能服务器，然后向第一边缘使能服务器请求获取边缘应用服务器的标识信息，再发送给UE。以此可以UE实现向边缘配置服务器发送信息，从而获取边缘服务。
结合第四方面，在某些可能的实现方式中，所述第一控制面核心网网元包括：会话管理功能网元或接入和移动性管理功能网元或策略控制网元。
根据本实施例提供的方法UE通过控制面核心网网元发送相关信息，可以实现当ECS为核心网网元或AF时，UE通过核心网网元向ECS发送信息，对应的，ECS通过核心网网元向UE发送信息，从而获取边缘服务，对现有机制(包括UE、网络侧网元)的改动较小。另外，本申请提供的技术方案可以实现在网络侧配置ECS的地址信息，提高了边缘服务器地址配置的灵活性，保障业务体验。而且本申请实施例还可以实现当EES或EAS的地址信息有变化时，UE也可以实时获取更新后的EES或EAS的地址信息。
第五方面，提供了一种获取边缘服务的装置，包括用于执行第一方面、第二方面、第三方面及第四方面中任一种可能实现方式中的方法的各个模块或单元。
第六方面，提供了一种获取边缘服务设备，包括，处理器，存储器，该存储器用于存储计算机程序，该处理器用于从存储器中调用并运行该计算机程序，使得该通信装置执行第一至第四方面中任一种可能实现方式中的通信方法。
所述处理器为一个或多个，所述存储器为一个或多个。所述存储器可以与所述处理器集成在一起，或者所述存储器与处理器分离设置。
该通信设备还包括，发射机(发射器)和接收机(接收器)。
一个可能的设计中，提供了一种通信设备，包括收发器、处理器和存储器。该处理器用于控制收发器收发信号，该存储器用于存储计算机程序，该处理器用于从存储器中调用并运行该计算机程序，使得该通信设备执行第一至第四方面或第一至第四方面任一种可能实现方式中的方法。
第七方面，提供了一种计算机程序产品，所述计算机程序产品包括：计算机程序(也可以称为代码，或指令)，当所述计算机程序被运行时，使得计算机执行上述第一方面至第四方面中任一种可能实现方式中的方法。
第八方面，提供了一种计算机可读介质，所述计算机可读介质存储有计算机程序(也可以称为代码，或指令)当其在计算机上运行时，使得计算机执行上述第一方面至第四方面中任一种可能实现方式中的方法。
第九方面，提供了一种芯片系统，包括存储器和处理器，该存储器用于存储计算机程序，该处理器用于从存储器中调用并运行该计算机程序，使得安装有该芯片系统的通信设备执行上述第一方面至第四方面中任一种可能实现方式中的方法。
第十方面，提供了一种芯片，芯片包括处理器和通信接口，该通信接口用于与外部器件或内部器件进行通信，该处理器用于实现上述第一方面至第四方面中任一种可能实现方式中的方法。
可选地，该芯片还可以包括存储器，该存储器中存储有指令，处理器用于执行存储器中存储的指令或源于其他的指令。当该指令被执行时，处理器用于实现上述第一方面至第四方面中任一种可能实现方式中的方法可选地，该芯片可以集成在接入网设备上。
第十一方面，提供了一种系统，所述系统包括第一控制面核心网网元以及用于与该第一控制面核心网网元进行通信的第一边缘配置服务器。可选的，该系统还可以包括第三核心网网元。
第十二方面，提供了一种获取边缘服务的方法，该方法包括：第一控制面核心网网元接收用户设备UE的第五信息；所述第一控制面核心网网元向第二边缘配置服务器发送第七消息，所述第七消息包括所述第七第五信息和所述UE的会话信息，所述UE的会话信息用于所述第二边缘配置服务器建立应用功能网元AF会话；所述第一控制面核心网网元通过所述AF会话接收所述第八消息，所述第八消息包括所述第二边缘配置服务器发送给所述UE的信息；所述第一控制面核心网网元向所述UE发送所述第八消息。
基于上述技术方案，用户设备可以向第一控制面核心网网元发送第五信息，第一控制面核心网网元向第二边缘配置服务器转发UE的第五信息并且携带述UE的会话信息，以便于第一边缘配置服务器和第一控制面核心网网元以及UE关联起来，从而可以直接确定向哪个核心网网元和哪个UE发送信息。第二边缘配置服务器确定发送给UE的信息并发送给第一控制面核心网网元，第一控制面核心网网元可以将该信息发送给UE。因此，本申请实施例所提供方法UE通过控制面核心网网元发送相关信息，可以实现当ECS或EES属于5GC网元时，UE也可以向边缘服务器发送信息从而获取边缘服务。
应理解，本申请实施例中，第五信息包括所述UE向边缘配置服务器请求信息，例如，第五信息可以是用于UE请求获取ECS标识信息的信息。
结合第十二方面，在某些可能的实现方式中，所述UE的会话信息，包括至少一下一项：所述UE的互联网协议IP地址、所述UE的会话对应的数据网络名称DNN以及单一网络切片选择辅助信息S-NSSAI。
结合第十二方面，在某些可能的实现方式中，该方法还包括：所述第一控制面核心网网元根据所述UE的位置信息确定所述第二边缘配置服务器。
结合第十二方面，在某些可能的实现方式中，所述第一控制面核心网网元接收用户设备UE的第五信息，包括：所述第一控制面核心网网元通过会话建立请求消息接收用户设备UE的第一信息；或者，所述第一控制面核心网网元通过会话修改请求消息接收用户设备UE的第一信息；或者，所述第一控制面核心网网元通过非接入层容器NAS Container消息接收用户设备UE的第一信息。
结合第十二方面，在某些可能的实现方式中，所述第五信息包括至少以下一项：服务配置请求、服务配置订阅请求、服务配置订阅更新请求、服务配置取消订阅请求。
结合第十二方面，在某些可能的实现方式中，所述第一控制面核心网网元向第二边缘配置服务器发送第七消息，包括：所述第一控制面核心网网元通过第二核心网网元向所述第二边缘配置服务器发送第七消息。
结合第十二方面，在某些可能的实现方式中，所述第一控制面核心网网元接收所述第二边缘配置服务器的第八消息，包括：所述第一控制面核心网网元通过第二核心网网元接收所述第二边缘配置服务器的第八消息。
结合第十二方面，在某些可能的实现方式中，所述第一控制面核心网网元包括：会话管理功能网元或接入和移动性管理功能网元或策略控制网元。
第十三方面，提供了一种获取边缘服务的方法，该方法包括：第二边缘配置服务器接 收所述第一控制面核心网网元的第七消息，所述第七消息包括第五信息和用户设备UE的会话信息，所述第五信息包括所述UE向边缘配置服务器请求信息；所述UE的会话信息用于所述第二边缘配置服务器建立应用功能网元AF会话；所述第二边缘配置服务器根据所述第五信息确定第八消息，所述第八消息包括所述第二边缘配置服务器发送给所述UE的信息；所述第二边缘配置服务器通过所述AF会话向所述第一控制面核心网网元发送所述第八消息。
结合第十三方面，在在某些可能的实现方式中，所述UE的会话信息，包括至少一下一项：所述UE的互联网协议IP地址、所述UE的会话对应的数据网络名称DNN以及单一网络切片选择辅助信息S-NSSAI。
结合第十三方面，在在某些可能的实现方式中，所述第二边缘配置服务器是根据所述UE的位置信息确定的。
结合第十三方面，在在某些可能的实现方式中，所述第一控制面核心网网元包括：会话管理功能网元或接入和移动性管理功能网元或策略控制网元。
根据本实施例提供的方法，可以实现当ECS为核心网网元或AF时，UE通过核心网网元向ECS发送信息，对应的，ECS通过核心网网元向UE发送信息，从而获取边缘服务，对现有机制(包括UE、网络侧网元)的改动较小。另外，本申请提供的技术方案可以实现在网络侧配置ECS的地址信息，提高了边缘服务器地址配置的灵活性，保障业务体验。而且本申请实施例还可以实现当EES或EAS的地址信息有变化时，UE也可以实时获取更新后的EES或EAS的地址信息。
第十四方面，提供了一种获取边缘服务的装置，包括用于执行第十一方面、第十二方面中任一种可能实现方式中的方法的各个模块或单元。
第十五方面，提供了一种获取边缘服务的设备，包括，处理器，存储器，该存储器用于存储计算机程序，该处理器用于从存储器中调用并运行该计算机程序，使得该通信装置执行第十一和第十二方面中任一种可能实现方式中的通信方法。
所述处理器为一个或多个，所述存储器为一个或多个。所述存储器可以与所述处理器集成在一起，或者所述存储器与处理器分离设置。
该通信设备还包括，发射机(发射器)和接收机(接收器)。
一个可能的设计中，提供了一种通信设备，包括收发器、处理器和存储器。该处理器用于控制收发器收发信号，该存储器用于存储计算机程序，该处理器用于从存储器中调用并运行该计算机程序，使得该通信设备执行第一至第四方面或第一至第四方面任一种可能实现方式中的方法。
第十六方面，提供了一种计算机程序产品，所述计算机程序产品包括：计算机程序(也可以称为代码，或指令)，当所述计算机程序被运行时，使得计算机执行上述第十一方面和第十二方面中任一种可能实现方式中的方法。
第十七方面，提供了一种计算机可读介质，所述计算机可读介质存储有计算机程序(也可以称为代码，或指令)当其在计算机上运行时，使得计算机执行上述第十一方面和第十二方面中任一种可能实现方式中的方法。
第十八方面，提供了一种芯片系统，包括存储器和处理器，该存储器用于存储计算机程序，该处理器用于从存储器中调用并运行该计算机程序，使得安装有该芯片系统的通信 设备执行上述第十一方面至第十二方面中任一种可能实现方式中的方法。
第十九方面，提供了一种芯片，芯片包括处理器和通信接口，该通信接口用于与外部器件或内部器件进行通信，该处理器用于实现上述第十一方面至第十二方面中任一种可能实现方式中的方法。
可选地，该芯片还可以包括存储器，该存储器中存储有指令，处理器用于执行存储器中存储的指令或源于其他的指令。当该指令被执行时，处理器用于实现上述第一方面至第四方面中任一种可能实现方式中的方法可选地，该芯片可以集成在接入网设备上。
第二十方面，提供了一种系统，所述系统包括第一控制面核心网网元以及用于与该第一控制面核心网网元进行通信的第二边缘配置服务器。
本申请提供了一种获取边缘服务的方法和装置，UE通过控制面核心网网元发送相关信息，可以实现当ECS为核心网网元或AF时，UE通过核心网网元向ECS发送信息，对应的，ECS通过核心网网元向UE发送信息，从而获取边缘服务，对现有机制(包括UE、网络侧网元)的改动较小。
附图说明
图1本申请实施例适用系统架构图。
图2是本申请实施例边缘业务架构示意图。
图3是本申请实施例另一边缘业务架构示意图。
图4是本申请实施例适用另一边缘业务架构示意图。
图5是本申请另一实施例提供的获取边缘服务的方法示意性流程图。
图6是本申请另一实施例提供的获取边缘服务的方法示意性流程图。
图7是本申请另一实施例提供的获取边缘服务的方法示意性流程图。
图8是本申请另一实施例提供的获取边缘服务的方法示意性流程图。
图9是本申请另一实施例提供的获取边缘服务的方法示意性流程图。
图10是本申请另一实施例提供的获取边缘服务的方法示意性流程图。
图11是本申请另一实施例提供的获取边缘服务的方法示意性流程图。
图12是本申请实施例提供的获取边缘服务装置的示意性框图。
图13是本申请实施例提供的获取边缘服务装置的示意性框图。
图14是本申请实施例提供的获取边缘服务设备的示意性框图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
本申请实施例提及的无线通信系统包括但不限于：全球移动通信(global system of mobile communication，GSM)系统、长期演进(long term evolution，LTE)频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)、LTE系统、先进的长期演进(LTE-Advanced，LTE-A)系统、下一代通信系统(例如，6G通信系统)、多种接入系统的融合系统，或演进系统。
本申请提供的技术方案还可以应用于机器类通信(machine type communication，MTC)、机器间通信长期演进技术(Long Term Evolution-machine，LTE-M)、设备到设备(device  to device，D2D)网络、机器到机器(machine to machine，M2M)网络、物联网(internet of things，IoT)网络或者其他网络。其中，IoT网络例如可以包括车联网。其中，车联网系统中的通信方式统称为车到其他设备(vehicle to X，V2X，X可以代表任何事物)，例如，该V2X可以包括：车辆到车辆(vehicle to vehicle，V2V)通信，车辆与基础设施(vehicle to infrastructure，V2I)通信、车辆与行人之间的通信(vehicle to pedestrian，V2P)或车辆与网络(vehicle to network，V2N)通信等。
本申请实施例中所涉及到的终端设备可以包括各种具有无线通信功能的接入终端、移动设备、用户终端或用户装置。例如，终端设备可以为用户设备(user equipment，UE)，例如，手机(mobile phone)、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端设备、增强现实(augmented reality，AR)终端设备等。终端设备也可是工业控制(industrial control)中的无线终端、机器类型通信(machine type communication，MTC)终端、客户终端设备(customer premise equipment，CPE)、无人驾驶(self-driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)、蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，5G网络中的终端设备或者未来演进的公用陆地移动通信网络(public land mobile network，PLMN)中的终端设备等。
下面结合图1和图2详细介绍本申请实施例涉及网络系统架构以及该架构下的边缘业务架构。
图1是本申请实施例适用的系统架构图，如图所示，该网络架构具体可以包括下列网元：
1、无线接入网(radio access network，RAN)：基于无线通信技术实现接入网络功能的接入网可以称为无线接入网。无线接入网能够管理无线资源，为终端提供接入服务，进而完成控制信号和用户数据在终端和核心网之间的转发。
无线接入网例如可以是全球移动通讯(global system of mobile communication，GSM)系统或码分多址(code division multiple access，CDMA)中的基站(base transceiver station，BTS)，也可以是宽带码分多址(wideband code division multiple access，WCDMA)系统中的基站(nodeB，NB)，还可以是LTE系统中的演进型基站(evolutional nodeB，eNB或eNodeB)，还可以是云无线接入网络(cloud radio access network，CRAN)场景下的无线控制器，或者该网络设备可以为中继站、接入点、车载设备、可穿戴设备以及未来5G网络中的网络设备或者未来演进的PLMN网络中的网络设备等，本申请实施例并不限定。
2、认证服务功能(authentication server function，AUSF)网元：主要用于用户鉴权等。
3、接入和移动性管理功能网元(access and mobility management function，AMF)：主要用于移动性管理和接入管理等，可以用于实现移动性管理实体(mobility management entity，MME)功能中除会话管理之外的其它功能，例如，合法监听、或接入授权(或鉴权)等功能。在本申请实施例中，可用于实现接入和移动管理网元的功能。
4、会话管理功能网元(session management function，SMF)：主要用于会话管理、 终端设备的IP地址分配和管理、选择和管理用户平面功能、策略控制、或收费功能接口的终结点以及下行数据通知等。在本申请实施例中，可用于实现会话管理网元的功能。
5、策略控制网元(policy control function，PCF)：用于指导网络行为的统一策略框架，为控制平面功能网元(例如AMF，SMF网元等)提供策略规则信息等。
6、应用功能网元(application function，AF)：用于进行应用影响的数据路由，接入网络开放功能网元，或，与策略框架交互进行策略控制等。
7、统一数据管理网元(unified data management，UDM)：用于统一数据管理、5G用户数据管理、处理用户标识、接入鉴权、注册、或移动性管理等。
8、用户面功能网元(user plane function，UPF)：可用于分组路由和转发、或用户面数据的服务质量(quality of service，QoS)处理等。用户数据可通过该网元接入到数据网络(data network，DN)。在本申请实施例中，可用于实现用户面网元的功能。
9、网络切片选择功能网元(network slice selection function，NSSF)：用于管理网络切片相关的信息。
10、数据网络(digital network,DN)：用于提供传输数据的网络。例如，运营商业务的网络、因特(Internet)网、第三方的业务网络等。
另外，上述网络架构还包括网络存储功能网元((network function(NF)repository function，NRF)：用于保存网络功能实体以及其提供服务的描述信息，以及支持服务发现，网元实体发现等；网络开放功能网元(network exposure function，NEF)：用于安全地向外部开放由第三代合作伙伴计划(3GPP)网络功能提供的业务和能力等。统一数据存储功能(unified data repository，UDR)，用于UDM存储订阅数据或读取订阅数据以及PCF存储策略数据或者读取策略数据。
需要说明的是本申请中的网络系统架构还可以包括边缘配置服务器(edge configuration server，ECS)网元，ECS网元可以是全局管理网元，维护各个边缘数据网络(edge data network，EDN)的信息，包括边缘数据网络的服务范围和边缘数据网络中的边缘使能服务器(edge enabler server，EES)地址等。其中，边缘数据网络的服务范围可以是拓扑地址信息(例如Cell ID、TAI(Trach area id)等)或几何地址信息(例如，省、市、区或经纬度等信息)，服务范围可以是地址信息的集合。在一种实现方式中，ECS网元是分布式部署的，即每个ECS可以管理不同区域的边缘数据网络。应该理解ECS网元可以与其它网元合设也可以是独立的网元，本申请对ECS网元在网络架构中的部署情况并不做任何限定。
需要说明的是本申请中的网络系统架构还可以包括边缘使能服务器(edge enabler server，EES)网元，EES网元可以是移动边缘计算(mobile edge computing，MEC)节点(MEC也可称为多接入边缘计算(multi acess edge computing))中的控制网元或者管理网元，负责管理部署在该EDN里的各个EAS，比如注册，域名系统(domain name system，DNS)解析内容路由选择、上层应用注册管理、无线信息交互等基础功能。此外，EES可以调用3GPP网络中的能力开放功能网元。应该理解EES网元可以与其它网元合设也可以是独立的网元，本申请对EES网元在网络架构中的部署情况并不做任何限定。
在该网络架构中，N2接口为RAN和AMF网元的接口，用于非接入层(non-access stratum，NAS)消息的发送等；N3接口为RAN和UPF网元之间的接口，用于传输用户面 的数据等；N4接口为SMF网元和UPF网元之间的接口，用于传输例如N3连接的隧道标识信息，数据缓存指示信息，以及下行数据通知消息等信息。
应理解，上述应用于本申请实施例的网络架构仅是举例说明的从传统点到点的架构和服务化架构的角度描述的网络架构，适用本申请实施例的网络架构并不局限于此，任何能够实现上述各个网元的功能的网络架构都适用于本申请实施例。
应理解，图1中的各个网元之间的接口名称只是一个示例，具体实现中接口的名称可能为其他的名称，本申请对此不作具体限定。此外，上述各个网元之间的所传输的消息(或信令)的名称也仅仅是一个示例，对消息本身的功能不构成任何限定。
图2是本申请实施例边缘业务架构示意图，如图所示，该网络架构具体可以包括：边缘数据网络(edge data network，EDN)可以是本地数据中心，EDN包含边缘使能服务器(edge enabler server，EES)和多个边缘应用服务器(edge application server，EAS)，每个EDN有特定的服务范围。其中，EES可以是移动边缘计算(mobile edge computing，MEC)节点(MEC也可称为多接入边缘计算(multi acess edge computing))中的控制网元或者管理网元，负责管理部署在该EDN里的各个EAS，比如注册，域名系统(domain name system，DNS)解析内容路由选择、上层应用注册管理、无线信息交互等基础功能。此外，EES可以调用3GPP网络中的能力开放功能网元。边缘数据网络配置服务器(edge data network configuration server，EDNCS)或者边缘配置服务器(edge configuration server，ECS)可以是全局管理网元，维护各个EDN的信息，包括服务范围和EES地址等。需要说明的是，在有的标准协议中，比如技术规范(technical specification，TS)23.501、TS23.502等，上述EES，EAS，ECS等都可以称之为AF(application function)，以下不再赘述。
用户设备(user equipment，UE)中可以包括：边缘使能客户端(edge enabler client，EEC)和应用客户端，其中，EEC为终端上的应用客户端提供必要的支持，EEC的功能包括：通过EDGE-4检索EDN信息、UE注册到EES、检索可用的EAS、EAS可用性变化、EAS迁移通知给EEC。
图2中的EDGE-8参考点支持边缘配置服务器和核心网之间的交互，它支持：(1)访问用于检索网络能力信息的核心网功能和应用程序接口(application programming interface，API)；(2)向核心网(例如：SMF)提供业务发放通知。EDGE-1：EES与EEC之间的接口，支持EEC在EES的注册/去注册；边缘数据网络中的边缘应用服务器发现。EDGE-2：EES与3GPP核心网之间的接口，用于EES获取3GPP网络能力。EDGE-3：EES与EAS之间的接口，支持EES注册/去注册EAS，包括EAS的可用性信息、服务范围信息、地址信息等；EES给EAS提供3GPP网络能力信息(如位置信息)。EDGE-4：EEC与ECS之间的接口，支持ECS提供/推送配置信息给EEC。EDGE-5：AC与EEC之间的接口，支持AC从EEC获取接入的EAS信息。EDGE-6：ECS与EES之间的接口，支持在ECS上配置EES信息。EDGE-7：EAS与3GPP核心网之间的接口，支持EAS获取3GPP网络能力。EDGE-8：ECS与3GPP核心网之间的接口，支持ECS获取3GPP网络能力。EDGE-9：跨MEC节点/同一MEC节点内不同EES之间的接口，支持做应用迁移。
图3是本申请实施例另一边缘业务架构示意图。如图所示，为提升用户的体验，缩短用户访问应用服务器的时延，运营商或服务提供商会将应用服务器的部署下沉到地市级 (原本应用服务器按省份或大区来部署)。如图中应用服务器#1所示，多个网络(包括了边缘数据网络和中心数据网络)或MEC节点中可能部署了该应用服务器。每个MEC节点或称为缘数据网络有对应的服务区域，不同的缘数据网络的服务区域之间可以有交叉。若UE访问某个应用时位置发生了移动，则UE访问的应用服务器通常也需要随之切换，以更低的时延访问该应用。
图4是本申请实施例适用的另一系统架构示意图，如图所示，该网络架构具体可以包括：边缘数据网络EDN,每个EDN有特定的服务范围,每一个边缘网络中都包含一个或多个边缘使能服务器EES和边缘应用服务器EAS。例如，EDN#1的服务范围里包含有一个EES#1,和EAS#1以及EAS#2；EDN#2的服务范围里包含有一个EES#2,和EAS#3以及EAS#4。边缘配置服务器ECS是全局管理网元，维护各个EDN的信息，包括服务范围和EES地址等。用户设备UE可以通过核心网网元访问边缘服务器。比如，UE可以通过UPF或者AMF或者SMF或者PCF等网元获取EES和EAS的地址信息。
UE访问边缘服务器时一般采用如下方案，EEC作为UE的一部分，先在EEC上，即，在用户设备UE上配置ECS的地址信息。步骤1，EEC向ECS发送请求，比如，服务配置请求(service provision request)或服务配置订阅请求(service provisioningrequest)以获取EES的地址信息；步骤2，ECS向EEC发送响应，比如，服务配置响应(service provision response)，向EEC发送EES的地址信息。UE或EEC获取到EES的地址信息后，步骤3，EEC向EES发送请求，例如，EAS发现请求(EAS discoveryrequest)，以获取EAS的地址信息。步骤4，EES向EEC发送响应，例如，EAS发现响应(EAS discoveryresponse)，向EEC发送EAS的地址信息。需要说明的是，上述技术方案中，服务配置请求、服务配置订阅请求、EAS发现请求等都是通过HTTP协议发送。
另外，上述技术方案是在UE上配置ECS地址，配置不灵活并且ECS存在单点故障风险。而且，如上所述，UE与ECS或EES之间的通信采用HTTP协议，如果EES的地址信息发生改变时，ECS需要动态的给UE下发EES的位置信息。此时，UE需要分配端口和资源用于实时监听ECS的通知信息，考虑到UE的耗电、安全等问题，UE目前不支持这个功能。所以，上述技术方案中通信采用HTTP协议无法解决在EES地址信息有变化的场景下实时通知UE这一个问题。若要支持上述场景，对UE的改动非常大。
本申请提供了一种获取边缘服务的方法是UE通过控制面核心网网元发送相关信息，使得当ECS或EES属于5GC网元或AF(application function)时，UE也可以向边缘服务器发送信息，对现有机制(包括UE、网络侧网元)的改动较小。另外，本申请提供的技术方案可以实现在网络侧配置ECS的地址信息，提高了边缘服务器地址配置的灵活性，保障业务体验。而且本申请实施例还可以实现当EES或EAS的地址信息有变化时，UE也可以实时获取更新后的EES或EAS的地址信息。
下面将结合附图详细说明本申请实施例提供的方法。需要说明的是，在下文中结合附图描述实施例的过程中，图中仅为便于理解而示意，不应对本申请构成任何限定。各网元名称仅为区分不同的功能而定义，不应对本申请构成任何限定。本申请并不排除定义其他网元来实现相同或相似功能的可能。
如前所述，ECS可以是全局管理网元，维护各个边缘数据网络EDN的信息，包括服务范围和边缘使能服务器EES的地址等。也就是说ECS上配置或者保存了EES的地址信 息。因此，在本申请实施例中的一种可能的实现方式中，UE向核心网发送请求消息，用于请求EES地址信息时，核心网可以先确定ECS，然后核心网向目标ECS发送请求，用于请求EES的地址信息，ECS确定EES的地址信息后发送给UE。
在本申请实施例中的另一种可能的实现方式中，当UE向核心网发送请求消息，用于请求EAS的地址信息时，此时，核心网可以向目标EES发送请求，由EES确定EAS的地址信息，这是因为EES上配置或者保存了EAS的地址信息。
应该理解，本申请实施例也不排除未来核心网可以通过配置等其它方式直接确定当前可以为UE服务的EES或EAS的地址信息。
还应理解，本申请实施例中的标识消息可以指代地址信息，也就是说本申请实施例中的标识信息可以包括边缘服务器的地址信息。另外，还可以包括边缘服务器的标识，例如，边缘服务器的统一资源标识符(uniform resource identifier，URI)和/或边缘服务器的互联网协议IP地址信息，标识信息还可以包括边缘服务器的实例标识符(instance ID)，标识信息还可以包括边缘服务器的全限定域名(fully qualified domain name，FQDN)。
也就是说根据标识消息可以获取边缘服务器的地址信息。其中，边缘服务器可以是ECS、EES或EAS。
需要说明的是以上仅仅是对标识信息的举例，不应对本申请造成任何限定，本申请并未排除标识信息还可以是其它任何可以获取边缘服务器地址信息的信息。
图5是本申请实施例提供的一种获取边缘服务方法的示意性流程图。本实施例中以UE#1为例，UE#1可以通过非接入层NAS消息等消息向5G核心网网元(5G Core，5GC)(本实施例中以SMF为例)发送信息，核心网网元可以将UE#1发送的信息转发给边缘服务器，从而实现UE向通过核心网网元向边缘服务器(ECS或EES)发送信息，对应的，边缘服务器通过核心网网元向UE发送EES或EAS的标识信息，从而获取边缘服务。另外，本申请实施例提供的技术方案可以实现在网络侧配置ECS的地址信息，提高了边缘服务器地址配置的灵活性，保障业务体验。
应理解，本实施例中5GC核心网网元也可以是AMF或PCF等其他网元，也就是说本实施例中将SMF换做AMF或PCF等其他网元也可以执行如下步骤，不做限定。需要说明的是，当实施例中的5G核心网网元为SMF或PCF时，可以通过AMF网元转发UE发送的信息给SMF或PCF。
图5是本申请提供的向边缘服务器发送信息方法100的示意性流程图。作为示例而非限定，图5中的第一控制面核心网网元可以AMF网元或者SMF网元或者PCF网元。
步骤S101，第一控制面核心网网元接收用户设备UE的第一信息，第一信息包括UE向边缘配置服务器发送的信息。
作为示例而非限定，用户设备UE可以通过会话建立请求消息、会话修改请求消息、非接入层容器NAS Container消息等向SMF发送第一信息。
作为示例而非限定，UE#1向SMF发送的第一信息可以包括：服务配置请求(service provisioning request)、服务订阅请求(service provisioning subscription request)、服务订阅更新请求(service provisioning subscription update request)、服务取消订阅请求(service provisioning unsubscribe request)。
在一种实现方式中，服务配置请求(service provisioning request)、服务订阅请求(service  provisioning subscription request)、服务订阅更新请求(service provisioning subscription update request)、服务取消订阅请求(service provisioning unsubscribe request)可以包含于会话建立请求消息或会话修改请求消息中。在另一种实现方式中，上述请求可以是一个单独的NAS请求。
需要说明的是，本申请实施例中，例如“服务配置请求消息”等也可称作为“服务配置请求”，以下不在赘述。
应该理解，本申请实施例中UE发送给第一控制面核心网网元的第一信息可以是UE发送给边缘配置服务器的信息。例如，第一信息可以是服务配置请求，用于请求获取EES的标识信息。
作为示例而非限定，第一信息还可以包括指示信息，指示信息用于指示UE#1要获取EES的标识信息。第一信息还还可以包括应用信息，比如，application ID(例如，UE#1要连接的业务的信息)或者application client profile。第一信息还可以包括UE#1的标识信息，UE#1的标识信息可用于5GC和/或ECS对UE#1进行身份验证。第一信息还可以包括UE#1的位置信息，UE#1的位置信息可用确定于网络侧确定为UE服务的ECS和EES。UE#1的位置信息可以包括：UE#1所在的跟踪区标识(tracking area identity，TAI)和/或小区标识(cell identity，Cell ID)，或者UE#1当前(PDU会话所)对应的数据网络接入标识(date network acess identity，DNAI)等信息。
第一信息还中还可携带订阅指示，用于指示5GC和/或ECS UE#1订阅EES的改变通知，即在可用的EES信息发生变更时，将变更的EES信息通知给UE#1。其中，变更的EES信息可以为以下信息中的一个或多个：新的EES信息、旧的EES信息、相比于之前发送给UE#1的EES信息发送了变化的EES信息。
应理解，订阅指示信息可以用于指示当UE位置发生改变时可以为UE服务的边缘服务器的变更信息。也就是说订阅指示信息可以使得UE动态获取当前实时更新的可以为UE服务的服务器的信息。在一种实现方式中，订阅指示信息可以通过服务订阅请求(service provisioning request)或服务订阅更新请求(service subscription update request)体现。
步骤S102，第一控制面核心网网元向第一边缘配置服务器发送第一消息，第一消息包括第一信息和第一通知信息，第一通知信息包括第一控制面核心网网元的通知地址信息和/或UE的上下文信息。
在一种实现方式中，第一控制面核心网网元可以通过第二核心网网元向第一边缘配置服务器发送第一消息。例如，当第一控制面核心网网元为SMF时，可以通过PCF网元向第一边缘配置服务器发送第一消息。
在一种实现方式中，第一控制面核心网网元接收第一信息后可以确定需要向ECS发送该消息，具体的，第一控制面核心网网元可以基于本地配置或根据消息名称或根据签约信息等确定需要向ECS转发发送该消息。
具体的，第一控制面核心网网元接收UE发送的第一信息可以向第三核心网网元(例如，NRF网元)查询，确定第一边缘配置服务器，然后向第一边缘配置服务器发送第一消息；或者，第一控制面核心网网元接收UE发送的第一信息，根据历史保存信息确定第一边缘配置服务器。由此可以看出，本申请实施例是在网络侧配置ECS的地址信息，提高 了边缘服务器地址配置的灵活性，保障业务体验。
需要说明的是，第一控制面核心网网元向第一边缘配置服务器发送第一消息，可以是第一控制面核心网网元直接转发用户设备UE的第一信息，也就是说第一消息的内容可以完全包括第一信息，并且，第一信息还包括第一通知信息。第一通知信息可以包括第一控制面核心网网元的通知地址信息和/或UE的上下文信息。根据第一通知信息可以便于第一边缘配置服务器确定第一控制面核心网网元的地址，也可用于第一边缘配置服务器或第一控制面核心网网元确定UE。
第一边缘配置服务器接收第一消息，可以根据第一信息确定发送给UE的信息，即，第二信息；可以根据第一通知地址信息确定第一控制面核心网网元的地址，然后向第一控制面核心网网元发送第二消息。
需要说明的是，本申请实施例中的第一通知信息用于指示第二信息的发送方向，例如：
在一种可能的实现方式中，当第一边缘配置服务器向核心网发送信息时，第一通知信息可以用于指示第一边缘配置服务器向第一控制面核心网网元方向发送信息。
在一另种可能的实现方式中，当第一边缘配置服务器向UE发送信息时，第一通知信息可以用于指示第一边缘配置服务器向UE方向发送信息。
在一另种可能的实现方式中，第一通知信息也可以用于指示第一边缘配置服务器通过核心网网元(例如，SMF)向UE方向发送信息。
本申请中的第二信息可以是第一边缘配置服务器发送给UE的信息，需要说明的是，第一边缘配置服务器发送给UE的信息可以是根据第一信息确定的。作为一个示例，如果第一消息中的第一信息用于UE请求获取EES的标识信息，此时，第一边缘配置服务器可以根据UE的位置信息或边缘使能服务器的负载信息或应用信息等信息获取目标EES的标识信息，然后将EES的标识信息(即，第二消息)发送给第一控制面核心网网元。作为另一个示例，如果第一消息中的第一信息包括订阅指示信息，此时，第一边缘配置服务器可以根据UE的位置信息确定当前为UE提供服务的边缘使能服务器的标识信息(即，第二消息)发送给第一控制面核心网网元。
第二信息可以包括：服务配置请求响应(service provisioning response)、服务配置订阅请求响应(service provisioning subscription response)、服务配置订阅更新请求响应(service provisioning subscription update response)、服务配置取消订阅请求响应(service provisioning unsubscribe response)。
步骤S103，第一控制面核心网网元接收第一边缘配置服务器的第二消息，第二消息包括第一通知信息和第二信息，第二信息包括第一边缘配置服务器发送给UE的信息。
在一种实现方式中，第一控制面核心网网元通过第二核心网网元接收所述第一边缘配置服务器的第二消息。例如，当第一控制面核心网网元为SMF时，可以通过PCF网元接收第一边缘配置服务器的第二消息。
在一种实现方式中，第一通知信息包含在第二消息数据包的目的地址中。
应理解，第二消息可以是第一消息的响应消息。若第一消息是订阅消息或包含了订阅信息，第二消息可以是对应于第一消息的通知消息，该通知消息可以多次发送。比如，在边缘配置服务器确定需要向UE发送更新的EES标识信息时，发送该通知消息。需要说明的是本申请中将请求消息、通知消息和响应消息都统称为“消息”，但是基于各个实施例 的具体步骤，本领域技术人员应该明白和了解该“消息”是请求消息、通知消息还是响应消息，以下不再赘述。
第一控制面核心网网元接收第一边缘配置服务器根据所述第一消息发送的第二消息，第二消息包括所述第一通知信息和第二信息。
在一种实现方式中，第一边缘配置服务器根据第一消息中的第一信息确定第二信息，例如第一信息为服务配置请求，第二信息为服务配置响应，响应信息中包括确定的EES的标识信息或连接信息。又例如，第一信息为服务配置订阅请求，第二信息为服务配置通知，响应信息中包括确定的EES的标识信息或连接信息。连接信息可以是URI和/或边缘服务器的互联网协议IP地址信息，连接信息还可以包括边缘服务器的实例标识符(instance ID)，连接信息还可以包括边缘服务器的全限定域名(fully qualified domain name，FQDN)
步骤S104，第一控制面核心网网元根据第一通知信息向UE发送第二信息。
需要说明的是，第一控制面核心网网元可以根据第一通知信息确定向哪个UE发送第二信息。
作为示例而非限定，第一控制面核心网网元可以通过会话建立接收消息向UE发送第二信息；或者，第一控制面核心网网元可以通过会话修改命令消息向UE发送第二信息，第二信息可作为一个NAS container包含于会话建立接收消息或会话修改命令消息中；或者，第一控制面核心网网元可以通过其它非接入层容器NAS消息向UE发送第二信息。
根据本申请实施例提供的向边缘服务器获取边缘服务的方法，UE通过控制面核心网网元发送相关信息，可以实现当ECS或EES属于5GC网元或AF(application function)时，UE可以通过核心网网元向边缘服务器(ECS或EES)发送信息，对应的，边缘服务器通过核心网网元向UE发送EES或EAS的标识信息，从而获取边缘服务。
图6是本申请第一个具体实施例向边缘服务器发送信息方法200的示意性流程图。图6所示的方法200可以由图1所示的系统中的AMF、SMF、NRF和ECS等网元执行。如图6所示，该方法包括S201至S211，本实施例以UE#1为例进行说明，下面详细描述每个步骤。
步骤S201，ECS可以将自身的配置信息注册到NRF。
作为示例而非限定，该配置信息可以包括ECS的服务范围以及ECS的ID等信息。
应该理解，ECS采用分布式部署的场景中，每个ECS有对应的服务范围，本实施例中包含多个边缘配置服务器，例如，ECS#1，ECS#2…ECS#n。也就是说，多个ECS可将自身的配置文件注册到NRF，其实可以包含多个边缘配置服务器将其配置信息注册到NRF。
步骤S202，UE#1可以向SMF发送第一信息，第一信息包括UE#1向边缘配置服务器发送的信息。
作为示例而非限定，UE#1可以通过会话建立请求消息、会话修改请求消息、非接入层容器NAS Container消息等向SMF发送第一信息。
作为示例而非限定，UE#1向SMF发送的第一信息可以包括：服务配置请求(service provisioning request)、服务配置订阅请求(service subscription request)、服务配置订阅更新请求(service subscription update request)、服务配置取消订阅请求(service unsubscribe request)。
在一种实现方式中，服务配置请求(service provisioning request)、服务配置订阅请 求(service subscription request)、服务配置订阅更新请求(service subscription update request)、服务配置取消订阅请求(service unsubscribe request)可以包含于会话建立请求消息或会话修改请求消息中。
作为示例而非限定，第一信息还可以包括指示信息，指示信息用于指示UE#1要获取EES的标识信息。第一信息还还可以包括应用信息，比如，application ID(例如，UE#1要连接的业务的信息)或者application client profile。第一信息还可以包括UE#1的标识信息，UE#1的标识信息可用于5GC和/或ECS对UE#1进行身份验证。第一信息还可以包括UE#1的位置信息，UE#1的位置信息可用确定于网络侧确定为UE服务的ECS和EES。UE#1的位置信息可以包括：UE#1所在的跟踪区标识(tracking area identity，TAI)和/或小区标识(cell identity，Cell ID)，或者UE#1当前(PDU会话所)对应的数据网络接入标识(date network acess identity，DNAI)等信息。
第一信息还中还可携带订阅指示，用于指示5GC和/或ECS UE#1订阅EES的改变通知，即在可用的EES信息发生变更时，将变更的EES信息通知给UE#1。其中，变更的EES信息可以为以下信息中的一个或多个：新的EES信息、旧的EES信息、相比于之前发送给UE#1的EES信息发送了变化的EES信息。
应理解，订阅指示信息可以用于指示当UE位置发生改变时可以为UE服务的边缘服务器的变更信息。也就是说订阅指示信息可以使得UE动态获取当前实时更新的可以为UE服务的服务器的信息。在一种实现方式中，订阅指示信息可以通过服务配置订阅请求(service provisioningrequest)或服务配置订阅更新请求(service subscription update request)体现。
步骤S203，SMF收到第一信息后，确定需要向ECS发送第一信息。
具体的，在一种实现方式中，SMF可以基于本地配置或根据第一信息的消息名称或根据签约信息等确定需要向ECS发送该信息。
在一些实施例中，在步骤S203中，SMF还可以检查是否允许该UE#1向边缘服务器发送信息。也就是说SMF可以检查UE#1给边缘配置服务器发送的信息是否合法。例如，SMF可根据UE#1的签约信息确定UE#1是否被允许向边缘服务器发送信息。
在一种可能的实现方式中，SMF可以先确定应该向哪个ECS发送该信息(第一信息)，也就是说，SMF可以先获取ECS(以ECS#1为例)的标识信息。
步骤S204，SMF获得ECS(以ECS#1为例)的标识信息。
需要说明的是，本申请为表述方便，以ECS#1为例，也就是说SMF获得ECS#1的标识消息。如前所述，NRF上保存或配置了ECS的地址信息以及服务范围信息等，所以SMF可以向NRF查询，确定能为UE#1所服务的ECS#1。
具体的，步骤S204a，SMF可以向NRF发送消息#1，用于请求查询ECS的信息。可选的，消息#1中可以包括UE#1的位置信息。
步骤S204b，NRF确定ECS#1的标识信息。
作为示例而非限定，NRF可以基于UE#1当前位置信息和ECS的服务范围确定目标ECS，即ECS#1。例如，ECS#1的服务范围包括区域1、区域2，而UE#1当前位置处于区域1，则NRF可以确定ECS#1为服务UE#1的ECS。
应理解，UE#1的位置信息可以是SMF上报给NRF的，NFR也可以向AMF发送请 求去查询UE#1位置信息。
步骤S204c，NRF可以向SMF发送消息#2，消息#2中包括ECS#1的标识信息。具体的，若NRF确定了目标ECS#1，则NRF向SMF发送ECS#1的标识信息(例如，ECS#1的统一资源标识符(uniform resource identifier，URI)和/或ECS#1的互联网协议IP地址信息，还可以是ECS#1的实例标识符(instance ID)等)。
在一些实施例中，还可以包括步骤S205，SMF还可以保存收到的ECS#1的标识信息，用于后续SMF接收到UE的第一信息后，检查UE的请求是否合法。
在一些实施例中，还可以包括步骤S206，ECS#1对UE#1进行认证和授权。可以采用类似现有技术中协议数据单元(protocol data unit，PDU)会话认证的方式对UE#1进行验证和授权，即，SMF为UE#1与ECS#1间的认证或授权相关的消息提供传递服务，具体可参照现有技术中第三方认证PDU会话的方法，在此不在赘述。
如上所述，SMF获取到ECS的标识信息后，可以向目标ECS(例如，ECS#1，第一边缘配置服务器的一例)发送消息#3(第一消息的一例)，消息#3中包括第一信息和第一通知信息，第一通知信息包括SMF的通知地址信息和/或UE的上下文信息。
步骤S207，SMF可以向ECS#1发送消息#3，消息#3中包括第一信息和第一通知信息，第一通知信息包括SMF的通知地址信息和/或UE的上下文信息。
SMF的通知地址信息，例如，可以是SMF的URI。
需要说明的是，本申请实施例中的第一通知信息用于指示第二信息的发送方向，例如：
在一种可能的实现方式中，当第一边缘配置服务器向核心网发送信息时，第一通知信息可以用于指示第一边缘配置服务器向第一控制面核心网网元方向发送信息。
在一另种可能的实现方式中，当第一边缘配置服务器向UE发送信息时，第一通知信息可以用于指示第一边缘配置服务器向UE方向发送信息。
在一另种可能的实现方式中，第一通知信息也可以用于指示第一边缘配置服务器通过核心网网元(例如，SMF)向UE方向发送信息，以下不在赘述。
也就是说，SMF可以向ECS#1转发所接收第一信息，并且携带第一通知信息。在本申请中，第一通知信息可以用于确定核心网网元的地址信息和/或UE的信息，例如，ECS#1可以根据第一通知地址信息确定向哪个SMF或者哪个UE发送响应消息。
也就是说，SMF可以根据步骤S204c收到的ECS#1的标识信息将第一信息发送给相应的ECS。
在一种实现方式中，SMF可以调用ECS#1的服务配置请求，比如，SMF向ECS#1发送service provisioning request消息，该消息包括：第一信息和第一通知信息。
具体的，第一信息的内容可以是步骤S202中第一信息的内容。
作为示例而非限定，消息#3的内容可以包括指示信息，指示信息用于指示UE#1要获取EES的标识信息。还可以包括UE#1的标识信息以及应用信息。消息#3的内容还可以包括UE#1的位置信息，UE#1的位置信息可用于ECS#1确定EES#1。UE#1的位置信息可以包括：UE#1所在的跟踪区标识(tracking area identity，TAI)和/或小区标识(cell identity，Cell ID)，或者UE#1当前(PDU会话所)对应的数据网络接入标识(date network acess identity，DNAI)等信息。应理解，请求#3还可携带订阅指示信息，用于订阅EES#1改变通知，例如，若在步骤S202中UE#1携带了订阅指示，则本步骤中SMF也可以携带订阅 指示信息。应理解，若SMF携带了订阅请求，则SMF还可携带SMF自身的通知地址(例如notification URI)，用于后续ECS#1向SMF发送EES#1改变通知。如前所述，本实施例中5GC核心网网元也可以不是SMF，而是AMF或PCF等其他网元，则，AMF或PCF可携带AMF或PCF自身的通知地址，用于后续ECS#1向AMF或PCF发送EES#1改变通知。
需要说明的是，SMF可以通过PCF向ECS#2发送消息#3，ECS#2也可以通过PCF接收消息#3。
步骤S208，ECS#1接收消息#3，确定消息#4。
在一种可能的实现方式中，ECS#1接收消息#3，可以根据第一信息确定UE#1想要获取信息。
作为一个示例，当第一信息包含指示信息，即，指示UE#1要获取EES的标识信息时，ECS#1需要确定EES#1的标识消息(第二信息的一例)。
具体的，ECS#1确定目标EES的可采用以下几种方式：
方式一：ECS#1根据UE#1的位置信息确定EES#1；
例如，ECS#1可以根据UE#1的位置将距离UE#1位置最近的EES确定为目标EES，即EES#1。假如EES#1的服务范围包括区域1、区域2，而UE#1当前位置处于区域1，则ECS#1可以确定EES#1为服务UE#1的EES。
方式二：ECS#1可以根据应用标识确定EES#1；
例如，ECS#1可以根据UE#1请求的应用标识信息，例如，UE#1要连接的业务的信息，将有此业务的EES确定为目标EES，即EES#1。假如EES#1管理的应用(即EAS)包括应用1、应用2，而UE#1请求的应用标识与应用1相对应，则ECS#1可以确定EES#1为服务UE#1的EES。
方式三：ECS#1可以根据负载信息确定EES#1。
例如，ECS#1可以根据管理的各EES的负载信息将负载最小或负载较小的EES确定为目标EES，即EES#1。
应理解，以上方式仅仅为举例，本实施例中ECS#1确定EES#1的方式并不限于此，本领域技术人员可以根据实际需要任意确定目标EES#1。
应理解，ECS#1确定EES#1的方式可以参见现有技术，本实施例不做限定。
应理解，在一些实施例中，如果包含了步骤S206，即ECS#1对UE#1进行认证和授权。若ECS#1对UE#1进行了认证，则可以在认证消息携带消息#3，即步骤S207可以包含在S206中。
步骤S209，ECS#1向SMF发送消息#4，消息#4包括第一通知信息和第二信息，第二信息包括ECS#1发送给UE#1的信息。应理解，ECS#1可通过PCF向SMF发送消息#4。
需要说明的是，消息#4中携带第一通知地址信息，以便于后续SMF确定向哪个UE发送第二信息。
作为一种可能的实现方式，第二信息可以是EES#1的标识信息。作为示例而非限定，EES#1的标识信息可以包括EES#1的URI和/或EES#1的互联网协议IP地址信息，还可以包括EES#1的instance ID。
作为另一种可能的实现方式，若第一信息中包含了订阅指示信息，ECS#1为了能动态 选择最适合UE#1当前位置的EES#1，需监控UE#1的位置变化。作为一个示例，ECS#1可以向SMF发送订阅请求用于订阅UE#1会话的用户面路径管理事件。应理解，当5GC为AMF时，此时ECS#1也可以向AMF发送订阅请求用于订阅UE#1的位置改变事件。
应理解，后续若UE#1的位置发生移动，导致SMF检测到DNAI change事件或AMF检测location change事件，SMF或AMF可以发送通知消息给ECS#1，ECS#1可以基于UE#1的新位置或新的DNAI确定新的EES#1。其中，EES#1可以是一个或多个EES。
针对EES#1地址信息改变通知，ECS#1可以将新(或变更后)EES#1的标识信息(第二信息的一例)发送给SMF。应理解，其中，变更的或者新的EES的标识信息可以为以下信息中的一个或多个：新的EES的标识信息、旧的EES的标识信息、相比于之前发送给UE#1的EES标识信息发送了变化的EES的标识信息。
在一些实施例中，还可以包括步骤S210，SMF保存收到的EES#1标识信息，用于后续UE#1向SMF请求EES#1信息时SMF检查请求是否合法。
需要说明的是，ECS#1可以通过PCF向SMF发送消息#4，SMF可以通过PCF接收消息#4，以下不再赘述。
步骤S211，SMF接收消息#4，根据第一通知地址信息向UE#1发送第二信息。
作为示例而非限定，SMF可以通过会话建立接收消息向UE发送第二信息；或者，SMF可以通过会话修改命令消息向UE发送第二信息；或者，SMF可以通过非接入层容器NAS Container消息向UE发送第二信息。
在一种实施方式中，SMF通过NAS消息将EES#1的标识信息发送给UE#1，例如，SMF可以向UE#1发送消息#5，消息#5包括EES#1的标识信息。对应于步骤S202，消息#5的消息名称可以包括但不限于：会话建立接收消息、会话修改命令消息或非接入层容器NAS Container消息等。
应理解，针对EES#1地址信息改变通知，SMF可通过UCU命令(UE configuration update command)消息、PDU会话修改请求消息等消息将新EES#1的标识信息(第二信息的一例)发送给UE#1。若通过PDU会话相关的消息发送EES#1的标识信息，则EES#1的标识信息可携带在协议配置选项(protocol configuration option，PCO)中发送给UE#1。
当然，在本申请实施例中，核心网也可以先把边缘服务器的标识信息发送给基站，然后基站再发送给UE#1。
根据本申请实施例的方法，UE通过控制面核心网网元发送相关信息，可以实现当ECS为核心网网元或AF时，UE通过核心网网元向ECS发送信息，对应的，ECS通过核心网网元向UE发送信息，从而获取边缘服务，对现有机制(包括UE、网络侧网元)的改动较小。另外，本申请提供的技术方案可以实现在网络侧配置ECS的地址信息，提高了边缘服务器地址配置的灵活性，保障业务体验。而且本申请实施例还可以实现当EES或EAS的地址信息有变化时，UE也可以实时获取更新后的EES或EAS的地址信息。
图7是本申请第二个具体实施例获取边缘服务方法300的示意性流程图。
应理解，本实施例中5GC核心也可以是AMF或PCF等其他5GC网元，也就是说本实施例中将SMF换做其他5GC网元也可以执行如下步骤。
图7所示的方法300可以由图1所示的系统中的AMF、SMF、NRF和ECS等网元执行。如图7所示，该方法包括步骤S301至步骤S313，本实施例以UE#2为例进行说明， 下面详细描述每个步骤。
步骤S301，ECS#2可以将自身的配置信息注册到NRF。
作为示例而非限定，该配置信息可以包括ECS的服务范围以及ECS的ID等信息。
应该理解，ECS采用分布式部署的场景中，每个ECS有对应的服务范围，本实施例中的ECS可以包含多个边缘配置服务器，例如，ECS#1，ECS#2…ECS#n。也就是说，多个ECS可将配置文件注册到NRF，其实可以包含多个边缘配置服务器将其配置文件注册到NRF。
步骤S302，UE#2可以向SMF发送第三信息，第三信息包括UE#1请求获取ECS的标识信息。
作为示例而非限定，UE#2可以通过会话建立请求消息、会话修改请求消息、非接入层容器NAS Container消息等向SMF发送第三信息。
作为示例而非限定，UE#1向SMF发送的第一信息可以包括：服务配置请求(service provisioning request)、服务配置订阅请求(service provisioning subscription request)、服务配置订阅更新请求(service provisioning subscription update request)、服务配置取消订阅请求(service provisioning unsubscribe request)。
在一种实现方式中，服务配置请求(service provisioning request)、服务配置订阅请求(service provisioning subscription request)、服务配置订阅更新请求(service provisioning subscription update request)、服务配置取消订阅请求(service provisioning unsubscribe request)可以包含于会话建立请求消息或会话修改请求消息中。
作为示例而非限定，第三信息还可以包括指示信息，用于指示UE#2要获取ECS的信息；第三信息还可以包括ECS的缺省通知地址。第三信息还可以包括UE#2的标识信息，UE#2的标识信息用于ECS对UE#2进行身份验证。第三信息还可以包括请求ECS的缺省通知地址。
步骤S303，SMF收到第三信息后，确定需要向ECS发送第三信息。
具体的，在一种实现方式中，SMF基于本地配置或根据第三信息的消息名称或根据签约信息等确定UE#2需要需要向ECS发送该信息。
在一种可能的实现方式中，SME可以先确定应该向哪个ECS发送该信息(第三信息)，也就是说，SMF可以先获取ECS(以ECS#2为例)的标识信息。
步骤S304，SMF获得ECS(以ECS#2为例)的标识信息。
具体的，步骤S304a，SMF可以向NRF发送消息#6，用于请求查询ECS信息。可选的，消息#6中包含UE#2的位置信息。
步骤S304b，NRF确定ECS#2的标识信息。具体的，NRF可以基于UE#2当前位置信息和ECS#2的服务范围确定目标ECS，即，ECS#2。例如，ECS#2的服务范围包括区域3、区域4，而UE#2当前位置处于区域4，则NRF可以确定ECS#2为服务UE#2的ECS。应理解，UE#2的位置信息可以是SMF上报给NRF的，NFR也可以向AMF发送请求去查询UE#2位置信息。
应理解，当消息#6中包括请求ECS的缺省通知地址时，此时，本步骤中NRF还可以将ECS的缺省通知地址发送给SMF。
步骤S304c，NRF可以向SMF发送消息#7，消息#7中包括ECS#2标识信息。具体的， 若NRF确定了合适的ECS#2，则NRF向SMF发送ECS#2标识信息(例如，ECS#2的URI和/或ECS#1的互联网协议IP地址信息，还可以是ECS#2的instance ID等)。
在一些实施例中，还可以包括步骤S305，SMF还可以保存收到的ECS#2的标识信息，用于后续SMF接收到UE的第三信息后，SMF检查UE的请求是否合法。
步骤S306，SMF向UE#2发送第四信息，第四信息包括ECS#2的标识信息。具体的，当有多个UE同时向SMF发送第四信息时，SMF可以通过UE的标识信息或者UE的上下文信息确定应该向哪个UE发送第四信息。
在一种实施方式中，SMF通过NAS消息将ECS#2的标识信息发送给UE#2。应理解，如果步骤S302中UE#2发送的第三消息中包括了请求ECS#2的缺省通知地址，那么在本步骤中SMF也可以将ECS#2的缺省通知地址发送给UE#2，即，第四信息中可以包括ECS#2的缺省通知地址。
作为示例而非限定，SMF元可以通过会话建立接收消息向UE发送第四信息；或者，SMF可以通过会话修改命令消息向UE发送第四信息；或者，SMF可以通过非接入层容器NAS Container消息向UE发送第四信息。
步骤S307，UE向SMF发送第五信息，第五信息包括UE#1向ECS发送的信息。
需要说明的是本实施例中的第五信息的内容可以和方法100或方法200中的第一信息包括的内容相同。
作为示例而非限定，第五信息可以包括ECS#2的标识信息，例如，ECS#2的instance ID等；第五信息还可以包括指示信息，用于指示UE#2想获取EES的信息；第五信息还可以包括UE#2发送给ECS#2的消息，例如，UE#2发送给ECS#2的service provisioning request或service provisioning subscription request。第五信息还可以包括UE#2获取EES标识信息时所需要的信息，应理解，此时，SMF需要根据上述信息生成service provisioning request消息或service provisioning subscription request消息，然后发送给ECS#2。第五信息中还可以包括ECS#2的缺省通知地址。
在一些实施例中，UE#2发送第五信息，第五信息中不包含ECS#2的标识信息，此时，SMF收到第五信息后可以根据之前保存的ECS#2标识信息(参见步骤S305)向对应的ECS#2发送消息，从而获取EES的标识信息。
应理解，第五信息中还可以包括订阅指示信息，用于订阅EES改变通知。
作为示例而非限定，第五信息也可以采用NAS container封装，即，第五信息的内容作为外层的NAS消息。应理解，UE#2与ECS#2之间的请求消息也可以采用其他格式，本实施例不限定。
在一些实施例中还包括步骤S308，SMF进行授权检查，确定是否将UE#2发送给ECS#2的消息，即，第五信息转发给ECS#2。具体的，可以基于步骤S305保存的ECS#2的标识信息做对比，若第五信息中的ECS的标识信息与保存的ECS的标识信息不一致，SMF判断UE#2的请求是非法的或无效的，则SMF可拒绝将第五信息发送给ECS#2。
如上所述，SMF获取到ECS的标识信息后，可以向目标ECS(例如，ECS#2)发送消息#8，消息#8中包括第五信息和第一通知信息，第一通知信息包括SMF的通知地址信息和/或UE的上下文信息。
步骤S309，SMF可以向ECS#2发送消息#8，消息#8(第一消息的一例)中包括第五 信息和第一通知信息，第一通知信息包括SMF的通知地址信息和/或UE的上下文信息。
其中，对应于步骤S307，消息#8可以是SMF根据第五信息生成的service provisioning request消息或service provisioning subscription request消息，也可以是第五信息中本身包含了NAS请求消息(service provisioning request消息或service provisioning subscription request消息)。
作为示例而非限定，SMF向ECS#2发送消息#8可采用以下几种方式：
方式一：SMF使用ECS#2的缺省通知地址或向ECS#2发送消息#8。
在一种实现方式中，SMF使用ECS#2的缺省通知地址向ECS#2发送该消息。应理解，当步骤S302中UE#2发送的请求#4包括了请求ECS#2的缺省通知地址，那么在步骤S304中SMF也可以获得ECS#2的缺省通知地址。此时，在本步骤中，SMF便可以使用ECS#2的缺省通知地址向ECS#2发送该消息。即SMF收到请求#4后向所述ECS的缺省通知地址发送请求#7以获取EES的标识信息。
在另外一种实现方式中，当步骤S302中UE#2发送的第三信息不包括ECS#2的缺省通知地址，而是包括ECS#2的其他标识信息，例如，ECS#2的instance ID。此时，SMF可以根据ECS#2的其他标识消息获取ECS#2的缺省通知地址，例如，SMF从本地保存的ECS#2的配置文件或从NRF获取的ECS#2的配置文件中获取ECS#2的缺省通知地址。
方式二：SMF调用ECS#2的服务配置请求向ECS#2发送消息#8。
在一种实现方式中，SMF调用ECS#2的服务配置请求向ECS#2发送消息#8。例如，ECS#2定义EES获取服务(service provisioning service)，SMF调用EES获取服务，将UE#2发送给ECS#2的消息(第五信息)发送给ECS#2，对应的，ECS#2向SMF发送可用的EES信息。在一种实现方式中，SMF可以根据ECS#2的标识获取ECS#2的服务地址信息，例如，SMF从本地保存的ECS#2的配置文件或从NRF获取的ECS#2的配置文件中获取ECS#2的地址信息。
方式三：利用service provisioning request消息或service provisioning subscription request消息发送消息#8。
在一种实现方式中，如果步骤S307中UE向SMF发送的第五信息中包括了订阅指示信息，则在本步骤中，SMF可以生成service provisioning subscriptionrequest消息发送消息#8。
在另一种实现方式中，SMF可以根据UE#2发送的信息生成service provisioning request消息或生成service provisioning subscription request消息，以便将其发送给ECS#2。此时，SMF可以模拟EEC生成service provisioning请求消息或service provisioning subscription请求消息。
在有些实施例中，消息#8还可以包括UE#2的位置信息，以便ECS#2根据UE#2的位置信息确定目标EES，即EES#2，例如，UE#1所在的TAI和/或Cell ID，或者UE#1当前PDU会话所对应的DNAI等信息。请求#7还可以包括应用信息。
应理解，如果步骤S307中UE向SMF发送的第五信息中包括订阅EES的改变通知信息，SMF可以在消息#8中携带UE#2的上下文标识信息，以便ECS#2在发送EES改变通知时可以使用该上下文标识，即，SMF将EES改变通知与该UE#2进行关联，从而可以将EES改变通知发送给对应的UE，即UE#2。
步骤S310，ECS#2接收消息#8，确定消息#9。
在一种可能的实现方式中，ECS#2接收消息#8，可以根据第五信息确定UE#2想要获取信息。
作为一个示例，当第五信息包含指示信息，即，指示UE#2要获取EES的标识信息时，ECS#2需要确定EES#2的标识消息。
作为示例而非限定，ECS#2确定目标EES(例如，EES#2)的可采用以下几种方式：
方式一：ECS#2根据UE#2的位置信息确定EES#2；
例如，ECS#2可以根据UE#2的位置将距离UE#2位置最近的EES确定为目标EES，即EES#2。假如EES#2的服务范围包括区域3、区域4，而UE#2当前位置处于区域3，则ECS#2可以确定EES#2为服务UE#2的EES。
方式二：ECS#2可以根据应用标识确定EES#2；
例如，ECS#2可以根据UE#2请求的应用标识，例如，UE#2要连接的业务的信息，将有此业务的EES确定为目标EES，即EES#2。假如EES#2管理的应用(即EAS)包括应用3、应用4，而UE#2请求的应用标识与应用4相对应，则ECS#2可以确定EES#2为服务UE#2的EES。
方式三：ECS#2可以根据负载信息确定EES#2。
例如，ECS#2可以根据管理的各EES负载信息将负载最小或负载较小的EES确定为目标EES，即EES#2。
应理解，以上方式仅仅为举例，本实施例中ECS#2确定EES#2的方式并不限于此，本领域技术人员可以根据实际需要任意确定目标EES#2。
应理解，ECS#2确定EES#2的方式也可以参见现有技术，本实施例不做限定。
步骤S311，ECS#2向SMF发送消息#10(第二消息的一例)，消息#10包括第一通知信息和第六信息，第六信息包括ECS#2发送给UE#2的信息。
需要说明的是，消息#10中携带第一通知地址信息，以便于后续SMF确定向哪个UE发送第六信息。
作为一种可能的实现方式，第六信息可以是EES#2的标识信息。作为示例而非限定，EES#2的标识信息可以包括EES#2的URI和/或EES#2的互联网协议IP地址信息，还可以包括EES#2的instance ID。
在一种实现方式中，ECS#2向SMF发送消息#10可以是NAS Containter或NAS消息。若该消息是EES改变通知消息，则通知消息中还携带UE#2的上下文标识，之后，SMF可根据UE#2的上下文标识关联到UE#2，从而将通知消息发送给UE#2。
在另一种实现方式中，ECS#2向SMF发送消息#10也可以是service provisioning response，此时，SMF需要从响应消息中获取EES#2的标识信息，之后，SMF将EES#2的标识信息通过NAS消息发送给UE#2。
若第五信息中包含了订阅指示，ECS#2为了能动态选择最适合UE#2当前位置的EES#2，需监控UE#2的位置变化。在一种实现方式中，ECS#2向SMF发送订阅请求用于订阅UE#2会话的用户面路径管理事件。应理解，当5GC为AMF时，此时ECS#2也可以向AMF发送订阅请求用于订阅UE#2的位置改变事件。
应理解，后续若UE#2的位置发生移动，导致SMF检测到DNAI change事件或AMF 检测location change事件，SMF或AMF可以发送通知消息给ECS#2，ECS#2可以基于UE#2的新位置或新的DNAI确定新的EES#2。其中，EES#2可以是一个或多个EES。
应理解，针对EES地址信息改变通知，则SMF可根据UE#2的上下文标识关联UE#2的上下文，从而可以将EES#2改变通知发送给UE#2。
在一些实施例中，还可以包括步骤S312，SMF保存收到的EES#2标识信息，用于后续UE#2向SMF请求EES#2信息时SMF检查请求是否合法。
步骤S313，SMF接收消息10，根据第一通知地址信息向UE#2发送第六信息。。
作为示例而非限定，SMF元可以通过会话建立接收消息向UE发送第六信息；或者，SMF可以通过会话修改命令消息向UE发送第六信息；或者，SMF可以通过非接入层容器NAS Container消息向UE发送第六信息。
若SMF在收到的是NAS容器或NAS消息，则SMF可直接将NAS容器发送给UE#2；若步骤S209c中，SMF在收到的是service provisioning response,则SMF可以将EES#2的标识信息封装在其他的NAS消息中发送给UE#2。
当然，在本申请实施例中，核心网也可以先把边缘服务器的标识信息发送给基站，然后基站再发送给UE#2。
根据本申请实施例的方法，UE通过控制面核心网网元发送相关信息，可以实现当ECS为核心网网元或AF时，UE通过核心网网元向ECS发送信息，对应的，ECS通过核心网网元向UE发送信息，从而获取边缘服务，对现有机制(包括UE、网络侧网元)的改动较小。另外，本申请提供的技术方案可以实现在网络侧配置ECS的地址信息，提高了边缘服务器地址配置的灵活性，保障业务体验。而且本申请实施例还可以实现当EES或EAS的地址信息有变化时，UE也可以实时获取更新后的EES或EAS的地址信息。
如前所述，涉及的5GC核心网元也可以是AMF，也就是说前面实施例的方法中将SMF换做AMF也是可以的，本实施例以5GC核心为AMF为例具体描述一下其流程。应该理解，在前面实施例所述的方法中虽然没有具体以AMF为例进行叙述，但是AMF的执行步骤和SMF的执行步骤基本类似，在个别步骤上的细微差异只要是本领域人员根据现有技术可以明白或者知道该如何变化的都在本申请的的保护范围之内。
图8是本申请第三个具体实施例获取边缘服务方法400的示意性流程图。图8所示的方法400可以由图1所示的系统中的AMF、PCF、NRF和ECS等网元执行。如图8所示，该方法包括步骤S401至步骤S411，本实施例以UE#3为例进行说明，本实施例的方法400和实施例图6的方法100类似，下面详细描述每个步骤。
步骤S401，ECS可以将自身的配置信息注册到NRF。
作为示例而非限定，该配置信息可以包括ECS的服务范围以及ECS的ID等信息。
应该理解，ECS采用分布式部署的场景中，每个ECS有对应的服务范围，本实施例中的ECS可以包含多个边缘配置服务器，例如，ECS#1，ECS#2…ECS#n。也就是说，多个ECS可将配置信息注册到NRF，其实可以包含多个边缘配置服务器将其配置文件注册到NRF。
步骤S402，UE#3可以向AMF发送第七信息(第一信息的一例)，第七信息包括UE#3向边缘配置服务器发送的信息。
作为示例而非限定，UE#3可以通过会话建立请求消息、会话修改请求消息、非接入 层容器NAS Container消息等向AMF发送第七信息。
作为示例而非限定，UE#3向AMF发送的第七信息可以包括：服务配置请求(service provisioning request)、服务配置订阅请求(service subscription request)、服务配置订阅更新请求(service subscription update request)、服务配置取消订阅请求(service unsubscribe request)。
在一种实现方式中，服务配置请求(service provisioning request)、服务配置订阅请求(service subscription request)、服务配置订阅更新请求(service subscription update request)、服务配置取消订阅请求(service unsubscribe request)可以包含于会话建立请求消息或会话修改请求消息中。
作为示例而非限定，第七信息可以包括指示信息，指示信息用于指示UE#3要获取EES的标识信息。第七信息还可以包括应用信息，比如application ID(例如，UE#3要连接的业务的信息)或者application client profile。第七信息中还可以包括UE#3的标识信息，UE#3的标识信息可用于5GC和/或ECS对UE#3进行身份验证。请求#8还可以包括请求ECS的缺省通知地址。第七信息中还可携带订阅指示，用于指示5GC和/或ECS UE#1订阅EES改变通知。第七信息还可以携带ECS的缺省通知地址。
步骤S403，AMF收到第七信息后，确定需要向ECS发送第七信息。
具体的，在一种实现方式中，AMF基于本地配置或根据第七信息的消息名称或根据签约信息等确定UE#3需要向ECS发送该信息。
在一些实施例中，在步骤S403中，AMF还可以检查是否允许该UE#3向边缘服务器发送信息。也就是说AMF可以检查UE#3给边缘配置服务器发送的信息是否合法。例如，AMF可根据UE#3的签约信息确定UE#3是否被允许向边缘服务器发送信息。
在一种可能的实现方式中，AMF可以先确定应该向哪个ECS发送该信息(第七信息)，也就是说，AMF可以先获取ECS(以ECS#3为例)的标识信息。
步骤S404，AMF获得ECS(以ECS#3为例)的标识信息。
可选的，AMF可以从NRF获取ECS#3的标识信息，具体的，步骤S404a，AMF可以向NRF发送消息#11，用于请求查询ECS的信息。
步骤S404b，NRF确定ECS#3标识信息。
作为示例而非限定，NRF可以基于UE#3当前位置信息和ECS#3的服务范围确定合适的ECS#3。应理解，UE#3的位置信息可以是AMF上报给NRF的，NFR也可以向AMF发送请求去查询UE#3位置信息。
步骤S404c，NRF可以向AMF发送消息#12，消息#12中包括ECS#3的标识信息。具体的，若NRF确定了目标ECS，即ECS#3，则NRF向AMF发送ECS#3的标识信息(例如，ECS#3的URI和/或ECS#1的互联网协议IP地址信息，还可以是ECS#3的instance ID等)。
AMF还可能通过其他方式获取ECS#3的标识信息，在一种实现方式中，第七信息中包括请求ECS的缺省通知地址，此时AMF便可获得ECS的缺省通知地址，从而获取ECS的标识信息。
在另外一种实现方式中，第七信息中不包括ECS的缺省通知地址，而是包括ECS的其他标识信息，例如，ECS的Instance ID，此时，AMF可以根据ECS的其他标识获取ECS#3 的通知地址，例如，AMF从本地保存的ECS的配置文件获取ECS#3的通知地址。
在一些实施例中，还可以包括步骤S405，AMF还可以保存收到的ECS#3的标识信息，用于后续AMF接收到UE的第七信息后，检查UE的请求是否合法。
在一些实施例中，还可以包括步骤S406，ECS#3对UE#3进行认证和授权。可以采用类似现有技术中PDU会话认证的方式对UE#3进行验证和授权，即，AMF为UE#3与ECS#3间的认证或授权相关的消息提供传递服务，具体可参照现有技术中第三方认证PDU会话的方法，在此不在赘述。
如上所述，AMF获取到ECS的标识信息后，可以向目标ECS(例如，ECS#3)发送消息#13，消息#13中包括第七信息和第一通知信息，第一通知信息包括AMF的通知地址信息和/或UE的上下文信息。
步骤S407，AMF可以向ECS#3发送消息#13，消息#13中包括第七信息和第一通知信息，第一通知信息包括AMF的通知地址信息和/或UE的上下文信息。
AMF的通知地址信息，例如，可以是AMF的URI。
也就是说，AMF可以向ECS#3转发所接收第七信息，并且携带第一通知信息。在本申请中，第一通知信息可以用于确定核心网网元的地址信息和UE的信息，例如，ECS#3可以根据第一通知地址信息确定向哪个AMF或者哪个UE发送响应消息。
在一种实现方式中，AMF可以调用ECS的服务配置请求，比如，AMF向ECS的发送的service provisioning request消息，该消息包括：第七信息和第一通知信息。
具体的，第七信息的内容可以是步骤S402中第七信息的内容。
作为示例而非限定，消息#13可以包括UE#3的标识信息以及应用信息。消息#13还可以包括UE#3的位置信息，UE#3的位置信息可用于ECS#3确定目标EES，即EES#3。UE#3的位置信息，例如，UE#3所在的TAI和/或Cell ID，或者UE#3当前PDU会话所对应的DNAI等信息。
应理解，消息#13还可携带订阅指示信息，用于订阅EES改变通知，例如，若在步骤S302中UE#3携带了订阅指示，则本步骤中AMF也可以携带订阅指示信息。若是订阅了EES#3的改变通知，则该消息中还可以携带UE#3的上下文标识，ECS#3在发送EES改变通知时可以使用该上下文标识，以便AMF和PCF将EES的改变通知与该UE#3进行关联，从而可以将EES改变通知发送给UE#3。
需要说明的是，AMF可以通过PCF和/或SMF向ECS#3发送消息#13，ECS#3也可以通过PCF和/或SMF接收消息#13。
步骤S408，ECS#3接收消息#13，确定消息#14。
在一种可能的实现方式中，ECS#3接收消息#13，可以根据第七信息确定UE#3想要获取信息。
作为一个示例，当第七信息包含指示信息，即，指示UE#3要获取EES的标识信息时，ECS#3需要确定EES#3的标识消息。
具体的，ECS#3确定目标EES(例如，EES#3)的可采用以下几种方式：
方式一：ECS#3根据UE#3的位置信息确定EES#3；
例如，ECS#3可以根据UE#3的位置将距离UE#3位置最近的EES确定为目标EES，即EES#3。假如EES#3的服务范围包括区域5、区域6，而UE#3当前位置处于区域5， 则ECS#3可以确定EES#3为服务UE#3的EES。
方式二：ECS#3可以根据应用标识确定EES#3；
例如，ECS#3可以根据UE#3的应用标识，例如，UE#3要连接的业务的信息，将有此业务的EES确定为目标EES，即EES#3。假如EES#3管理的应用(即EAS)包括应用5、应用6，而UE#1请求的应用标识与应用6相对应，则ECS#3可以确定EES#3为服务UE#3的EES。
方式三：ECS#3可以根据负载信息确定EES#3。
例如，ECS#3可以根据管理的各EES的负载信息将负载最小或负载较小的EES确定为目标EES，即EES#3。
应理解，以上方式仅仅为举例，本实施例中ECS#3确定EES#3的方式并不限于此，本领域技术人员可以根据实际需要任意确定目标EES#3。
应理解，ECS#3确定EES#3的方式可以参见现有技术，本实施例不做限定。
应理解，在一些实施例中，如果包含了步骤S206，即ECS#3对UE#3进行认证和授权。若ECS#3对UE#3进行了认证，则可以在认证消息携带消息#13，即步骤S307可以包含在S406中。
步骤S409，ECS#3向AMF发送消息#14，消息#14包括第一通知信息和第八信息，第八信息包括ECS#1发送给UE#1的信息。
需要说明的是，消息#14中携带第一通知地址信息，以便于后续AMF确定向哪个UE发送第二信息。
作为一种可能的实现方式，第八信息可以是EES#3的标识信息。作为示例而非限定，EES#3的标识信息可以包括EES#3的URI或EES#3的instance ID。
作为另一种可能的实现方式，若第七信息包含了订阅指示信息，ECS#3为了能动态选择最适合UE#3当前位置的EES#3，需监控UE#3的位置变化。在一种实现方式中，ECS#3向AMF发送订阅请求用于订阅UE#3会话的用户面路径管理事件，即，向AMF发送订阅请求用于订阅UE#3的位置改变事件。
应理解，后续若UE#3的位置发生移动，导致SMF检测到DNAI change事件或AMF检测location change事件，SMF或AMF可以发送通知消息给ECS#3，ECS#3可以基于UE#3的新位置或新的DNAI确定新的EES#3。其中，EES#3可以是一个或多个EES。
针对EES#3地址信息改变通知，ECS#3可以将将新(或变更后)EES#3的标识信息(第二信息的一例)发送给AMF。应理解，其中，变更的或者新的EES的标识信息可以为以下信息中的一个或多个：新的EES的标识信息、旧的EES的标识信息、相比于之前发送给UE#3的EES标识信息发送了变化的EES的标识信息。
在一些实施例中，还可以包括步骤S410，AMF保存收到的EES#3标识信息，用于后续UE#3向AMF请求EES#3信息时AMF检查请求是否合法。
步骤S411，AMF接收消息#14，根据第一通知地址信息向UE#3发送第八信息。
作为示例而非限定，AMF可以通过会话建立接收消息向UE发送第二信息；或者，AMF可以通过会话修改命令消息向UE发送第二信息；或者，AMF可以通过非接入层容器NAS Container消息向UE发送第二信息。
根据本申请实施例的方法，UE通过控制面核心网网元发送相关信息，可以实现当ECS 为核心网网元或AF时，UE通过核心网网元向ECS发送信息，ECS通过核心网网元向UE发送信息，给予NAS协议，从而获取边缘服务，对现有机制(包括UE、网络侧网元)的改动较小。另外，本申请提供的技术方案可以实现在网络侧配置ECS的地址信息，提高了边缘服务器地址配置的灵活性，保障业务体验。而且本申请实施例还可以实现当EES或EAS的地址信息有变化时，UE也可以实时获取更新后的EES或EAS的地址信息。
本实施例的应用场景可以是在前面实施例之后进行，即UE获得了EES的标识信息后，UE进一步向目标EES(以EES#4为例)发送请求，用于请求应用服务器EAS的标识信息。
应理解，UE获得了EES标识信息的方法可以采用本申请的方法，也可以采用现有技术的方法，在本实施例中对UE获取了EES的标识信息的方法并不做任何限定。
图9是本申请第四个具体实施例获取边缘服务方法500的示意性流程图。应理解，本实施例中5GC核心也可以是AMF，也就是说本实施例中将SMF换做AMF也可以执行如下步骤，不再赘述。
图9所示的方法500可以由图1所示的系统中的AMF、SMF、NRF和EES等网元执行。如图9所示，该方法包括步骤S501至步骤S507，下面详细描述每个步骤。
步骤S501，UE#4获得EES#4的标识信息。
如前所述，UE#4获得EES#4标识信息的方法可以采用本申请的方法，也可以采用按照现有技术的方法，在本实施例中对UE#4获取EES#4地址信息的方法并不做任何限定。
步骤S502，UE#4向SMF发送第九信息，第九信息包括UE#4向边缘使能服务器发送的信息。
作为示例而非限定，UE#4可以通过会话建立请求消息、会话修改请求消息、非接入层容器NAS Container消息等向AMF发送第九信息。
作为示例而非限定，第九信息可以包括指示信息，指示信息用于指示UE#4想获取EAS的标识信息；第九信息还可以包括EES#4标识信息；第九信息还可以包括应用信息，比如所要发现的应用标识、所要发现的类似的应用、应用客户端的配置文件等中的至少一项。
应理解，第九信息中还包含订阅指示信息，用于指示SMF或EES#4向UE#4订阅EAS改变通知。
应理解，第九信息中还可以包含EES#4的标识信息。
UE#4也可以将需要发送给EES#4的信息封装到NAS容器中，以便SMF将NAS容器中的信息转发给EES#4。
步骤S503，SMF接收第九信息，确定需要向EES发送第九信息。
具体的，在一种实现方式中，SMF基于本地配置或根据第九信息的消息名称或根据签约信息等确定UE#4需要向EES发送该信息。
在一些实施例中还包括步骤S504，SMF进行授权检查。
具体的，可以基于历史保存的EES#4的标识信息做对比，若第九信息中的EES#4的标识信息与保存的EES#4的标识信息不一致，SMF判断UE#4的请求是非法的或无效的，则SMF可拒绝将第九信息发送给EES#4。
在一种可能的实现方式中，SMF可以先确定应该向哪个EES发送该信息(第九信息)，也就是说，SMF可以先获取EES(以ECS#3为例)的标识信息。
步骤S505，SMF向EES#4发送消息#15，消息#15中包括第九信息和第一通知信息，第一通知信息包括SMF的通知地址信息和/或UE的上下文信息。
SMF的通知地址信息，例如，可以是SMF的URI。
也就是说，SMF可以向EES#4转发所接收第九信息，并且携带第一通知信息。在本申请中，第一通知信息可以用于确定核心网网元的地址信息和UE的信息，例如，EES#4可以根据第一通知地址信息确定向哪个SMF或者哪个UE发送响应消息。
在一种实现方式中，SMF可以基于步骤S502收到的EES#4的标识信息将EAS发现请求发送给EES#4；或者，按照本申请实施例的方法，若SMF保存了ECS#4发送的EES#4的标识信息，则SMF也可以根据历史保存的EES#4的标识信息将EAS发现请求发送给EES#4。
作为示例而非限定，SMF向EES#4发送消息#15，消息#15的发送也可以采用以下几种方式：
方式一：SMF使用EES#4的缺省通知地址向EES#4发送消息#15。
在一种实现方式中，SMF使用EES#4的缺省通知地址向EES#4发送该消息。应理解，当步骤S502中UE#4发送的第九信息包括了请求EES#4的缺省通知地址，那么SMF也可以获得EES#4的缺省通知地址。此时，在本步骤中，SMF便可以使用ECS#4的缺省通知地址向ECS#4发送该消息。
在另外一种实现方式中，当步骤S502中UE#4发送的第九信息不包括EES#4的缺省通知地址，而是包括EES#4的其他标识信息，例如，EES#4的instance ID。此时，SMF可以根据EES#4的其他标识消息获取EES#4的通知地址，例如，SMF从本地保存的EES#4的配置文件或从NRF获取的EES#4的配置文件中获取EES#4的通知地址，SMF便可以使用ECS#4的通知地址向ECS#4发送该消息。
方式二：SMF调用EES#4的服务向EES#4发送消息#14。
在一种实现方式中，SMF调用EES#4的服务向EES#4发送消息#14。例如，EES#4定义应用发现服务(EAS discovery service)，SMF调用应用发现服务，将UE#4发送给EES#4的消息发送给EES#4。在一种实现方式中，SMF可以根据EES#4的标识获取EES#4的服务地址信息，例如，SMF从本地保存的EES#4的配置文件或从NRF获取的ECS#2的配置文件中获取EES#4的地址信息。
方式三：利用service provisioning request消息或service provisioning subscription request消息发送消息#14。
方式四：第九信息中还可以包含EES#4的标识信息，SMF使用该EES#4的标识信息向EES#4发送该消息。
在一种实现方式中，如果步骤S502中UE向SMF发送的第九信息中包括了订阅指示，则在本步骤中，SMF可以生成EAS discovery请求消息发送消息#15。
在另一种实现方式中，SMF可以根据UE#2发送的信息生成EAS discovery request消息，以便将其发送给EES#4。此时，SMF可以模拟EEC生成EAS discoveryrequest消息。
在有些实施例中，消息#15还可以包括UE#4的位置信息，以便EES根据UE#4的位置信息确定目标EAS，即EAS#1。UE#4的位置信息可以包括，例如，UE#4所在的TAI和/或Cell ID，或者UE#4当前(PDU会话所)对应的DNAI等信息。消息#15还可以包 括应用信息。
应理解，如果步骤S502中UE向SMF发送第九信息中订阅了EAS的改变通知，则本步骤中，SMF也可以携带了订阅请求，若SMF携带了订阅请求，则SMF还可携带通知地址，用于EES#4发送EAS改变通知。
步骤S506，EES#4接收消息#15，确定消息#16。
在一种可能的实现方式中，EES#4接收消息#15，可以根据第九信息确定UE#4想要获取信息。
作为一个示例，当第九信息包含指示信息，即，指示UE#4要获取EAS的标识信息时，EES#4需要确定EAS#1的标识消息。
具体的，EES#4确定目标EAS(例如，EAS#1)的可采用以下几种方式：
方式一：EES#4根据UE#4的位置信息确定EAS#1；
例如，EES#4可以根据UE#4的位置将距离UE#4位置最近的EAS确定为目标EAS，即EAS#1。假如EAS#1的服务范围包括区域7、区域8，而UE#4当前位置处于区域7，则EES#4可以确定EAS#1为服务UE#4的EAS。
方式二：EES#4可以根据应用标识确定EAS#1；
例如，EES#4可以根据UE#4请求的应用标识，例如，UE#4要连接的业务的信息，将有此业务的EAS确定为目标EAS，即EAS#1。假如EAS#1管理的应用包括应用7、应用8，而UE#4请求的应用标识与应用8相对应，则EES#4可以确定EAS#1为服务UE#4的EAS。
方式三：EES#4可以根据负载信息确定EAS#1。
例如，EES#4可以根据管理的各EAS的负载信息将负载最小或负载较小的EAS确定为目标EAS，即EAS#1。
应理解，以上方式仅仅为举例，本实施例中EES#1确定EAS#1的方式并不限于此，本领域技术人员可以根据实际需要任意确定目标EAS#1。
应理解，EES#1确定EAS#1的方式可以参见现有技术，本实施例不做限定。
步骤S507，EES#4向SMF发送响应#16，消息#16包括第一通知信息和第十信息，第十信息包括EES#1发送给UE#4的信息。
需要说明的是，消息#16中携带第一通知地址信息，以便于后续AMF确定向哪个UE发送第十信息。
作为一种可能的实现方式，第十信息可以是EAS#1的标识信息。作为示例而非限定，EAS#1的标识信息可以包括EAS#1的URI或EAS#1的instance ID。
作为另一种可能的实现方式，若第九信息包含了订阅指示信息，EES#4为了能动态选择最适合UE#4当前位置的EAS#1，需监控UE#4的位置变化。在一种实现方式中，EES#4向SMF发送订阅请求用于订阅UE#4会话的用户面路径管理事件。应理解，当5GC为AMF时，此时EES#4也可以向AMF发送订阅请求用于订阅UE#4的位置改变事件。
应理解，后续若UE#4的位置发生移动，导致SMF检测到DNAI change事件或AMF检测location change事件，SMF或AMF可以发送通知消息给EES#4，EES#4可以基于UE#4的新位置或新的DNAI确定新的EAS#1。其中，EAS#1可以是一个或多个EAS。
针对EAS#1地址信息改变通知，EES#4可以将将新(或变更后)EAS#1的标识信息(第 二信息的一例)发送给AMF。应理解，其中，变更的或者新的EAS的标识信息可以为以下信息中的一个或多个：新的EAS的标识信息、旧的EAS的标识信息、相比于之前发送给UE#4的EAS标识信息发送了变化的EAS的标识信息。
步骤S507，SMF接收消息#16，根据第一通知地址信息向EAS#1发送第十信息。
作为示例而非限定，SMF可以通过会话建立接收消息向UE发送第十信息；或者，SMF可以通过会话修改命令消息向UE发送第十信息；或者，SMF可以通过非接入层容器NAS Container消息向UE发送第十信息。
如前所述，5GC核心也可以是AMF，也就是说本实施例的方法中将SMF换做AMF也是可以的。应该理解，在本实施例所述的方法中虽然没有具体以AMF为例进行叙述，但是AMF的执行步骤和SMF的执行步骤基本类似，在个别步骤上的细微差异只要是本领域人员根据现有技术可以明白或者知道该如何变化的都在本申请的的保护范围之内。
根据本申请实施例的方法，UE通过控制面核心网网元发送相关信息，可以实现当ECS为核心网网元或AF时，UE通过核心网网元向ECS发送信息从而获取边缘服务，对应的，ECS通过核心网网元向UE发送信息，对现有机制(包括UE、网络侧网元)的改动较小。另外，本申请提供的技术方案可以实现在网络侧配置ECS的地址信息，提高了边缘服务器地址配置的灵活性，保障业务体验。而且本申请实施例还可以实现当EES或EAS的地址信息有变化时，UE也可以实时获取更新后的EES或EAS的地址信息。
本实施例的应用场景可以是UE获得了目标ECS的标识信息后，给目标ECS发送订阅请求，该订阅请求用于订阅EES改变通知。需要说明的是，ECS给UE发送的订阅通知消息可以通过NAS消息。
应理解，UE获得了ECS标识信息的方法可以采用本申请的方法，也可以按照现有技术的方法，在本实施例中对UE获取ECS标识信息的方法并不做任何限定。
还应理解，UE给目标ECS发送订阅请求的方法可以采用现有技术的方法，也可以采用本申请实施中的方法。即可以通过HTTP协议发送订阅请求也可以采用NAS协议发送订阅请求，在本实施例中对UE给ECS发送订阅请求的方法不做任何限定。
应理解，UE可以在位置发生变化的时候向核心网或者向边缘服务器(以ECS为例)发送订阅请求，UE也可以在向核心网发送信息时，在该信息中包含订阅请求。
图10是本申请实施例提供的一种获取边缘服务方法600的示意性流程图。本实施例中以UE#5为例，UE#5向5G核心网(5G Core，5GC)发送订阅EES地址变更请求。对应的ECS#5检测到当前为UE#5所服务的EES(以EES#5为例)的地址有变更时，给5GC发送订阅变更通知，然后5GC将新的EES#5的标识信息发送给UE#5。
需要说明的是，本申请实施例中EES#5也可以指变更后的EES，以下不再赘述。
应理解，本申请实施例以UE获取EES的变更信息为例，对于UE获取EAS的地址变更通知的过程和步骤和本实施例基本类似，只需对应的将ECS换成EES，EES的变更订阅换成EAS的变更即可，不再赘述。
应理解，本申请前面几个实施例的方法中UE获取EES变更通知也可以按照本实施例的方法执行。
应理解，本实施例中5GC核心可以是SMF，也可以是AMF，还可以是PCF或者NEF。
图10所示的方法600可以由图1所示的系统中的AMF、SMF、PCF、NEF和ECS 等网元执行。如图10所示，该方法包括步骤S601至步骤S605，下面详细描述每个步骤。
在一些实施例中，可以包括步骤S601，UE#5获取ECS#5的标识信息。
作为示例而非限定，ECS#5的标识信息可以包括ECS#5的URI或ECS#5的Instance ID；还可以包括ECS#5的地址信息。
在一些实施例中还可以包括步骤S602，UE#5获取AMF或SMF或PCF的notification URI。
在一种实现方式中，AMF或SMF在会话建立响应或会话修改请求等消息中将AMF或SMF或PCF的notification URI发送给UE#5。在另一种实现方式中，AMF或SMF或PCF的notification URI和ECS#5的标识信息可以在同一个消息中发送给UE#5。可选的，UE#5还可以获取一个token，用于后续SMF做校验。
步骤S603，UE#5向ECS#5发送EES变更订阅请求。
可选的，UE#5可以通过核心网网元向ECS#5发送EES变更订阅请求。UE#5也可以直接向ECS#5发送EES变更订阅请求。
该变更订阅请求消息也可以称为service provisioning subscribe request，用于向ECS#5订阅EES的变更信息。
该请求消息可以包括指示信息，指示信息用于指示ECS#5通过5GC给UE#5发送通知；该请求消息还可以包括AMF或SMF或PCF的notification URI，后续ECS#5检测到EES的地址信息有变更时，ECS#5通过该notification URI给SMF或AMF或PCF发通知。请求消息中还可以包括UE#5的IP地址。请求消息中还可以包括token信息。在一种实现方式中，AMF或SMF或PCF在收到请求消息后，封装上自身的notification URI。在另一种实现方式中，UE在发送请求时，就包含了AMF或SMF或PCF的notification URI。
步骤S604，ECS#5检测事件。
需要说明的是，这里的事件可以是EES#5地址变更事件，满足EES#5更新的触发条件。
ECS#5为了能动态选择最适合UE#5当前位置的EES，需监控UE#5的位置变化。在一种实现方式中，ECS#5(可能通过PCF)向SMF发送订阅请求用于订阅UE#5会话的用户面路径管理事件。应理解，ECS#5也可以向AMF发送订阅请求用于订阅UE#5的位置改变事件。应理解，后续若UE#5的位置发生移动，导致SMF检测到DNAI change事件或AMF检测location change事件，SMF或AMF可以发送通知消息给ECS#5，ECS#5可以基于UE#5的新位置或新的DNAI确定新的EES#5。其中，EES#5可以是一个或多个EES。
步骤S605，ECS#5将EES#5变更后的信息发送给UE#5。
其中，变更的EES#5的地址信息可以包含在service provisioning notification消息中。可选的，ECS#5还可以发送步骤S503接收的token信息。ECS#5将变更的EES#5的信息(比如新的EES#5的信息，旧的EES#5的信息等)发送给UE#5，包括如下三种方式。
方式一：
步骤S605a1，ECS#5根据UE#5的IP地址确定服务UE#5的PCF，ECS#5将变更的EES#5的信息发送给PCF。在一种实现方式中，ECS#5可以通过NEF发送给PCF；在另一种实现方式中，ECS#5可以将变更后的EES#5的标识信息直接发送给PCF。在另一种 实现方式中，ECS#5可以通过NEF发送给PCF。
步骤S605b1，PCF可以通过IP地址确定服务UE#5的SMF，PCF将变更的EES#5的标识信息发送给SMF。
步骤S605c1，SMF再将变更的EES#5的标识信息发送给UE#5；或者，PCF通过AMF将变更的EES#5的标识信息发送给UE#5，具体的，可以通过UE Configuration Update流程下发给UE#5。
方式二：
步骤S605a2，假如步骤S503中请求消息里还包括AMF/SMF/PCF notification URI，ECS#5可以基于该notification URI给AMF/SMF/PCF发送变更的EES#5的标识信息。其中，变更后的EES#5的标识信息可以包含在service provisioning notification消息中。
步骤S605b2，AMF/SMF/PCF可以根据该notification URI关联到UE#5，然后将变更的EES#5的标识信息发送给UE#5。在一种实现方式中，变更的EES#5的标识信息可以通过PDU session establishment accept或PDU session modification request等消息由SMF发送给UE#5。在一些实施例中，SMF也可以根据notification URI和ECS#5地址计算一个校验码，然后SMF校验是不是合法，若不合法，SMF拒绝将变更的EES#5的标识信息发送给UE#5。
方式三：
步骤S605a3，ECS#5调用NEF的服务，将更新的EES#5的标识信息发送给NEF，同时还包含UE#5的标识(例如，UE#5的互联网协议(internet protocol，IP)地址或通用公共用户标识generic public subscription identifier，GPSI))。
步骤S605b3，在一种实现方式中，若UE#5的标识为GPSI，NEF可以根据GPSI确定服务UE#5的PCF，具体的，NEF可以通过UDR通知PCF有新的EES#5的标识信息。在另一种实现方式中，若UE的标识为IP地址，NEF确定服务UE#5的PCF，同方式一，不再赘述。
步骤S605c3，PCF(通过AMF)将新的EES#5的标识信息发送给UE#5。PCF将变更的EES#5的标识信息发送给UE，
在另一种实现方式中，ECS#5可以基于步骤S603中的指示信息，指示信息用于指示ECS#5通过5GC给UE#5发送通知，确定将变更的EES#5的标识信息发送给5GC网元(上述方式中所提及的NEF或PCF或SMF或AMF)，再由5GC网元发送给UE#5。
根据本申请实施例的方法，可以实现当EES或EAS的标识信息有变化时，UE也可以实时获取更新后的EES或EAS的标识信息，提高了UE向边缘服务器发送信息的灵活性，保障了业务体验。
图11是本申请提供的第六个具体实施例获取边缘服务器方法700的示意性流程图。图11所示的方法700可以由图1所示的系统中的AMF、SMF、NEF、PCF、UDR和ECS等网元执行。如图7所示，该方法包括步骤S701至步骤S710，本实施例以UE#6为例进行说明，下面详细描述每个步骤。
步骤701，ECS将自身的配置信息提供给5GC(例如PCF和/或SMF)。
具体的，该配置信息可以先通过请求#1发送到NEF，例如，请求#1可以是Nnef_Tra fficInfluence_Create/udpate请求。
作为示例而非限定，该配置信息可以包括以下信息中的一项或多项：ECS的服务范围、数据网络名称(data networkname，DNN)、单一网络切片选择辅助信息(single network slice selection assistance information，S-NSSAI)、DNAI以及ECS的地址。
应该理解，ECS采用分布式部署的场景中，每个ECS可以有对应的服务范围，本实施例中可以包含多个边缘配置服务器，例如，ECS#1，ECS#2…ECS#n。
本步骤中，ECS还可以向核心网订阅通知消息，例如，ECS向核心网提供通知地址，以便核心网向ECS发送通知消息。
可选的，ECS的配置信息也可以预先配置在5GC网元(例如配置在PCF、SMF或UDR中)，对此不作限定。
步骤702，NEF将ECS的配置信息保存到UDR。
在一些实施例中还可以包括步骤703，UDR将ECS配置信息发送给PCF。
在一种实现方式中，PCF可以提前向UDR订阅ECS的变更信息，当UDR收到或者保存了新的ECS的配置信息时，UDR会将新的ECS的配置信息通知给PCF和/或SMF，对应的，PCF和/或SMF上保存或配置新的ECS的配置信息。
在另一种实现方式，可让UDR在收到新的ECS的配置信息时，UDR主动将将ECS的配置信息通知给PCF。可选的，PCF可以将ECS配置信息发送到SMF。值得注意的是，ECS配置信息可以配置到PCF上，也可以配置到SMF，或者同时配置到SMF和PCF上，本申请不做限定。若在步骤S701中，ECS向核心网订阅通知消息，则PCF可根据DNN、S-NSSAI、DNA或ECS的服务范围确定向哪些SMF发送订阅请求，以便SMF在收到UE的信息时可以直接向ECS发送通知，或者通过PCF向ECS发送通知。
步骤S704，UE#6向5GC(以SMF为例)发送第十一信息，第十一信息包括UE#6向边缘配置服务器发送的信息。
作为示例而非限定，UE#6可以通过会话建立请求消息、会话修改请求消息、非接入层容器NAS Container消息等向SMF发送第十一信息。
作为示例而非限定，UE#6向SMF发送的第十一信息可以包括：服务配置请求(service provisioning request)、服务配置订阅请求(service provisioning subscription request)、服务配置订阅更新请求(service provisioning subscription update request)、服务配置取消订阅请求(service provisioning unsubscribe request)。
在一种实现方式中，服务配置请求(service provisioning request)、服务配置订阅请求(service provisioning subscription request)、服务配置订阅更新请求(service provisioning subscription update request)、服务配置取消订阅请求(service provisioning unsubscribe request)可以包含于会话建立请求消息或会话修改请求消息中。
在另一种实现方式中，服务配置请求(service provisioning request)、服务配置订阅请求(service provisioning subscription request)、服务配置订阅更新请求(service provisioning subscription update request)、服务配置取消订阅请求(service provisioning unsubscribe request)可以作为一个新的NAS消息。
作为示例而非限定，第十一信息还可以包括指示信息，指示信息用于指示UE#6要获取EES的标识信息。第十一信息还可以包括应用信息，比如，application ID(例如，UE#1要连接的业务的信息)或者application client profile。第十一信息还可以包括UE#6的标识 信息，UE#6的标识信息可用于5GC和/或ECS对UE#6进行身份验证。第十一信息还可以包括UE#6的位置信息，UE#1的位置信息可用确定于网络侧确定为UE服务的ECS和EES。UE#6的位置信息可以包括：UE#6所在的跟踪区标识(tracking area identity，TAI)和/或小区标识(cell identity，Cell ID)，或者UE#6当前(PDU会话所)对应的数据网络接入标识(date network acess identity，DNAI)等信息。
第十一信息还中还可携带订阅指示，用于指示5GC和/或ECS UE#6订阅EES的改变通知，即在可用的EES信息发生变更时，将变更的EES信息通知给UE#1。其中，变更的EES信息可以为以下信息中的一个或多个：新的EES信息、旧的EES信息、相比于之前发送给UE#1的EES信息发送了变化的EES信息。
应理解，订阅指示信息可以用于指示当UE位置发生改变时可以为UE服务的边缘服务器的变更信息。也就是说订阅指示信息可以使得UE动态获取当前实时更新的可以为UE服务的服务器的信息。在一种实现方式中，订阅指示信息可以通过服务订阅请求(service provisioning request)或服务订阅更新请求(service subscription update request)体现。
在一种可能的实现方式中，第十一信息还可以包括DNN，S-NSSAI等信息。
步骤S705，SMF接收第十一信息，确定需要向ECS发送第十一信息。
具体的，在一种实现方式中，SMF可以基于本地配置或根据第十一信息的消息名称或根据签约信息等确定需要向ECS发送该信息。
在一种可能的实现方式中，SMF可以先确定应该向哪个ECS发送该信息(第一信息)，也就是说，SMF可以先获取ECS(以ECS#1为例)的标识信息。
步骤S706，SMF获得ECS(以ECS#6为例)的标识信息。
在一种可能的实现方式中，若SMF保存或配置了ECS的配置信息，或者SMF从PCF获取了ECS配置信息，则SMF可根据UE位置和ECS的服务范围确定一个ECS，例如，ECS#6。
在一种可能的实现方式中，SMF可以将第十一信息发送给PCF，在PCF配置了ECS配置信息的情况下，可以由PCF根据UE位置和ECS的服务范围确定一个ECS，例如，ECS#6。
本实施例中由于5GC核心网中已经保存了ECS的配置信息，因此，SMF或PCF或AMF可以确定目标ECS，例如，ECS#6。
步骤S707，SMF可以向ECS#6发送消息#17，消息#17中包括第十一信息。
应理解，若在步骤S706中，是PCF确定ECS#6的标识信息时，本步骤中可以是PCF向ECS#6发送消息#17。
需要说明的是，SMF也可以通过PCF向ECS#6发送消息#17。
消息#17中还可以包括UE的IP地址、DNN、S-NSSAI。在一种可能的实现方式中，该消息可以为Npcf_PolicyAuthorization_Notify请求。
步骤S708，ECS#6接收消息#17，确定消息#18。
在一种可能的实现方式中，ECS#6接收消息#17，可以根据第十一信息确定UE#6想要获取信息。
作为一个示例，当第十一信息包含指示信息，即，指示UE#6要获取EES的标识信息 时，ECS#6需要确定EES#6的标识消息。
具体的，ECS确定EES#6的标识消息可参见方法200、方法300或方法400，不在赘述。
同时，本步骤中ECS还可以根据UE的IP地址、DNN、S-NSSAI建立一个应用功能网元AF会话，该AF会话与UE的IP地址和/或DNN、S-NSSAI对应的PDU会话绑定。例如，ECS可以发送Npcf_PolicyAuthorization_Create消息给PCF以便建立该AF会话。
步骤S709，ECS#6向PCF发送消息#18，消息#18包括第十二信息，第十二信息包括ECS#6发送给UE#6的信息。
作为一种可能的实现方式，第十二信息可以是EES#6的标识信息。作为示例而非限定，EES#6的标识信息可以包括EES#6的URI、FQDN和/或EES#6的互联网协议IP地址信息，还可以包括EES#6的instance ID。
在一种可能的实现方式中，ECS#6可以向PCF发送Npcf_PolicyAuthorization_Create请求消息，该消息包含了第十二信息。
在一种可能的实现方式中，ECS#6可以通过步骤S708建立的AF session向PCF发送消息#18，例如，ECS给PCF发送Npcf_PolicyAuthorization_update消息，该消息中包括了第十二信息。
若第十一信息中包含了订阅指示，ECS#6为了能动态选择最适合UE#6当前位置的E ES#6，需监控UE#6的位置变化或会话路径变化。在一种实现方式中，ECS#6向SMF发送订阅请求用于订阅UE#6会话的用户面路径管理事件。或者，ECS#6也可以向AMF发送订阅请求用于订阅UE#6的位置改变事件。
应理解，后续若UE#6的位置发生移动，导致SMF检测到DNAI change事件或AMF检测location change事件，SMF或AMF可以发送通知消息给ECS#6，ECS#6可以基于U E#6的新位置或新的DNAI确定新的EES#6。其中，EES#6可以是一个或多个EES。
步骤S710，PCF接收消息#18，向UE#6发送第十二信息。
需要说明的是，由于在步骤S708中ECS根据UE的IP地址、DNN、S-NSSAI建立一个AF会话，并且该AF会话与UE的IP地址和/或DNN、S-NSSAI对应的PDU会话绑定，因此，本步骤中，PCF可以确定向哪个UE发送第十二信息。
应理解，PCF接收消息#18后还可以通过SMF向UE#6发送第十二信息。
应理解，本实施例的方法700也可以和前所述的各个实施例方法的步骤之间结合使用，例如，本实施例的方法700也可以实现UE获取EAS的标识信息。
根据本申请实施例的方法，UE通过控制面核心网网元发送相关信息，可以实现当ECS为核心网网元或AF时，UE通过核心网网元向ECS发送信息从而获取边缘服务，对应的，ECS通过核心网网元向UE发送信息，对现有机制(包括UE、网络侧网元)的改动较小。另外，本申请提供的技术方案可以实现在网络侧配置ECS的地址信息，提高了边缘服务器地址配置的灵活性，保障业务体验。而且本申请实施例还可以实现当EES或EAS的地址信息有变化时，UE也可以实时获取更新后的EES或EAS的地址信息。
应该理解，本申请中描述的各个实施例可以为独立的方案，也可以根据内在逻辑进行组合，这些方案都落入本申请的保护范围中。
应该理解，本申请实施例中的第一控制面核心网网元仅仅是以SMF、AMF、PCF以 及涉及到的相关网元为例，不应对本申请构成任何限定。本申请并不排除在其它应用场景中使用其中之一或者多个实现相同或相似功能的可能，本申请也并不排除在其它应用场景中使用其它一个或者多个网元实现相同或相似功能的可能。
还应理解，在本申请的各种实施例中，各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
上面结合图5至图11分别从单个设备的执行动作以及各个设备之间的交互行为介绍
本申请实施例提供的通信方法。下面结合图12至图14介绍本申请实施例提供的获取边缘服务的装置。应理解，装置实施例的描述与方法实施例的描述相互对应，因此，未详细描述的内容可以参见上文方法实施例，为了简洁，这里不再赘述。
上述主要从各个网元之间交互的角度对本申请实施例提供的方案进行了介绍。可以理解的是，各个网元，为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对发射端设备或者接收端设备进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。下面以采用对应各个功能划分各个功能模块为例进行说明。
图12是本申请实施例提供的获取边缘服务的装置100的示意性框图。如图所示，该装置100可以包括：收发单元110和处理单元120。
在一种可能的设计中，该装置100可以是上文方法实施例中的第一控制面核心网网元，也可以是用于实现上文方法实施例中第一控制面核心网网元的功能的芯片。
应理解，该装置100可对应于根据本申请实施例的方法100中的第一控制面核心网网元、方法200中的SMF网元、方法300中的SMF网元、方法400中的AMF网元、方法500中的SMF网元、方法600中的SMF网元以及方法700中的SMF网元，该装置100可以包括用于执行图5中的方法100的第一控制面核心网网元执行的方法的单元、图6中的方法200的SMF执行的方法的单元、图7中的方法300的SMF执行的方法的单元、图8中方法400的AMF执行的方法的单元、图9中的方法500的SMF执行的方法的单元、图10中的方法600的SMF执行的方法的单元、图11中的方法700的SMF执行的方法的单元。并且，该装置100中的各单元和上述其他操作和/或功能分别为了实现图5中的方法100、图6中的方法200、图7中的方法300、图8中方法400、图9中方法500、图10中方法600、图11中方法700的相应流程。应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
图13是本申请实施例提供的获取边缘服务的装置200的示意性框图。如图所示，该 装置200可以包括：收发单元210和处理单元220。
在一种可能的设计中，该装置200可以是上文方法实施例中的第一边缘配置服务器网元，也可以是用于实现上文方法实施例中第一边缘配置服务器网元的功能的芯片。
应理解，该装置200可对应于根据本申请实施例的方法100中的第一边缘配置服务器、方法200中的ECS#1网元、方法300中的ECS#2网元、方法400中的ECS#3网元、方法600中的ECS#5网元以及方法700中的ECS#6网元，该装置200可以包括用于执行图5中的方法100的第一边缘配置服务器执行的方法的单元、图6中的方法200的ECS#1执行的方法的单元、图7中的方法300的ECS#2执行的方法的单元、图8中方法400的ECS#3执行的方法的单元、图10中的方法600的ECS#5执行的方法的单元、图11中的方法700的ECS#6执行的方法的单元。并且，该装置200中的各单元和上述其他操作和/或功能分别为了实现图5中的方法100、图6中的方法200、图7中的方法300、图8中方法400、图10中方法600、图11中方法700的相应流程。应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
在另一种可能的设计中，该装置200可以是上文方法实施例中的网络存储功能网元，也可以是用于实现上文方法实施例中网络存储功能网元的功能的芯片。
应理解，该装置200可对应于根据本申请实施例的方法200中的NRF网元、方法300中的NRF网元、方法400中的NRF网元以及方法500中的NRF网元，该装置200可以包括用于执行图6中的方法200的NRF执行的方法的单元、图7中的方法300的NRF执行的方法的单元、图8中方法400的NRF执行的方法的单元以及图9中的方法500的NRF执行的方法的单元。并且，该装置200中的各单元和上述其他操作和/或功能分别为了实现图6中的方法200、图7中的方法300、图8中方法400、图9中方法500的相应流程。应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
图14是本申请实施例提供的获取边缘服务的设备300的结构框图。图14所示的设备300包括：处理器310、存储器320和收发器330。该处理器310与存储器耦合，用于执行存储器中存储的指令，以控制收发器330发送信号和/或接收信号。
还应理解，该设备300中的收发器330可对应于图12示出的收发单元110和图13示出的收发单元210；该设备300中的处理器310可对应于图12示出的处理单元120和图13示出的处理单元220。
应理解，上述处理器310和存储器320可以合成一个处理装置，处理器310用于执行存储器320中存储的程序代码来实现上述功能。具体实现时，该存储器320也可以集成在处理器310中，或者独立于处理器310。应理解，处理器310也可以和前面装置中的各个处理单元相对应，收发器330可以和前面装置中的各个接收单元和各个发送单元相对应。
还应理解，收发器330可以包括接收器(或者称，接收机)和发射器(或者称，发射机)。收发器还可以进一步包括天线，天线的数量可以为一个或多个。收发器330还可以是通信接口或者接口电路。
在一种可能的设计中，该设备300可以是上文方法实施例中的第一控制面核心网网元，也可以是用于实现上文方法实施例中第一控制面核心网网元的功能的芯片。
具体的，该设备300可对应于根据本申请实施例的方法100中的第一控制面核心网网 元、方法200中的SMF网元、方法300中的SMF网元、方法400中的AMF网元、方法500中的SMF网元、方法600中的SMF网元以及方法700中的SMF网元，该设备300可以包括用于执行图5中的方法100的第一控制面核心网网元执行的方法的单元、图6中的方法200的SMF执行的方法的单元、图7中的方法300的SMF执行的方法的单元、图8中方法400的AMF执行的方法的单元、图9中的方法500的SMF执行的方法的单元、图10中的方法600的SMF执行的方法的单元、图11中的方法700的SMF执行的方法的单元。并且，该设备300中的各单元和上述其他操作和/或功能分别为了实现图5中的方法100、图6中的方法200、图7中的方法300、图8中方法400、图9中方法500、图10中方法600、图11中方法700的相应流程。应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
在一种可能的设计中，该设备300可以是上文方法实施例中的第一边缘配置服务器网元，也可以是用于实现上文方法实施例中第一边缘配置服务器网元的功能的芯片。
具体的，该设备300可对应于根据本申请实施例的方法100中的第一边缘配置服务器、方法200中的ECS#1网元、方法300中的ECS#2网元、方法400中的ECS#3网元、方法600中的ECS#5网元以及方法700中的ECS#6网元，该设备300可以包括用于执行图5中的方法100的第一边缘配置服务器执行的方法的单元、图6中的方法200的ECS#1执行的方法的单元、图7中的方法300的ECS#2执行的方法的单元、图8中方法400的ECS#3执行的方法的单元、图10中的方法600的ECS#5执行的方法的单元、图11中的方法700的ECS#6执行的方法的单元。并且，该设备300中的各单元和上述其他操作和/或功能分别为了实现图5中的方法100、图6中的方法200、图7中的方法300、图8中方法400、图10中方法600、图11中方法700的相应流程。应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
在另一种可能的设计中，该设备300可以是上文方法实施例中的网络存储功能网元，也可以是用于实现上文方法实施例中网络存储功能网元的功能的芯片。
具体的，该设备300可对应于根据本申请实施例的方法方法200中的NRF网元、方法300中的NRF网元、方法400中的NRF网元以及方法500中的NRF网元，该设备300可以包括用于执行图6中的方法200的NRF执行的方法的单元、图7中的方法300的NRF执行的方法的单元、图8中方法400的NRF执行的方法的单元以及图9中的方法500的NRF执行的方法的单元。并且，该设备300中的各单元和上述其他操作和/或功能分别为了实现图6中的方法200、图7中的方法300、图8中方法400、图9中方法500的相应流程。应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
根据本申请实施例提供的方法，本申请还提供一种计算机程序产品，该计算机程序产品包括：计算机程序代码，当该计算机程序代码在计算机上运行时，使得该计算机执行图5、图6、图7、图8、图9、图10、图11所示实施例中任意一个实施例的方法。
根据本申请实施例提供的方法，本申请还提供一种计算机可读介质，该计算机可读介质存储有程序代码，当该程序代码在计算机上运行时，使得该计算机执行图5、图6、图7、图8、图9、图10、图11所示实施例中任意一个实施例的方法。
根据本申请实施例提供的方法，本申请还提供一种系统，其包括前述的第一控制面核 心网网元、第一边缘配置服务器。该系统还可以包括第三核心网网元。
根据本申请实施例提供的方法，本申请还提供一种系统，其包括前述的第一控制面核心网网元、第二边缘配置服务器。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，高密度数字视频光盘(digital video disc，DVD))、或者半导体介质(例如，固态硬盘(solid state disc，SSD))等。
上述各个装置实施例中网络侧设备与终端设备和方法实施例中的网络侧设备或终端设备对应，由相应的模块或单元执行相应的步骤，例如通信单元(收发器)执行方法实施例中接收或发送的步骤，除发送、接收外的其它步骤可以由处理单元(处理器)执行。具体单元的功能可以参考相应的方法实施例。其中，处理器可以为一个或多个。
在本说明书中使用的术语“部件”、“模块”、“系统”等用于表示计算机相关的实体、硬件、固件、硬件和软件的组合、软件、或执行中的软件。例如，部件可以是但不限于，在处理器上运行的进程、处理器、对象、可执行文件、执行线程、程序和/或计算机。通过图示，在计算设备上运行的应用和计算设备都可以是部件。一个或多个部件可驻留在进程和/或执行线程中，部件可位于一个计算机上和/或分布在两个或更多个计算机之间。此外，这些部件可从在上面存储有各种数据结构的各种计算机可读介质执行。部件可例如根据具有一个或多个数据分组(例如来自与本地系统、分布式系统和/或网络间的另一部件交互的二个部件的数据，例如通过信号与其它系统交互的互联网)的信号通过本地和/或远程进程来通信。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组 件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-onlymemory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (51)

  1. 一种获取边缘服务的方法，其特征在于，包括：
    第一控制面核心网网元接收用户设备UE的第一信息；
    所述第一控制面核心网网元向第一边缘配置服务器发送第一消息，所述第一消息包括所述第一信息和第一通知信息，所述第一通知信息包括所述第一控制面核心网网元的通知地址信息和/或所述UE的上下文信息；
    所述第一控制面核心网网元接收所述第一边缘配置服务器根据所述第一消息发送的第二消息，所述第二消息包括所述第一通知信息和第二信息；
    所述第一控制面核心网网元根据所述第一通知信息向所述UE发送所述第二信息。
  2. 根据权利要求1所述的方法，其特征在于，所述第一通知信息用于指示所述第二信息的发送方向。
  3. 根据权利要求1或2所述的方法，其特征在于，所述第一控制面核心网网元接收用户设备UE的第一信息，包括：
    所述第一控制面核心网网元通过会话建立请求消息接收用户设备UE的第一信息；或者，
    所述第一控制面核心网网元通过会话修改请求消息接收用户设备UE的第一信息；或者，
    所述第一控制面核心网网元通过非接入层容器NAS Container消息接收用户设备UE的第一信息。
  4. 根据权利要求1至3中任一项所述的方法，其特征在于，所述第一信息包括至少以下一项：服务配置请求、服务配置订阅请求、服务配置订阅更新请求、服务配置取消订阅请求。
  5. 根据权利要求1至4中任一项所述的方法，其特征在于，所述第一控制面核心网网元根据所述第一通知信息向所述UE发送所述第二信息，包括：
    所述第一控制面核心网网元根据所述第一通知信息通过会话建立接收消息向所述UE发送所述第二信息；或者，
    所述第一控制面核心网网元根据所述第一通知信息通过会话修改命令消息向所述UE发送所述第二信息；或者，
    所述第一控制面核心网网元根据所述第一通知信息通过非接入层容器NAS Container消息向所述UE发送所述第二信息。
  6. 根据权利要求1至5中任一项所述的方法，其特征在于，所述第一控制面核心网网元向第一边缘配置服务器发送第一消息，包括：所述第一控制面核心网网元通过第二核心网网元向所述第一边缘配置服务器发送第一消息。
  7. 根据权利要求1至6中任一项所述的方法，其特征在于，所述第一控制面核心网网元接收所述第一边缘配置服务器的第二消息，包括：所述第一控制面核心网网元通过第二核心网网元接收所述第一边缘配置服务器的第二消息。
  8. 根据权利要求1至7中任一项所述的方法，其特征在于，所述方法还包括：
    所述第一控制面核心网网元向第三核心网网元发送第三消息，所述第三消息用于请求获取边缘配置服务器的标识信息，所述标识信息包括所述边缘配置服务器的统一资源标识符和/或所述边缘配置服务器的互联网协议IP地址信息；
    所述第一控制面核心网网元接收第三核心网网元的第四消息，所述第四消息包括第一边缘配置服务器的标识信息。
  9. 根据权利要求8所述的方法，其特征在于，所述第三消息包括所述UE的位置信息，所述UE的位置信息用于所述第三核心网网元确定所述第一边缘配置服务器，所述UE的位置信息包括至少以下一项：所述UE的跟踪区标识、所述UE的小区标识或所述UE的数据网络接入标识。
  10. 根据权利要求1至9中任一项所述的方法，其特征在于，所述第一信息还包括所述第一边缘配置服务器的标识信息，所述第一控制面核心网网元向第一边缘配置服务器发送第一消息，包括：
    所述第一控制面核心网网元根据所述第一边缘配置服务器的标识信息向所述第一边缘配置服务器发送第一消息。
  11. 根据权利要求1至10中任一项所述的方法，其特征在于，当所述第一信息包括所述UE请求获取边缘使能服务器的标识消息时，所述第二信息还包括第一边缘使能服务器的标识消息，
    所述标识信息包括至少以下一项：统一资源标识符信息、实例标识符信息或互联网协议IP地址信息。
  12. 根据权利要求1至11中任一项所述的方法，其特征在于，所述第二信息包括第一边缘使能服务器的标识消息，所述方法还包括：
    所述第一控制面核心网网元接收所述UE的第三信息，所述第三信息包括所述UE向所述第一边缘使能服务器发送的信息；
    所述第一控制面核心网网元向所述第一边缘使能服务器发送第五消息，所述第五消息包括所述第三信息和第一通知信息，所述第一通知信息包括所述第一控制面核心网网元的通知地址信息和/或所述UE的上下文信息；
    所述第一控制面核心网网元接收所述第一边缘使能服务器的第六消息，所述第六消息包括所述第一通知信息和第四信息，所述第四信息包括第一边缘应用服务器的标识信息；
    所述第一控制面核心网网元根据所述第一通知信息向所述UE发送所述第四信息。
  13. 根据权利要求1至12中任一项所述的方法，其特征在于，所述第一控制面核心网网元接收所述第一边缘配置服务器的第二消息，所述第二消息包括所述第一通知信息和第二信息，所述第二信息包括所述第一边缘配置服务器发送给所述UE的信息，所述方法还包括：所述第一控制面核心网网元保存所述第二信息。
  14. 根据权利要求1至13中任一项所述的方法，其特征在于，所述第一控制面核心网网元包括：会话管理功能网元或接入和移动性管理功能网元或策略控制网元。
  15. 一种获取边缘服务的方法，其特征在于，包括：
    第一边缘配置服务器接收第一控制面核心网网元的第一消息，所述第一消息包括第一信息和第一通知信息，所述第一通知信息包括所述第一控制面核心网网元的通知地址信息和/或所述UE的上下文信息；
    所述第一边缘配置服务器根据所述第一信息确定所述第二消息，所述第二消息包括所述第一通知信息和第二信息，所述第二信息包括所述第一边缘配置服务器发送给所述UE的信息；
    所述第一边缘配置服务器向所述第一控制面核心网网元发送第二消息。
  16. 根据权利要求15所述的方法，其特征在于，所述第一通知信息用于指示所述第二信息的发送方向。
  17. 根据权利要求15或16所述的方法，其特征在于，所述第一信息包括至少以下一项：服务配置请求、服务配置订阅请求、服务配置订阅更新请求、服务配置取消订阅请求。
  18. 根据权利要求15至16中任一项所述的方法，其特征在于，所述第一边缘配置服务器接收第一控制面核心网网元的第一消息，包括：
    所述第一边缘配置服务器通过第二核心网网元接收第一控制面核心网网元的第一消息。
  19. 根据权利要求15至18中任一项所述的方法，其特征在于，所述第一边缘配置服务器向所述第一控制面核心网网元发送第二消息，包括：
    所述第一边缘配置服务器通过第二核心网网元向所述第一控制面核心网网元发送第二消息。
  20. 根据权利要求15至19中任一项所述的方法，其特征在于，当所述第一信息包括所述UE请求获取边缘使能服务器的标识消息时，所述第二信息还包括第一边缘使能服务器的标识消息，所述标识信息包括至少以下一项信息：统一资源标识符信息、实例标识符信息或互联网协议IP地址信息。
  21. 根据权利要求15至20中任一项所述的方法，其特征在于，所述第一控制面核心网网元包括：会话管理功能网元或接入和移动性管理功能网元或策略控制网元。
  22. 一种获取边缘服务的方法，其特征在于，包括：
    第三核心网网元接收第一控制面核心网网元的第三消息，所述第三消息用于请求获取边缘配置服务器的标识信息，所述标识信息包括所述边缘配置服务器的统一资源标识符和/或所述边缘配置服务器的互联网协议IP地址信息；
    所述第三核心网网元根据所述第三消息确定第四消息，所述第四消息包括第一边缘配置服务器的标识信息；
    所述第三核心网网元向所述第一控制面核心网网元发送所述第四信息。
  23. 根据权利要求22所述的方法，其特征在于，所述第三消息包括所述UE的位置信息，所述UE的位置信息用于所述第三核心网网元确定所述第一边缘配置服务器，所述UE的位置信息包括至少以下一项：所述UE的跟踪区标识、所述UE的小区标识或所述UE的数据网络接入标识。
  24. 根据权利要求22或23所述的方法，其特征在于，所述第一控制面核心网网元包括：会话管理功能网元或接入和移动性管理功能网元或策略控制网元。
  25. 一种获取边缘服务的装置，其特征在于，包括收发单元：
    所述收发单元用于接收用户设备UE的第一信息；
    所述收发单元还用于向第一边缘配置服务器发送第一消息，所述第一消息包括所述第一信息和第一通知信息，所述第一通知信息包括所述第一控制面核心网网元的通知地址信 息和/或所述UE的上下文信息；
    所述收发单元还用于接收所述第一边缘配置服务器的第二消息，所述第二消息包括所述第一通知信息和第二信息，所述第二信息包括所述第一边缘配置服务器发送给所述UE的信息；
    所述收发单元还用于根据所述第一通知信息向所述UE发送所述第二信息。
  26. 根据权利要求25所述的装置，其特征在于，所述第一通知信息用于指示所述第二信息的发送方向。
  27. 根据权利要求25或26所述的装置，其特征在于，所述收发单元用于接收用户设备UE的第一信息，包括：
    所述收发单元通过会话建立请求消息接收用户设备UE的第一信息；或者，
    所述收发单元通过会话修改请求消息接收用户设备UE的第一信息；或者，
    所述收发单元通过非接入层容器NAS Container消息接收用户设备UE的第一信息。
  28. 根据权利要求25至27中任一项所述的装置，其特征在于，所述第一信息包括至少以下一项：服务配置请求、服务配置订阅请求、服务配置订阅更新请求、服务配置取消订阅请求。
  29. 根据权利要求25至28中任一项所述的装置，其特征在于，所述收发单元还用于接收所述第一边缘配置服务器的第二消息，包括：
    所述收发单元根据所述第一通知信息通过会话建立接收消息向所述UE发送所述第二信息；或者，
    所述收发单元根据所述第一通知信息通过会话修改命令消息向所述UE发送所述第二信息；或者，
    所述收发单元根据所述第一通知信息通过非接入层容器NAS Container消息向所述UE发送所述第二信息。
  30. 根据权利要求25至29中任一项所述的装置，其特征在于，所述收发单元还用于向第一边缘配置服务器发送第一消息，包括：所述收发单元通过第二核心网网元向所述第一边缘配置服务器发送第一消息。
  31. 根据权利要求25至30中任一项所述的装置，其特征在于，所述收发单元还用于接收所述第一边缘配置服务器的第二消息，包括：所述收发单元通过第二核心网网元接收所述第一边缘配置服务器的第二消息。
  32. 根据权利要求25至31中任一项所述的装置，其特征在于，
    所述收发单元还用于向第三核心网网元发送第三消息，所述第三消息用于请求获取边缘配置服务器的标识信息，所述标识信息包括所述边缘配置服务器的统一资源标识符和/或所述边缘配置服务器的互联网协议IP地址信息；
    所述收发单元还用于接收第三核心网网元的第四消息，所述第四消息包括第一边缘配置服务器的标识信息。
  33. 根据权利要求32所述的装置，其特征在于，所述第三消息包括所述UE的位置信息，所述UE的位置信息用于确定所述第一边缘配置服务器，所述UE的位置信息包括至少以下一项：所述UE的跟踪区标识、所述UE的小区标识或所述UE的数据网络接入标识。
  34. 根据权利要求25至33中任一项所述的装置，其特征在于，所述第一信息还包括所述第一边缘配置服务器的标识信息，所述收发单元还用于向第一边缘配置服务器发送第一消息，包括：
    所述收发单元还用于根据所述第一边缘配置服务器的标识信息向所述第一边缘配置服务器发送第一消息。
  35. 根据权利要求25至34中任一项所述的装置，其特征在于，当所述第一信息包括所述UE请求获取边缘使能服务器的标识消息时，所述第二信息还包括第一边缘使能服务器的标识消息，
    所述标识信息包括至少以下一项：统一资源标识符信息、实例标识符信息或互联网协议IP地址信息。
  36. 根据权利要求25至35中任一项所述的装置，其特征在于，所述第二信息还包括第一边缘使能服务器的标识消息，
    所述收发单元还用于向所述第一边缘使能服务器发送第五消息，所述第五消息包括所述第三信息和第一通知信息，所述第三信息包括所述UE向所述第一边缘使能服务器发送的信息，所述第一通知信息包括所述第一控制面核心网网元的通知地址信息和/或所述UE的上下文信息；
    所述收发单元还用于接收所述第一边缘使能服务器的第六消息，所述第六消息包括所述第一通知信息和第四信息，所述第四信息包括第一边缘应用服务器的标识信息；
    所述收发单元还用于根据所述第一通知信息向所述UE发送所述第三信息。
  37. 根据权利要求25至36中任一项所述的装置，其特征在于，所述收发单元还用于接收所述第一边缘配置服务器的第二消息，所述第二消息包括所述第一通知信息和第二信息，所述第二信息包括所述第一边缘配置服务器发送给所述UE的信息；
    所述装置还包括处理单元，所述处理用于保存所述第二信息。
  38. 根据权利要求25至37中任一项所述的装置，其特征在于，所述第一控制面核心网网元包括：会话管理功能网元或接入和移动性管理功能网元或策略控制网元。
  39. 一种获取边缘服务的装置，其特征在于，包括收发单元和处理单元：
    所述收发单元用于接收第一控制面核心网网元的第一消息，所述第一消息包括第一信息和第一通知信息，所述第一通知信息包括所述第一控制面核心网网元的通知地址信息和/或所述UE的上下文信息；
    所述处理单元用于根据所述第一信息确定所述第二消息，所述第二消息包括所述第一通知信息和第二信息，所述第二信息包括所述第一边缘配置服务器发送给所述UE的信息；
    所述收发单元还用于向所述第一控制面核心网网元发送第二消息。
  40. 根据权利要求39所述的装置，其特征在于，所述第一通知信息用于指示所述第二信息的发送方向。
  41. 根据权利要求39或40所述的装置，其特征在于，所述第一信息包括至少以下一项：服务配置请求、服务配置订阅请求、服务配置订阅更新请求、服务配置取消订阅请求。
  42. 根据权利要求39至41中任一项所述的装置，其特征在于，所述收发单元用于接收第一控制面核心网网元的第一消息，包括：
    所述收发单元通过第二核心网网元接收第一控制面核心网网元的第一消息。
  43. 根据权利要求39至42中任一项所述的装置，其特征在于，所述收发单元还用于向所述第一控制面核心网网元发送第二消息，包括：
    所述收发单元还用于通过第二核心网网元向所述第一控制面核心网网元发送第二消息。
  44. 根据权利要求39至43中任一项所述的装置，其特征在于，当所述第一信息为所述UE请求获取边缘使能服务器的标识消息时，所述第二信息还包括第一边缘使能服务器的标识消息，所述标识信息包括至少以下一项信息：统一资源标识符信息、实例标识符信息或互联网协议IP地址信息。
  45. 根据权利要求39至44中任一项所述的装置，其特征在于，所述第一控制面核心网网元包括：会话管理功能网元或接入和移动性管理功能网元或策略控制网元。
  46. 一种获取边缘服务的装置，其特征在于，包括收发单元和处理单元：
    所述收发单元用于接收第一控制面核心网网元的第三消息，所述第三消息用于请求获取边缘配置服务器的标识信息，所述标识信息包括所述边缘配置服务器的统一资源标识符和/或所述边缘配置服务器的互联网协议IP地址信息；
    所述处理单元用于根据所述第三消息确定第四消息，所述第四消息包括第一边缘配置服务器的标识信息；
    所述收发单元还用于向所述第一控制面核心网网元发送所述第四信息。
  47. 根据权利要求46所述的装置，其特征在于，所述第三消息包括所述UE的位置信息，所述UE的位置信息用于确定所述第一边缘配置服务器，所述UE的位置信息包括至少以下一项：所述UE的跟踪区标识、所述UE的小区标识或所述UE的数据网络接入标识。
  48. 根据权利要求46或47所述的装置，其特征在于，所述第一控制面核心网网元包括：会话管理功能网元或接入和移动性管理功能网元或策略控制网元。
  49. 一种计算机可读存储介质，其特征在于，其上存储有计算机程序，所述计算机程序被执行时，
    使得执行如权利要求1至14中任一项所述的方法；或者，
    使得执行如权利要求15至21任一项所述的方法；或者，
    使得执行如权利要求22至24中任一项所述的方法。
  50. 一种芯片系统，其特征在于，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片系统的设备执行如权利要求1至14中任意一项所述的方法；或者，使得安装有所述芯片系统的设备执行如权利要求15至21中任意一项所述的方法；或者，使得安装有所述芯片系统的设备执行如权利要求22至24中任意一项所述的方法。
  51. 一种获取边缘服务的系统，包括：用于执行如权利要求1至14中任一项所述的方法的第一控制面核心网网元以及用于与该第一控制面核心网网元进行通信的第一边缘配置服务器。
PCT/CN2021/114172 2020-11-10 2021-08-24 获取边缘服务的方法和装置 WO2022100197A1 (zh)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN202011250645 2020-11-10
CN202011250645.2 2020-11-10
CN202110065138.XA CN114466346A (zh) 2020-11-10 2021-01-18 获取边缘服务的方法和装置
CN202110065138.X 2021-01-18

Publications (1)

Publication Number Publication Date
WO2022100197A1 true WO2022100197A1 (zh) 2022-05-19

Family

ID=81405420

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/114172 WO2022100197A1 (zh) 2020-11-10 2021-08-24 获取边缘服务的方法和装置

Country Status (2)

Country Link
CN (1) CN114466346A (zh)
WO (1) WO2022100197A1 (zh)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020197288A1 (ko) * 2019-03-28 2020-10-01 삼성전자 주식회사 Edge computing 서비스를 이용하기 위하여 단말에 연결성을 제공하는 방법 및 장치
WO2020204474A1 (ko) * 2019-03-29 2020-10-08 삼성전자 주식회사 무선 통신 시스템에서 에지 컴퓨팅 서비스를 제공하기 위한 장치 및 방법

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020197288A1 (ko) * 2019-03-28 2020-10-01 삼성전자 주식회사 Edge computing 서비스를 이용하기 위하여 단말에 연결성을 제공하는 방법 및 장치
WO2020204474A1 (ko) * 2019-03-29 2020-10-08 삼성전자 주식회사 무선 통신 시스템에서 에지 컴퓨팅 서비스를 제공하기 위한 장치 및 방법

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
CONVIDA WIRELESS LLC, AT&T, SAMSUNG: "KI #1, New Sol: Edge Configuration Server Based Discovery", 3GPP DRAFT; S2-2003774, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Electronic Meeting; 20200601 - 20200612, 22 May 2020 (2020-05-22), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051889798 *
CONVIDA WIRELESS LLC, AT&T, SAMSUNG: "KI #1, Solution #16 Update", 3GPP DRAFT; S2-2007333, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Electronic Meeting; 20201012 - 20201023, 2 October 2020 (2020-10-02), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051938373 *

Also Published As

Publication number Publication date
CN114466346A (zh) 2022-05-10

Similar Documents

Publication Publication Date Title
US11653296B2 (en) Isolated network slice selection
JP7041212B2 (ja) 仮想化されたモバイルコアネットワークへの接続
US20240187303A1 (en) Method and apparatus for obtaining edge service
US20200196130A1 (en) Ue configuration and update with network slice selection policy
WO2023280121A1 (zh) 一种获取边缘服务的方法和装置
KR20200136985A (ko) 통신 방법 및 장치
AU2021221761B2 (en) Selection of ip version
WO2023030369A1 (zh) 通信感知业务中选择网元的方法、通信装置和通信系统
WO2023030368A1 (zh) 对终端设备进行感知的方法和通信装置
CN115299127A (zh) 无线通信系统中用于提供低时延位置信息服务的装置和方法
US11503533B2 (en) Method of registration with access and mobility management function re-allocation
US11729599B2 (en) Communication system
US20230247094A1 (en) Methods, architectures, apparatuses and systems directed to transaction management in blockchain-enabled wireless systems
US20230132454A1 (en) Method and apparatus for supporting edge computing service for roaming ue in wireless communication system
WO2022199451A1 (zh) 会话切换的方法和装置
US20240155325A1 (en) Information obtaining method and apparatus, and system
WO2022100197A1 (zh) 获取边缘服务的方法和装置
WO2022241704A1 (en) Method, device, and system for core network device re-allocation in wireless network
KR20220135130A (ko) 무선 통신 시스템에서 세션 관리를 위한 방법 및 장치
EP4451715A1 (en) Communication method and apparatus
WO2023015973A1 (zh) 一种网络切片准入控制方法和装置
WO2024146315A1 (zh) 通信方法和通信装置
US20240187532A1 (en) Systems and methods for generating network policy decisions for data sessions
WO2024032041A1 (zh) 通信方法和通信装置
US20240380848A1 (en) Communication method and apparatus

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: 21890726

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21890726

Country of ref document: EP

Kind code of ref document: A1