Information processing device, information processing method, and information processing program

Abstract

An information processing device according to the present application comprises a collection unit, a generation unit and a control unit. The collection unit collects metrics information indicating metrics regarding a plurality of microservices constructed in a microservice architecture in each of a plurality of MEC devices which respectively are provided to, and correspond to, a plurality of different base stations in a mobile communication network. When it is determined that a switch is to be performed among the plurality of MEC devices with respect to a microservice for an application being used by a user of a wireless terminal for which a handover is to be performed between the plurality of base stations, the generation unit generates information relating to the switch on the basis of the metrics information collected by the collection unit. On the basis of the information generated by the generation unit, the control unit causes the plurality of MEC devices to execute a switch in the microservice to be used by the user.

Description

Information processing device, information processing method, and information processing program

[0001] The present invention relates to an information processing device, an information processing method, and an information processing program.

[0002] In recent years, multi-access edge computing (MEC) devices have been attracting attention. Because MEC devices are deployed in mobile communication networks, they have less communication delay with wireless terminals and can shorten application response times compared to devices deployed in a cloud environment.

[0003] Patent document 1 proposes a technology in which an edge server that provides services to users of wireless terminals is provided for each base station, and the base station to which the wireless terminal should hand over is determined using the resource usage rate for providing the service.

[0004] JP 2018-113589 A

[0005] However, in the technology described in Patent Document 1, the condition for handover is that the edge server corresponding to the base station to which the wireless terminal is handed over provides services to the user of the wireless terminal, which limits the base stations to which the wireless terminal can be handed over.

[0006] An object of the present application is to provide an information processing device, an information processing method, and an information processing program that enable a MEC device to more appropriately provide services during handover of a wireless terminal.

[0007] The information processing device of the present application comprises: a collection unit that collects metrics information indicating metrics for multiple microservices constructed using a microservice architecture in each of multiple MEC devices that are provided corresponding to multiple different base stations in a mobile communication network; a generation unit that generates information related to the switching when it determines, based on the metrics information collected by the collection unit, that a microservice in an application being used by a user of a wireless terminal that is handed over between the multiple base stations should be switched between the multiple MEC devices; and a control unit that causes the multiple MEC devices to switch the microservices used by the user based on the information generated by the generation unit.

[0008] In addition, the collection unit collects information including information indicating the delay status in the microservice as the metrics information, and the generation unit determines whether or not to switch between the multiple MEC devices of the microservice based on the delay status.

[0009] The generation unit also determines whether to switch the microservice between the multiple MEC devices based on a comparison result of delays in the microservice before and after switching between the multiple MEC devices.

[0010] In addition, the collection unit collects information including information indicating resource usage in the microservice as the metrics information, and the generation unit determines whether to switch between the multiple MEC devices of the microservice based on the delay status and the resource usage.

[0011] In addition, the generation unit determines whether or not to switch the microservice between the multiple MEC devices based on a comparison result of delays and resources in the microservice before and after switching between the multiple MEC devices.

[0012] The plurality of microservices also includes a service that uses AI.

[0013] The information processing method of the present application is an information processing method executed by a computer, and includes: a collection step of collecting metrics information indicating metrics for multiple microservices constructed using a microservice architecture in each of multiple MEC devices provided corresponding to multiple different base stations in a mobile communication network; a generation step of generating information related to the switching when it is determined, based on the metrics information collected by the collection step, that a microservice in an application being used by a user of a wireless terminal that is handed over between the multiple base stations will be switched between the multiple MEC devices; and a control step of causing the multiple MEC devices to switch the microservices used by the user based on the information generated by the generation step.

[0014] The information processing program of the present application causes a computer to execute the following steps: a collection procedure for collecting metrics information indicating metrics for multiple microservices constructed using a microservice architecture in each of multiple MEC devices provided corresponding to multiple different base stations in a mobile communication network; a generation procedure for generating information regarding the switching when it is determined, based on the metrics information collected by the collection procedure, that a microservice in an application being used by a user of a wireless terminal that is handed over between the multiple base stations is to be switched between the multiple MEC devices; and a control procedure for causing the multiple MEC devices to switch the microservices used by the user based on the information generated by the generation procedure.

[0015] According to one aspect of the embodiment, it is possible to more appropriately provide services by the MEC device during handover of a wireless terminal.

