CN110830542B

CN110830542B - Method for obtaining network configuration information and related equipment

Info

Publication number: CN110830542B
Application number: CN201811161055.5A
Authority: CN
Inventors: 崇卫微; 吴晓波; 辛阳
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2018-08-14
Filing date: 2018-09-30
Publication date: 2023-01-13
Anticipated expiration: 2038-09-30
Also published as: CN110830542A

Abstract

The application provides a method for acquiring network configuration information and related equipment, wherein the method comprises the following steps: the method comprises the steps that a policy control network element sends request information to a data analysis network element, wherein the request information is used for requesting network configuration information corresponding to each slice network list in at least one slice network list, and each slice network list comprises one or more slice networks; and the policy control network element receives the network configuration information corresponding to each slice network list sent by the data analysis network element. In the above technical solution, the policy control network element may send the service quality requirement of the slice network list to be acquired to the data analysis network element. The data analysis network element may send the corresponding network configuration information to the policy control network element according to the requirement of the policy control network element. Therefore, the technical scheme provides an effective method for acquiring the network configuration information.

Description

Method for obtaining network configuration information and related equipment

The present application claims priority of chinese patent application having application number 201810923770.1, entitled "method and related apparatus for obtaining network configuration information" filed in 2018, 8, month 14, the entire contents of which are incorporated herein by reference.

Technical Field

The present application relates to the field of communications technologies, and in particular, to a method for acquiring network configuration information and a related device.

Background

With the continuous emergence of diverse communication services, there is a significant difference in the demands of different communication services on network performance. Fifth generation mobile communications (the 5) ^th Generation, 5G) system introducesThe concept of a sliced network. A slicing network may provide a customized network for an operator. An operator can meet the requirements of the user on the differentiation of functions such as priority, charging, policy control, security, mobility and the like and the requirements of the user on the differentiation of performances such as time delay, reliability, speed and the like through the slicing network. The operator can also utilize the slice network to reduce the investment cost of network operation and enrich the network operation mode. However, an effective scheme for acquiring the network configuration information corresponding to the slice network is not proposed in the industry at present.

Disclosure of Invention

The application provides a method for acquiring network configuration information and related equipment, and can provide an effective method for acquiring the network configuration information.

In a first aspect, an embodiment of the present application provides a method for acquiring network configuration information, where the method includes: the method comprises the steps that a policy control network element sends request information to a data analysis network element, wherein the request information is used for requesting network configuration information corresponding to each slice network list in at least one slice network list, and each slice network list comprises one or more slice networks; and the policy control network element receives the network configuration information corresponding to each slice network list sent by the data analysis network element. In the above technical solution, the policy control network element may send the service quality requirement of the slice network list to be acquired to the data analysis network element. The data analysis network element may send the corresponding network configuration information to the policy control network element according to the requirement of the policy control network element. Therefore, the technical scheme provides an effective method for acquiring the network configuration information.

With reference to the first aspect, in a possible implementation manner of the first aspect, the request information includes an identifier of a slice network included in each slice network list. In the above technical solution, the policy control network element may request to acquire the network configuration information through the identifier of the slice network in the slice network list. The technical scheme can reduce the content carried in the request information, thereby shortening the length of the request information and improving the communication efficiency.

With reference to the first aspect, in a possible implementation manner of the first aspect, the request information further includes a quality of service requirement of the network list per slice. Based on the above technical solution, the policy control network element may directly indicate which service quality requirements the network configuration information that needs to be acquired needs to meet. In the technical scheme, the data analysis network element does not need to acquire and store the corresponding relation between the slice network list and the service quality requirement in advance, so that the occupation of the storage space of the data analysis network element can be reduced, and in addition, the corresponding relation between the slice network list and the service quality requirement does not need to be transmitted by additional information.

With reference to the first aspect, in a possible implementation manner of the first aspect, the quality of service requirement of each slice network list includes a quality of service requirement corresponding to each slice network of the one or more slice networks. In the above technical solution, the service quality requirement of each slice network list may include a service quality requirement corresponding to one or more slice networks. Thus, the policy control network element can request the service quality requirement corresponding to one or more slice networks at one time. Therefore, the number of times of sending the request information can be reduced, and the signaling overhead is saved.

With reference to the first aspect, in a possible implementation manner of the first aspect, the service quality requirement corresponding to each slice network includes a service quality requirement of one or more services in each slice network. In the above technical solution, the qos requirement corresponding to each slice network may include qos requirements of one or more services. So that the policy control network element can request the quality of service requirements of one or more services at a time. Therefore, the number of times of sending the request information can be reduced, and the signaling overhead is saved.

With reference to the first aspect, in a possible implementation manner of the first aspect, the service quality requirement corresponding to each slice network includes a service quality requirement corresponding to at least one user type in each slice network. In the above technical solution, the qos requirement corresponding to each slice network may include qos requirements corresponding to one or more user types. Thus, the policy control network element can request the service quality requirement corresponding to one or more user types at one time. Therefore, the number of times of sending the request information can be reduced, and the signaling overhead is saved.

With reference to the first aspect, in a possible implementation manner of the first aspect, the method further includes: the policy control network element determines the service quality requirement of each slice network list in the at least one slice network list according to the slice network priority information and/or the service priority information and/or the priority information of the user type. Based on the above technical solution, the policy control network element may determine a slice network list in which network configuration information needs to be acquired according to the slice network priority information and/or the service priority information and/or the priority information of the user type.

With reference to the first aspect, in a possible implementation manner of the first aspect, the method further includes: the policy control network element determines the identity of the one or more sliced networks included in each sliced network list according to the sliced network priority information. Based on the above technical solution, the policy control network element may determine a slice network list in which network configuration information needs to be acquired according to the slice network priority information.

With reference to the first aspect, in a possible implementation manner of the first aspect, the method further includes: the strategy control network element sends slice network priority information and/or service priority information and/or user type priority information to the data analysis network element. Based on the above technical solution, the policy control network element may obtain the service quality requirement network configuration information of each slice network list provided by the data analysis network element according to the slice network priority information and/or the service priority information and/or the priority information of the user type.

With reference to the first aspect, in a possible implementation manner of the first aspect, the method further includes: and the strategy control network element sends the service quality requirements of all the slice networks to the data analysis network element. Based on the above technical solution, the data analysis network element may determine the service quality requirements of the sliced network list based on the service quality requirements of all sliced networks and the sliced network identifiers included in the sliced network list.

With reference to the first aspect, in a possible implementation manner of the first aspect, the method further includes: and the policy control network element sends the network configuration information corresponding to the first slice network list to the network management network element, wherein the first slice network list is contained in the at least one slice network list. In the foregoing technical solution, the policy control network element may determine the first sliced network list from the at least one sliced network list, and send the network configuration information corresponding to the received first sliced network list to the network configuration information of the network management network element. Therefore, the strategy control network element can determine the slice network which needs to be guaranteed to operate according to the current network resource state.

With reference to the first aspect, in a possible implementation manner of the first aspect, the method further includes: and the policy control network element determines the network configuration information corresponding to the first slice network list from the network configuration information corresponding to each slice network list sent by the data analysis network element according to the slice network priority information and/or the service priority information and/or the priority information of the user type. Based on the above technical solution, the policy control network element may determine the network configuration information that needs to be sent to the network management network element according to the slice network priority information and/or the service priority information and/or the priority information of the user type.

With reference to the first aspect, in a possible implementation manner of the first aspect, the method further includes: and the policy control network element receives notification information sent by the network management network element, where the notification information is used to notify the policy control network element that the network management network element cannot perform network configuration according to the network configuration information corresponding to the first slice network list. In the above technical solution, the policy control network element may learn, according to the notification message, that the network management network element cannot perform network configuration according to the network configuration information corresponding to the first slice network list, so that the policy control network element may perform subsequent operations conveniently.

With reference to the first aspect, in a possible implementation manner of the first aspect, the method further includes: the strategy control network element determines network configuration information corresponding to the second slice network list according to the notification information; and the policy control network element sends the network configuration information corresponding to the second slice network list to the network management network element. In the foregoing technical solution, the policy control network element may determine, again, the network configuration information corresponding to another slice network list sent to the network management network element, when it is known that the network management network element cannot perform network configuration according to the network configuration information corresponding to the first slice network list.

With reference to the first aspect, in a possible implementation manner of the first aspect, the determining, by the policy control network element according to the notification information, network configuration information corresponding to the second slice network list by the policy control network element includes: and the policy control network element determines, in the case of receiving the notification information, network configuration information corresponding to the second sliced network list from the received network configuration information corresponding to each sliced network list sent by the data analysis network element, where the at least one sliced network list includes the second sliced network list. In the above technical solution, the policy control network element may, upon learning that the network management network element is unable to perform network configuration according to the network configuration information corresponding to the first sliced network list, re-send, from the received network configuration information, network configuration information corresponding to another sliced network list that needs to be sent to the network management network element.

With reference to the first aspect, in a possible implementation manner of the first aspect, the determining, from the received network configuration information corresponding to each sliced network list sent by the data analysis network element, network configuration information corresponding to the second sliced network list includes: and the policy control network element determines the network configuration information corresponding to the second slice network list from the received network configuration information corresponding to each slice network list sent by the data analysis network element according to the slice network priority information and/or the service priority information and/or the priority information of the user type. Based on the above technical solution, the policy control network element may determine the network configuration information that needs to be sent to the network management network element according to the slice network priority information and/or the service priority information and/or the priority information of the user type.

With reference to the first aspect, in a possible implementation manner of the first aspect, the determining, by the policy control network element according to the notification information, network configuration information corresponding to the second slice network list includes: the policy control network element sends request information for requesting to acquire network configuration information corresponding to the second slice network list to the data analysis network element under the condition that the notification information is received; and the policy control network element receives the network configuration information corresponding to the second slice network list sent by the data analysis network element. In the above technical solution, the policy control network element may, upon learning that the network management network element is unable to perform network configuration according to the network configuration information corresponding to the first sliced network list, request, from the data analysis network element, network configuration information corresponding to another sliced network list that needs to be sent to the network management network element again.

With reference to the first aspect, in a possible implementation manner of the first aspect, the notification information further includes reason information, where the reason information is used to indicate a reason why the network management network element cannot perform network configuration. Therefore, the policy control network element can reselect the network configuration information corresponding to the slice network list which needs to be sent to the network management network element according to the reason that the network management network element cannot perform network configuration.

With reference to the first aspect, in a possible implementation manner of the first aspect, the notification message further includes a network parameter measurement value corresponding to the first slice network list. In this way, the policy control network element may reselect the network configuration information corresponding to the slice network list that needs to be sent to the network management network element according to the network parameter measurement value corresponding to the first slice network list.

With reference to the first aspect, in a possible implementation manner of the first aspect, the slice network is one of a network slice, a network slice instance, and a network slice subinstance.

With reference to the first aspect, in a possible implementation manner of the first aspect, the service quality requirement corresponding to each slice network includes a service quality requirement of at least one service in each slice network, and the service quality requirement of the service is a user proportion requirement that meets a single-user service quality requirement of the service.

In a second aspect, an embodiment of the present application provides a method for acquiring network configuration information, where the method includes: the data analysis network element determines network configuration information corresponding to each slice network list in at least one slice network list; and the data analysis network element sends the network configuration information corresponding to each slice network list to a policy control network element. Therefore, the above technical solution provides an effective method for notifying network configuration information.

With reference to the second aspect, in a possible implementation manner of the second aspect, before the determining, by the data analysis network element, network configuration information corresponding to each sliced network list in at least one sliced network list, the method further includes: the data analysis network element receives request information sent by the policy control network element, wherein the request information is used for requesting network configuration information corresponding to each slice network list; the data analysis network element determines network configuration information corresponding to each slice network list in at least one slice network list, and the network configuration information comprises: and the data analysis network element determines the network configuration information corresponding to each slice network list in the at least one slice network list according to the request information. In the above technical solution, the policy control network element may send the service quality requirement of the slice network list to be acquired to the data analysis network element. The data analysis network element may send the corresponding network configuration information to the policy control network element according to the requirement of the policy control network element. Therefore, the technical scheme provides an effective method for acquiring the network configuration information.

With reference to the second aspect, in a possible implementation manner of the second aspect, the request information includes an identification of the slice networks included in each slice network list. The technical scheme can reduce the content carried in the request information, thereby shortening the length of the request information and improving the communication efficiency.

With reference to the second aspect, in a possible implementation manner of the second aspect, the request information further includes a quality of service requirement of the per-slice network list. Based on the above technical solution, the policy control network element may directly indicate which service quality requirements the network configuration information required to be obtained needs to meet. In the technical scheme, the data analysis network element does not need to acquire and store the corresponding relation between the slice network list and the service quality requirement in advance, so that the occupation of the storage space of the data analysis network element can be reduced, and in addition, the corresponding relation between the slice network list and the service quality requirement does not need to be transmitted by additional information.

With reference to the second aspect, in a possible implementation manner of the second aspect, the data analysis network element determines network configuration information corresponding to each slice network list in at least one slice network list, and the method includes: and the data analysis network element determines the network configuration information corresponding to each slice network list in the at least one slice network list according to the slice network priority information and/or the service priority information and/or the priority information of the user type.

With reference to the second aspect, in a possible implementation manner of the second aspect, the method further includes: and the data analysis network element receives the slice network priority information and/or service priority information and/or user type priority information sent by the policy control network element.

With reference to the second aspect, in a possible implementation manner of the second aspect, each sliced network list includes one or more sliced networks, and the quality of service requirement of each sliced network list includes a quality of service requirement corresponding to each sliced network of the one or more sliced networks.

With reference to the second aspect, in a possible implementation manner of the second aspect, the quality of service requirement corresponding to each slice network includes a quality of service requirement of one or more services in each slice network.

With reference to the second aspect, in a possible implementation manner of the second aspect, the quality of service requirement corresponding to each slice network includes a quality of service requirement corresponding to at least one user type in each slice network.

With reference to the second aspect, in a possible implementation manner of the second aspect, the determining, by the data analysis network element, network configuration information corresponding to each slice network list in at least one slice network list includes: the data analysis network element acquires historical network configuration information corresponding to each slice network in each slice network list; the data analysis network element acquires the historical service quality of each slice network in each slice network list; the data analysis network element determines network configuration information corresponding to each slice network according to the historical network configuration information corresponding to each slice network, the historical service quality of each slice network and the service quality requirement of each slice network; and the data analysis network element determines the network configuration information corresponding to each slice network list in the at least one slice network list according to the network configuration information of each slice network.

With reference to the second aspect, in a possible implementation manner of the second aspect, the method further includes: receiving request information which is sent by a policy control network element and used for requesting network configuration information corresponding to a second sliced network list, wherein the request information used for requesting the network configuration information corresponding to the second sliced network list comprises the service quality requirement of the second sliced network list; and sending the network configuration information corresponding to the second slice network list to the policy control network element.

With reference to the second aspect, in a possible implementation manner of the second aspect, the historical quality of service of each slice network includes historical quality of service of one or more services of each slice network.

With reference to the second aspect, in a possible implementation manner of the second aspect, the historical quality of service of each slicing network includes historical quality of service of at least one user type of each slicing network.

With reference to the second aspect, in a possible implementation manner of the second aspect, the slice network is one of a network slice, a network slice instance, and a network slice sub-instance.

With reference to the second aspect, in a possible implementation manner of the second aspect, the service quality requirement corresponding to each slice network requires a service quality requirement of at least one service in each slice network, and the service quality requirement of the service is a user ratio that meets a single-user service quality requirement of the service.

In a third aspect, an embodiment of the present application provides a method for acquiring network configuration information, where the method includes: the network management network element acquires network configuration information corresponding to the first slice network list; and the network management network element performs network configuration on at least one slice network included in the first slice network list according to the network configuration information corresponding to the first slice network list.

With reference to the third aspect, in a possible implementation manner of the third aspect, the acquiring, by the network management element, network configuration information corresponding to the first slice network list includes: the network management network element receives network configuration information corresponding to each slice network list in at least one slice network list sent by a policy control network element, wherein the at least one slice network list comprises the first slice network list; the network management network element determines the network configuration information corresponding to the first slice network list from the received network configuration information corresponding to each slice network list.

With reference to the third aspect, in a possible implementation manner of the third aspect, the determining, by the network management network element, the network configuration information corresponding to the first sliced network list from the received network configuration information corresponding to each sliced network list includes: and the network management network element determines the network configuration information corresponding to the first slice network list from the network configuration information corresponding to each slice network list according to the slice network priority information and/or the service priority information and/or the priority information of the user type.

With reference to the third aspect, in a possible implementation manner of the third aspect, the acquiring, by the network management network element, network configuration information corresponding to the first slice network list includes: and the network management network element receives the network configuration information corresponding to the first slice network list sent by the policy control network element.

With reference to the third aspect, in a possible implementation manner of the third aspect, before the network management element receives the network configuration information corresponding to the first slice network list sent by the policy control element, the method further includes: and the network management network element sends a request message for requesting the network configuration information corresponding to the first slice network list to the policy control network element.

With reference to the third aspect, in a possible implementation manner of the third aspect, the method further includes: and the network management network element sends notification information to the policy control network element, where the notification information is used to notify the policy control network element that the network management network element cannot perform network configuration according to the network configuration information corresponding to the first slice network list.

With reference to the third aspect, in a possible implementation manner of the third aspect, the method further includes: and the network management network element acquires network configuration information corresponding to the second slice network list.

With reference to the third aspect, in a possible implementation manner of the third aspect, the notification information further includes reason information, where the reason information is used to indicate a reason why the network management network element cannot perform network configuration.

With reference to the third aspect, in a possible implementation manner of the third aspect, the notification message further includes a network parameter measurement value corresponding to the first slice network list.

With reference to the third aspect, in a possible implementation manner of the third aspect, the slice network is one of a network slice, a network slice instance, and a network slice subinstance.

In a fourth aspect, an embodiment of the present application provides a network device, where the network device includes a unit configured to perform the method described in the first aspect or any one of the possible implementation manners of the first aspect.

In a fifth aspect, an embodiment of the present application provides a network device, where the network device includes a unit configured to execute the method described in the second aspect or any possible implementation manner of the second aspect.

In a sixth aspect, an embodiment of the present application provides a network device, where the network device includes a unit configured to execute the method described in the third aspect or any one of the possible implementation manners of the third aspect.

In a seventh aspect, an embodiment of the present application provides a storage medium, where the storage medium stores instructions for implementing the method described in the first aspect or any one of the possible implementation manners of the first aspect.

In an eighth aspect, the present application provides a storage medium storing instructions for implementing the method according to the second aspect or any one of the possible implementation manners of the second aspect.

In a ninth aspect, an embodiment of the present application provides a storage medium, where the storage medium stores instructions for implementing the method described in the third aspect or any one of the possible implementation manners of the third aspect.

In a tenth aspect, the present application provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of the first aspect or any one of the possible implementations of the first aspect.

In an eleventh aspect, the present application provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of the second aspect or any of the possible implementations of the second aspect.

In a twelfth aspect, the present application provides a computer program product comprising instructions that, when run on a computer, cause the computer to perform the method according to any one of the possible implementation manners of the third aspect or the third aspect.

In a thirteenth aspect, the present application provides a chip capable of implementing the method according to the first aspect or any one of the possible implementation manners of the first aspect.

In a fourteenth aspect, the present application provides a chip capable of implementing the method according to the second aspect or any one of the possible implementation manners of the second aspect.

In a fifteenth aspect, the present application provides a chip, which is capable of implementing the method according to any one of the possible implementation manners of the third aspect or the third aspect.

Drawings

Fig. 1 is a schematic diagram of a communication system architecture according to an embodiment of the present application.

Fig. 2 is a schematic flow chart of a method for acquiring network configuration information according to an embodiment of the present application.

Fig. 3 is a schematic flowchart of another method for acquiring network configuration information according to an embodiment of the present application.

Fig. 4 is a schematic flow chart of a method for acquiring network configuration information according to an embodiment of the present application.

Fig. 5 is a schematic flow chart of a method for acquiring network configuration information according to an embodiment of the present application.

Fig. 6 is a block diagram of a network device according to an embodiment of the present application.

Fig. 7 is a block diagram of a network device according to an embodiment of the present application.

Fig. 8 is a block diagram of a network device according to an embodiment of the present application.

Fig. 9 is a block diagram of a network device according to an embodiment of the present application.

Fig. 10 is a block diagram of a network device according to an embodiment of the present application.

Fig. 11 is a block diagram of a network device according to an embodiment of the present application.

Detailed Description

The technical solution in the present application will be described below with reference to the accompanying drawings.

In the present application, "at least one" means one or more, "a plurality" means two or more. "and/or" describes the association relationship of the associated object, indicating that there may be three relationships, for example, a and/or B, which may indicate: a alone, A and B together, and B alone, wherein A and B may be singular or plural. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. "at least one of the following" or similar expressions refer to any combination of these items, including any combination of the singular or plural items. For example, at least one (one) of a, b, or c, may represent: a. b, c, a-b, a-c, b-c, or a-b-c, wherein a, b, c can be single or multiple. In addition, in the embodiments of the present application, the words "first", "second", and the like do not limit the number and the execution order.

It is noted that, in the present application, words such as "exemplary" or "for example" are used to mean exemplary, illustrative, or descriptive. Any embodiment or design described herein as "exemplary" or "e.g.," is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present concepts related in a concrete fashion.

The technical scheme of the embodiment of the application can be applied to the fifth generation (5) ^th generation, 5G), new Radio (NR) or future communication networks, etc.

First, in order to facilitate understanding of the embodiments of the present application, some technical terms related to the embodiments of the present application are described.

The slice network referred to in the embodiments of the present application may be one of a network slice, a network slice instance, and a network slice sub-instance.

Network Slice (NS), also referred to as slice for short, refers to customizing different logical networks according to service requirements of services of different tenants (tenants) on a physical or virtual network infrastructure. The network slice may be a complete end-to-end network including the terminal device, the access network, the transmission network, the core network and the service server, or may be a complete end-to-end network including only the core network but assisted by the terminal device, the access network, the transmission network and the service server, which is capable of providing a complete communication service and has a certain network capability, and the network slice may be a communication resource that ensures that a bearer service or a service can meet a service level agreement requirement, or may be considered as a combination of a network function and a communication resource that is required to complete a certain communication service or certain communication services. A network slice is identified by single network slice selection assistance information (S-NSSAI). The S-NSSAI is composed of a slice/service type (SST) and a slice differentiation identifier (SD). Wherein SST and SD may be defined by a standard or customized by an operator; SD is optional information that supplements SST to distinguish multiple network slices of the same SST, such as may be used to characterize the affiliation of a network slice.

A Network Slice Instance (NSI), which may also be referred to as a slice instance network, is an instantiated network created by an operator on an infrastructure according to a network slice template, and is formed by aggregating different network functional entities and physical resources. Logical isolation between different network slice instances. One network slice may instantiate one or more NSIs, each NSI identified by a network slice instance identifier (NSI ID). That is, one S-NSSAI corresponds to one or more NSI IDs.

A Network Slice Subinstance (NSSI), which may also be referred to as a slice subinstance network, a set of network functional network elements and arrangement and configuration of resources of the functional network elements, are used to form a local logical network, and the network slice subinstance is introduced to facilitate management of one network slice instantiation, for example, a network slice is divided into two network slice subinstances according to a core network element and an access network element, and the arrangement and configuration are performed on the core network resource and the network resource, respectively, so that management is facilitated.

Service Level Agreement (SLA): is a contract between a service provider and its customers to record application services provided by the service provider and to define fulfillment criteria that the service provider is obligated to meet. The SLA may establish customer expectations for the service provider in terms of fulfillment and quality. The SLA may include a series of qualitative or quantitative rules for availability, performance index baselines, reliability, response time, and the like.

Fig. 1 is a schematic diagram of a communication system architecture according to an embodiment of the present application. The communication system includes a network data analysis function (NWDAF) network element, AN Application Function (AF) network element, a Core Network (CN) network element, a radio access network (RAN/AN) network element, a Transport Network (TN), AN Operation Administration and Maintenance (OAM) network element, a terminal device, and a network open capability (NEF) network element. In fig. 1, the AF network element including AF1 and AF2 is taken as an example for explanation.

The core network elements may include Policy Control Function (PCF) elements, session Management Function (SMF) elements, access and mobility management Function (AMF) elements, user Plane Function (UPF) elements, and network storage Function (NRF) elements. The NWDAF network element may be deployed inside a core network, that is, the NWDAF also belongs to a core network element, or may not be deployed inside the core network, which is not specifically limited in this embodiment of the present application. In addition, the NWDAF may directly communicate with a network element that needs to communicate through the service interface, for example, the network data analysis device may communicate with a network element such as PCF, SMF, AMF, UPF, NRF, and RAN through the service interface by invoking a different service of the service interface. It is to be understood that in the communication system shown in fig. 1, the functions and interfaces of the network elements are only exemplary, and not all the functions of the network elements are necessary when the network elements are applied to the embodiments of the present application. In addition, the present application does not exclude that network elements communicate with each other based on a point-to-point interface, for example, an NWDAF is connected to a PCF network element via an N23 interface. The PCF is connected with the AF network element through an N5 interface, connected with the SMF network element through an N7 interface and connected with the AMF network element through an N15 interface, and can make dynamic QoS strategies and distribute the corresponding strategies to the SMF network element, the AMF network element and other network elements. And the UPF is connected with the SMF network element through an N4 interface and is connected with the RAN network element through an N3 interface. The AN is connected with the AMF network element through AN N2 interface. And the UE is connected with the AMF network element through an N1 interface. Only a portion of the interfaces listed above are shown in fig. 1.

Terminal devices include, but are not limited to: user Equipment (UE), a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile terminal, a user terminal, a wireless communication device, a user agent, a user equipment, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication functionality, a computing device, a processing device connected to a wireless modem, a vehicle mounted device, a wearable device, a terminal device in the internet of things, a home appliance, a virtual reality device, a terminal device in a future 5G network, or a terminal device in a future evolved Public Land Mobile Network (PLMN), and the like.

A tenant is a customer that leases a communications carrier network and utilizes the network to provide one or more services to its users, which may be from a vertical industry tenant, or from a tenant in the OTT industry or other third party tenant. In addition, the operator network leased by the tenant may be a network slice, or a slice network instance, a slice network subinstance in a slice network, or other types of networks, which is not specifically limited in this application.

The application function network element is a server side that provides a certain type of service to users and may therefore also be referred to as an application server or a service server.

The access network element may be a network element in communication with the terminal device. An access network element may provide communication coverage for a particular geographic area and may communicate with terminal devices located within that coverage area (cell). An access network element may communicate with any number of terminal devices. A plurality of air interfaces may be connected between the access network element and the terminal device, for example, two air interfaces exist between the access network element and the terminal device, and are respectively used for transmitting the data stream a and the data stream B. The network element of the access network may support communication protocols of different systems, or may support different communication modes. For example, the access network element may be a 5G base station or a next generation base station (gNB), an evolved node B (eNodeB), or a wireless fidelity access point (WiFi AP), or a worldwide interoperability for microwave access base station (WiMAX BS), or a wireless controller in a Cloud Radio Access Network (CRAN), or the network device may be an access network device in a future evolved PLMN, and the like.

The PCF network element has the function of policy control decision and provides a policy for the network. The AMF network element is used for mobility management, lawful interception, or access authorization, authentication and the like. The SMF network element is used to implement session and bearer management, address assignment, etc. The user plane functional network element is used for routing forwarding of user plane data, threshold control, flow monitoring, verification and other functions. The network storage function network element is used for providing a service discovery function or a network element discovery function, and maintaining the characteristics of the network element and the functions of services supported by the network element. The transmission network element has a function of transmitting network data, and for example, the transmission network element may be a router repeater.

A network operation, maintenance and management (OAM) network element or an NSMF network element has a network management function, including deploying and setting a network (such as a network slice or a network slice instance), measuring statistics of performance parameters at a device level or a network level, fault monitoring, fault reporting, fault location, fault repair, and the like.

The NWDAF has data statistics and analysis functions, and can be used for collecting and analyzing related data from a network element, a third-party service server, a terminal device or a network management system, and providing a data analysis result to the network element, the third-party service server, the terminal device or the network management system based on the related data, wherein the analysis result can assist the network in selecting service quality parameters of a service, or assist the network in executing traffic routing, or assist the network in selecting a background traffic transmission strategy, and the like. In embodiments of the present application, the data analysis device may be further configured to provide analysis results of a network (e.g., a network slice or network slice instance) so that the network performs deployment of the network (e.g., a network slice or network slice instance) or adjusts network resources according to the analysis results.

The network capability opening network element NEF has a function of providing or opening a function of the operator network to an external server or an external device, and functions as an intermediary for external communication within and outside the network. For example, when a third-party untrusted service server needs to communicate with the inside of a network, forwarding and processing operations of network elements through network capability opening are needed. Of course, if the service server inside the network or the third-party trusted service server communicates with the inside of the network, the network element does not need to be opened through the network capability.

In the embodiment of the present application, all or part of the network elements of the access network device and the core network may belong to a third generation partnership project (3 GPP) network or a non-3 GPP network, for example: an enterprise intranet. All or part of the network elements of the core network may be physical network elements, or may be virtualized network elements, which is not limited herein.

The network applied by the resource management method provided in the embodiment of the present application may be a network slice (for example, a slice in a 5G network), or a network slice instance in the network slice (for example, a network slice instance in the 5G network slice), or a 4G network corresponding to a Dedicated Core Network (DCN), or a network with other granularity, such as a network distinguished by a PLMN identifier, and the like, which is not specifically limited in the embodiment of the present application.

The data analysis network element in this application refers to a network element capable of providing a data analysis function, and the data analysis function related to this application may be deployed on a network data analysis function network element (NWDAF), or may be deployed on other network elements, that is, the data analysis network element in this application may include, but is not limited to, NWDAF. The data analysis network element may be a network element having the data analysis function according to the present invention on the core network control plane, or may be a network element having the data analysis function according to the present invention on the network management plane.

The policy control network element in this application refers to a network element capable of providing a policy control function, and the policy control function related to this application may be deployed on a policy control function network element (PCF), or may be deployed on another network element, that is, the policy control network element in this application may include, but is not limited to, a PCF.

The network management element in this application refers to an element capable of providing a network operation management and maintenance function, and the network operation management and maintenance function related to this application may be deployed on an Operation Administration and Maintenance (OAM) element or a Network Slice Management Function (NSMF) element, or may be deployed on other elements, for example, the network management element in this application may include, but is not limited to, an OAM and an NSMF.

In addition, the data analysis function and other functions may be merged and deployed on the same network element, for example, the data analysis function and the policy control function may be merged and deployed, and then the data analysis network element and the policy control network element are physically the same entity. Similarly, the data analysis function and the network management function may also be merged and deployed on the same network element, and then the data analysis network element and the network management network element are physically the same entity.

In addition, whether the policy control function and the network management function related to the present invention are merged and deployed is not limited in the present application, and when the policy control function and the network management function are merged and deployed, the policy control network element and the network management network element are actually the same network element, for example, the same network management network element, or the same policy control network element.

In addition, the quality of service referred to in the embodiments of the present application may also be referred to as a service experience.

And 201, the policy control network element sends request information to the data analysis network element, wherein the request information is used for requesting the network configuration information corresponding to the slice network list. Correspondingly, the data analysis network element receives the request information sent by the policy control network element. The list of slicing networks may include one or more slicing networks.

In some embodiments, the request information may include an identification of one or more slicing networks included in a slicing network list. When the slicing network list contains a slicing network, the request information comprises an identifier of the slicing network; when a plurality of slicing networks are included in the slicing network list, the request information includes an identification of the plurality of slicing networks. The identity of the slice network may be S-NSSAI, NSI ID, NSSI ID, etc. After receiving the identifier of the slice network included in the slice network list, the data analysis network element may determine the service quality requirement of the slice network list according to the correspondence between the slice network list and the service quality requirement. The correspondence between the slice network list and the service quality requirement may be pre-configured in the data analysis network element, or may be sent to the data analysis network element by other network devices or tenants. For example, the policy control network element may send the service quality requirements corresponding to all slice networks to the data analysis network element, and after the data analysis network element receives the request message sent by the policy control network element, the service quality requirements of each slice network in the slice network list included in the request message may be queried or mapped, and the service quality requirements of each slice network constitute the service quality requirements of the slice network list.

For example, table 1 is a slice network list and a corresponding relationship of service quality requirements.

TABLE 1

Slicing network identification	Quality of service requirements
		Slicing network 1	MOS>User ratio of 3>95％
Slicing network 2	MOS>User ratio of 3>90％
		Slicing network 3	MOS>User ratio of 3>85％

The list of slicing networks shown in table 1 includes three slicing networks, which are slicing network 1, slicing network 2, and slicing network 3. A quality of service requirement of a corresponding one of the three sliced networks. Specifically, the service quality requirement of the slice network may be a user satisfaction requirement of a service in the slice network, where the user satisfaction of the service refers to a proportion of users that satisfy the single-user service quality requirement of the service. As shown in table 1, the service quality requirement corresponding to the slice network 1 is that the user proportion of voice service Mean Opinion Score (MOS) greater than 3 is greater than 95%; the service quality requirement corresponding to the slicing network 2 is that the proportion of users with the voice service MOS larger than 3 is larger than 90%; the service quality requirement corresponding to the slice network 3 is that the proportion of users with voice service MOS greater than 3 is greater than 85%. It will be appreciated that a MOS greater than 3 points is one example of a single-user quality of service requirement for voice traffic, i.e. for each single user a MOS greater than 3 points for voice traffic is required. A proportion of users with MOS greater than 3 greater than 95% means that the MOS of voice traffic for more than 95% of the users in the sliced network are greater than 3 points.

In addition to the user satisfaction requirements of the services in the sliced network of the above example, the quality of service requirements of the sliced network may be inclusive or other requirements. For example, the service quality requirement of the slice network may further include a requirement of the number of users in the slice network, where the number of users in the slice network refers to the number of registered users or the number of online users in the slice.

The slice network list in the request message sent by the policy control network element may include the identifiers of slice networks 1 to 3. After the data analysis network element obtains the request information, the service quality requirement corresponding to each slice network can be determined according to the corresponding relation in table 1.

Further, in other embodiments, the request information may include service identifiers corresponding to all or part of services for each slice network identifier, in addition to identifiers of slice networks included in one slice network list. After receiving the identifier of the slice network and the service identifier included in the slice network list, the data analysis network element may determine the service quality requirement of the slice network list according to the correspondence between the slice network list and the service quality requirement. The correspondence between the slice network list and the service quality requirement may be pre-configured in the data analysis network element, or may be sent to the data analysis network element by other network devices or tenants. Before sending the request message, the policy control network element determines the slice network identifier and the service identifier contained in the slice network list according to the slice network priority information and the service priority information.

In some embodiments, the request information may also include a quality of service requirement for a sliced network list.

In some embodiments, the list of slicing networks may include only one slicing network. In this case, the quality of service requirement of the slice network list includes the quality of service requirement corresponding to the one slice network.

In other embodiments, the list of slicing networks may include a plurality of slicing networks. In this case, the quality of service requirement of the sliced network list includes a quality of service requirement corresponding to each of the plurality of sliced networks.

The network configuration information corresponding to the sliced network list can meet the service quality requirement of the sliced network list. Specifically, when the network management device performs network configuration on each slice network in the slice network list according to the network configuration information corresponding to each slice network, the service in each slice network can meet the service quality requirement corresponding to each slice network. In other words, if the qos requirements of the slice network list include a qos requirement corresponding to a slice network, the network configuration information corresponding to the slice network list can satisfy the qos requirement corresponding to the slice network. Specifically, when the network management device performs network configuration according to the network configuration information corresponding to the slice network list, the service in the slice network can meet the service quality requirement corresponding to the slice network; if the service quality requirement of the slice network list includes a service quality requirement corresponding to each slice network in the plurality of slice networks, the network configuration information corresponding to the slice network list can satisfy the service quality requirement corresponding to each slice network. Specifically, when the network management device performs network configuration according to the network configuration information corresponding to the slice network list, each slice in the slice network list is a service in the network and can satisfy the service quality requirement corresponding to each slice network.

In some embodiments, the qos requirements of the sliced network list may include a plurality of qos requirements, and each qos requirement of the plurality of qos requirements is a qos requirement corresponding to one sliced network. In this case, the quality of service requirement of the slice network list may include an identifier of the slice network in addition to the quality of service requirement. In other words, the qos requirements of the sliced network list may include identifiers of N sliced networks and N qos requirements, where the identifiers of N sliced networks correspond to the N qos requirements one to one, and N is a positive integer greater than or equal to 1. One of the qos requirements of the sliced network list is the qos requirement corresponding to the corresponding sliced network. For example, table 1 above is an illustration of the quality of service requirements for the sliced network list as well.

Further, the qos requirements of the three slice networks shown in table 1 are qos requirements of the same service (i.e., voice service). In some embodiments, the traffic corresponding to different slicing networks in the slicing network list may be different. For example, in the service quality requirements of the slice network list, the service corresponding to one slice network is a voice service, and the service corresponding to another slice network is a data service.

Further, even if different slice networks provide the same service, the single-user quality of service requirements for the service may differ. For example, the quality of service requirements of a single user of voice services corresponding to three different slice networks in table 1 may also be different, which may be determined by negotiation between tenants of the slice networks and the operator network. For example, the single user quality of service requirement for voice traffic in slice network 1 is MOS >3, while the single user quality of service requirement for voice traffic in slice network 2 is MOS >4.

In some embodiments, the quality of service requirement for each of the sliced networks comprises a quality of service requirement for at least one service in each of the sliced networks.

If the qos requirement corresponding to each slice network only includes the qos requirement of one service in each slice network, the qos requirement corresponding to each slice network may include an identifier of the slice network and the qos requirement. The service quality requirement corresponding to each slice network may further include service identification information of the service. In a case that the service quality requirement corresponding to each slice network does not include the service identification information of the service, the content of the service quality requirement corresponding to each slice network may be as shown in table 1.

If the qos requirement corresponding to each slice network includes qos requirements of a plurality of services, the qos requirement corresponding to each slice network may include an identifier of a service corresponding to each qos requirement in addition to the identifier of the slice network and the qos requirement. In other words, the service quality requirement of the slice network list may include the identities of N slice networks, and each of the identities of the N slice networks corresponds to the identities of the M services and the M service quality requirement. The M service quality requirements correspond to the M service identities one to one, and each service quality requirement in the service quality requirements of the slice network list is the service quality requirement of the corresponding service. For example, table 2 is an illustration of the quality of service requirements for a sliced network list.

TABLE 2

The list of slicing networks shown in table 2 includes three slicing networks, which are slicing network 1, slicing network 2, and slicing network 3. The quality of service of each of the three sliced networks includes the quality of service requirements of two services. For example, the slice network 1 includes a service quality requirement of a video service and a service quality requirement of a voice service, where the service quality requirement of the video service is that a user satisfaction degree of the video service is greater than 95%, where the user satisfaction degree of the video service refers to a user ratio that a video mean opinion score (vMOS) is greater than 4 points, and the service quality requirement of the voice service refers to a user satisfaction degree of the voice service is greater than 95%, where the user satisfaction degree of the voice service refers to a user ratio that a MOS is greater than 3. It will be appreciated that a vMOS score greater than 4 is one example of a single user quality of service requirement for video traffic, i.e. for each single user a vMOS score greater than 4 is required for video traffic; MOS greater than 3 is one example of a single-user quality of service requirement for voice traffic, i.e., MOS greater than 3 for voice traffic is required for each individual user. A proportion of users with a vMOS greater than 4 greater than 95% means that the vMOS of the video traffic for more than 95% of the users in the slice network is greater than 4 points. A proportion of users with MOS greater than 3 greater than 95% means that the MOS of voice traffic for more than 95% of the users in the sliced network are greater than 3 points.

In the example shown in table 2, the qos requirement for a service is a qos requirement. In other embodiments, the qos requirement corresponding to one service may be a plurality of qos requirements. Further, the number of qos requirements for different services may also be different. Table 3 is an illustration of the qos requirements of a slice network, where a plurality of qos requirements of a service refer to the service user satisfaction requirements corresponding to a plurality of single-user qos intervals.

TABLE 3

The list of slicing networks shown in table 3 includes three slicing networks, which are slicing network 1, slicing network 2, and slicing network 3. The quality of service of each of the three sliced networks includes the quality of service requirements of two services. For example, the slice network 1 includes quality of service requirements for video traffic and quality of service requirements for voice traffic. In the three slice networks shown in table 3, each slice network includes two services, and the quality of service requirements of the two services are different. Specifically, the service quality requirement of the video service included in the slice network 1 includes 3 service quality requirements, and the service quality requirement of the voice service included in the slice network 1 includes 2 service quality requirements; the service quality requirement of the video service included in the slice network 2 includes 2 service quality requirements, and the service quality requirement of the voice service included in the slice network 2 includes 1 service quality requirement; the quality of service requirements of the video service comprised by the slicing network 3 comprise 1 quality of service requirement and the quality of service requirements of the voice service comprised by the slicing network 2 comprise 2 quality of service requirements.

In addition, it can be seen that the number of the service quality requirements corresponding to the same service in different slice networks may also be different. Specifically, the video service corresponds to 3 service quality requirements in the slice network 1, 2 service quality requirements in the slice network 2, and 1 service quality requirement in the slice network 3; the voice service corresponds to 2 service quality requirements in the slice network 1, 1 service quality requirement in the slice network 2, and 2 service quality requirements in the slice network 3.

In some embodiments, the qos requirements for each of the slicing networks include qos requirements for at least one user type in each of the slicing networks.

If the qos requirement corresponding to each slice network only includes the qos requirement corresponding to one user type in each slice network, the qos requirement corresponding to each slice network may only include the identifier of the slice network and the qos requirement. In this case, the content of the qos requirement corresponding to each slice network may be as shown in table 1. Further, in some embodiments, even if the qos requirement for each of the slicing networks only includes qos requirements for one user type in each of the slicing networks, the qos requirement for each of the slicing networks may further include a user type identifier.

If the service quality requirement corresponding to each slice network includes service quality requirements corresponding to a plurality of user types, the service quality requirement corresponding to each slice network may include a user type identifier corresponding to each service quality requirement in addition to the identifier of the slice network and the service quality requirement. In other words, the service quality requirement of the slice network list may include the identities of N slice networks, where each of the identities of N slice networks corresponds to M user types and M service quality requirements. The M qos requirements correspond to the M user types one to one, and each qos requirement in the qos requirements of the slice network list is a qos requirement corresponding to a corresponding user type. For example, table 4 is an illustration of the quality of service requirements for a sliced network list.

TABLE 4

The list of slicing networks shown in table 4 includes three slicing networks, which are slicing network 1, slicing network 2, and slicing network 3. The service quality of each of the three sliced networks includes service quality requirements corresponding to the two user types. For example, the slicing network 1 includes a service quality requirement corresponding to a gold user and a service quality requirement corresponding to a silver user, where the service quality requirement corresponding to the gold user is that the proportion of users whose MOS is greater than 3 is 95%, and the service quality requirement corresponding to the silver user is that the proportion of users whose MOS is greater than 3 is 90%.

In some embodiments, the quality of service requirement corresponding to each of the sliced networks may include a quality of service requirement corresponding to at least one user type of one or more services in each of the sliced networks.

In other words, in some embodiments, the quality of service requirement corresponding to each of the sliced networks may include a quality of service requirement of a service of a user type in each of the sliced networks. In this case, the contents of the quality of service requirements of the sliced network list may be as shown in table 1. In addition to the contents shown in table 1, the contents of the service quality requirement of the slice network list may further include a user type identifier and/or a service identifier.

In other embodiments, the qos requirement corresponding to each of the slicing networks may include qos requirements of a plurality of services of one user type in each of the slicing networks. In this case, the contents of the quality of service requirements of the sliced network list may be as shown in table 2. In addition to the contents shown in table 2, the contents of the slicing network list's quality of service requirements may also include a user type identifier.

In other embodiments, the qos requirement corresponding to each of the sliced networks may include a qos requirement of a service of a plurality of user types in each of the sliced networks. In this case, the contents of the quality of service requirements of the slice network list may be as shown in table 4. In addition to the contents shown in table 4, the contents of the service quality requirement of the slice network list may also include a service identifier.

In other embodiments, the qos requirement corresponding to each of the sliced network lists may include qos requirements corresponding to a plurality of user types in a plurality of services in each of the sliced networks. For example, table 5 is an illustration of the quality of service requirements for a sliced network list.

TABLE 5

The list of slicing networks shown in table 5 includes three slicing networks, which are slicing network 1, slicing network 2, and slicing network 3. The service quality of each of the three slice networks comprises two services, and each service comprises service quality requirements corresponding to two user types. For example, the slice network 1 includes a service quality requirement corresponding to a gold-card user of a voice service, a service quality requirement corresponding to a silver-card user of the voice service, a service quality requirement corresponding to a gold-card user of a video service, and a service quality requirement corresponding to a silver-card user of the video service, where the service quality requirement corresponding to the gold-card user of the voice service is that the gold-card user satisfaction of the voice service is greater than 95%, the gold-card user satisfaction of the voice service is that the MOS of the speech audio service for the gold-card user type is greater than 3% of the total number of the gold-card users, and the service quality requirement corresponding to the silver-card user of the voice service is that the silver-card user satisfaction of the voice service is greater than 90%, where the silver-card user satisfaction of the voice audio service for the silver-card user type is greater than 90% of the total number of the silver-card users of the voice audio service for the silver-card user type, the gold-card user satisfaction of the video service is greater than 95%, the gold-card user satisfaction for the video service for the gold-card user type of the video service means that the MOS of the silver-card user type is greater than 3% of the total number of the silver-card user for the video service, and the satisfaction of the silver-card user for the video service is greater than 4% of the total number of the silver-card user for the video service, and the silver-card user for the video service is greater than the silver-card user type.

In some embodiments, the quality of service requirement corresponding to each of the slicing networks may include a quality of service requirement of one or more spatial information in each of the slicing networks. The spatial information may be spatial information defined in a 3GPP communication network, such as a serving cell a or a registration area B, or spatial information defined in a non-3 GPP communication network, such as a specific geographic location range (e.g., longitude and latitude or Global Positioning System (GPS) spatial information). For example, table 6 is an illustration of the quality of service requirements for a sliced network list.

TABLE 6

The list of slicing networks shown in table 6 includes three slicing networks, which are slicing network 1, slicing network 2, and slicing network 3. The quality of service for each of the three sliced networks includes the quality of service requirements for two regions. For example, each of the slicing networks 1, 2, and 3 includes a quality of service requirement for region 1 and a quality of service requirement for region 2.

Table 6 illustrates that one spatial information corresponds to one qos requirement, but in other embodiments one spatial information may also correspond to multiple qos requirements. For example, the qos requirement of one spatial information may be multiple qos requirements of the same service; as another example, the qos requirement of one spatial information may be the qos requirements of a plurality of services.

The number of quality of service requirements and/or the quality of service requirements for different spatial information may also be different.

In some embodiments, the quality of service requirement corresponding to each of the sliced networks may include a quality of service requirement of one or more time information in each of the sliced networks. The embodiment of the present application does not limit the specific form of the time information, as long as the time information can reflect the time. For example, the time information may be divided in an hour granularity, for example, the first time information is 8 to 10 points, and the second time information is 10 to 12 points. For another example, the time information may be divided by day granularity, for example, the first time information is 1 to 10 days of each month, and the second time information is 11 to 20 days of each month. For another example, the time information may be divided by the user's boot time length. For example, the first time information is 0 to 4 hours of power-on, and the second time information is 4 to 8 hours of power-on. For example, table 7 is an illustration of the quality of service requirements for a sliced network list.

TABLE 7

The list of slicing networks shown in table 7 includes three slicing networks, which are slicing network 1, slicing network 2, and slicing network 3. The quality of service of each of the three slicing networks includes a quality of service requirement of two time information. For example, each of the slicing network 1, the slicing network 2, and the slicing network 3 includes a quality of service requirement of the time information 1 and a quality of service requirement of the time information 2.

Table 7 illustrates that one time information corresponds to one quality of service requirement, while in other embodiments one time information may correspond to multiple quality of service requirements. For example, the qos requirement of one time information may be multiple qos requirements of the same service; as another example, the quality of service requirement of one time information may be the quality of service requirement of a plurality of services.

The number of quality of service requirements and/or the quality of service requirements for different time information may also be different.

The qos requirements of the slice network lists shown in tables 2, 4, 3, 6, and 7 are qos requirements of one dimension of the slice network list. Specifically, tables 2 and 3 are quality of service requirements for the service type dimension of the slice network list, table 4 is quality of service requirements for the user type dimension of the slice network list, table 6 is quality of service requirements for the space dimension of the slice network list, and table 7 is quality of service requirements for the time dimension of the slice network list.

Any two or more than two of the dimensions of the service type dimension, the user type dimension, the space dimension, the time dimension and the service quantity dimension can be combined to obtain the service quality requirements of multiple dimensions of the slice network list. For example, table 8 is the quality of service requirements for a sliced network list resulting from the combination of the service dimension and the user type dimension.

Table 8 is the quality of service requirements for the sliced network list resulting from the combination of the service type dimension and the spatial dimension.

TABLE 8

The list of slicing networks shown in table 8 includes three slicing networks, which are slicing network 1, slicing network 2, and slicing network 3. The quality of service for each of the three sliced networks includes two services, each service including the quality of service requirements for two regions. For example, the slice network 1 includes the service quality requirement of the area 1 of the voice service, the service quality requirement of the area 2 of the voice service, the service quality requirement of the area 1 of the video service, and the service quality requirement corresponding to the area 2 of the video service.

Although table 8 shows that one area of one service type of a slice network has only one qos requirement, the embodiment of the present application does not limit the number of qos requirements in one area of one service type of a slice network. In other words, a plurality of quality of service requirements may be included in an area of a traffic type of a slicing network.

