KR102054997B1 - Method and apparatus for providing service of multiple portable infrastructures - Google Patents

Abstract

This embodiment provides a service providing method and apparatus therefor that can provide more various services by sharing service resources through a connection between a plurality of mobile infrastructure devices.

Description

METHOD AND APPARATUS FOR PROVIDING SERVICE OF MULTIPLE PORTABLE INFRASTRUCTURES}

The present invention relates to a service providing method and apparatus therefor for a plurality of mobile infrastructures, and more particularly, to a method and an apparatus capable of providing more various services by sharing service resources between a plurality of mobile infrastructure devices.

The 4G mobile communication system currently in service uses a frequency band below 6 GHz and has a transmission capacity of up to 1 Gbps. However, the demand for wireless data traffic, which has more than doubled every year, is expected to be difficult to satisfy by simple structural expansion of 4G mobile communication systems. As a solution, 5G mobile communication systems are being actively developed.

The 5G mobile communication system is a next generation mobile communication method using an ultra-high frequency (mmWave) band (eg, 60 GHz band). Although 5G mobile communication systems have not yet been decided on technical specifications, requirements are defined as ultra-fast / low latency, reliability / security of 99% or more, and system cost reduction. The 5G mobile communication system has an advantage that it is easy to secure a continuous wide bandwidth of at least 500MHz and can transmit data at high speed.

On the other hand, in order to meet the demand for mobile communication services that are rapidly increasing in a specific area due to the occurrence of special events such as festivals or disasters, mobile infrastructure devices are usefully utilized. In particular, in the present situation where it is expected that considerable cost and time will be required to spread the 5G mobile communication system nationwide, the mobile infrastructure device may be usefully used to provide the 5G mobile communication system.

However, due to the limited number of operations and service resources of the mobile infrastructure device, the current service providing method has a problem in that it is difficult to meet all the service demands under special circumstances.

In order to solve such a problem, the present embodiment provides a service providing method and an apparatus therefor that can extend a service resource of a mobile infrastructure device.

According to an aspect of the present embodiment, in a method of providing a service by a mobile infrastructure device, in response to a service request of a user terminal, another available mobile infrastructure having service resources required for providing the requested service is provided. Searching for a device; Selecting at least one mobile infrastructure device from the discovered mobile infrastructure devices; Configuring a service resource pool by sharing the service resource through interconnection with the selected mobile infrastructure device; And providing the requested service from the service resource pool.

According to another aspect of the present embodiment, a method for providing a service by a mobile infrastructure device, the method comprising: requesting an allocation of another available mobile infrastructure device to a control center in response to a service request of a user terminal; In response to the allocation request, allocating at least one mobile infrastructure device having service resources necessary for providing the requested service from the control center; Configuring the service resource pool by sharing the service resource by interconnection with the assigned mobile infrastructure device; And providing the requested service from the service resource pool.

According to another aspect of the present embodiment, in the mobile infrastructure device, in response to the service request of the user terminal, a service request for determining the connection with another mobile infrastructure device, if the service resources required for the provision of the requested service is insufficient. Processing unit; An infrastructure search unit for searching for an available mobile infrastructure device having the service resource according to the connection determination; An infrastructure selecting unit configured to select at least one mobile infrastructure device from the found available mobile infrastructure devices; A connection unit connecting the selected mobile infrastructure device with the mobile infrastructure device using a connection resource connected with a network function module; And a service resource management unit configured to share a service resource with the connected mobile infrastructure device to configure a service resource pool.

According to yet another aspect of the present embodiment, in the mobile infrastructure device, in response to a service request from a user terminal, requesting allocation of another mobile infrastructure device to a control center when there is insufficient service resources necessary for providing the requested service. A service request processor; A connection unit for connecting at least one mobile infrastructure device allocated by the control center to the mobile infrastructure device using a connection resource connected to a network function module in response to the allocation request; And a service resource management unit configured to share a service resource with the connected mobile infrastructure device to configure a service resource pool.

According to the present embodiment, a plurality of mobile infrastructure devices are interconnected to form a service resource pool, thereby providing a variety of services quickly.

1 is a view schematically showing a mobile infrastructure system according to the present embodiment.
2 is a diagram illustrating a mobile infrastructure device according to the present embodiment.
3 is a diagram illustrating a configuration of a mobile infrastructure device according to an aspect of the present embodiment.
4 is a diagram schematically illustrating a connection type between mobile infrastructure devices according to the present embodiment.
5 is a view showing the configuration of a control center according to an aspect of the present embodiment.
6 is a flowchart illustrating a service providing process through connection between mobile infrastructure devices according to an embodiment of the present embodiment.
7 is a flowchart illustrating a process of sharing a service resource according to the present embodiment.
8 is a view showing the configuration of a mobile infrastructure device according to another aspect of the present embodiment.
9 is a flowchart illustrating a service providing process through connection between mobile infrastructure devices according to another aspect of the present embodiment.

Hereinafter, some embodiments of the present invention will be described in detail through exemplary drawings. In adding reference numerals to the components of each drawing, it should be noted that the same reference numerals are assigned to the same components as much as possible even though they are shown in different drawings. In addition, in describing the present invention, when it is determined that the detailed description of the related well-known configuration or function may obscure the gist of the present invention, the detailed description thereof will be omitted.

In addition, in describing the component of this invention, terms, such as 1st, 2nd, A, B, (a), (b), can be used. These terms are only for distinguishing the components from other components, and the nature, order or order of the components are not limited by the terms. Throughout the specification, when a part is said to include, 'include' a certain component, which means that it may further include other components, except to exclude other components unless otherwise stated. . In addition, as described in the specification. The term 'module' refers to a unit that processes at least one function or operation, which may be implemented by hardware or software or a combination of hardware and software.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