[0016] FIG. 1 is a diagram illustrating an example of a mobile communication network including an MEC device according to an embodiment. FIG. 2 is a diagram illustrating an example of the configuration of an information processing device according to an embodiment. FIG. 3 is a diagram illustrating an example of how metrics information is collected by a collection unit of the information processing device according to an embodiment. FIG. 4 is a diagram illustrating an example of how a control unit of the information processing device according to an embodiment controls switching of a target microservice from a source MEC device to a destination MEC device. FIG. 5 is a sequence diagram illustrating an information processing procedure according to an embodiment. FIG. 6 is a hardware configuration diagram illustrating an example of a computer that realizes the functions of the information processing device.

[0017] Hereinafter, an information processing device, an information processing method, and an information processing program according to the present application (hereinafter referred to as "embodiments") will be described in detail with reference to the drawings. Note that the information processing device, the information processing method, and the information processing program according to the present application are not limited to these embodiments. Furthermore, the same components in the following embodiments will be denoted by the same reference numerals, and duplicated descriptions will be omitted.

[0018] (Embodiment) [1. Introduction] In this embodiment, a multi-access edge computing (MEC) device is used as a device that provides a service using an application such as SaaS (Software as a Service).

[0019] The MEC device of this embodiment is, for example, a fifth generation mobile communication system (5 th The MEC device is disposed in a mobile communication network such as a Mobile Access Network (MEC) or a Mobile Access Network (MACE) and is capable of communicating with a user's wireless terminal. FIG. 1 is a diagram illustrating an example of a mobile communication network including an MEC device according to an embodiment. The mobile communication network according to this embodiment includes, for example, a RAN Intelligent Controller (RIC). The RIC controls and optimizes, for example, RAN (Radio Access Network) functions.

[0020] 1, a plurality of MEC devices including MEC devices 300A and 300B are arranged. The plurality of MEC devices are provided corresponding to different base stations in the mobile communication network.

[0021] The MEC devices 300A and 300B are arranged, for example, at a base station in the mobile communication network or at a location close to the base station, but may also be connected to a node in a core network of the mobile communication network, or to a node on a path between the core network of the mobile communication network and the base station. Hereinafter, when the MEC devices 300A and 300B are referred to without being individually distinguished, they may be referred to as the MEC devices 300.

[0022] The MEC device 300A is placed at the MEC site A, and the MEC device 300B is placed at the MEC site B. Each of the MEC site A and the MEC site B includes an RU (Radio Unit) that transmits and receives radio waves to and from the wireless terminal 200 and converts the signals between analog and digital.

[0023] Each of the MEC apparatus 300A and the MEC apparatus 300B includes a DU (Distributed Unit), a CU (Central Unit), a UPF (User Plane Function), and the like.

[0024] In addition, an application server and multiple microservices built using a microservice architecture are implemented in each of the MEC devices 300A and 300B. Hereinafter, the applications implemented in the MEC devices 300A and 300B may be referred to as MEC applications.

[0025] The application server functions as an endpoint that is the entrance of communication from the UPF, for example, and each microservice is accessed through the application server of the corresponding MEC application. Note that in the MEC application, the application server is also constructed as a microservice, but it may also be constructed as something other than a microservice.

[0026] 1 illustrates an application server, a microservice A, and a microservice B in one MEC application. The MEC application is an MEC application that provides an AI chat service using generative AI (artificial intelligence) such as LLM (Large Language Models).

[0027] The AI ​​chat service accepts questions and requests from user U, searches for data based on the accepted questions and requests, and generates and outputs answers using a generation AI based on the search results.

[0028] In this case, microservice A is, for example, a microservice that performs inference processing using generated AI as an AI inference server, and microservice B is, for example, a microservice that performs processing to search for data necessary for inference in microservice A as a search server, but is not limited to such examples.

[0029] In the AI ​​chat service, questions and requests from user U are accepted by an application server, and the application server outputs the accepted questions and requests from user U to microservice A and microservice B.

[0030] Microservice B searches a database in response to a question or request from user U and outputs the search results to microservice A. Microservice A uses a generation AI to generate an answer to user U's question or request based on the search results from microservice B and outputs the generated answer to the application server. The application server provides user U with the answer generated by microservice B.

[0031] Here, when a user U using an MEC application provided by the MEC device 300A of the MEC site A moves, a handover of the wireless terminal 200 is performed from the base station of the MEC site A to the base station of the MEC site B.

[0032] In the above example, the application server is connected to microservice A and microservice B, and microservice A and microservice B are connected to each other, but the connection relationship is not limited to the above example.

[0033] In a handover from the base station of MEC site A to the base station of MEC site B, the UPF is switched, and based on the UPF switching, the application server of the MEC application being used by user U is switched. The UPF switching is also called UPF rerouting.

[0034] In addition, in this embodiment, for microservices A and B, distributed tracing is used to monitor the delay status and resource usage status of microservices A and B, and an appropriate execution site is selected.

[0035] 1, an information processing device 100 is disposed in order to execute microservices A and B at appropriate EMC sites. The information processing device 100 includes a collection unit 131, a generation unit 132, and a control unit 133.

[0036] The collection unit 131 collects metrics information for microservices A and B from the MEC devices 300A and 300B, such as metrics information indicating the delay (latency) status of each of microservices A and B, and metrics information indicating the resource usage status of each of microservices A and B.

[0037] The metrics indicating the delay status are metrics indicating delay time, such as metrics indicating delay time due to processing delay, but may also be metrics indicating delay time including communication delay in addition to processing delay. Metrics indicating resource usage are, for example, processor usage rate and memory usage rate. Processor usage rate is, for example, the usage rate of the CPU (Central Processing Unit).

[0038] Based on the metrics information collected by the collection unit 131, the generation unit 132 determines whether or not to switch between multiple MEC devices 300A and 300B for microservices A and B of the EMC application being used by user U of the wireless terminal 200 undergoing handover.

[0039] Here, for convenience of explanation, when referring to microservices A and B without distinguishing between them individually, they will be referred to as microservice X, and switching between the multiple MEC devices 300A and 300B of microservice X will be explained.

[0040] When the microservice X has sufficient resources and the delay is small in the MEC apparatus 300B, the generation unit 132 determines to switch the microservice X used by the user U from the MEC apparatus 300A to the MEC apparatus 300B. On the other hand, when the microservice X has sufficient resources or the delay is large in the MEC apparatus 300B, the generation unit 132 determines not to switch the microservice X used by the user U from the MEC apparatus 300A to the MEC apparatus 300B.

[0041] The generation unit 132 can also compare the delay and resources of microservice X in the MEC device 300A with the delay and resources of microservice X in the MEC device 300B, and determine whether to switch microservice X from the MEC device 300A to the MEC device 300B based on the comparison result.

[0042] When the generation unit 132 determines that the microservice X is to be switched from the MEC device 300A to the MEC device 300B, the generation unit 132 generates network change information, which is information regarding the switching of the microservice X from the MEC device 300A to the MEC device 300B, and outputs the generated network change information to the control unit 133.

[0043] Based on the switching information output from the generation unit 132, the control unit 133 outputs a network change request to the MEC apparatus 300A and the MEC apparatus 300B to switch the microservice X from the MEC apparatus 300A to the MEC apparatus 300B.

[0044] As a result, microservices that are determined to require switching in the application being used by user U are switched from MEC device 300A to MEC device 300B, and microservices that are determined not to require switching are not switched to MEC device 300B and are provided by MEC device 300A.

[0045] In this way, the information processing device 100 determines whether or not to switch microservices between MEC devices 300 depending on delays and resources, thereby enabling the MEC device 300 to provide services more appropriately during handover of the wireless terminal 200.

[0046] In the above example, the information processing device 100 uses the resource status to determine whether or not to switch microservices between the MEC devices 300. However, if resources are available, the resource status can be excluded from the determination criteria. The information processing device 100 may be located in any of the MEC devices 300 in multiple MEC sites, or may be located as a separate MEC device from the MEC device 300 in the MEC site.

[0047] The metrics information may also include information on metrics of the application server. By using the metrics information of the application server, the information processing device 100 can more accurately determine whether or not to switch between the MEC devices 300 of microservices. The specific configuration and processing of the information processing device 100 according to the embodiment will be described in further detail below.

[0048] 2. Configuration of Information Processing Apparatus 100 Fig. 2 is a diagram showing an example of the configuration of the information processing apparatus 100 according to the embodiment. The information processing apparatus 100 includes a communication unit 110, a storage unit 120, and a processing unit 130.

[0049] The communication unit 110 is realized by, for example, a communication module or a network interface card (NIC). The communication unit 110 is connected to a mobile communication network via a wired or wireless connection, and transmits and receives information to and from, for example, the MEC devices 300A and 300B.

[0050] [2.2. Storage Unit 120] The storage unit 120 is realized by, for example, a semiconductor memory element such as a random access memory (RAM) or a flash memory, or a storage device such as a hard disk or an optical disk. The storage unit 120 has a metrics information storage unit 121. The metrics information storage unit 121 stores metrics information collected by the processing unit 130 from each MEC device 300.

[0051] [2.3. Processing Unit 130] The processing unit 130 is a controller, and is realized by a processor such as a CPU, an MPU (Micro Processing Unit), or a GPGPU (General Purpose Graphics Processing Unit) executing various programs (corresponding to examples of information processing programs) stored in a storage device inside the information processing device 100 using a RAM or the like as a working area.

[0052] The processing unit 130 is a controller, and may be realized by an integrated circuit such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array).

