Slice management system and method

Abstract

To regulate communication of a user terminal in a base even in an environment where a core network is common to a plurality of organization users.SOLUTION: A slice management system associates a virtual network not allocated to any slice, with a slice corresponding to an organization user. A base switch, which is a switch in a base of the organization user, is configured to transmit / receive user data associated with a virtual network ID set on the base switch, and not to transmit / receive user data not associated with the virtual network ID set on the base switch. The slice management system sets an ID of the virtual network associated with the slice of the organization user, to the base switch in the base of the organization user.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates generally to wireless communications. [Background technology]

[0002] The use of wireless communication services is expanding. There is a movement for carriers that do not have wireless communication services to develop local 5G (5th Generation) as a new wireless communication service.

[0003] As one form of such wireless communication service, a wireless communication service in which a 5G core (an example of a core network) is shared by multiple organizational users can be provided. In this form, there is no need to deploy a 5G core, which is generally expensive for terminal authentication and mobile communication termination processing, at each base. Note that an "organizational user" is an organization as a user. An "organization" may be a company, a public organization, etc. A "base" is a place where a local 5G is installed, such as a branch office or a factory of an organizational user.

[0004] In such wireless communication services, in order to guarantee network independence for users in an organization, it is conceivable to prepare a network slice (hereinafter, a slice) for each user in the organization. The slice is obtained by network slicing.

[0005] For example, Patent Document 1 discloses the following technology: Slices, which are virtual networks, are provided at multiple stages of a communication path for communication between a user terminal and a service server. A NW operation device acting as a slice management device acquires a slice setting request including service requirements. The NW operation device determines a slice setting policy that satisfies the service requirements based on a comparison result of costs calculated according to slices to be set for each of the multiple stages. The NW operation device performs processing related to the setting of slices at each of the multiple stages based on the slice setting policy. [Prior art documents] [Patent documents]

[0006] [Patent Document 1] WO2018 / 173564 Summary of the Invention [Problem to be solved by the invention]

[0007] One issue when a 5G core is common to multiple organizational users is that the common 5G core can be accessed from any of the locations. A specific example will be described with reference to FIG. 12. In FIG. 12, "UE-Xn" means a user terminal (wireless communication terminal) of an individual user Xn who belongs to organizational user X. A "station" is an example of a location where a common 5G core is installed, and is a building of a communications carrier. An "individual user" is a person who belongs to any of the organizational users, for example, an employee.

[0008] A 5G core and a UPF (User Plane Function) server connected to the 5G core are installed in a station building. Assume that three slices (slices 1 to 3) are set for the 5G core. Assume also that there are three bases (base 1 of organization user A, base 2 of organization user A, and base 1 of organization user B).

[0009] All individual users can access all slices 1 to 3 from any location using a user terminal. For this reason, for example, as illustrated in Fig. 12, even if individual user A3 moves from location 2 of organizational user A to location 1 of organizational user B, individual user A3 can access any of slices 1 to 3 (for example, slice 1 as shown) from location 1 of organizational user B using a user terminal.

[0010] The 5G network is a public network. For this reason, it is assumed that wireless communication is possible through any base station under the 5G core. Therefore, as described above, in an environment in which the 5G core is shared by multiple organizational users, there is a problem that all individual users can access all slices from any base station using a user terminal. For this reason, for each organizational user, a user terminal of an unspecified individual user for the organizational user (for example, an individual user other than an individual user belonging to the organizational user) can communicate at the organizational user's base using local 5G resources at the organizational user's base.

[0011] Patent Document 1 does not disclose or suggest the above-mentioned problems or the means for solving them.

[0012] The above-mentioned problems may also occur in wireless communication services other than local 5G, such as 6G (6th Generation) or LTE (Long Term Evolution) wireless communication services. [Means for solving the problem]

[0013] A slice management system including an association control unit and a setting control unit is constructed. The association control unit associates a target virtual network with a target slice of a target organization user. The setting control unit sets a virtual network ID of the target virtual network for one or more target bases of the target organization user to a base switch at the target base. The target organization user is one of the multiple organization users. The one or more target bases are all or a part of one or more bases of the target organization user. For each of the multiple organization users, each base of the organization user has a base station and a base switch. In each base, the base switch is a termination device connected to a mobile backhaul and a base station at the base. The target slice is one slice of one or more slices prepared for the target organization user. The target virtual network is one virtual network that is not assigned to any slice. A user data processing server and a mobile backhaul are connected to a station switch, which is a termination device to which a core network common to multiple organization users is connected. The user data processing server has a user data processing unit, which is a virtual router that relays user data passing through the slice and the data network, for each slice. For each base, the base switch at that base transmits and receives user data associated with the virtual network ID set in that base switch, and does not transmit or receive user data that is not associated with the virtual network ID set in that base switch. Effect of the Invention

[0014] According to the present invention, even in an environment in which a core network is shared by users of a plurality of organizations, it is possible to restrict communication of user terminals at bases. [Brief description of the drawings]

