COMMUNICATION SYSTEM, COMMUNICATION CONTROL METHOD, AND PROGRAM

The communication system with middleware layers at various network points addresses the challenge of managing IoT network resources by dynamically adjusting transmission timing based on application policies, optimizing resource use across virtual network slices.

JP7586744B2Active Publication Date: 2024-11-19HITACHI LTD
View PDF 6 Cites 0 Cited by

Patent Information

Application Number
JP2021048477
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2021-03-23
Publication Date
2024-11-19
Estimated Expiration
2041-03-23

AI Technical Summary

Technical Problem

In IoT systems with spatially distributed sensors and devices, managing network resources efficiently across multiple applications with varying communication needs and environmental dependencies is challenging, as conventional methods fail to adapt to location-specific traffic patterns and radio wave conditions, leading to inefficient use of limited network and computational resources.

Method used

A communication system with middleware layers at IoT terminals, edge servers, and cloud servers that analyze packet traffic and adjust transmission timing based on application policies, enabling dynamic management of network resources across virtual network slices.

Benefits of technology

This approach allows for efficient use of network resources by dynamically managing transmission timing, preventing resource overcommitment and optimizing bandwidth utilization across multiple applications and locations, thereby enhancing network efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007586744000001
    Figure 0007586744000001
  • Figure 0007586744000002
    Figure 0007586744000002
  • Figure 0007586744000003
    Figure 0007586744000003
Patent Text Reader

Abstract

To provide a communication system and a communication control method, making an effective operation as a network utilization possible.SOLUTION: A network system comprises: one or more IoT terminals; a base station device 10 connected by the IoT terminal; an edge server 30 which selectively receives a packet of a user plane transmitted and received by the base station device; and a cloud server 4 which selectively receives the packet of the user plane transmitted and received by the base station device or the edge server. At least one of the IoT terminal, the edge server, or the cloud server provides a first middleware structured by a software. The first middleware receives an instruction of a policy predetermined on the basis of a traffic analysis result of the packet transmitted by a communication system, receives a transmission instruction of the packet from an application arranged by procuration, adjusts a transmission timing of the packet in accordance with the instructed policy, and relays the transmission instruction to a communication module.SELECTED DRAWING: Figure 4
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to a communication control method in a communication system. [Background technology]

[0002] IoT systems, or the connection of things to the Internet, are expected to continue to develop in the future. In IoT systems, things such as sensors will become information sources, and machine-to-machine communication (M2M) is predicted to increase dramatically. Information transmitted from such things occurs from various locations in space. For example, in large factories and plants, things are placed scattered across a vast site, and large amounts of information is collected from these things.

[0003] In collecting information from such wide areas, using wireless communication is effective in reducing the cost of laying networks. For wireless communication, the standardization organization 3GPP has formulated the 5G standard, and a low-latency, high-capacity communication infrastructure environment is being established.

[0004] With 5G, a single physically integrated wireless network will be used, and multiple applications will be able to divide and use the integrated physical network by creating virtual network slices (NW slices) in accordance with the service level agreements (SLAs) defined for each application.

[0005] Furthermore, advances in device technology have made it possible for even low-cost devices to be equipped with graphics processing units (GPUs), and low-latency, high-capacity communications using 5G will enable large volumes of content information, such as video, to be provided to edge servers close to the site, enabling real-time processing using machine learning that involves advanced judgment.

[0006] As a result, in addition to the cloud that has been used up until now, multi-location computing is now possible, where calculations are performed on devices or edges in locations closer to the site, and the form of applications is also changing. In a multi-location computing environment, applications are not configured as a single monolithic software package, but rather, highly versatile parts are created as common modules that can be used for multiple purposes, and characteristic parts unique to each application are newly created to complete the application, and applications are beginning to transition to a microservice-type application that can handle frequent updates depending on the situation.

[0007] In a conventional configuration consisting of terminals and cloud servers, applications were placed on the cloud server and all information from the terminals was collected in the cloud and processed there. In the new multi-location computing environment, applications will be divided into modules and appropriately placed on terminals, edges, and the cloud, and processing that requires higher responsiveness will be processed in real time at a location close to the site (terminal) via high-speed, low-latency communications such as 5G.

[0008] Modules that make up an application are distributed and deployed from a repository installed in a center (or cloud). However, unlike the cloud, edge computing resources and communications between terminals and edges are realized using finite network resources or by dividing them using technologies such as network slicing. Therefore, when deploying, it is important to configure the network taking into consideration not only the characteristics of the application, but also environmental setting parameters such as how to use the network and how to distribute and allocate functions. Furthermore, for mobile objects, it is necessary to respond to the location where the object moves. However, the application itself should be designed to be deployed quickly and to eliminate environmental dependency, and it is necessary to provide an intermediate layer that grasps the network status and provides the network usage method expected by the application.

[0009] When constructing a NW slice, it is important to deal with the case where limited network resources are exhausted. Patent Document 1 discloses a technology in which, in a configuration of multiple NW slices, communication is performed by determining a priority order according to the communication quality (QoS) of each slice.

[0010] In order to clarify the issues with the conventional technology, we consider two specific use cases.

[0011] In the first use case, we consider an automated guided vehicle (AGV) used in factories, logistics warehouses, etc. AGVs are connected to a management system using wireless communication and are managed by the management system. The operation of an AGV can be broadly divided into four phases. The first phase is to retrieve items from the warehouse, the second phase is to transport the retrieved items, the third phase is to hand over the retrieved materials to the necessary workers, and the fourth phase is to return to the warehouse. Different tasks are performed in each phase. Since the content of communication and the required communication quality change for each phase, the priority should be changed according to the phase, even when viewed from the perspective of the entire network.

[0012] The second use case involves updating software on a production line in a factory. Software is installed on the semi-finished products that flow through the line, and the software may be updated according to the tests required for each process. Even if the wireless communication area is designed to cover the entire factory line, software updates should be performed at a specific process (i.e., location) on the line. If this is not the case, a mismatch will occur in the environment and test content of the downstream process, making the work of the downstream process difficult.