Tables 1 to 8 are only described by way of example as voice service and video service, and actually, other different types of services may exist in one slice network, which is not limited in this embodiment of the present application. In addition, the requirement of the quality of service of a service is a requirement on the proportion of users meeting the requirement of the quality of service of a single user of the service, and here, the requirement on the proportion of users meeting the requirement of the quality of service of a single user of the service may also be referred to as a requirement on the satisfaction degree of users of the service. The single-user service quality refers to data for evaluating the quality of service experience of each user, and a specific method for how to evaluate the service experience of each user may be determined by a service provider, for example, a voice service server determines to use an MOS to evaluate the voice service quality of a single user, an MOS score value range is [0,5], a higher MOS score represents better voice service experience of a user, and how to calculate the MOS score of each user belongs to an internal calculation method, which is not in the scope of the patent discussion. For the video service, the video service server decides to use the vMOS score to evaluate the video service experience of each user, and the calculation methods of the MOS score and the vMOS are different. Here, the evaluation of the quality of the single-user service by using MOS and vMOS is only two examples for the voice service and the video service, and for other types of services, there are other various methods for evaluating the quality of the single-user service, for example, for data services, the quality of the single-user service of the data service may be comprehensively evaluated by using parameters such as a data packet loss rate, a data packet transmission average delay, and the like, and the present patent is not limited. In addition, the preset single-user service quality requirement is negotiated by an operator and a service provider in advance, for example, for a voice service, the single-user service quality requirement can be preset to be MOS >3.

Furthermore, in some cases, a single user initiates only one service of the same service type. In this case, the number of services is equivalent to the number of users performing the service. Therefore, the user satisfaction requirement of a service is the user proportion requirement to meet the single-user service quality requirement of the service. In other cases, a single user may initiate multiple services of the same service type. For example, one user may initiate two voice services simultaneously. In this case, the number of services is not equivalent to the number of users performing the service. The user satisfaction requirement of a service may be a service proportion requirement to meet a single-user quality of service requirement of the service. For example, assuming that there are 1000 users in total, and each user initiates two voice services at the same time, there are 2000 voice services in total, and the requirement of MOS greater than 4 is the requirement of MOS greater than 4. Whereas if each user initiates only one voice service, the service proportion requirement is equivalent to the user proportion requirement.

In addition, in all the foregoing examples, the service quality requirement of one service is a requirement for a user ratio that meets the service quality requirement of a single user of the service, which is taken as an example for explanation, and actually, the service quality requirement of one service is not limited to this, and may include other requirements or be other requirements. For example, in addition to the requirement of the user proportion of the single-user quality of service requirement, the quality of service requirement of the service may also include a service number requirement of the service, where the service number requirement refers to a requirement for the total number of services of the service being executed in the slice network, such as a requirement that the slice network can accommodate 10000 voice services to be executed simultaneously. When it is assumed that one user can perform only one service of one service type at the same time, for example, one user can perform only one voice service at the same time, the number of services of one service is equivalent to the number of users performing the service. In addition, if one service corresponds to multiple qos requirements, in such a scenario, the requirement for the number of services may be the requirement for the number of services corresponding to each qos requirement. For example, taking table 3 as an example, when the multiple qos requirements refer to service user satisfaction requirements corresponding to multiple single-user qos intervals, the service quality requirements of the service at this time may further include service number requirements corresponding to each single-user qos interval. It is thus seen that the service quality requirement information of the service of the slice network referred to in the present application can be understood as the requirement for the overall service quality of the service in the slice network. Of course, besides the requirement of the satisfaction degree of the service, the requirement of the service quality of the service of the slice network may also be defined in other terms, for example, the requirement of the average data transmission delay of the service of the slice network, the requirement of the data throughput of the slice network, the requirement of the load of the slice network, and the like.

The qos requirements of the sliced network list may be in the form of any one of the sliced network combinations in table 1, table 2, table 4 and table 5. For example, the quality of service requirement of the slice network list may be a combination of the slice network 1 in table 1, the slice network 2 in table 2, the slice network 3 in table 4, and the slice network 3 in table 5. In the embodiment of the present application, no special combination restriction is imposed on the slice network list sent by the policy control network element to the data analysis network element.

Further, as described above, table 1 may be a correspondence between the sliced network list and the qos requirement, or may be the qos requirement of the sliced network list. Correspondingly, tables 2 to 5 may also be the corresponding relationship between the slice network list and the qos requirement. Taking table 2 as an example, if the request information includes the identifier from the slice network 1 to the slice network 3 in the slice network list, the data analysis network element may determine, according to the correspondence shown in table 2, that the service quality requirement corresponding to the slice network 1 includes the service quality requirement of the video service and the service quality requirement of the voice service, where the service quality requirement of the video service is that the user satisfaction of the video service is greater than 95%, and the service quality requirement of the voice service is that the user satisfaction of the voice service is greater than 95%. Similarly, the data analysis network element may also determine the service quality requirements corresponding to the slice network 2 and the slice network 3 according to the correspondence shown in table 2.

In some embodiments, the policy control network element may determine the quality of service requirement of the sliced network list according to the sliced network priority information. For example, the policy control network element determines the slice networks included in the slice network list according to the priority information, and then determines the service quality requirement corresponding to each slice network, where the service quality requirement corresponding to each slice network may be from each slice network tenant or a corresponding service server, or may be configured in the policy control network element. The operator network may provide and operate a plurality of slice networks simultaneously, and the plurality of slice networks have slice network priority information, so as to ensure that the slice networks can be configured or operated according to the slice network priority information under special conditions such as resource limitation, wherein each slice network in the plurality of slice networks may have different priorities, or some slice networks may have the same priority, and the latter is described below as an example.

Table 9 is an illustration of the slice network priority information for a total of 5 slice networks.

TABLE 9

Slicing network identification	Priority level
		Slicing network 1	1
Slicing network 2	2
		Slicing network 3	2
Slicing network 4	3
		Slicing network 5	4

As shown in table 9, the priority of the slice network 1 is value 1, the priority of the slice network 2 is value 2, the priority of the slice network 3 is value 2, the priority of the slice network 4 is value 3, and the priority of the slice network is value 4. It is assumed here that the larger the priority value, the lower the priority. As shown in table 9, since the value of the priority of the slice network 1 is the smallest, the priority of the slice network 1 is the highest. The priority values of the slicing network 2 and the slicing network 3 are greater than the priority value of the slicing network 1, and thus the priority of the slicing network 2 and the slicing network 3 is lower than that of the slicing network 1. The priority value of the slicing network 4 is greater than the priority value of the slicing network 2, and thus the priority of the slicing network 4 is lower than those of the slicing network 2 and the slicing network 3. The value of the priority of the slicing network 5 is the largest, and thus the priority of the slicing network 5 is the lowest.

In some embodiments, the policy control network element may determine that the qos requirements of the slice network list in the request message include qos requirements corresponding to several high-priority slice networks, that is, qos requirements corresponding to slice networks with priority values smaller than a preset priority value. Specifically, the preset priority value is set by the policy control network element according to the network resource status and the internal policy. For example, when network resources are sufficient or a particular value, the preset priority value may be set to a first priority value, which may be the maximum value of the priority. In this case, the slice network list may be composed of all slice networks, and the qos requirement of the slice network list in the request message may include qos requirements corresponding to all slice networks. Taking table 9 as an example, the first priority value may be 4. Assuming that the preset priority value is the first priority value, the slice network list is composed of slice networks with priority values smaller than 4. The quality of service requirements for the sliced network list may include quality of service requirements for sliced networks having a priority value less than 4. The quality of service requirements of the sliced network list may include quality of service requirements corresponding to sliced networks 1 to 5. The preset priority value may be set to a second priority value, which is less than the first priority value, when network resources are limited or another specific value. In this case, the sliced network list may be composed of sliced networks having priority values less than or equal to the second priority value, and the qos requirements of the sliced network list in the corresponding request message may include qos requirements corresponding to the sliced networks having priority values less than or equal to the second priority value. Also taking table 9 as an example, assuming that the preset priority value is 3, the qos requirements of the slice network list in the slice network list may include qos requirements corresponding to the slice networks with priority values less than or equal to 3. In this case, the quality of service requirements of the slice network list may include quality of service requirements corresponding to slice network 1, slice network 2, and slice network 3.

The network resource status information may come from a network management element, and the status information may be qualitative status information or quantitative status information, for example, the policy control element receives indication information of the network management element before sending the request message of step 201, and the indication information user informs the policy control element of the current network resource status. The policy control network element sets a specific value of the preset priority value according to the current network resource state.

The network resource status information may also come from a data analysis network element. The network resource status information is statistically analyzed by the data analysis network element in a historical process of slice operation, for example, if the data analysis network element statistically analyzes that network resources are always insufficient in a certain period of time, which results in a failure to meet the service quality requirements of all slices, the data analysis network element may feed back the information as network resource status information to the policy control network element, and the policy control network element decides to request only certain high-priority slices to form the slice network combination in the period of time. The network resource status information may help the data analysis network element to generate an applicable condition corresponding to the network configuration information. The applicable condition may include a time, a place, and the like, to which each set of network configuration information is applicable.

In addition, the network management element may also determine the slice list or the preset priority level by itself, and request the policy control element to provide the network configuration information applicable to the slice list or the slice list corresponding to the preset priority level, and the policy control element directly sends the request message to the data analysis element according to the request of the network management element.

In some embodiments, the policy control network element determines the identity of one or more sliced networks included in the sliced network list included in the request information according to the priority information of the sliced networks. For a specific method, reference may be made to the above description of how to determine the slicing networks included in the slicing network list according to the slicing network priority information, and details are not required here.

In some embodiments, the policy control network element may determine the quality of service requirement of the sliced network list according to the service priority information.

Table 10 is an illustration of service priority information comprising a total of 5 services.

TABLE 10

Service identification	Priority level
		Service 1	1
Service 2	2
		Service 3	2
Service 4	3
		Service 5	4

As shown in table 10, the priority of service 1 is value 1, the priority of service 2 is value 2, the priority of service 3 is value 2, the priority of service 4 is value 3, and the priority of service 4 is value 4. It is assumed that the larger the priority value, the lower the priority. As shown in table 10, the priority value of service 1 is the smallest, and thus the priority of service 1 is the highest. The priority values of service 2 and service 3 are greater than the priority value of service 1, and thus the priority of service 2 and service 3 is lower than the priority of service 1. The priority value of service 4 is greater than the priority value of service 2, so the priority of service 4 is lower than the priorities of service 2 and service 3. The priority value of service 5 is the largest and thus the priority of service 5 is the lowest.

In some embodiments, the policy control network element may determine that the qos requirements of the sliced network list in the request message include qos requirements of a service having a lower qos value than a preset qos value. Specifically, the policy control network element may determine which services may be included according to the service priority information, and then determine the service quality requirement of the slice network list according to the service quality requirement of each included service. The preset priority value is set by the policy control network element according to the network resource state and the internal policy. For example, when network resources are sufficient or a particular value, the preset priority value may be set to a first priority value, which may be the maximum value of the priority. In this case, the qos requirements of all services may be requested, and the qos requirements of the sliced network list in the corresponding request message may include the qos requirements of all services. Taking table 10 as an example, the first priority value may be 4. Assuming that the preset priority value is the first priority value, the qos requirements of all services can be requested. The quality of service requirements of the sliced network list may include quality of service requirements for services having a priority value of less than 4. The qos requirements of the sliced network list may include qos requirements corresponding to services 1 to 5. The preset priority value may be set to a second priority value, which is less than the first priority value, when network resources are limited or another specific value. In this case, the qos requirements of the services having the priority values less than or equal to the second priority value may be requested, and the qos requirements of the sliced network list in the corresponding request message may include the qos requirements of the services having the priority values less than or equal to the second priority value. Also taking table 10 as an example, assuming that the preset priority value is 3, the qos requirement of the service with the priority value less than or equal to 3 may be requested. In this case, the service quality requirements of service 1, service 2 and service 3 may be included in the service quality requirements of the slice network list.

In some embodiments, the policy control network element may determine the quality of service requirement of the sliced network list according to the sliced network priority information and the traffic priority information.

Table 11 is an illustration of the slice network priority information and the traffic priority information.

TABLE 11

As shown in table 11, the priority value of the slice network 1 is 1, the priority value of the slice network 2 is 2, and the priority value of the slice network 3 is 3. It is assumed that the larger the priority value, the lower the priority. As shown in table 11, since the value of the priority of the slice network 1 is the smallest, the priority of the slice network 1 is the highest. The priority value of the slice network 2 is greater than that of the slice network 1, and thus the priority of the slice network 2 is lower than that of the slice network 1. The value of the priority of the slice network 3 is the largest, and thus the priority of the slice network 3 is the lowest.

As shown in table 11, the priority of service 1 is value 1, the priority of service 2 is value 2, and the priority of service 3 is value 3. It is assumed that the larger the priority value, the lower the priority. As shown in table 11, the priority value of service 1 is the smallest, and thus the priority of service 1 is the highest. The priority value of service 2 is greater than the priority value of service 1, and thus the priority of service 2 is lower than the priority of service 1. The priority value of service 3 is the largest and thus the priority of service 3 is the lowest.

Specifically, the policy control network element may determine, according to the slice network priority information, the slice networks included in the slice network list, then determine, according to the service priority information, the services that can request the service quality requirement, and finally determine the service quality requirement of the slice network list.

In some embodiments, the policy control network element may determine that the sliced network list includes sliced networks with a sliced network priority value less than a preset sliced network priority value. For example, when network resources are sufficient or at some particular value, the preset sliced network priority value may be set to a first sliced network priority value, which may be the maximum value of the sliced network priority. In this case, the slice network list may be composed of all slice networks. Taking table 11 as an example, the first priority value may be 3. Assuming that the preset slice network priority value is the first slice network priority value, the slice network list is composed of slice networks with slice network priority values smaller than 3. When network resources are limited or another specific value, the preset sliced network priority value may be set to a second sliced network priority value that is less than the first sliced network priority value. In this case, the sliced network list may be composed of sliced networks having a sliced network priority value less than or equal to the second sliced network priority value. Also taking table 11 as an example, assuming that the preset slicing network priority value is 2, the slicing network list may include slicing networks having a slicing network priority value less than or equal to 2. In this case, the slice network list includes slice network 1 and slice network 2.

Further, the policy control network element may determine that the slice network list in the request message includes a service quality requirement of a service whose service priority value is smaller than a preset service priority value. For example, when network resources are sufficient or a specific value, the preset traffic priority value may be set to a first traffic priority value, which may be the maximum value of the traffic priority. In this case, the quality of service requirements of all services may be requested. Taking table 11 as an example, the first service priority value may be 3. Assuming that the preset service priority value is the first service priority value, the service quality requirements of all services can be requested. When network resources are limited or another specific value, the preset service priority value may be set to a second service priority value, which is smaller than the first service priority value. In this case, a quality of service requirement for services having a service priority value less than or equal to the second service priority value may be requested. Also taking table 11 as an example, assuming that the preset service priority value is 2, the service quality requirement of the service with the service priority value less than or equal to 2 may be requested. In this case, service 1 and service 2 and service 3 may be requested.

Taking table 11 as an example, assuming that the preset slicing network priority is 2 and the preset service priority is 2, the service quality requirements of the slicing network list may include the service quality requirement of service 1 of slicing network 1, the service quality requirement of service 2 of slicing network 1, the service quality requirement of service 1 of slicing network 2, and the service quality requirement of service 2 of slicing network 2.

In some embodiments, the policy control network element may further send priority information of the slice network and/or priority of the service and/or quality of service requirement of the slice network to the data analysis network element, where the priority information of the slice network and/or priority of the service and/or quality of service requirement of the slice network may or may not be included in the request information, and the order of sending the request information is not limited in time order.

In this step, the policy control network element sends the request information to the data analysis network element, which may be a real-time request information or a subscription request information. If the request information is the real-time request information, the data analysis network element may immediately return the content of the policy control network element request after receiving the request information without the operation of model training described in step 202, where the operation of model training is completed before receiving the request information. If the request information is the subscription request information, the data analysis network element receives the request information, and then the data analysis network element can return the content of the data analysis network element request after model training.

202, the data analysis network element sends network configuration information corresponding to the sliced network list to the policy control network element. Correspondingly, the policy control network element receives the network configuration information corresponding to the sliced network list sent by the data analysis network element.

In some embodiments, step 201 may not be performed. That is, the data analysis network element may determine and execute sending the network configuration information corresponding to a slice network list to the policy control network element by itself. For example, the data analysis net friend may determine network configuration information corresponding to a slice network list according to the slice network priority information and/or the service priority information, and send the network configuration information corresponding to the slice network list to the policy control network element. The manner in which the data analysis network element determines the network configuration information corresponding to the slice network list according to the slice network priority information and/or the service priority information may refer to the manner in which the policy control network element determines the service quality requirement of the slice network list according to the slice network priority information and/or the service priority information, which is not described herein again. It should be noted that the slice network priority information and/or the service priority information may be obtained by the data analysis network element from the policy control network element, the service server, or the network management network element in advance, or may be configured on the data analysis network element in advance, which is not limited herein. In addition, in addition to the slice network priority information and/or the service priority information, in order to obtain the network configuration information corresponding to the slice network list, the data analysis network element may further need to acquire the service quality requirement corresponding to each slice network in all slice networks, and the service quality requirement of each slice network may be obtained by the data analysis network element from the policy control network element, the service server, or the network management network element in advance, or may be configured on the data analysis network element in advance, which is not limited here.

If step 201 is executed, the data analysis network element may determine, according to the request information, network configuration information corresponding to the slice network list that needs to be sent to the policy control network element. The network configuration information corresponding to the slice network list sent to the policy control network element is the network configuration information corresponding to the slice network list acquired by the request information request.

The network configuration information is used to guide the setting of each slice network in the slice network list and the network elements related to each slice network.

Taking a network slice as an example, the network slice may be a complete end-to-end network including a terminal device, an access network, a transmission network, a core network, and a service server, and the network configuration information may be parameters for guiding setting of the access network, the transmission network, the core network, and/or the service server in the network slice; the network slice may also be a network slice that includes only the core network but is supplemented by the terminal device, the access network, the transport network and the traffic server, and the network configuration information may be parameters for directing the setting of the network slice parameters and the associated access network, transport network and/or traffic server. The parameters in the network configuration information include an end-to-end parameter of a network slice, a single network element device parameter or a parameter on a corresponding interface between network element devices.

In some embodiments, the network configuration information corresponding to the sliced network list may include a set of network configuration information.

In other embodiments, the network configuration information corresponding to the sliced network list may include multiple sets of network configuration information.

Table 12 shows an exemplary table of a slice network list corresponding to multiple sets of network configuration information.

TABLE 12

Table 12 is network configuration information corresponding to the sliced network list of table 2. Where Y1, Y2, Y3 are three sets of network configuration information. Each set of network configuration information can be used for guiding the setting of each of the three slice networks and the related network elements. For example, Y1 may be used to guide network settings for slice network 1, slice network 2, and slice network 3, Y2 may be used to guide network settings for slice network 1, slice network 2, and slice network 3, and Y3 may be used to guide network settings for slice network 1, slice network 2, and slice network 3.

In some embodiments, the policy control network element may further receive an applicable condition corresponding to the network configuration information sent by the data analysis network element. The applicable condition may include a time, a place, and the like, to which each set of network configuration information is applicable. The applicable condition may be used as a part of the network configuration information or as an additional information. In case the applicable condition is an additional information, the applicable condition may be sent to the network management element together with the network configuration information, and the applicable condition and the network configuration information may also be sent to the network management element separately.

In other embodiments, the policy control network element may further receive configuration effect information sent by the data analysis network element, where the configuration effect information is used to indicate a service quality effect that can be achieved by each group of network configuration information in multiple groups of network configuration information included in the network configuration information corresponding to the slice network list. For example, in the case that the service quality requirement of each slice network in the slice network list is the user satisfaction requirement of the service in the slice network, the configuration effect information is the user satisfaction effect that each group of network configuration information can achieve for the service of each slice network. The configuration effect information may be a part of the network configuration information or may be an additional information. In the case that the configuration effect information is an additional information, the configuration effect information may be sent to the network management element together with the network configuration information, and the configuration effect information and the network configuration information may also be sent to the network management element separately.

Specifically, if the qos requirements of the slice network list include qos requirements of a plurality of slice networks, the qos effect is a qos effect that can be achieved by each slice network. If the service quality requirement corresponding to each slice network includes the service quality requirement of at least one service in each slice network, the service quality effect is the service quality effect that each service can achieve. If the service quality requirement corresponding to each slice network comprises the service quality requirement corresponding to at least one user type in each slice network, the service quality effect is the service quality effect which can be achieved by each user type. If the qos requirement corresponding to each of the slice networks may include a qos requirement corresponding to at least one user type of one or more services in each of the slice networks, the qos effect is a qos effect that can be achieved by each user type of each service.

It is assumed that the qos requirements of the slice list sent by the policy control network element to the data analysis network element are as shown in table 2. The network configuration information and the configuration effect information sent by the data analysis network element may be as shown in table 13.

Watch 13

As shown in table 13, Y1, Y2, and Y3 respectively represent three sets of network configuration information. For example, the service quality effect that Y1 can achieve is that the user proportion of vMOS >4 of the video service of the slice network 1 is greater than 98%, the user proportion of MOS >4 of the voice service of the slice network 1 is greater than 98%, the user proportion of vMOS >4 of the video service of the slice network 2 is greater than 92%, the user proportion of MOS >4 of the voice service of the slice network 2 is greater than 98%, the user proportion of vMOS >4 of the video service of the slice network 3 is greater than 85%, and the user proportion of MOS >4 of the voice service of the slice network 3 is greater than 90%. It can be seen that the three sets of network configuration information shown in table 13 can satisfy the service quality requirements of the slice network 1, the slice network 2 and the slice network 3 shown in table 2.

In still other embodiments, the policy control network element may further receive usage priority information of the network configuration information sent by the data analysis network element, where the usage priority information indicates a priority of each set of network configuration information being adopted or used. For example, Y1, Y2, and Y3 respectively represent three sets of network configuration information, the usage priority of Y1 is 1, the usage priority of Y2 is 2, and the usage priority of Y3 is 3, where the usage priority of Y1 is the highest and the usage priority of Y3 is the lowest. The usage priority information may be part of the network configuration information or may be an additional piece of information. In case the usage priority information is an additional information, the usage priority information may be sent to a network management element together with network configuration information, and the usage priority information and the network configuration information may also be sent to the network management element separately.

How the data analysis network element determines the network configuration information will be described below.

The data analysis network element acquires historical network configuration information corresponding to each slice network in the slice network list; the data analysis network element acquires the historical service quality of each slice network in the slice network list; the data analysis network element determines network configuration information corresponding to each slicing network according to the historical network configuration information corresponding to each slicing network, the historical service quality of each slicing network and the service quality requirement of each slicing network; and the data analysis network element determines the network configuration information corresponding to the slice network list according to the network configuration information corresponding to each slice network.

In some embodiments, the historical quality of service data for each of the slicing networks comprises a historical quality of service for each of the services for each of the slicing networks. The historical service quality of each slice network comprises network identification information of the slice network and the number of users in the slice network, the network identification information of the slice network is used for uniquely identifying the slice network, and the number of the users in the slice network refers to the number of registered users or the number of online users in the slice. In addition, the historical quality of service for each service may include at least one of the following information: the service identification information of the service, the network identification information of the slice network, the service number of the service, and the user proportion information meeting the service quality requirement of the service single user. The service identification information of the service is used for uniquely identifying the service; the network identification information of the network is used for uniquely identifying the network, and the network is a network in which the service operates; the number of services of the service refers to the total number of services of the service being executed in the slice network, for example, the number of voice services being executed is 10000, and the number of video services being executed is 2000. When it is assumed that one user can perform only one service of one service type at the same time, for example, one user can perform only one voice service at the same time, the number of services of one service is equivalent to the number of users performing the service. In addition, if a service is subdivided into multiple single-user service quality value ranges, in such a scenario, the service number may be a requirement of the service number corresponding to each single-user service quality value range. For example, MOS = [3,4] corresponds to a traffic number of 5000, and MOS = [4,5] corresponds to a traffic number of 5000. The user proportion meeting the service quality requirement of the service single-user, i.e. the user satisfaction degree of the service, wherein, in some embodiments, the user proportion of the service quality requirement of the service single-user is the user proportion corresponding to the service quality requirement of one single-user, e.g. the user proportion of the voice service MOS is greater than 3, while in other embodiments, the user proportion of the service quality requirement of the service single-user is the user proportion corresponding to a plurality of service quality requirements of one user, e.g. the user proportion of the voice service 3 & ltm MOS & lt 4 & gt and the user proportion of the service 4 & ltm MOS & lt 5 & gt.

In some embodiments, the historical quality of service of each of the slicing networks may also be a quality of service differentiated by a user type dimension, i.e., the historical quality of service of each of the slicing networks includes the historical quality of service of at least one user type of the each of the slicing networks. In this scenario, in addition to the above information, the historical service quality of each slice network further includes user type information, where the user type information is used to distinguish the historical service qualities corresponding to different user types, for example, the historical service quality corresponding to a gold user and the historical service quality corresponding to a silver user.

