System and method for supporting service operation of wireless communication service

Abstract

To solve a problem of service operation of a wireless communication service.SOLUTION: A system for supporting operation of a wireless communication service includes one or more operation support units prepared for one or more service operations of wireless communication services. There are a plurality of network slices that have at least one function in common in a core network. The plurality of network slices includes a user slice for each user and a service operation slice common to the plurality of users. The operation support unit corresponding to the service operation sends, to a wireless communication terminal that has performed the connection sequence using connection information including identification information of the slice for the service operation, target information which is information containing at least one of parameters set in the service operation and parameters necessary for executing the service operation via the slice for the service operation.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 such a form, there is no need to deploy a 5G core, which is generally expensive for authenticating terminals and terminating mobile communications, for each user. In such wireless communication service, the 5G core is deployed, for example, on an edge data center or a cloud. Also, an "organizational user" is an organization as a user. A user may be an individual or an organization, but in this specification, an organization as a user is referred to as an "organizational user" for convenience. An "organization" may be a collection of one or more individuals, and may be, for example, a company or a department or business establishment within a company.

[0004] In such wireless communication services, in order to ensure network independence of organizational users, it is conceivable to prepare a network slice for each organizational user.

[0005] For example, Patent Document 1 discloses the following technology: In addition to a network slice for general services, a network slice for specific services is provided in a mobile network. In response to a switching instruction from a service server for the mobile network, the network slice applied to a user terminal is switched from the network slice for general services to the network slice for the specific service. [Prior art documents] [Patent documents]

[0006] [Patent Document 1] Patent Publication No. 2021-22889 Summary of the Invention [Problem to be solved by the invention]

[0007] Meanwhile, service operation (e.g., maintenance) is necessary to provide and maintain wireless communication services. Service operation includes terminal initial settings (initial settings for wireless communication terminals) and terminal diagnosis (diagnosis to identify the cause of a wireless communication terminal failure (e.g., unstable behavior)).

[0008] For example, there is the following problem with the terminal initial settings. That is, a wireless communication service provider (a business operator providing a local 5G wireless communication service) may set a configuration file in which parameters including an identifier of the network slice of the organizational user (e.g., an APN (Access Point Name) or a DNN (Data Network Name)) are described for each wireless communication terminal provided to the organizational user, and ship the terminal. However, if there are a large number of organizational users or if there are many terminals provided to the organizational user (e.g., employees), the initial setting work becomes complicated. In addition, there is a possibility that a wireless communication terminal with incorrect initial settings will be shipped. It is possible to have an administrator of the organizational user perform the initial settings, but in this case, if the administrator has little experience in wireless communication operations, there is a possibility that the initial settings will be incorrect.

[0009] As an example of the problem of terminal diagnosis, there is the following issue. That is, when a failure occurs in a wireless communication terminal, an operator needs to go to the site where the wireless communication terminal is located in order to investigate the cause of the failure (e.g., infection by a computer virus) at the site. In addition, until the cause of the failure is investigated in the local environment, there is a possibility that other wireless communication terminals connected to the network slice to which the wireless communication terminal in which the failure occurred is connected may be affected. As one method of avoiding this problem, it is considered that an organization user delivers the wireless communication terminal in which the failure occurred to a specified facility (e.g., a distribution center) and an operator investigates the cause of the failure at the facility. However, since such a facility cannot usually reproduce the same environment as the site, if the cause of the failure is site-dependent (e.g., radio wave interference), it is not possible to investigate the cause of the failure.

[0010] The above terminal initial settings and terminal diagnosis are an example of the service operation of a wireless communication service, but the problem may also arise with respect to the operation of at least one other service.

[0011] According to Patent Document 1, all network slices are for users, and a network slice for a specific service according to a requested service quality level from a user terminal is applied to the user terminal. Patent Document 1 does not disclose or suggest any service operation issues or means for solving the issues.

[0012] The above issues may also apply to 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 system for supporting the operation of a wireless communication service is constructed. The system includes one or more operation support units that provide identification information for one or more service operations of the wireless communication service. There are a plurality of network slices having at least one common function in a core network. The plurality of network slices include one or more user-oriented slices and one or more service operation-oriented slices. For each of a plurality of users, there are one or more user-oriented slices, and the user-oriented slice is a network slice prepared for the user.

[0014] For each of one or more service operations, there are one or more slices for the service operation, and the slice for the service operation is a network slice prepared for the service operation and common to multiple users. An operation support unit corresponding to the service operation transmits target information, which is information including at least one of parameters set in the service operation and parameters necessary for executing the service operation, to a target terminal (a wireless communication terminal that has performed a connection sequence using connection information including slice identification information of the slice for the service operation) via the network slice for the service operation. Effect of the Invention

[0015] According to the present invention, it is possible to solve the problems in the operation of wireless communication services. [Brief description of the drawings]

[0016] [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 shows an example of the configuration of a setting support server. [Figure 4] 2 shows an example of the configuration of a diagnostic support server. [Diagram 5] 1 shows an example of the configuration of a management server. [Figure 6] 13 shows an example of a flow of assistance for initial terminal settings. [Figure 7] An example of a flow of terminal diagnosis support is shown. [Figure 8] An example of the management UI is shown below. [Figure 9] An example of the management UI is shown below. [Figure 10] 13 illustrates another example of the configuration of the entire system according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0017] 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, e.g., 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)).