[0013] As in these two cases, the priority of communication depends on the process and location, and it is not sufficient to simply create virtual NW slices according to the SLA defined for the application and divide and use the integrated physical network as in the conventional technology. It is necessary to properly manage the network in conjunction with the environment such as the application's status and location. As already explained, the application should utilize the common parts while separating the functions that the application is trying to realize from the management of the network. A mechanism that mediates between the network and the application is needed between the application and the network management. In that sense, it is insufficient in these use cases to determine the priority only based on the communication quality of each slice that is predetermined, as disclosed in Patent Document 1.

[0014] Next, let us consider how to use networks assuming IoT. It is also important to deal with cases where intermittent and semi-periodic traffic flows. Patent Document 2 discloses a technology that performs semi-permanent scheduling in a wireless network.

[0015] In order to clarify the issues with the conventional technology, let us consider one more specific use case.

[0016] In the third use case, quality information of semi-finished products flowing through the manufacturing process is collected by collecting information from sensors placed at each process on a factory production line. There are several stages of inspection for each process. As products flow on the line at regular intervals, each sensor intermittently transmits numerical data to the center. However, when the number of sensors becomes huge, a large amount of inspection data is aggregated, which generates bursty traffic, causing temporary concentration of processing on the network and receiving side, which causes temporary exhaustion of network or computing resources. In order to manage such periodic traffic, it has been considered effective to allocate slots in advance to suppress the occurrence of temporal communication overlap (or collision).

[0017] However, the management of bursty traffic requires a mechanism that analyzes traffic concentrations through an analysis function that identifies them and automatically avoids them accordingly. However, conventional technologies only provide predetermined slots on the network side, and are insufficient in their response because they cannot handle intermittent operations that are thought to change due to various factors such as sensor placement and line cycles. In addition, other conventional technologies are described as having a network analysis means, but there is no conventional technology that arbitrates transmission timing in such a use case, and the response is considered to be insufficient.

[0018] Let us consider two further use cases for similar traffic moderation functionality that leverages analytics.

[0019] In the fourth use case, traffic congestion is grasped and large data is transmitted during the off-season. In the fourth use case, the application completes the transmission process by making a write request to the middleware that mediates the transmission. The middleware grasps the network status, estimates the off-season for traffic, and transmits data during the off-season.

[0020] The fifth use case is also a case where the radio wave conditions of the terminal are grasped, and a large amount of data is transmitted when the radio wave conditions are good. In the fifth use case, the application completes the transmission process by making a write request to the middleware that mediates the transmission. The middleware grasps the radio wave conditions of the terminal, estimates the terminal's radio wave state, and transmits the data at a good timing.

[0021] As in these two examples, the analysis function can improve the efficiency of network usage in non-urgent communications, but applications should be separated from network management and management of terminal radio wave conditions, etc., and as explained in each use case, a mechanism that mediates between the network and the application is necessary between the application and network management. In that sense, the analysis function alone, as disclosed in Patent Document 3, is insufficient for these use cases.

[0022] Patent Document 4 discloses a mechanism for enabling upstream transmission without a transmission grant, but even if this method is used, it does not solve the use cases introduced so far.

[0023] FIG. 1 is a diagram showing the configuration of a conventional 5G network system, and shows the configuration of a network system consisting of a 5G network, a terminal, an edge server, and a cloud server, as well as a network slice.

[0024] In Fig. 1, terminals 1-1 and 1-2 are connected to a base station device 10 via radio waves. The base station device 10 is also connected to a UPF (User Plane Function) 20. The UPF 20 carries control plane signals that transmit control signals for monitoring connections with terminals and controlling mobility such as handover, and user plane signals that transmit user data. The UPF 20 has a role of routing user plane signals based on predetermined rules, selecting and distributing those to be transferred to an edge server 30. This function allows specific communications to be distributed to the edge server 30 and processed by the edge server 30.

[0025] 1, a network slice 100 constructed by the functions of the UPF 20 is depicted as an image of a clay pipe (a horizontal cylinder). Packets distributed by the UPF 20 reach the edge server 30, where they are processed by a software module in the edge server 30, and some of the application operations are performed. Similarly, it is also possible to construct another network slice 101 including terminals 1-1 and 1-2, thereby providing a virtual environment in which a different application from the above operates.

[0026] The results of processing in the edge server 30 can be fed back to the terminals 1-1 and 1-2 via the network slice 101. In this case, the packets returned by the edge server 30 are returned to the base station device 10 via the UPF 20, and the feedback is transmitted to each of the terminals 1-1 and 1-2. The information sent to the center side by the UPF 20 is input to the UPF 21 on the center side, and the control plane and the user plane and transmitted to the device for which each plane is intended. That is, the control plane signal is transmitted to the 5G core device 50, and the user plane signal is transmitted to the cloud server 40.

[0027] In the cloud server 40, another software module that is part of the application runs, and processes user data based on the transmitted information. In addition, the control plane signals are used for network management in the 5G core device 50. The 5G core device is composed of a collection of multiple functions. The AF (Application Function), NEF (Network Exposure Function), PCF (Policy Control Function), AMF (Access and Mobility management Function), and SMF (Session Management Function) in Fig. 1 show some of them.

[0028] Also, at the bottom of FIG. 1, a network slice 102 including terminals 1-1 and 1-2 is depicted, and this network slice 102 includes terminals 1-1 and 1-2, as well as a network up to cloud server 40.

[0029] FIG. 2 is a diagram showing the configuration of a repository for deploying applications to terminals, edges, and clouds in a conventional network system.