In some embodiments, the historical quality of service of each of the slicing networks may also be a historical quality of service differentiated by a service type dimension, i.e., the historical quality of service of each of the slicing networks includes a historical quality of service of at least one service type of the each of the slicing networks. In this scenario, besides the above information, the historical service quality of each slice network further includes service type information or service identification information, where the service type information or service identification information is used to distinguish historical service qualities corresponding to different service types, for example, the historical service quality corresponding to the voice service and the historical service quality corresponding to the video service.

In some embodiments, the historical quality of service of each slice network may also be a historical quality of service differentiated by a spatial dimension, that is, the historical quality of service of each slice network includes a historical quality of service corresponding to at least one spatial information of each slice network. In this scenario, besides the above information, the historical service quality of each slice network also includes spatial information. For example, the historical quality of service for the sliced network may include the historical quality of service for region 1 and the historical quality of service for region 2. The embodiment of the present application does not limit the specific form of the spatial information, as long as the spatial information can be reflected, for example, the spatial information may be spatial information defined in a 3GPP communication network, such as a serving cell a or a registration area B, or the spatial information may be spatial information defined in a non-3 GPP communication network, such as the spatial information is a specific geographic location range (e.g., longitude and latitude or GPS spatial information).

In some embodiments, the historical quality of service of each slice network may be a historical quality of service differentiated in a time dimension, that is, the historical quality of service of each slice network includes a historical quality of service corresponding to at least one time information of each slice network. In this scenario, besides the above information, the historical service quality of each slice network also includes time information. The embodiment of the present application does not limit the specific form of the time information, as long as the time can be reflected. For example, the time information may be divided in an hour granularity, for example, the first time information is 8 to 10 points, and the second time information is 10 to 12 points. For another example, the time information may be divided by day granularity, for example, the first time information is 1 to 10 days of each month, and the second time information is 11 to 20 days of each month. For another example, the time information may be divided by the user's power-on time length. For example, the first time information is 0 to 4 hours of power-on, and the second time information is 4 to 8 hours of power-on. For example, the historical quality of service may include the historical quality of service for time information 1 and the historical quality of service for time information 2.

In some embodiments, the historical service quality of each slice network may be combined according to any two or more dimensions of a service type dimension, a user type dimension, a space dimension, and a time dimension, that is, the historical service quality is a historical service quality corresponding to multiple dimensions of the slice network. In this scenario, besides the above information, the historical service quality of each slice network further includes one or more of service type information, user type information, spatial information, and temporal information.

First, for a service of a slice network, how a data analysis network element obtains historical service quality of the service is described.

The data analysis network element may obtain the historical service quality of the service in the following three ways, which are specifically shown below.

Firstly, a data analysis network element obtains historical service quality of the service from a service server of the service.

In the service operation process, the service server may obtain the service quality at the user level by using a self-measurement and calculation method, and the like, where the service quality at the user level is used to indicate the service quality of the service corresponding to at least one single user (for example, the service server may determine the service quality of the service executed by each single user according to the self-measurement and calculation method), and the service server may also obtain the service quality requirement information of the service for the single user, where the service quality requirement information of the single user refers to the requirement on the service quality of the single user of the service (for example, the MOS score requirement of the voice service for the single user is greater than 3). The service server determines the service quality data of the service corresponding to a certain historical time (time or time period) according to a large amount of single-user service quality data and single-user service quality requirement information corresponding to the historical time, and the service server can generate a plurality of service quality data corresponding to the historical time through a plurality of similar determination processes, and the plurality of service quality data corresponding to the historical time form the historical service quality of the service. For example, in a determination process, if the service server determines that the voice service MOS of 80 users in 100 users is greater than 3, the service server determines that the service quality data corresponding to one historical time is 80%; in another determining process, the service server determines that the voice service MOS of 90 users in 100 users is greater than 3, and then the service server determines that the service quality data corresponding to another historical time is 90%; similarly, after a number of determination processes, the traffic server may then generate historical quality of service.

And the service server sends the historical service quality of the service to the data analysis network element. Illustratively, the traffic server may actively send the historical quality of service of the traffic to the data analysis network element; or, the data analysis network element sends request information for acquiring the historical service quality of the service to the server of the service, so that when the service server receives the request information, the historical service quality of the service can be sent to the data analysis network element.

Wherein the user-level quality of service data is used to indicate the quality of service for one or more individual users corresponding to the service. Specifically, the quality of service corresponding to each single user includes, but is not limited to, the quality of service of the user in a single service process, or the quality of service of the user in a certain time period, or the quality of service of the user in a certain time point.

The quality of service data per single user comprises at least one of the following information: user identification information, user association identification information, user service quality evaluation data and service description information. The identification information of the user is used to uniquely identify the user, for example, the identification information of the user may be one or more of the following: internet protocol address (IP), subscription permanent identifier (SUPI), permanent Equipment Identifier (PEI), general Public Subscription Identifier (GPSI), international Mobile Subscriber Identifier (IMSI), international Mobile Equipment Identifier (IMEI), IP quintuple (5-tu), and mobile station international integrated services digital network number (MSISDN), etc.; the associated identification information of the user is used to associate the service quality data of the user with the network data of the flow level corresponding to the service quality data of the user, for example, the associated identification information of the user may be an IP address of a user terminal used by the user or a temporary identification allocated by a network to a single service flow of the user terminal, where the temporary identification may be allocated to the service flow by a PCF network element or an NWDAF network element or an NRF network element or other service network elements in the process of establishing the single service flow of the user, the allocated temporary identification is distributed to each network element corresponding to the service flow by the PCF network element or the NWDAF network element or the NRF network element or other service network elements in the process of establishing the service flow, and the temporary identification is used to associate network data of various flow levels corresponding to the service flow with the service quality data of the user; the service quality evaluation data of the user refers to data for evaluating the service quality of the user, for example, if the service is a voice service, the evaluation data may be MOS scores, voice fluency, and the like of the voice service of the user at a certain time; the service description information may include one or more of the following information: the service identification to which the service flow belongs, IP filtering information, media bandwidth requirements, traffic routing information, jitter buffer requirements, media coding type requirements, coding rate requirements required by the media coding type, TCP congestion window requirements, TCP receive window requirements, buffer requirements, and value requirements of at least one data type.

Optionally, the service server may obtain the service quality data of each single user, including data after normalization processing, so as to ensure the security of the user information. The normalization process here refers to an operation of mapping the physical values of the parameters to a fixed value space, and for example, a maximum and minimum value normalization method, a Z-Score normalization method, and the like are used to map the physical values of each feature to a fixed value space.

In addition, the single-user service quality requirement information of the service is used for indicating the requirement on the single-user service quality of the service, that is, the requirement of the tenant or the service server on the service quality of each single user of the service can be provided by the tenant to the service server, and the single-user service quality requirement information of the service can be included in the SLA. Of course, the single-user qos requirement information of the service may also be configured in the service server. For example, the service is a voice service, and the single-user service quality requirement information of the service provided by the tenant is that the MOS score of the voice service of each user is greater than or equal to 3.

It should be noted that, the service server determines, according to the service quality data at the user level and the single-user service quality requirement information of the service, a method or an algorithm used for determining the historical service quality of the service, and a type of the generated historical service quality may be customized, which is not specifically limited in this embodiment of the present application.

Further, when the service server obtains the service quality data at the user level, the service quality of the multi-user may be obtained according to the time dimension to form the service quality data at the user level, the service quality of the multi-user may be obtained according to the space dimension to form the service quality data at the user level, or the service quality of the multi-user may be obtained according to the time dimension and the space dimension to form the service quality data at the user level. When the service server of the service obtains the service quality data at the user level according to the time dimension, the service quality data of each user of the service at a certain time point (for example, 8 am) or the service quality data of each user of the service within a certain time period (for example, 8 am to 6 pm) can be obtained. When the service server of the service acquires the service quality of the user level according to the spatial dimension, the service quality data of each user in the whole slice network running the service may be acquired, or the service quality data of each user in a certain area (for example, a certain longitude and latitude range or a Registration Area (RA) or a Tracking Area (TA) or a cell list) may be acquired, or the service quality data of each user in a certain location (for example, a certain cell or a certain longitude and latitude point) may be acquired. When the service server of the service obtains the service quality data at the user level according to the time dimension and the space dimension, the service quality data of each user of the service at a certain time point or a certain time period in a certain space may be obtained, for example, the data analysis network element may obtain the service quality data of each user of the service at 8 am of the serving cell a to form the service quality at the user level, or obtain the service quality data of each user of the service from 8 am to 6 pm of the serving cell a to form the service quality data at the user level, and the like. It is to be noted that, when the service server acquires the service quality data at the user level according to the time dimension, the space dimension, the time dimension, or the combination of the space dimensions, each historical service quality data of the service acquired by the service server according to the service quality data at the user level also has the characteristics of the time dimension, the space dimension, the time dimension, or the space dimension. For example, when the data analysis network element may obtain the service quality data of each user of the service from 8 am to 6 pm in the service cell a historically, thereby forming historical service quality data of the service, the historical service quality data of the service obtained according to the user-level service quality data corresponds to the historical service quality of all or multiple users performing the service from 8 am to 6 pm in the service cell a.

And secondly, the data analysis network element acquires the historical service quality data of the service at the user level from the service server and acquires the historical service quality of the service according to the historical service quality data of the user level.

The historical service quality data of the user level refers to historical service quality data obtained by executing the service by a single user, and the historical service quality data of the user level comprises one or more historical service quality data of the single user. The qos data of each single user is as described in the first embodiment, and is not described herein again.

In the service operation process, the service server can directly obtain the service quality data of the user level. The traffic server sends the user-level quality of service data (i.e. the user-level historical quality of service data) over a past period of time to the data analysis network element. Illustratively, the traffic server may actively send the user-level historical quality of service data to a data analysis network element; or, the data analysis network element sends request information for acquiring the historical service quality data of the user level to the service server, so that the historical service quality data of the user level can be sent to the data analysis network element when the request information is received by the service server.

In addition, the data analysis network element obtains the historical service quality of the service according to the historical service quality data of the user level, and the method comprises the following steps: the data analysis network element acquires the single-user service quality requirement information of the service from the service server or the strategy control network element, wherein the single-user service quality requirement information refers to the service quality requirement for executing the service for a single user, for example, the service quality requirement of the voice service single user is that the MOS is more than 3 minutes; and determining the historical service quality of the service according to a large amount of historical service quality data of the user level and the single-user service quality requirement information. For example, the data analysis network element determines whether the service quality data of each user at a historical time meets the service quality requirement of the user level, thereby determining the user proportion meeting the service quality requirement of a single user of the service, and taking the proportion as the historical service quality corresponding to the historical time.

It should be noted that the historical service quality data of the user level, which is sent to the data analysis network element by the service server, may be historical service quality data of a plurality of user levels, which is obtained by the service server according to a time dimension, a space dimension, or a combination of the time dimension and the space dimension.

In addition, the data analysis network element determines the historical service quality of the service according to the historical service quality data of the user level and the single-user service quality requirement information, and the method or algorithm adopted when determining the historical service quality of the service and the type of the generated historical service quality can be customized, which is not specifically limited in the embodiment of the present application.

And thirdly, the data analysis network element acquires the network data of the service at the user level or the flow level, and acquires the historical service quality of the service according to the network data of the user level or the flow level.

The network Data at the user level or the Flow level refers to network Flow Data corresponding to a single service process of each user, where the network Flow may specifically be a quality of service (QoS) Flow (Flow) in a 5G network, and the network Flow Data may specifically include quality of service (QoS) parameters provided by a network device for the single service process of the user, such as a Guaranteed Flow Bit Rate (GFBR), a Maximum Flow Bit Rate (MFBR), an Uplink or Downlink Maximum Packet Loss Rate (Uplink or Downlink Maximum Packet Loss Rate, UL or DL Max PLR), a Packet Delay (Packet Delay, PDB), a Packet Error Rate (Packet Error Rate, PER), an Average Window Size (Average), and a Maximum number of Data bursts (Volume).

Specifically, the present approach can be divided into three execution phases:

stage one: the data analysis network element obtains a single-user service quality model of the service, namely a user-level service quality model, wherein the model refers to a variation relation between the service quality of the service at the user level and network data at the user level or the flow level.

For example, the data analysis network element may obtain the single-user service quality model of the service through the following two steps:

A. the data analysis network element obtains the training data of the service, wherein the training data corresponds to the service quality data of the user level and the network data of the user level or the stream level.

The data analysis network element firstly collects data from network elements such as a service server (such as an AF), an access network element (such as a RAN), a user plane function network element (such as a UPF), a terminal device (such as a UE), a mobility management function network element (such as an AMF), a session management function network element (such as an SMF), a policy control function network element (such as a PCF) and the like, and then associates the data of each network element through information such as a service identifier, a service flow identifier, a terminal identifier, a session identifier where the service flow is located, an association identifier which is provided on each network element, time and the like, so as to obtain complete training data. The training data includes:

(1) And the service quality data of the user level come from the service server.

The user-level quality of service data includes at least one single-user quality of service data, wherein the content of the single-user quality of service data may be specifically described with reference to the first embodiment, and will not be repeated here.

(2) Other time-varying parameter data affecting quality of service data at the user level, i.e. network data at the user level or at the stream level. The method comprises the following steps:

i. TCP congestion window data, TCP receive window data, jitter buffer data, media coding type and coding rate data, buffer data, data of at least one data type from an AF network element;

bit rate data, packet loss rate data, time delay data, radio channel quality data, data of at least one data type from a RAN network stream;

stream bit rate data, packet loss rate data, time delay data, data of at least one data type from a UPF network element;

streaming bit rate data, packet loss rate data, time delay data, data of at least one data type, TCP congestion window data, TCP receive window data, jitter buffer data, media coding type and coding rate data, buffer data, CPU occupancy, memory occupancy data of at least one data type from the UE;

v. and so on.

It should be noted that the network data at the user level or the stream level may also include the network data after the normalization processing, and the embodiment of the present application is not particularly limited to this.

B. Exemplarily, the data analysis network element obtains a relation model between the service quality data at the user level and the network data at the user level or the stream level, i.e. a service experience model of a single user, based on a Linear Regression (Linear Regression) method, as follows

h(x)＝w ₀ x ₀ +w ₁ x ₁ +w ₂ x ₂ +w ₃ x ₃ +…+w _D x _D (formula 1.1)

In the formula (1.1), h (x) is the service quality of a user level of a certain service, for example, the MOS value of a voice service of a single user; x = (X) ₁ ，x ₂ ，x ₃ ，……，x _D ) For feature vectors, exemplary, x ₁ Which is indicative of the time delay,x ₂ indicates packet loss rate, x ₃ Identifying stream bit rate, \8230;, x _D Identifying TCP congestion Window, x ₀ Is a constant of 1; w = (W) ₁ ，w ₂ ，w ₃ ，……，w _D ) Is a vector of parameters, also called weight vector, w _i The magnitude of the weight representing the impact of the ith parameter on the quality of service at the user level.

The linear regression is only an exemplary data analysis algorithm, and the data analysis network element may obtain a service experience model of a single user based on other algorithms, which is not specifically limited in the present invention.

And a second stage: and the data analysis network element acquires the service quality data of the user level according to the existing single-user service quality model and the network data of the user level or the stream level.

It should be noted that the difference between the network data at the user level or the flow level in the second stage and the network data at the user level or the flow level in the first stage is that the former is generated after the latter, that is, the network data at the user level or the flow level in the first stage is the historical data of the network data at the user level or the flow level in the second stage, and thus it can be inferred that the user-level quality of service data corresponding to the network data at the user level or the flow level in the first stage is also the historical data of the user-level quality of service data corresponding to the network data at the user level or the flow level in the second stage. In addition, the difference between the user-level quality of service data in stage one and stage two is that the former is obtained by the data analysis network element from the service server, and the latter is obtained by the data analysis network element itself.

Specifically, if the data analysis network element already knows h (X) = model in the above equation (1.1), then X = (X) according to the argument X at the subsequent point in time ₁ ，x ₂ ，x ₃ ，……，x _D ) The data analysis network element can calculate a specific value of h (x) corresponding to a subsequent time point, for example, h (x) is MOS =3 of a voice service, and the value of h (x) is the deduced service quality of a single user. Multiple applications of the process The service quality data of a large number of single users is taken to form the service quality data of the user level.

In the method described in this stage, after the data analysis network element obtains the stable single-user service quality model by the stage one method, the data analysis network element can use the network data at the user level or the stream level to reversely deduce the service quality data at the corresponding user level.

And a third stage: and the data analysis network element acquires the historical service quality of the service according to the historical service quality data of the user level acquired in the second stage.

In this stage, how the network element analyzes the data in this stage obtains the historical quality of service of the service according to the historical quality of service data of the user level may specifically refer to the second manner described above, and this is not repeated here. The only difference is that the source of the user-level quality of service data is different, and in the second mode, the user-level quality of service data originates from the service server, and here originates from the data analysis network element itself generated in stage two.

And fourthly, the data analysis network element acquires the historical service quality of the service from other network elements with the data analysis function.

For example, when the data analysis network element in this embodiment is a network element (e.g., MDAS) having a data analysis function in the network management system, the data analysis functional network element may obtain the historical service quality of the service from the data analysis functional network element (e.g., NWDAF) in the control plane of the core network.

Before sending the historical service quality of the service to the data analysis network element, the other network elements with the data analysis function may obtain the historical service quality of the service by using any one of the first, second, and third methods, which is not described herein again.

In some embodiments, the other network element with data analysis function may actively send the historical quality of service data of the service to the data analysis network element;

in other embodiments, the data analysis network element sends request information for obtaining the historical qos data of the service to the other network element with the data analysis function, so that the historical qos data of the service can be sent to the data analysis network element when the request information is received by the other network element with the data analysis function.

Wherein, optionally, the request information is generated by the data analysis network element according to the service quality requirement of the sliced network list in step 201. For example, the MDAS receives the information of the quality of service requirement of the slice list as shown in table 2 via step 201, then the MDAS requests the following information from the NWDAF: historical service quality data corresponding to the voice service of the slice network 1, historical service quality data corresponding to the video service of the slice network 1, historical service quality data corresponding to the voice service of the slice network 2, historical service quality data corresponding to the video service of the slice network 2, historical service quality data corresponding to the voice service of the slice network 3, and historical service quality data corresponding to the video service of the slice network 3.

Or, optionally, the request information is generated by the data analysis network element according to the priority information and/or the traffic priority information of the sliced network sent in 201. For example, if the MDAS receives the priority information and the traffic priority information of the slice network as shown in table 11 in step 201, the MDAS may decide to request historical quality of service data corresponding to the slice network priority less than 2 and the traffic priority less than 1 from the NWDAF based on the information, that is, the MDAS requests the following information from the NWDAF: historical service quality data corresponding to the service 1 of the slicing network 1 and historical service quality data corresponding to the service 1 of the slicing network 2. Optionally, the historical quality of service of the sliced network requested by the data analysis network element in the request information corresponds to the network configuration information of the sliced network list sent by the data analysis network element to the policy control network element in step 202.

It should be noted that, when the data analysis network element obtains the spatial information in the historical service quality data and the spatial information in the historical network data at the stream level may be inconsistent, for example, the former is GPS spatial information, and the latter is cell identification information, the data analysis network element may establish a mapping relationship between the two different spatial information by using the associated identification information of the user, which is commonly included in the historical service quality data and the historical network data at the stream level. Thereafter, the data analysis network element may train the business experience model based on one of the spatial information.

In the foregoing, by taking a service in a slice network as an example, how a data analysis network element obtains historical service quality data of each slice network in a slice network list is described. On this basis, the data analysis network element obtains the historical network configuration information of each slice network corresponding to the historical service quality data of each slice network in the slice network list. For example, for one of the slice networks, the data analysis network element may associate, through the time information, historical network configuration information of the slice network corresponding to the service quality of the slice network at a historical time point (for example, eight morning points, the satisfaction of the voice service user of the slice network 1 is 80% and the satisfaction of the video service is 90%). The historical network configuration information of the slice network can be obtained from a network management network element or other network function network elements. The historical network configuration information of the slice network includes historical measurement data or historical performance data on the corresponding interfaces between the network slice end-to-end, single network element devices or network element devices, and the specific content thereof is described in detail in step 202. For another example, for one of the slice networks, the data analysis network element may associate, through the spatial information, historical network configuration information of the slice network corresponding to the service quality of the slice network in a certain space (e.g., the satisfaction of the voice service user of the cell 1 slice network 1 is 80% and the satisfaction of the video service is 90%). In addition, for one of the slice networks, the data analysis network element may associate, through the spatial information and the time information, historical network configuration information of the slice network corresponding to the service quality of the slice network at a certain spatial time (for example, the satisfaction of the voice service of the 1-slice network 1 at eight cells in the morning is 80% and the satisfaction of the video service is 90%). The historical network configuration information of the slice network can be obtained from a network management network element or other network function network elements. The historical network configuration information of the slice network includes historical measurement data or historical performance data on the corresponding interfaces between the network slice end-to-end, single network element devices or network element devices, and the specific content of the historical network configuration information is explained in step 202.

In the following, for a service in a slice network, how a data analysis network element determines a network configuration corresponding to the service in the slice network is described:

the data analysis network element may train a training model for the service of the slice network by using historical service quality data of the service in the slice network and historical network configuration information data of the slice network, where the training model refers to a functional relationship that the service quality of the service changes with the network configuration information of the slice network.

Illustratively, the training model obtained by the data analysis network element based on a linear regression method is as follows:

g(y)＝w ₀ y ₀ +w ₁ y ₁ +w ₂ y ₂ +w ₃ y ₃ +…+w _D y _D (formula 1.2)

g (y) represents the service quality of the service, such as the user satisfaction degree of the service, namely the proportion of users meeting the service quality requirement of the single user of the service. Y = (Y) in equation 1.2 ₁ ，y ₂ ，y ₃ ，……，y _D ) The feature vector refers to network configuration information that affects the quality of service of the service, where the network configuration information refers to network parameter settings of the slice network and network elements related to the slice network, and the network configuration information may be collected by the data analysis network element from a network management network element or directly collected from the network elements related to the slice network. Exemplary, y ₁ Represents the uplink packet loss ratio, y, of the next generation radio access network (NG RAN) ₂ Means average delay over the air interface, y ₃ Indicating N6 interface uplink/downlink usage. W = (W) ₁ ，w ₂ ，w ₃ ，……，w _D ) Is a parameter vector, also called weight vector identification, w _i Identifying the ith parameter y in network configuration information _i The size of the weight that affects the quality of service for the service.

To illustrate, the results obtained by model trainingEigenvector Y = (Y) ₁ ，y ₂ ，y ₃ ，……，y _D ) The type of the network configuration information in (2) may be included in the type of the slice historical network configuration information, i.e. is a subset of the set of types of the historical network configuration information. For example, the data analysis network element acquires 100 types of network configuration information of the slice network from the network management network element, but after model training, it is known that 50 types of network configuration information affect the service quality of the service of the slice network, and then the 50 types of network configuration information are the feature vectors,

after the training model is obtained, according to the model and the service quality requirement of the service in the slice network, the data analysis network element obtains network configuration information meeting the requirement, wherein the network configuration information means that if the network management network element performs network setting on the slice network according to the network configuration information, the service of the slice network can meet the service quality requirement corresponding to the service.

For example, suppose that the service quality requirement of the service of the slice network is that the user satisfaction is greater than 95%, i.e., the requirement g (y)>95%, then the data analysis network element can obtain g (y) according to the above formula 1.2>95% corresponding Y = (Y) ₁ ，y ₂ ，y ₃ ，……，y _D ) The specific value of the feature vector.

The above-mentioned determining, according to the training model, the value of the feature vector corresponding to the service quality requirement belongs to a multi-objective decision making (MCDM) problem, and the data analysis network element may obtain the value of the feature vector based on the existing MCDM method. Generally speaking, a plurality of sets of combinations of feature vectors satisfying the service quality requirement can be obtained, that is, a plurality of sets of corresponding network configuration information can be obtained.

The above describes how a data analysis network element determines a network configuration corresponding to a service in a slice network. For multiple services in a slice network, the data analysis network element can obtain training models corresponding to the multiple services, such as g, according to a similar method _i (y)：

g _i (y)＝w _i0 y ₀ +w _i1 y ₁ +w _i2 y ₂ +w _i3 y ₃ +…+w _iD y _D (formula 1.3)

Where formula 1.3 represents a training model corresponding to the ith service in the slice network, Y = (Y) ₁ ，y ₂ ，y ₃ ，……，y _D ) Indicates the corresponding network configuration information of the slice network, wherein y is indicated ₁ -y _D One parameter affects the quality of service of each service in the sliced network. G corresponding to the service i _i (y) model and g _i (Y) requirement, the data analysis network element can obtain Y = (Y) meeting the requirement ₁ ，y ₂ ，y ₃ ，……，y _D ) And possibly multiple different sets of values for the solution.