[0015] [Figure 1] 1 shows an example of the overall configuration of a system according to an embodiment of the present invention. [Diagram 2] 1 shows an example of the configuration of a mobile network. [Diagram 3] 1 illustrates an example of the configuration of a slice management system. [Figure 4] The flow of the environment provision process is shown below. [Diagram 5] 13 shows examples of the configuration of an application management database and a template management database. [Figure 6] 1 shows configuration examples of a VLAN management database and a slice management database. [Figure 7] 1 shows examples of the configuration of a base RAN resource database and a RAN resource allocation database. [Figure 8] 1 shows examples of the configuration of a station UPF resource database and a UPF resource allocation database. [Figure 9] An example of a case where the allocated bandwidth for one location in slice 2 exceeds the bandwidth upper limit of that location will be shown. [Figure 10] An example of a case where the allocated bandwidth for each of all bases in slice 2 is equal to or less than the upper bandwidth limit will be shown. [Figure 11] An example of the management UI is shown below. [Figure 12] An example of the related art will be given. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0016] In the following description, an "interface unit" may refer to one or more interface devices. The one or more interface devices may be at least one of the following: One or more I / O (Input / Output) interface devices. The I / O (Input / Output) interface devices are interface devices to at least one of the I / O devices and a remote display computer. The I / O interface device to the display computer may be a communications interface device. The at least one I / O device may be a user interface device, for example, either an input device such as a keyboard and a pointing device, or an output device such as a display device. One or more communication interface devices. The one or more communication interface devices may be one or more homogeneous communication interface devices (e.g., one or more NICs (Network Interface Cards)) or two or more heterogeneous communication interface devices (e.g., a NIC and an HBA (Host Bus Adapter)).

[0017] In the following description, a "memory" refers to one or more memory devices, which are an example of one or more storage devices, and may typically be a primary storage device. At least one memory device in the memory may be a volatile memory device or a non-volatile memory device.

[0018] In the following description, a "persistent storage device" may be one or more persistent storage devices, which are an example of one or more persistent storage devices. A persistent storage device may typically be a non-volatile storage device (e.g., an auxiliary storage device), and more specifically, may be, for example, a hard disk drive (HDD), a solid state drive (SSD), a non-volatile memory express (NVME) drive, or a storage class memory (SCM).

[0019] Also, in the following description, "storage device" may be at least memory, including memory and persistent storage device.

[0020] Furthermore, in the following description, a "processor" may be one or more processor devices. The at least one processor device may typically be a microprocessor device such as a CPU (Central Processing Unit), but may also be other types of processor devices such as a GPU (Graphics Processing Unit). The at least one processor device may be a single-core or multi-core. The at least one processor device may be a processor core. The at least one processor device may also be a broader processor device such as a circuit that is a collection of gate arrays written in a hardware description language that performs part or all of the processing (e.g., an FPGA (Field-Programmable Gate Array), a CPLD (Complex Programmable Logic Device), or an ASIC (Application Specific Integrated Circuit)).

[0021] In the following description, information that provides an output for an input may be described using an expression such as "xxx database," but the information may be data of any structure (for example, structured data or unstructured data), or may be a neural network that generates an output for an input, or a learning model such as a genetic algorithm or random forest. Therefore, the "xxx database" may be referred to as "xxx information." In the following description, the configuration of each database is an example, and one database may be divided into two or more databases, or all or part of two or more databases may be one database.

[0022] In the following description, functions may be described using the expression "yyy unit", but the functions may be realized by one or more computer programs being executed by a processor, or by one or more hardware circuits (e.g., FPGA or ASIC), or by a combination thereof. When a function is realized by a program being executed by a processor, the function may be at least a part of the processor, since the specified processing is performed using a storage device and / or an interface device, etc., as appropriate. Processing described with a function as the subject may be processing performed by a processor or a device having the processor. A program may be installed from a program source. The program source may be, for example, a program distribution computer or a storage medium (e.g., a non-transitory storage medium) that can be read by a computer. The description of each function is an example, and multiple functions may be combined into one function, or one function may be divided into multiple functions.

[0023] In addition, in the following description, when elements of the same type are described without distinction, common reference symbols will be used, and when elements of the same type are described with distinction, reference symbols will be used.

[0024] In addition, the identification information for identifying elements such as a network slice or a wireless communication terminal may be a combination of one or more of a "name," "ID," "identifier," "number," etc.

[0025] 1 shows an example of the overall configuration of a system according to an embodiment of the present invention. In the following description, an example of a plurality of organizational users is organizational users A and B. The organizational users may be called a user group, which is a group of one or more individual users.

[0026] A 5G core 111 (an example of a core network) is common to organizational users A and B. There are multiple slices that share the 5G core 111. There is a slice 90 for each organizational user.

[0027] There is also a user terminal 5, a slice management system 110, a UPF server 112, a DN (data network) 124, a user management terminal 12, and a 5G management terminal 11.

[0028] The user terminal 5 is a wireless communication terminal (typically a mobile terminal such as a notebook or tablet computer or a smartphone) used by an individual user.

[0029] The slice management system 110 is a system that supports the operation of wireless communication services, and specifically manages slices 90. In this embodiment, the slice management system 110 is a physical computer system (e.g., a system having an interface device, a storage device, and a processor connected to them) composed of one or more physical computers, but may also be a logical computer system based on a physical computer system (e.g., a system realized on a cloud platform).

[0030] The UPF server 112 may be a logical server provided on a physical server, but in this embodiment, it is a physical server. The UPF server 112 has a virtual UPF 21 prepared for each slice 90. The virtual UPF 21 is an example of a user data processing unit as a virtual router that relays user data (e.g., U-plane data packets) passing through the slice 90 corresponding to the virtual UPF 21 and the DN 124. The user data is data transmitted and received by the user terminal 5, and passes through the slice 90, the virtual UPF 21, and the DB 124.

[0031] The DN 124 is connected to the UPF server 112 (virtual UPF 21) and an external network (e.g., the Internet). Application services are provided by one or more servers 39 (39A, 39B, ...) via the DN 124. The servers 39 are, for example, application servers.

[0032] The user management terminal 12 is a computer (e.g., an information processing terminal) operated by an organization administrator (an administrator of organization users). In response to an operation by the organization administrator, the user management terminal 12 transmits a request for an application service to the 5G management terminal 11, or transmits a provision request specifying application service requirements to the slice management system 110.

