WO2022100197A1 - Procédé et appareil d'obtention de service périphérique - Google Patents

Procédé et appareil d'obtention de service périphérique 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)
Chinese (zh)
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/fr

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

La présente demande concerne un procédé et un appareil permettant d'obtenir un service périphérique. Le procédé comprend les étapes suivantes : un premier élément de réseau central de plan de commande reçoit des premières informations d'un équipement utilisateur (UE) ; le premier élément de réseau central de plan de commande envoie un premier message à un premier serveur de configuration de périphérie, le premier message comprenant les premières informations et des premières informations de notification, les premières informations de notification comprenant des informations d'adresse de notification du premier élément de réseau central de plan de commande et/ou des informations de contexte de l'UE ; le premier élément de réseau central de plan de commande reçoit un second message du premier serveur de configuration de périphérie, le second message comprenant les premières informations de notification et des secondes informations, les secondes informations comprenant des informations envoyées par le premier serveur de configuration de périphérie à l'UE ; le premier élément de réseau central de plan de commande envoie les secondes informations à l'UE en fonction des premières informations de notification, ce qui peut permettre à l'UE d'envoyer des informations à un serveur de périphérie au moyen de l'élément de réseau central, de façon à obtenir un service périphérique.
PCT/CN2021/114172 2020-11-10 2021-08-24 Procédé et appareil d'obtention de service périphérique WO2022100197A1 (fr)

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 (fr) 2022-05-19

Family

ID=81405420

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/114172 WO2022100197A1 (fr) 2020-11-10 2021-08-24 Procédé et appareil d'obtention de service périphérique

Country Status (2)

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

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020197288A1 (fr) * 2019-03-28 2020-10-01 삼성전자 주식회사 Procédé et dispositif pour fournir une connectivité à un terminal afin d'utiliser un service informatique périphérique
WO2020204474A1 (fr) * 2019-03-29 2020-10-08 삼성전자 주식회사 Dispositif et procédé permettant de fournir un service d'informatique en périphérie dans un système de communication sans fil

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020197288A1 (fr) * 2019-03-28 2020-10-01 삼성전자 주식회사 Procédé et dispositif pour fournir une connectivité à un terminal afin d'utiliser un service informatique périphérique
WO2020204474A1 (fr) * 2019-03-29 2020-10-08 삼성전자 주식회사 Dispositif et procédé permettant de fournir un service d'informatique en périphérie dans un système de communication sans fil

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
JP7041212B2 (ja) 仮想化されたモバイルコアネットワークへの接続
US11653296B2 (en) Isolated network slice selection
WO2023280121A1 (fr) Procédé et appareil d'obtention de service de périphérie
KR20200136985A (ko) 통신 방법 및 장치
US20200196130A1 (en) Ue configuration and update with network slice selection policy
KR20230149345A (ko) 무선 통신 시스템에서 등록 및 세션 관리를 처리하기 위한 방법 및 시스템
AU2021221761B2 (en) Selection of ip version
US11503533B2 (en) Method of registration with access and mobility management function re-allocation
CN115299127A (zh) 无线通信系统中用于提供低时延位置信息服务的装置和方法
US11729599B2 (en) Communication system
US20230247094A1 (en) Methods, architectures, apparatuses and systems directed to transaction management in blockchain-enabled wireless systems
WO2023030369A1 (fr) Procédé de sélection d'élément de réseau dans un service de détection de communication, dispositif de communication et système de communication
WO2022199451A1 (fr) Procédé et appareil de commutation de session
US20230370992A1 (en) Method, device, and system for core network device re-allocation in wireless network
US20230132454A1 (en) Method and apparatus for supporting edge computing service for roaming ue in wireless communication system
WO2023030368A1 (fr) Procédé de détection d'équipement utilisateur, et appareil de communication
WO2022100197A1 (fr) Procédé et appareil d'obtention de service périphérique
KR20220135130A (ko) 무선 통신 시스템에서 세션 관리를 위한 방법 및 장치
US20240155325A1 (en) Information obtaining method and apparatus, and system
WO2023015973A1 (fr) Procédé et appareil de commande d'admission à une tranche de réseau
WO2023143212A1 (fr) Procédé et appareil de communication
US20240187303A1 (en) Method and apparatus for obtaining edge service
US20240187532A1 (en) Systems and methods for generating network policy decisions for data sessions
WO2024032041A1 (fr) Procédé de communication et appareil de communication
WO2023193584A1 (fr) Procédé et appareil de positionnement

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