[0030] The dashed arrow extending from the repository, which is a component newly added to FIG. 1, represents the deployment of modules that are part of the application deployed in the terminals 1-1 and 1-2, the edge server 30, and the cloud server 40. The repository 60 is a warehouse that stores the software of modules that constitute the application. If the module is deployed only to the cloud server 40, there is no need to worry about resource management because there are sufficient resources that constitute the network in the cloud server 40. However, when the module is deployed to the edge server 30 and the terminals 1-1 and 1-2, it is necessary to consider that the resources of the 5G wireless communication connecting the terminals 1-1 and 1-2 and the edge server 30 and the wired network connecting the UPF 20 at the site and the UPF 21 at the center are limited, and there is a possibility that the resources will be insufficient depending on the environment and the situation in which other applications are used. Therefore, more appropriate management is required.

[0031] FIG. 3 is a signaling sequence diagram in which an application is deployed from a repository 60 to a terminal 1 and an edge server 30, and then a network configuration is set, in the prior art.

[0032] A message for deployment and software download (1000) transmits a message instructing each node to deploy and the software itself from the repository 60. For example, the terminal 1 performs application deployment for the terminal (2000-2), and the edge server 30 performs application deployment for the edge server (2000-1). The edge server 30 then performs a network configuration operation (2001), analyzes the network requirements required by the application, and transmits a request message to the 5G core device 50 (1001). The result is transmitted as a configuration message to the UPFs 20 and 21 via the SMF (1002, 1003). The configuration message is also transmitted to the base station device 10 and the terminal 1 via the AMF (1004, 1005). Then, a response message is returned from the 5G core device 50 to the edge server 30 (1006), and the configuration of the network is completed.

[0033] Through the above sequence, a network slice is constructed between the terminal and the edge server, and communication 1500 is established. [Prior art documents] [Patent documents]

[0034] [Patent Document 1] JP 2018-056867 A [Patent Document 2] JP 2020-520589 A [Patent Document 3] JP 2020-530703 A [Patent Document 4] JP 2020-504519 A Summary of the Invention [Problem to be solved by the invention]

[0035] In an environment where a large number of sensors and devices are spatially arranged and multiple applications operate for their own purposes, when a single physically integrated wireless network such as 5G is used and multiple applications use it by dividing it into virtual NW slices according to their respective SLAs, it is desirable for applications to transmit data without dependency on the network or other environment. On the other hand, depending on the application, efficient operation of the network can be achieved by transmitting data based on the device's location, the overall network traffic, or the device's radio wave conditions. However, it is difficult for each application to manage the network conditions due to the need to speed up application development.

[0036] In the prior art, a method is disclosed for determining a priority associated with a NW slice in advance, or for allocating slots for intermittent transmission in advance. However, it is difficult to manage temporary surplus resources that cannot be used in a NW slice and arbitrate between slices. Therefore, resources can only be used under the constraints of the SLA of the slice. It is difficult to effectively use the limited computing resources of the edge server 30 and the finite network resources connecting the terminal 1 and the edge server 30. [Means for solving the problem]

[0037] A representative example of the invention disclosed in the present application is as follows: That is, a communication system includes one or more IoT terminals, a base station device to which the IoT terminals are connected, an edge server that selectively receives user plane packets transmitted and received by the base station device, and a cloud server that selectively receives user plane packets transmitted and received by the base station device or the edge server, and a first middleware configured by software is arranged in at least one of the IoT terminals, the edge server, or the cloud server; A second middleware and a third middleware configured with software are disposed in the edge server, the third middleware captures packets transmitted from at least one of the IoT terminal, the edge server, and the cloud server, analyzes traffic from the captured packets, and provides the results of the analysis to the second middleware, the second middleware creates a control policy regarding packet transmission timing in accordance with a policy set by a user based on the results of the analysis of the packets transmitted in the communication system, and instructs the first middleware of the created control policy, The first middleware Policy instructions from the second middleware received, Sent from an application running on the cloud serverReceive a packet transmission instruction on behalf of the other party and adjust the packet transmission timing in accordance with the instructed policy; The edge server To the communication module , and transmits the packet at the adjusted transmission timing. It is characterized by relaying a transmission instruction. Effect of the Invention

[0038] According to one aspect of the present invention, it is possible to efficiently provide a network slice. Problems, configurations, and effects other than those described above will become apparent from the following description of the embodiments. [Brief description of the drawings]

[0039] [Figure 1] FIG. 1 is a diagram illustrating a configuration of a conventional 5G network system. [Diagram 2] FIG. 1 is a diagram illustrating deployment from a repository in a network system of a conventional example. [Diagram 3] FIG. 11 is a signaling sequence diagram in which a network configuration is set after an application is deployed in a conventional example. [Figure 4] FIG. 1 illustrates a configuration of a network system according to a first embodiment. [Diagram 5] A schematic diagram showing packets flowing in a network slice in a conventional example. [Figure 6] A schematic diagram showing packets flowing in a network slice in the first embodiment. [Figure 7] FIG. 11 is a signaling sequence diagram for setting a network configuration after an application is deployed in the first embodiment. [Figure 8] FIG. 11 is a signaling sequence diagram for setting a network configuration after an application is deployed in the first embodiment. [Figure 9] FIG. 11 is a signaling sequence diagram for setting a network configuration after an application is deployed in the first embodiment. [Figure 10]11 is a flowchart of a process executed by a resource control function according to the first embodiment; [Figure 11] FIG. 1 illustrates a first use case of the first embodiment. [Figure 12] FIG. 13 illustrates a second use case of the first embodiment. [Figure 13] FIG. 13 illustrates a third use case of the first embodiment. [Figure 14] FIG. 13 illustrates a fourth use case of the first embodiment. [Figure 15] FIG. 13 illustrates a fifth use case of the first embodiment. [Figure 16] FIG. 11 is a signaling sequence diagram for setting a network configuration after an application is deployed in the second embodiment. [Figure 17] 13 is a flowchart of a process executed by a resource control function according to the second embodiment. [Figure 18] 13 is a flowchart of a database update process executed by a repository according to the second embodiment. [Figure 19] 13 is a flowchart of a response process to a database information request executed by a repository according to the second embodiment. [Figure 20] FIG. 13 is a diagram showing connections between modules when one service is composed of divided modules. [Figure 21] FIG. 1 is a schematic diagram showing a case where there are two services and their priorities are determined. [Figure 22] FIG. 1 is a schematic diagram showing a case where there are two services and their priorities are determined. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0040] <Example 1> A first embodiment of the present invention will now be described.

