WO2023280121A1 - 一种获取边缘服务的方法和装置 - Google Patents

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

Info

Publication number
WO2023280121A1
WO2023280121A1 PCT/CN2022/103724 CN2022103724W WO2023280121A1 WO 2023280121 A1 WO2023280121 A1 WO 2023280121A1 CN 2022103724 W CN2022103724 W CN 2022103724W WO 2023280121 A1 WO2023280121 A1 WO 2023280121A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
edge configuration
configuration server
edge
network element
Prior art date
Application number
PCT/CN2022/103724
Other languages
English (en)
French (fr)
Inventor
姚琦
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2023280121A1 publication Critical patent/WO2023280121A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/50—Service provisioning or reconfiguring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition

Definitions

  • the present application relates to the communication field, and more specifically, to a method and device for obtaining edge services.
  • the user equipment (user equipment, UE) generally adopts the following scheme to obtain the address information of the edge configuration server (edge configuration server, ECS): the ECS can first send its address information to the unified data management network element (unified data management, UDM ), when the UE requests the address information of the ECS from the session management function network element (session management function, SMF), the SMF can determine the address of the ECS according to the local configuration or obtain the subscription data of the UE from the UDM, and then the SMF will set the address of the ECS The information is sent to the UE.
  • unified data management network element unified data management, UDM
  • SMF session management function network element
  • the network side can only determine one ECS address and send it to the UE.
  • the SMF obtains multiple ECS addresses according to the local configuration or from the UDM, the SMF cannot determine which/which ECS to send to the UE; The UE cannot determine which ECS to access to obtain the edge configuration information, resulting in poor experience of UE edge services.
  • This application provides a method and device for obtaining edge services.
  • the UE or the network side can determine the ECS, thereby ensuring user experience of edge services.
  • a method for obtaining an edge service includes: a user equipment UE receives policy information corresponding to at least two edge configuration servers from a first network element, and the policy information includes the first edge configuration server of each edge configuration server.
  • the first type of information includes one or more of the following information: information on the service scope, priority information, and identification information corresponding to each edge configuration server; UE according to the first type of information in the policy information , determining a first edge configuration server among at least two edge configuration servers.
  • the UE in a multi-ECS scenario, can receive policy information, which includes service range information corresponding to each ECS, or priority information, or identification information, so that the UE can operate on multiple ECS Determine the target ECS that needs to be accessed, which ensures the user's edge service experience. It solves the problem in the prior art that the UE cannot determine the target ECS in a multi-ECS scenario.
  • the policy information in this application may be user routing policy URSP.
  • the policy information in this application includes at least information corresponding to two edge configuration servers.
  • the policy information may include: service range information, priority information, and identification information of each edge configuration server.
  • the first type of information in the policy information can be used by the UE to subsequently determine the target ECS that needs to be accessed. Therefore, the content of the first type of information in the policy information can be flexibly determined, and the above cases are just examples and not limited.
  • the policy information further includes the second type of information of each edge configuration server, and the second type of information includes the data network name corresponding to each edge configuration server information and/or single network slice selection auxiliary information
  • the method further includes: the UE requests to establish a protocol data unit PDU session corresponding to the first edge configuration server according to the second type of information in the policy information; The UE accesses the first edge configuration server through the PDU session.
  • the policy information can also include the second type of information, and the UE can assist in establishing a PDU session according to the second type of information in the policy information, so that the UE can access the target edge configuration server and ensure the user's edge service experience .
  • the second type of information in the policy information may be used by the UE to subsequently establish a PDU session for determining the target ECS. Therefore, the content of the second type of information in the policy information can be flexibly determined, and the above cases are just examples and not limited.
  • the policy information includes priority information of each edge configuration server, and the UE, according to the second type of information in the policy information, in the at least Determining the first edge configuration server among the two edge configuration servers includes: if the priorities of the multiple edge configuration servers are different, the UE determines the edge configuration server with the highest priority as the first edge configuration server.
  • the UE can determine the first ECS among multiple ECSs according to the priority information of each edge configuration server, so as to ensure the experience of the user's edge service.
  • the policy information includes priority information and service scope information of each edge configuration server
  • determining the first edge configuration server among the at least two edge configuration servers includes: if multiple edge configuration servers have the same priority, the UE determines the first edge configuration server according to the service scope of the edge configuration server and the location information of the UE Edge configuration server.
  • the UE can determine the first ECS among multiple ECSs according to the priority information and service scope information of each edge configuration server, so as to ensure user experience of edge services.
  • the UE requesting to establish a protocol data unit PDU session corresponding to the first edge configuration server according to the second type of information in the policy information includes: the The UE sends a session establishment request to the second network element, where the session establishment request includes the data network name corresponding to the first edge configuration server and/or single network slice selection auxiliary information.
  • the UE can send a session establishment request to the AMF, thereby establishing a PDU session of the first edge configuration server, thereby accessing the first edge configuration server through the PDU session, ensuring user experience of edge services.
  • the session establishment request further includes: first indication information, where the first indication information is used to indicate the capability of the UE, and/or; Two indication information, where the second indication information is used to instruct the UE to request configuration information from the first edge configuration server.
  • the session establishment request sent by the UE to the AMF may include the first indication information and/or the second indication information, so that the AMF may determine the SMF according to the first indication information and/or the second indication information, and the SMF Supports UE access to the first edge configuration server to ensure the experience of user edge services.
  • the method further includes: the UE modifies the Access to the first edge configuration server is requested.
  • the UE can also access the first edge configuration server through a session modification request, so as to ensure user experience of edge services.
  • the first network element is a policy control network element
  • the second network element is a mobility management network element
  • a method for obtaining an edge service comprising: a second network element receives a session establishment request from a user equipment UE, and the session establishment request includes: information about a data network name of a first edge configuration server and/or or indication information, where the indication information includes first indication information and/or second indication information, where the first indication information is used to indicate the capability of the UE, and the second indication information is used to indicate the UE Request configuration information from the first edge configuration server, the first edge configuration server is determined by the UE among at least two edge configuration servers according to policy information, and the policy information includes the first edge configuration server of each edge configuration server Two types of information, the second type of information includes information about the data network name corresponding to each edge configuration server and/or single network slice selection auxiliary information; the second network element according to the second type of information and/or the The indication information determines a third network element, and the third network element supports the UE to access the first edge configuration server.
  • the second network element can determine the third network element according to the data network name of the first edge configuration server, or single network slice selection auxiliary information, or indication information, so that the third network element supports the UE to access the first edge Configure the server to ensure the experience of user edge services.
  • the policy information further includes the first type of information of each edge configuration server, and the first type of information includes one or more of the following information: The service scope information, priority information, and identification information corresponding to each edge configuration server.
  • the policy information in this application may also include the service scope information, priority information, identification information, etc. corresponding to the edge configuration server, so that the UE can determine the target ECS among multiple ECSs to ensure user edge services experience.
  • the policy information includes priority information of each edge configuration server, and the first edge configuration server is used by the UE in at least two
  • the determination in the edge configuration server includes: if the priorities of the multiple edge configuration servers are different, the first edge configuration server is the edge configuration server with the highest priority.
  • the policy information includes priority information and service scope information of each edge configuration server
  • the first edge configuration server is configured by the UE according to the policy information , determined in at least two edge configuration servers, including: if multiple edge configuration servers have the same priority, the first edge configuration server determines for the UE according to the service scope of the edge configuration server and the location information of the UE of.
  • the method further includes: the second network element receiving a session modification request from the UE, where the session modification request includes a first request, and the first The request is used for the UE to request configuration information from the first edge configuration server; the second network element sends the session modification request to the third network element.
  • the second network element can establish a session modification request, and access the first edge configuration server through the PDU session modification process, so as to ensure user experience of edge services.
  • the method further includes: the second network element receives policy information corresponding to at least two edge configuration servers from the first network element; the second network element The element sends the policy information to the UE.
  • a method for obtaining an edge service includes: a user equipment UE sends a session establishment request to a third network element, and the session establishment request includes a data network name of an edge configuration server and second indication information , the second indication information is used to instruct the UE to request configuration information from an edge configuration server; the UE receives policy information from a first network element, and the policy information includes identification information of a second edge configuration server and a data network name, the policy information is used to instruct the UE to access the second edge configuration server through the session, and the second edge configuration server is determined by a third network element according to the second indication information; the UE Determine to access the second edge configuration server through the session according to the policy information.
  • the third network element may determine that the UE needs to access the edge configuration server according to the second indication information, and then, the third network element may determine the target ECS according to factors such as local configuration and/or acquisition of subscription information from UDM, for example, the second ECS.
  • the network device can determine the target ECS that the UE needs to visit through the corresponding relationship between each ECS and each DNN in the multi-ECS, so as to ensure the user's edge service experience. Therefore, in the prior art, the problem that the network device cannot determine the target ECS in the multi-ECS scenario is solved.
  • the session establishment request further includes: first indication information, where the first indication information is used to indicate the capability of the UE.
  • the session establishment request sent by the UE to the AMF may contain the first indication information, so that the AMF can determine the SMF according to the first indication information or the second indication information or the name of the data network, and the SMF supports the UE to access the first
  • the edge configuration server ensures the user experience of edge services.
  • the first network element is a policy control network element
  • the second network element is a mobility management network element
  • the third network element is a session management network element Yuan.
  • a method for obtaining an edge service includes: a second network element receives a session establishment request from a user equipment UE, and the session establishment request includes a data network name and/or indication information of an edge configuration server, indicating The information includes first indication information and/or second indication information, where the first indication information is used to indicate the capabilities of the UE, and the second indication information is used to indicate that the UE requests configuration information from the edge configuration server; the second network The element determines the third network element according to the data network name and/or the indication information, the third network element supports the UE to access the second edge configuration server, and the second edge configuration server is determined by the third network element according to the indication information.
  • the second network element can determine the third network element according to the data network name and/or indication information of the second edge configuration server, so that the third network element supports the UE to access the first edge configuration server, thereby ensuring user edge business experience.
  • the method further includes: the second network element receives a session modification request from the UE, the session modification request includes a first request, and the first The request is used for the UE to request configuration information from the second edge configuration server; the second network element sends the session modification request to the third network element.
  • the method further includes: the second network element receives policy information from the first network element, and the policy information includes identification information of the second edge configuration server and A data network name, where the policy information is used to instruct the UE to access the second edge configuration server through the session; the second network element sends the policy information to the UE.
  • the first network element is a policy control network element
  • the second network element is a mobility management network element
  • the third network element is a session management network element Yuan.
  • an apparatus for obtaining an edge service may be a terminal device, for example, a user equipment UE.
  • the device can also be a chip.
  • the apparatus has a function of implementing any one of the above first aspect or the third aspect or any possible implementation manner of any one aspect of the user equipment UE. This function may be implemented by hardware, or may be implemented by executing corresponding software on the hardware.
  • the hardware or software includes one or more modules or units corresponding to the above functions.
  • an apparatus for obtaining an edge service may be a second network element, for example, a mobility management network element.
  • the device can also be a chip.
  • the apparatus has a function of realizing the second network element in any one of the second aspect or the fourth aspect or any possible implementation manner of any one of the above-mentioned aspects. This function may be implemented by hardware, or may be implemented by executing corresponding software on the hardware.
  • the hardware or software includes one or more modules or units corresponding to the above functions.
  • an apparatus for obtaining edge services including a processor.
  • the processor is coupled with the memory, and can be used to execute the instructions in the memory, so as to realize the functions of the terminal device in any one of the first aspect or the third aspect, or any possible implementation manner of any one aspect.
  • the terminal device can be, for example, User equipment UE.
  • the device further includes a memory.
  • the device further includes a communication interface, and the processor is coupled to the communication interface.
  • the apparatus is a terminal device.
  • the communication interface may be a transceiver, or an input/output interface.
  • the device is a chip configured in a terminal device.
  • the communication interface may be an input/output interface.
  • the transceiver may be a transceiver circuit.
  • the input/output interface may be an input/output circuit.
  • an apparatus for obtaining edge services including a processor.
  • the processor is coupled with the memory, and can be used to execute instructions in the memory, so as to realize the function of the second network element in any aspect of the second aspect or the fourth aspect, or any possible implementation manner of any aspect, the second network element
  • An element may be, for example, a mobility management network element.
  • the device further includes a memory.
  • the device further includes a communication interface, and the processor is coupled to the communication interface.
  • the device is a second network element, such as an AMF.
  • the communication interface may be a transceiver, or an input/output interface.
  • the device is a chip configured in the second network element.
  • the communication interface may be an input/output interface.
  • the transceiver may be a transceiver circuit.
  • the input/output interface may be an input/output circuit.
  • a processor including: an input circuit, an output circuit, and a processing circuit.
  • the processing circuit is configured to receive a signal through the input circuit and transmit a signal through the output circuit, so that the processor executes any one of the above-mentioned first to fourth aspects or any possible one of any aspect method in the implementation.
  • the above-mentioned processor can be a chip
  • the input circuit can be an input pin
  • the output circuit can be an output pin
  • the processing circuit can be a transistor, a gate circuit, a flip-flop, and various logic circuits.
  • the input signal received by the input circuit may be received and input by, for example but not limited to, the receiver
  • the output signal of the output circuit may be, for example but not limited to, output to the transmitter and transmitted by the transmitter
  • the circuit may be the same circuit, which is used as an input circuit and an output circuit respectively at different times.
  • the embodiment of the present application does not limit the specific implementation manners of the processor and various circuits.
  • an apparatus including a processor and a memory.
  • the processor is used to read instructions stored in the memory, and can receive signals through the receiver and transmit signals through the transmitter, so as to execute any one of the first to fourth aspects or any possible implementation of any one aspect method in .
  • processors there are one or more processors, and one or more memories.
  • the memory may be integrated with the processor, or the memory may be set separately from the processor.
  • the memory can be a non-transitory (non-transitory) memory, such as a read-only memory (read only memory, ROM), which can be integrated with the processor on the same chip, or can be respectively arranged in different On the chip, the embodiment of the present application does not limit the type of the memory and the configuration of the memory and the processor.
  • a non-transitory memory such as a read-only memory (read only memory, ROM)
  • ROM read only memory
  • a related data interaction process such as sending indication information may be a process of outputting indication information from a processor
  • receiving capability information may be a process of receiving input capability information from a processor.
  • processed output data may be output to the transmitter, and input data received by the processor may be from the receiver.
  • the transmitter and the receiver may be collectively referred to as a transceiver.
  • the device in the tenth aspect above can be a chip, and the processor can be implemented by hardware or by software.
  • the processor can be a logic circuit, integrated circuit, etc.; when implemented by software , the processor may be a general-purpose processor, implemented by reading software codes stored in a memory, the memory may be integrated in the processor, or be located outside the processor and exist independently.
  • a computer program product includes: a computer program (also referred to as code, or an instruction), which, when the computer program is executed, causes the computer to execute the above-mentioned first to A method in any one of the fourth aspects or any possible implementation of any one of the aspects.
  • a computer program also referred to as code, or an instruction
  • a computer-readable medium stores a computer program (also referred to as code, or instruction), and when it is run on a computer, it causes the computer to perform the above-mentioned first aspect to the method in any one of the fourth aspects or any possible implementation of any one of the aspects.
  • a computer program also referred to as code, or instruction
  • a system-on-a-chip including a processor, configured to call and run a computer program from a memory, so that a device installed with the system-on-a-chip executes any one of the first to fourth aspects or any one of the above-mentioned aspects.
  • a system in a fourteenth aspect, includes the device in the fifth aspect and the device in the sixth aspect.
  • FIG. 1 is a system architecture diagram 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 flowchart of a method 300 for acquiring edge services provided by the present application.
  • FIG. 4 is a schematic flowchart of a method 400 for acquiring edge services provided by the present application.
  • FIG. 5 is a schematic flowchart of a method 500 for acquiring edge services provided by the present application.
  • FIG. 6 is a schematic block diagram of an apparatus 100 for obtaining edge services provided by the present application.
  • FIG. 7 is a schematic block diagram of an apparatus 200 for obtaining edge services provided by the present application.
  • the wireless communication systems mentioned in the embodiments of this application include but are not limited to: global system of mobile communication (GSM) system, long term evolution (long term evolution, LTE) frequency division duplex (frequency division duplex, FDD) system , LTE time division duplex (time division duplex, TDD), LTE system, advanced long-term evolution (LTE-Advanced, LTE-A) system, next-generation communication system (for example, 6G communication system), integration of multiple access systems system, or evolved system.
  • GSM global system of mobile communication
  • LTE long term evolution
  • FDD frequency division duplex
  • FDD frequency division duplex
  • LTE time division duplex time division duplex
  • LTE-A advanced long-term evolution
  • next-generation communication system for example, 6G communication system
  • integration of multiple access systems system or evolved system.
  • the technical solution provided by this application can also be applied to machine type communication (machine type communication, MTC), inter-machine communication long-term evolution technology (Long Term Evolution-machine, LTE-M), device to device (device to device, D2D) network , machine to machine (machine to machine, M2M) network, Internet of things (internet of things, IoT) network or other networks.
  • MTC machine type communication
  • LTE-M inter-machine communication long-term evolution technology
  • D2D device to device
  • machine to machine machine to machine
  • M2M machine to machine
  • IoT Internet of things
  • the IoT network may include, for example, the Internet of Vehicles.
  • the communication methods in the Internet of Vehicles system are collectively referred to as vehicle to other devices (vehicle to X, V2X, X can represent anything), for example, the V2X can include: vehicle to vehicle (vehicle to vehicle, V2V) communication, vehicle and Infrastructure (vehicle to infrastructure, V2I) communication, vehicle to pedestrian (vehicle to pedestrian, V2P) or vehicle to network (vehicle to network, V2N) communication, etc.
  • vehicle to vehicle vehicle to vehicle
  • V2V vehicle to vehicle
  • V2I vehicle to infrastructure
  • V2P vehicle to pedestrian
  • V2N vehicle to network
  • the terminal equipment involved in the embodiments of the present application may include various access terminals, mobile equipment, user terminals or user devices with wireless communication functions.
  • the terminal device may be a user equipment (user equipment, UE), for example, 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.
  • Terminal equipment can also be wireless terminals in industrial control (industrial control), machine type communication (machine type communication, MTC) terminals, customer premise equipment (CPE), wireless terminals in self-driving , wireless terminals in remote medical, wireless terminals in smart grid, wireless terminals in transportation safety, wireless terminals in smart city, smart home ), cellular phones, cordless phones, session initiation protocol (session initiation protocol, SIP) phones, wireless local loop (wireless local loop, WLL) stations, personal digital assistants (personal digital assistant, PDA), handheld phones with wireless communication capabilities Devices, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, terminal devices in 5G networks or terminal devices in public land mobile networks (PLMN) that will evolve in the future, etc.
  • industrial control industrial control
  • machine type communication machine type communication
  • CPE customer premise equipment
  • wireless terminals in self-driving wireless terminals in remote medical
  • wireless terminals in smart grid wireless terminals in transportation safety
  • wireless terminals in smart city, smart home
  • FIG. 1 is a system architecture diagram applicable to the embodiment of the present application. As shown in the figure, the network architecture may specifically include the following network elements:
  • Wireless access network radio access network, RAN
  • the access network that realizes the access network function based on wireless communication technology can be called a radio access network.
  • the wireless access network can manage wireless resources, provide access services for terminals, and complete the forwarding of control signals and user data between terminals and the core network.
  • the wireless access network device involved in this application may be a device with a wireless transceiver function.
  • the wireless access network device may be a device that provides wireless communication function services, and is usually located on the network side, including but not limited to: a next-generation base station (gNodeB, gNB) in a fifth-generation (5th generation, 5G) communication system, a sixth-generation The next-generation base station in the 6th generation (6G) mobile communication system, the base station in the future mobile communication system or the access node in the WiFi system, etc., the evolved node B (evolved node B, eNB) in the LTE system, wireless Network controller (radio network controller, RNC), node B (node B, NB), base station controller (base station controller, BSC), home base station (for example, home evolved NodeB, or home Node B, HNB), baseband unit (base band unit, BBU), transmission reception point (transmission reception point, TRP), transmission point (transmitting point, TP), base transce
  • the access network device may include a centralized unit (centralized unit, CU) node, or a distributed unit (distributed unit, DU) node, or a RAN device including a CU node and a DU node, or a control plane CU Node and user plane CU node, and RAN equipment of DU node.
  • the access network device provides services for the cell, and the user equipment communicates with the base station through the transmission resources (for example, frequency domain resources, or spectrum resources) used by the cell.
  • the cell may be a cell corresponding to the base station (for example, a base station). It can belong to a macro base station, or it can belong to a base station corresponding to a small cell.
  • the small cell here can include: a metro cell, a micro cell, a pico cell, and a femto cell ( Femto cell), etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.
  • the wireless access network device can be a macro base station, a micro base station or an indoor station, or a relay node or a donor node, a device that provides wireless communication services for user equipment in a V2X communication system, a cloud wireless access network ( Cloud radio access network (CRAN) wireless controllers, relay stations, vehicle-mounted devices, wearable devices, and network devices in future evolution networks.
  • CRAN Cloud radio access network
  • the embodiment of the present application does not limit the specific technology and specific equipment form adopted by the radio access network equipment.
  • Authentication server function authentication server function, AUSF
  • network element mainly used for user authentication, etc.
  • 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 the mobility management entity (mobility management entity, MME) function Functions other than session management, such as lawful interception or access authorization (or authentication). In the embodiment of the present application, it can be used to implement functions of access and mobility management network elements.
  • AMF access and mobility management function
  • MME mobility management entity
  • Session management function network element (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 endpoints of charging function interfaces and downlink data notification etc. In the embodiment of the present application, it can be used to realize the function of the session management network element.
  • Policy control network element Policy control function, PCF: a unified policy framework for guiding network behavior, providing policy rule information for control plane functional network elements (such as AMF, SMF network elements, etc.).
  • Application function network element (Application function, AF): It is used for data routing affected by the application, accessing network opening function network elements, or interacting with the policy framework for policy control, etc.
  • Unified data management network element 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 (data network, DN) through this network element.
  • data network data network, DN
  • it can be used to realize the functions of the user plane network element.
  • Network slice selection function network element used to manage information related to network slices.
  • Data network a network used to provide data transmission.
  • DN Data network
  • a network of an operator's business an Internet (Internet) network, a business network of a third party, and the like.
  • network architecture also includes network repository function (network repository function, NRF): used to store the description information of network functional entities and the services they provide, and support functions such as service discovery and network element entity discovery; network open function network Element (network exposure function, NEF): used to securely open the services and capabilities provided by the third generation partnership project (3GPP) network function to the outside.
  • network repository function network repository function, NRF
  • NRF network repository function
  • NRF network repository function
  • NRF network repository function
  • NRF network repository function
  • NRF network repository function
  • NRF network repository function
  • the N2 interface is the interface between the RAN and the AMF network element, and is used for sending non-access stratum (non-access stratum, NAS) messages, etc.
  • the N3 interface is the interface between the RAN and the UPF network element, used
  • the N4 interface is the interface between the SMF network element and the UPF network element, and is used to transmit such information as the tunnel identification information of the N3 connection, data cache indication information, and downlink data notification messages.
  • the above-mentioned network architecture applied to the embodiment of the present application is only an example of 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 embodiment of the present application is not limited thereto. Any network architecture capable of implementing the functions of the foregoing network elements is applicable to this embodiment of the present application.
  • the name of the interface between network elements in FIG. 1 is just an example, and the name of the interface in a specific implementation may be another name, which is not specifically limited in this application.
  • the name of the message (or signaling) transmitted between the above network elements is only an example, and does not constitute any limitation on the function of the message itself.
  • Fig. 2 is a schematic diagram of the edge business architecture of the embodiment of the present application.
  • the network architecture may specifically include: edge data network (edge data network, EDN) (including: edge enabler server (edge enabler server, EES) edge application Server (edge application server, EAS)), edge configuration server (edge configuration server, ECS) and user equipment (user equipment, UE).
  • EDN edge data network
  • EES edge enabler server
  • EAS edge application server
  • ECS edge configuration server
  • user equipment user equipment
  • the EDN can be a local data center, and the EDN includes one or more EES and EAS, and each EDN has a specific service scope.
  • the user equipment may include: an edge enabler client (edge enabler client, EEC) and an application client, where the EEC provides necessary support for the application client on the terminal, and the functions of the EEC include: through EDGE-4 retrieves EDN information, UE registers to EES, retrieves available EAS, EAS availability changes, EAS migration notification to EEC.
  • EEC edge enabler client
  • the ECS network element (also referred to as edge data network configuration server (EDNCS)) can be a global management network element, maintaining the information of each EDN, including the service scope of the edge data network and the edge data network.
  • the edge enablement server EES address, etc. the service scope of the edge data network can be topological address information (such as Cell ID, TAI (Track area id), etc.) or geometric address information (for example, information such as province, city, district or latitude and longitude), and the service scope can be address information collection.
  • ECS network elements are deployed in a distributed manner, that is, each ECS can manage edge data networks in different regions. It should be understood that the ECS network element can be co-located with other network elements or can be an independent network element. This application does not make any limitation on the deployment of the ECS network element in the network architecture.
  • the EES network element which can be the control network element or management network element in the MEC node, is responsible for managing each EAS deployed in the EDN, such as registration, DNS resolution content routing selection, upper-layer application registration management, wireless information interaction and other basic functions.
  • the EES can call the network element with the capability opening function in the 3GPP network. It should be understood that the EES network element can be co-located with other network elements or can be an independent network element. This application does not make any restrictions on the deployment of the EES network element in the network architecture.
  • EES electronic book
  • EAS electronic book
  • ECS electronic book
  • the EDGE-8 reference point in Figure 2 supports the interaction between the edge provisioning 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 a service release notification to the core network (for example: SMF).
  • EDGE-1 The interface between EES and EEC, supporting the registration/de-registration of EEC in EES; the discovery of edge application servers in the edge data network.
  • EDGE-2 the interface between EES and 3GPP core network, used for EES to obtain 3GPP network capabilities.
  • EDGE-3 The interface between EES and EAS, supports EES registration/de-registration 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 EEC and ECS, supporting ECS to provide/push configuration information to EEC.
  • EDGE-5 The interface between the AC and the EEC, which supports the AC to obtain the 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, which supports EAS to obtain 3GPP network capabilities.
  • EDGE-8 The interface between ECS and 3GPP core network, which supports ECS to obtain 3GPP network capabilities.
  • EDGE-9 Cross-MEC nodes/interfaces between different EESs within the same MEC node, supporting application migration.
  • Data network name (data network name, DNN):
  • the data network name DNN can be used to select the SMF and UPF to establish a protocol data unit (protocol data unit, PDU) session, and can also be used to determine the policy applied to the PDU session .
  • the composition of DNN has two parts: 1) network identification (identification, ID), this part indicates an external network, which is mandatory; 2) operator ID, which indicates which operator it belongs to, and is optional.
  • Single network slice selection assistance information (single network slice selection assistance information, S-NSSAI): It can uniquely identify a network slice, and may contain one or more data network names DNN for AMF to select. Among them, the SMF selected for the PDU session is specified in the DNN.
  • NSSAI is a collection of S-NSSAI, which can identify a group of network slices. When performing services, the UE can select the corresponding slice group (including AMF/SMF/UPF) through the S-NSSAI.
  • the UE When the UE attaches (attach), the UE will provide S-NSSAI information, and the gNB selects the 5G core network (5G Core Network, 5GC) according to the S-NSSAI information; if the UE does not provide relevant S-NSSAI information, then the gNB The UE's NAS information will be routed to a default 5GC.
  • 5G Core Network 5GC
  • UE route selection policy It is a list containing one or more URSP rules (rules). Each URSP rule in URSP consists of the rule's precedence, traffic descriptor and route selection descriptor (RSD) list. Each rule has a different priority, and each rule is sorted from highest priority to lowest priority. Priority determines the order in which UEs use URSP rules.
  • a traffic descriptor consists of one or more components, which may include: application descriptor (application descriptor), Internet protocol (Internet protocol, IP) descriptor (IP descriptor), for example: destination IP, domain descriptor (domain descriptor), for example, fully qualified domain name (fully qualified domain name, FQDN), non-IP descriptor (non-IP descriptor), DNN descriptor, and connection capabilities (connection capabilities).
  • application descriptor application descriptor
  • IP descriptor Internet protocol
  • domain descriptor domain descriptor
  • non-IP descriptor for example, fully qualified domain name (fully qualified domain name, FQDN)
  • non-IP descriptor non-IP descriptor
  • DNN descriptor connection capabilities (connection capabilities).
  • connection capabilities connection capabilities
  • the route selection descriptor RSD list contains one or more RSDs, and each RSD consists of its own RSD precedence, route selection components and route selection verification criteria. Among them, the RSD priority determines the order of using RSDs, and other RSDs are used only when the RSD with a higher priority cannot be used.
  • the routing selection component describes various network resources that the application can use. It consists of one or more components, which can include service and session continuity (SSC) mode selection (SSC mode selection), network slice selection (network slice selection) ), DNN selection (DNN selection), PDU session type selection (PDU session type selection), non-seamless offload indication (non-seamless offload indication), access type preference (access type preference).
  • SSC service and session continuity
  • the routing verification criteria describe the corresponding effective conditions, which include time window and location criteria. If the current time is not within the time window or the UE location does not match the location criteria, the RSD is considered invalid.
  • each rule For each application, UE will inquire whether a rule is applicable according to the priority of the rule from high to low. If a rule is found to be applicable, this rule will be used; if no rules except the priority are applicable, the priority will be used.
  • the lowest rule which is equivalent to the default rule, applies to all applications.
  • each rule corresponds to a specific PDU session (including: session type, SSC mode, slice, DNN, etc.), when the corresponding session exists, the application uses the session; when the session does not exist, it is established New matching session.
  • the URSP can be used to allow the terminal to select (or establish) a PDU session (or slice).
  • the UE can determine according to the URSP policy whether the detected application can be associated with an established PDU session, can be offloaded to a non-3GPP access outside the PDU session, or can trigger the establishment of a new PDU session.
  • This URSP rule is applicable when each component in the service descriptor is matched with corresponding information from the application.
  • This URSP rule does not apply when corresponding information from the application does not match any value in the Flow Descriptor component, or when no corresponding information from the application is available.
  • the usage rules and procedures of URSP can refer to the protocol TS 24.526, which will not be repeated here.
  • the UE generally adopts the following scheme to obtain the address information of the edge configuration server ECS: the ECS can first send its address information to the UDM network element, and when the UE requests the SMF to obtain the address information of the ECS, the SMF can obtain it according to the local configuration or from the UDM.
  • the subscription data of the UE determines the ECS address, and then the SMF sends the address information of the ECS to the UE. It can be seen from the above that currently the network side can only determine one ECS address and send it to the UE.
  • the SMF cannot determine which/which ECS to send to the UE;
  • the UE cannot determine which ECS to access to obtain the edge network configuration information, resulting in poor experience of UE edge services.
  • the present application provides a method for obtaining edge services.
  • the network side and the UE can determine the ECS, thereby guaranteeing user experience of edge services.
  • the identification message in this embodiment of the present application may refer to address information, that is to say, the identification information in this embodiment of the present application may include address information of an edge server (eg, ECS).
  • the identification (for example, ECS ID) of the edge server can also be included, for example, the uniform resource identifier (uniform resource identifier, URI) of the edge server, the IP address information of the edge server, and the identification information can also include the instance identification of the edge server identifier (instance ID), and the identification information may also include the FQDN of the edge server.
  • the address information of the edge server can be obtained according to the identification message.
  • identification information may also be any other information from which the edge server address information can be obtained.
  • FIG. 3 is a schematic block diagram of a method 300 for obtaining edge services provided by the present application.
  • the method includes:
  • Step 301 UE receives policy information corresponding to at least two edge configuration servers from a first network element.
  • the policy information includes the first type of information of each edge configuration server, and the first type of information includes one or more of the following information: service scope information, priority information, and identification information corresponding to each edge configuration server .
  • the user equipment UE may receive policy information corresponding to multiple ECSs from the PCF, where the policy information corresponding to each ECS is the first type of information of each edge configuration server, and the first type of information It includes one or more of the following information: information about the service range corresponding to each edge configuration server, priority information, and identification information.
  • the UE may receive URSPs (an example of policy information) corresponding to three ECSs from the PCF, for example, the UE may receive policy information of ECS#1, ECS#2 and ECS#3.
  • the policy information can only include the information of each ECS priority; if the UE needs the information of the ECS service range in addition to the information of the ECS priority, the policy information can include the information of each ECS priority Level information and information on the scope of ECS services.
  • the policy information may also include the identification information of the ECS.
  • the content of the first type of information in the policy information can be flexibly determined, and each of the above cases is just an example and not limited.
  • one ECS may correspond to one URSP, and at this time, the UE may receive multiple URSPs corresponding to multiple ECSs.
  • the UE may receive the URSP corresponding to ECS#1, the URSP corresponding to ECS#2 and the URSP corresponding to ECS#3.
  • multiple ECSs may correspond to one URSP.
  • the UE only needs to receive one URSP, and the URSP includes three ECSs.
  • step 302 the UE determines a first edge configuration server among at least two edge configuration servers according to the first type of information in the policy information.
  • the UE receives URSPs corresponding to three ECSs as an example for introduction. For example, take the URSPs corresponding to ECS#1, ECS#2 and ECS#3 as an example.
  • the UE may determine the ECS with the highest priority among ECS#1, ECS#2, and ECS#3 as the first ECS, for example, the priority of ECS#2 The level is the highest, and the UE determines that ECS#2 is the first ECS.
  • the UE may jointly determine the first ECS according to its own location information and the service range information of ECS#1, ECS#2 and ECS#3. For example, the service range of ECS#1 just covers the current location of the UE, and at this time, the UE may determine that ECS#1 is the first ECS. For another example, the service ranges of ECS#1, ECS#2, and ECS#3 all cover the current location of the UE, and ECS#1 is the closest to the UE, at this time, the UE can also determine that ECS#1 is the first ECS, etc. Wait.
  • the UE can determine the The first ECS.
  • the UE can flexibly determine the first ECS.
  • the policy information in this application may also include the second type of information of each edge configuration server, and the second type of information includes information about the data network name corresponding to each edge configuration server and/or single network slice selection auxiliary information .
  • the UE may also request to establish a PDU session corresponding to the first edge configuration server according to the second type of information in the policy information.
  • the UE may create a session between the DNN and the S-NSSAI corresponding to ECS#1.
  • the UE may request the AMF to establish a protocol data unit PDU session corresponding to the first ECS (eg, ECS#1).
  • the session includes the DNN and/or S-NSSAI corresponding to ECS#1.
  • the UE can access the first edge configuration server through the PDU session.
  • the UE determines the target ECS that needs to be accessed according to the corresponding relationship between each ECS in the received URSP and its respective service scope and priority in the multi-ECS, and the UE can use the DNN .
  • the N-SSAI establishes a PDU session of the target ECS, and accesses the edge service through the session, thereby ensuring the experience of the user's edge service. That is to say, by enhancing the existing URSP mechanism, the present application achieves the technical effect of the UE determining the target ECS to be accessed among multiple ECSs with minor changes to the existing technology, and guarantees the user's edge service experience.
  • Fig. 4 is a schematic flowchart of a method 400 for obtaining edge services provided by the present application.
  • the method 400 shown in Fig. 4 can be implemented by AMF, SMF, NEF, UDM, PCF, ECS, etc. in the system shown in Fig. 1 Network element execution.
  • the method includes steps 401 to 412. This embodiment takes UE#1 as an example for illustration, and each step is described in detail below.
  • step 401 the ECS sends its own configuration information to the UDM.
  • ECS configuration information includes: ECS data network name DNN information, ECS service scope information, ECS priority information, ECS identification information (also understandable, ECS corresponding or associated identification information), ECS single network slice selection auxiliary information S-NSSAI and other information.
  • the ECS can call the parameters of the NEF to provide services, for example, parameter provisionservice sends the configuration information to the NEF, and then the NEF sends the configuration information to the UDM or UDR.
  • each ECS may send its various configuration information to the UDM.
  • the UDM can also send the configuration information to the UDR, and the UDR stores the configuration information.
  • step 402 the UDM or UDR sends notification information to the PCF to notify the UE that subscription data has changed.
  • the PCF receives the notification information.
  • the PCF may be the PCF serving the UE, for example, UE#1.
  • the PCF may first subscribe to the UDM or UDR for the notification of the UE's subscription data change event, and then send notification information to the PCF when the UDM or UDR detects that the UE's subscription data changes.
  • the notification information may include ECS configuration information, for example, one or more of ECS data network name DNN information, ECS service range information, and ECS priority information.
  • the notification information may further include ECS identification information (it can also be understood that identification information corresponding to or associated with the ECS), S-NSSAI of the ECS, and other information.
  • step 403 the PCF generates a user routing policy URSP (an example of policy information).
  • URSP an example of policy information
  • the URSP may include the first type of information of each edge configuration server, wherein the first type of information includes one or more of the following information: information of the service scope corresponding to each edge configuration server, priority information, identification information.
  • the URSP may also include the second type of information of each edge configuration server, where the second type of information includes information about the data network name corresponding to each edge configuration server and/or single network slice selection assistance information.
  • the PCF may generate a user routing policy URSP after receiving the notification message from the UDM or UDR.
  • the DNN information and S-NSSAI information of the ECS may be included in the route selection components (route selection components) field of the route selection descriptor in the URSP.
  • the service scope information of the ECS can be included in the location criteria (location criteria) field of the routing descriptor in the URSP.
  • ECS identification information can be included in the IP descriptor (IP descriptor) or domain descriptor (domain descriptor) of the traffic descriptor in URSP.
  • the priority information of ECS can be included in the priority value (precedence value) field in URSP.
  • the PCF may also re-determine the priority of each ECS according to local configuration or policy information or a signed service layer agreement (service layer agreement, SLA), that is, the PCF may adjust the priority of the ECS in step 401.
  • SLA service layer agreement
  • one ECS can correspond to one URSP, multiple ECS can correspond to multiple URSPs, and multiple ECS can also correspond to one URSP, without limitation.
  • Step 404 PCF sends URSP to UE#1.
  • UE#1 can receive and store the URSP.
  • Step 405 UE#1 determines the first ECS according to the first type of information in the URSP.
  • UE#1 may select the ECS with the highest priority. For example, the ECS with the highest priority is ECS#1 (for the convenience of description, the determined ECS is marked as ECS#1 in this embodiment), at this time, UE#1 determines to obtain the edge configuration information through ECS#1.
  • the edge configuration information may include, for example, identification information of the EES and the like.
  • UE#1 can also determine the ECS according to the service range of the ECS and the location of UE#1, that is, select the ECS whose service range includes the location of UE#1.
  • ECS communicates.
  • ECSs with the highest priority include ECS#1, ECS#2, and ECS#5.
  • UE#1 can determine to obtain edge configuration information through ECS#1 through the service range of each ECS and its own location information.
  • the edge configuration information may include, for example, identification information of the EES and the like.
  • step 302 in the method 300 which will not be repeated here.
  • the first request may be, for example: a service provisioning request, a service provisioning subscription request, a service provisioning subscription update request, a service unsubscription request (service provisioning unsubscribe request).
  • service provisioning requestIE service provisioning request information element
  • Step 406 UE#1 creates a session between DNN and S-NSSAI corresponding to ECS#1.
  • UE#1 may request to establish a protocol data unit PDU session corresponding to ECS#1 according to the second type of information in the policy information. For example, UE#1 may send a session establishment request to the AFM, and the session establishment request includes the DNN and/or S-NSSAI corresponding to ECS#1.
  • the session establishment request may also include indication information #1, where the indication information #1 is used to indicate the capability of UE #1.
  • the capability of UE#1 may refer to the capability of UE#1 (or EEC) to support receiving ECS configuration information.
  • the session establishment request may also include indication information #2, and the indication information #2 is used to instruct UE #1 to request configuration information (eg, service provisioning request IE) from the first ECS (eg, ECS #1).
  • the requested configuration information may include, for example, identification information of the EES.
  • the session establishment request also includes ECS#1 identification information.
  • the AMF determines the SMF according to the DNN and/or the indication information.
  • the AMF can select (also can be understood as, determine) a specific SMF according to the indication information (for example, indication information #1 and/or indication information #2) in step 406, that is, select a service provisioning request IE to send SMF for ECS capabilities.
  • the AMF may select an SMF according to the DNN, that is, only a specific SMF can serve the DNN.
  • step 408 the AMF sends a session context creation request to the SMF.
  • the SMF may receive a session context creation request from the AMF.
  • the session context creation request may also include the first request (for example, service provisioning request IE) and the identification information of ECS#1.
  • step 409 may also be included.
  • the SMF receives a session context creation request from the AMF. If the request does not carry the identification information of ECS#1, at this time, the SMF may obtain the ECS from the UDM or PCF. #1 identification information; or, the SMF may determine the ECS #1 identification information according to local configuration and/or subscription information. This is because each ECS has sent its configuration information to the UDM in step 401, so the SMF can determine which ECS it is based on the DNN and S-NSSAI corresponding to the session context creation request.
  • Step 410 SMF sends the first request (for example, service provisioning request IE) to ECS#1.
  • ECS#1 receives the first request.
  • step 406 from step 406 to step 410, it is described that UE#1 sends a service provisioning request in the session establishment process.
  • Other steps of the session establishment process include establishing a session of the user plane path between the UE and the UPF, which is prior art and will not be repeated here.
  • UE#1 may also access ECS#1 through a session modification request after the session is established.
  • UE#1 can send a session modification request to AMF, and the session modification request includes a first request (for example, service provisioning request).
  • the session modification request may include identification information of ECS#1. Then the AMF can send the session modification request to the SMF, and after the SMF receives the service provisioning request, it can continue to execute steps 409 and 410 to send the service provisioning request to ECS#1.
  • Step 411 ECS#1 determines to send a first response to UE#1, and the first response includes configuration information that ECS#1 needs to send to UE#1.
  • the first response may be identification information of the EES, for example, identification information of EES#1.
  • Step 412 ECS#1 sends a first response to UE#1, where the first response includes the identification information of the EES.
  • ECS#1 can send service provisioning response to UE#1 through SMF; or, ECS#1 can first send service provisioning response to SMF through PCF, and then send service provisioning response to UE through SMF #1.
  • ECS#1 may send the service provisioning response to UE#1 through the user plane path between UE and UPF. Similar to step 405, the first response may be: service provisioning response (service provisioning response), service subscription response (service provisioning subscription response), service subscription update response (service provisioning subscription update response) or service cancellation subscription request (service provisioning unsubscribe response)
  • service provisioning response service provisioning response
  • service subscription response service provisioning subscription response
  • service subscription update response service provisioning subscription update response
  • service cancellation subscription request service provisioning unsubscribe response
  • the UE determines the target ECS that needs to be accessed according to the corresponding relationship between each ECS in the received URSP and its respective priority and service scope in the multi-ECS, and the UE can use the DNN .
  • the N-SSAI establishes a PDU session of the target ECS, and accesses the edge service through the session, thereby ensuring the experience of the user's edge service. That is to say, by enhancing the existing URSP mechanism, the present application achieves the technical effect of the UE determining the target ECS to be accessed among multiple ECSs with minor changes to the existing technology, and guarantees the user's edge service experience.
  • Fig. 5 is a schematic flowchart of a method 500 for obtaining edge services provided by the present application.
  • the method 500 shown in Fig. 5 can be implemented by AMF, SMF, NEF, UDM, PCF, ECS, etc. in the system shown in Fig. 1 Network element execution.
  • the method includes steps 501 to 512.
  • UE#2 is taken as an example for illustration, and each step is described in detail below.
  • step 501 the ECS sends its own configuration information to the UDM.
  • the configuration information of the ECS includes: the data network name DNN information of the ECS, the service scope information of the ECS, and the priority information of the ECS.
  • ECS identification information (it can also be understood as identification information corresponding to or associated with the ECS), ECS single network slice selection auxiliary information S-NSSAI and other information.
  • the ECS can call the parameters of the NEF to provide services, for example, the parameter provision service sends the configuration information to the NEF, and then the NEF sends the configuration information to the UDM or UDR.
  • Step 502 UE#2 may send a session establishment request to the AFM, and the session establishment request includes DNN and indication information #2.
  • the indication information #2 is used to instruct UE #1 to request configuration information (for example, service provisioning request IE) from the ECS.
  • the configuration information may include, for example, identification information of the EES and the like.
  • the session establishment request may also include indication information #1, where the indication information #1 is used to indicate the capability of UE #1.
  • the capability of UE#1 may refer to the capability of UE#1 to support receiving ECS.
  • the AMF determines the SMF according to the DNN and/or the indication information.
  • the AMF can select (also can be understood as, determine) a specific SMF according to the indication information in step 406 (for example, indication information #1 and/or indication information #2), that is, select a service provisioning request IE SMF sent to ECS capability.
  • the AMF may select an SMF only according to the DNN, that is, only a specific SMF can serve the DNN.
  • step 504 the AMF sends a session context creation request to the SMF.
  • the SMF may receive a session context creation request from the AMF.
  • step 505 the SMF determines the identification information of the ECS.
  • the identification information of the ECS determined by the SMF is ECS#2 (an example of the second edge configuration service) as an example for description.
  • the SMF can determine that the UE needs to access the edge configuration server according to the indication information #2, and then the SMFSMF can determine the ECS#2 identification information according to the local configuration and/or obtain the subscription information from the UDM. This is because each ECS has sent its configuration information to the UDM in step 501, and the UE's subscription information or local configuration in the UDM has saved the configuration information of each ECS.
  • the configuration information includes, for example, ECS priority information, service range information, DNN information, S-NSSAI information, and the like. Therefore, the SMF can determine which ECS it is based on information such as the DNN and S-NSSAI corresponding to the session context creation request.
  • step 506 the SMF sends the determined configuration information of ECS#2 to the PCF.
  • the SMF may send the determined identification information of ECS#2 and the DNN to the PCF.
  • the PCF In step 507, the PCF generates a URSP about ECS#2 according to the configuration information of ECS#2, and the URSP includes identification information and data network name corresponding to ECS#2.
  • the SMF can trigger the PCF to generate a URSP about ECS#2.
  • the SMF can trigger the PCF to generate a URSP about ECS#2, wherein the URSP includes the corresponding DNN and identification information of ECS#2.
  • the URSP in this implementation may instruct UE#2 to access the determined ECS#2 through the session corresponding to the DNN (that is, the session that the UE currently requests to establish).
  • the DNN information and S-NSSAI information of ECS#2 may be included in the route selection components (route selection components) field of the route selection descriptor in the URSP.
  • the service scope information of ECS#2 can be included in the location criteria (location criteria) field of the routing descriptor in the URSP.
  • ECS#2 identification information can be included in the IP descriptor (IP descriptor) or domain descriptor (domain descriptor) of the flow descriptor in URSP.
  • the priority information of ECS#2 can be included in the priority value (precedence value) field in the URSP.
  • step 508 may also be included, where the SMF saves the determined identification information of ECS#2.
  • Step 509 PCF sends URSP about ECS#2 to UE#2.
  • UE#2 can receive the URSP.
  • step 509 in this application may be performed during the session establishment process of UE#2, or after UE#2 completes session establishment, and this application does not limit the time for performing step 509.
  • Step 510 UE#2 determines to send the first request to ECS#2 through the currently established session according to the URSP.
  • the first request is used for UE#2 to request configuration information from ECS#2, for example, UE#2 to request EES identification information from ECS#2.
  • the first request in this application may be, for example: service provisioning request, service provisioning subscription request, service provisioning subscription update request, service cancellation Subscription request (service provisioning unsubscribe request).
  • service provisioning request IE information element
  • the service provisioning request IE information element
  • UE#2 may also access ECS#2 through session modification after the session establishment is completed.
  • UE#2 may send a session modification request to the AMF, where the session modification request includes the first request (for example, service provisioning request).
  • the session modification request may also include identification information of ECS#2. It should be understood that if in step 508, the SMF saves the determined identification information of ECS#2, at this time, UE#2 may also not need to carry the identification information of ECS#2.
  • the AMF sends the session modification request to the SMF, and the SMF can directly send the first request (for example, service provisioning request) to the stored address corresponding to ECS#2. That is to say, at this time, the SMF may directly send the first request to ECS#2.
  • Step 511 ECS#2 determines to send a first response to UE#2, and the first response includes configuration information sent by ECS#2 to UE.
  • the first response may be identification information of the EES.
  • Step 512 ECS#2 sends a first response to UE#2, where the first response includes the identification information of the EES.
  • ECS#2 can send service provisioning response to UE#2 through SMF; or, ECS#2 can first send service provisioning response to SMF through PCF, and then send service provisioning response to UE through SMF #1.
  • ECS#2 may send the service provisioning response to UE#1 through the user plane path between UE and UPF. Similar to step 510, the first response may be: service configuration response (service provisioning response), service subscription response (service provisioning subscription response), service subscription update response (service provisioning subscription update response) or service cancellation subscription request (service provisioning unsubscribe response)
  • service configuration response service provisioning response
  • service subscription response service provisioning subscription response
  • service subscription update response service provisioning subscription update response
  • service cancellation subscription request service provisioning unsubscribe response
  • the network device can determine the target ECS that the UE needs to visit through the corresponding relationship between each ECS and its respective service scope, priority and identification information in the multi-ECS. And the network device can send the determined policy information of the ECS to the UE, instructing the UE to access the ECS through the currently established PDU session, so as to ensure the experience of the user's edge service. That is to say, by enhancing the existing URSP mechanism, this application achieves the technical effect of network equipment determining the target ECS to be accessed among multiple ECSs with minor changes to the existing technology, ensuring the user's edge service experience .
  • words such as “first” and “second” are used to describe the same functions and functions that are basically the same. item or similar items.
  • the first information and the second information are only for distinguishing different information, and the sequence thereof is not limited.
  • words such as “first” and “second” do not limit the number and execution order, and words such as “first” and “second” do not necessarily limit the difference.
  • one or more of the following or similar expressions refer to any combination of these items, including any combination of single or plural items.
  • one or more of a, b, or c may mean: a, b, c; a and b; a and c; b and c; or a and b and c.
  • a, b, c can be single or multiple.
  • each node such as a terminal device or a network device, includes a corresponding hardware structure and/or software module for performing each function.
  • each node such as a terminal device or a network device
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software drives hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the present application.
  • the embodiment of the present application may divide the terminal device or the terminal device into functional modules according to the above method examples.
  • each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module.
  • the above-mentioned integrated modules can be implemented in the form of hardware or in the form of software function modules. It should be noted that the division of modules in the embodiment of the present application is schematic, and is only a logical function division, and there may be other division methods in actual implementation. In the following, description will be made by taking the division of each functional module corresponding to each function as an example.
  • FIG. 6 is a schematic block diagram of an apparatus 100 according to an embodiment of the present application. As shown in the figure, the apparatus 100 may include: a transceiver unit 110 and a processing unit 120 .
  • the apparatus 100 may be the terminal device in the above method embodiment, for example, user equipment UE, or a chip for realizing the functions of the terminal device in the above method embodiment. It should be understood that the apparatus 100 may correspond to the UE in the method 300, method 400, and method 500 according to the embodiment of the present application, and the apparatus 100 may execute the method corresponding to the UE in the method 300, method 400, and method 500 of the embodiment of the present application. A step of. It should be understood that the specific process for each unit to perform the above corresponding steps has been described in detail in the above method embodiments, and for the sake of brevity, details are not repeated here.
  • the transceiver unit is used to receive policy information corresponding to at least two edge configuration servers, the policy information includes the first type of information of each edge configuration server, and the first type of information includes one or more of the following information Item: information on the service scope, priority information, and identification information corresponding to each edge configuration server; the processing unit is configured to, according to the first type of information in the policy information, configure the at least two edge configuration servers Identify the first edge configuration server.
  • the policy information further includes the second type of information of each edge configuration server, and the second type of information includes the information of the data network name corresponding to each edge configuration server and/or a single network slice selection assistance information
  • the processing unit is further configured to request to establish a protocol data unit PDU session corresponding to the first edge configuration server according to the second type of information in the policy information; the device accesses the first edge configuration server through the PDU session Edge configuration server.
  • the transceiving unit is configured to send a session establishment request, the session establishment request includes a data network name and second indication information, and the second indication information is used to instruct the device to request the edge configuration server configuration information; the transceiving unit is used to receive policy information, the policy information includes identification information and data network name of the second edge configuration server, and the policy information is used to instruct the device to access the second edge configuration server through the session An edge configuration server, where the second edge configuration server is determined by the third network element according to the second indication information; the device determines to access the second edge configuration server through the session according to the policy information.
  • the apparatus 100 may be the second network element in the above method embodiment, for example, an AMF, or may be a chip for realizing the function of the second network element in the above method embodiment. It should be understood that the apparatus 100 may correspond to the AMF in the method 400 and the method 500 according to the embodiment of the present application, and the apparatus 100 may execute the steps corresponding to the AMF in the method 500 and the method 700 of the embodiment of the present application. It should be understood that the specific process for each unit to perform the above corresponding steps has been described in detail in the above method embodiments, and for the sake of brevity, details are not repeated here.
  • the transceiving unit is configured to receive a session establishment request, the session establishment request includes: first edge configuration server data network name information and/or indication information, and the indication information includes first indication information and/or second Two indication information, wherein the first indication information is used to indicate the capability of the user equipment, the second indication information is used to indicate the user equipment to request configuration information from the first edge configuration server, and the first edge
  • the configuration server is determined by the user equipment among at least two edge configuration servers according to the policy information, the policy information includes the second type information of each edge configuration server, and the second type information includes each edge configuration server Information about the corresponding data network name and/or single network slice selection auxiliary information; the transceiver unit is configured to determine a third network element according to the second type of information and/or the indication information, and the third network element supports The device accesses the first edge configuration server.
  • the transceiving unit is further configured to receive a session modification request, the session modification request includes a first request, and the first request is used for the user equipment to request configuration information from the first edge configuration server ; The transceiving unit is used to send the session modification request.
  • the transceiving unit is further configured to receive policy information corresponding to at least two edge configuration servers; the transceiving unit is configured to send the policy information.
  • FIG. 7 is a schematic block diagram of an apparatus 200 provided by an embodiment of the present application.
  • the apparatus 200 includes: at least one processor 220 .
  • the processor 220 is coupled with the memory for executing instructions stored in the memory to send signals and/or receive signals.
  • the device 200 further includes a memory 230 for storing instructions.
  • the apparatus 200 further includes a transceiver 210, and the processor 220 controls the transceiver 210 to send signals and/or receive signals.
  • processor 220 and the memory 230 may be combined into one processing device, and the processor 220 is configured to execute the program codes stored in the memory 230 to implement the above functions.
  • the memory 230 may also be integrated in the processor 220 , or be independent of the processor 220 .
  • the transceiver 210 may include a transceiver (or a receiver) and a transmitter (or a transmitter).
  • the transceiver may further include antennas, and the number of antennas may be one or more.
  • the transceiver 210 may be a communication interface or an interface circuit.
  • the transceiver 210 in the device 200 may correspond to the transceiver unit 110 in the device 100
  • the processor 220 in the device 200 may correspond to the processing unit 120 in the device 200 .
  • each step of the above method can be completed by an integrated logic circuit of hardware in a processor or an instruction in the form of software.
  • the steps of the methods disclosed in connection with the embodiments of the present application may be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in the processor.
  • the software module can be located in a mature storage medium in the field such as random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, register.
  • the storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps of the above method in combination with its hardware. To avoid repetition, no detailed description is given here.
  • the processor in the embodiment of the present application may be an integrated circuit chip, which has a signal processing capability.
  • each step of the above-mentioned method embodiments may be completed by an integrated logic circuit of hardware in a processor or instructions in the form of software.
  • the above-mentioned processor can be a general-purpose processor, a digital signal processor (digital signal processor, DSP), an application-specific integrated circuit (application-specific integrated circuit, ASIC), a field-programmable gate array (field-programmable gate array, FPGA) or Other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.
  • DSP digital signal processor
  • ASIC application-specific integrated circuit
  • FPGA field-programmable gate array
  • Other programmable logic devices discrete gate or transistor logic devices, discrete hardware components.
  • a general-purpose processor may be a microprocessor, or the processor may be any conventional processor, or the like.
  • the steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a mature storage medium in the field such as random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, register.
  • the storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps of the above method in combination with its hardware.
  • the memory in the embodiments of the present application may be a volatile memory or a nonvolatile memory, or may include both volatile and nonvolatile memories.
  • the non-volatile memory can be read-only memory (read-only memory, ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically programmable Erases programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • Volatile memory can be random access memory (RAM), which acts as external cache memory.
  • RAM random access memory
  • static RAM static random access memory
  • dynamic RAM dynamic random access memory
  • DRAM dynamic random access memory
  • synchronous dynamic random access memory synchronous DRAM, SDRAM
  • double data rate synchronous dynamic random access memory double data rate SDRAM, DDR SDRAM
  • enhanced synchronous dynamic random access memory enhanced SDRAM, ESDRAM
  • synchronous connection dynamic random access memory direct ram-bus RAM, DR RAM
  • direct ram-bus RAM direct ram-bus RAM
  • the present application also provides a computer program product, the computer program product stores computer program code, and when the computer program code is run on the computer, the computer executes method 300 and method 400 .
  • the method in any one embodiment of the method 500 embodiment.
  • the present application also provides a computer-readable medium, the computer-readable medium stores program code, and when the program code is run on the computer, the computer is made to execute the method 300, method 400, The method in any one of the embodiments of the method 500.
  • the present application further provides a system, which includes the foregoing apparatus or equipment.
  • all or part of them may be implemented by software, hardware, firmware or any combination thereof.
  • software When implemented using software, it may 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 the computer, the processes or functions according to the embodiments of the present application will be generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices.
  • 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 transmitted from a website, computer, server, or data center Transmission to another website site, computer, server or data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.).
  • the computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server or a data center integrated with one or more available media.
  • the available medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a high-density digital video disc (digital video disc, DVD)), or a semiconductor medium (for example, a solid state disk (solid state disc, SSD)) etc.
  • a magnetic medium for example, a floppy disk, a hard disk, a magnetic tape
  • an optical medium for example, a high-density digital video disc (digital video disc, DVD)
  • a semiconductor medium for example, a solid state disk (solid state disc, SSD)
  • the network-side equipment in each of the above device embodiments corresponds to the terminal equipment and the network-side equipment or terminal equipment in the method embodiments, and the corresponding modules or units perform corresponding steps, for example, the communication unit (transceiver) executes the receiving method in the method embodiments. Or the step of sending, other steps besides sending and receiving may be performed by a processing unit (processor). For the functions of the specific units, reference may be made to the corresponding method embodiments. Wherein, there may be one or more processors.
  • a component may be, but is not limited to being, 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 can be components.
  • One or more components can reside within a process and/or thread of execution and a component can 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 packets of data, such as data from two components interacting with another component between a local system, a distributed system, and/or a network, such as the Internet through a signal interacting with other systems. Communicate through local and/or remote processes.
  • the disclosed systems, devices and methods may be implemented in other ways.
  • the device 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 can be combined or May be integrated into another system, or some features may be ignored, or not implemented.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit.
  • the functions described above are realized in the form of software function units and sold or used as independent products, they can be stored in a computer-readable storage medium.
  • the technical solution of the present application is essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) 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 (read-only memory, ROM), random access memory (random access memory, RAM), magnetic disk or optical disc and other media that can store program codes. .

Abstract

本申请提供了一种获取边缘服务的方法和装置，该方法包括：用户设备UE从网络设备接收至少两个边缘配置服务器对应的策略信息，该策略信息中包括以下信息的一项或者多项：每个边缘配置服务器的服务范围的信息、优先级的信息或者标识信息，UE根据该策略信息，在至少两个边缘配置服务器中确定目标边缘配置服务器。从而实现了在多个边缘配置服务器的场景下，UE可以确定所要访问的目标边缘配置服务器，保障了用户边缘业务的体验。

Description

一种获取边缘服务的方法和装置
本申请要求于2021年7月07日提交中国专利局、申请号为202110769700.7、申请名称为“一种获取边缘服务的方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，更具体地，涉及一种获取边缘服务的方法和装置。
背景技术
目前，用户设备(user equipment，UE)要获取边缘配置服务器(edge configuration server，ECS)的地址信息一般采用如下方案：ECS可以先将其地址信息发送到统一数据管理网元(unified data management，UDM)，UE向会话管理功能网元(session management function，SMF)请求获取ECS的地址信息时，SMF可以根据本地配置或从UDM中获取UE的签约数据从而确定ECS的地址，然后SMF将ECS的地址信息发送给UE。
由上可知，目前网络侧只能确定一个ECS地址并发送给UE。然而，在多ECS地址的场景下，如果SMF根据本地配置或从UDM中获取了多个ECS地址时，SMF无法确定给UE发送哪个/哪些ECS；对于UE而言，即便收到了SMF发送的多个ECS的地址信息，UE也无法确定访问哪个ECS获取边缘配置信息，从而造成UE边缘业务的体验较差。
发明内容
本申请提供一种获取边缘服务的方法和装置，在多ECS场景下，通过增强URSP机制，使得UE或者网络侧可以确定ECS，从而保障用户边缘业务的体验。
第一方面，提供了一种获取边缘服务的方法，该方法包括：用户设备UE从第一网元接收至少两个边缘配置服务器所对应的策略信息，该策略信息包括每个边缘配置服务器的第一类信息，所述第一类信息包括以下信息的一项或多项：每个边缘配置服务器对应的服务范围的信息、优先级的信息、标识信息；UE根据策略信息中的第一类信息，在至少两个边缘配置服务器中确定第一边缘配置服务器。
根据该技术方案，在多ECS的场景下，UE可以接收策略信息，该策略信息中包括每个ECS对应的服务范围的信息，或者优先级的信息，或者标识信息，从而UE可以在多个ECS中确定需要访问的目标ECS，保障了用户的边缘业务的体验。解决了现有技术中，多ECS场景中UE无法确定目标ECS的问题。
本申请中的策略信息可以是用户路由选择策略URSP。
本申请中的策略信息至少包含两个边缘配置服务器所对应的信息。例如，该策略信息可以包括：每个边缘配置服务器的服务范围的信息、优先级的信息、标识信息。
本申请中，策略信息中的第一类信息可以用于UE后续确定需要访问的目标ECS。因 此，策略信息中第一类信息的内容可以灵活确定，以上各个情况仅仅是举例，不作限定。
结合第一方面，在第一方面的某些实现方式中，所述策略信息还包括每个边缘配置服务器的第二类信息，所述第二类信息包括每个边缘配置服务器对应的数据网络名称的信息和/或单一网络切片选择辅助信息，该方法还包括：所述UE根据所述策略信息中的第二类信息请求建立所述第一边缘配置服务器对应的协议数据单元PDU会话；所述UE通过所述PDU会话访问所述第一边缘配置服务器。
基于上述技术方案，策略信息中还可以包括第二类信息，UE可以根据策略信息中的第二类信息，辅助建立PDU会话，从而使得UE可以访问目标边缘配置服务器，保障用户的边缘业务的体验。
本申请中，策略信息中第二类信息可以用于UE后续建立确定目标ECS的PDU会话。因此，策略信息中第二类信息的内容可以灵活确定，以上各个情况仅仅是举例，不作限定。
结合第一方面，在第一方面的某些实现方式中，所述策略信息包括每个边缘配置服务器的优先级信息，所述UE根据所述策略信息中的第二类信息，在所述至少两个边缘配置服务器中确定第一边缘配置服务器，包括：如果多个边缘配置服务器的优先级不同，则UE将优先级最高的边缘配置服务器确定为第一边缘配置服务器。
基于上述技术方案，UE可以根据各个边缘配置服务器的优先级信息在多个ECS中确定第一ECS，保障用户的边缘业务的体验。
结合第一方面，在第一方面的某些实现方式中，所述策略信息包括每个边缘配置服务器的优先级信息和服务范围的信息，所述UE根据所述策略信息中的第一类信息，在所述至少两个边缘配置服务器中确定所述第一边缘配置服务器，包括：如果多个边缘配置服务器的优先级相同，则UE根据边缘配置服务器的服务范围和UE的位置信息确定第一边缘配置服务器。
基于上述技术方案，UE可以根据各个边缘配置服务器的优先级信息和服务范围的信息在多个ECS中确定第一ECS，保障用户边缘业务的体验。
结合第一方面，在第一方面的某些实现方式中，所述UE根据所述策略信息中的第二类信息请求建立所述第一边缘配置服务器对应的协议数据单元PDU会话包括：所述UE向第二网元发送会话建立请求，所述会话建立请求中包括所述第一边缘配置服务器对应的数据网络名称和/或单一网络切片选择辅助信息。
基于上述技术方案，UE可以向AMF发送会话建立请求，从而建立第一边缘配置服务器的PDU会，从而通过该PDU会话访问第一边缘配置服务器，保障用户边缘业务的体验。
结合第一方面，在第一方面的某些实现方式中，所述会话建立请求中还包括：第一指示信息，所述第一指示信息用于指示所述UE的能力，和/或；第二指示信息，所述第二指示信息用于指示所述UE向所述第一边缘配置服务器请求配置信息。
基于上述技术方案，UE向AMF发送的会话建立请求中可以包含第一指示信息和/或第二指示信息，从而使得AMF可以根据该第一指示信息和/或第二指示信息确定SMF，该SMF支持UE访问第一边缘配置服务器，保障用户边缘业务的体验。
结合第一方面，在第一方面的某些实现方式中，所述UE建立关于所述第一边缘配置服务器对应的协议数据单元PDU会话完成后，所述方法还包括：所述UE通过会话修改 请求访问所述第一边缘配置服务器。
基于上述技术方案，UE还可以通过会话修改请求访问第一边缘配置服务器，保障用户边缘业务的体验。
结合第一方面，在第一方面的某些实现方式中，所述第一网元为策略控制网元，所述第二网元为移动管理网元。
第二方面，提供了一种获取边缘服务的方法，该方法包括：第二网元从用户设备UE接收会话建立请求，所述会话建立请求包括：第一边缘配置服务器数据网络名称的信息和/或指示信息，所述指示信息包括第一指示信息和/或第二指示信息，其中，所述第一指示信息用于指示所述UE的能力，所述第二指示信息用于指示所述UE向所述第一边缘配置服务器请求配置信息，所述第一边缘配置服务器是所述UE根据策略信息，在至少两个边缘配置服务器中确定的，所述策略信息包括每个边缘配置服务器的第二类信息，所述第二类信息包括每个边缘配置服务器对应的数据网络名称的信息和/或单一网络切片选择辅助信息；所述第二网元根据所述第二类信息和/或所述指示信息确定第三网元，所述第三网元支持所述UE访问所述第一边缘配置服务器。
根据该技术方案，第二网元可以根据第一边缘配置服务器的数据网络名称、或者单一网络切片选择辅助信息、或者指示信息确定第三网元，使得该第三网元支持UE访问第一边缘配置服务器，从而保障用户边缘业务的体验。
结合第二方面，在第二方面的某些实现方式中，所述策略信息还包括每个边缘配置服务器的第一类信息，所述第一类信息包括以下信息的一项或多项：每个边缘配置服务器对应的服务范围的信息、优先级的信息、标识信息。
基于上述技术方案，本申请中的策略信息还可以包括边缘配置服务器对应的服务范围的信息、优先级的信息、标识信息等，从而使得UE可以在多个ECS中确定目标ECS，保障用户边缘业务体验。
结合第二方面，在第二方面的某些实现方式中，所述策略信息包括每个边缘配置服务器的优先级信息，所述第一边缘配置服务器是所述UE根据策略信息，在至少两个边缘配置服务器中确定的，包括：如果多个边缘配置服务器的优先级不同，则所述第一边缘配置服务器为优先级最高的边缘配置服务器。
结合第二方面，在第二方面的某些实现方式中，所述策略信息包括每个边缘配置服务器的优先级信息和服务范围的信息，所述第一边缘配置服务器是所述UE根据策略信息，在至少两个边缘配置服务器中确定的，包括：如果多个边缘配置服务器的优先级相同，则所述第一边缘配置服务器为所述UE根据边缘配置服务器的服务范围和UE的位置信息确定的。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：所述第二网元从所述UE接收会话修改请求，所述会话修改请求包括第一请求，所述第一请求用于所述UE向所述第一边缘配置服务器请求配置信息；所述第二网元向所述第三网元发送所述会话修改请求。
基于上述技术方案，第二网元可以建立会话修改请求，通过该PDU会话修改流程访问第一边缘配置服务器，从而保障用户边缘业务的体验。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：所述第二网元从第一 网元接收至少两个边缘配置服务器所对应的策略信息；所述第二网元向所述UE发送所述策略信息。
第三方面，提供了一种获取边缘服务的方法，该方法包括：用户设备UE向第三网元发送会话建立请求，所述会话建立请求中包括边缘配置服务器的数据网络名称和第二指示信息，所述第二指示信息用于指示所述UE向边缘配置服务器请求配置信息；所述UE接收来自第一网元的策略信息，所述策略信息包括第二边缘配置服务器的标识信息和数据网络名称，所述策略信息用于指示所述UE通过所述会话访问所述第二边缘配置服务器，所述第二边缘配置服务器是第三网元根据所述第二指示信息确定的；所述UE根据所述策略信息确定通过所述会话访问所述第二边缘配置服务器。
本申请中，第三网元可以根据第二指示信息确定UE需要访问边缘配置服务器，之后，第三网元可以根据本地配置和/或从UDM获取签约信息等因素确定目标ECS，例如，第二ECS。
在多ECS的场景下，根据本实施的方法，使得网络设备可以在多ECS中通过各个ECS与各自DNN的对应关系确定UE需要访问的目标ECS，从而保障用户的边缘业务的体验。从而解决了现有技术中，多ECS场景中网络设备无法确定目标ECS的问题。
结合第三方面，在第三方面的某些实现方式中，所述会话建立请求中还包括：第一指示信息，所述第一指示信息用于指示所述UE的能力。
基于上述技术方案，UE向AMF发送的会话建立请求中可以包含第一指示信息，从而使得AMF可以根据该第一指示信息或者第二指示信息或者数据网络名称确定SMF，该SMF支持UE访问第一边缘配置服务器，保障用户边缘业务的体验。
结合第三方面，在第三方面的某些实现方式中，所述第一网元为策略控制网元，所述第二网元为移动管理网元，所述第三网元为会话管理网元。
第四方面，提供了一种获取边缘服务的方法，该方法包括：第二网元从用户设备UE接收会话建立请求，会话建立请求中包括边缘配置服务器的数据网络名称和/或指示信息，指示信息包括第一指示信息和/或第二指示信息，其中，第一指示信息用于指示UE的能力，所述第二指示信息用于指示UE向所述边缘配置服务器请求配置信息；第二网元根据数据网络名称和/或指示信息确定第三网元，第三网元支持UE访问第二边缘配置服务器，第二边缘配置服务器是第三网元根据指示信息确定的。
根据本技术方案，第二网元可以根据第二边缘配置服务器的数据网络名称和/或指示信息确定第三网元，使得该第三网元支持UE访问第一边缘配置服务器，从而保障用户边缘业务的体验。
结合第四方面，在第四方面的某些实现方式中，该方法还包括：所述第二网元从所述UE接收会话修改请求，所述会话修改请求包括第一请求，所述第一请求用于所述UE向所述第二边缘配置服务器请求配置信息；所述第二网元向所述第三网元发送所述会话修改请求。
结合第四方面，在第四方面的某些实现方式中，该方法还包括：所述第二网元从第一网元接收策略信息，所述策略信息包括第二边缘配置服务器的标识信息和数据网络名称，所述策略信息用于指示所述UE通过所述会话访问所述第二边缘配置服务器；所述第二网元向所述UE发送所述策略信息。
结合第四方面，在第四方面的某些实现方式中，所述第一网元为策略控制网元，所述第二网元为移动管理网元，所述第三网元为会话管理网元。
第五方面，提供了一种获取边缘服务的装置，该装置可以是终端设备，例如，用户设备UE。该装置也可以是芯片。该装置具有实现上述第一方面或第三方面中任一方面或任一方面中任意可能的实现方式中用户设备UE的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块或单元。
第六方面，提供了一种获取边缘服务的装置，该装置可以是第二网元，例如，移动管理网元。该装置也可以是芯片。该装置具有实现上述第二方面或第四方面中任一方面或任一方面中任意可能的实现方式中第二网元的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块或单元。
第七方面，提供了一种获取边缘服务的装置，包括处理器。该处理器与存储器耦合，可用于执行存储器中的指令，以实现上述第一方面或第三方面中任一方面或任一方面中任意可能的实现方式中终端设备的功能，终端设备例如可以是用户设备UE。可选地，该装置还包括存储器。可选地，该装置还包括通信接口，处理器与通信接口耦合。
在一种实现方式中，该装置为终端设备。当该装置为终端设备时，该通信接口可以是收发器，或，输入/输出接口。
在另一种实现方式中，该装置为配置于终端设备中的芯片。当该装置为配置于终端设备中的芯片时，该通信接口可以是输入/输出接口。
可选地，所述收发器可以为收发电路。可选地，所述输入/输出接口可以为输入/输出电路。
第八方面，提供了一种获取边缘服务的装置，包括处理器。该处理器与存储器耦合，可用于执行存储器中的指令，以实现上述第二方面或第四方面中任一方面或任一方面中任意可能的实现方式中第二网元的功能，第二网元例如可以是移动管理网元。可选地，该装置还包括存储器。可选地，该装置还包括通信接口，处理器与通信接口耦合。
在一种实现方式中，该装置为第二网元，例如AMF。当该装置为终端设备时，该通信接口可以是收发器，或，输入/输出接口。
在另一种实现方式中，该装置为配置于第二网元中的芯片。当该装置为配置于终端设备中的芯片时，该通信接口可以是输入/输出接口。
可选地，所述收发器可以为收发电路。可选地，所述输入/输出接口可以为输入/输出电路。
第九方面，提供了一种处理器，包括：输入电路、输出电路和处理电路。所述处理电路用于通过所述输入电路接收信号，并通过所述输出电路发射信号，使得所述处理器执行上述第一方面至第四方面中任一方面或任一方面中任一种可能实现方式中的方法。
在具体实现过程中，上述处理器可以为芯片，输入电路可以为输入管脚，输出电路可以为输出管脚，处理电路可以为晶体管、门电路、触发器和各种逻辑电路等。输入电路所接收的输入的信号可以是由例如但不限于接收器接收并输入的，输出电路所输出的信号可以是例如但不限于输出给发射器并由发射器发射的，且输入电路和输出电路可以是同一电路，该电路在不同的时刻分别用作输入电路和输出电路。本申请实施例对处理器及各种电 路的具体实现方式不做限定。
第十方面，提供了一种装置，包括处理器和存储器。该处理器用于读取存储器中存储的指令，并可通过接收器接收信号，通过发射器发射信号，以执行第一方面至第四方面中任一方面或者任一方面中任一种可能实现方式中的方法。
可选地，所述处理器为一个或多个，所述存储器为一个或多个。
可选地，所述存储器可以与所述处理器集成在一起，或者所述存储器与处理器分离设置。
在具体实现过程中，存储器可以为非瞬时性(non-transitory)存储器，例如只读存储器(read only memory，ROM)，其可以与处理器集成在同一块芯片上，也可以分别设置在不同的芯片上，本申请实施例对存储器的类型以及存储器与处理器的设置方式不做限定。
应理解，相关的数据交互过程例如发送指示信息可以为从处理器输出指示信息的过程，接收能力信息可以为处理器接收输入能力信息的过程。具体地，处理输出的数据可以输出给发射器，处理器接收的输入数据可以来自接收器。其中，发射器和接收器可以统称为收发器。
上述第十方面中的装置可以是芯片，该处理器可以通过硬件来实现也可以通过软件来实现，当通过硬件实现时，该处理器可以是逻辑电路、集成电路等；当通过软件来实现时，该处理器可以是一个通用处理器，通过读取存储器中存储的软件代码来实现，该存储器可以集成在处理器中，可以位于该处理器之外，独立存在。
第十一方面，提供了一种计算机程序产品，所述计算机程序产品包括：计算机程序(也可以称为代码，或指令)，当所述计算机程序被运行时，使得计算机执行上述第一方面至第四方面中任一方面或任一方面中任一种可能实现方式中的方法。
第十二方面，提供了一种计算机可读介质，所述计算机可读介质存储有计算机程序(也可以称为代码，或指令)，当其在计算机上运行时，使得计算机执行上述第一方面至第四方面中任一方面或任一方面中任一种可能实现方式中的方法。
第十三方面，提供了一种芯片系统，包括处理器，用于从存储器中调用并运行计算机程序，使得安装有该芯片系统的设备执行上述第一方面至第四方面任一方面或任一方面中任一种可能实现方式中的方法。
第十四方面，提供了一种系统，所述系统包括第五方面涉及的装置、第六方面涉及的装置。
附图说明
图1是本申请实施例适用系统架构图。
图2是本申请实施例边缘业务架构示意图。
图3是本申请提供的获取边缘服务的方法300的示意性流程图。
图4是本申请提供的获取边缘服务的方法400的示意性流程图。
图5是本申请提供的获取边缘服务的方法500的示意性流程图。
图6是本申请提供的获取边缘服务的装置100的示意性框图。
图7是本申请提供的获取边缘服务的装置200的示意性框图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
本申请实施例提及的无线通信系统包括但不限于：全球移动通信(global system of mobile communication，GSM)系统、长期演进(long term evolution，LTE)频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)、LTE系统、先进的长期演进(LTE-Advanced，LTE-A)系统、下一代通信系统(例如，6G通信系统)、多种接入系统的融合系统，或演进系统。
本申请提供的技术方案还可以应用于机器类通信(machine type communication，MTC)、机器间通信长期演进技术(Long Term Evolution-machine，LTE-M)、设备到设备(device to device，D2D)网络、机器到机器(machine to machine，M2M)网络、物联网(internet of things，IoT)网络或者其他网络。其中，IoT网络例如可以包括车联网。其中，车联网系统中的通信方式统称为车到其他设备(vehicle to X，V2X，X可以代表任何事物)，例如，该V2X可以包括：车辆到车辆(vehicle to vehicle，V2V)通信，车辆与基础设施(vehicle to infrastructure，V2I)通信、车辆与行人之间的通信(vehicle to pedestrian，V2P)或车辆与网络(vehicle to network，V2N)通信等。
本申请实施例中所涉及到的终端设备可以包括各种具有无线通信功能的接入终端、移动设备、用户终端或用户装置。例如，终端设备可以为用户设备(user equipment，UE)，例如，手机(mobile phone)、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端设备、增强现实(augmented reality，AR)终端设备等。终端设备也可是工业控制(industrial control)中的无线终端、机器类型通信(machine type communication，MTC)终端、客户终端设备(customer premise equipment，CPE)、无人驾驶(self-driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)、蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，5G网络中的终端设备或者未来演进的公用陆地移动通信网络(public land mobile network，PLMN)中的终端设备等。
下面结合图1和图2详细介绍本申请实施例涉及网络系统架构以及该架构下的边缘业务架构。
图1是本申请实施例适用的系统架构图，如图所示，该网络架构具体可以包括下列网元：
1、无线接入网(radio access network，RAN)：基于无线通信技术实现接入网络功能的接入网可以称为无线接入网。无线接入网能够管理无线资源，为终端提供接入服务，进而完成控制信号和用户数据在终端和核心网之间的转发。
本申请所涉及的无线接入网设备可以是具有无线收发功能的设备。该无线接入网设备可以是提供无线通信功能服务的设备，通常位于网络侧，包括但不限于：第五代(5th generation，5G)通信系统中的下一代基站(gNodeB，gNB)、第六代(6th generation，6G)移动通信系统中的下一代基站、未来移动通信系统中的基站或WiFi系统中的接入节点等， LTE系统中的演进型节点B(evolved node B，eNB)、无线网络控制器(radio network controller，RNC)、节点B(node B，NB)、基站控制器(base station controller，BSC)、家庭基站(例如，home evolved NodeB，或home Node B，HNB)、基带单元(base band unit，BBU)，传输接收点(transmission reception point，TRP)、发射点(transmitting point，TP)、基站收发台(base transceiver station，BTS)等。在一种网络结构中，该接入网设备可以包括集中单元(centralized unit，CU)节点、或分布单元(distributed unit，DU)节点、或包括CU节点和DU节点的RAN设备、或者控制面CU节点和用户面CU节点，以及DU节点的RAN设备。接入网设备为小区提供服务，用户设备通过该小区使用的传输资源(例如，频域资源，或者说，频谱资源)与基站进行通信，该小区可以是基站(例如基站)对应的小区，小区可以属于宏基站，也可以属于小小区(small cell)对应的基站，这里的小小区可以包括：城市小区(metro cell)、微小区(micro cell)、微微小区(pico cell)、毫微微小区(femto cell)等，这些小小区具有覆盖范围小、发射功率低的特点，适用于提供高速率的数据传输服务。无线接入网设备可以是宏基站，也可以是微基站或室内站，还可以是中继节点或施主节点，V2X通信系统中的为用户设备提供无线通信服务的设备、云无线接入网络(cloud radio access network，CRAN)场景下的无线控制器、中继站、车载设备、可穿戴设备以及未来演进网络中的网络设备等。本申请的实施例对无线接入网设备所采用的具体技术和具体设备形态不做限定。
2、认证服务功能(authentication server function，AUSF)网元：主要用于用户鉴权等。
3、接入和移动性管理功能网元(access and mobility management function，AMF)：主要用于移动性管理和接入管理等，可以用于实现移动性管理实体(mobility management entity，MME)功能中除会话管理之外的其它功能，例如，合法监听、或接入授权(或鉴权)等功能。在本申请实施例中，可用于实现接入和移动管理网元的功能。
4、会话管理功能网元(session management function，SMF)：主要用于会话管理、终端设备的IP地址分配和管理、选择和管理用户平面功能、策略控制、或收费功能接口的终结点以及下行数据通知等。在本申请实施例中，可用于实现会话管理网元的功能。
5、策略控制网元(policy control function，PCF)：用于指导网络行为的统一策略框架，为控制平面功能网元(例如AMF，SMF网元等)提供策略规则信息等。
6、应用功能网元(application function，AF)：用于进行应用影响的数据路由，接入网络开放功能网元，或，与策略框架交互进行策略控制等。
7、统一数据管理网元(unified data management，UDM)：用于统一数据管理、5G用户数据管理、处理用户标识、接入鉴权、注册、或移动性管理等。
8、用户面功能网元(user plane function，UPF)：可用于分组路由和转发、或用户面数据的服务质量(quality of service，QoS)处理等。用户数据可通过该网元接入到数据网络(data network，DN)。在本申请实施例中，可用于实现用户面网元的功能。
9、网络切片选择功能网元(network slice selection function，NSSF)：用于管理网络切片相关的信息。
10、数据网络(digital network，DN)：用于提供传输数据的网络。例如，运营商业务的网络、因特(Internet)网、第三方的业务网络等。
另外，上述网络架构还包括网络存储功能网元((networkrepository function，NRF)： 用于保存网络功能实体以及其提供服务的描述信息，以及支持服务发现，网元实体发现等功能；网络开放功能网元(network exposure function，NEF)：用于安全地向外部开放由第三代合作伙伴计划(3GPP)网络功能提供的业务和能力等。统一数据存储功能网元(unified data repository，UDR)，用于UDM存储订阅数据或读取订阅数据以及PCF存储策略数据或者读取策略数据。
在该网络架构中，N2接口为RAN和AMF网元的接口，用于非接入层(non-access stratum，NAS)消息的发送等；N3接口为RAN和UPF网元之间的接口，用于传输用户面的数据等；N4接口为SMF网元和UPF网元之间的接口，用于传输例如N3连接的隧道标识信息，数据缓存指示信息，以及下行数据通知消息等信息。
应理解，上述应用于本申请实施例的网络架构仅是举例说明的从传统点到点的架构和服务化架构的角度描述的网络架构，适用本申请实施例的网络架构并不局限于此，任何能够实现上述各个网元的功能的网络架构都适用于本申请实施例。
应理解，图1中的各个网元之间的接口名称只是一个示例，具体实现中接口的名称可能为其他的名称，本申请对此不作具体限定。此外，上述各个网元之间的所传输的消息(或信令)的名称也仅仅是一个示例，对消息本身的功能不构成任何限定。
图2是本申请实施例边缘业务架构示意图，如图所示，该网络架构具体可以包括：边缘数据网络(edge data network，EDN)(包括：边缘使能服务器(edge enabler server，EES)边缘应用服务器(edge application server，EAS))、边缘配置服务器(edge configuration server，ECS)以及用户设备(user equipment，UE)。
其中，EDN可以是本地数据中心，EDN包含一个或多个EES和EAS，每个EDN有特定的服务范围。
用户设备(user equipment，UE)中可以包括：边缘使能客户端(edge enabler client，EEC)和应用客户端，其中，EEC为终端上的应用客户端提供必要的支持，EEC的功能包括：通过EDGE-4检索EDN信息、UE注册到EES、检索可用的EAS、EAS可用性变化、EAS迁移通知给EEC。
ECS网元(也可称之为，边缘数据网络配置服务器(edge data network configuration server，EDNCS))可以是全局管理网元，维护各个EDN的信息，包括边缘数据网络的服务范围和边缘数据网络中的边缘使能服务器EES地址等。其中，边缘数据网络的服务范围可以是拓扑地址信息(例如Cell ID、TAI(Track area id)等)或几何地址信息(例如，省、市、区或经纬度等信息)，服务范围可以是地址信息的集合。在一种实现方式中，ECS网元是分布式部署的，即每个ECS可以管理不同区域的边缘数据网络。应该理解ECS网元可以与其它网元合设也可以是独立的网元，本申请对ECS网元在网络架构中的部署情况并不做任何限定。
EES网元，可以是MEC节点中的控制网元或者管理网元，负责管理部署在该EDN里的各个EAS，比如注册，DNS解析内容路由选择、上层应用注册管理、无线信息交互等基础功能。此外，EES可以调用3GPP网络中的能力开放功能网元。应该理解EES网元可以与其它网元合设也可以是独立的网元，本申请对EES网元在网络架构中的部署情况并不做任何限定。
上述EES，EAS，ECS等都可以称之为AF(application function)，以下不再赘述。
下面对图2中的各个参考点的功能进行简单的介绍。
图2中的EDGE-8参考点支持边缘配置服务器和核心网之间的交互，它支持：(1)访问用于检索网络能力信息的核心网功能和应用程序接口(application programming interface，API)；(2)向核心网(例如：SMF)提供业务发放通知。EDGE-1：EES与EEC之间的接口，支持EEC在EES的注册/去注册；边缘数据网络中的边缘应用服务器发现。EDGE-2：EES与3GPP核心网之间的接口，用于EES获取3GPP网络能力。EDGE-3：EES与EAS之间的接口，支持EES注册/去注册EAS，包括EAS的可用性信息、服务范围信息、地址信息等；EES给EAS提供3GPP网络能力信息(如位置信息)。EDGE-4：EEC与ECS之间的接口，支持ECS提供/推送配置信息给EEC。EDGE-5：AC与EEC之间的接口，支持AC从EEC获取接入的EAS信息。EDGE-6：ECS与EES之间的接口，支持在ECS上配置EES信息。EDGE-7：EAS与3GPP核心网之间的接口，支持EAS获取3GPP网络能力。EDGE-8：ECS与3GPP核心网之间的接口，支持ECS获取3GPP网络能力。EDGE-9：跨MEC节点/同一MEC节点内不同EES之间的接口，支持做应用迁移。
上述内容简要阐述了本申请实施例的系统架构和可能的应用场景，为更好地理解本申请实施例的技术方案，在开始介绍本申请实施例之前，首先对本申请涉及到的名词或术语进行简单介绍。
1)数据网络名称(data network name，DNN)：数据网络名称DNN可以用于选择建立协议数据单元(protocol data unit，PDU)会话的SMF和UPF，也可以用于确定应用于该PDU会话的策略。DNN的组成有两部分：1)网络标识(identification，ID)，这部分表示一个外部网络，是必选的；2)运营商ID，这部分表示其属于哪个运营商，是可选的。
2)单一网络切片选择辅助信息(single network slice selection assistance information，S-NSSAI)：可以唯一标识一个网络切片，可能包含一个或多个的数据网络名称DNN，供AMF进行选择。其中，DNN中指定了为PDU会话所选择的SMF。NSSAI是S-NSSAI的集合，可以标识一组网络切片。UE进行业务时可以通过S-NSSAI选择对应的切片组(包括AMF/SMF/UPF)。当UE进行附着(attach)的时候，UE会提供S-NSSAI信息，gNB根据S-NSSAI信息来选择5G核心网(5G Core Network，5GC)；如果UE没有提供相关的S-NSSAI信息，那么gNB会把UE的NAS信息路由到一个缺省的5GC。
3)UE路由选择策略(UE route selection policy，URSP)：是一张包含一个或者多个URSP规则(rule)的列表。URSP中的每个URSP规则由该规则的规则优先级(precedence)、流量描述符(traffic descriptor)和路由选择描述符(route selection descriptor，RSD)列表组成。每个规则的优先级各不相同，且各个规则按照优先级从高到低排序。优先级决定了UE使用URSP规则的顺序。
流量描述符由一个或者多个组件(component)组成，可以包括：应用描述符(application descriptor)、互联网协议(Internet protocol，IP)描述符(IP descriptor)，例如：目的IP、域描述符(domain descriptor)，例如，全限定域名(fully qualified domain name，FQDN)、非IP描述符(non-IP descriptor)、DNN描述符以及连接能力(connection capabilities)。流量描述符可以供UE使用，从而进行应用匹配。
路由选择描述符RSD列表包含一个或者多个RSD，每个RSD由各自的RSD优先级 (RSD precedence)、路由选择组件(route selection components)和路由选择校验标准(route selection verification criteria)组成。其中，RSD优先级决定了使用RSD顺序，当优先级高的RSD无法使用时，才使用其他RSD。路由选择组件描述了应用可以使用的各种网络资源，它由一个或多个组件组成，可以包括业务和会话连续性(serviceandsessioncontinuity，SSC)模式选择(SSC mode selection)、网络切片选择(network slice selection)、DNN选择(DNN selection)、PDU会话类型选择(PDU session type selection)、有缝卸载指示(non-seamless offload indication)、接入类型优先级(access type preference)。路由选择校验标准描述了对应的生效条件，它包括时间窗口(time window)和位置标准(location criteria)，如果当前时间不在时间窗口内或者UE位置不匹配位置标准，则认为RSD无效。
对于每个应用，UE会依照规则的优先级自高而低依次查询某条规则是否适用，如果查询到一条规则适用则使用此规则；如果除优先级外的规则都不适用，则使用优先级最低的规则，该规则相当于默认规则，适用于全部应用。其中，每一条规则都对应着一种特定的PDU会话(包括：会话类型、SSC模式、切片、DNN等)，当对应的会话存在时，该应用使用该会话；当会话不存在时，则建立新的符合要求的会话。
也可以理解为，URSP可以用来让终端选择(或建立)PDU会话(或切片)。UE可以根据URSP策略确定检测到的应用程序是否可以与已建立的PDU会话相关联，是否可以卸载到PDU会话之外的非3GPP接入，或者是否可以触发新PDU会话的建立。当业务描述符中的每个组件与来自应用程序的相应信息匹配时，该URSP规则是适用的。当来自应用程序的相应信息与流量描述符组件中的任何值都不匹配，或者没有来自应用的相应信息可用时，该URSP规则不适用。具体地，URSP的使用规则和流程可以参考协议TS 24.526，此处不再赘述。
目前，UE要获取边缘配置服务器ECS的地址信息一般采用如下方案：ECS可以先将其地址信息发送UDM网元，UE向SMF请求获取ECS的地址信息时，SMF可以根据本地配置或从UDM中获取UE的签约数据从而确定ECS地址，然后SMF将ECS的地址信息发送给UE。由上可知，目前网络侧只能确定一个ECS地址并发送给UE。然而，在多ECS地址的场景下，如果SMF根据本地配置或从UDM中获取了多个ECS地址时，SMF无法确定给UE发送哪个/哪些ECS；对于UE而言，即便收到了SMF发送的多个ECS的地址信息，UE也无法确定访问哪个ECS获取边缘网络配置信息，从而造成UE边缘业务的体验较差。
有鉴于此，本申请提供了一种获取边缘服务的方法，通过增强URSP机制，使得网络侧和UE可以确定ECS，从而保障用户边缘业务的体验。
下面将结合附图详细说明本申请实施例提供的方法。需要说明的是，在下文中结合附图描述实施例的过程中，图中仅为便于理解而示意，不应对本申请构成任何限定。各网元名称仅为区分不同的功能而定义，不应对本申请构成任何限定。本申请并不排除定义其他网元来实现相同或相似功能的可能。
本申请实施例中的标识消息可以指代地址信息，也就是说本申请实施例中的标识信息可以包括边缘服务器(例如，ECS)的地址信息。另外，还可以包括边缘服务器的标识(例如，ECS ID)，例如，边缘服务器的统一资源标识符(uniform resource identifier，URI)、边缘服务器的IP地址信息，标识信息还可以包括边缘服务器的实例标识符(instance ID)， 标识信息还可以包括边缘服务器的FQDN。换言之，本申请中，根据标识消息可以获取边缘服务器的地址信息。
需要说明的是，以上仅仅是对标识信息的举例，不应对本申请造成任何限定，本申请并未排除标识信息还可以是其它任何可以获取边缘服务器地址信息的信息。
图3是本申请提供的一种获取边缘服务的方法300的示意性框图。该方法包括：
步骤301，UE从第一网元接收至少两个边缘配置服务器所对应的策略信息。
该策略信息包括每个边缘配置服务器的第一类信息，所述第一类信息包括以下信息的一项或多项：每个边缘配置服务器对应的服务范围的信息、优先级的信息、标识信息。
在一种可能的实现方式中，用户设备UE可以从PCF接收多个ECS对应的策略信息，其中，每个ECS对应的策略信息每个边缘配置服务器的第一类信息，所述第一类信息包括以下信息的一项或多项：每个边缘配置服务器对应的服务范围的信息、优先级的信息、标识信息。
作为一个示例，UE可以从PCF接收3个ECS所对应的URSP(策略信息的一例)，例如，UE可以接收ECS#1、ECS#2和ECS#3的策略信息。如果UE只需要ECS优先级的信息，则策略信息中可以只包含各个ECS优先级的信息；如果UE除过ECS优先级的信息还需要ECS服务范围的信息，则策略信息中可以包含各个ECS优先级的信息和ECS服务范围的信息。如果UE需要ECS的标识信息，则策略信息中还可以包括ECS的标识信息。
本申请中，策略信息中的第一类信息内容可以灵活确定，以上各个情况仅仅是举例，不作限定。
本申请中，一个ECS可以对应一条URSP，此时，UE可以接收多个ECS对应的多条URSP。例如，UE可以接收ECS#1对应的URSP、ECS#2对应的URSP以及ECS#3对应的URSP。本申请中，也可以是多个ECS对应一条URSP，此时UE只需要接收一条URSP，该条URSP中包括3个ECS。
步骤302，UE根据该策略信息中的第一类信息，在至少两个边缘配置服务器中确定第一边缘配置服务器。
本实施例中，以UE接收3个ECS对应的URSP为例进行介绍，例如：以ECS#1、ECS#2和ECS#3对应的URSP为例。
作为一个示例，如果URSP中只包括ECS优先级的信息时，UE可以将ECS#1、ECS#2和ECS#3中优先级最高的那个ECS确定为第一ECS，例如，ECS#2的优先级最高，UE确定ECS#2为第一ECS。
作为一个示例，如果URSP中只包括ECS的服务范围的信息时，UE可以根据自身的位置信息以及ECS#1、ECS#2和ECS#3服务范围的信息共同确定第一ECS。例如，ECS#1的服务范围刚好覆盖UE当前所处的位置，此时，UE可以确定ECS#1为第一ECS。又例如，ECS#1、ECS#2和ECS#3的服务范围均覆盖了UE当前所处的位置，并且ECS#1距离UE最近，此时UE也可以确定ECS#1为第一ECS，等等。
作为另一个示例，如果URSP中包括各个ECS的优先级信息和ECS的服务范围的信息，如果多个边缘配置服务器的优先级相同，则UE可以根据边缘配置服务器的服务范围和UE的位置信息确定第一ECS。
本申请中，在多ECS的场景下，如果UE接收的ECS对应的URSP中包括多个信息时，UE可以灵活确定第一ECS。
可选的，本申请中的策略信息还可以包括每个边缘配置服务器的第二类信息，第二类信息包括每个边缘配置服务器对应的数据网络名称的信息和/或单一网络切片选择辅助信息。
在一些实施例中，UE还可以根据该策略信息中的第二类信息请求建立第一边缘配置服务器对应的协议数据单元PDU会话。在一种可能的实现方式中，UE可以创建与ECS#1对应的DNN和S-NSSAI的会话。例如，UE可以向AMF请求建立第一ECS(例如，ECS#1)对应的协议数据单元PDU会话。该会话中包括ECS#1对应的DNN和/或S-NSSAI。之后，UE可以通过该PDU会话访问第一边缘配置服务器。
在多ECS的场景下，根据本实施的方法，使得UE在多ECS中根据接收到的URSP中的各个ECS与各自服务范围、优先级的对应关系确定需要访问的目标ECS，并且UE可以根据DNN、N-SSAI建立目标ECS的PDU会话，通过该会话访问边缘业务，从而保障用户的边缘业务的体验。也就是说，本申请通过增强现有URSP机制，在对现有技术改动较小的情况下实现了UE在多个ECS中确定需要访问的目标ECS的技术效果，保障用户的边缘业务的体验。
图4是本申请提供的一种获取边缘服务的方法400的示意性流程图，图4所示的方法400可以由图1所示的系统中的AMF、SMF、NEF、UDM、PCF和ECS等网元执行。如图4所示，该方法包括步骤401至412，本实施例以UE#1为例进行说明，下面详细描述每个步骤。
步骤401，ECS向UDM发送自身的配置信息。
ECS的配置信息包括：ECS的数据网络名称DNN信息、ECS服务范围信息、ECS优先级信息、ECS标识信息(也可以理解，ECS对应的或关联的标识信息)、ECS的单一网络切片选择辅助信息S-NSSAI等信息。
在一种可能的实现方式中，ECS可以调用NEF的参数提供服务，例如，parameter provisionservice发送所述配置信息给NEF，再由NEF将该配置信息发送给UDM或UDR。
本申请中，步骤401中的ECS可以有一个或者多个，当有多个ECS时，各个ECS可以分别将其各种的配置信息发送给UDM。
可选的，UDM也可以将配置信息发送到UDR，由UDR存储该配置信息。
步骤402，UDM或UDR向PCF发送通知信息，通知UE的签约数据发生改变。对应的，PCF接收该通知信息。
其中，所述PCF可以是服务该UE，例如，UE#1的PCF。
在一种可能的实现方式中，PCF可以先向UDM或者UDR订阅UE的签约数据改变事件的通知，后续当UDM或UDR检测到UE的签约数据发生改变时可以发送通知信息给PCF。
作为一个示例，所述通知信息中可以包含ECS配置信息，例如，ECS的数据网络名称DNN信息、ECS服务范围信息、ECS优先级信息中的一个或多个。作为另一个示例，所述通知信息中还可以包含ECS标识信息(也可以理解，ECS对应的或关联的标识信息)、ECS的S-NSSAI等信息。
步骤403，PCF生成用户路由选择策略URSP(策略信息的一例)。
该URSP中可以包括每个边缘配置服务器的第一类信息，其中，第一类信息包括以下信息的一项或多项：每个边缘配置服务器对应的服务范围的信息、优先级的信息、标识信息。
在一些实施例中，该URSP中还可以包括每个边缘配置服务器的第二类信息，其中，第二类信息包括每个边缘配置服务器对应的数据网络名称的信息和/或单一网络切片选择辅助信息。
在一种可能的实现方式中，PCF可以从UDM或UDR收到通知消息后，生成用户路由选择策略URSP。
其中，ECS的DNN信息和S-NSSAI信息可以包含于URSP中路由选择描述符的路由选择组件(route selection components)字段中。ECS的服务范围信息可以包含于URSP中路由选择描述符的位置标准(location criteria)字段中。ECS标识信息可以包含于URSP中流量描述符的IP描述符(IP descriptor)或者域描述符(domain descriptor)中。ECS的优先级信息可以包含于URSP中优先级值(precedence value)字段中。
在一些场景中，PCF还可以根据本地配置或策略信息或签订的服务层协议(service layer agreement，SLA)重新确定各ECS的优先级，即PCF可能对步骤401中ECS的优先级进行调整。
本申请中，一个ECS可以对应一条URSP，多个ECS可以对应多条URSP，多个ECS也可以对应一条URSP，不作限定。
步骤404，PCF向UE#1发送URSP。对应的，UE#1可以接收并保存该URSP。
步骤405，UE#1根据URSP中的第一类信息确定第一ECS。
在一种可能的实现方式中，若多个ECS对应的优先级不同，则UE#1可以选择优先级最高的ECS。例如，优先级最高的ECS为ECS#1(为方便描述，本实施例将确定的ECS记为ECS#1)，此时，UE#1确定通过ECS#1获取边缘配置信息。该边缘配置信息例如可以包括EES的标识信息等。
在另一种可能的实现方式中，若优先级最高的ECS有多个，则UE#1还可以根据ECS的服务范围和UE#1位置确定ECS，即选择服务范围包含了UE#1位置的ECS进行通信。例如，优先级最高的ECS有ECS#1、ECS#2、ECS#5，此时，UE#1可以通过各个ECS的服务范围以及自己的位置信息确定通过ECS#1获取边缘配置信息。该边缘配置信息例如可以包括EES的标识信息等。
具体地，可以参照方法300中的步骤302，此处不再赘述。
情况一：如果UE#1已经建立了ECS#1对应的DNN和S-NSSAI的会话，此时，UE可以直接通过该会话发送第一请求，第一请求用于向第一ECS请求配置信息，后续步骤无须执行。
作为示例而非限定，第一请求例如可以是：服务配置请求(service provisioning request)、服务订阅请求(service provisioning subscription request)、服务订阅更新请求(service provisioning subscription update request)、服务取消订阅请求(service provisioning unsubscribe request)。下述描述中，出现的service provisioning requestinformation element(service provisioning requestIE)，也可以是此处的各个请求。
情况二：如果UE尚未建立ECS#1对应的DNN和S-NSSAI的会话，此时，还需要执行步骤406至步骤410。
方式一：
步骤406，UE#1创建与ECS#1对应的DNN和S-NSSAI的会话。
在一种可能的实现方式中，UE#1可以根据策略信息中的第二类信息请求建立ECS#1对应的协议数据单元PDU会话。例如，UE#1可以向AFM发送会话建立请求，会话建立请求中包含ECS#1对应的DNN和/或S-NSSAI。
可选的，会话建立请求中还可以包含指示信息#1，指示信息#1用于指示UE#1能力。本申请中，UE#1的能力可以指UE#1(或者也可以指EEC)支持接收ECS配置信息的能力。
可选的，会话建立请求中还可以包含指示信息#2，指示信息#2用于指示UE#1向第一ECS(例如，ECS#1)请求配置信息(例如，service provisioning request IE)。该请求的配置信息例如可以包括EES的标识信息等。
可选的，会话建立请求中还包含ECS#1标识信息。
步骤407，AMF根据DNN和/或指示信息确定SMF。
本申请考虑到并不是所有的SMF都具备(也可以理解为“支持”)将service provisioning request IE发送给ECS的能力，因此需要确定合适的SMF。
作为一个示例，如果UE通过一个默认的(default)DNN或公共的(common)DNN，例如，互联网接入点名称(internet access point name，APN)访问ECS#1。此时，AMF可以根据步骤406中的指示信息(例如，指示信息#1和/或指示信息#2)选择(也可以理解为，确定)特定的SMF，即选择一个具备将service provisioning request IE发送给ECS能力的SMF。作为另一个示例，如果ECS#1属于特别的DNN，AMF可以根据DNN就选择SMF，即特定的SMF才能服务该DNN。
步骤408，AMF向该SMF发送创建会话上下文请求。对应的，SMF可以从AMF接收创建会话上下文请求。
可选的，创建会话上下文请求中还可以包含第一请求(例如，service provisioning request IE)和ECS#1的标识信息。
可选的，在一些实施例中，还可以包括步骤409，SMF从AMF收到创建会话上下文请求，如果该请求中未携带ECS#1的标识信息，此时，SMF可从UDM或PCF获取ECS#1标识信息；或者，SMF可以根据本地配置和/或签约信息等确定ECS#1标识信息。这是由于，步骤401中各个ECS已经将各自的配置信息发送给UDM，因此，SMF可以根据该创建会话上下文请求对应的DNN和S-NSSAI等信息确定是哪个ECS。
步骤410，SMF将第一请求(例如，service provisioning request IE)发送给ECS#1。对应的，ECS#1接收第一请求。
本申请中，步骤406至步骤410中，描述了UE#1在会话建立流程中发送service provisioning request。会话建立流程的其它步骤还包括建立UE到UPF之间用户面路径的会话等为现有技术，不再赘述。
方式二：
在另一种实现方式中，UE#1也可以在会话建立完成后，可以通过会话修改请求访问ECS#1。作为一个示例，UE#1可以向AMF发送会话修改请求，该会话修改请求中包括第 一请求(例如，service provisioning request)。可选的，该会话修改请求可以包含ECS#1的标识信息。然后AMF可以向SMF发送该会话修改请求，SMF收到service provisioning request后，可以继续执行步骤409和步骤410，将service provisioning request发送到ECS#1。
步骤411，ECS#1确定向UE#1发送第一响应，第一响应中包括ECS#1需要向UE#1发送的配置信息。
在一种可能的实现方式中，第一响应可以是EES的标识信息，例如，EES#1的标识信息。
步骤412，ECS#1向UE#1发送第一响应，第一响应包括EES的标识信息。
在一种可能的实现方式中，ECS#1可以通过SMF发送service provisioning response给UE#1；或者，ECS#1可以先通过PCF向SMF发送service provisioning response，然后，通过SMF发送service provisioning response给UE#1。
在另一种可能的实现方式中，ECS#1可以通过UE到UPF之间用户面路径发送service provisioning response给UE#1。类似于步骤405，第一响应可以是：服务配置响应(service provisioning response)、服务订阅响应(service provisioning subscription response)、服务订阅更新响应(service provisioning subscription update response)或者服务取消订阅请求(service provisioning unsubscribe response)
在多ECS的场景下，根据本实施的方法，使得UE在多ECS中根据接收到的URSP中的各个ECS与各自优先级、服务范围的对应关系确定需要访问的目标ECS，并且UE可以根据DNN、N-SSAI建立目标ECS的PDU会话，通过该会话访问边缘业务，从而保障用户的边缘业务的体验。也就是说，本申请通过增强现有URSP机制，在对现有技术改动较小的情况下实现了UE在多个ECS中确定需要访问的目标ECS的技术效果，保障用户的边缘业务的体验。
图5是本申请提供的一种获取边缘服务的方法500的示意性流程图，图5所示的方法500可以由图1所示的系统中的AMF、SMF、NEF、UDM、PCF和ECS等网元执行。如图5所示，该方法包括步骤501至512，本实施例以UE#2为例进行说明，下面详细描述每个步骤。
步骤501，ECS向UDM发送自身的配置信息。
ECS的配置信息包括：ECS的数据网络名称DNN信息、ECS服务范围信息、ECS优先级信息。ECS标识信息(也可以理解，ECS对应的或关联的标识信息)、ECS单一网络切片选择辅助信息S-NSSAI等信息。
在一种可能的实现方式中，ECS可以调用NEF的参数提供服务，例如，parameter provision service发送所述配置信息给NEF，再由NEF将该配置信息发送给UDM或UDR。
步骤502，UE#2可以向AFM发送会话建立请求，会话建立请求中包含DNN和指示信息#2。
其中，指示信息#2用于指示UE#1向ECS请求配置信息(例如，service provisioning request IE)。该配置信息例如可以包括EES的标识信息等。
可选的，会话建立请求中还可以包含指示信息#1，指示信息#1用于指示UE#1能力。本申请中，UE#1的能力可以指UE#1支持接收ECS的能力。
步骤503，AMF根据DNN和/或指示信息确定SMF。
本申请考虑到并不是所有的SMF都具备(也可以理解为“支持”)将service provisioning request IE发送给ECS的能力，因此需要确定合适的SMF。
作为一个示例，如果UE通过一个默认的(default)DNN或公共的(common)DNN，例如，互联网接入点名称(internet access point name，APN)访问ECS#1。此时，AMF可以根据需步骤406中的指示信息(例如，指示信息#1和/或指示信息#2)选择(也可以理解为，确定)特定的SMF，即选择一个具备将service provisioning request IE发送给ECS能力的SMF。作为另一个示例，如果ECS#1属于特别的DNN，AMF可以只根据DNN就选择SMF，即特定的SMF才能服务该DNN。
步骤504，AMF向该SMF发送创建会话上下文请求。对应的，SMF可以从AMF接收创建会话上下文请求。
步骤505，SMF确定ECS的标识信息。
本实施例，以SMF确定ECS的标识信息为ECS#2(第二边缘配置服务的一例)为例进行说明。
本申请中，SMF可以根据指示信息#2确定UE需要访问边缘配置服务器，然后SMFSMF可以根据本地配置和/或从UDM获取签约信息等确定ECS#2标识信息。这是由于，步骤501中各个ECS已经将各自的配置信息发送给UDM，UDM中UE的签约信息或本地配置中已经保存了各个ECS配置信息。该配置信息例如包括，ECS的优先级信息、服务范围信息、DNN信息、S-NSSAI信息等。因此，SMF可以根据该创建会话上下文请求对应的DNN和S-NSSAI等信息确定是哪个ECS。
步骤506，SMF将确定的ECS#2的配置信息发送给PCF。
作为一个示例，SMF可以将确定的ECS#2标识信息和DNN发送给PCF。
步骤507，PCF根据ECS#2的配置信息，生成关于ECS#2的URSP，该URSP中包括ECS#2对应的标识信息和数据网络名称。
在一种可能的实现方式中，一旦SMF将确定的ECS#2的标识信息和数据网络名称发送给PCF，便可触发PCF生成关于ECS#2的URSP。例如，一旦SMF将确定的ECS#2的DNN和标识信息发送给PCF，便可触发PCF生成关于ECS#2的URSP，其中该URSP中包括ECS#2对应DNN和标识信息。
本实施中的URSP可以指示UE#2通过该DNN对应的会话(即UE当前请求建立的会话)访问确定的ECS#2。
具体地，在一种可能的实现方式中，ECS#2的DNN信息和S-NSSAI信息可以包含于URSP中路由选择描述符的路由选择组件(route selection components)字段中。ECS#2的服务范围信息可以包含于URSP中路由选择描述符的位置标准(location criteria)字段中。ECS#2标识信息可以包含于URSP中流量描述符的IP描述符(IP descriptor)或者域描述符(domain descriptor)中。ECS#2的优先级信息可以包含于URSP中优先级值(precedence value)字段中。
在一些实施例中，还可以包括步骤508，SMF保存所确定的ECS#2的标识信息。
步骤509，PCF向UE#2发送关于ECS#2的URSP。对应的，UE#2可以接收该URSP。
需要说明的是，本申请中步骤509可以在UE#2建立会话流程中执行，也可以在UE#2建立会话完毕后执行，本申请并不限定执行步骤509的时间。
步骤510，UE#2根据该URSP，确定通过当前建立的会话向ECS#2发送第一请求。
其中，第一请求用于UE#2向ECS#2请求配置信息，例如UE#2向ECS#2请求EES的标识信息。
作为示例而非限定，本申请中的第一请求例如可以是：服务配置请求(service provisioning request)、服务订阅请求(service provisioning subscription request)、服务订阅更新请求(service provisioning subscription update request)、服务取消订阅请求(service provisioning unsubscribe request)。下述描述中，出现的service provisioning request IE(information element)，也可以是此处的各个请求。
在另一种可能的实现方式中，UE#2可以在会话建立完成后，还可以通过会话修改访问ECS#2。作为一个示例，UE#2可以向AMF发送会话修改请求，该会话修改请求中包括第一请求，(例如，service provisioning request)。可选的，该会话修改请求还可以包含ECS#2的标识信息。应理解，如果步骤508，SMF保存所确定的ECS#2的标识信息时，此时，UE#2也可以无需携带ECS#2标识信息。然后AMF将该会话修改请求发送到SMF，SMF可以将第一请求(例如，service provisioning request)直接发送到所保存的ECS#2对应的地址。也就是说，此时，SMF可以直接向ECS#2发送第一请求。
步骤511，ECS#2确定向UE#2发送第一响应，第一响应中包括ECS#2向UE发送的配置信息。
在一种可能的实现方式中，第一响应可以是EES的标识信息。
步骤512，ECS#2向UE#2发送第一响应，第一响应包括EES的标识信息。
在一种可能的实现方式中，ECS#2可以通过SMF发送service provisioning response给UE#2；或者，ECS#2可以先通过PCF向SMF发送service provisioning response，然后，通过SMF发送service provisioning response给UE#1。
在另一种可能的实现方式中，ECS#2可以通过UE到UPF之间用户面路径发送service provisioning response给UE#1。类似于步骤510，第一响应可以是：服务配置响应(service provisioning response)、服务订阅响应(service provisioning subscription response)、服务订阅更新响应(service provisioning subscription update response)或者服务取消订阅请求(service provisioning unsubscribe response)
在多ECS的场景下，根据本实施的方法，使得网络设备可以在多ECS中通过各个ECS与各自服务范围、优先级以及标识信息的对应关系确定UE需要访问的目标ECS。并且网络设备可以将该确定的ECS的策略信息发送给UE，指示UE通过当前所建立的PDU会话访问该ECS，从而保障用户的边缘业务的体验。也就是说，本申请通过增强现有URSP机制，在对现有技术改动较小的情况下实现了网络设备在多个ECS中确定需要访问的目标ECS的技术效果，保障用户的边缘业务的体验。
需要说明的是，本申请中的为了便于清楚描述本申请实施例的技术方案，在本申请的实施例中，采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。例如，第一信息和第二信息仅仅是为了区分不同的信息，并不对其先后顺序进行限定。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。
本申请实施例中，“以下一项或多项”或其类似表达，是指的这些项中的任意组合， 包括单项或复数项的任意组合。例如，a，b，或c中的一项或多项，可以表示：a，b，c；a和b；a和c；b和c；或a和b和c。其中a，b，c可以是单个，也可以是多个。
可以理解，在本申请中，“如果…时”、“如果”均指在某种客观情况下装置会做出相应的处理，并非是限定时间，且也不要求装置实现时一定要有判断的动作，也不意味着存在其它限定。
以上，结合图3至图5详细说明了本申请实施例提供的获取边缘服务的方法。下面结合图6和图7介绍本申请实施例提供装置。应理解，装置实施例的描述与方法实施例的描述相互对应，因此，未详细描述的内容可以参见上文方法实施例，为了简洁，这里不再赘述。
上述主要从各个节点之间交互的角度对本申请实施例提供的方案进行了介绍。可以理解的是，各个节点，例如终端设备或者网络设备，为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对终端设备或者终端设备进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。下面以采用对应各个功能划分各个功能模块为例进行说明。
图6是本申请实施例提供装置100的示意性框图。如图所示，该装置100可以包括：收发单元110和处理单元120。
在一种可能的设计中，该装置100可以是上文方法实施例中的终端设备，例如，用户设备UE，也可以是用于实现上文方法实施例中终端设备的功能的芯片。应理解，该装置100可对应于根据本申请实施例的方法300、方法400、方法500中的UE，该装置100可以执行本申请实施例的方法300、方法400、方法500中的UE所对应的步骤。应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
具体地，收发单元用于接收至少两个边缘配置服务器所对应的策略信息，所述策略信息包括每个边缘配置服务器的第一类信息，所述第一类信息包括以下信息的一项或多项：每个边缘配置服务器对应的服务范围的信息、优先级的信息、标识信息；所述处理单元用于根据所述策略信息中的第一类信息，在所述至少两个边缘配置服务器中确定第一边缘配置服务器。
在一些实施例中，所述策略信息还包括每个边缘配置服务器的第二类信息，所述第二类信息包括每个边缘配置服务器对应的数据网络名称的信息和/或单一网络切片选择辅助信息，所述处理单元还用于根据所述策略信息中的第二类信息请求建立所述第一边缘配置服务器对应的协议数据单元PDU会话；所述装置通过所述PDU会话访问所述第一边缘配 置服务器。
在一些实施例中，所述收发单元用于发送会话建立请求，所述会话建立请求中包括数据网络名称和第二指示信息，所述第二指示信息用于指示所述装置向边缘配置服务器请求配置信息；所述收发单元用于接收策略信息，所述策略信息包括第二边缘配置服务器的标识信息和数据网络名称，所述策略信息用于指示所述装置通过所述会话访问所述第二边缘配置服务器，所述第二边缘配置服务器是第三网元根据所述第二指示信息确定的；所述装置根据所述策略信息确定通过所述会话访问所述第二边缘配置服务器。
在一种可能的设计中，该装置100可以是上文方法实施例中的第二网元，例如，AMF，也可以是用于实现上文方法实施例中第二网元的功能的芯片。应理解，该装置100可对应于根据本申请实施例的方法400、方法500中的AMF，该装置100可以执行本申请实施例的方法500、方法700中的AMF所对应的步骤。应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
具体地，所述收发单元用于接收会话建立请求，所述会话建立请求包括：第一边缘配置服务器数据网络名称的信息和/或指示信息，所述指示信息包括第一指示信息和/或第二指示信息，其中，所述第一指示信息用于指示用户设备的能力，所述第二指示信息用于指示所述用户设备向所述第一边缘配置服务器请求配置信息，所述第一边缘配置服务器是所述用户设备根据策略信息，在至少两个边缘配置服务器中确定的，所述策略信息包括每个边缘配置服务器的第二类信息，所述第二类信息包括每个边缘配置服务器对应的数据网络名称的信息和/或单一网络切片选择辅助信息；所述收发单元用于根据所述第二类信息和/或所述指示信息确定第三网元，所述第三网元支持所述装置访问所述第一边缘配置服务器。
在一些实施例中，所述收发单元还用于接收会话修改请求，所述会话修改请求包括第一请求，所述第一请求用于所述用户设备向所述第一边缘配置服务器请求配置信息；所述收发单元用于发送所述会话修改请求。
在一些实施例中，所述收发单元还用于接收至少两个边缘配置服务器所对应的策略信息；所述收发单元用于发送所述策略信息。
图7是本申请实施例提供的装置200的示意性框图。如图所示，该装置200包括：至少一个处理器220。该处理器220与存储器耦合，用于执行存储器中存储的指令，以发送信号和/或接收信号。可选地，该装置200还包括存储器230，用于存储指令。可选的，该装置200还包括收发器210，处理器220控制收发器210发送信号和/或接收信号。
应理解，上述处理器220和存储器230可以合成一个处理装置，处理器220用于执行存储器230中存储的程序代码来实现上述功能。具体实现时，该存储器230也可以集成在处理器220中，或者独立于处理器220。
还应理解，收发器210可以包括收发器(或者称，接收机)和发射器(或者称，发射机)。收发器还可以进一步包括天线，天线的数量可以为一个或多个。收发器210有可以是通信接口或者接口电路。
具体的，该装置200中的收发器210可以对应于装置100中的收发单元110，该装置200中的处理器220可对应于装置200中的处理单元120。
应理解，各收发器处理器执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
在实现过程中，上述方法的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。为避免重复，这里不再详细描述。
应注意，本申请实施例中的处理器可以是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(digital signal processor,DSP)、专用集成电路(application-specific integrated circuit,ASIC)、现场可编程门阵列(field-programmable gate array,FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可以理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synch-link DRAM，SLDRAM)和直接内存总线随机存取存储器(direct ram-bus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
根据本申请实施例提供的方法，本申请还提供一种计算机程序产品，该计算机程序产品上存储有计算机程序代码，当该计算机程序代码在计算机上运行时，使得该计算机执行方法300、方法400、方法500实施例中任意一个实施例的方法。
根据本申请实施例提供的方法，本申请还提供一种计算机可读介质，该计算机可读介质存储有程序代码，当该程序代码在计算机上运行时，使得该计算机执行方法300、方法400、方法500实施例中任意一个实施例的方法。
根据本申请实施例提供的方法，本申请还提供一种系统，其包括前述的装置或设备。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产 品包括一个或多个计算机指令。在计算机上加载和执行所述计算机指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，高密度数字视频光盘(digital video disc，DVD))、或者半导体介质(例如，固态硬盘(solid state disc，SSD))等。
上述各个装置实施例中网络侧设备与终端设备和方法实施例中的网络侧设备或终端设备对应，由相应的模块或单元执行相应的步骤，例如通信单元(收发器)执行方法实施例中接收或发送的步骤，除发送、接收外的其它步骤可以由处理单元(处理器)执行。具体单元的功能可以参考相应的方法实施例。其中，处理器可以为一个或多个。
在本说明书中使用的术语“部件”、“模块”、“系统”等用于表示计算机相关的实体、硬件、固件、硬件和软件的组合、软件、或执行中的软件。例如，部件可以是但不限于，在处理器上运行的进程、处理器、对象、可执行文件、执行线程、程序和/或计算机。通过图示，在计算设备上运行的应用和计算设备都可以是部件。一个或多个部件可驻留在进程和/或执行线程中，部件可位于一个计算机上和/或分布在2个或更多个计算机之间。此外，这些部件可从在上面存储有各种数据结构的各种计算机可读介质执行。部件可例如根据具有一个或多个数据分组(例如来自与本地系统、分布式系统和/或网络间的另一部件交互的二个部件的数据，例如通过信号与其它系统交互的互联网)的信号通过本地和/或远程进程来通信。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所述领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络 单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (30)

  1. 一种获取边缘服务的方法，其特征在于，
    用户设备UE从第一网元接收至少两个边缘配置服务器所对应的策略信息，所述策略信息包括每个边缘配置服务器的第一类信息，所述第一类信息包括以下信息的一项或多项：每个边缘配置服务器对应的服务范围的信息、优先级的信息、标识信息；
    所述UE根据所述策略信息中的第一类信息，在所述至少两个边缘配置服务器中确定第一边缘配置服务器。
  2. 根据权利要求1所述的方法，其特征在于，所述第一类信息包括每个边缘配置服务器的优先级信息，所述UE根据所述策略信息中的第一类信息，在所述至少两个边缘配置服务器中确定第一边缘配置服务器，包括：
    如果多个边缘配置服务器的优先级不同，则UE将优先级最高的边缘配置服务器确定为第一边缘配置服务器。
  3. 根据权利要求1所述的方法，其特征在于，所述策略信息包括每个边缘配置服务器的优先级信息和服务范围的信息，所述UE根据所述策略信息中的第一类信息，在所述至少两个边缘配置服务器中确定所述第一边缘配置服务器，包括：
    如果多个边缘配置服务器的优先级相同，则UE根据边缘配置服务器的服务范围和UE的位置信息确定第一边缘配置服务器。
  4. 根据权利要求1至3中任一项所述的方法，其特征在于，所述策略信息还包括每个边缘配置服务器的第二类信息，所述第二类信息包括每个边缘配置服务器对应的数据网络名称的信息和/或单一网络切片选择辅助信息，所述方法还包括：
    所述UE根据所述策略信息中的第二类信息请求建立所述第一边缘配置服务器对应的协议数据单元PDU会话；
    所述UE通过所述PDU会话访问所述第一边缘配置服务器。
  5. 根据权利要求4所述的方法，其特征在于，所述UE根据所述策略信息中的第二类信息请求建立所述第一边缘配置服务器对应的协议数据单元PDU会话，包括：
    所述UE向第二网元发送会话建立请求，所述会话建立请求中包括所述第一边缘配置服务器对应的数据网络名称和/或单一网络切片选择辅助信息。
  6. 根据权利要求5所述的方法，其特征在于，所述会话建立请求中还包括：
    第一指示信息，所述第一指示信息用于指示所述UE的能力，和/或；
    第二指示信息，所述第二指示信息用于指示所述UE向所述第一边缘配置服务器请求配置信息。
  7. 根据权利要求1至5中任一项所述的方法，其特征在于，所述第一网元为策略控制网元，所述第二网元为移动管理网元。
  8. 一种获取边缘服务的方法，其特征在于，包括：
    第二网元从用户设备UE接收会话建立请求，所述会话建立请求包括：第一边缘配置服务器数据网络名称的信息和/或指示信息，所述指示信息包括第一指示信息和/或第二指示信息，其中，所述第一指示信息用于指示所述UE的能力，所述第二指示信息用于指示 所述UE向所述第一边缘配置服务器请求配置信息，所述第一边缘配置服务器是所述UE根据策略信息，在至少两个边缘配置服务器中确定的，所述策略信息包括每个边缘配置服务器的第二类信息，所述第二类信息包括每个边缘配置服务器对应的数据网络名称的信息和/或单一网络切片选择辅助信息；
    所述第二网元根据所述第二类信息和/或所述指示信息确定第三网元，所述第三网元支持所述UE访问所述第一边缘配置服务器。
  9. 根据权利要求8所述的方法，其特征在于，所述策略信息还包括每个边缘配置服务器的第一类信息，所述第一类信息包括以下信息的一项或多项：每个边缘配置服务器对应的服务范围的信息、优先级的信息、标识信息。
  10. 根据权利要求8或9所述的方法，其特征在于，所述方法还包括：
    所述第二网元从所述UE接收会话修改请求，所述会话修改请求包括第一请求，所述第一请求用于所述UE向所述第一边缘配置服务器请求配置信息；
    所述第二网元向所述第三网元发送所述会话修改请求。
  11. 根据权利要求8至10中任一项所述的方法，其特征在于，所述方法还包括：
    所述第二网元从第一网元接收至少两个边缘配置服务器所对应的策略信息；
    所述第二网元向所述UE发送所述策略信息。
  12. 根据权利要求8至11中任一项所述的方法，其特征在于，所述第一网元为策略控制网元，所述第二网元为移动管理网元，所述第三网元为会话管理网元。
  13. 一种获取边缘服务的方法，其特征在于，包括：
    用户设备UE向第三网元发送会话建立请求，所述会话建立请求中包括数据网络名称和第二指示信息，所述第二指示信息用于指示所述UE向边缘配置服务器请求配置信息；
    所述UE接收来自第一网元的策略信息，所述策略信息包括第二边缘配置服务器的标识信息和数据网络名称，所述策略信息用于指示所述UE通过所述会话访问所述第二边缘配置服务器，所述第二边缘配置服务器是所述第三网元根据所述第二指示信息确定的；
    所述UE根据所述策略信息确定通过所述会话访问所述第二边缘配置服务器。
  14. 根据权利要求13所述的方法，其特征在于，所述会话建立请求中还包括：
    第一指示信息，所述第一指示信息用于指示所述UE的能力。
  15. 根据权利要求13或14所述的方法，其特征在于，所述第一网元为策略控制网元，所述第三网元为会话管理网元。
  16. 一种获取边缘服务的装置，其特征在于包括：收发单元和处理单元，
    所述收发单元用于接收至少两个边缘配置服务器所对应的策略信息，所述策略信息包括每个边缘配置服务器的第一类信息，所述第一类信息包括以下信息的一项或多项：每个边缘配置服务器对应的服务范围的信息、优先级的信息、标识信息；
    所述处理单元用于根据所述策略信息中的第一类信息，在所述至少两个边缘配置服务器中确定第一边缘配置服务器。
  17. 根据权利要求16所述的装置，其特征在于，所述第一类信息包括每个边缘配置服务器的优先级信息，所述处理单元根据所述策略信息中的第一类信息，在所述至少两个边缘配置服务器中确定第一边缘配置服务器，包括：
    如果多个边缘配置服务器的优先级不同，所述处理单元将优先级最高的边缘配置服务 器确定为第一边缘配置服务器。
  18. 根据权利要求16所述的装置，其特征在于，所述第一类信息包括每个边缘配置服务器的优先级信息和服务范围的信息，所述处理单元根据所述策略信息中的第一类信息，在所述至少两个边缘配置服务器中确定所述第一边缘配置服务器，包括：
    如果多个边缘配置服务器的优先级相同，所述处理单元根据边缘配置服务器的服务范围和所述装置的位置信息确定第一边缘配置服务器。
  19. 根据权利要求16至18中任一项所述的装置，其特征在于，所述策略信息还包括每个边缘配置服务器的第二类信息，所述第二类信息包括每个边缘配置服务器对应的数据网络名称的信息和/或单一网络切片选择辅助信息，
    所述处理单元还用于根据所述策略信息中的第二类信息请求建立所述第一边缘配置服务器对应的协议数据单元PDU会话；
    所述装置通过所述PDU会话访问所述第一边缘配置服务器。
  20. 根据权利要求19所述的装置，其特征在于，所述处理单元具体用于：
    控制所述收发单元发送会话建立请求，所述会话建立请求中包括所述第一边缘配置服务器对应的数据网络名称和/或单一网络切片选择辅助信息。
  21. 根据权利要求20所述的装置，其特征在于，所述会话建立请求中还包括：
    第一指示信息，所述第一指示信息用于指示所述装置的能力，和/或；
    第二指示信息，所述第二指示信息用于指示所述装置向所述第一边缘配置服务器请求配置信息。
  22. 一种获取边缘服务的装置，其特征在于，包括：收发单元和处理单元，
    所述收发单元用于接收会话建立请求，所述会话建立请求包括：第一边缘配置服务器数据网络名称的信息和/或指示信息，所述指示信息包括第一指示信息和/或第二指示信息，其中，所述第一指示信息用于指示用户设备的能力，所述第二指示信息用于指示所述用户设备向所述第一边缘配置服务器请求配置信息，所述第一边缘配置服务器是所述用户设备根据策略信息，在至少两个边缘配置服务器中确定的，所述策略信息包括每个边缘配置服务器的第二类信息，所述第二类信息包括每个边缘配置服务器对应的数据网络名称的信息和/或单一网络切片选择辅助信息；
    所述收发单元用于根据所述第二类信息和/或所述指示信息确定第三网元，所述第三网元支持所述装置访问所述第一边缘配置服务器。
  23. 根据权利要求21所述的装置，其特征在于，所述策略信息还包括每个边缘配置服务器的第一类信息，所述第一类信息包括以下信息的一项或多项：每个边缘配置服务器对应的服务范围的信息、优先级的信息、标识信息。
  24. 根据权利要求22或23所述的装置，其特征在于，
    所述收发单元还用于接收会话修改请求，所述会话修改请求包括第一请求，所述第一请求用于所述用户设备向所述第一边缘配置服务器请求配置信息；
    所述收发单元用于发送所述会话修改请求。
  25. 根据权利要求22至24中任一项所述的装置，其特征在于，
    所述收发单元还用于接收至少两个边缘配置服务器所对应的策略信息；
    所述收发单元用于发送所述策略信息。
  26. 根据权利要求22至25中任一项所述的装置，其特征在于，所述第三网元为会话管理网元。
  27. 一种获取边缘服务的装置，其特征在于，包括：收发单元和处理单元，
    所述收发单元用于发送会话建立请求，所述会话建立请求中包括数据网络名称和第二指示信息，所述第二指示信息用于指示所述装置向边缘配置服务器请求配置信息；
    所述收发单元用于接收策略信息，所述策略信息包括第二边缘配置服务器的标识信息和数据网络名称，所述策略信息用于指示所述装置通过所述会话访问所述第二边缘配置服务器，所述第二边缘配置服务器是第三网元根据所述第二指示信息确定的；
    所述装置根据所述策略信息确定通过所述会话访问所述第二边缘配置服务器。
  28. 根据权利要求27所述的装置，其特征在于，所述会话建立请求中还包括：
    第一指示信息，所述第一指示信息用于指示所述装置的能力。
  29. 根据权利要求27或28所述的装置，其特征在于，所述第三网元为会话管理网元。
  30. 一种获取边缘服务的装置，其特征在于，包括：处理器，所述处理器与存储器耦合，所述存储器用于存储程序或指令，当所述程序或指令被所述处理器执行时，使得所述装置执行如权利要求1至7中任一项所述的方法，或者；使得所述装置执行如权利要求8至12中任一项所述的方法，或者；使得所述装置执行如权利要求13至15中任一项所述的方法。