For a scenario where there are multiple slice networks in a slice list and each slice network has multiple services, the method for the data analysis network element to obtain the corresponding network configuration information of the slice list is similar to that described above. The method is described in detail below by taking the service quality requirements of the sliced network list shown in table 2 as an example:

exemplarily, by using the similar linear regression method, the data analysis network element obtains a plurality of corresponding service training models for a plurality of services in the slice network list listed in table 2 as illustrated in the following table:

TABLE 14

Wherein: (y) ₀ ，y ₁ ，y ₂ ，y ₃ ，…，y _h ) Is a feature vector affecting the video service of the slice network 1;

(y ₀ ，y ₁ ，y ₂ ，y ₃ ，…，y _i ) Is a feature vector that affects the voice service of the slice network 1;

(y ₀ ，y ₁ ，y ₂ ，y ₃ ，…，y _j ) Is a feature vector affecting the video service of the slice network 2;

(y ₀ ，y ₁ ，y ₂ ，y ₃ ，…，y _k ) Is a feature vector affecting the voice service of the network-on-chip 2;

(y ₀ ，y ₁ ，y ₂ ，y ₃ ，…，y _p ) Is a feature vector that affects the video service of the slice network 3;

(y ₀ ，y ₁ ，y ₂ ，y ₃ ，…，y _q ) Are feature vectors that affect the slicing network 3 voice traffic.

The feature vectors of the slice networks 1,2,3 may constitute a total feature vector Y = (Y) ₀ ，y ₁ ，y ₂ ，y ₃ ，…，y _h ，…，y _i ，…，y _j ，…，y _k ，…，y _q )。

Corresponding to the service quality requirements of the slice network list listed in table 2, the data analysis network element obtains multiple sets of solutions meeting the service quality requirements by using multiple models in table 14 as indicated by the following table, that is, obtains multiple sets of network configuration information corresponding to the service quality requirements:

watch 15

In table 15:

Y1＝(y ₁₀ ，y ₁₁ ，y ₁₂ ，y ₁₃ ，…，y _1h ，…，y _1i ，…，y _1j ，…，y _1k ，…，y _1q )；

Y2＝(y ₂₀ ，y ₂₁ ，y ₂₂ ，y ₂₃ ，…，y _2h ，…，y _2i ，…，y _2j ，…，y _2k ，…，y _2q )；

Y3＝(y ₃₀ ，y ₃₁ ，y ₃₂ ，y ₃₃ ，…，y _3h ，…，y _3i ，…，y _3j ，…，y _3k ，…，y _3q )。

y1, Y2, Y3 are three groups of specific values of the above total eigenvector, i.e., three groups of solutions satisfying the six service quality requirements listed in table 2, i.e., network configuration parameters of the slice networks 1,2, 3. If the configuration is performed according to the value of the vector listed in Y1, the 6 service quality requirements in the slice list combination can be simultaneously satisfied, and the meanings of Y2 and Y3 are similar. To illustrate, the network configuration parameter of the slice network 1 referred to herein is (y) ₀ ，y ₁ ，y ₂ ，y ₃ ，…，y _h ，…，y _i ) And the network configuration parameter of the slice network 2 is (y) ₀ ，y ₁ ，y ₂ ，y ₃ ，…，y _j ，…，y _k ) The network configuration parameter of the slice network 3 is (y) ₀ ，y ₁ ，y ₂ ，y ₃ ，…，y _p ，…，y _q ) And Y1 is a set of values for all network configuration parameters contained in the slice networks 1,2,3, and Y2, Y3 have similar meanings. After receiving Y1, the network management device can determine that the network configuration parameter of the slice network 1 is (Y) ₀ ，y ₁ ，y ₂ ，y ₃ ，…，y _h ，…，y _i ) And the network configuration parameter of the slice network 2 is (y) ₀ ，y ₁ ，y ₂ ，y ₃ ，…，y _j ，…，y _k ) The network configuration parameter of the slice network 3 is (y) ₀ ，y ₁ ，y ₂ ，y ₃ ，…，y _p ，…，y _q )。

To illustrate, in the embodiment, it is assumed that the slice networks 1,2,3 share some network resources, such as access network resources, AMF resources, etc.,and different services in each slice network are influenced by the configuration of the common resource parameters, so that the same element y exists in the characteristic vectors ₀ ，y ₁ ，y ₂ ，y ₃ Is not shown in (1). Of course, the present application does not limit whether resources are shared between different slice networks, nor does it limit whether network resources are shared between different services in the same slice network. When different slicing networks do not share network resources, common elements do not appear in the feature vectors of the services of different slices, and when different services do not share network resources in the same slicing network, common elements do not appear in the feature vectors of different services.

For a scenario in which there are multiple slice networks in a slice list, and each slice network has multiple services of multiple user types, the method for the data analysis network element to obtain the corresponding network configuration information of the slice list is similar to that described above. The method is described in detail below by taking the service quality requirements of the sliced network list shown in table 5 as an example:

Illustratively, with the above similar linear regression method, the data analysis network element obtains a plurality of corresponding service training models for a plurality of services in the slice network list listed in table 5, as illustrated in the following table:

TABLE 16

Wherein:

(y ₀ ，y ₁ ，y ₂ ，y ₃ ，…，y _h ) The feature vectors of the video service of the gold medal user in the slicing network 1 are influenced;

(y ₀ ，y ₁ ，y ₂ ，y ₃ ，…，y _i ) The feature vectors are the feature vectors influencing the video service of the tile network 1 bank card user;

(y ₀ ，y ₁ ，y ₂ ，y ₃ ，…，y _j ) Is a feature vector affecting the gold medal user voice service of the slice network 1;

(y ₀ ，y ₁ ，y ₂ ，y ₃ ，…，y _k ) Is the feature vector that affects the voice traffic of the slice network 1 bank user, and so on.

The feature vectors of the slice networks 1,2,3 may constitute a total feature vector Y = (Y) ₀ ，y ₁ ，y ₂ ，y ₃ ，…，y _h ，…，y _i ，…，y _j ，…，y _k ，…，y _p ，…，y _q ，…，y _r ，…，y _s ，…，y _t ，…，y _u ，…，y _v ，…y _w )。

Corresponding to the service quality requirements of the slice network list listed in table 5, the data analysis network element obtains, by using the multiple models in table 16 above, multiple sets of solutions that satisfy the service quality requirements, as indicated in the following table, that is, multiple sets of network configuration information corresponding to the service quality requirements are obtained:

TABLE 17

In table 17:

Y4＝(y ₄₀ ，y ₄₁ ，y ₄₂ ，y ₄₃ ，…，y _4h ，…，y _4i ，…，y _4j ，…，y _4k ，…，y _4p ，…，y _4q ，…，y _4r ，…，y _4s ，…，y _4t ，…，y _4u ，…，y _4v ，…y _4w )

Y5＝(y ₅₀ ，y ₅₁ ，y ₅₂ ，y ₅₃ ，…，y _5h ，…，y _5i ，…，y _5j ，…，y _5k ，…，y _5p ，…，y _5q ，…，y _5r ，…，y _5s ，…，y _5t ，…，y _5u ，…，y _5v ，…y _5w )。

y4 and Y5 are two specific values of the total eigenvector, that is, two solutions meeting the quality of service requirements of the two user types listed in table 5, that is, network configuration parameters of the slice networks 1,2 and 3. If the configuration is performed according to the value of the vector listed in Y4, the 12 qos requirements in the slice list combination can be simultaneously satisfied, and Y5 has a similar meaning. To illustrate a point, (y) ₀ ，y ₁ ，y ₂ ，y ₃ ，…，y _h ) Is a feature vector affecting the video service of the gold medal user in the slicing network 1; (y) ₀ ，y ₁ ，y ₂ ，y ₃ ，…，y _i ) The feature vectors are the feature vectors influencing the video service of the tile network 1 bank card user; (y) ₀ ，y ₁ ，y ₂ ，y ₃ ，…，y _j ) Is a feature vector affecting the gold medal user voice service of the slice network 1; (y) ₀ ，y ₁ ，y ₂ ，y ₃ ，…，y _k ) Is the feature vector affecting the voice service of the banker user of the network slice 1, the network configuration parameter related to the network slice 1 is the combination of the above four feature vectors, and so on. And Y4 is a set of values for all network configuration parameters contained in the slice networks 1,2,3, and Y5 has a similar meaning. The network management device can determine that the network configuration of the related slicing network 1 is (Y) after receiving Y4 ₀ ，y ₁ ，y ₂ ，y ₃ ，…，y _i )+(y ₀ ，y ₁ ，y ₂ ，y ₃ ，…，y _h )+(y ₀ ，y ₁ ，y ₂ ，y ₃ ，…，y _j )+(y ₀ ，y ₁ ，y ₂ ，y ₃ ，…，y _k ) And so on. .

To illustrate, in this embodiment, it is assumed that the slice networks 1,2,3 share some network resources, such as access network resources, AMF resources, etc., and different services in each slice network are affected by the configuration of these common resource parameters, so that several characteristics mentioned above appearIn amounts of the same element y ₀ ，y ₁ ，y ₂ ，y ₃ Is not shown in (1). Of course, the present application does not limit whether resources are shared between different slice networks, nor does it limit whether network resources are shared between different services in the same slice network. When different slice networks do not share network resources, common elements do not appear in the feature vectors of the services of different slices, and when different services in the same slice network do not share network resources, common elements do not appear in the feature vectors of different services.

One point is explained: the linear regression algorithm is only a specific example algorithm of the model related to training of the data analysis network element, and the data analysis network element may also perform training of the model and seek network configuration information based on other algorithms, which is not limited in this patent.

In addition, the data analysis network element trains a corresponding model for each user type corresponding to one service in one slice, for example, a gold user of the voice service of the slice network 1 trains a model, and a silver user of the voice service of the slice network 1 trains a model. In other algorithm designs, the data analysis network element may aggregate two user types to generate a comprehensive model expressing a variation relationship between the aggregated service satisfaction of all user types and the network configuration information of the slice network, where the aggregated service satisfaction of all user types may be an index expressing the service quality of a service defined by the data analysis network element itself or acquired from the policy control network element. See in particular the schematic methods below:

watch 18

In Table 18, the objective function f _i (y) isThe aggregated service satisfaction of all user types corresponding to the slice network i, for example, the data analysis network element may use the weighted service satisfaction of each type of user as the aggregated service satisfaction, specifically, the weight of the user satisfaction of each type is a proportion of the number of users of the type to the total number of users, and assuming that the number of gold medals users accounts for 30% of the total number of users and the number of silver medals users accounts for 70% of the total number of users, the aggregated satisfaction may be defined as 30% x gold medal user service satisfaction +70% x silver medal user service satisfaction. The left Y eigenvector is the eigenvector that affects the value of the objective function, and has similar meaning as before.

Before the process of training the model, firstly, a data analysis network element obtains historical service satisfaction degree data corresponding to gold and silver users in historical service quality data of the slice network, and then, historical aggregation satisfaction degree data of the slice network is calculated according to the definition of the aggregation satisfaction degree, and the historical aggregation satisfaction degree data is used as the objective function value f _i (y) for the model training process, and finally the data analysis network element may obtain the function model illustrated in table 18 above.

Wherein:

(y ₀ ，y ₁ ，y ₂ ，y ₃ ，…，y _a ) Is a feature vector affecting the video service of the slice network 1;

(y ₀ ，y ₁ ，y ₂ ，y ₃ ，…，y _b ) Is a feature vector affecting the voice service of the slice network 1;

(y ₀ ，y ₁ ，y ₂ ，y ₃ ，…，y _c ) Is a feature vector affecting the video service of the slice network 2;

(y ₀ ，y ₁ ，y ₂ ，y ₃ ，…，y _d ) Is the feature vector that affects the voice traffic of the slice network 2, and so on.

And the eigenvectors of the slicing network 1,2,3 may constitute a total eigenvector Y = (Y) ₀ ，y ₁ ，y ₂ ，y ₃ ，…，y _a ，…，y _b ，…，y _c ，…，y _d ，…，y _e ，…，y _f )。

After acquiring service quality requirements corresponding to multiple user types of the service of one slice network from a policy control network element, a data analysis network element may also calculate an aggregated service quality requirement of the service according to similar definitions, assuming that the gold token user number accounts for 30% of the total user number and the silver token user accounts for 70% of the total user number, and assuming that, according to the requirements shown in table 5, the gold token user service satisfaction requirement of the voice service of the slice network 1 is that a user proportion of MOS >3 is >95%, and the silver token user service satisfaction of the voice service of the slice network 1 is that a user proportion of MOS >3 is >90%, then the data analysis network element acquires the aggregated service quality requirement of 30% × 95% × 70% × 90=91.5, that is, the user proportion of MOS >3 is greater than 91.5%.

According to each f already acquired _i (y) model, and corresponding aggregate qos requirements, the data analysis network may obtain multiple sets of solutions that satisfy the aggregate qos requirements as follows:

watch 19

In table 19:

Y6＝(y ₆₀ ，y ₆₁ ，y ₆₂ ，y ₆₃ ，…，y _6a ，…，y _6b ，…，y _6c ，…，y _6d ，…，y _6e …，y _6f )；

Y7＝(y ₇₀ ，y ₇₁ ，y ₇₂ ，y ₇₃ ，…，y _7a ，…，y _7b ，…，y _7c ，…，y _7d ，…，y _7e …，y _7f )

y6 and Y7 are two groups of specific values of the total eigenvector, namely satisfying each slicing networkTwo sets of solutions for the aggregate qos requirements for each service, namely the network configuration parameters for the sliced network 1,2, 3. To illustrate, the network configuration parameter of the slice network 1 referred to herein is (y) ₀ ，y ₁ ，y ₂ ，y ₃ ，…，y _a ，…，y _b ) And the network configuration parameter of the slice network 2 is (y) ₀ ，y ₁ ，y ₂ ，y ₃ ，…，y _c ，…，y _d ) The network configuration parameter of the slice network 3 is (y) ₀ ，y ₁ ，y ₂ ，y ₃ ，…，y _e ，…，y _f ) And Y6 is a set of values for all network configuration parameters contained in the slice networks 1,2,3, Y7 having a similar meaning. The network management device, after receiving Y6, can determine that the network configuration parameter of the slice network 1 is (Y) ₀ ，y ₁ ，y ₂ ，y ₃ ，…，y _a ，…，y _b ) And the network configuration parameter of the slice network 2 is (y) ₀ ，y ₁ ，y ₂ ，y ₃ ，…，y _c ，…，y _d ) The network configuration parameter of the slice network 3 is (y) ₀ ，y ₁ ，y ₂ ，y ₃ ，…，y _e ，…，y _f )。

To illustrate, in the embodiment, it is assumed that the slice networks 1,2,3 share some network resources, such as access network resources, AMF resources, etc., and different services in each slice network are affected by the common resource parameter configuration, so that the same element y appears in the above feature vectors ₀ ，y ₁ ，y ₂ ，y ₃ The phenomenon of (2). Of course, the present application does not limit whether resources are shared between different slice networks, nor does it limit whether network resources are shared between different services in the same slice network. When different slice networks do not share network resources, common elements do not appear in the feature vectors of the services of different slices, and when different services in the same slice network do not share network resources, common elements do not appear in the feature vectors of different services.

The method illustrated in table 18 illustrates a process of training a synthetic model of a slice network by a data analysis network element for a scenario where a slice network corresponds to service quality requirements of multiple user types.

In other embodiments, for a scenario with multiple quality of service requirements corresponding to one service in one slice network, for example, the example in table 3, the data analysis network element may also train a comprehensive model corresponding to one service in one slice network, and optionally, the implementation method may be similar to the method referred to in table 18.

In other embodiments, when quality of service requirements of different service types are included in one slicing network, for example, in the scenario illustrated in table 2, the data analysis network element may also train a comprehensive model corresponding to one slicing network, and optionally, the implementation method may be similar to the method referred to in table 18.

In other embodiments, when a slicing network includes service quality requirements corresponding to different spatial information, for example, in the scenario illustrated in table 6, the data analysis network element may also train a comprehensive model corresponding to the slicing network, and optionally, the implementation method may be similar to the method referred to in table 18.

In other embodiments, when the service quality requirements of different time information included in one slice network, for example, the scenario illustrated in table 7, the data analysis network element may also train a comprehensive model corresponding to one slice network, and optionally, the implementation method may be similar to the method referred to in table 18.

In other embodiments, when a slicing network includes service quality requirements corresponding to any one or more dimensions of different user types, service types, time information, and spatial information, the data analysis network element may also train a comprehensive model corresponding to the slicing network, and optionally, the implementation method may be similar to the method referred to in table 18.

In some embodiments, the policy control network element may further send the slice network priority information and/or the traffic priority information and/or the user type priority information to the data analysis network element.

In some embodiments, the policy control network element may further send the corresponding quality of service requirements of all the sliced networks to the data analysis network element.

The information of the slice network priority information and/or the service priority information and/or the user type priority information, and the information of the corresponding service quality requirements of all slice networks may or may not be included in the request information of step 201, and there is no chronological order with the transmission of the request information.

The data analysis network element determines that when the service quality requirements of the slice network list are met, the service quality requirements of the slice network/service/user types of the slice network list are met as much as possible according to the priority.

For example, if the data analysis network element is connected to Y1, Y2 and Y3 in the above method, but Y1 meets the quality of service requirement corresponding to the slice network with the high priority in the slice network list, then the data analysis network element sets the use priority of Y1 higher. The policy control network element and the network management network element preferentially use Y1 as network configuration information for configuring the slice network.

The specific contents of the network configuration information will be described below.

Each set of network configuration information in the one or more sets of network configuration information may include at least one network configuration parameter.

If each set of network configuration information only includes one network configuration parameter, the network configuration parameter may be one of a performance parameter or a specific setting parameter.

If each set of network configuration information includes a plurality of network configuration parameters, each of the plurality of network configuration parameters may be one of a performance parameter or a specific setting parameter.

The performance parameter refers to a requirement for a certain performance index in the network. The network management element performs internal processing accordingly to meet the performance index requirement. For example, the end-to-end delay of a network slice is a performance parameter, and a network management network element performs internal resource setting according to a delay requirement to meet the delay requirement. For example, a Key Performance Indicator (KPI) of a network slice defined in the current standard is a specific example of a performance parameter

The specific setting parameter refers to a parameter according to which the network management network element can directly perform network setting. For example, the number of access network cache resources and the antenna tilt angle are two setting parameters. The network management network element directly sets the number of access network cache resources and the antenna inclination angle according to the method.

Examples of some specific network configuration parameters included in the network configuration information are listed in the following table, and the network configuration information includes, but is not limited to, the network configuration parameters listed in the following table.

Watch 20

In some embodiments, the method shown in fig. 2 may further include step 203.

203, the policy control network element may further send the received network configuration information corresponding to the slice network list to a network management network element. Correspondingly, the network management network element receives the network configuration information corresponding to the slice network list sent by the policy control network element.

As indicated above, the network configuration information corresponding to the sliced network list may include one or more sets of network configuration information.

In some embodiments, the policy control network element may send all network configuration information included in the received network configuration information corresponding to the sliced network list to the network management network element. In other words, if the network configuration information corresponding to the slice network list includes multiple sets of network configuration information, the policy control network element may send the multiple sets of network configuration information to the network management network element.

In some embodiments, the policy control network element may send a set of network configuration information included in the received network configuration information corresponding to the sliced network list to the network management network element. For convenience of description, a set of network configuration information in the network configuration information corresponding to the sliced network list that is sent to the network management element is referred to as first target network configuration information hereinafter.

In some embodiments, the policy control network element may further receive an applicable condition corresponding to the network configuration information sent by the data analysis network element. The applicable condition may include a time, a place, and the like, to which each set of network configuration information is applicable. The applicable condition may be sent to a network management element along with the network configuration information. The applicable condition may be included as part of the network configuration information or as an additional information.

It can be understood that, if the network configuration information corresponding to the sliced network list only includes one set of network configuration information, the first target network configuration information is the set of network configuration information included in the network configuration information corresponding to the sliced network list.

If the network configuration information corresponding to the sliced network list includes multiple sets of network configuration information, the first target network configuration information may be determined according to multiple ways.

In some embodiments, the policy control network element may determine that any one of the sets of network configuration information is the first target network configuration information.

In some embodiments, if the policy control network element receives the applicable condition of the network configuration information sent by the data analysis network element, the policy control network element may determine, according to the applicable condition of the network configuration information, that one of the multiple sets of network configuration information is the first target network configuration information. The first target network configuration information may be network configuration information applicable at the current time or place.

In other embodiments, when the policy control network element receives the configuration effect information sent by the data analysis network element, the policy control network element may determine, according to the configuration effect information, that one of the multiple sets of network configuration information is the first target network configuration information. The first target network configuration information may be a set of network configuration information that achieves the best quality of service effect. The effect of achieving the best service quality may be that all the slice networks in the slice network list can achieve the best service quality effect, or that a specified slice network or a specified service in the slice network list can achieve the best service quality effect. The designated slicing network may be determined according to a slicing network priority. That is, the policy control network element may determine the first target network configuration information according to the slice network priority information. For example, the slicing network with the highest slicing network priority is the designated slicing network. The specified service may be determined according to a service priority. That is, the policy control network element may determine the first target network configuration information according to the service network priority information. For example, the service with the highest priority of the service is the designated service.

Taking table 13 as an example, assuming that the first target network configuration information is such that the sliced network with the highest sliced network priority can achieve the best quality of service effect and assuming that the sliced network 1 has the highest priority, the first target network configuration information may be Y1.

Also taking table 13 as an example, assuming that the first target network configuration information is such that the service with the highest service priority can achieve the best service quality effect and assuming that the priority of the voice service is the highest, the first target network configuration information may be Y2, because Y2 enables the service quality effect of the voice service of the slice network 2 to be the highest.

Of course, the policy control network element may also determine the first target network configuration information according to the service priority information and the slice network priority information. For example, the first target network configuration information is such that the highest traffic priority service in the sliced network with the highest sliced network priority can achieve the best traffic quality. Also taking table 13 as an example, it is assumed that the slicing network priority of the slicing network 1 is the highest, and the service priority of the voice service is the highest. In this case, the first target network configuration information may be Y2.

In other embodiments, in a case that the policy control network element may further receive the usage priority information of the network configuration information sent by the data analysis network element, the policy control network element may directly select the first target network configuration information according to the usage priority of each set of network configuration information. The first target network configuration information may be network configuration information using a highest priority among the plurality of sets of network configuration information.

In the above embodiment, the first target network configuration information may be one of the plurality of sets of network configuration information. In other embodiments, the first target network configuration information may also be multiple sets of network configuration information. For example, assume a corresponding S for each slice network ₁ Group network configuration information, the first target network configuration information may be the S ₁ S in group network configuration information ₂ Group network configuration information, wherein S ₁ Is a positive integer greater than 2, S2 is greater than or equal to 1 and less than or equal to S ₁ Is a positive integer of (1). The method for determining that the plurality of sets of network configuration information are the first target network configuration information may refer to the above method for determining that the set of network configuration information is the first target network configuration information, and is not described herein again.

In some embodiments, the method shown in fig. 2 may further include step 204.

204, the network management element sends notification information to the policy control element, where the notification information is used to notify the policy control element that the network management element cannot perform network configuration according to the network configuration information corresponding to the slice network list. Correspondingly, the policy control network element receives the notification information sent by the network management network element.

In some embodiments, the network management element may send the notification information according to that the access network resources and/or the core network resources cannot satisfy the network configuration information corresponding to the slice network list.

In some embodiments, before step 204, the policy control network element may further send first indication information to the network management network element, where the first indication information is used to indicate that the network management network element sends the notification information to the policy control network element when the network management network element cannot perform network configuration according to the corresponding network configuration information of the slice list. Accordingly, the network management element receives the first indication before step 204.

In some embodiments, when the network management network element receives the network configuration information corresponding to the sliced network list sent by the policy control network element, if the network management network element determines that the network configuration information corresponding to the sliced network list cannot be used for network setting, the network management network element may immediately send notification information to the policy control network element. In other words, after receiving the network configuration information corresponding to the sliced network list, the network management network element will first determine whether the network configuration information corresponding to the sliced network list can be used for network setting, and send the notification information to the policy control network element if it is determined that the network configuration information corresponding to the sliced network list cannot be used for network setting.

In other embodiments, after receiving the network configuration information corresponding to the sliced network list sent by the policy control network element, if the network management network element determines that network setting cannot be performed according to the network configuration information corresponding to the sliced network list in the operation process of the sliced network, the network management network element may send notification information to the policy control network element. In other words, when the network management element receives the network configuration information corresponding to the sliced network list sent by the policy control element, the network management element may perform network setting according to the network configuration information corresponding to the sliced network list, but after the sliced network operates for a period of time, the network management element finds that the network setting cannot be performed according to the network configuration information corresponding to the sliced network list any more, and if the network resource is in short supply or the like, the network management element sends the notification information to the policy control element.

In some embodiments, the notification information further includes reason information indicating a reason why the network management element is unable to perform network configuration.

