Identifying the router causing the silent failure

Abstract

The present invention provides a router estimation system and router estimation method that are capable of accurately estimating a router causing a silent failure in network slices. A policy manager unit (90) uses, when it is determined that performance of functional components in slice communication has degraded, router group data to identify a group of routers present on a path of the slice communication for each of the plurality of functional components. The policy manager unit (90) estimates at least one router, which is included in every group of routers identified for each of the plurality of functional components determined to have degraded performance, as a router causing degradation in performance of the functional components.

Description

[Technical Field]

[0001] The present disclosure relates to estimating routers responsible for silent failures. [Background technology]

[0002] Patent Document 1 describes deploying multiple network functions (NFs) included in a network service (NS) to a server on which a container-type application execution environment is installed. Patent Document 1 also describes building a network slice and monitoring the NFs. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] International Publication No. 2021 / 171210 Summary of the Invention [Problem to be solved by the invention]

[0004] In a communication system such as that described in Patent Document 1, a separate group of routers is generally configured as a component for each network slice. Also, a common router may be configured as a component in multiple network slices.

[0005] Here, even if no abnormality is detected in a router, which is a component common to multiple network slices included in a communication system, multiple functional elements (NSs, NFs, etc.) may experience a degradation in the performance of the functional element in communication using the network slices available to that functional element (so-called silent failures), but it has been difficult to determine the cause of such silent failures.

[0006] The present disclosure has been made in consideration of the above-mentioned situation, and one of its objectives is to provide a router estimation system and a router estimation method that can accurately estimate the router that is the cause of a silent failure in a network slice. [Means for solving the problem]

[0007] The router estimation system according to the present disclosure includes one or more processors, and at least one of the one or more processors executes a router group data storage process, a determination process, a router group identification process, and a router estimation process. In the router group data storage process, router group data indicating the router groups constituting each of a plurality of network slices constructed in a communication system is stored. In the determination process, for each of a plurality of functional elements included in the communication system, for each network slice in which the functional element is available, it is determined whether the performance of the functional element in slice communication using the network slice has deteriorated. In the router group identification process, when it is determined that the performance of a plurality of functional elements in slice communication has deteriorated, a router group present on a path of the slice communication for each of the plurality of functional elements is identified based on the router group data. In the router estimation process, at least one router included in any of the router groups identified for each of the plurality of functional elements determined to have deteriorated performance is estimated as the router causing the deterioration of the performance of the functional element.

[0008] In addition, in a router estimation method according to the present disclosure, for each of a plurality of network slices constructed in a communication system, router group data indicating a group of routers constituting the network slice is stored. Furthermore, for each of a plurality of functional elements included in the communication system, for each network slice in which the functional element is available, it is determined whether the performance of the functional element in slice communication using the network slice has deteriorated. Furthermore, when it is determined that the performance of the functional element in slice communication has deteriorated for each of the plurality of functional elements, a group of routers present on the path of the slice communication for each of the plurality of functional elements is identified based on the router group data. Furthermore, at least one router included in any of the router groups identified for each of the plurality of functional elements determined to have deteriorated performance is estimated as the router causing the deterioration of the performance of the functional element. [Brief explanation of the drawings]

[0009] [Figure 1] 1 is a diagram illustrating an example of a communication system according to an embodiment of the present invention. [Figure 2] 1 is a diagram illustrating an example of a communication system according to an embodiment of the present invention. [Figure 3] FIG. 1 is a diagram illustrating an example of a network service according to an embodiment of the present invention. [Figure 4] FIG. 1 is a diagram illustrating an example of associations between elements established in a communication system according to an embodiment of the present invention. [Figure 5] FIG. 2 is a functional block diagram showing an example of functions implemented in a platform system according to an embodiment of the present invention. [Figure 6] FIG. 2 illustrates an example of a data structure of physical inventory data. [Figure 7] A diagram schematically showing an example of the configuration of a group of functional elements that communicate using a network slice. [Figure 8] FIG. 10 is a diagram illustrating an example of segment routing path management data. [Figure 9] FIG. 10 is a diagram illustrating an example of router group management data. [Figure 10] FIG. 2 is a flowchart showing an example of a flow of processing performed in a platform system according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0010] Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings.

[0011] 1 and 2 are diagrams illustrating an example of a communication system 1 according to an embodiment of the present invention. Fig. 1 is a diagram focusing on the locations of a group of data centers included in the communication system 1. Fig. 2 is a diagram focusing on various computer systems implemented in the group of data centers included in the communication system 1.

[0012] As shown in FIG. 1, the data centers included in the communication system 1 are classified into a central data center 10, regional data centers 12, and edge data centers .

[0013] For example, several central data centers 10 are distributed and placed within the area covered by the communication system 1 (for example, within Japan).

[0014] For example, several tens of regional data centers 12 are distributed and placed within the area covered by the communication system 1. For example, if the area covered by the communication system 1 is the entire country of Japan, one or two regional data centers 12 may be placed in each prefecture.

[0015] For example, several thousand edge data centers 14 are distributed within the area covered by the communication system 1. Each edge data center 14 is capable of communicating with communication equipment 18 equipped with an antenna 16. As shown in FIG. 1, one edge data center 14 may be capable of communicating with several communication equipment 18. The communication equipment 18 may include a computer such as a server computer. The communication equipment 18 according to this embodiment performs wireless communication with a UE (User Equipment) 20 via the antenna 16. The communication equipment 18 equipped with the antenna 16 is provided with, for example, a radio unit (RU) (described later).

[0016] In the central data center 10, the regional data center 12, and the edge data center 14 according to this embodiment, multiple servers are arranged.

[0017] In this embodiment, for example, the central data center 10, the regional data centers 12, and the edge data centers 14 are capable of communicating with each other. Furthermore, the central data centers 10, the regional data centers 12, and the edge data centers 14 are also capable of communicating with each other.

[0018] 2, the communication system 1 according to this embodiment includes a platform system 30, multiple radio access networks (RANs) 32, multiple core network systems 34, and multiple UEs 20. The core network systems 34, the RANs 32, and the UEs 20 cooperate with each other to realize a mobile communication network.

[0019] The RAN 32 is a computer system equipped with an antenna 16, and corresponds to an eNodeB (eNB) in a fourth-generation mobile communication system (hereinafter referred to as 4G) or a gNB (NR base station) in a fifth-generation mobile communication system (hereinafter referred to as 5G). The RAN 32 according to this embodiment is mainly implemented by a group of servers and communication equipment 18 arranged in an edge data center 14. Note that part of the RAN 32 (for example, a distributed unit (DU), a central unit (CU), a virtual distributed unit (vDU), and a virtual central unit (vCU)) may be implemented in the central data center 10, a regional data center 12, or the communication equipment 18, instead of the edge data center 14.

[0020] The core network system 34 is a system equivalent to an EPC (Evolved Packet Core) in 4G or a 5G Core (5GC) in 5G. The core network system 34 according to this embodiment is implemented mainly by a group of servers arranged in the central data center 10 and the regional data centers 12.

[0021] The platform system 30 according to this embodiment is configured on, for example, a cloud platform, and includes a processor 30a, a storage unit 30b, and a communication unit 30c, as shown in FIG. 2. The processor 30a is a program-controlled device such as a microprocessor that operates according to a program installed in the platform system 30. The storage unit 30b is, for example, a storage element such as a ROM or RAM, a solid-state drive (SSD), or a hard disk drive (HDD). The storage unit 30b stores programs executed by the processor 30a. The communication unit 30c is, for example, a communication interface such as a network interface controller (NIC) or a wireless local area network (LAN) module. Note that software-defined networking (SDN) may be implemented in the communication unit 30c. The communication unit 30c exchanges data with the RAN 32 and the core network system 34.

[0022] In this embodiment, the platform system 30 is implemented by a group of servers located in the central data center 10. Note that the platform system 30 may also be implemented by a group of servers located in the regional data centers 12.

[0023] In this embodiment, for example, in response to a purchase request for a network service (NS) from a purchaser, the requested network service is established in the RAN 32 and the core network system 34. Then, the established network service is provided to the purchaser.

[0024] For example, a purchaser such as an MVNO (Mobile Virtual Network Operator) is provided with network services such as voice communication services and data communication services. The voice communication services and data communication services provided by this embodiment are ultimately provided to customers (end users) of the purchaser (MVNO in the above example) who use the UE 20 shown in FIGS. 1 and 2. The end users can perform voice communication and data communication with other users via the RAN 32 and the core network system 34. The UE 20 of the end user can also access a data network such as the Internet via the RAN 32 and the core network system 34.

[0025] In addition, in this embodiment, an IoT (Internet of Things) service may be provided to an end user who uses a robot arm, a connected car, etc. In this case, for example, the end user who uses the robot arm, the connected car, etc. may become a purchaser of the network service according to this embodiment.

[0026] In this embodiment, a container-based virtualized application execution environment such as Docker (registered trademark) is installed on servers located in the central data center 10, the regional data centers 12, and the edge data center 14, allowing containers to be deployed and run on these servers. A cluster consisting of one or more containers generated by such virtualization technology may be built on these servers. For example, a Kubernetes cluster managed by a container management tool such as Kubernetes (registered trademark) may be built. Then, a processor on the built cluster may execute a container-based application.

[0027] In this embodiment, the network service provided to the purchaser is composed of one or more functional units (for example, network functions (NFs)). In this embodiment, the functional units are implemented as NFs realized by virtualization technology. NFs realized by virtualization technology are called VNFs (Virtualized Network Functions). It does not matter what virtualization technology is used to virtualize them. For example, in this description, a CNF (Containerized Network Function) realized by container-type virtualization technology is also included in the VNF. In this embodiment, the network service will be described as being implemented by one or more CNFs. Furthermore, the functional units in this embodiment may correspond to network nodes.

[0028] Fig. 3 is a diagram illustrating an example of an operating network service. The network service illustrated in Fig. 3 includes, as software elements, NFs such as a plurality of RUs 40, a plurality of DUs 42, a plurality of CUs 44 (CU-CP (Central Unit - Control Plane) 44a and CU-UP (Central Unit - User Plane) 44b), a plurality of AMFs (Access and Mobility Management Functions) 46, a plurality of SMFs (Session Management Functions) 48, and a plurality of UPFs (User Plane Functions) 50.

[0029] In the example of Figure 3, RU 40, DU 42, CU-CP 44a, AMF 46, and SMF 48 correspond to elements of the control plane (C-Plane), and RU 40, DU 42, CU-UP 44b, and UPF 50 correspond to elements of the user plane (U-Plane).

[0030] The network service may include other types of NFs as software elements. The network service is implemented on computer resources (hardware elements) such as multiple servers.

[0031] In this embodiment, for example, a communication service in a certain area is provided by the network service shown in FIG.

[0032] In this embodiment, it is assumed that multiple RUs 40, multiple DUs 42, multiple CU-UPs 44b, and multiple UPFs 50 shown in FIG. 3 belong to one end-to-end network slice.

[0033] Fig. 4 is a diagram schematically illustrating an example of associations between elements established in the communication system 1 in this embodiment. The symbols M and N shown in Fig. 4 represent any integers equal to or greater than 1, and indicate the relationship between the numbers of elements connected by a link. When both ends of a link are a combination of M and N, the elements connected by the link have a many-to-many relationship, and when both ends of a link are a combination of 1 and N or a combination of 1 and M, the elements connected by the link have a one-to-many relationship.

[0034] As shown in Figure 4, network services (NS), network functions (NF), CNFCs (Containerized Network Function Components), pods, and containers are configured in a hierarchical structure.

[0035] An NS corresponds to, for example, a network service configured from multiple NFs. Here, an NS may correspond to an element of granularity such as a 5G RAN (gNB), a 4G RAN (eNB), or the like.

[0036] In 5G, NFs correspond to elements with granularity such as RU, DU, CU-CP, CU-UP, AMF, SMF, and UPF. In 4G, NFs correspond to elements with granularity such as MME (Mobility Management Entity), HSS (Home Subscriber Server), S-GW (Serving Gateway), vDU, and vCU. In this embodiment, for example, one NS includes one or more NFs. In other words, one or more NFs are subordinate to one NS.

[0037] A CNFC corresponds to an element of granularity such as DU mgmt or DU Processing. A CNFC may be a microservice deployed on a server as one or more containers. For example, a CNFC may be a microservice that provides some of the functions of DU, CU-CP, CU-UP, etc. Also, a CNFC may be a microservice that provides some of the functions of UPF, AMF, SMF, etc. In this embodiment, for example, one NF includes one or more CNFCs. In other words, one or more CNFCs are subordinate to one NF.

[0038] A pod refers to the smallest unit for managing a Docker container in Kubernetes, for example. In this embodiment, for example, one CNFC includes one or more pods. In other words, one or more pods are under the control of one CNFC.

[0039] In this embodiment, for example, one pod includes one or more containers. That is, one or more containers are subordinate to one pod.

[0040] Also, as shown in Figure 4, network slices (NSIs) and network slice subnet instances (NSSIs) have a hierarchical structure.

[0041] The NSI can also be considered an end-to-end virtual circuit spanning multiple domains (e.g., from the RAN 32 to the core network system 34). The NSI may be a slice for high-speed, high-capacity communication (e.g., for enhanced Mobile Broadband (eMBB)), a slice for high-reliability and low-latency communication (e.g., for Ultra-Reliable and Low Latency Communications (URLLC)), or a slice for connecting a large number of terminals (e.g., for massive Machine Type Communication (mMTC)). The NSSI can also be considered a virtual circuit of a single domain obtained by dividing the NSI. The NSSI may be a slice of the RAN domain, a slice of a transport domain such as the Mobile Back Haul (MBH) domain, or a slice of the core network domain.

[0042] In this embodiment, for example, one NSI includes one or more NSSIs. That is, one or more NSSIs are subordinate to one NSI. Note that in this embodiment, multiple NSIs may share the same NSSI.

[0043] Furthermore, as shown in FIG. 4, NSSI and NS generally have a many-to-many relationship.

[0044] Furthermore, in this embodiment, for example, one NF can belong to one or more network slices. Specifically, for example, one NF can be configured with NSSAI (Network Slice Selection Assistance Information) including one or more S-NSSAI (Sub Network Slice Selection Assist Information). Here, S-NSSAI is information associated with a network slice. Note that an NF does not necessarily have to belong to a network slice.

[0045] Fig. 5 is a functional block diagram showing an example of functions implemented in the platform system 30 according to this embodiment. Note that the platform system 30 according to this embodiment does not need to implement all of the functions shown in Fig. 5, and functions other than the functions shown in Fig. 5 may also be implemented.

[0046] As shown in FIG. 5 , the platform system 30 according to this embodiment functionally includes, for example, an operations support system (OSS) unit 60, an orchestration (E2EO: End-to-End-Orchestration) unit 62, a service catalog storage unit 64, a big data platform unit 66, a data bus unit 68, an AI (Artificial Intelligence) unit 70, a monitoring function unit 72, an SDN controller 74, a configuration management unit 76, a container management unit 78, and a repository unit 80. The OSS unit 60 includes an inventory database 82, a ticket management unit 84, a fault management unit 86, and a performance management unit 88. The E2EO unit 62 includes a policy manager unit 90, a slice manager unit 92, and a lifecycle management unit 94. These elements are implemented primarily using a processor 30 a, a storage unit 30 b, and a communication unit 30 c.

[0047] The functions shown in Fig. 5 may be implemented by having a processor 30a execute a program that is installed in a platform system 30, which is one or more computers, and that includes instructions corresponding to the functions. This program may be supplied to the platform system 30 via a computer-readable information storage medium, such as an optical disk, a magnetic disk, a magnetic tape, a magneto-optical disk, or a flash memory, or via the Internet. The functions shown in Fig. 5 may also be implemented using circuit blocks, memory, or other LSIs. Those skilled in the art will understand that the functions shown in Fig. 5 can be realized in various forms, such as hardware alone, software alone, or a combination thereof.

[0048] The container management unit 78 manages the lifecycle of a container, which includes, for example, processes related to the construction of a container, such as the deployment and configuration of the container.

[0049] Here, the platform system 30 according to this embodiment may include a plurality of container management units 78. A container management tool such as Kubernetes and a package manager such as Helm may be installed in each of the plurality of container management units 78. Each of the plurality of container management units 78 may execute container construction, such as container deployment, for a server group (e.g., a Kubernetes cluster) associated with the corresponding container management unit 78.

[0050] It should be noted that the container management unit 78 does not need to be included in the platform system 30. The container management unit 78 may be provided, for example, in a server managed by the container management unit 78 (i.e., the RAN 32 or the core network system 34), or may be provided in another server that is annexed to the server managed by the container management unit 78.

[0051] In this embodiment, the repository unit 80 stores, for example, container images of containers included in a group of functional units (for example, a group of NFs) that realize a network service.

[0052] The inventory database 82 is a database that stores inventory information, which includes, for example, information about servers that are installed in the RAN 32 and the core network system 34 and that are managed by the platform system 30.

[0053] In this embodiment, inventory data is stored in the inventory database 82. The inventory data indicates the configuration of the elements included in the communication system 1 and the current status of the associations between the elements. The inventory data also indicates the status of resources managed by the platform system 30 (for example, the usage status of the resources). The inventory data may be physical inventory data or logical inventory data. The physical inventory data and logical inventory data will be described later.

[0054] Fig. 6 is a diagram showing an example of the data structure of physical inventory data. The physical inventory data shown in Fig. 6 is associated with one server. The physical inventory data shown in Fig. 6 includes, for example, a server ID, location data, building data, floor data, rack data, specification data, network data, an operating container ID list, a cluster ID, and the like.

[0055] The server ID included in the physical inventory data is, for example, an identifier of the server associated with the physical inventory data.

[0056] The location data included in the physical inventory data is, for example, data indicating the location (for example, the address of the location) of the server associated with the physical inventory data.

[0057] The building data included in the physical inventory data is, for example, data indicating the building (for example, the building name) in which the server associated with the physical inventory data is located.

[0058] The floor number data included in the physical inventory data is, for example, data indicating the floor number on which the server associated with the physical inventory data is located.

[0059] The rack data included in the physical inventory data is, for example, an identifier of the rack in which the server associated with the physical inventory data is located.

[0060] The specification data included in the physical inventory data is, for example, data indicating the specifications of the server associated with the physical inventory data, and the specification data indicates, for example, the number of cores, memory capacity, hard disk capacity, etc.

[0061] The network data included in the physical inventory data is, for example, data indicating information about the network of the server associated with the physical inventory data, and the network data indicates, for example, the NICs that the server has, the number of ports that the NICs have, the port IDs of the ports, etc.

[0062] The operating container ID list included in the physical inventory data is, for example, data that indicates information about one or more containers operating on a server associated with the physical inventory data, and the operating container ID list indicates, for example, a list of identifiers (container IDs) of instances of the containers.

[0063] The cluster ID included in the physical inventory data is, for example, an identifier of a cluster (for example, a Kubernetes cluster) to which a server associated with the physical inventory data belongs.

[0064] The logical inventory data includes topology data indicating the current state of associations between multiple elements included in the communication system 1, such as those shown in Fig. 4. For example, the logical inventory data includes topology data including an identifier of a certain NS and identifiers of one or more NFs under the NS. Also, for example, the logical inventory data includes topology data including an identifier of a certain network slice and identifiers of one or more NFs belonging to the network slice.

[0065] The inventory data may also include data indicating the current status of the geographical relationships and topological relationships between the elements included in the communication system 1. As described above, the inventory data includes location data indicating the locations where the elements included in the communication system 1 are operating, i.e., the current locations of the elements included in the communication system 1. From this, it can be said that the inventory data indicates the current status of the geographical relationships between the elements (for example, the geographical proximity between the elements).

[0066] The logical inventory data may also include NSI data indicating information about the network slice. The NSI data indicates attributes such as an identifier of an instance of the network slice and a type of the network slice. The logical inventory data may also include NSSI data indicating information about the network slice subnet. The NSSI data indicates attributes such as an identifier of an instance of the network slice subnet and a type of the network slice subnet.

[0067] The logical inventory data may also include NS data indicating information about an NS. The NS data indicates attributes such as an NS instance identifier and an NS type. The logical inventory data may also include NF data indicating information about an NF. The NF data indicates attributes such as an NF instance identifier and an NF type. The logical inventory data may also include CNFC data indicating information about a CNFC. The CNFC data indicates attributes such as an instance identifier and a CNFC type. The logical inventory data may also include pod data indicating information about a pod included in the CNFC. The pod data indicates attributes such as a pod instance identifier and a pod type. The logical inventory data may also include container data indicating information about a container included in the pod. The container data indicates attributes such as a container ID of a container instance and a container type.

[0068] The container ID of the container data included in the logical inventory data and the container ID included in the operating container ID list included in the physical inventory data associate a container instance with the server on which the container instance is running.

[0069] Furthermore, the logical inventory data may include data indicating various attributes such as a host name and an IP address. For example, container data may include data indicating an IP address of a container corresponding to the container data. For example, NF data may include data indicating an IP address and a host name of the NF indicated by the NF data.

[0070] The logical inventory data may also include data indicating an NSSAI, including one or more S-NSSAIs, configured in each NF.

[0071] Furthermore, the inventory database 82 is able to grasp the resource status as needed in cooperation with the container management unit 78. The inventory database 82 then updates the inventory data stored therein as needed based on the latest resource status.

[0072] In addition, in response to actions being performed, such as constructing a new element included in the communication system 1, changing the configuration of an element included in the communication system 1, scaling an element included in the communication system 1, or replacing an element included in the communication system 1, the inventory database 82 updates the inventory data stored in the inventory database 82.

[0073] The service catalog storage unit 64 stores service catalog data. The service catalog data may include, for example, service template data indicating logic used by the life cycle management unit 94. This service template data includes information necessary for building a network service. For example, the service template data includes information defining NSs, NFs, and CNFCs, and information indicating the correspondence between NSs, NFs, and CNFCs. Furthermore, for example, the service template data includes a workflow script for building a network service.

[0074] An example of service template data is an NSD (NS Descriptor). The NSD is associated with a network service and indicates the types of multiple functional units (e.g., multiple CNFs) included in the network service. The NSD may also indicate the number of each type of functional unit, such as CNF, included in the network service. The NSD may also indicate the file names of CNFDs (described later) related to the CNFs included in the network service.

[0075] An example of service template data is a CNF Descriptor (CNFD). The CNFD may indicate the computer resources (e.g., CPU, memory, hard disk, etc.) required by the CNF. For example, the CNFD may indicate the computer resources (CPU, memory, hard disk, etc.) required by each of multiple containers included in the CNF.

[0076] The service catalog data may also include information about thresholds (for example, anomaly detection thresholds) that are used by the policy manager 90 to compare with the calculated performance index values. The performance index values ​​will be described later.

[0077] The service catalog data may also include, for example, slice template data, which includes information necessary to perform instantiation of a network slice, including, for example, logic utilized by the slice manager unit 92.

[0078] The slice template data includes information on the "Generic Network Slice Template" defined by the GSMA (GSM Association) ("GSM" is a registered trademark). Specifically, the slice template data includes network slice template data (NST), network slice subnet template data (NSST), and network service template data. The slice template data also includes information indicating the hierarchical structure of these elements, as shown in FIG. 4.

[0079] In this embodiment, for example, the life cycle management unit 94 constructs a new network service in response to a purchase request for an NS from a purchaser.

[0080] For example, in response to a purchase request, the lifecycle management unit 94 may execute a workflow script associated with the network service to be purchased. By executing this workflow script, the lifecycle management unit 94 may instruct the container management unit 78 to deploy a container included in the new network service to be purchased. The container management unit 78 may then obtain a container image of the container from the repository unit 80 and deploy the container corresponding to the container image to a server.

[0081] In addition, in this embodiment, the life cycle management unit 94 executes, for example, scaling and replacement of elements included in the communication system 1. Here, the life cycle management unit 94 may output a container deployment instruction or deletion instruction to the container management unit 78. Then, the container management unit 78 may execute processing such as container deployment or container deletion in accordance with the instruction. In this embodiment, the life cycle management unit 94 is capable of executing scaling and replacement that cannot be handled by a tool such as Kubernetes in the container management unit 78.

[0082] Furthermore, the life cycle management unit 94 may output an instruction to create a communication path to the SDN controller 74. For example, the life cycle management unit 94 presents two IP addresses at both ends of the communication path to be created to the SDN controller 74, and the SDN controller 74 creates a communication path connecting these two IP addresses. The created communication path may be managed in association with these two IP addresses.

[0083] Furthermore, the life cycle management unit 94 may output to the SDN controller 74 an instruction to create a communication path between the two IP addresses that is associated with the two IP addresses.

[0084] In this embodiment, for example, the slice manager unit 92 performs instantiation of a network slice. In this embodiment, for example, the slice manager unit 92 performs instantiation of a network slice by executing logic indicated by a slice template stored in the service catalog storage unit 64.

[0085] The slice manager unit 92 is configured to include the functions of the NSMF (Network Slice Management Function) and the NSSMF (Network Slice Sub-network Management Function), for example, as described in the specification "TS28 533" of the 3GPP (registered trademark) (Third Generation Partnership Project). The NSMF is a function that generates and manages network slices and provides management services for NSIs. The NSSMF is a function that generates and manages network slice subnets that constitute part of the network slice and provides management services for NSSIs.

[0086] Here, the slice manager unit 92 may output a configuration management instruction related to instantiation of the network slice to the configuration management unit 76. Then, the configuration management unit 76 may perform configuration management such as setting in accordance with the configuration management instruction.

[0087] Furthermore, the slice manager unit 92 may present two IP addresses to the SDN controller 74 and output an instruction to create a communication path between these two IP addresses.