PCT/CN2022/103724 2021-07-07 2022-07-04 一种获取边缘服务的方法和装置 WO2023280121A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110769700.7A CN113630749B (zh) 2021-07-07 2021-07-07 一种获取边缘服务的方法和装置
CN202110769700.7 2021-07-07

Publications (1)

Publication Number Publication Date
WO2023280121A1 true WO2023280121A1 (zh) 2023-01-12

Family

ID=78379231

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/103724 WO2023280121A1 (zh) 2021-07-07 2022-07-04 一种获取边缘服务的方法和装置

Country Status (2)

Country Link
CN (1) CN113630749B (zh)
WO (1) WO2023280121A1 (zh)

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115185669A (zh) * 2021-04-06 2022-10-14 中国移动通信有限公司研究院 一种边缘配置服务器信息处理方法、装置和通信设备
CN113630749B (zh) * 2021-07-07 2023-05-16 华为技术有限公司 一种获取边缘服务的方法和装置
CN114363173A (zh) * 2021-12-01 2022-04-15 华为技术有限公司 通信方法、装置及可读存储介质
CN114302428B (zh) * 2021-12-24 2023-06-23 中国联合网络通信集团有限公司 一种mec节点的确定方法及装置
CN116471219A (zh) * 2022-01-11 2023-07-21 腾讯科技（深圳）有限公司 数据传输方法及相关设备
CN116867032A (zh) * 2022-03-28 2023-10-10 华为技术有限公司 一种通信方法及装置
CN116939009A (zh) * 2022-03-29 2023-10-24 华为技术有限公司 一种通信方法、装置及设备
CN114884819B (zh) * 2022-05-31 2023-08-22 中国联合网络通信集团有限公司 能力开放系统、方法、装置及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111919264A (zh) * 2018-04-13 2020-11-10 通用电气公司 用于使成像系统和边缘计算系统同步的系统和方法
WO2021064717A1 (en) * 2019-10-04 2021-04-08 Telefonaktiebolaget Lm Ericsson (Publ) Method for identification of traffic suitable for edge breakout and for traffic steering in a mobile network
CN113630749A (zh) * 2021-07-07 2021-11-09 华为技术有限公司 一种获取边缘服务的方法和装置

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112583880B (zh) * 2019-09-30 2022-02-25 大唐移动通信设备有限公司 一种服务器发现方法及相关设备
CN111586114A (zh) * 2020-04-24 2020-08-25 腾讯科技（深圳）有限公司 业务协同处理方法及相关设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111919264A (zh) * 2018-04-13 2020-11-10 通用电气公司 用于使成像系统和边缘计算系统同步的系统和方法
WO2021064717A1 (en) * 2019-10-04 2021-04-08 Telefonaktiebolaget Lm Ericsson (Publ) Method for identification of traffic suitable for edge breakout and for traffic steering in a mobile network
CN113630749A (zh) * 2021-07-07 2021-11-09 华为技术有限公司 一种获取边缘服务的方法和装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on enhancement of support for Edge Computing in 5G Core network (5GC) (Release 17)", 3GPP STANDARD; TECHNICAL REPORT; 3GPP TR 23.748, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. V0.3.0, 3 February 2020 (2020-02-03), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , pages 1 - 40, XP051861023 *
CHINA MOBILE: "Update for ECS configuration information", 3GPP DRAFT; S6-210767, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG6, no. e-meeting; 20210412 - 20210420, 6 April 2021 (2021-04-06), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051994356 *