In some embodiments, before step 204, the policy control network element may further send second indication information to the network management network element, where the second indication information is used to indicate a reason why the network management network element cannot perform network configuration to the policy control network element when the network management network element cannot perform network configuration according to the corresponding network configuration information of the slice list. Accordingly, the network management element receives the second indication information before step 204.

In some embodiments, the reason information may specify which of the network configuration parameters in the network configuration information cannot be met, e.g., cannot meet average latency requirements or other network configuration parameters, examples of which are shown in table 20.

In other embodiments, the reason information may further indicate an internal reason that the network configuration parameters cannot be met, for example, the reason information may include that the average delay requirement cannot be met due to insufficient access network cache resources. And if the current user capacity cannot be borne due to insufficient CPU resources of the AMF, or if the N3 interface delay cannot meet the requirement due to insufficient link capacity of the N3 interface.

In some embodiments, the notification information may further include a network parameter measurement value corresponding to the sliced network list. The network parameter measurement value corresponding to the slice network list is the network parameter measurement value of the slice network in the slice network list. The network parameter measurement value may be a specific measurement value of all or part of the network configuration parameters listed in table 20, for example, a specific measurement value including an average delay, a downlink packet loss rate measurement value, an average or maximum Radio Resource Control (RRC) connection number measurement value, and the like.

In some embodiments, before step 204, the policy control network element may further send third indication information to the network management network element, where the third indication information is used to indicate that the network management network element sends the measured value of the network parameter corresponding to the sliced network list to the policy control network element when the network management network element cannot perform network configuration according to the network configuration information corresponding to the sliced network list. Accordingly, the network management element receives the third indication information before step 204.

In other embodiments, the network management element may send the notification information, the reason information, and/or the network parameter measurement value corresponding to the slice network list, respectively.

To explain this point, the embodiment of the present application does not exclude that, after receiving the network configuration information corresponding to the sliced network list sent by the policy control network element, the network management network element sends, to the policy control network element, notification information that network setting can be performed according to the network configuration information corresponding to the sliced network list, or sends notification information that network setting has been successfully performed according to the network configuration information corresponding to the sliced network list.

As described above, in some embodiments, the network configuration information corresponding to the slice network list sent by the policy control network element to the network management network element may be all network configuration information in a plurality of sets of network configuration information. In this case, after receiving the notification information sent by the network management network element, the policy control network element may request the data analysis network element to obtain the network configuration information corresponding to the sliced network list again, and send the newly obtained network configuration information corresponding to the sliced network list to the management network element.

In other embodiments, the network configuration information corresponding to the slice network list sent by the policy control network element to the network management network element may be one of multiple sets of network configuration information (i.e., the first target network configuration information). In this case, after receiving the notification information sent by the network management network element, the policy control network element may determine second target network configuration information, where the second target network configuration information is different from the first target network configuration information.

In some embodiments, the policy control network element may determine that any one of the sets of network configuration information other than the first target network configuration information is the second target network configuration information.

In other embodiments, when the policy control network element obtains the configuration effect information, the policy control network element may determine the second target network configuration information according to the configuration effect information, for example, the second target network configuration information is a group of network configuration information with the best service quality effect, except the first target network configuration information. Step 201 may be referred to specifically for a method for determining, by the policy control network element, the second target network configuration information according to the configuration effect information and the configuration effect information corresponding to the second target network configuration information, which is not described herein again.

In other embodiments, if the notification information further includes reason information, the policy control network element may determine the second target network configuration information according to the reason information. For example, if the reason information is that the average delay requirement cannot be met, the policy control network element may select another set of network configuration information with a lower average delay requirement as the second target network configuration information.

In other embodiments, if the notification information further includes a measurement value of the network configuration information, the policy control network element may determine the second target network configuration information according to the measurement value of the network configuration information. For example, if the specific measurement value of the average delay included in the notification information is 5ms, and the measurement value of the packet loss rate of the downlink data packet is 3%, the policy control network element selects a group of network configuration information having an average delay requirement of greater than 5ms and a downlink data packet loss rate requirement of greater than 3% as the second target network configuration information.

In some embodiments, the method shown in fig. 2 may further include step 205.

205. The policy control network element may request the data analysis network element to acquire network configuration information corresponding to another sliced network list, where the another sliced network list includes one or more sliced networks. Correspondingly, the data analysis network element sends network configuration information corresponding to another slice network list to the policy control network element.

In some embodiments, the network configuration information corresponding to the slice network list sent by the policy control network element to the network management network element may be all network configuration information in a plurality of sets of network configuration information. In this case, after receiving the notification information sent by the network management network element, the policy control network element may request the data analysis network element to obtain network configuration information corresponding to another slice network list, where the another slice network list includes one or more slice networks. Accordingly, the policy control network element may receive network configuration information corresponding to another sliced network list sent by the data analysis network element, where the network configuration information corresponding to the another sliced network list may also be one or more sets of network configuration information. The process of re-requesting and obtaining the network configuration information corresponding to another slice network list may reuse the method in steps 201 to 202, and is not repeated in a cycle.

In some embodiments, before requesting to obtain the network configuration information corresponding to another sliced network list, the policy control network element may determine the service quality requirement of the another sliced network list according to the sliced network priority information and/or the service priority information.

For convenience of description, the slice network list requested to acquire the network configuration information in step 201 is referred to as slice network list 1, and the other slice network list is referred to as slice network list 2.

In some embodiments, the policy control network element may determine the quality of service requirement of another sliced network list based on the slice priority information. Specifically, the policy control network element may determine the slice networks included in the slice network list 1 and the slice network list 2 according to the slice priority information, and further determine the service quality requirement of the slice network list 1 and the service quality requirement of the slice network list 2. The slicing networks included in the slicing network list 1 may be determined according to a first preset priority value, and the slicing networks included in the slicing network list 2 may be determined according to a second preset priority value. The first preset priority value and the second preset priority value refer to priority values in the slice network priority information. In some embodiments, the first predetermined priority value is greater than the second predetermined priority value. In this case, the slice netlist 2 may be a subset of the slice netlist 1. Also taking table 9 as an example, assuming that the first preset priority value is 3, the slice network list 1 includes slice network 1, slice network 2, slice network 3, and slice network 4. Assuming that the second preset priority value is 2, the slice network list 2 includes a slice network 1, a slice network 2, and a slice network 3.

In other embodiments, the policy control network element may determine the qos requirement of another sliced network list according to the service priority information. Specifically, the policy control network element may determine, according to the service priority information, a service included in the service quality requirement corresponding to each slice network in the service quality requirements of the slice network list 1 and a service included in the service quality requirement corresponding to each slice network in the service quality requirements of the slice network list 2, and further determine a service quality requirement of a service in the service quality requirement corresponding to each slice network in the service quality requirements of the slice network list 1 and a service quality requirement of a service in the service quality requirement corresponding to each slice network in the service quality requirements of the slice network list 2. The service requested by each slice network in the slice network list 1 may be determined according to a third preset priority value, and the service requested by each slice network in the slice network list 2 may be determined according to a fourth preset priority value. Here, the third preset priority value and the fourth preset priority value are priority values in the service priority information. In some embodiments, the third predetermined priority value is greater than the fourth predetermined priority value. In this case, the requested services of each slice network in slice network list 2 are a subset of the requested services of each slice network in slice network list 1. Also taking table 10 as an example, assuming that the third preset priority value is 3, the qos requirements corresponding to each slice network in the slice network list 1 include qos requirements of service 1, qos requirements of service 2, qos requirements of service 3, and qos requirements of service 4. Assuming that the fourth preset priority value is 2, the qos requirement corresponding to each slice network in the slice network list 2 includes qos requirement of service 1, qos requirement of service 2, and qos requirement of service 3.

Of course, the policy control network element may also determine the qos requirements of the slice network list 1 and the qos requirements of the slice network list 2 according to the slice network priority information and the service priority information. Taking table 11 as an example, assume that the first predetermined priority value is 3, the second predetermined priority value is 2, the third predetermined priority value is 3, and the fourth predetermined priority value is 1. In this case, the slice network list 1 includes service quality requirements of services 1 to 3 of the slice network 1, service quality requirements of services 1 to 3 of the slice network 2, and service quality requirements of services 1 to 3 of the slice network 3. The slice network list 2 includes the quality of service requirements of service 1 of slice network 1 and the quality of service requirements of service 1 of slice network 2.

In some embodiments, before requesting to obtain the network configuration information corresponding to another sliced network list, the policy control network element may determine, according to the sliced network priority information, the sliced networks included in the another sliced network list. Accordingly, the request information for requesting the network configuration information corresponding to the another slice network list may also include only the identifier of the slice network included in the another slice network list. The specific case can be seen in the description in step 201.

In the above embodiment, under the condition that the network resource is not enough, the normal operation of the high-priority slice network and the high-priority service can be ensured as much as possible.

In other embodiments, if the notification information further includes the reason information, the policy control network element may further consider the reason information when determining the slice network list 2.

In other embodiments, if the notification information further includes the network parameter measurement value, the policy control network element may further consider the network parameter measurement value when determining the slice network list 2.

The different network elements in the embodiment shown in fig. 2 are only one logical functional division, and there may be other division ways in actual implementation. For example, the functions that can be implemented by the data analysis network element and the functions that can be implemented by the policy control network element as shown in fig. 2 can be implemented by one network device. Also for example, the functions that can be implemented by the data analysis network element and the functions that can be implemented by the network management network element as shown in fig. 2 can be implemented by one network device. Also for example, the functions that can be implemented by the policy control network element and the functions that can be implemented by the network management network element shown in fig. 2 can be implemented by one network device. In this case, some of the steps shown in fig. 2 need not be performed. For example, if the functions that can be implemented by the policy control network element and the functions that can be implemented by the network management network element shown in fig. 2 are implemented by one network device, the interaction steps between the network management network element and the policy control network element shown in steps 203 and 204 may not need to be executed.

301, the policy control network element sends request information to the data analysis network element, where the request information is used to request network configuration information corresponding to each slice network list in the multiple slice network lists. Correspondingly, the data analysis network element receives the request information sent by the policy control network element. The per-slice network list may include one or more slice networks.

In some embodiments, the request information may include an identification of one or more slicing networks included in each of the plurality of slicing network lists. After receiving the sliced network lists, the data analysis network element can determine the service quality requirement of each sliced network list in the sliced network lists according to the corresponding relationship between the sliced network lists and the service quality requirement. For a specific determination method, and a correspondence between a slice network list and a service quality requirement, reference may be made to the description of the embodiment shown in fig. 2, which is not described herein again.

In some embodiments, the request information includes a quality of service requirement of each of the plurality of sliced network lists, and the request information is used for requesting network configuration information corresponding to each sliced network list

And 302, the data analysis network element sends the corresponding network configuration information of each slice list to the policy control network element. Correspondingly, the policy control network element receives the network configuration information corresponding to each slice network list sent by the data analysis network element.

It can be seen that the embodiment shown in fig. 3 differs from the embodiment shown in fig. 2 in that: in the embodiment shown in fig. 2, the request information is used to request the network configuration information corresponding to the one sliced network list, and the network configuration information corresponding to the one sliced network list is also returned by the data analysis network element; in the embodiment shown in fig. 3, the request information is used to request the network configuration information corresponding to each sliced network list in the sliced network lists, and the data analysis network element returns the network configuration information corresponding to each sliced network list.

In some embodiments, step 301 may not be performed. That is to say, the data analysis network element may determine, by itself, which network configuration information corresponding to the slice lists needs to be sent to the policy control network element, and send the network configuration information corresponding to the slice network lists that needs to be sent to the policy control network element. For example, the data analysis network element may determine, according to the slice network priority information and/or the service priority information, network configuration information corresponding to each slice network list in the plurality of slice network lists, and send the network configuration information corresponding to each slice network list in the plurality of slice network lists to the policy control network element. The manner in which the data analysis network element determines the network configuration information corresponding to each sliced network list in the sliced network lists according to the sliced network priority information and/or the service priority information may refer to the manner in which the policy control network element determines the service quality requirement of each sliced network list in the sliced network lists according to the sliced network priority information and/or the service priority information, which is not described herein again.

If step 301 is executed, the data analysis network element may determine, according to the request information, network configuration information corresponding to each of the plurality of slice network lists that needs to be sent to the policy control network element. The network configuration information corresponding to each of the plurality of slice network lists sent to the policy control network element is the network configuration information corresponding to each of the plurality of slice network lists acquired by the request information request.

The manner in which the data analysis network element determines the network configuration information may refer to the embodiment shown in fig. 2, and thus, details are not described here.

Each of the slice net lists in the embodiment shown in fig. 3 may have the same characteristics as the slice net list in the embodiment shown in fig. 2.

For example, the each slice network list contains one or more slice networks, and the quality of service requirement of each slice network list may include a quality of service requirement corresponding to each slice network of the one or more slice networks. The network configuration information corresponding to each sliced network list can meet the service quality requirement of each sliced network list. In other words, if the qos requirement of each slice list includes a qos requirement corresponding to a slice network, the network configuration information corresponding to each slice network list can satisfy the qos requirement corresponding to the slice network; if the service quality requirement of each slice network list includes a service quality requirement corresponding to each slice network in a plurality of slice networks, the network configuration information corresponding to each slice network list can meet the service quality requirement corresponding to each slice network.

As another example, the quality of service requirement corresponding to each of the sliced networks may include quality of service requirements of one or more services in each of the sliced networks.

As another example, the qos requirement corresponding to each of the sliced networks may include qos requirements corresponding to at least one user type in each of the sliced networks.

As another example, the quality of service requirement corresponding to each of the slicing networks may include a quality of service requirement corresponding to at least one user type in one or more services in each of the slicing networks.

For another example, the qos requirement corresponding to each slice network may include a qos requirement of at least one service in each slice network, where the qos requirement of the service refers to a requirement for a user ratio that meets a single-user qos requirement of the service.

Specific embodiments of the sliced netlist refer to the embodiment shown in fig. 2. For example, table 1 in the embodiment shown in fig. 2 may be the quality of service requirements of one of the plurality of sliced network lists.

It can be understood that, since the service quality requirement of each of the plurality of slice network lists is included in the request information, the service quality requirements of the plurality of slice network lists shown in table 1 or the service quality requirements of the plurality of slice network lists shown in table 2 or the service quality requirements of the plurality of slice network lists shown in table 4 or the service quality requirements of the plurality of slice network lists shown in table 5 may be included in the request information.

It will be appreciated that the quality of service requirements for different sliced network lists may be different. The difference here may mean that the number of sliced networks included in the quality of service requirements of different sliced network lists is different, but the quality of service requirements corresponding to the same sliced network may be the same. For example, table 2 is the quality of service requirement of one of the plurality of sliced network lists, and table 21 is the quality of service requirement of another one of the plurality of sliced network lists.

TABLE 21

As shown in table 21, the qos requirements of the slice network list include qos requirements corresponding to the slice network 1 and qos requirements corresponding to the slice network 2. The qos requirements corresponding to the slice network 1 in table 21 are the same as the qos requirements corresponding to the slice network 1 in table 2, and the qos requirements corresponding to the slice network 2 in table 21 are the same as the qos requirements corresponding to the slice network 2 in table 2.

It may also mean that the slicing networks included in the qos requirements of different slicing network lists are the same, but the qos requirements corresponding to the same slicing network are different. For example, table 4 is the quality of service requirement of one of the plurality of sliced network lists and table 22 is the quality of service requirement of another of the plurality of sliced network lists.

TABLE 22

As shown in table 22, the qos requirements of the slice network list include qos requirements corresponding to slice networks 1 to 3. The difference from table 2 is that the quality of service requirement for each sliced network in table 2 comprises the quality of service requirements of two services, while the quality of service requirement for each sliced network in table 22 comprises the quality of service requirement of one service.

Of course, the difference here may also mean that the qos requirements of different slice network lists include different numbers of slice networks and different qos requirements corresponding to each slice network. For example, table 2 is the quality of service requirement of one of the plurality of sliced network lists, and table 23 is the quality of service requirement of another of the plurality of sliced network lists.

TABLE 23

As shown in table 23, the qos requirements of the slice network list include qos requirements corresponding to the slice network 1 and qos requirements corresponding to the slice network 2. The difference from table 2 is that table 2 includes the qos requirements corresponding to 3 slicing networks in total, and the qos requirement corresponding to each slicing network includes the qos requirements of two services, while table 23 includes the qos requirements corresponding to 2 slicing networks in total, and the qos requirement corresponding to each slicing network includes the qos requirement of one service.

In some embodiments, the policy control network element may determine the quality of service requirement for each of the plurality of sliced network lists based on the sliced network priority information and/or the traffic priority information.

It is assumed that the slice net list 1 and the slice net list 2 are two slices in the plurality of slice net lists as net lists. The policy control network element may determine the qos requirements of the sliced network list 1 and the sliced network list 2 in the following manner.

In some embodiments, the policy control network element may determine the qos requirements of the sliced network list 1 and the qos requirements of the sliced network list 2 according to the slice priority information. Specifically, the policy control network element may determine the slice networks included in the slice network list 1 and the slice network list 2 according to the slice priority information, and further determine the service quality requirement of the slice network list 1 and the service quality requirement of the slice network list 2. The slicing networks included in the slicing network list 1 may be determined according to a first preset priority value, and the slicing networks included in the slicing network list 2 may be determined according to a second preset priority value. The first preset priority value and the second preset priority value refer to priority values in the slice network priority information. In some embodiments, the first predetermined priority value is greater than the second predetermined priority value. In this case, the slice netlist 2 may be a subset of the slice netlist 1. Also taking table 9 as an example, assuming that the first preset priority value is 3, the slice network list 1 includes slice network 1, slice network 2, slice network 3, and slice network 4. Assuming that the second preset priority value is 2, the slice network list 2 includes a slice network 1, a slice network 2, and a slice network 3.

In other embodiments, the policy control network element may determine the qos requirements of the sliced network list 1 and the qos requirements of the sliced network list 2 according to the service priority information. Specifically, the policy control network element may determine, according to the service priority information, a service included in the service quality requirement corresponding to each slice network in the service quality requirements of the slice network list 1 and a service included in the service quality requirement corresponding to each slice network in the service quality requirements of the slice network list 2, and further determine a service quality requirement of a service in the service quality requirement corresponding to each slice network in the service quality requirements of the slice network list 1 and a service quality requirement of a service in the service quality requirement corresponding to each slice network in the service quality requirements of the slice network list 2. The service requested by each slice network in the slice network list 1 may be determined according to a third preset priority value, and the service requested by each slice network in the slice network list 2 may be determined according to a fourth preset priority value. Here, the third preset priority value and the fourth preset priority value are priority values in the service priority information. In some embodiments, the third predetermined priority value is greater than the fourth predetermined priority value. In this case, the requested services of each slice network in the slice network list 2 are a subset of the requested services of each slice network in the slice network list 1. Also taking table 10 as an example, assuming that the third preset priority value is 3, the qos requirements corresponding to each slice network in the slice network list 1 include qos requirements of service 1, qos requirements of service 2, qos requirements of service 3, and qos requirements of service 4. Assuming that the fourth preset priority value is 2, the qos requirement corresponding to each slice network in the slice network list 2 includes qos requirement of service 1, qos requirement of service 2, and qos requirement of service 3.

Of course, the policy control network element may also determine the service quality requirement of the slice network list 1 and the service quality requirement of the slice network list 2 according to the slice network priority information and the service priority information. Taking table 11 as an example, assume that the first predetermined priority value is 3, the second predetermined priority value is 2, the third predetermined priority value is 3, and the fourth predetermined priority value is 1. In this case, the slice network list 1 includes service quality requirements of services 1 to 3 of the slice network 1, service quality requirements of services 1 to 3 of the slice network 2, and service quality requirements of services 1 to 3 of the slice network 3. The slice network list 2 includes the quality of service requirements of service 1 of slice network 1 and the quality of service requirements of service 1 of slice network 2.

In some embodiments, the method may further comprise: the policy control network element may send network configuration information corresponding to a first sliced network list to the network management network element, where the first sliced network list is included in the sliced network lists.

The network configuration information corresponding to the first cut network list may be one or more sets of network configuration information. In some embodiments, the policy control network element may send all network configuration information corresponding to the first slice network list to a network management network element. In other embodiments, the policy control network element may further determine that the first slice network list corresponds to first target network configuration information, and send the first target network configuration information to the network management network element. The network configuration information corresponding to the first cut network list includes the first target network configuration information. The manner in which the policy control network element determines the first target network configuration information may refer to the embodiment shown in fig. 2, and thus, details are not described herein.

In some embodiments, the policy control network element may determine, according to the slice network priority information and/or the service priority information, the network configuration information corresponding to the first slice network list from the network configuration information corresponding to each slice network list sent by the data analysis network element.

In some embodiments, the policy control network element may determine the network configuration information corresponding to the first sliced network list from the network configuration information corresponding to each sliced network list sent by the data analysis network element according to the sliced network priority information.

For example, the policy control network element may determine that the network configuration information corresponding to the first slice network list can meet the service quality requirements corresponding to several slice networks with high priorities, that is, the network configuration information corresponding to the first slice network list can meet the service quality requirement corresponding to a slice network with a priority value smaller than a preset priority value. Specifically, the preset priority value is set by the policy control network element according to the network resource status and the internal policy. For example, when network resources are sufficient or a particular value, the preset priority value may be set to a first priority value, which may be the maximum value of the priority. In this case, the first slice network list may be composed of all slice networks. Taking table 9 as an example, the first priority value may be 4. Assuming that the preset priority value is the first priority value, the first slice network list is composed of slice networks with priority values smaller than 4. Correspondingly, the network configuration information corresponding to the first slice network list can meet the service quality requirement corresponding to the slice network with the priority value smaller than 4. The preset priority value may be set to a second priority value, which is less than the first priority value, when network resources are limited or another specific value. In this case, the first list of sliced networks may be composed of sliced networks having priority values less than or equal to the second priority value. Also taking table 9 as an example, assuming that the preset priority value is 3, the first slice network list may include slice network 1, slice network 2, and slice network 3. Correspondingly, the network configuration information corresponding to the first slice network list can meet the service quality requirements corresponding to the slice network 1, the slice network 2 and the slice network 3.

In some embodiments, the policy control network element may determine, according to the service priority information, network configuration information corresponding to the first slice network list from the network configuration information corresponding to each slice network list sent by the data analysis network element.

For example, the policy control network element may determine that the network configuration information corresponding to the first slice network list can meet the service quality requirement of the service whose service priority value is smaller than a preset priority value. For example, when network resources are sufficient or a particular value, the preset priority value may be set to a first priority value, which may be the maximum value of the priority. In this case, the network configuration information corresponding to the first slice network list can meet the service quality requirements of all services. Taking table 10 as an example, the first priority value may be 4. Assume that the predetermined priority value is the first priority value. The network configuration information corresponding to the first slice network list can meet the service quality requirement of the service with the priority value less than 4. The predetermined priority value may be set to a second priority value that is less than the first priority value when network resources are limited or another specific value. In this case, the network configuration information corresponding to the first slice network list can satisfy the qos requirement of the service with the priority value less than or equal to the second priority value. Also taking table 10 as an example, assuming that the preset priority value is 3, the qos requirement of the service with the priority value less than or equal to 3 can be requested. In this case, the network configuration information corresponding to the first slice network list can satisfy the service quality requirements of service 1, service 2, and service 3.

In some embodiments, the policy control network element may determine, according to the sliced network priority information and the service priority information, the network configuration information corresponding to the first sliced network list from the network configuration information corresponding to each sliced network list sent by the data analysis network element.

For example, the policy control network element may determine that the network configuration information corresponding to the first slice network list can meet the service quality requirements corresponding to several high-priority slice networks, that is, the network configuration information corresponding to the first slice network list can meet the service quality requirement corresponding to a slice network whose slice network priority value is smaller than a preset priority value. Specifically, the preset slice network priority value is set by the policy control network element according to the network resource state and the internal policy. For example, when network resources are sufficient or at some particular value, the preset sliced network priority value may be set to a first sliced network priority value, which may be the maximum value of the sliced network priority. In this case, the first slice network list may be composed of all slice networks. When network resources are limited or another specific value, the preset sliced network priority value may be set to a second sliced network priority value that is less than the first sliced network priority value. In this case, the first list of sliced networks may be composed of sliced networks having a sliced network priority value less than or equal to the second sliced network priority value.

Further, the policy control network element may determine that the network configuration information corresponding to the first slice network list can meet a service quality requirement of a service whose service priority value is smaller than a preset priority value. For example, when network resources are sufficient or a specific value, the preset traffic priority value may be set to a first traffic priority value, which may be the maximum value of the traffic priority. In this case, the network configuration information corresponding to the first slice network list can meet the service quality requirements of all services. The network configuration information corresponding to the first slice network list can meet the service quality requirement of the service with the service priority value less than 4. When network resources are limited or another specific value, the preset service priority value may be set to a second service priority value, which is smaller than the first service priority value. In this case, the network configuration information corresponding to the first slice network list can satisfy the qos requirement of the service having the service priority value less than or equal to the second service priority value.