[0088] In this embodiment, the configuration management unit 76 executes configuration management such as setting of element groups such as NFs in accordance with configuration management instructions received from the life cycle management unit 94 and the slice manager unit 92, for example.

[0089] In this embodiment, the SDN controller 74 creates a communication path between two IP addresses associated with a communication path creation instruction received from, for example, the life cycle management unit 94 or the slice manager unit 92. The SDN controller 74 may create a communication path between two IP addresses using a known path calculation method such as Flex Algo.

[0090] For example, the SDN controller 74 may use a segment routing technology (e.g., SRv6 (segment routing IPv6)) to construct NSIs and NSSIs for aggregation routers, servers, and the like present along the communication paths. The SDN controller 74 may also generate NSIs and NSSIs across multiple target NFs by issuing commands to multiple target NFs to set up a common Virtual Local Area Network (VLAN) and commands to assign the bandwidth and priority indicated in the setting information to the VLAN.

[0091] In addition, the SDN controller 74 may perform operations such as changing the maximum bandwidth available for communication between two IP addresses without constructing a network slice.

[0092] The platform system 30 according to this embodiment may include multiple SDN controllers 74. Each of the multiple SDN controllers 74 may execute processing such as creating a communication path for a group of network devices such as an aggregation router associated with the SDN controller 74.

[0093] Furthermore, in this embodiment, the SDN controller 74 may appropriately change the created communication path. For example, the SDN controller 74 may detect the occurrence of a failure in a network device associated with the SDN controller 74, and in response to the detection, change the communication path that passes through the network device created by the SDN controller 74 to a communication path that does not pass through the network device.

[0094] Furthermore, the life cycle management unit 94 or the slice manager unit 92 may output a communication path change instruction to the SDN controller 74. Then, the SDN controller 74 may change the communication path created by the SDN controller 74 in accordance with the change instruction.

[0095] For example, the life cycle management unit 94 or the slice manager unit 92 may output an instruction to change a communication path associated with an identifier of a network device to be excluded from the communication path to the SDN controller 74. Then, in response to receiving the change instruction, the SDN controller 74 may change the communication path created by the SDN controller 74 to a communication path that excludes the network device identified by the identifier associated with the change instruction (i.e., a communication path that does not pass through the network device identified by the identifier associated with the change instruction).

[0096] In this embodiment, for example, the monitoring function unit 72 monitors the group of elements included in the communication system 1 in accordance with a given management policy. Here, the monitoring function unit 72 may monitor the group of elements in accordance with a monitoring policy specified by a purchaser when purchasing a network service, for example.

[0097] In this embodiment, the monitoring function unit 72 performs monitoring at various levels, such as the slice level, the NS level, the NF level, the CNFC level, and the hardware level of a server or the like.

[0098] For example, the monitoring function unit 72 may set a module that outputs metric data in hardware such as a server or in a software element included in the communication system 1 so that monitoring can be performed at the various levels described above. Here, for example, an NF may output metric data indicating metrics that are measurable (identifiable) in the NF to the monitoring function unit 72. Also, a server may output metric data indicating metrics related to hardware that is measurable (identifiable) in the server to the monitoring function unit 72.

[0099] Furthermore, for example, the monitoring function unit 72 may deploy a sidecar container on the server that aggregates metric data indicating metrics output from multiple containers for each CNFC (microservice). This sidecar container may include an agent called an exporter. The monitoring function unit 72 may repeatedly execute, at a given monitoring interval, a process of acquiring metric data aggregated for each microservice from the sidecar container, using the mechanisms of a monitoring tool such as Prometheus that can monitor container management tools such as Kubernetes.

[0100] The monitoring function unit 72 may monitor performance indicator values ​​for performance indicators described in, for example, “TS 28.552, Management and orchestration; 5G performance measurements” or “TS 28.554, Management and orchestration; 5G end to end Key Performance Indicators (KPI).” Then, the monitoring function unit 72 may obtain metric data indicating the monitored performance indicator values.

[0101] In this embodiment, the monitoring function unit 72 performs a process (enrichment) to aggregate metric data, for example, in a predetermined aggregation unit, thereby generating performance index value data indicating the performance index values ​​of the elements included in the communication system 1 in that aggregation unit.

[0102] For example, for one gNB, performance index value data for the gNB is generated by aggregating metric data indicating the metrics of elements (e.g., network nodes such as DU42 and CU44) under the control of the gNB. In this way, performance index value data indicating communication performance in the area covered by the gNB is generated. Here, for example, performance index value data indicating multiple types of communication performance such as traffic volume (throughput) and latency may be generated for each gNB. Furthermore, performance index value data indicating the communication performance of a certain element (e.g., DU42) for a predetermined period may be generated by aggregating metric data indicating the metrics of the element for the predetermined period. Note that the communication performance indicated by the performance index value data is not limited to traffic volume and latency.

[0103] Then, the monitoring function unit 72 outputs the performance index value data generated by the above-mentioned enrichment to the data bus unit 68.

[0104] In this embodiment, for example, the data bus unit 68 receives performance index value data output from the monitoring function unit 72. Then, based on the received one or more pieces of performance index value data, the data bus unit 68 generates a performance index value file including the one or more pieces of performance index value data. Then, the data bus unit 68 outputs the generated performance index value file to the big data platform unit 66.

[0105] In addition, elements such as network slices, NSs, NFs, CNFCs, and hardware such as servers included in the communication system 1 notify the monitoring function unit 72 of various alerts (for example, notification of an alert triggered by the occurrence of a failure).

[0106] Then, for example, when the monitoring function unit 72 receives the above-mentioned alert notification, it outputs alert message data indicating the notification to the data bus unit 68. Then, the data bus unit 68 generates an alert file in which alert message data indicating one or more notifications are compiled into a single file, and outputs the alert file to the big data platform unit 66.

[0107] In this embodiment, the big data platform unit 66 accumulates, for example, performance index value files and alert files output from the data bus unit 68.

[0108] In this embodiment, for example, a plurality of trained machine learning models are stored in advance in the AI ​​unit 70. The AI ​​unit 70 uses the various machine learning models stored in the AI ​​unit 70 to perform estimation processing such as future prediction processing of the usage status and service quality of the communication system 1. The AI ​​unit 70 may generate estimation result data indicating the results of the estimation processing.

[0109] The AI ​​unit 70 may perform estimation processing based on the files stored in the big data platform unit 66 and the above-mentioned machine learning model. This estimation processing is suitable for infrequently predicting long-term trends.

[0110] The AI ​​unit 70 is also capable of acquiring performance index value data stored in the data bus unit 68. The AI ​​unit 70 may perform estimation processing based on the performance index value data stored in the data bus unit 68 and the above-described machine learning model. This estimation processing is suitable for performing short-term predictions frequently.

[0111] In this embodiment, for example, the performance management unit 88 calculates a performance index value (e.g., KPI) based on a plurality of metric data and the metrics indicated by the metric data. The performance management unit 88 may also calculate a performance index value that is an overall evaluation of a plurality of types of metrics (e.g., a performance index value related to an end-to-end network slice) that cannot be calculated from a single metric data. The performance management unit 88 may also generate overall performance index value data that indicates the performance index value that is the overall evaluation.

[0112] The performance management unit 88 may acquire the above-mentioned performance index value file from the big data platform unit 66. The performance management unit 88 may also acquire estimation result data from the AI ​​unit 70. Then, performance index values ​​such as KPIs may be calculated based on at least one of the performance index value file and the estimation result data. The performance management unit 88 may also directly acquire metric data from the monitoring function unit 72. Then, performance index values ​​such as KPIs may be calculated based on the metric data.

[0113] In this embodiment, the fault management unit 86 detects the occurrence of a fault in the communication system 1 based on, for example, at least one of the above-mentioned metric data, the above-mentioned alert notification, the above-mentioned estimation result data, and the above-mentioned overall performance index value data. The fault management unit 86 may detect the occurrence of a fault that cannot be detected from a single piece of metric data or a single alert notification, for example, based on a predetermined logic. The fault management unit 86 may generate detected fault data that indicates the detected fault.

[0114] The fault management unit 86 may obtain metric data and alert notifications directly from the monitoring function unit 72. The fault management unit 86 may also obtain performance index value files and alert files from the big data platform unit 66. The fault management unit 86 may also obtain alert message data from the data bus unit 68.

[0115] In this embodiment, the policy manager unit 90 executes a predetermined judgment process based on, for example, at least one of the above-mentioned metric data, the above-mentioned performance index value data, the above-mentioned alert message data, the above-mentioned performance index value file, the above-mentioned alert file, the above-mentioned estimation result data, the above-mentioned overall performance index value data, and the above-mentioned detected fault data.