[0018] 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.

[0019] 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).

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

[0021] 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)).

[0022] In the following description, information that provides an output for an input may be described using expressions such as "xxxDB" ("DB" is an abbreviation for 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, "xxxDB" may be referred to as "xxx information." In the following description, the configuration of each DB is an example, and one DB may be divided into two or more DBs, or all or part of two or more DBs may be one DB.

[0023] 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.

[0024] 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.

[0025] 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.

[0026] Fig. 1 shows an example of the overall configuration of a system according to an embodiment of the present invention. In the drawings, "Un" (n is a natural number) means corporate user n, and "Un-AAA" means AAA corresponding to corporate user n. "AAA" includes, for example, slice (network slice), DN (data network), and UPF (User Plane Function).

[0027] There are multiple network slices that have at least one function in common in the 5G core 111 (an example of a core network). The multiple network slices are one or more user-facing slices S50 and one or more service operation slices S51.

[0028] There is a user slice 51 for each corporate user. The user slice 51 is a network slice for corporate users. According to the example shown in FIG. 1, there is a slice U1-slice 51A for corporate user 1 and a slice U2-slice 51B for corporate user 2.

[0029] For each of one or more service operations, there are one or more slices 50 for service operation, and the slices 50 for service operation are slices prepared for the service operation. In other words, for one service operation, there may be one or more slices 50 for service operation. In this embodiment, examples of "service operation" include terminal initial setting and terminal diagnosis. Therefore, the slices 50 for service operation include a setting slice 50A that is a slice for terminal initial setting, and a diagnosis slice 50B that is a slice for terminal diagnosis.

[0030] There are also a user terminal 5, an operation support system 110, a UPF server 112, a DN (data network) 124, a user management system 12, and a 5G management system 11.

[0031] The user terminal 5 is a wireless communication terminal. The user terminal 5 is shipped from a distribution center (an example of a shipping source) to a corporate user, and provided to an employee or the like of the corporate user.

[0032] The operation support system 110 is a system that supports the operation of a wireless communication service. The operation support system 110 includes a management server 121, a setting support server 122, and a diagnostic support server 123. The management server 121 is an example of a management unit. The setting support server 122 and the diagnostic support server 123 are each an operation support server (an example of an operation support unit) prepared for service operation. Specifically, for example, the setting support server 122 is an example of a setting support unit as an operation support unit corresponding to terminal initial setting. The diagnostic support server 123 is an example of a diagnostic support unit as an operation support unit corresponding to terminal diagnosis. In this embodiment, the operation support system 110 is a physical computer system (for example, a system having an interface device, a storage device, and a processor connected to them) composed of one or more physical computers, but may be a logical computer system based on a physical computer system (for example, a system realized on a cloud platform). That is, each server in the operation support system 110 may be a physical server or may be realized by a logical server (for example, a VM (Virtual Machine) or a container).

[0033] The UPF server 112 is an example of a logical or physical UPF set. The logical UPF set may be provided on a physical server, and the physical UPF set may be a physical server. In this embodiment, the UPF server 112 is a physical UPF set. The UPF server 112 includes a UPF 21 prepared for each service operation and a UPF 22 prepared for each user-oriented slice 51. According to the example shown in FIG. 1, the UPF 21 includes, for example, a setting UPF 21A corresponding to terminal initial settings and a diagnostic UPF 21B corresponding to terminal diagnosis. In addition, the UPF 22 includes, for example, a U1-UPF 22A corresponding to a corporate user 1 and a U2-UPF 22B corresponding to a corporate user 2.

[0034] The DN 124 is connected to the UPF 22 and an external network (e.g., the Internet). The user terminal 5 connected to the user slice 51 can communicate with devices connected to the external network via the user slice 51, the UPF 22, and the DN 124. The DN 124 includes, for example, U1-DN124A connected to the U1-UPF 22A and corresponding to the corporate user 1, and U2-DN124B connected to the U2-UPF 22B and corresponding to the corporate user 2.

[0035] The user management system 12 is connected to the DN 124 corresponding to the corporate user. When a failure occurs in the user terminal 5, the user management system 12 can detect the failure through the user-oriented slice 51, the UPF 22, and the DN 124, and notify the management server 121 of the detected failure. As the user management system 12, for example, there is a user management system 12A connected to U1-DN 124A and corresponding to corporate user 1, and a user management system 12B connected to U2-DN 124B and corresponding to corporate user 2.

[0036] The 5G management system 11 is an information processing terminal serving as an input / output console for the management server 121, and is typically operated by a 5G administrator.

[0037] Take one service operation as an example. In this embodiment, a user terminal (hereinafter, in this paragraph, "target user terminal") 5 that is the target of the service operation performs a connection sequence using connection information including a slice ID (e.g., APN or DNN) of the slice 50 for the service operation, thereby connecting the target user terminal 5 to the slice 50 for the service operation. An operation support unit corresponding to the service operation transmits target information (information including at least one of parameters set in the service operation and parameters required for executing the service operation) to the target user terminal 5 connected to the slice 50 for the service operation via the slice 50 for the service operation.

[0038] In this manner, in this embodiment, service operation to the user terminal 5 is performed without passing through the user-oriented slice 51 prepared for each corporate user. This supports service operation.

[0039] At least one slice 50 for service operation may be restricted so as to be unable to communicate with any server other than a specific server (e.g., an operation support server corresponding to the slice 50) (e.g., so as to be unable to communicate between user terminals 5). For example, by setting a prohibition on return transfer to a data input port for a switch (network communication device) belonging to a network slice for service operation, it is possible to suppress communication between user terminals 5 even if multiple user terminals 5 are connected to the slice 50 for service operation. In addition, by limiting the servers logically or physically connected to the slice 50 for service operation to the operation support server (and the 5G core 111) corresponding to the service operation, it is possible to suppress a user terminal 5 connected to the slice 50 for service operation from connecting to an unspecified server. In this way, the reliability or stability of service operation is improved.

[0040] There is a service operation called terminal initial setting. The terminal initial setting is, for example, as follows. An example of a shipping destination is a corporate user 1. From the distribution center, connection information (for example, information including a slice ID of the setting slice 50A) for connecting to the setting slice 50A is set in the user terminal 5-1 (or a SIM card (an example of a portable storage medium for wireless communication mounted on the user terminal 5)), and the user terminal 5-1 (and / or the SIM card) is shipped. The connection information is the same regardless of the shipping destination. The SIM card in which the connection information is stored is connected to the user terminal 5-1. The initial setting for adjusting the wireless communication of the user terminal 5 for the shipping destination corporate user 1 is performed via the setting slice 50A. Specifically, for example, by inserting the SIM card into the user terminal 5, the user terminal 5 performs a connection sequence using the connection information set in the user terminal 5, and connects to the setting slice 50A. The connection information may include access information for accessing the setting support server 122. The user terminal 5 accesses the setting support server 122 using the access information. The setting support server 122 identifies the corporate user 1 using the terminal ID of the user terminal 5 as a key, identifies an initial setting configuration file corresponding to the corporate user 1, and installs the initial setting configuration file in the user terminal 5. The initial setting configuration file has connection information including the slice ID of the U1-slice 51A. The user terminal 5 connects to the U1-slice 51A using the initial setting configuration file. In this manner, the terminal initial setting is supported. Specifically, the user terminal 5 (and / or SIM card) can be shipped without setting for each corporate user, thereby reducing the workload of setting costs. In addition, even if a person with little experience in wireless communication has little experience in wireless communication, the optimal setting for the slice for the corporate user 1 can be easily performed.

[0041] There is also a service operation called terminal diagnosis. The terminal diagnosis is, for example, as follows. Take the corporate user 2 as an example. When a failure occurs in the user terminal 5-2 (for example, when the behavior becomes unstable), the failure is detected by the user management system 12B through the U2-DN 124B, and the failure is notified to the management server 121 by the user management system 12B. Alternatively, the failure is detected by the administrator of the corporate user 2 through the U2-DN 124B and notified to the 5G administrator, and the 5G administrator notifies the management server 121 through the 5G management system 11. When the failure is notified, the management server 121 changes the connection destination slice ID of the user terminal 5-2 to the slice ID of the diagnosis slice 50B for the U2-UPF 22B via (or not via) the 5G core 111. As a result, the user terminal 5-2 is disconnected from the U2-slice 51B and connected to the diagnosis slice 50B. Then, the diagnostic support server 123 performs a remote diagnosis on the user terminal 5-2 via the diagnostic UPF 21B and the diagnostic slice 50B. This makes it possible to remotely diagnose the user terminal 5-2 while preventing the user terminal 5-2 in which a fault has occurred from affecting other user terminals 5, thereby making it possible to, for example, investigate the cause of a terminal whose behavior is unstable in the local environment.

[0042] The number of user terminals 5 simultaneously connected to the diagnostic slice 50 may be limited to one or both of the following: "Connected at the same time" does not mean connected at the same time, but connected during the same period (at least a portion of the connection time overlaps). In order to reduce the impact on other user terminals 5, the number of terminals that are permitted to be simultaneously connected may be a predetermined number (for example, 1) or less. If the behavior of N (N is a natural number greater than or equal to 2) user terminals 5 simultaneously becomes unstable, the number of terminals allowed to be connected simultaneously may be N, the number of user terminals 5 that simultaneously experienced failures, in order to enable diagnosis in an environment identical to the on-site environment.

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

[0044] The mobile network includes an (R)AN (Radio) Access Network) 252, a switch 253M, a UPF server 112, a switch 253D, a DN 124, and a 5G core 111. The (R)AN 290 may include a base station that wirelessly communicates with a user terminal 5, which is a user equipment (UE). If the (R)AN 290 does not include a base station, packets transmitted and received between the user terminal 5 and the base station (gNB) may pass through the (R)AN 290. The (R)AN 290 and the UPF server 112 are connected to a MBH (Mobile Back Haul) that includes one or more switches 253M. The UPF server 112 includes a DN 124 that includes one or more switches 253D. As the DN 124, for example, as described above, there is a DN 124 for each user-oriented slice 51. The U-plane 220 includes at least a part of the (R)AN 252, the switch 253M, the UPF server 112, and the switch 253D.