[0053] 2, the processing unit 130 has a collection unit 131, a generation unit 132, and a control unit 133, and realizes or executes the functions and actions of the information processing described below. Note that the internal configuration of the processing unit 130 is not limited to the configuration shown in FIG. 3, and may be any other configuration as long as it performs the information processing described below.

[0054] [2.3.1. Collection Unit 131] The collection unit 131 collects various pieces of information via the communication unit 110 and the like.

[0055] For example, the collection unit 131 collects metrics information indicating metrics for multiple microservices constructed using a microservice architecture in each of multiple MEC devices 300, each of which is provided corresponding to multiple different base stations in a mobile communication network.

[0056] Microservice metrics include metrics that indicate delay (latency) conditions and metrics that indicate resource usage conditions of the microservice. Metrics that indicate delay conditions include metrics that indicate delay time and metrics that indicate processing delay. Metrics that indicate resource usage conditions include, for example, processor usage rate and memory usage rate. Processor usage rate is, for example, CPU usage rate.

[0057] For example, the collection unit 131 collects, as metrics information, information including information indicating a delay state in each microservice of the multiple MEC devices 300. The collection unit 131 also collects, as metrics information, information including information indicating a resource usage state in each microservice of the multiple MEC devices 300.

[0058] The collection unit 131 also collects, as metrics information, information including information indicating, as metrics, communication delays between the multiple MEC devices 300. The collection unit 131 also collects, as metrics information, information including information indicating, as metrics, the availability of resources of each MEC device 300.