[0033] The 5G management terminal 11 is an information processing terminal serving as an input / output console of the slice management system 110, and is typically operated by a 5G administrator. In response to the operation of the 5G administrator, the 5G management terminal 11 transmits a provision request specifying an application service requirement to the slice management system 110. This provision request may be a request following a request from an organization administrator (a request from the user management terminal 12), or may be a request generated based on an operation by the 5G administrator without a request from the organization administrator.

[0034] There are a plurality of bases 50. The bases 50 are, for example, factories or branches. The bases 50 correspond to any of a plurality of organizational users. In this embodiment, one organizational user corresponds to one or more bases 50, and one base 50 corresponds to one organizational user. The bases 50 are provided with, for example, a base station 2 and a base switch 3 as resources as an edge-side network. The base switch 3 is an edge-side termination device connected to the base station 2 and the mobile backhaul 271. In this embodiment, the edge-side network is a local 5G network, but other types of networks (private LTE networks) may be adopted. In the example shown in FIG. 1, there are two bases 50A1 and 50A2 as bases of organizational user A, and there is one base 50B1 as a base of organizational user B. In addition, there is an individual user An (n=1 to 4) belonging to organizational user A, and the individual user An has a user terminal 5An. Similarly, there is an individual user Bm (m=1) belonging to organizational user B, and the individual user Bm has a user terminal 5Bm.

[0035] There is a station 60. The station 60 is an example of a place where a common 5G core 111 is provided, and is a building of a communication carrier. The station 60 is provided with a station switch 80 and a UPF server 112. The station switch 80 is a core-side termination device connected to a mobile backhaul 271, and is connected to the 5G core 111. The UPF server 112 is connected to at least the station switch 80 out of the 5G core 111 and the station switch 80.

[0036] The slice management system 110 communicates with at least one of the user management terminal 12 and the 5G management terminal 11. For example, the slice management system 110 accepts a provision request from at least one of the user management terminal 12 and the 5G management terminal 11. The provision request specifies a base 50, an application service, and an application service requirement, as described below.

[0037] In this embodiment, the slice 90:virtual UPF 21 is 1:1, and the virtual UPF 21:organization user is 1:1 (or multiple:1). Therefore, one slice 90 corresponds to one virtual UPF 21, and one virtual UPF 21 is assigned to one organization user. Therefore, one slice 90 is assigned to one organization user. The slice management system 110 associates a VLAN ((Virtual LAN)) 91 that is not associated with any slice 90 with the slice 90. The slice management system 110 sets the ID of the VLAN 91 (VLAN path) associated with the slice 90 in the base switch 3 in the base 50 of the organization user to which the slice 90 is assigned. In this embodiment, the setting of the VLAN ID for the base switch 3 is performed via the central office switch 80 (and may be further performed via the 5G core 111), but instead, it may be performed via a management network (e.g., a network in the M plane) not shown in the figure.

[0038] The base switch 3 transmits and receives user data associated with a VLAN ID set in the base switch 3, and does not transmit and receive user data not associated with a VLAN ID set in the base switch 3.

[0039] The slice management system 110 includes an association control unit 321 and a setting control unit 322. The association control unit 321 associates a VLAN 91 with the slice 90. The setting control unit 322 sets the ID of the VLAN 91 associated with the slice 90 in the base switch 3. As a result, the user terminal 5 at the base 50 can perform wireless communication via the slice 90 if the VLAN ID associated with the slice 90 is set in the base switch 3, but cannot perform wireless communication if the VLAN ID is not set in the base switch 3. That is, the communication of the user terminal 5 at the base 50 is appropriately restricted. In addition, in this embodiment, an example of the core network is the 5G core 111, an example of the user data processing server is the UPF server 112, and an example of the user data processing unit is the virtual UPF 21. As a result, it is possible to appropriately restrict the communication of the user terminal 5 at the base 50 in an environment in which the 5G core 111 is common to multiple organizational users. The setting control unit 322 may also set the VLAN ID set in the base switch 3 in the station switch 80 (for example, if the station switch 80 has ports for each base, the VLAN IDs set in the base switches 3A1, 3A2, and 3B1 may be set in the station switch 80).

[0040] When a VLAN ID is set for a slice 90 in the base station 2 and user data via the slice 90 is received from a user terminal 5, the base station 2 transmits the user data associated with the VLAN ID. When a VLAN ID associated with a slice 90 corresponding to the virtual UPF 21 is set in the virtual UPF 21 and the virtual UPF 21 receives user data via the slice 90, the virtual UPF 21 transfers the user data if a VLAN ID that matches (matches) the set VLAN ID is associated with the received user data, but does not transfer the user data if a VLAN ID that matches the set VLAN ID is not associated with the received user data. When a VLAN ID associated with a slice 90 corresponding to the virtual UPF 21 is set in the virtual UPF 21 and user data via the slice 90 is to be transmitted to a user terminal 5 that is the destination of the user data, the virtual UPF 21 transmits the user data associated with the VLAN ID. The setting control unit 322 sets the VLAN ID associated with the slice 90 to the base station 2 in the site 50 where communication via the slice 90 is permitted, and to the virtual UPF 21 corresponding to the slice 90. As a result, the VLAN ID set in the site switch 3 is associated with both the user data transmitted from the user terminal 5 via the base station 2 and the user data transmitted from the virtual UPF 21, so that the user data can pass through the site switch 3, and thus communication of the user terminal 5 is appropriately restricted. For example, the user terminal 5 performs wireless communication by specifying a slice ID (for example, requests a session start or transmits user data). The base station 2 communicating with the user terminal 5 transmits information that associates the specified slice ID with the VLAN ID set in the base station 2. If a VLAN ID that matches the VLAN ID set in the site switch 3 is set in the information, the site switch 3 transmits the information. The information is received by the UPF server 112 via the central office switch 80.The slice ID may be, for example, an APN (Access Point Name) or a DNN (Data Network Name).