[0045] 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 exists for each corporate user (or for each user slice 51) like the UPF 22. Also, the SMF 262 exists for each service operation like the UPF 21. In this embodiment, one user slice 51 exists for each corporate user, but multiple user slices (for example, user slices prepared for each element such as QoS or use) may exist for each corporate user. The 5G core 111 is connected to the UPF server 112 and the switch 253M via one or more switches 253C. The C-plane 210 may include the 5G core 111 and the switch 253C, and may further include a part of the (R)AN 252, the switch 253M, the UPF server 112, and the switch 253D.

[0046] The M plane 230 includes the management server 121 and the operation support server (the setting support server 122 and the diagnosis support server 123 in this embodiment) in the operation support system 110.

[0047] A wireless communication facility as an equipment package may be provided to a user site (e.g., a user site such as a factory). The wireless communication facility may include an (R)AN 252, a switch 253M, a UPF server 112, and a switch 253D. After the wireless communication facility is set up at the user site, terminal initial settings may be performed on the user terminal 5 at the user site.

[0048] FIG. 3 shows an example of the configuration of the setting support server 122. As shown in FIG.

[0049] The setting assistance server 122 includes a communication interface device 301, a storage device 302, and a setting assistance controller 303 (an example of a processor) connected thereto.

[0050] As illustrated in FIG. 2, the communication interface device 301 is communicatively connected to the UPF server 112 (configuration UPF 21A (see FIG. 1)) via the switch 253D.

