WO2021189938A1 - 一种移动边缘业务更新方法、装置、***、设备及介质 - Google Patents

一种移动边缘业务更新方法、装置、***、设备及介质 Download PDF

Info

Publication number
WO2021189938A1
WO2021189938A1 PCT/CN2020/134060 CN2020134060W WO2021189938A1 WO 2021189938 A1 WO2021189938 A1 WO 2021189938A1 CN 2020134060 W CN2020134060 W CN 2020134060W WO 2021189938 A1 WO2021189938 A1 WO 2021189938A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
resource usage
user
mobile edge
core network
Prior art date
Application number
PCT/CN2020/134060
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 WO2021189938A1 publication Critical patent/WO2021189938A1/zh

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/50Service provisioning or reconfiguring
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5051Service on demand, e.g. definition and deployment of services in real time
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5054Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12Messaging; Mailboxes; Announcements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/04Wireless resource allocation
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/50Allocation or scheduling criteria for wireless resources
    • H04W72/53Allocation or scheduling criteria for wireless resources based on regulatory allocation policies
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W88/00Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/18Service support devices; Network management devices

Definitions

  • This application relates to the field of network technology, and in particular to a method, device, system, equipment, and medium for updating mobile edge services.
  • edge computing refers to the nearest-end service provided by an open platform that integrates network, computing, storage, and application core capabilities on the side close to the source of things or data.
  • edge computing adopts a distributed computing architecture, which transfers the computing of applications, data, and services previously processed by network center nodes to edge nodes on the network logic.
  • the essence of edge computing is to provide services near the edge of the network near the data source; a new service model in which data or tasks can be calculated and executed at the edge of the network near the data source, allowing storage and processing at the edge of the network Data, in collaboration with cloud computing, provides intelligent services on the data side.
  • This technology greatly reduces the end-to-end delay of mobile service delivery by deeply integrating traditional telecommunications cellular networks and Internet services, thereby improving user experience, and the inherent capabilities of wireless networks have been successfully tapped.
  • the edge data network 10 (Edge Data Network, EDN) in this structure includes an edge application server 101 (Edge Application Server, EAS) and an edge enable server 102. (Edge Enabler Server, EES), and an Edge Configuration Server (ECS) connected to the EDN.
  • EDS Edge Configuration Server
  • the Edge Configuration Server 20 provides necessary initial configuration information for user equipment (User Equipment, UE) when accessing the EES.
  • EES is the core function of EDN. It provides enabling functions for upper-layer applications to access the mobile communication network through EDN, provides application server discovery functions for UEs, and provides application server access control.
  • the upper-level application is created and loaded on the EAS in the form of an EAS instance, and multiple EAS instances can be created and loaded on the same EAS.
  • Each UE can register one or more EAS instances on an EAS at the same time.
  • the discovery of the EAS by the UE is achieved by obtaining the list of available EAS instances from the EES by the UE.
  • ECS provides necessary initial configuration information for UE to access EES.
  • EAS accesses the upper application server of the mobile communication network through EDN, performs EDN network access and registration through EES, and obtains UE information related to edge computing enabled services through EES.
  • the UE's discovery of EDN applications is actively initiated by the UE side according to its preset conditions.
  • the preset conditions only consider the requirements, capabilities, or status of the UE side, and do not consider network resources such as network congestion.
  • EAS is discovered by actual situations such as insufficient network resources or poor network experience quality. If the EAS instance loaded on the EAS cannot be used due to insufficient network resources, EES will still notify the UE of all EAS instance lists in the prior art, but there is no guarantee that the network resources of an EDN can meet the needs of updated application services, and It is not possible to further coordinate the application service requirements and network resource conditions to perform resource scheduling and allocation to the terminal in a targeted manner.
  • the existing technology does not support the real-time release and update of applications in the EDN, and the available applications can only be configured on the EES through pre-configuration.
  • This method cannot adapt to the needs of edge computing applications changing at any time, and the UE side cannot find information about new applications online or application update information in real time.
  • This application provides a mobile edge service update method, device, system, equipment, and medium to solve the problem that network resources cannot meet the needs of real-time application services in the prior art, and cannot coordinate application service requirements, and the network resource situation is targeted.
  • an embodiment of the present application provides a mobile edge service update method, including:
  • the mobile edge computing network service update is initiated to the user.
  • obtaining the service resource usage requirements of the mobile edge computing network includes:
  • determining the resource scheduling strategy of the user of the service to be updated according to the service resource usage demand includes:
  • the user's resource scheduling strategy is determined based on the service resource usage requirements and experience information.
  • determining the resource scheduling strategy of the user of the service to be updated according to the service resource usage demand includes:
  • the traffic impact request includes a traffic impact creation request or a traffic impact update request.
  • a PDU session is established between the user and the core network, and the resource scheduling strategy of the user to be updated for the service is determined according to service resource usage requirements, including:
  • initiating a mobile edge computing network service update to a user based on a resource scheduling strategy includes:
  • the mobile edge computing network service update is initiated to the user.
  • an embodiment of the present application provides a mobile edge service update device, which includes:
  • the obtaining unit is used to obtain service resource usage requirements of the mobile edge computing network
  • the determining unit is used to determine the resource scheduling strategy of the user of the service to be updated according to the service resource usage demand;
  • the processing unit is used to initiate a mobile edge computing network service update to the user based on the resource scheduling strategy.
  • an embodiment of the present application provides a mobile edge computing system, which includes an edge application server, a service registration function device, and a resource management function device;
  • the service registration function device is used to obtain service resource usage requirements of the mobile edge computing network from the edge application server, instruct the resource management function device to obtain experience information of network resources, and send a service update notification to the user;
  • the resource management function device is used to obtain the experience information of the service to be updated, determine the user's resource scheduling strategy based on the service resource usage demand and experience information, and send the service resource usage demand and experience information to the edge application server;
  • the edge application server is used to generate service resource usage requirements, and initiate mobile edge computing network service updates to users based on service resource usage requirements and experience information.
  • a PDU session is established between the user and the core network, and the resource management function device is also used for:
  • an embodiment of the present application provides an electronic device, including: at least one processor, at least one memory, and computer program instructions stored in the memory.
  • the computer program instructions are executed by the processor, the implementation is On the one hand the method provided.
  • an embodiment of the present application provides a computer-readable storage medium on which computer program instructions are stored, and when the computer program instructions are executed by a processor, the method provided in the first aspect of the embodiments of the present application is implemented.
  • Utilizing the mobile edge service update method, device, system, equipment and medium provided in this application has the following beneficial effects: obtaining the service resource usage requirements of the mobile edge computing network, obtaining network resource experience information according to the service resource usage requirements, and according to the above information Determine the resource scheduling strategy of the user whose service is to be updated and assist the core network in the user's network resource allocation. Based on the resource scheduling strategy, initiate a mobile edge computing network service update to the user.
  • This application determines resource scheduling strategies based on service resource usage requirements and network resource experience information, and assists the core network in network resource allocation for users, ensuring that mobile edge network resources meet the new resource usage requirements brought about by application updates, while also ensuring The service quality of users in the edge network can adapt to the needs of application updates, and solves the problem of lack of coordination and matching between application requirements and user network resources in the edge network.
  • FIG. 1 is a schematic diagram of the application layer structure of the mobile edge service update provided by the background technology
  • FIG. 2 is a schematic flowchart of a mobile edge service update method provided by an embodiment of the application
  • FIG. 3 is a schematic diagram of the application layer structure of the mobile edge service update method provided by an embodiment of the application
  • FIG. 4 is a schematic flowchart of a specific process of a mobile edge service update method provided by an embodiment of this application;
  • FIG. 5 is a schematic diagram of the interaction process between the service registration function module and the resource management function module in the mobile edge service update method provided by an embodiment of the application;
  • FIG. 6 is a schematic diagram of a physical device structure of a mobile edge service update method provided by an embodiment of this application.
  • FIG. 7 is a schematic diagram of the flow of EES initiating traffic influence through NEF in the mobile edge service update method provided by an embodiment of the application;
  • FIG. 8 is a schematic diagram of the flow of triggering PDU session modification between the EES and the core network according to an embodiment of the application;
  • FIG. 9 is a schematic flowchart of a specific process of another mobile edge service update method provided by an embodiment of this application.
  • FIG. 10 is a schematic diagram of the physical device structure of another mobile edge service update method provided by an embodiment of the present application.
  • FIG. 11 is a schematic diagram of the flow of ECS initiating traffic influence through NEF in the mobile edge service update method provided by an embodiment of the application;
  • FIG. 12 is a schematic diagram of the flow of triggering PDU session modification between the ECS and the core network according to an embodiment of the application;
  • FIG. 13 is a schematic structural diagram of a mobile edge service update apparatus provided by an embodiment of this application.
  • FIG. 14 is a schematic structural diagram of a mobile edge service update system provided by an embodiment of this application.
  • FIG. 15 is a schematic structural diagram of an electronic device provided by an embodiment of this application.
  • UE an important concept in mobile communications, refers to user terminals in mobile networks.
  • MEC Mobile Edge Computing
  • the embodiment of the present application provides a mobile edge service update method, as shown in FIG. 2, including:
  • Step 201 Obtain service resource usage requirements of the mobile edge computing network.
  • service resource usage requirements for service release or service update, usually pass service resource usage requirements through service update notifications, and then request experience information of network resources from the core network according to the service resource usage requirements.
  • the service resource usage requirements carry the relevant identification information EAS ID of the application and the KPI requirements of the application, such as bandwidth, priority, delay, application service area range, application type and quality of service (QoS) requirements, etc. .
  • the service resource usage requirements may also include the UE's identification GPSI, EAS Instance ID, data network name (Data Network Name, DNN), network slice identification S-NSSAI information).
  • the experience information may be the experience information of a certain user, the experience information of multiple users, or the experience information of a certain network slice, which is not limited in the embodiment of the present application.
  • the DNN and S-NSSAI information corresponding to the application can also be determined according to the application location information provided in the service resource usage requirements . It should be noted that if the service resource usage requirement does not include the UE identity, the subsequent processing is directed to all registered UEs; if the UE identity is included, the subsequent processing is only directed to the designated UE corresponding to the UE identity.
  • Step 202 Determine the resource scheduling strategy of the user of the service to be updated according to the service resource usage requirement.
  • the user's resource scheduling strategy is determined based on the service resource usage requirements and experience information.
  • the experience information service resource usage requirements match, it can be based on the service resource usage requirements and experience information
  • a processing method in the prior art may also be adopted, which is not limited in the embodiment of the present application.
  • the resource scheduling strategy can be determined by one or more of the following information: UE identification, bandwidth, QoS requirements, media type, DNN, S-NSSAI information, etc., as well as routing for the UE determined by the resource management function
  • this step also includes initiating the process of modifying the PDU session of the core network for a specific UE, and initiating the flow influencing operation on the core network.
  • Initiating an operation to affect the core network traffic including initiating a creation or update command to the Network Exposure Function (NEF), that is, sending a request for a traffic influence creation request or a traffic influence update request.
  • NEF Network Exposure Function
  • This operation can be for a specific UE, or for all UEs related to DNN and S-NSSAI. This operation will affect the selection of the User Plane Function (UPF) of the UE related to the specific DNAI in the traffic routing.
  • UPF User Plane Function
  • Step 203 based on the resource scheduling strategy, initiate a mobile edge computing network service update to the user.
  • a service update notification is sent to the user, and the mobile edge computing network service update is initiated to the user.
  • the mobile edge computing network service update is initiated to the user based on the modified PDU session.
  • edge application server 303 (EAS) provide applications for terminal users
  • the cloud server accesses and uses the functions provided by the core network through the EDN.
  • the service registration function module 304 and the resource management function module 305 are newly added facilities in this embodiment of the application.
  • the business registration function module interacts with EAS through existing interfaces, and is responsible for receiving and processing application service releases or application update notifications sent by EAS, and generating registry for EAS instances, and at the same time, responsible for pushing business service releases to registered UEs in EDN And business update notifications.
  • the information issued by the EAS received by the service registration function may be application information for a certain geographic area or within a certain EDN range, and may have nothing to do with a single UE.
  • the resource management function module is responsible for network resource management operations with the core network, and can obtain the service requirements for network resources (such as bandwidth, delay, application service area range, application type, etc.) from the service registration function module. Demand). The experience information of related network elements can also be obtained from the core network.
  • the resource management function module can synthesize the information obtained above to determine the resource scheduling strategy, and then adjust the resource allocation of the core network (5GC) to the user.
  • the resource management function module can be in EES or ECS, as follows Taking EES and ECS as examples respectively, the mobile edge service update method provided in the embodiments of the present application will be described in detail.
  • FIG. 4 a schematic flow diagram of a specific process of a mobile edge service update method provided by an embodiment of this application, where the EES includes a service registration function module and a resource management function module.
  • the service registration function module in EES or EES is responsible for receiving and processing EAS service updates and publishing EAS service updates to UE.
  • the resource management function module in EES or EES interacts with the core network to obtain user experience information of related network elements. Specifically, it can include the following steps:
  • Step 401 EAS sends service resource usage requirements.
  • EAS sends to the service registration function module the service resource usage requirements for service release or service update.
  • the service resource usage requirements carry the relevant identification information EAS ID of the application and the KPI requirements of the application, such as bandwidth, priority, delay, service area range of the application, application type, and QoS requirements.
  • the service resource usage requirements may also include the UE's identity (GPSI, EAS Instance ID, DNN, network slice identity (S-NSSAI information)).
  • GPSI Global System for Mobile communications
  • EAS Instance ID EAS Instance ID
  • DNN DNN
  • S-NSSAI information network slice identity
  • the service registration function module determines the DNN and S-NSSAI information corresponding to the application.
  • the specific determination method is to determine the corresponding DNN and S-NSSAI information from the application location information provided in the service resource usage requirements sent by the EAS.
  • the subsequent processing of the service registration function is for all UEs registered in it. If the UE identity is included, the subsequent processing is only for the designated UE corresponding to the UE identity.
  • Step 402 Obtain experience information through the core network and determine a resource scheduling strategy.
  • Step 501 The service registration function module sends a service dynamic information notification to the resource management function module.
  • the service registration function module after receiving the service resource usage requirements sent by EAS, the service registration function module sends a service dynamic information notification to the resource management function module.
  • the service dynamic information notification includes UE identification GPSI, application KPI requirements, (such as bandwidth, priority, etc.). Level, time delay, application service area range, application type and QoS requirements, etc.), DNN, DNAI list, S-NSSAI information. Preferably, it may also include an index ID of the application.
  • Step 502 Obtain experience information from the core network according to the service dynamic information notification.
  • the resource management function module After receiving, the resource management function module interacts with the core network to obtain experience information.
  • the experience information may be the experience information of a certain user, the experience information of multiple users, or the experience information of a certain network slice, which is not limited in the embodiment of the present application.
  • Step 503 Determine the resource scheduling strategy of the user according to service resource usage requirements and experience information.
  • the user's resource scheduling strategy is determined based on service resource usage requirements and experience information, and the core network is assisted in allocating network resources according to the resource scheduling strategy.
  • the specific configuration process is as follows:
  • the resource management module modifies the existing PDU session according to the requirements of the new application or application update, so that the UE can use the application.
  • the parameters used include UE identification, bandwidth, QoS requirements, media type, DNN, S-NSSAI information, etc. , And the DNAI list and corresponding routing profile ID (routing profile ID(s)) or N6 traffic routing information (N6 traffic routing information) determined by the resource management function for the UE routing.
  • the UE needs to have established a PDU session before step 401.
  • Initiate traffic impact operations on the core network including the creation or update instruction initiated by the resource management module to the NEF.
  • This operation can be for a specific UE or for all UEs related to DNN and S-NSSAI. This operation will affect the UPF selection of specific DNAI related UEs in traffic routing.
  • Step 403 The EES sends a service announcement or service update notification to the UE.
  • the service registration function in the EES sends a service announcement or service update notification to the UE.
  • the service update notification carries the relevant identification information EAS ID of the application and the KPI requirements of the application, such as bandwidth, priority, delay, and application.
  • the service update notification may also include EAS Instance ID, DNN, DNAI list, network slice identification S-NSSAI information, and index ID of the application.
  • step 404 an application service is initiated between the UE and the EAS.
  • the UE and the EAS initiate an upper-layer application call based on the established user plane resources.
  • both the service registration function and the resource management function are located in the EES entity, as shown in FIG. 6, which is a schematic diagram of the physical device structure of a mobile edge service update method provided by this embodiment of the application.
  • the device is composed of an edge application server 601 and an edge enable server 602.
  • the edge enable server 602 includes a service registration function 6021 module and a resource management function module 6022.
  • the resource management function module 6022 is connected to NEF through an Nnef interface, and the resource management function module 6022 Connect with PCF through the Npcf interface, or use other compatible or Nnef interfaces to connect with NEF, and use other compatible or Npcf interfaces to connect with PCF to ensure the connection between the resource management function module 6022 and the core network Interactions can reuse existing processes.
  • the other parts can be connected by using an EDGE interface, or can be connected by using other interfaces that meet actual requirements, which is not limited in the embodiment of the present application.
  • the EES initiates the flow influence through the NEF.
  • the resource management function module sends a traffic influence creation request (Nnef_TrafficInfluence_Create) or a traffic influence update request (Nnef_TrafficInfluence_Update) through NEF. Since the Nnef interface is selected to connect with NEF, the acquisition process can reuse the existing process, where the user experience information request includes : UE's identity, DNN, S-NSSAI information.
  • the resource management function module receives the traffic influence creation response (Nnef_TrafficInfluence_Create Response) or the traffic influence update response (Nnef_TrafficInfluence_Update Response).
  • other interfaces compatible with or containing the Nnef interface can also be used to connect to the NEF, which is not limited in the embodiment of the present application.
  • the entity that obtains the experience information may be an existing entity EES, or may pass the entity resource management function module defined in this application.
  • an embodiment of the present application provides a schematic diagram of the flow of triggering PDU session modification between the EES and the core network.
  • Npcf_PolicyAuthorization_Create a policy authorization creation request
  • PDU session network requested PDU Session Modification
  • other interfaces compatible with or including the Npcf interface can also be used to connect to the PCF, which is not limited in the embodiment of the present application.
  • the entity that initiates the request to the core network is the existing entity EES, or the entity resource management function module defined in this application.
  • the request to initiate a policy authorization creation to the PCF may include the following content: UE identification, bandwidth, QoS requirements, media type, DNN, S-NSSAI information, etc.
  • FIG. 9 it is a schematic flowchart of a specific process of another mobile edge service update method provided by an embodiment of this application, where the EES includes a service registration function module, and the ECS includes a resource management function module.
  • the service registration function module is responsible for receiving and processing EAS service updates and publishing EAS service updates to the UE.
  • the resource management function module in ECS interacts with the core network to obtain user experience information of related network elements, which may specifically include the following steps:
  • Step 901 EAS sends service resource usage requirements.
  • EAS sends to the service registration function module the service resource usage requirements for service release or service update.
  • the service resource usage requirements carry the relevant identification information EAS ID of the application and the KPI requirements of the application, such as bandwidth, priority, delay, service area range of the application, application type, and QoS requirements.
  • the service resource usage requirements may also include the UE's identity (GPSI, EAS Instance ID, DNN, network slice identity (S-NSSAI information)).
  • GPSI Global System for Mobile communications
  • EAS Instance ID EAS Instance ID
  • DNN DNN
  • S-NSSAI information network slice identity
  • Step 902 Send a service dynamic information notification to the resource management function module.
  • the service registration function module after receiving the service resource usage requirements sent by EAS, the service registration function module sends a service dynamic information notification to the resource management function module.
  • the service dynamic information notification includes UE identification GPSI, application KPI requirements, (such as bandwidth, priority, etc.). Level, time delay, application service area range, application type and QoS requirements, etc.), DNN, DNAI list, S-NSSAI information. Preferably, it may also include an index ID of the application.
  • the service registration function module determines the DNN and S-NSSAI information corresponding to the application.
  • the specific determination method is to determine the corresponding DNN and S-NSSAI information from the application location information provided in the service resource usage requirements sent by the EAS in step 801.
  • the subsequent processing of the service registration function is for all UEs registered in it. If the UE identity is included, the subsequent processing is only for the designated UE corresponding to the UE identity.
  • Step 903 Obtain experience information through the core network and determine a resource scheduling strategy.
  • the resource management function module in the ECS interacts with the core network to obtain experience information and determine the resource scheduling strategy, and assist the core network to allocate network resources based on the experience information and resource scheduling strategy.
  • the specific configuration process is as follows:
  • the resource management module modifies the existing PDU session according to the requirements of the new application or application update, so that the UE can use the application.
  • the parameters used include UE identification, bandwidth, QoS requirements, media type, DNN, S-NSSAI information, etc. , And the DNAI list and corresponding routing profile ID (routing profile ID(s)) or N6 traffic routing information (N6 traffic routing information) determined by the resource management function for the UE routing.
  • the UE needs to have established a PDU session before step 801.
  • Initiating an operation to influence the flow of the core network including the resource management module initiating a creation or update instruction to the NEF, that is, sending a request for a flow-influenced creation request or a flow-influenced update request.
  • This operation can be for a specific UE, or for all UEs related to DNN and S-NSSAI. This operation will affect the UPF selection of specific DNAI related UEs in traffic routing.
  • Step 904 The EES sends a service announcement or service update notification to the UE.
  • the service registration function in the EES sends a service announcement or service update notification to the UE.
  • the service update notification carries the relevant identification information EAS ID of the application and the KPI requirements of the application, such as bandwidth, priority, delay, and application.
  • the service update notification may also include EAS Instance ID, DNN, DNAI list, network slice identification S-NSSAI information, and index ID of the application.
  • step 905 an application service is initiated between the UE and the EAS.
  • the UE and the EAS initiate an upper-layer application call based on the established user plane resources.
  • the service registration function is located in the EES entity, and the resource management function is located in the ECS entity.
  • FIG. 10 it is a schematic diagram of the physical device structure of another mobile edge service update method provided by this embodiment of the application.
  • the device is composed of an edge application server 1001, an edge enable server 1002, and an edge configuration server 1003.
  • the edge enable server 1002 includes a service registration function module
  • the edge configuration server 1003 includes a resource management function module.
  • the resource management function module and NEF pass through Nnef. Interface connection, the resource management function module is connected with the PCF through the Npcf interface, and other compatible or Nnef interfaces can also be used to connect with the NEF, and other compatible or Npcf interfaces can be used to connect with the PCF to ensure the resource management function module
  • the interaction with the core network can reuse existing processes.
  • the other parts can be connected by using an EDGE interface, or can be connected by using other interfaces that meet actual requirements, which is not limited in the embodiment of the present application.
  • the ECS initiates the flow influence through the NEF.
  • the resource management function module sends a traffic influence creation request (Nnef_TrafficInfluence_Create) or a traffic influence update request (Nnef_TrafficInfluence_Update) to the NEF through NEF. Since the Nnef interface is selected to connect with NEF, the acquisition process can reuse the existing process, where the user experience information request includes : UE's identity, DNN, S-NSSAI information.
  • the resource management function module receives the traffic influence creation response (Nnef_TrafficInfluence_Create Response) or the traffic influence update response (Nnef_TrafficInfluence_Update Response).
  • other interfaces that are compatible with or include the Nnef interface can also be used to connect to the NEF, which is not limited in the embodiment of the present application.
  • the entity that obtains the experience information may be an existing entity ECS, or may pass the entity resource management function module defined in this application.
  • an embodiment of the present application provides a schematic flow chart of triggering PDU session modification between the ECS and the core network.
  • Npcf_PolicyAuthorization_Create a policy authorization creation request
  • PDU session network requested PDU Session Modification
  • other interfaces compatible with or including the Npcf interface can also be used to connect to the PCF, which is not limited in the embodiment of the present application.
  • the entity that initiates the request to the core network is the existing entity ECS, or the entity resource management function module defined in this application.
  • the request to initiate a policy authorization creation to the PCF may include the following content: UE identification, bandwidth, QoS requirements, media type, DNN, S-NSSAI information, etc.
  • this application also provides a mobile edge service update device, which includes:
  • the obtaining unit 1301 is configured to obtain service resource usage requirements of the mobile edge computing network
  • the determining unit 1302 is configured to determine the resource scheduling strategy of the user whose service is to be updated according to service resource usage requirements;
  • the processing unit 1303 is configured to initiate a mobile edge computing network service update to the user based on the resource scheduling strategy.
  • the obtaining unit 1301 is specifically configured to:
  • the determining unit 1302 is specifically configured to:
  • the user's resource scheduling strategy is determined based on the service resource usage requirements and experience information.
  • the determining unit 1302 is configured to:
  • the traffic impact request includes a traffic impact creation request or a traffic impact update request.
  • a PDU session is established between the user and the core network, and the determining unit 1302 is configured to:
  • the processing unit 1303 is specifically configured to:
  • the mobile edge computing network service update is initiated to the user.
  • the present application also provides a mobile edge service update system, which includes an edge application server 1401, a service registration function device 1402, and a resource management function device 1403;
  • the service registration function device 1402 is configured to obtain service resource usage requirements of the mobile edge computing network from the edge application server 1401, instruct the resource management function device 1403 to obtain experience information of the service to be updated, and send a service update notification to the user;
  • the resource management function device 1403 is used to obtain the experience information of the service to be updated, determine the user's resource scheduling strategy based on the service resource usage demand and experience information, and send the service resource usage demand and experience information to the edge application server 1401;
  • the edge application server 1401 is used to generate service resource usage requirements, and initiate mobile edge computing network service updates to users based on the service resource usage requirements and experience information.
  • a PDU session is established between the user and the core network, and the resource management function device 1403 is further configured to:
  • FIG. 15 shows a schematic diagram of the hardware structure of an electronic device provided by an embodiment of the present application.
  • the electronic device may include a processor 1501 and a memory 1502 storing computer program instructions;
  • the processor 1501 is configured to read program instructions in the memory 1502 and execute:
  • a mobile edge computing network service update is initiated to the user.
  • the foregoing processor 1501 may include a central processing unit (Central Processing Units, CPU), or a specific integrated circuit (Application Specific Integrated Circuit, ASIC), or may be configured to implement one or more integrated circuits of the embodiments of the present application .
  • CPU Central Processing Units
  • ASIC Application Specific Integrated Circuit
  • the memory 1502 may include a large-capacity memory for data or instructions.
  • the memory 1502 may include a hard disk drive (Hard Disk Drive, HDD), a floppy disk drive, a flash memory, an optical disk, a magneto-optical disk, a magnetic tape, or a Universal Serial Bus (USB) drive, or two or more Multiple combinations of these.
  • the storage 1502 may include removable or non-removable (or fixed) media.
  • the memory 1502 may be internal or external to the data processing device.
  • the memory 1502 is a non-volatile solid state memory.
  • the memory 1502 includes read-only memory (ROM).
  • the ROM can be mask-programmed ROM, programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), electrically rewritable ROM (EAROM) or flash memory or A combination of two or more of these.
  • the processor 1501 is specifically configured to:
  • the processor 1501 is specifically configured to:
  • the processor 1501 is specifically configured to:
  • the traffic influence request includes a traffic influence creation request or a traffic influence update request.
  • the processor 1501 is specifically configured to:
  • the processor 1501 is specifically configured to:
  • a mobile edge computing network service update is initiated to the user.
  • the electronic device may further include a communication interface 1503 and a bus 1510. Among them, as shown in FIG. 15, the processor 1501, the memory 1502, and the communication interface 1503 are connected through a bus 1510 and complete mutual communication.
  • the communication interface 1503 is mainly used to implement communication between various modules, devices, units and/or devices in the embodiments of the present application.
  • the bus 1510 includes hardware, software, or both, and couples the components of the electronic device to each other.
  • the bus may include accelerated graphics port (AGP) or other graphics bus, enhanced industry standard architecture (EISA) bus, front side bus (FSB), hypertransport (HT) interconnect, industry standard architecture (ISA) Bus, unlimited bandwidth interconnect, low pin count (LPC) bus, memory bus, microchannel architecture (MCA) bus, peripheral component interconnect (PCI) bus, PCI-Express (PCI-X) bus, serial advanced technology Attachment (SATA) bus, Video Electronics Standards Association Local (VLB) bus or other suitable bus or a combination of two or more of these.
  • the bus 1510 may include one or more buses.
  • the electronic device can execute the mobile edge service update method in the embodiment of the present application based on the received resource information, thereby realizing the mobile edge service update method and device described in conjunction with FIG. 2 to FIG. 13.
  • the embodiment of the present application may provide a computer-readable storage medium for implementation.
  • the computer-readable storage medium stores computer program instructions; when the computer program instructions are executed by the processor, any one of the mobile edge service update methods in the foregoing embodiments is implemented.
  • Utilizing the mobile edge service update method, device, system, equipment and medium provided in this application has the following beneficial effects: obtaining the service resource usage requirements of the mobile edge computing network, obtaining network resource experience information according to the service resource usage requirements, and according to the above information Determine the resource scheduling strategy of the user whose service is to be updated and assist the core network in the user's network resource allocation. Based on the resource scheduling strategy, initiate a mobile edge computing network service update to the user.
  • This application determines resource scheduling strategies based on service resource usage requirements and network resource experience information, and assists the core network in network resource allocation for users, ensuring that mobile edge network resources meet the new resource usage requirements brought about by application updates, while also ensuring The service quality of users in the edge network can adapt to the needs of application updates, and solves the problem of lack of coordination and matching between application requirements and user network resources in the edge network.
  • These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction device.
  • the device implements the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.
  • These computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operation steps are executed on the computer or other programmable equipment to produce computer-implemented processing, so as to execute on the computer or other programmable equipment.
  • the instructions provide steps for implementing the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

本申请提供一种移动边缘业务更新方法、装置、***、设备及介质,用以解决现有技术中出现网络资源不能满足实时应用业务的需要,且不能协同应用业务需求、网络资源情况有针对性地对进行资源匹配和调度的技术问题,该方法包括:获取移动边缘计算网络的业务资源使用需求;根据所述业务资源使用需求确定待更新业务的用户的资源调度策略;基于所述资源调度策略,向所述用户发起移动边缘计算网络业务更新。

Description

一种移动边缘业务更新方法、装置、***、设备及介质
相关申请的交叉引用
本申请要求在2020年03月24日提交中国专利局、申请号为202010211451.5、申请名称为“一种移动边缘业务更新方法、装置、***、设备及介质”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
技术领域
本申请涉及网络技术领域,尤其涉及一种移动边缘业务更新方法、装置、***、设备及介质。
背景技术
边缘计算起源是指在靠近物或数据源头的一侧,采用网络、计算、存储、应用核心能力为一体的开放平台,就近提供的最近端服务。通常,边缘计算采用一种分散式运算的架构,将之前由网络中心节点处理的应用程序、数据资料与服务的运算交由网络逻辑上的边缘节点处理。边缘计算的实质是,在靠近数据源的网络边缘某处就近提供服务;数据或任务能够在靠近数据源头的网络边缘侧进行计算和执行计算的一种新型服务模型,允许在网络边缘存储和处理数据,和云计算协作,在数据端提供智能服务。该技术通过将传统电信蜂窝网络和互联网业务深度融合,大大降低了移动业务交付的端到端时延,进而提升用户体验,无线网络的内在能力被成功挖掘。
如图1所示,为现有移动边缘计算的应用层结构示意图,该结构中边缘数据网络10(Edge Data Network,EDN)包括边缘应用服务器101(Edge Application Server,EAS)和边缘使能服务器102(Edge Enabler Server,EES),以及与EDN连接的边缘配置服务器20(Edge Configuration Server,ECS),边缘配置服务器20为用户设备(User Equipment,UE)在接入EES时提供必要的初始配置信息。
EES是EDN的核心功能,为上层应用通过EDN接入移动通信网络提供使能功能,为UE提供应用服务器发现功能,并提供应用服务器接入控制。上层应用程序以EAS实例的形式创建和加载在EAS上,同一个EAS上可以创建和加载多个EAS实例。每个UE可以同时注册一个EAS上的一个或多个EAS实例。现有技术中,UE对EAS的发现是通过UE从EES上获取可用的EAS实例列表来实现。ECS为UE接入EES提供必要的初始配置信息。
EAS通过EDN接入移动通信网络的上层应用服务器,通过EES进行EDN网络接入和注册,并通过EES获取UE的和边缘计算使能服务相关的信息。
现有技术中,UE对EDN应用的发现由UE侧根据其预置条件主动发起,一般该预置条件只会考虑UE侧的要求、能力、或状态,而不会考虑网络资源如是否网络拥塞,是否网络资源不够或网络体验质量不佳等实际情况来发现EAS。如果加载在EAS上的EAS实例由于网络资源不够而无法使用,现有技术中EES仍会向UE通知所有的EAS实例列表,但无法保证一个EDN的网络资源能满足更新的应用业务的需要,且不能进一步协同应用业务需求、网络资源情况有针对性地对终端进行资源调度和分配。同时,现有技术不支持应用在EDN的实时发布和更新,只能通过预配的方式在EES上配置可用的应用。这种方式不能适应边缘计算应用随时变化的需要,UE侧不能实时发现新应用上线的信息或应用更新信息。
发明内容
本申请提供一种移动边缘业务更新方法、装置、***、设备及介质,用以解决现有技术中出现网络资源不能满足实时应用业务的需要,且不能协同应用业务需求、网络资源情况有针对性地对用户进行资源调度和分配的技术问题。
第一方面,本申请实施例提供一种移动边缘业务更新方法,包括:
获取移动边缘计算网络的业务资源使用需求;
根据业务资源使用需求确定待更新业务的用户的资源调度策略;
基于资源调度策略,向用户发起移动边缘计算网络业务更新。
在一种可能实施的方式中,本申请实施例提供的方法中,获取移动边缘计算网络的业务资源使用需求,包括:
获取移动边缘计算网络的业务资源使用需求;
根据业务资源使用需求向核心网请求网络资源的体验信息;
在一种可能实施的方式中,本申请实施例提供的方法中,根据业务资源使用需求确定待更新业务的用户的资源调度策略,包括:
当体验信息不匹配业务资源使用需求时,基于业务资源使用需求和体验信息,确定用户的资源调度策略。
在一种可能实施的方式中,本申请实施例提供的方法中,根据业务资源使用需求确定待更新业务的用户的资源调度策略,包括:
根据业务资源使用需求向核心网发送流量影响请求,流量影响请求包括流量影响创建请求或流量影响更新请求。
在一种可能实施的方式中,本申请实施例提供的方法中,用户与核心网之间建立有PDU会话,根据业务资源使用需求确定待更新业务的用户的资源调度策略,包括:
根据业务资源使用需求指示核心网修改用户与核心网之间的PDU会话。
在一种可能实施的方式中,本申请实施例提供的方法中,基于资源调度策略,向用户发起移动边缘计算网络业务更新,包括:
向用户发送业务更新通知;
基于核心网修改后的PDU会话,向用户发起移动边缘计算网络业务更新。
第二方面,本申请实施例提供一种移动边缘业务更新装置,该装置包括:
获取单元,用于获取移动边缘计算网络的业务资源使用需求;
确定单元,用于根据业务资源使用需求确定待更新业务的用户的资源调度策略;
处理单元,用于基于资源调度策略,向用户发起移动边缘计算网络业务更新。
第三方面,本申请实施例提供一种移动边缘计算***,该***包括边缘应用服务器、业务注册功能装置和资源管理功能装置;
业务注册功能装置用于从边缘应用服务器获取移动边缘计算网络的业务资源使用需求,指示资源管理功能装置获取网络资源的体验信息,并向用户发送业务更新通知;
资源管理功能装置用于获取待更新业务的体验信息,基于业务资源使用需求和体验信息确定用户的资源调度策略,并将业务资源使用需求和体验信息发送至边缘应用服务器;
边缘应用服务器用于生成业务资源使用需求,并基于业务资源使用需求和体验信息向用户发起移动边缘计算网络业务更新。
在一种可能实施的方式中,本申请实施例提供的***中,用户与核心网之间建立有PDU会话,资源管理功能装置还用于:
根据业务资源使用需求修改用户与核心网之间的PDU会话。
第四方面,本申请实施例提供一种电子设备,包括:至少一个处理器、至少一个存储器以及存储在存储器中的计算机程序指令,当计算机程序指令被处理器执行时实现如本申请实施例第一方面所提供的方法。
第五方面,本申请实施例提供一种计算机可读存储介质,其上存储有计算机程序指令,当计算机程序指令被处理器执行时实现如本申请实施例第一方面所提供的方法。
利用本申请提供的移动边缘业务更新方法、装置、***、设备及介质,具有以下有益效果:获取移动边缘计算网络的业务资源使用需求,根据业务资源使用需求获取网络资源体验信息,并根据以上信息确定待更新业务的用户的资源调度策略并协助核心网进行用户的网络资源分配,基于资源调度策略,向用户发起移动边缘计算网络业务更新。本申请通过业务资源使用需求和网络资源体验信息确定资源调度策略,并针对用户协助核心网进行网络资源分配,保证了移动边缘网络资源满足应用更新带来的新的资源使用需求,同时也保证了用户在边缘网络的服务质量能够适应应用更新的需求,解决了 应用需求和用户网络资源之间在边缘网络缺乏协调和匹配的问题。
附图说明
图1为本背景技术提供的移动边缘业务更新的应用层结构示意图;
图2为本申请实施例提供的一种移动边缘业务更新方法的流程示意图;
图3为本申请实施例提供的移动边缘业务更新方法的应用层结构示意图;
图4为本申请实施例提供的一种移动边缘业务更新方法具体过程的流程示意图;
图5为本申请实施例提供的移动边缘业务更新方法中业务注册功能模块和资源管理功能模块的交互的流程示意图;
图6为本申请实施例提供的一种移动边缘业务更新方法实体装置结构示意图;
图7为本申请实施例提供的移动边缘业务更新方法中EES通过NEF发起流量影响的流程示意图;
图8为本申请实施例提供的EES与核心网之间触发PDU会话修改的流程示意图;
图9为本申请实施例提供的另一移动边缘业务更新方法具体过程的流程示意图;
图10本申请实施例提供的另一移动边缘业务更新方法实体装置结构示意图;
图11为本申请实施例提供的移动边缘业务更新方法中ECS通过NEF发起流量影响的流程示意图;
图12为本申请实施例提供的ECS与核心网之间触发PDU会话修改的流程示意图;
图13为本申请实施例提供的一种移动边缘业务更新装置的结构示意图;
图14为本申请实施例提供的移动边缘业务更新***的结构示意图;
图15为本申请实施例提供的一种电子设备的结构示意图。
具体实施方式
为了使本申请的目的、技术方案和优点更加清楚,下面将结合附图对本申请作进一步地详细描述,显然,所描述的实施例仅仅是本申请一部分实施例,而不是全部的实施例。基于本申请中的实施例,本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其它实施例,都属于本申请保护的范围。
下面对文中出现的一些词语进行解释:
1、本申请实施例中术语“和/或”,描述关联对象的关联关系,表示可以存在三种关系,例如,A和/或B,可以表示:单独存在A,同时存在A和B,单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。
2、UE,移动通讯中的重要概念,在移动网络中,指用户终端。
3、移动边缘计算(Mobile Edge Computing,MEC),利用无线接入网络就近提供电信用户所需服务和云端计算功能,从而创造出一个具备高性能、低延迟与高带宽的电信级服务环境,加速网络中各项内容、服务及应用的快速下载,提供不间断的高质量网络体验。
下面结合附图和实施例对本申请提供的移动边缘业务更新的方法、装置、***、设备及介质进行更详细地说明。
本申请实施例提供一种移动边缘业务更新方法,如图2所示,包括:
步骤201,获取移动边缘计算网络的业务资源使用需求。
具体实施时,先获取用于业务发布或业务更新的业务资源使用需求,通常通过业务更新通知传递业务资源使用需求,再根据业务资源使用需求向核心网请求网络资源的体验信息。其中业务资源使用需求中携带该应用的相关标识信息EAS ID和应用的KPI要求,如带宽、优先级、时延、应用的服务区域范围、应用类型和服务质量(Quality of Service,QoS)要求等。
优选的,业务资源使用需求中还可以包括UE的标识GPSI,EAS Instance ID,数据网络名称(Data Network Name,DNN),网络切片标识S-NSSAI信息)。
需要说明的是,体验信息可以是某一用户的体验信息,也可以是多个用户的体验信息,也可以是某个网络切片的体验信息,本申请实施例对此不做限定。
在一种可能实施的方式中,若获取的业务资源使用需求中不包含DNN和S-NSSAI信息,还可以根据业务资源使用需求中提供的应用位置信息确定该应用对应的DNN和S-NSSAI信息。需要说明的是,若业务资源使用需求中不包含UE标识,则后续处理针对所有已注册的UE;如果包含UE标识,则后续处理只针对UE标识对应指定的UE。
步骤202,根据业务资源使用需求确定待更新业务的用户的资源调度策略。
具体实施时,当体验信息不匹配业务资源使用需求时,基于业务资源使用需求和体验信息,确定用户的资源调度策略,当体验信息业务资源使用需求匹配时,可以根据业务资源使用需求和体验信息调整用户的资源调度策略,也可以采用现有技术的处理方式,本申请实施例对此不做限定。
需要说明的是,可通过如下一种或多种信息确定资源调度策略:UE标识,带宽,QoS要求,媒体类型,DNN,S-NSSAI信息等,以及由资源管理功能决定的用于该UE路由的DNAI列表和相应路由配置ID(routing profile ID(s))或N6流量路由信息(N6 traffic routing information)。
另外,本步骤中,还包括发起对核心网的针对特定UE的PDU会话修改过程,发起对核心网的流量影响操作。
(1)发起对核心网的针对特定UE的PDU会话修改过程,包括向策略控制功能(Policy Control function,PCF)起创建指令,以及由此触发的核心网内部的PDU会话修改过程。具体实施时,根据新应用或应用更新的业务资源使用需求在现有PDU会话上进行修改,从而使UE可以使用该应用,使用的参数包括UE标识,带宽,QoS要求,媒体类型,DNN,S-NSSAI信息等,以及由资源管理功能决定的用于该UE路由的DNAI列表和相应路由配置ID(routing profile ID(s))或N6流量路由信息(N6 traffic routing information)。
(2)发起对核心网的流量影响操作,包括向网络开放功能(Network  Exposure Function,NEF)发起创建或更新指令,也即发送请求流量影响创建请求或流量影响更新请求。该操作可针对特定UE,也可以是针对和DNN和S-NSSAI相关的所有UE。该操作会影响特定DNAI相关的UE在流量路由中的用户面功能(User Plane Function,UPF)选择。
步骤203,基于资源调度策略,向用户发起移动边缘计算网络业务更新。
具体实施时,基于资源调度策略,向用户发送业务更新通知,向用户发起移动边缘计算网络业务更新。
优选的,基于修改后的PDU会话,向用户发起移动边缘计算网络业务更新。
下面结合图3对本申请实施例提供的移动边缘业务更新方法的具体过程进行详细说明。
如图3所示,本申请实施例提供的移动边缘业务更新方法中,UE301和核心网302和标准中已经定义的现有逻辑功能实体,边缘应用服务器303(EAS)是为终端用户提供应用的云端服务器,它通过EDN接入和使用核心网提供的功能,业务注册功能模块304和资源管理功能模块305为本申请实施例新增的设施。业务注册功能模块和EAS通过现有接口进行交互,负责接收和处理EAS发来的应用服务发布或应用更新通知,并为EAS实例生成注册表,同时负责向EDN中已注册的UE推送业务服务发布和业务更新通知。
需要说明的是,业务注册功能所接收的EAS发布的信息可以是针对某个地理位置区域的或某个EDN范围内的应用信息,可以和单个UE无关。
资源管理功能模块负责与核心网之间的网络资源管理操作,可以从业务注册功能模块处获取业务对网络资源的需求(例如带宽、时延、应用的服务区域范围、应用类型等业务对网络资源的需求)。还可以从核心网获取相关网元的体验信息。
综上所述,资源管理功能模块可以综合上述获取的信息确定资源调度策略,进而调整核心网(5GC)对用户的资源分配,其中资源管理功能模块可以在EES中,也可以在ECS中,以下分别以在EES和ECS为例,对本申请实 施例提供的移动边缘业务更新方法进行详细说明。
实施例一
如图4所示,为本申请实施例提供的一种移动边缘业务更新方法具体过程的流程示意图,其中EES包含业务注册功能模块和资源管理功能模块。由EES或EES中的业务注册功能模块负责接收处理EAS的服务更新,并向UE发布EAS的服务更新,由EES或EES中的资源管理功能模块和核心网交互获取相关网元的用户体验信息,具体可以包括如下步骤:
步骤401,EAS发送业务资源使用需求。
具体实施时,当有新的应用上线或应用更新时,EAS向业务注册功能模块发送用于业务发布或业务更新的业务资源使用需求。业务资源使用需求中携带该应用的相关标识信息EAS ID和应用的KPI要求,如带宽、优先级、时延、应用的服务区域范围、应用类型和QoS要求等。
优选的,业务资源使用需求中还可以包括UE的标识GPSI,EAS Instance ID,DNN,网络切片标识S-NSSAI信息)。
优选的,业务注册功能模块在收到EAS发送的业务资源使用需求后,若该消息中不包含DNN和S-NSSAI信息,业务注册功能确定该应用对应的DNN和S-NSSAI信息。具体确定方法为,从EAS发送的业务资源使用需求中提供的应用位置信息确定其对应的DNN和S-NSSAI信息。
需要说明的是,若业务资源使用需求中不包含UE标识,则业务注册功能后续处理针对所有在其已注册的UE,如果包含UE标识,则后续处理只针对UE标识对应指定的UE。
步骤402,通过核心网获取体验信息并确定资源调度策略。
具体业务注册功能模块和资源管理功能模块的交互过程如图5所示。
步骤501,业务注册功能模块向资源管理功能模块发送业务动态信息通知。
具体实施时,业务注册功能模块在收到EAS发送的业务资源使用需求后,向资源管理功能模块发送业务动态信息通知,业务动态信息通知包括UE标识GPSI,应用的KPI要求,(如带宽、优先级、时延、应用的服务区域范围、应 用类型和QoS要求等),DNN,DNAI列表,S-NSSAI信息。优选的,还可以包括一个该应用的索引ID。
步骤502,根据业务动态信息通知,向核心网获取体验信息。
资源管理功能模块收到后通过与核心网进行交互,获取体验信息。
需要说明的是,体验信息可以是某一用户的体验信息,也可以是多个用户的体验信息,也可以是某个网络切片的体验信息,本申请实施例对此不做限定。
步骤503,根据业务资源使用需求和体验信息,确定用户的资源调度策略。
具体实施时,基于业务资源使用需求和体验信息确定用户的资源调度策略,并依据资源调度策略协助核心网分配网络资源,具体配置过程如下:
(1)发起对核心网的针对特定UE的PDU会话修改过程,包括由资源管理模块向PCF发起创建指令,以及由此触发的核心网内部的PDU会话修改过程。资源管理模块根据新应用或应用更新的要求在现有PDU会话上进行修改,从而使UE可以使用该应用,使用的参数包括UE标识,带宽,QoS要求,媒体类型,DNN,S-NSSAI信息等,以及由资源管理功能决定的用于该UE路由的DNAI列表和相应路由配置ID(routing profile ID(s))或N6流量路由信息(N6 traffic routing information)。
需要说明的是,要进行PDU会话修改,需在步骤401之前,UE已建立一个PDU会话。
(2)发起对核心网的流量影响操作,包括由资源管理模块向NEF发起创建或更新指令,该操作可针对特定UE,也可以是针对和DNN和S-NSSAI相关的所有UE。该操作会影响特定DNAI相关的UE在流量路由中的UPF选择。
步骤403,EES向UE发送业务宣告或业务更新通知。
具体实施时,由EES中的业务注册功能向UE发送业务宣告或业务更新通知,业务更新通知中携带该应用的相关标识信息EAS ID和应用的KPI要求,如带宽、优先级、时延、应用的服务区域范围、应用类型和QoS要求等。
优选的,业务更新通知中还可以包括EAS Instance ID,DNN,DNAI列 表,网络切片标识S-NSSAI信息,该应用的索引ID。
步骤404,UE与EAS之间发起应用业务。
具体实施时,UE和EAS之间基于建立好的用户面资源,发起上层应用调用。
本实施例中,业务注册功能和资源管理功能都位于EES实体中,如图6所示,为本申请实施例提供的一种移动边缘业务更新方法实体装置结构示意图。
装置由边缘应用服务器601和边缘使能服务器602构成,边缘使能服务器602中包括业务注册功能6021模块和资源管理功能模块6022,资源管理功能模块6022与NEF通过Nnef接口连接,资源管理功能模块6022与PCF通过Npcf接口连接,也可以使用其他兼容或包含Nnef接口的接口与NEF进行连接,使用其他兼容或包含Npcf接口的接口与PCF进行连接,以保障资源管理功能模块6022与核心网之间的交互可重用现有流程。其他各部分间可以使用EDGE接口进行连接,也可以使用其他符合实际需求的接口进行连接,本申请实施例对此不做限定。
如图7所示,本申请实施例提供的移动边缘业务更新方法中EES通过NEF发起流量影响的流程示意图。
资源管理功能模块通过NEF发送流量影响创建请求(Nnef_TrafficInfluen ce_Create)或流量影响更新请求(Nnef_TrafficInfluence_Update),由于选用N nef接口与NEF进行连接,该获取过程可重用现有流程,其中用户体验信息请求中包括:UE的标识,DNN,S-NSSAI信息。资源管理功能模块接收流量影响创建响应(Nnef_TrafficInfluence_Create Response)或流量影响更新响应(Nnef_TrafficInfluence_Update Response)。当然,也可以使用其他兼容或包含Nnef接口的接口与NEF进行连接,本申请实施例对此不做限定。
具体实施时,获取体验信息的实体可以为现有的实体EES,也可以通过本申请定义的实体资源管理功能模块。
如图8所示,本申请实施例提供的EES与核心网之间触发PDU会话修改 的流程示意图。
由于选用Npcf接口与PCF进行连接,该实施例可重用现有流程,具体实施时,向核心网中的PCF发起策略授权创建请求(Npcf_PolicyAuthorization_Create),由核心网修改PDU会话(network requested PDU Session Modification)。当然,也可以使用其他兼容或包含Npcf接口的接口与PCF进行连接,本申请实施例对此不做限定。
向核心网发起请求的实体为现有实体EES,或本申请定义的实体资源管理功能模块。
需要说明的是,向PCF发起策略授权创建的请求中可以包括如下内容:UE标识,带宽,QoS要求,媒体类型,DNN,S-NSSAI信息等。
实施例二
如图9所示,为本申请实施例提供的另一移动边缘业务更新方法具体过程的流程示意图,其中EES包含业务注册功能模块,ECS中包含资源管理功能模块。由业务注册功能模块负责接收处理EAS的服务更新,并向UE发布EAS的服务更新,由ECS中的资源管理功能模块和核心网交互获取相关网元的用户体验信息,具体可以包括如下步骤:
步骤901,EAS发送业务资源使用需求。
具体实施时,当有新的应用上线或应用更新时,EAS向业务注册功能模块发送用于业务发布或业务更新的业务资源使用需求。业务资源使用需求中携带该应用的相关标识信息EAS ID和应用的KPI要求,如带宽、优先级、时延、应用的服务区域范围、应用类型和QoS要求等。
优选的,业务资源使用需求中还可以包括UE的标识GPSI,EAS Instance ID,DNN,网络切片标识S-NSSAI信息)。
步骤902,向资源管理功能模块发送业务动态信息通知。
具体实施时,业务注册功能模块在收到EAS发送的业务资源使用需求后,向资源管理功能模块发送业务动态信息通知,业务动态信息通知包括UE标识GPSI,应用的KPI要求,(如带宽、优先级、时延、应用的服务区域范围、应 用类型和QoS要求等),DNN,DNAI列表,S-NSSAI信息。优选的,还可以包括一个该应用的索引ID。
优选的,业务注册功能模块在收到EAS发送的业务资源使用需求后,若该消息中不包含DNN和S-NSSAI信息,业务注册功能确定该应用对应的DNN和S-NSSAI信息。具体确定方法为,从步骤801中EAS发送的业务资源使用需求中提供的应用位置信息确定其对应的DNN和S-NSSAI信息。
需要说明的是,若业务资源使用需求中不包含UE标识,则业务注册功能后续处理针对所有在其已注册的UE,如果包含UE标识,则后续处理只针对UE标识对应指定的UE。
步骤903,通过核心网获取体验信息并确定资源调度策略。
ECS中的资源管理功能模块收到后通过与核心网进行交互,获取体验信息并确定资源调度策略,并基于体验信息和资源调度策略协助核心网分配网络资源,具体配置过程如下:
(1)发起对核心网的针对特定UE的PDU会话修改过程,包括由资源管理模块向PCF发起创建指令,以及由此触发的核心网内部的PDU会话修改过程。资源管理模块根据新应用或应用更新的要求在现有PDU会话上进行修改,从而使UE可以使用该应用,使用的参数包括UE标识,带宽,QoS要求,媒体类型,DNN,S-NSSAI信息等,以及由资源管理功能决定的用于该UE路由的DNAI列表和相应路由配置ID(routing profile ID(s))或N6流量路由信息(N6 traffic routing information)。
需要说明的是,要进行PDU会话修改,需在步骤801之前,UE已建立一个PDU会话。
(2)发起对核心网的流量影响操作,包括由资源管理模块向NEF发起创建或更新指令,也即发送请求流量影响创建请求或流量影响更新请求。该操作可针对特定UE,也可以是针对和DNN和S-NSSAI相关的所有UE。该操作会影响特定DNAI相关的UE在流量路由中的UPF选择。
步骤904,EES向UE发送业务宣告或业务更新通知。
具体实施时,由EES中的业务注册功能向UE发送业务宣告或业务更新通知,业务更新通知中携带该应用的相关标识信息EAS ID和应用的KPI要求,如带宽、优先级、时延、应用的服务区域范围、应用类型和QoS要求等。
优选的,业务更新通知中还可以包括EAS Instance ID,DNN,DNAI列表,网络切片标识S-NSSAI信息,该应用的索引ID。
步骤905,UE与EAS之间发起应用业务。
具体实施时,UE和EAS之间基于建立好的用户面资源,发起上层应用调用。
本实施例中,业务注册功能位于EES实体中,资源管理功能位于ECS实体中,如图10所示,为本申请实施例提供的另一移动边缘业务更新方法实体装置结构示意图。
装置由边缘应用服务器1001、边缘使能服务器1002和边缘配置服务器1003构成,边缘使能服务器1002中包括业务注册功能模块,边缘配置服务器1003中包括资源管理功能模块,资源管理功能模块与NEF通过Nnef接口连接,资源管理功能模块与PCF通过Npcf接口连接,也可以使用其他兼容或包含Nnef接口的接口与NEF进行连接,使用其他兼容或包含Npcf接口的接口与PCF进行连接,以保障资源管理功能模块与核心网之间的交互可重用现有流程。其他各部分间可以使用EDGE接口进行连接,也可以使用其他符合实际需求的接口进行连接,本申请实施例对此不做限定。
如图11所示,本申请实施例提供的移动边缘业务更新方法中ECS通过NEF发起流量影响的流程示意图。
资源管理功能模块通过NEF向发送流量影响创建请求(Nnef_TrafficInfl uence_Create)或流量影响更新请求(Nnef_TrafficInfluence_Update),由于选用Nnef接口与NEF进行连接,该获取过程可重用现有流程,其中用户体验信息请求中包括:UE的标识,DNN,S-NSSAI信息。资源管理功能模块接收流量影响创建响应(Nnef_TrafficInfluence_Create Response)或流量影响更新响应(Nnef_TrafficInfluence_Update Response)。当然,也可以使用其他兼容或 包含Nnef接口的接口与NEF进行连接,本申请实施例对此不做限定。
具体实施时,获取体验信息的实体可以为现有的实体ECS,也可以通过本申请定义的实体资源管理功能模块。
如图12所示,本申请实施例提供的ECS与核心网之间触发PDU会话修改的流程示意图。
由于选用Npcf接口与PCF进行连接,该实施例可重用现有流程,具体实施时,向核心网中的PCF发起策略授权创建请求(Npcf_PolicyAuthorization_Create),由核心网修改PDU会话(network requested PDU Session Modification)。当然,也可以使用其他兼容或包含Npcf接口的接口与PCF进行连接,本申请实施例对此不做限定。
向核心网发起请求的实体为现有实体ECS,或本申请定义的实体资源管理功能模块。
需要说明的是,向PCF发起策略授权创建的请求中可以包括如下内容:UE标识,带宽,QoS要求,媒体类型,DNN,S-NSSAI信息等。
如图13所示,基于移动边缘业务更新方法同样的发明构思,本申请还提供一种移动边缘业务更新装置,该装置包括:
获取单元1301,用于获取移动边缘计算网络的业务资源使用需求;
确定单元1302,用于根据业务资源使用需求确定待更新业务的用户的资源调度策略;
处理单元1303,用于基于资源调度策略,向用户发起移动边缘计算网络业务更新。
在一种可能实施的方式中,本申请实施例提供的装置中,所述获取单元1301具体用于:
获取移动边缘计算网络的业务资源使用需求;
根据业务资源使用需求向核心网请求网络资源的体验信息;
在一种可能实施的方式中,本申请实施例提供的装置中,所述确定单元1302具体用于:
当体验信息不匹配业务资源使用需求时,基于业务资源使用需求和体验信息,确定用户的资源调度策略。
在一种可能实施的方式中,本申请实施例提供的装置中,所述确定单元1302用于:
根据业务资源使用需求向核心网发送流量影响请求,流量影响请求包括流量影响创建请求或流量影响更新请求。
在一种可能实施的方式中,本申请实施例提供的装置中,用户与核心网之间建立有PDU会话,所述确定单元1302用于:
根据业务资源使用需求指示核心网修改用户与核心网之间的PDU会话。
在一种可能实施的方式中,本申请实施例提供的装置中,所述处理单元1303具体用于:
向用户发送业务更新通知;
基于核心网修改后的PDU会话,向用户发起移动边缘计算网络业务更新。
如图14所示,本申请还提供一种移动边缘业务更新***,该***包括边缘应用服务器1401、业务注册功能装置1402和资源管理功能装置1403;
业务注册功能装置1402用于从边缘应用服务器1401获取移动边缘计算网络的业务资源使用需求,指示资源管理功能装置1403获取待更新业务的体验信息,并向用户发送业务更新通知;
资源管理功能装置1403用于获取待更新业务的体验信息,基于业务资源使用需求和体验信息确定用户的资源调度策略,并将业务资源使用需求和体验信息发送至边缘应用服务器1401;
边缘应用服务器1401用于生成业务资源使用需求,并基于业务资源使用需求和体验信息向用户发起移动边缘计算网络业务更新。
在一种可能实施的方式中,本申请实施例提供的***中,用户与核心网之间建立有PDU会话,所述资源管理功能装置1403还用于:
根据业务资源使用需求修改用户与核心网之间的PDU会话。
另外,结合图2-图13描述的本申请实施例的移动边缘业务更新方法和装 置可以由电子设备来实现。图15示出了本申请实施例提供的电子设备的硬件结构示意图。
电子设备可以包括处理器1501以及存储有计算机程序指令的存储器1502;
所述处理器1501用于读取所述存储器1502中的程序指令并执行:
获取移动边缘计算网络的业务资源使用需求;
根据所述业务资源使用需求确定待更新业务的用户的资源调度策略;
基于所述资源调度策略,向所述用户发起移动边缘计算网络业务更新。
具体地,上述处理器1501可以包括中央处理器(Central Processing Units,CPU),或者特定集成电路(Application Specific Integrated Circuit,ASIC),或者可以被配置成实施本申请实施例的一个或多个集成电路。
存储器1502可以包括用于数据或指令的大容量存储器。举例来说而非限制,存储器1502可包括硬盘驱动器(Hard Disk Drive,HDD)、软盘驱动器、闪存、光盘、磁光盘、磁带或通用串行总线(Universal Serial Bus,USB)驱动器或者两个或更多个以上这些的组合。在合适的情况下,存储器1502可包括可移除或不可移除(或固定)的介质。在合适的情况下,存储器1502可在数据处理装置的内部或外部。在特定实施例中,存储器1502是非易失性固态存储器。在特定实施例中,存储器1502包括只读存储器(ROM)。在合适的情况下,该ROM可以是掩模编程的ROM、可编程ROM(PROM)、可擦除PROM(EPROM)、电可擦除PROM(EEPROM)、电可改写ROM(EAROM)或闪存或者两个或更多个以上这些的组合。
在一种可能实施的方式中,所述处理器1501具体用于:
获取移动边缘计算网络的业务资源使用需求;
根据所述业务资源使用需求向核心网请求网络资源的体验信息。
在一种可能实施的方式中,所述处理器1501具体用于:
当所述体验信息不匹配所述业务资源使用需求时,基于所述业务资源使用需求和所述体验信息,确定所述用户的资源调度策略。
在一种可能实施的方式中,所述处理器1501具体用于:
根据所述业务资源使用需求向核心网发送流量影响请求,所述流量影响请求包括流量影响创建请求或流量影响更新请求。
在一种可能实施的方式中,所述处理器1501具体用于:
根据所述业务资源使用需求指示核心网修改所述用户与所述核心网之间的PDU会话。
在一种可能实施的方式中,所述处理器1501具体用于:
向所述用户发送业务更新通知;
基于所述核心网修改后的PDU会话,向所述用户发起移动边缘计算网络业务更新。
在一个示例中,电子设备还可包括通信接口1503和总线1510。其中,如图15所示,处理器1501、存储器1502、通信接口1503通过总线1510连接并完成相互间的通信。
通信接口1503,主要用于实现本申请实施例中各模块、装置、单元和/或设备之间的通信。
总线1510包括硬件、软件或两者,将电子设备的部件彼此耦接在一起。举例来说而非限制,总线可包括加速图形端口(AGP)或其他图形总线、增强工业标准架构(EISA)总线、前端总线(FSB)、超传输(HT)互连、工业标准架构(ISA)总线、无限带宽互连、低引脚数(LPC)总线、存储器总线、微信道架构(MCA)总线、***组件互连(PCI)总线、PCI-Express(PCI-X)总线、串行高级技术附件(SATA)总线、视频电子标准协会局部(VLB)总线或其他合适的总线或者两个或更多个以上这些的组合。在合适的情况下,总线1510可包括一个或多个总线。尽管本申请实施例描述和示出了特定的总线,但本申请考虑任何合适的总线或互连。
该电子设备可以基于接收到的资源信息,执行本申请实施例中的移动边缘业务更新方法,从而实现结合图2-图13描述的移动边缘业务更新方法和装置。
另外,结合上述实施例中的电子设备,本申请实施例可提供一种计算机 可读存储介质来实现。该计算机可读存储介质上存储有计算机程序指令;该计算机程序指令被处理器执行时实现上述实施例中的任意一种移动边缘业务更新方法。
利用本申请提供的移动边缘业务更新方法、装置、***、设备及介质,具有以下有益效果:获取移动边缘计算网络的业务资源使用需求,根据业务资源使用需求获取网络资源体验信息,并根据以上信息确定待更新业务的用户的资源调度策略并协助核心网进行用户的网络资源分配,基于资源调度策略,向用户发起移动边缘计算网络业务更新。本申请通过业务资源使用需求和网络资源体验信息确定资源调度策略,并针对用户协助核心网进行网络资源分配,保证了移动边缘网络资源满足应用更新带来的新的资源使用需求,同时也保证了用户在边缘网络的服务质量能够适应应用更新的需求,解决了应用需求和用户网络资源之间在边缘网络缺乏协调和匹配的问题。
本申请是参照根据本申请实施例的方法、设备(***)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器,使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中,使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品,该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上,使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理,从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图 一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管已描述了本申请的优选实施例,但本领域内的技术人员一旦得知了基本创造性概念,则可对这些实施例作出另外的变更和修改。所以,所附权利要求意欲解释为包括优选实施例以及落入本申请范围的所有变更和修改。
显然,本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样,倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内,则本申请也意图包含这些改动和变型在内。