[0041] Figure 4 is a diagram showing the configuration of a network system of a first embodiment of the present invention, and shows the configuration of a network system including a 5G network, a terminal, an edge server, and a cloud server, and an image of a network slice.

[0042] In Fig. 4, terminals 1-1 and 1-2 are connected to a base station device 10 via radio waves. The base station device 10 is also connected to a UPF (User Plane Function) 20. The UPF 20 carries control plane signals that transmit control signals for monitoring connections with terminals and controlling mobility such as handover, and user plane signals that transmit user data. The UPF 20 has a role of routing user plane signals based on predetermined rules, selecting and distributing those to be transferred to an edge server 30. This function allows specific communications to be distributed to the edge server 30 and processed by the edge server 30.

[0043] 4, the network slice 100 constructed by the function of the UPF 20 is depicted as an image of a clay pipe (a horizontal cylinder). Packets selectively distributed by the UPF 20 reach the edge server 30, where they are processed by a software module in the edge server 30, and some of the application operations are performed. Similarly, it is also possible to construct another network slice 101 including terminals 1-1 and 1-2, and to provide a virtual environment in which a different application than the above operates.

[0044] The results of processing in the edge server 30 can be fed back to the terminals 1-1 and 1-2 via the network slice 101. In this case, the packets returned by the edge server 30 are returned to the base station device 10 via the UPF 20, and the feedback is transmitted to each of the terminals 1-1 and 1-2. The information sent to the center side by the UPF 20 is input to the UPF 21 on the center side, and the control plane and the user planeand transmitted to the destination device of each plane. That is, the control plane signal is transmitted to the 5G core device 50, and the user plane signal is transmitted to the cloud server 40.

[0045] In the cloud server 40, another software module that is a part of the application runs, and processes user data based on the transmitted information. In addition, the control plane signal is used for network management in the 5G core device 50. The 5G core device 50 is composed of a collection of multiple functions.

[0046] Also, at the bottom of FIG. 4, a network slice 102 including terminals 1-1 and 1-2 is depicted, and this network slice 102 includes terminals 1-1 and 1-2, as well as a network up to cloud server 40.

[0047] With reference to FIG. 5, an example in which comprehensive management of packets flowing through multiple slices is effective will be described. FIG. 5 illustrates packets flowing through two network slices 100 and 101. Since the network slices are virtual, packets flowing through the two network slices 100 and 101 flow in a superimposed manner in the actual physical network 110. As can be seen from the figure, if each network slice is considered independent, packets flowing simultaneously will overlap on the time axis. In particular, in an IoT use case based on M2M that reports in synchronization with time, a burst occurs due to an event in which packets flow simultaneously from multiple sensors at a specified time (for example, 0:00).

[0048] Fig. 6 illustrates a state in which the transmission timing of the network slice 101 is shifted. In the case illustrated in Fig. 6, although packets flowing through the two network slices 100 and 101 are superimposed, they are shifted in time, so that no burst occurs in the actual physical network 111. In this way, in order to guarantee the bandwidth defined in the SLA of each network slice, overall control across multiple network slices is required. Control of the entire network is performed at the network layer, and Patent Document 1 discloses a method of determining priority between different network slices based on QoS.

[0049] However, when timing is managed in a network, for example in a protocol that expects a response, such as TCP / IP, if a response delay occurs due to timing adjustment, other effects such as throttling of the bandwidth will occur. For this reason, it is desirable to operate at a layer closer to the application. On the other hand, applications that manage the network become complicated and affect application development, so a mechanism for management at an intermediate layer is desirable.

[0050] The middleware that controls the transmission timing can be placed in various locations. In FIG. 4, middleware 90-1 and 90-2 are placed in the terminal 1, middleware 91 is placed in the edge server 30, and middleware 92 is placed in the cloud server 40. The on-site UPF 20 through which all packets pass mirrors the packets and delivers them to the edge server 30. Another middleware 81 in the edge server 30 captures and analyzes the packets mirrored by the UPF 20, and provides the analysis results to the resource control function 80. The resource control function 80 that arbitrates the transmission timing in cooperation with the results and in cooperation with the middleware 90, 91, and 92 that control the transmission timing is implemented as middleware. Specifically, the resource control function 80 creates a control policy regarding the transmission timing of packets according to a policy set by the user based on the analysis results by the packet analysis middleware 81, and instructs the created control policy to the transmission timing control middleware 90, 91, and 92. The transmission timing control middleware 90, 91, and 92 receive packet transmission instructions from applications of each device (terminal 1, edge server 30, cloud server 40) on behalf of the other devices, adjust the packet transmission timing in accordance with the policy instructed by the resource control function 80, and relay the transmission instructions to the communication module.

[0051] Fig. 7 is a signaling sequence diagram in which an application is deployed from the repository 60 to the terminal 1 and the edge server 30, and then the network configuration is set. The embodiment shown in Fig. 7 is characterized in that a transmission control middleware 90 built into the terminal 1 exchanges messages with a resource control function 80 to perform transmission control.

[0052] A message for deployment and software download (1000) transmits a message instructing each node to deploy and the software itself from the repository 60. For example, the terminal 1 performs application deployment for the terminal (2000-2), and the edge server 30 performs application deployment for the edge server (2000-1). After that, the edge server 30 performs a network configuration operation (2001), analyzes the network requirements required by the application, and transmits a request message to the 5G core device 50 (1001). The result is transmitted as a configuration message to the UPFs 20 and 21 via the SMF (1002, 1003). The configuration message is also transmitted to the base station device 10 and the terminal 1 via the AMF (1004, 1005). Then, a response message is returned from the 5G core device 50 to the edge server 30 (1006), and the network configuration is completed.