[0059] 3 is a diagram illustrating an example of how metrics information is collected by the collection unit 131 of the information processing device 100 according to the embodiment. In the example illustrated in Fig. 3, a user U of a wireless terminal 200 uses an application implemented in an MEC device 300A at an MEC site A, and the application server and microservices A and B of the application used by user U are highlighted.

[0060] 3, the collection unit 131 collects metrics information from multiple MEC devices including an MEC device 300A and an MEC device 300B. The metrics information collected from the MEC devices is, for example, metrics information for an application server and microservices A and B. Collection of metrics information from the multiple MEC devices is repeatedly executed at predetermined intervals. In addition to the predetermined intervals, the collection unit 131 collects metrics information from the switching source MEC device and the switching destination MEC device when a handover request is received from the wireless terminal 200.

[0061] [2.3.2. Generation Unit 132] Based on the metrics information collected by the collection unit 131, the generation unit 132 determines, for each microservice, whether to switch between the multiple MEC devices 300 the microservice in the application being used by the user U of the wireless terminal 200 that is handed over between multiple base stations.

[0062] Here, the MEC device 300 in the MEC site including the base station to which the wireless terminal 200 is connected before handover is referred to as the source MEC device, and the MEC device 300 in the MEC site including the base station to which the wireless terminal 200 is connected after handover is referred to as the destination MEC device. Also, a microservice in an application being used by the user U is referred to as a target microservice.

[0063] The generation unit 132 determines, for each target microservice, whether to switch the target microservice from the source MEC device to the destination MEC device, based on, for example, the resource status and delay status of the target microservice in the destination MEC device.

[0064] The delay of the target microservice in the source MEC device is the delay when the application server switches to the destination MEC device, and includes the processing delay in the target microservice in the source MEC device and the communication delay between the source MEC device and the destination MEC device.

[0065] For example, when the resource status and delay status of the target microservice in the destination MEC device satisfy predetermined conditions, the generation unit 132 determines to switch the target microservice from the source MEC device to the destination MEC device.

[0066] Furthermore, if the resource status and delay status of the target microservice in the destination MEC device do not satisfy predetermined conditions, the generation unit 132 determines not to switch the target microservice from the source MEC device to the destination MEC device.