[0041] According to FIG. 1, for example,

[0042] That is, a slice 90-1 is provided for individual user A, and a virtual UPF 21-1 corresponds to the slice 90-1. A VLAN 91-1 is associated with the slice 90-1, and an ID of the VLAN 91-1 is set in the branch switches 3A1 and 3A2. A slice 90-2 is provided for individual user A, and a virtual UPF 21-2 corresponds to the slice 90-2. A VLAN 91-2 is associated with the slice 90-2, and an ID of the VLAN 91-2 is set in the branch switches 3A1 and 3A2. The IDs of the VLANs 91-1 and 91-2 are set in the base stations 2A1 and 2A2, respectively. The ID of the VLAN 91-1 is set in the virtual UPF 21-1, and the ID of the VLAN 91-2 is set in the virtual UPF 21-2. Therefore, any of the user terminals 5A1 to 5A4 can perform wireless communication via the slice 90-1 or 90-2 (that is, communication specifying the ID of the slice 90-1 or 90-2) from either the point 50A1 or A2.

[0043] Also, there is a slice 90-3 for individual user B, and the slice 90-3 corresponds to the virtual UPF 21-3. The slice 90-3 is associated with the VLAN 91-3, and the ID of the VLAN 91-3 is set in the site switch 3B1. Also, the ID of the VLAN 91-3 is set in the base station 2B1 and the virtual UPF 21-3. Therefore, the user terminal 5B1 can perform wireless communication from the site 50B1 via the slice 90-3. On the other hand, the user terminal 5A3 that has moved from the site 50A2 to the site 50B1 cannot perform communication via either the slice 90-1 or 90-2. This is because neither the VLAN ID associated with the slice 90-1 nor the VLAN ID associated with the slice 90-2 is set in the site switch 3B1 (and the base station 2B1 and the virtual UPF 21-3).

[0044] In this embodiment, the setting of the VLAN ID for the base switch 3 may be performed in response to a provision request from the user management terminal 12 or the 5G management terminal 11, as described later.

[0045] The present embodiment will now be described in more detail.

[0046] FIG. 2 shows an example of the configuration of a mobile network.

[0047] The mobile network includes an (R)AN (Radio) Access Network) 252, a branch switch 3, a central office switch 80, a UPF server 112, a DN 124, and a 5G core 111. The (R)AN 252 may include a base station 2 that wirelessly communicates with a user terminal 5 that is a user equipment (UE). The (R)AN 290 and the UPF server 112 are connected to a mobile backhaul 271 that is connected to the branch switch 3 and the central office switch 80. The UPF server 112 has a DN 124 that is configured with one or more switches 255. The U-plane 220 includes at least a part of the (R)AN 252, the branch switch 3, the UPF server 112, the central office switch 80, and the switch 255.

[0048] The 5G core 111 includes functions such as an access and mobility management function (AMF) 261, a session management function (SMF) 262, a policy control function (PCF) 263, and a unified data management (UDM) 264. The SMF 262 may exist for each organizational user, similar to the UPF 22. The 5G core 111 is connected to the UPF server 112 and the branch switch 3 via the central office switch 80. The C-plane 210 may include the 5G core 111, and may further include a part of the (R)AN 252, the branch switch 3, the central office switch 80, and the UPF server 112.

[0049] The M-plane 230 may include the slice management system 110 .

[0050] A wireless communication facility as an equipment package (for example, a facility as a resource collection of an edge-side network) may be provided in the base 50. The wireless communication facility may include an (R)AN 252 and a base switch 3. The wireless communication facility may include a UPF server 112 and a switch 255. Also, the center 60 may be provided with a DN 124 (switch 255) in addition to the center switch 80 and the UPF server 112.

[0051] FIG. 3 shows an example of the configuration of the slice management system 110. As shown in FIG.

[0052] The slice management system 110 includes an interface device 301, a storage device 302, and a processor 303 connected thereto.

[0053] The interface device 301 is communicatively connected to at least one of the user management terminal 12, the 5G management terminal 11, the 5G core 111, and the station switch 80.

[0054] The storage device 302 stores information and programs, such as an application management database 311, a template management database 312, a slice management database 313, a RAN resource allocation database 314, a base RAN resource database 315, a UPF resource allocation database 316, a station UPF resource database 317, and a VLAN management database 318.

[0055] The processor 303 executes the program to implement an association control unit 321 and a setting control unit 322 .

[0056] Hereinafter, as an example of the processing performed in this embodiment, an environment providing processing will be described, which is processing for providing an environment in which an application service can be provided to the user terminal 5. Note that, in this embodiment, it is assumed that the following processing is performed as pre-processing of the environment providing processing. -Define slice performance for each slice. - Allocate one or more slices to each organization user. Construction of a virtual UPF 21 for each slice (for each slice, a resource amount for achieving the performance of the slice may be allocated to the virtual UPF 21).

[0057] FIG. 4 shows the flow of the application provision process.

[0058] The slice management system 110 receives a provision request (S401). In the provision request, as shown in Fig. 5, a location 50, an application service, and an application service requirement are specified (in the example shown in Fig. 5, the location 50 is specified by a combination of an organization user ID and the location number of the organization user).

[0059] The setting control unit 322 converts the application service requirements specified in the provision request received in S401 into network requirements (S402).