[0053] After that, the edge server 30 sends an instruction to adjust the transmission timing to the resource control function 80 by a message including information on the deployed application and connection information of the terminal (1107). The resource control function 80 returns a response message to the instruction (1108). This response message includes a telemetry request to the analysis middleware 81. The analysis middleware 81 installed in the edge server starts a task to analyze packets flowing in the slice. During communication, the terminal 1 sends a message including information related to the communication to the resource control function 80 (1109). The resource control function 80 sends a message including information related to scheduling to the terminal 1 (1110).

[0054] Through the above sequence, a network slice is constructed between the terminal and the edge server, and communication 1500 is established. In communication 1500, the terminal 1 transmits packets based on rules related to scheduling distributed from the resource control function 80. In addition, analysis of the communication 1500 is performed in the analysis middleware 81, and the resulting telemetry 1501 is provided to the resource control function 80. Using the telemetry information, the resource control function 80 transmits a message including information related to scheduling to the terminal 1 as necessary, and updates the scheduling (1110).

[0055] Fig. 8 is a signaling sequence diagram in which an application is deployed from the repository 60 to the terminal 1 and the edge server 30, and then the network configuration is set. The embodiment shown in Fig. 8 is characterized in that the transmission control middleware 91 built into the edge server 30 exchanges messages with the resource control function 80 and performs transmission control.

[0056] A message for deployment and software download (1000) transmits a message instructing each node to deploy and the software itself from the repository 60. For example, the terminal 1 performs application deployment for the terminal (2000-2), and the edge server 30 performs application deployment for the edge server (2000-1). After that, the edge server 30 performs a network configuration operation (2001), analyzes the network requirements required by the application, and transmits a request message to the 5G core device 50 (1001). The result is transmitted as a configuration message to the UPFs 20 and 21 via the SMF (1002, 1003). The configuration message is also transmitted to the base station device 10 and the terminal 1 via the AMF (1004, 1005). Then, a response message is returned from the 5G core device 50 to the edge server 30 (1006), and the network configuration is completed.

[0057] Thereafter, the edge server 30 transmits an instruction to adjust the transmission timing to the resource control function 80 by a message including information on the deployed application and connection information of the terminal (1107). This message includes a telemetry request to the analysis middleware 81. This message causes the analysis middleware 81 installed in the edge server to start a task of analyzing packets flowing in the slice. The resource control function 80 returns a response message (1108).

[0058] During communication, the edge server 30 sends a message including information about the communication to the resource control function 80 (1111). The resource control function 80 sends a message including information about scheduling to the edge server 30 (1112).

[0059] Through the above sequence, a network slice is constructed between the terminal and the edge server, and communication 1500 is established. In communication 1500, the edge server 30 transmits packets based on rules related to scheduling distributed from the resource control function 80. In addition, analysis of the communication 1500 is performed in the analysis middleware 81, and the resulting telemetry 1501 is provided to the resource control function 80. Using the telemetry information, the resource control function 80 transmits a message including information related to scheduling to the edge server 30 as necessary, and updates the scheduling (1112).

[0060] Fig. 9 is a signaling sequence diagram in which an application is deployed from the repository 60 to the terminal 1, the edge server 30, and the cloud server 40, and then the network configuration is set. The embodiment shown in Fig. 9 is characterized in that the transmission control middleware (92) built into the cloud server 40 exchanges messages with the resource control function 80 and performs transmission control.

[0061] A message for deployment and software download (1000) transmits a message instructing each node to deploy and the software itself from the repository 60. For example, the terminal 1 performs application deployment for the terminal (2000-2), and the edge server 30 performs application deployment for the edge server (2000-1). The edge server 30 then performs a network configuration operation (2001), analyzes the network requirements required by the application, and transmits a request message to the 5G core device 50 (1001). The result is transmitted as a configuration message to the UPFs 20 and 21 via the SMF (1002, 1003). The configuration message is also transmitted to the base station device 10 and the terminal 1 via the AMF (1004, 1005). Then, a response message is returned from the 5G core device 50 to the edge server 30 (1006), and the configuration of the network is completed.

[0062] Thereafter, the edge server 30 transmits an instruction to adjust the transmission timing to the resource control function 80 by a message including information on the deployed application and connection information of the terminal (1107). This message includes a telemetry request to the analysis middleware 81. This message causes the analysis middleware 81 installed in the edge server to start a task of analyzing packets flowing in the slice. The resource control function 80 returns a response message (1108).

[0063] During communication, the cloud server 40 sends a message including information about the communication to the resource control function 80 (1113). The resource control function 80 sends a message including information about scheduling to the cloud server 40 (1114). The resource control function 80 also reports the status. messageto the terminal 1 (1115). For example, telemetry 1503 on information such as the location of the terminal 1 and radio wave strength is reported to the edge server 30. A network slice is constructed between the terminal and the cloud server, and communication 1502 is established. In the communication 1502, the cloud server 40 transmits a packet based on the rules on scheduling distributed from the resource control function 80. Furthermore, analysis of the communication 1502 and analysis of the telemetry 1503 from the terminal 1 are performed in the analysis middleware 81, and the resulting telemetry 1501 is provided to the resource control function 80. The resource control function 80 uses the telemetry information to transmit a message including information on scheduling to the cloud server 40 as necessary, and updates the scheduling (1114).

[0064] FIG. 10 is a flowchart of the process executed by the resource control function 80 of the first embodiment.

[0065] First, the resource control function 80 receives an instruction to adjust the transmission timing by a message (1107) including information on the deployed application and connection information of the terminal from the edge server 30 (402). Then, the resource control function 80 transmits a telemetry request (1108) to the analysis middleware 81 together with a response to the instruction (403). During communication, the resource control function 80 receives information on the terminal status report and transmission request (1109) from the terminal 1 as information on the communication (404). The resource control function 80 receives telemetry 1501 (405) and distributes a transmission schedule (1110) according to the policy set in the instruction received in step 402 (406). Since the telemetry 1501 continues, the resource control function 80 collects application evaluation data and evaluates the use of the network by the application (407).