In the present embodiment, the mobile communication service is a service for providing voice, video, data, etc., and may be provided based on various mobile communication standards and mobile communication technologies. For example, the mobile communication service according to the present embodiment includes WCDMA mobile communication service and CDMA2000 mobile communication service according to 3G mobile communication standard, HSDPA mobile communication service and LTE mobile communication service according to 3.9G mobile communication standard, and 4G mobile communication. LTE-A mobile communication service according to the standard and may include mobile communication services provided by 5G mobile communication. In the present specification, the present embodiment will be described on the premise of a mobile infrastructure system that provides a 5G mobile communication service. However, it should be noted that this is for convenience of description only and does not limit the embodiments of the present invention.

1 is a view schematically showing a mobile infrastructure system according to the present embodiment.

Referring to FIG. 1, the mobile infrastructure system 100 may include a mobile infrastructure device 110 and a control center 130.

The mobile infrastructure device 110 refers to a device that is provided with all functions and services of a control plane and a user plane defined in the 5G network standard, thereby providing a mobile communication service. In addition, the mobile infrastructure device 110 may be installed and operated at one mobile site to provide a simple mobile communication service, support an access network or core network connection, or even perform a function of a content server. It means an independent type of E2E (End-to End) service providing apparatus.

The mobile infrastructure device 110 is a device equipped with all the modules used for providing a mobile communication service, and may be implemented in the form of a mobile body such as a vehicle. 1 illustrates a mobile infrastructure device 110 implemented in the form of a vehicle, but this is exemplary and the present embodiment is not limited thereto.

The mobile infrastructure device 110 may be connected to an external content server, a control center, or the like as needed to provide a mobile communication service. Here, the external network may include a backhaul network (eg, wireless LTE backhaul, wired optical backhaul, etc.), a wireless network (eg, WiFi, LTE, etc.) or a wired network, and the location or request of the mobile infrastructure device 110. It may optionally support connection with the outside according to the type of service.

The control center 130 may control and manage the mobile infrastructure device 110 connected through the external network. For example, the control center 130 may monitor the current location and communication status of the plurality of mobile infrastructure devices 110, and allocate at least one infrastructure device 110 to a specific area that needs to provide a mobile communication service. Can be.

In summary, the mobile infrastructure device 110 may be used independently or under the control of the control center 130 in various areas such as an area where a mobile communication system is not constructed or a mobile communication service request is excessively generated. Mobile communication services can be provided.

2 is a diagram illustrating a mobile infrastructure device according to the present embodiment.

Referring to FIG. 2, the mobile infrastructure device 110 may include all network function modules of a control plane and a user plane defined in the 5G network standard. In this case, each network function module may be divided into hardware and / or software and implemented as an independent module. A brief summary of the performance functions of the network function module shown in FIG. 2 is given in Table 1.

Network function module
Perform function NSSF (Network Slice Selection Function) Network Slice Selection Function Network Exposure Function (NEF) Network exposure function NF Repository Function Registration and search function for mutual network discovery and communication Policy Control Function (PCF) Policy control function corresponding to network slice Unified Data Management (UDM) Storage and management of subscriber data and profile information AF (Application Function) Application management function Authentication Server Function (AUSF) Authentication function AMF (Access and Mobility Management Function) Access control and mobility management, network slice selection Session Management Function (SMF) Subscriber session setup and management function according to network policy UE (User Equipment) User terminal (R) AN ((Radio) Access Network) Wireless access network UPF (User Plane Function) Establish data traffic delivery according to service type in user plane DN (Data Network) External data network

The plurality of network function modules listed in Table 1 may be interconnected through a plurality of interfaces such as N1, N2, and N4 to transmit and receive information. In addition, the mobile infrastructure device 110 uses NRFs and NEFs corresponding to the core network to share information on an external management plane, for example, a control center and the network, thereby promoting efficient device operation. can do.

As such, the mobile infrastructure device 110 may include various network function modules that perform functions of an access network and a core network. In addition, the mobile infrastructure device 110 may provide a mobile communication service requested by the user terminal 130 from a content server connected directly or through an external network through various network function modules.

Next, the mobile infrastructure device 110 may include a connection resource. Here, the connection resource is used to connect various network functions of the mobile infrastructure device 110 with a separate external network or another mobile infrastructure device 110 as well as a data network (DN), which is a typical external network in the infrastructure. The interface may include all radio resources (eg, WiFi, Bluetooth, LTE, 5G, etc.) and wired resources. The connection resource may be implemented as a kind of physical or virtual port, and may selectively support the connection with the outside according to the location of the mobile infrastructure device 110 or the type of the requested service.

The mobile infrastructure device 110 according to the present embodiment may be connected to another mobile infrastructure device 110 through a connection resource to share a service resource, thereby providing a mobile communication service.

Hereinafter, a service providing method through connection between mobile infrastructure devices according to an embodiment of the present invention will be described in detail with reference to FIGS. 3 to 8.

FIG. 3 is a diagram illustrating a configuration of a mobile infrastructure device according to an aspect of the present embodiment, and FIG. 4 is a diagram schematically illustrating a connection type between mobile infrastructure devices.

Referring to FIG. 3, the mobile infrastructure device 110 may include a service resource manager 310, a service request processor 330, a connector 350, and a storage 370. However, this is only a component of 'service providing operation through the connection between mobile infrastructure devices' performed by the mobile infrastructure device 110 for convenience of description. Therefore, although not directly shown in the drawings, the mobile infrastructure device 110 may further include components for controlling overall operations of the mobile infrastructure device 110.