[0060] The setting control unit 322 specifies one or more slices for which performance satisfying the network requirements obtained by the conversion in S402 is defined as slice candidates (S403).

[0061] The setting control unit 322 determines, for each slice candidate identified in S403, the amount of resources that satisfies the network requirements obtained by the conversion in S402 (S404).

[0062] The setting control unit 322 judges whether or not it is possible to provide an environment that satisfies the provision request received in S401 (S405). If the total resource amount including the resource amount determined in S404 for at least one slice candidate is equal to or less than the upper resource amount limit, the judgment result in S405 is true. On the other hand, if the total resource amount including the resource amount determined in S404 for all slice candidates exceeds the upper resource amount limit, the judgment result in S405 is false.

[0063] When the determination result of S405 is true (S405: Yes), the setting control unit 322 sets the VLAN ID associated with the selected slice 90 to the base switch 3 and the base station 2 of the base 50 specified in the provision request received in S401, and sets the VLAN ID to the virtual UPF 21 corresponding to the selected slice 90 (S406). Then, the setting control unit 322 notifies the terminal that is the sender of the provision request received in S401 of successful provision (S407). In this paragraph, the "selected slice 90" refers to one slice among the one or more slices 90 whose resource amount determined in S404 is equal to or less than the upper limit of the resource amount. In addition, the "VLAN ID associated with the selected slice 90" may be a VLAN ID that is previously associated in a pre-processing of this environment provision processing, or may be a VLAN ID that is dynamically associated in this environment provision processing.

[0064] If the determination result in S405 is false (S405: No), the setting control unit 322 notifies the terminal that is the sender of the provision request received in S401 of failure to provide the service (S408).

[0065] The environment providing process will be described in detail below.

[0066] Fig. 5 shows an example of the configuration of the application management database 311 and the template management database 312. S402 in Fig. 4 will be described in detail with reference to Fig. 5.

[0067] The application management database 311 indicates, for each application service, the application service name and a template ID.

[0068] The template management database 312 has a plurality of templates. The template is an example of conversion information that is information for converting an application service requirement into a network requirement. The template represents a relationship between an application requirement item and an application requirement value, a network requirement item, and a network requirement value. The application requirement item is one item of the application service requirement. The application requirement value is a value (or a range) corresponding to the application requirement item. The network requirement item is one item of the network requirement. The network requirement value is a value (or a range) corresponding to the network requirement item. By referring to the template, a network requirement corresponding to the application service requirement (in other words, a network requirement that satisfies the application service requirement) can be obtained. The conversion information, of which the template is an example, may be other types of information such as a machine learning model instead of the template.

[0069] In S402 in FIG. 4, for example, the following process is performed.

[0070] As described above, the provision request specifies the location 50, the application service, and the application service requirements. The setting control unit 322 identifies a template ID corresponding to the specified application service from the application management database 311. The setting control unit 322 identifies a template corresponding to the identified template ID from the application management database 311. The setting control unit 322 uses the identified template to convert the specified application service requirements into network requirements.

[0071] Fig. 6 shows an example of the configuration of the VLAN management database 318 and the slice management database 313. S403 in Fig. 4 will be described in detail with reference to Fig. 6.

[0072] The VLAN management database 318 indicates the following for each VLAN 91: ·VLAN ID (the ID of the relevant VLAN91). - Organization user ID (ID of the organization user to whom the VLAN 91 is provided). Slice ID (the ID of the slice 90 to which the VLAN 91 is associated).

[0073] The slice management database 313 indicates, for each slice 90, the following: -Slice ID (ID of the slice 90 in question). Virtual UPF ID (ID of the virtual UPF 21 corresponding to the slice 90). -VLAN ID (the ID of the VLAN 91 associated with the slice 90). · Organization user ID (ID of the organization user to which the slice 90 is assigned). Base number (identification number of the base 50 in which the VLAN ID associated with the slice 90 is set). Bandwidth (bandwidth allocated to the slice 90). Computational resources (the amount of computational resources allocated to the slice 90). Number of UEs (the number of user terminals 5 that can be connected to the slice 90). Performance parameters (one or more parameters that indicate the performance defined for the slice 90). Parameters included in the performance parameters include, for example, delay, packet loss rate, and jitter.

[0074] In this embodiment, an associable VLAN ID is prepared in advance. In S403 of Fig. 4, the setting control unit 322 identifies a slice candidate in which a performance parameter that satisfies the network requirement (for example, at least one of delay, packet loss rate, and jitter) obtained in S402 is defined from the slice management database 313. Here, it is assumed that a slice candidate with slice ID "2" is identified. In S403, the setting control unit 322 identifies a VLAN ID that is not assigned to any slice 90 from the VLAN management database 318, and provisionally assigns the organizational user ID "A" specified in the provision request and the identified slice ID "2" to the identified VLAN ID (provisional update of the VLAN management database). In addition, the setting control unit 322 provisionally assigns the organizational user ID "A" and base numbers "1, 2" specified in the provision request to the identified slice candidate (to the record with slice ID "2"), and the association control unit 321 provisionally associates the VLAN ID "A" identified from the VLAN management database 313 with the slice candidate (provisional update of the slice management database 313).

[0075] Fig. 7 shows an example of the configuration of the site RAN resource database 315 and the RAN resource allocation database 314. Fig. 8 shows an example of the configuration of the station UPF resource database 317 and the UPF resource allocation database 316. S404 and S405 in Fig. 4 will be described in detail with reference to Figs. 7 and 8.