Claims (21)

  1. 一种移动边缘业务更新方法,其特征在于,所述方法包括:
    获取移动边缘计算网络的业务资源使用需求;
    根据所述业务资源使用需求确定待更新业务的用户的资源调度策略;
    基于所述资源调度策略,向所述用户发起移动边缘计算网络业务更新。
  2. 根据权利要求1所述的方法,其特征在于,所述获取移动边缘计算网络的业务资源使用需求,包括:
    获取移动边缘计算网络的业务资源使用需求;
    根据所述业务资源使用需求向核心网请求网络资源的体验信息。
  3. 根据权利要求1所述的方法,其特征在于,所述根据所述业务资源使用需求确定待更新业务的用户的资源调度策略,包括:
    当所述体验信息不匹配所述业务资源使用需求时,基于所述业务资源使用需求和所述体验信息,确定所述用户的资源调度策略。
  4. 根据权利要求1所述的方法,其特征在于,所述根据所述业务资源使用需求确定待更新业务的用户的资源调度策略,包括:
    根据所述业务资源使用需求向核心网发送流量影响请求,所述流量影响请求包括流量影响创建请求或流量影响更新请求。
  5. 根据权利要求1所述的方法,其特征在于,所述用户与核心网之间建立有PDU会话,所述根据所述业务资源使用需求确定待更新业务的用户的资源调度策略,包括:
    根据所述业务资源使用需求指示核心网修改所述用户与所述核心网之间的PDU会话。
  6. 根据权利要求1所述的方法,其特征在于,所述基于所述资源调度策略,向所述用户发起移动边缘计算网络业务更新,包括:
    向所述用户发送业务更新通知;
    基于所述核心网修改后的PDU会话,向所述用户发起移动边缘计算网络 业务更新。
  7. 一种移动边缘业务更新装置,其特征在于,所述装置包括:
    获取单元,用于获取移动边缘计算网络的业务资源使用需求;
    确定单元,用于根据所述业务资源使用需求确定待更新业务的用户的资源调度策略;
    处理单元,用于基于所述资源调度策略,向所述用户发起移动边缘计算网络业务更新。
  8. 根据权利要求7所述的装置,其特征在于,所述获取单元具体用于:
    获取移动边缘计算网络的业务资源使用需求;
    根据所述业务资源使用需求向核心网请求网络资源的体验信息。
  9. 根据权利要求7所述的装置,其特征在于,所述确定单元具体用于:
    当所述体验信息不匹配所述业务资源使用需求时,基于所述业务资源使用需求和所述体验信息,确定所述用户的资源调度策略。
  10. 根据权利要求7所述的装置,其特征在于,所述确定单元用于:
    根据所述业务资源使用需求向核心网发送流量影响请求,所述流量影响请求包括流量影响创建请求或流量影响更新请求。
  11. 根据权利要求7所述的装置,其特征在于,所述用户与核心网之间建立有PDU会话,所述确定单元用于:
    根据所述业务资源使用需求指示核心网修改所述用户与所述核心网之间的PDU会话。
  12. 根据权利要求7所述的装置,其特征在于,所述处理单元具体用于:
    向所述用户发送业务更新通知;
    基于所述核心网修改后的PDU会话,向所述用户发起移动边缘计算网络业务更新。
  13. 一种移动边缘业务更新***,其特征在于,所述***包括边缘应用服务器、业务注册功能装置和资源管理功能管理装置;
    所述业务注册功能装置用于从边缘应用服务器获取移动边缘计算网络的 业务资源使用需求,指示所述资源管理功能装置获取网络资源的体验信息,并向所述用户发送业务更新通知;
    所述资源管理功能装置用于获取待更新业务的体验信息,基于所述业务资源使用需求和所述体验信息确定所述用户的资源调度策略,并将所述业务资源使用需求和所述体验信息发送至所述边缘应用服务器;
    所述边缘应用服务器用于生成所述业务资源使用需求,并基于所述业务资源使用需求和所述体验信息向所述用户发起移动边缘计算网络业务更新。
  14. 根据权利要求13所述的***,其特征在于,所述用户与核心网之间建立有PDU会话,所述资源管理功能装置还用于:
    根据所述业务资源使用需求修改所述用户与核心网之间的PDU会话。
  15. 一种电子设备,其特征在于,包括:处理器和存储器;
    其中,所述存储器用于存储计算机程序指令;
    所述处理器用于读取所述存储器中的程序指令并执行:
    获取移动边缘计算网络的业务资源使用需求;
    根据所述业务资源使用需求确定待更新业务的用户的资源调度策略;
    基于所述资源调度策略,向所述用户发起移动边缘计算网络业务更新。
  16. 根据权利要求15所述的电子设备,其特征在于,所述处理器具体用于:
    获取移动边缘计算网络的业务资源使用需求;
    根据所述业务资源使用需求向核心网请求网络资源的体验信息。
  17. 根据权利要求15所述的电子设备,其特征在于,所述处理器具体用于:
    当所述体验信息不匹配所述业务资源使用需求时,基于所述业务资源使用需求和所述体验信息,确定所述用户的资源调度策略。
  18. 根据权利要求15所述的电子设备,其特征在于,所述处理器具体用于:
    根据所述业务资源使用需求向核心网发送流量影响请求,所述流量影响 请求包括流量影响创建请求或流量影响更新请求。
  19. 根据权利要求15所述的电子设备,其特征在于,所述处理器具体用于:
    根据所述业务资源使用需求指示核心网修改所述用户与所述核心网之间的PDU会话。
  20. 根据权利要求15所述的电子设备,其特征在于,所述处理器具体用于:
    向所述用户发送业务更新通知;
    基于所述核心网修改后的PDU会话,向所述用户发起移动边缘计算网络业务更新。
  21. 一种计算机可读存储介质,其上存储有计算机程序指令,其特征在于,当所述计算机程序指令被处理器执行时实现如权利要求1-6中任一项所述的方法。