[0116] The policy manager unit 90 may then execute an action according to the result of the determination process. For example, the policy manager unit 90 may output an instruction to construct a network slice to the slice manager unit 92. Also, for example, the policy manager unit 90 may output an instruction to switch a communication path to the slice manager unit 92. Also, the policy manager unit 90 may output an instruction to scale or replace an element to the life cycle management unit 94 according to the result of the determination process.

[0117] The policy manager unit 90 according to this embodiment is capable of acquiring performance index value data stored in the data bus unit 68. The policy manager unit 90 may then execute a predetermined determination process based on the performance index value data acquired from the data bus unit 68. The policy manager unit 90 may also execute a predetermined determination process based on alert message data stored in the data bus unit 68.

[0118] In this embodiment, for example, the ticket management unit 84 generates a ticket indicating the content to be notified to the administrator of the communication system 1. The ticket management unit 84 may generate a ticket indicating the content of the occurred fault data. The ticket management unit 84 may also generate a ticket indicating the value of performance index value data or metric data. The ticket management unit 84 may also generate a ticket indicating the determination result by the policy manager unit 90.

[0119] Then, the ticket management unit 84 notifies the administrator of the communication system 1 of the generated ticket. For example, the ticket management unit 84 may send an email with the generated ticket attached to the email address of the administrator of the communication system 1.

[0120] In the communication system 1 according to this embodiment, a degradation in performance of the NS, NF, etc. (so-called silent failure) may occur without an abnormality such as a failure being detected.

[0121] An example of how to deal with the occurrence of a silent failure, which is executed in the platform system 30 according to this embodiment, will be described below. In the following description, elements that implement communication functions, such as NSs and NFs, will be referred to as functional elements.

[0122] A plurality of network slices are constructed in the communication system 1 according to the present embodiment. A separate group of routers is set as a component for each of the plurality of network slices constructed in the communication system 1 according to the present embodiment. Here, a common router may be set as a component in the plurality of network slices.

[0123] FIG. 7 is a diagram schematically illustrating an example of the configuration of a group of functional elements that perform communication using one of a plurality of network slices constructed in the communication system 1 of this embodiment.

[0124] The network slice shown in FIG. 7 includes multiple segment routing paths 100 as components. As such, in this embodiment, each of multiple network slices constructed in the communication system 1 may include one or multiple segment routing paths 100 as components. In the segment routing path 100, packets are forwarded by segment routing (for example, packets are forwarded by SRv6 or SRMPLS (Segment Routing Multi-Protocol Label Switching)). Each of the multiple segment routing paths 100 may include a router group as a component. Here, a common router may be set as a component in the multiple segment routing paths 100.

[0125] In this embodiment, each of the functional elements included in the communication system 1 can use one or more network slices that are at least a part of the multiple network slices constructed in the communication system 1. The functional elements included in the communication system 1 can perform communication using the network slices available to the functional elements. Hereinafter, communication performed by a functional element using the network slices available to the functional elements will be referred to as slice communication.

[0126] In the example of Figure 7, a group of functional elements that communicate using a network slice includes multiple UPFs 50 (50a, 50b, 50c, ...) and multiple gNBs 102 (102a, 102b, 102c, ...). The gNB 102 includes a DU 42 and a CU 44. Note that the group of functional elements that communicate using the network slice may also include other types of functional elements (e.g., an AMF 46, an SMF 48, etc.).

[0127] In the communication system 1 according to this embodiment, the router group constituting each of the multiple network slices constructed in the communication system 1 is managed. Here, for example, the inventory database 82 may store router group data indicating the router group constituting each of the multiple network slices constructed in the communication system 1.

[0128] The router group data according to this embodiment may include, for example, the segment routing path management data exemplified in FIG. 8 and the router group management data exemplified in FIG.

[0129] The segment routing path management data in this embodiment is, for example, data indicating one or more segment routing paths 100 through which packets are forwarded in communication performed by a functional element using a network slice available to the functional element.

[0130] As shown in FIG. 8, the segment routing path management data includes, for example, a functional element ID, a slice ID, and a segment routing path ID list.

[0131] In the segment routing path management data, a functional element ID, which is an identifier of a functional element, is associated with a slice ID, which is an identifier of a network slice that the functional element can use. Also, the segment routing path management data is associated with a segment routing path ID list, which is a list of identifiers (segment routing path IDs) of segment routing paths 100 through which packets are forwarded in communication performed by the functional element using the network slice.

[0132] Here, it is assumed that the identifiers of gNB102a, gNB102b, and gNB102c are "gNB001," "gNB002," and "gNB003," respectively.

[0133] In this case, the segment routing path management data shown in Figure 8 indicates that gNB102a, gNB102b, and gNB102c can all use multiple network slices, including three network slices with slice IDs "001," "002," and "003," respectively. Note that the available network slices do not need to be common to all functional elements. The available network slices may differ depending on the functional element.

[0134] Hereinafter, the network slice with slice ID "001" will be referred to as the first network slice. Also, the network slice with slice ID "002" will be referred to as the second network slice. Also, the network slice with slice ID "003" will be referred to as the third network slice.

[0135] For example, when gNB102a performs slice communication using a first network slice, communication is performed using a segment routing path 100 whose segment routing path ID is one of "001", "002", "003", .... Also, when gNB102a performs slice communication using a second network slice, communication is performed using a segment routing path 100 whose segment routing path ID is one of "011", "012", "013", .... Also, when gNB102a performs slice communication using a third network slice, communication is performed using a segment routing path 100 whose segment routing path ID is one of "021", "022", "023", ....

[0136] Furthermore, when gNB102b performs slice communication using the first network slice, communication is performed using a segment routing path 100 whose segment routing path ID is one of "101", "102", "103", .... When gNB102b performs slice communication using the second network slice, communication is performed using a segment routing path 100 whose segment routing path ID is one of "111", "112", "113", .... When gNB102b performs slice communication using the third network slice, communication is performed using a segment routing path 100 whose segment routing path ID is one of "121", "122", "123", ....

[0137] Furthermore, when gNB102c performs slice communication using the first network slice, communication is performed using a segment routing path 100 whose segment routing path ID is one of "201", "202", "203", .... When gNB102c performs slice communication using the second network slice, communication is performed using a segment routing path 100 whose segment routing path ID is one of "211", "212", "213", .... When gNB102c performs slice communication using the third network slice, communication is performed using a segment routing path 100 whose segment routing path ID is one of "221", "222", "223", ....

[0138] The router group management data according to this embodiment is, for example, data indicating a route group that is a component of each of a plurality of segment routing paths 100 .

[0139] 9, the router group management data includes, for example, a segment routing path ID and a router ID list. The segment routing path ID is an identifier of the segment routing path 100. As described above, the segment routing path ID corresponds to an element of the segment routing path ID list included in the segment routing path management data. In the router group management data, the segment routing path ID is associated with a router ID list, which is a list of identifiers (router IDs) of routers that are components of the segment routing path 100 identified by the segment routing path ID.

[0140] 9, it is shown that the identifiers of multiple routers constituting the segment routing path 100 whose segment routing path ID is "011" are "10000", "10001", "10002", ..., "20001", .... It is also shown that the identifiers of multiple routers constituting the segment routing path 100 whose segment routing path ID is "012" are "10000", "10011", "10012", .... It is also shown that the identifiers of multiple routers constituting the segment routing path 100 whose segment routing path ID is "013" are "10000", "10021", "10022", ....

[0141] It also shows that the identifiers of multiple routers constituting the segment routing path 100 whose segment routing path ID is "101" are "11000", "11001", "11002", etc. It also shows that the identifiers of multiple routers constituting the segment routing path 100 whose segment routing path ID is "102" are "11000", "11011", "11012", etc., "20001", etc. It also shows that the identifiers of multiple routers constituting the segment routing path 100 whose segment routing path ID is "103" are "11000", "11021", "11022", etc.

[0142] It also shows that the identifiers of multiple routers constituting the segment routing path 100 whose segment routing path ID is "221" are "12000", "12001", "12002", etc. It also shows that the identifiers of multiple routers constituting the segment routing path 100 whose segment routing path ID is "222" are "12000", "12011", "12012", etc. It also shows that the identifiers of multiple routers constituting the segment routing path 100 whose segment routing path ID is "223" are "12000", "12021", "12022", etc., "20001", etc.

[0143] In the example of FIG. 9, a router with a router ID of "20001" is a common component of three segment routing paths 100 with segment routing path IDs of "011", "102", and "223", respectively.

[0144] In addition, in this embodiment, as described above, the slice manager unit 92, the life cycle management unit 94, or the SDN controller 74 may change the segment routing path 100, which is a component of the network slice, or the router, which is a component of the segment routing path 100.