[0066] Next, a use case to which this embodiment can be applied will be described with reference to FIG. 11 to FIG.

[0067] FIG. 11 is a diagram showing a first use case of the first embodiment. In the use case shown in FIG. 11, communication of an automated guided vehicle (AGV) 500 used in a factory, a logistics warehouse, etc. is controlled. The AGV 500 is connected to a management system using wireless communication and is managed by the management system. The operation of the AGV 500 is roughly divided into four phases. First, phase 603 is for taking out an item from the warehouse, second, phase 600 is for transporting the taken out item, third, phase 602 is for handing over the taken out material to a necessary worker, and fourth, phase 601 is for returning to the warehouse. The work performed in each phase is different. Since the communication contents and the required communication quality change for each phase, the priority should be changed according to the phase even when viewed from the entire network.

[0068] In this embodiment, a policy can be set according to the application deployed in FIG. 7 (1107). The policy that is set requires management based on the location of the terminal, and a report including location information is sent to the terminal side in communication 1500, and the edge server 30 reports the location information to the resource control function 80 via telemetry 1501. By associating the location with the phase, the policy can be changed by switching the phase. For example, in the second and fourth phases when the user is moving, the priority is raised and real-time communication control is performed. On the other hand, in the first and third In this phase, the priority may be lowered and other communications may be prioritized. Thus, the problem is solved.

[0069] Fig. 12 is a diagram showing a second use case of this embodiment. In the use case shown in Fig. 12, software is updated on a production line in a factory. Software is installed on semi-finished products 510 flowing on the line, and the software may be updated according to tests required for each process. Even if a wireless communication area 610 is designed to cover the entire factory line, software updates should be performed at a specific process (i.e., location 611) on the line. If this is not the case, a mismatch will occur in the environment and test contents of the subsequent process, making the work of the subsequent process difficult.

[0070] In this embodiment, a policy can be set according to the application deployed in Fig. 9 (1107). For this reason, similarly to the first use case, by collecting information about the location from the terminal 1 (1503) and associating the location with transmission availability in the resource control function 80, a transmission task that is matched with a specific location and activated can be defined, and transmission can be started at the specific location. Thus, the problem is solved.

[0071] FIG. 13 is a diagram showing a third use case of this embodiment. In the use case shown in FIG. 13, information is collected from sensors arranged at each process in a factory production line to collect quality information of semi-finished products flowing through the manufacturing process. Several stages of inspection are provided for each process. As products flow on the line at regular intervals, numerical data is intermittently transmitted from each sensor to the center (530). However, when the number of sensors becomes huge, a large amount of inspection data is aggregated, which causes burst-like traffic, which causes temporary concentration of processing on the network and the receiving side, and causes temporary exhaustion of network or computational resources. In order to manage such periodic traffic, it has been considered effective to try to suppress the occurrence of temporal communication overlap (or collision) by allocating slots in advance.

[0072] However, the management of bursty traffic requires a mechanism that analyzes traffic concentrations through an analysis function that identifies them and automatically avoids them accordingly. However, conventional technologies only provide predetermined slots on the network side, and are insufficient in their response because they cannot handle intermittent operations that are thought to change due to various factors such as sensor placement and line cycles. In addition, other conventional technologies are described as having a network analysis means, but there is no conventional technology that arbitrates transmission timing in such a use case, and the response is considered to be insufficient.

[0073] In this embodiment, a policy can be set (1107) according to the application 520 deployed in FIG. 7. In the set policy, the middleware 81, which monitors and analyzes the network, grasps the network status (540) and automatically adjusts the timing while searching for free space (550). When a new periodic connection request (1109) occurs according to the analysis result by the middleware 81, a message including scheduling information including an appropriate offset is transmitted (1110), so that traffic concentration can be avoided without human intervention. In addition, since the resource control function 80 grasps the situation using the telemetry 1501, it can detect the occurrence of a partial burst, update the scheduling information for correction each time, and feed back the transmission timing of the terminal 1 to the transmission control middleware 90, so that the bias of a specific traffic can be automatically corrected. Thus, the problem is solved.

[0074] Fig. 14 is a diagram showing a fourth use case of this embodiment. In the use case shown in Fig. 14, traffic congestion is grasped and large data is transmitted during the off-season. In the fourth use case, the application completes the transmission process by making a write request to the middleware that mediates the transmission. The middleware grasps the network status, estimates the off-season for traffic, and transmits data during the off-season.

[0075] In this embodiment, a policy can be set according to the application 521 deployed in FIG. 7 (1107). In the policy that is set, the middleware 81 that monitors and analyzes the network grasps the network status and predicts a period of free time. Specifically, a conventional method, for example, the SARIMA method, is used to predict the off-peak period, and the timing of data transmission is automatically adjusted based on the off-peak period prediction result. Then, when the appropriate timing arrives, a message including scheduling information is transmitted (1110). This makes it possible to automatically estimate the off-peak period without any manual effort. Thus, the problem is solved.

[0076] Fig. 15 is a diagram showing a fifth use case of this embodiment. In the use case shown in Fig. 15, the radio wave conditions of the terminal 1 are grasped, and a large amount of data is transmitted when the radio wave conditions are good. In the fifth use case, the application completes the transmission process by making a write request to the middleware that mediates the transmission. The middleware grasps the radio wave conditions of the terminal, estimates the radio wave state of the terminal, and transmits data at a good timing.

[0077] As described above in the second use case, in the sequence of FIG. 9, based on a telemetry instruction (1115) of the radio wave state to the terminal 1, the terminal 1 instructs telemetry 1503 to periodically report the radio wave situation. Based on this information, the resource control function 80 can know the appropriate timing. When the radio wave state continues to be higher than the threshold, the file can be easily updated from the cloud server 40. Thus, the problem is solved.