[0076] The site RAN resource database 315 shown in FIG. Organization user ID (ID of the organization user who owns the relevant base 50). -Location number (identification number of the relevant location 50). · Maximum bandwidth (maximum available bandwidth). · Upper limit of UE number (upper limit of the number of user terminals 5 that can be connected at the same time).

[0077] The band and the number of UEs are examples of the amount of RAN resources, and the upper limit band and the upper limit number of UEs are examples of the upper limit of the amount of RAN resources. "RAN resources" are resources in base 50 that can be allocated to slice 90. "Amount of RAN resources" is the amount of RAN resources, and the unit of the amount depends on the type of RAN resources.

[0078] The RAN resource allocation database 314 indicates, for each site 50, the following: Organization user ID (ID of the organization user who owns the relevant base 50). -Location number (identification number of the relevant location 50). Slice ID (ID of slice 90 that can be connected (wirelessly communicated) with the site 50). Allocated bandwidth (bandwidth allocated from the relevant site 50 to the relevant slice 90). Number of assigned UEs (the number of user terminals 5 that can be connected to the slice at the same time at the site 50).

[0079] The station UPF resource database 317 shown in FIG. -Station ID (ID of the station 60). Upper limit bandwidth (the upper limit of the bandwidth that can be allocated in the station 60). Upper limit of computational resources (upper limit of computational resources of the UPF server 112 in the station 60). Upper limit of UE number (the upper limit of the total upper limit of UE number of all the bases 50 communicating with the UPF server 112 in the station 60).

[0080] The bandwidth, the amount of computational resources, and the number of UEs are examples of the amount of UPF resources, and the upper limit bandwidth, the upper limit amount of computational resources, and the upper limit number of UEs are examples of the upper limit of the amount of UPF resources. "UPF resources" are resources related to the UPF server 112 in the station 60 and can be allocated to slice 90. "UPF resource amount" is the amount of UPF resources, and the unit of the amount depends on the type of UPF resource.

[0081] The UPF resource allocation database 316 represents, for each slice 90: Station ID (ID of the station 60 having the 5G core 111 in which the slice 90 is configured). -Slice ID (ID of the slice 90 in question). Virtual UPF ID (ID of the virtual UPF 21 corresponding to the slice 90). Organization user ID (the ID of the organization user corresponding to the slice 90). Allocated bandwidth (bandwidth allocated to the slice 90). Allocated computational resource amount (amount of computational resources allocated to the slice 90). Number of assigned UEs (number of UEs assigned to the slice 90).

[0082] For slice ID "2", the total allocated bandwidth shown in FIG. 7 matches the allocated bandwidth shown in FIG. 8, and the total allocated UE number shown in FIG. 7 matches the allocated UE number shown in FIG.

[0083] An example of S404 and S405 in FIG. 4 is as follows.

[0084] The setting control unit 322 judges whether or not there is a slice that satisfies the requirements specified in the provision request among the multiple slices 90. If the result of the judgment is true, the slice that satisfies the requirements is selected, for example, in the following S406. As a result, the slice that satisfies the requirements specified in the provision request is the slice with which the VLAN ID is associated for the organizational user specified in the provision request, and is the slice used to provide the application service specified in the provision request.

[0085] In the provision request, application service requirements are specified. The slice candidates identified in S403 are slice candidates that satisfy the network requirements obtained by converting the application service requirements (conversion in S402). As a result, by specifying requirements for requirement items according to the type of application service in the provision request, it is possible to provide a slice that satisfies the application service requirements. Although the network requirements may be specified in the provision request instead of the application service requirements, it is more convenient to be able to specify the application service requirements.

[0086] In S404, the configuration control unit 322 determines the amount of RAN resources to satisfy the network requirements obtained by the conversion in S402 for the slice candidate identified as satisfying the network requirements. The configuration control unit 322 provisionally allocates the amount of RAN resources to the slice candidate for the base 50 specified in the provision request (provisional update of the RAN resource allocation database 314). In S405, the configuration control unit 322 determines whether or not the total amount of RAN resources allocated in the base 50 (the sum of the allocated bandwidth and the number of allocated UEs in the RAN resource allocation database 314) exceeds the upper limit of the amount of RAN resources (upper limit bandwidth and upper limit number of UEs) of the base 50. If the determination result is false for the slice candidate, the determination result in S405 becomes false. This makes it possible to appropriately restrict communication of the user terminal 5 within the range of the upper limit of the amount of RAN resources of the base 50.

[0087] In addition, in S404, the setting control unit 322 determines the amount of UPF resources to satisfy the network requirements for the slice candidate identified as satisfying the network requirements obtained by the conversion in S402. The setting control unit 322 provisionally allocates the amount of UPF resources for the virtual UPF 21 corresponding to the slice candidate (provisionally updating the UPF resource allocation database 316). In S405, the setting control unit 322 determines whether the total amount of UPF resources allocated to the station 60 having the UPF server 112 (the sum of the allocated bandwidth, the allocated calculation resource amount, and the allocated UE number in the UPF resource allocation database 316) exceeds the UPF resource amount upper limit (upper limit bandwidth, upper limit calculation resource amount, and upper limit UE number) of the station 60. If the determination result is false for the slice candidate, the determination result in S405 becomes false. This makes it possible to appropriately restrict communication of the user terminal 5 within the range of the upper limit of the UPF resource amount of the station 60.

[0088] Furthermore, in S405, the configuration control unit 322 judges whether or not the maximum value of the allocated RAN resource amount of all bases 50 to which the slice candidate is provisionally allocated exceeds the UPF resource amount allocated to the virtual UPF 21 corresponding to the slice candidate. If the judgment result is false for the slice candidate, the judgment result of S405 becomes false. This makes it possible to appropriately restrict communication of the user terminal 5 while maintaining an appropriate relationship between the UPF resource amount allocated to the virtual UPF 21 and the RAN resource amount allocated to the slice corresponding to the virtual UPF 21 at each base.