[0145] In this embodiment, in response to such changes in components, the router group data stored in the inventory database 82 (for example, the segment routing path management data shown in FIG. 8 and the router group management data shown in FIG. 9) is updated.

[0146] Therefore, by referring to the router group data, it is possible to identify the segment routing path 100, which is a current component of the network slice, and the router group, which is a current component of the segment routing path 100.

[0147] In this embodiment, for example, the monitoring function unit 72 monitors the performance of each of the multiple functional elements included in the communication system 1 in slice communication using the network slice for each network slice in which the functional element is available.

[0148] Specifically, for example, the performance of gNB102a in slice communication using the first network slice, the performance of gNB102a in slice communication using the second network slice, the performance of gNB102a in slice communication using the third network slice, the performance of gNB102b in slice communication using the first network slice, the performance of gNB102b in slice communication using the second network slice, the performance of gNB102b in slice communication using the third network slice, the performance of gNB102c in slice communication using the first network slice, the performance of gNB102c in slice communication using the second network slice, and the performance of gNB102c in slice communication using the third network slice are monitored.

[0149] Then, in this embodiment, for example, the policy manager unit 90 determines, for each of the multiple functional elements included in the communication system 1, for each network slice in which the functional element is available, whether the performance of the functional element in slice communication using the network slice has deteriorated.

[0150] Here, the policy manager unit 90 may repeatedly determine whether the performance of the functional element in the slice communication has deteriorated. For example, the policy manager unit 90 may repeatedly determine whether the performance of the functional element in the slice communication has deteriorated at predetermined time intervals (for example, every 15 minutes).

[0151] For example, the monitoring function unit 72 may generate, at a predetermined time interval (e.g., every 15 minutes), performance index value data indicating the performance of the functional element in slice communication using the network slice for a most recent predetermined time (e.g., the most recent 15 minutes) for each network slice available for the functional element, and then output the generated performance index value data to the data bus unit 68 at the time interval.

[0152] The policy manager unit 90 may then acquire the output performance index value data in response to the output of the performance index value data to the data bus unit 68. The policy manager unit 90 may then determine whether or not the performance of the functional element in slice communication using the network slice has deteriorated based on the performance index value data. In this manner, it may be determined at predetermined time intervals whether or not the performance of the functional element in slice communication has deteriorated.

[0153] For example, if the performance index value data indicates that the larger the value, the higher the performance indicated by the performance index value data, the policy manager unit 90 may determine that the performance of the functional element in the slice communication has deteriorated if the value of the latest performance index value data indicating the performance of the functional element in the slice communication is smaller than a predetermined threshold value.

[0154] Furthermore, if the performance index value data indicates that the larger the value, the lower the performance indicated by the performance index value data, the policy manager unit 90 may determine that the performance of the functional element in the slice communication has deteriorated if the value of the latest performance index value data indicating the performance of the functional element in the slice communication is greater than a predetermined threshold value.

[0155] Here, examples of the performance indicated by the performance index value data include a bearer connection completion rate, an abnormal disconnection count, an abnormal disconnection rate, etc. Furthermore, an overall value (e.g., a linear combination value of multiple types of performance index values) calculated based on performance index values ​​indicating multiple types of performance (e.g., a bearer connection completion rate and an abnormal disconnection count) may be used as the value of the performance index value data. Note that the performance indicated by the performance index value data is not limited to the above, and may be, for example, throughput, latency, etc.

[0156] In this embodiment, for example, when it is determined that the performance of a plurality of functional elements in slice communication has deteriorated, the policy manager unit 90 identifies, for each of the plurality of functional elements, a router group that exists on the path of the slice communication based on the router group data. Here, as described above, the path may be a path on which packets are forwarded by segment routing.

[0157] For example, the policy manager unit 90 may determine whether or not the performance of a plurality of functional elements in slice communication has deteriorated at the same timing at a predetermined time interval, and may identify a plurality of functional elements whose performance in slice communication has deteriorated in the most recent determination.

[0158] Then, the policy manager unit 90 may identify a group of routers that exist on the path of the slice communication for each of the identified functional elements.

[0159] In this embodiment, for example, the policy manager unit 90 estimates that at least one router included in any of the router groups identified for each of the multiple functional elements whose performance is determined to be degraded is the router causing the degradation in the performance of the functional element.

[0160] For example, suppose that the latest determination determined that the performance of gNB102a in slice communication using the second network slice has deteriorated.

[0161] In this case, for example, in the segment routing path management data, a segment routing path ID included in the segment routing path ID list associated with the functional element ID "gNB001" and the slice ID "002" is identified. The segment routing path ID identified here is, for example, "011," "012," "013," etc.

[0162] Then, for each of the segment routing path IDs thus identified, the router ID included in the router ID list associated with the segment routing path ID in the router group management data is identified.

[0163] For example, in the router group management data, a router ID list associated with segment routing path ID "011", a router ID list associated with segment routing path ID "012", and a router ID list associated with segment routing path ID "013" are identified.

[0164] Then, a router ID included in at least one of the router ID lists identified in this way is identified. Hereinafter, a group of router IDs including the router IDs identified in this way will be referred to as a cause candidate router ID group. Hereinafter, for example, "10000," "10001," "10002," "10011," "10012," "10021," "10022," "20001," ... are identified as a cause candidate router ID group associated with the gNB 102a and the second network slice.

[0165] Furthermore, it is assumed that the latest determination determined that the performance of gNB102b in slice communication using the first network slice has deteriorated.

[0166] In this case, similarly, "11000", "11001", "11002", "11011", "11012", "11021", "11022", "20001", etc. are identified as a group of possible cause router IDs associated with gNB102b and the first network slice.

[0167] Furthermore, it is assumed that the latest determination determined that the performance of gNB102c in slice communication using the third network slice has deteriorated.

[0168] In this case, similarly, "12000", "12001", "12002", "12011", "12012", "12021", "12022", "20001", ... are identified as a group of possible cause router IDs associated with gNB102c and the third network slice.

[0169] The policy manager unit 90 then identifies at least one router ID included in any of the cause candidate router IDs identified as described above for each of the multiple functional elements determined to have degraded performance in slice communication, and estimates the router identified by the identified router ID as the router causing the degradation of the performance of the functional element.

[0170] Here, as described above, a group of cause candidate router IDs associated with gNB102a and the second network slice, a group of cause candidate router IDs associated with gNB102b and the first network slice, and a group of cause candidate router IDs associated with gNB102c and the third network slice are identified.

[0171] Therefore, in this case, the router ID "20001", which is included in all three groups of router IDs that are candidates for the cause, is estimated to be the router ID of the router that is causing the degradation in performance of the functional element.

[0172] For ease of explanation, in the above example, one router is estimated as the router causing the degradation of the performance of the functional element, but multiple routers may be estimated as the router causing the degradation of the performance of the functional element.

[0173] In this embodiment, for example, the slice manager unit 92 may output to the SDN controller 74, for each of one or more routers estimated to be the cause of the degradation in performance of a functional element, an instruction to change the communication path for the network slice that includes the router as a component. Then, the SDN controller 74 may change the communication path created by the SDN controller 74 in accordance with the instruction to change.

[0174] For example, the slice manager unit 92 may output an instruction to change the communication path associated with the router ID of a router that is presumed to be the cause of the degradation in performance of a functional element to the SDN controller 74. Then, in response to receiving the instruction to change the communication path, the SDN controller 74 may change the communication path created by the SDN controller 74 to a communication path that excludes the router identified by the router ID (i.e., a communication path that does not pass through the router).

[0175] Furthermore, an administrator or the like of the platform system 30 may check whether or not an abnormality such as a failure or overcapacity has occurred in each of the routers that are presumed to be the cause of the degradation of the performance of the functional elements. Then, the administrator or the like of the platform system 30 may output an instruction to the SDN controller 74 to exclude the router in which the occurrence of an abnormality has been confirmed from the communication path. Then, in response to receiving the instruction, the SDN controller 74 may change the communication path created by the SDN controller 74 to a communication path that excludes the router (i.e., a communication path that does not pass through the router).

[0176] In addition, the SDN controller 74 or the slice manager unit 92 may update the segment routing path management data shown in Figure 8 or the router group management data shown in Figure 9 stored in the inventory database 82 in response to a change in the communication path.

[0177] Even if no abnormality is detected in a router, which is a component common to multiple network slices included in the communication system 1 of this embodiment, as described above, multiple functional elements may experience a degradation in the performance of the functional element (so-called silent failure) in communication using a network slice that the functional element can use.

[0178] In this embodiment, as described above, for each of a plurality of functional elements whose performance in slice communication is determined to be degraded, a group of routers existing on the path of the slice communication is identified, and at least one router included in any of the identified groups of routers is estimated to be the router causing the degradation of the performance of the functional element.