[0067] The predetermined conditions are conditions for each microservice, such as having sufficient resources and small delays. The presence or absence of sufficient resources is determined by setting a threshold for each microservice, for example, by determining whether the processor availability is equal to or greater than a threshold and whether the memory availability is equal to or greater than a threshold. The magnitude of delay is also determined by setting a threshold for each microservice, for example, by determining whether the delay time is equal to or less than a threshold.

[0068] For example, if the available processor space is equal to or greater than a threshold and the available memory space is equal to or greater than a threshold, the generation unit 132 determines that there is a surplus of resources, and if not, determines that there is a surplus of resources. Also, if the delay time is equal to or less than a threshold, the generation unit 132 determines that the delay is long, and if not, determines that the delay is short.

[0069] In this way, if there is sufficient resource for the target microservice in the switching destination MEC apparatus and the delay is small, the generation unit 132 determines to switch the target microservice from the switching source MEC apparatus to the switching destination MEC apparatus.

[0070] On the other hand, if the target MEC apparatus does not have sufficient resources for the target microservice or the delay is large, the generation unit 132 determines not to switch the target microservice from the source MEC apparatus to the target MEC apparatus.

[0071] The generation unit 132 can also compare the delay and resources of the target microservice in the source MEC apparatus with the delay and resources of the target microservice in the destination MEC apparatus. In this case, the generation unit 132 determines whether to switch the target microservice from the source MEC apparatus to the destination MEC apparatus based on the comparison result.

[0072] For example, the generation unit 132 determines whether the amount of available resources in the target microservice in the destination MEC apparatus is greater than the amount of available resources in the target microservice in the source MEC apparatus by a threshold or more. For example, the generation unit 132 determines whether the amount of available processor space and the amount of available memory space are greater than or equal to different thresholds.

[0073] Furthermore, the generation unit 132 determines whether the delay in the target microservice in the switching destination MEC apparatus is smaller than the delay in the target microservice in the switching source MEC apparatus by a threshold or more.

[0074] When the generation unit 132 determines that the available resources in the target microservice of the destination MEC device are greater than or equal to a threshold and the delay is smaller than or equal to a threshold in comparison with the source MEC device, it determines to switch the target microservice from the source MEC device to the source MEC device.

[0075] In addition, if the generation unit 132 determines that the available resources in the target microservice of the destination MEC device are not greater than a threshold value or the delay is not smaller than a threshold value compared to the source MEC device, it determines not to switch the target microservice from the source MEC device to the source MEC device.

[0076] In addition, if the target application is not present in the destination MEC device, the generation unit 132 can also estimate the resource status and delay status of the target application when the target application is deployed to the destination MEC device based on the resource status of the destination MEC device.

[0077] In this case, the generation unit 132 can determine whether to switch the target microservice from the source MEC device to the destination MEC device using a determination method similar to the above-mentioned determination method based on the estimated resource status and delay status.

[0078] Furthermore, the generation unit 132 can also determine switching between the MEC devices 300 of microservices based on the delays and resources of the application server in addition to the delays and resources of the microservices.

[0079] For example, based on the delay status and resource status of the microservice and the delay status and resource status of the application server, the generation unit 132 predicts the future delay status and future resource status of the microservice for each MEC device 300. Then, based on the prediction result, the generation unit 132 can also determine whether or not to switch between the MEC devices 300 of the microservice.

[0080] In addition, if the generation unit 132 determines, based on the metrics information of the application server, that there is no available resource in the application server of the destination MEC device (for example, the availability is less than a threshold) or that there is a large delay (for example, the delay is greater than a threshold), it can also maintain the application in the source MEC device.

[0081] The method by which the generation unit 132 determines whether or not a microservice is switched between the MEC apparatuses 300 is not limited to the above example, and various modifications are possible. For example, the generation unit 132 can use a learning model to determine whether or not a microservice is switched between the MEC apparatuses 300. The learning model is a model that receives, for example, metrics information such as microservices of the switching source MEC apparatus and metrics information such as microservices of the switching destination MEC apparatus as input, and is configured using learning information to output information indicating whether or not a microservice is switched between the MEC apparatuses 300, and is generated by a model such as a convolutional neural network.

[0082] When the generation unit 132 determines that the microservice of the target application is to be switched from the source MEC device to the destination MEC device, it generates network change information, which is information regarding the switching of the target microservice from the source MEC device to the destination MEC device.

[0083] The network change information is information for causing the source MEC apparatus and the destination MEC apparatus to switch the target microservice from the source MEC apparatus to the destination MEC apparatus. The network change information includes, for example, information indicating the connection configuration between the source MEC apparatus and each user U of the destination MEC apparatus when the target microservice is switched from the source MEC apparatus to the destination MEC apparatus, but is not limited to this example. The generation unit 132 outputs the generated network change information to the control unit 133.