[0051] The storage device 302 stores a terminal DB 311 and an initial setting DB 312. The terminal DB 311 indicates, for each user terminal 5, a terminal ID (the terminal ID of the user terminal 5) and a corporate user ID (the ID of the corporate user to which the user terminal 5 is to be shipped). The initial setting DB 312 indicates, for each user terminal 5, a terminal ID (the terminal ID of the user terminal 5) and an initial setting configuration file (a configuration file for initial setting provided to the user terminal 5 or a path to that file). According to the example shown in Fig. 3, the same initial setting configuration file is provided to the same corporate user.

[0052] The setting support controller 303 supports the initial terminal settings, as will be described in detail later.

[0053] FIG. 4 shows an example of the configuration of the diagnostic support server 123.

[0054] The diagnostic support server 123 includes a communication interface device 401, a storage device 402, and a diagnostic support controller 403 (an example of a processor) connected to these devices.

[0055] As illustrated in FIG. 2, the communication interface device 401 is communicatively connected to the UPF server 112 (the diagnostic UPF 21B (see FIG. 1)) via the switch 253D.

[0056] The storage device 402 stores a diagnosis DB 411 and a log DB 412. The diagnosis DB 411 indicates, for each user terminal 5, a terminal ID (the terminal ID of the user terminal 5) and a remote diagnosis file (an executable file for remote diagnosis to be executed by the user terminal 5 or a path to that file). The log DB 412 indicates, for each user terminal 5, a terminal ID (the terminal ID of the user terminal 5) and an analysis log (a log of remote diagnosis (and a log as a result of analyzing that log)).

[0057] The diagnosis support controller 403 supports terminal diagnosis, the details of which will be described later.

[0058] FIG. 5 shows an example of the configuration of the management server 121.

[0059] The management server 121 includes a communication interface device 501, a storage device 502, and a management controller 503 (an example of a processor) connected to these devices.

[0060] The communication interface device 401 is communicatively connected to the 5G core 111, as illustrated in FIG. 2.

[0061] The storage device 502 stores a terminal DB 511 and an operational slice DB 512. Of the terminal DB 511 and the operational slice DB 512, at least the operational slice DB 512 is an example of at least a part of management information.

[0062] The terminal DB 511 represents, for each user terminal 5, a terminal ID (the terminal ID of the user terminal 5), a corporate user ID (the ID of the corporate user to which the user terminal 5 is shipped), a terminal status (the status of the user terminal 5), and a slice ID (the slice ID of the slice to which the user terminal 5 is connected).

[0063] The operation slice DB 512 indicates, for each service operation slice, a slice ID (slice ID of the service operation slice), a slice status (status of the service operation slice), the number of connections (the number of user terminals 5 connected to the service operation slice), and a corporate user ID (the ID of the corporate user to which the service operation slice is assigned). Note that the operation slice DB 512 may further indicate, for each service operation slice, the number of allowed simultaneous connections (the number of user terminals allowed to be simultaneously connected to the service operation slice).

[0064] The management controller 503 manages the network slices and the user terminals 5 connected to the network slices, and transmits a connection destination slice switching instruction to the user terminals 5. Details will be described later.

[0065] The function of at least one of the above-mentioned setting assistance controller 303, diagnosis assistance controller 403, and management controller 503 as the controller may be realized by having a processor of the server 122, 123, or 121 read and execute a program stored in the storage device 302, 402, or 502. A part or all of the program may be stored in the storage device 302, 402, or 502 in advance, or may be read as necessary from a non-transitory storage device of another device connected via a network, or from a non-transitory recording medium connected to an I / F (not shown), and stored in the storage device 302, 402, or 502.

[0066] An example of the flow of service operation support will be described below for each of the terminal initial setting and terminal diagnosis employed in this embodiment as an example of service operation.