The service resource manager 310 may monitor and manage service resources of the mobile infrastructure device 110. Here, the service resource means a content resource (eg, a video file), a connection required for providing data traffic related services such as a web / internet service, augmented reality (AR) / virtual reality (VR) streaming service, and a voice recognition service. Resources (eg, 5G, LTE, WiFi, etc.), equipment resources (eg, CPU, memory, storage, etc.) and radio resources (eg, 5G Radio Unit, etc.) may all include. In addition, the service resource may include setting and configuration information (eg, resource allocation scheduling information, etc.) for various resources required for providing an end-to-end service.

In detail, the service resource manager 310 may monitor the type, capacity, and state of a service resource held by the mobile infrastructure device 110. For example, if the mobile infrastructure device 110 provides a real-time VR streaming service using a video file stored in the storage, the size of the video file (for example, 100 GB) and the storage capacity (for example, 1 TB in total) 0.5 TB available), service rates (eg 1,000 Mb / s) and more.

In addition, when the mobile infrastructure device 110 is connected to another mobile infrastructure device 110, the service resource management unit 310 shares service resources of both devices under the control of the connection unit 350, which will be described later. Can be extended.

For reference, in the present specification, the mobile infrastructure device 110 that accepts the service request is referred to as a master mobile infrastructure device, and the other mobile infrastructure device 110 connected thereto is referred to as a slave mobile infrastructure device. However, this is only for convenience of description, and it should be noted that the master mobile infrastructure device and the slave mobile infrastructure device do not have a major relationship. That is, the master and the slave may be different according to the subject who accepts the service request, and the plurality of mobile infrastructure devices 110 may provide their own services even during the interconnection.

The sharing scope of service resources may be a part of service resources (eg, depending on the type or capacity of service resources required and the connection state between mobile infrastructure devices (eg, latency, jitter, bandwidth, etc.). : Some video data and setting data) or all (for example, all data required for VR streaming service).

If necessary to provide a service, the service resource manager 310 may change the sharing range of the service resource under the control of the service request processor 330 to be described later. For example, the service resource manager 310 may further share the LTE connection resource in order to provide an LTE service while sharing the 5G connection resource of the slave mobile infrastructure device. Alternatively, the service resource management unit 310 may release the sharing of storage resources of the completed portion when the service is partially provided while all the storage resources of the slave mobile infrastructure device are shared to provide the real-time AR streaming service. have.

The service resource manager 310 may configure a service resource pool using service resources of the master and slave mobile infrastructure devices. According to the present embodiment, the service resource information regarding the type, capacity, etc. of the service resources included in the service resource pool may be stored in a table form in the storage unit 370 to be described later.

A specific example of the service resource pool information table is shown in Table 2. However, since the contents of Table 2 are exemplary, it should be noted that the present embodiment is not limited thereto.