[0084] [2.3.3. Control unit 133] Based on the network change information generated by the generation unit 132, the control unit 133 outputs a network change request to each of the multiple MEC devices 300 to cause the MEC devices 300 to switch the target microservice, which is the microservice of the application being used by the user U.

[0085] The control unit 133 outputs a network change request to the switching source MEC apparatus and the switching destination MEC apparatus to switch the target microservice from the switching source MEC apparatus to the switching destination MEC apparatus based on the switching information output from the generation unit 132. As a result, the target microservice, which is a microservice of the application being used by the user U, is switched between the switching source MEC apparatus and the switching destination MEC apparatus.

[0086] 4 is a diagram illustrating an example of switching control of a target microservice from a source MEC apparatus to a destination MEC apparatus by the control unit 133 of the information processing apparatus 100 according to the embodiment. The example illustrated in FIG. 4 illustrates a case where the connection destination of the wireless terminal 200 is switched from MEC site A to MEC site B while a user U of the wireless terminal 200 is using an application implemented in an MEC apparatus 300A of the MEC site A.

[0087] In the example shown in Figure 4, the target microservices include microservice A and microservice B, and based on a network change request from the control unit 133, microservice A is switched to the MEC device 300B, but microservice B is not switched to the MEC device 300B.

[0088] In the example shown in Figure 4, the switching process by the control unit 133 assigns the application server of the MEC device 300B, the microservice A of the MEC device 300B, and the microservice B of the MEC device 300A to the user U of the wireless terminal 200 that has performed the handover.

[0089] In addition, application server and microservice instances that were allocated only to user U of the wireless terminal 200 that performed the handover and that are released from allocation due to the switch may be deleted along with the resources allocated to such instances.

[0090] 5 is a sequence diagram showing an information processing procedure according to an embodiment. As shown in FIG. 5, when the wireless terminal 200 is connected to the UPF of the MEC site A (step S10), the collection unit 131 collects metrics information from the application server and each microservice of the MEC site A (steps S11 and S12).

[0091] The processes of steps S11 and S12 are repeated. Although not shown, the collection unit 131 collects metrics information from the application server and each microservice of the MEC site B. The metrics information collected by the collection unit 131 is output to the generation unit 132 (step S13). The generation unit 132 determines whether a network change is necessary (step S14). The network change may be, for example, switching the MEC device 300 that executes the microservice.

[0092] When a handover becomes necessary due to the movement of user U, wireless terminal 200 transmits a handover (HO) request to MEC site A (step S15). MEC site A outputs a handover instruction to wireless terminal 200 in response to the handover request (step S16). Upon receiving the handover instruction, wireless terminal 200 transmits a connection request in response to the handover instruction to MEC site B (step S17) and connects to the UPF of MEC site B (step S18).

[0093] The application server of the MEC site B requests switching of the edge application service (EAS) in response to connection of the wireless terminal 200 to the UPF of the MEC site B (step S19). As a result, the application server of the application being used by the user U is switched from the application server of the MEC device 300A to the application server of the MEC device 300B.

[0094] The collection unit 131 collects metrics information from the application server and each microservice of the MEC site B (steps S20 and S21). The processes of steps S20 and S21 are repeated. The metrics information collected by the collection unit 131 is output to the generation unit 132 (step S22).

[0095] The generation unit 132 determines whether a network change is necessary to optimize the execution site of the microservice based on the metrics information output from the collection unit 131 in steps S13 and S22 (step S23). In step S23, the generation unit 132 determines, as the necessity of a network change, whether each microservice of the application being used at the MEC site A by the wireless terminal 200 of the user U who performed the handover needs to be switched.

[0096] When the generation unit 132 determines that switching of at least one microservice is necessary to optimize the execution site of the microservice, the generation unit 132 generates network change information and outputs the generated network change information to the control unit 133 (step S24). The network change information includes information for causing the source MEC device and the destination MEC device to switch the microservice from the source MEC device to the destination MEC device.

[0097] Based on the network change information acquired from the generation unit 132, the control unit 133 sends a network change request for the microservice to the MEC device 300B and changes the connection relationship so that the microservice of the MEC device 300B becomes available to the user U (steps S25, 26).