PCT/CN2020/134060 2020-03-24 2020-12-04 一种移动边缘业务更新方法、装置、***、设备及介质 WO2021189938A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010211451.5A CN113453194B (zh) 2020-03-24 2020-03-24 一种移动边缘业务更新方法、装置、***、设备及介质
CN202010211451.5 2020-03-24

Publications (1)

Publication Number Publication Date
WO2021189938A1 true WO2021189938A1 (zh) 2021-09-30

Family

ID=77806339

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/134060 WO2021189938A1 (zh) 2020-03-24 2020-12-04 一种移动边缘业务更新方法、装置、***、设备及介质

Country Status (2)

Country Link
CN (1) CN113453194B (zh)
WO (1) WO2021189938A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114614989A (zh) * 2021-11-18 2022-06-10 亚信科技(中国)有限公司 基于数字孪生技术的网络业务的可行性验证方法及装置
CN115695187A (zh) * 2022-10-24 2023-02-03 中国工商银行股份有限公司 通讯资源获取方法、装置、计算机设备和存储介质

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115914339A (zh) * 2021-09-30 2023-04-04 华为技术有限公司 应用上下文重定位的方法和装置
CN113891359B (zh) * 2021-10-11 2023-06-20 中国联合网络通信集团有限公司 一种数据处理方法、装置及存储介质
CN114500530B (zh) * 2021-12-31 2023-12-08 北方信息控制研究院集团有限公司 一种民用边缘信息***自动调整方法

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1620653A (zh) * 2001-05-23 2005-05-25 国际商业机器公司 计算网络中服务的动态部署
US20170064597A1 (en) * 2015-08-28 2017-03-02 Fujitsu Limited Method for deployment, deployment destination identification program, and deployment system
US20170237607A1 (en) * 2016-02-16 2017-08-17 Vodafone Ip Licensing Limited Telecommunications Network Communication Sessions
CN110291298A (zh) * 2016-11-16 2019-09-27 费德罗-莫格尔汽车零部件有限责任公司 改进的承窝组件和制造方法
CN110769038A (zh) * 2019-10-09 2020-02-07 腾讯科技(深圳)有限公司 服务器调度方法及装置、存储介质、电子设备

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10939232B2 (en) * 2016-12-09 2021-03-02 Nokia Technologies Oy Location related application management

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1620653A (zh) * 2001-05-23 2005-05-25 国际商业机器公司 计算网络中服务的动态部署
US20170064597A1 (en) * 2015-08-28 2017-03-02 Fujitsu Limited Method for deployment, deployment destination identification program, and deployment system
US20170237607A1 (en) * 2016-02-16 2017-08-17 Vodafone Ip Licensing Limited Telecommunications Network Communication Sessions
CN110291298A (zh) * 2016-11-16 2019-09-27 费德罗-莫格尔汽车零部件有限责任公司 改进的承窝组件和制造方法
CN110769038A (zh) * 2019-10-09 2020-02-07 腾讯科技(深圳)有限公司 服务器调度方法及装置、存储介质、电子设备

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114614989A (zh) * 2021-11-18 2022-06-10 亚信科技(中国)有限公司 基于数字孪生技术的网络业务的可行性验证方法及装置
CN114614989B (zh) * 2021-11-18 2024-05-28 亚信科技(中国)有限公司 基于数字孪生技术的网络业务的可行性验证方法及装置
CN115695187A (zh) * 2022-10-24 2023-02-03 中国工商银行股份有限公司 通讯资源获取方法、装置、计算机设备和存储介质
CN115695187B (zh) * 2022-10-24 2024-05-24 中国工商银行股份有限公司 通讯资源获取方法、装置、计算机设备和存储介质