[0179] In this way, according to this embodiment, it is possible to accurately estimate the router that is the cause of a silent failure in a network slice.

[0180] In addition, in this embodiment, the policy manager unit 90 may determine whether the performance of a functional element in slice communication has deteriorated based on the performance of the functional element at a given point in time in slice communication and the performance of the functional element prior to the given point in time in the slice communication.

[0181] For example, a threshold may be determined based on past performance index data values, and it may be determined whether the performance of the functional element has deteriorated based on the determined threshold.

[0182] For example, the AI ​​unit 70 may calculate the expected value (e.g., moving average value) and standard deviation of the performance index value based on past performance index value data (e.g., performance index value data for a recent period) indicating the performance of a functional element in slice communication using a network slice. Here, the expected value and standard deviation of the performance index value may be calculated using a trained machine learning model. Then, the above-mentioned threshold value may be determined based on the calculated expected value and standard deviation.

[0183] For example, the threshold value may be determined to be the sum of the expected value of the performance index value and twice the standard deviation of the performance index value. In this case, if the value of the latest performance index value data indicating the performance of the functional element in the slice communication is greater than the threshold value, it may be determined that the performance of the functional element in the slice communication has deteriorated.

[0184] Alternatively, for example, the threshold value may be determined by subtracting twice the standard deviation of the performance index value from the expected value of the performance index value. In this case, if the value of the latest performance index value data indicating the performance of the functional element in the slice communication is smaller than the threshold value, it may be determined that the performance of the functional element in the slice communication has deteriorated.

[0185] Here, the AI ​​unit 70 may determine a threshold value for each period type (for example, time zone, day of the week, etc.). For example, the AI ​​unit 70 may calculate an expected value and a standard deviation of the performance index values ​​for a specific period type based on performance index value data for a period belonging to the specific period type among the most recent fixed periods. Then, the AI ​​unit 70 may determine a threshold value for the specific period type based on the expected value and standard deviation of the performance index values ​​for the specific period type calculated in this way.

[0186] The policy manager unit 90 may determine whether the performance of a functional element in a slice communication has deteriorated based on the performance of the functional element at a given time point in the slice communication and the performance of the functional element in a period of the same period type as the period to which the given time point in the slice communication belongs, prior to the given time point in the slice communication. For example, assume that the day of the week to which the given time point belongs is Sunday. In this case, the policy manager unit 90 may determine whether the performance of the functional element has deteriorated based on a performance index value indicating the performance of the functional element at that time point in the slice communication and a threshold value for Sunday in the slice communication.

[0187] In this way, it becomes possible to determine whether the performance of a functional element has deteriorated, taking into account the past performance of the functional element.

[0188] Furthermore, for example, the policy manager unit 90 may identify a group of routers present on the path of slice communication for each functional element whose performance in slice communication has been determined to be degraded in at least one of the most recent predetermined number of determinations, and at least one router included in any of the groups of routers identified in this manner may be estimated as the router causing the degradation in performance of the functional element.

[0189] For example, it is assumed that a determination as to whether or not the performance of a functional element in slice communication has deteriorated is made at a predetermined time interval (for example, every 15 minutes). In this case, a router group for a plurality of functional elements whose performance in slice communication has been determined to have deteriorated in at least one of the most recent four determinations (i.e., determinations made 45 minutes ago, 30 minutes ago, 15 minutes ago, and the present time) may be identified.

[0190] Even if a performance degradation is caused by a single router, there may be a lag in the timing at which the performance degradation occurs due to functional elements, depending on the distance from the router, etc. As described above, by identifying a group of routers for a functional element whose performance is determined to be degraded in at least one of the most recent predetermined number of determinations, it becomes possible to accurately estimate the router that is the cause of the silent failure in the network slice, even if such a lag occurs.

[0191] In addition, the policy manager unit 90 may determine that the performance of a functional element in slice communication has deteriorated if a performance index value indicating the performance of the functional element in slice communication satisfies a predetermined condition for a predetermined period of time.

[0192] For example, it may be assumed that a determination is made every 15 minutes as to whether or not a performance index value indicating the performance of a functional element in slice communication satisfies a predetermined condition (e.g., whether or not the performance index value is smaller than a threshold value). In this case, if it is determined that the performance index value from 45 minutes ago to the present satisfies the predetermined condition (i.e., the performance index value satisfies the predetermined condition in three consecutive determinations), it may be determined that the performance of the functional element in the slice communication has deteriorated.

[0193] In this way, it is possible to prevent a functional element that has experienced a temporary performance degradation that does not require any action from being determined to have a performance degradation.

[0194] Furthermore, the performance management unit 88 may generate overall performance index value data indicating the performance of the functional element in slice communication using the network slice for each network slice in which the functional element is available, by aggregating the performance index value data generated by the monitoring function unit 72. Then, the policy manager unit 90 may determine, for each network slice in which the functional element is available, whether the performance of the functional element in slice communication using the network slice has deteriorated, based on the overall performance index value data generated by the performance management unit 88.

[0195] In addition, in this embodiment, the policy manager unit 90 may exclude routers that are located on the path of slice communication for a functional element that is not determined to have a decline in performance in slice communication from the routers that are estimated to be the cause of the decline in performance of the functional element.

[0196] For example, suppose that it is not determined that the performance of gNB 102a is degraded in slice communication using the first network slice. In this case, a router included in a group of routers that are components of the segment routing path 100 whose segment routing path ID is "001," "002," or "003" may be identified as an excluded router. If the excluded router is included in the routers estimated to be the cause of the degradation in performance of the functional element, the policy manager unit 90 may exclude the excluded router from the routers estimated to be the cause of the degradation in performance of the functional element.

[0197] This makes it possible to more accurately identify the router that is the cause of a silent failure in a network slice.

[0198] In the above example, for each network slice available to a functional element included in RAN 32 (gNB 102 in the above example), it is determined whether the performance of the functional element in slice communication using the network slice is degraded. In this case, a group of routers present on the path between RAN 32 and core network system 34 (the path between gNB 102 and UPF 50 in the above example) may be identified.

[0199] Here, in this embodiment, for each network slice available to a functional element (e.g., UPF 50) included in the core network system 34, it may be determined whether the performance of the functional element in slice communication using the network slice has deteriorated. Then, a group of routers present on the path between the RAN 32 and the core network system 34 may be identified. In this case, it may be determined whether the performance of UPF 50 in slice communication using the network slice has deteriorated, for example, based on a performance index value related to UPF 50.

[0200] The present invention is also applicable to estimating routers that are the cause of silent failures in network slices on paths other than those between the RAN 32 and the core network system 34.

[0201] For example, a router on the path (midhaul) between CU44 and DU42 that is the cause of the silent failure in the network slice may be estimated.

[0202] In this case, the policy manager unit 90 may determine, for each network slice available to a CU44, whether the performance of the CU44 in slice communication using the network slice has deteriorated. Then, for each of multiple CU44s determined to have deteriorated performance in slice communication, the policy manager unit 90 may identify a group of routers present on the path of the slice communication between the CU44 and the DU42. Then, at least one router included in any of the groups of routers identified in this manner may be estimated as the router causing the deterioration of the performance of the CU44.

[0203] Furthermore, the value of the performance index data may be a value indicating the performance of a functional element in the user plane, or a value indicating the performance of a functional element in the control plane. In this case, the above-mentioned bearer connection completion rate, abnormal disconnection count, abnormal disconnection rate, etc. correspond to the performance of the functional element in the user plane. An example of the performance of a functional element in the control plane is the registration success rate.

[0204] Then, when determining whether the performance of a functional element in the user plane is degraded, the router that is causing the degradation in performance of the functional element may be estimated from among the group of routers that are components of the user plane.

[0205] Furthermore, when determining whether the performance of a functional element in the control plane is degraded, the router that is causing the degradation in performance of the functional element may be estimated from among the group of routers that are components of the control plane.

[0206] Furthermore, even when a judgment is made about the performance of a functional element in the control plane, the router that is causing the degradation in performance of the functional element may be estimated from among the group of routers that are components of the control plane and the user plane.

[0207] Furthermore, for each of multiple functional elements whose performance in slice communication is determined to be degraded, it is not necessary to identify a router group including all routers present on the path of the slice communication. Here, among the router group present on the path of the slice communication, a router group that is a component of one or more network slice subnet instances may be identified. For example, a router group in the backhaul portion present on the path may be identified. Or, for example, a router group in the midhaul portion present on the path may be identified.

[0208] Here, an example of the flow of processing performed in the platform system 30 according to this embodiment to infer the router causing the degradation of the performance of a functional element will be described with reference to the flow diagram shown in FIG.

