ORCHESTRATOR DEVICE, COMMUNICATION SYSTEM, APPLICATION USAGE DETERMINATION PROCEDURES, CONTROL CIRCUIT AND STORAGE MEDIUM

The orchestrator device optimizes application usage across edge and cloud servers to overcome session limitations, allowing UE to access multiple services concurrently.

DE112022006599T5Active Publication Date: 2024-12-05MITSUBISHI ELECTRIC CORP
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
DE112022006599
Authority / Receiving Office
DE · DE
Patent Type
Applications
Current Assignee / Owner
Filing Date
2022-04-05
Publication Date
2024-12-05
Estimated Expiration
2042-04-05

AI Technical Summary

Technical Problem

User equipment (UE) cannot simultaneously use all desired services due to an upper limit on the number of sessions that can be established across edge networks and clouds, leading to service limitations.

Method used

An orchestrator device dynamically manages application usage across edge servers and cloud servers based on user location, maximum sessions, and service requirements to optimize session allocation.

Benefits of technology

Enables simultaneous provision of services to UE beyond the session limit by dynamically reallocating applications and sessions, ensuring continuous service availability.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 00000000_0000_ABST
    Figure 00000000_0000_ABST
Patent Text Reader

Abstract

An edge orchestrator (1) is an orchestrator device for dynamically utilizing one or more applications for at least one edge server and at least one cloud server to provide one or more services to at least one user device. The edge orchestrator (1) includes an application usage determination unit (14) which, upon detecting a state in which usage determination of the one or more applications is required, determines the usage of the one or more applications based on: the location of each user device using the one or more services; the maximum number of sessions, which represents an upper limit on the number of sessions that may be concurrently set for each individual user device using the one or more services; and a request for the service provided by each application to be used.
Need to check novelty before this filing date? Find Prior Art

Description

Area

[0001] The present disclosure relates to an orchestrator apparatus for determining the usage of an application providing a service to a user device, a communication system, an application usage determination method, a control circuit, and a storage medium. background

[0002] Cloud computing, now widely used, runs applications on groups of servers installed in a large-scale facility, called a data center, and delivers services over the internet. On the other hand, edge computing installs (groups of) servers for application deployment closer to the user in a network, thus reducing communication latency and the load on the main network compared to cloud computing.

[0003] In edge computing, a server is selected to use the application from a group of servers distributed / located across multiple network locations to meet service network requirements. In edge computing, the server is also changed to use the application according to time-dependent changes in the usage states of the network resources and servers, the user's location, and the service used by a user.

[0004] Non-Patent Literature 1 provides a framework and architecture for implementing such a change in application usage. For example, Patent Literature 1 discloses a system that, when a terminal device is handed over in a mobile communication network, determines whether to change the server for application usage based on the quality of the network communication between the terminal device after the handover and a server. Reference listPatent literature

[0005] Patent Literature 1: Japanese Patent Application, Publication No. 2011-103567 Non-patent literature

[0006] Non-Patent Literature 1: ETSI GS MEC 003 V2.1.1 (2019-01) SummaryTechnical task

[0007] If a user wishes to use a variety of services, it is possible that the applications for the services will be distributed across multiple server groups in the network if the different services have different requirements. Even if the services have similar requirements, it is possible that the servers on which the applications are deployed at a given time will vary depending on the resource status of the network and the servers, as well as the previous usage of the applications.

[0008] 3GPP TS23.548 V17.0.0 defines distributed anchor points, multiple Protocol Data Unit (PDU) sessions, and session aborts as three types of connectivity models for edge computing in a mobile communications network. In the previous types of connectivity models, a user equipment (UE) must establish a session over the mobile communications network for each point of connection to a data network (DN), which is an external network. This means that the UE must establish a session for each edge network to which an edge server belongs and a session for each common point of connection to the Internet.

[0009] On the other hand, there is an upper limit on the number of sessions that can be established concurrently for the UE. Thus, the user cannot use all services if the applications for the services the user wants to use are distributed across the edge networks or clouds beyond the upper limit on the number of sessions that can be established concurrently for the UE.

[0010] The present disclosure has been made in view of the circumstances, and an object of the present disclosure is to provide an orchestrator device implementing a communication system capable of simultaneously providing services to a UE, the UE having a limitation on the number of sessions that may be simultaneously set, the services exceeding an upper limit on the number of sessions that may be simultaneously set. Solution to the task

[0011] To achieve the above object and to achieve the goal, the present disclosure provides an orchestrator device for dynamically utilizing one or more applications for at least one edge server and at least one cloud server to provide one or more services to at least one user device, the orchestrator device comprising: an app usage determination unit for, upon detecting a state in which determination of usage of the one or more applications is required, determining usage of the one or more applications based on: a location of each user device to use the one or more services; a maximum number of sessions that represents an upper limit on the number of sessions that may be set simultaneously for each user device to use the one or more services;and a request for the service provided by each application to be used.; Advantageous effects of the invention

[0012] The orchestrator device according to the present disclosure effects the implementation of the communication system capable of simultaneously providing the services to the UE, wherein the UE has the limitation of the number of sessions that may be set up simultaneously, wherein the services exceed the upper limit of the number of sessions that may be set up simultaneously. Brief description of the drawings Fig. 1 is a diagram showing an example configuration of a communication system implemented by applying an edge orchestrator according to an embodiment. Fig. 2 is a block diagram showing a functional configuration of the edge orchestrator according to the embodiment. Fig. 3 is a diagram showing a state of the communication system before relocating a usage of an application. Fig. Figure 4 is a diagram showing a state of the communication system after the relocation of the use of the application. Fig. 5 is a flowchart showing an example of operations of the edge orchestrator according to the embodiment. Fig. 6 is a diagram showing an example of hardware implementing the edge orchestrator according to the embodiment. Description of embodiments

[0013] Hereinafter, an orchestrator device, a communication system, an application usage determination method, a control circuit, and a storage medium according to an embodiment of the present disclosure will be described in detail with reference to the drawings. Embodiment.

[0014] Fig. 1 is a diagram showing an example configuration of a communication system 100 implemented by applying an edge orchestrator 1 according to the embodiment.

[0015] The communication system 100 includes the edge orchestrator 1, which is an orchestrator device, edge networks (edge ​​NWs) 2, a wide area network (WAN) 3, radio access networks (RANs) 4, a core network 5, and UEs 6. In the communication system 100, the edge orchestrator 1 uses the edge servers (ES) 21 that define the edge networks 2 or the cloud servers (clouds) 31 that define the WAN 3 to provide server-side applications for services received by users using the UEs 6. Note that in the following description, the edge network and application are sometimes referred to as "edge" and "app," respectively.

[0016] A mobile network with edge networks 2 and RANs 4 under the core network 5 is operated by one or a plurality of operators. The WAN 3 is a network in which the systems of the plurality of operators are interconnected. The WAN 3 includes the illustrated cloud servers 31 as well as the internet.

[0017] The UEs 6 are each a user device such as a smartphone, a tablet, or an in-vehicle device. The UE 6 is connected to the edge server 21 or the cloud server 31 on which the application is used or deployed, so that the user using the UE 6 can receive the service.

[0018] Each RAN 4 includes a so-called base station. For simplicity, the RAN 4 is sometimes referred to as base station 4 in the following description. The RAN 4, which is wirelessly connected to the UE 6 located within range of the respective RAN 4, transmits to the core network 5 the signals received from the UE 6 and addressed to the WAN 3 or the signals received from the UE 6 and addressed to the edge networks 2 connected to the core network 5, and transmits to the UE 6 the signals received from the core network 5 and addressed to the UE 6. In addition, the base station 4 is also connected to the near edge 2, transmits signals received from the UE 6 and addressed to the near edge 2 to the near edge 2, and transmits signals received from the near edge 2 to the UE 6.It should be noted that the communication between the base station 4 and the nearby edge 2 also takes place via a signal transfer function (which is also used or deployed in the vicinity of the base stations 4) between functions of the core network 5, which will be described later but is not shown.

[0019] In addition to signal transfer between the base stations 4 and the external networks (including the WAN 3 and the Edges 2), the core network 5 performs functions such as registration and authentication of the UEs 6, location management, and establishment and control of communication paths (including PDU sessions) between the UEs 6 and the external networks. The core network 5 also performs the function of making information in the mobile network available to an application outside the mobile network and enabling the external application to control the mobile network.

[0020] The edges 2 are each connected to the base station 4 or the core network 5 and each contain the edge server 21 in which an application is used and processing is performed to provide a service to the UE 6. It should be noted that although the edges 2 may each comprise a plurality of edge servers 21, in Fig. 1 only one edge server 21 is shown in each edge network 2.

[0021] The edge orchestrator 1 provides an instruction to use the application or to change the use of the application and notifies the mobile network of a necessary session based on network and server requirements of services delivered to the UE 6 via the mobile network, resource information about the mobile network, resource information about the edge server 21, location information about the UE 6, the use or non-use of the service by the UE 6, and information about the maximum number of sessions for the UE 6. The maximum number of sessions for the UE 6 is the upper limit for the number of sessions that may be set for the UE 6 at the same time.It should be noted that the utilization of the application involves not only whether to utilize the application on each server, but also how many server resources should be allocated to the application when the application is utilized. For example, Non-Patent Literature 1 discloses the control of such resource allocation amounts, and various methods for calculating the resource allocation amounts are considered. An example of the methods includes a method for calculating the resource allocation amounts based on the number of UEs 6, since it is assumed that more resources are required the larger the number of UEs 6 connected to each server. Whether to perform utilization or deployment will be described below.

[0022] Fig. Figure 2 is a block diagram showing a functional configuration of the edge orchestrator 1 according to the embodiment. The edge orchestrator 1 includes a resource information management unit 11, a mobile network information acquisition unit 12, a policy setting unit 13, and an app usage determination unit 14.

[0023] The resource information management unit 11 manages, for example, the network locations of each edge server 21 and each cloud server 31, amounts of communication latency between the UE 6 and each edge server 21 and each cloud server 31, information about the usage states and use states (or availability states) of resources (including a computing resource, a memory resource, and a storage resource) of each edge server 21, usage states of resources (including a communication band from the UE 6 to each cloud server 31 and a communication band from the UE 6 to each edge server 21) of the mobile network, and information about the usage states (or availability states) of the resources of the mobile network.

[0024] The mobile network information acquisition unit 12 acquires a location and the maximum number of sessions for each UE 6, as well as information about the resources of the mobile network (including the communication bands from the UE 6 to each cloud server 31 and from the UE 6 to each edge server 21). Furthermore, the mobile network information acquisition unit 12 receives a handover notification of the handover of the UE 6.

[0025] The policy setting unit 13 maintains policies for the use and modification of the application's usage. For example, the policies stipulate that the server on which the application is used should be set to the highest possible level among the cloud servers 31 and the edge servers 21, and that the number of servers on which the applications are used for identical services should be reduced as much as possible (i.e., should not be distributed).

[0026] In response to the handover of the UE 6, the change to a usage state of the UE 6's service, and the start of provisioning a new service, the app usage determining unit 14 determines the usage of the application based on: the requests for the services; the information managed by the resource information managing unit 11; the UE information acquired by the mobile network information acquiring unit 12; and the policies related to the usage of the application managed by the policy setting unit 13. Furthermore, the app usage determining unit 14 manages, for each service, the request for the service, the UE 6 using the service, and information about the usage of the application for the service. The information about the usage of the application for the service includes information indicating on which server the application for the service is used or installed.is deployed, and information indicating which server each UE using the service is connected to in order to receive the service. The UE information, which is information related to the UE 6, includes, for example, information about the number of sessions allowed to be set up for the UE 6 simultaneously, a current location of the UE 6, and a base station to which the UE 6 is connected. The requirement of the service is, for example, a request latency, a required band, a required resource, a deployment area, or the like. The app usage determination unit 14 further instructs the edge server 21 and the cloud server 31 to use and reuse the application, as appropriate, and notifies the mobile network of a necessary session between the UE 6 and the edge server 21 or the cloud server 31.

[0027] The following is based on the Fig. 3 and Fig. 4 describes a processing example in which the edge orchestrator 1 of the communication system 100 shifts the use of the applications. Fig. 3 is a diagram showing a state of the communication system 100 before the change to use the application, and Fig. Figure 4 is a diagram showing the state of the communication system 100 after the change to use the application. It should be noted that in the Fig. 3 and Fig. 4 some of the edge networks 2 and the cloud server 31 of the WAN 3, which are integrated into the communication system 100 in Fig. 1 are included, are not shown.

[0028] To simplify the description, this example assumes that the edge server 21 of the edge network 2, which is connected to each base station (RAN 4), is a candidate for the server on which the application is used. Of course, the edge server 21 connected to the core network and the cloud server 31 of the WAN are also typically considered candidates for the servers on which the applications are used, and the idea described below is also applicable where such candidates are included. Note that in the following description, as shown in the figure, the plurality of edge networks 2 can be referred to as edge networks #1 to #4 to distinguish them from one another, and the plurality of RANs 4 can be referred to as RANs #1 to #4 to distinguish them from one another. The edge networks #1 to #4 are connected to the RANs #1 to #4, respectively.It is also assumed that each of the edge networks 2 comprises an edge server 21.

[0029] In this example, it is assumed that three types of services A, B, and C are provided: a service requiring ultra-low latency communication (= Service A); a service requiring low latency communication (= Service B); and a service that has no special requirement for communication latency (= Service C). Ultra-low latency can be realized with Edge 2 near RAN 4, which hosts each UE 6, and low latency can be implemented with Edge 2 near RAN 4, adjacent to RAN 4, which hosts each UE 6. Fig. 3, Edge Orchestrator 1 uses applications for all four Edges #1 to #4 for Service A, uses applications for every other Edge (here Edges #1 and #3) for Service B, and uses an application for only one Edge (here Edge #1) for Service C. In Fig. 3, the rectangles labeled A1 to A4 respectively indicate the application for service A, the rectangles labeled B1 and B3 respectively indicate the application for service B, and a rectangle labeled C1 indicates the application for service C. It should be noted that in a case where the edge network 2 is defined by the plurality of edge servers 21, the application can be used in any of the edge servers 21 of the edge network 2. On which edge server 21 the application should be used is determined, for example, based on the usage states, the usage states, etc. of the resources of the respective edge servers 21. The same applies to Fig. 4.

[0030] Although the range of each of RANs #1 to #4 is actually two-dimensional, for simplicity, the one-dimensional range is described here. Furthermore, it is assumed that each UE 6 receives all three types of services A to C. Since, as described above, the UE 6 must establish a session for each connected external network, each UE 6 must establish one session or as many sessions as the Fig. 3. This means that the UE 6 connected to RAN #1 must establish one session, specifically one session with Edge #1 to receive services A to C. The UE 6 connected to RAN #2 must establish two sessions, specifically one session with Edge #2 to receive service A and one session with Edge #1 to receive services B and C. The UE 6 connected to RAN #3 must establish two sessions, specifically one session with Edge #3 to receive services A and B and one session with Edge #1 to receive service C. The UE 6 connected to RAN #4 must establish three sessions, specifically one session with Edge #4 to receive service A, one session with Edge #3 to receive service B, and one session with Edge #1 to receive service C.

[0031] Consider a situation where the UE 6 connected to RAN #3 moves and is handed over to RAN #4. Furthermore, assume that the maximum number of sessions, which represents the upper limit of the number of sessions that can be set simultaneously, for the UE 6 connected to RAN #3 is two, and the Edge Orchestrator 1 knows this maximum number in advance. Examples of a method by which the Edge Orchestrator 1 knows the maximum number of sessions for each UE 6 include a method of obtaining information about the maximum number of sessions for each UE 6 from the mobile network, since the mobile network may know the information about the maximum number of sessions for the UE 6 at the time of registration of the UE 6.Of course, without being dependent on this procedure, the following procedure can also be used alternatively: The maximum number of sessions for each UE 6 can be set separately in the Edge Orchestrator 1, and only the information (e.g., ID) about the UE 6 present in the service area can be obtained from the mobile network. Alternatively, another procedure can also be used.

[0032] The Edge Orchestrator 1 is notified by the mobile network that the UE 6 is to be handed over from RAN #3 to RAN #4. Knowing how the applications are used on the Edge Networks 2 (Edge #1 to Edge #4) and that the maximum number of sessions for this UE 6 is two, the Edge Orchestrator 1 determines that the UE 6 cannot continuously receive the three types of services in RAN #4, the target of the UE handover, instructs each Edge Network 2 to switch the application usage, and instructs the mobile network to establish the session so that the UE 6 can connect to the Edge Networks 2 that have switched the application usage. Fig. Figure 4 shows an example of repurposing, and Edge Orchestrator 1 propagates the application's usage for service C to Edge 4.

[0033] As described above, after notifying the UE 6 of the handover, the Edge Orchestrator 1 determines whether the UE 6 to be handed over can continuously use the currently used services without changing the application usage for each service. This determination is made based on the application usage and the maximum number of sessions for the UE 6. In a case where the UE 6 cannot continuously use the services due to a lack of sessions, the Edge Orchestrator 1 changes the application usage so that the UE 6 can continuously receive the required services with the maximum number of sessions for the UE 6.As described above, the use of applications taking into account the maximum number of sessions for the UE 6 enables the UE 6 to receive the plurality of services even if the UE 6 has a limitation on the number of sessions that can be set up simultaneously.

[0034] The handover notification may precede the actual handover, occur simultaneously with, or follow the handover. However, in some cases, the handover notification must occur before the actual handover, depending on the allowable duration of the service disruption, because it takes time to change the application usage after the handover notification. To shorten the time between the handover notification and the instruction to change the application usage, Edge Orchestrator 1 can calculate the application usage in advance and provide the handover to the RAN 4 that is a possible target of the handover. The RANs 4 that are potential handover targets are expected to be the RANs 4 with adjacent ranges.For example, if the UE 6 is an in-vehicle device, the Edge Orchestrator 1 is expected to separately have map information and compare the map information with the range information, making it possible to further narrow down the RANs 4 that are candidates for handover. Furthermore, the Edge Orchestrator 1 may utilize the applications prior to the handover notification. Instead of receiving the handover notification from the cellular network, the Edge Orchestrator 1 may determine the handover based on the location information about the UE 6 and the range information. Alternatively, the Edge Orchestrator 1 may use both the receipt of the handover notification and the handover determination in combination. The Edge Orchestrator 1 may obtain the location information about the UE 6 from the cellular network or from another system that collects the location information from the UE 6.

[0035] An example of the functionality of the Edge Orchestrator 1 described above is shown in a flowchart in Fig. 5 shown. Fig. 5 is a flowchart showing an example of operations of the edge orchestrator 1 according to this embodiment.

[0036] First, the app usage determination unit 14 of the edge orchestrator 1 checks whether the handover of the UE 6 has been completed, i.e., whether the mobile network information acquisition unit 12 has received a notification from the mobile network indicating the handover of the UE 6 (step S11). If the handover of the UE 6 has not been completed (step S11: No), the app usage determination unit 14 repeats the check to determine whether the handover has been completed. If the handover of the UE 6 has been completed (step S11: Yes), the app usage determination unit 14 checks whether the change is necessary for using the applications, i.e., whether the UE 6 to be handed over can continue to receive the services even after the handover of the UE 6 (step S12). If the change is required for the use of the applications (step S12: Yes), the app usage determination unit 14 changes the use of the applications (step S13).In step S13, as described above, the app usage determination unit 14 changes the usage of the applications so that the handed-over UE 6 can use the services used before the handover of the UE 6 in the number of sessions less than or equal to the maximum number of sessions. After executing step S13, if the change is not required for the usage of the applications (step S12: No), the app usage determination unit 14 returns to step S11 and repeats the processes of steps S11 to S13.

[0037] In the example described above, there is a possibility that the application usage for service C cannot be switched to Edge 4, depending on the resource states of Edge 4 and the resource states of the mobile network. The app usage determination unit 14 of the edge orchestrator 1 can obtain the resource states of Edges 1 to 4 and the resource states of the mobile network before calculating the application usage, and can calculate the switched application usage using these states as constraints. For example, if Edge 4 does not have sufficient resources but Edge 3 has sufficient resources, the app usage determination unit 14 can assign the application usage for service C to Edge 3 instead of Edge 4.Furthermore, the service provided by the application considered as repurposed usage is not limited to the service that cannot be continuously provided to the UE 6 if the repurposed usage is not performed. In particular, when resources are insufficient, the repurposed usage of the applications, including other services, is calculated to potentially achieve the usage that enables continuous provision of the required services to all UEs 6. On the contrary, regardless of how the applications are repurposed, in some cases it is impossible to continuously provide the required services to all UEs 6. In such a case, the Edge Orchestrator 1 may notify the UEs 6 that are not allowed to receive the services continuously that the services cannot be continuously provided.Edge Orchestrator 1 can notify a service provider that it is not possible to provide the service continuously. As described above, an attempt is made to calculate the usage for the potential handover in advance, but it turns out that the services cannot be provided continuously. In this case, the corresponding notification can be made before the handover.

[0038] On the other hand, there may be different application usage patterns that can continuously provide services to each UE 6. In this case, the app usage determination unit 14 of the edge orchestrator 1 determines usage in accordance with the policies set in the policy setting unit 13. Since the migrated application usage may impact service continuity, the following policies, for example, should be considered: selecting a migrated usage pattern that entails as few changes as possible, selecting a migrated usage pattern with consistent resource utilization, etc.

[0039] Furthermore, in the above example, it is necessary to deploy an additional application in accordance with the handover from UE 6. However, there is also the opposite case, where the application in use is no longer needed. In such a case, Edge Orchestrator 1 can delete the no longer required application.

[0040] Although it was described above that the applications are reused in response to the handover of the UE 6, it is also conceivable that the service received from the UE 6 is added or deleted, in which case the Edge Orchestrator 1 can reuse the applications accordingly in the same way. That is, in step S11 of Fig. 5, the app usage determination unit 14 may check whether the service used by the UE 6 is changed (addition or deletion of the service), in addition to checking whether the handover of the UE 6 is executed, and may execute step S12 when the handover is executed or the service used by the UE 6 is changed. For example, an administrator of the edge orchestrator 1 may, upon request from a user of the UE 6, set in the edge orchestrator 1 whether the UE 6 uses the service and change the setting. Alternatively, this setting and change may also be performed by a service that manages whether the service should be used. In the latter case, this management service should be used as a precondition. It is assumed that such a service does not have special latency requirements, and thus, for example, it is necessary to use the services centrally on the cloud server 31 so that the UE 6 can be connected to it at any time.The request for the service may include whether the UE 6 uses the service.

[0041] The following is based on reference to Fig. 6 describes a hardware configuration of the edge orchestrator 1 according to the present embodiment. Fig. Fig. 6 is a diagram showing an example of hardware implementing the edge orchestrator 1 according to the embodiment. The edge orchestrator 1 includes, for example, hardware having the Fig. 6, namely, a central processing unit (CPU) 201, a read-only memory (ROM) 202, a random access memory (RAM) 203, an external storage device 204 such as a hard disk drive (HDD), and a communication interface 205. These components are connected to each other via a bus. The CPU 201 is a control circuit that performs all processing and control of the edge orchestrator 1. The ROM 202 and the external storage device 204 store programs such as a boot program, a communication program, and a data analysis program. The RAM 203 is used as the work area of ​​the CPU 201. The communication interface 205 is connected to an external device.

[0042] The functions of the (in Fig.The units of the edge orchestrator 1 (shown in Figure 2) are implemented by software, firmware, or a combination of software and firmware. The software and firmware for implementing each unit of the edge orchestrator 1 are described as programs and stored in the ROM 202 or the external storage device 204. As a result of the CPU 201 reading and executing the above-described programs stored in the ROM 202 or the external storage device 204, the functions of the resource information management unit 11, the mobile network information acquisition unit 12, the policy setting unit 13, and the app usage determination unit 14 of the edge orchestrator 1 are implemented.

[0043] For example, the programs stored in the ROM 202 or the external storage device 204 and described for implementing the units of the edge orchestrator 1 may be made available to a user or the like by storing them in a storage medium such as a compact disc (CD)-ROM or a digital versatile disc (DVD)-ROM, or they may be provided over a network.

[0044] As described above, in the communication system 100 according to the present embodiment, the edge orchestrator 1 changes the usage of each application based on the maximum number of sessions for each UE 6, the RAN 4 to which each UE 6 is connected, and the requirement of each service used by each UE 6, when it is necessary to change the usage of the applications that provide services for each UE 6 connected to the RAN 4. Thus, a communication system capable of simultaneously offering services that exceed the upper limit of the number of concurrently configurable sessions can be implemented.

[0045] The configurations described in the above embodiment are only illustrative and may be combined with other known techniques, and a part of each of the configurations may be omitted or modified without departing from the gist. List of reference symbols

[0046] 1 Edge Orchestrator; 2 Edge Network; 3 WAN; 4 RAN; 5 Core Network; 6 UE; 11 Resource Information Management Unit; 12 Mobile Network Information Acquisition Unit; 13 Policy Setting Unit; 14 App Usage Determination Unit; 21 Edge Server; 31 Cloud Server; 100 Communication System. QUOTES CONTAINED IN THE DESCRIPTION

[0000] This list of documents submitted by the applicant was generated automatically and is included solely for the convenience of the reader. This list is not part of the German patent or utility model application. The DPMA assumes no liability for any errors or omissions. Cited patent literature

[0000] 2011-103567

[0005]

Claims

[1] An orchestrator device for dynamically utilizing one or more applications for at least one edge server and at least one cloud server to provide one or more services to at least one user device, the orchestrator device comprising: an app usage determination unit for, upon detecting a condition requiring a determination of usage of the one or more applications, determining usage of the one or more applications based on: a location of each user device to use the one or more services; a maximum number of sessions that represents an upper limit on the number of sessions that may be set up concurrently for each user device to use the one or more services; and a requirement for the service provided by each application to be used. [2] The orchestrator device of claim 1, wherein the app usage determination unit determines, upon handover of the at least one user device, whether a change in usage of the one or more applications is required and changes the usage if the change is required. [3] The orchestrator device according to claim 1 or 2, wherein the app usage determining unit determines, upon changing the one or more services used by the at least one user device, whether a change in usage of the one or more applications is required, and changes the usage if the change is required. [4] Orchestrator device according to one of claims 1 to 3, comprising: a resource information management unit for managing a network location of each edge server, an amount of communication latency between the at least one user device and each edge server, a usage state and a use state of a resource of each edge server, and a usage state and a use state of a resource of a mobile network; a mobile network information acquisition unit for obtaining location information about the at least one user device and the maximum number of sessions for each user device from the mobile network; and a policy setting unit for adhering to policies relating to the use and modification of the use of the one or more applications, where the app usage determination unit determines the usage of the one or more applications based on the information managed by the resource information management unit, the location information and the maximum number of sessions acquired by the mobile network information acquisition unit, the policies, and the requirements. [5] Communication system comprising: the orchestrator device according to one of claims 1 to 4; and a mobile network for managing the location information and the maximum number of sessions for the at least one user device and for notifying the orchestrator device of the location information and the maximum number of sessions, wherein upon handover of the at least one user device, the mobile network notifies the orchestrator device of the handover of the location information on the at least one user device. [6] An application usage determination method performed by an orchestrator device for dynamically utilizing one or more applications for at least one edge server and at least one cloud server to provide one or more services to at least one user device, the method comprising: a first step of detecting a condition in which a determination of a use of the one or more applications is required; and a second step of determining the use of the one or more applications based on: a location of each user device to use the one or more services; a maximum number of sessions that represents an upper limit on the number of sessions that may be set up concurrently for each user device to use the one or more services; and a requirement of the service provided by each application to be used. [7] Control circuitry for controlling an orchestrator device to dynamically utilize one or more applications for at least one edge server and at least one cloud server to provide one or more services to at least one user device, the control circuitry causing the orchestrator device to perform: a first step of detecting a condition in which a determination of a use of the one or more applications is required; and a second step of determining the use of the one or more applications based on: a location of each user device to use the one or more services; the maximum number of sessions, which represents an upper limit on the number of sessions that may be set up concurrently for each user device to use the one or more services; and a requirement of the service provided by each application to be used. [8] A storage medium storing a control program for an orchestrator device for dynamically utilizing one or more applications for at least one edge server and at least one cloud server to provide one or more services to at least one user device, wherein the control program causes the orchestrator device to execute: a first step of detecting a condition in which a determination of a use of the one or more applications is required; and a second step of determining the use of the one or more applications based on: a location of each user device to use one or more services; the maximum number of sessions, which represents an upper limit on the number of sessions that may be set up concurrently for each user device to use the one or more services; and a requirement of the service provided by each application to be used.

Citation Information

Patent Citations

  • Communication system, communication method and radio communication apparatus

    JP2011103567A

  • Method and system for edge and non-edge networks allocation

    US20210105191A1