[0067] Fig. 6 shows an example of a flow of assistance for initial terminal settings. In the explanation of Fig. 6, it is assumed that the corporate user is corporate user 1. It is assumed that the correspondence between the terminal ID and the corporate user ID for the user terminal 5 shipped to the corporate user 1 is registered in the setting assistance server 122 and the management server 121. It is also assumed that the connection destination slice ID included in the connection information set for the shipped user terminal 5 (the SIM card inserted therein) is the slice ID of any of the setting slices 50A, and therefore, it is assumed that the slice ID of the setting slice 50A is registered as the slice ID for the user terminal 5 in the management server 121.

[0068] When the user terminal 5 is powered on, the user terminal 5 starts a connection sequence (for example, a standard connection sequence in 3GPP (3rd Generation Partnership Project)) using the configured connection information (connection information including the slice ID of the configured slice 50A) (S600). The user terminal 5 accesses the (R)AN 252 (S601). The (R)AN 252 transmits a session establishment request to the AMF 261 (S602). The AMF 261 transmits a session establishment request to the configuration SMF 262A (SFM 262 corresponding to the terminal initial setting) (S603). The configuration SMF 262A registers session information in the UDM 264 (S604). A response is returned from the UDM 264 to the configuration SMF 262A (S605A), and a response is returned from the configuration SMF 262A to the AMF 261 (S605B).

[0069] The configuration SMF 262A transmits a communication policy request to the PCF 263 (S606), and the PCF 263 returns a response to the configuration SMF 262A (S607).

[0070] The configuration SMF 262A notifies the configuration UPF 21A of the session information (S608), and the configuration UPF 21A returns a response to the configuration SMF 262A (S609). The configuration SMF 262A notifies the AMF 261 of the session information (S610), and the AMF 261 returns a response to the configuration SMF 262A (S611).

[0071] The AMF 261 notifies the (R)AN 252 of the session information (S612), and the (R)AN 252 notifies the user terminal 5 of the session information (S613). A response is returned from the user terminal 5 to the (R)AN 252 (S614), and the connection to the configured slice 50A is completed for the user terminal 5 (S615). A response is returned from the (R)AN 252 to the AMF 261 (S616). The AFM 261 notifies the configuring SMF 262A of the base station side session information (S617). The configuring SMF 262A notifies the configuring UPF 21A of the wireless information (S618). A response is returned from the configuring UPF 21A to the configuring SMF 262A (S619), and the configuring SMF 262A returns a response to the AFM 261 (S620). With the above, the connection sequence for connecting the user terminal 5 to the configured slice 50A is completed.

[0072] The connection information set in the user terminal 5 (SIM card) includes, for example, information necessary for accessing the configured UPF 21A. Based on the necessary information, the user terminal 5 notifies the configured UPF 21A of an initial connection via the configured slice 50A (S621).

[0073] Thereafter, the setting support server 122 is notified of the initial connection from the setting UPF 21A (S622). The setting support server 122 requests a terminal ID from the user terminal 5 via the setting UPF 21A (S623 and S624). In response to the request, the user terminal 5 notifies the setting support server 122 of the terminal ID via the setting UPF 21A (S625 and S626).

[0074] The setting support server 122 uses the notified terminal ID as a key to identify an initial setting configuration file (a configuration file that includes connection information having the slice ID of U1-slice 51A and is used to connect to the slice 51A for the user) from the initial setting DB 312. The identified initial setting configuration file is transmitted from the setting support server 122 to the user terminal 5 via the setting UPF 21A (S627 and S628). A response is returned from the user terminal 5 to the setting support server 122 via the setting UPF 21A (S629 and S630).

[0075] The user terminal 5 sets the initial setting configuration file therein and executes the file, thereby restarting and starting a connection sequence using the connection information included in the initial setting configuration file (S631). A session establishment request is sent from the user terminal 5 to U1-SMF 262U1 (SFM 262 corresponding to corporate user 1) via the (R)AN 252 and AMF 261 (S632, S633, and S634). Session information is registered from U1-SMF 262U1 to UDM 264 (S635). A response is returned from UDM 264 to U1-SMF 262U1 (S636), and a response is returned from U1-SMF 262U1 to AMF 261 (S637).

[0076] The U1-SMF 262U1 transmits a communication policy request to the PCF 263 (S638), and the PCF 263 returns a response to the U1-SMF 262U1 (S639).

[0077] The session information is notified from the U1-SMF 262U1 to the U1-UPF 22U1 (S640), and a response is returned from the U1-UPF 21U1 to the U1-SMF 262U1 (S641). The session information is notified from the U1-SMF 262U1 to the AMF 261 (S642), and a response is returned from the AMF 261 to the U1-SMF 262U1 (S643).

[0078] The AMF 261 notifies the user terminal 5 of the session information via the (R)AN 252 (S644 and S645). A response is returned from the user terminal 5 to the (R)AN 252 (S646), and the connection to the U1-slice 51A is completed for the user terminal 5 (S647). A response is returned from the (R)AN 252 to the AMF 261 (S648). The AFM 261 notifies the U1-SMF 262U1 of the base station side session information (S649). The U1-SMF 262U1 notifies the U1-UPF 21U1 of the radio information (S650). A response is returned from the U1-UPF 21U1 to the U1-SMF 262U1 (S651), and a response is returned from the U1-SMF 262U1 to the AFM 261 (S652). This completes the connection sequence for connecting the user terminal 5 to the U1-slice 51A.