[0089] FIG. 9 shows an example of a case where the allocated bandwidth for one location 50A2 for slice 2 (slice 90 with slice ID "2") exceeds the bandwidth upper limit. FIG. 10 shows an example of a case where the allocated bandwidth for each of all locations for slice 2 is equal to or less than the bandwidth upper limit. In FIG. 9 and FIG. 10, for location 50, the number in parentheses indicates the bandwidth upper limit, and the number above the number in parentheses indicates the allocated bandwidth (the allocated bandwidth when the determined bandwidth is hypothetically added). Locations 50A1 and 50A2 are the locations specified in the provision request.

[0090] 9, the allocated bandwidth of "50M" for the point 50A2 exceeds the upper bandwidth limit of "10M" for the point 50A2. In this case, the determination result of S405 is false, and in S408, a failure of the provision is notified to the source terminal of the provision request.

[0091] On the other hand, according to the example shown in FIG. 10, the allocated bandwidth is equal to or less than the bandwidth upper limit in both the bases 50A1 and 50A2. Moreover, the maximum allocated bandwidth "50M" of the bases 50A1 and 50A2 is equal to or less than the allocated bandwidth "50M" of the virtual UPF 21-2 corresponding to slice 2. In this case, the determination result of S405 is true, and in S406, the provisional allocation (update) is confirmed, and the VLAN ID is set, and in S407, the source terminal of the provision request is notified of the successful provision. Note that if the allocated bandwidth of the base 50A1 is "60M", the allocated bandwidth "60M" is equal to or less than the bandwidth upper limit "100M" of the base 50A1, but exceeds the allocated bandwidth "50M" of the virtual UPF 21-2. Therefore, for slice 2, the relationship between the allocated bandwidth of the virtual UPF 21-2 and the allocated bandwidth of the base 50A1 is not appropriate, and therefore the determination result of S405 is false.

[0092] In this embodiment, the association of the VLAN 91 with the slice 90 may be performed in advance by the association control unit 321 in response to an operation from an administrator, or may be performed dynamically in the environment providing process (the process shown in FIG. 4). That is, any of the following may be adopted. For each VLAN 91, an organization user ID and a slice ID may be recorded in advance in the VLAN management database 318, and for each slice 90, a virtual UPF ID, a VLAN ID, an organization user ID, and a base number may be recorded in advance in the slice management database 313. According to these databases 313 and 318, a corresponding VLAN ID may be recorded in each base switch 3, each base station 2, and each virtual UPF 21. Then, in the environment provision process (the process shown in FIG. 4), the VLAN ID associated with the selected slice candidate may be enabled for the base switch 3, the base station 2, and the virtual UPF 21 in which the VLAN ID is recorded. With this method, it is possible to design in advance which VLAN is set in which base switch, and it is possible to appropriately restrict communication of the user terminal 5 within the scope of the design in advance. 6, before the environment provision process is performed, the VLAN management database 318 lists available VLAN IDs, and the VLAN IDs in the list may be dynamically associated with slices in the environment provision process. This allows VLAN association to be performed appropriately to restrict communication of the user terminal 5 without the above-mentioned advance design.

[0093] FIG. 11 shows an example of an administration UI 1100.

[0094] The slice management system 110 displays a management UI (User Interface) 1100 on the 5G management terminal 11 (or the user management terminal 12) based on at least a part of the databases 311 to 318. The management UI 1100 is typically a GUI (Graphical User Interface).

[0095] For example, an application service being provided 1113 is displayed. The application service being provided 1113 indicates information such as the application service name, the slice ID of an available slice, the ID of the user of the organization to which the service is provided, the base number of the base to which the service is provided, and the specified application service requirements for each application service being provided.

[0096] The administration UI 1100 has an application service selection tool 1111 (for example, one or more GUI components). Via the application service selection tool 1111, it is possible to input an organization user ID, a base number, and an application service name to be specified in a provision request.

[0097] The administration UI 1100 also has an input tool 1112 (e.g., one or more GUI components) for application service requirements. Through the input tool 1112, it is possible to input application service requirements (requirement values ​​for each service requirement item corresponding to a selected application service) specified in a provision request.

[0098] Although one embodiment has been described above, this is merely an example for explaining the present invention, and the scope of the present invention is not limited to only these embodiments. The present invention can be implemented in various other forms. For example, the following description is possible as a supplement to the description of the above embodiment and a description of a modified example.

[0099] At least some of the functions in the slice management system 110 may be operated by a Mobile Network Operator (MNO) or an entity such as a Mobile Virtual Network Operator (MVNO).

[0100] A slice may also be a logical network (e.g., a logical network capable of providing specific network capabilities and specific network characteristics) obtained by logically dividing a network (e.g., EtoE logical division). A slice may or may not include functions such as UPF 21 or 22 and SMF 262. For example, a slice may be composed of one or more slice instances. A slice instance may refer to a set of one or more network functions and one or more resources (e.g., computing resources, storage resources, networking resources) that form a deployed slice. [Explanation of symbols]

[0101] 110: Slice management system

Claims