Taking table 11 as an example, assuming that the preset slice network priority is 2 and the preset service priority is 2, the network configuration information corresponding to the first slice network list can satisfy the service quality requirement of service 1 of slice network 1, the service quality requirement of service 2 of slice network 1, the service quality requirement of service 1 of slice network 2, and the service quality requirement of service 2 of slice network 2. Accordingly, the first slice network list includes slice network 1 and slice network 2.

When determining the network configuration information corresponding to the first sliced network list from the network configuration information corresponding to each sliced network list sent by the data analysis network element according to the sliced network priority information and/or the service priority information, the policy control network element may also refer to other information, for example, according to the network resource information. The policy control network element can ensure that the determined first slice network list can ensure the normal operation of the high-priority slice network and the high-priority service under the condition of knowing that the network resources are insufficient.

In other embodiments, the policy control network element may further determine the first list of sliced networks according to other rules. For example, the policy control network may randomly determine that the network configuration information corresponding to one of the plurality of sliced network lists is the network configuration information corresponding to the first sliced network list. As another example, the policy control network element may determine that a group of network configuration information with the largest number of network configuration information groups is the network configuration information corresponding to the first cut network list. For another example, the policy control network element may determine, according to the request message sent by the network management network element, the network configuration information corresponding to the first slice list. The request message may include slice network identifications included in the list of slice networks that need to be acquired. Slice net list 1 and slice net list 2 are also taken as examples. Assuming that the request message includes the slice network 4, the network configuration information corresponding to the first slice network list is the network configuration information corresponding to the slice network list 2. Or, the network configuration information corresponding to the first slice network list is the network configuration information corresponding to the slice network 4.

In some embodiments, the network management element may further send notification information to the policy control element when the network management element cannot perform network configuration according to the network configuration information corresponding to the first slice network list, where the notification information is used to notify the policy control element that the network management element cannot perform network configuration according to the network configuration information corresponding to the first slice network list.

In some embodiments, the policy control network element may further send first indication information to the network management network element, where the first indication information is used to indicate that the network management network element sends the notification information to the policy control network element when the network configuration cannot be performed according to the network configuration information corresponding to the first slice network list. Accordingly, the network management network element receives the first indication information.

In some embodiments, when the network management network element receives the network configuration information corresponding to the first slice network list sent by the policy control network element, if the network management network element determines that the network configuration information corresponding to the first slice network list cannot be used for network setting, the network management network element may immediately send notification information to the policy control network element. In other words, after receiving the network configuration information corresponding to the first slice network list, the network management network element may first determine whether the network configuration information corresponding to the first slice network list is usable for network setting, and send the notification information to the policy control network element if it is determined that the network configuration information corresponding to the first slice network list is not usable for network setting.

In other embodiments, after receiving the network configuration information corresponding to the first sliced network list sent by the policy control network element, if the network management network element determines that network setting cannot be performed according to the network configuration information corresponding to the first sliced network list in the operation process of the sliced network, the network management network element may send notification information to the policy control network element. In other words, when the network management element receives the network configuration information corresponding to the first slice network list sent by the policy control element, the network management element may perform network configuration according to the network configuration information corresponding to the first slice network list, but after the slice network operates for a period of time, the network management element finds that the network configuration information corresponding to the first slice network list cannot be performed any more, and if the network resource is in short supply or the like, the network management element sends the notification information to the policy control element.

In some embodiments, the notification information further includes reason information indicating a reason why the network management network element is unable to perform network configuration. The specific content of the reason information can be referred to the embodiment shown in fig. 2, and thus, the detailed description is not needed here.

In some embodiments, the policy control network element may further send second indication information to the network management network element, where the second indication information is used to indicate a reason why the network management network element cannot perform network configuration to the policy control network element when the network management network element cannot perform network configuration according to the corresponding network configuration information of the slice list. Accordingly, the network management network element receives the second indication information.

In some embodiments, the notification information may further include a network parameter measurement value corresponding to the first cut network list. The detailed contents of the network parameter measurement values can be referred to the embodiment shown in fig. 2, and thus the details are not repeated herein.

In some embodiments, the policy control network element may further send third indication information to the network management network element, where the third indication information is used to indicate that the network management network element sends the network parameter measurement value corresponding to the sliced network list to the policy control network element when the network management network element cannot perform network configuration according to the network configuration information corresponding to the sliced network list. Accordingly, the network management network element receives the third indication information.

In other embodiments, the network management element may send the notification information, the reason information, and/or the network parameter measurement value corresponding to the first slice network list, respectively.

In some embodiments, the policy control network element may determine the second target network configuration information after receiving the notification message. The method for determining the second target network configuration information may refer to the embodiment shown in fig. 2, and is not described herein again.

In some embodiments, the policy control network element may determine, according to the notification information, network configuration information corresponding to the second slice network list; and the policy control network element sends the network configuration information corresponding to the second slice network list to the network management network element. The second list of slicing networks includes at least one slicing network. The network configuration information corresponding to the second slice network list may be a set of network configuration information or multiple sets of network configuration information. The manner in which the policy control network element sends the network configuration information corresponding to the second sliced network list to the network management network element is the same as the manner in which the policy control network element sends the network configuration information corresponding to the first sliced network list to the network management network element, and details are not repeated here.

In some embodiments, the determining, by the policy control network element according to the notification information, network configuration information corresponding to the second slice network list includes: and when receiving the notification information, the policy control network element determines network configuration information corresponding to the second slice network list from the network configuration information corresponding to each slice network list sent by the data analysis network element, where the plurality of slice network lists include the second slice network list.

In some embodiments, the policy control network element may determine the quality of service requirement of the second sliced network list based on the sliced network priority information and/or the traffic priority information. The method for determining the qos requirement of the second sliced network list by the policy control network element according to the sliced network priority information and/or the service priority information may refer to the method for determining the qos requirement of another sliced network list in the embodiment shown in fig. 2, which is not described herein again.

In some embodiments, the second list of sliced networks may be a subset of the first list of sliced networks, e.g., the sliced networks included in the second list of sliced networks may have a higher priority than the sliced networks included in the first list of sliced networks.

In some embodiments, the network configuration information corresponding to the second sliced network list may be the network configuration information corresponding to any sliced network column of the sliced networks lists except the first sliced network list.

In other embodiments, the policy control network element may further request the data analysis network element for network configuration information corresponding to the second sliced network list, and receive the network configuration information corresponding to the second sliced network list sent by the data analysis network element. In order to distinguish from the request information in step 301, the request information in step 301 is hereinafter referred to as first request information, and the request information including the quality of service requirement of the second slice list is referred to as second request information. The policy control network element may send the second request information to the data analysis network element, where the second request information may include a quality of service requirement of the second sliced network list, and the second request information is used to request network configuration information corresponding to the second sliced network list. The policy control network element may receive the network configuration information corresponding to the second sliced network list sent by the data analysis network element. In other words, the quality of service requirements of the second sliced network list are not included in the quality of service requirements of the plurality of sliced network lists in the first request message. The policy control needs to request to acquire the network configuration information corresponding to the second slice network list through the second request information. Of course, in other embodiments, the second request message may include the qos requirements of other sliced networks lists in addition to the qos requirements of the second sliced network list. Correspondingly, the data analysis network element will also feed back the service quality requirements of the other slice network lists to the policy control network element.

In some embodiments, similar to the first request information, the second request information may also include an identifier of the slice network included in the second slice network list, which may be described in step 301.

In some embodiments, if the notification information further includes the reason information, the policy control network element may further consider the reason information when determining the second slice network list.

In other embodiments, if the notification information further includes the network parameter measurement value, the policy control network element may further consider the network parameter measurement value when determining the second slice network list.

As described above, the slicing network referred to in the embodiments of the present application may be one of a network slice, a network slice instance, and a network slice sub-instance. Accordingly, the sliced netlist referred to in the embodiments of the present application may also be referred to as a netlist, or a netlist.

The different network elements in the embodiment shown in fig. 3 are only one logical functional division, and there may be other division ways in actual implementation. The functions that can be implemented by the data analysis network element and the functions that can be implemented by the policy control network element as shown in fig. 3 can be implemented by one network device, for example. Also for example, the functions that can be implemented by the data analysis network element and the functions that can be implemented by the network management network element as shown in fig. 3 can be implemented by one network device. Also for example, the functions that can be implemented by the policy control network element and the functions that can be implemented by the network management network element as shown in fig. 3 can be implemented by one network device. In this case, some of the steps shown in fig. 3 need not be performed. For example, if the functions that can be implemented by the policy control network element and the functions that can be implemented by the network management network element shown in fig. 3 are implemented by one network device, the interaction step between the network management network element and the policy control network element shown in fig. 3 may not need to be executed.

Fig. 4 is a schematic flowchart of a method for acquiring network configuration information according to an embodiment of the present application.

401, the pcf sends an analysis information request message to the NWDAF. The analysis information request message includes quality of service requirement information of at least one slice network list, and the analysis request message is used for requesting network configuration information corresponding to each slice network list in the at least one slice network list. Correspondingly, the NWDAF receives the analysis information request message sent by the PCF.

For specific content of the qos requirement information of each slice network list, reference may be made to content of the qos requirement information of each slice network in the embodiments shown in fig. 2 and fig. 3, which is not described herein again.

A specific form of the quality of service requirement information of the slice network list 1 is given here, as shown in table 24.

Watch 24

The range (range) of the slice network requirement list in table 24 with a value of 1 indicates that the table is for the qos requirement of slice network list 1. A slicing network requirement range of 1 to M indicates that 1 to M slicing networks may be included in the slicing network list 1, where each slicing network is identified by a specific S-NSSAI. A service requirement list ranging from 1 to N indicates that a specific slice network contains 1 to N services, each of which is distinguished by a service identifier (application ID). In addition, the service quality requirement of each service is a requirement for a user ratio that meets the single-user service quality requirement of the service, that is, a user satisfaction requirement of the service. The meaning of whether the corresponding table item content is necessary or optional is meant.

Table 24 shows a specific form of the qos requirement information of the slice network list 1, and when the request message sent by the PCF to the NWDAF includes the qos requirement information of X (X > 1) slice network lists, the specific form of the qos requirement information of the slice network lists 2-X is similar to table 24, and is not described herein again.

In this step, the PCF sends the analysis information Request message to the NWDAF, which may be a real-time Request message (e.g., NWDAF _ analyticnfo _ Request) or a subscription Request message (e.g., NWDAF _ analyticnfo _ Subscribe). If the analysis information request message is a real-time request message, the NWDAF, after receiving the request message, may immediately return the content of the PCF request without the model training operation described in step 202, wherein the model training operation has been completed before receiving the request message; if the analysis information request message is a subscription request message, the NWDAF needs model training before returning the contents requested by the PCF after receiving the request message.

402, the nwdaf sends an analysis information request feedback message to the PCF that includes network configuration information for each of the sliced network lists. Correspondingly, the PCF receives an analysis information request feedback message sent by the NWDAF.

The meaning and content of the network configuration information corresponding to each sliced network list may refer to the content of the network configuration information corresponding to each sliced network list in step 202 in the embodiment shown in fig. 2 or step 302 in the embodiment shown in fig. 3, which is not described herein again.

In addition, for a specific method for how the NWDAF obtains the network configuration information corresponding to each slice network list, reference may also be made to the method in step 202 in the embodiment shown in fig. 2, which is not described herein again.

A specific form of a set of network configuration information corresponding to the slice network list 1 is given here, as shown in table 25, where a Key Performance Indicator (KPI) of the slice network is taken as an example of the network configuration information.

TABLE 25

In table 25, a Key Performance Indicator (KPI) range (range) of the slice network is 1, which indicates that the table is the network configuration information corresponding to the slice network list 1. The range of time 09. The KPI of the slice network having a range of 1 to M indicates that the network configuration information includes network configuration information corresponding to each of the 1 to M slice networks in the slice network list 1, for example, specific network configuration information for the 2 nd slice in the M slice networks.

To illustrate, the slice network list 1 corresponds to at least one set of network configuration information, wherein the set of network configuration information is shown in table 25. When the slice network list 1 corresponds to the P (P > 1) group network configuration information, the specific form of the 2 nd to P group network configuration information is similar to that of table 23, and is not described herein again.

In addition, table 25 provides a group of network configuration information corresponding to the sliced network list 1, and when the request message sent by the PCF to the NWDAF in step 501 includes service quality requirement information for X (X > 1) sliced network lists, the specific form of the group of network configuration information corresponding to the sliced network lists 2-X is similar to table 25, and is not described herein again.

Table 20 shows some specific network configuration parameters that may be included in the network configuration information in table 25, and details thereof are not repeated here.

In this step, the NWDAF sends the analysis information request feedback message to the PCF, which may specifically belong to a real-time Response message (e.g., NWDAF _ analysisinfo _ Response) or a subscription report message (e.g., NWDAF _ analysisinfo _ Notify). If the analysis information request feedback message is a real-time response message, the NWDAF can immediately return the content of the PCF request without the operation of model training after receiving the analysis information request message sent by the PCF, wherein the operation of model training is completed before receiving the request message; if the analysis information request feedback message is a subscription report message, the NWDAF needs to perform model training before returning the content requested by the PCF after receiving the analysis information request message sent by the PCF.

The pcf sends network configuration information corresponding to the first list of fragmented networks to the OAM 403. Correspondingly, the OAM receives the network configuration information corresponding to the first cut network list.

If the analysis information request message in step 401 only contains the qos requirement information of one slice network list, the first slice network list is the slice network list contained in the request message, in other words, the network configuration information corresponding to the first slice network list is the network configuration information corresponding to the slice network list.

If the analysis information request message in step 401 includes the qos requirement information of the multiple slice network lists, the first slice network list is one of the multiple slice network lists, in other words, the network configuration information corresponding to the first slice network list is the network configuration information corresponding to one of the multiple slice network lists.

For the case that the analysis information request message in step 401 includes the qos requirement information of multiple slice network lists, before sending the network configuration information corresponding to the first slice network list to the OAM, the PCF may determine the network configuration information corresponding to the first slice network list according to the slice network priority information and/or the service priority information, and the specific determination method refers to the description of the embodiment shown in fig. 3.

If the network configuration information corresponding to the first cut network list is a set of network configuration information, the PCF sends a set of network configuration information to the OAM. If the network configuration information corresponding to the first cut network list is multiple sets of network configuration information, the PCF sends multiple sets of network configuration information to the OAM.

The method for the PCF to send the network configuration information corresponding to the first slice network list may refer to the embodiments shown in fig. 2 and fig. 3, and thus, it is not necessary to describe here any further.

The OAM sends a notification message to the PCF indicating that the OAM cannot configure the network based on the received network configuration information 404. Correspondingly, the PCF receives the notification information sent by the OAM.

The content and the sending method of the notification information can refer to the embodiments shown in fig. 2 and fig. 3, and need not be described herein again.

405, the pcf sends network configuration information corresponding to the second sliced network list to the OAM. Correspondingly, the OAM receives the network configuration information corresponding to the second sliced network list sent by the PCF.

If the analysis information request feedback message received by the PCF in step 402 contains network configuration information corresponding to multiple sliced network lists and the second sliced network list is contained in the multiple sliced network lists, the specific method in this step refers to a method in which the PCF sends network configuration information corresponding to the first sliced network list to the OAM in step 403.

If the analysis information request feedback message received by the PCF in step 402 does not contain the network configuration information corresponding to the second sliced network list, the PCF sends a request message requesting the network configuration information corresponding to the second sliced network list to the NWDAF with reference to step 401 before this step. The method for determining the second sliced netlist can refer to the embodiment shown in fig. 3.

Fig. 5 is a schematic flow chart of a method for acquiring network configuration information according to an embodiment of the present application. It should be noted that, for convenience of description, in this embodiment, specific network element entities such as PCF, NWDAF, OAM, etc. are only used as examples for description, but it is not excluded that these entities may be replaced by other network element entities with equivalent or similar functions, for example, in this embodiment, PCF may be replaced by other network elements with policy control functions related to the present invention, for example, PCF is replaced by NSSF or network storage function (NRF) network element or management plane policy control network element; the NWDAF may be replaced by other network elements having the data analysis function related to the present invention, for example, the NWDAF is replaced by a Management Data Analysis Service (MDAS) network element; the OAM may be replaced by other network elements having the network management functions involved in the present invention, such as the OAM being replaced by the nsff.

501, pcf sends an analysis information request message to NWDAF, the analysis request message requesting network configuration information corresponding to the first list of slice networks. Correspondingly, the NWDAF receives the analysis information request message sent by the PCF.

The method of this embodiment is different from the method of the embodiment shown in fig. 4 in that the analysis request message is used to request network configuration information corresponding to the first slice network list and is directly sent to OAM by NWDAF.

The analysis information request message carries identification information of one or more slice networks contained in the first slice network list. Specifically, in this embodiment, the identification information of a slice network is a specific S-NSSAI.

Before sending the analysis information request message, the PCF determines the first slice network list according to the slice network priority information, i.e. determines which slice networks the first slice network list includes the identification information of which slice networks, and the specific method is described with reference to step 201 and is not described herein again.

The PCF may also send the quality of service requirement information of all the slicing networks and/or priority information of all the slicing networks to the NWDAF before sending the analysis information request message. Of course, the PCF does not limit the time sequence for sending the analysis information request message and/or the service quality requirement information of all slice networks and/or the priority information of all slice networks.

After the NWDAF receives the analysis request message sent by the PCF, the NWDAF determines a quality of service requirement corresponding to the first list of slice networks.

If the PCF sends the qos requirement information of all the slice networks to the NWDAF, the NWDAF may determine the qos requirement information of the first slice network list according to the qos requirement information of all the slice networks and the identification information of one or more slice networks included in the first slice network list.

If the NWDAF itself stores or receives the qos requirement information from all slice networks of the AF/tenant, the NWDAF may also determine the qos requirement information of the first slice network list according to the qos requirement information of all slice networks and the identification information of one or more slice networks included in the first slice network list.

For specific content of the qos requirement information of the first slice network list, reference may be made to content of the qos requirement information of each slice network in the embodiments shown in fig. 2 and fig. 3, which is not described herein again.

The specific form of the qos requirement information of the first slice network list is shown in table 26.

Watch 26

The range (range) of the slice network requirement list in table 26 with a value of 1 indicates that the table is for the qos requirement of the first slice network list. A slice network requirement range of 1 to M indicates that 1 to M slice networks may be included in the first slice network list, where each slice network is identified by a particular S-NSSAI. A service requirement list ranging from 1 to N indicates that a specific slice network contains 1 to N services, each of which is distinguished by a service identifier (application ID). In addition, the service quality requirement of each service is a requirement for a user ratio that meets the single-user service quality requirement of the service, that is, a user satisfaction requirement of the service. The meaning of whether the corresponding table item content is necessary or optional is meant.

In this step, the PCF sends the analysis information Request message to the NWDAF, which may be a real-time Request message (e.g., NWDAF _ analyticnfo _ Request) or a subscription Request message (e.g., NWDAF _ analyticnfo _ Subscribe). If the analysis information request message is a real-time request message, the NWDAF, after receiving the request message, may immediately feed back the contents of the PCF request to the OAM without the model training operation described in step 202, where the model training operation is completed before receiving the request message; if the analysis information request message is a subscription request message, the NWDAF needs model training before feeding back the contents of the PCF request to the OAM after receiving the request message.

It should be noted that, in this embodiment, a method is described in which an analysis information request message sent by a PCF includes identification information of one or more slice networks included in a first slice network list, and then NWDAF determines service quality requirement information corresponding to the first slice network list. This embodiment does not exclude that the analysis information request message sent by the PCF directly includes the qos requirement of the first list of the cut networks.

502, the nwdaf sends network configuration information corresponding to the first slice network list to the OAM. Correspondingly, the OAM receives the network configuration information corresponding to the first slice network list sent by the NWDAF.

The meaning and content of the network configuration information corresponding to the first slice network list may refer to step 202 in the embodiment shown in fig. 2, and need not be described herein again.

In addition, for a specific method for how the NWDAF obtains the network configuration information corresponding to the first slice network list, reference may also be made to the method in step 202 in the embodiment shown in fig. 2, which is not described herein again.

A specific form of a set of network configuration information corresponding to the first sliced network list is given here, as shown in table 27, where KPIs of the sliced network are taken as an example of the network configuration information.

Watch 27

Information name	Whether or not it is necessary to	Range
			Slicing network KPI List		1
>Time		09:00-12:00
			>KPI for slicer networks		1-M
>>Uplink or downlink packet loss rate of F1-U interface in gNB-CU	Must choose
			>>Downlink packet drop rate in gNB-CU	Must choose
…
			>>Other slicing network KPIs	Must choose

A Key Performance Indicator (KPI) range (range) of the slice network in table 27 of 1 indicates that the table is the network configuration information corresponding to the first slice network list. The range of time 09. The KPIs of the slice networks having a range of 1 to M indicate that the network configuration information includes network configuration information corresponding to each of the 1 to M slice networks in the first slice network list, for example, specific network configuration information for the 2 nd slice in the M slice networks.

To illustrate, the first slice network list corresponds to at least one set of network configuration information, wherein the set of network configuration information is shown in table 27. When the slice network list corresponds to P (P > 1) group network configuration information, the specific form of the 2 nd to P group network configuration information is similar to table 27, and is not described herein again.

Table 27 shows some specific network configuration parameters that may be included in the network configuration information, which are shown in table 20 and are not described herein again.

It should be noted that, if the network configuration information corresponding to the first slice network list is a set of network configuration information, the NWDAF sends a set of network configuration information to the OAM. If the network configuration information corresponding to the first slice network list is multiple sets of network configuration information, the NWDAF sends the multiple sets of network configuration information to the OAM. Of course, if the network configuration information corresponding to the first slice network list is multiple sets of network configuration information, the NWDAF sends one or more sets of network configuration information in the multiple sets of network configuration information to the OAM as the first target network configuration information of the first slice network list. The method for sending, by the NWDAF, the network configuration information corresponding to the first sliced network list to the OAM may refer to step 203 of the embodiment shown in fig. 2, where the policy control network element sends a description of the network configuration information corresponding to the sliced network list to the network management network element.

If the NWDAF sends all the network configuration information corresponding to the first slice network list to the OAM in step 502, then steps 503-505 are performed subsequently. If, in step 502, the NWDAF sends one or more sets of network configuration information in the multiple sets of network configuration information to the OAM as the first target network configuration information corresponding to the first slice network list, then steps 506 to 507 are performed subsequently.

503, the OAM sends a first notification message to the PCF, where the first notification message is used to indicate that the OAM cannot perform network configuration according to the network configuration information corresponding to the first cut network list. Correspondingly, the PCF receives the notification information sent by the OAM.

The OAM may send the first notification information directly to the PCF.

The OAM may also send the first notification message to the NWDAF, which forwards the first notification message to the PCF.

The content and method of the first notification information may specifically refer to the description of the embodiment shown in fig. 2.

The pcf sends 504, to the NWDAF, an analysis information request message requesting network configuration information corresponding to the second slice network list. Correspondingly, the NWDAF receives an analysis information request message sent by the PCF for requesting network configuration information corresponding to the second slice network list.

The method in this step refers to step 501, which is not described herein again.

505, the nwda sends network configuration information corresponding to the second slice network list to the OAM.

The method in this step refers to step 502, which is not described herein again.

The OAM sends a second notification to the NWDAF indicating that the OAM cannot configure the network based on the first target network configuration information 506. Correspondingly, the NWDAF receives the second notification information transmitted by the OAM.

The method for sending the second notification information to the NWDAF by OAM and the content of the second notification information refer to the content and the method for sending the notification information from the network management element to the policy control element in the embodiment shown in fig. 2.

507, the nwdaf sends the second target network configuration information corresponding to the first slice network list to the OAM.

Fig. 6 is a block diagram of a network device according to an embodiment of the present application. The network device 600 shown in fig. 6 includes: processing unit 601, transmitting unit 602, and receiving unit 603. The network device 600 may be a policy control network element in the embodiments shown in fig. 2 and 3, and a PCF in the embodiments shown in fig. 4 and 5.

A processing unit 601, configured to request the request information to request network configuration information corresponding to each slice network list in at least one slice network list, where each slice network list includes one or more slice networks.

A sending unit 602, configured to send the request information to a data analysis network element.

A receiving unit 603, configured to receive the network configuration information corresponding to each slice network list sent by the data analysis network element.

In a possible approach, the processing unit 601 may be implemented by a processor, the transmitting unit 602 may be implemented by a transmitter, and the receiving unit 603 may be implemented by a receiver. Specific functions and advantageous effects of the processing unit 601, the sending unit 602, and the receiving unit 603 may refer to the methods shown in fig. 2 to fig. 5, and are not described herein again.