[0209] First, for each of the multiple functional elements included in the communication system 1, the policy manager unit 90 determines, for each network slice in which the functional element is available, whether the performance of the functional element in slice communication using the network slice has deteriorated (S101).

[0210] Then, the policy manager unit 90 identifies a plurality of functional elements that have been determined to have deteriorated performance in slice communication in the process shown in S101 (S102).

[0211] Then, the policy manager unit 90 identifies a group of routers present on the path of the slice communication for each of the functional elements identified in the process shown in S102 (S103).

[0212] Then, at least one router included in any of the router groups identified in the process shown in S103 is estimated to be the router causing the degradation in performance of the multiple functional elements identified in the process shown in S102 (S104), and the process shown in this processing example is terminated.

[0213] The present invention is not limited to the above-described embodiment.

[0214] For example, the functional units according to this embodiment are not limited to those shown in FIG.

[0215] Furthermore, the functional unit according to this embodiment does not need to be a 5G NF. For example, the functional unit according to this embodiment may be a 4G network node such as an eNodeB, a vDU, a vCU, a Packet Data Network Gateway (P-GW), a Serving Gateway (S-GW), a Mobility Management Entity (MME), or a Home Subscriber Server (HSS).

[0216] Furthermore, the division of roles among the functions shown in FIG. 5 is not limited to those described above.

[0217] Furthermore, the functional units according to the present embodiment may be realized using hypervisor-type or host-type virtualization technology instead of container-type virtualization technology. Furthermore, the functional units according to the present embodiment do not need to be implemented by software, but may be implemented by hardware such as electronic circuits. Furthermore, the functional units according to the present embodiment may be implemented by a combination of electronic circuits and software.

[0218] The technology described in this disclosure can also be expressed as follows. [1] a router group data storage means for storing, for each of a plurality of network slices constructed in the communication system, router group data indicating a router group constituting the network slice; a determination means for determining, for each of a plurality of functional elements included in the communication system, whether the performance of the functional element in slice communication using the network slice is degraded for each network slice in which the functional element is available; a router group identification means for identifying, for each of the plurality of functional elements, a router group present on a path of the slice communication based on the router group data when it is determined that the performance of the functional element in the slice communication has deteriorated for the plurality of functional elements; a router estimation means for estimating at least one router included in any of the router groups identified for each of the plurality of functional elements whose performance is determined to be degraded as the router causing the degradation of the performance of the functional element; A router estimation system including: [2] The determining means determines that the performance of the functional element in the slice communication has deteriorated when a performance index value indicating the performance of the functional element in the slice communication satisfies a predetermined condition for a predetermined period of time. The router estimation system described in [1]. [3] the determining means repeatedly determines whether or not the performance of the functional element in the slice communication is degraded; the router group identification means identifies the router group for the functional element whose performance is determined to have deteriorated in at least one determination among a predetermined number of most recent determinations. [1] or [2]. A router estimation system. [4] The router estimation means excludes routers present on a path of the slice communication of the functional element whose performance in the slice communication is not determined to be degraded from routers estimated to be the cause of the degradation of the performance of the functional element. A router estimation system according to any one of [1] to [3]. [5] The determining means determines whether the performance of the functional element in the slice communication has deteriorated based on the performance of the functional element at a given time point in the slice communication and the performance of the functional element prior to the given time point in the slice communication. A router estimation system according to any one of [1] to [4]. [6] The determination means determines whether the performance of the functional element in the slice communication has deteriorated based on the performance of the functional element at a given time point in the slice communication and the performance of the functional element in a period type that is the same as the period type to which the given time point belongs prior to the given time point in the slice communication. The router estimation system described in [5]. [7] The determination means determines, for each network slice available to a functional element included in the radio access network of the communication system, whether or not the performance of the functional element in slice communication using the network slice is degraded; the router group identification means identifies the router group present on a path between the wireless access network and a core network system of the communication system; A router estimation system according to any one of [1] to [6]. [8] The determination means determines, for each network slice available to a functional element included in a core network system of the communication system, whether or not the performance of the functional element in slice communication using the network slice is degraded; the router group identification means identifies the router group present on a path between the core network system and the radio access network of the communication system; A router estimation system according to any one of [1] to [6]. [9] The determination means determines, for each network slice available to a CU (Central Unit), whether or not the performance of the CU in slice communication using the network slice is degraded; The router group identification means identifies the router group present on a path between the CU and a DU (Distributed Unit) included in the communication system. A router estimation system according to any one of [1] to [6].

[10] The route is a route through which packets are forwarded by segment routing. A router estimation system according to any one of [1] to [9].

[11] the functional element is a network service or a network function; A router estimation system according to any one of [1] to

[10] .

[12] Storing router group data indicating a router group constituting each of a plurality of network slices constructed in the communication system; For each of a plurality of functional elements included in the communication system, for each network slice in which the functional element is available, determining whether or not the performance of the functional element in slice communication using the network slice is degraded; When it is determined that the performance of a plurality of functional elements in the slice communication has deteriorated, for each of the plurality of functional elements, a router group that exists on a path of the slice communication is identified based on the router group data; Inferring at least one router included in any of the router groups identified for each of the plurality of functional elements whose performance is determined to be degraded as a router causing the degradation of the performance of the functional element; A router estimation method including:

Claims

1. a router group data storage process for storing, for each of a plurality of network slices constructed in the communication system, router group data indicating a router group constituting the network slice; a determination process for determining, for each of a plurality of functional elements included in the communication system, whether or not the performance of the functional element in slice communication using the network slice is degraded for each network slice in which the functional element is available; a router group identification process for identifying a router group present on a path of the slice communication for each of the plurality of functional elements based on the router group data when it is determined that the performance of the functional elements in the slice communication has deteriorated for the plurality of functional elements; a router estimation process for estimating at least one router included in any of the router groups identified for each of the plurality of functional elements whose performance is determined to be degraded as the router causing the degradation of the performance of the functional element; A router estimation system that performs

2. In the determination process, when a performance index value indicating the performance of the functional element in the slice communication satisfies a predetermined condition for a predetermined period of time, it is determined that the performance of the functional element in the slice communication has deteriorated. The router estimation system according to claim 1 .

3. In the determination process, it is repeatedly determined whether or not the performance of the functional element in the slice communication is degraded; In the router group identification process, the router group for the functional element whose performance is determined to be degraded in at least one determination among a predetermined number of most recent determinations is identified. The router estimation system according to claim 1 .

4. In the router estimation process, a router present on a path of the slice communication of the functional element whose performance is not determined to be degraded in the slice communication is excluded from routers estimated to be the cause of the degradation of the performance of the functional element. The router estimation system according to claim 1 .

5. In the determination process, it is determined whether the performance of the functional element in the slice communication has deteriorated based on the performance of the functional element at a given time point in the slice communication and the performance of the functional element prior to the given time point in the slice communication. The router estimation system according to claim 1 .

6. In the determination process, it is determined whether the performance of the functional element in the slice communication has deteriorated based on the performance of the functional element at a given time point in the slice communication and the performance of the functional element in a period type that is the same as the period type to which the given time point in the slice communication belongs, prior to the given time point in the slice communication. The router estimation system according to claim 5 .

7. In the determination process, for each network slice available to a functional element included in the radio access network of the communication system, it is determined whether or not the performance of the functional element in slice communication using the network slice is degraded; In the router group identification process, the router group present on a path between the wireless access network and a core network system of the communication system is identified. The router estimation system according to claim 1 .

8. In the determination process, for each network slice available to a functional element included in a core network system of the communication system, it is determined whether or not the performance of the functional element in slice communication using the network slice is degraded; In the router group identification process, the router group present on a path between the core network system and a radio access network of the communication system is identified. The router estimation system according to claim 1 .

9. In the determination process, for each network slice available to a CU (Central Unit), it is determined whether the performance of the CU in slice communication using the network slice is degraded; In the router group identification process, the router group present on a path between the CU and a DU (Distributed Unit) included in the communication system is identified. The router estimation system according to claim 1 .

10. The route is a route through which packets are forwarded by segment routing. The router estimation system according to claim 1 .

11. the functional element is a network service or a network function; The router estimation system according to claim 1 .

12. Storing router group data indicating a router group constituting each of a plurality of network slices constructed in the communication system; For each of a plurality of functional elements included in the communication system, for each network slice in which the functional element is available, determining whether or not the performance of the functional element in slice communication using the network slice is degraded; When it is determined that the performance of a plurality of functional elements in the slice communication has deteriorated, for each of the plurality of functional elements, a router group that exists on a path of the slice communication is identified based on the router group data; Inferring at least one router included in any of the router groups identified for each of the plurality of functional elements whose performance is determined to be degraded as a router causing the degradation of the performance of the functional element; A router estimation method executed by one or more computers, comprising:

Images