[0078] As described above, according to the first embodiment, temporary surplus resources that cannot be used in a slice can be managed and arbitrated between slices. Moreover, even if an unused surplus occurs in the limited computing resources of the edge server 30 or in the finite network resources connecting the terminal 1 and the edge server 30 by allowing overcommitment of the SLA of the slice, the NW slice can be efficiently provided.

[0079] <Example 2> A second embodiment of the present invention will be described. The second embodiment differs from the first embodiment in that messages exchanged between the resource control function 80 and the repository 60 are added. In the second embodiment, differences from the first embodiment will be mainly described, and descriptions of the same configurations and functions as the first embodiment will be omitted.

[0080] FIG. 16 is a signaling sequence diagram in which an application is deployed from the repository 60 to the terminal 1 and the edge server 30 and then a network configuration is set in the second embodiment of the present invention.

[0081] A message for deployment and software download (1000) transmits a message instructing each node to deploy and the software itself from the repository 60. For example, the terminal 1 performs application deployment for the terminal (2000-2), and the edge server 30 performs application deployment for the edge server (2000-1). After that, the edge server 30 performs a network configuration operation (2001), analyzes the network requirements required by the application, and transmits a request message to the 5G core device 50 (1001). The result is transmitted as a configuration message to the UPFs 20 and 21 via the SMF (1002, 1003). The configuration message is also transmitted to the base station device 10 and the terminal 1 via the AMF (1004, 1005). Then, a response message is returned from the 5G core device 50 to the edge server 30 (1006), and the network configuration is completed.

[0082] After that, the resource control function 80 receives an instruction to adjust the transmission timing from the edge server 30 by a message including information on the deployed application and connection information on the terminal (1107). Prior to this, the resource control function 80 receives policy information for each application from the repository 60 through regular communication with the repository 60 (1200, 1201). For example, the resource control function 80 requests update information for a table from the repository 60, and the repository 60 returns the update information to the resource control function 80. The resource control function 80 also receives the analysis results of the analysis middleware 81 (1501), reports the results to the repository 60 (1202), and receives a response (1203). Through this series of procedures, the resource control function 80 can change the policy based on the trends among multiple locations where the same application is used.

[0083] FIG. 17 is a flowchart of the process executed by the resource control function 80 of the second embodiment.

[0084] First, the resource control function 80 periodically communicates with the repository 60 to receive application-specific configurations stored in the database (401). Next, the resource control function 80 receives instructions to adjust the transmission timing from the edge server 30 by a message (1107) including information on the deployed application and terminal connection information (402). Then, the resource control function 80 transmits a telemetry request (1108) to the analysis middleware 81 together with a response to the instruction (403). During communication, the resource control function 80 receives a terminal status report and transmission request information (1109) from the terminal 1 as information related to the communication (404). The resource control function 80 receives the telemetry 1501 (405) and distributes a transmission schedule (1110) according to the policy set in the instruction received in step 402 (406). Since the telemetry 1501 continues, the resource control function 80 collects application evaluation data and evaluates the network usage by the application (407). The resource control function 80 feeds back the evaluation results to the repository 60 with which it periodically communicates (408).

[0085] FIG. 18 is a flowchart of the database update process executed by the repository 60 of the second embodiment.

[0086] The repository 60 receives evaluation results from resource control functions 80 individually arranged at multiple bases (421) and accumulates the results in a database (422). After a predetermined period of time, the repository 60 analyzes the database. For example, it is possible to adjust parameters in priority ratings and scheduling, and to generalize responses to changes in application linkages. Specifically, rather than responding to an individual environment, it is possible to reflect the analysis results of the database across all related bases in response to changes such as an increase in data transmission volume due to an application update. Thus, the problem is solved.

[0087] FIG. 19 is a flowchart of a process for responding to a database information request, which is executed by the repository 60 in the second embodiment.

[0088] As shown in the figure, the repository 60 reads out information on related applications from the database in response to a data analysis request from each site, and repeats the procedure of responding to the resource control function 80 of the requested site.

[0089] <Example 3> In the third embodiment of the present invention, a policy is set in advance, and communications are automatically prioritized based on rules.

[0090] FIG. 20 is a diagram showing the relationship between modules when one service is composed of a plurality of divided modules 200 to 208.

[0091] The communication from the module 203 to the next module 206 and module 204 is wireless communication. The resources of wireless communication are limited, and the line bandwidth is narrower than other communication paths. When comparing the communication from the module 203 to the module 206 with the communication from the module 203 to the module 204, the path via the module 204 has more modules. If the module 207 cannot transmit the processing result to the final module 208 unless data arrives from both the path from the module 206 and the path from the module 204, the path from the module 203 to the module 204 should be given priority in transmitting data, and the overall delay should be suppressed. Such a judgment can also be made by the network analysis middleware 81, which grasps the topology of the modules, and determines the priority order based on the topology. Thus, the problem is solved.

[0092] 21 and 22 are schematic diagrams showing two services and how their priorities are determined. In the case shown in FIG. 21, the communication from module 210 to module 211 is wireless communication. However, the results of processing in module 211 are transmitted to multiple modules 212 and 213. In the case shown in FIG. 22, the communication from module 214 to module 215 is wireless communication. Comparing these two, the configuration in FIG. 21 can be understood as an application with a large impact because data transmitted wirelessly is used for multiple purposes. Such a judgment can also be made by grasping the topology of the modules in the network analysis middleware 81, and determining the priority order based on the topology. Thus, the problem is solved.

[0093] In this way, even when configuring complex microservices, priorities can be determined by assigning simple rules.

[0094] The present invention is not limited to the above-described embodiments, and includes various modified examples and equivalent configurations within the spirit of the appended claims. For example, the above-described embodiments have been described in detail to clearly explain the present invention, and the present invention is not necessarily limited to those including all of the configurations described. Furthermore, a part of the configuration of one embodiment may be replaced with the configuration of another embodiment. Furthermore, the configuration of another embodiment may be added to the configuration of one embodiment. Furthermore, a part of the configuration of each embodiment may be added, deleted, or replaced with another configuration.