[0098] 4. Modifications In the above example, an AI-based service has been described as an example of an application implemented in the MEC device 300. However, the application is not limited to this example. For example, the application implemented in the MEC device 300 may be an Internet of Things (IoT) application that processes data from the IoT in real time, or a game application that uses augmented reality (AR).

[0099] Furthermore, services using AI are not limited to AI chat services, but may include, for example, a service that performs image recognition using image recognition AI, or an autonomous driving service that controls a vehicle using autonomous driving AI or algorithms based on data obtained from various sensors installed in the vehicle.

[0100] 5. Effects As described above, the information processing device 100 according to the embodiment includes a collection unit 131, a generation unit 132, and a control unit 133. The collection unit 131 collects metrics information indicating metrics for multiple microservices built using a microservice architecture in each of multiple MEC devices 300 provided corresponding to multiple different base stations in a mobile communication network. The generation unit 132 generates information related to switching when it determines, based on the metrics information collected by the collection unit 131, that a microservice in an application being used by a user U of a wireless terminal 200 undergoing handover between multiple base stations is to be switched between multiple MEC devices. The control unit 133 causes the multiple MEC devices 300 to switch the microservice used by the user U based on the information generated by the generation unit 132. This enables the information processing device 100 to more appropriately provide services via the MEC devices 300 during handover of the wireless terminal 200.

[0101] Furthermore, the collection unit 131 collects information including information indicating a delay state in the microservice as metrics information, and the generation unit 132 determines, based on the delay state, whether to switch the microservice between the multiple MEC devices 300. This allows the information processing device 100 to more appropriately provide services by the MEC device 300 when the wireless terminal 200 is handed over.

[0102] Furthermore, the generation unit 132 determines whether to switch the microservice between the multiple MEC devices 300 based on a comparison result of delays in the microservice before and after the switch between the multiple MEC devices 300. This enables the information processing device 100 to more appropriately provide the service by the MEC device 300 when the wireless terminal 200 is handed over.

[0103] Furthermore, the collection unit 131 collects information including information indicating resource usage status in the microservice as metrics information, and the generation unit 132 determines whether to switch the microservice between the multiple MEC devices 300 based on the delay status and the resource usage status. This enables the information processing device 100 to more appropriately provide services by the MEC device 300 when the wireless terminal 200 is handed over.

[0104] Furthermore, the generation unit 132 determines whether to switch microservices between the multiple MEC devices 300 based on a comparison result of delays and resources in the microservices before and after the switch between the multiple MEC devices 300. This enables the information processing device 100 to more appropriately provide services by the MEC device 300 when the wireless terminal 200 is handed over.

[0105] Furthermore, the plurality of microservices includes a service using AI. This allows the information processing device 100 to more appropriately provide the AI ​​application service by the MEC device 300 at the time of handover of the wireless terminal 200.

[0106] 6. Hardware Configuration The information processing device 100 according to the embodiment described above is realized by a computer 1000 having a configuration such as that shown in Fig. 6. Fig. 6 is a hardware configuration diagram showing an example of a computer that realizes the functions of the information processing device 100. The computer 1000 includes a CPU 1100, a RAM 1200, a ROM 1300, a HDD 1400, a communication interface (I / F) 1500, an input / output interface (I / F) 1600, and a media interface (I / F) 1700.

[0107] The CPU 1100 operates and controls each unit based on programs stored in the ROM 1300 or the HDD 1400. The ROM 1300 stores a boot program executed by the CPU 1100 when the computer 1000 starts up, programs that depend on the hardware of the computer 1000, and the like.

[0108] The HDD 1400 stores programs executed by the CPU 1100, data used by such programs, etc. The communication interface 1500 receives data from other devices via a predetermined communication network and sends it to the CPU 1100, and transmits data generated by the CPU 1100 to other devices via the predetermined communication network.

[0109] The CPU 1100 controls output devices such as a display and a printer, and input devices such as a keyboard and a mouse, via the input / output interface 1600. The CPU 1100 acquires data from the input devices via the input / output interface 1600. The CPU 1100 also outputs generated data to the output devices via the input / output interface 1600.

[0110] Media interface 1700 reads a program or data stored in recording medium 1800 and provides it to CPU 1100 via RAM 1200. CPU 1100 loads the program or data from recording medium 1800 onto RAM 1200 via media interface 1700 and executes the loaded program. Recording medium 1800 is, for example, an optical recording medium such as a DVD (Digital Versatile Disc) or a PD (Phase Change Rewritable Disc), a magneto-optical recording medium such as an MO (Magneto-Optical disk), a tape medium, a magnetic recording medium, or a semiconductor memory.

[0111] For example, when the computer 1000 functions as the information processing device 100 according to the embodiment, the CPU 1100 of the computer 1000 executes programs loaded onto the RAM 1200 to realize the functions of the processing unit 130. The CPU 1100 of the computer 1000 reads and executes these programs from the recording medium 1800, but as another example, the CPU 1100 may obtain these programs from another device via a predetermined communication network.

[0112] Although some of the embodiments of the present application have been described in detail above with reference to the drawings, these are merely examples, and the present invention can be implemented in other forms that include the embodiments described in the Disclosure of the Invention section and that have undergone various modifications and improvements based on the knowledge of those skilled in the art.

[0113] [7. Other] Furthermore, among the processes described in the above embodiments and modifications, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using known methods. In addition, the information including the processing procedures, specific names, various data, and parameters shown in the above documents and drawings can be changed as desired unless otherwise specified. For example, the various information shown in each drawing is not limited to the information shown in the drawings.

[0114] Furthermore, the components of each device shown in the figure are conceptual functional components and do not necessarily have to be physically configured as shown in the figure. In other words, the specific form of distribution and integration of each device is not limited to that shown in the figure, and all or part of them can be functionally or physically distributed and integrated in any unit depending on various loads, usage conditions, etc.

[0115] Furthermore, the above-described embodiments and modifications can be combined as appropriate within the scope of not causing any contradiction in the processing content.

[0116] Furthermore, the above-mentioned "section, module, unit" can be read as "means" or "circuit," etc. For example, an acquisition unit can be read as an acquisition means or an acquisition circuit.

[0117] REFERENCE SIGNS LIST 100 Information processing device 110 Communication unit 120 Storage unit 130 Processing unit 131 Collection unit 132 Generation unit 133 Control unit 200 Wireless terminal 300, 300A, 300B MEC device

Claims

1. An information processing device comprising: a collection unit that collects metrics information indicating metrics for multiple microservices constructed using a microservice architecture in each of multiple MEC devices provided corresponding to multiple different base stations in a mobile communication network; a generation unit that generates information regarding the switching when it is determined, based on the metrics information collected by the collection unit, that a microservice in an application being used by a user of a wireless terminal that is handed over between the multiple base stations should be switched between the multiple MEC devices; and a control unit that causes the multiple MEC devices to switch the microservices used by the user based on the information generated by the generation unit.

2. The information processing device described in claim 1, wherein the collection unit collects information including information indicating a delay situation in the microservice as the metrics information, and the generation unit determines whether or not to switch between the multiple MEC devices of the microservice based on the delay situation.

3. The information processing device according to claim 2, wherein the generation unit determines whether or not to switch the microservice between the plurality of MEC devices based on a comparison result of delays in the microservice before and after switching between the plurality of MEC devices.

4. An information processing device as described in claim 2 or 3, wherein the collection unit collects information including information indicating resource usage status in the microservice as the metrics information, and the generation unit determines whether or not to switch between the multiple MEC devices of the microservice based on the delay status and the resource usage status.

5. The information processing device described in claim 4, wherein the generation unit determines whether or not to switch the microservice between the multiple MEC devices based on a comparison result of delays and resources in the microservice before and after switching between the multiple MEC devices.

6. The information processing device according to any one of claims 1 to 3, wherein the plurality of microservices includes a service that uses AI.

7. An information processing method executed by a computer, comprising: a collection step of collecting metrics information indicating metrics for multiple microservices constructed using a microservice architecture in each of multiple MEC devices provided corresponding to multiple different base stations in a mobile communication network; a generation step of generating information related to the switching when it is determined, based on the metrics information collected by the collection step, that a microservice in an application being used by a user of a wireless terminal that is handed over between the multiple base stations is to be switched between the multiple MEC devices; and a control step of causing the multiple MEC devices to switch the microservices used by the user, based on the information generated by the generation step.

8. An information processing program that causes a computer to execute the following steps: a collection procedure for collecting metrics information indicating metrics for multiple microservices constructed using a microservice architecture in each of multiple MEC devices provided corresponding to multiple different base stations in a mobile communication network; a generation procedure for generating information related to the switching when it is determined, based on the metrics information collected by the collection procedure, that a microservice in an application being used by a user of a wireless terminal that is handed over between the multiple base stations is to be switched between the multiple MEC devices; and a control procedure for causing the multiple MEC devices to switch the microservices used by the user, based on the information generated by the generation procedure.

Images