In a possible implementation manner, a communication device is further provided, and the communication device may be a network device, and may also be a component (e.g., a chip or a circuit) of the network device. The communication device may include a processor. The communication device may also include a receiver, a transmitter, and a memory. Wherein the processor may be adapted to implement the respective functions and operations of the processing unit described above. The transmitter may be used to implement the corresponding functions and operations of the transmitting unit described above. The receiver may be used to implement the functions and operations of the receiving unit described above. The transmitter and the receiver may be integrated together, referred to as a transceiver. The device for realizing the receiving function in the transceiver is regarded as a receiving unit, and the device for realizing the transmitting function is regarded as a transmitting unit. The memory can be used for storing execution instructions or application program codes, and is controlled by the processor to execute, and the method provided by the above embodiment of the application is realized by combining the receiver and the transmitter; and/or may be used to temporarily store some data and instruction information, etc. The memory may exist independently of the processor, in which case the memory may be coupled to the processor via a communication line. In yet another possible design, the memory may be integrated with the processor, and the embodiment of the present application is not limited thereto.

Fig. 7 is a block diagram of a network device according to an embodiment of the present application. As shown in fig. 7, the network device 700 includes a processor 701, a memory 702. The processor 701 may be used to process communication protocols and communication data, as well as to control network devices, execute software programs, process data of software programs, and so on. The memory 702 is used primarily for storing software programs and data.

For ease of illustration, only one memory and processor are shown in FIG. 7. In an actual network device product, there may be one or more processors and one or more memories. The memory may also be referred to as a storage medium or a storage device, etc. The memory may be provided independently of the processor, or may be integrated with the processor, which is not limited in this embodiment.

In the embodiment of the present application, a circuit or a device having a transceiving function may be regarded as the transceiver 703 of the network device, and a processor having a processing function may be regarded as a processing unit of the network device. A transceiver may also be referred to as a transceiver unit, transceiver, transceiving means, etc. A processing unit may also be referred to as a processor, a processing board, a processing module, a processing device, or the like. A device for implementing a receiving function in the transceiver 703 may be regarded as a receiving unit, and a device for implementing a transmitting function in the transceiver 703 may be regarded as a transmitting unit, that is, the transceiver 703 includes a receiving unit and a transmitting unit. A receiving unit may also be referred to as a receiver, a receiving circuit, or the like. A transmitting unit may also sometimes be referred to as a transmitter, or a transmitting circuit, etc.

The processor 701, the memory 702, and the transceiver 703 communicate with each other via internal connection paths to transfer control and/or data signals

The method disclosed in the embodiments of the present application may be applied to the processor 701, or implemented by the processor 701. The processor 701 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be implemented by integrated logic circuits of hardware or instructions in the form of software in the processor 701.

The processor described in the embodiments of the present application may be a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software modules may be located in a Random Access Memory (RAM), a flash memory, a read-only memory (ROM), a programmable ROM, an electrically erasable programmable ROM, a register, or other storage medium known in the art. The storage medium is located in a memory, and a processor reads instructions in the memory and combines hardware thereof to complete the steps of the method.

In some embodiments, the memory 702 may store instructions for performing a method performed by a policy control network element of the method shown in fig. 2. The processor 701 may execute the instructions stored in the memory 702 to perform the steps performed by the policy control network element in the method shown in fig. 2, in combination with other hardware (for example, the transceiver 703), and the specific working process and beneficial effects can be referred to the description in the embodiment shown in fig. 2.

In some embodiments, the memory 702 may store instructions for performing a method performed by a policy control network element of the method shown in fig. 3. The processor 701 may execute the instructions stored in the memory 702 to complete the steps performed by the policy control network element in the method shown in fig. 3 in combination with other hardware (e.g. the transceiver 703), and the specific working process and beneficial effects may refer to the description in the embodiment shown in fig. 3.

In some embodiments, memory 702 may store instructions for performing a method performed by a PCF in the method illustrated in fig. 4. The processor 701 may execute the instructions stored in the memory 702 to perform the steps performed by the PCF in the method shown in fig. 4 in combination with other hardware (e.g., the transceiver 703), and the specific working process and beneficial effects can be referred to the description in the embodiment shown in fig. 4.

In some embodiments, memory 702 may store instructions for performing a method performed by a PCF in the method illustrated in fig. 5. The processor 701 may execute the instructions stored in the memory 702 to perform the steps performed by the PCF in the method shown in fig. 5 in combination with other hardware (e.g., the transceiver 703), and the specific working process and beneficial effects may refer to the description in the embodiment shown in fig. 5.

The embodiment of the application further provides a chip, which comprises a transceiving unit and a processing unit. The transceiver unit can be an input/output circuit and a communication interface; the processing unit is a processor or a microprocessor or an integrated circuit integrated on the chip. The chip can execute the method of the policy control network element side or the PCF side in the above method embodiments.

The embodiment of the present application further provides a computer-readable storage medium, on which instructions are stored, and when executed, the instructions perform the method of the policy control network element side or the PCF side in the foregoing method embodiment.

Embodiments of the present application further provide a computer program product containing instructions, where the instructions, when executed, perform the method of the policy control network element side or the PCF side in the foregoing method embodiments.

Fig. 8 is a block diagram of a network device according to an embodiment of the present application. The network device 800 shown in fig. 8 includes: a processing unit 801 and a transmitting unit 802. The network device 800 may be a data analysis network element in the embodiments shown in fig. 2 and 3, and an NWDAF in the embodiments shown in fig. 4 and 5.

The processing unit 801 is configured to determine network configuration information corresponding to each slice network list in at least one slice network list.

A sending unit 802, configured to send, to the policy control network element, the network configuration information corresponding to each slice network list.

In a possible approach, the processing unit 801 may be implemented by a processor and the transmitting unit 802 may be implemented by a transmitter. Specific functions and advantageous effects of the processing unit 801 and the sending unit 802 can be referred to the methods shown in fig. 2 to fig. 5, and are not described herein again.

In a possible implementation manner, a communication apparatus is further provided, and the communication apparatus may be a network device or a component (e.g., a chip or a circuit) of the network device. The communication device may include a processor. The communication device may also include a transmitter and a memory. Wherein the processor may be adapted to implement the respective functions and operations of the processing unit described above. The transmitter may be used to implement the corresponding functions and operations of the transmitting unit described above. The transmitter and receiver may be integrated together, referred to as a transceiver. The device for realizing the receiving function in the transceiver is regarded as a receiving unit, and the device for realizing the transmitting function is regarded as a transmitting unit. The memory can be used for storing execution instructions or application program codes, and is controlled by the processor to execute, and the method provided by the above embodiment of the application is realized by combining the transmitter; and/or may be used to temporarily store some data and instruction information, etc. The memory may exist independently of the processor, in which case the memory may be coupled to the processor via a communications link. In yet another possible design, the memory may be integrated with the processor, and the embodiment of the present application is not limited thereto.

Fig. 9 is a block diagram of a network device according to an embodiment of the present application. As shown in fig. 9, the network device includes a processor 901 and a memory 902. The processor 901 may be used for processing communication protocols and communication data, controlling network devices, executing software programs, processing data of software programs, and the like. The memory 902 is used primarily for storing software programs and data.

For ease of illustration, only one memory and processor are shown in FIG. 9. In an actual network device product, there may be one or more processors and one or more memories. The memory may also be referred to as a storage medium or a storage device, etc. The memory may be provided independently of the processor, or may be integrated with the processor, which is not limited in this embodiment.

In the embodiment of the present application, a circuit or a device having a transceiving function may be regarded as the transceiver 903 of the network device, and a processor having a processing function may be regarded as a processing unit of the network device. A transceiver may also be referred to as a transceiver unit, transceiver, transceiving means, etc. A processing unit may also be referred to as a processor, a processing board, a processing module, a processing device, or the like. A device for implementing a receiving function in the transceiver 903 may be regarded as a receiving unit, and a device for implementing a transmitting function in the transceiver 903 may be regarded as a transmitting unit, that is, the transceiver 903 includes a receiving unit and a transmitting unit. A receiving unit may also be referred to as a receiver, a receiving circuit, or the like. A transmitting unit may also sometimes be referred to as a transmitter, or a transmitting circuit, etc.

The processor 901, the memory 902 and the transceiver 903 communicate with each other via internal connection paths to transfer control and/or data signals

The method disclosed in the embodiments of the present application may be applied to the processor 901, or implemented by the processor 901. The processor 901 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be implemented by integrated logic circuits of hardware or instructions in the form of software in the processor 901.

The processor described in the embodiments of the present application may be a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software modules may be located in a Random Access Memory (RAM), a flash memory, a read-only memory (ROM), a programmable ROM, an electrically erasable programmable memory, a register, or other storage media that are well known in the art. The storage medium is located in a memory, and a processor reads instructions in the memory and combines hardware thereof to complete the steps of the method.

In some embodiments, the memory 902 may store instructions for performing a method performed by a data analysis network element of the method shown in fig. 2. The processor 901 may execute the instructions stored in the memory 902 to complete the steps performed by the data analysis network element in the method shown in fig. 2 in combination with other hardware (e.g. the transceiver 903), and specific working procedures and beneficial effects may refer to the description in the embodiment shown in fig. 2.

In some embodiments, the memory 902 may store instructions for performing a method performed by a data analysis network element of the method shown in fig. 3. The processor 901 can execute the instructions stored in the memory 902 to complete the steps performed by the data analysis network element in the method shown in fig. 3 in combination with other hardware (e.g. the transceiver 903), and specific working procedures and beneficial effects can be referred to the description in the embodiment shown in fig. 3.

In some embodiments, memory 902 may store instructions for performing a method such as the NWDAF execution of the method shown in fig. 4. The processor 901 may execute the instructions stored in the memory 902 in combination with other hardware (e.g., the transceiver 903) to perform the steps performed by the NWDAF in the method shown in fig. 4, and the specific operation and beneficial effects may refer to the description in the embodiment shown in fig. 4.

In some embodiments, memory 902 may store instructions for performing a method such as the NWDAF execution of the method illustrated in fig. 5. The processor 901 may execute the instructions stored in the memory 902 in combination with other hardware (e.g., the transceiver 903) to perform the steps performed by the NWDAF in the method shown in fig. 5, and the specific operation and beneficial effects may refer to the description in the embodiment shown in fig. 5.

The embodiment of the application also provides a chip, which comprises a transceiver unit and a processing unit. The transceiver unit can be an input/output circuit and a communication interface; the processing unit is a processor or a microprocessor or an integrated circuit integrated on the chip. The chip can execute the method of the data analysis network element side or the NWDAF side in the above method embodiments.

Embodiments of the present application further provide a computer-readable storage medium, on which instructions are stored, and when executed, the instructions perform the method for analyzing data on a network element side or an NWDAF side in the foregoing method embodiments.

Embodiments of the present application further provide a computer program product containing instructions, which when executed perform the method of the foregoing method embodiments for data analysis on a network element side or an NWDAF side.

Fig. 10 is a block diagram of a network device according to an embodiment of the present application. The network device 1000 shown in fig. 10 includes: a processing unit 1001 and a receiving unit 1002. The network device 800 may be a network management network element in the embodiments shown in fig. 2 and 3, and OAM in the embodiments shown in fig. 4 and 5.

A receiving unit 1002, configured to receive network configuration information sent by a policy control network element

The processing unit 1001 is configured to perform network configuration on at least one slice network included in the first slice network list according to the network configuration information corresponding to the first slice network list.

In some embodiments, the receiving unit 1002 is specifically configured to receive network configuration information corresponding to each of at least one sliced network list sent by the policy control network element, where the at least one sliced network list includes the first sliced network list. The processing unit 1001 is further configured to determine, from the received network configuration information corresponding to each slice network list, network configuration information corresponding to the first slice network list.

In some embodiments, the receiving unit 1002 is specifically configured to receive network configuration information corresponding to the first cut network list, where the network configuration information is sent by the policy control network element.

In a possible approach, the processing unit 1001 may be implemented by a processor and the transmitting unit 1002 may be implemented by a transmitter. Specific functions and advantageous effects of the processing unit 1001 and the sending unit 1002 can refer to the methods shown in fig. 2 to fig. 5, and are not described herein again.

In a possible implementation manner, a communication apparatus is further provided, and the communication apparatus may be a network device or a component (e.g., a chip or a circuit) of the network device. The communication device may include a processor. The communication device may also include a receiver and a memory. Wherein the processor may be adapted to implement the respective functions and operations of the processing unit described above. The receiver may be used to implement the functionality and operation of the receiving unit described above. The transmitter and the receiver may be integrated together, referred to as a transceiver. The device for realizing the receiving function in the transceiver is regarded as a receiving unit, and the device for realizing the transmitting function is regarded as a transmitting unit. The memory can be used for storing execution instructions or application program codes, and is controlled by the processor to execute, and the method provided by the above embodiment of the application is realized by combining the receiver; and/or may be used to temporarily store some data and instruction information, etc. The memory may exist independently of the processor, in which case the memory may be coupled to the processor via a communication line. In another possible design, the memory may also be integrated with the processor, which is not limited in this embodiment.

Fig. 11 is a block diagram of a network device according to an embodiment of the present application. As shown in fig. 11, the network device includes a processor 1101, a memory 1102. The processor 1101 may be used for processing communication protocols and communication data, controlling network devices, executing software programs, processing data of software programs, and the like. The memory 1102 is primarily used to store software programs and data.

For ease of illustration, only one memory and processor are shown in FIG. 11. In an actual network device product, there may be one or more processors and one or more memories. The memory may also be referred to as a storage medium or a storage device, etc. The memory may be provided independently of the processor, or may be integrated with the processor, which is not limited in this embodiment.

In this embodiment, a circuit or a device with transceiving function may be regarded as the transceiver 1103 of the network device, and a processor with processing function may be regarded as the processing unit of the network device. A transceiver may also be referred to as a transceiver unit, transceiver, transceiving means, etc. A processing unit may also be referred to as a processor, a processing board, a processing module, a processing device, or the like. A device for implementing a receiving function in the transceiver 1103 can be regarded as a receiving unit, and a device for implementing a sending function in the transceiver 1103 can be regarded as a sending unit, that is, the transceiver 1103 includes a receiving unit and a sending unit. A receiving unit may also be referred to as a receiver, a receiving circuit, or the like. A transmitting unit may also sometimes be referred to as a transmitter, or a transmitting circuit, etc.

The processor 1101, memory 1102 and transceiver 1103 communicate with each other, passing control and/or data signals, via internal connection paths

The method disclosed in the embodiments of the present application may be applied to the processor 1101, or implemented by the processor 1101. The processor 1101 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by instructions in the form of hardware, integrated logic circuits, or software in the processor 1101.

The processor described in the embodiments of the present application may be a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an FPGA (field programmable gate array) or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software modules may be located in a Random Access Memory (RAM), a flash memory, a read-only memory (ROM), a programmable ROM, an electrically erasable programmable ROM, a register, or other storage medium known in the art. The storage medium is located in a memory, and a processor reads instructions in the memory and combines hardware thereof to complete the steps of the method.

In some embodiments, the memory 1102 may store instructions for performing the method performed by the network management element of the method illustrated in fig. 2. The processor 1101 may execute the instructions stored in the memory 1102 to perform the steps performed by the network management element in the method shown in fig. 2 in combination with other hardware (for example, the transceiver 1103), and the specific working process and beneficial effects can be referred to the description in the embodiment shown in fig. 2.

In some embodiments, the memory 1102 may store instructions for performing the method performed by the network management element in the method illustrated in fig. 3. The processor 1101 may execute the instructions stored in the memory 1102 to perform the steps performed by the network management element in the method shown in fig. 3 in combination with other hardware (for example, the transceiver 1103), and the specific working process and beneficial effects can be referred to the description in the embodiment shown in fig. 3.

In some embodiments, memory 1102 may store instructions for performing a method such as the OAM execution in the method illustrated in fig. 4. The processor 1101 may execute the instructions stored in the memory 1102, and in combination with other hardware (for example, the transceiver 1103) to complete the steps performed by OAM in the method shown in fig. 4, and specific working procedures and beneficial effects may refer to the description in the embodiment shown in fig. 4.

In some embodiments, memory 1102 may store instructions for performing a method such as OAM execution in the method illustrated in fig. 5. The processor 1101 may execute the instructions stored in the memory 1102 to complete the steps of OAM execution in the method shown in fig. 5 in combination with other hardware (e.g., the transceiver 1103), and specific working procedures and beneficial effects may refer to the description in the embodiment shown in fig. 5.

The embodiment of the application also provides a chip, which comprises a transceiver unit and a processing unit. The transceiver unit can be an input/output circuit and a communication interface; the processing unit is a processor or a microprocessor or an integrated circuit integrated on the chip. The chip may execute the method on the network management element side or the OAM side in the above method embodiments.

The embodiment of the present application further provides a computer-readable storage medium, on which instructions are stored, and when executed, the instructions perform the method of the network management element side or the OAM side in the above method embodiment.

The present application further provides a computer program product containing instructions, where the instructions, when executed, perform the method on the network management element side or the OAM side in the foregoing method embodiments.

In an embodiment of the application, the network device includes a hardware layer, an operating system layer running on top of the hardware layer, and an application layer running on top of the operating system layer. The hardware layer includes hardware such as a Central Processing Unit (CPU), a Memory Management Unit (MMU), and a memory (also referred to as a main memory). The operating system may be any one or more computer operating systems that implement business processing through processes (processes), such as a Linux operating system, a Unix operating system, an Android operating system, or a windows operating system. Furthermore, the embodiment of the present application does not particularly limit a specific structure of the execution subject of the method provided in the embodiment of the present application, as long as the program recorded with the code of the method provided in the embodiment of the present application can be run to perform communication according to the method provided in the embodiment of the present application, for example, the execution subject of the method provided in the embodiment of the present application may be a network device, or a functional module capable of calling a program and executing the program in the network device.

In the devices of fig. 6-11 of the present application, the respective components are communicatively connected, i.e., the processing unit (or processor), the storage unit (or memory), and the transceiving unit (transceiver) communicate with each other via internal connection paths, and control and/or data signals are transmitted. 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 having signal processing capabilities. In implementation, the steps of the above method embodiments may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The processor may be a Central Processing Unit (CPU), a Network Processor (NP), or a combination of a CPU and an NP, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component. The various methods, steps, and logic blocks disclosed in this application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in this application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor. Although only one processor is shown in the figure, the apparatus may comprise a plurality of processors or a processor may comprise a plurality of processing units. Specifically, the processor may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor.

The memory is used for storing computer instructions executed by the processor. The memory may be a memory circuit or a memory. The memory may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The non-volatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. Volatile memory can be Random Access Memory (RAM), 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 apparatus may comprise a plurality of memories or the memory may comprise a plurality of memory units.

The transceiver is used for enabling the processor to interact with the content of other units or network elements. Specifically, the transceiver may be a communication interface of the apparatus, a transceiving circuit or a communication unit, and may also be a transceiver. The transceiver may also be a communication interface or transceiving circuitry of the processor. Alternatively, the transceiver may be a transceiver chip. The transceiver may also include a transmitting unit and/or a receiving unit. In one possible implementation, the transceiver may include at least one communication interface. In another possible implementation, the transceiver may also be a unit implemented in software. In embodiments of the application, the processor may interact with other elements or network elements via 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 elements of the apparatus without going through the transceiver.

In one possible implementation, the processor, the memory, and the transceiver may be connected to each other by a bus. The bus may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc.

In the embodiments of the present application, the words "exemplary" or "such as" are used herein to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "e.g.," is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present concepts related in a concrete fashion.

In the embodiments of the present application, various illustrations are made for the sake of an understanding of aspects. However, these examples are merely examples and are not meant to be the best mode of practicing the present application.

In the embodiments of the present application, names of a request message, a response message, and other various messages are used for convenience of description. However, these messages are only used to illustrate the content to be carried or the functions to be implemented, and the specific names of the messages do not limit the application, for example: but also a first message, a second message, a third message, etc. These messages may be specific ones, and may be some fields in the messages. These messages may also represent various servicing operations.

In addition, various aspects or features of the present application may be implemented as a method, apparatus, or article of manufacture using standard programming and/or engineering techniques. The term "article of manufacture" as used herein is intended to encompass a computer program accessible from any computer-readable device, carrier, or media. For example, computer-readable media can include but are not limited to magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips, etc.), optical disks (e.g., compact Disk (CD), digital Versatile Disk (DVD), etc.), smart cards, and flash memory devices (e.g., erasable programmable read-only memory (EPROM), card, stick, key drive, etc.). In addition, various storage media described herein can represent one or more devices and/or other machine-readable media for storing information. The term "machine-readable medium" can include, without being limited to, wireless channels and various other media capable of storing, containing, and/or carrying instruction(s) and/or data.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one position, or may be distributed on multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method for obtaining network configuration information, the method comprising:

a policy control network element sends request information to a data analysis network element, wherein the request information is used for requesting network configuration information corresponding to each slice network list in at least one slice network list, each slice network list comprises one or more slice networks, the request information further comprises a service quality requirement of each slice network list, the network configuration information comprises a performance parameter or a specific setting parameter, and the specific setting parameter is used for a network management network element to execute network setting;

and the policy control network element receives the network configuration information corresponding to each slice network list sent by the data analysis network element, wherein the network configuration information is determined according to the service quality requirement of each slice network list.

2. The method of claim 1, wherein the request information includes an identification of the slice networks that the each slice network list includes.

3. The method of claim 1 or 2, wherein the quality of service requirements of each sliced network list comprises a quality of service requirement corresponding to each sliced network of the one or more sliced networks.

4. The method of claim 3, wherein the quality of service requirements for each of the slicing networks comprises quality of service requirements for one or more services in each of the slicing networks.

5. The method of claim 3, wherein the quality of service requirement for each of the sliced networks comprises a quality of service requirement for at least one user type in each of the sliced networks.

6. The method of claim 3, wherein the QoS requirement for each of the networks slices comprises a QoS requirement for at least one service in each of the networks slices, and the QoS requirement for the service is a user proportion requirement that satisfies a single-user QoS requirement for the service.

7. The method of claim 2, wherein the method further comprises: and the policy control network element determines the identifier of the one or more slicing networks included in each slicing network list according to the slicing network priority information.

8. The method of claim 1 or 2, further comprising: and the strategy control network element determines the service quality requirement of each slice network list according to the slice network priority information and/or the service priority information.

9. The method of claim 1 or 2, wherein the method further comprises:

and the policy control network element sends the network configuration information corresponding to a first slice network list to a network management network element, wherein the first slice network list is contained in the at least one slice network list.

10. The method of claim 9, wherein the method further comprises:

and the policy control network element determines the network configuration information corresponding to the first slice network list from the network configuration information corresponding to each slice network list sent by the data analysis network element according to the slice network priority information and/or the service priority information.

11. The method of claim 9, wherein the method further comprises:

and the policy control network element receives notification information sent by the network management network element, where the notification information is used to notify the policy control network element that the network management network element cannot perform network configuration according to the network configuration information corresponding to the first slice network list.

12. The method of claim 11, wherein the method further comprises:

the strategy control network element determines network configuration information corresponding to the second slice network list according to the notification information;

And the policy control network element sends the network configuration information corresponding to the second slice network list to the network management network element.

13. The method according to claim 11 or 12, wherein the notification information further comprises reason information indicating a reason why the network management network element is unable to perform network configuration.

14. The method according to claim 11 or 12, wherein the notification message further comprises network parameter measurements corresponding to the first list of sliced networks.

15. The method of claim 1 or 2, wherein the slice network is one of a network slice, a network slice instance, and a network slice subinstance.

16. A network device, characterized in that the network device comprises:

a processing unit, configured to determine request information, where the request information is used to request network configuration information corresponding to each slice network list in at least one slice network list, where each slice network list includes one or more slice networks, the request information further includes a service quality requirement of each slice network list, the network configuration information includes a performance parameter or a specific setting parameter, and the specific setting parameter is used for a network management network element to perform network setting;

A sending unit, configured to send the request information to a data analysis network element;

a receiving unit, configured to receive network configuration information corresponding to each slice network list sent by the data analysis network element, where the network configuration information is determined according to a quality of service requirement of each slice network list.

17. The network device according to claim 16, wherein the processing unit is specifically configured to determine, according to slicing network priority information, an identification of the one or more slicing networks included in each slicing network list, and determine that the identification of the one or more slicing networks included in each slicing network list is included in the request information.

18. The network device of claim 17, wherein the processing unit is further configured to determine a quality of service requirement for each of the sliced network lists according to sliced network priority information and/or traffic priority information, and determine that the quality of service requirement for each of the sliced network lists is also included in the request information.

19. The network device according to any one of claims 16 to 18, wherein the sending unit is further configured to send network configuration information corresponding to a first sliced network list to a network management network element, where the first sliced network list is included in the at least one sliced network list.

20. The network device according to claim 19, wherein the processing unit is further configured to determine the network configuration information corresponding to the first sliced network list from the network configuration information corresponding to each sliced network list sent by the data analysis network element according to sliced network priority information and/or service priority information.

21. The network device of claim 19, wherein the receiving unit is further configured to receive notification information sent by the network management element, where the notification information is used to notify a policy control element that the network management element cannot perform network configuration according to network configuration information corresponding to the first slice network list.

22. The network device of claim 21, wherein the processing unit is further configured to determine network configuration information corresponding to a second slice network list according to the notification information;

the sending unit is further configured to send the network configuration information corresponding to the second slice network list to the network management network element.

23. A chip for performing the method according to any one of claims 1 to 15.