[0079] The above is an example of the flow of supporting the terminal initial setting. Note that, in cases where the system scale is large (for example, many user terminals 5 are shipped), multiple setting slices 50A may be provided. The destination setting slice ID (slice ID of destination setting slice 50A) in the connection information set in the shipped user terminal 5 (or SIM card) may differ by organization (for example, by corporate user or by department). This distributes the load when the terminal initial setting is performed simultaneously for multiple user terminals 5, and is expected to reduce the time required for simultaneous terminal initial setting for multiple user terminals 5.

[0080] Fig. 7 shows an example of the flow of supporting terminal diagnosis. In the explanation of Fig. 7, it is assumed that the corporate user is corporate user 2. Also, in the explanation of Fig. 7, user terminal 5 is the user terminal in which a failure has occurred.

[0081] The management server 121 receives a notification of an abnormality in the user terminal 5 connected to the U2-slice 50B (S701). The source (input source) of the notification may be a person such as a 5G administrator, or a computer such as the user management system 12B. The received notification may include access information (information used to access the user terminal 5) such as the terminal ID of the user terminal 5.

[0082] The management server 121 determines the connection destination diagnosis slice 50B of the user terminal 5 (S702). The management server 121 transmits to the user terminal 5 a switching instruction associated with connection information (information used for connecting the connection destination diagnosis slice 50B) including the slice ID of the determined connection destination diagnosis slice 50B, via the U2-UPF 22U2 (and the U2-slice 50B) (S703 and S704). This allows the user terminal 5 to be connected to an appropriate service operation slice 50.

[0083] In response to the switching instruction, the user terminal 5 sets connection information associated with the switching instruction internally, restarts, and starts a connection sequence using the connection information (S705). A session establishment request is transmitted from the user terminal 5 to the diagnosis SMF 262B (SFM 262 corresponding to terminal diagnosis) via the (R)AN 252 and the AMF 261 (S706, S707, and S708). The diagnosis SMF 262B registers session information in the UDM 264 (S709). A response is returned from the UDM 264 to the diagnosis SMF 262B (S710), and a response is returned from the diagnosis SMF 262B to the AMF 261 (S711). After S702, the management server 121 notifies the diagnosis support server 123 of a predetermined type of information such as the terminal ID of the user terminal 5 (S712).

[0084] The diagnostic SMF 262B transmits a communication policy request to the PCF 263 (S713), and the PCF 263 returns a response to the diagnostic SMF 262B (S714).

[0085] The diagnostic SMF 262B notifies the diagnostic UPF 22B of the session information (S715), and the diagnostic UPF 21B returns a response to the diagnostic SMF 262B (S716). The diagnostic SMF 262B notifies the AMF 261 of the session information (S717), and the AMF 261 returns a response to the diagnostic SMF 262B (S718).

[0086] The AMF 261 notifies the user terminal 5 of the session information via the (R)AN 252 (S719 and S720). A response is returned from the user terminal 5 to the (R)AN 252 (S721), and the connection to the diagnostic slice 50B is completed for the user terminal 5 (S722). A response is returned from the (R)AN 252 to the AMF 261 (S723). The AFM 261 notifies the diagnostic SMF 262B of the base station side session information (S724). The diagnostic SMF 262B notifies the diagnostic UPF 22B of the radio information (S725). A response is returned from the diagnostic UPF 22B to the diagnostic SMF 262B (S726), and a response is returned from the diagnostic SMF 262B to the AFM 261 (not shown). With the above, the connection sequence for connecting the user terminal 5 to the diagnostic slice 50B is completed. After this, the user terminal 5 and the diagnostic assistance server 123 can communicate with each other via the diagnostic UPF 21B (and the diagnostic slice 50B).

[0087] Specifically, an initial connection notification is transmitted from the user terminal 5 to the diagnostic support server 123 via the diagnostic UPF 21B (S727 and S728). A remote login command is transmitted from the diagnostic support server 123 to the user terminal 5 via the diagnostic UPF 21B (S729 and S730).

[0088] A login completion response is transmitted from the user terminal 5 to the diagnostic support server 123 via the diagnostic UPF 21B (S731 and S732). The diagnostic support server 123 requests terminal log information (information on the log of the user terminal 5) from the user terminal 5 via the diagnostic UPF 21B (S733 and S734).

[0089] The user terminal 5 responds with terminal log information to the diagnostic support server 123 via the diagnostic UPF 21B (S735 and S736). The terminal log information may include a terminal ID. The diagnostic support server 123 stores the terminal log information in the log DB 412 and identifies the remote diagnostic file using the terminal ID as a key. The remote diagnostic file is transmitted from the diagnostic support server 123 to the user terminal 5 via the diagnostic UPF 21B (S737 and S738).

[0090] The user terminal 5 executes the remote diagnostic file (S739). Diagnostic log information (information on logs accumulated in the user terminal 5 during execution of the remote diagnostic file) is returned from the user terminal 5 to the diagnostic support server 123 via the diagnostic UPF 21B (S740 and S741). The diagnostic support server 123 stores the diagnostic log information in the log DB 412 and identifies a correction patch file based on the diagnostic log information. The correction patch file is transmitted from the diagnostic support server 123 to the user terminal 5 via the diagnostic UPF 21B (S742 and S743).

[0091] The user terminal 5 executes the correction patch file. The user terminal 5 responds that the correction is complete to the diagnostic support server 123 via the diagnostic UPF 21B (S744 and S745). The diagnostic support server 123 instructs the user terminal 5 to initialize the terminal via the diagnostic UPF 21B (S746 and S745).

[0092] In response to the instruction, the user terminal 5 restarts and starts a connection sequence using connection information including the slice ID of the U2-slice 51B (S748). As a result, the connection destination of the user terminal 5 changes from the diagnosis slice 50B to the U2-slice 51B again. In other words, after the remote diagnosis is completed, the user terminal 5 is automatically disconnected from the diagnosis slice 50B and connected to the U2-slice 51B.

[0093] The above is an example of the flow of the terminal diagnosis support. Note that the destination diagnosis slice 50B in S702 may be determined in any one of the following ways. The management server 121 identifies a diagnostic slice 50B having a predetermined number or less of connections (e.g., 0 or less) from the operational slice DB 512, and determines the identified diagnostic slice 50B. This makes it possible to keep other user terminals 5 that may be affected by a user terminal 5 in which a failure has occurred within a predetermined range. When a fault is notified simultaneously for multiple user terminals 5 of the corporate user 2, the management server 121 may determine the same diagnostic slice 50B for each of the multiple user terminals 5. In this case, the identified diagnostic slice 50B may be a diagnostic slice with a predetermined number of connections or less.

[0094] FIG. 8 shows an example of an administration UI.

[0095] The management server 121 displays a management UI (User Interface) 800 on the 5G management system 11 based on management information including the operational slice DB 512.

[0096] The management UI 800 displays, for example, display objects (e.g., figures and character strings) 801 of slices for service operation.

[0097] Furthermore, the management UI 800 displays, for example, an operational slice table 820 that is a table having the same contents as the operational slice DB 512. However, the slice ID may be replaced with a slice name that can be understood by the 5G administrator.

[0098] In addition, for example, when the administration UI 800 receives a notification of a fault in a user terminal 5, it may display a fault notification table 810 that shows at least a part of the notification (for example, the terminal ID of the user terminal 5 in which the fault occurred, the ID of the corporate user to which the user terminal 5 was shipped, and the symptoms of the fault).

[0099] The above-described management UI 800 supports management of slices for service operation. For example, a 5G administrator can easily grasp the status of slices for service operation.

[0100] The fault notification table 810 may have a selection tool (e.g., a pull-down menu) for a slice ID. When the selection tool is operated by the 5G administrator, the management server 121 may display a list of slice IDs of diagnostic slices selectable by the 5G administrator, as illustrated in FIG. 9. For example, the management server 121 may identify slice IDs of diagnostic slices with a predetermined number or less of connections from the operation slice DB 512, and display the identified slice IDs as a list of slice IDs selectable by the 5G administrator. In this way, the determination of a diagnostic slice with a predetermined number or less of connections as a connection switching destination of a user terminal 5 in which a fault has occurred may be performed automatically by the management server 121 or manually by the 5G administrator.

[0101] 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.

[0102] As illustrated in FIG. 10, for each of a plurality of locations (e.g., user-side sites), there may be a user-oriented slice 51 and a service operation-oriented slice 50, the user-oriented slice 51 being a network slice at the location, and the service operation-oriented slice may be common to the plurality of locations. For example, the first location 1000A may be a commercial building in which a plurality of corporate users 1 and 2 are tenants. The second location 1000B may be a factory of one corporate user 3. The second location 1000B may have a user-oriented network slice for each purpose, for example, a slice 51C for field work and a slice 51D for field monitoring. The service operation-oriented slices such as the setting slice 50A and the diagnostic slice 50B (and the UPF and SMF corresponding to the service operation) may be common to such a plurality of locations. This eliminates the need to change the connection information of the service operation-oriented slice for each corporate user or purpose. Note that a service operation-oriented slice being common to a plurality of locations may mean that the connection information of the service operation-oriented slice is the same regardless of the location.

[0103] Furthermore, at least one server in the operation support system 110 may be operated by an MNO (Mobile Network Operator) or an entity such as an MVNO (Mobile Virtual Network Operator).

[0104] A network 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., logically dividing into EtoE). A network slice may or may not include functions such as UPF21 or 22 and SMF262. For example, a network slice may be composed of one or more network slice instances. A network 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 network slice. [Explanation of symbols]

[0105] 110: Operational support system

Claims

1. A system for supporting operation of a wireless communication service, comprising: one or more operation support units for one or more service operations of wireless communication services; a plurality of network slices having at least one function in common in a core network; The plurality of network slices include one or more user slices and one or more service operation slices; For each of a plurality of users, There are one or more slices for users, A user-facing slice is a network slice prepared for a user, For each of the one or more service operations, There are one or more slices for service operations, A slice for service operation is a network slice prepared for the operation of the service and common to multiple users, An operation support unit corresponding to the service operation transmits target information, which is information including at least one of parameters set in the service operation and parameters necessary for executing the service operation, to a target terminal, which is a wireless communication terminal that has performed a connection sequence using connection information including slice identification information of the slice for the service operation, via the network slice for the service operation. system.

2. One of the one or more service operations is a terminal initial setting; Regarding the operation of the service called terminal initial settings, A slice for service operation to which the target terminal is connected in response to the service operation is a configuration slice, The target terminal is a wireless communication terminal in which initial information, which is information including slice identification information of the set slice, is set as the connection information, The target information is configuration information used to connect to a slice for a user, the slice identification information including the slice identification information of the slice for the user. The system of claim 1 .

3. One of the one or more service operations is terminal diagnosis; Regarding the operation of the terminal diagnosis service, A slice for service operation to which the target terminal is connected in response to the service operation is a diagnostic slice, The target information is diagnostic information that includes parameters for terminal diagnosis, When the target terminal executes the diagnostic information, an operation support unit that is capable of performing terminal diagnosis and is communicably connected to the target terminal via the diagnostic slice performs remote diagnosis of the target terminal via the diagnostic slice. The system of claim 1 .

4. The number of wireless communication terminals that may be simultaneously connected to the diagnostic slice to which the target terminal is connected is equal to or less than a predetermined number, or is equal to the number of wireless communication terminals in which a failure has occurred simultaneously. The system of claim 3.

5. Further comprising a management section; When a failure in the target terminal is detected via a data network of a user-oriented slice to which the target terminal is connected, the management unit determines a diagnostic slice to which a number of wireless communication terminals that may be connected simultaneously is equal to or less than a predetermined number, and transmits a switching instruction associated with connection information including slice identification information of the determined diagnostic slice to the target terminal via the user-oriented slice to which the target terminal is connected; the target terminal, in response to the switching instruction, connects to the determined diagnostic slice using connection information associated with the switching instruction; The system of claim 4.

6. Further comprising a management section; When a failure of the target terminal is detected via a data network of a user-oriented slice to which the target terminal is connected, the management unit transmits a switching instruction associated with connection information including slice identification information of the diagnostic slice to the target terminal via the user-oriented slice to which the target terminal is connected; In response to the switching instruction, the target terminal connects to the diagnostic slice using connection information associated with the switching instruction. The system of claim 3.

7. For each of the plurality of locations, There are slices for users and slices for service operations. the user-facing slice is a network slice at the location, A slice for service operation is common to the multiple locations. The system of claim 1 .

8. A management unit that manages management information including slice information, which is information regarding each of the one or more service operation slices, and outputs the management information; Further comprising: For each service operation slice, the slice information includes at least one of the number of wireless communication terminals connected to the service operation slice and identification information of a user who uses the service operation slice. The system of claim 1 .

9. A communication partner of a wireless communication terminal via each of the one or more service operation slices is limited to a specific partner. The system of claim 1 .

10. 1. A method for facilitating operation of a wireless communication service, comprising: There are a plurality of slices in the core network that have at least one function in common; The plurality of slices include one or more user slices and one or more service operation slices; For each of a plurality of users, There are one or more slices for users, A user-facing slice is a network slice prepared for a user, For each of the one or more service operations, There are one or more slices for service operations, A slice for service operation is a network slice prepared for the service operation and common to the multiple users, The method further comprising: Identification information for one or more service operations of a wireless communication service, and an operation support unit corresponding to a targeted service operation among the one or more service operations transmits target information, which is information including at least one of parameters set in the service operation and parameters necessary for executing the service operation, to a target terminal, which is a wireless communication terminal that has performed a connection sequence using connection information including slice identification information of the slice for the service operation, via a network slice for the service operation; method.

11. One of the one or more service operations is a terminal initial setting; Regarding the operation of the service called terminal initial settings, A slice for service operation to which the target terminal is connected in response to the service operation is a configuration slice, The target terminal is a wireless communication terminal in which initial information, which is information including slice identification information of the set slice, is set as the connection information, The target information is configuration information used to connect to a slice for a user, the slice identification information including the slice identification information of the slice for the user. The method of claim 10.

12. One of the one or more service operations is terminal diagnosis; Regarding the operation of the terminal diagnosis service, A slice for service operation to which the target terminal is connected in response to the service operation is a diagnostic slice, The target information is diagnostic information that includes parameters for terminal diagnosis, When the target terminal executes the diagnostic information, an operation support unit that is capable of performing terminal diagnosis and is communicably connected to the target terminal via the diagnostic slice performs remote diagnosis of the target terminal via the diagnostic slice. The method of claim 10.

13. A computer program for supporting the operation of a wireless communication service, comprising: a plurality of network slices having at least one function in common in a core network; The plurality of network slices include one or more user slices and one or more service operation slices; For each of a plurality of users, There are one or more slices for users, A user-facing slice is a network slice prepared for a user, For each of the one or more service operations, There are one or more slices for service operations, A slice for service operation is a network slice prepared for the operation of the service and common to multiple users, The computer program comprising: Transmitting target information, which is information including at least one of parameters set in the service operation and parameters necessary for executing the service operation, via a network slice for the service operation to a target terminal, which is a wireless communication terminal that has performed a connection sequence using connection information including slice identification information of a slice for the service operation of the service operation corresponding to the computer program; A computer program that causes a computer to do something.

Images