Also Published As

Publication number Publication date
CN113630749B (zh) 2023-05-16
CN113630749A (zh) 2021-11-09

Similar Documents

Publication Publication Date Title
WO2023280121A1 (zh) 一种获取边缘服务的方法和装置
WO2023284584A1 (zh) 通信方法和装置
WO2023011210A1 (zh) 一种获取边缘服务的方法和装置
US20220330361A1 (en) Method for establishing connection and obtaining relay service code and communications apparatus
US11057865B1 (en) Apparatus and methods for enhanced paging in wireless networks
WO2019196680A1 (zh) 通信方法和通信装置
WO2023124457A1 (zh) 选择网络的方法和装置
WO2020217224A1 (en) Amf and scp behavior in delegated discovery of pcf
US20220263879A1 (en) Multicast session establishment method and network device
WO2022199451A1 (zh) 会话切换的方法和装置
CN113595911B (zh) 数据转发方法、装置、电子设备及存储介质
WO2023051430A1 (zh) 通信的方法和装置
WO2022256754A2 (en) Network discovery and selection of accessing localized services
CN116868603A (zh) 针对af会话的外部参数提供的新方法
WO2023143212A1 (zh) 一种通信方法及装置
WO2022170798A1 (zh) 确定策略的方法和通信装置
WO2023134630A1 (zh) 配置策略的方法和装置
WO2023051381A1 (zh) 一种应用服务器的确定方法
WO2023051428A1 (zh) 信息传输的方法和装置
WO2023051427A1 (zh) 通信的方法和装置
WO2022100197A1 (zh) 获取边缘服务的方法和装置
WO2023185620A1 (zh) 通信的方法和装置
WO2023160394A1 (zh) 通信的方法和装置
WO2023160199A1 (zh) 一种接入通信网络的方法和装置
WO2023051431A1 (zh) 通信的方法和装置

Legal Events

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

Ref document number: 22836872

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE