CN110062407B

CN110062407B - Method and device for managing network slice performance

Info

Publication number: CN110062407B
Application number: CN201810055349.3A
Authority: CN
Inventors: 蒋若冰; 孙文琦; 冯珍妮; 陆伟; 杨水根; 谭巍
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2018-01-19
Filing date: 2018-01-19
Publication date: 2022-05-13
Anticipated expiration: 2038-01-19
Also published as: CN110062407A

Abstract

The application provides a method and a device for managing network slice performance, which can realize the management of the accessibility performance of resources or services of a network slice level. The method is performed by a network element management unit (EM) managing an access and mobility management function (AMF), the method comprising: the EM receives a network slice performance measurement request sent by a network slice management system, wherein the network slice performance measurement request is used for requesting measurement of the performance of a terminal device accessing a target network slice, and the AMF supports the target network slice; the EM acquires measurement data for the network slice performance measurement request; the EM transmits a measurement reply to the network slice management system corresponding to the network slice performance measurement request, the measurement reply including the measurement data.

Description

Method and device for managing network slice performance

Technical Field

The present application relates to the field of communications, and more particularly, to a method and apparatus for network slice performance management in the field of communications.

Background

One of the new features of the 5G communication system is to push out the concept of network slicing. A network slice is a logical network that can provide a particular network function, meeting the needs of a particular service, including a collection of network function modules and resources needed to complete a particular function or service. An operator may provide multiple network slice instances that can achieve the same network functionality for groups of users of different features or quality of service levels. The same user can also access multiple network slice instances simultaneously through the 5G access network to use different types of services provided by the network slice instances. In order to ensure unified support and cooperative operation of network slices by different operators in a global range, three slice/service types are proposed, namely enhanced mobile broadband service (eMBB), ultra-reliable low latency communications (URLLC) and massive Internet of Things (MIoT).

While network slices are a communication resource, existing network slice management systems do not provide a management scheme for accessibility performance (accessibility) of resources or services at the network slice or network slice instance level.

Disclosure of Invention

The application provides a method for managing network slice performance, which can realize the management of the accessibility performance of the resources or services of a network slice level.

In a first aspect, a method for network slice performance management is provided, where the method is performed by an element management unit (EM) that manages an access and mobility management function (AMF), and the method includes the EM receiving a network slice performance measurement request sent by a network slice management system, where the network slice performance measurement request is used to request measurement of performance of a terminal device accessing a target network slice, where the AMF supports the target network slice; the EM acquires measurement data for the network slice performance measurement request; the EM transmits a measurement reply to the network slice management system corresponding to the network slice performance measurement request, the measurement reply including the measurement data.

Therefore, in this embodiment of the present application, an EM (AMF-EM) that manages an AMF may obtain measurement data of performance of a terminal device accessing a target network slice according to a network slice performance measurement request sent by a network slice management system, and send the measurement data to the network slice management system, so that the network slice management system may obtain the performance of the terminal device accessing the network slice, thereby implementing management of accessibility performance of resources or services at a network slice level by the network slice management system.

Here, a plurality of different interactive processes, such as a registration process, a request service process, or a session establishment process, may occur when the terminal device uses the network slice. Correspondingly, the access procedure of the network slice may include a control plane access procedure and a user plane access procedure. Among them, the control plane access procedure may exist in the registration procedure and the request service procedure, and the user plane access procedure may exist in the registration procedure and the session establishment procedure.

Optionally, the network slice performance measurement request includes a first performance measurement type, where the first performance measurement type includes a control plane access success rate of the terminal device accessing the network slice and/or a parameter for determining the control plane access success rate;

when the first performance measurement type comprises the control plane access success rate, the measurement data comprises at least one of: the control plane access success rate, the control plane access failure rate, the control plane access attempt times, the control plane access success times and the control plane access failure times of the target network slice;

when the first performance measurement type includes a parameter for determining the control plane access success rate, the measurement data includes at least one of: the control plane access attempt times, the control plane access success times and the control plane access failure times of the target network slice;

the control plane access success rate is a ratio of control plane access success times to control plane access attempt times, and the control plane access failure rate is a ratio of control plane access failure times to control plane access attempt times.

Specifically, the terminal device may send a request message requesting to use the network slice to the AMF, where the request message may include NSSAI of the network slice that the terminal needs to use. Accordingly, the AMF receives the request message. Here, a process in which the terminal device transmits a message requesting use of the network slice to the AMF is referred to as a process in which the control plane of the terminal device attempts access. Specifically, the number of times the control plane attempts to access is the number of times the terminal device sends the message.

Specifically, after receiving a message for requesting to use a network slice sent by a terminal device, the AMF succeeds in accessing a control plane of the network slice by the terminal device when an S-NSSAI corresponding to the network slice carried in the request message is in a set of allowed NSSAIs (allowed NSSAIs). When the S-NSSAI corresponding to the network slice carried in the request message may be in the set of rejected NSSAIs (rejected NSSAIs), the control plane access to the network slice by the terminal device fails.

Optionally, the network slice performance measurement request includes a second performance measurement type, where the second performance measurement type includes a user plane access success rate of the terminal device accessing the network slice and/or a parameter for determining the user plane access success rate;

when the second performance measurement type comprises a user plane access success rate of a network slice, the measurement data comprises at least one of: the user plane access success rate, the user plane access failure rate, the user plane access attempt access times, the user plane access success times and the user plane access failure times of the target network slice;

when the second performance measurement type comprises a parameter for determining the user plane access success rate, the measurement data comprises at least one of: the access times of the user plane access attempt, the successful times of the user plane access and the failed times of the user plane access of the target network slice;

the user plane access success rate is the ratio of the user plane access success times to the user plane access attempt times, and the user plane access failure rate is the ratio of the user plane access failure times to the user plane access attempt times. In addition, the successful user plane access may be defined as that the network or the SMF successfully establishes the PDU session supported by the network slice for the terminal device, and the failed user plane access may be defined as that the network or the SMF establishes the PDU session supported by the network slice for the terminal device.

Optionally, the measurement data further includes a reason for a failure of user plane access, where the reason for the failure of user plane access includes at least one of: and an invalid request of the terminal equipment, and failure of data network authentication of a user request or failure of resource allocation of a wireless access network by a Session Management Function (SMF).

The measurement and statistics of the control plane access success rate and the user plane access success rate can be taken charge of by the network element AMF, and the network element AMF is involved in the processes of registration, service request, PDU Session establishment and the like, so that the network slice management system can more efficiently determine the performance of the terminal equipment accessing the network slice. Or, the measurement and statistics of the user plane access success rate may also be taken charge of by the SMF and sent to the network slice management system by the network element management unit SMF-EM of the SMF. In addition, the NEF may also provide measurement data to the network slice management system through its network element management function EM, that is, the NEF may also serve as a network element for counting all performance measurement data and results, except that the data provided by the NEF is obtained from a network element such as the relevant AMF or SMF. Because the statistics and the report of the control plane access success rate and/or the data plane access success rate can be carried out by different network elements, the network can be deployed flexibly.

Optionally, the network slice performance measurement request includes a third performance measurement type, where the third performance measurement type includes a load allocation rate of a network slice instance corresponding to a network slice and/or a parameter for determining the load allocation rate;

wherein, when the third performance measurement type comprises the load distribution ratio, the measurement data comprises at least one of: the load distribution rate of at least one network slice instance corresponding to the target network slice, the number of sessions supported by each network slice instance in the at least one network slice instance, and the total number of sessions supported by the target network slice;

when the third performance measurement type comprises a parameter for determining the load distribution ratio, the measurement data of the target network slice comprises at least one of: a number of sessions supported by each of the at least one network slice instance and a total number of sessions supported by the target network slice;

wherein the load distribution rate of each network slice instance in the at least one network slice instance is a ratio of the number of sessions supported by each network slice instance to the total number of sessions supported by the network slice.

For the network slice management system, the load distribution of each network slice instance under one network slice is also a performance index that needs to be concerned. Based on the load distribution rate of each slice example, the method can provide a basis for distributing specific network slice examples after the terminal equipment is accessed into one network slice, can also know the load condition of each network slice example in real time, and can adjust the capacity and performance of the slice examples in time.

Optionally, the network slice performance measurement request includes an identifier of all SMFs corresponding to each network slice instance in at least one network slice instance of the target network slice;

wherein the EM obtaining measurement data of the target network slice comprises:

the EM acquires SMF corresponding to each session in all the sessions supported by the target network slice;

and the EM determines the load distribution rate of the network slice instance corresponding to the target network slice or the parameters for determining the load distribution rate according to the SMF corresponding to each session and the identifications of all the SMFs corresponding to each network slice instance in at least one network slice instance.

Optionally, the measurement data of the target network slice further includes:

the number of sessions supported by each of all SMFs involved in the target network slice.

After the PDU Session is successfully established, the SMF sends information of success or failure of establishment to the AMF, so the AMF can know to which SMF network element each successfully established PDU Session of each network slice identified by the S-NSSAI is allocated. However, since the network element AMF may not be able to sense the network slice instance, that is, cannot know which slice instance each SMF network element belongs to, the network element AMF may not be able to directly count the load allocation rate of the network slice instance, but needs to send the measured related data (such as a parameter for calculating the load allocation rate) to the 3GPP management system or the network element in the network slice management system, and then the management network element capable of sensing the network slice instance performs the classification and statistics on the PDU Session number of each slice instance according to the network slice instance information to which each SMF belongs, and calculates the load allocation rate of each network slice instance.

Optionally, in this embodiment of the present application, the network slice measurement request message may further include an identifier of the target network slice. Specifically, the Identification (ID) of the network slice may be single network slice selection assistance information (S-NSSAI). Specifically, Network Slice Selection Assistance Information (NSSAI) may be used to identify a set of network slices that the UE may need to access. Here, NSSAI is a collection of one or more S-NSSAIs, which can uniquely identify a network slice. The S-NSSAI may include a slice/service type (SST) for describing services or characteristics of a network slice instance. The S-NSSAI may further include slice differentiation information (SD), which is supplementary information for further differentiating network slice instances when there are multiple network slice instances of the same slice/service type.

In a second aspect, a method for network slice performance management is provided, where the method is performed by a first network slice management function, and the method includes:

the first network slice management function unit sends a first network slice performance measurement request to at least one network element management unit (EM), wherein the first network slice performance measurement request is used for requesting measurement of performance of terminal equipment accessing a target network slice, and an access and mobility management function (AMF) managed by each EM in the at least one EM supports the target network slice;

the first network slice management function unit receives a first measurement reply corresponding to the first network slice performance measurement request sent by the each EM, the first measurement reply including measurement data for the first network slice performance measurement request.

Therefore, in this embodiment of the present application, an EM (AMF-EM) that manages the AMF may obtain measurement data of performance of a terminal device accessing a target network slice according to a network slice performance measurement request sent by a network slice management system, and send the measurement data to the network slice management system, so that the network slice management system can obtain the performance of the terminal device accessing the network slice, thereby implementing management of accessibility performance of resources or services at a network slice level by the network slice management system.

when the first performance measurement type comprises the control plane access success rate, the measurement data comprises at least one of: control plane access success rate, control plane access failure rate, control plane access attempt times, control plane access success times and control plane access failure times of the target network slice;

Specifically, the terminal device may send a message requesting to use the network slice to the AMF, where the message may include NSSAI of the network slice that the terminal needs to use. Accordingly, the AMF receives the message. Here, a process in which the terminal device transmits a message requesting use of the network slice to the AMF is referred to as a process in which the control plane of the terminal device attempts access. Specifically, the number of times the control plane attempts to access is the number of times the terminal device sends the message.

Specifically, after receiving the message sent by the terminal device to request to use the network slice, the AMF succeeds in controlling plane access to the network slice by the terminal device when the S-NSSAI corresponding to the network slice is in the set of allowed NSSAIs (allowed NSSAIs). When the S-NSSAI corresponding to the network slice may be in the set of rejected NSSAIs (rejected NSSAIs), then the control plane access of the terminal device to the network slice fails.

Optionally, the measurement data of the target network slice further includes a reason for a failure of user plane access, where the reason for the failure of user plane access includes at least one of: and an invalid request of the terminal equipment, and failure of data network authentication of a user request or failure of resource allocation of a wireless access network by a Session Management Function (SMF).

Optionally, the measurement data of the target network slice further includes:

a number of sessions supported by each of all SMFs involved in the target network slice;

the method further comprises the following steps:

and the first network slice management functional unit determines a network slice instance load distribution rate corresponding to the target network slice or a parameter for determining the load distribution rate according to the number of sessions supported by each SMF and the identification of the SMF corresponding to each network slice instance in the at least one network slice instance.

Optionally, when the number of the at least one EM is at least two, the method further comprises:

and the first network slice management functional unit determines the performance of the terminal equipment accessing the target network slice according to the measurement data acquired by each EM.

Optionally, before the first network slice management functional unit sends the first network slice performance measurement request to the at least one network element management unit EM, the method further includes:

the first network slice management functional unit receives a second network slice performance measurement request sent by a second network slice management functional unit, wherein the second network slice performance measurement request is used for requesting to measure the performance of a terminal device accessing the target network slice, and the first network slice management functional unit belongs to a network slice management functional unit in the management domain of the second network slice management functional unit;

after receiving the first measurement reply, the first network slice management functional unit further includes:

sending a second measurement reply corresponding to the second network slice performance measurement request to the second network slice management function, the second measurement reply including measurement data for the second network slice performance measurement request.

In a third aspect, a method for network slice performance management is provided, where the method is performed by a second network slice management function unit, and the method includes:

the second network slice management functional unit sends a second network slice performance measurement request to at least one first network slice management functional unit, the second network slice performance measurement request is used for requesting to measure the performance of a terminal device accessing a target network slice, the first network slice management functional unit belongs to a network slice management functional unit in a management domain of the second network slice management functional unit, and the management domain of the first network slice management functional unit comprises a network element management unit EM used for managing access corresponding to the target network slice and a mobility management function AMF;

the second network slice management function unit receives a second measurement reply corresponding to the second network slice performance measurement request, which is sent by each first network slice management function unit and includes measurement data for the second network slice performance measurement request.

Optionally, when the number of the at least one first network slice management function unit is at least two, the method further includes:

and the second network slice management functional unit determines the performance of the terminal equipment accessing the target network slice according to the measurement data acquired by each first network slice management functional unit.

In a fourth aspect, an apparatus for network slice performance management is provided, configured to perform the method in the first aspect or any possible implementation manner of the first aspect. In particular, the apparatus for network slice performance management comprises means for performing the method of the first aspect described above or any possible implementation manner of the first aspect.

In a fifth aspect, an apparatus for network slice performance management is provided, configured to perform the method of the second aspect or any possible implementation manner of the second aspect. In particular, the apparatus for network slice performance management comprises means for performing the method of the second aspect described above or any possible implementation manner of the second aspect.

A sixth aspect provides an apparatus for network slice performance management, configured to perform the method in the third aspect or any possible implementation manner of the third aspect. In particular, the apparatus for network slice performance management comprises means for performing the method of the third aspect described above or any possible implementation manner of the third aspect.

In a seventh aspect, an apparatus for network slice performance management is provided, where the apparatus for network slice performance management includes: a transceiver, a memory, a processor, and a bus system. Wherein the transceiver, the memory and the processor are connected by the bus system, the memory is configured to store instructions, and the processor is configured to execute the instructions stored by the memory to control the transceiver to receive and/or transmit signals, and when the processor executes the instructions stored by the memory, the execution causes the processor to perform the method of the first aspect or any possible implementation manner of the first aspect.

In an eighth aspect, an apparatus for network slice performance management is provided, and the apparatus for network slice performance management includes: a transceiver, a memory, a processor, and a bus system. Wherein the transceiver, the memory and the processor are connected by the bus system, the memory is used for storing instructions, the processor is used for executing the instructions stored by the memory to control the transceiver to receive and/or transmit signals, and when the processor executes the instructions stored by the memory, the execution causes the processor to execute the method of the second aspect or any possible implementation manner of the second aspect.

In a ninth aspect, an apparatus for network slice performance management is provided, and the apparatus for network slice performance management includes: a transceiver, a memory, a processor, and a bus system. Wherein the transceiver, the memory and the processor are connected by the bus system, the memory is used for storing instructions, the processor is used for executing the instructions stored by the memory to control the transceiver to receive and/or transmit signals, and when the processor executes the instructions stored by the memory, the execution causes the processor to execute the method in any possible implementation manner of the third aspect or the third aspect.

In a tenth aspect, a computer-readable medium is provided for storing a computer program comprising instructions for performing the method in any possible implementation of the first aspect described above.

In an eleventh aspect, a computer-readable medium is provided for storing a computer program comprising instructions for performing the method in any possible implementation of the second aspect described above.

In a twelfth aspect, a computer-readable medium is provided for storing a computer program comprising instructions for performing the method in any possible implementation of the third aspect described above.

In a thirteenth aspect, there is provided a computer program product comprising: computer program code which, when run by a communication unit, a processing unit or a transceiver, a processor of a communication device (e.g. an apparatus for network slice performance management), causes the apparatus for beam training to perform the method of any possible implementation of the first aspect described above.

In a fourteenth aspect, there is provided a computer program product comprising: computer program code which, when run by a communication unit, processing unit or transceiver, processor of a communication device (e.g. an apparatus for network slice performance management), causes the apparatus for beam training to perform the method in any possible implementation of the second aspect described above.

In a fifteenth aspect, a computer program product is provided, the computer program product comprising: computer program code which, when run by a communication unit, a processing unit or a transceiver, a processor of a communication device (e.g. an apparatus for network slice performance management), causes the apparatus for beam training to perform the method of any possible implementation of the third aspect described above.

Drawings

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

Fig. 2 is a schematic diagram illustrating multiple network slice examples under different network slices according to an embodiment of the present application.

Fig. 3 is a schematic diagram illustrating a control plane access procedure according to an embodiment of the present application.

Fig. 4 shows a schematic diagram of a system architecture of a specific embodiment of the present application.

FIG. 5 is a schematic diagram of a system architecture illustrating another embodiment of the present application

Fig. 6 shows a schematic diagram of a system architecture of another embodiment of the present application.

Fig. 7 is a schematic flow chart illustrating a method for network slice performance management according to an embodiment of the present application.

Fig. 8 shows a schematic diagram of a system architecture of another embodiment of the present application.

Fig. 9 is a schematic flow chart of another method for network slice performance management provided in an embodiment of the present application.

Fig. 10 is a schematic block diagram illustrating an apparatus for network slice performance management according to an embodiment of the present application.

Fig. 11 is a schematic block diagram illustrating another apparatus for network slice performance management according to an embodiment of the present application.

Fig. 12 is a schematic block diagram illustrating another apparatus for network slice performance management according to an embodiment of the present application.

Fig. 13 is a schematic block diagram illustrating another apparatus for network slice performance management according to an embodiment of the present application.

Fig. 14 is a schematic block diagram illustrating another apparatus for network slice performance management according to an embodiment of the present application.

Fig. 15 is a schematic block diagram illustrating another apparatus for network slice performance management 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.

The technical scheme of the embodiment of the application can be applied to various communication systems, for example: a global System for Mobile communications (GSM) System, a Code Division Multiple Access (CDMA) System, a Wideband Code Division Multiple Access (WCDMA) System, a General Packet Radio Service (GPRS), a Long Term Evolution (Long Term Evolution, LTE) System, an LTE Frequency Division Duplex (FDD) System, an LTE Time Division Duplex (TDD), a Universal Mobile Telecommunications System (UMTS), a Worldwide Interoperability for Microwave Access (WiMAX) communication System, a future fifth Generation (5G) System, or a New Radio Network (NR), etc.

Terminal equipment in the embodiments of the present application may refer to user equipment, access terminals, subscriber units, subscriber stations, mobile stations, remote terminals, mobile devices, user terminals, wireless communication devices, user agents, or user devices. The terminal device may also be 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 function, a computing device or other processing device connected to a Wireless modem, a vehicle-mounted device, a wearable 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, which are not limited in this embodiment.

The Network device in this embodiment may be a device for communicating with a terminal device, where the Network device may be a Base Transceiver Station (BTS) in a Global System for Mobile communications (GSM) System or a Code Division Multiple Access (CDMA) System, may also be a Base Station (NodeB, NB) in a Wideband Code Division Multiple Access (WCDMA) System, may also be an evolved node b (eNB, eNodeB) in an LTE System, may also be a wireless controller in a Cloud Radio Access Network (CRAN) scenario, or may be a relay Station, an Access point, a vehicle-mounted device, a wearable device, a Network device in a future 5G Network, or a Network device in a future evolved PLMN Network, and the like, and the embodiment of the present invention is not limited.

Fig. 1 is a schematic diagram of a system architecture according to an embodiment of the present application. The system architecture includes a network slice management system 110, an element management unit (EM) 14, a Network Element (NE) 15, and optionally a virtual network function management unit (VNFM) 16. The NE may specifically be an access and mobility management function (AMF), a Session Management Function (SMF), or a network capability openness function (NEF), and the EM14 is a management unit of the NE. A VNFM managed Virtual Network Function (VNF) may be a module or unit having an access and mobility management function or a session management function, and there is a communication interface between VNFM16 and EM 14. The element management unit EM may also be referred to herein as an element manager.

The network slice management system 110 may include a first network slice management function unit 11 and/or a second network slice management function unit 12, among others. In addition, the network slice management system 110 may further include a Communication Service Management Function (CSMF) 13. The network slice management system 110 is mainly responsible for managing network slices in the system, such as unifying network slice related terms and specifications, creating corresponding network slices for different service types, fault configuration, charging, performance and security (FCAPS) management of network slice instances, automation of network slice management, orchestration of network slices, management of shared network slice instances, orchestration of network slices across different management domains, and the like.

Specifically, the first network slice management function unit 11 may be a Network Slice Subnet Management Function (NSSMF). The second network slice management functional unit 12 may be a Network Slice Management Function (NSMF) or a cross-domain NSSMF, and at this time, the second network slice management functional unit may be denoted as NSMF/NSSMF, that is, in this embodiment, the NSMF/NSSMF may represent NSMF or a cross-domain NSSMF.

Specifically, the CSMF translates communication service related requirements into network slice related requirements and passes information of the related service requirements and management responsibilities to the network slice management function, NSMF, through an interface with the NSMF. Here, the requirement related to the communication service is, for example, a network type, a capacity, a Quality of service (QoS) requirement, or the like. The NSMF is responsible for the management and orchestration of network slice instances and communicates subnet management requirements to the NSSMF over an interface with the NSSMF. NSSMF is responsible for the management and orchestration of network slice subnet instances. Specifically, the network slice subnet management request may be obtained through an interface with the NSMF.

In the embodiment of the present application, one or more network slice instances may exist under one network slice. Fig. 2 shows a schematic diagram of multiple network slice instances under a different network slice. In particular, S-NSSAI₁Can be used to identify network slice #1, S-NSSAI₂May be used to identify network slice # 2. And, AMF, SMF₁And SMF₂Both support network slice #1 and network slice #2, AMF and SMF₃Network slice #2 is supported. Under network slice #1, there are two network slice instances, respectively NSI₁₁And NSI₁₂Wherein NSI₁₁From AMF and SMF₁Support, NSI₁₂From AMF and SMF₂And (4) supporting. Network slice #2 is followed by a network slice instance NSI₂₁，NSI₂₁From AMF and SMF₃And (4) supporting.

In this embodiment, an Identifier (ID) of a network slice may be single network slice selection assistance information (S-NSSAI). Specifically, Network Slice Selection Assistance Information (NSSAI) may be used to identify a set of network slices that the UE may need to access. Here, NSSAI is a collection of one or more S-NSSAIs, which can uniquely identify a network slice. The S-NSSAI may include a slice/service type (SST) for describing services or characteristics of a network slice instance. The S-NSSAI may further include slice differentiation information (SD), which is supplementary information for further differentiating network slice instances when there are multiple network slice instances of the same slice/service type.

In the embodiment of the application, the network slice is used as a communication resource, and the availability of the resource of the network slice can be monitored. Specifically, the detection of the resource availability of the network slice may be implemented by monitoring the access performance of the terminal device to the network slice. Therefore, in the embodiment of the present application, the management of the access performance (access availability) of the network slice may be realized by measuring the performance of the terminal device accessing the network slice.

Here, a process in which a terminal device accesses a network slice may be referred to as an access process of the network slice. Specifically, when the terminal device uses the network slice, a plurality of different interactive processes may occur, such as a registration process, a service request process, or a session establishment process. Correspondingly, the access procedure of the network slice may include a control plane access procedure and a user plane access procedure. Among them, the control plane access procedure may exist in the registration procedure and the request service procedure, and the user plane access procedure may exist in the registration procedure and the session establishment procedure. In this embodiment, the session may specifically be a Protocol Data Unit (PDU) session. For convenience of description, the session establishment procedure will be described as an example of the PDU session establishment procedure.

In the embodiment of the application, in the process that the terminal device may use the network slice, there are possibilities that the terminal device attempts to access the network slice, the network slice is successfully accessed, or the network slice is unsuccessfully accessed, so that management of the access performance of the network slice can be achieved by calculating the access success rate of the terminal device accessing the network slice.

Optionally, the access success rate of the terminal device accessing the network slice may include a control plane access success rate, where the control plane access success rate is a success rate of a control plane of the terminal device accessing the network slice, and the measurement of the control plane access success rate relates to a registration process, a service request process, or other processes.

Specifically, fig. 3 shows a schematic diagram of a control plane access procedure.

The end device sends a request message for using the network slice to the AMF 310, where the request message may include NSSAI of the network slice that the end device needs to use, where NSSAI may include a set of S-NSSAIs. Accordingly, the AMF receives the request message. Specifically, the request message may be a registration request or a service request.

In this embodiment, a process in which the terminal device sends a message requesting use of the network slice to the AMF is referred to as a process in which the control plane of the terminal device attempts access. Specifically, the number of times that the control plane attempts to access is the number of times that the terminal device sends the message.

At 320, the AMF sends a response message to the end device corresponding to the request message at 310, specifically the response message may indicate that the end device is allowed to use the network slice or indicate that the end device is denied to use the network slice. Accordingly, the terminal device receives the response message sent by the AMF. And, when the request message in 310 is a registration request, the response message is a registration response, and when the request message in 310 is a service request, the response message is a service response.

Specifically, after receiving a request message for requesting to use a network slice sent by a terminal device, the AMF may determine whether the user may use the network slice requested to be used according to subscription information of the user or information of other users. After determining the network slice that can be used or cannot be used by the user, a response corresponding to the request message in 310 may be sent to the terminal device, and specifically, the response may include a set of allowed nssais (allowed nssais) and/or a set of rejected nssais (rejected nssais). Specifically, the allowed NSSAI set and the rejected NSSAI set may be determined by the AMF in real time and comprehensively according to the user request, the user subscription information, and other information.

When the S-NSSAI corresponding to the network slice carried in the request message in 310 is in the set of allowed NSSAIs (allowed NSSAIs), the terminal device accesses the control plane of the network slice successfully. When the S-NSSAI corresponding to the network slice carried in the request message in 310 is in the set of rejected NSSAIs (rejected NSSAIs), the control plane access to the network slice by the terminal device fails.

The access success rate of the terminal device to the network slice may include a control plane access success rate. The control plane access success rate refers to a ratio of the control plane access success number to the control plane access attempt number, and specifically, the control plane access attempt number is a sum of the control plane access success number and the control plane access failure number. Correspondingly, the control plane access failure rate is the ratio of the control plane access failure times to the control plane access attempt times.

Optionally, the access success rate of the terminal device accessing the network slice may include a user plane access success rate, which is a success rate of the user plane of the terminal device accessing the network slice, and the measurement of the user plane access success rate relates to a registration process, a PDU session establishment process, or other processes.

Specifically, the successful user plane access may be defined as that the network or the SMF successfully establishes the PDU session supported by the network slice for the terminal device, and the failed user plane access may be defined as that the network or the SMF fails to establish the PDU session supported by the network slice for the terminal device. Here, the reason for the user plane access failure may be various reasons, for example, radio access network resource allocation failure (RAN resource/channel allocation failure), data network authentication failure (DN authentication/authentication failure) of the SMF to the user request, a user request not valid (UE request not valid), and the like, which is not limited in the embodiment of the present application.

The user plane access success rate may be defined as a ratio of the number of successful user plane accesses to the number of attempted user plane accesses, and specifically, the number of attempted user plane accesses is the sum of the number of successful user plane accesses and the number of failed user plane accesses. Correspondingly, the user plane access failure rate is the ratio of the number of times of user plane access failure to the number of times of user plane access attempt.

When a network slice indicated by S-NSSAI relates to an AMF element, the AMF element or a related element (such as SMF or NEF) may measure and count a control plane access success rate and a user plane access success rate of the network slice.

When a network slice indicated by S-NSSAI relates to multiple AMFs or SMF network elements, a network element (e.g., NSSMF or NSMF) in a network slice management system needs to count data measured by the multiple AMFs or SMFs, so as to determine a control plane access success rate and a user plane access success rate of the network slice. At this time, the multiple AMFs or SMFs are required to send the parameters for determining the control plane access success rate and the parameters for determining the user plane access success rate to the network slice management system through the network element management unit EM that manages the AMFs or SMFs, and the network slice management system determines the control plane access success rate and the user plane access success rate of the network slice according to the data measured by the AMFs or SMFs.

Optionally, in this embodiment of the present application, the management of the resource access performance of the network slice may be implemented by calculating load allocation rates of a plurality of network slice instances under the network slice.

Specifically, after a terminal device successfully accesses a network slice, the terminal device is assigned to a specific network slice instance below the network slice to complete a communication service (when there are multiple network slice instances below the network slice). The load distribution rate of a network slice instance under a network slice is defined as the ratio of the number of pduses corresponding to (i.e., supported by) the network slice instance to the number of total PDU sessions supported by the network slice. The measurement and statistics of the load distribution rate of the network slice instance relate to the successful access procedure of the network slice user plane, i.e. the successful establishment procedure of the PDU Session. And, the number of total PDU sessions supported by the network slice is the same as the number of successful user plane accesses.

Therefore, in the embodiment of the present application, the performance of the terminal device accessing the network slice is represented by three performance measurement types, i.e., the network slice management system in the embodiment of the present application may manage the accessibility performance of the resource or service of the network slice according to one of the performance of the control plane access success rate, the user plane access success rate, and the load distribution rate of the network slice instance.

In the embodiment of the present application, the time delay of accessing the network slice refers to the time required for the process of accessing the network slice. Specifically, the time when the network receives the access request sent by the terminal device and the time when the network completes the access process and sends the response message to the terminal device may be measured, and the time difference between the time when the network receives the access request sent by the terminal device and the time when the network completes the access process and sends the response message to the terminal device may be determined as the time delay of accessing the network slice.

Fig. 4 shows a schematic diagram of a system architecture of a specific embodiment of the present application. The system architecture includes a Network Element (NE)/Virtual Network Function Manager (VNFM), a network Element Manager (EM), an NSSMF, an NSMF, and a Network Manager (NM). Here, the network slice management system includes an NSMF and an NSSMF, where the NSSMF may be specifically the first network slice management functional unit, and the NSMF may be specifically the second network slice management functional unit.

In the embodiment of the application, the NE/VNFM may measure the resource access performance. For example, various parameters for determining access success rate of a network slice, load distribution rate of network slice instances, may be measured. In this embodiment, each parameter obtained by measuring the NE/VNFM and the performance of the network slice, such as the access success rate of the network slice and the load distribution rate of the network slice instance, determined by the NE/VNFM according to the parameter may be referred to as performance measurement data of the network slice. Also, the NE/VNFM may report the obtained performance measurement data of the network slice to the EM. In some possible embodiments, the NE/VNFM may be AMF or SMF.

The EM may configure and manage the NE/VNFM. Specifically, the NE/VNFM may be instructed to perform network slice performance measurement and receive network slice performance measurement data sent by the local NE/VNFM. Meanwhile, the EM also needs to receive a network slice performance management request sent by the network slice management system and send a performance management response (containing performance measurement data) to the network slice performance management request.

The NSSMF may instruct the network function involved in the relevant network slice and its management unit EM to perform network slice performance measurements. Specifically, a performance management request may be transmitted to the EM of the corresponding domain, and a performance management response transmitted by the EM of the corresponding domain may be received. NSSMF may also receive performance management requests from and send performance management responses to the NSMF/NSSMF/NM (e.g., NSMF or NM) in a higher level management domain.

The NSMF or NM may make a performance management request to the NSSMF or EM and, in response, receive a performance management response sent by the NSSMF or EM. Further, the performance measurement result of the network slice may be generated based on the performance measurement data included in the acquired performance management response.

It should be noted that the embodiment of the present application is described by taking the system architecture shown in fig. 4 as an example, but the embodiment of the present application is not limited thereto. In particular, in some possible implementations, the NSMF may be one functional unit with the NM, or the NSMF may be in the NM, that is, the NM may include a module having the same or similar function as the NSMF. At this time, if NSSMF and EM are two separate functional units, NSSMF and NSMF can reuse the existing interface between EM and NM for communication. If the functionality of NSSMF and EM is incorporated in a new network element (e.g. AM), the communication between NSSMF and NSMF and the communication between EM and NM use the interface between NM and AM.

In other possible implementations, NSMF and NM are independent of each other. At this time, if NSSMF and EM are two separate functional units, information interaction is performed according to the connection relationship in fig. 4, and a new communication interface needs to be established between NSSMF and EM. If the NSSMF and EM functions are merged in a new network element (e.g. AM), AM needs to establish a new interface with NSMF and NM, respectively, for information interaction.

Fig. 5 shows a schematic diagram of a system architecture of a specific embodiment of the present application. When only one AMF supports the target network slice for which performance measurements are required and is managed by only one NSSMF, it may correspond to the system architecture shown in fig. 5. At this time, the access success rate of the target network slice and the load distribution rate of the network slice instance under the target network slice can be measured, counted, calculated and uploaded by the AMF or the AMF-EM. It is understood that in the embodiment of the present application, the AMF-EM is an EM for configuring and managing the AMF.

Fig. 6 shows a schematic diagram of a system architecture of another embodiment of the present application. When there are multiple AMFs supportingThe target network slice for which performance measurements are required, and these AMFs are managed by a single NSSMF, may correspond to the system architecture shown in fig. 6. For example, different AMFs supporting a target network slice may be located in different geographic areas or may serve different groups of users (e.g., AMFs)₁In region 1, AMF₂Located in region 2), but these AMFs may still be managed by one NSSMF. At this time, one subdomain of the target network slice may correspond to one AMF or AMF-EM, and the access success rate of the target network slice in each subdomain and the load distribution rate of the network slice instance under the target network slice may be measured, counted, calculated, and uploaded by the AMF or AMF-EM in the subdomain, and each AMF or AMF-EM may also upload parameters used for determining the access success rate of the target network slice and the load distribution rate of the network slice instance under the target network slice in its corresponding subdomain.

701, the network slice management system sends a network slice performance measurement request to the EM. Correspondingly, the EM receives the network slice performance measurement request sent by the network slice management system.

Specifically, in this embodiment, NSSMF or NSMF in the network slice management system may send the network slice performance measurement request to an EM (i.e., AMF-EM) that manages the AMF, where the network slice performance measurement request is used to request to measure performance of a terminal device accessing a target network slice, where the AMF supports the target network slice. For convenience of description, the NSSMF in the network slice management system will be described as an example of managing the performance of a network slice.

In particular, the NSSMF may be a network element in a network slice management system. The NSSMF may here relate to one or more AMF-EM. In particular, when the NSSMF relates to an AMF-EM in the method of network slice performance management shown in fig. 7, it may correspond to the system architecture shown in fig. 5. When the NSSMF refers to multiple AMFs-EM in the method of network slice performance management shown in fig. 7, it may correspond to the system architecture shown in fig. 6.

The NSSMF may generate a network slice performance measurement request for the target network slice or receive a network slice performance measurement request from a higher level management network element (e.g., an NSMF or a higher level NSSMF). The NSSMF then sends the network slice performance measurement request to the EM (AMF-EM) that supports all AMFs for the target network slice.

In some specific implementations, the network slice performance measurement request may carry an identifier of the target network slice. As an example, the marker may be S-NSSAI. Specifically, the identifier may refer to the description above, and is not described herein again to avoid repetition.

Optionally, in this embodiment of the application, the network slice performance measurement request may include an indication of a first performance measurement type, where the first performance measurement type includes a control plane access success rate at which the terminal device accesses the network slice and/or a parameter used for determining the control plane access success rate.

Specifically, the access success rate of the terminal device accessing the network slice control plane and the parameter for determining the access success rate of the control plane may refer to the description above, and for avoiding repetition, the description is not repeated here.

Optionally, in this embodiment of the present application, the network slice performance measurement request includes an indication of a second performance measurement type, where the second performance measurement type includes a user plane access success rate of the terminal device accessing the network slice and/or a parameter for determining the user plane access success rate.

Specifically, the user plane access success rate of the terminal device accessing the network slice and the parameter for determining the user plane access success rate may refer to the description above, and are not described herein again to avoid repetition.

Optionally, in this embodiment of the application, the network slice performance measurement request includes an indication of a third performance measurement type, where the third performance measurement type includes a load distribution rate of a network slice instance corresponding to the network slice or a parameter used for determining the load distribution rate.

Specifically, the load distribution rate of the network slice example corresponding to the network slice or the parameter for determining the load distribution rate may refer to the description above, and is not described herein again to avoid repetition.

In the embodiment of the application, when the target network slice only relates to one AMF, the AMF-EM may obtain a measurement result of the target network slice according to data obtained by its own measurement. When the target network slice relates to a plurality of AMF network elements, NSSMF is required to count data measured by the plurality of AMFs or SMFs, so as to determine a control plane access success rate, a user plane access success rate, or a load distribution rate of a network slice example of the target network slice. At this time, the AMFs are required to send parameters for determining the control plane access success rate, parameters for determining the user plane access success rate, and/or parameters for determining the load distribution rate to the NSSMF through the AMF-EM, and the NSSMF determines the control plane access success rate and the user plane access success rate of the target network slice according to data measured by the AMF-EM.

Optionally, when the network slice performance measurement request includes the indication of the third performance measurement type, the network slice performance measurement request may further include an identifier of an SMF involved in each of at least one network slice instance of the target network slice.

Specifically, when the measurement request includes an indication of the load distribution rate of the network slice instance under the target network slice, if the AMF can sense the network slice instance, the AMF may directly measure the parameter for determining the load distribution rate of each network slice instance, and further determine the load distribution rate of each network slice instance.

There may be two solutions if the AMF is not aware of the network slice instance. The first solution is that the network slice performance measurement request may carry the identities of all SMFs involved in each network slice instance, at this time, the AMF-EM may count the number of PDU sessions supported by the network slice instance to be measured according to the specified SMF identities, and may further calculate the load distribution rate of the network slice instance to be measured by NSSMF.

The second solution is that the network slice performance measurement request may carry indication information indicating that the corresponding AMF-EM counts SMFs of all PDU sessions supported by the target network slice, and then the AMF-EM may report the number of PDU sessions supported by each SMF, and NSSMF calculates the load distribution rate of each network slice instance according to the network slice instance NSI to which each SMF belongs. Since the scheme two AMF-EM needs to upload the number of PDU sessions supported by all SMFs, NSSMF can simultaneously calculate the load distribution rate of all network slice instances under the target network slice.

The EM acquires measurement data 702.

In particular, the AMF-EM may instruct the AMF to perform performance measurements on the target network slice. After obtaining the measurement data, the AMF sends the measurement data to the AMF-EM.

Optionally, when the performance measurement type included in the network slice performance measurement request includes a control plane access success rate, the measurement data may include at least one of the following: the control plane access success rate, the control plane access failure rate, the control plane access attempt times, the control plane access success times and the control plane access failure times of the target network slice. When the performance measurement type included in the network slice performance measurement request includes a parameter for determining the control plane access success rate, the measurement data may include at least one of: and the control plane access attempt times, the control plane access success times and the control plane access failure times of the target network slice.

Optionally, when the performance measurement type included in the network slice performance measurement request includes a user plane access success rate, the measurement data may include at least one of the following: the user plane access success rate, the user plane access failure rate, the user plane access attempt access times, the user plane access success times and the user plane access failure times of the target network slice. When the performance measurement type included in the network slice performance measurement request includes a parameter for determining the user plane access success rate, the measurement data includes at least one of: and the access times of the user plane access attempt, the successful times of the user plane access and the failed times of the user plane access of the target network slice.

Optionally, the measurement data further includes a reason for the failure of the user plane access, where the reason for the failure of the user plane access includes: and an invalid request of the terminal equipment, and failure of data network authentication of a user request or failure of resource allocation of a wireless access network by a Session Management Function (SMF). At this time, the network slice management system may count the number of times of the network slice user plane access failure according to different failure reasons, or the network slice management system may configure and adjust different types of resources of the network slice according to the user plane access failure rates of different reasons.

Optionally, when the performance measurement type included in the network slice performance measurement request includes a load allocation rate of a network slice instance corresponding to the network slice, the measurement data may include at least one of the following: the load distribution rate of at least one network slice instance corresponding to the target network slice, the number of sessions supported by each of the at least one network slice instance, and the total number of sessions supported by the target network slice. When the network slice performance measurement request includes a performance measurement type including a parameter for determining the load distribution rate, the measurement data of the target network slice includes at least one of: a number of sessions supported by each of the at least one network slice instance and a total number of sessions supported by the target network slice.

Optionally, when the network slice performance measurement request includes an identifier of an SMF corresponding to each network slice instance in at least one network slice instance of the target network slice, the EM obtains the SMF corresponding to each session in all sessions supported by the target network slice, and then determines a network slice instance load distribution rate corresponding to the target network slice or a parameter for determining the load distribution rate according to the SMF corresponding to each session and the identifiers of all SMFs corresponding to each network slice instance in the at least one network slice instance.

When the target network slice is supported by multiple AMFs, since the control plane access success rate, the user plane access success rate, or the load distribution rate of the target network slice instance of each AMF or the EM statistics of the AMF may have special significance, such as geographical range, user group type, etc., the performance measurement results such as the access rate, the load distribution rate, etc., calculated in each AMF range are also valuable, and thus when each AMF sends the parameter for determining the access rate or the parameter for calculating the load distribution rate to the NSSMF, the performance measurement results such as the access rate, the load distribution rate, etc., calculated in each AMF range may also be sent to the NSSMF.

Optionally, the measurement result may further include: the target network slice refers to the number of sessions supported by each of all SMFs involved in the target network slice.

Specifically, when the AMF cannot perceive the network slice instance, the measurement result may carry the number of PDU sessions supported by each of all SMFs involved in the target network slice.

703, the EM sends a measurement reply corresponding to the network slice performance measurement request to the network slice management system, the measurement reply including the measurement data.

Correspondingly, the network slice management system receives a measurement reply sent by the EM and corresponding to the network slice performance measurement request.

The network slice management system determines performance measurements for the target network slice based on the received measurement reply 704.

In the embodiment of the application, when the target network slice only relates to one AMF, the AMF-EM may obtain a measurement result of the target network slice according to data obtained by its own measurement. When the target network slice relates to a plurality of AMF network elements, a network slice management system needs to count data measured by the plurality of AMFs or SMFs, so as to determine a control plane access success rate, a user plane access success rate, or a load distribution rate of a network slice example of the target network slice. At this time, the multiple AMFs are required to send parameters for determining the control plane access success rate, parameters for determining the user plane access success rate, and/or parameters for determining the load distribution rate to the network slice management system through the AMF-EM, and the network slice management system determines the control plane access success rate and the user plane access success rate of the target network slice according to data measured by the AMF-EM.

Specifically, when the number of AMFs-EMs is only one, and the measurement reply includes a control plane access success rate, a user plane success access rate, or a load distribution rate of a network slice instance under the target network slice, the NSSMF may determine, according to the measurement data, a performance measurement result of the target network slice, that is, determine performance of the terminal device accessing the target network slice. That is, at this time, the AMF or AMF-EM may process the measurement data to obtain a measurement result corresponding to the target network slice, and report the measurement result to the NSSMF.

When the measurement data includes a parameter (i.e., measurement data) for determining a control plane access success rate for the terminal device to access the target network slice, the NSSMF may determine the control plane access success rate for the terminal device to access the target network slice according to the measurement data.

For example, in the case that the number of AMFs is two and the AMFs are AMF1 and AMF2, when the number of successful accesses of the control plane in the measurement result corresponding to the EM of AMF1 is 3, the number of attempted accesses of the control plane is 5, the number of successful accesses of the control plane in the measurement result corresponding to the EM of AMF2 is 4, and the number of attempted accesses of the control plane is 6, the NSSMF may determine that the successful access rate of the control plane of the target network slice is a ratio of (3+4) to (5+6), that is, 0.64.

When the measurement data includes a parameter for determining the user plane access success rate of the terminal device accessing the target network slice, the NSSMF may determine the user plane access success rate of the terminal device accessing the target network slice according to the measurement data.

For example, in the case that the number of AMFs is two and the AMFs are AMF1 and AMF2, respectively, when the number of successful accesses of the user plane in the measurement result corresponding to the EM of AMF1 is 5, the number of attempted accesses of the user plane is 7, the number of successful accesses of the user plane in the measurement result corresponding to the EM of AMF2 is 4, and the number of attempted accesses of the user plane is 5, the NSSMF may determine that the user plane successful access rate of the target network slice is a ratio of (5+4) to (7+5), that is, 0.75.

When the measurement data includes a parameter for determining a load distribution rate of a network slice instance under the target network slice, the NSSMF may determine the load distribution rate of the network slice instance from the measurement data.

For example, if the target network slice relates to SMF11, SMF12, SMF21, where SMF11 and SMF12 support slice instance NSI1, SMF21 supports slice instance NSI2, the number of AMFs supporting the target network slice is two and is AMF1 and AMF2, respectively, AMF1 is required to measure the number of sessions supported by SMF11 and SMF12, respectively, and AMF2 is required to measure the number of sessions supported by SMF 21. At this time, the number of sessions supported by SMF11 and SMF12 in the performance measurement data of the EM of AMF1 is 3, 5, the number of sessions supported by SMF21 in the performance measurement data of the EM of AMF2 is 10, NSSMF may determine that the total number of sessions supported by the target network slice is (3+5+10), and the load allocation rate of the network slice instance NSI1 is the ratio of (3+5) to (3+5+10), that is, 0.44, and the load allocation rate of the network slice NSI2 is the ratio of 10 to (3+5+10), that is, 0.56.

When the measurement data contains the number of PDU sessions supported by each of all SMFs involved in the target network slice, the NSSMF may calculate the load distribution rate of each network slice instance from the network slice instances NSI supported by each SMF. Specifically, the behavior or operation of NSSMF at this time may refer to the description in 101, and is not described herein again to avoid repetition.

When the NSSMF determines at least one of a control plane access success rate of the target network slice, a user plane access success rate, or a load distribution rate of a network slice instance under the target network slice, it may be considered that the NSSMF determines a performance of the terminal device accessing the target network slice, and thus management of the accessible performance of resources and services of the network slice level can be achieved.

In addition, when the NSSMF receives a network slice performance measurement request from another network element, a measurement reply corresponding to the network slice performance measurement request may be sent to the other network element. Here, the measurement reply may include NSSMF determined performance of the terminal device to access the target network slice.

Fig. 8 shows a schematic diagram of a system architecture of another embodiment of the present application. When there are multiple AMFs supporting a target network slice for which performance measurements are needed, and the AMFs are managed by multiple NSSMFs, it may correspond to the system architecture shown in fig. 8. For example, AMFs supporting target network slices may be located in different geographic areas or may serve different groups of users (e.g., AMFs)₁In region 1, AMF₂Located in region 2), these AMFs may each be managed by a different NSSMF, such as an AMF₁Can be prepared from NSSMF₁To manage, AMF₂Can be prepared from NSSMF₂To manage, etc. And, all of the sub-domains of NSSMF (e.g., NSSMF)₁And NSSMF₂) The method can be connected with one NSMF or cross-domain NSSMF, and the performance measurement data of each sub-domain is sent to the NSMF or cross-domain NSSMF, and the performance of the terminal device accessing the target network slice is calculated by the NSMF or cross-domain NSSMF.

Fig. 9 is a schematic flow chart of another method for network slice performance management provided in an embodiment of the present application. The method of network slice management shown in fig. 9 may be applied to the system architecture shown in fig. 8.

901, the second network slice management function unit sends a second network slice performance measurement request to the first network slice management function unit. Correspondingly, the first network slice management functional unit receives a second network slice performance measurement request sent by the second network slice management functional unit.

Specifically, the second network slice performance measurement request is used to request measurement of the performance of the terminal device accessing the target network slice. Also, the second network slice management function may be NSMF or cross-domain NSSMF (the second network slice management function may be denoted as NSMF/NSSMF), and the first network slice management function is NSSMF. At this time, the NSSMF belongs to a network slice management function unit in a management domain of NSMF/NSSMF, and an EM (AMF-EM) for managing an AMF corresponding to the target network slice is included in the management domain of each NSSMF.

Here, the second network slice management function unit may generate a network slice performance measurement request or receive a network slice performance measurement request from another network element (e.g., a higher-level network slice management network element). Then, the second network slice management function unit transmits the network slice performance measurement request to the first network slice management function unit corresponding to the EM (AMF-EM) supporting all AMFs of the target network slice. In this embodiment of the present application, a network slice performance measurement request sent by a second network slice management functional unit to a first network slice management functional unit is referred to as a second network slice performance management request, and a network slice performance measurement request sent by a first network slice management functional unit to an AFM-EM is referred to as a first network slice performance measurement request.

It is understood that the first or second network slice performance measurement request is only for distinguishing the sending device and the receiving device of the network slice performance measurement request, and the sequence of sending the network slice request is not limited. In addition, in this embodiment of the present application, the content carried by the first network slice performance measurement request or the second network slice performance measurement request may be the same. Specifically, the content carried by the first and second network slice performance measurement requests may refer to the description in the network slice performance measurement request in fig. 7, and is not described herein again to avoid repetition.

The first network slice management function sends a first network slice performance measurement request to the EM 902. Correspondingly, the EM receives the first network slice performance measurement request sent by the first network slice management function unit.

903, the EM takes the measurement.

The EM sends 904 a first measurement reply to the first network slice management function. Correspondingly, the first network slice management functional unit receives the first measurement reply sent by the EM.

Here, a reply corresponding to the first network slice performance measurement request is referred to as a first measurement reply. Specifically, the description in fig. 7 can be referred to as 122-124, and details are not repeated here to avoid repetition.

905, each first network slice management functional unit acquires measurement data of the target network slice in its own management domain according to the first measurement reply.

Specifically, when the number of the first network slice management functional units is multiple, each first network slice management functional unit needs to acquire measurement data of the target network slice in its own management domain according to measurement data reported by each AMF-EM in its own management domain.

The first network slice management function unit sends 906 a second measurement reply to the second network slice management function units, respectively. Correspondingly, the second network slice management function unit receives the second measurement reply sent by the first network slice management function unit. Here, a reply corresponding to the second network slice performance measurement request is referred to as a second measurement reply including measurement data of the target network slice acquired by the first network slice management function unit within its own management domain.

907, the second network slice management function unit determines the performance of the internal terminal device accessing the target network slice according to the second measurement reply.

Specifically, the number of the first network slice management function units may be multiple, that is, the multiple first network slice management function units are respectively network slice management function units in multiple sub-domains of the second network slice management function unit. Therefore, the plurality of first network slice management functional units may respectively send the second measurement reply to the second network slice management functional unit, so that the second network slice management functional unit may determine the performance of the terminal device accessing the target network slice according to the plurality of second measurement replies. Specifically, the manner in which the second network slice management function unit determines the performance of the terminal device accessing the target network slice is similar to the manner in which the first network slice management function unit determines the performance of the terminal device accessing the target network slice, and for avoiding repetition, details are not repeated here.

In addition, when the second network slice management function unit receives a network slice performance measurement request from another network element (e.g., a higher-level management network element), a measurement reply corresponding to the network slice performance measurement request may be sent to the other network element. Here, the measurement reply may include accessibility performance of the target network slice for resources and services within the management domain of the second network slice management function.

The method for network slice performance management provided by the embodiment of the present application is described in detail above with reference to fig. 1 to 9, and the apparatus for network slice performance management provided by the embodiment of the present application is described in detail below with reference to fig. 10 to 15.

Fig. 10 is a schematic block diagram illustrating an apparatus 1000 for network slice performance management according to an embodiment of the present application. The apparatus 1000 may specifically be an element management unit EM that manages access and mobility management functions AMF.

A receiving unit 1010, configured to receive a network slice performance measurement request sent by a network slice management system, where the network slice performance measurement request is used to request measurement of performance of a terminal device accessing a target network slice, and the AMF supports the target network slice;

an obtaining unit 1020, configured to obtain measurement data for the network slice performance measurement request;

a sending unit 1030, configured to send a measurement reply corresponding to the network slice performance measurement request to the network slice management system, where the measurement reply includes the measurement data.

the user plane access success rate is the ratio of the user plane access success times to the user plane access attempt times, and the user plane access failure rate is the ratio of the user plane access failure times to the user plane access attempt times.

Optionally, the measurement data further includes a reason for the failure of the user plane access, where the reason for the failure of the user plane access includes at least one of: and an invalid request of the terminal equipment, and failure of data network authentication of a user request or failure of resource allocation of a wireless access network by a Session Management Function (SMF).

wherein the load distribution rate of each of the at least one network slice instance is a ratio of the number of sessions supported by each network slice instance to the total number of sessions supported by the network slice.

Optionally, the measurement data of the target network slice further includes:

It should be noted that, in the embodiment of the present invention, the receiving unit 1010 and the transmitting unit 1020 may be implemented by a transceiver. As shown in fig. 11, an apparatus 1100 for network slice performance management may include a processor 1110, a memory 1120, and a transceiver 1130. The memory 1120 may be used for storing codes and the like executed by the processor 1110, and the processor 1110 may be used for processing data or programs.

In implementation, the steps of the above method may be performed by integrated logic circuits of hardware or instructions in the form of software in the processor 1110. The steps of a method disclosed in connection with the embodiments of the present invention may be directly implemented by a hardware processor, or may be implemented by a combination of hardware and software modules in the 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 the memory 1120, and the processor 1110 reads the information in the memory 1120 and performs the steps of the method in combination with the hardware thereof. To avoid repetition, it is not described in detail here.

The apparatus 1000 for network slice performance management shown in fig. 10 or the apparatus 1100 for network slice performance management shown in fig. 11 can implement each process of the EM corresponding to the foregoing method embodiment, and specifically, the apparatus 1000 for network slice performance management or the apparatus 1100 for network slice performance management may refer to the above description, and is not repeated here to avoid repetition.

Fig. 12 is a schematic block diagram illustrating an apparatus 1200 for network slice performance management according to an embodiment of the present application. The apparatus 1200 may specifically be a first network slice management function.

A sending unit 1210, configured to send a first network slice performance measurement request to at least one network element management unit EM, where the first network slice performance measurement request is used to request measurement of performance of a terminal device accessing a target network slice, and an access and mobility management function AMF managed by each EM in the at least one EM supports the target network slice.

A receiving unit 1220, configured to receive a first measurement reply sent by each EM and corresponding to the first network slice performance measurement request, where the first measurement reply includes measurement data for the first network slice performance measurement request.

Optionally, the network slice performance measurement request includes a first performance measurement type, where the first performance measurement type includes a control plane access success rate of accessing the network slice by the terminal device and/or a parameter used for determining the control plane access success rate;

when the second performance measurement type comprises a user plane access success rate of a network slice, the measurement data comprises at least one of: the user plane access success rate, the user plane access failure rate, the user plane access trial access times, the user plane access success times and the user plane access failure times of the target network slice;

Optionally, the measurement data of the target network slice further includes:

the apparatus 1200 further comprises:

a first determining unit, configured to determine, according to the number of sessions supported by each SMF and an identifier of an SMF corresponding to each network slice instance in the at least one network slice instance, a network slice instance load distribution rate corresponding to the target network slice or a parameter used for determining the load distribution rate.

Optionally, when the number of the at least one EM is at least two, the apparatus 1200 further includes:

and a second determining unit, configured to determine, according to the measurement data obtained by each EM, performance of accessing the target network slice by the terminal device.

Optionally, before the sending unit 1210 sends the first network slice performance measurement request to the at least one network element management unit EM, the receiving unit 1220 is further configured to receive a second network slice performance measurement request sent by a second network slice management function unit, where the second network slice performance measurement request is used to request to measure the performance of a terminal device accessing the target network slice, and the apparatus 1200 belongs to a network slice management function unit in a management domain of the second network slice management function unit;

after the receiving unit 1220 receives the first measurement reply, the sending unit 1210 sends a second measurement reply corresponding to the second network slice performance measurement request to the second network slice management function unit, where the second measurement reply includes measurement data for the second network slice performance measurement request.

It should be noted that, in the embodiment of the present invention, the sending unit 1210 and the receiving unit 1220 may be implemented by a transceiver. As shown in fig. 13, an apparatus 1300 for network slice performance management may include a processor 1310, a memory 1320, and a transceiver 1330. The memory 1320 may be used for storing codes and the like executed by the processor 1310, and the processor 1310 may be used for processing data or programs.

In implementation, the steps of the above method may be performed by integrated logic circuits of hardware or instructions in the form of software in the processor 1310. The steps of a method disclosed in connection with the embodiments of the present invention may be directly implemented by a hardware processor, or may be implemented by a combination of hardware and software modules in the 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 the memory 1320, and the processor 1310 reads the information in the memory 1320, and performs the steps of the above method in combination with the hardware thereof. To avoid repetition, it is not described in detail here.

The apparatus 1200 for network slice performance management shown in fig. 12 or the apparatus 1300 for network slice performance management shown in fig. 13 can implement each process of the foregoing method embodiment corresponding to the first network slice management functional unit, and specifically, the apparatus 1200 for network slice performance management or the apparatus 1300 for network slice performance management may refer to the above description, and is not described here again to avoid repetition.

Fig. 14 is a schematic block diagram illustrating an apparatus 1400 for network slice performance management according to an embodiment of the present application. The apparatus 1400 may specifically be a second network slice management function unit, and the apparatus 1400 includes a sending unit 1410 and a receiving unit 1420.

A sending unit 1410, configured to send a second network slice performance measurement request to at least one first network slice management function unit, where the second network slice performance measurement request is used to request measurement of performance of a terminal device accessing a target network slice, the first network slice management function unit belongs to a network slice management function unit in a management domain of the apparatus 1400, and the management domain of the first network slice management function unit includes a network element management unit EM configured to manage access and mobility management functions AMF corresponding to the target network slice;

a receiving unit 1420, configured to receive a second measurement reply corresponding to the second network slice performance measurement request, sent by each first network slice management function unit, where the second measurement reply includes measurement data for the second network slice performance measurement request.

Optionally, when the number of the at least one first network slice management function unit is at least two, the apparatus 1400 further includes:

and the determining unit is used for determining the performance of the terminal equipment accessing the target network slice according to the measurement data acquired by each first network slice management functional unit.

It should be noted that, in the embodiment of the present invention, the transmitting unit 1410 and the receiving unit 1420 may be implemented by a transceiver. As shown in fig. 15, the apparatus 1500 of network slice performance management may include a processor 1510, a memory 1520, and a transceiver 1530. The memory 1520 may be used to store codes and the like executed by the processor 1510, and the processor 1510 may be used to process data or programs.

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 1510. The steps of a method disclosed in connection with the embodiments of the present invention may be directly implemented by a hardware processor, or may be implemented by a combination of hardware and software modules in the 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 the memory 1520, and the processor 1510 reads the information in the memory 1520 and performs the steps of the above method in combination with the hardware thereof. To avoid repetition, it is not described in detail here.

The apparatus 1400 for network slice performance management shown in fig. 14 or the apparatus 1500 for network slice performance management shown in fig. 15 can implement each process of the foregoing method embodiment corresponding to the second network slice management functional unit, and specifically, the apparatus 1400 for network slice performance management or the apparatus 1500 for network slice performance management may refer to the above description, and is not described here again to avoid repetition.

The embodiment of the present application further provides a computer-readable medium for storing a computer program, where the computer program includes instructions for executing the method corresponding to the first device or the second device in the above method embodiments.

An embodiment of the present application further provides a computer program product, where the computer program product includes: computer program code which, when run by a communication unit, processing unit or transceiver, processor of a communication device (e.g. a terminal device or a network device), causes the communication device to perform a method corresponding to the first device or the second device of any of the above-described method embodiments.

The embodiments in the present application may be used independently or jointly, and are not limited herein.

It should be understood that the Processor mentioned in the embodiments of the present invention may be a Central Processing Unit (CPU), other 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, a discrete hardware component, and the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

It will also be appreciated that the memory referred to in this embodiment of the invention 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 PROM (EEPROM), or a flash Memory. The volatile Memory may be a Random Access Memory (RAM) which functions as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static random access memory (Static RAM, SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic random access memory (Synchronous DRAM, SDRAM), Double Data Rate Synchronous Dynamic random access memory (DDR SDRAM), Enhanced Synchronous SDRAM (ESDRAM), Synchronous link SDRAM (SLDRAM), and Direct rambus RAM (DR RAM).

It should be noted that when the processor is a general-purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, the memory (memory module) is integrated in the processor.

It should be noted that the memory described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

It should be understood that the descriptions of the first, second, etc. appearing in the embodiments of the present application are only for illustrating and differentiating the objects, and do not represent a particular limitation to the number of devices in the embodiments of the present application, and do not constitute any limitation to the embodiments of the present application.

It should also be understood that, in the various embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

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 place, or may be distributed on a plurality of 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 conceive 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 network slice performance management, characterized in that the method is performed by an element management unit, EM, managing an access and mobility management function, AMF, the method comprising:

the EM receives a network slice performance measurement request sent by a network slice management system, wherein the network slice performance measurement request is used for requesting measurement of the performance of a terminal device accessing a target network slice, and the AMF supports the target network slice;

the EM acquires measurement data for the network slice performance measurement request;

the EM sends a measurement reply corresponding to the network slice performance measurement request to the network slice management system, the measurement reply including the measurement data, wherein

The network slice performance measurement request comprises a first performance measurement type, and the first performance measurement type comprises a control plane access success rate of terminal equipment accessing to the network slice and/or a parameter for determining the control plane access success rate; when the first performance measurement type comprises the control plane access success rate, the measurement data comprises at least one of: the control plane access success rate, the control plane access failure rate, the control plane access attempt times, the control plane access success times and the control plane access failure times of the target network slice; when the first performance measurement type includes a parameter for determining the control plane access success rate, the measurement data includes at least one of: the control plane access attempt times, the control plane access success times and the control plane access failure times of the target network slice; the control plane access success rate is the ratio of the control plane access success times to the control plane access attempt times, and the control plane access failure rate is the ratio of the control plane access failure times to the control plane access attempt times; and/or

The network slice performance measurement request comprises a second performance measurement type, and the second performance measurement type comprises a user plane access success rate of the terminal equipment accessing the network slice and/or a parameter for determining the user plane access success rate; when the second performance measurement type comprises a user plane access success rate of a network slice, the measurement data comprises at least one of: the user plane access success rate, the user plane access failure rate, the user plane access attempt access times, the user plane access success times and the user plane access failure times of the target network slice; when the second performance measurement type comprises a parameter for determining the user plane access success rate, the measurement data comprises at least one of: the access times of the user plane access attempt, the successful times of the user plane access and the failed times of the user plane access of the target network slice; the user plane access success rate is the ratio of the user plane access success times to the user plane access attempt times, and the user plane access failure rate is the ratio of the user plane access failure times to the user plane access attempt times.

2. The method of claim 1, wherein the network slice performance measurement request comprises a third performance measurement type, and wherein the third performance measurement type comprises a load distribution rate of a network slice instance corresponding to a network slice and/or a parameter for determining the load distribution rate;

3. The method of claim 2, wherein the network slice performance measurement request includes an identification of all SMFs corresponding to each of at least one network slice instance of the target network slice;

4. A method of network slice performance management, the method performed by a first network slice management function, the method comprising:

the first network slice management function unit receives a first measurement reply corresponding to the first network slice performance measurement request sent by each EM, the first measurement reply comprising measurement data for the first network slice performance measurement request, wherein

5. The method of claim 4, wherein the network slice performance measurement request comprises a third performance measurement type, and wherein the third performance measurement type comprises a load distribution rate of a network slice instance corresponding to a network slice and/or a parameter for determining the load distribution rate;

6. The method of claim 5, wherein the measurement data of the target network slice further comprises:

the method further comprises the following steps:

7. The method according to any one of claims 4-6, wherein when the number of the at least one EM is at least two, the method further comprises:

8. The method according to any of claims 4-6, wherein before said first network slice management function element sending a first network slice performance measurement request to at least one element management element, EM, further comprising:

9. A method of network slice performance management, the method performed by a second network slice management function, the method comprising:

the second network slice management function unit receiving a second measurement reply corresponding to the second network slice performance measurement request sent by each of the first network slice management function units, the second measurement reply including measurement data for the second network slice performance measurement request,

the network slice performance measurement request comprises a first performance measurement type, and the first performance measurement type comprises a control plane access success rate of terminal equipment accessing to the network slice and/or a parameter for determining the control plane access success rate; when the first performance measurement type comprises the control plane access success rate, the measurement data comprises at least one of: control plane access success rate, control plane access failure rate, control plane access attempt times, control plane access success times and control plane access failure times of the target network slice; when the first performance measurement type includes a parameter for determining the control plane access success rate, the measurement data includes at least one of: the control plane access attempt times, the control plane access success times and the control plane access failure times of the target network slice; the control plane access success rate is the ratio of the control plane access success times to the control plane access attempt times, and the control plane access failure rate is the ratio of the control plane access failure times to the control plane access attempt times; and/or

10. An apparatus for network slice performance management, characterized in that the apparatus is an element management unit, EM, managing an access and mobility management function, AMF, the apparatus comprising:

a receiving unit, configured to receive a network slice performance measurement request sent by a network slice management system, where the network slice performance measurement request is used to request measurement of performance of a terminal device accessing a target network slice, and the AMF supports the target network slice;

an obtaining unit, configured to obtain measurement data for the network slice performance measurement request;

a sending unit for sending a measurement reply corresponding to the network slice performance measurement request to the network slice management system, the measurement reply including the measurement data, wherein

11. The apparatus of claim 10, wherein the network slice performance measurement request comprises a third performance measurement type, and wherein the third performance measurement type comprises a load distribution rate of a network slice instance corresponding to a network slice and/or a parameter for determining the load distribution rate;

12. The apparatus of claim 11, wherein the network slice performance measurement request includes an identification of all SMFs corresponding to each of at least one network slice instance of the target network slice;

13. An apparatus for network slice performance management, the apparatus being a first network slice management function, the apparatus comprising:

a sending unit, configured to send a first network slice performance measurement request to at least one network element management unit EM, where the first network slice performance measurement request is used to request measurement of performance of a terminal device accessing a target network slice, and an access and mobility management function AMF managed by each EM in the at least one EM supports the target network slice;

a receiving unit, configured to receive a first measurement reply corresponding to the first network slice performance measurement request sent by each EM, the first measurement reply including measurement data for the first network slice performance measurement request, wherein

14. The apparatus of claim 13, wherein the network slice performance measurement request comprises a third performance measurement type, and wherein the third performance measurement type comprises a load distribution rate of a network slice instance corresponding to a network slice and/or a parameter for determining the load distribution rate;

15. The apparatus of claim 14, wherein the measurement data for the target network slice further comprises:

the device further comprises:

16. The apparatus according to any of claims 13-15, wherein when the number of the at least one EM is at least two, the apparatus further comprises:

17. The apparatus according to any of claims 13-15, wherein said sending unit, before sending the first network slice performance measurement request to the at least one network element management unit EM, further comprises:

the receiving unit is further configured to receive a second network slice performance measurement request sent by a second network slice management functional unit, where the second network slice performance measurement request is used to request measurement of performance of a terminal device accessing the target network slice, and the first network slice management functional unit belongs to a network slice management functional unit in a management domain of the second network slice management functional unit;

after receiving the first measurement reply, the receiving unit further includes:

the transmission unit transmits a second measurement reply corresponding to the second network slice performance measurement request to the second network slice management function, the second measurement reply including measurement data for the second network slice performance measurement request.

18. An apparatus for network slice performance management, the apparatus being a second network slice management function, the apparatus comprising:

a sending unit, configured to send a second network slice performance measurement request to at least one first network slice management function unit, where the second network slice performance measurement request is used to request measurement of performance of a terminal device accessing a target network slice, the first network slice management function unit belongs to a network slice management function unit in a management domain of the second network slice management function unit, and the management domain of the first network slice management function unit includes a network element management unit EM configured to manage access and a mobility management function AMF corresponding to the target network slice;

a receiving unit, configured to receive a second measurement reply corresponding to the second network slice performance measurement request sent by each of the first network slice management function units, the second measurement reply including measurement data for the second network slice performance measurement request, wherein