1. an association control unit that associates a target virtual network with a target slice of a target organization user; a setting control unit that sets a virtual network ID of the target virtual network to a base switch in each of the one or more target bases of the target organization user; Equipped with The target organization user is one organization user among a plurality of organization users, The one or more target locations are all or a part of one or more locations of the target organizational user, For each of the plurality of organizational users, a base station and a base switch are provided at each base of the organizational user; At each site, the site switch is a terminal device connected to the mobile backhaul and the base station at that site, The target slice is one slice among one or more slices prepared for the target organizational user; The target virtual network is a virtual network that is not assigned to any slice, A user data processing server and the mobile backhaul are connected to a central office switch, which is a terminal device to which a core network common to the plurality of organizational users is connected; the user data processing server has a user data processing unit for each slice, the user data processing unit being a virtual router that relays user data passing between the slice and a data network; For each base, a base switch in the base transmits and receives user data associated with a virtual network ID set in the base switch, and does not transmit and receive user data not associated with a virtual network ID set in the base switch. Slice management system.

2. For each base station, when a virtual network ID for a slice is set in the base station and user data via the slice is received from a user terminal, the base station in the base station transmits the user data associated with the virtual network ID, For each user data processing unit, When a virtual network ID associated with a slice corresponding to the user data processing unit is set in the user data processing unit and user data is received via the slice, if a virtual network ID matching the set virtual network ID is associated with the received user data, the user data is transferred, but if a virtual network ID matching the set virtual network ID is not associated with the received user data, the user data is not transferred, and the user data processing unit is configured such that a virtual network ID associated with a slice corresponding to the user data processing unit is set in the user data processing unit, and when transmitting user data via the slice to a user terminal that is a destination of the user data, the user data associated with the virtual network ID is transmitted; The setting control unit sets a virtual network ID of the target virtual network for the target slice in a base station in each of the one or more target bases and in a user data processing unit corresponding to the target slice. The slice management system of claim 1 .

3. The setting control unit determines whether or not there is a slice that satisfies the requirements among the plurality of slices in response to a provision request that specifies the one or more target bases and requirements; If the result of the determination is true, the slice that satisfies the requirement is the target slice. The slice management system of claim 1 .

4. the provision request specifies an application service to be received at each of the one or more target locations; the requirements specified in the provision request are application service requirements related to the specified application service; For each application service, conversion information is provided to convert application service requirements into network requirements. A performance of each of the plurality of slices is defined; and The setting control unit is Identifying conversion information corresponding to the specified application service from among conversion information for each application service; translating the specified application service requirements into network requirements based on the identified translation information; The determination of whether or not there is a slice that satisfies the requirement includes determining whether or not there is a slice that has a defined performance that satisfies the network requirement obtained by the conversion. The slice management system according to claim 3 .

5. Determining whether there is a slice that satisfies the requirements includes determining: determining whether or not a total resource amount allocated to each of the one or more target locations exceeds an upper limit of a resource amount of the target location when a resource amount for satisfying the network requirement obtained by the conversion is allocated to each of the one or more target locations; The slice management system according to claim 4 .

6. Determining whether there is a slice that satisfies the requirements includes determining: whether or not a total resource amount allocated in the user data processing server exceeds a resource amount upper limit of the user data processing server when a resource amount for satisfying the network requirements obtained by the conversion is allocated to the user data processing unit corresponding to the slice in which the performance for satisfying the network requirements obtained by the conversion is defined; The slice management system according to claim 4 .

7. Determining whether there is a slice that satisfies the requirements includes determining: When a resource amount for satisfying the network requirement obtained by the conversion is allocated to each of the one or more target locations, a maximum resource amount among the one or more target locations exceeds a resource amount allocated to a user data processing unit corresponding to a slice that satisfies the network requirement obtained by the conversion, or The slice management system according to claim 4 .

8. The core network is a 5G core; The user data processing server is a UPF (User Plane Function) server, The user data processing unit is a virtual UPF. The slice management system of claim 1 .

9. The present invention has the following (A) and (B): (A) a computer associates a target virtual network with a target slice of a target organization user; (B) the computer sets a virtual network ID of the target virtual network to a base switch in each of the one or more target bases of the target organization user. The target organization user is one organization user among a plurality of organization users, The one or more target locations are all or a part of one or more locations of the target organizational user, For each of the plurality of organizational users, a base station and a base switch are provided at each base of the organizational user; At each site, the site switch is a terminal device connected to the mobile backhaul and the base station at that site, The target slice is one slice among one or more slices prepared for the target organizational user; The target virtual network is a virtual network that is not assigned to any slice, A user data processing server and the mobile backhaul are connected to a central office switch, which is a terminal device to which a core network common to the plurality of organizational users is connected; the user data processing server has a user data processing unit for each slice, the user data processing unit being a virtual router that relays user data passing between the slice and a data network; For each base, a base switch in the base transmits and receives user data associated with a virtual network ID set in the base switch, and does not transmit and receive user data not associated with a virtual network ID set in the base switch. Slice management method.

10. Associating a target virtual network with a target slice of a target organization user; For each of one or more target bases of the target organization user, a virtual network ID of the target virtual network is set for a base switch in the target base. Have the computer do this, The target organization user is one organization user among a plurality of organization users, The one or more target locations are all or a part of one or more locations of the target organizational user, For each of the plurality of organizational users, a base station and a base switch are provided at each base of the organizational user; At each site, the site switch is a terminal device connected to the mobile backhaul and the base station at that site, The target slice is one slice among one or more slices prepared for the target organizational user; The target virtual network is a virtual network that is not assigned to any slice, A user data processing server and the mobile backhaul are connected to a central office switch, which is a terminal device to which a core network common to the plurality of organizational users is connected; the user data processing server has a user data processing unit for each slice, the user data processing unit being a virtual router that relays user data passing between the slice and a data network; For each base, a base switch in the base transmits and receives user data associated with a virtual network ID set in the base switch, and does not transmit and receive user data not associated with a virtual network ID set in the base switch. Computer program.

Images