Also Published As

Publication number Publication date
CN113453194A (zh) 2021-09-28
CN113453194B (zh) 2022-08-23

Similar Documents

Publication Publication Date Title
WO2021189938A1 (zh) 一种移动边缘业务更新方法、装置、***、设备及介质
US20200336410A1 (en) Routing rule obtaining method, device, and system
EP4199579B1 (en) Network resource management method, apparatus, and system
EP4132022A1 (en) Multicast and broadcast service communication method, apparatus, electronic device, and storage medium
JP2022093339A (ja) QoS制御方法およびデバイス
WO2021037175A1 (zh) 一种网络切片的管理方法及相关装置
CN108011899B (zh) 一种会话建立优化方法、装置和***
CN109392024B (zh) 一种业务质量流的控制方法及相关设备
WO2022105897A1 (zh) 业务路径建立方法、通信装置及存储介质
WO2013152565A1 (zh) 能力聚合开放的方法和***
WO2020083322A1 (zh) 一种呼叫方法、设备及***
CN106792923B (zh) 一种配置QoS策略的方法及装置
WO2018170707A1 (zh) 控制面连接管理方法和装置
US10268532B2 (en) Application message processing system, method, and application device
US10511494B2 (en) Network control method and apparatus
CN113541981B (zh) 网络切片的成员管理方法及***
WO2020200057A1 (zh) 一种通信方法及装置
US20230216798A1 (en) Data Steering Method and Apparatus
CN115004744B (zh) 一种在5g通信网络的边缘站点之间建立连接的方法
CN110708678A (zh) 一种通信方法及设备
EP3834386B1 (en) System and method for sharing subscriber resources in a network environment
WO2022188570A1 (zh) 群组内点到多点通信业务的话权控制方法、装置及介质
JP7406015B2 (ja) アプリケーション要求処理方法、システム、電子機器及び記憶媒体
WO2022062733A1 (zh) QoS流更新方法、设备及存储介质
EP4084452A1 (en) Apparatus, method and computer program

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20926592

Country of ref document: EP

Kind code of ref document: A1