[0095] In addition, each of the above-mentioned configurations, functions, processing units, processing means, etc. may be realized in hardware, for example by designing some or all of them as an integrated circuit, or may be realized in software by a processor interpreting and executing a program that realizes each function.

[0096] Information such as programs, tables, and files that realize each function can be stored in a storage device such as a memory, a hard disk, or an SSD (Solid State Drive), or in a recording medium such as an IC card, an SD card, or a DVD.

[0097] In addition, the control lines and information lines shown are those considered necessary for the explanation, and do not necessarily show all the control lines and information lines necessary for implementation. In reality, it can be considered that almost all components are connected to each other. [Explanation of symbols]

[0098] 1. Terminal 10...Base station equipment 20...1st UPF 21...Second UPF 30 Edge Server 40 Cloud Server 50 5G core equipment 60···Repository 80 Resource control function 81. Analysis middleware 90 Terminal side transmission control middleware 91 Edge server side transmission control middleware 92 Cloud server side transmission control middleware 100, 101, 102... network slices

Claims

1. 1. A communication system comprising: One or more IoT devices; A base station device to which the IoT terminal is connected; an edge server that selectively receives user plane packets transmitted and received by the base station device; a cloud server that selectively receives user plane packets transmitted and received by the base station device or the edge server, a first middleware configured by software is disposed in at least one of the IoT terminal, the edge server, or the cloud server; a second middleware and a third middleware configured as software are disposed in the edge server; The third middleware captures packets transmitted from at least one of the IoT terminal, the edge server, and the cloud server, analyzes traffic from the captured packets, and provides a result of the analysis to the second middleware; the second middleware creates a control policy regarding a packet transmission timing in accordance with a policy set by a user based on a result of an analysis of a packet transmitted in the communication system, and instructs the first middleware of the created control policy; The first middleware includes: receiving an instruction of the policy from the second middleware; Receive, on behalf of the application running on the cloud server, a transmission instruction for a packet transmitted from the application; Adjusting packet transmission timing according to the specified policy; a communication module of the edge server, which relays a transmission instruction for transmitting the packet at the adjusted transmission timing;

2. A communication system as claimed in claim 1, a first demultiplexing device connected to the base station device and configured to selectively demultiplex the packets and transmit the packets to the edge server; A communication system comprising: a second demultiplexing device connected to the first demultiplexing device, selectively demultiplexing the packets and transmitting the packets to the cloud server.

3. A communication system as claimed in claim 1, The first middleware disposed in the IoT terminal includes: Detecting the strength or location information of the radio wave of the base station device received by the IoT terminal, reporting the detected radio wave intensity or location information to the second middleware; A communication system, characterized in that the second middleware creates the control policy based on the reported radio wave strength or location information.

4. A communication system as claimed in claim 1, A repository is provided in which modules constituting the application are stored and which deploys the modules to the IoT terminal, the edge server, or the cloud server; The second middleware creates the control policy in accordance with individual settings associated with the application configured by modules deployed from the repository.

5. A communication system as claimed in claim 1, A communication system characterized in that the second middleware creates the control policy based on a predicted value of the analysis result by the third middleware, location information of the IoT terminal, or radio wave strength of the IoT terminal.

6. A communication control method in a communication system, comprising: The communication system includes one or more IoT terminals, a base station device to which the IoT terminals are connected, an edge server that selectively receives user plane packets transmitted and received by the base station device, and a cloud server that selectively receives user plane packets transmitted and received by the base station device or the edge server, At least one of the IoT terminal, the edge server, or the cloud server is provided with a first middleware and a resource control function configured with software; a second middleware and a third middleware configured as software are disposed in the edge server; The communication control method includes: The third middleware captures a packet transmitted from at least one of the IoT terminal, the edge server, and the cloud server; the third middleware analyzes traffic from the captured packets; the third middleware providing a result of the analysis to the second middleware; the second middleware creates a control policy regarding a packet transmission timing in accordance with a policy set by a user based on a result of an analysis of a packet transmitted in the communication system; the second middleware instructs the first middleware of the created control policy; the first middleware receives from the resource control function an instruction of a policy determined based on a result of an analysis of traffic transmitted in the communication system; the first middleware receives, on behalf of the application running on the cloud server, a transmission instruction for a packet transmitted from the application; The first middleware adjusts a packet transmission timing according to the specified policy; The communication control method, wherein the first middleware relays a transmission instruction to a communication module of the edge server to transmit the packet at the adjusted transmission timing.

7. A program for controlling communication in a communication system, comprising: The communication system includes one or more IoT terminals, a base station device to which the IoT terminals are connected, an edge server that selectively receives user plane packets transmitted and received by the base station device, and a cloud server that selectively receives user plane packets transmitted and received by the base station device or the edge server, An application is placed on the cloud server, The program is Capture a packet transmitted from at least one of the IoT terminal and the cloud server; analyzing traffic from the captured packets; creating a control policy for packet transmission timing according to a policy set by a user based on a result of the analysis of the transmitted packets; generating policy instructions based on results of a traffic analysis of packets transmitted in the communication system; receiving, on behalf of the application, a transmission instruction for a packet transmitted from the application; adjusting packet transmission timing according to the created policy; and a procedure of relaying a transmission instruction for transmitting the packet at the adjusted transmission timing to a communication module of the edge server.

Citation Information

Patent Citations

  • Communication system and communication method

    JP2018056867A

  • Signaling cached segments for broadcast

    JP2018524882A

  • Cloud system, cloud server, edge server and user device

    JP2019135578A

  • Method and apparatus for performing uplink transmission in a wireless communication system

    JP2020504519A

  • Semi-persistent scheduling in wireless networks

    JP2020520589A