WO2020143384A1 - 一种网络切片的资源调度的方法及设备 - Google Patents

一种网络切片的资源调度的方法及设备 Download PDF

Info

Publication number
WO2020143384A1
WO2020143384A1 PCT/CN2019/124618 CN2019124618W WO2020143384A1 WO 2020143384 A1 WO2020143384 A1 WO 2020143384A1 CN 2019124618 W CN2019124618 W CN 2019124618W WO 2020143384 A1 WO2020143384 A1 WO 2020143384A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
network
slice
network slice
network element
Prior art date
Application number
PCT/CN2019/124618
Other languages
English (en)
French (fr)
Inventor
崇卫微
辛阳
吴晓波
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP19908635.6A priority Critical patent/EP3893439A4/en
Priority to AU2019421312A priority patent/AU2019421312B2/en
Priority to KR1020217024156A priority patent/KR20210104902A/ko
Priority to JP2021539647A priority patent/JP7343590B2/ja
Priority to KR1020237044211A priority patent/KR20240005143A/ko
Publication of WO2020143384A1 publication Critical patent/WO2020143384A1/zh
Priority to US17/369,510 priority patent/US12089241B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/54—Allocation or scheduling criteria for wireless resources based on quality criteria
    • H04W72/542—Allocation or scheduling criteria for wireless resources based on quality criteria using measured or perceived quality
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5061—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the interaction between service providers and their network customers, e.g. customer relationship management
    • H04L41/5067—Customer-centric QoS measurements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
    • H04L41/0897—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities by horizontal or vertical scaling of resources, or by migrating entities, e.g. virtual resources or entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5003—Managing SLA; Interaction between SLA and QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5003—Managing SLA; Interaction between SLA and QoS
    • H04L41/5019—Ensuring fulfilment of SLA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/78—Architectures of resource allocation
    • H04L47/781—Centralised allocation of resources
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0894—Policy-based network configuration management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition

Definitions

  • This application relates to the field of communication technology, and in particular to a method and device for resource scheduling of network slices.
  • the fifth generation (5G) network introduces the concept of network slices (NS) to cope with the different needs of different communication services for network performance, that is, 5G networks divide the actual network resources and functions. Different network slices are formed to meet these different needs, which can reduce the network operation investment cost and enrich the network operation model.
  • NS network slices
  • the network management NE determines the service level agreement (SLA) templates of different tenants according to the service level requirements of each tenant, and deploys the corresponding network slicing according to the SLA templates.
  • SLA service level agreement
  • the granularity of the SLA template determined by the network management network element based only on the service level requirements of each tenant is very coarse, and it is difficult to guarantee the performance of network slicing.
  • the network management network element allocates network resources to network slices of different tenants, it can only determine the approximate resource deployment situation according to the SLA template. This may cause waste of resources or insufficient deployment resources, thereby reducing the performance of network slices.
  • Embodiments of the present application provide a resource scheduling method for network slicing, which is used to solve the problems of resource waste and low performance of network slicing when allocating network resources for network slicing in the prior art.
  • the embodiments of the present application also provide corresponding equipment.
  • a first aspect of the present application provides a method for resource scheduling of a network slice.
  • the method may include: a slice management network element sends a request to a data analysis network element, and the request includes service experience requirement information for the first network slice;
  • the slice management network element receives the response sent by the data analysis network element, where the response includes first area information and/or first time information of the first network slice corresponding to the service experience requirement information;
  • the slice management and control network element sends second area information and/or second time information to the network device according to the first area information and/or first time information, and the second area information and/or second time information is used for all
  • the network device schedules resources for the first network slice according to the second area information and/or second time information.
  • the slice management and control network element refers to a network element with user access, resource deployment, and function execution that manages and controls network slices. It can be located on the control plane of the operator's network. For example, the slice management and control network element selects a functional network element for the network slice (network slice selection function (NSSF); it can also be located on the management plane of the operator's network, for example, the slice management and control network element is operation management and maintenance network element (operation, administration, and maintenance, OAM).
  • the network device includes at least one of the following devices: an access network device, a core network device for allocating user plane or control plane resources, a transmission network device, and a network management network element.
  • the slice management and control network element is NSSF
  • the network management network element It can be OAM.
  • the second area information may be the same as or different from the first area information
  • the second time information may be the same as or different from the first time information.
  • the response may further include the first area information and/or the first time information
  • the first service experience information of the first network slice may include: the slice management network element determines the second area information and/or the second time information according to the first service experience information.
  • the second area information may be the area with the worst service experience in the first area information, and the second time information may also be the time with the worst service experience in the first time information. In this way, it is possible to prioritize or focus on increasing resource scheduling for the areas or times with the worst service experience, thereby further improving the accuracy and utilization of resource scheduling.
  • the second area information may also be the area with the best service experience in the first area information, and the second time information may also be the time with the best service experience in the first time information. In this way, it is possible to prioritize or focus on reducing resource scheduling for the areas or times where these services experience best, thereby further improving the accuracy and utilization of resource scheduling.
  • the method may further include: the slice management network element Sending the second area information and/or the slice quality information corresponding to the second time information to the network device, wherein the slice quality information includes at least one of the following information: the second area information and/or Or the second time information corresponding to the second service experience information of the first network slice, and the satisfaction degree information of the second service experience information relative to the target service level agreement requirement information of the first network slice.
  • the second service experience information may be (Quality of Experience, QoE) information
  • the satisfaction degree information may be fulfilment information
  • the target service level agreement requirement information may be SLA requirement information. It can be known from the second possible implementation manner described above that further sending the second service experience information and the satisfaction degree information to the network device can facilitate the network device to make more accurate resource scheduling.
  • the satisfaction degree information includes unsatisfiability, satisfaction, or excess satisfaction.
  • unsatisfiable means that the second service experience information does not meet the target service level agreement requirement information of the first network slice
  • satisfaction means that the second service experience information reaches the target service level agreement of the first network slice
  • the requirement of information requirement, excess satisfaction means that the second service experience information exceeds the target service level agreement requirement information of the first network slice. It can be known from the fourth possible implementation manner that the satisfaction degree information can make the scheduling of network resources more accurate.
  • the request further includes
  • the third area information may be included
  • the third area indicated by the third area information includes the first area indicated by the first area information
  • the third area information is used to request the data analysis network element
  • the request further includes
  • the third time indicated by the third time information includes the first time indicated by the first time information
  • the third time information is used to analyze the network element to the data Requesting the first time information corresponding to the service experience requirement information in the third time. It can be known from the sixth possible implementation manner that including the third time information in the request can narrow the range of determining the first time, thereby improving the efficiency of determining the first time, and thus also improving the efficiency of resource scheduling.
  • the slice management network Before the element sends a request to the data analysis network element, the method may further include: the slice management network element obtains third service experience information of the first network slice; if the third service experience information and the target service If the level agreement requirement information does not correspond, the slice management network element determines service experience requirement information of the first network slice, and the service experience requirement information of the first network slice corresponds to the target service level agreement requirement. According to the seventh possible implementation manner, if the third service experience information does not correspond to the target service level agreement requirement information, it may be determined that the resource adjustment method as described in the first aspect needs to be performed, thereby improving The accuracy of resource scheduling.
  • the third service experience information may be service experience information of the entire network slice, or may not be service experience information of the entire network slice, but a service experience corresponding to a certain area or time of the network slice (such as the fourth area or the fourth time) information.
  • the method may further include: the slice management and control network element 3.
  • the service experience information is compared with the target service level agreement requirement information; if the third service experience information does not meet or exceeds the target service level agreement requirement information, the slice management and control network element determines the third The service experience information does not correspond to the target service level agreement requirement information.
  • the slice management network element determines the service experience requirement information of the first network slice, which may include: if the third service experience information does not satisfy the target service level agreement requirement information, the slice The management and control network element determines the service experience requirement information of the first network slice corresponding to the unsatisfactory situation; or, if the third service experience information exceeds the target service level agreement requirement information, the slice management and control network Yuan determines the service experience requirement information of the first network slice corresponding to the situation of excess satisfaction.
  • the method may further include: if the third service If the experience information does not meet the target service level agreement requirement information, the slice management network element reduces the number of service users of the first network slice; if the third service experience information exceeds the target service level agreement requirement information , The slice management network element increases the number of service users of the first network slice.
  • the third service experience information does not meet the target service level agreement requirement information, it means that the first network slice can serve fewer users, and the first network slice needs to be reduced. If the number of service users is exceeded, it means that the first network slice can serve more users, and the number of service users of the first network slice needs to be increased.
  • the third service experience information may be service experience information of the entire network slice, or may not be service experience information of the entire network slice, but a service experience corresponding to a certain area or time of the network slice (such as the fourth area or the fourth time) information.
  • the method may further include: The slice management network element obtains the initial service level agreement requirement information of the first network slice; the slice management network element determines at least one service level agreement requirement information according to the initial service level agreement requirement information of the first network slice; The slicing control network element determines one of the at least one service level agreement requirement information as the target service level agreement requirement information.
  • the initial service level agreement requirement information provided by the tenant may include single file requirements or multiple file requirements.
  • the slice management and control network element directly or indirectly determines multiple file requirements based on the initial service level agreement request information, and can choose one The file serves as the target service level agreement requirement information.
  • the target service level agreement requirement information may also be the initial service level agreement requirement information itself.
  • the The service experience requirement information of a network slice includes at least one of the following information: the user number requirement of the first network slice, the average user experience requirement of the service, and the user satisfaction ratio requirement of the service, where the The user satisfaction ratio is the ratio of the number of users whose user experience corresponding to the service is not worse than the preset value to the total number of users of the service.
  • any one of the first to eleventh possible implementation manners of the first aspect, in another possible implementation manner of the first aspect, the first The first service experience information, the second service experience information, or the third service experience information of the network slice may include at least one of the following information: the number of users of the first network slice, the number of users of the service, and the average of the services User experience information and user satisfaction ratio information of a service, wherein the user satisfaction ratio of the service is the ratio of the number of users whose user experience corresponding to the service is not less than a preset value to the total number of users of the service.
  • the slice management network element sends a service experience information request to the data analysis network element, the service experience information request is used to request service experience information of a second network slice, and the service experience information request includes the second network
  • the second network slice may be the same as the first network slice, or may be different from the first network slice.
  • the service experience information request may be a subscribe request or a request request.
  • the method further It may include that the slice management network element learns from the network management network element that a new network slice needs to be created or a network slice is deleted.
  • the method further It may include: the reason that the slicing control network element determines that the problem area and/or the problem time is the first network domain (network) domain, the problem area includes the first area or the second area, and the problem time includes the first Time or second time; the slice management network element determines the network device according to the first network domain.
  • the slice control network element can first accurately locate the problem area and the cause of the problem time is that it originates from a network domain (such as the access network domain), and then to the network domain.
  • the network device sends the problem area (ie the second area) information and/or the problem time (ie the second time) information.
  • This method can avoid blindly adjusting the resource scheduling of other normally working network domains and improve the accuracy of resource scheduling.
  • the slice management and control network element determines the cause of the problem area and/or problem time In the first network domain, it may include that the slice management network element learns from the network management network element that the cause of the problem area and/or problem time lies in the first network domain.
  • the slice management network element when the slice control network element is a slice management network element located on the operator's network control plane, the slice management network element can interact with the network management network element located on the operator's network management plane , So as to know that the first network domain is the cause of the problem area and/or problem time.
  • the slice management and control network element determines the network according to the first network domain
  • the device may include: the slice management and control network element obtains first credibility information from the network management network element, and the first credibility information is used to indicate that the cause of the problem area and/or problem time lies in the first network The credibility of the domain; the slice management network element determines the network device according to the first credibility information.
  • the method may further include: The reason why the slice management and control network element determines that the third service experience information does not correspond to the target service level agreement requirement information lies in the second network domain, and the slice management and control network element determines the second network domain according to the second network domain Network equipment.
  • the slice management and control network element can first accurately locate the third service experience of the first network slice that cannot meet the target service level agreement requirements. The reason is that it comes from a network domain (such as Into the domain), and then send the problem area (ie the second area) information and/or the problem time (ie the second time) information to the network devices in the network domain, this method can avoid blindly adjusting other working networks
  • the resource scheduling situation in the domain improves the accuracy of resource scheduling.
  • the slice management and control network element determines that the third service experience information and all The reason why the target service level agreement requirement information does not correspond lies in the second network domain, which may include: the slice management network element learns from the network management network element that the third service experience information does not correspond to the target service level agreement requirement information The reason lies in the second network domain.
  • the slice management and control network element when the slice management and control network element is a slice management and control network element located on the operator's network control plane, the slice management and control network element can interact with the network management network element on the operator's network management plane , So as to know that the second network domain is the reason why the third service experience information does not correspond to the target service level agreement requirement information.
  • the slice management and control network element determines the network according to the second network domain
  • the device may include: the slice management and control network element obtains second credibility information from the network management network element, the second credibility information is used to indicate that the third service experience information and the target service level are caused The reason why the information required by the protocol does not correspond is the credibility of the second network domain; the slice management network element determines the network device according to the second credibility information.
  • the first The network domain or the second network domain includes at least one of the following: an access network domain, a core network domain, and a transmission network domain.
  • a second aspect of the present application provides a method for resource scheduling of a network slice, which may include: a network device receiving second area information and/or second time information of a first network slice sent by a slice management network element; the network device Scheduling resources for the first network slice according to the second area information and/or second time information.
  • the slice management and control network element refers to a network element with user access, resource deployment, and function execution that manages and controls network slices. It can be located on the control plane of the operator's network. For example, the slice management and control network element selects a functional network element for the network slice (network slice selection function (NSSF); it can also be located on the management plane of the operator's network, for example, the slice management and control network element is operation management and maintenance network element (operation, administration, and maintenance, OAM).
  • the network device includes at least one of the following devices: an access network device, a core network device for allocating user plane or control plane resources, a transmission network device, and a network management network element.
  • the slice management and control network element is NSSF
  • the network management network element It can be OAM.
  • the second area information may be the same as or different from the first area information
  • the second time information may be the same as or different from the first time information.
  • the network device of the present application can perform resource scheduling based on the second area information and/or second time information, which improves the accuracy of resource scheduling and utilization of network resources, and also improves the performance of network slicing.
  • the method may further include: the network device receives the first sent by the slice management network element Slice quality information corresponding to the network slice, the slice quality information including service experience information of the first network slice and/or satisfaction degree information of the service experience information of the first network slice with respect to a target service level agreement; The network device adjusts the resource scheduled for the first network slice according to the slice quality information.
  • the service experience information may be (Quality of Experience, QoE) information
  • the satisfaction degree information may be fulfilment information
  • the target service level agreement requirement information may be SLA requirement information. It can be known from this possible implementation manner that the network device can more accurately adjust the resources scheduled for the first network slice according to the service experience information and/or satisfaction information, which can facilitate the network device to make more accurate resource scheduling.
  • the slice quality information corresponding to the first network slice includes the first The service experience information corresponding to the second area of the network slice and/or the satisfaction degree information of the service experience information corresponding to the second area relative to the target service level agreement, the second area is the second area information The indicated area.
  • the slice corresponding to the first network slice The quality information includes service experience information corresponding to the second time of the first network slice and/or satisfaction degree information of the service experience information corresponding to the second time relative to the target service level agreement requirements, the second time Is the time indicated by the second time information shown.
  • the second time is that the target service level cannot be met or exceeded The time required by the agreement.
  • the slice corresponding to the first network slice The quality information includes service experience information corresponding to the second area and the second time of the first network slice and/or satisfaction of the service experience information corresponding to the second area and the second time relative to the target service level agreement requirements Degree information, the second area is the area indicated by the second area information, and the second time is the time indicated by the shown second time information.
  • the network device according to the slice quality Adjusting the information to the resources scheduled by the first network slice may include: if the service experience information of the first network slice cannot meet the requirements of the target service level agreement, the network device is increased to the first network slice Scheduling resources; if the service experience information of the first network slice exceeds the requirements of the target service level agreement, the network device reduces the resources scheduled for the first network slice. It can be known from this possible implementation that if it cannot be satisfied, it means that the resources of the first network slice are insufficient and resources need to be added to the first network slice. If it is exceeded, it means that the resources of the first network slice are redundant and need to be One network slice reduces resources. Thus, the utilization rate of resources can be improved.
  • the network device includes At least one of the following equipment: access network equipment, core network equipment for allocating user plane or control plane resources, transmission network equipment, and network management network elements.
  • a third aspect of the present application provides a method for resource scheduling of a network slice.
  • the method may include: a data analysis network element receives a request sent by a slice management network element, and the request includes service experience requirement information for the first network slice; The data analysis network element determines first area information and/or first time information corresponding to the service experience requirement information; the data analysis network element sends a response to the slice management network element, the response includes The first area information and/or first time information corresponding to the service experience requirement information.
  • the data analysis network element refers to the network element with the function of analyzing the operator's network data or business data, which can be located on the control plane of the operator's network.
  • the data analysis network element can be a network data analysis network element (network data analysis function, NWDAF), which can also be located on the management plane of the operator's network, for example, the data analysis network element can be (Management Data Analytic System, MDAS).
  • NWDAF network data analysis function
  • MDAS Management Data Analytic System
  • the slice management and control network element refers to a network element with user access, resource deployment, and function execution that manages and controls network slices. It can be located on the control plane of the operator's network.
  • the slice management and control network element selects the function network element NSSF for the network slice; It can also be located on the management plane of the operator's network.
  • the slice management network element is the operation management and maintenance network element OAM. It can be known from the third aspect that the data analysis network element can determine the problematic first area information and/or first time information in the first network slice, thereby facilitating network devices to more accurately perform resource scheduling.
  • the method may further include: the data analysis network element determining the first area information and/or location The first service experience information of the first network slice corresponding to the first time information; then the response may further include the first area information and/or the first A first service experience information of network slicing.
  • the service experience requirement information of the first network slice includes Positive service experience requirement information and/or negative service experience requirement information
  • the positive service experience requirement information is filtering information that exceeds the first service level agreement requirement information
  • the negative service experience requirement information is not satisfying Two service level agreements require information filtering information.
  • the request may further include the In the case of three-region information, the third region indicated by the third region information includes the first region indicated by the first region information, and the method may further include: the data analysis network element according to the third region information , Acquiring the first area information corresponding to the service experience requirement information in the third area. It can be known from the possible implementation manner that the request carries the third area information, narrowing the searchable range, which is beneficial to the data analysis network element to quickly determine the first area information.
  • the request also includes
  • the third time information may be included, the third time indicated by the third time information includes the first time indicated by the first time information, and the method may further include: the data analysis network element according to the Third time information, acquiring the first time information corresponding to the service experience requirement information in the third time information. It can be known from the possible implementation manner that the request carries the third time information, narrowing the searchable range, which is helpful for the data analysis network element to quickly determine the first time information.
  • the sliced service experience requirement information includes at least one of the following information: the number of users of the first network slice, the average user experience requirement of the service, and the user satisfaction percentage requirement of the service, where the user of the service is satisfied
  • the ratio is the ratio of the number of users whose user experience corresponding to the service is not worse than a preset value to the total number of users of the service.
  • the first network The sliced first service experience information includes at least one of the following information: the number of users of the first network slice, the number of users of the service, the average user experience information of the service, and the user satisfaction ratio information of the service, wherein
  • the user satisfaction ratio of the service is the ratio of the number of users whose user experience corresponding to the service is not worse than a preset value to the total number of users of the service.
  • a fourth aspect of the present application provides a method for resource scheduling of a network slice, which may include: a network device receives resource configuration information of a first network slice sent by a network management network element, and the resource configuration information includes maximum resource configuration information (maximum resource configuration) information) and/or guaranteed resource configuration information (guarantee resource configuration), the maximum resource configuration information is used to indicate the maximum available resources of the first network slice, and the guaranteed resource configuration information is used to indicate the first The network slice guarantees resources that can be used; the network device schedules resources for the first network slice according to the resource configuration information of the first network slice.
  • the network device includes at least one of the following devices: an access network device, a core network device for allocating user plane or control plane resources, and a transmission network device.
  • the network management network element refers to a device that has deployment network resources and has management and maintenance functions for the operation of the network, such as OAM or NSSF. It can be seen from the fourth aspect that the resources of the network do not need to be bound to the network slice. In other words, the resources of the network are not fixedly allocated to a network slice.
  • the network resource scheduling method provided in the fourth aspect, wherein the network device can schedule resources for a certain network slice based on the guaranteed resource range under the maximum available resource range according to the instructions of the network management network element.
  • This method enables the network device to flexibly schedule resources for the network slice according to the actual amount of resources required by the network slice, and promises to be able to schedule resources for the network slice to ensure the usable resource range when the network slice needs it.
  • network slicing may also allow the use of resources with the maximum available resource range. This method not only ensures that the network slice has resources available, but also improves the flexibility of the resources.
  • the first network slice guarantees that resources that can be used are allowed to be used by the second network slice. It can be seen from this possible implementation that the resources guaranteed to be used by the first network slice can also be used by the second network slice, especially when the first network slice does not need to use too many resources, the remaining resources within the usable resource range are guaranteed.
  • the resources are allowed to be used by other network slices, as long as it can ensure that the first network slice can certainly schedule resources for the first network slice to be used in a guaranteed range of resources. This method improves the flexibility of resource utilization.
  • the maximum resource configuration information is maximum air interface resource configuration information and/or guaranteed resource configuration information is guaranteed air interface resource configuration information.
  • the network device according to the The resource configuration information of the first network slice is the first network slice scheduling resource, which may include: the network device is within the limit of the maximum resource configuration information, and the priority is the first according to the guaranteed resource configuration information
  • the network slice schedules the resources that can be guaranteed to be used.
  • the information and/or guaranteed resource configuration information is the maximum resource configuration information and/or guaranteed resource configuration information corresponding to the first time;
  • the network device schedules resources for the first network slice according to the resource configuration information of the first network slice May include: the network device scheduling resources for the first network slice at the first time according to the maximum resource configuration information and/or guaranteed resource configuration information corresponding to the first time.
  • the first time may be included in the maximum resource configuration information and/or guaranteed resource configuration information, or may be pre-negotiated or included in the maximum resource configuration information and/or guaranteed resource configuration information, not It needs to be included in the maximum resource configuration information and/or guaranteed resource configuration information.
  • the information and/or guaranteed resource configuration information is the maximum resource configuration information and/or guaranteed resource configuration information corresponding to the first area; the network device schedules resources for the first network slice according to the resource configuration information of the first network slice May include: the network device scheduling resources for the first network slice in the first area according to the maximum resource configuration information and/or guaranteed resource configuration information corresponding to the first area.
  • the first area may be included in the maximum resource configuration information and/or guaranteed resource configuration information, or may be pre-negotiated or included in the maximum resource configuration information and/or guaranteed resource configuration information, not It needs to be included in the maximum resource configuration information and/or guaranteed resource configuration information.
  • the method may further include : The network device receives slice quality information corresponding to the first network slice sent by a slice management network element, where the slice quality information includes service experience information of the first network slice and/or the first network slice The satisfaction degree information of the service experience information relative to the target service level agreement; the network device adjusts the resource scheduled for the first network slice according to the slice quality information.
  • the slice quality information corresponding to the first network slice includes the first The service experience information corresponding to the second area of the network slice and/or the satisfaction degree information of the service experience information corresponding to the second area relative to the target service level agreement requirements.
  • the second area is unable to meet or exceed the target service level The area required by the agreement.
  • the slice quality information corresponding to the first network slice includes The service experience information corresponding to the second time of the first network slice and/or the satisfaction degree information of the service experience information corresponding to the second time relative to the target service level agreement requirements.
  • the second time is that the target service level cannot be met or exceeded The time required by the agreement.
  • the slice quality information corresponding to the first network slice includes the first The service experience information corresponding to the second area and the second time of a network slice and/or the satisfaction degree information of the service experience information corresponding to the second area and the second time relative to the target service level agreement requirements.
  • the network device Adjusting the quality information to the resources scheduled by the first network slice may include: if the service experience information of the first network slice cannot meet the requirements of the target service level agreement, the network device is increased to the first network Resources for slice scheduling; if the service experience information of the first network slice exceeds the requirements of the target service level agreement, the network device reduces the resources scheduled for the first network slice.
  • a fifth aspect of the present application provides a method for resource scheduling of a network slice, which may include: a network management network element determines resource configuration information of a first network slice, and the resource configuration information includes maximum resource configuration information (maximum resource configuration) and// Or guaranteed resource configuration information (guarantee resource configuration), the maximum resource configuration information is used to indicate the maximum available resources of the first network slice, and the guaranteed resource configuration information is used to indicate the guaranteed performance of the first network slice Resources used; the network management network element sends resource configuration information of the first network slice to the network device, where the resource configuration information is used by the network device to schedule the first network slice according to the resource configuration information Resources.
  • a network management network element determines resource configuration information of a first network slice, and the resource configuration information includes maximum resource configuration information (maximum resource configuration) and// Or guaranteed resource configuration information (guarantee resource configuration), the maximum resource configuration information is used to indicate the maximum available resources of the first network slice, and the guaranteed resource configuration information is used to indicate the guaranteed performance of the first network slice Resources used; the
  • the network management network element refers to a device that has deployment network resources and has management and maintenance functions for the operation of the network, such as OAM or NSSF. It can be seen from the fifth aspect that the resources of the network need not be bound to the network slice. In other words, the resources of the network are not fixedly allocated to a network slice.
  • the network device includes at least one of the following devices: an access network device, a core network device for allocating user plane or control plane resources, and a transmission network device. According to the network resource scheduling method provided in the fifth aspect, the network device can schedule resources for a certain network slice based on the guaranteed resource range under the maximum available resource range according to the instructions of the network management network element.
  • This method enables the network device to flexibly schedule resources for the network slice according to the actual amount of resources required by the network slice, and promises to be able to schedule resources for the network slice to ensure the usable resource range when the network slice needs it.
  • network slicing may also allow the use of resources with the maximum available resource range. This method not only ensures that the network slice has resources available, but also improves the flexibility of the resources.
  • the maximum resource configuration information is a maximum air interface resource configuration
  • the information and/or guaranteed resource configuration information is guaranteed air interface resource configuration information.
  • the maximum resource configuration information and/or guaranteed resource configuration is the maximum resource configuration information and/or guaranteed resource configuration information corresponding to the first time; or, the maximum resource configuration information and/or guaranteed resource configuration information is the maximum resource configuration information and/or guaranteed resource configuration corresponding to the first area information.
  • the first time may be included in the maximum resource configuration information and/or guaranteed resource configuration information, or may be pre-negotiated or included in the maximum resource configuration information and/or guaranteed resource configuration information, not It needs to be included in the maximum resource configuration information and/or guaranteed resource configuration information.
  • the resource configuration information of the network slice may include: the network management network element determines the resource configuration information of the first network slice according to the target service level agreement requirement information of the first network slice.
  • the method may further include :
  • the network management network element obtains information on resources that the network device schedules for the first network slice;
  • the network management network element obtains slice quality information of the first network slice, and the slice quality information includes the first Service experience information of a network slice and/or satisfaction degree information of the service experience information of the first network slice relative to the target service level agreement;
  • the network management network element is the first network according to the network device Slicing scheduled resource information and the slicing quality information, updating resource configuration information of the first network slice; the network management network element sending the updated resource configuration information to the network device.
  • the information of the resource includes the second area of the first network slice
  • the service experience information of the first network slice includes service experience information corresponding to the second area of the first network slice
  • the network management network element is the first according to the network device
  • the information about the resource scheduled by the network slice and the slice quality information to update the resource configuration information of the first network slice may include: the network management network element according to the information about the resource corresponding to the second area and the second Update service configuration information of the first network slice according to the service experience information corresponding to the area.
  • the information of the resource includes the second time of the first network slice
  • the service experience information of the first network slice includes service experience information corresponding to the second time of the first network slice
  • the network management network element is the first according to the network device
  • the information of the resource scheduled by the network slice and the slice quality information to update the resource configuration information of the first network slice may include: the information of the resource corresponding to the second time and the second The service experience information corresponding to time updates the resource configuration information of the first network slice.
  • the resource information includes the second area of the first network slice Information about resources corresponding to the second time
  • the service experience information of the first network slice includes the second area of the first network slice and service experience information corresponding to the second time
  • the network management network element Updating, by the network device, the resource scheduling information of the first network slice and the slice quality information, updating the resource configuration information of the first network slice may include: the network management network element according to the second area and the first Update the resource configuration information of the first network slice with the resource information corresponding to the second time and the service experience information corresponding to the second area and the second time.
  • the resource configuration information may include: the network management network element updates the maximum resource configuration information and/or guaranteed resource configuration information so that the updated maximum resource configuration information is not less than the network device being the first network Resource for slicing scheduling.
  • the network management network element obtains the first
  • the slice quality information of a network slice may include: the network management network element obtains the slice quality information from the slice management network element or data analysis device.
  • a sixth aspect of the present application provides a method for controlling the number of users in a network slice, which may include: a slice management network element receiving information about the number of users of a target network slice sent by the network management network element, and indication information, where the indication information is used to indicate The reliability of the status information of the target network slice or the restriction information of the number of users; the slice control network element controls the number of users served by the target network slice according to the indication information and the number restriction information of users .
  • the slice management and control network element may be a network element with user access, resource deployment, and function execution that manages and controls network slices. It may be located on the control plane of the operator's network.
  • the network management network element can be a device with deployment network resources and management and maintenance functions for the operation of the network, such as OAM. From this sixth aspect, it can be known that the number of users served by the target network slice can be controlled according to the indication information and the user quantity limitation information, and the accuracy of the user quantity control can be improved.
  • the indication information is used to indicate status information of the target network slice; the slice management and control network element is based on
  • the instruction information and the user quantity limitation information controlling the number of users served by the target network slice may include: the slice management network element according to the user quantity limitation information according to the control mode corresponding to the status information To control the number of users served by the target network slice.
  • the state information is different, and the control method is also different. Therefore, accurate user quantity control can be achieved based on status information.
  • the state information includes a test state or a stable state.
  • the control manner is Ladder control. That is to say, the slicing control network element may access a number of users limited by the user quantity limitation information to the target network slice in a ladder manner or exclude users who have been served by the target network slice.
  • the control manner is One-time control. That is to say, according to the stable state of the target network slice, the slicing control network element accesses the target network slice or the number of users restricted by the user number restriction information at a time to the target network slice Eliminate users who provide services.
  • the indication information is used to indicate the credibility of the user quantity limitation information; the slice management network The element controls the number of users served by the target network slice according to the instruction information and the user quantity limitation information, which may include: the slice management network element corresponding to the credibility according to the user quantity limitation information Control mode, which controls the number of users served by the target network slice.
  • the The control method is a step control method. That is to say, the slicing control network element accesses the target network slice by the number of users limited by the user quantity limitation information in a ladder manner or excludes users who have been served by the target network slice.
  • the The control method is a one-time control method. That is, the slicing control network element accesses the number of users limited by the number of users restriction information to the target network slice at a time or excludes users who have been served by the target network slice.
  • the slice management The network element receives the user quantity limit information of the target network slice sent by the network management network element, which may include: the slice management network element receives service level agreement requirement information of the target network slice sent by the network management network element, and the service level The protocol requirement information includes information about the number of users of the target network slice.
  • the service level agreement requirement information of the target network slice sent by the network management network element to the slice control network element does not contain the user quantity limit information, then the user quantity limit information can be sent separately, and can be related to the target network slice service level agreement requirement Information is sent side by side.
  • the slice management The network element receiving the user quantity limitation information of the target network slice sent by the network management network element may include: the slice management network element receiving the user quantity limitation information corresponding to the area information of the target network slice sent by the network management network element;
  • the slicing control network element controls the number of users served by the target network slicing according to the instruction information and the user quantity limitation information, which may include: the slicing control network element targeting the area indicated by the area information, The number of users served by the target network slice is controlled according to the number of users corresponding to the indication information and the area information.
  • the slice management The network element receives the user quantity limitation information of the target network slice sent by the network management network element, which may include: the slice management and control network element receives the user quantity restriction information corresponding to the time information sent by the network management network element; the slice management and control network element Controlling the number of users served by the target network slice according to the indication information and the number of users restriction information may include: the slice management network element controlling the time indicated by the time information according to the indication information and The limitation information of the number of users corresponding to the time information controls the number of users served by the target network slice.
  • the slice The control network element receives the user quantity limitation information of the target network slice sent by the network management network element, which may include: the user corresponding to the area information and time information of the target network slice received by the slice management network element from the network management network element Quantity restriction information; the slice management and control network element controls the number of users served by the target network slice according to the instruction information and the user quantity restriction information, which may include: the slice management and control network element targets the area information The indicated area and the time indicated by the time information control the number of users served by the target network slice according to the indication information and the number of users corresponding to the area information and the time information.
  • the The user number limitation information includes online user number limitation information and/or registered user number limitation information.
  • a seventh aspect of the present application provides a method for controlling the number of users in a network slice.
  • the method may include: the network management network element determines user number limit information and indication information for a target network slice, and the indication information is used to indicate the target The reliability of the status information of the network slice or the quantity limitation information of the user; the network management network element sends the quantity limitation information of the target network slice to the slice management network element, and the indication information, the indication The information and the user quantity limitation information are used by the slice management network element to control the number of users served by the target network slice.
  • the network management network element can be a device with deployment network resources and management and maintenance functions for the operation of the network.
  • it can be OAM.
  • the slice management network element can be user access, resource deployment, and function execution with management and control network slices. May be located on the control plane of the operator's network, for example, the slice management and control network element is NSSF. According to the seventh aspect, it is possible to control the number of users served by the target network slice according to the indication information and the user number limitation information, and the accuracy of user number control can be improved.
  • the network management network element determining the number of users of the target network slice limit information may include: the network management network element Obtain the service level agreement requirement information of the target network slice; the network management network element determines the user quantity limit information of the target network slice according to the service level agreement requirement information.
  • the network management network element reports to the slice management network
  • the element sending information about the number of users of the target network slice may include: the network management network element sending the area information of the target network slice and the number of users corresponding to the area information to the slice management network element,
  • the area information and the user quantity limitation information corresponding to the area information are used by the slice management network element for the area indicated by the area information, within the range indicated by the user quantity limitation information corresponding to the area information Internally control the number of users served by the target network slice.
  • the network management network element reports to the slice management network Meta-transmitting information on the number of users of the target network slice may include: the network management network element sending the time information of the target network slice and the number of users corresponding to the time information to the slice management network element, The time information and the user quantity limitation information corresponding to the time information are used to control the target network within the range indicated by the user quantity limitation information corresponding to the time information for the time indicated by the time information The number of users served by slicing.
  • the network management network element reports to the slice management network
  • the element sending information about the number of users of the target network slice may include: the network management network element sending the area information of the target network slice and the number of users corresponding to the area information to the slice management network element, And the time information of the target network slice and the user quantity restriction information corresponding to the time information, the area information and the user quantity restriction information corresponding to the area information are used by the slice management network element to target the area The area indicated by the information, controlling the number of users served by the target network slice within the range indicated by the number of users corresponding to the area information limit information, the time information and the number of users corresponding to the time information
  • the limit information is used to control the number of users served by the target network slice within the range indicated by the number of users corresponding to the time information for the time indicated by the time information.
  • the method may also include:
  • the network management network element obtains slice quality information of the target network slice, where the slice quality information includes service experience information of the target network slice and/or service experience information of the target network slice relative to the service level agreement Request information satisfaction degree information;
  • the network management network element updates the restriction information of the number of users of the target network slice or the indication information according to the slice quality information
  • the network management network element sends the updated user quantity limitation information or the updated indication information to the slice management network element.
  • the network management network element obtains slice quality information of the target network slice, It may include that the network management network element obtains the slice quality information from the slice management network element or the data analysis network element.
  • the service experience information of the target network slice includes the The service experience information corresponding to the area indicated by the area information of the target network slice
  • the network management network element updating the restriction information of the number of users of the target network slice or the indication information according to the slice quality information may include: The network management network element updates the user quantity limitation information of the target network slice or the indication information according to the service experience information corresponding to the area indicated by the area information.
  • the service experience information of the target network slice includes the The service experience information corresponding to the time indicated by the time information of the target network slice
  • the network management network element updating the restriction information of the number of users of the target network slice or the indication information according to the slice quality information may include: The network management network element updates the user quantity limitation information of the target network slice or the indication information according to the service experience information corresponding to the time indicated by the time information.
  • the service experience information of the target network slice includes the The area indicated by the area information of the target network slice and the service experience information corresponding to the time indicated by the time information
  • the network management network element updates the restriction information of the number of users of the target network slice according to the slice quality information or
  • the indication information may include: the network management network element updates the user quantity limitation information or the location of the target network slice according to the service experience information corresponding to the area indicated by the area information and the time indicated by the time information The instructions.
  • An eighth aspect of the present application provides a slice management and control network element, which is used to perform a resource scheduling method for network slices in the first aspect or any possible implementation manner of the first aspect.
  • the slice management and control network element may include a unit or module for performing resource scheduling of the network slice in the first aspect or any possible implementation manner of the first aspect, such as a receiving unit, a sending unit, and a processing unit .
  • a ninth aspect of the present application provides a network device for performing a method for resource scheduling of network slices in the second aspect or any possible implementation manner of the second aspect.
  • the network device may include a unit or module for performing resource scheduling of network slicing in the second aspect or any possible implementation manner of the second aspect, such as a receiving unit, a sending unit, and a processing unit.
  • a tenth aspect of the present application provides a data analysis network element, which is used to perform a resource scheduling method for network slices in the third aspect or any possible implementation manner of the third aspect.
  • the data analysis network element may include a unit or module for performing resource scheduling of the network slice in the third aspect or any possible implementation manner of the third aspect, such as a receiving unit, a sending unit, and a processing unit .
  • An eleventh aspect of the present application provides a network device for performing a method for resource scheduling of network slices in the fourth aspect or any possible implementation manner of the fourth aspect.
  • the network device may include a unit or module for performing resource scheduling of the network slice in the fourth aspect or any possible implementation manner of the fourth aspect, such as a receiving unit, a sending unit, and a processing unit.
  • a twelfth aspect of the present application provides a network management network element, which is used to perform a resource scheduling method for network slicing in the fifth aspect or any possible implementation manner of the fifth aspect.
  • the network management network element may include a unit or module for performing resource scheduling of network slicing in the fifth aspect or any possible implementation manner of the fifth aspect, such as a receiving unit, a sending unit, and a processing unit.
  • a thirteenth aspect of the present application provides a slice management and control network element, which is used to perform a resource scheduling method for network slices in the sixth aspect or any possible implementation manner of the sixth aspect.
  • the slice management and control network element may include a unit or module for performing resource scheduling of the network slice in the sixth aspect or any possible implementation manner of the sixth aspect, such as a receiving unit, a sending unit, and a processing unit .
  • a fourteenth aspect of the present application provides a network management network element, which is used to perform a resource scheduling method for network slicing in the seventh aspect or any possible implementation manner of the seventh aspect.
  • the network management network element may include a unit or module for performing resource scheduling of network slicing in the seventh aspect or any possible implementation manner of the seventh aspect, such as a receiving unit, a sending unit, and a processing unit.
  • a fifteenth aspect of the present application provides a slice management and control network element, which includes: at least one processor, a memory, a transceiver, and a computer-executable instruction stored in the memory and executable on the processor.
  • the processor executes, the processor executes the method as described in the first aspect or any possible implementation manner of the first aspect.
  • a sixteenth aspect of the present application provides a network device, including: at least one processor, a memory, a transceiver, and a computer-executable instruction stored in the memory and executable on the processor.
  • the processor executes the method as described in the second aspect or any possible implementation manner of the second aspect.
  • a seventeenth aspect of the present application provides a data analysis network element, including: at least one processor, a memory, a transceiver, and a computer-executable instruction stored in the memory and executable on the processor.
  • the processor executes, the processor executes the method as described in the third aspect or any possible implementation manner of the third aspect.
  • An eighteenth aspect of the present application provides a network device, including: at least one processor, a memory, a transceiver, and a computer-executable instruction stored in the memory and executable on the processor.
  • a network device including: at least one processor, a memory, a transceiver, and a computer-executable instruction stored in the memory and executable on the processor.
  • the processor executes the method described in the fourth aspect or any possible implementation manner of the fourth aspect.
  • a nineteenth aspect of the present application provides a network management network element, including: at least one processor, a memory, a transceiver, and a computer-executable instruction stored in the memory and executable on the processor.
  • the computer-executed instruction is When the processor executes, the processor executes the method described in the fifth aspect or any possible implementation manner of the fifth aspect.
  • a twentieth aspect of the present application provides a slice management and control network element, including: at least one processor, a memory, a transceiver, and a computer-executable instruction stored in the memory and executable on the processor.
  • the processor executes, the processor executes the method described in the sixth aspect or any possible implementation manner of the sixth aspect.
  • a twenty-first aspect of the present application provides a network management network element, including: at least one processor, a memory, a transceiver, and a computer-executable instruction stored in the memory and executable on the processor.
  • the computer-executed instruction is When the processor executes, the processor executes the method described in the seventh aspect or any possible implementation manner of the seventh aspect.
  • a twenty-second aspect of the present application provides a computer-readable storage medium that stores one or more computer-executable instructions.
  • the processor executes the first aspect or the first aspect described above The method described in any possible implementation manner of the aspect.
  • a twenty-third aspect of the present application provides a computer-readable storage medium that stores one or more computer-executable instructions.
  • the processor executes the second aspect or the second as described above The method described in any possible implementation manner of the aspect.
  • a twenty-fourth aspect of the present application provides a computer-readable storage medium that stores one or more computer-executable instructions.
  • the processor executes the third aspect or the third aspect described above The method described in any possible implementation manner of the aspect.
  • a twenty-fifth aspect of the present application provides a computer-readable storage medium that stores one or more computer-executable instructions.
  • the processor executes the fourth aspect or the fourth aspect described above The method described in any possible implementation manner of the aspect.
  • a twenty-sixth aspect of the present application provides a computer-readable storage medium that stores one or more computer-executable instructions.
  • the processor executes the fifth aspect or the fifth aspect described above The method described in any possible implementation manner of the aspect.
  • a twenty-seventh aspect of the present application provides a computer-readable storage medium that stores one or more computer-executable instructions.
  • the processor executes the sixth aspect or the sixth aspect described above The method described in any possible implementation manner of the aspect.
  • a twenty-eighth aspect of the present application provides a computer-readable storage medium that stores one or more computer-executable instructions.
  • the processor executes the seventh aspect or the seventh aspect described above The method described in any possible implementation manner of the aspect.
  • a twenty-ninth aspect of the present application provides a computer program product that stores one or more computer-executable instructions.
  • the processor When the computer-executed instructions are executed by the processor, the processor performs the first aspect or the first aspect described above Any possible method of implementation.
  • a thirtieth aspect of the present application provides a computer program product that stores one or more computer-executable instructions.
  • the processor When the computer-executed instructions are executed by the processor, the processor performs the second aspect or any of the second aspect A possible way to achieve it.
  • a thirty-first aspect of the present application provides a computer program product that stores one or more computer-executable instructions.
  • the processor When the computer-executed instructions are executed by the processor, the processor performs the third aspect or the third aspect Any possible method of implementation.
  • a thirty-second aspect of the present application provides a computer program product that stores one or more computer-executable instructions.
  • the processor When the computer-executed instructions are executed by the processor, the processor performs the fourth aspect or the fourth aspect described above Any possible method of implementation.
  • a thirty-third aspect of the present application provides a computer program product that stores one or more computer-executable instructions.
  • the processor When the computer-executed instructions are executed by the processor, the processor performs the fifth aspect or the fifth aspect described above Any possible method of implementation.
  • a thirty-fourth aspect of the present application provides a computer program product that stores one or more computer-executable instructions.
  • the processor When the computer-executed instructions are executed by the processor, the processor performs the sixth aspect or the sixth aspect described above Any possible method of implementation.
  • a thirty-fifth aspect of the present application provides a computer program product that stores one or more computer-executable instructions.
  • the processor When the computer-executed instructions are executed by the processor, the processor performs the seventh aspect or the seventh aspect described above Any possible method of implementation.
  • a thirty-sixth aspect of the present application provides a chip system.
  • the chip system includes a processor for supporting a slice management and control network element to implement the functions involved in the first aspect or any possible implementation manner of the first aspect.
  • the chip system may further include a memory, which is used to store necessary program instructions and data of the slice management and control network element.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • a thirty-seventh aspect of the present application provides a chip system.
  • the chip system includes a processor for supporting a network device to implement the functions mentioned in the second aspect or any possible implementation manner of the second aspect.
  • the chip system may further include a memory, which is used to store necessary program instructions and data of the network device.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • a thirty-eighth aspect of the present application provides a chip system.
  • the chip system includes a processor for supporting a data analysis network element to implement the functions described in the third aspect or any possible implementation manner of the third aspect.
  • the chip system may further include a memory, which is used to store necessary program instructions and data of the data analysis network element.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • a thirty-ninth aspect of the present application provides a chip system.
  • the chip system includes a processor for supporting a network device to implement the functions mentioned in the fourth aspect or any possible implementation manner of the fourth aspect.
  • the chip system may further include a memory, which is used to store necessary program instructions and data of the network device.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • a chip system includes a processor for supporting a network management network element to implement the functions involved in the fifth aspect or any possible implementation manner of the fifth aspect.
  • the chip system may further include a memory, which is used to store necessary program instructions and data of the network management network element.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • a forty-first aspect of the present application provides a chip system.
  • the chip system includes a processor for supporting a slice management and control network element to implement the functions mentioned in the sixth aspect or any possible implementation manner of the sixth aspect.
  • the chip system may further include a memory, which is used to store necessary program instructions and data of the slice management and control network element.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • a chip system includes a processor for supporting a network management network element to implement the functions involved in the seventh aspect or any possible implementation manner of the seventh aspect.
  • the chip system may further include a memory, which is used to store necessary program instructions and data of the network management network element.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the technical effects brought by any of the implementation methods in the eleventh aspect, the eighteenth aspect, the twenty-fifth aspect, the thirty-second aspect, and the thirty-ninth aspect can be found in the different implementation methods in the fourth aspect The technical effects brought about will not be repeated here.
  • the technical effects of any of the fourteenth aspect, the twenty-first aspect, the twenty-eighth aspect, the thirty-fifth aspect, and the forty-second aspect can be found in the different realizations of the seventh aspect The technical effects brought by the method will not be repeated here.
  • a forty-third aspect of the present application provides a communication system.
  • the communication system includes:
  • a slice management and control network element used to perform the method of the first aspect or any possible implementation manner of the first aspect
  • a network device configured to perform the method of the second aspect or any possible implementation manner of the second aspect
  • the data analysis network element is used to perform the method of the third aspect or any possible implementation manner of the third aspect.
  • a forty-fourth aspect of the present application provides a communication system.
  • the communication system includes:
  • a network device for performing the method of the fourth aspect or any possible implementation manner of the fourth aspect
  • the network management network element is used to perform the method of the fifth aspect or any possible implementation manner of the fifth aspect.
  • a forty-fifth aspect of the present application provides a communication system.
  • the communication system includes:
  • a slice management and control network element used to perform the method of the sixth aspect or any possible implementation manner of the sixth aspect
  • the network management network element is used to execute the method of the seventh aspect or any possible implementation manner of the seventh aspect.
  • the slicing management and control network element When scheduling resources for network slicing in the embodiments of the present application, the slicing management and control network element will send area information and/or time information to the network device according to, so that the network device can schedule resources for the network slice according to the area information and/or time information , To achieve precise scheduling of resources, improve the utilization of network resources, and also improve the performance of network slicing.
  • a forty-sixth aspect of the present application provides a method for resource scheduling of a network slice, which may include: a network device determines state information of a first network slice, and the state information of the first network slice includes the first network slice being in an unsigned service In a state of service agreement (SLA) or signed SLA, the network device schedules resources for the first network slice according to the state information of the first network slice.
  • SLA state of service agreement
  • the unsigned SLA state includes the test state or the new state
  • the signed SLA state includes the stable state.
  • the network device may include at least one of the following devices: an access network device, a core network device or a transmission network device for allocating user plane or control plane resources. It can be known from the forty-sixth aspect that the network device can schedule resources for the first network slice according to whether the first network slice is in the unsigned SLA state or has signed the SLA state, thereby improving scheduling accuracy.
  • the network device when the network device is an access network device, the network device
  • the state information of the first network slice is the first network slice scheduling resource, which may include: the network device scheduling air interface resources for the first network slice according to the state information of the first network slice.
  • the method may further include : The network device determines that the state information of the second network slice is that the second network slice is in the signed SLA state; when the state information of the first network slice is that the first network slice is in the unsigned SLA state, all The network device scheduling resources for the first network slice according to the state information of the first network slice may include: the network device is deprioritized behind the second network slice to schedule the first network slice Resources.
  • the network device preferentially schedules resources for network slices that have signed SLAs, which can avoid the impact of network slices that have not signed SLAs on network slices that have been signed SLAs. If the first network slice is in an unsigned SLA state, the network device may lower the priority of scheduling the first network slice resource. In other words, the network device gives priority to scheduling resources for other network slices that have signed SLAs. Only then can resources be scheduled for the first network slice.
  • the method may further include : The network device determines that the state information of the second network slice is that the second network slice is in an unsigned SLA state;
  • the network device scheduling resources for the first network slice according to the state information of the first network slice may include: The network device prioritizes the second network slice and schedules resources for the first network slice.
  • the network device if the network device learns that the first network slice is in the signed SLA state, or the first network slice never enters the signed SLA state from the signed SLA state, the network device improves Prioritize the resource scheduling of the first network slice to prevent the first network slice from being preempted by other newly created network slices.
  • the network device determining the status information of the first network slice may include: the network device determining the status information of the first network slice according to the status indication information of the first network slice sent by a network management network element, the The status indication information includes status information of the first network slice.
  • any one of the first to fourth possible implementation manners of the forty-sixth aspect, in the fifth possible implementation manner of the forty-sixth aspect may further include:
  • the network device receives the resource configuration information of the first network slice sent by the network management network element, where the resource configuration information includes maximum resource configuration information (maximum resource configuration) and/or guaranteed resource configuration information (guarantee resource configuration) information ,
  • the maximum resource configuration information is used to indicate the maximum available resources of the first network slice, and the guaranteed resource configuration information is used to indicate the guaranteed resources of the first network slice;
  • the network device uses the
  • the resource configuration information of the first network slice and the state information of the first network slice are scheduling resources of the first network slice.
  • the resource configuration information may also include status information of the first network slice.
  • the maximum resource configuration information is maximum air interface resource configuration information and/or guaranteed resource configuration information is guaranteed air interface resource configuration information.
  • a forty-seventh aspect of the present application provides a method for resource scheduling of a network slice, which may include: a network management network element determines state information of a first network slice, and the state information of the first network slice includes that the first network slice is in Not signed SLA status or signed SLA status; the network management network element sends the status information of the first network slice to a network device, the status information of the first network slice is used for the network device to be the first network Slicing resources.
  • the unsigned SLA state may include a test state or a newly created state, and the signed SLA state includes a stable state.
  • the network management network element refers to a device that has deployment network resources and management and maintenance functions for the operation of the network. For example, it can be OAM, NSSF, or NSMF.
  • the network device may include at least one of the following devices: an access network device, a core network device for allocating user plane or control plane resources, and a transmission network device. It can be known from the forty-sixth aspect that the network management network element can promptly notify the network device of the state information of the first network slice, so that the network device performs corresponding resource scheduling according to the SLA state of the first network slice.
  • the method may further include:
  • the network management network element determines resource configuration information of the first network slice, the resource configuration information includes maximum resource configuration information and/or guaranteed resource configuration information, and the maximum resource configuration information is used to indicate the first network slice Maximum available resources, the guaranteed resource configuration information is used to indicate the resources that the first network slice is guaranteed to use; the network management network element sends the resource configuration information of the first network slice to the network device, so The resource configuration information is used by the network device to schedule resources for the first network slice according to the resource configuration information.
  • the resource configuration information may also include status information of the first network slice.
  • the maximum resource configuration information is maximum air interface resource configuration information and/or guaranteed resource configuration information is guaranteed air interface resource configuration information.
  • the resource configuration information includes the first Network slice status information.
  • a forty-eighth aspect of the present application provides a method for resource scheduling of a network slice, which may include: the slice management network element determines that the service experience information of the first network slice fails to meet or exceeds the target service level of the first network slice The reason for the protocol information is in the first network domain; the slice management network element sends the slice quality information of the first network slice to the network device in the first network domain, and the slice quality information is used by the network device according to The slice quality information is the first network slice scheduling resource.
  • the slice quality information includes at least one of the following information: service experience information of the first network slice, and service satisfaction information of the first network slice relative to the target service level agreement requirement information.
  • the reason why the slice control network element can accurately locate the service experience information of the first network slice that cannot meet the target service level agreement information is because it comes from a network domain (such as the access network domain), and then Then the slice quality information of the first network slice is provided to the network device in the network domain, so that the network device in the network domain adjusts the resource scheduling situation.
  • This method can avoid blindly adjusting the resource scheduling situation of other normally working network domains, and improve the accuracy of resource scheduling.
  • the method may further include: the slice management and control network element analyzes the network element or network management network from data Yuan obtains the slice quality information of the first network slice.
  • the method may further include: the slice management and control network element determines the service experience information of the first network slice relative to the target according to the service experience information of the first network slice Service level agreements require information about the degree of satisfaction of information.
  • the method further It may include: the slice management network element determining that the service experience information of the first network slice cannot meet or exceed the target service level agreement information of the first network slice.
  • any one of the first to third possible implementation manners of the forty-eighth aspect, in the fourth possible implementation manner of the forty-eighth aspect, all The reason that the slice management and control network element determines that the service experience information of the first network slice fails to meet or exceeds the target service level agreement information of the first network slice is that the first network domain may include:
  • the slice management and control network element obtains indication information from the network management network element, the indication information is used to indicate that the service experience information of the first network slice cannot be satisfied or exceeds the target service level agreement information of the first network slice The reason lies in the first network domain;
  • the slice management and control network element obtains an indication from the network management network element Information, which can include:
  • the slice management network element sends a request message to the network management network element, the request message is used to request that the service experience information of the first network slice fails to meet or exceeds the target service level agreement of the first network slice
  • the network domain of information
  • the slice management network element receives a response message sent by the network management network element, and the response message includes the indication information.
  • the slice management network element Before a network device in a network domain sends the slice quality information of the first network slice, it may further include:
  • the slice management network element obtains credibility information from the network management network element, and the credibility information is used to indicate the credibility of the indication information;
  • the slice management network element sending the slice quality information of the first network slice to the network device in the first network domain may include:
  • the slice management and control network element sends slice quality information of the first network slice to the network device of the first network domain according to the credibility information.
  • the service experience information includes service experience information of the first network slice corresponding to the area information and/or time information.
  • the area information may be information of a problematic area
  • the time information may be information of a problematic time.
  • any one of the first to seventh possible implementation manners of the forty-eighth aspect, in the eighth possible implementation manner of the forty-eighth aspect, all Said satisfaction degree information includes unsatisfiability, satisfaction or excess satisfaction.
  • a possible implementation manner, combined with the forty-eighth aspect, any one of the first to eighth implementation aspects of the forty-eighth aspect, in the ninth possible implementation manner of the forty-eighth aspect, all The method may further include:
  • the slice management and control network element obtains the initial service level agreement requirement information of the first network slice
  • the slice management and control network element determines at least one service level agreement requirement information according to the initial service level agreement requirement information of the first network slice;
  • the slicing control network element determines one of the at least one service level agreement requirement information as the target service level agreement requirement information.
  • the first network domain includes at least one of the following: an access network domain, a core network domain, and a transmission network domain.
  • the network device includes at least one of the following devices: an access network device, a core network device for allocating user plane or control plane resources, and a transmission network device.
  • the service level agreement requirement information includes at least one of the following information: user number requirement information for the first network slice, request information for the average user experience of the service, and request information for the user satisfaction percentage of the service, wherein
  • the user satisfaction ratio of the service is the ratio of the number of users whose user experience corresponding to the service is not worse than the preset value to the total number of users of the service.
  • a forty-ninth aspect of the present application provides a resource scheduling method for a network slice.
  • the method includes: the network management network element determines that the service experience information of the first network slice fails to meet or exceeds the target of the first network slice The reason for the service level agreement information lies in the first network domain; the network management network element sends indication information to the slice management network element, the indication information is used to indicate that the service experience information of the first network slice cannot be satisfied or exceeds the first The reason for the target service level agreement information of a network slice lies in the first network domain.
  • the slice management network element can be notified of the first network domain where the service experience information of the first network slice cannot meet or exceed the target service level agreement information of the first network slice, For example: access to the network domain, so as to avoid blindly adjusting the resource scheduling situation of other normally working network domains, and improve the accuracy of resource scheduling.
  • the method further includes: the network management network element determines credibility information, the credibility The degree information is used to indicate the credibility of the indication information; the network management network element sends the credibility information to the slice management network element.
  • the method further includes: The network management network element obtains slice quality information of the first network slice from the data analysis network element, wherein the slice quality information includes at least one of the following information: service experience information of the first network slice, and the first network slice Satisfaction information of the service experience information of the target service level agreement with respect to the information required by the target service level agreement.
  • the method further includes: the network management network element determines the service experience information of the first network slice relative to the target service level according to the service experience information of the first network slice The agreement requires information about the degree of satisfaction of the information.
  • the method may further include: The network management network element determines that the service experience information of the first network slice fails to meet or exceeds the first network slice target service level agreement information.
  • the service experience information includes service experience information of the first network slice corresponding to the area information and/or time information.
  • the method further includes:
  • the network management network element receives a request message sent by the slice management network element, where the request message is used to request a network domain that causes the service experience information to fail or exceed the target service level agreement information of the first network slice ;
  • the network management network element sending instruction information to the slice management network element includes:
  • all The method may further include:
  • the slice management and control network element obtains the initial service level agreement requirement information of the first network slice
  • the slice management and control network element determines at least one service level agreement requirement information according to the initial service level agreement requirement information of the first network slice;
  • the slicing control network element determines one of the at least one service level agreement requirement information as the target service level agreement requirement information.
  • the first network domain includes at least one of the following: an access network domain, a core network domain, and a transmission network domain.
  • all The service level agreement requirement information includes at least one of the following information: requirement information of the number of users of the first network slice, requirement information of the average user experience of the service, and requirement information of the user satisfaction ratio of the service, wherein the service The user satisfaction ratio is the ratio of the number of users whose user experience corresponding to the service is not worse than the preset value to the total number of users of the service.
  • a fiftieth aspect of the present application provides a network device for performing the method for resource scheduling of network slicing in the foregoing forty-sixth aspect or any possible implementation manner of the forty-sixth aspect.
  • the network device may include a unit or module for performing resource scheduling of network slicing in the forty-sixth aspect or any possible implementation manner of the forty-sixth aspect, such as: a receiving unit, a sending unit, and Processing unit.
  • a fifty-first aspect of the present application provides a network management network element, the network management network element being used to perform the resource scheduling method for network slicing in the foregoing forty-seventh aspect or any possible implementation manner of the forty-seventh aspect .
  • the network management network element may include a unit or module for performing resource scheduling of the network slice in the forty-seventh aspect or any possible implementation manner of the forty-seventh aspect, such as: a receiving unit and a sending unit And processing unit.
  • a fifty-second aspect of the present application provides a slicing control network element, which is used to perform resource scheduling of network slicing in the foregoing forty-eighth aspect or any possible implementation manner of the forty-eighth aspect Methods.
  • the slicing management network element may include a unit or module for performing resource scheduling of network slicing in the forty-eighth aspect or any possible implementation manner of the forty-eighth aspect, such as: receiving unit, sending Unit and processing unit.
  • a fifty-third aspect of the present application provides a network management network element, which is used to perform a resource scheduling method for network slicing in the foregoing forty-ninth aspect or any possible implementation manner of the forty-ninth aspect .
  • the network management network element may include a unit or module for performing resource scheduling of network slicing in the forty-ninth aspect or any possible implementation manner of the forty-ninth aspect, such as a receiving unit and a sending unit And processing unit.
  • a fifty-fourth aspect of the present application provides a network device, including: at least one processor, a memory, a transceiver, and a computer-executable instruction stored in the memory and executable on the processor.
  • the computer-executed instruction is When the processor executes, the processor executes the method as described in the forty-sixth aspect or any possible implementation manner of the forty-sixth aspect.
  • a fifty-fifth aspect of the present application provides a network management network element, including: at least one processor, a memory, a transceiver, and a computer-executable instruction stored in the memory and executable on the processor.
  • the computer-executed instruction is When the processor executes, the processor executes the method described in the forty-seventh aspect or any possible implementation manner of the forty-seventh aspect.
  • a fifty-sixth aspect of the present application provides a slice management and control network element, including: at least one processor, a memory, a transceiver, and a computer-executable instruction stored in the memory and executable on the processor.
  • the computer-executed instruction is When the processor executes, the processor executes the method as described in the forty-eighth aspect or any possible implementation manner of the forty-eighth aspect.
  • a fifty-seventh aspect of the present application provides a network management network element, including: at least one processor, a memory, a transceiver, and a computer-executable instruction stored in the memory and executable on the processor.
  • the computer-executed instruction is When the processor executes, the processor executes the method described in the forty-ninth aspect or any possible implementation manner of the forty-ninth aspect.
  • a fifty-eighth aspect of the present application provides a computer-readable storage medium that stores one or more computer-executable instructions.
  • the processor executes the forty-sixth aspect or The method described in any possible implementation manner of the forty-sixth aspect.
  • a fifty-ninth aspect of the present application provides a computer-readable storage medium that stores one or more computer-executable instructions.
  • the processor executes the forty-seventh aspect or The method described in any possible implementation manner of the forty-seventh aspect.
  • the sixtieth aspect of the present application provides a computer-readable storage medium that stores one or more computer-executable instructions.
  • the processor executes the forty-eighth aspect or the first The method described in any possible implementation manner of the forty-eight aspect.
  • a sixty-first aspect of the present application provides a computer-readable storage medium that stores one or more computer-executable instructions.
  • the processor executes the forty-ninth aspect or The method described in any possible implementation manner of the forty-ninth aspect.
  • a sixty-second aspect of the present application provides a computer program product that stores one or more computer-executable instructions.
  • the processor When the computer-executed instructions are executed by the processor, the processor performs the forty-sixth aspect or the first Forty-six aspects of any possible implementation method.
  • a sixty-third aspect of the present application provides a computer program product that stores one or more computer-executable instructions.
  • the processor When the computer-executed instructions are executed by the processor, the processor performs the forty-seventh aspect or the first Forty-seven aspects of any possible implementation method.
  • a sixty-fourth aspect of the present application provides a computer program product that stores one or more computer-executable instructions.
  • the processor When the computer-executed instructions are executed by the processor, the processor performs the forty-eighth aspect or the first Any one of the possible implementation methods in the forty-eight aspect.
  • a sixty-fifth aspect of the present application provides a computer program product that stores one or more computer-executable instructions.
  • the processor When the computer-executed instructions are executed by the processor, the processor performs the forty-ninth aspect or the first Forty-nine aspects of any possible implementation method.
  • a sixty-sixth aspect of the present application provides a chip system.
  • the chip system includes a processor for supporting a network device to implement the functions involved in the foregoing forty-sixth aspect or any possible implementation manner of the forty-sixth aspect .
  • the chip system may further include a memory, which is used to store necessary program instructions and data of the network device.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • a sixty-seventh aspect of the present application provides a chip system.
  • the chip system includes a processor for supporting a network management network element to implement the foregoing forty-seventh aspect or any possible implementation manner of the forty-seventh aspect Features.
  • the chip system may further include a memory, which is used to store necessary program instructions and data of the network management network element.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • a sixty-eighth aspect of the present application provides a chip system.
  • the chip system includes a processor for supporting a slice management and control network element to implement the foregoing forty-eighth aspect or any possible implementation manner of the forty-eighth aspect Function.
  • the chip system may further include a memory, which is used to store necessary program instructions and data of the slice management and control network element.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • a sixty-ninth aspect of the present application provides a chip system.
  • the chip system includes a processor for supporting a network management network element to implement the foregoing forty-ninth aspect or any possible implementation manner of the forty-ninth aspect.
  • the chip system may further include a memory, which is used to store necessary program instructions and data of the network management network element.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the technical effects of any of the implementation methods in the fifty-fifth aspect, the fifty-fourth aspect, the fifty-eighth aspect, the sixty-second aspect, and the sixty-sixth aspect can be found in the forty-sixth aspect The technical effects brought by different implementations will not be repeated here.
  • the technical effects of any of the implementation methods in the fifty-second aspect, the fifty-sixth aspect, the sixtyth aspect, the sixty-fourth aspect, and the sixty-eighth aspect can be found in the forty-eighth aspect
  • the technical effects brought by different implementations will not be repeated here.
  • the fifty-seventh aspect, the sixty-first aspect, the sixty-fifth aspect, and the sixty-ninth aspect please refer to the forty-ninth aspect
  • the technical effects brought by the different implementations in the system will not be repeated here.
  • Figure 1 is a schematic diagram of a scenario of network slicing
  • FIG. 2 is a schematic diagram of an embodiment of a method for resource scheduling of network slices in an embodiment of the present application
  • FIG. 3 is a schematic diagram of another embodiment of a method for resource scheduling of network slices in an embodiment of the present application.
  • FIG. 4 is a schematic diagram of another embodiment of a method for resource scheduling of network slices in an embodiment of the present application.
  • FIG. 5 is a schematic diagram of an embodiment of controlling the number of users of a network slice in an embodiment of the present application
  • FIG. 6 is a schematic diagram of an embodiment of a network structure
  • FIG. 7A is a schematic diagram of an embodiment of resource scheduling and user number control of network slices in an embodiment of the present application.
  • FIG. 7B is a schematic diagram of another embodiment of a method for resource scheduling of network slices in an embodiment of the present application.
  • 7C is a schematic diagram of another embodiment of a method for resource scheduling of network slices in an embodiment of the present application.
  • 7D is a schematic diagram of another embodiment of the control of the number of users of the network slice in the embodiment of the present application.
  • FIG. 8 is a schematic diagram of an embodiment of a communication device in an embodiment of the present application.
  • FIG. 9 is a schematic diagram of an embodiment of a slice management and control network element in an embodiment of the present application.
  • FIG. 10 is a schematic diagram of an embodiment of a network device in an embodiment of the present application.
  • FIG. 11 is a schematic diagram of an embodiment of a data analysis network element in an embodiment of the present application.
  • FIG. 12 is a schematic diagram of another embodiment of a network device in an embodiment of this application.
  • FIG. 13 is a schematic diagram of an embodiment of a network management network element in an embodiment of the present application.
  • FIG. 14 is a schematic diagram of another embodiment of a slice management and control network element in an embodiment of the present application.
  • 15 is a schematic diagram of an embodiment of a network management network element in an embodiment of the present application.
  • 16 is a schematic diagram of another embodiment of a slice management and control network element in an embodiment of the present application.
  • 17 is a schematic diagram of another embodiment of a network management network element in an embodiment of the present application.
  • FIG. 18 is a schematic diagram of another embodiment of a network device in an embodiment of this application.
  • 19 is a schematic diagram of another embodiment of a network management network element in an embodiment of the present application.
  • the 5th generation (5G) network adopts the form of network slicing, thereby realizing the division of network resources with suitable characteristics for services with different needs. Different services have different needs, and the types of network slices are also different. As shown in Figure 1, several types of network slices and their corresponding relationships with tenants and network resources are introduced. Of course, the solutions provided in the embodiments of the present application are not limited to 5G networks, and all networks including network slices are applicable.
  • FIG. 1 is a schematic diagram of a scenario of network slicing in an embodiment of the present application.
  • eMBB enhanced mobile broadband
  • URLLC ultra-high reliability and low-latency communication
  • mIoT large Massive Internet of Things
  • the types of network slices are not limited to the ones listed here, and network slices can also have custom types.
  • Each type of network slice has its own characteristics, and the applicable fields are also different, for example:
  • eMBB is mainly used for ultra-high-definition video, holographic technology, augmented reality, virtual reality and other applications, which have high requirements on network bandwidth and speed.
  • URLLC is mainly used in unmanned driving, connected vehicles, automatic factories, telemedicine and other fields, requiring low latency and high reliability.
  • mIoT is mainly used for massive IoT sensors deployed in the fields of measurement, architecture, agriculture, logistics, smart cities, homes, etc. It does not have high requirements on latency and mobility.
  • Tenants can rent different types of network slices according to their needs. Tenants are mostly enterprises that provide various applications.
  • Network slicing is actually the division of radio access network resources, core network resources and transmission resources.
  • the corresponding radio access network resources, core network resources and transmission resources are Users provide business support.
  • the network slices involved in this application may also be referred to as slices for short, including but not limited to slices, slice instances, or slice sub-instances, where the slices may be single network slice selection support information (single network selection selection information, S-NSSAI) ID unique
  • the slice instance can be uniquely identified by the network slice information (network slice information, NSI) ID
  • the slice sub-instance can be uniquely identified by the network slice selection information (network slice selection, information, NSSI) ID.
  • the network slicing resources are managed and controlled by network management network elements, where network management network elements refer to devices that have deployment network resources and management and maintenance functions for network operation.
  • the network management network element can be located on the management plane of the operator's network.
  • the network management network element can be the OAM for operation management and maintenance.
  • the network management network element can also be located on the control plane of the operator network.
  • the network management network element can also select functions for network slice Network element NSSF.
  • the network management network element may notify the network equipment according to the actual situation of the network slice, for example: the access network equipment, the core network equipment, the transmission network equipment, or other slice management network elements adjust the corresponding resources of the network slice.
  • the slice management network element When the slice management network element controls the resources of the network slice, it can also obtain information related to the network slice from the data analysis network element, for example: area information or time information corresponding to the network slice, so that the network device can
  • the resource scheduling corresponding to the area information or time information of the network slice can improve the accuracy and utilization rate of resource scheduling, and can also improve the performance of the network slice.
  • the data analysis network element may be the network data analysis network element NWDAF, which may also be located on the management plane of the operator's network, for example, the data analysis network element may be MDAS.
  • FIG. 2 is a schematic diagram of an embodiment of a method for resource scheduling of network slices in an embodiment of the present application.
  • an embodiment of the method for resource scheduling of a network slice provided by an embodiment of the present application may include:
  • the slice management network element sends a request to the data analysis network element, where the request includes service experience requirement information for the first network slice.
  • the slice management and control network element refers to a network element with user access, resource deployment, and function execution that manages and controls network slices. It can be located on the control plane of the operator's network. For example, the slice management and control network element selects a functional network element (NSSF) for network slices. ); can also be located on the management plane of the operator's network, for example, the slice management network element is the operation management and maintenance network element (OAM).
  • the data analysis network element may be the network data analysis network element NWDAF, which may also be located on the management plane of the operator's network, for example, the data analysis network element may be MDAS.
  • the first network slice may be any network slice in the operator's network, may be a newly created network slice in a test state, or may be a network slice in a stable state.
  • the service experience requirement information of the first network slice may include at least one of the following information:
  • the user number requirement may include a filtering requirement for the user number
  • the user number requirement may include a registered user number requirement and/or an online user number requirement.
  • the requirements of the average user experience of the service may refer to the filtering requirements of the average user experience of the service, and the requirements of the average user experience of the service may include the filtering requirements of Mean Opinion Score (MOS).
  • MOS Mean Opinion Score
  • the requirements of the user satisfaction ratio of the business may refer to the filtering requirements of the user satisfaction ratio of the business.
  • the service experience requirement information of the first network slice refers to information corresponding to the target service level agreement requirement information.
  • the target service level agreement requirement information includes the number of users requirement, the average user experience requirement of the service, and the requirement of the user satisfaction ratio of the service, wherein the user satisfaction ratio of the service is that the user experience corresponding to the service is not worse than a preset value Of users accounted for the proportion of the total number of users of the service.
  • User number requirements may include registered user number requirements and/or online user number requirements.
  • the requirement of the average user experience of the service may refer to the requirement of the average user experience of the service, where the average user experience of the service may include an average opinion score (Mean Opinion Score, MOS).
  • MOS average opinion score
  • the requirement of the user satisfaction ratio of the business may refer to the requirement of the user satisfaction ratio of the business.
  • the service experience requirement information is used to filter problem areas and/or time in the first network slice.
  • the service experience requirement information of the first network slice may include positive service experience requirement information and/or negative service experience requirement information, where the positive service experience requirement information is filtering information that exceeds the first service level agreement requirement information
  • the negative service experience requirement information is filtering information that does not satisfy the second service level agreement requirement information.
  • the first service level agreement requirement information and the second service level agreement requirement information may be the same as or different from the target service level agreement requirement information.
  • the forward service experience requirement information is: the maximum number of registered users of the slice> 1 million, business average MOS>3, business user satisfaction rate>90%; negative service experience requirements information is: the maximum number of registered users of slices ⁇ 1 million, business average MOS ⁇ 3, business user satisfaction rate ⁇ 90%.
  • the forward service experience requirement information is: the maximum number of registered users of the slice >1.2 million, business average MOS>4, business user satisfaction rate>95%; negative service experience requirements information: the maximum number of registered users of slices ⁇ 800,000, business average MOS ⁇ 2.5, business user satisfaction rate ⁇ 85%.
  • the information required by the target service level agreement can be determined as follows:
  • the slice management and control network element obtains the initial service level agreement requirement information of the first network slice
  • the slice management and control network element determines at least one service level agreement requirement information according to the initial service level agreement requirement information of the first network slice;
  • the slicing control network element determines one of the at least one service level agreement requirement information as the target service level agreement requirement information.
  • the slice management and control network element may obtain initial service level agreement requirement information of the first network slice from tenant or network management network element or operator configuration information.
  • the initial service level agreement requires multiple files of information, for example:
  • the data analysis network element After receiving the request sent by the slice management network element, the data analysis network element determines first area information and/or first time information corresponding to the service experience requirement information.
  • the first area information generally refers to the area that meets the information of the positive service experience requirements or the information of the negative service experience requirements.
  • the first time information communication refers to the time when the information on the positive service experience requirements is met or the information on the negative service experience requirements is met.
  • Network slicing usually has a corresponding relationship with area and time.
  • a network slicing in different areas, or corresponding to the radio access network resources, core network resources or transmission network resources at different times will also be different, so the same network slice may be in Some areas or/and some time can meet the target service level agreement requirements information, some areas or/and some time can not meet the target service level agreement requirements information, some areas or/and some time exceed the target service level The agreement requires information.
  • the data analysis network element may determine the area or time that cannot meet the target service level agreement requirements or determine the area or time that exceeds the target service level agreement requirements in excess according to the service experience requirement information. Specifically, the data analysis network element can determine the area or time that cannot meet the requirements of the target service level agreement based on the negative service experience requirement information, or the data analysis network element can determine the excess satisfaction target based on the positive service experience requirement information The area or time required by the service level agreement.
  • the area information may be area information defined in a 3rd generation partnership (3GPP) communication network, which may be referred to as communication network area information, such as serving cell A or registration area B.
  • the area information may also be area information defined in a non-3GPP communication network.
  • the position information is a specific geographic location range, for example, latitude and longitude or global positioning system (GPS) position information, which may be referred to as geographic area information. This embodiment of the present application is not limited thereto.
  • Time information can be absolute time, for example, from 00:00 on January 1, 2017 to 24:00 on January 30, 2017, or Monday to Friday; it can also be relative time information, for example, relative to receiving Within one month before the request.
  • the granularity of the time information may be a granularity of hours, or a granularity of minutes or days, which is not limited in the embodiments of the present application.
  • the data analysis network element sends a response to the slice management network element, where the response includes first area information and/or first time information corresponding to the service experience requirement information.
  • the data analysis network element determines the first service experience information of the first network slice corresponding to the first area information and/or the first time information; then the response Also includes the first service experience information of the first network slice corresponding to the first area information and/or the first time information.
  • the first service experience information corresponds to the first area information and/or the first time information.
  • the first service experience information of the first network slice includes at least one of the following information: user number information of the first network slice, service user number information, and average service experience of the service Information and user satisfaction ratio information of a service, wherein the user satisfaction ratio of the service is the ratio of the number of users whose user experience corresponding to the service is not less than a preset value to the total number of users of the service.
  • the information on the number of users in the first network slice may include information on the number of registered users and/or information on the number of online users in the first network slice.
  • the information on the number of users of the service may include information on the number of registered users of the service and/or information on the number of online users.
  • the average service experience information of the business may include the average opinion score MOS of the business.
  • the service user satisfaction ratio information of the service may be, for example: The service user satisfaction of the service A means that the user ratio of the service A whose MOS is greater than 3 is 90%.
  • the slice management and control network element After receiving the response sent by the data analysis network element, the slice management and control network element sends second area information and/or second time information to the network device according to the first area information and/or first time information.
  • the second area information may be the same as the first area information, and the second time information may also be the same as the first time information.
  • the second area information may also be different from the first area information, and the second time information may also be different from the first time information.
  • the slice management network element may determine the second area information according to the first area information, and the format of the second area information and the first area information may be different.
  • the slice management and control network element may determine the second time information according to the first time information, and the format of the second time information and the first time information may be different, or the time indicated by the second time information may be included in the first area information. time.
  • the response further includes first service experience information of the first network slice corresponding to the first area information and/or the first time information, and the slice manages and controls the network element
  • the second area information and/or the second time information may be determined according to first service experience information.
  • the area indicated by the first area information is the first area
  • the area indicated by the second area information is the second area.
  • the second area is included in the first area. It can also be understood that the second area is a resource in the first area Areas with more serious problems, such as areas with scarce resources or areas with more redundant resources.
  • the slice management network element may also send slice quality information corresponding to the second area information and/or the second time information to the network device, where the slice quality information includes the following information At least one of: second service experience information corresponding to the first network slice of the second area information and/or second time information, and the second service experience information relative to the first network slice
  • the target service level agreement requires information about the degree of satisfaction of the information.
  • the second service experience information corresponds to the second area information and/or the second time information.
  • the satisfaction degree information includes unsatisfiability, satisfaction, or excess satisfaction.
  • satisfaction or excess satisfaction can be understood as:
  • the actual business average MOS 4, the actual business user satisfaction rate is 95%, which is over-satisfaction;
  • the satisfaction information is expressed as a percentage value, such as 80% of service experience information that meets the target service level agreement requirements information, or service 120% of the experience information meets the information required by the target service level agreement, and no specific restrictions are made here.
  • the network device may schedule resources for the first network slice according to the second area information and/or second time information.
  • the network equipment includes at least one of the following equipment: access network equipment, core network equipment, transmission network equipment, and network management network elements.
  • the access network device may be a (radio access network, RAN) device, such as a 5G base station (gNodeB, gNB).
  • RAN radio access network
  • gNodeB 5G base station
  • Core network equipment may include at least one of the following equipment: user plane function network element (user plane function (UPF), policy control network element (policy control function, PCF), session management function network element (session management function, SMF), access Network element for access and mobility management function (access and mobility management function, AMF).
  • user plane function network element user plane function (UPF)
  • policy control network element policy control function
  • PCF policy control network element
  • session management function network element session management function
  • SMF session management function
  • AMF access Network element for access and mobility management function
  • the transmission network equipment may include a backhaul link between the wireless access network and the core network, such as a router.
  • the network management network element may be OAM.
  • the access network device schedules access network resources for the first network slice according to the second area information, and the access network device uses the second time
  • the information is scheduling access network resources for the first network slice.
  • the core network device schedules core network resources for the first network slice according to the second area information, and the core network device uses the second time information as the The first network slice schedules core network resources.
  • the transmission network device schedules transmission network resources for the first network slice according to the second area information, and the transmission network device uses the second time information as the The first network slice schedules transmission network resources.
  • the network management network element controls the access network device or the core network device or the transmission network device to adjust the corresponding resources of the second area and/or the second time of the first network slice Dispatch volume.
  • the network device when scheduling resource for the first network slice, may perform resource scheduling according to the second area information and/or second time information, which may improve the accuracy and utilization rate of resource scheduling, and also improve the The performance of a network slice.
  • the request may further include third area information and/or third time information.
  • the request in the embodiment of the present application may be a subscription request message or a direct request message.
  • the direct request message requires NWDAF to return a response message immediately, and the subscription request message requires NWDAF to return a response message after the subscription reporting condition is met.
  • the third area indicated by the third area information includes the first area indicated by the first area information, and the third area information is used to request the data analysis network element to The first area information corresponding to the service experience requirement information.
  • the third time indicated by the third time information includes the first time indicated by the first time information, and the third time information is used to request the data analysis network element for the third time and The first time information corresponding to the service experience requirement information.
  • the third area includes the first area, and the first area includes the second area.
  • the third time includes the first time, and the first time includes the second time.
  • step 101 above: before the slice management network element sends a request to the data analysis network element, may further include:
  • the slice management and control network element obtains the third service experience information of the first network slice
  • the slice management network element determines the service experience requirement information of the first network slice, and the service experience requirement of the first network slice The information corresponds to the target service level agreement requirements.
  • the third service experience information corresponds to the fourth area information and/or the fourth time information of the first network slice.
  • the third service experience information is the fourth area information And/or service experience information of the first network slice corresponding to the fourth time information.
  • the fourth area may be the service area of the entire network slice or a part of the service area of the entire network slice; and the fourth time may be all the service time of the entire network slice or part of the service time of the entire network slice.
  • the first service experience information is corresponding to the first area information and/or first time information corresponding to the first network slice
  • the second service experience information is the second area information and/or second time corresponding to the first network slice
  • the information corresponds.
  • the fourth area includes the first area, and the first area includes the second area; the fourth time includes the first time, and the first time includes the second time.
  • whether the third service experience information corresponds to the target service level agreement requirement information can be determined in the following manner:
  • the slice management and control network element compares the third service experience information with the target service level agreement requirement information
  • the slice management network element determines that the third service experience information does not correspond to the target service level agreement requirement information.
  • the slice management network element determining the service experience requirement information of the first network slice may include :
  • the slice management network element determines the service experience requirement information of the first network slice corresponding to the unsatisfactory situation, which is the foregoing Describe the negative service experience request information.
  • the slice management network element determines the service experience requirement information of the first network slice corresponding to the excess satisfaction condition, which is the foregoing Describe the positive service experience request information.
  • the number of service users of the first network slice may also be adjusted, and the adjustment method may be:
  • the slice management and control network element reduces the number of service users of the first network slice
  • the slice management network element increases the number of service users of the first network slice.
  • both the first area and the second area can be attributed to the problem area, and both the first time information and the second time information can be attributed to the problem time.
  • the network domain where the cause of the problem area and/or problem time is located may be determined first, and then the network device is further determined. Therefore, the method of resource scheduling of the network slice also includes the following two possible implementations , Respectively:
  • the method for resource scheduling of network slices may further include:
  • the first network domain may be an access network domain, a core network domain, or a transmission network domain.
  • the problem area includes a first area or a second area
  • the problem time includes a first time or a second time
  • the slice management network element may learn from the network management network element that the cause of the problem area and/or problem time lies in the first network domain.
  • the slice management and control network element When the slice management and control network element is a slice management and control network element (such as NSSF) located on the operator's network control plane, the slice management and control network element can interact with the network management network element (such as OAM) located on the operator's network management plane, so as to know the first A network domain is the cause of the problem area and/or problem time; when the slice management and control network element is a slice management and control network element (such as NSMF) located on the operator's network management plane, the slice management and control network element can be connected to the operator's network Network management network elements (such as MDAS) of the management plane interact to learn that the first network domain is the cause of the problem area and/or problem time.
  • the network management network element such as OAM
  • the slice management and control network element when the slice management and control network element is a slice management and control network element (such as NSMF) located on the operator's network management plane, the slice management and control network element can be connected to the operator's network Network management network elements (
  • the slice control network element determines the cause of the problem area and/or the problem time by itself in the first network domain where the network device is located.
  • the slice management network element determines the network device from the first network domain and sends the network device to the network
  • the device sends the problem area/problem time described in the embodiment of FIG. 2.
  • the network device may refer to all network devices in the first network domain, or may be part of network devices in the first network domain, for example, only networks in the first network domain related to the problem area/problem time equipment.
  • the slice management network element may also obtain from the network management network The element obtains first credibility information, and the first credibility information is used to indicate that the cause of the problem area and/or problem time is the credibility of the first network domain; the slice control network element according to the A credibility information determines the network device.
  • first credibility information For the specific expression form of the first credibility information, reference may be made to the expression form of the credibility of the user quantity limitation information in the embodiment of FIG. 5, which will not be repeated here.
  • the specific method for the slice management and control network element to determine the network device according to the first credibility information is: when the first credibility information is higher than a preset credibility value (such as the first credibility (Degree information value is greater than 90%), the slice management network element determines the network device from the first network domain; conversely, when the first credibility information is lower than the preset credibility value (such as A credibility information value is less than 60%), the slice control network element will not determine the network device from the first network domain, in other words, the network where the subsequent slice control network element sends the problem area/problem time to it The device will not come from the first network domain.
  • a preset credibility value such as the first credibility (Degree information value is greater than 90%
  • the slice management network element determines the network device from the first network domain
  • the preset credibility value such as A credibility information value is less than 60%
  • the method for resource scheduling of network slices may further include:
  • the reason why the slice management and control network element determines that the third service experience information does not correspond to the target service level agreement requirement information is that the second network domain may include: the slice management and control network The reason that the element learns from the network management network element that the third service experience information does not correspond to the target service level agreement requirement information lies in the second network domain.
  • the slice management network element When the slice management network element is a slice management network element (such as NSSF) located on the operator's network control plane, the slice management network element can interact with the network management network element (such as OAM) located on the operator's network management plane, so as to know The second network domain is the reason why the third service experience information does not correspond to the target service level agreement requirement information; when the slice management and control network element is a slice management and control network element (such as NSMF) located on the operator's network management plane At this time, the slice management and control network element can interact with a network management network element (such as MDAS) located on the operator's network management plane to learn that the second network domain is causing the third service experience information and the target service level agreement requirements The reason why the information does not correspond.
  • a network management network element such as MDAS
  • the slice management network element may also determine that the reason why the third service experience information does not correspond to the target service level agreement requirement information lies in the second network domain.
  • the reason why the third service experience information does not correspond to the target service level agreement requirement information is obtained by any design is that after the second network domain, the slice management network element determines the network device from the second network domain And send the problem area/problem described in the embodiment of FIG. 2 to the network device.
  • the network device may refer to all network devices in the second network domain, or may be part of network devices in the second network domain, for example, only networks in the second network domain related to the problem area/problem time equipment.
  • the slice management network element may also obtain second credibility information from the network management network element, where the second credibility information is used to indicate that the third service experience information does not correspond to the target service level agreement requirement information The reason is that the credibility of the second network domain; the slice management network element determines the network device according to the second credibility information.
  • the second credibility information For the specific expression form of the second credibility information, reference may be made to the expression form of the credibility of the user quantity limitation information in the embodiment of FIG. 5, which will not be repeated here.
  • the specific method for the slice management and control network element to determine the network device according to the second credibility information is: when the second credibility information is higher than a preset credibility value (such as the second credibility (Degree information value is greater than 90%), the slice management network element determines the network device from the second network domain; conversely, when the second credibility information is lower than the preset credibility value (such as If the value of the second credibility information is less than 60%), the slice control network element will not determine the network device from the second network domain, in other words, the network to which the subsequent slice control network element sends the problem area/problem time The device will not come from the second network domain.
  • a preset credibility value such as the second credibility (Degree information value is greater than 90%
  • another embodiment of the method for resource scheduling of a network slice provided by an embodiment of the present application may include:
  • the network management network element determines resource configuration information of the first network slice, where the resource configuration information includes maximum resource configuration information and/or guaranteed resource configuration information.
  • the maximum resource configuration information is used to indicate a maximum usable resource of the first network slice
  • the guaranteed resource configuration information is used to indicate a guaranteed usable resource of the first network slice.
  • the network management network element refers to a device that has deployment network resources and has management and maintenance functions for network operation.
  • the network management network element may be OAM or NSSF.
  • the resource configuration information of the first network slice may be determined according to target service level agreement requirement information of the first network slice.
  • the target service level agreement requirement information may be the same as the target service level agreement requirement information described in the embodiment corresponding to FIG. 2 and will not be repeated here.
  • the network management network element sends resource configuration information of the first network slice to the network device.
  • the network device may include at least one of the following devices: an access network device, a core network device, and a transmission network device. Among them, the meanings of the access network device, the core network device and the transmission network device are shown in step 105, and will not be repeated here.
  • the maximum resource configuration information is maximum air interface resource configuration information and/or guaranteed resource configuration information is guaranteed air interface resource configuration information.
  • the resource configuration information may not correspond to the entire first network slice, may be resource configuration information corresponding to one or more areas of the first network slice, or may correspond to Resource configuration information for a period or a period of time.
  • the maximum resource configuration information and/or guaranteed resource configuration information is the maximum resource configuration information and/or guaranteed resource configuration information corresponding to the first time; or, the maximum resource configuration information and/or guaranteed resource configuration The information is maximum resource configuration information and/or guaranteed resource configuration information corresponding to the first area.
  • the network device After receiving the resource configuration information of the first network slice sent by the network management network element, the network device schedules resources for the first network slice according to the resource configuration information of the first network slice.
  • the network device When scheduling resources for the first network slice, the network device will first consider the demand for resources. If the demand for resources does not exceed the resources guaranteed by the first network slice indicated by the guaranteed resource configuration information, it will be the first A network slice schedules resources of the required size. Within the range of resources that can be used by the first network slice, the network device schedules the first network slice. If the demand exceeds the resources guaranteed to be used by the first network slice, but does not exceed the resources that can be used by the first network slice indicated by the maximum resource configuration information, at least the resources guaranteed to be used by the first network slice will be scheduled according to the actual situation The amount of resources.
  • the maximum resource that the first network slice can use is 20 units, and the first network slice guarantees that the resource that can be used is 11 units. If the demand is 8 units, the network equipment will dispatch 8 units of resources to For the first network slice, if the demand is 15 units, when the amount of resources is sufficient, 15 units will be scheduled for the first network slice. If the amount of resources is insufficient, at least 11 units of resources will also be scheduled Slice the first network.
  • the network device may schedule resources for a certain network slice according to the guaranteed resource range under the maximum available resource range according to the instructions of the network management network element.
  • This method enables the network device to flexibly schedule resources for the network slice according to the actual amount of resources required by the network slice, and promises to be able to schedule resources for the network slice to ensure the usable resource range when the network slice needs it.
  • network slicing may also allow the use of resources with the maximum available resource range. This method not only ensures that the network slice has resources available, but also improves the flexibility of the resources.
  • the resources guaranteed by the first network slice are allowed to be used by the second network slice. Especially when the first network slice does not need to use too many resources, it is guaranteed that the remaining resources within the usable resource range are allowed to be used by other network slices, as long as it can be guaranteed that the first network slice can be sliced for the first network slice when needed It is sufficient to schedule resources that can be used in a range of resources. This method improves the flexibility of resource utilization.
  • the network device may use the maximum resource configuration information corresponding to the first time And/or guaranteed resource configuration information for the first network slice to schedule resources at the first time.
  • the first time may be included in the maximum resource configuration information and/or guaranteed resource configuration information, or may be pre-negotiated or included in the maximum resource configuration information and/or guaranteed resource configuration information, not It needs to be included in the maximum resource configuration information and/or guaranteed resource configuration information.
  • the network device may use the maximum resource configuration information corresponding to the first area And/or guaranteed resource configuration information to schedule resources for the first network slice in the first area.
  • the first area may be included in the maximum resource configuration information and/or guaranteed resource configuration information, or may be pre-negotiated or included in the maximum resource configuration information and/or guaranteed resource configuration information, not It needs to be included in the maximum resource configuration information and/or guaranteed resource configuration information.
  • resources may be preferentially scheduled for a certain network slice according to the guaranteed resource range.
  • This method enables the network device to flexibly schedule resources for the network slice according to the actual amount of resources required by the network slice, and promises to be able to schedule resources for the network slice to ensure the usable resource range when the network slice needs it.
  • network slicing may also allow the use of resources with the maximum available resource range. This method not only ensures that the network slice has resources available, but also improves the flexibility of the resources.
  • FIG. 4 As shown in FIG. 4, on the basis of the embodiment corresponding to FIG. 3 above, another embodiment of the method for resource scheduling of a network slice provided by an embodiment of the present application may include:
  • the network management network element obtains information about resources scheduled by the network device for the first network slice.
  • the resource information may include information of resources corresponding to the area or corresponding time.
  • the information of the resource may include information of the resource corresponding to the second area of the first network slice, and/or, the information of the resource may include information corresponding to the second time of the first network slice Resource information.
  • the first area may be the same as or different from the second area, and the second time may be the same as or different from the first time.
  • the network management network element obtains slice quality information of the first network slice from the slice management network element or data analysis device.
  • the slice quality information includes service experience information of the first network slice and/or satisfaction degree information of the service experience information of the first network slice with respect to the target service level agreement requirements.
  • the service experience information of the first network slice may be the same as the first service experience information, the second service experience information, or the third service experience information described in the embodiment corresponding to FIG. 2 and will not be repeated here.
  • Satisfaction information may include unsatisfied, satisfied, or over-satisfied, or other manifestations, and is also the same as the satisfaction information described in the embodiment corresponding to FIG. 2, and will not be repeated here.
  • the slice quality information corresponding to the first network slice may include service experience information corresponding to the second area of the first network slice and/or Or satisfaction degree information of the service experience information corresponding to the second area relative to the target service level agreement.
  • the second area is an area that cannot meet or exceed the requirements of the target service level agreement.
  • the slice quality information corresponding to the first network slice includes service experience information corresponding to the second time of the first network slice and/or the second time The satisfaction degree information of the corresponding service experience information relative to the target service level agreement.
  • the second time is a time that cannot meet or exceed the requirements of the target service level agreement.
  • the network management network element updates the resource configuration information of the first network slice according to the information of the resource scheduled by the network device for the first network slice and the slice quality information.
  • the network management network element updates the first network slice according to the information of the resource corresponding to the second area and the service experience information corresponding to the second area Resource configuration information.
  • the network management network element updates the first network slice according to the resource information corresponding to the second time and the service experience information corresponding to the second time Resource configuration information.
  • the network management network element If the resource information is the information of the resource corresponding to the second area and the second time, the network management network element according to the information of the resource corresponding to the second area and the service experience information corresponding to the second area, and the second Updating the resource configuration information of the first network slice according to the resource information corresponding to the time and the service experience information corresponding to the second time.
  • the network management network element updates the maximum resource configuration information and/or guaranteed resource configuration information so that the updated maximum resource The configuration information is not less than the resources scheduled by the network device for the first network slice.
  • the network management network element sends the updated resource configuration information to the network device.
  • the updated resource configuration information includes updated maximum resource configuration information and/or updated guaranteed resource configuration information.
  • the network device schedules resources for the first network slice according to the updated resource configuration information.
  • the network device can schedule resources for the first network slice according to the updated maximum available resource range according to the instructions of the network management network element according to the updated guaranteed useable resource range, thereby improving resource flexibility.
  • the network management network element can update the resource configuration information of the first network slice in time, so that the network device can adjust the resources scheduled by the first network slice in time, thereby improving the accuracy of resource scheduling and the first network slice Performance.
  • the network device may also adjust to the resource scheduled by the first network slice. In this case, it may be:
  • the network device receives the slice quality information corresponding to the first network slice sent by the slice management network element, and the slice quality information includes service experience information of the first network slice and/or service experience information of the first network slice Information about the degree of satisfaction relative to the requirements of the target service level agreement;
  • the network device adjusts the resources scheduled for the first network slice according to the slice quality information.
  • the slice quality information corresponding to the first network slice may include service experience information corresponding to the second area of the first network slice and/or service experience information corresponding to the second area relative to the target service level Information on the degree of satisfaction required by the agreement.
  • the slice quality information corresponding to the first network slice may include service experience information corresponding to the second time of the first network slice and/or service experience information corresponding to the second time relative to the target service level agreement requirements Satisfaction information.
  • the slice quality information corresponding to the first network slice may include service experience information corresponding to the second area and the second time of the first network slice and/or relative service experience information corresponding to the second area and the second time Information about the degree of satisfaction required by the target service level agreement.
  • the second area is an area that cannot meet or exceed the requirements of the target service level agreement.
  • the second time is a time that cannot meet or exceed the requirements of the target service level agreement.
  • the network device adjusting the resources scheduled for the first network slice according to the slice quality information may include: if the service experience information of the first network slice fails to meet the target service level agreement requirements, the network device increases Resources scheduled for the first network slice; if the service experience information of the first network slice exceeds the target service level agreement requirements, the network device reduces resources scheduled for the first network slice.
  • the above solution whether the network management network element updates the resource configuration information of the first network slice in time, or the network device adjusts the resource scheduled by the first network slice according to the slice quality information corresponding to the first network slice, can improve the accuracy of resource scheduling Performance and performance of the first network slice.
  • the former may be more accurate, because the network management network element obtains the updated resource configuration information after analyzing more dimensions and a larger amount of data, and the accuracy is higher; the latter is more
  • the network device may consider adjusting the resources scheduled for the first network slice directly according to the slice quality information corresponding to the first network slice. If the two are used in combination, better results can be achieved.
  • FIG. 3 and FIG. 4 above introduce the resource scheduling solution of the network slice under the indication of the maximum resource configuration information and/or guaranteed resource configuration information.
  • the content related to the resource scheduling of the network slice also has the control of the number of users.
  • the method of controlling the number of users in the embodiment of the present application will be described below with reference to FIG. 5.
  • an embodiment of the method for controlling the number of users provided by the embodiments of the present application may include:
  • the network management network element determines the user quantity limitation information and indication information of the target network slice.
  • the restriction information of the number of users of the target network slice refers to the restriction of the number of access users, which may include information on the number of online users or information on the number of registered users.
  • the user number restriction information generally refers to the maximum user number information, that is, user capacity information.
  • the indication information is used to indicate the status information of the target network slice or the credibility of the user quantity limitation information.
  • the state information includes a test state or a stable state.
  • the test state means that the target network slice is a new slice or is in the testing stage.
  • the service level agreement is officially signed between the operator and the tenant for the target network slice;
  • the stable state means that the target network slice is stable At this stage, in other words, a service level agreement has been formally signed between the operator and the tenant on the target network slice.
  • the embodiment of the present application does not limit the specific expression form indicating the test state or the stable state, for example, it may be a binary enumeration value, 0 represents the test state, and 1 represents the stable state. You can also use F to indicate the test state and T to indicate the stable state. Of course, you can also use other forms to represent the test state or stable state.
  • Credibility refers to the degree of believability.
  • the embodiment of the present application does not limit the specific manifestation of untrustworthiness.
  • the trustworthiness may be a floating point number in the range [0,1].
  • a larger floating point value indicates a higher degree of reliability;
  • Reliability can be a percentage value between 0-100%, the higher the ratio, the higher the degree of reliability;
  • the credibility information can also be a predefined set (such as ⁇ A, B, C, D ⁇ ), where different enumeration values correspond to different degrees of reliability (eg, A>B>C>D).
  • the network management network element refers to a device that has deployment network resources and has management and maintenance functions for the operation of the network, such as OAM.
  • the embodiment of the present application does not limit the manner in which the network management network element determines the information about the number of users of the target network slice, and one of the methods may be:
  • the network management network element obtains service level agreement requirement information of the target network slice
  • the network management network element determines, according to the service level agreement requirement information, the user quantity limitation information of the target network slice.
  • the network management network element can obtain the service level agreement requirement information of the target network slice from the tenant.
  • the service level agreement requirement information basically has the same meaning as the service level agreement requirement information described in the foregoing embodiments, and will not be repeated here. Repeat in detail.
  • the network management network element sends to the slice management network element the information about the number of users of the target network slice and the indication information.
  • the slice management and control network element refers to a network element with user access, resource deployment, and function execution that manages and controls network slices. For example, the slice management and control network element selects a function network element (NSSF) for network slices. In order to achieve more fine-grained control over the number of users, the network management network element sends to the slice management network element the area information of the target network slice and the user quantity limit information corresponding to the area information.
  • NSF function network element
  • the area information and the user quantity limitation information corresponding to the area information are used by the slice management network element for the area indicated by the area information, within the range indicated by the user quantity limitation information corresponding to the area information Internally control the number of users served by the target network slice.
  • the network management network element sends the time information of the target network slice and the user quantity limitation information corresponding to the time information to the slice management network element.
  • the time information and the user quantity limitation information corresponding to the time information are used to control the target network within the range indicated by the user quantity limitation information corresponding to the time information for the time indicated by the time information The number of users served by slicing.
  • the slice management and control network element After the slice management and control network element receives the user quantity limitation information of the target network slice sent by the network management network element and the indication information, the number of users served by the target network slice is controlled according to the indication information and the user quantity limitation information .
  • the slice management and control network element controls the service of the target network slice according to the control method corresponding to the state information according to the user quantity limitation information The number of users.
  • the control mode is a step control mode. That is to say, the slicing control network element may access a number of users limited by the user quantity limitation information to the target network slice in a ladder manner or exclude users who have been served by the target network slice.
  • the control mode is a one-time control mode. That is to say, according to the stable state of the target network slice, the slicing control network element accesses the target network slice or the number of users restricted by the user number restriction information at a time to the target network slice Eliminate users who provide services.
  • the slice management and control network element controls the target network according to the control mode corresponding to the credibility according to the user quantity limitation information The number of users served by slicing.
  • the control method is a step control method. That is to say, the slicing control network element accesses the target network slice by the number of users limited by the user quantity limitation information in a ladder manner or excludes users who have been served by the target network slice.
  • the control mode is a one-time control mode. That is, the slicing control network element accesses the number of users limited by the number of users restriction information to the target network slice at a time or excludes users who have been served by the target network slice.
  • the credibility meets the credibility requirements. If the credibility is a specific value, you can determine whether the credibility is by setting the credibility threshold Greater than the credibility threshold. If the credibility is a preset set of enumeration values, it can be determined whether the credibility is the corresponding enumeration value to meet the credibility requirements. Moreover, different credibility corresponds to different control methods, which is not limited to the above-mentioned ladder method or one-time method, and there may be other corresponding control methods.
  • the limitation information of the number of users of the target network slice may be service level agreement requirement information of the target network slice received by the slice management and control network element from the network management network element, and the service level agreement requirement information includes Information about the number of users of the target network slice is limited.
  • the service level agreement requirement information of the target network slice sent by the network management network element to the slice control network element does not contain the user quantity limit information, then the user quantity limit information can be sent separately, and can be related to the target network slice service level agreement requirement Information is sent side by side.
  • the slice management and control network element When the user quantity limitation information is the user quantity limitation information corresponding to a certain area, the slice management and control network element, according to the indication information and the user quantity limitation information corresponding to the area information, for the area indicated by the area information Control the number of users served by the target network slice.
  • the slice management and control network element When the user quantity limitation information is the user quantity limitation information corresponding to a certain time, the slice management and control network element, according to the indication information and the user quantity limitation information corresponding to the time information, for the time indicated by the time information Control the number of users served by the target network slice.
  • FIG. 6 is a schematic diagram of an embodiment of a network architecture in a network slicing scenario. As shown in FIG.
  • the network elements related to the foregoing embodiments include third-party network elements, for example, application function network elements (Application Function, AF), access network equipment, core network equipment (for example: AMF, PCF, etc.) for allocating user plane or control plane resources, slice management and control network elements (for example: NSSF), data analysis network elements (for example: NWDAF) and Network management network element (for example: OAM).
  • application function network elements Application Function, AF
  • access network equipment for example: AMF, PCF, etc.
  • core network equipment for example: AMF, PCF, etc.
  • slice management and control network elements for example: NSSF
  • data analysis network elements for example: NWDAF
  • Network management network element for example: OAM
  • the slice management network element (for example: NSSF) and the data analysis network element (for example: NWDAF) actually belong to the core network equipment.
  • the network management network element creates a network slice.
  • the network management network element obtains the service level agreement (SLA) requirement information of the tenant for the network slice.
  • SLA service level agreement
  • the network management network element creates the network slice according to the SLA requirement information.
  • creating the network slice specifically refers to that the network management network element sets resource configuration information for the network slice.
  • the network slice here is not limited to a newly created network slice, but may also be an existing network slice. If it is an existing network slice, there is no need to set resource configuration information.
  • the resource configuration information may be the maximum resource configuration information and/or the guaranteed resource configuration information described in the embodiment corresponding to FIG. 3 above.
  • the resource configuration information is used to indicate the network resources that can be scheduled for the network slice.
  • the network resources may include access network resources or core network resources, and may also include transmission network resources.
  • the access network resources corresponding to one network slice may include: a guaranteeable air interface resource or a maximum air interface resource corresponding to the network slice.
  • the configuration of the access network resource for the network slice by the network management network element specifically refers to the configuration of a guaranteed air interface resource or the largest air interface resource for the network slice.
  • the air interface resource here may be actual physical resources, such as physical resource blocks (PRB), processor resources and storage resources of the access network device, that is, the network management network element instructs the access network device to schedule Physical resources.
  • PRB physical resource blocks
  • Air interface resources can also be parameters that reflect air interface performance, such as the uplink/downlink data packet loss rate of the network access device, the maximum/average radio resource control (RRC) number of connections, and the average delay of the data unit (DU) And so on, that is, the network management network element uses these performance parameters to indicate the physical resources to be scheduled by the access network device.
  • RRC radio resource control
  • DU average delay of the data unit
  • the core network resources corresponding to one network slice may include: a guaranteeable core network resource corresponding to the network slice or the largest core network resource.
  • the configuration of core network resources for the network slice by the network management network element specifically refers to configuring a guaranteed core resource or a maximum core network resource for the network slice.
  • the core network resources are explained in the same way as the access network resources above. They can be specific core network physical resources, such as UPF storage resources, AMF CPU resources, or parameters reflecting core network performance, such as the N3 interface.
  • General wireless packet service channel protocol general packet radio service Tuningelling Protocol, GTP
  • GTP General wireless packet radio service Tuningelling Protocol
  • the network management network element configuring the access network resource for the network slice specifically refers to that the network management network element sends the access network resource configuration information corresponding to the network slice to the access network device, and the access network The device schedules the corresponding access network resources for the network slice according to the resource configuration information of the access network.
  • the access network resource configuration information includes guaranteed air interface resource configuration information or maximum air interface resource configuration information, and the access network device may be a base station or an access network domain management device; in addition, the network management network element configures core network resources Specifically, it means that the network management network element sends core network resource configuration information to the core network device, and the core network device schedules the corresponding core network resource according to the core network resource configuration information.
  • the core network resource configuration information includes guaranteed core network resource configuration information or the largest core network resource configuration information, and the core network device can specifically allocate user plane or control plane resources to the core network device (such as AMF, SMF, UPF, etc.) ) Or for core network domain management equipment;
  • the specific representation of the resource allocation amount issued in the resource configuration information is not limited, and it can be a ratio of total resources, such as configuring 30% of the total air interface resources for a slice, 40% of the total core network resources, or Specific resource values such as the number of PRBs and the size of the UPF storage space.
  • the network management network element can also configure network resources for network slices by area information.
  • the network management network element configures different access network resources or core network resources for different areas of the network slice, such as different tracking areas (TA), TA lists, different cells (cells), cell lists, etc. Or transmission network resources.
  • TA tracking areas
  • TA lists different cells
  • cell lists cell lists
  • transmission network resources This application does not limit the definition and form of regional information.
  • the area information here is equivalent to the first area information of step 202 in the embodiment of FIG. 3.
  • the network management element may initially allocate network resources evenly to different areas of the network slice, because in the initial state, the network management does not have or has little service experience information about the network slice, It does not know how to configure different network resources for different areas.
  • the network management network element can also allocate network resources for network slices by time information. For example, with different time information, such as day/night, free/busy hours, 02:00-04:00, Monday-Friday, etc., the network management network element configures different access network resources or core network resources for the network slice .
  • time information such as day/night, free/busy hours, 02:00-04:00, Monday-Friday, etc.
  • the network management network element configures different access network resources or core network resources for the network slice .
  • This application does not limit the definition and form of time information.
  • the area information here is equivalent to the first time information of step 202 in the embodiment of FIG. 3.
  • the network management element may initially allocate network resources to the network slice at different times on average, because in the initial state, the network management does not have or has little service experience information about the network slice. It does not know how to configure different network resources for different times.
  • the network management network element sends the initial user number information and indication information corresponding to the network slice to the slice management network element.
  • the information of the initial number of users of the network slice is equal to the restriction information of the number of users in step 401 of the embodiment of FIG. 5, which may include the information of the initial registered users or the number of online users of the network slice.
  • the user number information is used to guide the slice management and control network element to perform the user number access control operation on the network slice.
  • the slice management and control network element allows or denies the user's request to register into the network slice according to the information about the number of registered users sent by the network management network element, or removes the registered users from the network slice to control the network slice network Number of registered users.
  • the slice management and control network element allows or denies the user to enter the online state according to the information about the number of online users sent by the network management network element, or changes the already online user to an offline or idle state to control the online user of the network slice network ⁇ Number effect.
  • the user number information generally refers to the maximum user number information, that is, user capacity information.
  • the initial user number information may include initial maximum registered user number information or maximum online user number information of the network slice.
  • the network management network element may also inform the slice management network element of the SLA requirement information corresponding to the network slice.
  • the SLA requirement information here can be the trial operation stage, that is, the SLA requirement information in the test state. After the test is completed, a stable state SLA requirement information can be determined.
  • the network management network element can send the user number information inside the SLA request information to the slice control network element, or, instead of using the user number information as part of the SLA request information, the two can be sent separately Slicing control network element.
  • the network management network element may also send user number information or SLA requirements to the slice management and control network element in different regions. That is to say, the network management network element informs the slice management network element of different numbers of users or SLA requirements corresponding to different areas. For example, TA1 corresponds to a maximum of 1 million registered users, SLA requires 1, TA2 corresponds to a maximum of 2 million registered users, and SLA requires 2.
  • the area here is equivalent to the area information in step 402.
  • All area information in the embodiments of the present application may be area information defined in a 3GPP communication network, which may be referred to as communication network area information), such as serving cell A or registration area B, and the area information may also be defined in a non-3GPP communication network
  • Regional information for example, the location information is a specific geographic location range (for example, latitude and longitude or global positioning system (GPS) location information, which may be referred to as geographic area information).
  • GPS global positioning system
  • the number of users or SLA requirements can also be sent in time. That is to say, the network management network element informs the slice management network element of different user number information or SLA requirements corresponding to different times. For example, time period 1 corresponds to a maximum of 1 million registered users, SLA requires 1, and time period 2 corresponds to a maximum of 2 million registered users, and SLA requires 2.
  • the time domain here is equivalent to the time information in step 402.
  • All time information in the embodiment may be absolute time, for example, from 00:00 on January 1, 2017 to 24:00 on January 30, 2017, or from Monday to Friday; it may also be relative time information , For example, within one month after sending the user number information or SLA request information.
  • the granularity of the time information may be a granularity of hours, or a granularity of minutes or days, which is not limited in the embodiments of the present application.
  • the indication information may be first indication information, where the first indication information is used to indicate the credibility information of the number of users or SLA requirement information sent by the network management network element, where the credibility information It refers to the degree of confidence/confidence of the network management network element for the user number information or SLA requirement information, which is a measure of the reliability of the user number information or SLA requirement information.
  • This application does not limit the specific expression of credibility information, as long as it can reflect the credibility of the user number information or SLA requirements information.
  • the credibility information can be a floating-point number in the range [0,1].
  • a larger floating-point value indicates a higher degree of reliability; for another example, the credibility information can be a percentage between 0-100% The ratio value, the higher the ratio, the higher the degree of reliability; for another example, the credibility information can also be an enumerated value in a predefined set (such as ⁇ A, B, C, D ⁇ ), where different The degree of reliability corresponding to the value is different (for example, A>B>C>D).
  • the credibility value corresponding to this state set by the network management network element is lower, for example, the credibility value is 60%, which is Because the network management network element does not have or has little service experience information about the network slice at this time, that is to say, the number of users generated by the network management network element or the basis information required by the SLA is very small, so the credibility at this time is more low.
  • the indication information may also be second indication information, where the second indication information is used to indicate that the network slice is a new network slice or the network slice is in a test state or is in a stable state.
  • the new network slicing or testing state is relatively stable.
  • the former operator and the network tenant have not officially signed the SLA, and the network is in a state of continuous adjustment; the latter, the operator and the network tenant have officially signed the SLA.
  • the network is in a relatively stable state and does not frequently perform resource adjustments.
  • the present application does not limit the specific expression form indicating the test state or the stable state, for example, it may be a binary enumeration value, 0 represents the test state, and 1 represents the stable state. Or, F represents the test state and T represents the steady state.
  • the test state or stable state can also be expressed in other forms.
  • the slice management and control network element performs user number control on the network slice according to the initial user number information and the instruction information sent by the network management network element.
  • the access control of the number of users specifically refers to controlling the number of registered users or the number of online users in the network slice. For details, see step 502.
  • the slice control network element may allow users to access the network gradually or in stages Network slicing. For example, if the network management network element instructs the slice control network element that the maximum number of registered users of the network slice is 10 million, then the slice management network element can only allow 1 million users to access the network slice at a time, where the user access is allowed gradually or in stages.
  • the purpose of the network slicing is to avoid the simultaneous access to a large number of users at the same time, which leads to a significant decrease in the service experience of the network slicing, and even affects the service experience of other network slicing which is already in a stable stage.
  • the slice control network element determines that the credibility corresponding to the user number information or SLA requirement information is low, then the slice control network element can also eliminate users or gradually or in stages.
  • the purpose of transferring users to other network slices, where the number of users of the network slice is reduced gradually or in stages, is to avoid affecting the service experience of a large number of users in the network slice at the same time, thereby avoiding affecting the service experience of the network slice.
  • Increasing or decreasing the number of users in the network slice step by step or step by step corresponds to the ladder control method in the embodiment of FIG. 5.
  • the slice management and control network element may allow the user to access the network slice gradually or in stages. For example, if the network management network element initially indicates that the maximum number of registered users of the network slice of the slice management network element is 10 million, then the slice management network element may only allow 1 million users to access the network slice at a time. Increasing or decreasing the number of users in the network slice step by step or step by step corresponds to the ladder control method in the embodiment of FIG. 5.
  • the slice management and control network element may also perform user number access control on the network slice according to the area information. For example, the network management network element informs the slice management network element that the maximum number of registered users corresponding to the TA1 of the network slice is 1 million, and the maximum number of registered users corresponding to TA2 is 2 million. The slice management network element can only allow 1 million users to register with the network slice. TA1, 2 million users registered in TA2.
  • the slice management and control network element may also perform access control on the number of users of the network slice according to the time information. For example, if the network management NE informs the slice management NE that period 1 (such as weekends) corresponds to a maximum of 1 million registered users, and period 2 (such as weekdays) corresponds to a maximum of 2 million registered users, then slice management NEs have the most in period 1 Only 1 million users are allowed to register on the network slice, and in period 2 only up to 2 million users are allowed to register on the network slice.
  • period 1 such as weekends
  • period 2 such as weekdays
  • the slice management network element sends a first request to the data analysis network element, where the first request is used to request service experience information corresponding to the network slice.
  • the service experience information corresponding to the newly created network slice in 501 may be requested here, or service experience information of other network slices.
  • the other network slices may be network slices that are already in a stable state.
  • service experience information of multiple network slices can also be requested together, but whether it is requesting service experience information of several network slices, the subsequent processing procedures are the same for the problematic network slices.
  • the service experience information corresponding to each network slice includes: experience information of network slice granularity and experience information of service granularity in network slice.
  • the network slice granularity experience information refers to information that can reflect the overall service experience of a network slice, which may include: information about the number of users of the network slice (such as network slice registration or online users), and end-to-end delay of the network slice Information, load information of network slices, etc.
  • the service granularity experience information refers to the information that can reflect the service experience of a certain service in the network slice, including the quality information of the service's business granularity (that is, the information reflecting the overall service experience of the service), and the quality of the service's user granularity Information (that is, information reflecting the individual service experience of each user performing the service).
  • the first request contains the network slice identification information of the requested network slice, where the network slice identification information is used to uniquely identify a network slice, and the network slice identification information may specifically be network slice selection support information (network slice selection support information, NSSAI), one or more of S-NSSAI, NSI and NSSI.
  • network slice selection support information network slice selection support information, NSSAI
  • S-NSSAI S-NSSAI
  • NSI NSSI
  • the first request may also include service identification information, that is, the first request is specifically used to request service experience information corresponding to a network slice corresponding to the service identification information, in other words, service experience information corresponding to a requested network slice
  • service identification information that is, the first request is specifically used to request service experience information corresponding to a network slice corresponding to the service identification information, in other words, service experience information corresponding to a requested network slice
  • the quality information of the business will be included.
  • the service experience information corresponding to the network slice can be displayed in the form of a table, as shown in Table 1, of course, Table 1 only reflects one form of data structure expression, and may be other data structures.
  • some cells are optional and not necessary.
  • area information When there is no area information, it indicates that the slice experience information is network-wide experience information and is not limited to a certain area.
  • the network slice 1 in Table 1 below may refer to the newly created network slice in 501, or may refer to any existing network slice.
  • the first request includes area information, that is, the first request is specifically used to request service experience information of a network slice corresponding to the area information.
  • the first request includes time information, that is, the first request is specifically used to request service experience information of a network slice corresponding to the time information.
  • the service experience information of the requested network slice in this step is equivalent to the third service experience information described in step 105 of the embodiment of FIG. 2.
  • the network management network element sends a second request to the data analysis network element.
  • the second request is used to request service experience information corresponding to the network slice.
  • This step 505 can be understood according to step 504, except that the execution subject is changed from the slice management network element to the network management network element.
  • the data analysis network element obtains service experience information of the network slice.
  • the data analysis network element may obtain the service experience information of the network slice according to the request of the slice control network element or the network management network element, or may obtain the service experience information of the network slice by itself.
  • the network slice here may be the first network slice, the second network slice, or the third network slice, or other network slices, or multiple network slices.
  • Step 506 may also be described as the data analysis network element acquiring service experience information of the Nth network slice, where N is a specific value, or may be a set of multiple values.
  • Data analysis network elements can obtain the service experience information of network slices in the following ways:
  • the data analysis network element directly obtains service experience information related to the network slice from the AF corresponding to the network slice.
  • This method may be based on the premise that the information provided by the AF is credible, and the AF can already provide some service experience information of the network slice, such as the number of users in the network slice, end-to-end delay, average service MOS, MOS distribution, single User's MOS, etc.
  • the data analysis network element collects these experience data and performs simple statistical calculation to obtain the experience information of the network slice requested by the slice control network element or the network management network element.
  • AF can provide data analysis network elements with user experience data of a single user performing service A, such as the MOS points of a single user performing service A, and the delay of a single user's service A, the data analysis network element is based on all single user's User experience can obtain the average MOS value of service A, the average end-to-end delay of service A, and can know the distribution of user experience of the service, etc. These data will be sent as service experience information to the slice management network element or network management network element .
  • the data analysis network element obtains the relevant experience information of the network slice by performing model training on the services in the network slice.
  • this method may include the following steps:
  • Step A The data analysis network element can separately collect historical service data of a service from the AF network element, and obtain the service experience flow (Quality ofof) from the network network element (eg, RAN, AMF network element, SMF network element, UPF network element) Service, flow, QoS, and flow) historical network data.
  • the network network element eg, RAN, AMF network element, SMF network element, UPF network element
  • Service flow, QoS, and flow
  • the service data involved in this application may be: bandwidth, delay, packet loss rate, jitter buffer, transmission control protocol (Transmission Control Protocol, TCP) congestion window, TCP receive window, media encoding type, media encoding Data such as rate and other parameters.
  • transmission control protocol Transmission Control Protocol, TCP
  • TCP Transmission Control Protocol
  • the network data of the QoS flow level involved in this application can be any of the following parameters: bandwidth, delay, packet loss rate, according to the signal received power (reference signal reception power, RSRP), according to the signal reception quality (reference signal reception quality , RSRQ), block error rate (BLER) and channel quality indicator (CQI), network slice identification information, data network name (DNN) and other parameter data.
  • RSRP reference signal reception power
  • RSRQ reference signal reception quality
  • BLER block error rate
  • CQI channel quality indicator
  • DNN data network name
  • the data analysis network element obtains historical service data corresponding to one or more services such as video service, payment service, automatic driving service, and vertical (vertical) service through the AF network element.
  • the data analysis network element can obtain historical network data from 5G NF.
  • Table 2 illustrates the data content from tenant service experience data
  • Table 3 illustrates the content of 5G NF network data. For details, see Tables 2 and 3:
  • Step B The data analysis network element analyzes the historical network data and the historical service data to obtain a service experience model for each service in the network slice.
  • the business experience model refers to the change relationship of the business data with the network data.
  • a business experience model is as follows:
  • the X variable represents each network data, for example, X1 may be GFBR, X2 may be PDB, X3 may be PER, X4 may be network data X4, and X5 may be network data X5.
  • Wn represents the weight of the nth variable
  • n represents the number of variables
  • Xn represents the nth variable.
  • n is an integer greater than or equal to 1.
  • the value of H(x) represents the value of business data.
  • Step C Based on the model relationship and the current or predicted network data X, the data analysis network element can calculate the current or predicted H(X) value, that is, the current or predicted business data value.
  • the calculated value of the business data will be continuously statistically stored, and send the slice management network element or network management network element as service experience information.
  • the data analysis network element sends the service experience information of the network slice to the slice management network element.
  • This step 507 may be initiated based on step 504, or may be actively triggered by the data analysis network element, that is, the data analysis network element may send service experience information to the slice management network element according to the request of the slice management network element, or it may be Actively sent.
  • the service experience information of the network slice in this step may be the service experience information of the newly created network slice in step 501, or may include service experience information of other existing network slices.
  • the service experience information corresponding to a certain time information of the network slice is sent, such as the service experience information corresponding to the first time information.
  • the service experience information corresponding to certain area information of the network slice is sent, such as the service experience information corresponding to the first area information.
  • the data analysis network element may also send third indication information to the slice management network element, and the third indication information is used to indicate the corresponding credibility of the service experience information of the network slice sent by the data analysis network element
  • the information, or the third indication information is used to indicate that the experience information for the newly created network slice has been collected.
  • the data analysis network element sends the network slice service experience information to the network management network element.
  • This step 508 can be performed by referring to step 507, except that the sent object is changed from the slice management network element to the network management network element.
  • the slice management and control network element determines whether the service experience of the network slice meets the SLA requirement according to the service experience information of the network slice sent by the data analysis network element.
  • the network slice may include the newly created network slice described in step 501, or may include other existing network slices, but no matter which network slice is used, the slice management network element determines whether the service experience of the network slice meets the corresponding SLA requirements And the subsequent processing operations are the same.
  • This step means that the slice management and control network element directly or indirectly compares the service experience information sent by the data analysis network element with the SLA requirements required by the tenant, and determines whether the SLA requirements can be met.
  • the two are the same type of information, the two can be directly compared; when the two information cannot be directly compared, the slice control network element needs to process the service experience information received from NWDAF first, and convert it into the ability to meet the SLA requirements Compare the same types of information.
  • whether the service experience of the network slice meets the SLA requirements of the corresponding time and area of the network slice may be determined by time and by area.
  • the slice management and control network element sends a query request to the data analysis network element.
  • the query request is used to query the data analysis network element that the first network slice cannot be satisfied Specify the required area information/time information.
  • the first network slice may be the newly created network slice described in step 501, or may be any other existing network slice, as long as it is determined that its service experience cannot meet the corresponding SLA requirements, it can be regarded as the first network slice Therefore, the first network slice may refer to multiple network slices that cannot meet the corresponding SLA requirements, that is, the query request may be used for area information/time information in the multiple network slices that cannot meet the corresponding specified requirements.
  • the specified requirements include specified service experience requirements of network slice granularity or service experience requirements of business granularity.
  • the specified requirements here are the same as the service experience information in the previous embodiment.
  • the specified requirement is obtained according to the SLA requirement of the first network slice.
  • the specific value of the specified requirement is the same as the value of the SLA requirement.
  • the query request may include at least one filter condition, each filter condition corresponds to a network slice, and the network slice is a network slice that cannot meet the corresponding SLA requirements.
  • Each filter condition is used to indicate to the data analysis network element the filter of the query content, which is generated according to the above specified requirements.
  • the filtering conditions corresponding to network slice 1 are: network slice users ⁇ 1 million, end-to-end delay> 2 ms, average MOS ⁇ 3, and user satisfaction ⁇ 80%.
  • the query request queries sub-region information/time information that cannot meet the specified requirements.
  • the query condition corresponding to the network slice filtering conditions should include The area information and the area information in the filter condition correspond to the third area information in the embodiment of FIG. 2.
  • the query request queries sub-time information/region information that cannot meet the specified requirements within the time.
  • the query request corresponds to the filtering conditions of the network slice.
  • the time information is included, and the time information in the filter condition corresponds to the third time information in the embodiment of FIG. 2.
  • the filter condition of the query request corresponding to the network slice may contain both the time information and the area information.
  • the query request in this step 510 queries that the time and the area cannot be satisfied Specify the required sub-time information/sub-area information.
  • a network slice such as the first network slice
  • the specified requirement and at least one filter condition in this step have the same functional meaning as the service experience requirement information in the embodiment of FIG. 2, and will not be described in detail here.
  • the query request is used to query the data analysis network element for the area information/time information in the first network slice that cannot meet the specified requirements as an example for illustration.
  • the query request is used to query the data analysis network element for the area information/time information in the first network slice that exceeds a certain requirement in excess.
  • the slice control network element determines that the first network slice exceeds the corresponding SLA requirement
  • the query request is used to query the data analysis network element for the area information/time information in the first network slice that exceeds a specified requirement.
  • the method here is similar to the above method for querying the area information/time information that cannot meet the specified requirements, except that the specified requirements in the query request may be different, which will not be repeated here.
  • the query request may be used to query the data analysis network element for area information/time information in the first network slice that cannot meet the first specified requirement and to query the first network slice for exceeding the second specified requirement
  • the area information/time information of the first designated requirement and the second designated requirement may be the same or different.
  • the data analysis network element sends a response message to the slice management and control network element according to the query request.
  • the response message includes area information/time information corresponding to the first network slice that cannot meet the corresponding specified requirements.
  • the response message here may include area information/time information corresponding to the plurality of network slices that cannot meet the specified requirements.
  • the area information/time information contained in the response message in this step that cannot meet the corresponding designated requirements is equivalent to the first area information/first time information in the embodiment of FIG. 2.
  • the response message further includes first service experience information of the first network slice corresponding to the area information/time information.
  • the first service experience information here is the same as the first service experience information in the embodiment of FIG. 2.
  • Service experience information has the same meaning.
  • the slice management and control network element can query from the data analysis network element which specific areas/times in the network slice cannot meet the SLA requirements , Further, the specific service experience information corresponding to these problem areas/times can also be obtained from the data analysis network, so that subsequent networks can only accurately adjust network resources for these areas to avoid blindly adjusting network resources for the entire network, Thereby avoiding heavy workload and waste of network resources.
  • the response message includes the first network slice Area information/time information that meets the specified requirements in excess.
  • the method here is similar to the method in the above response message that includes the area information/time information corresponding to the first network slice that cannot meet the corresponding designated requirements, and details are not described here.
  • the query request is used to query the data analysis network element for area information/time information in the first network slice that cannot meet the first specified requirement and inquires that the first network slice exceeds the second specified requirement in excess
  • the area information/time information of the area the response message contains the area information/time information in the first network slice that cannot meet the first specified requirement and the area information/time information in the first network slice that exceeds the second specified requirement in excess.
  • the slice management network element sends a first notification message to the network device, where the first notification message is used to notify the network device of the slice quality information of the first network slice.
  • the first notification message includes network slice identification information corresponding to the first network slice.
  • the slice quality information of the first network slice includes service experience information of the first network slice, or information about the degree of satisfaction of the service experience information of the first network slice to the SLA requirements of the first network slice.
  • the slice quality information reference may be made to the meaning of the slice quality information in the embodiment of FIG. 2.
  • the first notification message further includes area information, which is that the slice management and control network element cannot satisfy or exceed the specified amount in the first network slice obtained from the data analysis network element through the query request/response message.
  • Required area information The area information here corresponds to the second area information in the embodiment of FIG. 2, and it is considered that the second area information is equivalent to the first area information.
  • the first notification message contains the area information to inform a network slicing network of specific areas that cannot meet or exceed the SLA requirements, so that the access network device only performs resource adjustments on these specific areas and fine-tunes network resource adjustments. The process avoids blindly trying to work, thereby optimizing the allocation of network resources.
  • the first notification message further includes time information
  • the time information in the first notification message is each network slice obtained by the slice management and control network element from the data analysis network element via the first request/response message Time information that cannot meet or exceed the specified requirements in.
  • the time information here corresponds to the second time information in the embodiment of FIG. 2, and it is considered that the second time information is equivalent to the first time information.
  • step 512b the following step 512a may also exist.
  • the access network device sends a third request to the slice management and control network element.
  • the third request is used to request slice quality information of the first network slice.
  • the slice management and control network element may also send a second notification message to the network management network element, where the second notification message is used to notify the network management network element of slice quality information of the first network slice.
  • step 512b The operation mode of this step is similar to step 512b, and it only needs to change the sending object from the access network device to the slice management and control network element.
  • step 513a before 513b there may be step 513a before 513b:
  • the network management network element sends a fourth request to the slice management network element.
  • the fourth request is used to request slice quality information of the first network slice.
  • the network device schedules resources for the first network slice according to the slice quality information of the first network slice obtained from the slice management network element in step 512b.
  • the access network device schedules more air interface resources for network slice 1 or preferentially schedules air interface resources to ensure that network slice 1
  • the satisfaction degree of SLA requirement 1 is improved (for example, to 100%), and the quality of the final network slice 1 can meet its SLA requirement 1.
  • the access network device schedules more air interface resources within the maximum air interface resource range (such as 30%) sent by the network management network element, that is, the increased air interface resource scheduling cannot exceed the maximum air interface resource range delivered by the network management network element.
  • the access network device also needs to schedule more air interface resources by referring to the guaranteed air interface resource range (such as 20%) sent by the network management NE, for example, scheduling more air interface resources near the guaranteed air interface resource range (20%) .
  • the access network device schedules fewer air interface resources for network slice 1 or the priority of air interface resource scheduling is reduced to ensure network slice 1
  • the degree of satisfaction of its SLA requirement 1 is reduced (for example, to 100%), and the quality of the final network slice 1 can meet its SLA requirement 1.
  • the access network device schedules fewer air interface resources within the maximum air interface resource range (such as 30%) sent by the network management network element, that is, the scheduled air interface resources cannot exceed the maximum air interface resource range delivered by the network management network element.
  • the access network device also needs to refer to the guaranteed air interface resource range (such as 20%) sent by the network management network element and schedule fewer air interface resources, for example, scheduling less air interface resources near the guaranteed air interface resource range (20%) .
  • the above SLA requirement 1 may be one of the target SLA requirements of the network slice 1, and the method for obtaining the target SLA requirement of the file is shown in the example in FIG. 2.
  • the network device may also schedule resources for the first network slice according to the time information That is, the network device adjusts the first network slice resource scheduling only for the time information.
  • the network device may also schedule resources for the first network slice according to the area information That is, the network device adjusts the first network slice resource scheduling only for the area information.
  • the network device may be an access network device, a core network device, or a transmission network device.
  • An access network device is used as an example.
  • the access network device continuously generates air interface resource scheduling data. For example, the base station slices each network Time (such as time period or time point), a certain area (such as a cell or a list of cells) has scheduled air interface resource amount (such as the type and number of air interface physical resource blocks), scheduling priority and other data, which will be continuously used as air interface resource scheduling data Measure, collect, and report to the network management network element. These data will be used by the network management network element to detect and adjust the air interface resources.
  • the manifestation of the amount of air interface resources is not limited to the type and number of air interface physical resource blocks that the access network device specifically calls for each network slice, such as the number of CPUs, the number of memories, and the number of channels. It can also be an access network device Call the air interface resources for each network slice as a proportion of the total air interface resources of the access network device, such as network slice 1 accounts for 20%, network slice 2 accounts for 30%, etc.
  • the network management network element adjusts the network resource configuration information of the first network slice according to the acquired service experience information of the first network slice, so that the first network slice can meet the corresponding SLA requirements.
  • the service experience information of the first network slice obtained by the network management network element may include: the service experience information of the first network slice obtained from the data analysis network element according to step 508, or the first network obtained from the slice management network element according to step 513b Slice quality information for slices.
  • the network management network element determines that a network slice cannot meet the corresponding SLA requirements, the network management network element increases the configuration of the access network resource, the core network resource, or the transmission network resource. For details, see step 501; on the contrary, the network management network When the element judges that a network slice exceeds the corresponding SLA requirement, the network management network element reduces the configuration of the access network resource, the core network resource, or the transmission network resource. For details, see step 501.
  • the network management network element determines that the service experience of a network slice just meets the corresponding SLA requirements, there is no need to adjust the configuration of the access network resources or core network resources or transmission network resources.
  • the network management network element may target the time or the area Adjust the network resource configuration of the first network slice.
  • the network management network element when adjusting the network resources of the first network slice, the network management network element also needs to consider the air interface resource scheduling data obtained from the access network device.
  • the air interface resource scheduling data is executed by the access network for the first network slice Generated during the air interface resource scheduling process.
  • the initial air interface resource configuration information set by the network management network element on network slice 1 is: the maximum air interface resource configuration is 30%, and the guaranteed air interface resource configuration is 20%. If the network management network element obtains that the amount of air interface resources scheduled by an access network device for network slice 1 is 20%, and the network management network element learns according to step 508 or step 513b that the corresponding air interface resource volume is 20%, the network slice 1 If the SLA requirement 1 is only 80% satisfied, the configuration of the network management network element adjustable air interface resource becomes: the maximum air interface resource configuration is 30%, and the guaranteed air interface resource configuration is 23%, which increases the access network equipment’s The amount of air interface resources for network slicing (e.g., increased to 23%) is ultimately to achieve the goal that network slice 1 satisfies its SLA requirement 1 to 100%.
  • the initial air interface resource configuration information set by the network management network element on network slice 2 is: the maximum air interface resource configuration is 30%, and the guaranteed air interface resource configuration is 25%.
  • the network management network element obtains that the amount of air interface resources scheduled by a certain access network device for network slice 2 is 25%, and the network management network element learns that the air interface resource quantity corresponds to 25% according to step 508 or step 513b, the network slice 2 SLA requirement 2 is only 120% satisfied, then the network management network element can adjust the configuration of the access network resources, so that the access network device reduces the amount of air interface resources for the network slice (for example, to 20%).
  • the purpose of the network slice 2 meeting the requirement of its slice1 SLA is 100%.
  • the adjustment of the core network resource configuration information can also be understood by referring to the adjustment of the access network resource configuration information, but the type of the adjusted resource is different, and the core network resource configuration information can be understood by referring to step 501.
  • the network management network element can continuously adjust the network slice based on the service experience data of the network slice obtained from the data analysis network element and the slice control network element through the loop operation of steps 502-515 And other related network slice resource configuration information, the purpose is to make the network slice meet the SLA requirements of the network slice proposed by the tenant as much as possible, if the SLA requirements cannot be met, you need to re-negotiate with the tenant to achieve new SLA requirements, And does not affect the quality of other existing network slices that are in a stable stage.
  • the network management network element determines the new SLA requirements that the newly created network slice can meet, and sends new user number information to the slice management network element according to the new SLA requirements.
  • the meaning of the new user number information may be based on the meaning of the initial user number information in step 502.
  • the new SLA requirement may be the same as or different from the SLA requirement in step 1.
  • the network management network element may also inform the slice management network element of the new SLA requirements corresponding to the newly created network slice network.
  • the network management network element may also inform the slice management network element of the fourth indication information, and the fourth indication information is used to notify the slice management network element of the new user number information or the credibility information of the new SLA requirement information sent by the network management network element.
  • the credibility value corresponding to this state set by the network management network element is higher (for example, the credibility value is 99%).
  • the network management network element may also inform the slice management network element of the fifth indication information, where the fifth indication information is used to indicate that the network slice is in a stable state. In this state, the network is relatively stable, and resource adjustments are not frequently performed. In addition, the network management network element needs to negotiate with the tenant and regard the new SLA requirement as the final signed SLA requirement.
  • the slice management and control network element performs user number access control on the network slice according to the new user number information sent by the network management network element.
  • the access control of the number of users specifically refers to controlling the number of registered users or the number of online users in the network slice. For details, see step 502.
  • the slice management network element may also perform user number control on the network slice based on the fourth indication information.
  • the slice management and control network element when the slice management and control network element is informed of the new user number information or the new SLA requirement information sent by the network management network element according to the fourth instruction information, the credibility is relatively high (such as 99%), the slice management and control network element can allow a large number of users at the same time Access the network slice. For example, if the slice management network element newly instructed by the network management network element has no more than 10 million registered users of the network slice, the slice management network element can allow 10 million users to access the network slice, without the need to allow users to access gradually or in stages. Or remove the network slice.
  • the slice management network element may also perform user number control on the network slice based on the fifth indication information. Specifically, when the slice management network element learns that the network slice is in a stable stage according to the fifth instruction information, the slice management network element may allow a large number of users to access the network slice at the same time. For example, the network management network element initially instructs the slice management network element that the number of registered users of the network slice does not exceed 10 million, then the slice management network element may allow 10 million users to access the network slice.
  • the slice management network element may also receive the fourth indication information and the fifth indication information from the network management network element, then the slice management network element only needs to control the number of users in the above manner.
  • new user number information or new SLA requirements may also be sent by region, same as step 501.
  • different states of network slices can be distinguished.
  • the slice management and control network element can achieve differentiated control over the access of the number of users of network slices to improve The accuracy and fineness of the number of users control.
  • the slice control network element can query from the data analysis network element to know which specific areas and/or times in the network slice cannot meet the SLA requirements, so that subsequent networks can only target These areas accurately adjust network resources to avoid blindly adjusting network resources on the entire network, thereby avoiding heavy workload and waste of network resources.
  • 7B is a schematic diagram of another embodiment of a method for resource scheduling of network slices in an embodiment of the present application.
  • another embodiment of the method for resource scheduling of a network slice provided by an embodiment of the present application may include one or more of the following steps:
  • the slice management and control network element obtains slice quality information of the first network slice from the data analysis network element or the network management network element.
  • the slice quality information includes at least one of the following information: service experience information of the first network slice, and service satisfaction information of the first network slice relative to the target service level agreement requirement information.
  • the service experience information of the first network slice here may be specifically understood by referring to the meaning and content of the service experience information (for example, the third service experience information) described in the embodiment of FIG. 2.
  • the service experience information of the first network slice here may be service experience information corresponding to the entire network range or all time ranges of the first network slice.
  • the service experience information of the first network slice here may also be service experience information of the first network slice corresponding to certain area information or certain time information in the first network slice.
  • the satisfaction degree information may include unsatisfiability, satisfaction or excess satisfaction. Specifically, for the meaning and expression of the satisfaction degree information, refer specifically to the satisfaction degree information in the embodiment of FIG. 2.
  • the slice management and control network element obtains the slice quality information of the first network slice from the data analysis network element or the network management network element. For details, refer to the slice management and control network element described in steps 504 and 507 in the embodiment of FIG. 7A to obtain the network slice corresponding to the network slice from the data analysis network element. The description of the service experience information is understood and will not be repeated here.
  • this embodiment may further include: a slice management network element according to the service experience of the first network slice
  • the information determines the satisfaction degree information of the service experience information of the first network slice relative to the target service level agreement requirement information of the first network slice.
  • the satisfaction degree information includes unsatisfiability, satisfaction, or excess satisfaction.
  • the satisfaction degree information refer specifically to the satisfaction degree information in the embodiment of FIG. 2.
  • the target service level agreement requirement information of the first network slice reference may be made to the target service level agreement requirement information described in the embodiment of FIG. 2.
  • the slice management and control network element determines that the service experience information of the first network slice cannot meet or exceed the target service level agreement information of the first network slice according to the quality information of the first network slice.
  • the slice management and control network element may directly determine the first network slice's The service experience information cannot meet or exceed the target service level agreement information of the first network slice.
  • the slice management network element determines, based on the service experience information, that the service experience information of the first network slice cannot meet or exceed the first network slice.
  • the slice management network element sends a request to the network management network element.
  • the request is used to request a network domain from the network management network element that causes the service experience information of the first network slice to fail to meet or exceed the target service level agreement information of the first network slice.
  • the network domain includes but is not limited to the following fields: access network domain (RAN domain), core network domain (CN domain), and transmission network domain (TN domain).
  • RAN domain access network domain
  • CN domain core network domain
  • TN domain transmission network domain
  • the network management network element determines that the service experience information of the first network slice fails to meet or exceeds the target service level agreement information of the first network slice due to the first network domain.
  • step 523 one or more of the following steps may also be included:
  • Step A The network management network element obtains the slice quality information of the first network slice from the data analysis network element.
  • Step B The network management network element determines, according to the slice quality information of the first network slice, that the service experience information of the first network slice cannot meet or exceeds the first network slice target service level agreement information.
  • step 521 or step 509 in the embodiment corresponding to step 7A For the method of this step, reference may be made to step 521 or step 509 in the embodiment corresponding to step 7A.
  • the judgment result that the service experience information of the first network slice fails to meet or exceeds the first network slice target service level agreement information is a prerequisite for step 523 to be executed.
  • step 523 and subsequent steps 524 may not Was executed.
  • the network management network element Since the network management network element is a network element responsible for deploying, maintaining, and managing network slices, it can learn the global data of a network slice, so the network management network element can determine the service experience information of the first network slice for the first network slice target service Satisfaction information of the level agreement information, and can also locate the problematic network area that causes the service experience information of the first network slice to exceed or fail to meet the target service level agreement information of the first network slice, for example, the problematic network domain is RAN One or more of domain, CN domain, TN domain.
  • the network management network element uses the problematic network domain as the first network domain. Specifically, for a network slice, the network management network element may preset one or more key performance indicators (KPIs) corresponding to each network domain. During the actual operation of network slicing, the network management network element compares the actual measured value and the preset value of the key performance indicators of each network domain to locate the problem area.
  • KPIs key performance indicators
  • the network management network element sends instruction information to the slice management network element.
  • the indication information is used to indicate that the service experience information of the first network slice fails to meet or exceeds the target service level agreement information of the first network slice due to the first network domain.
  • the network management network element may send the indication information to the slice management and control network element as required by the slice management and control network element.
  • the network management network element may also actively send the indication information to the slice management network element, that is, step 522 may not be executed.
  • the network management network element may also send credibility information to the slice management network element, where the credibility information is used to indicate the credibility of the indication information.
  • the credibility information is used to indicate the credibility of the indication information.
  • the network management network element generates the credibility information according to an internal strategy or algorithm.
  • the slice management network element determines that the service experience information of the first network slice fails to meet or exceeds the target service level agreement information of the first network slice because of the first network domain.
  • the slice management network element may determine, based on the indication information sent by the network management network element, that the service experience information of the first network slice fails to meet or exceeds the target service level agreement information of the first network slice The reason lies in the first network domain.
  • 522, 523, and 524 are optional steps. In another possible implementation manner, these three steps may not be executed, and the slice management and control network element may determine the first network slice. The reason why the service experience information cannot satisfy or exceed the target service level agreement information of the first network slice lies in the first network domain. For a specific determination method, reference may be made to the determination method of the network management network element in step 523.
  • the slice management network element sends the slice quality information of the first network slice to the network device in the first network domain.
  • the reason that the service experience information of the first network slice cannot be satisfied or exceeds the target service level agreement information of the first network slice is that after the first network domain, the slice management network element A network device is determined in the first network domain, and slice quality information of the first network slice is sent to the network device.
  • the network device may refer to all network devices in the first network domain, or may be part of network devices in the first network domain, for example, only in the first network domain corresponding to certain area information/time information Network equipment.
  • the slice quality information is used by the network device to schedule resources for the first network slice according to the slice quality information.
  • the slice management network element sends the slice quality information of the first network slice to the access network device in the access network domain, so that the access network device
  • the network slice quality information is the first network slice scheduling air interface resource. How the access network device schedules more or less air interface resources for the first network slice according to the slice quality information of the first network slice can be specifically understood by referring to the related description in step 105 of FIG. 2 or step 514 of the embodiment of FIG. 7A .
  • the resource scheduling method is basically the same as the access network domain where the first network domain is, except that the resources of the core network or the transmission network are scheduled.
  • the resource scheduling method is also basically the same, as long as the corresponding resources are scheduled in the corresponding network domains, respectively.
  • the slice management network element determines that the service experience information of the first network slice cannot be satisfied or exceeds the target service of the first network slice based on the indication information sent by the network management network element in step 524
  • the reason of the horizontal protocol information is in the first network domain
  • the slice management and control network element also receives credibility information sent by the network management network element.
  • the credibility information is used to indicate the credibility of the indication information.
  • the network element may also send the slice quality information of the first network slice to the network device of the first network domain according to the credibility information.
  • the slice management network element when the credibility information is higher than a preset credibility value (eg, the credibility information value is greater than 90%), the slice management network element sends the first network to a network device in the first network domain Slice quality information of the slice; conversely, when the credibility information is lower than the preset credibility value (eg, the credibility information value is less than 60%), the slice management network element does not send to the network device in the first network domain Sending slice quality information of the first network slice.
  • a preset credibility value eg, the credibility information value is greater than 90%
  • the slice management network element when the credibility information is lower than the preset credibility value (eg, the credibility information value is less than 60%), the slice management network element does not send to the network device in the first network domain Sending slice quality information of the first network slice.
  • the quality information of the first network slice may be slice quality information corresponding to the entire network range or the entire time range of the first network slice, or may be slice quality information corresponding to certain area information or certain time information in the first network slice.
  • the certain area information or the certain time information may be that the slice management and control network element determines the second area information and/or the second time information using the method described in the embodiment of FIG. 2.
  • the method described in the embodiment of FIG. 7B can be used in combination with the method described in the embodiment of FIG. 2.
  • the slice control network element can be located using the method described in FIG. 7B.
  • the first network domain and then send the second area information and/or the second time information to the network device of the first network domain, so that the network device of the first network domain is the first according to the second area information and/or the second time information Network slice scheduling resources.
  • the reason why the slice management and control network element can accurately locate the service experience information of the first network slice that cannot meet the target service level agreement information is because it comes from a network domain (such as the access network domain), and then Then the slice quality information of the first network slice is provided to the network device in the network domain, so that the network device in the network domain adjusts the resource scheduling situation.
  • This method can avoid blindly adjusting the resource scheduling situation of other normally working network domains, and improve the accuracy of resource scheduling.
  • 7C is a schematic diagram of another embodiment of a method for resource scheduling of network slices in an embodiment of the present application.
  • another embodiment of the network slice resource scheduling method provided in this application includes one or more of the following steps:
  • the network management network element determines the state information of the first network slice.
  • the state information of the first network slice includes the unsigned SLA state or the signed SLA state of the first network slice.
  • the unsigned SLA state means that a service level agreement for the first network slice has not been signed with the slice tenant.
  • the first network slice belongs to a newly created network slice or a network slice that is still in the testing stage.
  • the signed SLA status means that a service level agreement has been signed with the slice tenant for the first network slice.
  • the first network slice belongs to a stable state network slice or it has completed the test phase.
  • the network management network element may determine whether a service level agreement corresponding to the first network slice has been signed with the tenant according to the internal configuration information, so as to determine the status information of the first network slice.
  • the network management network element may also determine the state information of the first network slice according to the slice quality information of the first network slice obtained from the data analysis network element.
  • the slice quality information of the first network slice includes service experience information of the first network slice or service experience information of the first network slice relative to the target network service level agreement requirement information of the first network slice.
  • the network management network element may determine the status information of the first network slice according to whether the service experience information meets the target service level agreement requirement information. For example, if the service experience information satisfies the target service level agreement requirement information, the status information of the first network slice is determined to be signed SLA status or equivalent stable state, on the contrary, it is determined to be unsigned SLA status or equivalent test status.
  • the network management network element may also determine credibility information corresponding to the status information of the first network slice, where the credibility information is used to indicate the credibility of the status information.
  • the credibility information is used to indicate the credibility of the status information.
  • the specific expression form of the credibility information refer to the expression form of the credibility of the user quantity limitation information in the embodiment of FIG. 5.
  • the network management network element sends the status indication information of the first network slice to the network device.
  • the status indication information includes status information of the first network slice.
  • the network management network element receives a status request message to be sent by the network device, where the status request message is used to request status information of the first network slice.
  • the network management network element may actively send the status indication information of the first network slice to the network device, that is, it does not have to be based on the status request message of the network device.
  • the network management network element can also indicate to the network device the target service level agreement requirement information corresponding to the status information, in other words, notify the network device which SLA the network slice is not signed or signed.
  • the status indication information may be included in the resource configuration information and sent to the network device by the network management network element.
  • the meaning and content of the resource configuration information refer to the resource configuration in the embodiment of FIG. 3 or FIG. 4 for details. The meaning of the information.
  • the status indication information can be sent to the network device by the network management network element independently of the resource configuration information.
  • the network management network element may also send the credibility information corresponding to the status information of the first network slice to the network device.
  • the credibility information may be included in the status indication information and sent to the network device, or may be sent to the network device independently of the status indication information.
  • the network device determines the state information of the first network slice.
  • the network device determines the status information of the first network slice according to the status indication information of the first network slice sent by the network management network element.
  • the network device determines the status information of the first network slice by itself. For details, refer to the method for the network management network element in step 520 to determine the status information of the first network slice. If the network device can determine the status information of the first network slice by itself, steps 530 and 531 can be omitted.
  • the network device can also determine the target service level corresponding to the status information by itself or according to the notification of the network management network element
  • the agreement requires information, in other words, to determine which SLA the network slice is unsigned or signed.
  • the network device schedules resources for the first network slice according to the state information of the first network slice.
  • the network device when the state information of the first network slice is that the first network slice has not signed the SLA state, and the state information of the second network slice is that the second network slice has signed the SLA state, the network device is deprioritized behind the second network slice to schedule resources for the first network slice. In other words, at this time, the network device preferentially schedules resources for the second network slice, and only schedules resources for the first network slice when there are resources remaining.
  • the second network slice is another network slice that is different from the first network slice.
  • the network device prioritizes the second network slice and schedules resources for the first network slice. In other words, at this time, the network device preferentially schedules resources for the first network slice, and only schedules resources for the second network slice when there are resources left.
  • the network device schedules resources for the first network slice and the second network slice at the same level. In other words, at this time, there is no priority difference between the two network slices, and resource scheduling can be obtained from the network device at the same opportunity.
  • the network device schedules resources for the first network slice and the second network slice at the same level; or, the network device schedules resources for the first network slice and the second network slice according to other information, for example, the network device
  • the preemption of priority information between different networks schedules resources for different network slices.
  • the network device can also schedule resources for different network slices according to the specific SLA signed by different slices. For example, the SLA signed by the first network slice requires high For SLA requirements of the second network slice, priority is given to scheduling resources for the first network slice.
  • the network device may also schedule resources for the first network slice according to the credibility information. For example, when the credibility information is higher than a preset credibility value (eg, the credibility information value is greater than 90%), the network device schedules resources for the first network slice according to the foregoing several possible ways; otherwise, When the credibility information is lower than the preset credibility value (for example, the credibility information value is less than 60%), the network device does not schedule resources for the first network slice in the foregoing several possible ways. There are other possible implementation ways for the network device to schedule resources for the first network slice according to the credibility information, and the invention is not limited.
  • a preset credibility value eg, the credibility information value is greater than 90%
  • how the network device schedules resources for the first network slice may also be combined with the embodiment described in FIG. 3 or 4, that is, the network device may also configure the resource according to the network management network element.
  • the information is the first network slice scheduling resource, which will not be repeated here.
  • the network equipment described in this embodiment includes one or more of the following equipment types: access network equipment, core network equipment, and transmission network equipment.
  • access network equipment access network equipment
  • core network equipment core network equipment
  • transmission network equipment for the specific meaning of the network device herein, reference may be made to the network device in the embodiment described in FIG. 3 or 4.
  • step 533 is specifically that the access network device schedules air interface resources for the first network slice according to the state information of the first network slice.
  • step 533 is specifically that the core network device schedules core network resources for the first network slice according to the state information of the first network slice.
  • step 533 is specifically that the transmission network device schedules transmission network resources for the first network slice according to the state information of the first network slice.
  • step 533 is that the corresponding network device each schedules the resources of the corresponding network.
  • 7D is a schematic diagram of another embodiment of a method for controlling the number of users in an embodiment of the present application.
  • another embodiment of the method for controlling the number of users provided in the embodiments of the present application may include one or more of the following steps:
  • the network management network element determines the initial user number limit information of the target network slice.
  • the network management network element may determine the initial user number restriction information according to the initial service level agreement requirement information provided by the tenant of the network slice.
  • the initial service level agreement requirement information generally refers to a trial operation service level agreement requirement provided by the tenant before signing the formal service level agreement, which may contain initial user number limit information.
  • the network management network element sends to the slice management network element the initial user number limitation information of the target network slice.
  • step 402 For specific details of this step, reference may be made to the method in which the network management network element sends the target network slice user number limitation information to the slice management network element in step 402, the only difference is that the instruction information described in step 402 is not sent in this step. I will not repeat them here.
  • the slice management and control network element controls the number of users of the target network slice according to the initial user number limit information.
  • the network management network element obtains slice quality information of the target network slice.
  • the slice quality information includes the service experience information of the target network slice and/or the satisfaction degree information of the service experience information of the target network slice relative to the target service level agreement requirements of the target network slice.
  • the meaning and content of the slice quality information reference may be made to the meaning and content of the slice quality information described in the embodiments of FIG. 2 to FIG. 7A, which will not be repeated here.
  • the network management network element may obtain the slice quality information of the target network slice from the slice management network element or the data analysis network element. For details, refer to step 4 or FIG. 7A.
  • the network management network element obtains the slice quality information or service experience of the first network slice The method of information will not be repeated here.
  • the network management network element determines, according to the slice quality information of the target network slice, the new user number limitation information of the target network slice.
  • the network management network element may also determine the satisfaction degree information of the service experience information relative to the target service level agreement requirement information according to the service experience information of the target network slice .
  • the satisfaction degree information may include unsatisfiability, satisfaction, and excess satisfaction, or the satisfaction degree information may be other manifestations, which are not limited here.
  • the network management network element determines the restriction information of the number of new users of the target network slice according to the satisfaction degree information of the service experience information of the target network slice relative to the target service level agreement requirement information of the target network slice. For example, when the satisfaction degree information is unsatisfiable, the number of users included in the new user number limit information determined by the network management network element is less than the initial user number limit information. In other words, the network management network element decides to reduce the number of users in the target network slice ; On the contrary, when the satisfaction degree information is over-fulfilled, the number of users contained in the new user number limit information determined by the network management network element is greater than the initial user number limit information. In other words, the network management network element decides to increase the number of users in the target network slice Quantity.
  • the network management network element decides not to change the users in the target network slice Quantity.
  • the network management network element sends the new user number limitation information to the slice management network element.
  • step 541 the difference is that the initial user number restriction information in step 541 is replaced with new user number restriction information.
  • the slice management and control network element controls the number of users served by the target network slice according to the new user number restriction information.
  • the slice management and control network element does not need to do anything.
  • the slice management and control network element needs to restrict more users to access the target network slice, and even needs to remove the excess from the target network slice The user accesses the target network slice.
  • the slice management and control network element allows more users to access the target network slice.
  • the network management network element and the slice control network element can continuously update the user number limit information in the target network slice to achieve the optimal number of users state, that is, the target network slice
  • the service experience information meets the status of the information required by the target service level agreement.
  • some steps in some embodiments of the present application may illustrate the network slice obtained by the slice management network element from the data analysis network element.
  • Service experience information (such as service experience information corresponding to the first area information/first time information) and the service experience information of the network slice (such as second area information/second time information corresponding to the service experience information sent to the network device )
  • both service experience information contains the network granularity experience information and service granularity experience information of the network slice, but in fact both can also contain different types of experience information, such as the former contains users Granular experience information, the latter contains experience information of network granularity and business granularity.
  • the slice management and control network element may generate service experience information to be sent based on the received service experience information, and the two may be the same or different.
  • the same is true for network management network elements.
  • this embodiment involves both the slice control network element and the network management network element to obtain the service experience information of the network slice from the data analysis network element.
  • this embodiment analyzes the two and the same data Network element interaction is taken as an example for illustration. There are also scenarios where the two interact with different data analysis network elements to obtain service experience information of network slices, which is not excluded in this embodiment.
  • a slice management and control network element refers to a network element that has at least one of the following functions: user access function for managing and controlling network slices, resource deployment function, and network management command execution function, which can be located on the control plane of the operator network, such as a slice management and control network It selects the functional network element (NSSF) for network slicing; it can also be located on the management plane of the operator's network.
  • NSSF functional network element
  • the network element for slice management and control is OAM, NSMF, or communication service management function (CSMF).
  • the data analysis network element refers to a network element that has at least one of the following data analysis functions: operator network data, service data, and user data. It can be located under operator control, for example, the data analysis network element can be the network data analysis network element NWDAF, or it can be located on the management plane of the operator network, for example, the data analysis network element can be MDAS.
  • the network management network element refers to a network element having at least one of the following functions: the function of deploying network resources and the function of managing the network.
  • the network management network element may be NSSF, OAM, NSMF, or CSMF.
  • the slice management and control network element may be the NSSF of the control plane, then the corresponding network management network element may be OAM, NSMF or CSMF.
  • the slice management and control network element may also be NSMF and CSMF of the management plane, then the corresponding network management network element may be MDAS.
  • the above-mentioned slice management network element, network device, data analysis network element, and network management network element include hardware structures and/or software modules corresponding to performing each function.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is performed by hardware or computer software driven hardware depends on the specific application of the technical solution and design constraints. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.
  • the above-mentioned slice management and control network element, network device, data analysis network element or network management network element can be implemented by one physical device, can also be implemented by multiple physical devices together, or can be one within a physical device
  • the logical function unit is not specifically limited in the embodiment of the present application.
  • FIG. 8 is a schematic diagram of a hardware structure of a communication device provided by an embodiment of the present application.
  • the communication device includes at least one processor 601, memory 602, and communication line 603.
  • the communication device may also include at least one of a transceiver 604 and a communication interface 606.
  • the processor 601 can be a general-purpose central processing unit (central processing unit, CPU), microprocessor, application-specific integrated circuit (application-specific integrated circuit, server IC), or one or more used to control the application program execution Integrated circuit.
  • CPU central processing unit
  • microprocessor application-specific integrated circuit
  • server IC application-specific integrated circuit
  • the communication line 603 may include a path to transfer information between the above components.
  • Transceiver 604 using any transceiver-like device for communicating with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc. .
  • the transceiver 604 may also be a transceiver circuit or a transceiver.
  • the communication device is a slice management and control network element, a network device, a data analysis network element, or a network management network element, the transceiver may be included.
  • the communication device may also include a communication interface 606.
  • the memory 602 may be read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (random access memory, RAM), or other types that can store information and instructions
  • the dynamic storage device can also be electrically erasable programmable read-only memory (electrically programmable) read-only memory (EEPROM), read-only compact disc (compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (Including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be used by a computer Access to any other media, but not limited to this.
  • the memory may exist independently, and is connected to the processor 601 through a communication line 603.
  • the memory 602 may also be integrated with the processor 601.
  • the memory 602 is used to store computer execution instructions for executing the solution of the present application, and the processor 601 controls execution.
  • the processor 601 is used to execute computer-executed instructions stored in the memory 602, so as to implement the drone supervision method provided by the foregoing method embodiments of the present application.
  • the computer execution instructions in the embodiments of the present application may also be called application program codes, which are not specifically limited in the embodiments of the present application.
  • the processor 601 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 8.
  • the communication device may include multiple processors, such as the processor 601 and the processor 605 in FIG. 8.
  • processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor.
  • the processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (eg, computer execution instructions).
  • this application can divide the functional units of the slice management and control network element, network equipment, data analysis network element or network management network element according to the above method embodiments, for example, each functional unit can be divided corresponding to each function, or Integrate two or more functions into one functional unit.
  • the above integrated functional units can be implemented in the form of hardware or software functional units.
  • FIG. 9 shows a schematic structural diagram of a slice management and control network element.
  • an embodiment of the slice management network element 70 of the present application may include a receiving unit 701, a processing unit 702, and a sending unit 703;
  • the sending unit 703 is configured to send a request to the data analysis network element, where the request includes service experience requirement information for the first network slice;
  • the receiving unit 701 is configured to receive a response sent by the data analysis network element, where the response includes first area information and/or first time information of the first network slice corresponding to the service experience requirement information;
  • a sending unit 703, configured to send second area information and/or second time information to the network device according to the first area information and/or first time information, the second area information and/or second time information
  • the network device schedules resources for the first network slice according to the second area information and/or second time information.
  • the solution described above enables the network device to perform resource scheduling based on the second area information and/or second time information, which improves the accuracy of resource scheduling and utilization of network resources, and also improves the performance of network slicing.
  • the processing unit 702 is configured to determine the second area information and/or the second time information according to the first service experience information.
  • the sending unit 703 is configured to send slice quality information corresponding to the second area information and/or the second time information to the network device, where the slice quality information includes At least one of the following information: second service experience information corresponding to the first network slice of the second area information and/or second time information, and the second service experience information relative to the first
  • the target service level agreement for network slicing requires information about the degree of satisfaction of the information.
  • the second area information is used by the access network device to schedule the first network slice according to the second area information
  • the second time information is used by the access network device to schedule access network resources for the first network slice according to the second time information.
  • the satisfaction degree information includes unsatisfiability, satisfaction, or excess satisfaction.
  • the third area indicated by the third area information includes the first area indicated by the first area information
  • the first The three-region information is used to request the data analysis network element for the first region information corresponding to the service experience requirement information in the third region.
  • the third time indicated by the third time information includes the first time indicated by the first time information
  • the The third time information is used to request the first time information corresponding to the service experience requirement information in the third time from the data analysis network element.
  • the processing unit 702 is configured to obtain third service experience information of the first network slice; if the third service experience information does not correspond to the target service level agreement requirement information, then Determining service experience requirement information of the first network slice, the service experience requirement information of the first network slice corresponding to the target service level agreement requirement.
  • the processing unit 702 is configured to compare the third service experience information with the target service level agreement requirement information; if the third service experience information does not meet or exceeds the requirements Target service level agreement requirement information, it is determined that the third service experience information does not correspond to the target service level agreement requirement information.
  • the processing unit 702 is configured to determine, if the third service experience information does not satisfy the target service level agreement requirement information, the first network slice corresponding to the unsatisfied situation Service experience requirement information; if the third service experience information exceeds the target service level agreement requirement information, determine the service experience requirement information of the first network slice corresponding to the excess satisfaction condition.
  • the processing unit 702 is configured to reduce the number of service users of the first network slice if the third service experience information does not meet the target service level agreement requirement information; if the If the third service experience information exceeds the target service level agreement requirement information in excess, the number of service users of the first network slice is increased.
  • the processing unit 702 is further configured to obtain the initial service level agreement requirement information of the first network slice; determine at least one service level according to the initial service level agreement requirement information of the first network slice Agreement requirement information; determining one of the at least one service level agreement requirement information as the target service level agreement requirement information.
  • the service experience requirement information of the first network slice includes at least one of the following information: the user number requirement of the first network slice, the average user experience requirement of the service, and the service The filtering requirement of the user satisfaction ratio, wherein the user satisfaction ratio of the service is the ratio of the number of users whose user experience corresponding to the service is not worse than the preset value to the total number of users of the service.
  • the sending unit 703 is further configured to send a subscription request to the data analysis network element, where the subscription request is used to request service experience information of the second network slice.
  • the receiving unit 701 is also used to learn from the network management network element that a new network slice needs to be created or a network slice is deleted.
  • the processing unit 702 is further configured to determine that the cause of the problem area and/or problem time is the first network domain, and the problem area includes the first area or the second area.
  • the problem time includes a first time or a second time; the slice management network element determines the network device according to the first network domain.
  • the processing unit 702 is configured to learn from the network management network element that the cause of the problem area and/or problem time lies in the first network domain.
  • the processing unit 702 is configured to acquire first credibility information from the network management network element, and the first credibility information is used to indicate a cause of the problem area and/or problem time It lies in the degree of credibility of the first network domain; determining the network device according to the first credibility information and the first network domain.
  • the processing unit 702 is configured to learn from the network management network element that the cause that the third service experience information does not correspond to the target service level agreement requirement information is the second network domain.
  • the processing unit 702 is configured to obtain second credibility information from the network management network element, and the second credibility information is used to indicate that the third service experience information and all The reason why the target service level agreement requirement information does not correspond lies in the degree of credibility of the second network domain; the network device is determined according to the second credibility information and the second network domain.
  • the first network domain or the second network domain includes at least one of the following: an access network domain, a core network domain, and a transmission network domain.
  • the slice control network element 70 provided by the embodiment of the present application is used to execute the method performed by the slice control network element in the method embodiment corresponding to FIG. 2 or FIG. 7A, so the embodiment of the present application may be implemented with reference to the method corresponding to FIG. 2 or FIG. 7A Understand the relevant parts of the example.
  • the slice management and control network element 70 is presented in the form of dividing each functional unit in an integrated manner.
  • the "functional unit” herein may refer to an application-specific integrated circuit, a processor and memory that execute one or more software or firmware programs, integrated logic circuits, and/or other devices that can provide the above-mentioned functions.
  • the slice management and control network element 70 may adopt the form shown in FIG. 8.
  • the processor 601 of FIG. 8 may call the computer execution instruction stored in the memory 602 to cause the slice management network element 70 to execute the method executed by the slice management network element in the method embodiment corresponding to FIG. 2 or FIG. 7A.
  • the functions/implementation processes of the receiving unit 701, the processing unit 702, and the sending unit 703 in FIG. 9 may be implemented by the processor 601 in FIG. 8 mobilizing the computer stored in the memory 602 to execute instructions.
  • the function/implementation process of the processing unit 702 in FIG. 9 can be implemented by the processor 601 in FIG. 8 calling the computer execution instructions stored in the memory 602, and the function/implementation of the receiving unit 701 and the sending unit 703 in FIG. The process can be realized by the transceiver 604 in FIG. 8.
  • the slice management and control network element provided by the embodiment of the present application can be used to perform the method of the embodiment corresponding to FIG. 2 or FIG. 7A, for the technical effects that can be obtained by the embodiment of the present application, refer to the method embodiment corresponding to FIG. 2 or FIG. 7A. I won't repeat them here.
  • FIG. 10 shows a schematic structural diagram of a network device.
  • an embodiment of the network device 80 provided by the present application may include: a receiving unit 801, a processing unit 802, and a sending unit 803;
  • the receiving unit 801 is configured to receive second area information and/or second time information of the first network slice sent by the slice management network element;
  • the processing unit 802 is configured to schedule resources for the first network slice according to the second area information and/or second time information.
  • the network device of the present application can perform resource scheduling according to the second area information and/or the second time information, which improves the accuracy of resource scheduling and the utilization rate of network resources, and also improves the performance of network slicing.
  • the receiving unit 801 is further configured to receive slice quality information corresponding to the first network slice sent by the slice management network element, the slice quality information including the first network slice Service experience information and/or satisfaction degree information of the first network slice service experience information relative to the target service level agreement requirements;
  • the processing unit 802 is configured to adjust resources scheduled for the first network slice according to the slice quality information.
  • the slice quality information corresponding to the first network slice includes service experience information corresponding to the second area of the first network slice and/or service experience information corresponding to the second area is relatively According to the satisfaction degree information required by the target service level agreement, the second area is an area indicated by the second area information.
  • the second area is an area that cannot meet or exceed the requirements of the target service level agreement.
  • the slice quality information corresponding to the first network slice includes service experience information corresponding to the second time of the first network slice and/or relative service experience information corresponding to the second time
  • the second time is the time indicated by the shown second time information.
  • the second time is a time that cannot meet or exceed the requirements of the target service level agreement.
  • the slice quality information corresponding to the first network slice includes service experience information corresponding to the second area and the second time of the first network slice and/or the second area and the first
  • the service experience information corresponding to the two times corresponds to the satisfaction degree information required by the target service level agreement
  • the second area is the area indicated by the second area information
  • the second time is the second time information shown The indicated time.
  • the processing unit 802 is configured to increase resources scheduled for the first network slice if the service experience information of the first network slice cannot meet the requirements of the target service level agreement; if If the service experience information of the first network slice exceeds the requirements of the target service level agreement in excess, the resources scheduled for the first network slice are reduced.
  • the network device 80 provided in the embodiment of the present application is used to execute the method performed by the network device in the method embodiment corresponding to FIG. 2 or FIG. 7A, so for the embodiment of the present application, reference may be made to the related method embodiments corresponding to FIG. 2 or FIG. 7A. Partially understand.
  • the network device 80 is presented in the form of dividing each functional unit in an integrated manner.
  • the "functional unit” herein may refer to an application-specific integrated circuit, a processor and memory that execute one or more software or firmware programs, integrated logic circuits, and/or other devices that can provide the above-mentioned functions.
  • the network device 80 may adopt the form shown in FIG. 8.
  • the processor 601 of FIG. 8 may call the computer stored in the memory 602 to execute instructions, so that the network device 80 executes the method executed by the network device in the method embodiment corresponding to FIG. 2 or FIG. 7A.
  • the functions/implementation processes of the receiving unit 801, the processing unit 802, and the sending unit 803 in FIG. 10 may be implemented by the processor 601 in FIG. 8 mobilizing the computer stored in the memory 602 to execute instructions.
  • the function/implementation process of the processing unit 802 in FIG. 10 may be implemented by the processor 601 in FIG. 8 calling the computer execution instructions stored in the memory 602, and the function/implementation of the receiving unit 801 and the sending unit 803 in FIG. The process can be realized by the transceiver 604 in FIG. 8.
  • the network device provided by the embodiment of the present application can be used to perform the method of the embodiment corresponding to FIG. 2 or FIG. 7A, for the technical effects that can be obtained by the embodiment of the present application, refer to the method embodiment corresponding to FIG. 2 or FIG. 7A, here No longer.
  • FIG. 11 shows a schematic structural diagram of a data analysis network element.
  • an embodiment of the data analysis network element 90 provided by the present application may include: a receiving unit 901, a processing unit 902, and a sending unit 903;
  • the receiving unit 901 is configured to receive a request sent by a slice management network element, where the request includes service experience requirement information for the first network slice;
  • the processing unit 902 is configured to determine first area information and/or first time information corresponding to the service experience requirement information;
  • the sending unit 903 is configured to send a response to the slice management network element, where the response includes first area information and/or first time information corresponding to the service experience requirement information.
  • the data analysis network element can determine the problematic first area information and/or first time information in the first network slice, thereby facilitating the network device to perform resource scheduling more accurately.
  • the processing unit 902 is configured to determine first service experience information of the first network slice corresponding to the first area information and/or the first time information; then the The response also includes first service experience information of the first network slice corresponding to the first area information and/or the first time information.
  • the service experience requirement information of the first network slice includes positive service experience requirement information and/or negative service experience requirement information
  • the positive service experience requirement information is that the excess meets the first
  • the service level agreement requires filtering information of the information
  • the negative service experience requirement information is filtering information that does not satisfy the second service level agreement requirement information.
  • the processing unit 902 is further configured to: when the request further includes third area information, the third area indicated by the third area information includes the first area information In the first area, the first area information corresponding to the service experience requirement information is obtained in the third area according to the third area information.
  • the processing unit 902 is further configured to include third time information in the request, and the third time indicated by the third time information includes the first time information. At the first time, according to the third time information, the first time information corresponding to the service experience requirement information is obtained from the third time information.
  • the service experience requirement information of the first network slice includes at least one of the following information: the user number requirement of the first network slice, the average user experience MOS filtering requirement of the service, The filtering requirement of the user satisfaction ratio of the service, where the user satisfaction ratio of the service is the ratio of the number of users whose user experience corresponding to the service is not less than a preset value to the total number of users of the service.
  • the first service experience information of the first network slice includes at least one of the following information: user number information of the first network slice, service user number information, and service average User experience MOS information and user satisfaction ratio information of a service, wherein the user satisfaction ratio of the service is the ratio of the number of users whose user experience corresponding to the service is not less than a preset value to the total number of users of the service.
  • the data analysis network element 90 provided by the embodiment of the present application is used to execute the method performed by the slice management network element in the method embodiment corresponding to FIG. 2 or FIG. 7A, so the embodiment of the present application may be implemented with reference to the method corresponding to FIG. 2 or FIG. 7A Understand the relevant parts of the example.
  • the data analysis network element 90 is presented in the form of dividing each functional unit in an integrated manner.
  • the "functional unit” herein may refer to an application-specific integrated circuit, a processor and memory that execute one or more software or firmware programs, integrated logic circuits, and/or other devices that can provide the above-mentioned functions.
  • the data analysis network element 90 may adopt the form shown in FIG. 8.
  • the processor 601 of FIG. 8 may invoke the computer execution instruction stored in the memory 602 to cause the data analysis network element 90 to execute the method performed by the data analysis network element in the method embodiment corresponding to FIG. 2 or FIG. 7A.
  • the functions/implementation processes of the receiving unit 901, the processing unit 902, and the sending unit 903 in FIG. 11 may be implemented by activating the computer stored in the memory 602 to execute instructions by the processor 601 in FIG.
  • the function/implementation process of the processing unit 902 in FIG. 11 can be implemented by the processor 601 in FIG. 8 calling the computer execution instructions stored in the memory 602, and the function/implementation of the receiving unit 901 and the sending unit 903 in FIG.
  • the process can be realized by the transceiver 604 in FIG. 8.
  • the network device provided by the embodiment of the present application can be used to perform the method of the embodiment corresponding to FIG. 2 or FIG. 7A, for the technical effects that can be obtained by the embodiment of the present application, refer to the method embodiment corresponding to FIG. 2 or FIG. 7A, here No longer.
  • FIG. 12 shows a schematic structural diagram of a network device.
  • an embodiment of the network device 100 of the present application may include: a receiving unit 1001, a processing unit 1002, and a sending unit 1003;
  • the receiving unit 1001 is configured to receive resource configuration information of a first network slice sent by a network management network element, where the resource configuration information includes maximum resource configuration information and/or guaranteed resource configuration information, and the maximum resource configuration information is used to indicate the A maximum usable resource of the first network slice, and the guaranteed resource configuration information is used to indicate a guaranteed usable resource of the first network slice;
  • the processing unit 1002 is configured to schedule resources for the first network slice according to the resource configuration information of the first network slice.
  • the resources of the network slice do not need to be bound to the network slice.
  • the resources that can be used can be preferentially used within the range of the maximum available resources, which ensures that the network slice has The availability of resources also increases the flexibility of resources.
  • the first network slice guarantees that resources that can be used are allowed to be used by the second network slice.
  • the maximum resource configuration information is maximum air interface resource configuration information and/or guaranteed resource configuration information is guaranteed air interface resource configuration information.
  • the processing unit 1002 is configured to, based on the guaranteed resource configuration information, preferentially guarantee scheduling of the guaranteed availability of the first network slice based on the guaranteed resource configuration information Resources.
  • the processing unit 1002 is configured to use the maximum resource configuration information and/or guaranteed resource configuration information as the maximum resource configuration information and/or guaranteed resource configuration information corresponding to the first time; Maximum resource configuration information and/or guaranteed resource configuration information corresponding to a time schedules resources for the first network slice at the first time.
  • the processing unit 1002 is configured to use the maximum resource configuration information and/or guaranteed resource configuration information as the maximum resource configuration information and/or guaranteed resource configuration information corresponding to the first area, according to the Maximum resource configuration information and/or guaranteed resource configuration information corresponding to an area schedule resources for the first network slice in the first area.
  • the receiving unit 1001 is configured to receive slice quality information corresponding to the first network slice sent by a slice management network element, and the slice quality information includes service experience information of the first network slice And/or satisfaction degree information of the service experience information of the first network slice relative to the target service level agreement requirements;
  • the processing unit 1002 is configured to adjust resources scheduled for the first network slice according to the slice quality information.
  • the slice quality information corresponding to the first network slice includes service experience information corresponding to the second area of the first network slice and/or service experience information corresponding to the second area is relatively Information about the degree of satisfaction required by the target service level agreement.
  • the second area is an area that cannot meet or exceed the requirements of the target service level agreement.
  • the slice quality information corresponding to the first network slice includes service experience information corresponding to the second time of the first network slice and/or relative service experience information corresponding to the second time Information about the degree of satisfaction required by the target service level agreement.
  • the second time is a time that cannot meet or exceed the requirements of the target service level agreement.
  • the processing unit 1002 is configured to add resources scheduled for the first network slice if the service experience information of the first network slice cannot meet the requirements of the target service level agreement; if If the service experience information of the first network slice exceeds the requirements of the target service level agreement in excess, the resources scheduled for the first network slice are reduced.
  • the network device 100 provided by the embodiment of the present application is used to execute the method performed by the slice management network element in the method embodiment corresponding to FIG. 3, FIG. 4 or FIG. 7A, so for the embodiment of the present application, refer to FIG. 3, FIG. 4 or FIG. 7A Understand the relevant parts in the corresponding method embodiments.
  • the network device 100 is presented in the form of dividing each functional unit in an integrated manner.
  • the "functional unit” herein may refer to an application-specific integrated circuit, a processor and memory that execute one or more software or firmware programs, integrated logic circuits, and/or other devices that can provide the above-mentioned functions.
  • the network device 100 may adopt the form shown in FIG. 8.
  • the processor 601 of FIG. 8 may call the computer execution instruction stored in the memory 602 to cause the network device 100 to execute the method executed by the network device in the method embodiment corresponding to FIG. 3, FIG. 4, or FIG. 7A.
  • the functions/implementation processes of the receiving unit 1001, the processing unit 1002, and the sending unit 1003 in FIG. 12 may be implemented by activating the computer 601 stored in the memory 602 to execute instructions by the processor 601 in FIG. 8.
  • the function/implementation process of the processing unit 1002 in FIG. 12 can be implemented by the processor 601 in FIG. 8 calling the computer execution instructions stored in the memory 602, and the function/implementation process of the receiving unit 1001 and the sending unit 1003 in FIG. It can be realized by the transceiver 604 in FIG. 8.
  • the network device provided by the embodiment of the present application can be used to execute the method of the embodiment corresponding to FIG. 3, FIG. 4 or FIG. 7A, the technical effects that can be obtained by the embodiment of the present application can refer to the corresponding ones of FIG. 3, FIG. 4 or FIG. 7A The method embodiments are not repeated here.
  • FIG. 13 shows a schematic structural diagram of a network management network element.
  • an embodiment of the network management network element 110 of the present application may include: a receiving unit 1101, a processing unit 1102, and a sending unit 1103;
  • the processing unit 1102 is configured to determine resource configuration information of the first network slice, where the resource configuration information includes maximum resource configuration information and/or guaranteed resource configuration information, and the maximum resource configuration information is used to indicate that the first network slice is the largest Resources that can be used, and the guaranteed resource configuration information is used to indicate resources that the first network slice is guaranteed to use;
  • the sending unit 1103 is configured to send resource configuration information of the first network slice to the network device, where the resource configuration information is used by the network device to schedule resources for the first network slice according to the resource configuration information.
  • the resources of the network slice do not need to be bound to the network slice.
  • the resources that can be used can be preferentially used within the range of the maximum available resources, which ensures that the network slice has The availability of resources also increases the flexibility of resources.
  • the maximum resource configuration information is maximum air interface resource configuration information and/or the guaranteed resource configuration information is guaranteed air interface resource configuration information.
  • the maximum resource configuration information and/or guaranteed resource configuration information is the maximum resource configuration information and/or guaranteed resource configuration information corresponding to the first time; or, the maximum resource configuration information and/or Or the guaranteed resource configuration information is the maximum resource configuration information and/or the guaranteed resource configuration information corresponding to the first area.
  • the processing unit 1102 is configured to determine resource configuration information of the first network slice according to target service level agreement requirement information of the first network slice.
  • the processing unit 1102 is configured to acquire information about resources scheduled by the network device for the first network slice; acquire slice quality information of the first network slice, and the slice quality information Including service experience information of the first network slice and/or satisfaction degree information of the service experience information of the first network slice relative to the target service level agreement; slicing the first network according to the network device
  • the information of the scheduled resource and the slice quality information update the resource configuration information of the first network slice; the network management network element sends the updated resource configuration information to the network device.
  • the processing unit 1102 is configured to include, in the resource information, information of resources corresponding to the second area of the first network slice, and service experience information of the first network slice includes all When the service experience information corresponding to the second area of the first network slice is updated, the resource of the first network slice is updated according to the information of the resource corresponding to the second area and the service experience information corresponding to the second area Configuration information.
  • the processing unit 1102 is configured to: when the resource information includes resource information corresponding to the second time of the first network slice, and service experience information of the first network slice includes all When the service experience information corresponding to the second time of the first network slice is updated, the resource of the first network slice is updated according to the information of the resource corresponding to the second time and the service experience information corresponding to the second time Configuration information.
  • the processing unit 1102 is configured to update the maximum resource configuration information and/or guaranteed resource configuration information so that the updated maximum resource configuration information is not less than the network device is the first A resource for network slice scheduling.
  • the receiving unit 1101 is configured to obtain the slice quality information from the slice management network element or data analysis device.
  • the network management network element 110 provided by the embodiment of the present application is used to execute the method performed by the slice management network element in the method embodiment corresponding to FIG. 3, FIG. 4 or FIG. 7A, so for the embodiment of the present application, reference may be made to FIG. 3, FIG. 4 or FIG. The relevant part of the method embodiment corresponding to 7A is understood.
  • the network management network element 110 is presented in the form of dividing each functional unit in an integrated manner.
  • the "functional unit” herein may refer to an application-specific integrated circuit, a processor and memory that execute one or more software or firmware programs, integrated logic circuits, and/or other devices that can provide the above-mentioned functions.
  • the network management and network element 110 may adopt the form shown in FIG. 8.
  • the processor 601 of FIG. 8 may call the computer execution instruction stored in the memory 602 to cause the network management network element 110 to execute the method executed by the network management network element in the method embodiment corresponding to FIG. 3, FIG. 4, or FIG. 7A.
  • the functions/implementation processes of the receiving unit 1101, the processing unit 1102, and the sending unit 1103 in FIG. 13 can be implemented by activating the computer stored in the memory 602 in the processor 601 in FIG. 8 to execute instructions.
  • the function/implementation process of the processing unit 1102 in FIG. 13 can be implemented by the processor 601 in FIG. 8 calling the computer execution instructions stored in the memory 602, and the function/implementation of the receiving unit 1101 and the sending unit 1103 in FIG. The process can be realized by the transceiver 604 in FIG. 8.
  • the network management network element provided by the embodiment of the present application can be used to perform the method of the embodiment corresponding to FIG. 3, FIG. 4 or FIG. 7A, the technical effects that can be obtained by the embodiment of the present application can be referred to the correspondence of FIG. 3, FIG. 4 or FIG. 7A The method embodiment is not repeated here.
  • FIG. 14 shows a schematic structural diagram of a slice management and control network element.
  • an embodiment of the slice management network element 120 of the present application may include: a receiving unit 1201, a processing unit 1202, and a sending unit 1203;
  • the receiving unit 1201 is configured to receive the user quantity limitation information of the target network slice and the indication information sent by the network management network element, where the indication information is used to indicate the status information of the target network slice or the credibility of the user quantity limitation information degree;
  • the processing unit 1202 is configured to control the number of users served by the target network slice according to the instruction information and the user number limitation information.
  • the solution provided in this embodiment can control the number of users served by the target network slice according to the indication information and the user number limitation information, and can improve the accuracy of user number control.
  • the processing unit 1202 is configured to, when the indication information is used to indicate the status information of the target network slice, according to the control method corresponding to the status information according to the user quantity limitation information To control the number of users served by the target network slice.
  • the state information includes a test state or a stable state.
  • the control mode when the state information is a test state, the control mode is a step control mode.
  • the control mode when the state information is a stable state, the control mode is a one-time control mode.
  • the processing unit 1202 is configured to, when the indication information is used to indicate the credibility of the user quantity restriction information, correspond to the credibility according to the user quantity restriction information Control mode, which controls the number of users served by the target network slice.
  • the control mode is a step control mode.
  • the control mode when the credibility meets the credibility requirements, is a one-time control mode.
  • the receiving unit 1201 is configured to receive service level agreement requirement information of the target network slice sent by the network management network element, where the service level agreement requirement information includes the target network slice User number limit information.
  • the receiving unit 1201 is configured to receive the user quantity limitation information corresponding to the area information of the target network slice sent by the network management network element;
  • the processing unit 1202 is configured to, for the area indicated by the area information, control the number of users served by the target network slice according to the indication information and the user number restriction information corresponding to the area information.
  • the slice control network element 120 provided by the embodiment of the present application is used to execute the method performed by the slice control network element in the method embodiment corresponding to FIG. 5 or FIG. 7A, so the embodiment of the present application may be implemented with reference to the method corresponding to FIG. 5 or FIG. 7A Understand the relevant parts of the example.
  • the slice management and control network element 120 is presented in the form of dividing each functional unit in an integrated manner.
  • the "functional unit” herein may refer to an application-specific integrated circuit, a processor and memory that execute one or more software or firmware programs, integrated logic circuits, and/or other devices that can provide the above-mentioned functions.
  • the slice management and control network element 120 may adopt the form shown in FIG. 8.
  • the processor 601 of FIG. 8 may call the computer execution instruction stored in the memory 602 to cause the slice management network element 120 to execute the method executed by the slice management network element in the method embodiment corresponding to FIG. 5 or FIG. 7A.
  • the functions/implementation processes of the receiving unit 1201, the processing unit 1202, and the sending unit 1203 in FIG. 14 can be implemented by activating the computer stored in the memory 602 to execute instructions by the processor 601 in FIG. 8.
  • the function/implementation process of the processing unit 1202 in FIG. 14 may be implemented by the processor 601 in FIG. 8 calling the computer execution instructions stored in the memory 602, and the function/implementation of the receiving unit 1201 and the sending unit 1203 in FIG. 14
  • the process can be realized by the transceiver 604 in FIG. 8.
  • the slice management and control network element provided by the embodiment of the present application can be used to perform the method of the embodiment corresponding to FIG. 5 or FIG. 7A, for the technical effects that can be obtained by the embodiment of the present application, refer to the method embodiment corresponding to FIG. 5 or FIG. 7A. I won't repeat them here.
  • FIG. 15 shows a schematic structural diagram of a network management network element.
  • an embodiment of the network management network element 130 of the present application may include: a receiving unit 1301, a processing unit 1302, and a sending unit 1303;
  • the processing unit 1302 is configured to determine the user quantity limitation information and the indication information of the target network slice, where the indication information is used to indicate the status information of the target network slice or the credibility of the user quantity limitation information;
  • the sending unit 1303 is configured to send the number limitation information of the target network slice to the slice management network element and the indication information, the indication information and the number limitation information of the user are used for the slice management network element Control the number of users served by the target network slice.
  • the solution provided by the present application can control the number of users served by the target network slice according to the instruction information and the user number limitation information, and can improve the accuracy of user number control.
  • the processing unit 1302 is configured to obtain service level agreement requirement information of the target network slice; and determine the user quantity limit information of the target network slice according to the service level agreement requirement information.
  • the sending unit 1303 is configured to send to the slice management network element the area information of the target network slice and the user quantity limitation information corresponding to the area information, the area information and all The quantity limitation information corresponding to the area information is used by the slice management network element to control the target network within the range indicated by the quantity limitation information corresponding to the area information for the area indicated by the area information The number of users served by slicing.
  • the sending unit 1303 is configured to send the time information of the target network slice and the user quantity limitation information corresponding to the time information to the slice management network element, and the time information and all The user quantity limitation information corresponding to the time information is used for controlling the time served by the target network slice within the range indicated by the user quantity limitation information corresponding to the time information for the time indicated by the time information Quantity.
  • the network management network element 130 provided by the embodiment of the present application is used to execute the method performed by the network management network element in the method embodiment corresponding to FIG. 5 or FIG. 7A, so for the embodiment of the present application, reference may be made to the method embodiment corresponding to FIG. 5 or FIG. 7A To understand the relevant parts.
  • the network management network element 130 is presented in the form of dividing each functional unit in an integrated manner.
  • the "functional unit” herein may refer to an application-specific integrated circuit, a processor and memory that execute one or more software or firmware programs, integrated logic circuits, and/or other devices that can provide the above-mentioned functions.
  • a person skilled in the art may think that the network management network element 130 may adopt the form shown in FIG. 8.
  • the processor 601 of FIG. 8 may call the computer execution instruction stored in the memory 602 to cause the network management network element 130 to execute the method executed by the network management network element in the method embodiment corresponding to FIG. 5 or FIG. 7A.
  • the functions/implementation processes of the receiving unit 1301, the processing unit 1302, and the sending unit 1303 in FIG. 15 can be implemented by activating the computer 601 stored in the memory 602 to execute instructions by the processor 601 in FIG.
  • the function/implementation process of the processing unit 1302 in FIG. 15 may be implemented by the processor 601 in FIG. 8 calling a computer execution instruction stored in the memory 602, and the function/implementation of the receiving unit 1301 and the sending unit 1303 in FIG. 15
  • the process can be realized by the transceiver 604 in FIG. 8.
  • the network management network element provided by the embodiment of the present application can be used to perform the method of the embodiment corresponding to FIG. 5 or FIG. 7A, for the technical effects that can be obtained by the embodiment of the present application, refer to the method embodiment corresponding to FIG. 5 or FIG. 7A. I will not repeat them here.
  • FIG. 16 shows a schematic structural diagram of a slice management and control network element.
  • an embodiment of the slice management network element 140 of the present application may include: a receiving unit 1401, a processing unit 1402, and a sending unit 1403;
  • the processing unit 1402 is configured to determine that the service experience information of the first network slice cannot meet or exceed the target service level agreement information of the first network slice due to the first network domain;
  • the sending unit 1403 is configured to send slice quality information of the first network slice to the network device in the first network domain, and the slice quality information is used by the network device to determine the first slice according to the slice quality information.
  • Network slice scheduling resources are configured to send slice quality information of the first network slice to the network device in the first network domain.
  • the slice management network element can first accurately locate the service experience information of the first network slice that cannot meet the target service level agreement. The reason is that it comes from a network domain (such as the access network domain), and then The network device in the network domain provides slice quality information of the first network slice, so that the network device in the network domain adjusts resource scheduling.
  • This method can avoid blindly adjusting the resource scheduling situation of other normally working network domains, and improve the accuracy of resource scheduling.
  • the receiving unit 1401 is configured to obtain slice quality information of the first network slice from a data analysis network element or a network management network element.
  • the processing unit 1402 is further configured to, when the slice quality information of the first network slice is service experience information of the first network slice, according to the service experience of the first network slice The information determines the satisfaction degree information of the service experience information of the first network slice relative to the target service level agreement requirement information.
  • the processing unit 1402 is further configured to determine that the service experience information of the first network slice cannot meet or exceed the target service level agreement information of the first network slice.
  • the receiving unit 1401 is configured to obtain indication information from the network management network element, where the indication information is used to indicate that the service experience information of the first network slice cannot be satisfied or exceeds the first The reason for the target service level agreement information of a network slice lies in the first network domain;
  • the processing unit 1402 is further configured to determine, according to the indication information, that the service experience information of the first network slice fails to meet or exceeds the target service level agreement information of the first network slice due to the first network domain.
  • the sending unit 1403 is used to send a request message to the network management network element, where the request message is used to request that the service experience information of the first network slice cannot be satisfied or exceeds the requirement The network domain of the target service level agreement information of the first network slice;
  • the receiving unit 1401 is configured to receive a response message sent by the network management network element, where the response message includes the instruction information.
  • the receiving unit 1401 is configured to obtain credibility information from the network management network element, and the credibility information is used to indicate the credibility of the indication information;
  • the processing unit 1402 is configured to determine, according to the credibility information and the indication information, that the service experience information of the first network slice cannot meet or exceed the target service level agreement information of the first network slice because the first Network domain.
  • the service experience information includes service experience information of the first network slice corresponding to area information and/or time information.
  • the satisfaction degree information includes unsatisfiability, satisfaction, or excess satisfaction.
  • the processing unit 1402 is used to:
  • One of the at least one service level agreement requirement information is determined as the target service level agreement requirement information.
  • the first network domain includes at least one of the following: an access network domain, a core network domain, and a transmission network domain.
  • the network device includes at least one of the following devices: an access network device, a core network device for allocating user plane or control plane resources, and a transmission network device.
  • the service level agreement requirement information includes at least one of the following information: user number requirement information of the first network slice, request information of the average user experience of the service, user satisfaction of the service Requirement information of the ratio, wherein the user satisfaction ratio of the service is the ratio of the number of users whose user experience corresponding to the service is not worse than the preset value to the total number of users of the service.
  • the slice management and control network element 140 provided in the embodiment of the present application is used to execute the method performed by the slice management and control network element in the method embodiment corresponding to FIG. 7B, so the embodiment of the present application may refer to the relevant part in the method embodiment corresponding to FIG. 7B. understanding.
  • the slice management network element 140 is presented in the form of dividing each functional unit in an integrated manner.
  • the "functional unit” herein may refer to an application-specific integrated circuit, a processor and memory that execute one or more software or firmware programs, integrated logic circuits, and/or other devices that can provide the above-mentioned functions.
  • the slice management and control network element 140 may adopt the form shown in FIG. 8.
  • the processor 601 of FIG. 8 may call the computer execution instruction stored in the memory 602 to cause the slice management network element 140 to execute the method executed by the slice management network element in the method embodiment corresponding to FIG. 7B.
  • the functions/implementation processes of the receiving unit 1401, the processing unit 1402, and the sending unit 1403 in FIG. 16 can be implemented by the processor 601 in FIG. 8 mobilizing the computer stored in the memory 602 to execute instructions.
  • the function/implementation process of the processing unit 1402 in FIG. 16 may be implemented by the processor 601 in FIG. 8 calling the computer execution instructions stored in the memory 602, and the function/implementation of the receiving unit 1401 and the sending unit 1403 in FIG. The process can be realized by the transceiver 604 in FIG. 8.
  • the slice management and control network element provided by the embodiment of the present application can be used to execute the method corresponding to the embodiment of FIG. 7B, for the technical effects that can be obtained by the embodiment of the present application, refer to the method embodiment corresponding to FIG. 7B, and details are not described herein again.
  • FIG. 17 shows a schematic structural diagram of a network management network element.
  • an embodiment of the network management network element 150 of the present application may include: a receiving unit 1501, a processing unit 1502, and a sending unit 1503;
  • the processing unit 1502 is configured to determine that the service experience information of the first network slice cannot meet or exceed the target service level agreement information of the first network slice due to the first network domain;
  • Indication information is sent to the slice management network element, where the indication information is used to indicate that the service experience information of the first network slice fails to meet or exceeds the target service level agreement information of the first network slice due to the first network domain.
  • the network management network element may notify the slice management network element of the first network domain where the service experience information of the first network slice cannot be satisfied or exceeds the target service level agreement information of the first network slice, For example: access to the network domain, so as to avoid blindly adjusting the resource scheduling situation of other normally working network domains, and improve the accuracy of resource scheduling.
  • the processing unit 1502 is also used to determine credibility information, and the credibility information is used to indicate the credibility of the indication information;
  • the sending unit 1503 is further configured to send the credibility information to the slice management and control network element.
  • the receiving unit 1501 is configured to obtain slice quality information of a first network slice from a data analysis network element, where the slice quality information includes at least one of the following information: the first network Satisfaction information of the sliced service experience information and the first network sliced service experience information relative to the target service level agreement requirement information.
  • the processing unit 1502 is further configured to, when the slice quality information of the first network slice is service experience information of the first network slice, according to the service experience of the first network slice The information determines the satisfaction degree information of the service experience information of the first network slice relative to the target service level agreement requirement information.
  • the processing unit 1502 is further configured to determine that the service experience information of the first network slice cannot meet or exceed the first network slice target service level agreement information.
  • the service experience information includes service experience information of the first network slice corresponding to area information and/or time information.
  • the receiving unit 1501 is further configured to receive a request message sent by the slice management and control network element, where the request message is used to request that the service experience information cannot be satisfied or exceeds the first Network domain of target service level agreement information of network slice;
  • the sending unit 1503 is further configured to send a response message to the slice management network element, where the response message includes the indication information.
  • processing unit 1502 is also used to:
  • One of the at least one service level agreement requirement information is determined as the target service level agreement requirement information.
  • the first network domain includes at least one of the following: an access network domain, a core network domain, and a transmission network domain.
  • the service level agreement requirement information includes at least one of the following information: user number requirement information of the first network slice, request information of the average user experience of the service, user satisfaction of the service Requirement information of the ratio, wherein the user satisfaction ratio of the service is the ratio of the number of users whose user experience corresponding to the service is not worse than the preset value to the total number of users of the service.
  • the network management network element 150 provided in the embodiment of the present application is used to execute the method performed by the network management network element in the method embodiment corresponding to FIG. 7B, so the embodiment of the present application can be understood by referring to the relevant part in the method embodiment corresponding to FIG. 7B.
  • the network management network element 150 is presented in the form of dividing each functional unit in an integrated manner.
  • the "functional unit” herein may refer to an application-specific integrated circuit, a processor and memory that execute one or more software or firmware programs, integrated logic circuits, and/or other devices that can provide the above-mentioned functions.
  • the network management network element 150 may adopt the form shown in FIG. 8.
  • the processor 601 in FIG. 8 may invoke the computer execution instruction stored in the memory 602 to cause the network management network element 150 to execute the method performed by the network management network element in the method embodiment corresponding to FIG. 7B.
  • the functions/implementation processes of the receiving unit 1501, the processing unit 1502, and the sending unit 1503 in FIG. 17 can be implemented by activating the computer 601 stored in the memory 602 to execute instructions by the processor 601 in FIG. 8.
  • the function/implementation process of the processing unit 1502 in FIG. 17 may be implemented by the processor 601 in FIG. 8 calling a computer execution instruction stored in the memory 602, and the function/implementation of the receiving unit 1501 and the sending unit 1503 in FIG.
  • the process can be realized by the transceiver 604 in FIG. 8.
  • the network management network element provided by the embodiment of the present application can be used to perform the method of the embodiment corresponding to FIG. 7B, for the technical effects that can be obtained by the embodiment of the present application, refer to the method embodiment corresponding to FIG. 7B, and details are not described here.
  • FIG. 18 shows a schematic structural diagram of a network device.
  • an embodiment of the network device 160 of the present application may include: a receiving unit 1601, a processing unit 1602, and a sending unit 1603;
  • the processing unit 1602 is configured to determine the state information of the first network slice.
  • the state information of the first network slice includes that the first network slice is in an unsigned SLA state or has been signed SLA state;
  • the processing unit 1602 is further configured to schedule resources for the first network slice according to the state information of the first network slice.
  • the processing unit 1602 is configured to schedule air interface resources for the first network slice according to the state information of the first network slice when the network device is an access network device.
  • the processing unit 1602 is further configured to determine the state information of the second network slice as that the second network slice is in an SLA signed state;
  • the processing unit 1602 is configured to schedule resources for the first network slice when the state information of the first network slice is that the first network slice is in an unsigned SLA state, deprioritized to the second network slice .
  • the processing unit 1602 is further configured to determine the state information of the second network slice as that the second network slice is in an unsigned SLA state;
  • the processing unit 1602 is configured to schedule resources for the first network slice prior to the second network slice when the state information of the first network slice is the signed SLA state of the first network slice.
  • the processing unit 1602 is configured to determine the status information of the first network slice according to the status indication information of the first network slice sent by a network management network element, where the status indication information includes all The status information of the first network slice is described.
  • the receiving unit 1601 is configured to receive resource configuration information of the first network slice sent by a network management network element, where the resource configuration information includes maximum resource configuration information and/or guaranteed resource configuration information,
  • the maximum resource configuration information is used to indicate a maximum usable resource of the first network slice, and the guaranteed resource configuration information is used to indicate a guaranteed resource of the first network slice; the network device according to the first
  • the resource configuration information of a network slice and the state information of the first network slice are scheduling resources for the first network slice.
  • the resource configuration information may also include status information of the first network slice.
  • the maximum resource configuration information is maximum air interface resource configuration information and/or guaranteed resource configuration information is guaranteed air interface resource configuration information.
  • the network device 160 provided in the embodiment of the present application is used to execute the method performed by the network device in the method embodiment corresponding to FIG. 7C, so the embodiment of the present application can be understood with reference to the relevant parts in the method embodiment corresponding to FIG. 7C.
  • the network device 160 is presented in the form of dividing each functional unit in an integrated manner.
  • the "functional unit” herein may refer to an application-specific integrated circuit, a processor and memory that execute one or more software or firmware programs, integrated logic circuits, and/or other devices that can provide the above-mentioned functions.
  • the network device 160 may take the form shown in FIG. 8.
  • the processor 601 of FIG. 8 may call the computer stored in the memory 602 to execute instructions, so that the network device 160 executes the method executed by the network device in the method embodiment corresponding to FIG. 7C.
  • the functions/implementation processes of the receiving unit 1601, the processing unit 1602, and the sending unit 1603 in FIG. 18 may be implemented by activating the computer stored in the memory 602 in the processor 601 in FIG. 8 to execute instructions.
  • the function/implementation process of the processing unit 1602 in FIG. 18 may be implemented by the processor 601 in FIG. 8 calling a computer execution instruction stored in the memory 602, and the function/implementation of the receiving unit 1601 and the sending unit 1603 in FIG. 18 The process can be realized by the transceiver 604 in FIG. 8.
  • the network device provided by the embodiment of the present application can be used to execute the method corresponding to the embodiment of FIG. 7C, the technical effects that can be obtained by the embodiment of the present application can refer to the method embodiment corresponding to FIG. 7C, and details are not described herein again.
  • FIG. 19 shows a schematic structural diagram of a network management network element.
  • an embodiment of the network management network element 170 of the present application may include: a receiving unit 1701, a processing unit 1702, and a sending unit 1703;
  • the processing unit 1702 is configured to determine the state information of the first network slice, where the state information of the first network slice includes that the first network slice is in an unsigned SLA state or has been signed SLA state;
  • the sending unit 1703 is configured to send the state information of the first network slice to a network device, and the state information of the first network slice is used by the network device to schedule resources for the first network slice.
  • the network management network element can promptly notify the network device of the state information of the first network slice, so that the network device performs corresponding resource scheduling according to the SLA state of the first network slice.
  • the processing unit 1702 is configured to determine resource configuration information of the first network slice, the resource configuration information includes maximum resource configuration information and/or guaranteed resource configuration information, and the maximum resource configuration The information is used to indicate the maximum usable resource of the first network slice, and the guaranteed resource configuration information is used to indicate the guaranteed resource of the first network slice; the network management network element sends the resource to the network device Resource configuration information of the first network slice, where the resource configuration information is used by the network device to schedule resources for the first network slice according to the resource configuration information.
  • the resource configuration information may also include status information of the first network slice.
  • the maximum resource configuration information is maximum air interface resource configuration information and/or guaranteed resource configuration information is guaranteed air interface resource configuration information.
  • the resource configuration information includes status information of the first network slice.
  • the network management network element 170 provided in the embodiment of the present application is used to execute the method performed by the network management network element in the method embodiment corresponding to FIG. 7C, so the embodiment of the present application can be understood by referring to the relevant part in the method embodiment corresponding to FIG. 7C.
  • the network management network element 170 is presented in the form of dividing each functional unit in an integrated manner.
  • the "functional unit” herein may refer to an application-specific integrated circuit, a processor and memory that execute one or more software or firmware programs, integrated logic circuits, and/or other devices that can provide the above-mentioned functions.
  • the network management network element 170 may adopt the form shown in FIG. 8.
  • the processor 601 of FIG. 8 may call the computer execution instruction stored in the memory 602 to cause the network management network element 170 to execute the method executed by the network management network element in the method embodiment corresponding to FIG. 7C.
  • the functions/implementation processes of the receiving unit 1701, the processing unit 1702, and the sending unit 1703 in FIG. 19 can be implemented by activating the computer stored in the memory 602 to execute instructions by the processor 601 in FIG. 8.
  • the function/implementation process of the processing unit 1702 in FIG. 19 can be implemented by the processor 601 in FIG. 8 calling the computer execution instructions stored in the memory 602, and the function/implementation of the receiving unit 1701 and the sending unit 1703 in FIG. 19
  • the process can be realized by the transceiver 604 in FIG. 8.
  • the network management network element provided by the embodiment of the present application can be used to perform the method of the embodiment corresponding to FIG. 7C, for the technical effects that can be obtained by the embodiment of the present application, refer to the method embodiment corresponding to FIG. 7C, and details are not described herein again.
  • the communication connection of each component that is, the processing unit (or processor), the storage unit (or memory), and the transceiver unit (transceiver) communicate with each other through an internal connection channel to transfer control and /Or data signal.
  • the above method embodiments of the present application may be applied to a processor, or the processor may implement the steps of the above method embodiments.
  • the processor may be an integrated circuit chip with signal processing capabilities.
  • the steps of the foregoing method embodiments may be completed by instructions in the form of hardware integrated logic circuits or software in the processor.
  • the above processor may be a central processing unit (CPU), a network processor (NP) or a combination of CPU and NP, a digital signal processor (DSP), an application specific integrated circuit (application specific integrated circuit (ASIC), ready-made programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • CPU central processing unit
  • NP network processor
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA ready-made programmable gate array
  • the 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 this application can be directly embodied and executed by a hardware decoding processor, or can be executed and completed by a combination of hardware and software modules in the decoding processor.
  • the software module may be located in a mature storage medium in the art, such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an electrically erasable programmable memory, and a 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 apparatus may include multiple processors or the processor includes multiple processing units.
  • the processor may be a single-CPU processor or a multi-CPU processor.
  • the memory is used to store computer instructions executed by the processor.
  • the memory may be a storage circuit or a memory.
  • the memory may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be a read-only memory, a programmable read-only memory, an erasable programmable read-only memory, an electrically erasable programmable read-only memory, or a flash memory.
  • Volatile memory can be random access memory, which acts as external cache memory.
  • the memory may be independent of the processor, or may be a storage unit in the processor, which is not limited herein. Although only one memory is shown in the figure, the device may also include multiple memories or the memory includes multiple storage units.
  • the transceiver is used to implement content interaction between the processor and other units or network elements.
  • the transceiver may be a communication interface of the device, a transceiver circuit or a communication unit, or a transceiver.
  • the transceiver may also be a communication interface of the processor or a transceiver circuit.
  • the transceiver may be a transceiver chip.
  • the transceiver may also include a sending unit and/or a receiving unit.
  • the transceiver may include at least one communication interface.
  • the transceiver may also be a unit implemented in software.
  • the processor may interact with other units or network elements through the transceiver. For example, the processor obtains or receives content from other network elements through the transceiver. If the processor and the transceiver are physically separate components, the processor may interact with other units of the device without going through the transceiver.
  • the processor, the memory, and the transceiver may be connected to each other through a bus.
  • the bus may be a peripheral component interconnection (PCI) bus or an extended industry standard architecture (EISA) bus.
  • PCI peripheral component interconnection
  • EISA extended industry standard architecture
  • the bus can be divided into an address bus, a data bus, and a control bus.
  • names of request messages, response messages, and other various messages are used. However, these messages are only used to illustrate the content to be carried or the functions to be implemented.
  • the application does not limit the specific names of the messages, for example, the first message, the second message, and the third message may also be used.
  • These messages can be specific messages or some fields in the message. These messages can also represent various service-oriented operations.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a dedicated computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be from a website site, computer, server or data center Transmission to another website, computer, server or data center via wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.).
  • wired such as coaxial cable, optical fiber, digital subscriber line (DSL)
  • wireless such as infrared, wireless, microwave, etc.
  • the computer-readable storage medium may be any available medium that can be stored by a computer or a data storage device including a server, a data center, and the like integrated with one or more available media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, Solid State Disk (SSD)), or the like.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Electrotherapy Devices (AREA)
  • Paper (AREA)
  • Control Of Motors That Do Not Use Commutators (AREA)

Abstract

本申请实施例公开了一种网络切片的资源调度的方法，包括：切片管控网元向数据分析网元发送请求，请求包括对第一网络切片的服务体验要求信息；接收数据分析网元发送的响应，响应中包括与服务体验要求信息对应的第一网络切片的第一区域信息和/或第一时间信息；根据第一区域信息和/或第一时间信息向网络设备发送第二区域信息和/或第二时间信息，网络设备根据第二区域信息和/或第二时间信息为第一网络切片调度资源。本申请实施例中的技术方案由于网络设备在为第一网络切片调度资源时，可以根据存在问题的第二区域信息和/或第二时间信息做资源调度，提高了资源调度的准确度和利用率，也提高网络切片的性能。

Description

一种网络切片的资源调度的方法及设备
本申请要求于2019年1月8日提交中国专利局、申请号为201910017032.5、发明名称为“一种网络切片的资源调度的方法及设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
本申请要求于2019年1月23日提交中国专利局、申请号为201910070695.3、发明名称为“一种网络切片的资源调度的方法及设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，具体涉及一种网络切片的资源调度的方法及设备。
背景技术
第五代(the fifth gen generation，5G)网络引入了网络切片(network slice，NS)的概念，以应对不同通信业务对网络性能的不同需求，即5G网络将实际网络进行资源和功能的划分，形成不同的网络切片以满足这些不同的需求，这样可以降低网络运营投资成本，丰富网络运营模式。
目前，对于不同租户的网络切片，网管网元根据每个租户对服务水平的要求，确定不同租户的服务水平协议(service level agreement，SLA)模板，并根据SLA模板部署相应的网络切片。但是，网管网元仅根据每个租户对服务水平的要求确定的SLA模板的粒度很粗，很难保障网络切片的性能。同时，网管网元为不同租户的网络切片分配网络资源时，只能根据SLA模板确定大致的资源部署情况，这样很可能会造成资源浪费或部署资源不足的问题，从而降低网络切片的性能。
发明内容
本申请实施例提供一种网络切片的资源调度的方法，用于解决现有技术中在为网络切片分配网络资源时存在资源浪费，网络切片性能低的问题。本申请实施例还提供了相应的设备。
本申请第一方面提供一种网络切片的资源调度的方法，该方法可以包括：切片管控网元向数据分析网元发送请求，所述请求包括对第一网络切片的服务体验要求信息；所述切片管控网元接收所述数据分析网元发送的响应，所述响应中包括与所述服务体验要求信息对应的所述第一网络切片的第一区域信息和/或第一时间信息；所述切片管控网元根据所述第一区域信息和/或第一时间信息向网络设备发送第二区域信息和/或第二时间信息，所述第二区域信息和/或第二时间信息用于所述网络设备根据所述第二区域信息和/或第二时间信息为所述第一网络切片调度资源。
切片管控网元是指具备管理和控制网络切片的用户接入、资源部署、功能执行的网元，其可以位于运营商网络的控制面，例如切片管控网元为网络切片选择功能网元(network slice selection function，NSSF)；也可以位于运营商网络的管理面，例如切片管控网元为运行管理和维护网元(operation,administration,and maintenance，OAM)。所述网络设备包括以下设备的至少一个：接入网设备、用于分配用户面或控制面资源的核心网设 备、传输网设备和网管网元，在切片管控网元是NSSF时，网管网元可以是OAM。第二区域信息可以与第一区域信息相同，也不可以不相同，第二时间信息可以与第一时间信息相同，也可以不相同。由上述第一方面可知，本申请使网络设备可以根据第二区域信息和/或第二时间信息做资源调度，提高了资源调度的准确度和网络资源的利用率，也提高了网络切片的性能。
一种可能的实现方式，结合上述第一方面，在第一方面的第一种可能的实现方式中，所述响应还可以包括所述第一区域信息和/或所述第一时间信息所对应的所述第一网络切片的第一服务体验信息，该方法可以包括：所述切片管控网元根据第一服务体验信息确定所述第二区域信息和/或所述第二时间信息。
第二区域信息可以是第一区域信息中服务体验最差的区域，第二时间信息也可以与第一时间信息中服务体验最差的时间。这样，就可以优先或重点为这些服务体验最差的区域或时间增加资源调度，从而进一步提高资源调度的准确度和利用率。相反，第二区域信息也可以是第一区域信息中服务体验最好的区域，第二时间信息也可以与第一时间信息中服务体验最好的时间。这样，就可以优先或重点为这些服务体验最好的区域或时间减少资源调度，从而进一步提高资源调度的准确度和利用率。
一种可能的实现方式，结合上述第一方面或第一方面第一种可能的实现方式，在第一方面的第二种可能的实现方式中，该方法还可以包括：所述切片管控网元向所述网络设备发送所述第二区域信息和/或所述第二时间信息对应的切片质量信息，其中，所述切片质量信息包括以下信息的至少一项：所述第二区域信息和/或所述第二时间信息的对应所述第一网络切片的第二服务体验信息、所述第二服务体验信息相对于所述第一网络切片的目标服务水平协议要求信息的满足程度信息。
第二服务体验信息可以是(Quality of Experience，QoE)信息，满足程度信息可以为fulfilment信息,目标服务水平协议要求信息可以为SLA要求信息。由上述第二种可能的实现方式可知，将第二服务体验信息和满足程度信息进一步发送给网络设备，可以利于网络设备做出更准确的资源调度。
一种可能的实现方式，结合上述第一方面、第一方面第一种或第二种可能的实现方式，在第一方面的第三种可能的实现方式中，当所述网络设备为接入网设备时，所述第二区域信息用于所述接入网设备根据所述第二区域信息为所述第一网络切片调度接入网资源，所述第二时间信息用于所述接入网设备根据所述第二时间信息为所述第一网络切片调度接入网资源。由上述第三种可能的实现方式可知，接入网络设备可以根据第二区域信息和/或第二时间信息为第一网络切片调度更准确的接入网资源。
一种可能的实现方式，结合上述第一方面第二种可能的实现方式，在第一方面的第四种可能的实现方式中，所述满足程度信息包括无法满足、满足或者超额满足。其中，无法满足指的是第二服务体验信息不满足所述第一网络切片的目标服务水平协议要求信息，满足指的是第二服务体验信息达到了所述第一网络切片的目标服务水平协议要求信息的要求，超额满足指的是第二服务体验信息超出了所述第一网络切片的目标服务水平协议要求信息。由该第四种可能的实现方式可知，满足程度信息可以使网络资源的调度更准确。
一种可能的实现方式，结合上述第一方面、第一方面第一种至第四种中任一可能的实现方式，在第一方面的第五种可能的实现方式中，所述请求中还可以包括第三区域信息时，所述第三区域信息所指示的第三区域包括所述第一区域信息所指示的第一区域，所述第三区域信息用于向所述数据分析网元请求所述第三区域中与所述服务体验要求信息对应的所述第一区域信息。由该第五种可能的实现方式可知，在请求中包括第三区域信息，可以缩小确定第一区域的范围，从而提高了确定第一区域的效率，从而也提高了资源调度的效率。
一种可能的实现方式，结合上述第一方面、第一方面第一种至第五种中任一可能的实现方式，在第一方面的第六种可能的实现方式中，所述请求中还可以包括第三时间信息时，所述第三时间信息所指示的第三时间包括所述第一时间信息所述指示的第一时间，所述第三时间信息用于向所述数据分析网元请求所述第三时间中与所述服务体验要求信息对应的所述第一时间信息。由该第六种可能的实现方式可知，在请求中包括第三时间信息，可以缩小确定第一时间的范围，从而提高了确定第一时间的效率，从而也提高了资源调度的效率。
一种可能的实现方式，结合上述第一方面、第一方面第一种至第六种中任一可能的实现方式，在第一方面的第七种可能的实现方式中，所述切片管控网元向数据分析网元发送请求之前，所述方法还可以包括：所述切片管控网元获取所述第一网络切片的第三服务体验信息；若所述第三服务体验信息与所述目标服务水平协议要求信息不对应，则所述切片管控网元确定所述第一网络切片的服务体验要求信息，所述第一网络切片的服务体验要求信息对应于所述目标服务水平协议要求。由该第七种可能的实现方式可知，若所述第三服务体验信息与所述目标服务水平协议要求信息不对应，则可以确定需要进行如第一方面所述的资源调整的方法，从而提高资源调度的准确性。
第三服务体验信息可以是整个网络切片的服务体验信息，也可以不是整个网络切片的服务体验信息，而是网络切片的某个区域或时间(如第四区域或第四时间)对应的服务体验信息。
一种可能的实现方式，结合上述第一方面第七种可能的实现方式，在第一方面的第八种可能的实现方式中，该方法还可以包括：所述切片管控网元将所述第三服务体验信息与所述目标服务水平协议要求信息进行比较；若所述第三服务体验信息不满足或者超额满足所述目标服务水平协议要求信息，则所述切片管控网元确定所述第三服务体验信息与所述目标服务水平协议要求信息不对应。
一种可能的实现方式，结合上述第一方面第八种可能的实现方式，在第一方面的第九种可能的实现方式中，若所述第三服务体验信息与所述目标服务水平协议要求信息不对应，则所述切片管控网元确定所述第一网络切片的服务体验要求信息，可以包括：若所述第三服务体验信息不满足所述目标服务水平协议要求信息，则所述切片管控网元确定与不满足情况下对应的所述第一网络切片的服务体验要求信息；或者，若所述第三服务体验信息超额满足所述目标服务水平协议要求信息，则所述切片管控网元确定与超额满足情况下对应的所述第一网络切片的服务体验要求信息。
一种可能的实现方式，结合上述第一方面第八种或第九种可能的实现方式，在第一方 面的第十种可能的实现方式中，该方法还可以包括：若所述第三服务体验信息不满足所述目标服务水平协议要求信息，则所述切片管控网元减少所述第一网络切片的服务用户数量；若所述第三服务体验信息超额满足所述目标服务水平协议要求信息，则所述切片管控网元增加所述第一网络切片的服务用户数量。该种可能的实现方式中，若所述第三服务体验信息不满足所述目标服务水平协议要求信息，则说明第一网络切片所能服务的用户数量更少，则需要减少第一网络切片的服务用户数量，若超额满足，则说明第一网络切片所能服务的用户数量更多，则需要增加第一网络切片的服务用户数量。
第三服务体验信息可以是整个网络切片的服务体验信息，也可以不是整个网络切片的服务体验信息，而是网络切片的某个区域或时间(如第四区域或第四时间)对应的服务体验信息。
一种可能的实现方式，结合上述第一方面第二种至第十种中任一可能的实现方式，在第一方面的第十一种可能的实现方式中，该方法还可以包括：所述切片管控网元获取所述第一网络切片的初始服务水平协议要求信息；所述切片管控网元根据所述第一网络切片的初始服务水平协议要求信息确定至少一个服务水平协议要求信息；所述切片管控网元将所述至少一个服务水平协议要求信息中的一个确定为所述目标服务水平协议要求信息。该实现方式中，租户提供的初始服务水平协议要求信息可能包括单档要求或者多档要求，切片管控网元根据初始服务水平协议要求信息直接或间接地确定出多档要求，并可以从中选择一档作为目标服务水平协议要求信息，其实，该目标服务水平协议要求信息也可以是初始服务水平协议要求信息本身。
一种可能的实现方式，结合上述第一方面、第一方面第一种至第十一种中任一可能的实现方式，在第一方面的第十二种可能的实现方式中，所述第一网络切片的服务体验要求信息包括以下信息中的至少一项：所述第一网络切片的用户数要求、业务的平均用户体验的要求、业务的用户满意比例的要求，其中，所述业务的用户满意比例为所述业务对应的用户体验不差于预设值的用户数占该业务总用户数的比例。
一种可能的实现方式，结合上述第一方面、第一方面第一种至第十一种中任一可能的实现方式，在第一方面的另一种可能的实现方式中，所述第一网络切片的第一服务体验信息、第二服务体验信息或第三服务体验信息可以包括以下信息中的至少一项：所述第一网络切片的用户数信息、业务的用户数信息、业务的平均用户体验信息、业务的用户满意比例信息，其中，所述业务的用户满意比例为所述业务对应的用户体验不差于预设值的用户数占所述业务总用户数的比例。
一种可能的实现方式，结合上述第一方面、第一方面第一种至第十二种中任一可能的实现方式，在第一方面的第十三种可能的实现方式中，该方法还可以包括：
所述切片管控网元向所述数据分析网元发送服务体验信息请求，所述服务体验信息请求用于请求第二网络切片的服务体验信息，所述服务体验信息请求中包含所述第二网络切片的切片标识信息和/或所述第二网络切片对应的服务区域信息。其中，第二网络切片可以与第一网络切片相同，也可以与第一网络切片不同。该服务体验信息请求可以为subscribe请求，也可以为request请求。
一种可能的实现方式，结合上述第一方面、第一方面第一种至第十三种中任一可能的实现方式，在第一方面的第十四种可能的实现方式中，该方法还可以包括：所述切片管控网元从网管网元获知需要新建网络切片或者删除网络切片。
一种可能的实现方式，结合上述第一方面、第一方面第一种至第十四种中任一可能的实现方式，在第一方面的第十五种可能的实现方式中，该方法还可以包括：所述切片管控网元确定导致问题区域和/或问题时间的原因在于第一网络域(network domain)，所述问题区域包括第一区域或第二区域，所述问题时间包括第一时间或第二时间；所述切片管控网元根据所述第一网络域确定所述网络设备。
在该第十五种可能的实现方法中，切片管控网元可首先精确定位出问题区域、问题时间的产生的原因是出自某网络域(如接入网域)，随后再向该网络域的网络设备发送问题区域(即第二区域)信息和/或问题时间(即第二时间)信息，该方法可避免盲目地调整其他正常工作的网络域的资源调度情况，提升资源调度的准确性。
一种可能的实现方式，结合上述第十五种可能的实现方式，在第一方面的第十六种可能的实现方式中，所述切片管控网元确定导致问题区域和/或问题时间的原因在于第一网络域，可以包括：所述切片管控网元从网管网元获知导致问题区域和/或问题时间的原因在于第一网络域。
由该第十六种可能的实现方式可知，当该切片管控网元是位于运营商网络控制面的切片管控网元时，该切片管控网元可以与位于运营商网络管理面的网管网元交互，从而获知第一网络域是导致问题区域和/或问题时间的原因。
一种可能的实现方式，结合上述第十六种可能的实现方式，在第一方面的第十七种可能的实现方式中，所述切片管控网元根据所述第一网络域确定所述网络设备，可以包括：所述切片管控网元从所述网管网元获取第一可信度信息，所述第一可信度信息用于指示导致问题区域和/或问题时间的原因在于第一网络域的可信程度；所述切片管控网元根据所述第一可信度信息确定所述网络设备。
一种可能的实现方式，结合上述第一方面的第七种至第十七种中任一可能的实现方式，在第一方面的第十八种可能的实现方式中，该方法还可以包括：所述切片管控网元确定导致所述第三服务体验信息与所述目标服务水平协议要求信息不对应的原因在于第二网络域，所述切片管控网元根据所述第二网络域确定所述网络设备。
在该第十八种可能的实现方法中，所述切片管控网元可首先精确定位出第一网络切片的第三服务体验无法满足目标服务水平协议要求信息的原因是出自某网络域(如接入网域)，随后再向所述网络域的网络设备发送问题区域(即第二区域)信息和/或问题时间(即第二时间)信息，该方法可避免盲目地调整其他正常工作的网络域的资源调度情况，提升资源调度的准确性。
一种可能的实现方式，结合上述第十八种可能的实现方式，在第一方面的第十九种可能的实现方式中，所述切片管控网元确定导致所述第三服务体验信息与所述目标服务水平协议要求信息不对应的原因在于第二网络域，可以包括：所述切片管控网元从网管网元获知导致所述第三服务体验信息与所述目标服务水平协议要求信息不对应的原因在于所述第 二网络域。
由该第十九种可能的实现方式可知，当该切片管控网元是位于运营商网络控制面的切片管控网元时，该切片管控网元可以与位于运营商网络管理面的网管网元交互，从而获知所述第二网络域是导致所述第三服务体验信息与所述目标服务水平协议要求信息不对应的原因。
一种可能的实现方式，结合上述第十九种可能的实现方式，在第一方面的第二十种可能的实现方式中，所述切片管控网元根据所述第二网络域确定所述网络设备，可以包括：所述切片管控网元从所述网管网元获取第二可信度信息，所述第二可信度信息用于指示导致所述第三服务体验信息与所述目标服务水平协议要求信息不对应的原因在于第二网络域的可信程度；所述切片管控网元根据所述第二可信度信息确定出所述网络设备。
一种可能的实现方式，结合上述第一方面的第十五种至第二十种中任一可能的实现方式，在第一方面的第二十一种可能的实现方式中，所述第一网络域或第二网络域包括以下至少一种：接入网域、核心网域、传输网域。
本申请第二方面提供一种网络切片的资源调度的方法，可以包括：网络设备接收切片管控网元发送的第一网络切片的第二区域信息，和/或第二时间信息；所述网络设备根据所述第二区域信息和/或第二时间信息为所述第一网络切片调度资源。
切片管控网元是指具备管理和控制网络切片的用户接入、资源部署、功能执行的网元，其可以位于运营商网络的控制面，例如切片管控网元为网络切片选择功能网元(network slice selection function，NSSF)；也可以位于运营商网络的管理面，例如切片管控网元为运行管理和维护网元(operation,administration,and maintenance，OAM)。所述网络设备包括以下设备的至少一个：接入网设备、用于分配用户面或控制面资源的核心网设备、传输网设备和网管网元，在切片管控网元是NSSF时，网管网元可以是OAM。第二区域信息可以与第一区域信息相同，也不可以不相同，第二时间信息可以与第一时间信息相同，也可以不相同。由上述第二方面可知，本申请网络设备可以根据第二区域信息和/或第二时间信息做资源调度，提高了资源调度的准确度和网络资源的利用率，也提高了网络切片的性能。
一种可能的实现方式，结合上述第二方面，在第二方面的第一种可能的实现方式中，该方法还可以包括：所述网络设备接收所述切片管控网元发送的所述第一网络切片对应的切片质量信息，所述切片质量信息包括所述第一网络切片的服务体验信息和/或所述第一网络切片的服务体验信息相对于目标服务水平协议要求的满足程度信息；所述网络设备根据所述切片质量信息调整为所述第一网络切片调度的资源。
服务体验信息可以是(Quality of Experience，QoE)信息，满足程度信息可以为fulfilment信息,目标服务水平协议要求信息可以为SLA要求信息。由该种可能的实现方式可知，网络设备根据服务体验信息和/或满足程度信息可以更准确的调整为所述第一网络切片调度的资源，可以利于网络设备做出更准确的资源调度。
一种可能的实现方式，结合上述第二方面第一种可能的实现方式，在第二方面的第二种可能的实现方式中，所述第一网络切片对应的切片质量信息包括所述第一网络切片的第 二区域对应的服务体验信息和/或所述第二区域对应的服务体验信息相对于所述目标服务水平协议要求的满足程度信息，所述第二区域为所述第二区域信息所指示的区域。
一种可能的实现方式，结合上述第二方面第二种可能的实现方式，在第二方面的第三种可能的实现方式中，所述第二区域为无法满足或超额满足所述目标服务水平协议要求的区域。
一种可能的实现方式，结合上述第二方面第一种至第三种中任一可能的实现方式，在第二方面的第四种可能的实现方式中，所述第一网络切片对应的切片质量信息包括所述第一网络切片的第二时间对应的服务体验信息和/或所述第二时间对应的服务体验信息相对于所述目标服务水平协议要求的满足程度信息，所述第二时间为所示第二时间信息所指示的时间。
一种可能的实现方式，结合上述第二方面第四种可能的实现方式，在第二方面的第五种可能的实现方式中，所述第二时间为无法满足或超额满足所述目标服务水平协议要求的时间。
一种可能的实现方式，结合上述第二方面第一种至第三种中任一可能的实现方式，在第二方面的第五种可能的实现方式中，所述第一网络切片对应的切片质量信息包括所述第一网络切片的第二区域和第二时间对应的服务体验信息和/或所述第二区域和第二时间对应的服务体验信息相对于所述目标服务水平协议要求的满足程度信息，所述第二区域为所述第二区域信息所指示的区域，所述第二时间为所示第二时间信息所指示的时间。
一种可能的实现方式，结合上述第二方面第一种至第六种中任一可能的实现方式，在第二方面的第六种可能的实现方式中，所述网络设备根据所述切片质量信息调整为所述第一网络切片调度的资源，可以包括：若所述第一网络切片的服务体验信息无法满足所述目标服务水平协议要求，则所述网络设备增加为所述第一网络切片调度的资源；若所述第一网络切片的服务体验信息超额满足所述目标服务水平协议要求，则所述网络设备减少为所述第一网络切片调度的资源。由该种可能的实现方式可知，若无法满足，则说明第一网络切片的资源不足，需要为第一网络切片增加资源，若超额满足，则说明第一网络切片的资源冗余，需要为第一网络切片减少资源。从而可以提高资源的利用率。
一种可能的实现方式，结合上述第二方面、第二方面第一种至第六种中任一可能的实现方式，在第二方面的第七种可能的实现方式中，所述网络设备包括以下设备的至少一个：接入网设备、用于分配用户面或控制面资源的核心网设备、传输网设备和网管网元。
一种可能的实现方式，结合上述第二方面、第二方面第一种至第七种中任一可能的实现方式，在第二方面的第八种可能的实现方式中，当所述网络设备为接入网设备时，所述接入网设备根据所述第二区域信息为所述第一网络切片调度接入网资源，或者，所述接入网设备根据所述第二时间信息为所述第一网络切片调度接入网资源。
本申请第三方面提供一种网络切片的资源调度的方法，该方法可以包括：数据分析网元接收切片管控网元发送的请求，所述请求包括对第一网络切片的服务体验要求信息；所述数据分析网元确定与所述服务体验要求信息对应的第一区域信息和/或第一时间信息；所述数据分析网元向所述切片管控网元发送响应，所述响应中包括与所述服务体验要求信息 对应的第一区域信息和/或第一时间信息。
其中，数据分析网元是指具备分析运营商网络数据或业务数据功能的网元，其可以位于运营商网络的控制面，例如数据分析网元可以为网络数据分析网元(network data analytics function，NWDAF)，其也可以位于运营商网络的管理面，例如数据分析网元可以为(Management Data Analytic System，MDAS)。切片管控网元是指具备管理和控制网络切片的用户接入、资源部署、功能执行的网元，其可以位于运营商网络的控制面，例如切片管控网元为网络切片选择功能网元NSSF；也可以位于运营商网络的管理面，例如切片管控网元为运行管理和维护网元OAM。由上述第三方面可知，数据分析网元可以确定出第一网络切片中存在问题的第一区域信息和/或第一时间信息，从而有利于网络设备更准确的做资源调度。
一种可能的实现方式，结合上述第三方面，在第三方面的第一种可能的实现方式中，该方法还可以包括：所述数据分析网元确定所述第一区域信息和/或所述第一时间信息所对应的所述第一网络切片的第一服务体验信息；则所述响应中还可以包括所述第一区域信息和/或所述第一时间信息所对应的所述第一网络切片的第一服务体验信息。
一种可能的实现方式，结合上述第三方面或第三方面第一种可能的实现方式，在第三方面的第二种可能的实现方式中，所述第一网络切片的服务体验要求信息包括正向服务体验要求信息和/或负向服务体验要求信息，所述正向服务体验要求信息为超额满足第一服务水平协议要求信息的过滤信息，所述负向服务体验要求信息为不满足第二服务水平协议要求信息的过滤信息。
一种可能的实现方式，结合上述第三方面、第三方面第一种或第二种可能的实现方式，在第三方面的第三种可能的实现方式中，所述请求中还可以包括第三区域信息时，所述第三区域信息所指示的第三区域包括所述第一区域信息所指示的第一区域，该方法还可以包括：所述数据分析网元根据所述第三区域信息，在所述第三区域中获取与所述服务体验要求信息对应的所述第一区域信息。由该种可能的实现方式可知，请求中带有第三区域信息，缩小可查找的范围，有利于数据分析网元快速确定第一区域信息。
一种可能的实现方式，结合上述第三方面、第三方面第一种至第三种中任一可能的实现方式，在第三方面的第四种可能的实现方式中，所述请求中还可以包括第三时间信息时，所述第三时间信息所指示的第三时间包括所述第一时间信息所指示的第一时间，所述方法还可以包括：所述数据分析网元根据所述第三时间信息，在所述第三时间信息中获取与所述服务体验要求信息对应的所述第一时间信息。由该种可能的实现方式可知，请求中带有第三时间信息，缩小可查找的范围，有利于数据分析网元快速确定第一时间信息。
一种可能的实现方式，结合上述第三方面、第三方面第一种至第四种中任一可能的实现方式，在第三方面的第五种可能的实现方式中，所述第一网络切片的服务体验要求信息包括以下信息中的至少一项：所述第一网络切片的用户数要求、业务的平均用户体验的要求、业务的用户满意比例的要求，其中，所述业务的用户满意比例为所述业务对应的用户体验不差于预设值的用户数占所述业务总用户数的比例。
一种可能的实现方式，结合上述第三方面、第三方面第一种至第五种中任一可能的实 现方式，在第三方面的第六种可能的实现方式中，所述第一网络切片的第一服务体验信息包括以下信息中的至少一项：所述第一网络切片的用户数信息、业务的用户数信息、业务的平均用户体验信息、业务的用户满意比例信息，其中，所述业务的用户满意比例为所述业务对应的用户体验不差于预设值的用户数占所述业务总用户数的比例。
本申请第四方面提供一种网络切片的资源调度的方法，可以包括：网络设备接收网管网元发送的第一网络切片的资源配置信息，所述资源配置信息包括最大资源配置信息(maximum resource configuration information)和/或保证资源配置信息(guarantee resource configuration information)，所述最大资源配置信息用于指示所述第一网络切片最大能使用的资源，所述保证资源配置信息用于指示所述第一网络切片保证能使用的资源；所述网络设备根据所述第一网络切片的资源配置信息为所述第一网络切片调度资源。
所述网络设备包括以下设备的至少一个：接入网设备、用于分配用户面或控制面资源的核心网设备和传输网设备。网管网元是指具备部署网络资源，并对网络的运行具备管理和维护功能的设备，例如可以为OAM或NSSF。由第四方面可知，网络的资源不需要与网络切片绑定，换句话说，网络的资源不是固定配置给某网络切片的。第四方面提供的网络资源调度方法，其中网络设备可以根据网管网元的指示在最大能使用的资源范围下，优先根据保证能使用的资源范围为某网络切片调度资源。该方法能使得网络设备根据网络切片的实际需要的资源量灵活地为该网络切片调度资源，并且承诺在网络切片需要时一定能为该网络切片调度保证能使用的资源范围量的资源，而在某些突发情况下，网络切片可能还允许使用最大能使用的资源范围量的资源。该方法既保证了网络切片有资源可用，也提高了资源的灵活性。
一种可能的实现方式，结合上述第四方面，在第四方面的第一种可能的实现方式中，所述第一网络切片保证能使用的资源允许被第二网络切片使用。由该种可能的实现方式可知，第一网络切片保证能使用的资源还可以被第二网络切片使用，尤其是在第一网络切片无需使用过多资源时，保证能使用的资源范围内的剩余资源允许被其他网络切片所使用，只要能够保证在第一网络切片需要时一定能为该第一网络切片调度保证能使用的资源范围量的资源即可，该方法提高了资源利用的灵活性。
一种可能的实现方式，结合上述第四方面或第四方面的第一种可能的实现方式，在第四方面的第二种可能的实现方式中，当所述网络设备为接入网设备时，所述最大资源配置信息为最大空口资源配置信息和/或保证资源配置信息为保证空口资源配置信息。
一种可能的实现方式，结合上述第四方面、第四方面的第一种或第二种可能的实现方式，在第四方面的第三种可能的实现方式中，所述网络设备根据所述第一网络切片的资源配置信息为所述第一网络切片调度资源，可以包括：所述网络设备在所述最大资源配置信息的限制范围内，根据所述保证资源配置信息优先为所述第一网络切片调度所述保证能使用的资源。
一种可能的实现方式，结合上述第四方面、第四方面的第一种至第三种任一可能的实现方式，在第四方面的第四种可能的实现方式中，所述最大资源配置信息和/或保证资源配置信息为第一时间对应的最大资源配置信息和/或保证资源配置信息；所述网络设备根据所 述第一网络切片的资源配置信息为所述第一网络切片调度资源，可以包括：所述网络设备根据所述第一时间对应的最大资源配置信息和/或保证资源配置信息为所述第一网络切片在所述第一时间调度资源。
其中，第一时间可以包含于所述最大资源配置信息和/或保证资源配置信息中，也可以是预先协商好的或者包含在所述最大资源配置信息和/或保证资源配置信息外的，不需要包含于所述最大资源配置信息和/或保证资源配置信息中。
一种可能的实现方式，结合上述第四方面、第四方面的第一种至第三种任一可能的实现方式，在第四方面的第五种可能的实现方式中，所述最大资源配置信息和/或保证资源配置信息为第一区域对应的最大资源配置信息和/或保证资源配置信息；所述网络设备根据所述第一网络切片的资源配置信息为所述第一网络切片调度资源，可以包括：所述网络设备根据所述第一区域对应的最大资源配置信息和/或保证资源配置信息为所述第一网络切片在所述第一区域调度资源。其中，第一区域可以包含于所述最大资源配置信息和/或保证资源配置信息中，也可以是预先协商好的或者包含在所述最大资源配置信息和/或保证资源配置信息外的，不需要包含于所述最大资源配置信息和/或保证资源配置信息中。
一种可能的实现方式，结合上述第四方面、第四方面的第一种至第五种任一可能的实现方式，在第四方面的第六种可能的实现方式中，该方法还可以包括：所述网络设备接收切片管控网元发送的所述第一网络切片对应的切片质量信息，所述切片质量信息包括所述第一网络切片的服务体验信息和/或所述第一网络切片的服务体验信息相对于目标服务水平协议要求的满足程度信息；所述网络设备根据所述切片质量信息调整为所述第一网络切片调度的资源。
一种可能的实现方式，结合上述第四方面第六种可能的实现方式，在第四方面的第七种可能的实现方式中，所述第一网络切片对应的切片质量信息包括所述第一网络切片的第二区域对应的服务体验信息和/或所述第二区域对应的服务体验信息相对于所述目标服务水平协议要求的满足程度信息。
一种可能的实现方式，结合上述第四方面第七种可能的实现方式，在第四方面的第八种可能的实现方式中，所述第二区域为无法满足或超额满足所述目标服务水平协议要求的区域。
一种可能的实现方式，结合上述第四方面第七种或第八种可能的实现方式，在第四方面的第九种可能的实现方式中，所述第一网络切片对应的切片质量信息包括所述第一网络切片的第二时间对应的服务体验信息和/或所述第二时间对应的服务体验信息相对于所述目标服务水平协议要求的满足程度信息。
一种可能的实现方式，结合上述第四方面第九种可能的实现方式，在第四方面的第十种可能的实现方式中，所述第二时间为无法满足或超额满足所述目标服务水平协议要求的时间。
一种可能的实现方式，结合上述第四方面第九种可能的实现方式，在第四方面的第十一种可能的实现方式中，所述第一网络切片对应的切片质量信息包括所述第一网络切片的第二区域和第二时间对应的服务体验信息和/或所述第二区域和第二时间对应的服务体验 信息相对于所述目标服务水平协议要求的满足程度信息。
一种可能的实现方式，结合上述第四方面第六种至第十一种任一可能的实现方式，在第四方面的第十二种可能的实现方式中，所述网络设备根据所述切片质量信息调整为所述第一网络切片调度的资源，可以包括：若所述第一网络切片的服务体验信息无法满足所述目标服务水平协议要求，则所述网络设备增加为所述第一网络切片调度的资源；若所述第一网络切片的服务体验信息超额满足所述目标服务水平协议要求，则所述网络设备减少为所述第一网络切片调度的资源。
本申请第五方面提供一种网络切片的资源调度的方法，可以包括：网管网元确定第一网络切片的资源配置信息，所述资源配置信息包括最大资源配置信息(maximum resource configuration information)和/或保证资源配置信息(guarantee resource configuration information)，所述最大资源配置信息用于指示所述第一网络切片最大能使用的资源，所述保证资源配置信息用于指示所述第一网络切片保证能使用的资源；所述网管网元向所述网络设备发送所述第一网络切片的资源配置信息，所述资源配置信息用于网络设备根据所述资源配置信息为所述第一网络切片的调度资源。
网管网元是指具备部署网络资源，并对网络的运行具备管理和维护功能的设备，例如可以为OAM或NSSF。由第五方面可知，网络的资源不需要与网络切片绑定，换句话说，网络的资源不是固定配置给某网络切片的。所述网络设备包括以下设备的至少一个：接入网设备、用于分配用户面或控制面资源的核心网设备和传输网设备。第五方面提供的网络资源调度方法，其中网络设备可以根据网管网元的指示在最大能使用的资源范围下，优先根据保证能使用的资源范围为某网络切片调度资源。该方法能使得网络设备根据网络切片的实际需要的资源量灵活地为该网络切片调度资源，并且承诺在网络切片需要时一定能为该网络切片调度保证能使用的资源范围量的资源，而在某些突发情况下，网络切片可能还允许使用最大能使用的资源范围量的资源。该方法既保证了网络切片有资源可用，也提高了资源的灵活性。
一种可能的实现方式，结合上述第五方面，在第五方面的第一种可能的实现方式中，当所述网络设备为接入网设备时，所述最大资源配置信息为最大空口资源配置信息和/或保证资源配置信息为保证空口资源配置信息。
一种可能的实现方式，结合上述第五方面或第五方面第一种可能的实现方式，在第五方面的第二种可能的实现方式中，所述最大资源配置信息和/或保证资源配置信息为第一时间对应的最大资源配置信息和/或保证资源配置信息；或者，所述最大资源配置信息和/或保证资源配置信息为第一区域对应的最大资源配置信息和/或保证资源配置信息。
其中，第一时间可以包含于所述最大资源配置信息和/或保证资源配置信息中，也可以是预先协商好的或者包含在所述最大资源配置信息和/或保证资源配置信息外的，不需要包含于所述最大资源配置信息和/或保证资源配置信息中。
一种可能的实现方式，结合上述第五方面、第五方面第一种或第二种可能的实现方式，在第五方面的第三种可能的实现方式中，所述网管网元确定第一网络切片的资源配置信息，可以包括：所述网管网元根据所述第一网络切片的目标服务水平协议要求信息，确定所述 第一网络切片的资源配置信息。
一种可能的实现方式，结合上述第五方面、第五方面第一种至第三种中任一可能的实现方式，在第五方面的第四种可能的实现方式中，该方法还可以包括：所述网管网元获取所述网络设备为所述第一网络切片调度的资源的信息；所述网管网元获取所述第一网络切片的切片质量信息，所述切片质量信息包括所述第一网络切片的服务体验信息和/或所述第一网络切片的服务体验信息相对于所述目标服务水平协议要求的满足程度信息；所述网管网元根据所述网络设备为所述第一网络切片调度的资源的信息和所述切片质量信息，更新所述第一网络切片的资源配置信息；所述网管网元向所述网络设备发送所述更新后的资源配置信息。
一种可能的实现方式，结合上述第五方面第四种可能的实现方式，在第五方面的第五种可能的实现方式中，所述资源的信息包括所述第一网络切片的第二区域对应的资源的信息，所述第一网络切片的服务体验信息包括所述第一网络切片的所述第二区域对应的服务体验信息，所述网管网元根据所述网络设备为所述第一网络切片调度的资源的信息和所述切片质量信息，更新所述第一网络切片的资源配置信息，可以包括：所述网管网元根据所述第二区域对应的资源的信息和所述第二区域对应的服务体验信息，更新所述第一网络切片的资源配置信息。
一种可能的实现方式，结合上述第五方面第四种可能的实现方式，在第五方面的第六种可能的实现方式中，所述资源的信息包括所述第一网络切片的第二时间对应的资源的信息，所述第一网络切片的服务体验信息包括所述第一网络切片的所述第二时间对应的服务体验信息，所述网管网元根据所述网络设备为所述第一网络切片调度的资源的信息和所述切片质量信息，更新所述第一网络切片的资源配置信息，可以包括：所述网管网元根据所述第二时间对应的资源的信息和所述第二时间对应的服务体验信息，更新所述第一网络切片的资源配置信息。
一种可能的实现方式，结合上述第五方面第四种可能的实现方式，在第五方面的第七种可能的实现方式中，所述资源的信息包括所述第一网络切片的第二区域和第二时间对应的资源的信息，所述第一网络切片的服务体验信息包括所述第一网络切片的所述第二区域和第二时间对应的服务体验信息，所述网管网元根据所述网络设备为所述第一网络切片调度的资源的信息和所述切片质量信息，更新所述第一网络切片的资源配置信息，可以包括：所述网管网元根据所述第二区域和第二时间对应的资源的信息，以及所述第二区域和第二时间对应的服务体验信息，更新所述第一网络切片的资源配置信息。
一种可能的实现方式，结合上述第五方面第四种至第七种中任一可能的实现方式，在第五方面的第八种可能的实现方式中，所述更新所述第一网络切片的资源配置信息，可以包括：所述网管网元更新所述最大资源配置信息和/或保证资源配置信息，使得所述更新后的最大资源配置信息不小于所述网络设备为所述第一网络切片调度的资源。
一种可能的实现方式，结合上述第五方面第四种至第八种中任一可能的实现方式，在第五方面的第九种可能的实现方式中，所述网管网元获取所述第一网络切片的切片质量信息，可以包括：所述网管网元从所述切片管控网元或数据分析设备获取所述切片质量信息。
本申请第六方面提供一种网络切片中用户数量控制的方法，可以包括：切片管控网元接收网管网元发送的目标网络切片的用户数量限制信息，以及指示信息，所述指示信息用于指示所述目标网络切片的状态信息或者所述用户数量限制信息的可信度；所述切片管控网元根据所述指示信息和所述用户数量限制信息控制所述目标网络切片所服务的用户的数量。
切片管控网元可以是具备管理和控制网络切片的用户接入、资源部署、功能执行的网元，其可以位于运营商网络的控制面，例如切片管控网元为网络切片选择功能网元NSSF)，网管网元可以是具备部署网络资源，并对网络的运行具备管理和维护功能的设备，例如可以为OAM。由该第六方面可知，可以根据指示信息和所述用户数量限制信息控制目标网络切片所服务的用户的数量，可以提高用户数量控制的准确度。
一种可能的实现方式，结合上述第六方面，在第六方面的第一种可能的实现方式中，所述指示信息用于指示所述目标网络切片的状态信息；所述切片管控网元根据所述指示信息和所述用户数量限制信息控制所述目标网络切片所服务的用户的数量，可以包括：所述切片管控网元根据所述用户数量限制信息按照所述状态信息所对应的控制方式，控制所述目标网络切片所服务的用户的数量。该种可能的实现方式中，状态信息不同，控制方式也不同。因此，可以根据状态信息实现精准的用户数量控制。
一种可能的实现方式，结合上述第六方面的第一种可能的实现方式，在第六方面的第二种可能的实现方式中，所述状态信息包括测试状态或稳定状态。
一种可能的实现方式，结合上述第六方面的第二种可能的实现方式，在第六方面的第三种可能的实现方式中，当所述状态信息为测试状态时，所述控制方式为阶梯控制的方式。也就是说，所述切片管控网元可以以阶梯的方式将所述用户数量限制信息所限制的数量的用户接入所述目标网络切片或将已由所述目标网络切片提供服务的用户剔除。
一种可能的实现方式，结合上述第六方面的第二种可能的实现方式，在第六方面的第四种可能的实现方式中，当所述状态信息为稳定状态时，所述控制方式为一次性控制的方式。也就是说，所述切片管控网元根据所述目标网络切片的稳定状态，一次将所述用户数量限制信息所限制的数量的用户接入所述目标网络切片或将已由所述目标网络切片提供服务的用户剔除。
一种可能的实现方式，结合上述第六方面，在第六方面的第五种可能的实现方式中，所述指示信息用于指示所述用户数量限制信息的可信度；所述切片管控网元根据所述指示信息和所述用户数量限制信息控制所述目标网络切片所服务的用户的数量，可以包括：所述切片管控网元根据所述用户数量限制信息按照所述可信度所对应的控制方式，控制所述目标网络切片所服务的用户的数量。
一种可能的实现方式，结合上述第六方面的第五种可能的实现方式，在第六方面的第六种可能的实现方式中，在所述可信度不符合可信度要求时，所述控制方式为阶梯控制的方式。也就是说，所述切片管控网元以阶梯的方式将所述用户数量限制信息所限制的数量的用户接入所述目标网络切片或将已由所述目标网络切片提供服务的用户剔除。
一种可能的实现方式，结合上述第六方面的第五种可能的实现方式，在第六方面的第 七种可能的实现方式中，在所述可信度符合可信度要求时，所述控制方式为一次性控制的方式。也就是说，所述切片管控网元一次将所述用户数量限制信息所限制的数量的用户接入所述目标网络切片或将已由所述目标网络切片提供服务的用户剔除。
一种可能的实现方式，结合上述第六方面、第六方面的第一种至第七种中任一可能的实现方式，在第六方面的第八种可能的实现方式中，所述切片管控网元接收网管网元发送的目标网络切片的用户数量限制信息，可以包括：所述切片管控网元接收所述网管网元发送的所述目标网络切片的服务水平协议要求信息，所述服务水平协议要求信息中包括所述目标网络切片的用户数量限制信息。当然，若网管网元向切片管控网元发送的目标网络切片的服务水平协议要求信息中没有用户数量限制信息，那么可以单独发送用用户数量限制信息，而且可以与目标网络切片的服务水平协议要求信息并列发送。
一种可能的实现方式，结合上述第六方面、第六方面的第一种至第八种中任一可能的实现方式，在第六方面的第九种可能的实现方式中，所述切片管控网元接收网管网元发送的目标网络切片的用户数量限制信息，可以包括：所述切片管控网元接收所述网管网元发送的所述目标网络切片的区域信息所对应的用户数量限制信息；所述切片管控网元根据所述指示信息和所述用户数量限制信息控制所述目标网络切片所服务的用户的数量，可以包括：所述切片管控网元针对所述区域信息所指示的区域，根据所述指示信息和所述区域信息所对应的用户数量限制信息控制所述目标网络切片所服务的用户的数量。
一种可能的实现方式，结合上述第六方面、第六方面的第一种至第八种中任一可能的实现方式，在第六方面的第十种可能的实现方式中，所述切片管控网元接收网管网元发送的目标网络切片的用户数量限制信息，可以包括：所述切片管控网元接收所述网管网元发送的时间信息所对应的用户数量限制信息；所述切片管控网元根据所述指示信息和所述用户数量限制信息控制所述目标网络切片所服务的用户的数量，可以包括：所述切片管控网元针对所述时间信息所指示的时间，根据所述指示信息和所述时间信息所对应的用户数量限制信息控制所述目标网络切片所服务的用户的数量。
一种可能的实现方式，结合上述第六方面、第六方面的第一种至第八种中任一可能的实现方式，在第六方面的第十一种可能的实现方式中，所述切片管控网元接收网管网元发送的目标网络切片的用户数量限制信息，可以包括：所述切片管控网元接收所述网管网元发送的所述目标网络切片的区域信息和时间信息所对应的用户数量限制信息；所述切片管控网元根据所述指示信息和所述用户数量限制信息控制所述目标网络切片所服务的用户的数量，可以包括：所述切片管控网元针对所述区域信息所指示的区域和所述时间信息所指示的时间，根据所述指示信息，以及所述区域信息和所述时间信息所对应的用户数量限制信息控制所述目标网络切片所服务的用户的数量。
一种可能的实现方式，结合上述第六方面、第六方面的第一种至第十一种中任一可能的实现方式，在第六方面的第十二种可能的实现方式中，所述用户数量限制信息包括在线用户数量限制信息和/或注册用户数量限制信息。
本申请第七方面提供一种网络切片中用户数量控制的方法，该方法可以包括：所述网管网元确定目标网络切片的用户数量限制信息以及指示信息，所述指示信息用于指示所述 目标网络切片的状态信息或者所述用户数量限制信息的可信度；所述网管网元向所述切片管控网元发送所述目标网络切片的用户数量限制信息，以及所述指示信息，所述指示信息和所述用户数量限制信息用于所述切片管控网元控制所述目标网络切片所服务的用户的数量。
网管网元可以是具备部署网络资源，并对网络的运行具备管理和维护功能的设备，例如可以为OAM，切片管控网元可以是具备管理和控制网络切片的用户接入、资源部署、功能执行的网元，其可以位于运营商网络的控制面，例如切片管控网元为NSSF。该第七方面可知，可以根据指示信息和所述用户数量限制信息控制目标网络切片所服务的用户的数量，可以提高用户数量控制的准确度。
一种可能的实现方式，结合上述第七方面，在第七方面的第一种可能的实现方式中，所述网管网元确定目标网络切片的用户数量限制信息，可以包括：所述网管网元获取所述目标网络切片的服务水平协议要求信息；所述网管网元根据所述服务水平协议要求信息确定所述目标网络切片的用户数量限制信息。
一种可能的实现方式，结合上述第七方面或第七方面的第一种可能的实现方式，在第七方面的第二种可能的实现方式中，所述网管网元向所述切片管控网元发送所述目标网络切片的用户数量限制信息，可以包括：所述网管网元向所述切片管控网元发送所述目标网络切片的区域信息和所述区域信息所对应的用户数量限制信息，所述区域信息和所述区域信息所对应的用户数量限制信息用于所述切片管控网元针对所述区域信息所指示的区域，在所述区域信息所对应的用户数量限制信息所指示的范围内控制所述目标网络切片所服务的用户的数量。
一种可能的实现方式，结合上述第七方面或第七方面的第一种可能的实现方式，在第七方面的第三种可能的实现方式中，所述网管网元向所述切片管控网元发送所述目标网络切片的用户数量限制信息，可以包括：所述网管网元向所述切片管控网元发送所述目标网络切片的时间信息和所述时间信息所对应的用户数量限制信息，所述时间信息和所述时间信息所对应的用户数量限制信息用于针对所述时间信息所指示的时间，在所述时间信息所对应的用户数量限制信息所指示的范围内控制所述目标网络切片所服务的用户的数量。
一种可能的实现方式，结合上述第七方面或第七方面的第一种可能的实现方式，在第七方面的第四种可能的实现方式中，所述网管网元向所述切片管控网元发送所述目标网络切片的用户数量限制信息，可以包括：所述网管网元向所述切片管控网元发送所述目标网络切片的区域信息和所述区域信息所对应的用户数量限制信息，以及所述目标网络切片的时间信息和所述时间信息所对应的用户数量限制信息，所述区域信息和所述区域信息所对应的用户数量限制信息用于所述切片管控网元针对所述区域信息所指示的区域，在所述区域信息所对应的用户数量限制信息所指示的范围内控制所述目标网络切片所服务的用户的数量，所述时间信息和所述时间信息所对应的用户数量限制信息用于针对所述时间信息所指示的时间，在所述时间信息所对应的用户数量限制信息所指示的范围内控制所述目标网络切片所服务的用户的数量。
一种可能的实现方式，结合上述第七方面或第七方面的第一种至第四种中任一可能的 实现方式，在第七方面的第五种可能的实现方式中，该方法还可以包括：
所述网管网元获取所述目标网络切片的切片质量信息，所述切片质量信息包括所述目标网络切片的服务体验信息和/或所述目标网络切片的服务体验信息相对于所述服务水平协议要求信息满足程度信息；
所述网管网元根据所述切片质量信息更新所述目标网络切片的用户数量限制信息或所述指示信息；
所述网管网元向所述切片管控网元发送所述更新后的用户数量限制信息，或者所述更新后的指示信息。
一种可能的实现方式，结合上述第七方面第五种可能的实现方式，在第七方面的第六种可能的实现方式中，所述网管网元获取所述目标网络切片的切片质量信息，可以包括：所述网管网元从所述切片管控网元或者数据分析网元获取所述切片质量信息。
一种可能的实现方式，结合上述第七方面第五种或第六种可能的实现方式，在第七方面的第七种可能的实现方式中，所述目标网络切片的服务体验信息包括所述目标网络切片的所述区域信息所指示的区域对应的服务体验信息，所述网管网元根据所述切片质量信息更新所述目标网络切片的用户数量限制信息或所述指示信息，可以包括：所述网管网元根据所述区域信息所指示的区域对应的服务体验信息，更新所述目标网络切片的用户数量限制信息或所述指示信息。
一种可能的实现方式，结合上述第七方面第五种或第六种可能的实现方式，在第七方面的第八种可能的实现方式中，所述目标网络切片的服务体验信息包括所述目标网络切片的所述时间信息所指示的时间对应的服务体验信息，所述网管网元根据所述切片质量信息更新所述目标网络切片的用户数量限制信息或所述指示信息，可以包括：所述网管网元根据所述时间信息所指示的时间对应的服务体验信息，更新所述目标网络切片的用户数量限制信息或所述指示信息。
一种可能的实现方式，结合上述第七方面第五种或第六种可能的实现方式，在第七方面的第八种可能的实现方式中，所述目标网络切片的服务体验信息包括所述目标网络切片的所述区域信息所指示的区域和所述时间信息所指示的时间对应的服务体验信息，所述网管网元根据所述切片质量信息更新所述目标网络切片的用户数量限制信息或所述指示信息，可以包括：所述网管网元根据所述区域信息所指示的区域和所述时间信息所指示的时间对应的服务体验信息，更新所述目标网络切片的用户数量限制信息或所述指示信息。
本申请第八方面提供一种切片管控网元，所述切片管控网元用于执行上述第一方面或第一方面的任一可能的实现方式中的网络切片的资源调度的方法。具体地，所述切片管控网元可以包括用于执行第一方面或第一方面的任一可能的实现方式中的网络切片的资源调度的单元或模块，如：接收单元、发送单元和处理单元。
本申请第九方面提供一种网络设备，所述网络设备用于执行上述第二方面或第二方面的任一可能的实现方式中的网络切片的资源调度的方法。具体地，所述网络设备可以包括用于执行第二方面或第二方面的任一可能的实现方式中的网络切片的资源调度的单元或模块，如：接收单元、发送单元和处理单元。
本申请第十方面提供一种数据分析网元，所述数据分析网元用于执行上述第三方面或第三方面的任一可能的实现方式中的网络切片的资源调度的方法。具体地，所述数据分析网元可以包括用于执行第三方面或第三方面的任一可能的实现方式中的网络切片的资源调度的单元或模块，如：接收单元、发送单元和处理单元。
本申请第十一方面提供一种网络设备，所述网络设备用于执行上述第四方面或第四方面的任一可能的实现方式中的网络切片的资源调度的方法。具体地，所述网络设备可以包括用于执行第四方面或第四方面的任一可能的实现方式中的网络切片的资源调度的单元或模块，如：接收单元、发送单元和处理单元。
本申请第十二方面提供一种网管网元，所述网管网元用于执行上述第五方面或第五方面的任一可能的实现方式中的网络切片的资源调度的方法。具体地，所述网管网元可以包括用于执行第五方面或第五方面的任一可能的实现方式中的网络切片的资源调度的单元或模块，如：接收单元、发送单元和处理单元。
本申请第十三方面提供一种切片管控网元，所述切片管控网元用于执行上述第六方面或第六方面的任一可能的实现方式中的网络切片的资源调度的方法。具体地，所述切片管控网元可以包括用于执行第六方面或第六方面的任一可能的实现方式中的网络切片的资源调度的单元或模块，如：接收单元、发送单元和处理单元。
本申请第十四方面提供一种网管网元，所述网管网元用于执行上述第七方面或第七方面的任一可能的实现方式中的网络切片的资源调度的方法。具体地，所述网管网元可以包括用于执行第七方面或第七方面的任一可能的实现方式中的网络切片的资源调度的单元或模块，如：接收单元、发送单元和处理单元。
本申请第十五方面提供一种切片管控网元，包括：至少一个处理器、存储器、收发器以及存储在存储器中并可在处理器上运行的计算机执行指令，当所述计算机执行指令被所述处理器执行时，所述处理器执行如上述第一方面或第一方面任意一种可能的实现方式所述的方法。
本申请第十六方面提供一种网络设备，包括：至少一个处理器、存储器、收发器以及存储在存储器中并可在处理器上运行的计算机执行指令，当所述计算机执行指令被所述处理器执行时，所述处理器执行如上述第二方面或第二方面任意一种可能的实现方式所述的方法。
本申请第十七方面提供一种数据分析网元，包括：至少一个处理器、存储器、收发器以及存储在存储器中并可在处理器上运行的计算机执行指令，当所述计算机执行指令被所述处理器执行时，所述处理器执行如上述第三方面或第三方面任意一种可能的实现方式所述的方法。
本申请第十八方面提供一种网络设备，包括：至少一个处理器、存储器、收发器以及存储在存储器中并可在处理器上运行的计算机执行指令，当所述计算机执行指令被所述处理器执行时，所述处理器执行如上述第四方面或第四方面任意一种可能的实现方式所述的方法。
本申请第十九方面提供一种网管网元，包括：至少一个处理器、存储器、收发器以及 存储在存储器中并可在处理器上运行的计算机执行指令，当所述计算机执行指令被所述处理器执行时，所述处理器执行如上述第五方面或第五方面任意一种可能的实现方式所述的方法。
本申请第二十方面提供一种切片管控网元，包括：至少一个处理器、存储器、收发器以及存储在存储器中并可在处理器上运行的计算机执行指令，当所述计算机执行指令被所述处理器执行时，所述处理器执行如上述第六方面或第六方面任意一种可能的实现方式所述的方法。
本申请第二十一方面提供一种网管网元，包括：至少一个处理器、存储器、收发器以及存储在存储器中并可在处理器上运行的计算机执行指令，当所述计算机执行指令被所述处理器执行时，所述处理器执行如上述第七方面或第七方面任意一种可能的实现方式所述的方法。
本申请第二十二方面提供一种存储一个或多个计算机执行指令的计算机可读存储介质，当所述计算机执行指令被处理器执行时，所述处理器执行如上述第一方面或第一方面任意一种可能的实现方式所述的方法。
本申请第二十三方面提供一种存储一个或多个计算机执行指令的计算机可读存储介质，当所述计算机执行指令被处理器执行时，所述处理器执行如上述第二方面或第二方面任意一种可能的实现方式所述的方法。
本申请第二十四方面提供一种存储一个或多个计算机执行指令的计算机可读存储介质，当所述计算机执行指令被处理器执行时，所述处理器执行如上述第三方面或第三方面任意一种可能的实现方式所述的方法。
本申请第二十五方面提供一种存储一个或多个计算机执行指令的计算机可读存储介质，当所述计算机执行指令被处理器执行时，所述处理器执行如上述第四方面或第四方面任意一种可能的实现方式所述的方法。
本申请第二十六方面提供一种存储一个或多个计算机执行指令的计算机可读存储介质，当所述计算机执行指令被处理器执行时，所述处理器执行如上述第五方面或第五方面任意一种可能的实现方式所述的方法。
本申请第二十七方面提供一种存储一个或多个计算机执行指令的计算机可读存储介质，当所述计算机执行指令被处理器执行时，所述处理器执行如上述第六方面或第六方面任意一种可能的实现方式所述的方法。
本申请第二十八方面提供一种存储一个或多个计算机执行指令的计算机可读存储介质，当所述计算机执行指令被处理器执行时，所述处理器执行如上述第七方面或第七方面任意一种可能的实现方式所述的方法。
本申请第二十九方面提供一种存储一个或多个计算机执行指令的计算机程序产品，当所述计算机执行指令被所述处理器执行时，所述处理器执行上述第一方面或第一方面任意一种可能实现方式的方法。
本申请第三十方面提供一种存储一个或多个计算机执行指令的计算机程序产品，当所述计算机执行指令被所述处理器执行时，所述处理器执行上述第二方面或第二方面任意一 种可能实现方式的方法。
本申请第三十一方面提供一种存储一个或多个计算机执行指令的计算机程序产品，当所述计算机执行指令被所述处理器执行时，所述处理器执行上述第三方面或第三方面任意一种可能实现方式的方法。
本申请第三十二方面提供一种存储一个或多个计算机执行指令的计算机程序产品，当所述计算机执行指令被所述处理器执行时，所述处理器执行上述第四方面或第四方面任意一种可能实现方式的方法。
本申请第三十三方面提供一种存储一个或多个计算机执行指令的计算机程序产品，当所述计算机执行指令被所述处理器执行时，所述处理器执行上述第五方面或第五方面任意一种可能实现方式的方法。
本申请第三十四方面提供一种存储一个或多个计算机执行指令的计算机程序产品，当所述计算机执行指令被所述处理器执行时，所述处理器执行上述第六方面或第六方面任意一种可能实现方式的方法。
本申请第三十五方面提供一种存储一个或多个计算机执行指令的计算机程序产品，当所述计算机执行指令被所述处理器执行时，所述处理器执行上述第七方面或第七方面任意一种可能实现方式的方法。
本申请第三十六方面提供一种芯片系统，该芯片系统包括处理器，用于支持切片管控网元实现上述第一方面或第一方面任意一种可能的实现方式中所涉及的功能。在一种可能的实现方式中，芯片系统还可以包括存储器，存储器，用于保存切片管控网元必要的程序指令和数据。该芯片系统，可以由芯片构成，也可以包含芯片和其他分立器件。
本申请第三十七方面提供一种芯片系统，该芯片系统包括处理器，用于支持网络设备实现上述第二方面或第二方面任意一种可能的实现方式中所涉及的功能。在一种可能的实现方式中，芯片系统还可以包括存储器，存储器，用于保存网络设备必要的程序指令和数据。该芯片系统，可以由芯片构成，也可以包含芯片和其他分立器件。
本申请第三十八方面提供一种芯片系统，该芯片系统包括处理器，用于支持数据分析网元实现上述第三方面或第三方面任意一种可能的实现方式中所涉及的功能。在一种可能的实现方式中，芯片系统还可以包括存储器，存储器，用于保存数据分析网元必要的程序指令和数据。该芯片系统，可以由芯片构成，也可以包含芯片和其他分立器件。
本申请第三十九方面提供一种芯片系统，该芯片系统包括处理器，用于支持网络设备实现上述第四方面或第四方面任意一种可能的实现方式中所涉及的功能。在一种可能的实现方式中，芯片系统还可以包括存储器，存储器，用于保存网络设备必要的程序指令和数据。该芯片系统，可以由芯片构成，也可以包含芯片和其他分立器件。
本申请第四十方面提供一种芯片系统，该芯片系统包括处理器，用于支持网管网元实现上述第五方面或第五方面任意一种可能的实现方式中所涉及的功能。在一种可能的实现方式中，芯片系统还可以包括存储器，存储器，用于保存网管网元必要的程序指令和数据。该芯片系统，可以由芯片构成，也可以包含芯片和其他分立器件。
本申请第四十一方面提供一种芯片系统，该芯片系统包括处理器，用于支持切片管控 网元实现上述第六方面或第六方面任意一种可能的实现方式中所涉及的功能。在一种可能的实现方式中，芯片系统还可以包括存储器，存储器，用于保存切片管控网元必要的程序指令和数据。该芯片系统，可以由芯片构成，也可以包含芯片和其他分立器件。
本申请第四十二方面提供一种芯片系统，该芯片系统包括处理器，用于支持网管网元实现上述第七方面或第七方面任意一种可能的实现方式中所涉及的功能。在一种可能的实现方式中，芯片系统还可以包括存储器，存储器，用于保存网管网元必要的程序指令和数据。该芯片系统，可以由芯片构成，也可以包含芯片和其他分立器件。
其中，第八方面、第十五方面、第二十二方面、第二十九方面、第三十六方面中任一种实现方式所带来的技术效果可参见第一方面中不同实现方式所带来的技术效果，此处不再赘述。
其中，第九方面、第十六方面、第二十三方面、第三十方面、第三十七方面中任一种实现方式所带来的技术效果可参见第二方面中不同实现方式所带来的技术效果，此处不再赘述。
其中，第十方面、第十七方面、第二十四方面、第三十一方面、第三十八方面中任一种实现方式所带来的技术效果可参见第三方面中不同实现方式所带来的技术效果，此处不再赘述。
其中，第十一方面、第十八方面、第二十五方面、第三十二方面、第三十九方面中任一种实现方式所带来的技术效果可参见第四方面中不同实现方式所带来的技术效果，此处不再赘述。
其中，第十二方面、第十九方面、第二十六方面、第三十三方面、第四十方面中任一种实现方式所带来的技术效果可参见第五方面中不同实现方式所带来的技术效果，此处不再赘述。
其中，第十三方面、第二十方面、第二十七方面、第三十四方面、第四十一方面中任一种实现方式所带来的技术效果可参见第六方面中不同实现方式所带来的技术效果，此处不再赘述。
其中，第十四方面、第二十一方面、第二十八方面、第三十五方面、第四十二方面中任一种实现方式所带来的技术效果可参见第七方面中不同实现方式所带来的技术效果，此处不再赘述。
本申请第四十三方面提供一种通信系统，该通信系统包括：
切片管控网元，用于执行上述第一方面或第一方面任意一种可能实现方式的方法；
网络设备，用于执行上述第二方面或第二方面任意一种可能实现方式的方法；
数据分析网元，用于执行上述第三方面或第三方面任意一种可能实现方式的方法。
本申请第四十四方面提供一种通信系统，该通信系统包括：
网络设备，用于执行上述第四方面或第四方面任意一种可能实现方式的方法；
网管网元，用于执行上述第五方面或第五方面任意一种可能实现方式的方法。
本申请第四十五方面提供一种通信系统，该通信系统包括：
切片管控网元，用于执行上述第六方面或第六方面任意一种可能实现方式的方法；
网管网元，用于执行上述第七方面或第七方面任意一种可能实现方式的方法。
本申请实施例中在为网络切片调度资源时，切片管控网元会向网络设备发送需要根据的区域信息和/或时间信息，以便网络设备可以根据区域信息和/或时间信息为网络切片调度资源，实现了资源的精准调度，提高了网络资源的利用率，也提高网络切片的性能。
本申请第四十六方面提供一种网络切片的资源调度的方法，可以包括：网络设备确定第一网络切片的状态信息，第一网络切片的状态信息包括所述第一网络切片处于未签署服务水平协议(service level agreement，SLA)状态或已经签署SLA状态，所述网络设备根据所述第一网络切片的状态信息为所述第一网络切片调度资源。
未签署SLA状态包括测试状态或新建状态，已经签署SLA状态包括稳定状态。网络设备可以包括以下设备的至少一个：接入网设备、用于分配用户面或控制面资源的核心网设备或传输网设备。由该第四十六方面可知，网络设备可以根据第一网络切片处于未签署SLA状态或已经签署SLA状态为第一网络切片调度资源，从而提高了调度的准确度。
一种可能的实现方式，结合上述第四十六方面，在第四十六方面的第一种可能的实现方式中，当所述网络设备为接入网设备时，所述网络设备根据所述第一网络切片的状态信息为所述第一网络切片调度资源，可以包括：所述网络设备根据所述第一网络切片的状态信息为所述第一网络切片调度空口资源。
一种可能的实现方式，结合上述第四十六方面或第四十六方面第一种可能的实现方式，在第四十六方面的第二种可能的实现方式中，所述方法还可以包括：所述网络设备确定第二网络切片的状态信息为所述第二网络切片处于已经签署SLA状态；当所述第一网络切片的状态信息为所述第一网络切片处于未签署SLA状态，所述网络设备根据所述第一网络切片的状态信息为所述第一网络切片调度资源，可以包括：所述网络设备落后(deprioritized)于所述第二网络切片而为所述第一网络切片调度资源。
由该第四十六方面第二种可能的实现方式可知，网络设备优先为已经签署SLA的网络切片调度资源，这样可以避免因未签署SLA的网络切片对已经签署SLA的网络切片造成影响，因第一网络切片处于未签署SLA状态，则网络设备可降低对第一网络切片资源调度的优先级，换句话说，网络设备优先为其他已经签署SLA的网络切片调度资源，在有资源剩余的情况下，才为第一网络切片调度资源。
一种可能的实现方式，结合上述第四十六方面或第四十六方面第一种可能的实现方式，在第四十六方面的第三种可能的实现方式中，所述方法还可以包括：所述网络设备确定第二网络切片的状态信息为所述第二网络切片处于未签署SLA状态；
当所述第一网络切片的状态信息为所述第一网络切片已签署SLA状态，所述网络设备根据所述第一网络切片的状态信息为所述第一网络切片调度资源，可以包括：所述网络设备优先于所述第二网络切片而为所述第一网络切片调度资源。
由该第四十六方面第三种可能的实现方式可知，若网络设备获知第一网络切片处于已签署SLA状态，或者第一网络切片从未签署SLA状态进入已经签署SLA状态，则网络设备提高对第一网络切片的资源调度的优先级，避免该第一网络切片被其他新建网络切片抢占资源。
一种可能的实现方式，结合上述第四十六方面、第四十六方面第一种至第三种中任一可能的实现方式，在第四十六方面的第四种可能的实现方式中，所述网络设备确定第一网络切片的状态信息，可以包括：所述网络设备根据网管网元发送的所述第一网络切片的状态指示信息确定所述第一网络切片的状态信息，所述状态指示信息中包含所述第一网络切片的状态信息。
一种可能的实现方式，结合上述第四十六方面、第四十六方面第一种至第四种中任一可能的实现方式，在第四十六方面的第五种可能的实现方式中，所述方法还可以包括：
所述网络设备接收网管网元发送的所述第一网络切片的资源配置信息，所述资源配置信息包括最大资源配置信息(maximum resource configuration information)和/或保证资源配置信息(guarantee resource configuration information)，所述最大资源配置信息用于指示所述第一网络切片最大能使用的资源，所述保证资源配置信息用于指示所述第一网络切片保证能使用的资源；所述网络设备根据所述第一网络切片的资源配置信息和所述第一网络切片的状态信息为所述第一网络切片调度资源。该资源配置信息还可以包括第一网络切片的状态信息。
一种可能的实现方式，结合上述第四十六方面第五种可能的实现方式，在第四十六方面的第六种可能的实现方式中，当所述网络设备为接入网设备时，所述最大资源配置信息为最大空口资源配置信息和/或保证资源配置信息为保证空口资源配置信息。
本申请第四十七方面提供一种网络切片的资源调度的方法，可以包括：网管网元确定第一网络切片的状态信息，所述第一网络切片的状态信息包括所述第一网络切片处于未签署SLA状态或已经签署SLA状态；所述网管网元向网络设备发送所述第一网络切片的状态信息，所述第一网络切片的状态信息用于所述网络设备为所述第一网络切片调度资源。
未签署SLA状态可以包括测试状态或新建状态，已经签署SLA状态包括稳定状态。网管网元是指具备部署网络资源，并对网络的运行具备管理和维护功能的设备，例如可以为OAM或NSSF或NSMF。网络设备可以包括以下设备的至少一个：接入网设备、用于分配用户面或控制面资源的核心网设备和传输网设备。由该第四十六方面可知，网管网元能及时将第一网络切片的状态信息通知给网络设备，以便网络设备根据第一网络切片所处的SLA状态执行对应的资源调度。
一种可能的实现方式，结合第四十七方面，在第四十七方面第一种可能的实现方式中，该方法还可以包括：
所述网管网元确定所述第一网络切片的资源配置信息，所述资源配置信息包括最大资源配置信息和/或保证资源配置信息，所述最大资源配置信息用于指示所述第一网络切片最大能使用的资源，所述保证资源配置信息用于指示所述第一网络切片保证能使用的资源；所述网管网元向所述网络设备发送所述第一网络切片的资源配置信息，所述资源配置信息用于网络设备根据所述资源配置信息为所述第一网络切片的调度资源。该资源配置信息还可以包括第一网络切片的状态信息。
一种可能的实现方式，结合第四十七方面或第四十七方面第一种可能的实现方式，在第四十七方面第二种可能的实现方式中，当所述网络设备为接入网设备时，所述最大资源 配置信息为最大空口资源配置信息和/或保证资源配置信息为保证空口资源配置信息。
一种可能的实现方式，结合第四十七方面第一种或第二种可能的实现方式，在第四十七方面第三种可能的实现方式中，所述资源配置信息包括所述第一网络切片的状态信息。
本申请第四十八方面提供一种网络切片的资源调度的方法，可以包括：切片管控网元确定导致第一网络切片的服务体验信息无法满足或超额满足所述第一网络切片的目标服务水平协议信息的原因在于第一网络域；所述切片管控网元向所述第一网络域的网络设备发送所述第一网络切片的切片质量信息，所述切片质量信息用于所述网络设备根据所述切片质量信息为所述第一网络切片调度资源。
所述切片质量信息包括以下信息的至少一项：所述第一网络切片的服务体验信息、所述第一网络切片的服务体验信息相对于所述目标服务水平协议要求信息的满足程度信息。
由该第四十八方面可知，切片管控网元可先精确定位出第一网络切片的服务体验信息无法满足目标服务水平协议要求信息的原因是出自某网络域(如接入网域)，随后再向该网络域的网络设备提供该第一网络切片的切片质量信息，以便于该网络域的网络设备调整资源的调度情况。该方法可避免盲目地调整其他正常工作的网络域的资源调度情况，提升资源调度的准确性。
一种可能的实现方式，结合第四十八方面，在第四十八方面第一种可能的实现方式中，所述方法还可以包括：所述切片管控网元从数据分析网元或网管网元获取所述第一网络切片的切片质量信息。
一种可能的实现方式，结合第四十八方面第一种可能的实现方式，在第四十八方面第二种可能的实现方式中，当所述第一网络切片的切片质量信息为所述第一网络切片的服务体验信息时，所述方法还可以包括：所述切片管控网元根据所述第一网络切片的服务体验信息确定所述第一网络切片的服务体验信息相对于所述目标服务水平协议要求信息的满足程度信息。
一种可能的实现方式，结合第四十八方面、第四十八方面第一种或第二种可能的实现方式，在第四十八方面第三种可能的实现方式中，所述方法还可以包括：所述切片管控网元确定所述第一网络切片的服务体验信息无法满足或超额满足所述第一网络切片的目标服务水平协议信息。
一种可能的实现方式，结合第四十八方面、第四十八方面第一种至第三种中任一可能的实现方式，在第四十八方面第四种可能的实现方式中，所述切片管控网元确定导致第一网络切片的服务体验信息无法满足或超额满足所述第一网络切片的目标服务水平协议信息的原因在于第一网络域，可以包括：
所述切片管控网元从所述网管网元获取指示信息，所述指示信息用于指示导致第一网络切片的服务体验信息无法满足或超额满足所述第一网络切片的目标服务水平协议信息的原因在于第一网络域；
所述切片管控网元根据所述指示信息确定导致第一网络切片的服务体验信息无法满足或超额满足所述第一网络切片的目标服务水平协议信息的原因在于第一网络域。
一种可能的实现方式，结合第四十八方面第四种可能的实现方式，在第四十八方面第 五种可能的实现方式中，所述切片管控网元从所述网管网元获取指示信息，可以包括：
所述切片管控网元向所述网管网元发送请求消息，所述请求消息用于请求导致所述第一网络切片的服务体验信息无法满足或超额满足所述第一网络切片的目标服务水平协议信息的网络域；
所述切片管控网元接收所述网管网元发送的响应消息，所述响应消息中包含所述指示信息。
一种可能的实现方式，结合第四十八方面第四种或第五种可能的实现方式，在第四十八方面第六种可能的实现方式中，所述切片管控网元向所述第一网络域的网络设备发送所述第一网络切片的切片质量信息之前，还可以包括：
所述切片管控网元从所述网管网元获取可信度信息，所述可信度信息用于指示所述指示信息的可信程度；
所述切片管控网元向所述第一网络域的网络设备发送所述第一网络切片的切片质量信息，可以包括：
所述切片管控网元根据所述可信度信息向所述第一网络域的网络设备发送所述第一网络切片的切片质量信息。
一种可能的实现方式，结合第四十八方面、第四十八方面第一种至第三种中任一可能的实现方式，在第四十八方面第七种可能的实现方式中，所述服务体验信息包括区域信息和/或时间信息对应的第一网络切片的服务体验信息。该区域信息可以是存在问题的区域的信息，该时间信息可以是存在问题的时间的信息。
一种可能的实现方式，结合第四十八方面、第四十八方面第一种至第七种中任一可能的实现方式，在第四十八方面第八种可能的实现方式中，所述满足程度信息包括无法满足、满足或者超额满足。
一种可能的实现方式，结合第四十八方面、第四十八方面第一种至第八种中任一可能的实现方式，在第四十八方面第九种可能的实现方式中，所述方法还可以包括：
所述切片管控网元获取所述第一网络切片的初始服务水平协议要求信息；
所述切片管控网元根据所述第一网络切片的初始服务水平协议要求信息确定至少一个服务水平协议要求信息；
所述切片管控网元将所述至少一个服务水平协议要求信息中的一个确定为所述目标服务水平协议要求信息。
一种可能的实现方式，结合第四十八方面、第四十八方面第一种至第九种中任一可能的实现方式，在第四十八方面第十种可能的实现方式中，所述第一网络域包括以下至少一项：接入网域、核心网域、传输网域。
一种可能的实现方式，结合第四十八方面、第四十八方面第一种至第十种中任一可能的实现方式，在第四十八方面第十一种可能的实现方式中，所述网络设备包括以下设备的至少一个：接入网设备、用于分配用户面或控制面资源的核心网设备、传输网设备。
一种可能的实现方式，结合第四十八方面、第四十八方面第一种至第十一种中任一可能的实现方式，在第四十八方面第十二种可能的实现方式中，所述服务水平协议要求信息 包括以下信息中的至少一项：所述第一网络切片的用户数要求信息、业务的平均用户体验的要求信息、业务的用户满意比例的要求信息，其中，所述业务的用户满意比例为所述业务对应的用户体验不差于预设值的用户数占该业务总用户数的比例。
本申请第四十九方面提供一种网络切片的资源调度方法，所述方法包括：所述网管网元确定导致第一网络切片的服务体验信息无法满足或超额满足所述第一网络切片的目标服务水平协议信息的原因在于第一网络域；所述网管网元向切片管控网元发送指示信息，所述指示信息用于指示导致第一网络切片的服务体验信息无法满足或超额满足所述第一网络切片的目标服务水平协议信息的原因在于第一网络域。
由该第四十九方面可知，可以通知切片管控网元导致第一网络切片的服务体验信息无法满足或超额满足所述第一网络切片的目标服务水平协议信息的原因所在的第一网络域，例如：接入网络域，这样就可以可避免盲目地调整其他正常工作的网络域的资源调度情况，提升资源调度的准确性。
一种可能的实现方式，结合第四十九方面、在第四十九方面第一种可能的实现方式中，所述方法还包括：所述网管网元确定可信度信息，所述可信度信息用于指示所述指示信息的可信程度；所述网管网元向所述切片管控网元发送所述可信度信息。
一种可能的实现方式，结合第四十九方面或第四十九方面第一种可能的实现方式，在第四十九方面第二种可能的实现方式中，所述方法还包括：所述网管网元从数据分析网元获取第一网络切片的切片质量信息，其中，所述切片质量信息包括以下信息的至少一项：所述第一网络切片的服务体验信息、所述第一网络切片的服务体验信息相对于所述目标服务水平协议要求信息的满足程度信息。
一种可能的实现方式，结合第四十九方面第二种可能的实现方式，在第四十九方面第三种可能的实现方式中，当所述第一网络切片的切片质量信息为所述第一网络切片的服务体验信息时，所述方法还包括：所述网管网元根据所述第一网络切片的服务体验信息确定所述第一网络切片的服务体验信息相对于所述目标服务水平协议要求信息的满足程度信息。
一种可能的实现方式，结合第四十九方面或第四十九方面第一种至第三种中任一可能的实现方式，在第四十九方面第四种可能的实现方式中，在所述网管网元确定导致第一网络切片的服务体验信息无法满足或超额满足所述第一网络切片的目标服务水平协议信息的原因在于第一网络域之前，所述方法还可以包括：所述网管网元确定所述第一网络切片的服务体验信息无法满足或超额满足所述第一网络切片目标服务水平协议信息。
一种可能的实现方式，结合第四十九方面或第四十九方面第一种至第四种中任一可能的实现方式，在第四十九方面第五种可能的实现方式中，所述服务体验信息包括区域信息和/或时间信息对应的第一网络切片的服务体验信息。
一种可能的实现方式，结合第四十九方面或第四十九方面第一种至第五种中任一可能的实现方式，在第四十九方面第六种可能的实现方式中，所述网管网元向切片管控网元发送指示信息之前，所述方法还包括：
所述网管网元接收所述切片管控网元发送的请求消息，所述请求消息用于请求导致所 述服务体验信息无法满足或超额满足所述第一网络切片的目标服务水平协议信息的网络域；
所述网管网元向切片管控网元发送指示信息，包括：
所述网管网元向所述切片管控网元发送的响应消息，所述响应消息中包含所述指示信息。
一种可能的实现方式，结合第四十九方面或第四十九方面第一种至第六种中任一可能的实现方式，在第四十九方面第七种可能的实现方式中，所述方法还可以包括：
所述切片管控网元获取所述第一网络切片的初始服务水平协议要求信息；
所述切片管控网元根据所述第一网络切片的初始服务水平协议要求信息确定至少一个服务水平协议要求信息；
所述切片管控网元将所述至少一个服务水平协议要求信息中的一个确定为所述目标服务水平协议要求信息。
一种可能的实现方式，结合第四十九方面或第四十九方面第一种至第七种中任一可能的实现方式，在第四十九方面第八种可能的实现方式中，所述第一网络域包括以下至少一项：接入网域、核心网域、传输网域。
一种可能的实现方式，结合第四十九方面或第四十九方面第一种至第八种中任一可能的实现方式，在第四十九方面第九种可能的实现方式中，所述服务水平协议要求信息包括以下信息中的至少一项：所述第一网络切片的用户数要求信息、业务的平均用户体验的要求信息、业务的用户满意比例的要求信息，其中，所述业务的用户满意比例为所述业务对应的用户体验不差于预设值的用户数占该业务总用户数的比例。
本申请第五十方面提供一种网络设备，所述网络设备用于执行上述第四十六方面或第四十六方面的任一可能的实现方式中的网络切片的资源调度的方法。具体地，所述网络设备可以包括用于执行第四十六方面或第四十六方面的任一可能的实现方式中的网络切片的资源调度的单元或模块，如：接收单元、发送单元和处理单元。
本申请第五十一方面提供一种网管网元，所述网管网元用于执行上述第四十七方面或第四十七方面的任一可能的实现方式中的网络切片的资源调度的方法。具体地，所述网管网元可以包括用于执行第四十七方面或第四十七方面的任一可能的实现方式中的网络切片的资源调度的单元或模块，如：接收单元、发送单元和处理单元。
本申请第五十二方面提供一种切片管控网元，所述切片管控网元用于执行上述第四十八方面或第四十八方面的任一可能的实现方式中的网络切片的资源调度的方法。具体地，所述切片管控网元可以包括用于执行第四十八方面或第四十八方面的任一可能的实现方式中的网络切片的资源调度的单元或模块，如：接收单元、发送单元和处理单元。
本申请第五十三方面提供一种网管网元，所述网管网元用于执行上述第四十九方面或第四十九方面的任一可能的实现方式中的网络切片的资源调度的方法。具体地，所述网管网元可以包括用于执行第四十九方面或第四十九方面的任一可能的实现方式中的网络切片的资源调度的单元或模块，如：接收单元、发送单元和处理单元。
本申请第五十四方面提供一种网络设备，包括：至少一个处理器、存储器、收发器以 及存储在存储器中并可在处理器上运行的计算机执行指令，当所述计算机执行指令被所述处理器执行时，所述处理器执行如上述第四十六方面或第四十六方面任意一种可能的实现方式所述的方法。
本申请第五十五方面提供一种网管网元，包括：至少一个处理器、存储器、收发器以及存储在存储器中并可在处理器上运行的计算机执行指令，当所述计算机执行指令被所述处理器执行时，所述处理器执行如上述第四十七方面或第四十七方面任意一种可能的实现方式所述的方法。
本申请第五十六方面提供一种切片管控网元，包括：至少一个处理器、存储器、收发器以及存储在存储器中并可在处理器上运行的计算机执行指令，当所述计算机执行指令被所述处理器执行时，所述处理器执行如上述第四十八方面或第四十八方面任意一种可能的实现方式所述的方法。
本申请第五十七方面提供一种网管网元，包括：至少一个处理器、存储器、收发器以及存储在存储器中并可在处理器上运行的计算机执行指令，当所述计算机执行指令被所述处理器执行时，所述处理器执行如上述第四十九方面或第四十九方面任意一种可能的实现方式所述的方法。
本申请第五十八方面提供一种存储一个或多个计算机执行指令的计算机可读存储介质，当所述计算机执行指令被处理器执行时，所述处理器执行如上述第四十六方面或第四十六方面任意一种可能的实现方式所述的方法。
本申请第五十九方面提供一种存储一个或多个计算机执行指令的计算机可读存储介质，当所述计算机执行指令被处理器执行时，所述处理器执行如上述第四十七方面或第四十七方面任意一种可能的实现方式所述的方法。
本申请第六十方面提供一种存储一个或多个计算机执行指令的计算机可读存储介质，当所述计算机执行指令被处理器执行时，所述处理器执行如上述第四十八方面或第四十八方面任意一种可能的实现方式所述的方法。
本申请第六十一方面提供一种存储一个或多个计算机执行指令的计算机可读存储介质，当所述计算机执行指令被处理器执行时，所述处理器执行如上述第四十九方面或第四十九方面任意一种可能的实现方式所述的方法。
本申请第六十二方面提供一种存储一个或多个计算机执行指令的计算机程序产品，当所述计算机执行指令被所述处理器执行时，所述处理器执行上述第四十六方面或第四十六方面任意一种可能实现方式的方法。
本申请第六十三方面提供一种存储一个或多个计算机执行指令的计算机程序产品，当所述计算机执行指令被所述处理器执行时，所述处理器执行上述第四十七方面或第四十七方面任意一种可能实现方式的方法。
本申请第六十四方面提供一种存储一个或多个计算机执行指令的计算机程序产品，当所述计算机执行指令被所述处理器执行时，所述处理器执行上述第四十八方面或第四十八方面任意一种可能实现方式的方法。
本申请第六十五方面提供一种存储一个或多个计算机执行指令的计算机程序产品，当 所述计算机执行指令被所述处理器执行时，所述处理器执行上述第四十九方面或第四十九方面任意一种可能实现方式的方法。
本申请第六十六方面提供一种芯片系统，该芯片系统包括处理器，用于支持网络设备实现上述第四十六方面或第四十六方面任意一种可能的实现方式中所涉及的功能。在一种可能的实现方式中，芯片系统还可以包括存储器，存储器，用于保存网络设备必要的程序指令和数据。该芯片系统，可以由芯片构成，也可以包含芯片和其他分立器件。
本申请第六十七方面提供一种芯片系统，该芯片系统包括处理器，用于支持网管网元实现上述第四十七方面或第四十七方面任意一种可能的实现方式中所涉及的功能。在一种可能的实现方式中，芯片系统还可以包括存储器，存储器，用于保存网管网元必要的程序指令和数据。该芯片系统，可以由芯片构成，也可以包含芯片和其他分立器件。
本申请第六十八方面提供一种芯片系统，该芯片系统包括处理器，用于支持切片管控网元实现上述第四十八方面或第四十八方面任意一种可能的实现方式中所涉及的功能。在一种可能的实现方式中，芯片系统还可以包括存储器，存储器，用于保存切片管控网元必要的程序指令和数据。该芯片系统，可以由芯片构成，也可以包含芯片和其他分立器件。
本申请第六十九方面提供一种芯片系统，该芯片系统包括处理器，用于支持网管网元实现上述第四十九方面或第四十九方面任意一种可能的实现方式中所涉及的功能。在一种可能的实现方式中，芯片系统还可以包括存储器，存储器，用于保存网管网元必要的程序指令和数据。该芯片系统，可以由芯片构成，也可以包含芯片和其他分立器件。
其中，第五十方面、第五十四方面、第五十八方面、第六十二方面、第六十六方面中任一种实现方式所带来的技术效果可参见第四十六方面中不同实现方式所带来的技术效果，此处不再赘述。
其中，第五十一方面、第五十五方面、第五十九方面、第六十三方面、第六十七方面中任一种实现方式所带来的技术效果可参见第四十七方面中不同实现方式所带来的技术效果，此处不再赘述。
其中，第五十二方面、第五十六方面、第六十方面、第六十四方面、第六十八方面中任一种实现方式所带来的技术效果可参见第四十八方面中不同实现方式所带来的技术效果，此处不再赘述。
其中，第五十三方面、第五十七方面、第六十一方面、第六十五方面、第六十九方面中任一种实现方式所带来的技术效果可参见第四十九方面中不同实现方式所带来的技术效果，此处不再赘述。
附图说明
图1是网络切片的一场景示意图；
图2是本申请实施例中网络切片的资源调度的方法的一实施例示意图；
图3是本申请实施例中网络切片的资源调度的方法的另一实施例示意图；
图4是本申请实施例中网络切片的资源调度的方法的另一实施例示意图；
图5是本申请实施例中网络切片的用户数控制的一实施例示意图；
图6是网络结构一实施例示意图；
图7A是本申请实施例中网络切片的资源调度以及用户数控制的一实施例示意图；
图7B是本申请实施例中网络切片的资源调度的方法的另一实施例示意图；
图7C是本申请实施例中网络切片的资源调度的方法的另一实施例示意图；
图7D是本申请实施例中网络切片的用户数控制的另一实施例示意图；
图8是本申请实施例中通信设备的一实施例示意图；
图9是本申请实施例中切片管控网元的一实施例示意图；
图10是本申请实施例中网络设备的一实施例示意图；
图11是本申请实施例中数据分析网元的一实施例示意图；
图12是本申请实施例中网络设备的另一实施例示意图；
图13是本申请实施例中网管网元的一实施例示意图；
图14是本申请实施例中切片管控网元的另一实施例示意图；
图15是本申请实施例中网管网元的一实施例示意图；
图16是本申请实施例中切片管控网元的另一实施例示意图；
图17是本申请实施例中网管网元的另一实施例示意图；
图18是本申请实施例中网络设备的另一实施例示意图；
图19是本申请实施例中网管网元的另一实施例示意图。
具体实施方式
本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”“第三”、“第四”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的术语在适当情况下可以互换，这仅仅是描述本申请的实施例中对相同属性的对象在描述时所采用的区分方式。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，以便包含一系列单元的过程、方法、系统、产品或设备不必限于那些单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它单元。
第五代(5th generation，5G)网络采用了网络切片的形式，从而实现了为不同需求的业务划分适合特性的网络资源。不同业务的需求不同，网络切片的类型也不相同，如图1所示，介绍了几种网络切片的类型，以及与租户和网络资源的对应关系。当然，本申请实施例所提供的方案不限于5G网络，所有包含网络切片的网络都适用。
图1为本申请实施例中网络切片的一场景示意图。
如图1所示，网络切片有多种不同类型，如：增强移动宽带(enhanced mobile broadband，eMBB)、超高可靠性低时延通信(ultra high-reliability and low-latency communication，URLLC)、大规模物联网(massive internet of things，mIoT)等。当然，网络切片的类型不限于这里列举的几种，网络切片还可以有自定义类型。
每种类型的网络切片都有各自的特点，所适用的领域也不太相同，例如：
eMBB主要用于超高清视频、全息技术、增强现实、虚拟现实等应用，对网络带宽和速率要求较高。
URLLC主要用于无人驾驶、车联网、自动工厂、远程医疗等领域，要求低时延和高可 靠性。
mIoT主要用于海量的物联网传感器部署于测量、建筑、农业、物流、智慧城市、家庭等领域，对时延和移动性的要求不高。
租户可以根据自己的需求，租用不同类型的网络切片，租户多是提供各种应用的企业。
网络切片实际上是对无线接入网资源、核心网资源以及传输资源的划分，各种不同类型的切片在为用户提供服务时，由相应的无线接入网资源、核心网资源以及传输资源为用户提供业务支持。
本申请中涉及的网络切片也可以简称为切片，包括但不限于切片、切片实例或切片子实例，其中切片可以通过单个网络切片选择支撑信息(single network slice selection assistance information，S-NSSAI)ID唯一地标识，切片实例可以通过网络切片信息(network slice information，NSI)ID唯一地标识，切片子实例可以通过网络切片选择信息(network slice selection information，NSSI)ID唯一地标识。
网络切片的资源是由网管网元进行管理和控制的，其中网管网元是指具备部署网络资源，并对网络的运行具备管理和维护功能的设备。网管网元可以位于运营商网络的管理面，例如网管网元可以为运行管理和维护网元OAM,网管网元也可以位于运营商网络的控制面，例如网管网元也可以为网络切片选择功能网元NSSF。网管网元可以根据网络切片的实际情况通知网络设备，例如：接入网设备、核心网设备、传输网设备或者其他切片管控网元调整该网络切片的相应资源。
在切片管控网元管控网络切片的资源时，还可以向数据分析网元获取与该网络切片相关的信息，例如：与该网络切片相对应的区域信息或者时间信息，这样，网络设备可以根据该网络切片相对应的区域信息或者时间信息进行资源调度，可以提高资源调度的准确度和利用率，还可以提高网络切片的性能。数据分析网元可以为网络数据分析网元NWDAF，其也可以位于运营商网络的管理面，例如数据分析网元可以为MDAS。
图2为本申请实施例中网络切片的资源调度的方法的一实施例示意图。
如图2所示，本申请实施例提供的网络切片的资源调度的方法的一实施例可以包括：
101、切片管控网元向数据分析网元发送请求，所述请求包括对第一网络切片的服务体验要求信息。
切片管控网元是指具备管理和控制网络切片的用户接入、资源部署、功能执行的网元，其可以位于运营商网络的控制面，例如切片管控网元为网络切片选择功能网元(NSSF)；也可以位于运营商网络的管理面，例如切片管控网元为运行管理和维护网元(OAM)。数据分析网元可以为网络数据分析网元NWDAF，其也可以位于运营商网络的管理面，例如数据分析网元可以为MDAS。
第一网络切片可以为运营商网络中的任意一个网络切片，可以是新建的处于测试状态的网络切片，也可以是处于稳定状态的网络切片。
所述第一网络切片的服务体验要求信息可以包括以下信息中的至少一项：
所述第一网络切片的用户数要求、业务的平均用户体验的要求，业务的用户满意比例的要求，其中，所述业务的用户满意比例为所述业务对应的用户体验不差于预设值的用户 数占所述业务总用户数的比例。其中，用户数要求包括可以指对用户数的过滤要求，用户数要求可以包括注册用户数要求和/或在线用户数要求。业务的平均用户体验的要求可以指对业务的平均用户体验的过滤要求，业务的平均用户体验的要求可以包括平均意见分(Mean Opinion Score，MOS)的过滤要求。业务的用户满意比例的要求可以指对业务的用户满意比例的过滤要求。
所述第一网络切片的服务体验要求信息指的是与目标服务水平协议要求信息对应的信息。
目标服务水平协议要求信息包括用户数要求、业务的平均用户体验的要求，业务的用户满意比例的要求，其中，所述业务的用户满意比例为所述业务对应的用户体验不差于预设值的用户数占所述业务总用户数的比例。用户数要求可以包括注册用户数要求和/或在线用户数要求。业务的平均用户体验的要求可以指对业务的平均用户体验的要求，其中，业务的平均用户体验可以包括平均意见分(Mean Opinion Score，MOS)。业务的用户满意比例的要求可以指对业务的用户满意比例的要求。
服务体验要求信息用于过滤第一网络切片中存在问题的区域和/或时间。
所述第一网络切片的服务体验要求信息可以包括正向服务体验要求信息和/或负向服务体验要求信息，所述正向服务体验要求信息为超额满足第一服务水平协议要求信息的过滤信息，所述负向服务体验要求信息为不满足第二服务水平协议要求信息的过滤信息。
第一服务水平协议要求信息和第二服务水平协议要求信息可以与目标服务水平协议要求信息相同，也可以不相同。
例如，目标服务水平协议要求为：切片的最大注册用户数＝100万，业务平均MOS＝3，业务的用户满意度比例＝90％。
在一种可能的设计中，当第一服务水平协议要求信息和第二服务水平协议要求信息与目标服务水平协议要求信息相同时，则正向服务体验要求信息为：切片的最大注册用户数>100万，业务平均MOS>3，业务的用户满意度比例>90％；负向服务体验要求信息为：切片的最大注册用户数<100万，业务平均MOS<3，业务的用户满意度比例<90％。
在另一种可能的设计中，当第一服务水平协议要求信息或第二服务水平协议要求信息与目标服务水平协议要求信息不同时，则正向服务体验要求信息为：切片的最大注册用户数>120万，业务平均MOS>4，业务的用户满意度比例>95％；负向服务体验要求信息为：切片的最大注册用户数<80万，业务平均MOS<2.5，业务的用户满意度比例<85％。
一种可能的实现方式，目标服务水平协议要求信息的可以通过如下方式确定：
所述切片管控网元获取所述第一网络切片的初始服务水平协议要求信息；
所述切片管控网元根据所述第一网络切片的初始服务水平协议要求信息确定至少一个服务水平协议要求信息；
所述切片管控网元将所述至少一个服务水平协议要求信息中的一个确定为所述目标服务水平协议要求信息。
其中，切片管控网元可以从租户或者网管网元或者运营商配置信息获取第一网络切片的初始服务水平协议要求信息。
在一种可能的设计中，初始服务水平协议要求信息有多个档，例如：
1、最大注册用户数量＝105万，业务平均MOS＝3，业务用户满意比例＝95％；
2、最大注册用户数量＝100万，业务平均MOS＝3，业务用户满意比例＝90％；
3、最大注册用户数量＝95万，业务平均MOS＝3，业务用户满意比例＝85％；
4、最大注册用户数量＝90万，业务平均MOS＝3，业务用户满意比例80％。
则切片管控网元可以直接从中确定一个作为目标服务水平协议要求信息。例如：确定最大注册用户数量＝95万，业务平均MOS＝3，业务用户满意比例＝85％作为目标服务水平协议要求信息。
在另一种可能的实现方式中，初始服务水平协议要求信息仅有一档，例如：最大注册用户数量＝100万，业务平均MOS＝3，业务用户满意比例＝90％，则切片管控网元可以根据初始服务水平协议要求信息确定多档服务水平协议要求信息，例如：
1、最大注册用户数量＝105万，业务平均MOS＝3，业务用户满意比例＝95％；
2、最大注册用户数量＝100万，业务平均MOS＝3，业务用户满意比例＝90％；
3、最大注册用户数量＝95万，业务平均MOS＝3，业务用户满意比例＝85％；
4、最大注册用户数量＝90万，业务平均MOS＝3，业务用户满意比例80％。
切片管控网元再从多档服务水平协议要求信息中确定一个作为目标服务水平协议要求信息。例如：最大注册用户数量＝100万，业务平均MOS＝3，用户满意比例＝90％。
102、数据分析网元接收切片管控网元发送的请求后，确定与所述服务体验要求信息对应的第一区域信息和/或第一时间信息。
第一区域信息通常是指符合正向服务体验要求信息，或者符合负向服务体验要求信息的区域。第一时间信息通是指符合正向服务体验要求信息，或者符合负向服务体验要求信息的时间。
网络切片通常与区域和时间是有对应关系的，一个网络切片在不同区域，或者不同时间所对应的无线接入网资源、核心网资源或者传输网资源也会有不同，所以同一网络切片可能在有的区域或/和有的时间能满足目标服务水平协议要求信息，有的区域或/和有的时间不能满足目标服务水平协议要求信息，有的区域或/和有的时间超额满足目标服务水平协议要求信息。
本申请实施例中，数据分析网元可以根据服务体验要求信息，确定不能满足目标服务水平协议要求的区域或时间，或者确定超额满足目标服务水平协议要求的区域或时间。具体地，数据分析网元能够根据负向的服务体验要求信息，确定不能满足目标服务水平协议要求的区域或时间，或者，数据分析网元能够根据正向的服务体验要求信息，确定超额满足目标服务水平协议要求的区域或时间。
区域信息可以是第三代合作伙伴计划(3rd generation partnership project，3GPP)通信网络中定义的区域信息，可简称通信网络区域信息，比如服务小区A或注册区域B。该区域信息也可以是非3GPP通信网络中定义的区域信息，比如该位置信息为某具体的地理位置范围，例如，经纬度或者全球定位系统(global positioning system，GPS)位置信息，可简称地理区域信息，本申请实施例对此并不限定。
时间信息，可以是绝对时间，例如，从2017年1月1日00:00至2017年1月30日24:00，或者，每周一至周五；也可以是相对时间信息，例如相对于接收到该请求之前的一个月内。该时间信息的粒度可以是以小时为粒度，也可以是以分钟或者天为粒度，本申请实施例对此并不限定。
103、数据分析网元向所述切片管控网元发送响应，所述响应中包括与所述服务体验要求信息对应的第一区域信息和/或第一时间信息。
一种可能的实现方式，所述数据分析网元确定所述第一区域信息和/或所述第一时间信息所对应的所述第一网络切片的第一服务体验信息；则所述响应中还包括所述第一区域信息和/或所述第一时间信息所对应的所述第一网络切片的第一服务体验信息。
第一服务体验信息是与第一区域信息和/或所述第一时间信息所对应的。
一种可能的实现方式，所述第一网络切片的第一服务体验信息包括以下信息中的至少一项：所述第一网络切片的用户数信息、业务的用户数信息、业务的平均服务体验信息、业务的用户满意比例信息，其中，所述业务的用户满意比例为所述业务对应的用户体验不差于预设值的用户数占所述业务总用户数的比例。第一网络切片的用户数信息可以包括第一网络切片的注册用户数信息和/或在线用户数信息。业务的用户数信息可以包括业务的注册用户数信息和/或在线用户数信息。业务的平均服务体验信息可以包括业务的平均意见分MOS。业务的用户满意比例信息例如可以是：业务A的业务用户满意度是指业务A的MOS大于3的用户比例为90％。
104、切片管控网元接收所述数据分析网元发送的响应后，根据所述第一区域信息和/或第一时间信息向网络设备发送第二区域信息和/或第二时间信息。
第二区域信息可以与第一区域信息相同，第二时间信息也可以与第一时间信息相同。
第二区域信息也可以与第一区域信息不相同，第二时间信息也可以与第一时间信息不相同。
切片管控网元可以根据第一区域信息确定第二区域信息，第二区域信息与第一区域信息的格式可以不相同。
切片管控网元可以根据第一时间信息确定第二时间信息，第二时间信息与第一时间信息的格式可以不相同，也可以是第二时间信息所指示的时间包含于第一区域信息所指示的时间。
一种可能的实现方式，所述响应还包括所述第一区域信息和/或所述第一时间信息所对应的所述第一网络切片的第一服务体验信息，则所述切片管控网元可以根据第一服务体验信息确定所述第二区域信息和/或所述第二时间信息。
第一区域信息所指示的区域为第一区域，第二区域信息所指示的区域为第二区域，第二区域包含于第一区域中，也可以理解为，第二区域是第一区域中资源问题更严重的区域，例如资源更为匮乏的区域或者资源更为冗余的区域。
一种可能的实现方式，切片管控网元还可以向所述网络设备发送所述第二区域信息和/或所述第二时间信息对应的切片质量信息，其中，所述切片质量信息包括以下信息的至少一项：所述第二区域信息和/或所述第二时间信息的对应所述第一网络切片的第二服务体验 信息、所述第二服务体验信息相对于所述第一网络切片的目标服务水平协议要求信息的满足程度信息。
第二服务体验信息是与所述第二区域信息和/或所述第二时间信息所对应的。
所述满足程度信息包括无法满足、满足或者超额满足。
关于无法满足、满足或者超额满足可以理解为：
例如，网络切片的服务水平协议要求(slice SLA requirement)为：业务平均MOS＝3，业务用户满意度比例＝90％，则以下几种情况：
1、实际业务平均MOS＝4，实际业务用户满意度比例95％，属于超额满足；
2、实际业务平均MOS＝3，实际业务用户满意度比例90％，属于满足；
3、实际业务平均MOS＝2，实际业务用户满意度比例85％，属于不满足。
除上述无法满足、满足或者超额满足表现形式外，满足程度信息的还可以存在其他表现形式，例如满足程度信息表现为一个百分比数值，如服务体验信息80％满足目标服务水平协议要求信息，或者服务体验信息120％满足目标服务水平协议要求信息，此处不做具体限制。
105、网络设备可以根据所述第二区域信息和/或第二时间信息为所述第一网络切片调度资源。
网络设备包括以下设备的至少一个：接入网设备、核心网设备、传输网设备和网管网元。
接入网设备可以为(radio access network，RAN)设备，例如：5G基站(gNodeB，gNB)。
核心网设备可以包括以下设备的至少一个：用户面功能网元(user plane function，UPF)、策略控制网元(policy control function，PCF)、会话管理功能网元(session management function，SMF)、接入和移动性管理功能网元(access and mobility management function，AMF)。
传输网设备可以包括无线接入网与核心网之间的回传链路，如路由器等。
当切片管控网元为NSSF时，网管网元可以为OAM。
当所述网络设备为接入网设备时，所述接入网设备根据所述第二区域信息为所述第一网络切片调度接入网资源，所述接入网设备根据所述第二时间信息为所述第一网络切片调度接入网资源。
当所述网络设备为核心网设备时，所述核心网设备根据所述第二区域信息为所述第一网络切片调度核心网资源，所述核心网设备根据所述第二时间信息为所述第一网络切片调度核心网资源。
当所述网络设备为传输网设备时，所述传输网设备根据所述第二区域信息为所述第一网络切片调度传输网资源，所述传输网设备根据所述第二时间信息为所述第一网络切片调度传输网资源。
当所述网络设备为网管网元时，所述网管网元控制接入网设备或核心网设备或传输网设备调整所述第一网络切片的第二区域和/或第二时间的相应资源的调度量。
本申请实施例中，网络设备在为第一网络切片调度资源时，可以根据第二区域信息和/或第二时间信息做资源调度，可以提高资源调度的准确度和利用率，也提高了第一网络切片的性能。
一种可能的实现方式，上述步骤101中，切片管控网元发送请求时，该请求中还可以包括第三区域信息和/或第三时间信息。
本申请实施例中的请求可以是订阅请求消息，或者直接请求消息，直接请求消息要求NWDAF立即返回响应消息，而订阅请求消息要求NWDAF在满足订阅上报条件后返回响应消息。
所述第三区域信息所指示的第三区域包括所述第一区域信息所指示的第一区域，所述第三区域信息用于向所述数据分析网元请求所述第三区域中与所述服务体验要求信息对应的所述第一区域信息。
所述第三时间信息所指示的第三时间包括所述第一时间信息所述指示的第一时间，所述第三时间信息用于向所述数据分析网元请求所述第三时间中与所述服务体验要求信息对应的所述第一时间信息。
本申请实施例中，第三区域包括第一区域，第一区域包括第二区域。第三时间包括第一时间，第一时间包括第二时间。
一种可能的实现方式，上述步骤101：所述切片管控网元向数据分析网元发送请求之前，还可以包括：
所述切片管控网元获取所述第一网络切片的第三服务体验信息；
若所述第三服务体验信息与所述目标服务水平协议要求信息不对应，则所述切片管控网元确定所述第一网络切片的服务体验要求信息，所述第一网络切片的服务体验要求信息对应于所述目标服务水平协议要求。
本申请实施例的一种可能的设计中，第三服务体验信息与第一网络切片的第四区域信息和/或第四时间信息对应，换句话说，第三服务体验信息是第四区域信息和/或第四时间信息对应的第一网络切片的服务体验信息。其中，第四区域可以是整个网络切片的服务区域，也可以是整个网络切片的部分服务区域；而第四时间可以是整个网络切片的所有服务时间，也可以是整个网络切片的部分服务时间。第一服务体验信息是与第一网络切片对应的第一区域信息和/或第一时间信息对应的，第二服务体验信息是与第一网络切片对应的第二区域信息和/或第二时间信息对应的。第四区域包括第一区域，第一区域包括第二区域；第四时间包括第一时间，第一时间包括第二时间。
一种可能的实现方式，第三服务体验信息与所述目标服务水平协议要求信息是否对应可以通过如下方式确定：
所述切片管控网元将所述第三服务体验信息与所述目标服务水平协议要求信息进行比较；
若所述第三服务体验信息不满足或者超额满足所述目标服务水平协议要求信息，则所述切片管控网元确定所述第三服务体验信息与所述目标服务水平协议要求信息不对应。
一种可能的实现方式，在确定所述第三服务体验信息与所述目标服务水平协议要求信 息不对应后，所述切片管控网元确定所述第一网络切片的服务体验要求信息，可以包括：
若所述第三服务体验信息不满足所述目标服务水平协议要求信息，则所述切片管控网元确定与不满足情况下对应的所述第一网络切片的服务体验要求信息，也就是前文所描述的负向服务体验要求信息。
若所述第三服务体验信息超额满足所述目标服务水平协议要求信息，则所述切片管控网元确定与超额满足情况下对应的所述第一网络切片的服务体验要求信息，也就是前文所描述的正向服务体验要求信息。
在第三服务体验信息不满足或超额满足所述目标服务水平协议要求信息时，还可以调整第一网络切片的服务用户数量，调整方式可以为：
若所述第三服务体验信息不满足所述目标服务水平协议要求信息，则所述切片管控网元减少所述第一网络切片的服务用户数量；
若所述第三服务体验信息超额满足所述目标服务水平协议要求信息，则所述切片管控网元增加所述第一网络切片的服务用户数量。
实际上，在上述图2所对应的实施例中，无论是第一区域还是第二区域都可以归结为是问题区域，无论是第一时间信息还是第二时间信息都可以归结为是问题时间。
在上述实施例中，还可以先确定导致问题区域和/或问题时间的原因所在的网络域，再进一步确定出网络设备，因此该网络切片的资源调度的方法还包括以下两种可能的实现方式，分别为:
一种可能的实现方式，网络切片的资源调度的方法还可以包括：
切片管控网元确定导致问题区域和/或问题时间的原因在于第一网络域；所述切片管控网元根据所述第一网络域确定所述网络设备。
其中，第一网络域可以是接入网域，也可以是核心网域，也可以是传输网域。
所述问题区域包括第一区域或第二区域，所述问题时间包括第一时间或第二时间。
一种可能的设计中，所述切片管控网元可以从网管网元获知导致问题区域和/或问题时间的原因在于第一网络域。
当该切片管控网元是位于运营商网络控制面的切片管控网元(如NSSF)时，该切片管控网元可以与位于运营商网络管理面的网管网元(如OAM)交互，从而获知第一网络域是导致问题区域和/或问题时间的原因；当该切片管控网元是位于运营商网络管理面的切片管控网元(如NSMF)时，该切片管控网元可以与位于运营商网络管理面的网管网元(如MDAS)交互，从而获知第一网络域是导致问题区域和/或问题时间的原因。
另一种可能的设计中，还可以是切片管控网元自行确定导致问题区域和/或问题时间的原因在于所述网络设备所在的第一网络域。
无论通过哪种设计获知导致问题区域和/或问题时间的原因在于所述网络设备所在的第一网络域后，切片管控网元从所述第一网络域中确定出网络设备，并向该网络设备发送图2实施例中所述的问题区域/问题时间。其中，所述网络设备可以是指第一网络域中的所有网络设备，也可以是第一网络域中的部分网络设备，例如仅是与问题区域/问题时间相关的第一网络域中的网络设备。
在上述第一种设计中，若所述切片管控网元从网管网元获知导致问题区域和/或问题时间的原因在于第一网络域，则所述切片管控网元还可从所述网管网元获取第一可信度信息，所述第一可信度信息用于指示导致问题区域和/或问题时间的原因在于第一网络域的可信程度；所述切片管控网元根据所述第一可信度信息确定所述网络设备。其中，第一可信度信息的表现形式具体可以参考图5实施例中的用户数量限制信息的可信度的表现形式，此处不再赘述。
所述切片管控网元根据所述第一可信度信息确定所述网络设备的具体方法为：当所述第一可信度信息高于预设的可信度值时(如第一可信度信息值大于90％)，则切片管控网元从第一网络域中确定出所述网络设备；反之，当所述第一可信度信息低于预设的可信度值时(如第一可信度信息值小于60％)，则切片管控网元不会从第一网络域中确定出所述网络设备，换句话说，后续切片管控网元向其发送问题区域/问题时间的网络设备不会出自第一网络域。
另一种可能的实现方式中，网络切片的资源调度的方法还可以包括：
所述切片管控网元确定导致所述第三服务体验信息与所述目标服务水平协议要求信息不对应的原因在于第二网络域，所述切片管控网元根据所述第二网络域确定所述网络设备。
在一种可能的设计中，所述切片管控网元确定导致所述第三服务体验信息与所述目标服务水平协议要求信息不对应的原因在于第二网络域，可以包括：所述切片管控网元从网管网元获知导致所述第三服务体验信息与所述目标服务水平协议要求信息不对应的原因在于所述第二网络域。
当该切片管控网元是位于运营商网络控制面的切片管控网元(如NSSF)时，该切片管控网元可以与位于运营商网络管理面的网管网元(如OAM)交互，从而获知所述第二网络域是导致所述第三服务体验信息与所述目标服务水平协议要求信息不对应的原因；当该切片管控网元是位于运营商网络管理面的切片管控网元(如NSMF)时，该切片管控网元可以与位于运营商网络管理面的网管网元(如MDAS)交互，从而获知所述第二网络域是导致所述第三服务体验信息与所述目标服务水平协议要求信息不对应的原因。
在另一种可能的设计中，还可以所述切片管控网元自行确定导致所述第三服务体验信息与所述目标服务水平协议要求信息不对应的原因在于第二网络域。
无论通过哪种设计获知导致所述第三服务体验信息与所述目标服务水平协议要求信息不对应的原因在于第二网络域后，切片管控网元从所述第二网络域中确定出网络设备，并向该网络设备发送图2实施例中所述的问题区域/问题时间。其中，所述网络设备可以是指第二网络域中的所有网络设备，也可以是第二网络域中的部分网络设备，例如仅是与问题区域/问题时间相关的第二网络域中的网络设备。
在上述第一种设计中，若所述切片管控网元从网管网元获知导致所述第三服务体验信息与所述目标服务水平协议要求信息不对应的原因在于第二网络域，则所述切片管控网元还可从所述网管网元获取第二可信度信息，所述第二可信度信息用于指示导致所述第三服务体验信息与所述目标服务水平协议要求信息不对应的原因在于第二网络域的可信程度； 所述切片管控网元根据所述第二可信度信息确定所述网络设备。其中，第二可信度信息的表现形式具体可以参考图5实施例中的用户数量限制信息的可信度的表现形式，此处不再赘述。
所述切片管控网元根据所述第二可信度信息确定所述网络设备的具体方法为：当所述第二可信度信息高于预设的可信度值时(如第二可信度信息值大于90％)，则切片管控网元从第二网络域中确定出所述网络设备；反之，当所述第二可信度信息低于预设的可信度值时(如第二可信度信息值小于60％)，则切片管控网元不会从第二网络域中确定出所述网络设备，换句话说，后续切片管控网元向其发送问题区域/问题时间的网络设备不会出自第二网络域。
以上从切片管控网元、网络设备和数据分析网元的角度描述了本申请实施例中网络切片的资源调度的方案。下面，结合图3，介绍本申请实施例中另一网络切片的资源调度的方法。
如图3所示，本申请实施例提供的网络切片的资源调度的方法的另一实施例可以包括：
201、网管网元确定第一网络切片的资源配置信息，所述资源配置信息包括最大资源配置信息和/或保证资源配置信息。
所述最大资源配置信息用于指示所述第一网络切片最大能使用的资源，所述保证资源配置信息用于指示所述第一网络切片保证能使用的资源。
网管网元是指具备部署网络资源，并对网络的运行具备管理和维护功能的设备，例如网管网元可以为OAM或者NSSF。
一种可能的实现方式，本申请实施例中，可以根据所述第一网络切片的目标服务水平协议要求信息，确定所述第一网络切片的资源配置信息。
目标服务水平协议要求信息可以与图2所对应实施例中所描述的目标服务水平协议要求信息相同，此处不再重复介绍。
202、所述网管网元向所述网络设备发送所述第一网络切片的资源配置信息。
所述网络设备可以包括以下设备的至少一个：接入网设备、核心网设备和传输网设备。其中，接入网设备、核心网设备和传输网设备的含义见步骤105，此处不再赘述。当所述网络设备为接入网设备时，所述最大资源配置信息为最大空口资源配置信息和/或保证资源配置信息为保证空口资源配置信息。
一种可能的实现方式，为了更精细化的调度资源，该资源配置信息可以不对应整个第一网络切片，可以是对应第一网络切片的一个或多个区域的资源配置信息，也可以是对应一段时间或几段时间的资源配置信息。
这种情形下，所述最大资源配置信息和/或保证资源配置信息为第一时间对应的最大资源配置信息和/或保证资源配置信息；或者，所述最大资源配置信息和/或保证资源配置信息为第一区域对应的最大资源配置信息和/或保证资源配置信息。
203、网络设备接收网管网元发送的第一网络切片的资源配置信息后，根据所述第一网络切片的资源配置信息为所述第一网络切片调度资源。
为所述第一网络切片调度资源时，网络设备会首先考虑资源的需求量，若资源的需求 量不超过保证资源配置信息所指示的第一网络切片保证能使用的资源，则会为该第一网络切片调度该需求量大小的资源，第一网络切片保证能使用的资源范围内，网络设备都会为第一网络切片调度。若需求量超过第一网络切片保证能使用的资源，但没有超过最大资源配置信息所指示的第一网络切片最大能使用的资源，会根据实际情况至少为第一网络切片调度保证能使用的资源大小的资源量。
例如：第一网络切片最大能使用的资源为20个单位，第一网络切片保证能使用的资源为11个单位，若需求量为8个单位，则网络设备会调度8个单位的资源量给第一网络切片，若需求量为15个单位，则在资源量充足的情况下，会调度15个单位量给第一网络切片，若资源量不充足，也至少会调度11单位量的资源量给第一网络切片。
本申请实施例中，网络设备可以根据网管网元的指示在最大能使用的资源范围下，优先根据保证能使用的资源范围为某网络切片调度资源。该方法能使得网络设备根据网络切片的实际需要的资源量灵活地为该网络切片调度资源，并且承诺在网络切片需要时一定能为该网络切片调度保证能使用的资源范围量的资源，而在某些突发情况下，网络切片可能还允许使用最大能使用的资源范围量的资源。该方法既保证了网络切片有资源可用，也提高了资源的灵活性。
一种可能的实现方式，所述第一网络切片保证能使用的资源允许被第二网络切片使用。尤其是在第一网络切片无需使用过多资源时，保证能使用的资源范围内的剩余资源允许被其他网络切片所使用，只要能够保证在第一网络切片需要时一定能为该第一网络切片调度保证能使用的资源范围量的资源即可，该方法提高了资源利用的灵活性。
当所述最大资源配置信息和/或保证资源配置信息为第一时间对应的最大资源配置信息和/或保证资源配置信息时，所述网络设备可以根据所述第一时间对应的最大资源配置信息和/或保证资源配置信息为所述第一网络切片在所述第一时间调度资源。其中，第一时间可以包含于所述最大资源配置信息和/或保证资源配置信息中，也可以是预先协商好的或者包含在所述最大资源配置信息和/或保证资源配置信息外的，不需要包含于所述最大资源配置信息和/或保证资源配置信息中。
当所述最大资源配置信息和/或保证资源配置信息为第一区域对应的最大资源配置信息和/或保证资源配置信息时，所述网络设备可以根据所述第一区域对应的最大资源配置信息和/或保证资源配置信息为所述第一网络切片在所述第一区域调度资源。其中，第一区域可以包含于所述最大资源配置信息和/或保证资源配置信息中，也可以是预先协商好的或者包含在所述最大资源配置信息和/或保证资源配置信息外的，不需要包含于所述最大资源配置信息和/或保证资源配置信息中。
本申请实施例中，可以根据网管网元的指示在最大能使用的资源范围下，优先根据保证能使用的资源范围为某网络切片调度资源。该方法能使得网络设备根据网络切片的实际需要的资源量灵活地为该网络切片调度资源，并且承诺在网络切片需要时一定能为该网络切片调度保证能使用的资源范围量的资源，而在某些突发情况下，网络切片可能还允许使用最大能使用的资源范围量的资源。该方法既保证了网络切片有资源可用，也提高了资源的灵活性。
以上描述了为第一网络切片调度资源时，需要参考资源配置信息的情况，实际上，资源配置信息并不是一经配置就不再变化的，网管网元会根据实际情况，更新第一网络切片的资源配置信息，再及时通知给网络设备。资源配置信息的更新过程可以参阅图4进行理解，如图4所示，在上述图3对应的实施例的基础上，本申请实施例提供的网络切片的资源调度的方法的另一实施例可以包括：
301、网管网元获取所述网络设备为所述第一网络切片调度的资源的信息。
若考虑到更精细化调度的情形，该资源信息可以包括对应区域或者对应时间的资源的信息。
也就是说，所述资源的信息可以包括所述第一网络切片的第二区域对应的资源的信息，和/或，所述资源的信息可以包括所述第一网络切片的第二时间对应的资源的信息。第一区域可以与第二区域相同，也可以不相同，第二时间可以与第一时间相同，也可以不相同。
302、网管网元从切片管控网元或数据分析设备获取第一网络切片的切片质量信息。
切片质量信息包括所述第一网络切片的服务体验信息和/或所述第一网络切片的服务体验信息相对于所述目标服务水平协议要求的满足程度信息。
第一网络切片的服务体验信息可以与图2所对应实施例中所描述的第一服务体验信息、第二服务体验信息或第三服务体验信息相同，此处不再重复介绍。
满足程度信息可以包括不满足、满足或超额满足或其他表现形式，也与图2所对应实施例中所描述的满足程度信息相同，此处不再重复介绍。
若步骤301中所述资源的信息是第二区域对应的资源的信息，则所述第一网络切片对应的切片质量信息可以包括所述第一网络切片的第二区域对应的服务体验信息和/或所述第二区域对应的服务体验信息相对于所述目标服务水平协议要求的满足程度信息。
所述第二区域为无法满足或超额满足所述目标服务水平协议要求的区域。
若资源的信息是第二时间对应的资源的信息，则所述第一网络切片对应的切片质量信息包括所述第一网络切片的第二时间对应的服务体验信息和/或所述第二时间对应的服务体验信息相对于所述目标服务水平协议要求的满足程度信息。
所述第二时间为无法满足或超额满足所述目标服务水平协议要求的时间。
303、网管网元根据所述网络设备为所述第一网络切片调度的资源的信息和所述切片质量信息，更新所述第一网络切片的资源配置信息。
若资源的信息是第二区域对应的资源的信息，则所述网管网元根据所述第二区域对应的资源的信息和所述第二区域对应的服务体验信息，更新所述第一网络切片的资源配置信息。
若资源的信息是第二时间对应的资源的信息，则所述网管网元根据所述第二时间对应的资源的信息和所述第二时间对应的服务体验信息，更新所述第一网络切片的资源配置信息。
若资源的信息是第二区域和第二时间对应的资源的信息，则所述网管网元根据所述第二区域对应的资源的信息和所述第二区域对应的服务体验信息，以及第二时间对应的资源的信息和所述第二时间对应的服务体验信息，更新所述第一网络切片的资源配置信息。
因为资源配置信息包括最大资源配置信息和/或保证资源配置信息，所以在更新时，所述网管网元更新所述最大资源配置信息和/或保证资源配置信息，使得所述更新后的最大资源配置信息不小于所述网络设备为所述第一网络切片调度的资源。
304、所述网管网元向所述网络设备发送所述更新后的资源配置信息。
更新后的资源配置信息包括更新后的最大资源配置信息和/或更新后的保证资源配置信息。
305、网络设备根据更新后的资源配置信息，为所述第一网络切片调度资源。
网络设备可以根据网管网元的指示在更新后的最大能使用的资源范围下，优先根据更新后的保证能使用的资源范围为第一网络切片调度资源，提高了资源的灵活性。
本申请实施例中，网管网元可以及时更新第一网络切片的资源配置信息，从而可以使得网络设备及时为第一网络切片调度的资源进行调整，提高了资源调度的准确性和第一网络切片的性能。
实际上，若网管网元不更新资源配置信息，网络设备也可以调整为第一网络切片调度的资源，这种情形下，可以是：
网络设备接收切片管控网元发送的所述第一网络切片对应的切片质量信息，所述切片质量信息包括所述第一网络切片的服务体验信息和/或所述第一网络切片的服务体验信息相对于目标服务水平协议要求的满足程度信息；
网络设备根据所述切片质量信息调整为所述第一网络切片调度的资源。
其中，所述第一网络切片对应的切片质量信息可以包括所述第一网络切片的第二区域对应的服务体验信息和/或所述第二区域对应的服务体验信息相对于所述目标服务水平协议要求的满足程度信息。
所述第一网络切片对应的切片质量信息可以包括所述第一网络切片的第二时间对应的服务体验信息和/或所述第二时间对应的服务体验信息相对于所述目标服务水平协议要求的满足程度信息。
所述第一网络切片对应的切片质量信息可以包括所述第一网络切片的第二区域和第二时间对应的服务体验信息和/或所述第二区域和第二时间对应的服务体验信息相对于所述目标服务水平协议要求的满足程度信息。
所述第二区域为无法满足或超额满足所述目标服务水平协议要求的区域。
所述第二时间为无法满足或超额满足所述目标服务水平协议要求的时间。
网络设备根据所述切片质量信息调整为所述第一网络切片调度的资源，可以包括：若所述第一网络切片的服务体验信息无法满足所述目标服务水平协议要求，则所述网络设备增加为所述第一网络切片调度的资源；若所述第一网络切片的服务体验信息超额满足所述目标服务水平协议要求，则所述网络设备减少为所述第一网络切片调度的资源。
以上的方案，不管是网管网元及时更新第一网络切片的资源配置信息，还是网络设备根据第一网络切片对应的切片质量信息调整为第一网络切片调度的资源，都可以提高资源调度的准确性和第一网络切片的性能。两种方案相比，前者可能更为准确，因为网管网元经对更多维度的、更大数量的数据分析后而获取到更新后的资源配置信息，其准确性更高； 后者更为及时，网络设备直接根据第一网络切片对应的切片质量信息便可考虑调整为第一网络切片调度的资源。若将两者结合使用，则可以达到更好的效果。
以上图3和图4的方案介绍了在最大资源配置信息和/或保证资源配置信息指示下的网络切片的资源调度的方案。实际上，与网络切片的资源调度相关的内容还有用户数量的控制，下面结合图5介绍本申请实施例中用户数量控制的方法。如图5所示，本申请实施例提供的用户数量控制的方法的一实施例可以包括：
401、所述网管网元确定目标网络切片的用户数量限制信息以及指示信息。
目标网络切片的用户数量限制信息指的是限制接入用户的数量，可以包括在线用户数信息、或者注册用户数信息。用户数量限制信息一般指的是最大用户数信息，也即用户容量信息。
所述指示信息用于指示所述目标网络切片的状态信息或者所述用户数量限制信息的可信度。
所述状态信息包括测试状态或稳定状态。其中，测试状态是指目标网络切片是一个新建切片或者处于测试阶段，换句话说，运营商和租户之间还为就该目标网络切片正式签订服务水平协议；稳定状态是指目标网络切片处于稳定阶段，换句话说，运营商和租户之间已经就该目标网络切片正式签订了服务水平协议。
本申请实施例并不限定指示测试状态或稳定状态的具体表现形式，例如，其可以是二进制枚举值，0表示测试状态，1表示稳定状态。也可以用F表示测试状态，T表示稳定状态。当然，还可以用其他形式来表示测试状态或稳定状态。
可信度指的是可以相信的程度。本申请实施例并限定不可信度的具体表现形式，例如，可信度可以是一个[0,1]区间内的浮点数，浮点数值越大表明可以信赖的程度越高；又如，可信度可以是0-100％之间的百分制比例数值，比例越高表明可以信赖的程度越高；又如，可信度信息还可以是预先定义的集合(如{A,B,C,D})中的枚举值，其中，不同枚举值对应的可以信赖的程度不同(如，A>B>C>D)。
网管网元是指具备部署网络资源，并对网络的运行具备管理和维护功能的设备，例如可以为OAM。
一种可能的实现方式，本申请实施例中不限定网管网元确定目标网络切片的用户数量限制信息的方式，其中一种可以是：
所述网管网元获取所述目标网络切片的服务水平协议要求信息；
所述网管网元根据所述服务水平协议要求信息确定所述目标网络切片的用户数量限制信息。
其中，网管网元可以从租户获取到所述目标网络切片的服务水平协议要求信息，服务水平协议要求信息与上述实施例中所描述的服务水平协议要求信息的含义基本相同，此处不再做详细赘述。
402、所述网管网元向切片管控网元发送所述目标网络切片的用户数量限制信息，以及所述指示信息。
切片管控网元是指具备管理和控制网络切片的用户接入、资源部署、功能执行的网元， 例如切片管控网元为网络切片选择功能网元(NSSF)。为了实现对用户数量的更精细化控制，所述网管网元向所述切片管控网元发送所述目标网络切片的区域信息和所述区域信息所对应的用户数量限制信息。
所述区域信息和所述区域信息所对应的用户数量限制信息用于所述切片管控网元针对所述区域信息所指示的区域，在所述区域信息所对应的用户数量限制信息所指示的范围内控制所述目标网络切片所服务的用户的数量。
也可以是，所述网管网元向所述切片管控网元发送所述目标网络切片的时间信息和所述时间信息所对应的用户数量限制信息。
所述时间信息和所述时间信息所对应的用户数量限制信息用于针对所述时间信息所指示的时间，在所述时间信息所对应的用户数量限制信息所指示的范围内控制所述目标网络切片所服务的用户的数量。
该实施例中的区域信息和时间信息的含义都可以参与前文步骤102中的描述进行理解，本处不再重复赘述。
403、切片管控网元接收网管网元发送的目标网络切片的用户数量限制信息，以及指示信息之后，根据所述指示信息和所述用户数量限制信息控制所述目标网络切片所服务的用户的数量。
当所述指示信息用于指示所述目标网络切片的状态信息时，所述切片管控网元根据所述用户数量限制信息按照所述状态信息所对应的控制方式，控制所述目标网络切片所服务的用户的数量。
当所述状态信息为测试状态时，所述控制方式为阶梯控制的方式。也就是说，所述切片管控网元可以以阶梯的方式将所述用户数量限制信息所限制的数量的用户接入所述目标网络切片或将已由所述目标网络切片提供服务的用户剔除。
当所述状态信息为稳定状态时，所述控制方式为一次性控制的方式。也就是说，所述切片管控网元根据所述目标网络切片的稳定状态，一次将所述用户数量限制信息所限制的数量的用户接入所述目标网络切片或将已由所述目标网络切片提供服务的用户剔除。
当所述指示信息用于指示所述用户数量限制信息的可信度时；所述切片管控网元根据所述用户数量限制信息按照所述可信度所对应的控制方式，控制所述目标网络切片所服务的用户的数量。
在所述可信度不符合可信度要求时，所述控制方式为阶梯控制的方式。也就是说，所述切片管控网元以阶梯的方式将所述用户数量限制信息所限制的数量的用户接入所述目标网络切片或将已由所述目标网络切片提供服务的用户剔除。
在所述可信度符合可信度要求时，所述控制方式为一次性控制的方式。也就是说，所述切片管控网元一次将所述用户数量限制信息所限制的数量的用户接入所述目标网络切片或将已由所述目标网络切片提供服务的用户剔除。
关于可信度是否符合可信度要求可以参与前文步骤401中可信度的表现形式进行理解，如果可信度是具体的数值，可以通过设置可信度阈值的方式，来确定可信度是否大于可信度阈值。如果可信度是预先设定的枚举值集合，可以通过确定可信度是否是对应的枚 举值的方式来确定是够满足可信度要求。并且，不同的可信度对应的控制方式不同，并不限于上述阶梯方式或一次性方式，还可能存在其他对应的控制方式。
本申请实施例中目标网络切片的用户数量限制信息可以是所述切片管控网元接收所述网管网元发送的所述目标网络切片的服务水平协议要求信息，所述服务水平协议要求信息中包括所述目标网络切片的用户数量限制信息。当然，若网管网元向切片管控网元发送的目标网络切片的服务水平协议要求信息中没有用户数量限制信息，那么可以单独发送用用户数量限制信息，而且可以与目标网络切片的服务水平协议要求信息并列发送。
当用户数量限制信息是某个区域对应的用户数量限制信息时，所述切片管控网元针对所述区域信息所指示的区域，根据所述指示信息和所述区域信息所对应的用户数量限制信息控制所述目标网络切片所服务的用户的数量。
当用户数量限制信息是某个时间对应的用户数量限制信息时，所述切片管控网元针对所述时间信息所指示的时间，根据所述指示信息和所述时间信息所对应的用户数量限制信息控制所述目标网络切片所服务的用户的数量。
以上分别介绍了图2至图5所对应的实施例，实际上，这几个实施例不是各不相关的，而是可以互相关联的，不管是网络切片的资源调度还是用户数量控制都是与网络切片的租户所提出的服务水平协议要求，以及网络切片的服务体验信息是相关的。图6所示出的网络切片场景下的网络架构的一实施例示意图，如图6所示，与上述实施例相关的网元有第三方的网元，例如：应用功能网元(Application Function，AF)、接入网设备、用于分配用户面或控制面资源的核心网设备(例如：AMF、PCF等)、切片管控网元(例如：NSSF)、数据分析网元(例如：NWDAF)和网管网元(例如：OAM)。其中，切片管控网元(例如：NSSF)、数据分析网元(例如：NWDAF)其实也属于核心网设备。
在上述图6所对应的架构下，下面结合图7A介绍本申请实施例中与网络切片相关的资源调度和用户数控制的过程：
501、网管网元创建一个网络切片。
网管网元获取租户对于该网络切片的服务水平协议(Service Level Agreement，SLA)要求信息，其中SLA要求信息的具体内容和含义可参考图2中的目标服务水平协议要求信息的内容和含义。网管网元根据SLA要求信息创建该网络切片，这里的创建网络切片具体是指网管网元为该网络切片设置资源配置信息。
实际上，该处的网络切片不限于是新创建的网络切片，也可以是已有的网络切片，若是已有的网络切片，则不需要再设置资源配置信息。
资源配置信息可以是上述图3所对应的实施例中所描述的最大资源配置信息和/或保证资源配置信息。
资源配置信息用于指示对该网络切片所能调度的网络资源，该网络资源可以包括接入网资源或核心网资源，也还可以包括传输网资源。
在一种可能设计中，一个网络切片对应的接入网资源可以包括：该网络切片对应的可保证的空口资源或最大的空口资源。换句话说，网管网元为该网络切片配置接入网资源具体是指为该网络切片配置可保证的空口资源或最大的空口资源。其中，这里的空口资源可 以是实际的物理资源，如物理资源块(physical resource block，PRB)、接入网设备的处理器资源、存储资源等，也即网管网元指示接入网设备该调度的物理资源。空口资源也可以是体现空口性能的参数，如入网设备的上/下行数据丢包率，最大/平均无线资源控制(radio resource control，RRC)连接数，数据单元(data unit，DU)平均时延等，也即网管网元利用这些性能参数指示接入网设备该调度的物理资源。
在一种可能设计中，一个网络切片对应的核心网资源可以包括：该网络切片对应的可保证的核心网资源或最大的核心网资源。换句话说，网管网元为该网络切片配置核心网资源具体是指为该网络切片配置可保证的核心资源或最大的核心网资源。核心网资源的解释同上面接入网资源的示意，可以是具体的核心网物理资源，如UPF的存储资源量，AMF的CPU资源量，也可以是体现核心网性能的参数，如，N3接口上的通用无线分组业务信道协议(general packet radio service Tunnelling Protocol，GTP)数据包吞吐量，N6接口输出链路的利用率，AMF上平均/最大注册用户数等。
在一种可能的设计中，网管网元为该网络切片配置接入网资源具体是指网管网元向接入网设备发送对应于该网络切片的接入网的资源配置信息，则接入网设备按照该接入网的资源配置信息为该网络切片调度对应的接入网资源。其中，接入网资源配置信息中包括可保证的空口资源配置信息或最大的空口资源配置信息，而接入网设备可以为基站或者接入网域管理设备；另外，网管网元配置核心网资源具体是指网管网元向核心网设备发送核心网资源配置信息，则核心网设备按照该核心网资源配置信息调度对应的核心网资源。其中，核心网资源配置信息包括可保证的核心网资源配置信息或最大的核心网资源配置信息，而核心网设备具体可以分配用户面或控制面资源的核心网设备(如AMF,SMF,UPF等)或者为核心网域管理设备；
资源配置信息中下发的资源配置量的具体表现形式不限，可以是一个总资源的比例数据，如为某个切片配置总空口资源的30％,总核心网资源的40％，也可以是具体的资源数值如PRB的数量值，UPF存储空间的大小。
除上述所述的设计方式之外，网管网元还可以分区域信息为网络切片配置网络资源。例如，网管网元对该网络切片的不同区域，如不同的跟踪区(tracking area，TA)、TA list，不同的小区(cell)、cell list等，配置不同的接入网资源或核心网资源或传输网资源。本申请对区域信息的定义和形式不做限制。这里的区域信息与图3实施例中步骤202的第一区域信息等同。在一种可能的设计中，网管网元初始可能对于网络切片不同的区域平均地配置网络资源，这是因为在初始状态，网络管理不具备或具备很少的关于该网络切片的服务体验信息，其并不知道如何对不同的区域配置不同的网络资源。
除上述所述的设计方式之外，网管网元还可以分时间信息为网络切片配置网络资源。例如，不同的时间信息，如白天/夜晚、闲时/忙时、02:00-04:00、周一-周五等，网管网元对该网络切片配置不同的接入网资源或核心网资源。本申请对时间信息的定义和形式不做限制。这里的区域信息与图3实施例中步骤202的第一时间信息等同。在一种可能的设计中，网管网元初始可能对于网络切片不同的时间平均地配置网络资源，这是因为在初始状态，网络管理不具备或具备很少的关于该网络切片的服务体验信息，其并不知道如何对 不同的时间配置不同的网络资源。
当然，上述各种方式中一种或几种可以结合使用。
502、网管网元向切片管控网元发送该网络切片对应的初始的用户数信息和指示信息。
其中，网络切片的初始用户数信息与图5实施例步骤401中的用户数限制信息等同，其可以包括该网络切片初始的注册用户数信息或在线用户数信息。该用户数信息用于指导切片管控网元对该网络切片做用户数接入控制操作。例如，切片管控网元按照网管网元发送的注册用户数信息允许或拒绝用户的注册入该网络切片的请求，或者，将已经注册的用户从该网络切片中剔除，以达到控制该网络切片网络的注册用户数效果。又如，切片管控网元按照网管网元发送的在线用户数信息允许或拒绝用户的进入在线状态，或者，将已经在线的用户转变为离线或空闲状态，以达到控制该网络切片网络的在线用户数效果。说明一点，用户数信息一般指最大用户数信息，也即用户容量信息，例如，初始用户数信息可以包括该网络切片初始的最大注册用户数信息或最大在线用户数信息。
一种可能的实现方式中，网管网元还可以告知切片管控网元该网络切片对应的SLA要求信息。该处的SLA要求信息可以是试运行阶段，也就是测试状态的SLA要求信息，测试结束后，可以再确定一个稳定状态的SLA要求信息。SLA要求可以包括但不限于两个层面的要求：网络切片粒度的服务体验要求或业务粒度的服务体验要求。其中，网络切片粒度的服务体验要求是指对一个网络切片提出的整体服务体验要求，例如，网络切片中注册用户数要求(如<＝100万)、在线用户数要求(如<＝80万)、网络切片的端到端时延要求(如<＝2ms)、网络切片的负载要求等。而业务粒度的服务体验要求是指对于该网络切片中某种业务提出的服务体验要求，如网络中业务A的用户数要求(如<＝50万)、业务A的平均体验要求(如平均意见分MOS>＝3)、业务A的平均意见分大于3的用户数占业务A总用户数的比例要求(如>＝95％)等。说明一点，网管网元可以将用户数信息包含于该SLA要求信息的内部发送给切片管控网元，或者，也可以不将用户数信息作为该SLA要求信息部分，而是将两者分开发送给切片管控网元。
一种可能的实现方式中，网管网元还可以分区域发送用户数信息或SLA要求给切片管控网元。也就是说，网管网元告知切片管控网元不同区域对应的不同的用户数信息或SLA要求。例如，TA1对应最大注册用户数为100万，SLA要求1,TA2对应最大注册用户数为200万，SLA要求2。这里的区域与步骤402中的区域信息等同。
本申请实施例中所有的区域信息，可以是3GPP通信网络中定义的区域信息，可简称通信网络区域信息)，比如服务小区A或注册区域B，该区域信息也可以是非3GPP通信网络中定义的区域信息，比如该位置信息为某具体的地理位置范围(例如，经纬度或者全球定位系统(global positioning system，GPS)位置信息，可简称地理区域信息)。
一种可能的实现方式中，还可以分时间发送用户数信息或SLA要求。也就是说，网管网元告知切片管控网元不同时间对应的不同的用户数信息或SLA要求。例如，时间段1对应最大注册用户数为100万，SLA要求1,时间段2对应最大注册用户数为200万，SLA要求2。这里的时间域与步骤402中的时间信息等同。
实施例中所有的时间信息，可以是绝对时间，例如，从2017年1月1日00:00至2017 年1月30日24:00，或者，每周一至周五；也可以是相对时间信息，例如相对于发送该用户数信息或SLA要求信息之后的一个月内。该时间信息的粒度可以是以小时为粒度，也可以是以分钟或者天为粒度，本申请实施例对此并不限定。
一种可能的实现方式中，指示信息可以是第一指示信息，该第一指示信息用于指示网管网元发送的用户数信息或SLA要求信息的可信度信息，其中，该可信度信息是指网管网元对该用户数信息或SLA要求信息确信/自信程度，是一种衡量用户数信息或SLA要求信息可以信赖程度的信息。本申请并不限定可信度信息的具体表现形式，只要能反应出用户数信息或SLA要求信息的可以信赖程度即可。例如，可信度信息可以是一个[0,1]区间内的浮点数，浮点数值越大表明可以信赖的程度越高；又如，可信度信息可以是0-100％之间的百分制比例数值，比例越高表明可以信赖的程度越高；又如，可信度信息还可以是预先定义的集合(如{A,B,C,D})中的枚举值，其中，不同枚举值对应的可以信赖的程度不同(如，A>B>C>D)。
一般情况下，对比于稳定状态，对一个新建的网络切片或者处于测试状态的网络切片，网管网元设置的该状态对应的可信度值较低，例如可信度值为60％，这是因为此时网管网元不具备或具备很少的该网络切片的服务体验信息，也就是说此时网管网元生成用户数信息或SLA要求的依据信息很少，因此此时的可信度较低。
一种可能的实现方式中，该指示信息还可以是第二指示信息，该第二指示信息用于指示该网络切片是新建网络切片或该网络切片处于测试状态或者是处于稳定状态。其中，新建网络切片或测试状态相对于稳定状态，前者运营商和网络租户之间还未正式签署SLA，网络处于不断的调整状态中；后者，运营商和网络租户之间正式签署了SLA，网络处于相对稳定状态，不会频繁地执行资源调整。本申请并不限定指示测试状态或稳定状态的具体表现形式，例如，其可以是二进制枚举值，0表示测试状态，1表示稳定状态。或者，F表示测试状态，T表示稳定状态。当然，还可以通过其他形式来表示测试状态或者稳定状态。
503、切片管控网元根据网管网元发送的初始用户数信息和指示信息对该网络切片执行用户数控制。
其中，用户数接入控制具体是指控制该网络切片中的注册用户数或在线用户数，具体解释见步骤502。
当切片管控网元根据第一指示信息获知网管网元发送的用户数信息或SLA要求信息对应的可信度较低，如60％，则切片管控网元可以允许用户逐步或分阶段接入该网络切片。例如，网管网元指示切片管控网元该网络切片的最大注册用户数为1000万，则切片管控网元可以每次只允许100万用户接入该网络切片，其中逐步或分阶段允许用户接入该网络切片的目的，是为了避免一次性同时接入大量的用户而导致本网络切片的服务体验显著下降、甚至影响到其他已经处于稳定阶段的网络切片的服务体验。同理，当需要从网络中减少用户数时，若切片管控网元在判定用户数信息或SLA要求信息对应的可信度较低，则切片管控网元也可以逐步或分阶段地剔除用户或转移用户至其他网络切片，其中逐步或分阶段减少该网络切片用户数的目的，是为了避免同时影响网络切片中的大量用户的业务体验，从而避免影响该网络切片的服务体验。此处的逐步或分阶段增加或减少网络切片中的用户数 对应于图5实施例中的阶梯控制方式。
当切片管控网元根据第二指示信息获知该网络切片处于测试阶段或新建网络切片时，切片管控网元可以允许用户逐步或分阶段接入该网络切片。例如，网管网元初始指示切片管控网元该网络切片的最大注册用户数为1000万，则切片管控网元可以每次只允许100万用户接入该网络切片。此处的逐步或分阶段增加或减少网络切片中的用户数对应于图5实施例中的阶梯控制方式。
若切片管控网元还从网管网元接收区域信息，则切片管控网元还可以按区域信息对该网络切片执行用户数接入控制。例如，网管网元告知切片管控网元该网络切片的TA1对应最大注册用户数为100万,TA2对应最大注册用户数为200万，则切片管控网元最多只允许100万用户注册于网络切片的TA1，200万用户数注册于TA2。
若切片管控网元还从网管网元接收时间信息，则切片管控网元还可以按时间信息对该网络切片执行用户数接入控制。例如，网管网元告知切片管控网元时段1(如周末)对应最大注册用户数为100万,时段2(如工作日)对应最大注册用户数为200万，则切片管控网元在时段1最多只允许100万用户注册于该网络切片，时段2最多只允许200万用户数注册于该网络切片。
504、切片管控网元向数据分析网元发送第一请求，该第一请求用于请求网络切片对应的服务体验信息。
实际上，这里请求的可以是501中新建网络切片对应的服务体验信息，也可以是其他网络切片的服务体验信息，其他网络切片可以是已经处于稳定状态的网络切片。这里也可以一起请求多个网络切片的服务体验信息，但不管是请求几个网络切片的服务体验信息，针对存在问题的网络切片，后续的处理过程都是相同的。
每个网络切片对应的服务体验信息包括：网络切片粒度的体验信息、网络切片中业务粒度的体验信息。
其中，网络切片粒度体验信息是指能够反映一个网络切片的整体服务体验的信息，可以包括：该网络切片的用户数信息(如网络切片注册或在线用户数)、网络切片的端到端时延信息、网络切片的负载信息等。
业务粒度的体验信息是指能够反映网络切片中某种业务的服务体验的信息，包括该业务的业务粒度的质量信息(也即反映该业务整体服务体验的信息)、该业务的用户粒度的质量信息(也即反映执行该业务的每个用户个体的服务体验信息)。其中，业务粒度的质量信息包括：该业务的用户数信息(业务注册或在线用户数)、该业务的用户平均体验数值(如业务A的平均MOS＝3)、该业务的用户体验数值分布信息(如MOS分在[3,4]区间的用户数比例为60％，在[4,5]区间的用户数比例为30％)等。
第一请求中包含所请求的网络切片的网络切片标识信息，其中，网络切片标识信息用于唯一的标识一个网络切片，网络切片标识信息具体可以是网络切片选择支撑信息(network slice selection assistance information，NSSAI),S-NSSAI、NSI和NSSI中的一种或几种。
第一请求中还可以包含业务标识信息，也即第一请求具体是用于请求该业务标识信息 对应的某网络切片对应的服务体验信息，换句话说，请求的某网络切片对应的服务体验信息将包含该业务的质量信息。
以上，网络切片所对应的服务体验信息可以通过表格的形式进行展示，如表1所示，当然表1只是反映了一种数据结构表现形式，可以是其他数据结构。
另外，有些信元是可选的，并不是必须的，如区域信息，当没有区域信息时，说明切片体验信息是全网范围的体验信息，不限于某个区域。下面表1中的网络切片1可以是指501中的新建网络切片，也可以是指任意一个已经存在的网络切片。
表1：
Figure PCTCN2019124618-appb-000001
Figure PCTCN2019124618-appb-000002
一种可能的实现方式中，第一请求中包含区域信息，也即第一请求具体是用于请求该区域信息对应的某网络切片的服务体验信息。
一种可能的实现方式中，第一请求中包含时间信息，也即第一请求具体是用于请求该时间信息对应的某网络切片的服务体验信息。
本步骤中的请求的网络切片的服务体验信息等同于图2实施例步骤105中所述的第三服务体验信息。
505、网管网元向数据分析网元发送第二请求。
该第二请求用于请求网络切片对应的服务体验信息。
该步骤505可以根据步骤504进行理解，只是将执行主体从切片管控网元换成网管网元。
506、数据分析网元获取网络切片的服务体验信息。
这里数据分析网元可以根据切片管控网元或网管网元的请求而获取网络切片的服务体验信息，也可以自行获取网络切片的服务体验信息。该处的网络切片可以是第一网络切片，也可以是第二网络切片，也可以是第三网络切片，或者其他网络切片，也可以是多个网络切片。也可以将步骤506描述为数据分析网元获取第N网络切片的服务体验信息，N个是一个具体的数值，也可以是多个数值的集合。
数据分析网元获取网络切片的服务体验信息的方式包括以下几种：
数据分析网元从网络切片对应的AF直接获取网络切片的相关的服务体验信息。
这种方式可能基于AF提供的信息是可信的前提，则AF已经能提供一些网络切片的服务体验信息，如网络切片中的用户数，端到端时延，业务平均MOS，MOS分布，单用户的 MOS等等。数据分析网元收集这些体验数据，进行简单的统计计算即可获得切片管控网元或网管网元请求的网络切片的体验信息。例如，AF能够向数据分析网元提供单个用户执行业务A的用户体验数据，如单个用户执行业务A的MOS分，单个用户的业务A的时延，则数据分析网元根据所有的单用户的用户体验能够获取业务A的平均MOS值、业务A的平均端到端时延，并且能够获知业务的用户体验分布情况等，这些数据将被作为服务体验信息发送给切片管控网元或网管网元。
数据分析网元通过对网络切片中的业务进行模型训练，而获取网络切片的相关体验信息。
示例性地，本方式可以包括如下几个步骤：
步骤A、数据分析网元可以分别从AF网元收集一个业务的历史业务数据、以及从网络网元(例如，RAN、AMF网元、SMF网元、UPF网元)获取服务体验流(Quality of Service flow，QoS flow)级别的历史网络数据。
示例性的，本申请所涉及到的业务数据可以为：带宽、时延、丢包率、抖动缓存、传输控制协议(Transmission Control Protocol，TCP)拥塞窗口、TCP接收窗口、媒体编码类型、媒体编码速率等参数的数据。
本申请所涉及到的QoS流级别的网络数据可以为以下任一个参数：带宽、时延、丢包率、根据信号接收功率(reference signal receiving power，RSRP)、根据信号接收质量(reference signal receiving quality，RSRQ)、误块率(block error rate，BLER)和信道质量指示(channel quality indication，CQI)、网络切片标识信息、数据网络名称(data network name，DNN)等参数数据。
具体的，如表2所示，数据分析网元通过AF网元获取视频业务、支付业务、自动驾驶业务、Vertical(垂直)业务等一个或多个业务对应的历史的业务数据。如表3所示，数据分析网元可以从5G NF获取历史的网络数据。
示例性的，表2示例出了来自租户业务体验数据的数据内容，表3示例出了5G NF的网络数据的内容，详见下述表2和表3：
表2
Figure PCTCN2019124618-appb-000003
表3
Figure PCTCN2019124618-appb-000004
步骤B、数据分析网元对历史的网络数据和历史的业务数据分析得到该网络切片中每个业务的业务体验模型。
其中业务体验模型是指该业务数据随网络数据的变化关系，示例性的，一个业务体验模型如下公式所示：
H(x)＝W0X0+W1X1+W2X2+W3X3+W4X4+W5X5+......+WnXn。(1)
其中，X变量代表各网络数据，例如X1可以为GFBR、X2可以为PDB、X3为PER、X4为网络数据X4、X5为网络数据X5。其中，Wn表示第n变量的权值，n表示变量的数量，Xn表示第n个变量。n为大于或等于1的整数。H(x)的取值代表业务数据的取值。
步骤C、根据该模型关系，以及当前或预测的网络数据X，数据分析网元能够推算出当前或预测的H(X)的取值，也即当前或预测业务数据的取值。该推算出的业务数据的取值将被不断的统计存储，并发送切片管控网元或网管网元作为服务体验信息。
507、数据分析网元向切片管控网元发送网络切片的服务体验信息。
该步骤507可以是基于步骤504发起的，也可以是数据分析网元主动触发的，也即数据分析网元可以根据切片管控网元的请求而向切片管控网元发送服务体验信息，也可以是主动发送的。本步骤中的网络切片的服务体验信息可以步骤501中新建网络切片的服务体验信息，也可以包括其他已经存在的网络切片的服务体验信息。
一种可能的实现方式中，发送网络切片的某时间信息对应的服务体验信息，如第一时间信息对应的服务体验信息。
一种可能的实现方式中，发送网络切片的某区域信息对应的服务体验信息，如第一区域信息对应的服务体验信息。
服务体验信息见步骤504所述的服务体验信息的解释。
一种可能的实现方式中，数据分析网元还可向切片管控网元发送第三指示信息，第三指示信息用于指示数据分析网元发送的网络切片的服务体验信息的对应的可信度信息，或者第三指示信息用于指示针对该新建的网络切片的体验信息已经收集完成。
508、数据分析网元向网管网元发送网络切片的服务体验信息。
该步骤508可以参阅步骤507进行，只是将发送的对象从切片管控网元换成网管网元。
509、切片管控网元根据数据分析网元发送的网络切片的服务体验信息确定该网络切片的服务体验是否满足SLA要求。
该步骤中网络切片可以包括步骤501中所述的新建网络切片，也可以包括其他已经存在的网络切片，但不论对于哪个网络切片，切片管控网元确定网络切片的服务体验是否满足对应的SLA要求以及后续的处理操作是相同的。
该步骤也就是说切片管控网元根据数据分析网元发送的服务体验信息直接或间接地与租户要求的SLA要求进行比较，判断是否能满足SLA要求。当两者是同一类信息时，则两者可以直接进行比较；当两个信息无法直接类比时，切片管控网元需要先对从NWDAF接收到的服务体验信息进行处理，转化成能够与SLA要求信息相同的类型，再进行比较。
具体地，可以分时间、分区域地确定该网络切片的服务体验是否满足该网络切片的对应时间、区域的SLA要求。
510、若确定第一网络切片的服务体验无法满足对应的SLA要求，则切片管控网元向数据分析网元发送查询请求，该查询请求用于向数据分析网元查询第一网络切片中无法满足指定要求的区域信息/时间信息。
该第一网络切片可能是步骤501中所述的新建的网络切片，也可能是其他任意一个已经存在的网络切片，只要被确定其服务体验无法满足对应的SLA要求即可被作为第一网络切片，因此该第一网络切片可能指代多个无法满足对应的SLA要求网络切片，也即查询请求中可能用于多个网络切片中无法满足对应的指定要求的区域信息/时间信息。
其中，指定要求包括指定的网络切片粒度的服务体验要求或业务粒度的服务体验要求。该处的指定要求与前面实施例中服务体验信息是相同的，例如，指定要求为网络切片用户数<＝100万，端到端时延<＝2ms，平均MOS>＝3,用户满意度比例(MOS>3的用户比例)>＝90％。其中，指定要求是根据第一网络切片的SLA要求得来的，一般而言，指定要求具体取值与SLA要求取值相同。
可能存在一个或多个网络切片的服务体验无法满足对应的SLA要求的情况，则请求的是其中每个网络切片中无法满足相应指定要求的区域信息/时间信息。例如，网络切片1无法满足SLA要求1和网络切片2无法满足SLA要求2，则查询请求实际上请求的是网络切片1中无法满足指定要求1的区域/时间和网络切片2中无法满足指定要求2的区域/时间，其中，指定要求1可以等于SLA要求1，指定要求2可以等于SLA要求2。
具体地，查询请求中可以包含至少一个过滤条件，每个过滤条件对应于一个网络切片，该网络切片是无法满足对应SLA要求的网络切片。每个过滤条件用于向数据分析网元指明查询内容的过滤器，其是根据上述指定要求生成的。例如，网络切片1对应的过滤条件是网络切片用户数<100万，端到端时延>2ms,平均MOS<3，用户满意度<80％。说明一点，若步骤509中，切片管控网元是按区域确定的某网络切片的服务体验无法满足对应SLA要求的，也就是说，对于某个网络切片，若切片管控网元已经确定某一区域内的对应的网络切片服务体验无法满足SLA要求，则在本步骤510中的查询请求查询的是无法满足指定要求的子区域信息/时间信息，此时查询请求对应该网络切片的过滤条件应该包含该区域信息，该过 滤条件中的区域信息对应于图2实施例中的第三区域信息。
另外，若步骤509中，切片管控网元是按时间确定的网络切片的服务体验无法满足对应SLA要求的，也就是说，对于某个网络切片，若切片管控网元已经确定某一时间内的对应的网络切片服务体验无法满足SLA要求，则在本步骤510中的查询请求查询的是该时间内无法满足指定要求的子时间信息/区域信息，此时查询请求对应该网络切片的过滤条件应该包含该时间信息，该过滤条件中的时间信息对应于图2实施例中的第三时间信息。
上述方式也可以结合使用，也即查询请求对应该网络切片的过滤条件可能同时包含该时间信息和区域信息，换句话说，本步骤510中的查询请求查询的是该时间和该区域内无法满足指定要求的子时间信息/子区域信息。
对于一个网络切片，如第一网络切片，可能存在多个过滤条件，此处的过滤条件与图2实施例中的服务体验要求信息具备相同的含义，此处不再详细赘述。
本步骤中的指定要求和至少一个过滤条件与图2实施例中的服务体验要求信息具备相同的功能含义，此处不再详细赘述。
说明一点，本步骤中仅以查询请求用于向数据分析网元查询第一网络切片中无法满足指定要求的区域信息/时间信息为例加以举例说明，在另一种可能的设计中，还存在查询请求是用于向数据分析网元查询第一网络切片中超额满足某指定要求的区域信息/时间信息的场景。例如，当切片管控网元确定第一网络切片超额满足对应的SLA要求，则此时查询请求用于向数据分析网元查询第一网络切片中超额满足某指定要求的区域信息/时间信息。此处方法类似于上述查询无法满足指定要求的区域信息/时间信息的方法，仅查询请求中的指定要求可能不同，此处不再赘述。
在另一种可能的设计中，查询请求可能用于向数据分析网元查询第一网络切片中无法满足第一指定要求的区域信息/时间信息并且查询第一网络切片中超额满足第二指定要求的区域信息/时间信息，第一指定要求和第二指定要求可以相同或不同。
511、数据分析网元根据查询请求，向切片管控网元发送响应消息。
响应消息中包含第一网络切片对应的无法满足对应指定要求的区域信息/时间信息。其中，当步骤510中的第一网络切片是多个网络切片时，则此处的响应消息中可以包含多个网络切片对应的无法满足指定要求的区域信息/时间信息。
本步骤中响应消息中包含的无法满足对应指定要求的区域信息/时间信息与图2实施例中的第一区域信息/第一时间信息等同。
一种可能的实现方式中，响应消息中还包含该区域信息/时间信息所对应的第一网络切片的第一服务体验信息，此处的第一服务体验信息与图2实施例中的第一服务体验信息具备相同的含义。
经过上述509和510两个步骤，当确定某网络切片的服务体验无法满足对应SLA要求的时候，切片管控网元可以从数据分析网元查询该网络切片中具体哪些区域/时间无法满足该SLA要求，进一步地，还可以从数据分析网获取这些问题区域/时间所对应的具体的服务体验信息，以便于后续网络仅针对这些区域精确地网络资源调整，避免盲目的对全网做网络资源调整，从而避免繁重的工作量以及网络资源的浪费。
说明一点，在另一种可能的设计中，若查询请求是用于向数据分析网元查询第一网络切片中超额满足某指定要求的区域信息/时间信息，则响应消息中包含第一网络切片中超额满足对应指定要求的区域信息/时间信息。此处方法类似于上述响应消息中包含第一网络切片对应的无法满足对应指定要求的区域信息/时间信息的方法，此处不再赘述。
在另一种可能的设计中，若查询请求用于向数据分析网元查询第一网络切片中无法满足第一指定要求的区域信息/时间信息并且查询第一网络切片中超额满足第二指定要求的区域信息/时间信息，则响应消息中包含第一网络切片中无法满足第一指定要求的区域信息/时间信息和第一网络切片中超额满足第二指定要求的区域信息/时间信息。
512b，切片管控网元向网设备发送第一通知消息，该第一通知消息中用于向网络设备通知第一网络切片的切片质量信息。
第一通知消息中包含第一网络切片对应的网络切片标识信息。
第一网络切片的切片质量信息包括第一网络切片的服务体验信息，或者第一网络切片的服务体验信息对于第一网络切片SLA要求的满足程度信息。其中，切片质量信息的含义具体可以参考图2实施例中的切片质量信息的含义。
一种可能的实现方式中，第一通知消息中还包含区域信息，该区域信息是切片管控网元经查询请求/响应消息从数据分析网元获取的第一网络切片中无法满足或超额满足指定要求的区域信息。此处的区域信息对应于图2实施例中的第二区域信息，并且认为第二区域信息等同于第一区域信息。第一通知消息中包含该区域信息是用于告知一个网络切片网络具体哪些区域无法满足或超额满足SLA要求，以便于接入网设备仅对这些具体区域执行资源调整，精细化地网络资源调整的流程，避免了盲目尝试工作，从而优化网络资源的分配。
一种可能的实现方式中，第一通知消息中还包含时间信息，该第一通知消息中的时间信息是切片管控网元经第一请求/响应消息从数据分析网元获取的每个网络切片中无法满足或超额满足指定要求的时间信息。此处的时间信息对应于图2实施例中的第二时间信息，并且认为第二时间信息等同于第一时间信息。
一种可能的实现方式中，步骤512b之前，还可以存在如下步骤512a。
512a、接入网设备向切片管控网元发送第三请求。
该第三请求用于请求第一网络切片的切片质量信息。
513b、切片管控网元还可以向网管网元发送第二通知消息，该第二通知消息中用于向网管网元通知第一网络切片的切片质量信息。
本步骤操作方式类似于步骤512b，仅需将发送对象从接入网设备变为切片管控网元即可。
一种可能的实现方式中，类似于512a，在513b之前还可能存在步骤513a：
513a、网管网元向切片管控网元发送第四请求。
该第四请求用于请求第一网络切片的切片质量信息。
本步骤具体参见512a。
514、网络设备根据步骤512b从切片管控网元获取的第一网络切片的切片质量信息， 为第一网络切片调度资源。
例如，切片质量信息显示网络切片1对于其SLA要求1的满足程度仅为60％，则接入网设备为网络切片1调度更多的空口资源或优先调度空口资源，以保证网络切片1对于其SLA要求1的满足程度得以提高(例如提高到100％)，最终网络切片1的质量能够符合其SLA要求1。说明一点，接入网设备在网管网元发送的最大空口资源范围(如30％)内调度更多空口资源，也即增加调度的空口资源不能超过网管网元下发的最大空口资源范围。同时，接入网设备还需参考网管网元发送的保证空口资源范围(如20％)而调度更多的空口资源，例如，在保证空口资源范围附近(20％)附近调度更多的空口资源。
又如，切片质量信息中显示网络切片1对于其SLA要求1的满足程度为120％，则接入网设备为网络切片1调度更少的空口资源或空口资源调度优先级降低，以保证网络切片1对于其SLA要求1的满足程度得以降低(例如降低到100％)，最终网络切片1的质量能够符合其SLA要求1。说明一点，接入网设备在网管网元发送的最大空口资源范围(如30％)内调度更少空口资源，也即调度的空口资源不能超过网管网元下发的最大空口资源范围。同时，接入网设备还需参考网管网元发送的保证空口资源范围(如20％)而调度更少的空口资源，例如，在保证空口资源范围附近(20％)附近调度更少的空口资源。
其中上述SLA要求1可以是网络切片1的其中一档目标SLA要求，该档目标SLA要求的获取方法具体见图2实例。
一种可能的实现方式中，若步骤512b中网络设备获取的切片质量信息是第一网络切片的某时间信息对应的切片质量信息，则网络设备还可以按该时间信息为第一网络切片调度资源，也即网络设备只针对该时间信息调整第一网络切片资源调度。
一种可能的实现方式中，若步骤512b中网络设备获取的切片质量信息是第一网络切片的某区域信息对应的切片质量信息，则网络设备还可以按该区域信息为第一网络切片调度资源，也即网络设备只针对该区域信息调整第一网络切片资源调度。
经过本步骤514，网络设备可以是接入网设备，核心网设备或传输网设备，一接入网设备为例，接入网设备不断产生空口资源调度数据，例如基站为每个网络切片在某时间(如时段或时间点)、某区域(如小区或小区列表)调度了空口资源量(如空口物理资源块的类型和数量)、调度优先级等数据，将作为空口资源调度数据不断地被测量，收集，并上报给网管网元。这些数据后续会被网管网元用于空口资源的检测和调整。
空口资源量的表现形式并不限定于该接入网设备具体为每个网络切片调用的空口物理资源块的类型和数量，如CPU数量、内存数量、信道数量等，还可以是接入网设备为每个网络切片调用空口资源占该接入网设备总空口资源总量的比重，如网络切片1占20％，网络切片2占30％等。
515、网管网元根据获取的第一网络切片的服务体验信息，调整第一网络切片的网络资源配置信息，以使得第一网络切片能够满足对应的SLA要求。
网管网元获取的第一网络切片的服务体验信息可以包括：根据步骤508从数据分析网元获取的第一网络切片的服务体验信息，或者，根据步骤513b从切片管控网元获取的第一网络切片的切片质量信息。具体地，当网管网元判断一个网络切片无法满足对应的SLA要 求时，则网管网元增加接入网资源或核心网资源或传输网资源的配置，具体见步骤501描述；相反地，网管网元判断一个网络切片超过对应的SLA要求时，则网管网元降低接入网资源或核心网资源或传输网资源的配置，具体见步骤501描述。若网管网元判断一个网络切片的服务体验刚好满足对应的SLA要求，则无需调整接入网资源或核心网资源或传输网资源的配置。一种可能的实现方式中，若网管网元获取的第一网络切片的服务体验信息是某时间或某区域对应的第一网络切片的服务体验信息，则网管网元可以针对该时间或该区域调整第一网络切片的网络资源配置。
一种可能的实现方式中，网管网元调整第一网络切片的网络资源时还需考虑从接入网设备获取的空口资源调度数据，这些空口资源调度数据是接入网为第一网络切片执行空口资源调度处理过程中产生的。
例如，网管网元对网络切片1设置的初始空口资源配置信息为：最大空口资源配置为30％，保证空口资源配置为20％。若网管网元获取到某接入网设备为网络切片1调度的空口资源量为20％，并且网管网元根据步骤508或步骤513b获知对应于空口资源量为20％时，该网络切片1对于其SLA要求1的满足程度仅为80％，则网管网元可调整空口资源的配置变为：最大空口资源配置为30％，保证空口资源配置为23％，使得该接入网设备增加对该网络切片的空口资源量(如提升至23％)，最终是为了达到网络切片1对于其SLA要求1的满足程度为100％的目的。
又如，网管网元对网络切片2设置的初始空口资源配置信息为：最大空口资源配置为30％，保证空口资源配置为25％。网管网元获取到某接入网设备为网络切片2调度的空口资源量为25％，并且网管网元根据步骤508或步骤513b获知对应于空口资源量为25％时，该网络切片2对于其SLA要求2的满足程度仅为120％，则网管网元可调整接入网资源的配置，使得该接入网设备降低对该网络切片的空口资源量(如降低至20％)，最终是为了达到网络切片2对于其slice1SLA要求的满足程度为100％的目的。
当然核心网资源配置信息的调整也可以参阅接入网资源配置信息的调整进行理解，只是调整的资源类型不同，核心网的资源配置信息可以参考步骤501进行理解。
对于一个新建或处于测试阶段的网络切片，经步骤502-515的循环操作，网管网元能够根据从数据分析网元、切片管控网元获取的网络切片的服务体验数据，不断地调整该网络切片以及其它相关网络切片的资源配置信息，目的是为了使得该网络切片尽量满足租户提出的该网络切片的SLA要求，若该SLA要求实在无法满足，则需要与租户重新商定新的能够实现SLA要求，并且不影响其他已经存在的并处于稳定阶段的网络切片的质量。
516、该新建网络切片进入稳定阶段后，网管网元确定该新建网络切片能满足的新的SLA要求，并根据该新的SLA要求向切片管控网元发送新的用户数信息。
其中，新的用户数信息的含义具体可以根据步骤502中的初始用户数信息的含义。
其中，新的SLA要求可以与步骤1中的SLA要求相同或不同。一种可能的实现方式中，网管网元还可以告知切片管控网元该新建网络切片网络对应的新SLA要求。
网管网元还可以告知切片管控网元第四指示信息，该第四指示信息用于向切片管控网元通知网管网元发送的新用户数信息或新SLA要求信息的可信度信息。一般情况下，对比 于测试阶段状态，当网络切片网络处于稳定状态时，网管网元设置的该状态对应的可信度值较高(例如可信度值为99％)。
一种可能的实现方式中，在另一种可能的设计中，网管网元还可以告知切片管控网元第五指示信息，该第五指示信息用于指示该网络切片处于稳定阶段状态。此状态下，网络处于相对稳定状态，不会频繁地执行资源调整。另外，网管网元需要与租户协商并将该新SLA要求作为最终签署的SLA要求。
517、切片管控网元根据网管网元发送的新的用户数信息对该网络切片执行用户数接入控制。
其中，用户数接入控制具体是指控制该网络切片中的注册用户数或在线用户数，具体解释见步骤502。
一种可能的实现方式中，若切片管控网元还从网管网元接收第四指示信息，则切片管控网元还可以基于第四指示信息对该网络切片执行用户数控制。具体地，当切片管控网元根据第四指示信息获知网管网元发送的新用户数信息或新SLA要求信息对应的可信度较高(如99％)，切片管控网元可以允许大量用户同时接入该网络切片。例如，网管网元新指示的切片管控网元该网络切片的注册用户数不超过1000万，则切片管控网元可以允许1000万用户接入该网络切片，无需再逐步或分阶段允许用户接入或剔除该网络切片。
一种可能的实现方式中，若切片管控网元还从网管网元接收第五指示信息，则切片管控网元还可以基于第五指示信息对该网络切片执行用户数控制。具体地，当切片管控网元根据第五指示信息获知该网络切片处于稳定阶段时，切片管控网元可以允许大量用户同时接入该网络切片。例如，网管网元初始指示切片管控网元该网络切片的注册用户数不超过1000万，则切片管控网元可以允许1000万用户接入该网络切片。
当然，切片管控网元也可能从网管网元接收到第四指示信息和第五指示信息，那么切片管控网元只需要按照上述方式控制用户数即可。
一种可能的实现方式中，还可以分区域发送新用户数信息或新SLA要求，同步骤501。
本申请实施例中，可以区分网络切片的不同状态，根据网管网元发送的不同网络切片状态信息或可信度，切片管控网元能够做到对网络切片的用户数接入做区别控制，提高了用户数控制的准确度和精细度。另外，确定某网络切片质量无法满足对应SLA要求的时候，切片管控网元可以从数据分析网元查询获知该网络切片中具体哪些区域和/或时间无法满足该SLA要求，以便于后续网络仅针对这些区域精确地网络资源调整，避免盲目的对全网做网络资源调整，从而避免繁重的工作量以及网络资源的浪费。
图7B为本申请实施例中网络切片的资源调度的方法的另一实施例示意图。
如图7B所示，结合图2所述实施例，本申请实施例提供的网络切片的资源调度的方法的另一实施例可以包括以下一个或多个步骤：
520、切片管控网元从数据分析网元或网管网元获取第一网络切片的切片质量信息。
其中，切片质量信息包括以下信息的至少一项：第一网络切片的服务体验信息、第一网络切片的服务体验信息相对于所述目标服务水平协议要求信息的满足程度信息。
此处的第一网络切片的服务体验信息具体可参考图2实施例中的所述的服务体验信息(例如，第三服务体验信息)的含义和内容进行理解。
在一种可能的实现方式中，此处的第一网络切片的服务体验信息可以为该第一网络切片的整个网络范围或全部时间范围对应的服务体验信息。
在另一种可能的实现方式中，此处的第一网络切片的服务体验信息还可以为第一网络切片中某区域信息或某时间信息对应的第一网络切片的服务体验信息。
其中，满足程度信息可以包括无法满足、满足或者超额满足。具体地，满足程度信息的含义和表现形式具体参考图2实施例中的所述的满足程度信息。
切片管控网元从数据分析网元或网管网元获取第一网络切片的切片质量信息具体可以参考图7A实施例步骤504和507所述的切片管控网元从数据分析网元获取网络切片对应的服务体验信息的描述进行理解，此处不再赘述。
在一种可能的实现方式中，若第一网络切片的切片质量信息仅包括第一网络切片的服务体验信息时，本实施例还可以包括：切片管控网元根据该第一网络切片的服务体验信息确定所述第一网络切片的服务体验信息相对于第一网络切片的目标服务水平协议要求信息的满足程度信息。其中，满足程度信息包括无法满足、满足或者超额满足。具体地，满足程度信息的含义和表现形式具体参考图2实施例中的所述的满足程度信息。第一网络切片的目标服务水平协议要求信息具体可以参考图2实施例中的所述的目标服务水平协议要求信息。
521、切片管控网元根据第一网络切片的质量信息确定第一网络切片的服务体验信息无法满足或超额满足所述第一网络切片的目标服务水平协议信息。
当第一网络切片的质量信息包括第一网络切片的服务体验信息相对于所述目标服务水平协议要求信息的满足程度信息时，切片管控网元可以直接根据该满足程度信息确定第一网络切片的服务体验信息无法满足或超额满足所述第一网络切片的目标服务水平协议信息。
当第一网络切片的质量信息仅包括第一网络切片的服务体验信息时，切片管控网元如何根据该服务体验信息确定第一网络切片的服务体验信息无法满足或超额满足所述第一网络切片的目标服务水平协议信息具体可以参考步骤509。
522、切片管控网元向网管网元发送请求。
该请求用于向网管网元请求导致所述第一网络切片的服务体验信息无法满足或超额满足所述第一网络切片的目标服务水平协议信息的网络域。
一般而言，网络域包括但不限于以下领域：接入网域(RAN domain)、核心网域(CN domain)、传输网域(TN domain)。
523、网管网元确定导致第一网络切片的服务体验信息无法满足或超额满足所述第一网络切片的目标服务水平协议信息的原因在于第一网络域。
在一种可能的实现方式中，在步骤523之前，还可以包括以下步骤中一个或多个：
步骤A、网管网元从数据分析网元获取第一网络切片的切片质量信息。
该步骤的方法可以参考步骤520中切片管控网元从数据分析网元获取第一网络切片的 切片质量信息的方法，或者参考图7A所对应实施例中的步骤505和508所述的网管网元从数据分析网元获取网络切片的服务体验信息的方法。
步骤B、网管网元根据第一网络切片的切片质量信息确定所述第一网络切片的服务体验信息无法满足或超额满足所述第一网络切片目标服务水平协议信息。
该步骤的方法可以参考步骤521或步骤图7A所对应实施例中的步骤509。
在该种实现方式中，所述第一网络切片的服务体验信息无法满足或超额满足所述第一网络切片目标服务水平协议信息这一判断结果是步骤523执行的前提条件。
换句话说，若网管网元根据第一网络切片的切片质量信息确定所述第一网络切片的服务体验信息满足所述第一网络切片目标服务水平协议信息，则步骤523以及后续步骤524可以不被执行。
因网管网元是负责部署、维护、管理网络切片的网元，其能够获知一个网络切片的全局数据，因此网管网元能够判断第一网络切片的服务体验信息对于所述第一网络切片目标服务水平协议信息的满足程度信息，并且还能够定位出导致第一网络切片的服务体验信息超额满足或者无法满足第一网络切片目标服务水平协议信息的问题网络区域，例如定于出问题网络域为RAN domain、CN domain、TN domain中的一种或多种。网管网元将问题网络域作为第一网络域。具体地，针对一个网络切片，网管网元可以预先设置每个网络域对应的一个或多个关键性能指标(key performance indicator，KPI)。网络切片实际运行过程中，网管网元通过比较每个网络域的关键性能指标的实际测量值与预设值，从而定位出问题区域。
524、网管网元向切片管控网元发送指示信息。
所述指示信息用于指示导致第一网络切片的服务体验信息无法满足或超额满足所述第一网络切片的目标服务水平协议信息的原因在于第一网络域。
在一种可能的实现方式中，网管网元可以应切片管控网元的要求而向切片管控网元发送该指示信息。
在另一种可能的实现方式中，网管网元也可以主动向切片管控网元发送该指示信息，也即步骤522可以不被执行。
一种可能的实现方式，网管网元还可以向切片管控网元发送可信度信息，所述可信度信息用于指示所述指示信息的可信程度。其中，可信度信息的表现形式具体可以参考图5实施例中的用户数量限制信息的可信度的表现形式，此处不再赘述。网管网元根据内部策略或算法生成所述可信度信息。
525、切片管控网元确定导致第一网络切片的服务体验信息无法满足或超额满足所述第一网络切片的目标服务水平协议信息的原因在于第一网络域。
在一种可能的实现方式中，切片管控网元可以根据网管网元发送的指示信息确定导致第一网络切片的服务体验信息无法满足或超额满足所述第一网络切片的目标服务水平协议信息的原因在于第一网络域。
说明一点，本实施例中522、523、524是可选步骤，在另一种可能的实现方式中，这三个步骤可以不被执行，而切片管控网元可以自行确定出导致第一网络切片的服务体验信 息无法满足或超额满足所述第一网络切片的目标服务水平协议信息的原因在于第一网络域。例如具体的确定方法可以参考步骤523中网管网元的确定方法。
526、切片管控网元向第一网络域的网络设备发送所述第一网络切片的切片质量信息。
无论通过步骤525中哪种实现方式确定导致第一网络切片的服务体验信息无法满足或超额满足所述第一网络切片的目标服务水平协议信息的原因在于第一网络域后，切片管控网元从所述第一网络域中确定出网络设备，并向该网络设备发送第一网络切片的切片质量信息。其中，所述网络设备可以是指第一网络域中的所有网络设备，也可以是第一网络域中的部分网络设备，例如仅是与某区域信息/某时间信息对应的第一网络域中的网络设备。
所述切片质量信息用于所述网络设备根据所述切片质量信息为所述第一网络切片调度资源。
例如，当第一网络域是接入网域时，切片管控网元向接入网域中的接入网设备发送所述第一网络切片的切片质量信息，以便于接入网设备根据第一网络切片的切片质量信息为所述第一网络切片调度空口资源。接入网设备如何根据第一网络切片的切片质量信息为所述第一网络切片调度更多或更少的空口资源具体可以参考图2步骤105或图7A实施例步骤514中相关的描述进行理解。
当第一网络域与核心网域或传输网域时，资源调度方法与第一网络域是接入网域基本是相同的，只是调度的是核心网的资源或传输网的资源。
当第一网络域是接入网域、核心网域、传输网域中两种或以上的结合时，资源调度的方法也基本相同，只要分别在相应的网域调度相应的资源即可。
在一种可能的实现方式中，若切片管控网元是根据网管网元在步骤524发送的指示信息确定导致第一网络切片的服务体验信息无法满足或超额满足所述第一网络切片的目标服务水平协议信息的原因在于第一网络域的，并且切片管控网元还接收网管网元发送可信度信息，所述可信度信息用于指示所述指示信息的可信程度，则该切片管控网元还可以根据所述可信度信息向第一网络域的网络设备发送所述第一网络切片的切片质量信息。
具体地，当所述可信度信息高于预设可信度值时(如可信度信息值大于90％)，则切片管控网元向第一网络域的网络设备发送所述第一网络切片的切片质量信息；反之，当所述可信度信息低于预设可信度值时(如可信度信息值小于60％)，则切片管控网元不向第一网络域的网络设备发送所述第一网络切片的切片质量信息。
该步骤中第一网络切片的质量信息可以是第一网络切片整网范围或全部时间范围对应的切片质量信息，也可以是第一网络切片中某区域信息或某时间信息对应的切片质量信息。例如，某区域信息或某时间信息可以是切片管控网元利用图2实施例所述的方法确定出所述第二区域信息和/或第二时间信息。换句话说，图7B实施例所述方法可以和图2实施例所述方法结合使用，在图2实施例方法所示的步骤104之前，切片管控网元可以利用图7B所述方法先定位出第一网络域，再向第一网络域的网络设备发送第二区域信息和/或第二时间信息，以便第一网络域的网络设备根据第二区域信息和/或第二时间信息为第一网络切片调度资源。
上述图7B对应的实施例中，切片管控网元可先精确定位出第一网络切片的服务体验信 息无法满足目标服务水平协议要求信息的原因是出自某网络域(如接入网域)，随后再向该网络域的网络设备提供该第一网络切片的切片质量信息，以便于该网络域的网络设备调整资源的调度情况。该方法可避免盲目地调整其他正常工作的网络域的资源调度情况，提升资源调度的准确性。
图7C为本申请实施例中网络切片的资源调度的方法的另一实施例示意图。
如图7C所示，结合图3或4所述实施例方法，在本申请提供的网络切片资源调度方法的另一实施例包括以下一个或多个步骤：
530、网管网元确定第一网络切片的状态信息。
第一网络切片的状态信息包括该第一网络切片未签署SLA状态或已经签署SLA状态。
所述未签署SLA状态是指还未与切片租户签订针对第一网络切片的服务水平协议，换句话说，此时第一网络切片属于一个新建网络切片或其还处于测试阶段的网络切片。
所述已经签署SLA状态是指已经与切片租户签订了针对第一网络切片的服务水平协议，换句话说，此时第一网络切片属于一个稳定状态的网络切片或其已经完成测试阶段。
在一种可能的实现方式中，网管网元可以根据内部配置信息确定是否已经与租户签订了第一网络切片对应的服务水平协议，从而确定第一网络切片的状态信息。
在另一种可能的实现方式中，网管网元还可以根据从数据分析网元获取的第一网络切片的切片质量信息确定第一网络切片的状态信息。其中，第一网络切片的切片质量信息包括第一网络切片的服务体验信息或第一网络切片的服务体验信息相对于第一网络切片的目标服务水平协议要求信息的满足程度信息。具体地，网管网元可以根据该服务体验信息是否满足目标服务水平协议要求信息确定第一网络切片的状态信息。例如，若该服务体验信息满足目标服务水平协议要求信息，则确定第一网络切片的状态信息为已经签署SLA状态或者等价的稳定状态，相反，则确定为未签署SLA状态或者等价的测试状态。
在一种可能的实现方式中，网管网元还可以确定第一网络切片的状态信息对应的可信度信息，所述可信度信息用于指示所述状态信息的可信程度。该可信度信息的具体表现形式可以参考图5实施例中的用户数量限制信息的可信度的表现形式。
531、网管网元向网络设备发送该第一网络切片的状态指示信息。
该状态指示信息中包含第一网络切片的状态信息。
在一种可能的实现方式中，在步骤531之前，网管网元接收待网络设备发送的状态请求消息，该状态请求消息用于请求第一网络切片的状态信息。
在另一种可能的实现方式中，网管网元可主动向网络设备发送该第一网络切片的状态指示信息，也即不必基于网络设备的状态请求消息。
值得注意的是，类似于步骤101中描述的方法，若所述目标服务水平协议要求信息是根据多档服务水平协议要求信息得来的，例如，目标服务水平协议要求信息是多档服务水平协议要求信息中的一档，则网管网元还可以向网络设备指明该状态信息对应的目标服务水平协议要求信息，换句话说，也即通知网络设备网络切片究竟未签署或已经签署的哪个SLA。
在一种可能的实现方式中，该状态指示信息可以包含在资源配置信息中一并被网管网 元发送给网络设备，资源配置信息的含义和内容具体参考图3或图4实施例中资源配置信息的含义。
在另一种可能的实现方式中，该状态指示信息可以独立于资源配置信息被网管网元发送给网络设备。
在一种可能的实现方式中，网管网元还可以向网络设备发送第一网络切片的状态信息对应的可信度信息。该可信度信息可以被包含在所述状态指示信息中发送给网络设备，也可以独立于所述状态指示信息而被发送给网络设备。
532、网络设备确定第一网络切片的状态信息。
在一种可能的实现方式中，网络设备根据网管网元发送的第一网络切片的状态指示信息确定第一网络切片的状态信息。
在另一种可能的实现方式中，网络设备自行确定第一网络切片的状态信息，具体可以参考步骤520中网管网元确定第一网络切片的状态信息的方法。若网络设备可以自行确定第一网络切片的状态信息，则步骤530和531可以省略。
值得注意的是，若所述目标服务水平协议要求信息是根据多档服务水平协议要求信息得来的，则网络设备还可以自行确定或根据网管网元的通知而确定状态信息对应的目标服务水平协议要求信息，换句话说，也即确定网络切片究竟未签署或已经签署的哪个SLA。
533、网络设备根据所述第一网络切片的状态信息为所述第一网络切片调度资源。
在一种可能的实现方式中，当所述第一网络切片的状态信息为所述第一网络切片未签署SLA状态，而第二网络切片的状态信息为该第二网络切片已经签署SLA状态，则该网络设备落后(deprioritized)于所述第二网络切片而为所述第一网络切片调度资源。换句话说，此时，网络设备优先为第二网络切片调度资源，在有资源剩余的情况下，才为第一网络切片调度资源。其中，第二网络切片为区别于第一网络切片的另一个网络切片。
在另一种可能的实现方式中，当所述第一网络切片的状态信息为所述第一网络切片已经签署SLA状态，而第二网络切片的状态信息为该第二网络切片未签署SLA状态，则该网络设备优先于第二网络切片而为第一网络切片调度资源。换句话说，此时，网络设备优先为第一网络切片调度资源，在有资源剩余的情况下，才为第二网络切片调度资源。
在另一种可能的实现方式中，当所述第一网络切片的状态信息为所述第一网络切片未签署SLA状态，而第二网络切片的状态信息为该第二网络切片未签署SLA状态，则该网络设备同等级别地为第一网络切片和第二网络切片调度资源。换句话说，此时，两个网络切片之间没有优先级区别，可同等机会地从网络设备获取资源调度。
在另一种可能的实现方式中，当所述第一网络切片的状态信息为所述第一网络切片已经签署SLA状态，而第二网络切片的状态信息为该第二网络切片已经签署SLA状态，则该网络设备同等级别地为第一网络切片和第二网络切片调度资源；或者，该网络设备根据其他信息为第一网络切片和第二网络切片调度资源，例如网络设备可以根据不同切片之间的抢占优先级信息的高低而为不同网络切片调度资源，又如，网络设备还可根据不同切片签订的具体的SLA而为不同的网络切片调度资源，例如第一网络切片签订的SLA要求高于第二网络切片的SLA要求，则优先为第一网络切片调度资源。
在一种可能的实现方式中，若网络设备还接收网管网元发送的所述第一网络切片的状态指示信息对应的可信度信息，所述可信度信息用于指示所述状态信息的可信程度，则网络设备还可以根据所述可信度信息为所述第一网络切片调度资源。例如，当所述可信度信息高于预设可信度值时(如可信度信息值大于90％)，则网络设备按照上述几种可能的方式为第一网络切片调度资源；反之，当所述可信度信息低于预设可信度值时(如可信度信息值小于60％)，则网络设备并不按照上述几种可能的方式为第一网络切片调度资源。网络设备根据所述可信度信息为所述第一网络切片调度资源还有其他可能的实现方式，并发明并不限制。
具体地，除第一网络切片的状态信息之外，网络设备如何为第一网络切片调度资源还可以结合图3或4所述实施例，也即网络设备还可根据网管网元发送的资源配置信息为第一网络切片调度资源，此处不再赘述。
本实施例中所述的网络设备包括以下设备类型中的一种或多种：接入网设备、核心网设备、传输网设备。此处网络设备具体的含义可以参考图3或4所述实施例中的网络设备。
当网络设备为接入网设备时，步骤533具体为接入网设备根据所述第一网络切片的状态信息为所述第一网络切片调度空口资源。
当网络设备为核心网设备时，步骤533具体为核心网设备根据所述第一网络切片的状态信息为所述第一网络切片调度核心网资源。
当网络设备为传输网设备时，步骤533具体为传输网设备根据所述第一网络切片的状态信息为所述第一网络切片调度传输网资源。
当网络设备为接入网设备、核心网设备、传输网设备中的两种或多种结合时，步骤533是相应网络设备各自调度相应网络的资源。
图7D为本申请实施例中用户数量控制的方法的另一实施例示意图。
如图7D所示，结合图5所述实施例方法，本申请实施例提供的用户数量控制的方法的另一实施例可以包括以下一个或多个步骤：
540、当需要新建一个目标网络切片时，网管网元确定目标网络切片的初始用户数限制信息。
其中，用户数限制信息的含义和内容具体可以参考图5实施例中的用户数限制信息，此处不再赘述。
当新建一个网络切片时，网管网元可以根据该网络切片的租户提供的初始的服务水平协议要求信息确定初始的用户数限制信息。说明一点，初始的服务水平协议要求信息一般是指未签署正式的服务水平协议之前租户提供的一个试运行的服务水平协议要求，其中可以包含初始用户数限制信息。
541、网管网元向切片管控网元发送该目标网络切片的初始用户数限制信息。
本步骤具体细节可以参考步骤402中网管网元向切片管控网元发送所述目标网络切片的用户数量限制信息的方法，不同点仅在于本步骤中没有发送步骤402中所述的指示信息，此处不再赘述。
542、切片管控网元根据初始用户数限制信息控制该目标网络切片的用户的数量。
本步骤具体细节可以参考步骤403中根据用户数量限制信息控制目标网络切片所服务的用户的数量的方法，此处不再赘述。
543、网管网元获取该目标网络切片的切片质量信息。
切片质量信息包括所述目标网络切片的服务体验信息和/或所述目标网络切片的服务体验信息相对于目标网络切片的目标服务水平协议要求的满足程度信息。切片质量信息的含义和内容具体可以参见图2至图7A实施例中所述的切片质量信息的含义和内容，此处不再赘述。
网管网元可以从切片管控网元或数据分析网元获取目标网络切片的切片质量信息，具体可以参见步骤图4或图7A实施例中网管网元获取第一网络切片的切片质量信息或者服务体验信息的方法，此处不再赘述。
544、网管网元根据目标网络切片的切片质量信息确定该目标网络切片的新用户数限制信息。
可选地，当切片的质量信息仅包含目标网络切片的服务体验信息时，网管网元还可以根据目标网络切片的服务体验信息确定该服务体验信息相对于目标服务水平协议要求信息的满足程度信息。其中，满足程度信息可以包括无法满足、满足、超额满足，或者满足程度信息可以是其他表现形式，此处不加以限制。
网管网元根据目标网络切片的服务体验信息相对于该目标网络切片的目标服务水平协议要求信息的满足程度信息确定该目标网络切片的新用户数限制信息。例如，当满足程度信息为无法满足时，则网管网元确定的新用户数限制信息中包含的用户数小于初始用户数限制信息，换句话说，网管网元决定减少目标网络切片中的用户数量；相反，当满足程度信息为超额满足时，则网管网元确定的新用户数限制信息中包含的用户数大于初始用户数限制信息，换句话说，网管网元决定增加目标网络切片中的用户数量。又如，当满足程度信息为满足时，则网管网元确定的新用户数限制信息中包含的用户数等于初始用户数限制信息，换句话说，网管网元决定不改变目标网络切片中的用户数量。
545、网管网元向切片管控网元发送该新用户数限制信息。
具体参考步骤541，不同点在于步骤541中的初始用户数限制信息被新用户数限制信息代替。
546、切片管控网元根据该新用户数限制信息，控制所述目标网络切片所服务的用户的数量。
在一种可能实现方式中，当新的用户数限制信息等于初始用户数限制信息时，切片管控网元无需做任何操作。
在一种可能实现方式中，当新的用户数限制信息小于初始用户数限制信息时，切片管控网元需要限制更多的用户接入该目标网络切片，甚至需要从目标网络切片中剔除多余的用户接入该目标网络切片。
在另一种可能的实现方式中，当新的用户数限制信息大于初始用户数限制信息时，切片管控网元允许更多的用户接入该目标网络切片。
循环执行步骤543至546中的一个或多个步骤，网管网元和切片管控网元可以不断地交 互更新目标网络切片中的用户数限制信息，可达到最佳用户数状态，也即目标网络切片的服务体验信息满足目标服务水平协议要求信息的状态。
值得注意的是，为了描述方便，在本申请的一些实施例中的某些步骤(如图7A实施例步骤511和512b)中可能说明了切片管控网元从数据分析网元获取到的网络切片的服务体验信息(如第一区域信息/第一时间信息对应的服务体验信息)与其向网络设备发送的该网络切片的服务体验信息(如第二区域信息/第二时间信息对应的服务体验信息)的类型是相同的，例如两个服务体验信息均包含了该网络切片的网络粒度的体验信息和业务粒度的体验信息，但实际上两者也可以包含不同类型的体验信息，如前者包含用户粒度的体验信息，后者包含网络粒度和业务粒度的体验信息。换句话说，切片管控网元可以根据接收到的服务体验信息生成即将发送的服务体验信息，两者可以相同，也可以不同。另外，对于网管网元也是如此。
另外，说明一点，本实施例中涉及到切片管控网元和网管网元两者从数据分析网元获取网络切片的服务体验信息，为了描述方便，本实施例是以两者与同一个数据分析网元交互为例加以说明的，实例上还存在两者与不同的数据分析网元交互以获取网络切片的服务体验信息的场景，本实施例并不排除。
另外，在此对本申请各实施例所涉及的网元进行说明：
切片管控网元是指具备以下至少一种功能的网元：管理和控制网络切片的用户接入功能、资源部署功能、网管命令执行功能，其可以位于运营商网络的控制面，例如切片管控网元为网络切片选择功能网元(NSSF)；也可以位于运营商网络的管理面，例如切片管控网元为OAM、NSMF或通信业务管理功能网元(communication service management function，CSMF)等。
数据分析网元是指具备分析以下至少一种数据功能的网元：运营商网络数据、业务数据、用户数据。其可以位于运营商控制，例如数据分析网元可以为网络数据分析网元NWDAF，其也可以位于运营商网络的管理面，例如数据分析网元可以为MDAS。
网管网元是指具备以下至少一种功能的网元：部署网络资源功能、管理网络的运行功能。例如网管网元可以为NSSF、OAM、NSMF或CSMF。
切片管控网元可是控制面的NSSF，那么对应的网管网元可以是OAM、NSMF或CSMF。
切片管控网元也可以是管理面的NSMF、CSMF，那么对应网管网元可以是MDAS。
上述主要从各个网元之间交互的角度对本申请实施例提供的方案进行了介绍。可以理解的是，上述切片管控网元、网络设备、数据分析网元、网管网元为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的功能，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
从实体设备角度来描述，上述切片管控网元、网络设备、数据分析网元或者网管网元可以由一个实体设备实现，也可以由多个实体设备共同实现，还可以是一个实体设备内的 一个逻辑功能单元，本申请实施例对此不作具体限定。
例如，上述切片管控网元、网络设备、数据分析网元或者网管网元可以由图8中的通信设备来实现。图8所示为本申请实施例提供的通信设备的硬件结构示意图。该通信设备包括至少一个处理器601、存储器602、通信线路603。该通信设备还可以包括收发器604以及通信接口606中的至少一个。
处理器601可以是一个通用中央处理器(central processing unit，CPU)，微处理器，特定应用集成电路(application-specific integrated circuit，服务器IC)，或一个或多个用于控制本申请方案程序执行的集成电路。
通信线路603可包括一通路，在上述组件之间传送信息。
收发器604，使用任何收发器一类的装置，用于与其他设备或通信网络通信，如以太网，无线接入网(radio access network，RAN)，无线局域网(wireless local area networks，WLAN)等。该收发器604也可以是收发电路或者收发信机。当该通信设备为切片管控网元、网络设备、数据分析网元或者网管网元时，可以包括该收发器。
该通信设备也可以包括通信接口606。
存储器602可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically erable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过通信线路603与处理器601相连接。存储器602也可以和处理器601集成在一起。
其中，存储器602用于存储执行本申请方案的计算机执行指令，并由处理器601来控制执行。处理器601用于执行存储器602中存储的计算机执行指令，从而实现本申请上述方法实施例提供的无人机监管的方法。
一种可能的实现方式，本申请实施例中的计算机执行指令也可以称之为应用程序代码，本申请实施例对此不作具体限定。
在具体实现中，作为一种实施例，处理器601可以包括一个或多个CPU，例如图8中的CPU0和CPU1。
在具体实现中，作为一种实施例，通信设备可以包括多个处理器，例如图8中的处理器601和处理器605。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机执行指令)的处理核。
从功能单元的角度，本申请可以根据上述方法实施例对切片管控网元、网络设备、数据分析网元或者网管网元进行功能单元的划分，例如，可以对应各个功能划分各个功能单元，也可以将两个或两个以上的功能集成在一个功能单元中。上述集成的功能单元既可以 采用硬件的形式实现，也可以采用软件功能单元的形式实现。
比如，以采用集成的方式划分各个功能单元的情况下，图9示出了一种切片管控网元的结构示意图。如图9所示，本申请切片管控网元70的一个实施例可以包括接收单元701、处理单元702以及发送单元703；
发送单元703，用于向数据分析网元发送请求，所述请求包括对第一网络切片的服务体验要求信息；
接收单元701，用于接收所述数据分析网元发送的响应，所述响应中包括与所述服务体验要求信息对应的所述第一网络切片的第一区域信息和/或第一时间信息；
发送单元703，用于根据所述第一区域信息和/或第一时间信息向网络设备发送第二区域信息和/或第二时间信息，所述第二区域信息和/或第二时间信息用于所述网络设备根据所述第二区域信息和/或第二时间信息为所述第一网络切片调度资源。
以上所描述的方案，使网络设备可以根据第二区域信息和/或第二时间信息做资源调度，提高了资源调度的准确度和网络资源的利用率，也提高了网络切片的性能。
在本申请的一些实施例中，处理单元702，用于根据第一服务体验信息确定所述第二区域信息和/或所述第二时间信息。
在本申请的一些实施例中，发送单元703，用于向所述网络设备发送所述第二区域信息和/或所述第二时间信息对应的切片质量信息，其中，所述切片质量信息包括以下信息的至少一项：所述第二区域信息和/或所述第二时间信息的对应所述第一网络切片的第二服务体验信息、所述第二服务体验信息相对于所述第一网络切片的目标服务水平协议要求信息的满足程度信息。
在本申请的一些实施例中，当所述网络设备为接入网设备时，所述第二区域信息用于所述接入网设备根据所述第二区域信息为所述第一网络切片调度接入网资源，所述第二时间信息用于所述接入网设备根据所述第二时间信息为所述第一网络切片调度接入网资源。
在本申请的一些实施例中，所述满足程度信息包括无法满足、满足或者超额满足。
在本申请的一些实施例中，所述请求中还包括第三区域信息时，所述第三区域信息所指示的第三区域包括所述第一区域信息所指示的第一区域，所述第三区域信息用于向所述数据分析网元请求所述第三区域中与所述服务体验要求信息对应的所述第一区域信息。
在本申请的一些实施例中，所述请求中还包括第三时间信息时，所述第三时间信息所指示的第三时间包括所述第一时间信息所述指示的第一时间，所述第三时间信息用于向所述数据分析网元请求所述第三时间中与所述服务体验要求信息对应的所述第一时间信息。
在本申请的一些实施例中，处理单元702，用于获取所述第一网络切片的第三服务体验信息；若所述第三服务体验信息与所述目标服务水平协议要求信息不对应，则确定所述第一网络切片的服务体验要求信息，所述第一网络切片的服务体验要求信息对应于所述目标服务水平协议要求。
在本申请的一些实施例中，处理单元702，用于将所述第三服务体验信息与所述目标服务水平协议要求信息进行比较；若所述第三服务体验信息不满足或者超额满足所述目标服务水平协议要求信息，则确定所述第三服务体验信息与所述目标服务水平协议要求信息 不对应。
在本申请的一些实施例中，处理单元702，用于若所述第三服务体验信息不满足所述目标服务水平协议要求信息，则确定与不满足情况下对应的所述第一网络切片的服务体验要求信息；若所述第三服务体验信息超额满足所述目标服务水平协议要求信息，则确定与超额满足情况下对应的所述第一网络切片的服务体验要求信息。
在本申请的一些实施例中，处理单元702，用于若所述第三服务体验信息不满足所述目标服务水平协议要求信息，则减少所述第一网络切片的服务用户数量；若所述第三服务体验信息超额满足所述目标服务水平协议要求信息，则增加所述第一网络切片的服务用户数量。
在本申请的一些实施例中，处理单元702，还用于取所述第一网络切片的初始服务水平协议要求信息；根据所述第一网络切片的初始服务水平协议要求信息确定至少一个服务水平协议要求信息；将所述至少一个服务水平协议要求信息中的一个确定为所述目标服务水平协议要求信息。
在本申请的一些实施例中，所述第一网络切片的服务体验要求信息包括以下信息中的至少一项：所述第一网络切片的用户数要求、业务的平均用户体验的要求、业务的用户满意比例的过滤要求，其中，所述业务的用户满意比例为所述业务对应的用户体验不差于预设值的用户数占该业务总用户数的比例。
在本申请的一些实施例中，发送单元703，还用于向所述数据分析网元发送订阅请求，所述订阅请求用于请求第二网络切片的服务体验信息。
在本申请的一些实施例中，接收单元701，还用于从网管网元获知需要新建网络切片或者删除网络切片。
在本申请的一些实施例中，处理单元702，还用于确定导致问题区域和/或问题时间的原因在于第一网络域(network domain)，所述问题区域包括第一区域或第二区域，所述问题时间包括第一时间或第二时间；所述切片管控网元根据所述第一网络域确定所述网络设备。
在本申请的一些实施例中，处理单元702，用于从网管网元获知导致问题区域和/或问题时间的原因在于第一网络域。
在本申请的一些实施例中，处理单元702，用于从所述网管网元获取第一可信度信息，所述第一可信度信息用于指示导致问题区域和/或问题时间的原因在于第一网络域的可信程度；根据所述第一可信度信息以及所述第一网络域确定所述网络设备。
在本申请的一些实施例中，处理单元702，用于从网管网元获知导致所述第三服务体验信息与所述目标服务水平协议要求信息不对应的原因在于所述第二网络域。
在本申请的一些实施例中，处理单元702，用于从所述网管网元获取第二可信度信息，所述第二可信度信息用于指示导致所述第三服务体验信息与所述目标服务水平协议要求信息不对应的原因在于第二网络域的可信程度；根据所述第二可信度信息以及所述第二网络域确定出所述网络设备。
在本申请的一些实施例中，所述第一网络域或第二网络域包括以下至少一种：接入网 域、核心网域、传输网域。
本申请实施例提供的切片管控网元70用于执行图2或图7A对应的方法实施例中切片管控网元所执行的方法，故本申请实施例可以参考图2或图7A对应的方法实施例中的相关部分进行理解。
本申请实施例中，切片管控网元70以采用集成的方式划分各个功能单元的形式来呈现。这里的“功能单元”可以指特定应用集成电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到切片管控网元70可以采用图8所示的形式。
比如，图8的处理器601可以通过调用存储器602中存储的计算机执行指令，使得切片管控网元70执行图2或图7A对应的方法实施例中切片管控网元所执行的方法。
具体的，图9中的接收单元701、处理单元702以及发送单元703的功能/实现过程可以通过图8中的处理器601调动存储器602中存储的计算机执行指令来实现。或者，图9中的处理单元702的功能/实现过程可以通过图8中的处理器601调用存储器602中存储的计算机执行指令来实现，图9中的接收单元701和发送单元703的功能/实现过程可以通过图8中的收发器604来实现。
由于本申请实施例提供的切片管控网元可用于执行图2或图7A对应的实施例方法，因此本申请实施例所能获得到的技术效果可参考图2或图7A对应的方法实施例，此处不再赘述。
比如，以采用集成的方式划分各个功能单元的情况下，图10示出了一种网络设备的结构示意图。如图10所示，本申请提供的网络设备80的一个实施例可以包括：接收单元801、处理单元802以及发送单元803；
接收单元801，用于接收切片管控网元发送的第一网络切片的第二区域信息，和/或第二时间信息；
处理单元802，用于根据所述第二区域信息和/或第二时间信息为所述第一网络切片调度资源。
本申请网络设备可以根据第二区域信息和/或第二时间信息做资源调度，提高了资源调度的准确度和网络资源的利用率，也提高了网络切片的性能。
在本申请的一些实施例中，接收单元801，还用于接收所述切片管控网元发送的所述第一网络切片对应的切片质量信息，所述切片质量信息包括所述第一网络切片的服务体验信息和/或所述第一网络切片的服务体验信息相对于目标服务水平协议要求的满足程度信息；
处理单元802，用于根据所述切片质量信息调整为所述第一网络切片调度的资源。
在本申请的一些实施例中，所述第一网络切片对应的切片质量信息包括所述第一网络切片的第二区域对应的服务体验信息和/或所述第二区域对应的服务体验信息相对于所述目标服务水平协议要求的满足程度信息，所述第二区域为所述第二区域信息所指示的区域。
在本申请的一些实施例中，所述第二区域为无法满足或超额满足所述目标服务水平协议要求的区域。
在本申请的一些实施例中，所述第一网络切片对应的切片质量信息包括所述第一网络切片的第二时间对应的服务体验信息和/或所述第二时间对应的服务体验信息相对于所述目标服务水平协议要求的满足程度信息，所述第二时间为所示第二时间信息所指示的时间。
在本申请的一些实施例中，所述第二时间为无法满足或超额满足所述目标服务水平协议要求的时间。
在本申请的一些实施例中，所述第一网络切片对应的切片质量信息包括所述第一网络切片的第二区域和第二时间对应的服务体验信息和/或所述第二区域和第二时间对应的服务体验信息相对于所述目标服务水平协议要求的满足程度信息，所述第二区域为所述第二区域信息所指示的区域，所述第二时间为所示第二时间信息所指示的时间。
在本申请的一些实施例中，处理单元802，用于若所述第一网络切片的服务体验信息无法满足所述目标服务水平协议要求，则增加为所述第一网络切片调度的资源；若所述第一网络切片的服务体验信息超额满足所述目标服务水平协议要求，则减少为所述第一网络切片调度的资源。
本申请实施例提供的网络设备80用于执行图2或图7A对应的方法实施例中网络设备所执行的方法，故本申请实施例可以参考图2或图7A对应的方法实施例中的相关部分进行理解。
本申请实施例中，网络设备80以采用集成的方式划分各个功能单元的形式来呈现。这里的“功能单元”可以指特定应用集成电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到网络设备80可以采用图8所示的形式。
比如，图8的处理器601可以通过调用存储器602中存储的计算机执行指令，使得网络设备80执行图2或图7A对应的方法实施例中网络设备所执行的方法。
具体的，图10中的接收单元801、处理单元802以及发送单元803的功能/实现过程可以通过图8中的处理器601调动存储器602中存储的计算机执行指令来实现。或者，图10中的处理单元802的功能/实现过程可以通过图8中的处理器601调用存储器602中存储的计算机执行指令来实现，图10中的接收单元801和发送单元803的功能/实现过程可以通过图8中的收发器604来实现。
由于本申请实施例提供的网络设备可用于执行图2或图7A对应的实施例方法，因此本申请实施例所能获得到的技术效果可参考图2或图7A对应的方法实施例，此处不再赘述。
比如，以采用集成的方式划分各个功能单元的情况下，图11示出了一种数据分析网元的结构示意图。如图11所示，本申请提供的数据分析网元90的一个实施例可以包括：接收单元901、处理单元902以及发送单元903；
接收单元901，用于接收切片管控网元发送的请求，所述请求包括对第一网络切片的服务体验要求信息；
处理单元902，用于确定与所述服务体验要求信息对应的第一区域信息和/或第一时间信息；
发送单元903，用于向所述切片管控网元发送响应，所述响应中包括与所述服务体验 要求信息对应的第一区域信息和/或第一时间信息。
由本申请的方案可知，数据分析网元可以确定出第一网络切片中存在问题的第一区域信息和/或第一时间信息，从而有利于网络设备更准确的做资源调度。
在本申请的一些实施例中，处理单元902，用于确定所述第一区域信息和/或所述第一时间信息所对应的所述第一网络切片的第一服务体验信息；则所述响应中还包括所述第一区域信息和/或所述第一时间信息所对应的所述第一网络切片的第一服务体验信息。
在本申请的一些实施例中，所述第一网络切片的服务体验要求信息包括正向服务体验要求信息和/或负向服务体验要求信息，所述正向服务体验要求信息为超额满足第一服务水平协议要求信息的过滤信息，所述负向服务体验要求信息为不满足第二服务水平协议要求信息的过滤信息。
在本申请的一些实施例中，处理单元902，还用于在所述请求中还包括第三区域信息时，所述第三区域信息所指示的第三区域包括所述第一区域信息所指示的第一区域时，根据所述第三区域信息，在所述第三区域中获取与所述服务体验要求信息对应的所述第一区域信息。
在本申请的一些实施例中，处理单元902，还用于在所述请求中还包括第三时间信息，所述第三时间信息所指示的第三时间包括所述第一时间信息所指示的第一时间时，根据所述第三时间信息，在所述第三时间信息中获取与所述服务体验要求信息对应的所述第一时间信息。
在本申请的一些实施例中，所述第一网络切片的服务体验要求信息包括以下信息中的至少一项：所述第一网络切片的用户数要求、业务的平均用户体验MOS的过滤要求、业务的用户满意比例的过滤要求，其中，所述业务的用户满意比例为所述业务对应的用户体验不差于预设值的用户数占所述业务总用户数的比例。
在本申请的一些实施例中，所述第一网络切片的第一服务体验信息包括以下信息中的至少一项：所述第一网络切片的用户数信息、业务的用户数信息、业务的平均用户体验MOS信息、业务的用户满意比例信息，其中，所述业务的用户满意比例为所述业务对应的用户体验不差于预设值的用户数占所述业务总用户数的比例。
本申请实施例提供的数据分析网元90用于执行图2或图7A对应的方法实施例中切片管控网元所执行的方法，故本申请实施例可以参考图2或图7A对应的方法实施例中的相关部分进行理解。
本申请实施例中，数据分析网元90以采用集成的方式划分各个功能单元的形式来呈现。这里的“功能单元”可以指特定应用集成电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到数据分析网元90可以采用图8所示的形式。
比如，图8的处理器601可以通过调用存储器602中存储的计算机执行指令，使得数据分析网元90执行图2或图7A对应的方法实施例中数据分析网元所执行的方法。
具体的，图11中的接收单元901、处理单元902以及发送单元903的功能/实现过程可以通过图8中的处理器601调动存储器602中存储的计算机执行指令来实现。或者，图 11中的处理单元902的功能/实现过程可以通过图8中的处理器601调用存储器602中存储的计算机执行指令来实现，图11中的接收单元901和发送单元903的功能/实现过程可以通过图8中的收发器604来实现。
由于本申请实施例提供的网络设备可用于执行图2或图7A对应的实施例方法，因此本申请实施例所能获得到的技术效果可参考图2或图7A对应的方法实施例，此处不再赘述。
比如，以采用集成的方式划分各个功能单元的情况下，图12示出了一种网络设备的结构示意图。如图12所示，本申请网络设备100的一个实施例可以包括：接收单元1001、处理单元1002以及发送单元1003；
接收单元1001，用于接收网管网元发送的第一网络切片的资源配置信息，所述资源配置信息包括最大资源配置信息和/或保证资源配置信息，所述最大资源配置信息用于指示所述第一网络切片最大能使用的资源，所述保证资源配置信息用于指示所述第一网络切片保证能使用的资源；
处理单元1002，用于根据所述第一网络切片的资源配置信息为所述第一网络切片调度资源。
本申请实施例提供的方案，网络切片的资源不需要与网络切片绑定，在需要使用时，可以在最大能使用的资源的范围下，优先使用保证能使用的资源，既保证了网络切片有资源可用，也提高了资源的灵活性。
在本申请的一些实施例中，所述第一网络切片保证能使用的资源允许被第二网络切片使用。
在本申请的一些实施例中，当所述网络设备为接入网设备时，所述最大资源配置信息为最大空口资源配置信息和/或保证资源配置信息为保证空口资源配置信息。
在本申请的一些实施例中，处理单元1002，用于根在所述最大资源配置信息的限制范围内，根据所述保证资源配置信息优先保证为所述第一网络切片调度所述保证能使用的资源。
在本申请的一些实施例中，处理单元1002，用于所述最大资源配置信息和/或保证资源配置信息为第一时间对应的最大资源配置信息和/或保证资源配置信息；根据所述第一时间对应的最大资源配置信息和/或保证资源配置信息为所述第一网络切片在所述第一时间调度资源。
在本申请的一些实施例中，处理单元1002，用于所述最大资源配置信息和/或保证资源配置信息为第一区域对应的最大资源配置信息和/或保证资源配置信息，根据所述第一区域对应的最大资源配置信息和/或保证资源配置信息为所述第一网络切片在所述第一区域调度资源。
在本申请的一些实施例中，接收单元1001，用于接收切片管控网元发送的所述第一网络切片对应的切片质量信息，所述切片质量信息包括所述第一网络切片的服务体验信息和/或所述第一网络切片的服务体验信息相对于目标服务水平协议要求的满足程度信息；
处理单元1002，用于根据所述切片质量信息调整为所述第一网络切片调度的资源。
在本申请的一些实施例中，所述第一网络切片对应的切片质量信息包括所述第一网络 切片的第二区域对应的服务体验信息和/或所述第二区域对应的服务体验信息相对于所述目标服务水平协议要求的满足程度信息。
在本申请的一些实施例中，所述第二区域为无法满足或超额满足所述目标服务水平协议要求的区域。
在本申请的一些实施例中，所述第一网络切片对应的切片质量信息包括所述第一网络切片的第二时间对应的服务体验信息和/或所述第二时间对应的服务体验信息相对于所述目标服务水平协议要求的满足程度信息。
在本申请的一些实施例中，所述第二时间为无法满足或超额满足所述目标服务水平协议要求的时间。
在本申请的一些实施例中，处理单元1002，用于若所述第一网络切片的服务体验信息无法满足所述目标服务水平协议要求，则增加为所述第一网络切片调度的资源；若所述第一网络切片的服务体验信息超额满足所述目标服务水平协议要求，则减少为所述第一网络切片调度的资源。
本申请实施例提供的网络设备100用于执行图3、图4或图7A对应的方法实施例中切片管控网元所执行的方法，故本申请实施例可以参考图3、图4或图7A对应的方法实施例中的相关部分进行理解。
本申请实施例中，网络设备100以采用集成的方式划分各个功能单元的形式来呈现。这里的“功能单元”可以指特定应用集成电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到网络设备100可以采用图8所示的形式。
比如，图8的处理器601可以通过调用存储器602中存储的计算机执行指令，使得网络设备100执行图3、图4或图7A对应的方法实施例中网络设备所执行的方法。
具体的，图12中的接收单元1001、处理单元1002以及发送单元1003的功能/实现过程可以通过图8中的处理器601调动存储器602中存储的计算机执行指令来实现。或者，图12的处理单元1002的功能/实现过程可以通过图8中的处理器601调用存储器602中存储的计算机执行指令来实现，图12中的接收单元1001和发送单元1003的功能/实现过程可以通过图8中的收发器604来实现。
由于本申请实施例提供的网络设备可用于执行图3、图4或图7A对应的实施例方法，因此本申请实施例所能获得到的技术效果可参考图3、图4或图7A对应的方法实施例，此处不再赘述。
比如，以采用集成的方式划分各个功能单元的情况下，图13示出了一种网管网元的结构示意图。如图13所示，本申请网管网元110的一个实施例可以包括：接收单元1101、处理单元1102以及发送单元1103；
处理单元1102，用于确定第一网络切片的资源配置信息，所述资源配置信息包括最大资源配置信息和/或保证资源配置信息，所述最大资源配置信息用于指示所述第一网络切片最大能使用的资源，所述保证资源配置信息用于指示所述第一网络切片保证能使用的资源；
发送单元1103，用于向所述网络设备发送所述第一网络切片的资源配置信息，所述资 源配置信息用于网络设备根据所述资源配置信息为所述第一网络切片的调度资源。
本申请实施例提供的方案，网络切片的资源不需要与网络切片绑定，在需要使用时，可以在最大能使用的资源的范围下，优先使用保证能使用的资源，既保证了网络切片有资源可用，也提高了资源的灵活性。
在本申请的一些实施例中，所述最大资源配置信息为最大空口资源配置信息和/或保证资源配置信息为保证空口资源配置信息。
在本申请的一些实施例中，所述最大资源配置信息和/或保证资源配置信息为第一时间对应的最大资源配置信息和/或保证资源配置信息；或者，所述最大资源配置信息和/或保证资源配置信息为第一区域对应的最大资源配置信息和/或保证资源配置信息。
在本申请的一些实施例中，处理单元1102，用于根据所述第一网络切片的目标服务水平协议要求信息，确定所述第一网络切片的资源配置信息。
在本申请的一些实施例中，处理单元1102，用于获取所述网络设备为所述第一网络切片调度的资源的信息；获取所述第一网络切片的切片质量信息，所述切片质量信息包括所述第一网络切片的服务体验信息和/或所述第一网络切片的服务体验信息相对于所述目标服务水平协议要求的满足程度信息；根据所述网络设备为所述第一网络切片调度的资源的信息和所述切片质量信息，更新所述第一网络切片的资源配置信息；所述网管网元向所述网络设备发送所述更新后的资源配置信息。
在本申请的一些实施例中，处理单元1102，用于在所述资源的信息包括所述第一网络切片的第二区域对应的资源的信息，所述第一网络切片的服务体验信息包括所述第一网络切片的所述第二区域对应的服务体验信息时，根据所述第二区域对应的资源的信息和所述第二区域对应的服务体验信息，更新所述第一网络切片的资源配置信息。
在本申请的一些实施例中，处理单元1102，用于在所述资源的信息包括所述第一网络切片的第二时间对应的资源的信息，所述第一网络切片的服务体验信息包括所述第一网络切片的所述第二时间对应的服务体验信息时，根据所述第二时间对应的资源的信息和所述第二时间对应的服务体验信息，更新所述第一网络切片的资源配置信息。
在本申请的一些实施例中，处理单元1102，用于更新所述最大资源配置信息和/或保证资源配置信息，使得所述更新后的最大资源配置信息不小于所述网络设备为所述第一网络切片调度的资源。
在本申请的一些实施例中，接收单元1101，用于从所述切片管控网元或数据分析设备获取所述切片质量信息。
本申请实施例提供的网管网元110用于执行图3、图4或图7A对应的方法实施例中切片管控网元所执行的方法，故本申请实施例可以参考图3、图4或图7A对应的方法实施例中的相关部分进行理解。
本申请实施例中，网管网元110以采用集成的方式划分各个功能单元的形式来呈现。这里的“功能单元”可以指特定应用集成电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到网管网元110可以采用图8所示的形式。
比如，图8的处理器601可以通过调用存储器602中存储的计算机执行指令，使得网管网元110执行图3、图4或图7A对应的方法实施例中网管网元所执行的方法。
具体的，图13中的接收单元1101、处理单元1102以及发送单元1103的功能/实现过程可以通过图8中的处理器601调动存储器602中存储的计算机执行指令来实现。或者，图13中的处理单元1102的功能/实现过程可以通过图8中的处理器601调用存储器602中存储的计算机执行指令来实现，图13中的接收单元1101和发送单元1103的功能/实现过程可以通过图8中的收发器604来实现。
由于本申请实施例提供的网管网元可用于执行图3、图4或图7A对应的实施例方法，因此本申请实施例所能获得到的技术效果可参考图3、图4或图7A对应的方法实施例，此处不再赘述。
比如，以采用集成的方式划分各个功能单元的情况下，图14示出了一种切片管控网元的结构示意图。如图14所示，本申请切片管控网元120的一个实施例可以包括：接收单元1201、处理单元1202以及发送单元1203；
接收单元1201，用于接收网管网元发送的目标网络切片的用户数量限制信息，以及指示信息，所述指示信息用于指示所述目标网络切片的状态信息或者所述用户数量限制信息的可信度；
处理单元1202用于，根据所述指示信息和所述用户数量限制信息控制所述目标网络切片所服务的用户的数量。
该实施例提供的方案可以根据指示信息和所述用户数量限制信息控制目标网络切片所服务的用户的数量，可以提高用户数量控制的准确度。
在本申请的一些实施例中，处理单元1202用于，在所述指示信息用于指示所述目标网络切片的状态信息时，根据所述用户数量限制信息按照所述状态信息所对应的控制方式，控制所述目标网络切片所服务的用户的数量。
在本申请的一些实施例中，所述状态信息包括测试状态或稳定状态。
在本申请的一些实施例中，当所述状态信息为测试状态时，所述控制方式为阶梯控制的方式。
在本申请的一些实施例中，当所述状态信息为稳定状态时，所述控制方式为一次性控制的方式。
在本申请的一些实施例中，处理单元1202用于，在所述指示信息用于指示所述用户数量限制信息的可信度时，根据所述用户数量限制信息按照所述可信度所对应的控制方式，控制所述目标网络切片所服务的用户的数量。
在本申请的一些实施例中，在所述可信度不符合可信度要求时，所述控制方式为阶梯控制的方式。
在本申请的一些实施例中，在所述可信度符合可信度要求时，所述控制方式为一次性控制的方式。
在本申请的一些实施例中，接收单元1201，用于接收所述网管网元发送的所述目标网络切片的服务水平协议要求信息，所述服务水平协议要求信息中包括所述目标网络切片的 用户数量限制信息。
在本申请的一些实施例中，接收单元1201，用于接收所述网管网元发送的所述目标网络切片的区域信息所对应的用户数量限制信息；
处理单元1202用于，针对所述区域信息所指示的区域，根据所述指示信息和所述区域信息所对应的用户数量限制信息控制所述目标网络切片所服务的用户的数量。
本申请实施例提供的切片管控网元120用于执行图5或图7A对应的方法实施例中切片管控网元所执行的方法，故本申请实施例可以参考图5或图7A对应的方法实施例中的相关部分进行理解。
本申请实施例中，切片管控网元120以采用集成的方式划分各个功能单元的形式来呈现。这里的“功能单元”可以指特定应用集成电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到切片管控网元120可以采用图8所示的形式。
比如，图8的处理器601可以通过调用存储器602中存储的计算机执行指令，使得切片管控网元120执行图5或图7A对应的方法实施例中切片管控网元所执行的方法。
具体的，图14中的接收单元1201、处理单元1202以及发送单元1203的功能/实现过程可以通过图8中的处理器601调动存储器602中存储的计算机执行指令来实现。或者，图14中的处理单元1202的功能/实现过程可以通过图8中的处理器601调用存储器602中存储的计算机执行指令来实现，图14中的接收单元1201和发送单元1203的功能/实现过程可以通过图8中的收发器604来实现。
由于本申请实施例提供的切片管控网元可用于执行图5或图7A对应的实施例方法，因此本申请实施例所能获得到的技术效果可参考图5或图7A对应的方法实施例，此处不再赘述。
比如，以采用集成的方式划分各个功能单元的情况下，图15示出了一种网管网元的结构示意图。如图15所示，本申请网管网元130的一个实施例可以包括：接收单元1301、处理单元1302以及发送单元1303；
处理单元1302，用于确定目标网络切片的用户数量限制信息以及指示信息，所述指示信息用于指示所述目标网络切片的状态信息或者所述用户数量限制信息的可信度；
发送单元1303，用于向所述切片管控网元发送所述目标网络切片的用户数量限制信息，以及所述指示信息，所述指示信息和所述用户数量限制信息用于所述切片管控网元控制所述目标网络切片所服务的用户的数量。
本申请提供的方案，可以根据指示信息和所述用户数量限制信息控制目标网络切片所服务的用户的数量，可以提高用户数量控制的准确度。
在本申请的一些实施例中，处理单元1302，用于获取所述目标网络切片的服务水平协议要求信息；根据所述服务水平协议要求信息确定所述目标网络切片的用户数量限制信息。
在本申请的一些实施例中，发送单元1303，用于向所述切片管控网元发送所述目标网络切片的区域信息和所述区域信息所对应的用户数量限制信息，所述区域信息和所述区域信息所对应的用户数量限制信息用于所述切片管控网元针对所述区域信息所指示的区域， 在所述区域信息所对应的用户数量限制信息所指示的范围内控制所述目标网络切片所服务的用户的数量。
在本申请的一些实施例中，发送单元1303，用于向所述切片管控网元发送所述目标网络切片的时间信息和所述时间信息所对应的用户数量限制信息，所述时间信息和所述时间信息所对应的用户数量限制信息用于针对所述时间信息所指示的时间，在所述时间信息所对应的用户数量限制信息所指示的范围内控制所述目标网络切片所服务的用户的数量。
本申请实施例提供的网管网元130用于执行图5或图7A对应的方法实施例中网管网元所执行的方法，故本申请实施例可以参考图5或图7A对应的方法实施例中的相关部分进行理解。
本申请实施例中，网管网元130以采用集成的方式划分各个功能单元的形式来呈现。这里的“功能单元”可以指特定应用集成电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到网管网元130可以采用图8所示的形式。
比如，图8的处理器601可以通过调用存储器602中存储的计算机执行指令，使得网管网元130执行图5或图7A对应的方法实施例中网管网元所执行的方法。
具体的，图15中的接收单元1301、处理单元1302以及发送单元1303的功能/实现过程可以通过图8中的处理器601调动存储器602中存储的计算机执行指令来实现。或者，图15中的处理单元1302的功能/实现过程可以通过图8中的处理器601调用存储器602中存储的计算机执行指令来实现，图15中的接收单元1301和发送单元1303的功能/实现过程可以通过图8中的收发器604来实现。
由于本申请实施例提供的网管网元可用于执行图5或图7A对应的实施例方法，因此本申请实施例所能获得到的技术效果可参考图5或图7A对应的方法实施例，此处不再赘述。
比如，以采用集成的方式划分各个功能单元的情况下，图16示出了一种切片管控网元的结构示意图。如图16所示，本申请切片管控网元140的一个实施例可以包括：接收单元1401、处理单元1402以及发送单元1403；
处理单元1402，用于确定导致第一网络切片的服务体验信息无法满足或超额满足所述第一网络切片的目标服务水平协议信息的原因在于第一网络域；
发送单元1403，用于向所述第一网络域的网络设备发送所述第一网络切片的切片质量信息，所述切片质量信息用于所述网络设备根据所述切片质量信息为所述第一网络切片调度资源。
本申请提供的方案，切片管控网元可先精确定位出第一网络切片的服务体验信息无法满足目标服务水平协议要求信息的原因是出自某网络域(如接入网域)，随后再向该网络域的网络设备提供该第一网络切片的切片质量信息，以便于该网络域的网络设备调整资源的调度情况。该方法可避免盲目地调整其他正常工作的网络域的资源调度情况，提升资源调度的准确性。
在本申请的一些实施例中，接收单元1401，用于从数据分析网元或网管网元获取所述第一网络切片的切片质量信息。
在本申请的一些实施例中，处理单元1402，还用于当所述第一网络切片的切片质量信息为所述第一网络切片的服务体验信息时，根据所述第一网络切片的服务体验信息确定所述第一网络切片的服务体验信息相对于所述目标服务水平协议要求信息的满足程度信息。
在本申请的一些实施例中，处理单元1402，还用于确定所述第一网络切片的服务体验信息无法满足或超额满足所述第一网络切片的目标服务水平协议信息。
在本申请的一些实施例中，接收单元1401，用于元从所述网管网元获取指示信息，所述指示信息用于指示导致第一网络切片的服务体验信息无法满足或超额满足所述第一网络切片的目标服务水平协议信息的原因在于第一网络域；
处理单元1402，还用于根据所述指示信息确定导致第一网络切片的服务体验信息无法满足或超额满足所述第一网络切片的目标服务水平协议信息的原因在于第一网络域。
在本申请的一些实施例中，发送单元1403，用于向所述网管网元发送请求消息，所述请求消息用于请求导致所述第一网络切片的服务体验信息无法满足或超额满足所述第一网络切片的目标服务水平协议信息的网络域；
接收单元1401，用于接收所述网管网元发送的响应消息，所述响应消息中包含所述指示信息。
在本申请的一些实施例中，接收单元1401，用于从所述网管网元获取可信度信息，所述可信度信息用于指示所述指示信息的可信程度；
处理单元1402，用于根据所述可信度信息以及所述指示信息确定导致第一网络切片的服务体验信息无法满足或超额满足所述第一网络切片的目标服务水平协议信息的原因在于第一网络域。
在本申请的一些实施例中，所述服务体验信息包括区域信息和/或时间信息对应的第一网络切片的服务体验信息。
在本申请的一些实施例中，所述满足程度信息包括无法满足、满足或者超额满足。
在本申请的一些实施例中，处理单元1402用于：
获取所述第一网络切片的初始服务水平协议要求信息；
根据所述第一网络切片的初始服务水平协议要求信息确定至少一个服务水平协议要求信息；
将所述至少一个服务水平协议要求信息中的一个确定为所述目标服务水平协议要求信息。
在本申请的一些实施例中，所述第一网络域包括以下至少一项：接入网域、核心网域、传输网域。
在本申请的一些实施例中，所述网络设备包括以下设备的至少一个：接入网设备、用于分配用户面或控制面资源的核心网设备、传输网设备。
在本申请的一些实施例中，所述服务水平协议要求信息包括以下信息中的至少一项：所述第一网络切片的用户数要求信息、业务的平均用户体验的要求信息、业务的用户满意比例的要求信息，其中，所述业务的用户满意比例为所述业务对应的用户体验不差于预设值的用户数占该业务总用户数的比例。
本申请实施例提供的切片管控网元140用于执行图7B对应的方法实施例中切片管控网元所执行的方法，故本申请实施例可以参考图7B对应的方法实施例中的相关部分进行理解。
本申请实施例中，切片管控网元140以采用集成的方式划分各个功能单元的形式来呈现。这里的“功能单元”可以指特定应用集成电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到切片管控网元140可以采用图8所示的形式。
比如，图8的处理器601可以通过调用存储器602中存储的计算机执行指令，使得切片管控网元140执行图7B对应的方法实施例中切片管控网元所执行的方法。
具体的，图16中的接收单元1401、处理单元1402以及发送单元1403的功能/实现过程可以通过图8中的处理器601调动存储器602中存储的计算机执行指令来实现。或者，图16中的处理单元1402的功能/实现过程可以通过图8中的处理器601调用存储器602中存储的计算机执行指令来实现，图16中的接收单元1401和发送单元1403的功能/实现过程可以通过图8中的收发器604来实现。
由于本申请实施例提供的切片管控网元可用于执行图7B对应的实施例方法，因此本申请实施例所能获得到的技术效果可参考图7B对应的方法实施例，此处不再赘述。
比如，以采用集成的方式划分各个功能单元的情况下，图17示出了一种网管网元的结构示意图。如图17所示，本申请网管网元150的一个实施例可以包括：接收单元1501、处理单元1502以及发送单元1503；
处理单元1502，用于确定导致第一网络切片的服务体验信息无法满足或超额满足所述第一网络切片的目标服务水平协议信息的原因在于第一网络域；
向切片管控网元发送指示信息，所述指示信息用于指示导致第一网络切片的服务体验信息无法满足或超额满足所述第一网络切片的目标服务水平协议信息的原因在于第一网络域。
本申请实施例中，网管网元可以通知切片管控网元导致第一网络切片的服务体验信息无法满足或超额满足所述第一网络切片的目标服务水平协议信息的原因所在的第一网络域，例如：接入网络域，这样就可以可避免盲目地调整其他正常工作的网络域的资源调度情况，提升资源调度的准确性。
在本申请的一些实施例中，处理单元1502，还用于确定可信度信息，所述可信度信息用于指示所述指示信息的可信程度；
发送单元1503，还用于向所述切片管控网元发送所述可信度信息。
在本申请的一些实施例中，接收单元1501，用于从数据分析网元获取第一网络切片的切片质量信息，其中，所述切片质量信息包括以下信息的至少一项：所述第一网络切片的服务体验信息、所述第一网络切片的服务体验信息相对于所述目标服务水平协议要求信息的满足程度信息。
在本申请的一些实施例中，处理单元1502，还用于当所述第一网络切片的切片质量信 息为所述第一网络切片的服务体验信息时，根据所述第一网络切片的服务体验信息确定所述第一网络切片的服务体验信息相对于所述目标服务水平协议要求信息的满足程度信息。
在本申请的一些实施例中，处理单元1502，还用于确定所述第一网络切片的服务体验信息无法满足或超额满足所述第一网络切片目标服务水平协议信息。
在本申请的一些实施例中，所述服务体验信息包括区域信息和/或时间信息对应的第一网络切片的服务体验信息。
在本申请的一些实施例中，接收单元1501，还用于接收所述切片管控网元发送的请求消息，所述请求消息用于请求导致所述服务体验信息无法满足或超额满足所述第一网络切片的目标服务水平协议信息的网络域；
发送单元1503，还用于向所述切片管控网元发送的响应消息，所述响应消息中包含所述指示信息。
在本申请的一些实施例中，处理单元1502还用于：
获取所述第一网络切片的初始服务水平协议要求信息；
根据所述第一网络切片的初始服务水平协议要求信息确定至少一个服务水平协议要求信息；
将所述至少一个服务水平协议要求信息中的一个确定为所述目标服务水平协议要求信息。
在本申请的一些实施例中，所述第一网络域包括以下至少一项：接入网域、核心网域、传输网域。
在本申请的一些实施例中，所述服务水平协议要求信息包括以下信息中的至少一项：所述第一网络切片的用户数要求信息、业务的平均用户体验的要求信息、业务的用户满意比例的要求信息，其中，所述业务的用户满意比例为所述业务对应的用户体验不差于预设值的用户数占该业务总用户数的比例。
本申请实施例提供的网管网元150用于执行图7B对应的方法实施例中网管网元所执行的方法，故本申请实施例可以参考图7B对应的方法实施例中的相关部分进行理解。
本申请实施例中，网管网元150以采用集成的方式划分各个功能单元的形式来呈现。这里的“功能单元”可以指特定应用集成电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到网管网元150可以采用图8所示的形式。
比如，图8的处理器601可以通过调用存储器602中存储的计算机执行指令，使得网管网元150执行图7B对应的方法实施例中网管网元所执行的方法。
具体的，图17中的接收单元1501、处理单元1502以及发送单元1503的功能/实现过程可以通过图8中的处理器601调动存储器602中存储的计算机执行指令来实现。或者，图17中的处理单元1502的功能/实现过程可以通过图8中的处理器601调用存储器602中存储的计算机执行指令来实现，图17中的接收单元1501和发送单元1503的功能/实现过程可以通过图8中的收发器604来实现。
由于本申请实施例提供的网管网元可用于执行图7B对应的实施例方法，因此本申请 实施例所能获得到的技术效果可参考图7B对应的方法实施例，此处不再赘述。
比如，以采用集成的方式划分各个功能单元的情况下，图18示出了一种网络设备的结构示意图。如图18所示，本申请网络设备160的一个实施例可以包括：接收单元1601、处理单元1602以及发送单元1603；
处理单元1602，用于确定第一网络切片的状态信息，第一网络切片的状态信息包括所述第一网络切片处于未签署SLA状态或已经签署SLA状态；
处理单元1602，还用于根据所述第一网络切片的状态信息为所述第一网络切片调度资源。
在本申请的一些实施例中，处理单元1602，用于当所述网络设备为接入网设备时，根据所述第一网络切片的状态信息为所述第一网络切片调度空口资源。
在本申请的一些实施例中，处理单元1602，还用于确定第二网络切片的状态信息为所述第二网络切片处于已经签署SLA状态；
处理单元1602，用于当所述第一网络切片的状态信息为所述第一网络切片处于未签署SLA状态，落后(deprioritized)于所述第二网络切片而为所述第一网络切片调度资源。
在本申请的一些实施例中，处理单元1602，还用于确定第二网络切片的状态信息为所述第二网络切片处于未签署SLA状态；
处理单元1602，用于当所述第一网络切片的状态信息为所述第一网络切片已签署SLA状态，优先于所述第二网络切片而为所述第一网络切片调度资源。
在本申请的一些实施例中，处理单元1602，用于根据网管网元发送的所述第一网络切片的状态指示信息确定所述第一网络切片的状态信息，所述状态指示信息中包含所述第一网络切片的状态信息。
在本申请的一些实施例中，接收单元1601，用于接收网管网元发送的所述第一网络切片的资源配置信息，所述资源配置信息包括最大资源配置信息和/或保证资源配置信息，所述最大资源配置信息用于指示所述第一网络切片最大能使用的资源，所述保证资源配置信息用于指示所述第一网络切片保证能使用的资源；所述网络设备根据所述第一网络切片的资源配置信息和所述第一网络切片的状态信息为所述第一网络切片调度资源。该资源配置信息还可以包括第一网络切片的状态信息。
在本申请的一些实施例中，当所述网络设备为接入网设备时，所述最大资源配置信息为最大空口资源配置信息和/或保证资源配置信息为保证空口资源配置信息。
本申请实施例提供的网络设备160用于执行图7C对应的方法实施例中网络设备所执行的方法，故本申请实施例可以参考图7C对应的方法实施例中的相关部分进行理解。
本申请实施例中，网络设备160以采用集成的方式划分各个功能单元的形式来呈现。这里的“功能单元”可以指特定应用集成电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到网络设备160可以采用图8所示的形式。
比如，图8的处理器601可以通过调用存储器602中存储的计算机执行指令，使得网络设备160执行图7C对应的方法实施例中网络设备所执行的方法。
具体的，图18中的接收单元1601、处理单元1602以及发送单元1603的功能/实现过程可以通过图8中的处理器601调动存储器602中存储的计算机执行指令来实现。或者，图18中的处理单元1602的功能/实现过程可以通过图8中的处理器601调用存储器602中存储的计算机执行指令来实现，图18中的接收单元1601和发送单元1603的功能/实现过程可以通过图8中的收发器604来实现。
由于本申请实施例提供的网络设备可用于执行图7C对应的实施例方法，因此本申请实施例所能获得到的技术效果可参考图7C对应的方法实施例，此处不再赘述。
比如，以采用集成的方式划分各个功能单元的情况下，图19示出了一种网管网元的结构示意图。如图19所示，本申请网管网元170的一个实施例可以包括：接收单元1701、处理单元1702以及发送单元1703；
处理单元1702，用于确定第一网络切片的状态信息，所述第一网络切片的状态信息包括所述第一网络切片处于未签署SLA状态或已经签署SLA状态；
发送单元1703，用于向网络设备发送所述第一网络切片的状态信息，所述第一网络切片的状态信息用于所述网络设备为所述第一网络切片调度资源。
本申请实施例中，网管网元能及时将第一网络切片的状态信息通知给网络设备，以便网络设备根据第一网络切片所处的SLA状态执行对应的资源调度。
在本申请的一些实施例中，处理单元1702，用于确定所述第一网络切片的资源配置信息，所述资源配置信息包括最大资源配置信息和/或保证资源配置信息，所述最大资源配置信息用于指示所述第一网络切片最大能使用的资源，所述保证资源配置信息用于指示所述第一网络切片保证能使用的资源；所述网管网元向所述网络设备发送所述第一网络切片的资源配置信息，所述资源配置信息用于网络设备根据所述资源配置信息为所述第一网络切片的调度资源。该资源配置信息还可以包括第一网络切片的状态信息。
在本申请的一些实施例中，当所述网络设备为接入网设备时，所述最大资源配置信息为最大空口资源配置信息和/或保证资源配置信息为保证空口资源配置信息。
在本申请的一些实施例中，所述资源配置信息包括所述第一网络切片的状态信息。
本申请实施例提供的网管网元170用于执行图7C对应的方法实施例中网管网元所执行的方法，故本申请实施例可以参考图7C对应的方法实施例中的相关部分进行理解。
本申请实施例中，网管网元170以采用集成的方式划分各个功能单元的形式来呈现。这里的“功能单元”可以指特定应用集成电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到网管网元170可以采用图8所示的形式。
比如，图8的处理器601可以通过调用存储器602中存储的计算机执行指令，使得网管网元170执行图7C对应的方法实施例中网管网元所执行的方法。
具体的，图19中的接收单元1701、处理单元1702以及发送单元1703的功能/实现过程可以通过图8中的处理器601调动存储器602中存储的计算机执行指令来实现。或者，图19中的处理单元1702的功能/实现过程可以通过图8中的处理器601调用存储器602中存储的计算机执行指令来实现，图19中的接收单元1701和发送单元1703的功能/实现过 程可以通过图8中的收发器604来实现。
由于本申请实施例提供的网管网元可用于执行图7C对应的实施例方法，因此本申请实施例所能获得到的技术效果可参考图7C对应的方法实施例，此处不再赘述。
在本申请图9-图19的设备中各个组件通信连接，即处理单元(或者处理器)、存储单元(或者存储器)和收发单元(收发器)之间通过内部连接通路互相通信，传递控制和/或数据信号。本申请上述方法实施例可以应用于处理器中，或者由处理器实现上述方法实施例的步骤。处理器可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是中央处理器(central processing unit，CPU)，网络处理器(network processor，NP)或者CPU和NP的组合、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。虽然图中仅仅示出了一个处理器，该装置可以包括多个处理器或者处理器包括多个处理单元。具体的，处理器可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器。
存储器用于存储处理器执行的计算机指令。存储器可以是存储电路也可以是存储器。存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器、可编程只读存储器、可擦除可编程只读存储器、电可擦除可编程只读存储器或闪存。易失性存储器可以是随机存取存储器，其用作外部高速缓存。存储器可以独立于处理器，也可以是处理器中的存储单元，在此不做限定。虽然图中仅仅示出了一个存储器，该装置也可以包括多个存储器或者存储器包括多个存储单元。
收发器用于实现处理器与其他单元或者网元的内容交互。具体的，收发器可以是该装置的通信接口，也可以是收发电路或者通信单元，还可以是收发信机。收发器还可以是处理器的通信接口或者收发电路。可选的，收发器可以是一个收发芯片。该收发器还可以包括发送单元和/或接收单元。在一种可能的实现方式中，该收发器可以包括至少一个通信接口。在另一种可能的实现方式中，该收发器也可以是以软件形式实现的单元。在本申请的各实施例中，处理器可以通过收发器与其他单元或者网元进行交互。例如：处理器通过该收发器获取或者接收来自其他网元的内容。若处理器与收发器是物理上分离的两个部件，处理器可以不经过收发器与该装置的其他单元进行内容交互。
一种可能的实现方式中，处理器、存储器以及收发器可以通过总线相互连接。总线可 以是外设部件互连标准(peripheral component interconnect，PCI)总线或扩展工业标准结构(extended industry standard architecture，EISA)总线等。所述总线可以分为地址总线、数据总线、控制总线等。
本申请实施例中，“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请实施例中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其他实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念。
在本申请的各实施例中，为了方面理解，进行了多种举例说明。然而，这些例子仅仅是一些举例，并不意味着是实现本申请的最佳实现方式。
在本申请的各实施例中，为了方便的描述，采用了请求消息，响应消息以及其他各种消息的名称。然而，这些消息仅仅是以举例方式说明需要携带的内容或者实现的功能，本申请不限定消息的具体名称，例如：还可以是第一消息，第二消息，第三消息等。这些消息可以是具体的一些消息，可以是消息中的某些字段。这些消息还可以代表各种服务化操作。
上述实施例，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现，当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。
所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机执行指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存储的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘Solid State Disk(SSD))等。
以上对本申请所提供的技术方案进行了详细介绍，本申请中应用了具体个例对本申请的原理及实施方式进行了阐述，以上实施例的说明只是用于帮助理解本申请的方法及其核心思想；同时，对于本领域的一般技术人员，依据本申请的思想，在具体实施方式及应用范围上均会有改变之处，综上所述，本说明书内容不应理解为对本申请的限制。

Claims (30)

  1. 一种网络切片的资源调度的方法，其特征在于，包括：
    网管网元获取网络设备为第一网络切片调度的资源的信息；
    所述网管网元从数据分析设备获取所述第一网络切片的切片质量信息；
    所述网管网元根据所述网络设备为所述第一网络切片调度的资源的信息和所述切片质量信息，更新所述第一网络切片的资源配置信息。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述网管网元向所述网络设备发送所述更新后的资源配置信息。
  3. 根据权利要求1或2所述的方法，其特征在于，所述第一网络切片的切片质量信息包括所述第一网络切片的服务体验信息和/或所述第一网络切片的服务体验信息相对于目标服务水平协议要求的满足程度信息。
  4. 根据权利要求3所述的方法，其特征在于，所述第一网络切片的服务体验信息，包括：网络切片粒度的体验信息或网络切片中业务粒度的体验信息。
  5. 根据权利要求4所述的方法，其特征在于，所述网络切片粒度的体验信息包括以下信息的至少一种：网络切片的用户数信息、网络切片的端到端时延信息或网络切片的负载信息。
  6. 根据权利要求4所述的方法，其特征在于，所述网络切片中业务粒度的体验信息包括业务粒度的质量信息或业务的用户粒度的质量信息。
  7. 根据权利要求6所述的方法，其特征在于，所述业务粒度的质量信息包括：业务的用户数信息、业务的用户平均体验数值或业务的用户体验数值分布信息。
  8. 根据权利要求1-7任一项所述的方法，其特征在于，所述网络设备为接入网设备时，所述资源配置信息为空口资源配置信息。
  9. 根据权利要求1-8任一项所述的方法，其特征在于，所述资源配置信息包括最大资源配置信息和/或保证资源配置信息，所述最大资源配置信息用于指示所述第一网络切片最大能使用的资源，所述保证资源配置信息用于指示所述第一网络切片保证能使用的资源。
  10. 根据权利要求9所述的方法，其特征在于，所述最大资源配置信息和/或保证资源配置信息为第一时间对应的最大资源配置信息和/或保证资源配置信息；或者，所述最大资源配置信息和/或保证资源配置信息为第一区域对应的最大资源配置信息和/或保证资源配置信息。
  11. 根据权利要求1所述的方法，其特征在于，所述资源的信息包括所述第一网络切片的第二区域对应的资源的信息，所述第一网络切片的服务体验信息包括所述第一网络切片的所述第二区域对应的服务体验信息；
    所述网管网元根据所述网络设备为所述第一网络切片调度的资源的信息和所述第一网络切片的服务体验信息，调整所述第一网络切片的资源配置信息，可以包括：所述网管网元根据所述第二区域对应的资源的信息和所述第二区域对应的服务体验信息，调整所述第一网络切片的资源配置信息。
  12. 根据权利要求1所述的方法，其特征在于，所述资源的信息包括所述第一网络切片的第二时间对应的资源的信息，所述第一网络切片的服务体验信息包括所述第一网络切片的所述第二时间对应的服务体验信息；
    所述网管网元根据所述网络设备为所述第一网络切片调度的资源的信息和所述第一网络切片的服务体验信息，调整所述第一网络切片的资源配置信息，可以包括：所述网管网元根据所述第二时间对应的资源的信息和所述第二时间对应的服务体验信息，调整所述第一网络切片的资源配置信息。
  13. 一种网络切片的资源调度的方法，其特征在于，包括：
    切片管控网元向数据分析网元发送请求，所述请求包括对第一网络切片的服务体验要求信息；
    所述切片管控网元接收所述数据分析网元发送的响应，所述响应中包括与所述服务体验要求信息对应的所述第一网络切片的第一区域信息和/或第一时间信息；
    所述切片管控网元根据所述第一区域信息和/或第一时间信息向网络设备发送第二区域信息和/或第二时间信息，所述第二区域信息和/或第二时间信息用于所述网络设备根据所述第二区域信息和/或第二时间信息为所述第一网络切片调度资源。
  14. 根据权利要求13所述的方法，其特征在于，所述响应还包括所述第一区域信息和/或所述第一时间信息所对应的所述第一网络切片的第一服务体验信息，所述方法包括：
    所述切片管控网元根据所述第一服务体验信息确定所述第二区域信息和/或所述第二时间信息。
  15. 根据权利要求13或14所述的方法，其特征在于，所述方法还包括：
    所述切片管控网元向所述网络设备发送所述第二区域信息和/或所述第二时间信息对应的切片质量信息，其中，所述切片质量信息包括以下信息的至少一项：所述第二区域信息和/或所述第二时间信息的对应所述第一网络切片的第二服务体验信息、所述第二服务体验信息相对于所述第一网络切片的目标服务水平协议要求信息的满足程度信息。
  16. 根据权利要求13-15任一项所述的方法，其特征在于，当所述网络设备为接入网设备时，所述第二区域信息用于所述接入网设备根据所述第二区域信息为所述第一网络切片调度接入网资源，所述第二时间信息用于所述接入网设备根据所述第二时间信息为所述第一网络切片调度接入网资源。
  17. 根据权利要求15所述的方法，其特征在于，所述满足程度信息包括无法满足、满足或者超额满足。
  18. 根据权利要求13-17任一项所述的方法，其特征在于，所述请求中还包括第三区域信息时，所述第三区域信息所指示的第三区域包括所述第一区域信息所指示的第一区域，所述第三区域信息用于向所述数据分析网元请求所述第三区域中与所述服务体验要求信息对应的所述第一区域信息。
  19. 根据权利要求13-18任一项所述的方法，其特征在于，所述请求中还包括第三时间信息时，所述第三时间信息所指示的第三时间包括所述第一时间信息所述指示的第一时间，所述第三时间信息用于向所述数据分析网元请求所述第三时间中与所述服务体验要求信息 对应的所述第一时间信息。
  20. 一种网络切片的资源调度的方法，其特征在于，包括：
    网络设备接收切片管控网元发送的第一网络切片的第二区域信息，和/或第二时间信息；
    所述网络设备根据所述第二区域信息和/或第二时间信息为所述第一网络切片调度资源。
  21. 根据权利要求20所述的方法，其特征在于，所述方法还包括：
    所述网络设备接收所述切片管控网元发送的所述第一网络切片对应的切片质量信息，所述切片质量信息包括所述第一网络切片的服务体验信息和/或所述第一网络切片的服务体验信息相对于目标服务水平协议要求的满足程度信息；
    所述网络设备根据所述切片质量信息调整为所述第一网络切片调度的资源。
  22. 一种网管网元，其特征在于，包括：
    接收单元，用于接收网络设备为第一网络切片调度的资源的信息，并从数据分析设备获取所述第一网络切片的切片质量信息；
    处理单元，用于根据所述接收单元接收的所述网络设备为所述第一网络切片调度的资源的信息和所述切片质量信息，更新所述第一网络切片的资源配置信息。
  23. 根据权利要求22所述的网管网元，其特征在于，还包括：
    发送单元，用于向所述网络设备发送所述更新后的资源配置信息。
  24. 根据权利要求22或23所述的网管网元，其特征在于，所述资源的信息包括所述第一网络切片的第二区域对应的资源的信息，所述第一网络切片的服务体验信息包括所述第一网络切片的所述第二区域对应的服务体验信息；
    所述处理单元，用于根据所述第二区域对应的资源的信息和所述第二区域对应的服务体验信息，调整所述第一网络切片的资源配置信息，所述第二区域与所述第一区域相同，或者所述第二区域与所述第一区域不相同。
  25. 根据权利要求22或23所述的网管网元，其特征在于，所述资源的信息包括所述第一网络切片的第二时间对应的资源的信息，所述第一网络切片的服务体验信息包括所述第一网络切片的所述第二时间对应的服务体验信息；
    所述处理单元，用于根据所述第二时间对应的资源的信息和所述第二时间对应的服务体验信息，调整所述第一网络切片的资源配置信息，所述第二时间与所述第一时间相同，或者所述第二时间与所述第一时间不相同。
  26. 一种切片管控网元，其特征在于，包括：
    发送单元，用于向数据分析网元发送请求，所述请求包括对第一网络切片的服务体验要求信息；
    接收单元，用于接收所述数据分析网元发送的响应，所述响应中包括与所述服务体验要求信息对应的所述第一网络切片的第一区域信息和/或第一时间信息；
    所述发送单元，用于根据所述第一区域信息和/或第一时间信息向网络设备发送第二区域信息和/或第二时间信息，所述第二区域信息和/或第二时间信息用于所述网络设备根据 所述第二区域信息和/或第二时间信息为所述第一网络切片调度资源。
  27. 一种网络设备，其特征在于，包括：
    接收单元，用于接收切片管控网元发送的第一网络切片的第二区域信息，和/或第二时间信息；
    处理单元，用于根据所述第二区域信息和/或第二时间信息为所述第一网络切片调度资源。
  28. 一种通信系统，其特征在于，包括：网管网元和数据分析设备，
    所述数据分析设备用于向所述网管网元发送第一网络切片的切片质量信息；
    所述网管网元用于执行上述权利要求1至12任一项所述的方法。
  29. 一种存储一个或多个计算机执行指令的计算机可读存储介质，其特征在于，当所述计算机执行指令被处理器执行时，所述处理器执行如上述权利要求1-12任一所述的方法，或者执行如上述权利要求13-19任一所述的方法，或者执行如上述权利要求20或21所述的方法。
  30. 一种存储一个或多个计算机执行指令的计算机程序产品，其特征在于，当所述计算机执行指令被所述处理器执行时，所述处理器执行如上述权利要求1-12任一所述的方法，或者执行如上述权利要求13-19任一所述的方法，或者执行如上述权利要求20或21所述的方法。
PCT/CN2019/124618 2019-01-08 2019-12-11 一种网络切片的资源调度的方法及设备 WO2020143384A1 (zh)

Priority Applications (6)

Application Number Priority Date Filing Date Title
EP19908635.6A EP3893439A4 (en) 2019-01-08 2019-12-11 METHOD OF PLANNING RESOURCES FOR NETWORK DISCS AND DEVICE
AU2019421312A AU2019421312B2 (en) 2019-01-08 2019-12-11 Resource scheduling method for network slice and device
KR1020217024156A KR20210104902A (ko) 2019-01-08 2019-12-11 네트워크 슬라이스를 위한 리소스 스케줄링 방법 및 디바이스
JP2021539647A JP7343590B2 (ja) 2019-01-08 2019-12-11 ネットワークスライスのためのリソーススケジューリング方法及びデバイス
KR1020237044211A KR20240005143A (ko) 2019-01-08 2019-12-11 네트워크 슬라이스를 위한 리소스 스케줄링 방법 및 디바이스
US17/369,510 US12089241B2 (en) 2019-01-08 2021-07-07 Resource scheduling method for network slice and device

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN201910017032 2019-01-08
CN201910017032.5 2019-01-08
CN201910070695.3 2019-01-23
CN201910070695.3A CN111416729B (zh) 2019-01-08 2019-01-23 一种网络切片的资源调度的方法及设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/369,510 Continuation US12089241B2 (en) 2019-01-08 2021-07-07 Resource scheduling method for network slice and device

Publications (1)

Publication Number Publication Date
WO2020143384A1 true WO2020143384A1 (zh) 2020-07-16

Family

ID=71492672

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/124618 WO2020143384A1 (zh) 2019-01-08 2019-12-11 一种网络切片的资源调度的方法及设备

Country Status (7)

Country Link
US (1) US12089241B2 (zh)
EP (1) EP3893439A4 (zh)
JP (1) JP7343590B2 (zh)
KR (2) KR20210104902A (zh)
CN (1) CN111416729B (zh)
AU (1) AU2019421312B2 (zh)
WO (1) WO2020143384A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115225478A (zh) * 2021-03-29 2022-10-21 网络通信与安全紫金山实验室 网络切片动态配置方法、装置、电子设备及存储介质

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2602734B (en) * 2019-06-11 2022-11-02 Samsung Electronics Co Ltd Improvements in and relating to the provision of data analytics in a telecommunication network
GB202012634D0 (en) * 2020-08-13 2020-09-30 Samsung Electronics Co Ltd NWDAF service experience analytics discrimination
CN114143217A (zh) * 2020-08-14 2022-03-04 中兴通讯股份有限公司 一种允许nssai确定方法、网络设备及存储介质
CN112272108B (zh) * 2020-10-14 2022-09-27 中国联合网络通信集团有限公司 一种调度方法和装置
CN114501623B (zh) * 2020-10-23 2024-05-28 中国电信股份有限公司 保障网络切片服务等级协议的方法和装置
CN114666233B (zh) * 2020-12-23 2023-08-22 上海华为技术有限公司 一种网络资源的请求方法及其相关设备
US20220279621A1 (en) * 2021-02-26 2022-09-01 Nokia Solutions And Networks Oy Emergency operations slice exchange between entities in mobile networks
US11785636B1 (en) * 2021-09-03 2023-10-10 T-Mobile Innovations Llc Wireless communication network access for wireless user equipment based on their wireless network slices
US11950138B2 (en) * 2021-11-17 2024-04-02 Dish Wireless L.L.C. Predictive user plane function (UPF) load balancing based on network data analytics
CN114125948B (zh) * 2021-11-25 2024-06-21 中国联合网络通信集团有限公司 一种最大业务资源门限确定方法、装置及存储介质
KR20230086980A (ko) * 2021-12-09 2023-06-16 삼성전자주식회사 5g nr 시스템에서 네트워크 슬라이스 간 무선 자원 최적화 방법 및 장치
EP4429323A1 (en) * 2021-12-09 2024-09-11 Samsung Electronics Co., Ltd. Method and apparatus for optimizing radio resources between network slices in 5g nr system
CN115623602B (zh) * 2022-12-19 2023-04-07 浪潮通信信息系统有限公司 资源重选方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107770794A (zh) * 2016-08-15 2018-03-06 华为技术有限公司 一种网络切片配置方法及装置
CN107889169A (zh) * 2016-09-29 2018-04-06 华为技术有限公司 网络切片的建立方法和装置
WO2018153289A1 (zh) * 2017-02-21 2018-08-30 华为技术有限公司 Sla分解方法、设备以及系统

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP6315588B2 (ja) * 2014-10-09 2018-04-25 国立大学法人東北大学 無線ネットワーク統合システムおよび無線ネットワーク統合方法
CN109041137B (zh) * 2016-01-16 2020-01-17 华为技术有限公司 一种切换的方法、基站及终端设备
US20170289791A1 (en) * 2016-04-05 2017-10-05 Electronics And Telecommunications Research Institute Communication method and apparatus using network slice
GB2553077B (en) 2016-04-27 2019-07-24 Toshiba Kk Radio resource slicing in a radio access network
CN107517488B (zh) * 2016-06-15 2020-10-23 华为技术有限公司 报文处理的方法及设备
CN109392096B (zh) * 2017-08-04 2020-11-03 华为技术有限公司 一种资源配置方法和装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107770794A (zh) * 2016-08-15 2018-03-06 华为技术有限公司 一种网络切片配置方法及装置
CN107889169A (zh) * 2016-09-29 2018-04-06 华为技术有限公司 网络切片的建立方法和装置
WO2018153289A1 (zh) * 2017-02-21 2018-08-30 华为技术有限公司 Sla分解方法、设备以及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
CHINA MOBILE ET AL.: "Solution for Key Issue 14: How to Ensure that Slice SLA is Guaranteed", SA WG2 MEETING #S2-129BIS, no. S2-1813213, 30 October 2018 (2018-10-30), XP051499702 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115225478A (zh) * 2021-03-29 2022-10-21 网络通信与安全紫金山实验室 网络切片动态配置方法、装置、电子设备及存储介质
CN115225478B (zh) * 2021-03-29 2023-07-28 网络通信与安全紫金山实验室 网络切片动态配置方法、装置、电子设备及存储介质

Also Published As

Publication number Publication date
CN111416729B (zh) 2021-09-21
EP3893439A1 (en) 2021-10-13
AU2019421312B2 (en) 2022-11-17
US20210337553A1 (en) 2021-10-28
JP2022517210A (ja) 2022-03-07
CN111416729A (zh) 2020-07-14
KR20240005143A (ko) 2024-01-11
EP3893439A4 (en) 2022-01-19
KR20210104902A (ko) 2021-08-25
US12089241B2 (en) 2024-09-10
JP7343590B2 (ja) 2023-09-12
AU2019421312A1 (en) 2021-08-05

Similar Documents

Publication Publication Date Title
WO2020143384A1 (zh) 一种网络切片的资源调度的方法及设备
CN110972193B (zh) 一种切片信息处理方法及装置
US11838802B2 (en) Slice information processing method and apparatus
CN111148165B (zh) 一种处理网络切片中用户接入的方法及装置
US11184289B2 (en) Systems and methods for managing network traffic with a network operator
WO2020057261A1 (zh) 通信方法和装置
EP3304826B1 (en) Method and apparatus for data analytics management
WO2020063963A1 (zh) 通信方法和相关设备
US20220103435A1 (en) Data processing method and apparatus
CN113518354B (zh) 一种确定策略的方法、装置及系统
US20220104127A1 (en) Method and apparatus for power management in a wireless communication system
CN104301250A (zh) 一种无线拥塞控制方法和设备
WO2021159314A1 (zh) 一种业务处理方法、装置以及系统
WO2021208920A1 (zh) 网络性能监控方法、装置及系统
WO2023056855A1 (zh) 一种通信方法、通信装置及通信系统
RU2787009C2 (ru) Способ связи и связанное устройство
EP4135387A1 (en) System and method for delivering quality of service
US20240251376A1 (en) Time-related network resource management
EP4432635A1 (en) Communication method and communication apparatus

Legal Events

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

Ref document number: 19908635

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021539647

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2019908635

Country of ref document: EP

Effective date: 20210707

ENP Entry into the national phase

Ref document number: 20217024156

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2019421312

Country of ref document: AU

Date of ref document: 20191211

Kind code of ref document: A