infra-01 index resourece ID capacities
(total / available) service schedule allocation
priority
(rank) sharing info One E-S001
(storage # 1) 10 TB / 3 TB a. 2 TB for service # 1
(VR streaming) a. rank # 1 infra-02
3TB for master service # 3
(AR streaming) 2 E-S002
(storage # 2) 20 TB / 18 TB NULL NULL NULL 3 E-M001
(memory # 1) 64GB / 30GB a. 5GB for service # 2
(AR streaming)
b. 10 GB for
service # 1
(VR streaming) a. rank # 2


b. rank # 1 a. NULL


b. infra-02
3GB for master service # 3
(AR streaming) .
.
. .
.
. .
.
. .
.
. .
.
. .
.
.

Referring to Table 2, Storage Resource 1 (E-S001) of Mobile Infrastructure Device 1 (infra-01) is (1) 10 TB total capacity and 3 TB usable capacity, and (2) VR streaming service (service # 1). 2 TB is allocated as the first priority (rank # 1), and (3) it is connected to the master mobile infrastructure device 2 (infra-02) to share the 3 TB to provide the AR streaming service (service # 3).

Storage resource 2 (E-S002) of mobile infrastructure device 1 (infra-01) is (1) 20 TB of total capacity and 18 TB of usable capacity, and (2) it is idle.

Memory resource 1 (E-M001) of mobile infrastructure device 1 (infra-01) is (1) 64 GB total capacity and 30 GB available capacity, and (2) second priority for providing AR streaming service (service # 2). 5 GB is allocated as a rank (rank # 2), (3) 10 GB is allocated as the first priority (rank # 1) to provide VR streaming service (service # 1), and (4) AR streaming service (service # 3). 3 GB shared with Master Portable Infrastructure Device 2 (infra-02) to provide

For reference, the priority may be set by the service request processor 330, which will be described later, in consideration of a weight factor, a workload, and the like based on the performance of each service resource.

Hereinafter, a detailed connection form between the mobile infrastructure devices will be described with reference to FIG. 4.

Referring to FIG. 4, the master mobile infrastructure device and the slave mobile infrastructure device may be connected in various forms such as '1: 1', '1: n', and 'n: m'. As described above, the master infrastructure device refers to a mobile infrastructure device that accepts a service request, and the slave mobile infrastructure device refers to a mobile infrastructure device connected thereto. In addition, since the connection form shown in FIG. 4 is exemplary, it should be noted that the present embodiment is not limited thereto.

4A illustrates the simplest form of connection in which mobile infrastructure devices are connected '1: 1'.

4B to 4E illustrate four types of connection in which mobile infrastructure devices are connected by '1: n'. Specifically, b of FIG. 4 is a line topology, c of FIG. 4 is a star topology, d of FIG. 4 is a tree topology, and e of FIG. 4 is a ring topology. 4 f shows the mesh topology.

In addition, the mobile infrastructure devices may be connected in a 'n: m' form by combining one or more connection types shown in FIGS. 4A to 4E.

3, the rest of the configuration of the mobile infrastructure device according to the aspect of the present embodiment will be described.

The service request processing unit 330 determines whether the requested service can be provided from the current service resource pool (that is, the total service resources of the master and the slave mobile infrastructure devices already connected), thereby providing the requested service or other infrastructure. You can decide to do any of the connections with resources.

Specifically,

If the requested service can be provided from the current service resource pool, the service request processing unit 330 may set the priority of the requested service and thus provide the requested service. Here, the priority may be set in consideration of a weight factor and a workload based on the performance of each service resource.

If it is necessary to extend the resource sharing range with the slave mobile infrastructure device already connected to provide the requested service, under the control of the service request processing unit 330, the service resource management unit 310 performs an additional service resource sharing process. can do. As a result, since the range of available resources in the current service resource pool is expanded, the service request processing unit 330 may provide the requested service.

If the requested service cannot be provided from the current service resource pool, the service request processor 330 may transmit service resource information necessary for the control center 130 to request allocation of the slave mobile infrastructure device.

In response, the control center 130 may search for available mobile infrastructure devices and assign at least one of the discovered devices to the master mobile infrastructure device. In addition, the service resource management unit 310 may perform a service resource sharing process with the assigned slave mobile infrastructure device. Here, specific contents of the service resource sharing process will be described later with reference to FIG. 7. As a result, since the range of the current service resource pool and the available resources is expanded, the service request processing unit 330 can provide the requested service.

The connection unit 350 may perform a connection operation with a slave mobile infrastructure device by selectively using the plurality of connection resources described above with reference to FIG. 2. In detail, the connection unit 350 may set a connection condition by using information such as a current location, a moving speed, and a connection resource type of the slave mobile infrastructure device. Here, the connection conditions may refer to the distance between mobile infrastructure devices (e.g. 10 m or less), moving speed (e.g. 30 km / h), connection resource type and speed (e.g. WiFi-200Mb / s, 5G-1000Mb / s) It may include. In addition, the connection unit 350 may perform a connection operation with the slave mobile infrastructure device according to the set connection condition.

When the master and slave mobile infrastructure devices are interconnected, the connection unit 350 may notify the service resource management unit 310 to control sharing of service resources for providing a service. In response, the service resource manager 310 may expand the service resource of the master mobile infrastructure device by sharing the service resource of the slave mobile infrastructure device.

The storage unit 370 may include a memory device in which the aforementioned service resource information table is stored. The memory device may be a volatile memory device such as a dynamic random access memory (DRAM) or the like and / or a nonvolatile memory device such as a flash memory.

In summary, the mobile infrastructure device 110 may provide the requested service on its own or through a connection with a slave mobile infrastructure device.

5 is a view showing the configuration of a control center according to an aspect of the present embodiment.

Referring to FIG. 5, the control center 130 may include an infrastructure search unit 510, an infrastructure selecting unit 530, an infrastructure control unit 550, and a storage unit 570. However, this is only for illustrating the control and management operations of the mobile infrastructure device performed by the control center 130 as a component for convenience of description. Accordingly, although not directly shown in the drawings, the control center 130 may further include components for controlling the overall operation of the control center 130.

The infrastructure search unit 510 may search for a plurality of mobile infrastructure devices and collect mobile infrastructure device information. In detail, the infrastructure search unit 510 may be connected to a plurality of mobile infrastructure devices through a connection resource and an external network to collect current location, communication status, service resource information, etc. of each of the plurality of mobile infrastructure devices.

According to the present embodiment, the collected mobile infrastructure device information may be stored in a table form in the storage unit 370 which will be described later. A specific example of the mobile infrastructure device information table is shown in Table 3. However, since the content of Table 3 is illustrative, it should be noted that the present embodiment is not limited thereto.

index infra ID current location
(latitude, longitude) state of
communication service resource info One infra-01 (36.0123260,128.4307890) busy mode [storage]
a. E-S001: 10 TB / 3 TB
b. E-S002: 20 TB / 18 TB
[memory]
a. E-M001: 64 GB / 30 GB
[core]
.
.
. 2 infra-02 (151.0123260,138.4307890) idle mode [storage]
a. E-S001: 10 TB / 3 TB
b. E-S002: 20 TB / 18 TB
[memory]
a. E-M001: 64 GB / 30 GB
[core]
.
.
. .
.
. .
.
. .
.
. .
.
. .
.
.

In Table 3, the current position (latitude / longitude coordinates), communication state, and service resource information of the mobile infrastructure device 1 (infra-01) and the mobile infrastructure device 2 (infra-02) discovered by the infrastructure search unit 510 ( Type, capacity).

The infrastructure search unit 510 may re-collect the mobile infrastructure device information and update the mobile infrastructure device information table at predetermined intervals or when there is a slave mobile infrastructure device allocation request.

The infrastructure selecting unit 530 may select at least one of the available mobile infrastructure devices as the slave mobile infrastructure device in response to the slave infrastructure device allocation request. For example, the infrastructure selecting unit 530 is a device that holds the service resources required by the master mobile infrastructure device and moves to connect with the master mobile infrastructure device until the service is provided, and has the largest available resource capacity. Alternatively, the mobile infrastructure device closest to the master mobile infrastructure device may be selected as the slave mobile infrastructure device. Here, the selection criteria of the slave mobile infrastructure device may include the type of service requested, the communication status (for example, latency, jitter, bandwidth, etc.), and the operation status of the mobile infrastructure device (for example). Number of devices, allocation area, etc.) or service requirements (e.g., system operation policies, user quality indicators, etc.).

The infrastructure controller 550 may transmit a connection control signal to the master and slave mobile infrastructure devices, respectively. The connection control signal may include necessary service resource information, ID information of the master mobile infrastructure device, destination information, path information, and the like. Here, the destination is a place that can be connected to the master mobile infrastructure device, the current position, the moving speed, the communication state (eg, wireless condition, bandwidth (B / W), latency) of each of the master and slave mobile infrastructure devices ), And the like.

The slave mobile infrastructure device may move to the destination based on the received connection control signal and perform a connection operation with the master mobile infrastructure device.

The storage unit 570 may include a memory device in which the above-described mobile infrastructure device information table is stored. The memory device may be a volatile memory device such as a dynamic random access memory (DRAM) or the like or a nonvolatile memory device such as a flash memory.

In summary, the control center 130 may monitor the current state of the plurality of mobile infrastructure devices and allocate a slave mobile infrastructure device in response to a request of the master mobile infrastructure device.

3, 4, 6, and 7, a service providing process and a service resource sharing process through connection between mobile infrastructure devices according to an embodiment of the present embodiment will be described.

6 is a flowchart illustrating a service providing process through connection between mobile infrastructure devices according to an embodiment of the present embodiment.

Referring to FIG. 6, in step S610, the master mobile infrastructure device may receive a service request. Here, the master mobile infrastructure device is a mobile-type device including all service resources for providing an end-to-end service, and means a device that is requested to provide a service. In contrast, the slave mobile infrastructure device refers to a device connected to the master mobile infrastructure device in order to support service resources. For reference, as described above, it should be noted that the concepts of master and slave are relative and do not limit the present embodiment.

On the other hand, the service resource management unit 310 may monitor the type, capacity and status of the service resources possessed by the mobile infrastructure device 110. In addition, when the master mobile infrastructure device is connected to the slave mobile infrastructure device, the service resource manager 310 may expand service resources by sharing service resources of both devices under the control of the connection unit 350.

In operation S620, the service request processing unit 330 determines whether the requested service can be provided from the current service resource pool (that is, the total service resources of the master and the slave mobile infrastructure devices that are already connected), and determines whether the requested service is available. It may be decided to perform either the provision or the connection with another mobile infrastructure device 110.

If it is determined in step S620 that the requested service can be provided from the current service resource pool (YES), the service request processing unit 330 may proceed to step S630 to provide the requested service.

In operation S630, the service request processor 330 may determine whether an available resource exists and determine whether the service resource sharing range is extended. Here, the available resource means a resource available for providing a requested service in a service resource unique to a master mobile infrastructure device and a service resource already shared.

If it is determined in step S630 that available resources exist (Yes), the service request processing unit 330 may provide the requested service according to service priority in step S660. The service priority may be set in consideration of a weight factor and a workload based on the performance of each service resource.

If it is determined in step S630 that no available resources exist (No), the service request processing unit 330 transmits a signal including the necessary service resource information to the service resource management unit 310 and expands the shared resource. In order to proceed to the process S650.

Returning to step S620, if the requested service cannot be provided from the current service resource pool (No), the service request processing unit 330 sends a slave mobile infrastructure to the control center 130 to provide the requested service. The allocation of the device may be requested, and the process may proceed to step S640.

In operation S640, the control center 130 may select at least one of the available mobile infrastructure devices capable of providing the requested service as the slave mobile infrastructure device and assign the slave mobile infrastructure device to the master mobile infrastructure device.

In detail, in step S641, the infrastructure search unit 510 may search for a plurality of mobile infrastructure devices and collect mobile infrastructure device information in response to a slave mobile infrastructure device allocation request.

Next, in step S642, the infrastructure selecting unit 530 may determine whether the available mobile infrastructure device exists and determine whether to re-search for the mobile infrastructure device. Here, the available mobile infrastructure device refers to a device that has necessary service resources and can move for connection with a master mobile infrastructure device until a service is provided.

As a result of the determination in step S642, when there is no available mobile infrastructure device (No), the infrastructure search unit 510 and the infrastructure selecting unit 530 select the slave mobile infrastructure device to process S641 and S642. Can be repeated.

As a result of the determination in step S642, if an available mobile infrastructure device exists ('Yes'), the infrastructure selecting unit 530 may select a slave mobile infrastructure device and assign it to the master mobile infrastructure device, and then proceed to step S650. .

In detail, the infrastructure selecting unit 530 may select, as a slave mobile infrastructure device, a mobile infrastructure device having the largest available resource capacity or the closest to the master mobile infrastructure device among the available mobile infrastructure devices. At this time, the selection criteria of the slave mobile infrastructure device may vary depending on the type of service requested, the operation status of the mobile infrastructure device, or a system operating policy.

Meanwhile, the infrastructure controller 550 may transmit a connection control signal to the master and slave mobile infrastructure devices, respectively. The connection control signal may include necessary service resource information, ID information of the master mobile infrastructure device, destination information, path information, and the like.

The slave mobile infrastructure device may move to the destination based on the received connection control signal and perform a connection operation with the master mobile infrastructure device.

In step S650, the service resource management unit 310 may expand the available service resource of the master mobile infrastructure device by sharing the service resource with the slave mobile infrastructure device.

Specifically, when the service request processing unit 330 determines the expansion of the shared resource with the slave mobile infrastructure device already connected (YES in step S630), the service resource management unit 310 may perform an additional service resource sharing process. Can be. Here, specific contents of the service resource sharing process will be described later with reference to FIG. 7.

When the infrastructure selecting unit 530 allocates the slave mobile infrastructure device (YES in step S642), the connection unit 350 selectively connects the master and slave mobile infrastructure devices by using a plurality of connection resources. Can be performed. When the master and slave mobile infrastructure devices are connected to each other, the service resource manager 310 may expand service resources by sharing service resources of both devices.

As a result, when the service resource manager extends the service resource of the master mobile infrastructure device in step S650, the service request processor 330 may provide the requested service according to the service priority in step S660.

7 is a flowchart illustrating a process of sharing a service resource according to the present embodiment.

In step S710, the master mobile infrastructure device may request the slave mobile infrastructure device to share necessary service resources. In this case, the master mobile infrastructure device may transmit information on necessary service resources, for example, types and capacities of service resources, priority of requested services, and the like to the slave mobile infrastructure device.

The slave mobile infrastructure device may prepare for distribution of necessary service resources based on the received service resource information (1) in step S720, and (2) in step S730, may transmit a deployment ready signal to the master mobile infrastructure device. .

The master mobile infrastructure device, at step S740, completes preparation for loading service resources to be distributed from the slave mobile infrastructure device, and at step S750, the master mobile infrastructure device requests the slave mobile infrastructure device to start distribution of service resources. Can be.

The slave mobile infrastructure device may (1) prepare the distribution of the requested service resource in step S760, and (2) distribute the requested service resource to the master mobile infrastructure device in step S770.

In step S780, the master mobile infrastructure device may load the service resource distributed in step S720.

In step S790, the master mobile infrastructure device may start providing the requested service using the loaded service resource.

In FIG. 6 and FIG. 7, a plurality of processes are sequentially executed, but this is merely illustrative of the technical idea of an embodiment of the present invention. In other words, one of ordinary skill in the art to which an embodiment of the present invention belongs may change the order described in FIGS. 6 and 7 without departing from the essential characteristics of the embodiment of the present invention, 6 and 7 are not limited to the time-series order because various modifications and variations may be applicable to one or more processes in parallel.

6 and 7 may be embodied as computer readable codes on a computer readable recording medium. The computer-readable recording medium includes all kinds of recording devices in which data that can be read by a computer system is stored. That is, the computer-readable recording medium may be a magnetic storage medium (for example, ROM, floppy disk, hard disk, etc.), an optical reading medium (for example, CD-ROM, DVD, etc.) and a carrier wave (for example, the Internet Storage medium). The computer readable recording medium can also be distributed over network coupled computer systems so that the computer readable code is stored and executed in a distributed fashion.

Hereinafter, a service providing method through connection between mobile infrastructure devices according to another aspect of the present embodiment will be described in detail with reference to FIGS. 8 and 9.

8 is a view showing the configuration of a mobile infrastructure device according to another aspect of the present embodiment.

Referring to FIG. 8, the mobile infrastructure device 110 may include a service resource management unit 810, a service request processing unit 820, an infrastructure search unit 830, an infrastructure selection unit 840, an infrastructure control unit 850, and a connection unit ( 860 and a storage unit 870. The mobile infrastructure device 110 of FIG. 8 differs from the mobile infrastructure device 110 of FIG. 3 in that it directly selects a slave mobile infrastructure device.

The service resource manager 810 may monitor and manage the type, capacity, and state of a service resource held by the mobile infrastructure device 110.

In addition, when the mobile infrastructure device 110 is connected to another mobile infrastructure device 110, the service resource manager 810 may share the service resources of both devices under the control of the connection unit 860, which will be described later. Can be extended.

The sharing scope of the service resources may be partial or full resources of the service resources according to the type or capacity of the required service resources, the connection state between the mobile infrastructure devices, and the like. If necessary to provide a service, the service resource manager 810 may change the sharing range of the service resource under the control of the service request processor 820, which will be described later.

The service resource manager 810 may configure a service resource pool using service resources of the master and slave mobile infrastructure devices. According to the present embodiment, the service resource information regarding the type, capacity, etc. of the service resources included in the service resource pool may be stored in a table form in the storage unit 870 to be described later. A specific example of the service resource pool information table is shown in Table 1 described above with reference to FIG. 3.

The master mobile infrastructure device and the slave mobile infrastructure device may be connected in various forms such as '1: 1', '1: n', and 'n: m'. A detailed connection form is as described above with reference to FIG. 4.

The service request processing unit 820 determines whether the requested service can be provided from the current service resource pool (that is, the total service resources of the master and the slave mobile infrastructure devices already connected), thereby providing the requested service or other infrastructure. You can decide to do any of the connections with resources.

Specifically,

When the requested service can be provided from the current service resource pool, the service request processing unit 820 may set the priority of the requested service and thus provide the requested service. Here, the priority may be set in consideration of a weight factor and a workload based on the performance of each service resource.

If it is necessary to extend the resource sharing range with the slave mobile infrastructure device already connected in order to provide the requested service, under the control of the service request processing unit 820, the service resource management unit 810 performs an additional service resource sharing process. can do. As a result, since the range of available resources in the current service resource pool is expanded, the service request processing unit 820 may provide the requested service.

If the requested service cannot be provided from the current service resource pool, the service request processor 820 may determine a connection with the new slave mobile infrastructure device.

The infrastructure search unit 830 may search for a plurality of mobile infrastructure devices and collect mobile infrastructure device information in order to connect with a new slave mobile infrastructure device. In detail, the infrastructure search unit 830 may be connected to a plurality of mobile infrastructure devices through a connection resource and an external network to collect current location, communication status, and service resource information of each of the plurality of mobile infrastructure devices.

According to the present embodiment, the collected mobile infrastructure device information may be stored in a table form in the storage unit 870 to be described later. A specific example of the mobile infrastructure device information table is shown in Table 2 described above with reference to FIG. 3.

The infrastructure selecting unit 840 may select at least one of the found mobile infrastructure devices as a slave mobile infrastructure device.

For example, the infrastructure selecting unit 840 is a device that holds the service resources required by the master mobile infrastructure device and moves to connect with the master mobile infrastructure device until the service is provided, and has the largest available resource capacity. Alternatively, the mobile infrastructure device closest to the master mobile infrastructure device may be selected as the slave mobile infrastructure device.

Here, the selection criteria of the slave mobile infrastructure device may include the type of service requested, the communication status (for example, latency, jitter, bandwidth, etc.), and the operation status of the mobile infrastructure device (for example). Number of devices, allocation area, etc.) or service requirements (e.g., system operation policies, user quality indicators, etc.).

The infrastructure controller 850 may transmit a connection control signal to the slave mobile infrastructure device. The connection control signal may include necessary service resource information, ID information of the master mobile infrastructure device, destination information, path information, and the like. Here, the destination is a place that can be connected to the master mobile infrastructure device, the current position, the moving speed, the communication state (eg, wireless condition, bandwidth (B / W), latency) of each of the master and slave mobile infrastructure devices ), And the like.

The connection unit 860 may selectively use the plurality of connection resources described above with reference to FIG. 2 to perform a connection operation with the slave mobile infrastructure device arriving at the destination based on the received connection control signal. In detail, the connection unit 860 may set a connection condition using information such as a current location, a moving speed, and a connection resource type of the slave mobile infrastructure device. In addition, the connection unit 860 may perform a connection operation with the slave mobile infrastructure device according to the set connection condition.

When the master and slave mobile infrastructure devices are connected to each other, the connection unit 860 may notify the service resource management unit 810 to control sharing of service resources for providing a service. In response, the service resource manager 810 may expand the service resource of the master mobile infrastructure device by sharing the service resource of the slave mobile infrastructure device.

The storage unit 870 may include a memory device in which the aforementioned service resource information table and the mobile infrastructure device information table are stored. The memory device may be a volatile memory device such as a dynamic random access memory (DRAM) or the like and / or a nonvolatile memory device such as a flash memory.

In summary, the mobile infrastructure device 110 may provide the requested service on its own or through a connection with a slave mobile infrastructure device.

8 and 9, a process of providing a service for connection between mobile infrastructure devices according to another aspect of the present embodiment will be described.

9 is a flowchart illustrating a service providing process through a connection between mobile infrastructure devices according to another aspect of the present embodiment. The service providing process of FIG. 9 is different from the service providing process of FIG. 7 in that the master mobile infrastructure device directly selects the slave mobile infrastructure device.

Referring to FIG. 9, in step S910, the master mobile infrastructure device may receive a service request.

The service resource manager 810 may monitor the type, capacity, and state of a service resource held by the mobile infrastructure device. In addition, when the master mobile infrastructure device is connected to the slave mobile infrastructure device, the service resource manager 810 may expand service resources by sharing service resources of both devices under the control of the connection unit 860.

In step S920, the service request processing unit 820 determines whether the requested service can be provided from the current service resource pool (that is, the total service resources of the master and the slave mobile infrastructure devices already connected), You can decide to either provide or connect with other mobile infrastructure devices.

If it is determined in step S920 that the requested service can be provided from the current service resource pool (YES), the service request processing unit 820 may proceed to step S930 to provide the requested service.

In operation S930, the service request processor 820 may determine whether an available resource exists and determine whether the service resource sharing range is extended. Here, the available resource means a resource available for providing a requested service in a service resource unique to a master mobile infrastructure device and a service resource already shared.

As a result of the determination in step S930, if available resources exist (Yes), the service request processing unit 820 may provide the requested service according to the service priority in step S980. The service priority may be set in consideration of a weight factor and a workload based on the performance of each service resource.

As a result of the determination in step S930, when no available resource exists (No), the service request processing unit 820 transmits a signal including the necessary service resource information to the service resource management unit 810 and expands the shared resource. In order to proceed to step S970.

Returning to step S920, if the requested service cannot be provided from the current service resource pool (No), the service request processing unit 820 determines a connection with the new slave mobile infrastructure device, and proceeds to step S940. Can be.

In operation S940, the infrastructure search unit 830 may search for a plurality of mobile infrastructure devices and collect mobile infrastructure device information in response to a slave mobile infrastructure device allocation request.

Next, in operation S950, the infrastructure selecting unit 840 may determine whether the available mobile infrastructure device exists in the found device, and determine whether to re-search for the mobile infrastructure device. Here, the available mobile infrastructure device refers to a device that has necessary service resources and can move for connection with a master mobile infrastructure device until a service is provided.

As a result of the determination in step S950, when there is no available mobile infrastructure device ('no'), the infrastructure search unit 830 and the infrastructure selecting unit 840 select the slave mobile infrastructure device to process the process S940 and the process S950. Can be repeated.

As a result of the determination in step S950, when there is an available mobile infrastructure device (“Yes”), in step S960, the infrastructure selecting unit 840 may select at least one of the available mobile infrastructure devices as the slave mobile infrastructure device.

Specifically, the slave mobile infrastructure device may be selected as the mobile infrastructure device having the largest available resource capacity or the closest to the master mobile infrastructure device among the available mobile infrastructure devices. At this time, the selection criteria of the slave mobile infrastructure device may vary depending on the type of service requested, the operation status of the mobile infrastructure device, or a system operating policy.

Meanwhile, the infrastructure controller 850 may transmit a connection control signal to the master and slave mobile infrastructure devices, respectively. The connection control signal may include necessary service resource information, ID information of the master mobile infrastructure device, destination information, path information, and the like. The slave mobile infrastructure device may move to the destination based on the received connection control signal and perform a connection operation with the master mobile infrastructure device.

In step S970, the service resource manager 810 may expand the available service resource of the master mobile infrastructure device by sharing the service resource with the slave mobile infrastructure device.

Specifically, when the service request processing unit 820 determines the expansion of the shared resource with the slave mobile infrastructure device already connected (YES in step S930), the service resource management unit 810 may perform an additional service resource sharing process. Can be.

When the infrastructure selecting unit 840 selects the slave mobile infrastructure device (step S960), the connection unit 860 may perform a connection operation between the master and the slave mobile infrastructure devices by selectively using a plurality of connection resources. When the master and slave mobile infrastructure devices are connected to each other, the service resource manager 810 may expand service resources by sharing service resources of both devices.

As a result, when the service resource manager extends the service resource of the master mobile infrastructure device in step S970, the service request processor 820 may provide the requested service according to the service priority in step S980.

The above description is merely illustrative of the technical idea of the present embodiment, and those skilled in the art will appreciate that various modifications and variations can be made without departing from the essential characteristics of the present embodiment. Therefore, the present embodiments are not intended to limit the technical idea of the present embodiment but to describe the present invention, and the scope of the technical idea of the present embodiment is not limited by these embodiments. The scope of protection of the present embodiment should be interpreted by the following claims, and all technical ideas within the scope equivalent thereto should be construed as being included in the scope of the present embodiment.

Claims (11)

In the mobile infrastructure device to provide a service,
Determining whether the requested service can be provided from a current service resource pool based on a service characteristic including a type of service requested from a user terminal;
If it is not possible to provide the requested service, searching for another available mobile infrastructure device having a service resource necessary for providing the requested service;
Selecting at least one mobile infrastructure device from the discovered mobile infrastructure devices; And
Providing the requested service by sharing the service resource through an interconnection with the selected mobile infrastructure device;
How we deliver the service. The method of claim 1,
Configuring the current service resource pool using the shared service resource; And
Changing the sharing scope of the current service resource pool when the provision of the requested service is completed or necessary for the provision of a newly requested service.
How we deliver the service. The method of claim 1,
The selected mobile infrastructure device,
Connected according to a connection condition including at least one of a moving speed, a distance to the selected mobile infrastructure device, a type of connection resource connected to a network function module, and a communication speed
The connection condition is,
It is set using the type of the connection resource, the current location and the moving speed of the selected mobile infrastructure device
How we deliver the service. In the mobile infrastructure device to provide a service,
Determining whether the requested service can be provided from a current service resource pool based on a service characteristic including a type of service requested from a user terminal;
If the provision of the requested service is not possible, requesting a control center to allocate another available mobile infrastructure device;
In response to the allocation request, allocating at least one mobile infrastructure device having service resources necessary for providing the requested service from the control center; And
Sharing the service resource by interconnection with the assigned mobile infrastructure device to provide the requested service.
How we deliver the service. The method of claim 4, wherein
Configuring the current service resource pool using the shared service resource; And
Changing the sharing scope of the current service resource pool when the provision of the requested service is completed or necessary for the provision of a newly requested service.
How we deliver the service. The method of claim 4, wherein
The assigned mobile infrastructure device,
Interconnected based on a connection control signal received from the control center,
The connection control signal,
Type and capacity of the service resources, including destination information
How we deliver the service. In the mobile infrastructure device,
A service request processing unit that determines whether the requested service can be provided from a current service resource pool based on a service feature including a type of service requested from a user terminal;
An infrastructure search unit for searching for another available mobile infrastructure device having a service resource necessary for providing the requested service, if the requested service is not available;
An infrastructure selecting unit configured to select at least one mobile infrastructure device from the found available mobile infrastructure devices; And
It includes a connection for connecting the selected mobile infrastructure device,
The service request processing unit,
Sharing the service resource with the connected mobile infrastructure device to provide the requested service
Mobile infrastructure device. The method of claim 7, wherein
A service resource manager configured to configure the current service resource pool using the shared service resource and to change the sharing range of the current service resource pool when the requested service is completed or necessary for the newly requested service. Containing more
Mobile infrastructure device. The method of claim 7, wherein
The connecting portion,
Connecting the selected mobile infrastructure device according to a connection condition including at least one of a moving speed, a distance to the selected mobile infrastructure device, a type of connection resource connected to a network function module, and a communication speed,
The connection condition is,
It is set using the type of the connection resource, the current location and the moving speed of the selected mobile infrastructure device
Mobile infrastructure device. In the mobile infrastructure device,
It is determined whether the requested service can be provided from the current service resource pool based on the service feature including the type of service requested from the user terminal, and if the provision of the requested service is not possible, A service request processing unit for requesting allocation of an available mobile infrastructure device; And
A connection unit for connecting at least one mobile infrastructure device allocated by the control center in response to the allocation request,
The service request processing unit,
Sharing the service resource with the connected mobile infrastructure device to provide the requested service
Mobile infrastructure device. The method of claim 10,
The connecting portion,
Based on a connection control signal received from the control center, interconnecting with the assigned mobile infrastructure device,
The connection control signal,
Type and capacity of the service resources, including destination information
Mobile infrastructure device.

Images