TWI769134B - Communication device, communication method and communication program - Google Patents

Abstract

An apparatus, method and program for appropriately selecting an edge server providing services to a terminal are provided.

A device comprising: an obtaining unit for obtaining the aforesaid relay, which is provided by a relay node that relays communication between the aforementioned device and a core network, and is used by a service providing device that provides services to the aforementioned device Obtain the relevant information of the API required for the relevant information of the communication of the node; and the selection processing unit performs the pre-recorded service provision for selecting the source of the service provision based on the relevant information of the pre-recorded API that has been acquired by the pre-recorded acquisition unit The processing required by the device.

Description

Communication device, communication method and communication program

The present disclosure relates to apparatus, methods and programs.

In recent years, data processing is performed by servers (hereinafter also referred to as edge servers) that are installed physically close to terminals such as smartphones, and a technology called Mobile-Edge Computing (MEC: Mobile-Edge Computing) is developing attracted attention. For example, it is disclosed in the following Non-Patent Document 1, and the standard specification of the MEC technology is discussed.

In MEC, an edge server is placed physically close to the terminal. Therefore, the communication delay is shortened compared with the general cloud server that is centrally placed, making it possible to use applications that require high real-time. . In addition, in MEC, the functions that have been processed on the terminal side so far are distributed and processed by the edge server close to the terminal, so that high-speed web application processing can be realized without being limited by the performance of the terminal. The edge server can have various functions such as the function as an application server and the function as a content server, etc., and can provide various services to the terminal.

[Prior Art Literature] [Non-patent literature]

[Non-Patent Document 1] ETSI, "Mobile-Edge Computing-Introductory Technical White Paper", September 2014, [retrieved on May 28, 2015], Internet <https://portal.etsi.org/Portals /0/TBpages/MEC/Docs/Mobile-edge_Computing_-_Introductory_Technical_White_Paper_V1%2018-09-14.pdf>

The content of the study in the above-mentioned Non-Patent Document 1 and the like is not long since the study was started, so it is difficult to say that the technology about the MEC has been sufficiently proposed. For example, the technology required to select the edge server that provides services to the terminal is one of the technologies that has been fully proposed.

Therefore, the present disclosure proposes a novel and improved device, method and program that can appropriately select an edge server that provides services to a terminal.

According to the present disclosure, it is possible to provide a device comprising: an acquisition unit, which is to be provided by a relay node that relays the communication between the aforementioned device and the core network, and is used by a service providing device that provides services to the aforementioned device , which is used to obtain the information related to the communication of the previous relay node. The required API (Application Programing Interface) related information is acquired; and the selection processing unit is based on the pre-recorded API-related information that has been acquired by the pre-recorded acquisition unit. need to be dealt with.

Furthermore, according to the present disclosure, an apparatus can be provided, which is provided with: an obtaining unit, which is provided by a relay node that relays the communication between the terminal device and the core network, and is used to obtain the communication data of the aforementioned relay node. The relevant information of the API required for the relevant information is obtained; and the notification unit is to notify the aforementioned terminal device of the relevant information of the aforementioned API that has been acquired by the aforementioned obtaining section.

Furthermore, according to the present disclosure, it is possible to provide a device comprising: a relay processing unit for relaying the communication between the terminal device and the core network; and a providing unit for being stored in the aforementioned relay processing unit Subsequently, the relevant information of the communication is provided to the service providing device that provides the service to the terminal device of the previous record.

In addition, according to the present disclosure, a method can be provided, which includes: to be provided by a relay node that relays communication between the device and the core network, and used by a service providing device that provides services to the forwarding device, using The API-related information required to obtain the communication-related information of the pre-relay node, and the steps for obtaining it; and the pre-recording for selecting the source of service provision by the processor based on the obtained pre-recording API-related information The steps of the processing required by the service providing device.

In addition, according to the present disclosure, a method can be provided, which includes: the information required by the relay node that relays the communication between the terminal device and the core network to obtain the relevant information of the communication of the aforementioned relay node. The relevant information of the API obtained, and the steps of obtaining it; and the step of notifying the terminal device of the preceding description through the processor of the relevant information of the preceding API that has been obtained.

In addition, according to the present disclosure, a method can be provided, which includes: the steps of relaying the communication between the terminal device and the core network; and providing the relevant information of the relayed communication by the processor. A service providing device that provides services to the terminal device of the previous record.

Furthermore, according to the present disclosure, a program can be provided, which is used to make a computer function to become: an acquisition unit is provided by a relay node that relays the communication between the terminal device and the core network, and is used to acquire Obtain the relevant information of the API required for the communication-related information of the aforementioned relay node; and the notification unit notifies the aforementioned terminal device of the relevant information of the aforementioned API that has been acquired by the aforementioned obtaining unit.

In addition, according to the present disclosure, a program can be provided, which is used to make a computer function to become: a relay processing unit that relays the communication between the terminal device and the core network; and a providing unit that will be The information related to the communication relayed by the aforementioned relay processing unit is provided to the service providing device that provides services to the aforementioned terminal device.

In addition, according to the present disclosure, a program can be provided, which is used to make a computer function to become: the acquisition part is provided by a relay node that relays the communication between the device and the core network, and is forwarded to the device. Obtain the relevant information of the API used by the service providing device that provides the service to obtain the relevant information of the communication of the preceding relay node; and the selection processing unit is based on the preceding API that has been obtained by the preceding recording obtaining unit Of The relevant information is used to perform the processing required by the service providing device for selecting the service providing source.

As described above, according to the present disclosure, the edge server that provides services to the terminal can be appropriately selected. In addition, the above-mentioned effects are not necessarily limited to interpretation, and can be combined with the above-mentioned effects or replace the above-mentioned effects to achieve any effect disclosed in this specification, or other effects that can be grasped according to this specification.

1‧‧‧System

10‧‧‧Honeycomb

40‧‧‧Core Network

50‧‧‧Packet Data Network

60‧‧‧Application Server

100‧‧‧Wireless communication device

110‧‧‧Antenna Section

120‧‧‧Wireless Communication Department

130‧‧‧Network Communication Department

140‧‧‧Memory Department

150‧‧‧Processing Department

151‧‧‧Relay Processing Department

153‧‧‧Provide Department

155‧‧‧Notification Department

200‧‧‧Terminal devices

210‧‧‧Antenna Section

220‧‧‧Wireless Communication Department

230‧‧‧Memory Department

240‧‧‧Processing Department

241‧‧‧Acquisition Department

243‧‧‧Select Processing

300‧‧‧MEC Server

310‧‧‧Communications Department

320‧‧‧Memory Department

330‧‧‧Processing Department

331‧‧‧Acquisition Department

333‧‧‧Notification Department

335‧‧‧Exploration

337‧‧‧Service Processing Department

800‧‧‧eNB

810‧‧‧Antenna

820‧‧‧Base Station Device

821‧‧‧Controller

822‧‧‧Memory

823‧‧‧Internet Interface

824‧‧‧Core Network

825‧‧‧Wireless Communication Interface

826‧‧‧BB Processor

827‧‧‧RF Circuit

830‧‧‧eNodeB

840‧‧‧Antenna

850‧‧‧ base station device

851‧‧‧Controller

852‧‧‧Memory

853‧‧‧Internet Interface

854‧‧‧Core Network

855‧‧‧Wireless Communication Interface

856‧‧‧BB Processor

857‧‧‧Connection interface

860‧‧‧RRH

861‧‧‧Connection interface

863‧‧‧Wireless Communication Interface

864‧‧‧RF Circuit

870‧‧‧eNB

881‧‧‧Inter Cell RRM

882‧‧‧RB Control

883‧‧‧Connection Mobility Control

884‧‧‧Radio Admission Control

885‧‧‧eNB Measurement Configuration & Provision

886‧‧‧Dynamic Resource Allocation(Scheduler)

891‧‧‧RRC

892‧‧‧PDCP

893‧‧‧RLC

894‧‧‧MAC

895‧‧‧PHY

900‧‧‧Smartphone

901‧‧‧Processor

902‧‧‧Memory

903‧‧‧Storage

904‧‧‧External connection interface

906‧‧‧Camera

907‧‧‧Sensor

908‧‧‧Microphone

909‧‧‧Input Device

910‧‧‧Display device

911‧‧‧Speakers

912‧‧‧Wireless Communication Interface

913‧‧‧BB Processor

914‧‧‧RF Circuit

915‧‧‧Antenna Switch

916‧‧‧Antenna

917‧‧‧Busbar

918‧‧‧battery

919‧‧‧Auxiliary Controller

920‧‧‧Car navigation device

921‧‧‧Processor

922‧‧‧Memory

924‧‧‧GPS Module

925‧‧‧Sensor

926‧‧‧Data interface

927‧‧‧Content Player

928‧‧‧Memory Media Interface

929‧‧‧Input Devices

930‧‧‧Display Device

931‧‧‧Speakers

933‧‧‧Wireless Communication Interface

934‧‧‧BB Processor

935‧‧‧RF Circuit

936‧‧‧Antenna Switch

937‧‧‧Antenna

938‧‧‧battery

940‧‧‧In-vehicle system

941‧‧‧In-vehicle network

942‧‧‧Vehicle side module

[FIG. 1] An explanatory diagram for explaining the outline of MEC.

[Fig. 2] An explanatory diagram for explaining the platform of the MEC server.

[ Fig. 3] Fig. 3 is an explanatory diagram of an example of a schematic configuration of a system according to an embodiment of the present disclosure.

4 is a block diagram of an example of the configuration of the wireless communication device according to an embodiment of the present disclosure.

[ Fig. 5] Fig. 5 is a block diagram of an example of a configuration of a terminal device according to an embodiment of the present disclosure.

6 is a block diagram of an example of the configuration of the MEC server according to an embodiment of the present disclosure.

[ Fig. 7] Fig. 7 is an explanatory diagram for explaining an example of UI displayed on the terminal device according to the first embodiment.

[ Fig. 8] Fig. 8 is an explanatory diagram for explaining an example of UI displayed on the terminal device described in the same embodiment.

[ Fig. 9] Fig. 9 is an explanatory diagram for explaining an example of a communication path between the devices described in the first specific example.

[ Fig. 10 ] A flowchart of an example of the flow of the confirmation processing of API information executed in the system described in the specific example.

[ Fig. 11 ] A flowchart of an example of the flow of the confirmation process of API information executed in the system described in the specific example.

[ Fig. 12] Fig. 12 is an explanatory diagram for explaining an example of a communication path between the devices described in the specific example.

[ Fig. 13 ] A flowchart of an example of the flow of the application program start processing executed in the UE described in the specific example.

[ Fig. 14 ] An explanatory diagram for explaining the configuration of ECGI.

[ Fig. 15] Fig. 15 is a flowchart showing an example of the flow of service provision processing executed in the system described in the specific example.

[ Fig. 16] Fig. 16 is a flowchart showing an example of the flow of service provision processing executed in the system described in the specific example.

[ Fig. 17] Fig. 17 is an explanatory diagram for explaining an example of a communication path between devices according to the second specific example.

[ Fig. 18] Fig. 18 is an explanatory diagram for explaining an example of a communication path between the devices described in the specific example.

[ Fig. 19] Fig. 19 is a flowchart showing an example of the flow of service provision processing executed in the system described in the specific example.

[Fig. 20] A communication path for explaining the communication path between the devices described in the third specific example An illustration of an example.

[ Fig. 21] Fig. 21 is a flowchart showing an example of the flow of service provision processing executed in the system described in the specific example.

[ Fig. 22] Fig. 22 is an explanatory diagram for explaining an example of a communication path between the devices described in the specific example.

[ Fig. 23 ] A flowchart showing an example of the flow of service provision processing executed in the system described in the specific example.

[ Fig. 24] Fig. 24 is an explanatory diagram for explaining supplementary matters related to the system according to an embodiment of the present disclosure.

[ Fig. 25] Fig. 25 is an explanatory diagram for explaining supplementary matters related to the system according to an embodiment of the present disclosure.

[ Fig. 26] Fig. 26 is a diagram illustrating an example of a communication protocol used between devices included in a system according to an embodiment of the present disclosure.

[ Fig. 27] Fig. 27 is a diagram illustrating an example of a communication protocol used between devices included in a system according to an embodiment of the present disclosure.

[ Fig. 28] Fig. 28 is a diagram illustrating an example of a communication protocol used between devices included in a system according to an embodiment of the present disclosure.

[ Fig. 29] Fig. 29 is a diagram illustrating an example of a communication protocol used between devices included in a system according to an embodiment of the present disclosure.

[ Fig. 30] Fig. 30 is a diagram illustrating an example of a communication protocol used between devices included in a system according to an embodiment of the present disclosure.

[ Fig. 31 ] A diagram showing an example of a communication protocol used between devices included in a system according to an embodiment of the present disclosure.

[FIG. 32] The system described in an embodiment of the present disclosure is used to describe An explanatory diagram of the supplementary items.

[ Fig. 33 ] An explanatory diagram for explaining supplementary matters related to the system according to an embodiment of the present disclosure.

34 is a block diagram of a first example of a schematic configuration of an eNB.

35 is a block diagram of a second example of a schematic configuration of an eNB.

36 is a block diagram of an example of a schematic functional configuration of an eNB.

[ Fig. 37 ] A block diagram of an example of a schematic configuration of a smartphone.

[ Fig. 38 ] A block diagram of an example of a schematic configuration of a car navigation device.

Hereinafter, preferred embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. In addition, in this specification and drawing, about the component which has substantially the same functional structure, the same code|symbol is attached|subjected, and overlapping description is abbreviate|omitted.

In addition, in this specification and the drawings, elements having substantially the same functional configuration may be distinguished by adding different alphabets after the same symbol. For example, a plurality of elements having substantially the same functional configuration are distinguished as the terminal devices 200A, 200B, and 200C as necessary. However, when it is not necessary to distinguish each of the plural elements having substantially the same functional structure, the same symbol is only indicated. For example, if there is no particular need to distinguish the terminal devices 200A, 200B, and 200C, it is simply referred to as the terminal device 200 .

In addition, the description is performed in the following order.

1. Introduction

1.1. MEC

1.2. Technical issues

2. Schematic composition of the system

3. Configuration of each device

4. The first embodiment

4.1. Technical Features

4.2. Specific examples

4.2.1. Case 1

4.2.2. The second case

4.2.3. The third case

5. Supplement

6. Application example

7. Summary

<<1. Introduction>> <1.1. MEC> (1) Outline

First, with reference to FIG. 1 , an overview of the MEC will be described. FIG. 1 is an explanatory diagram for explaining the outline of the MEC. In FIG. 1, the upper part is a diagram showing the communication required for UE (User Equipment) to access applications and content in the current state of mobile communication represented by LTE (Long Term Evolution) (where MEC is not introduced) path. Also, the lower part shows the communication path required for UE to access applications and content when MEC is introduced.

As shown in the upper part of FIG. 1 , in current mobile communication, applications and contents are placed on an IP network that is outside (farther from the UE) than EPC (Evolved Packet Core). Therefore, in order to execute the application or obtain the content, the UE must pass through all the relay networks (such as Backbone network), EPC, backhaul link, base station, and access on the intermediate path to the data center. link for communication. Therefore, huge network costs and delays will be incurred.

On the other hand, as shown in the lower part of FIG. 1 , in the MEC, applications and contents are held inside the EPC (closer to the UE side). For example, in the example shown in FIG. 1 , the MEC server (ie, the edge server) integrally formed with the base station functions as an application server and a content server. Therefore, in order to execute the application or obtain the content, the UE only needs to perform the main communication inside the EPC (strictly speaking, the communication with the server outside the EPC is also possible). Therefore, by introducing MEC, not only extremely low-latency communication can be achieved, but also traffic outside the access link (eg, backhaul link, EPC, and relay network) can be reduced. Even the lower latency of communication and the reduction of traffic outside the access link will contribute to the improvement of throughput and the reduction of power consumption on the UE and network side. In this way, through the introduction of MEC, various advantages can be produced for users, network providers, and service providers. MEC, which distributes data on the local side (that is, the side closer to the UE), is expected to be applied to applications with high regional relevance and applications to distributed computers.

In addition, although illustrated in Figure 1, the MEC server is An example in which the base station is integrally formed, but the present technology is not limited to the above example. The MEC server can also be formed separately from the device of the base station, and can also be physically separated from the base station. In the present embodiment, as an example, the MEC server is assumed to be provided integrally with the base station for description. Hereinafter, the MEC server formed integrally with the base station is also referred to as the MEC server corresponding to the base station, and vice versa is also similarly referred to as the base station corresponding to the MEC server.

(2) Platform

Next, referring to FIG. 2, the platform of the MEC server will be described.

FIG. 2 is an explanatory diagram for explaining the platform of the MEC server. The lowermost component is the 3GPP Radio Network Element, which is the base station equipment such as antennas and amplifiers. The hosting infrastructure on it is formed by the hardware resources (Hardware Resources) such as server equipment, and the virtualization layer (Virtualization Layer) formed by the software that virtualizes these , which can provide general virtual server technology. On the virtual server, there is an application platform (Application Platform) action.

The Virtualization Manager (Virtualization Manager) manages the creation and destruction of VMs (Virtual Machines), which are machines operated by top-level applications (MEC App). Each application can be executed by different enterprises, so the virtualization manager requires security and considers the separation of allocated resources, etc., but it can be applied to general cloud infrastructure. infrastructure technology.

Application Platform Service is a collection of characteristic common services of MEC. The Traffic Offload Function is performed when the request from the UE is processed by the application on the MEC server and by the application on the Internet (the parent application on the data server). Switch control of routing, etc. Radio Network Information Services (Radio Network Information Services) requires each application on the MEC server to correspond to wireless status information such as the radio wave strength between the base station of the MEC server and the UE, from the lower layer. The wireless network obtains the information and provides it to the application. Communication Services (Communication Services) provides the path for each application on the MEC server to communicate with the UE or the application on the Internet. Service Registry: When there is a request for the creation or action of each application on the MEC server, the application is authenticated, registered, and answered inquiries from other entities.

On the application platform described above, each application on each VM operates to replace the application on the Internet or provide various services to the UE by cooperating.

Since MEC servers are supposed to be installed in many base stations, studies on the mechanism for managing and cooperating many MEC servers with each other are also required. Hosting Infrastructure Management System, Application Platform Management System, The Application Management System manages the corresponding entities on the MEC server and makes them work together.

(3) The trend of standardization

In Europe, in October 2014, ISG (Industry Specification Groups) was set up in ETSI, and the standardization of MEC was started. The original specification was targeted at the end of 2016, and is now moving towards standardized operations. More specifically, with the cooperation of ETSI ISG NFV (Network Function Virtualization), 3GPP, etc., the standardization of APIs required for MEC implementation is the center, and is moving towards standardization.

<1.2. Technical issues>

So far, regarding the provision of content from a cloud server, the selection of the server providing the source is mainly based on the delay time or bandwidth at the network layer (IP). However, with respect to the path including the wireless section, the delay time, bandwidth, etc. may vary according to the conditions of the wireless network, so that it may be difficult to provide stable service. Therefore, it is desirable to define a standard API (Application Programming Interface) for the base station to provide wireless network information to upper layers (eg, applications). Currently, such an API is not defined.

It is assumed that even if such an API is defined, the opening and closing (opening/closing) of the API may still change according to the situation of the wireless network operator (such as contract, maintenance, traffic conditions, etc.). Therefore, in the upper layer, it is necessary to adapt the application process considering the conditions of the wireless network. It is difficult to set the action of the formula.

When the MEC technology is introduced, it is expected that such a situation can be improved.

Therefore, taking the above-mentioned situation as a focus, the system described in one embodiment of the present disclosure is created. In the system described in this embodiment, APIs required for providing information of the wireless network from the base station to the upper layer are defined.

Thereby, it becomes possible to adaptively set the operation of the application in consideration of the situation of the wireless network in the upper layer. For example, the MEC server can perform data format, data transfer rate, and content codec based on the state of the wireless area known by using the above-mentioned API before the content is provided at the start of the session at the application layer. , data length and other action settings. By starting communication through such an action setting, the MEC server can optimize the application provided.

In addition, the terminal can dynamically select the MEC server from which the service is provided according to the presence or absence of the above-mentioned API, as well as the opening and closing. Up to now, the communication path of the terminal has been selected by the operator, whereas the communication path of the terminal has been selected by the application program. In this way, the user can receive the provision of the service through a more appropriate communication path.

<<2. Schematic configuration of the system>>

Next, a schematic configuration of the system 1 according to an embodiment of the present disclosure will be described with reference to FIG. 3 . FIG. 3 is an explanatory diagram of an example of a schematic configuration of the system 1 according to an embodiment of the present disclosure. Referring to Figure 3, system 1 includes There are: the wireless communication device 100 , the terminal device 200 , and the MEC server 300 . Here, the terminal device 200 is also referred to as a user. The user may also be referred to as user equipment (User Equipment: UE). The wireless communication device 100C is also called UE-Relay. The UE here may be the UE defined in LTE or LTE-A, and the UE-Relay may also be the Prose UE to Network Relay discussed in 3GPP, and may also mean a general communication device.

(1) Wireless communication device 100

The wireless communication device 100 is a device that provides wireless communication services to its devices. For example, the wireless communication device 100A is a base station of a cellular system (or a mobile communication system). The base station 100A performs wireless communication with a device (eg, the terminal device 200A) located in the cellular network 10A of the base station 100A. For example, the base station 100A sends a downlink signal to the terminal device 200A, and receives an uplink signal from the terminal device 200A.

The base station 100A is logically connected to other base stations through, for example, an X2 interface, and can transmit and receive control information. In addition, the base station 100A is logically connected to the core network 40 through, for example, the S1 interface, and can transmit and receive control information and the like. In addition, communications between these devices can be physically relayed by a variety of devices.

Here, the wireless communication device 100A shown in FIG. 3 is a macro cellular network base station, and the cellular network 10 is a macro cellular network. the other party On the other hand, the wireless communication devices 100B and 100C are master devices using the small cellular networks 10B and 10C, respectively. As an example, the main device 100B is a small cellular base station that is fixedly installed. The small cellular network base station 100B establishes a wireless backhaul link with the macro cellular network base station 100A, and establishes an access link with one or more terminal devices (such as the terminal device 200B) in the small cellular network 10B . The host device 100C is a dynamic AP (Access Point). The dynamic AP100C is a mobile device that uses the small cellular network 10C dynamically. The dynamic AP 100C establishes a wireless backhaul link with the macro cellular network base station 100A, and establishes an access link with more than one terminal device (eg, the terminal device 200C) in the small cellular network 10C. The dynamic AP 100C can be, for example, a terminal device equipped with hardware or software that can operate as a base station or wireless access point. The small cellular network 10C in this case is a dynamically formed localized network (Localized Network/Virtual cell).

The cellular network 10 is used according to any wireless communication method such as LTE, LTE-A (LTE-Advanced), GSM (registered trademark), UMTS, W-CDMA, CDMA200, WiMAX, WiMAX2, or IEEE802.16. Can.

In addition, a small-cell network is a type of honeycomb network (e.g., femto-cell, femto-cell, pico-cell, etc.) network and micro honeycomb network, etc.) concept. In one example, small cellular networks are used by dedicated base stations. In another example, a small cellular network is a terminal that acts as a master device and temporarily operates as a small cellular network base station. made, and used. The so-called relay node can also be regarded as one of the forms of small cellular network base stations. In addition, the relay node is described in, for example, the technical specification "3GPP TS36.216 version12.0.0 Release 12 "Universal Mobile Telecommunications System (UMTS); LTE; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer for relaying operation" " is described in detail.

(2) Terminal device 200

The terminal device 200 can communicate in a cellular network system (or a mobile communication system). The terminal device 200 performs wireless communication with a wireless communication device (eg, the base station 100A, the main device 100B or 100C) of the cellular network system. For example, the terminal device 200A receives the downlink signal from the base station 100A and transmits the uplink signal to the base station 100A.

(3) Application server 60

The application server 60 is a device that provides services to users. The application server 60 is connected to a packet data network (PDN) 50 . On the other hand, the base station 100 is connected to the core network 40 . The core network 40 is connected to the PDN 50 through a gateway device (not shown). Therefore, the wireless communication device 100 provides the services provided by the application server 60 to the MEC server 300 and the user through the packet data network 50, the core network 40 and the wireless communication channel.

(4) MEC server 300

The MEC server 300 is a service providing device that provides services (applications, content, etc.) to users. The MEC server 300 may be installed in the wireless communication device 100 . In this case, the wireless communication device 100 provides the service provided by the MEC server 300 to the user through the wireless communication path. The MEC server 300 may also be implemented as a logical functional entity, or may be integrally formed with the wireless communication device 100 as shown in FIG. 3 .

For example, the base station 100A provides the service provided by the MEC server 300A to the terminal device 200A connected to the macro cellular network 10 . In addition, the base station 100A provides the service provided by the MEC server 300A to the terminal device 200B connected to the small cellular network 10B through the main device 100B.

In addition, the main device 100B provides the service provided by the MEC server 300B to the terminal device 200B connected to the small cellular network 10B. Similarly, the main device 100C provides the service provided by the MEC server 300C to the terminal device 200C connected to the small cellular network 10C.

(5) Supplement

Although the schematic configuration of the system 1 has been described above, the present technology is not limited to the example shown in FIG. 3 . For example, as the configuration of the system 1, a configuration without a main device, SCE (Small Cell Enhancement), HetNet (Heterogeneous Network), MTC (Machine Type Communication) network, etc.

<<3. Configuration of each device>>

Next, with reference to FIGS. 4 to 6 , the configurations of the wireless communication device 100 , the terminal device 200 , and the MEC server 300 according to an embodiment of the present disclosure will be described.

<3.1. Configuration of wireless communication device>

First, with reference to FIG. 4 , an example of the configuration of the wireless communication device 100 according to an embodiment of the present disclosure will be described. FIG. 4 is a block diagram of an example of the structure of the wireless communication device 100 according to an embodiment of the present disclosure. 4 , the wireless communication device 100 includes an antenna unit 110 , a wireless communication unit 120 , a network communication unit 130 , a memory unit 140 , and a processing unit 150 .

(1) Antenna unit 110

The antenna unit 110 radiates the signal output from the wireless communication unit 120 in the space by means of radio waves. In addition, the antenna unit 110 converts radio waves in space into signals, and outputs the current signals to the wireless communication unit 120 .

(2) Wireless communication unit 120

The wireless communication unit 120 transmits and receives signals. For example, the wireless communication unit 120 sends a downlink signal to the terminal device and receives an uplink signal from the terminal device.

(3) Network communication unit 130

The network communication unit 130 transmits information. For example, the network communication unit 130 transmits information to and receives information from other nodes. For example, the other nodes listed above include other base stations, macro cellular network base stations when the wireless communication device 100 is a small cellular network base station, and core network nodes.

(4) Memory unit 140

The memory unit 140 temporarily or permanently memorizes programs and various data required for the operation of the wireless communication device 100 .

(5) Processing unit 150

The processing unit 150 provides various functions of the wireless communication device 100 . The processing unit 150 includes a relay processing unit 151 , a providing unit 153 , and a notification unit 155 . In addition, the processing unit 150 may further include other components other than these components. That is, the processing unit 150 may perform operations other than those of these constituent elements.

The operations of the relay processing unit 151, the providing unit 153, and the notification unit 155 will be described in detail later.

<3.2. Configuration of terminal device>

Next, an example of the configuration of the terminal device 200 according to an embodiment of the present disclosure will be described with reference to FIG. 5 . FIG. 5 is an embodiment of the present disclosure A block diagram of an example of the configuration of the terminal device 200 described above. 5 , the terminal device 200 includes an antenna unit 210 , a wireless communication unit 220 , a memory unit 230 , and a processing unit 240 .

(l) Antenna unit 210

The antenna part 210 radiates the signal output from the wireless communication part 220 in the space by means of radio waves. In addition, the antenna unit 210 converts the radio waves in the space into signals, and outputs the current signals to the wireless communication unit 220 .

(2) Wireless communication unit 220

The wireless communication unit 220 transmits and receives signals. For example, the wireless communication unit 220 receives the downlink signal from the base station or the main device, and sends the uplink signal to the base station or the main device.

(3) Memory unit 230

The memory unit 230 temporarily or permanently memorizes programs and various data required for the operation of the terminal device 200 .

(4) Processing unit 240

The processing unit 240 provides various functions of the terminal device 200 . The processing unit 240 includes an acquisition unit 241 and a selection processing unit 243 . In addition, the processing unit 240 may further include other components other than these components. That is, the processing unit 240 may perform operations other than those of these constituent elements.

The operations of the acquisition unit 241 and the selection processing unit 243 will be described in detail later.

<3.3. Configuration of MEC server>

Next, an example of the configuration of the MEC server 300 according to an embodiment of the present disclosure will be described with reference to FIG. 6 . FIG. 6 is a block diagram of an example of the structure of the MEC server 300 according to an embodiment of the present disclosure. 6 , the MEC server 300 includes a communication unit 310 , a memory unit 320 , and a processing unit 330 .

(1) Communication section 310

The communication unit 310 transmits and receives signals. For example, the communication unit 310 communicates with the corresponding wireless communication device 100 . If the MEC server 300 is formed as a logical entity and is included in the wireless communication device 100 , the communication unit 310 communicates with the processing unit 150 , for example.

(2) Memory unit 320

The memory unit 320 temporarily or permanently memorizes programs and various data required for the operation of the MEC server 300 . For example, the MEC server 300 can memorize various contents and applications provided to the user.

(3) Processing unit 330

The processing unit 330 provides various functions of the MEC server 300 . The processing unit 330 includes an acquisition unit 331 , a notification unit 333 , a search unit 335 , and a service processing unit 337 . In addition, the processing unit 330 may further include other components other than these components. That is, the processing unit 330 may perform operations other than those of these constituent elements.

The operations of the acquisition unit 331, the notification unit 333, the search unit 335, and the service processing unit 337 will be described in detail later.

<<4. The first embodiment>> <4.1. Technical Features>

First, the technical features of this embodiment will be described.

(1) Provision of services

The MEC server 300 (eg, the service processing unit 337 ) performs processing necessary for providing a service (application program, content, etc.) to the terminal device 200 . The provided service is relayed by the corresponding wireless communication device 100 and sent to the terminal device 200 . Information from the terminal device 200 is also relayed by the wireless communication device 100 and then sent to the MEC server 300 .

In addition, the MEC server 300 is connected to other MEC servers corresponding to other wireless communication devices 100 higher than the corresponding wireless communication device 100 (eg, macro cellular network base stations for small cellular network base stations). 300 to provide services, it may not provide services itself.

The wireless communication device 100 (eg, the relay processing unit 151 ) relays the communication between the terminal device 200 and the core network. In addition, the wireless communication device 100 relays the communication between the terminal device 200 and the MEC server 300 . In this way, the wireless communication device 100 transmits the service provided by the MEC server 300 to the terminal device 200 by its function as a relay node.

(2) Contents of various information

The wireless communication device 100 , the terminal device 200 and the MEC server 300 can exchange various information. The following describes each information exchanged.

(a) Communication Information

The communication information is information related to the communication of the wireless communication device 100 .

(a1) First communication information

The communication information may include information related to wireless communication between the wireless communication device 100 and the terminal device 200 connected to the wireless communication device 100 . Such information is also referred to as first communication information. For example, the first communication information may include information about the base station and the wireless communication with the terminal device connected to the cellular network used by the base station. Specifically, the first communication information may include, for example, an SIB (System Information Block) held by the wireless communication device 100 . In addition, the first communication information The signal system may also be a measurement value of CQI (Channel Quality Indicator) measured between the wireless communication device 100 and the terminal device 200 , or may be information calculated/judged based on the measurement value.

An example of CQI is shown in Table 1 below.

(a2) Second communication information

The communication information may include information related to the communication between the wireless communication device 100 and the MEC server 300 connected to the wireless communication device 100 . Such information is also referred to as second communication information. For example, the second communication information may include information representing at least any one of throughput rate, delay time, or location information. Here, the location information may also include at least either physical location information or meaningful location information. The so-called physical location information is obtained by GPS, etc., and includes longitude and latitude information indicating the location, etc. The so-called meaningful location information is information indicating the meaning of the installed place (for example, the names of the installed rooms, buildings, vehicles, etc., roles, etc.). The second communication information is useful when, for example, the MEC server 300 and the corresponding wireless communication device 100 are physically isolated.

(a3) Third communication information

The communication information may include information related to the communication between the wireless communication device 100 and other wireless communication devices 100 connected to the wireless communication device 100 . Such information is also referred to as third communication information. For example, the third communication information may include: information related to the communication between the macro cellular network base station and the small cellular network base station. To put it more simply, the third communication information is information related to wireless/wired communication between relay nodes. The third communication information may include, for example, throughput rate, delay time, location information, wireless access method, CQI, SIB (System Information Block) held by the wireless communication device 100 , and the like. Here, the location information may also include at least either physical location information or meaningful location information.

An example of the communication information has been described above. The first, second, and third communication information are collectively referred to as communication information unless it is necessary to distinguish them.

(b) API Information

API information includes: information indicating whether the API required to provide communication information is available. Indicates whether information is available or not, or It contains information indicating the presence or absence of the API, and may also include information indicating whether the API is open or closed. That is, the API information may include information indicating whether there is an API (whether it is defined), and if sometimes it has been opened. In addition, API can be defined in various ways in addition to providing communication information. For example, it can also be defined that: for the wireless communication device 100 , APIs required for changing the relevant settings of the wireless communication required to meet the level required by the application (eg, delay and transmission speed, etc.) are required. The API information may also include information indicating whether the API can be used or not.

In addition, the API information may also include information indicating whether the API related to the QoS request is available. Examples of APIs related to QoS requirements include: CQI (QoS Class Identifier) information, PCC (Policy and charging control) information, TEID (Tunnel Endpoint ID), SPID (Subscriber Profile ID), QCI (Quality Class Indicator) ) to obtain or set the required API. In addition, as APIs related to QoS requirements, there are APIs required for bandwidth requirements or packet filtering requirements. In addition, related CQI information, for example, in the technical specification "3GPP TS23.203 V13.4.0 Release 13 "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Policy and charging control architecture" "Table 6.1.7: Standardized" There are detailed records in QCI characteristics". In addition, the PCC information is described in detail in, for example, "Table 6.3: The PCC rule information" in the same technical specification.

Also, the API information system may also include: Whether the related API of the instance is available information. As the related API of the entity, for example, the creation, execution and termination of the entity, the request for moving the entity to different servers, and the API required for parameter setting can be cited.

(3) Exchange of information (a) Wireless communication device 100

The wireless communication device 100 (eg, the providing unit 153 ) provides the communication information to the MEC server 300 . Specifically, the wireless communication device 100 defines an API, and provides communication information through the API. In the upper layer, the API information can be obtained by using the API, and the communication information can also be obtained if it is available. API, which is a RESTful API, is ideal. For example, when the wireless communication device 100 receives a GET request (GET command of the HTTP protocol), it sends back the communication information.

In addition, the wireless communication device 100 (eg, the providing unit 153 ) can switch the API on and off according to an instruction from the operator or autonomously. In this way, the operator can switch the API on and off according to needs.

The wireless communication device 100 (eg, the notification unit 155 ) may also notify the terminal device 200 of the API information. In addition, the wireless communication device 100 may notify the information indicating the presence or absence of the corresponding MEC server 300, the content of the service provided by the MEC server 300, and the like. For example, the wireless communication device 100 may use the RRC (Radio Resource Control) layer defined in 3GPP as one of means to notify the terminal device 200 of API information and the like as notification information. For example, wireless The communication device 100 may also broadcast API information and the like as SIB information.

Here, the base station of E-UTRAN (Evolved Universal Terrestrial Radio Access Network) broadcasts various information to the terminal device. For example, as shown in Table 2 below, a total of 14 types of master information blocks (Master Information Block) and 13 types of system information blocks (System Information Block) are reported. The base station 100 may add API information and the like to these information and report it. In addition, the so-called neighbor means the surrounding honeycomb network of the own honeycomb network.

(b) Terminal device 200

The terminal device 200 (eg, the obtaining unit 241 ) obtains the API information provided by the wireless communication device 100 and related to the API used by the MEC server 300 . However, from the terminal device 200 to the MEC server The communication path of 300 may sometimes include a plurality of wireless communication devices 100 (eg, a macro cellular network base station and a small cellular network base station). As a result, the terminal device 200 is provided by more than one wireless communication device 100 (such as a macro cellular network base station and a small cellular network base station) included in the communication path all the way to the MEC server 300 . API information related to the API can be obtained. Similarly, the terminal device 200 (for example, the obtaining unit 241 ) obtains the communication information. Thereby, the terminal device 200 can grasp the status of a series of communication between the terminal device 200 and the MEC server 300 via one or more wireless communication devices 100 and/or whether the API can be used.

(c) MEC server 300

The MEC server 300 (eg, the obtaining unit 331 ) obtains API information related to the API provided by the wireless communication device 100 . Then, the MEC server 300 (eg, the notification unit 333 ) notifies the terminal device 200 of the acquired API information. Thereby, the terminal device 200 can obtain the API information.

The opening and closing of the API can be changed according to the needs of the operator. Therefore, the MEC server 300 (for example, the obtaining unit 331 ) can also periodically perform inquiries, etc., to repeatedly obtain the API information. Thereby, the MEC server 300 can grasp the switching of whether the API can be used or not. The MEC server 300 (for example, the notification unit 333 ) can also notify the API information obtained repeatedly at arbitrary timings such as each time it is obtained or each time it changes. In this way, the terminal device 200 can also grasp whether the API can be used or not. switch.

In addition, the MEC server 300 (for example, the acquisition unit 331 ) acquires the communication information by using the API. Thereby, the MEC server 300 can obtain the communication information. Then, the MEC server 300 (eg, the notification unit 333 ) notifies the terminal device 200 of the acquired communication information. Thereby, the terminal device 200 can obtain the communication information.

Communication information may be obtained separately from API information, or may be obtained together. An example obtained together will be described below. For example, the MEC server 300 (eg, the acquisition unit 331 ) acquires API information based on the result of using the API. The so-called result of use refers to whether there is a response, and if there is a response, it refers to its content. For example, the MEC server 300 (eg, the obtaining unit 331 ) uses an API to request communication information (eg, sending a GET request). On the other hand, if there is no response, the MEC server 300 determines that there is no API. Also, if there is a response that does not contain communication information, the MEC server 300 determines that there is an API, but is blocked. Also, if there is a response including communication information, the MEC server 300 determines that there is an API, but it is opened.

The above response may also have the same status code as the HTTP status code shown in Table 3 below. In addition, for each status code, the presence or absence of the corresponding API and the opening and closing can also be established respectively.

(5) Processing corresponding to the acquired information (a) Terminal device 200

For example, the terminal device 200 (eg, the selection processing unit 243 ) performs processing required for selecting the MEC server 300 of the service providing source based on the acquired API information. In this way, the terminal device 200 can select an appropriate service providing source according to the API information. More specifically, the terminal device 200 (eg, the selection processing unit 243 ) selects the MEC server 300 that can be used by the API based on the API information, and preferentially selects it as a service providing source. For example, the MEC server 300 corresponding to the wireless communication device 100 that has an API and is open is selected as the service providing source. In this way, the terminal device 200 can receive the application program from the MEC server 300 which can adaptively set the operation in consideration of the availability of the API.

In addition, the case where the API has not been opened and the case where there is no API can have different processing results. For example, even if the API is not released, if it is only temporarily, the terminal device 200 can select the MEC server 300 whose API is unavailable.

In addition, the terminal device 200 (for example, the selection processing unit 243 ) may also select the MEC server from which the service is provided based on the communication information. device 300. Thereby, the terminal device 200 can accept the provision of an application program whose adaptive action setting is performed in consideration of the communication status between the terminal device 200 and the MEC server 300 .

Here, the terminal device 200 (for example, the selection processing unit 243 ) is executed when the terminal device 200 itself is not included under the management of the wireless communication device 100 corresponding to the MEC server 300 selected as the service providing source. Communication path change processing so that it is included under management. The term "under the management of the wireless communication device 100" means that there is a terminal device 200 connected to the wireless communication device 100, or to the main device connected to the wireless communication device 100 (macrocell base station), there is a terminal device 200. Connecting etc. For example, if the base station corresponding to the selected MEC server 300 is different from the serving base station, the terminal device 200 regards the base station corresponding to the selected MEC server 300 as the target base station and takes over. In this way, the terminal device 200 can change the communication path and receive the service provision when it is difficult to receive the service provision from the MEC server 300 using the established communication path.

In addition, the communication path from the terminal device 200 to the MEC server 300 may sometimes include a plurality of wireless communication devices 100 (eg, a macro cellular network base station and a small cellular network base station). In this case, the terminal device 200 (for example, the selection processing unit 243 ) is on the communication path up to the MEC server 300 that has been selected as the service provider source, and if the wireless communication device 100 whose API is unavailable, communicates Path change processing to become other wireless communication devices that will be available via API 100 to communicate with the MEC server 300. For example, if the terminal device 200 is on the communication path up to the macro cellular network base station corresponding to the MEC server 300, and contains a small cellular network base station whose API is unavailable, then go to other small cellular network bases whose API is available. The station takes over and communicates with the MEC server 300 . Thereby, the terminal device 200 can receive service provision from the MEC server 300 in a state in which only the wireless communication device 100 whose API is usable is included in the communication path.

(b) MEC server 300

The MEC server 300 (eg, the discovery unit 335 ) can also discover other wireless communication devices 100 for which the API is available. For example, the MEC server 300 performs a search when the API information indicating that the API is unavailable has already been acquired. Exploration, the system can also be limited to, for example, the surrounding honeycomb network.

The search may be performed on an occasional basis by an inquiry from the terminal device 200, or may be performed periodically. The MEC server 300 (eg, the memory unit 320 ) may also store information indicating the search results. Then, the MEC server 300 (for example, the notification unit 333 ) may also notify the stored information indicating the search result in response to the inquiry from the terminal device 200 .

The information representing the search result includes: identification information of the other wireless communication device 100 discovered, identification information of the MEC server 300 corresponding to the other wireless communication device 100 , and API provided from the other wireless communication device 100 related information. Even, the information representing the exploration result may contain communication information.

An example of information indicating the search results is shown in the table below 4.

In addition, "Server No.", "Host name" and "IP address" correspond to identification information of other MEC servers 300 . "eNB information" includes identification information of other wireless communication devices 100 corresponding to other MEC servers 300 . The "API information" is equivalent to information about APIs provided from other wireless communication devices 100 . "Latency Time", "Band", "Geolocation Database" and "Location Information" are equivalent to communication information. In addition, the "Geolocation Database" contains information indicating the available time band and maximum output power for each frequency. information on the rate (ie the maximum transmission power). In addition, "location information", as shown in Table 4, includes substantial location information and meaningful location information. Hereinafter, this list represents the information of the exploration result, also known as the neighbor list. In addition, the unit information in the neighbor list (for example, a row in Table 4) is also called neighbor information. The neighbor list may also contain neighbor information of the MEC server 300 itself. For example, in the example shown in Table 4, the row of "Server No. 1" is the neighbor information of the MEC server 300 itself that maintains this neighbor list. In addition, in addition to the search results, the MEC server 300 may also memorize, for example, a list of the terminal devices 200 connected to the corresponding wireless communication device 100, or information of the terminal devices 200, etc., and related information of the terminal devices 200. .

The MEC server 300 (eg, the service processing unit 337 ) performs the operation setting of the application based on the communication information obtained by using the API. For example, the MEC server 300 performs operation settings such as data format, data transmission rate, content codec, data length, and the like. By starting communication through such an action setting, the MEC server can optimize the application provided.

In addition, the MEC server 300 (eg, the service processing unit 337 ) may request the wireless communication device 100 to change the communication setting based on the communication information obtained by using the API. For example, the MEC server 300 may also request the modulation method, transmission power, allocation of wireless resources (frequency resources or time resources, etc.) to the wireless communication device 100 connected to the terminal device 200 of the service providing target. Changes in message settings. In response to the request, the wireless communication device 100 (eg, the relay processing unit 151 ) sends the wireless Communication related settings are changed. Thereby, the MEC server 300 can provide, for example, a communication environment that satisfies the level required by the application.

(7) UI example

The terminal device 200 (eg, the selection processing unit 243 ) can also select the MEC server 300 from which the service is provided based on user operations. An example of UI related to this user operation will be described with reference to FIG. 7 and FIG. 8 .

FIG. 7 is an explanatory diagram for explaining an example of UI displayed on the terminal device 200 according to the present embodiment. As shown in FIG. 7, in the UI example 401, the small icons 403 of the application are displayed in plural. The color difference of the small icon 403 is generated according to whether the MEC server 300 of the service providing source can use the API. For example, the small icon 403A represents that the service is provided from the MEC server 300 which can use the API. In addition, the small icon 403B shows that the service is provided from the MEC server 300 which cannot use the API. On the other hand, in the UI example 402, instead of the difference in color, light and off is used to express whether or not the API can be used.

FIG. 8 is an explanatory diagram for explaining an example of UI displayed on the terminal device 200 according to the present embodiment. As shown in FIG. 8 , in the UI examples 411 to 413 , whether or not the API can be used is expressed by the difference in the color of the small icon 403 . For example, in the UI example 411, when the small icon 403C indicating that the service is provided from the MEC server 300 that cannot use the API is touched, the screen transitions to the UI example 412. In the UI example 412, a selection window 404 necessary for user operation for accepting whether to change the network is displayed. Here, once the user selects "YES", the The terminal device 200 selects the MEC server 300 of the service providing source, and selects (takes over) the wireless communication device 100 of the connection destination accompanying this. Once the network is changed, as shown in the UI example 413, the color of the small icon 430 changes to the color indicating that the service is provided from the MEC server 300 which can use the API.

<4.2. Specific example> <4.2.1. Case 1>

This specific example is an example in which the service is provided from the MEC server 300 corresponding to the base station 100 (eg, the macro cellular base station) to which the terminal device 200 is connected.

(1) Basic relationship of each device

First, with reference to FIG. 9 , the basic relationship of each device will be described.

FIG. 9 is an explanatory diagram for explaining an example of a communication path between the apparatuses described in this specific example. The UE corresponds to the terminal device 200 . The eNB corresponds to the wireless communication device 100 . The server system corresponds to the MEC server 300 . Solid double arrows indicate physical connections. The dotted double arrows indicate logical connections (IP connections). As shown in FIG. 9 , the UE establishes a wireless connection with the eNB. The eNB is connected to the Server.

The eNB includes MNM (MEC Network Manager). The MNM is a logical entity required to implement the related technical features of the wireless communication device 100 described above. The eNB, based on the control performed by the MNM, performs specific processing such as the provision of communication information. MNM series example For example, it is implemented as an intermediary software (software) installed in the wireless communication device 100 .

The UE system contains MCM (MEC Client Manager). The MCM is a logical entity required for realizing the related technical features of the terminal device 200 described above. The UE performs specific processing such as wireless connection based on the control performed by the MCM. The MCM system is realized, for example, as a middleware (software) installed in the terminal device 200 .

The Server system includes MAM (MEC Application Manager). MAM is a logical entity required for realizing the related technical features of the MEC server 300 described above. Server, based on the control done by MAM, performs specific processing such as service provision. The MAM system is implemented, for example, as a middleware (software) installed in the MEC server 300 .

MCM and MAM are logically connected and can send and receive information. MAM and MNM are logically connected and can send and receive information. Here, MAM uses the API described above to send and receive information to and from MNM.

(2) Basic processing flow

Next, with reference to FIG. 10 , an example of the flow of processing performed in each device having the basic relationship described above will be described.

FIG. 10 is a flowchart showing an example of the flow of the confirmation process of API information executed in the system 1 according to this specific example. In this procedure, UE, Server, and eNB participate.

As shown in FIG. 10, first, the UE sends a GET request of the HTTP/Web-API command to the Server (step S101). A GET request is an information requesting the return of at least either API information or communication information. Next, the Server also sends a GET request to the eNB (step S102). The eNB receiving the GET request sends the HTTP/Web-API response to the Server (step S103). The response contains at least either API information or communication information. Then, the Server system transmits the response to the UE similarly (step S104).

FIG. 11 is a flowchart showing an example of the flow of the confirmation process of API information executed in the system 1 according to this specific example. In this procedure, UE, Server, and eNB participate. In this program, messages are sent and received by any unique protocol other than HTTP/Web-API.

As shown in FIG. 11, the UE and the Server establish a UDP/IP or TCP/IP session using a unique protocol other than HTTP/Web-API (step S105). Next, the UE sends the information request message of the unique agreement to the Server (step S106). An information request message is a message that requests the return of at least one of API information or communication information. Next, the Server also sends the information request message to the eNB (step S107). After receiving the information request message, the eNB sends the unique protocol response message to the Server (step S108). The response message contains at least one of API information or communication information. Then, the Server system similarly transmits the reply message to the UE (step S109).

In addition, the communication between the Server and the eNB can also use Use HTTP/Web-API. Specifically, in the above-mentioned step S107, the Server can also send the GET request of the HTTP/Web-API command to the eNB. In addition, in the above-mentioned step S108, the eNB may also send the HTTP/Web-API response to the Server.

(3) The specific relationship of each device

Next, with reference to FIG. 12, an example of the specific relationship of each apparatus is demonstrated.

FIG. 12 is an explanatory diagram for explaining an example of a communication path between apparatuses according to this specific example. The numbers indicated by UE, eNB and Server represent the indices of each device. The solid lines in this figure represent wired connections or wireless connections, and the dotted lines represent wireless connections. The dashed line of reference numeral 421 represents the established wireless connection, and the dashed line of reference numeral 422 represents the wireless connection of the handover candidate. References to logical connections are omitted. For example, UE-1 is connected to eNB-1 as indicated by symbol 421 . When the eNB-1 has an API and is open, the UE-1 is connected to the eNB-1 without changing, and receives service provision from the Server-1. On the other hand, if there is no API in eNB-1, or if there is an API but it is blocked, UE-1 attempts to take over to eNB-2 as indicated by reference numeral 422. The UE-1 may attempt to take over to any eNB such as the eNB-3 other than the eNB-2.

Here, the relationship between eNB-1 and eNB-2 may be considered in various ways. For example, the honeycomb nets used may or may not overlap. Also, it can be used by the same or different operators. Also, different wireless access methods (3G/4G/5G/W-Fi (registered trademark), etc.) may be used. also profitable Part or all of the frequency bands used may overlap, or none of them may overlap. Also, one eNB may be shared by a plurality of companies.

(4) Specific processing flow

Next, with reference to FIGS. 13-16, an example of the flow of the process performed in each apparatus which has the specific relationship demonstrated above is demonstrated.

(Processing of the terminal device 200 alone)

Hereinafter, the detailed conditional divergence will be described focusing on UE-1 with reference to FIGS. 13 and 14 first.

FIG. 13 is a flowchart showing an example of the flow of the application program start processing executed in the UE-1 according to this specific example.

As shown in FIG. 13, first, UE-1 starts the application (step S202).

Next, UE-1 establishes a wireless connection with the eNB (step S204). For example, UE-1 establishes a wireless connection with eNB-1 based on a preset setting (eg, a connection condition based on an operator's contract). Next, UE-1 establishes an IP connection with the Server (step S206). For example, UE-1 establishes an IP connection with Server-1 corresponding to the connected eNB-1. Then, UE-1 sends a request for API information to the Server (MAM), and receives a response from the Server (step S208).

If it is determined that the API is available (step S210/YES), and the eNB that is available for the API is the serving eNB (step S212/YES), the UE-1 directly accepts service provision (step S214). Furthermore, once the After the process in step S224 to be described later, an eNB whose API is available may not be the serving eNB. The API is to determine whether the usable eNB is the serving eNB, for example, by checking the ECGI (E-UTRAN Cell Global ID) or eNB ID of the two eNBs. FIG. 14 is an explanatory diagram for explaining the configuration of the ECGI. As shown in FIG. 14 , the ECGI is composed of: a PLMN (Public Land Mobile Network) number (PLMN identity) and a cellular network number (Cell identity). In addition, the cellular network number is composed of: a macro eNB number (Macro eNB identity) and a macro cellular network number (Macro Cell identity).

On the other hand, if it is determined that the API is available (step S210/YES), and the eNB whose API is available is not the serving eNB (step S212/NO), the UE-1 takes over from the eNB whose API is available. (step S215). For example, UE-1, takes over to eNB-2 where eg API is available. If the takeover is successful (step S216/YES), UE-1 receives the service provision from Server-2 (step S214). If the takeover fails (step S216/NO), UE-1 re-takes over to the original eNB (step S217 ), and receives service provision from Server-1 (step S214 ).

Furthermore, if it is determined that the API is not usable (step S210/NO), and when it is allowed to be disabled (step S218/YES), the UE-1 directly accepts the provision of the service (step S214).

On the other hand, if it is determined that the API is not usable (step S210/NO), and the inability to be used is not allowed (step S218/NO), UE-1 searches for another server (step S220). For example, UE-1 will request the Server for information about other Servers and eNBs that can use the API. beg. This request can also be a request for neighbor information. In addition, this request may also contain, for example, the information of the application program that has been activated by the UE-1, or the information indicating the desired service quality.

If it is determined that the search is successful (step S222/YES), the UE-1 sets the IP address of the discovered Server as a connection target (step S224). After that, the process returns to step S206.

On the other hand, if it is determined that the exploration fails (step S222/NO), the UE-1 directly accepts the provision of the service (step S214).

With the above, the process ends.

In addition, in step S224, the server of the connection target can be selected by the server in the connection, and can also be selected by the eNB.

(Processing of the whole system 1)

Next, with reference to FIG. 15 , an example of the flow of processing when UE-1 is connected to eNB-1 and accepts service provision will be described.

FIG. 15 is a flowchart showing an example of the flow of the service providing process executed in the system 1 according to this specific example. In this procedure, UE-1, Server-1, and eNB-1 are involved.

As shown in FIG. 15, first, UE-1 establishes a wireless connection with eNB-1 (step S302). Next, UE-1 establishes an IP connection with Server-1 (step S304). Then, UE-1 sends a request for API information to Server-1 (step S306).

Next, Server-1 establishes an IP connection with eNB-1 (step S308). Next, Server-1 uses the API provided by eNB-1 to eNB-1 obtains API information (step S310). In addition, if Server-1 maintains a neighbor list, these processes can also be omitted.

Next, Server-1 sends the response of the API information to UE-1 (step S312). It is assumed that the API information indicates that there is an API in eNB-1 and it is open. In this case, Server-1 starts service to UE-1 (step S314).

With the above, the process ends.

Next, referring to FIG. 16 , an example of the flow of processing when UE-1 switches the connection destination from eNB-1 to eNB-2 and receives service provision will be described.

FIG. 16 is a flowchart showing an example of the flow of the service providing process executed in the system 1 according to this specific example. In this procedure, UE-1, Server-1, eNB-1, Server-2, and eNB-2 are involved.

As shown in FIG. 16 , the processes described in steps S402 to S412 are the same as the processes described in steps S302 to S312 shown in FIG. 15 . However, it is assumed that the API information obtained in step S412 indicates that there is no API in the eNB-1, or that the API is present but locked.

In this case, UE-1 sends a request for neighbor information related to other servers to Server-1 (step S414).

Next, Server-1 and Server-2 establish an IP connection (step S416). Next, Server-1 obtains neighbor information of eNB-2 from Server-2 (step S418). In addition, if Server-1 maintains a neighbor list, these processes can also be omitted.

Next, Server-1 sends the response of neighbor information to to UE-1 (step S420). The neighbor information contained in the response can also be limited to an eNB that has an API and is open.

Next, UE-1 establishes a wireless connection with eNB-2 based on the neighbor information (step S422). For example, UE-1 establishes a wireless connection with an open eNB with API from neighbor information. Next, UE-1 establishes an IP connection with Server-2 (step S424). Then, UE-1 sends a request for API information to Server-2 (step S426).

Next, Server-2 establishes an IP connection with eNB-2 (step S428). Next, Server-2 obtains API information from eNB-2 using the API provided by eNB-2 (step S430). In addition, if Server-2 maintains a neighbor list, these processes can also be omitted.

Next, Server-2 sends the response of the API information to UE-1 (step S432). It is assumed that the API information indicates that there is an API in eNB-2 and it is open. In this case, Server-2 starts service to UE-1 (step S434).

With the above, the process ends.

In addition, in step S412, neighbor information can also be sent together with the API information. In this case, the processing described in steps S414 to S420 is omitted.

In addition, before step S422, UE-1 first confirms whether the target eNB is suitable based on the neighbor information, and then attempts the wireless connection. For example, UE-1 may first confirm the principle of connecting to the target network shown in the neighbor information, etc., and then try to connect wirelessly.

<4.2.2. Second case>

This specific example is a form in which the service is provided from the MEC server 300 corresponding to the main device 100 (for example, a small cellular base station or a dynamic AP) to which the terminal device 200 is connected.

(1) Basic relationship of each device

First, with reference to FIG. 17 , the relationship of each device will be described.

FIG. 17 is an explanatory diagram for explaining an example of a communication path between the apparatuses according to this specific example. The UE Slave is equivalent to the terminal device 200 connected to the main device 100 . The UE Slave is also referred to as Slave for short below. The UE/eNB Master is equivalent to the master device 100 (eg, a small cellular network base station or a dynamic AP). The UE/eNB Master is also referred to as Master for short below. The server system corresponds to the MEC server 300 . Solid double arrows indicate physical connections. The dotted double arrows indicate logical connections (IP connections).

The Master line contains MNM. Master, based on the control done by MNM, carries out specific processing such as the provision of communication information.

The Slave line contains MCM. Slave, based on the control done by MCM, performs specific processing such as wireless connection.

As shown in Figure 17, the Slave establishes a wireless connection with the Master. The Master system is connected to the Server. In addition, MCM and MAM are logically connected and can transmit and receive information. MAM and MNM are logically connected and can send and receive information.

(2) The specific relationship of each device

Next, with reference to FIG. 18, an example of the specific relationship of each apparatus is demonstrated.

FIG. 18 is an explanatory diagram for explaining an example of a communication path between apparatuses according to this specific example. The numbers indicated by Slave, Master and Server indicate the index of each device. The solid lines in this figure represent wired connections or wireless connections, and the dotted lines represent wireless connections. The dashed line of the reference numeral 431 represents the established wireless connection, and the dashed line of the reference numeral 432 represents the wireless connection of the handover candidate. References to logical connections are omitted. For example, Slave-1 is connected to Master-1 as indicated by symbol 431. Also, Master-1 is connected to eNB-1. When Master-1 has an API and is open, Slave-1 is connected to Master-1 unchanged, and receives service provision from Server-1. On the other hand, if there is no API in Master-1, or there is API but it is blocked, Slave-1 will try to take over from Master-2 as indicated by the symbol 432. Slave-1, in addition to Master-2, can also try to take over from any Master such as Master-3.

(3) Specific processing flow

FIG. 19 shows an example of the flow of processing performed in each device having the specific relationship described above.

FIG. 19 is a flowchart showing an example of the flow of the service providing process executed in the system 1 according to this specific example. In this program, Slave-1, Server-1, MAM-1, Master-1, and MNM-1, and Server-2, MAM-2, Master-2, and MNM-2 participate. Figure 19 As shown, the processes described in steps S502 to S534 are the same as the processes described in steps S402 to S434 shown in FIG. 16 . Regarding the description of FIG. 19 , it is sufficient to read “UE” as “Slave” and “eNB” as “Master” in the description of FIG. 16 above.

<4.2.3. The third case>

In this specific example, the terminal device 200 is provided from the MEC server 300 corresponding to the base station 100 (such as a macro cellular base station) connected to the main device 100 (such as a small cellular network base station or dynamic AP) connected to the terminal device 200. form of service.

(1) The specific relationship of each device 1

Hereinafter, an example of a specific relationship of each device will be described with reference to FIG. 20 .

FIG. 20 is an explanatory diagram for explaining an example of a communication path between the apparatuses according to this specific example. The numbers denoted by Slave, Master, eNB and Server represent the indexes of each device. The solid lines in this figure represent wired connections or wireless connections, and the dotted lines represent wireless connections. The dashed line of the reference numeral 441 represents the established wireless connection, and the dashed line of the reference numeral 442 represents the wireless connection of the handover candidate. References to logical connections are omitted. Also, in this specific example, no service is provided from the server system corresponding to the master. Therefore, in this figure, the Server corresponding to the Master is omitted, and only the MAM is shown.

For example, Slave-1 is connected to Master-1. Also, Master-1 is connected to eNB-1 as indicated by reference numeral 441 . Master- 1 has an API and is open, and eNB-1 has an API and is open, Slave-1 is connected to Master-1 unchanged, and Master-1 is connected to eNB-1 unchanged, it will receive services from Server-1 provided. On the other hand, if there is no API in the Master-1 or eNB-1, or there is an API but it is blocked, at least one of the change of the communication path or the change of the server of the service providing source is attempted.

For example, if there is no API in eNB-1, or there is an API but it is blocked, Master-1 tries to take over to eNB-2 as indicated by symbol 442 . Master-1, in addition to eNB-2, can also try to take over to any eNB such as eNB-3.

(2) Specific processing flow 1

Next, with reference to FIG. 21 , an example of the flow of processing performed in each device having the specific relationship described above will be described.

FIG. 21 is a flowchart showing an example of the flow of the service providing process executed in the system 1 according to this specific example. In this procedure, Slave-1, MAM-4, Master-1, Server-1, eNB-1, Server-2, and eNB-2 participate.

As shown in FIG. 21, first, Slave-1 establishes a wireless connection with Master-1 (step S602). Furthermore, the Master-1 establishes a wireless connection with the eNB-1 (step S604). Next, Slave-1 establishes an IP connection with MAM-4 (step S606). Then, Slave-1 sends a request for API information to MAM-4 (step S608).

Next, MAM-4 establishes an IP connection with Master-1 (step step S610). Next, MAM-4 uses the API provided by Master-1 to obtain API information from Master-1 (step S612). In addition, if MAM-4 maintains a neighbor list, these processes can also be omitted.

Next, MAM-4 establishes an IP connection with Server-1 (step S614). Then, MAM-4 sends a request for API information to Server-1 (step S616).

Next, Server-1 establishes an IP connection with eNB-1 (step S618). Next, Server-1 obtains API information from eNB-1 using the API provided by eNB-1 (step S620). In addition, if Server-1 maintains a neighbor list, these processes can also be omitted.

Next, Server-1 sends the response of the API information to MAM-4 (step S622). Next, MAM-4 sends the response of the API information obtained in steps S614 and S622 to Slave-1 (step S624).

Next, in MAM-4, judgment processing is performed (step S626). For example, MAM-4, based on the obtained API information, determines whether to change the communication path and whether to change the server that provides the service. Here, it is assumed that the acquired API information indicates that there is no API in eNB-1, or that although there is an API, it is blocked. In this case, although not shown in Figure 21, MAM-4 obtains the neighbor information related to other Servers from Sever-1. It is assumed that the obtained neighbor information contains, has API, and is an open eNB, which is the related information of eNB-2. In this case, MAM-4 selects eNB-2 as the connection target. Hereinafter, an example of the processing flow at this time will be described.

MAM-4 entrusts Master-1 with switching of the connection destination (step S628). Next, Master-1 establishes a wireless connection with eNB-2 (step S630). Next, MAM-4 establishes an IP connection with Server-2 (step S632). Then, MAM-4 sends a request for API information to Server-2 (step S634).

Next, Server-2 establishes an IP connection with eNB-2 (step S636). Next, Server-2 obtains API information from eNB-2 using the API provided by eNB-2 (step S638). In addition, if Server-2 maintains a neighbor list, these processes can also be omitted.

Next, Server-2 notifies UE-1 of completion of preparation via MAM-4 (Server Ready contact) (step S640), and starts the service (step S642).

With the above, the process ends.

(3) The specific relationship of each device 2

Next, another example of the specific relationship of each device will be described with reference to FIG. 22 .

FIG. 22 is an explanatory diagram for explaining an example of a communication path between apparatuses according to this specific example. The numbers denoted by Slave, Master, eNB and Server represent the indexes of each device. The solid lines in this figure represent wired connections or wireless connections, and the dotted lines represent wireless connections. The dashed line of the reference numeral 451 represents the established wireless connection, and the dashed line of the reference numeral 452 represents the wireless connection of the handover candidate. References to logical connections are omitted. Also, in this specific example, no service is provided from the server system corresponding to the master. because In this figure, the Server corresponding to the Master is omitted, and only the MAM is shown.

For example, Slave-1 is connected to Master-1 as indicated by symbol 451 . Also, Master-1 is connected to eNB-1. When Master-1 has an API and is open, and eNB-1 has an API and is open, Slave-1 is connected to Master-1 unchanged, and Master-1 is connected to eNB-1 unchanged. Accept the provision of services. On the other hand, if there is no API in the Master-1 or eNB-1, or there is an API but it is blocked, at least one of the change of the communication path or the change of the server of the service providing source is attempted.

For example, if there is no API in Master-1, or there is API but it is blocked, Slave-1 will try to take over from Master-2 as indicated by symbol 452. Slave-1, in addition to Master-2, can also try to take over from any Master such as Master-3.

(4) Specific processing flow 2

Next, with reference to FIG. 23 , an example of the flow of processing performed in each device having the specific relationship described above will be described.

FIG. 23 is a flowchart showing an example of the flow of the service providing process executed in the system 1 according to this specific example. Slave-1, MAM-4, Master-1, Server-1, eNB-1, MAM-5, Master-2, Server-2, and eNB-2 participate in this procedure.

As shown in FIG. 23 , the processes described in steps S702 to S724 are the same as the processes described in steps S602 to S624 shown in FIG. 21 .

Then, in Slave-1, judgment processing is performed (step S726). For example, Slave-1, based on the acquired API information, determines whether to change the communication path and whether to change the server that provides the service. Here, it is assumed that the acquired API information indicates that there is no API in eNB-1 and Master-1, or that although there is an API, it is blocked. In this case, although not shown in Figure 23, Slave-1 obtains the neighbor information related to other Servers from Sever-1. It is assumed that the obtained neighbor information contains, has API, and is an open Master and eNB, which is the related information of Master-2 and eNB-2. In this case, Slave-1 selects Master-2 and eNB-2 as connection targets. Hereinafter, an example of the processing flow at this time will be described.

Slave-1 establishes a wireless connection with Master-2 (step S728). Next, the Master-2 establishes a wireless connection with the eNB-2 (step S730). Next, Slave-1 establishes an IP connection with MAM-5 (step S732). Then, Slave-1 sends a request for API information to MAM-5 (step S734).

Next, MAM-5 establishes an IP connection with Master-2 (step S736). Next, MAM-5 uses the API provided by Master-2 to obtain API information from Master-2 (step S738). In addition, if MAM-5 maintains a neighbor list, these processes can also be omitted.

Next, MAM-5 establishes an IP connection with Server-2 (step S740). Then, MAM-5 sends a request for API information to Server-2 (step S742).

Next, Server-2 establishes an IP connection with eNB-2 (step S744). Next, Server-2 obtains API information from eNB-2 using the API provided by eNB-2 (step S746). In addition, if Server-2 maintains a neighbor list, these processes can also be omitted.

Next, Server-2 notifies UE-1 of completion of preparation via MAM-5 (Server Ready contact) (step S748), and starts the service (step S750).

With the above, the process ends.

In addition, if there is no API in Master-1, or although there is an API but it is blocked, but there is an API in eNB-1 and it is open, UE-1 will set Server-1 as the service provider, and only connect the communication path from Master-1 to the service provider. -1 switches to Master-2.

<<5. Supplement>>

Next, supplementary matters will be described with reference to FIGS. 24 to 31 .

FIG. 24 is an explanatory diagram for explaining supplementary matters related to the system 1 according to an embodiment of the present disclosure. As shown in FIG. 24, the wireless communication device 100, as RRH (Remote Radio Head) and BBU (Base Band Unit) connected by CPRI (Common Public Radio Interface), is a form of plural devices that can also be separated geographically, and be formed. The RRH system can also be, for example, provided by each operator individually. The BBU can also be shared, for example, by a plurality of operators.

FIG. 25 is an explanatory diagram for explaining supplementary matters related to the system 1 according to an embodiment of the present disclosure. The example shown in Figure 25 is SDN (Software-Defined Networking)/NFV (Network Functions Virtualization) architecture. In System 1, the interfaces defined in SDN/NFV can also be utilized. For example, for the communication between MAM and MNM, SWA-1/SWA-2 can also be used. In addition, SWA-5 can also be used for the communication between the MNM and the Master or eNB or other core network entities (eg PCRF/HSS/MME/Geolocation Data-base, etc.). In addition, Fig. 25 refers to "ETSI, "GS NFV-SWA 001 V1.1.1 (2014-12)", December 2014, [retrieved on June 12, 2014], Internet <http:// www.etsi.org/deliver/etsi_gs/NFV-SWA/001_099/001/01.01.01_60/gs_NFV-SWA001v010101p.pdf>”.

Next, referring to FIGS. 26 to 31 , an example of communication between the MEC server 300 and the expected components and other devices when the communication protocol between the devices of the LTE EPC is used is shown. In addition, Figures 26 to 31 are based on "Magnus Olsson, Catherine Mulligan, "EPC and 4G Packet Networks, Second Edition: Driving the Mobile Broadband Revolution," 2nd Edition, Academic Press, December 12, 2012 's diagram.

For example, when the information held by the devices in the EPC is pulled out due to a request from the MAM, the communication protocol between the devices in the EPC is assumed to be used. In particular, principle information from HSS, priority control on packet units, or other principle setting information, etc., from PCRF (Policy and Charging Rules Function), BBERF (Bearer Binding and Event Reporting Function), or PCEF (Policy and Charging Enforcement Function), it is expected that the communication protocol between the EPC machines will be used.

FIG. 26 is a diagram illustrating an example of a communication protocol used between devices included in the system 1 according to an embodiment of the present disclosure. FIG. 26 shows an example of the user data path (IP transmission path) in the terminal device 200 (MCM) and the MEC server 300 (MAM).

FIG. 27 is a diagram illustrating an example of a communication protocol used between devices included in the system 1 according to an embodiment of the present disclosure. In FIG. 27, the path of the user data in the terminal device 200 (MCM), the MEC server 300 (MAM), the S-GW, the P-GW, and the application server (Source-Server) ( An example of IP transmission path).

FIG. 28 is a diagram illustrating an example of a communication protocol used between devices included in the system 1 according to an embodiment of the present disclosure. FIG. 28 shows an example of a path (IP transmission path) for control information in the terminal device 200 (MCM) and the MEC server 300 (MAM).

FIG. 29 is a diagram illustrating an example of a communication protocol used between devices included in the system 1 according to an embodiment of the present disclosure. FIG. 29 shows an example of the path (IP transmission path) of the control information among the MEC server 300 (MAM), the P-GW, the S-GW, and the MME.

FIG. 30 is a diagram illustrating an example of a communication protocol used between devices included in the system 1 according to an embodiment of the present disclosure. FIG. 30 shows an example of the control information path (IP transport path) in the MME and the HSS.

FIG. 31 shows the system 1 according to an embodiment of the present disclosure. An illustration of an example of the communication protocol used between the included devices. FIG. 31 shows an example of a control information path (IP transport path) in the P-GW (PCEF), S-GW (BBERF), and PCRF.

Next, with reference to FIG. 32, the distribution function of an application is demonstrated.

FIG. 32 is an explanatory diagram for explaining supplementary matters related to the system according to an embodiment of the present disclosure. This figure shows the state in which the application program is distributed in the specific relationship of each device of the system 1 as described above with reference to FIG. 18 . The solid lines in this figure represent wired connections or wireless connections, and the dotted lines represent wireless connections. However, the connection between the P-GW and the ISP/MVNO Internet and between the ISP/MVNO Internet and the Server-S is basically assumed to be a wired connection. References to logical connections are omitted. In addition, in this figure, the Server is also provided in the eNB. For example, the functional part of the application requiring low latency or high throughput is placed in Server-1~N, and the other functional parts are placed in Server-A1~AN. Also, from Server-S, to Server-1~N or Server-A1~AN, the functional parts that should be installed will be delivered and installed. This matter is not merely to disperse the application programs, but also to map functional parts suitable for the configuration and characteristics of the MEC server 300 to each of the MEC servers 300 .

FIG. 33 is an explanatory diagram for explaining supplementary matters related to the system according to an embodiment of the present disclosure. This figure shows the state in which the application program is distributed in the specific relationship of each device of the system 1 as described above with reference to FIG. 18 . The solid lines in this figure represent wired connections or a wireless connection, the dotted line indicates a wireless connection. However, the connection between the P-GW and the ISP/MVNO Internet and between the ISP/MVNO Internet and the Server-S is basically assumed to be a wired connection. References to logical connections are omitted. In addition, in this figure, the Server is also provided in the eNB and the S-GW. For example, the functional part of the application requiring low latency or high throughput is placed in Server-1 to N, and the other functional parts are placed in Server-A1 to AN or Server-α. Also, from Server-S, to Server-1~N, Server-A1~AN, or Server-α, the functional parts that should be installed will be delivered and installed. This matter is not merely to disperse the application programs, but also to map functional parts suitable for the configuration and characteristics of the MEC server 300 to each of the MEC servers 300 .

<<6. Application examples>>

The techniques described in this disclosure can be applied to various products. For example, the wireless communication device 100 can also be implemented as any type of eNB (evolved Node B) such as a macro eNB or a small eNB. Small eNBs may also be pico eNBs, micro eNBs, or home (femto) eNBs, etc., which cover smaller cellular networks than macro cellular networks. Alternatively, the wireless communication device 100 can be implemented as other types of base stations such as NodeB or BTS (Base Transceiver Station). The wireless communication device 100 may include a main body (also referred to as a base station device) for controlling wireless communication, and one or more RRHs (Remote Radio Heads) arranged in a place separate from the main body. In addition, it is also possible to temporarily or semi- The base station function is permanently executed to operate as the wireless communication device 100 . Even, at least a part of the constituent elements of the wireless communication device 100 can also be implemented in the base station device or the modules required by the base station device.

In addition, for example, the terminal device 200 can also be implemented as a mobile terminal such as a smartphone, a tablet PC (Personal Computer), a notebook PC, a portable game terminal, a portable/key-type mobile router, or a digital camera, etc. Or vehicle terminal such as driving navigation device. In addition, the terminal device 200 can also be implemented as a terminal for M2M (Machine To Machine) communication (also referred to as an MTC (Machine Type Communication) terminal). Furthermore, at least a part of the constituent elements of the terminal device 200 may be implemented in a module (for example, an integrated circuit module composed of one chip) mounted on these terminals.

<6.1. Application example of base station> (1st application example)

FIG. 34 is a block diagram of a first example of a schematic configuration of an eNB to which the technique described in the present disclosure can be applied. The eNB 800 has one or more antennas 810 and a base station apparatus 820 . Each of the antennas 810 and the base station device 820 can be connected to each other through RF cables.

Each of the antennas 810 , having a single or multiple antenna elements (eg, a plurality of antenna elements forming a MIMO antenna), is used to transmit wireless signals from the base station device 820 . The eNB 800 has complex antennas 810 as shown in FIG. 34 , and the complex antennas 810 may also respectively correspond to, for example, complex frequency bands used by the eNB 800 . In addition, although FIG. 34 shows the The example in which the eNB 800 has multiple antennas 810 is shown, but the eNB 800 may also have a single antenna 810 .

The base station device 820 includes a controller 821 , a memory 822 , a network interface 823 and a wireless communication interface 825 .

The controller 821 can be, for example, a CPU or a DSP, and causes various functions of the upper layer of the base station apparatus 820 to operate. For example, the controller 821 generates data packets from the data in the signal processed by the wireless communication interface 825 , and transmits the generated packets through the network interface 823 . The controller 821 can also bundle the data from the plurality of baseband processors to generate a bundled packet, and transmit the generated bundled packet. In addition, the controller 821 may also have functions for performing Radio Resource Control, Radio Bearer Control, Mobility Management, Admission Control, or Scheduling. The logical function of control. In addition, the appropriate control can also be performed in cooperation with the surrounding eNBs or core network nodes. The memory 822 includes RAM and ROM, and stores programs to be executed by the controller 821 and various control data (eg, terminal list, transmission power data, and scheduling data, etc.).

The network interface 823 is a communication interface required for connecting the base station device 820 to the core network 824 . The controller 821 can also communicate with core network nodes or other eNBs through the network interface 823 . In this case, the eNB 800 and core network nodes or other eNBs can also be connected to each other through a logical interface (eg, S1 interface or X2 interface). The network interface 823 can be a wired communication interface, or can be a wireless communication interface for wireless backhauling. information interface. If the network interface 823 is a wireless communication interface, the network interface 823 can also use a higher frequency band than the frequency band used by the wireless communication interface 825 for wireless communication.

The wireless communication interface 825 supports any cellular network communication method such as LTE (Long Term Evolution) or LTE-Advanced, and provides wireless connection to terminals located in the cellular network of the eNB 800 through the antenna 810 . The wireless communication interface 825 can typically include a baseband (BB) processor 826, an RF circuit 827, and the like. For example, the BB processor 826 can perform encoding/decoding, modulation/demodulation, multiplexing/inverse multiplexing, etc., and executes various layers (eg, L1, MAC (Medium Access Control), RLC (Radio Link Control), and PDCP ( Packet Data Convergence Protocol)) various signal processing. The BB processor 826 can also replace the controller 821 and have some or all of the above-mentioned logic functions. The BB processor 826 can also be a module including a memory for memorizing the communication control program, a processor for executing the program and related circuits, and the function of the BB processor 826 can also be changed by upgrading the above program. In addition, the above-mentioned module can also be a board or a blade board inserted into the slot of the base station device 820 , and can also be a chip mounted on the above-mentioned board card or the above-mentioned blade board. On the other hand, the RF circuit 827 may also include mixers, filters, amplifiers, etc., and transmit wireless signals through the antenna 810 .

The wireless communication interface 825 includes a plurality of BB processors 826 as shown in FIG. 34 , and the plurality of BB processors 826 respectively correspond to the plurality of frequency bands used by, for example, the eNB 800 . In addition, the wireless communication interface 825 includes a complex RF circuit 827 as shown in FIG. 34, and the complex RF circuit 827 The systems may also respectively correspond to, for example, complex antenna elements. In addition, although the wireless communication interface 825 shown in FIG. 34 is an example including plural BB processors 826 and plural RF circuits 827 , the wireless communication interface 825 may also include a single BB processor 826 or a single RF circuit 827 .

In the eNB 800 shown in FIG. 34 , one or more constituent elements (the relay processing unit 151 , the providing unit 153 and/or the notification unit 155 ) included in the wireless communication device 100 described with reference to FIG. 4 may be Implemented in the wireless communication interface 825 . Furthermore, one or more constituent elements (the acquisition unit 331 , the notification unit 333 , the search unit 335 and/or the service processing unit 337 ) included in the MEC server 300 described with reference to FIG. 6 can also be implemented in Wireless communication interface 825. Alternatively, at least a part of these constituent elements may also be implemented in the controller 821 . As an example, the eNB 800 may also be equipped with a module including part or all of the wireless communication interface 825 (eg, the BB processor 826 ), and/or the controller 821 , and one or more of the above-mentioned constituent elements are implemented in the module. In this case, the above-mentioned module may also be a program required to make the processor operate as one or more of the above-mentioned components (in other words, a program required for the processor to execute the operation of the above-mentioned one or more components) ) to memorize and execute the appropriate program. As another example, programs required to make the processor operate as one or more of the above-mentioned components may also be installed in the eNB 800, and the wireless communication interface 825 (eg, the BB processor 826) and/or the controller 821 execute the program. program. As described above, it is also possible to provide the eNB 800, the base station device 820, or the above-mentioned module in the form of a device having one or more of the above-mentioned constituent elements, and to provide the processor to operate as one or more of the above-mentioned components. The program required for the above components. In addition, a readable recording medium on which the above-described program is recorded may be provided.

Furthermore, in the eNB 800 shown in FIG. 34 , the wireless communication unit 120 described with reference to FIG. 4 may also be implemented in the wireless communication interface 825 (eg, the RF circuit 827 ). Also, the antenna portion 110 may also be implemented in the antenna 810 . Also, the network communication unit 130 can also be implemented in the controller 821 and/or the network interface 823 . Also, the memory portion 140 may also be implemented in the memory 822 .

(2nd application example)

FIG. 35 is a block diagram of a second example of a schematic configuration of an eNB to which the technique described in the present disclosure can be applied. The eNB 830 has one or more antennas 840 , a base station apparatus 850 , and an RRH 860 . Each of the antennas 840 and the RRH 860 can be connected to each other through RF cables. In addition, the base station apparatus 850 and the RRH 860 can be connected to each other by a high-speed line such as an optical fiber.

Each of the antennas 840, having a single or multiple antenna elements (eg, a plurality of antenna elements forming a MIMO antenna), is used to transmit wireless signals of the RRH 860. The eNB 830 has a complex number of antennas 840 as shown in FIG. 35 , and the complex number of antennas 840 may respectively correspond to, for example, complex frequency bands used by the eNB 830 . In addition, although FIG. 35 illustrates an example in which the eNB 830 has a plurality of antennas 840 , the eNB 830 may also have a single antenna 840 .

The base station device 850 is provided with: a controller 851, a memory 852 , a network interface 853 , a wireless communication interface 855 and a connection interface 857 . The controller 851 , the memory 852 and the network interface 853 are the same as the controller 821 , the memory 822 and the network interface 823 described with reference to FIG. 34 .

The wireless communication interface 855 supports any cellular network communication method such as LTE or LTE-Advanced. Through the RRH860 and the antenna 840, a wireless connection is provided to the terminals located in the section corresponding to the RRH860. The wireless communication interface 855 can typically include a BB processor 856 and the like. The BB processor 856 is the same as the BB processor 826 described with reference to FIG. 34 except that it is connected to the RF circuit 864 of the RRH 860 through the connection interface 857 . As shown in FIG. 35 , the wireless communication interface 855 includes a plurality of BB processors 856 , and the plurality of BB processors 856 respectively correspond to the plurality of frequency bands used by, for example, the eNB 830 . In addition, although the wireless communication interface 855 shown in FIG. 35 is an example including a plurality of BB processors 856 , the wireless communication interface 855 may also include a single BB processor 856 .

The connection interface 857 is an interface required for connecting the base station device 850 (the wireless communication interface 855 ) and the RRH860. The connection interface 857 can also be a communication module for connecting the base station device 850 (wireless communication interface 855 ) with the above-mentioned high-speed line communication of the RRH860.

In addition, the RRH860 is provided with a connection interface 861 and a wireless communication interface 863 .

The connection interface 861 is an interface required for connecting the RRH 860 (the wireless communication interface 863 ) and the base station device 850 . The connection interface 861 can also be a communication module required for the above-mentioned high-speed line communication.

The wireless communication interface 863 transmits wireless signals through the antenna 840 . The wireless communication interface 863 can typically include an RF circuit 864 and the like. The RF circuit 864 may also include mixers, filters, amplifiers, etc., to transmit wireless signals through the antenna 840 . The wireless communication interface 863 includes a complex number of RF circuits 864 as shown in FIG. 35 , and the complex number of RF circuits 864 may also respectively correspond to, for example, complex number of antenna elements. In addition, although the wireless communication interface 863 shown in FIG. 35 is an example including a plurality of RF circuits 864 , the wireless communication interface 863 may also include a single RF circuit 864 .

In the eNB 830 shown in FIG. 35 , one or more constituent elements (the relay processing unit 151 , the providing unit 153 and/or the notification unit 155 ) included in the wireless communication device 100 described with reference to FIG. 4 may be Implemented in wireless communication interface 855 and/or wireless communication interface 863 . Furthermore, one or more constituent elements (the acquisition unit 331 , the notification unit 333 , the search unit 335 and/or the service processing unit 337 ) included in the MEC server 300 described with reference to FIG. 6 can also be implemented in Wireless communication interface 855 and/or wireless communication interface 863. Alternatively, at least a part of these constituent elements may also be implemented in the controller 851 . As an example, the eNB 830 may also be equipped with a module including part or all of the wireless communication interface 855 (eg, the BB processor 856 ), and/or the controller 851 , and one or more of the above-mentioned constituent elements are implemented in the module. In this case, the above-mentioned module may also be a program required to make the processor operate as one or more of the above-mentioned components (in other words, a program required for the processor to execute the operation of the above-mentioned one or more components) ) to memorize and execute the appropriate program. As another example, the programs required to make the processor operate as one or more of the above-mentioned components may also be installed in the eNB 830, and the wireless communication interface 855 (eg, the BB processor 856) and/or the controller 851 execute the program. program. As described above, it is also possible to provide the eNB 830, the base station device 850, or the above-mentioned module in the form of a device having one or more of the above-mentioned components, and to provide all the components for operating the processor to become the above-mentioned one or more of the above-mentioned components. required program. In addition, a readable recording medium on which the above-described program is recorded may be provided.

Furthermore, in the eNB 830 shown in FIG. 35 , for example, the wireless communication unit 120 described with reference to FIG. 4 can also be implemented in the wireless communication interface 863 (eg, the RF circuit 864 ). Also, the antenna portion 110 may also be implemented in the antenna 840 . Also, the network communication unit 130 can also be implemented in the controller 851 and/or the network interface 853 . Also, the memory portion 140 may also be implemented in the memory 852 .

(Example of functional structure)

FIG. 36 is a block diagram of an example of a schematic functional configuration of an eNB 870 to which the techniques described in the present disclosure can be applied. As shown in FIG. 36 , eNB 870 includes Inter Cell RRM 881 , RB Control 882 , Connection Mobility Control 883 , Radio Admission Control 884 , eNB Measurement Configuration & Provision 885 , and Dynamic Resource Allocation (Scheduler) 886 .

Inter Cell RRM (Radio Resource Management) 881 provides a function of managing radio resources between cellular networks. example For example, the Inter Cell RRM881 reduces the interference between cellular networks through the allocation of radio resources and the adjustment of transmission power.

RB (Radio Bearer) Control882 provides radio bearer control function. For example, RB Control 882 establishes, modifies or opens radio bearers based on the service requirements of each radio bearer.

Connection Mobility Control883 provides connection control functions that allow mobility. For example, Connection Mobility Control 883 controls the mobility of the UE in RRC_CONNECTED based on information from the UE, and makes a takeover decision.

Radio Admission Control 884 provides connection admission control functions. For example, the Radio Admission Control 884 determines whether to allow a new RRC connection and a new radio bearer based on the usage of resources in the cellular network and the resource requirements of the service.

eNB Measurement Configuration & Provision885 provides measurement information supply function. For example, eNB Measurement Configuration & Provision885 provides measurement results to operators or control entities to optimize the usage of radio resources and network settings.

Dynamic Resource Allocation (Scheduler) 886 provides a dynamic radio resource allocation function to the UE. For example, Dynamic Resource Allocation (Scheduler) 886 dynamically allocates radio resources to each UE based on the state of the channel to maximize radio efficiency.

In addition, the eNB870 system also includes: RRC (Radio Resource Control) 891, PDCP (Packet Domain Convergence Protocol) 892, RLC (Radio Link Control) 893, MAC (Media Access Control) 894, PHY (Physical Layer) 895. These are stacks of protocols.

In addition, the block diagram shown in FIG. 36 is described in the technical specification "3GPP TS36.300 version 12.5.0 Release 12" LTE; Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E- UTRAN); Overall description; "Figure 4.1-1: Functional Split between E-UTRAN and EPC" of Stage 2"". That is, the technology described in the present disclosure can be applied to the eNB described in the technical specification. For example, the MEC server 300 may be mounted on the eNB described in this specification.

<6.2. Application examples related to terminal devices> (1st application example)

FIG. 37 is a block diagram of an example of a schematic configuration of a smartphone 900 to which the technology described in the present disclosure can be applied. Smartphone 900 includes: processor 901 , memory 902 , storage 903 , external connection interface 904 , camera 906 , sensor 907 , microphone 908 , input device 909 , display device 910 , speaker 911 , wireless communication interface 912 , more than one antenna switch 915 , more than one antenna 916 , bus bar 917 , battery 918 and auxiliary controller 919 .

The processor 901 can be, for example, a CPU or a SoC (System on Chip), to control the functions of the application layer and other layers of the smart phone 900 . The memory 902 includes RAM and ROM, and stores programs and data executed by the processor 901 . The storage body 903 may include a memory medium such as a semiconductor memory or a hard disk. The external connection interface 904 can also be an interface required for connecting an external device such as a memory card or a USB (Universal Serial Bus) device to the smart phone 900 .

The camera 906 has, for example, an imaging element such as a CCD (Charge Coupled Device) or a CMOS (Complementary Metal Oxide Semiconductor), and generates a captured image. The sensor 907 may include, for example, a sensor group such as a positioning sensor, a gyroscope sensor, a geomagnetic sensor, and an acceleration sensor. The microphone 908 converts the sound input to the smart phone 900 into a sound signal. The input device 909 includes, for example, a touch sensor for detecting touches on the screen of the display device 910 , a key pad, a keyboard, a button or a switch, etc., and accepts operations or information input from the user. The display device 910 has a screen such as a liquid crystal display (LCD) or an organic light emitting diode (OLED) display, and displays the output image of the smartphone 900 . The speaker 911 converts the sound signal output from the smart phone 900 into sound.

The wireless communication interface 912 supports any cellular network communication method such as LTE or LTE-Advanced to perform wireless communication. The wireless communication interface 912 typically includes a BB processor 913, an RF circuit 914, and the like. The BB processor 913 can perform, for example, encoding/decoding, modulation/demodulation, multiplexing/inverse multiplexing, etc., to perform various signal processing required for wireless communication. On the other hand, the RF circuit 914 may also include mixers, filters The antenna 916 transmits wireless signals through the antenna 916 . The wireless communication interface 912 can also be a single-chip module formed by integrating the BB processor 913 and the RF circuit 914 . The wireless communication interface 912 can also include a plurality of BB processors 913 and a plurality of RF circuits 914 as shown in FIG. 37 . In addition, although the wireless communication interface 912 shown in FIG. 37 is an example including multiple BB processors 913 and multiple RF circuits 914 , the wireless communication interface 912 may also include a single BB processor 913 or a single RF circuit 914 .

Furthermore, the wireless communication interface 912, in addition to the cellular network communication method, can also support other types of wireless communication methods such as short-range wireless communication method, proximity wireless communication method or wireless LAN (Local Area Network) method. , may contain BB processor 913 and RF circuit 914 for each wireless communication method.

Each of the antenna switches 915 switches the connection destination of the antenna 916 between a plurality of circuits included in the wireless communication interface 912 (eg, circuits used in different wireless communication methods).

Each of the antennas 916 , having a single or multiple antenna elements (eg, a plurality of antenna elements forming a MIMO antenna), is used to transmit wireless signals of the wireless communication interface 912 . The smartphone 900 may also have a plurality of antennas 916 as shown in FIG. 37 . In addition, although FIG. 37 illustrates an example in which the smartphone 900 has a plurality of antennas 916 , the smartphone 900 may also have a single antenna 916 .

Even, the smart phone 900 series can have the antenna 916 for each wireless communication method. In this case, the antenna switch 915 can be omitted from the configuration of the smartphone 900 .

The bus bar 917 connects the processor 901, the memory 902, the storage 903, the external connection interface 904, the camera 906, the sensor 907, the microphone 908, the input device 909, the display device 910, the speaker 911, the wireless communication interface 912 and the The auxiliary controllers 919 are connected to each other. The battery 918 supplies power to each block of the smartphone 900 shown in FIG. 37 through the power supply line shown by the dotted line in the figure. The auxiliary controller 919 operates, for example, the minimum necessary functions of the smartphone 900 in the sleep mode.

In the smartphone 900 shown in FIG. 37 , one or more constituent elements (the acquisition unit 241 and/or the selection processing unit 243 ) included in the terminal device 200 described with reference to FIG. 5 can also be implemented in the wireless communication interface 912 . Furthermore, one or more constituent elements (the acquisition unit 331 , the notification unit 333 , the search unit 335 and/or the service processing unit 337 ) included in the MEC server 300 described with reference to FIG. 6 can also be implemented in In the wireless communication interface 912 . Alternatively, at least a part of these constituent elements may also be implemented in the processor 901 or the auxiliary controller 919 . As an example, the smart phone 900 can also be equipped with a module including a part or all of the wireless communication interface 912 (eg, the BB processor 913 ), the processor 901 , and/or the auxiliary controller 919 , and implemented in the module One or more components listed above. In this case, the above-mentioned module may also be a program required to make the processor operate as one or more of the above-mentioned components (in other words, a program required for the processor to execute the operation of the above-mentioned one or more components) ) to memorize and execute the appropriate program. As another example, the program required to make the processor operate as one or more of the above-mentioned components may also be Installed in the smart phone 900 , the program is executed by the wireless communication interface 912 (eg, the BB processor 913 ), the processor 901 , and/or the auxiliary controller 919 . As described above, the smartphone 900 or the above-mentioned module can also be provided as a device having one or more of the above-mentioned constituent elements, and to provide the necessary for operating the processor to become the above-mentioned one or more of the above-mentioned constituent elements program. In addition, a readable recording medium on which the above-described program is recorded may be provided.

Furthermore, in the smart phone 900 shown in FIG. 37 , for example, the wireless communication unit 220 described with reference to FIG. 5 can also be implemented in the wireless communication interface 912 (eg, the RF circuit 914 ). Also, the antenna portion 210 may also be implemented in the antenna 916 . Also, the memory portion 230 may also be implemented in the memory 902 .

(2nd application example)

FIG. 38 is a block diagram of an example of a schematic configuration of a driving navigation device 920 to which the technology described in the present disclosure can be applied. The driving navigation device 920 includes: a processor 921, a memory 922, a GPS (Global Positioning System) module 924, a sensor 925, a data interface 926, a content player 927, a memory media interface 928, an input device 929, and a display device 930 , speaker 931 , wireless communication interface 933 , more than one antenna switch 936 , more than one antenna 937 and battery 938 .

The processor 921 can be, for example, a CPU or a SoC, and controls the navigation function and other functions of the driving navigation device 920 . The memory 922 includes RAM and ROM, and stores programs and data executed by the processor 921. material.

The GPS module 924 uses GPS signals received from GPS satellites to determine the location (eg, latitude, longitude, and altitude) of the driving navigation device 920 . The sensor 925 may include, for example, a sensor group such as a gyroscope sensor, a geomagnetic sensor, and an air pressure sensor. The data interface 926 is, for example, connected to the in-vehicle network 941 through a terminal not shown, and obtains data generated on the vehicle side such as vehicle speed data.

The content player 927 reproduces the content stored in the storage medium (eg, CD or DVD) inserted into the storage medium interface 928 . The input device 929 includes, for example, a touch sensor, a button or a switch that detects touch on the screen of the display device 930, and accepts operations or information input from the user. The display device 930 has a screen such as an LCD or an OLED display, and displays a navigation function or an image of the reproduced content. The speaker 931 outputs the sound of the navigation function or the reproduced content.

The wireless communication interface 933 supports any cellular network communication method such as LTE or LTE-Advanced to perform wireless communication. The wireless communication interface 933 typically includes a BB processor 934, an RF circuit 935, and the like. The BB processor 934 can perform, for example, encoding/decoding, modulation/demodulation, multiplexing/inverse multiplexing, etc., to perform various signal processing required for wireless communication. On the other hand, the RF circuit 935 may also include mixers, filters, amplifiers, etc., and transmit wireless signals through the antenna 937 . The wireless communication interface 933 can also be a single-chip module formed by integrating the BB processor 934 and the RF circuit 935 . The wireless communication interface 933 can also be as shown in Figure 38 As shown, a complex BB processor 934 and a complex RF circuit 935 are included. In addition, although the wireless communication interface 933 shown in FIG. 38 is an example including multiple BB processors 934 and multiple RF circuits 935 , the wireless communication interface 933 may also include a single BB processor 934 or a single RF circuit 935 .

Furthermore, the wireless communication interface 933, in addition to the cellular network communication method, can also support other types of wireless communication methods such as short-range wireless communication method, proximity wireless communication method or wireless LAN method. The BB processor 934 and the RF circuit 935 of the wireless communication method.

Each of the antenna switches 936 switches the connection destination of the antenna 937 between a plurality of circuits included in the wireless communication interface 933 (eg, circuits used in different wireless communication methods).

Each of the antennas 937 , having a single or multiple antenna elements (eg, a plurality of antenna elements constituting a MIMO antenna), is used to transmit the wireless signal of the wireless communication interface 933 . The driving navigation device 920 may also have a plurality of antennas 937 as shown in FIG. 38 . In addition, although FIG. 38 illustrates an example in which the driving navigation device 920 has a plurality of antennas 937 , the driving navigation device 920 may also have a single antenna 937 .

Even the driving navigation device 920 can also be provided with an antenna 937 for each wireless communication method. In this case, the antenna switch 936 can be omitted from the configuration of the driving navigation device 920 .

The battery 938 supplies power to each block of the driving navigation device 920 shown in FIG. 38 through the power supply line shown by the dotted line in the figure. In addition, the battery 938 stores electric power supplied from the vehicle side.

In the driving navigation device 920 shown in FIG. 38 , one or more constituent elements (the acquisition unit 241 and/or the selection processing unit 243 ) included in the terminal device 200 described with reference to FIG. 5 can also be implemented. in the wireless communication interface 933. Furthermore, one or more constituent elements (the acquisition unit 331 , the notification unit 333 , the search unit 335 and/or the service processing unit 337 ) included in the MEC server 300 described with reference to FIG. 6 can also be implemented in In the wireless communication interface 933. Alternatively, at least a part of these constituent elements may also be implemented in the processor 921 . As an example, the driving navigation device 920 can also be equipped with a module including part or all of the wireless communication interface 933 (eg, the BB processor 934 ) and/or the processor 921 , and the above-mentioned one or more configurations are implemented in the module. elements. In this case, the above-mentioned module may be a program required to make the processor operate as one or more of the above-mentioned constituent elements (in other words, a program required to make the processor execute the operation of the above-mentioned one or more constituent elements) ) to memorize and execute the appropriate program. As another example, the programs required to make the processor operate as one or more of the above-mentioned components may also be installed in the driving navigation device 920 through the wireless communication interface 933 (eg, the BB processor 934 ) and/or the processor 921 to execute the appropriate program. As described above, the driving navigation device 920 or the above-mentioned module can also be provided in the form of a device having one or more of the above-mentioned constituent elements, and to provide the necessary for the operation of the processor to become the above-mentioned one or more of the above-mentioned constituent elements program. In addition, a readable recording medium on which the above-described program is recorded may be provided.

In addition, in the driving navigation device 920 shown in FIG. 38 , for example, the wireless communication unit 220 described with reference to FIG. 5 can also be implemented in In the wireless communication interface 933 (eg, the RF circuit 935). Also, the antenna portion 210 may also be implemented in the antenna 937 . Also, the memory portion 230 can also be implemented in the memory 922 .

In addition, the technology described in the present disclosure can also be implemented as an in-vehicle system (or vehicle) 940 including one or more blocks of the above-mentioned driving navigation device 920 , an in-vehicle network 941 , and a vehicle-side module 942 . That is, it is also possible to provide the in-vehicle system (or vehicle) by including the devices of the acquisition unit 241 and/or the selection processing unit 243 (and the acquisition unit 331, the notification unit 333, the search unit 335, and/or the service processing unit 337). 940. The vehicle-side module 942 generates vehicle-side data such as vehicle speed, engine revolutions, or fault information, and outputs the generated data to the in-vehicle network 941 .

<<7. Summary>>

One embodiment of the present disclosure has been described above in detail with reference to FIGS. 1 to 38 . As explained above, the terminal device 200 will be provided by the wireless communication terminal 100 and used by the MEC server 300 to obtain the API information related to the API required for the wireless communication of the terminal device 200 itself. Obtain, perform processing required by the MEC server 300 for selecting a service providing source based on the API information. By referring to the API information, the terminal device 200 can select an open MEC server 300 that has an API in the corresponding wireless communication device 100 . Thereby, the selection of the appropriate MEC server 300 as the service provider source is realized.

By implementing the selection of the appropriate MEC server 300, the Users, application providers, and operators can all enjoy benefits. For example, the user can receive the service more comfortably (appropriate speed, delay environment, etc.). In addition, the application provider can provide users with higher quality services. In addition, the operator can optimize operations such as load distribution and optimization of radio resources. In addition, regarding the sharing of infrastructures in the same wireless coverage area (eg, the wireless communication device 100 ), the terminal device 200 can also access the optimal MEC server 300 . In addition, the terminal device 200 can access the optimum MEC server 300 when it takes over. In addition, the upper layer (application), by grasping the API as the wireless communication device 100 that can be used, can provide a service that can utilize special features according to the user's contract or the like. For example, an application can select a connection target that meets the application's requirements in the same wireless service area.

Although the preferred embodiments of the present disclosure have been described in detail above with reference to the accompanying drawings, the technical scope of the present disclosure is not limited to the examples. Those with ordinary knowledge in the technical field of the present disclosure can naturally conceive of various modifications or amendments within the scope of the technical idea described in the scope of the application, and these also belong to the technical scope of the present disclosure.

For example, in the above-described embodiment, it is assumed that the wireless communication device 100 provides the API and the MEC server 300 uses the API for description, but the present technology is not limited to the above-described example. Alternatively, the API provided by the MEC server 300 is used by the wireless communication device 100 . In addition, regarding the provision of API, the wireless communication device can also Either one of the device 100 or the MEC server 300 can participate, or both parties can participate (ie, provide APIs through cooperative operation). The wireless communication device 100 and the MEC server 300 are in the framework of the MEC server platform shown in FIG. 2 to exchange information. For example, in the MEC application platform shown in Figure 2, APIs may be provided.

In addition, the process demonstrated using the flowchart and the program diagram in this specification may not necessarily be performed in the order shown. It is also possible that several processing steps are performed in parallel. In addition, additional processing steps may be employed, and some processing steps may be omitted.

In addition, the processor (such as CPU, DSP, etc.) provided in the device (such as the wireless communication device 100, the terminal device 200, or the MEC server 300) in this specification can also be made to be the operation of the constituent elements of the above-mentioned device. The required computer program (in other words, the computer program required for the above-mentioned processor to execute the operations of the constituent elements of the above-mentioned device. Also, a recording medium on which the computer program is recorded may be provided. Also, a computer program capable of memorizing the above-mentioned computer program may be provided. Memory, and a device capable of executing the above-mentioned computer program with one or more processors (such as a base station, a base station device or a module required by a base station device, or a terminal device or a module required by a terminal device). In addition, the method including the operation of the constituent elements of the above-mentioned device is also included in the technology described in this disclosure.

In addition, the effects described in this specification are merely illustrative or exemplary, and are not intended to be interpreted limitedly. That is, the technology described in the present disclosure can also be in addition to the above-mentioned effects, or can also replace the above-mentioned effects, to achieve other effects that can be self-evident to the practitioners according to the description of this specification.

In addition, the following configurations also belong to the technical scope of the present disclosure.

(1)

A device comprising: an obtaining unit for obtaining the aforesaid relay, which is provided by a relay node that relays communication between the aforementioned device and a core network, and is used by a service providing device that provides services to the aforementioned device Obtain the relevant information of the API required for the relevant information of the communication of the node; and the selection processing unit performs the pre-recording service provision for selecting the source of the service provision based on the relevant information of the pre-recording API that has been acquired by the pre-recording obtaining unit The processing required by the device.

(2)

The device according to the preceding paragraph (1), wherein the relevant information of the preceding paragraph API includes: information indicating whether the preceding paragraph API is usable.

(3)

The device according to the preceding paragraph (2), wherein the information indicating whether or not the aforementioned API is usable includes: information indicating whether the aforementioned API is present or not.

(4)

The device according to (2) or (3) above, wherein the information indicating whether the above-mentioned API is usable or not includes: information indicating whether the above-mentioned API is open or closed.

(5)

The device according to any one of (1) to (4) above, wherein the information related to the communication of the relay node in the previous description includes: the relay node in the previous description and the connection Information about the wireless communication of the pre-recorded device to the pre-recorded relay node.

(6)

The device according to any one of (1) to (5) above, wherein the information related to the communication of the relay node in the previous description includes: the communication between the relay node in the previous description and the service providing device connected to the relay node in the previous description. related information.

(7)

The device according to any one of (1) to (6) above, wherein the information related to the communication of the relay node in the previous description includes: the communication between the relay node in the previous description and other relay nodes connected to the relay node in the previous description. related information.

(8)

The device according to any one of (1) to (7) above, wherein the information related to the communication of the relay node in the above description includes at least one of physical location information or meaningful location information.

(9)

The device according to any one of the preceding paragraphs (1) to (8), wherein the preceding paragraph selection processing unit selects the preceding paragraph API as a usable preceding paragraph service providing device, and preferentially selects it as a service providing source.

(10)

The device according to any one of the preceding items (1) to (9), wherein the preceding item selection processing unit is not under the management of the preceding item relay node corresponding to the preceding item service providing apparatus that has been selected as the service providing source. When the aforementioned device is included, the communication path change process is performed so that it is included in the management.

(11)

The device according to any one of (1) to (10) above, wherein the above-mentioned selection processing unit includes the above-mentioned API on the communication path until the service providing device that has been selected as the service providing source is reached. In the case of an unusable preamble relay node, a communication path change process is performed so that the preamble service provider can communicate with another preamble relay node that can be used via the preamble API.

(12)

The device according to any one of (1) to (11) above, wherein the above-mentioned acquisition unit is provided by one or more of the preceding-mentioned relay nodes included in the communication path to the preceding-mentioned service providing device. The information about the API mentioned above can be obtained.

(13)

The device according to any one of the preceding paragraphs (1) to (12), wherein the preceding paragraph obtaining unit acquires the information related to the preceding paragraph communication that has been acquired using the preceding paragraph API; the preceding paragraph selection processing unit is also based on The relevant information of the previous communication, to select the service providing source, the previous service providing device.

(14)

The device according to any one of (1) to (13) above, wherein the aforementioned selection processing unit selects the aforementioned service providing device based on a user operation to select a service providing source.

(15)

A device comprising: an acquisition unit that relays communication between a terminal device and a core network The information provided by the relay node is used to obtain the relevant information of the API required for obtaining the relevant information of the communication of the previous relay node; Notify the aforementioned terminal device.

(16)

According to the device described in the preceding paragraph (15), the preceding paragraph acquiring unit repeatedly obtains the relevant information of the preceding paragraph API; the preceding paragraph notifying unit is to notify the preceding paragraph related information of the API that has been repeatedly obtained by the preceding paragraph obtaining unit.

(17)

The apparatus according to (15) or (16) above, wherein the apparatus further includes: a search unit that searches for other relay nodes that can be used by the aforementioned API.

(18)

The device according to the preceding paragraph (17), wherein the preceding device is further provided with: a memory unit for memorizing the information representing the search result by the searching unit in the preceding paragraph.

(19)

The device according to (18) above, wherein the information representing the search result in the preceding paragraph includes: identification information of other relay nodes in the preceding paragraph, identification information on other devices corresponding to the other relay nodes in the preceding paragraph, and other relays in the preceding paragraph. Information about the preamble API provided by the node.

(20)

The device according to any one of the preceding notes (15) to (19), wherein the preceding The recording device further includes a service processing unit that performs processing required for providing a service to the recording terminal device.

(twenty one)

The device according to the preceding paragraph (20), wherein the preceding paragraph service processing unit requests the preceding paragraph relay node to change the communication settings based on the preceding paragraph communication-related information.

(twenty two)

The device according to any one of the preceding paragraphs (15) to (21), wherein the preceding paragraph obtaining part obtains the relevant information of the preceding paragraph communication; The aforementioned terminal device.

(twenty three)

The device according to any one of the preceding paragraphs (15) to (22), wherein the preceding paragraph obtaining unit acquires the relevant information of the preceding paragraph API based on the result of using the preceding paragraph API.

(twenty four)

A device comprising: a relay processing unit for relaying communication between a terminal device and a core network; and a providing unit for providing information related to the communication relayed by the aforementioned relay processing unit to a The aforesaid terminal device provides a service providing device.

(25)

The device as described in the preceding paragraph (24), wherein the preceding device is further provided with: a notification part, which notifies the end of the preceding paragraph with the relevant information of the preceding paragraph providing part end device.

(26)

The device according to the preceding paragraph (24) or (25), wherein the preceding paragraph providing part uses API to provide the relevant information of the preceding paragraph communication.

(27)

The device as described in the preceding paragraph (26), wherein the preceding paragraph providing part switches the opening and closing of the preceding paragraph API.

(28)

A method, comprising: to be provided by a relay node that relays communication between a device and a core network, and used by a service providing device that provides services to the pre-recorded device, for obtaining the correlation of the communication of the pre-recorded relay node The relevant information of the API required for the information, and the steps of obtaining it; and the processing steps required by the processor to select the source of the service provision by the processor based on the relevant information of the pre-recorded API that has been acquired.

(29)

A method comprising: the steps of obtaining API-related information provided by a relay node that relays the communication between a terminal device and a core network and used to obtain the relevant information of the communication of the relay node described above. ; and the step of notifying the pre-recorded terminal device through the processor of the relevant information of the pre-recorded API that has been obtained.

(30)

A method comprising: the steps of relaying communication between a terminal device and a core network; and providing, by a processor, relevant information of the relayed communication to a service provider for providing a service to the previous terminal device device.

(31)

A program used to make a computer function as: an acquisition unit, which is provided by a relay node that relays the communication between the terminal device and the core network, and is used to obtain the information required for the communication of the relay node mentioned above. The relevant information of the API obtained by the previous record is obtained; and the notification department is to notify the aforesaid terminal device of the relevant information of the previous record API that has been obtained by the previous record acquisition department.

(32)

A program used to make a computer function as: a relay processing part, which relays the communication between the terminal device and the core network; and a providing part, which relays the communication relayed by the aforementioned relay processing part. The relevant information is provided to the service providing device that provides the service to the terminal device of the previous record.

(33)

A program used to make a computer function as: an acquisition part, which will be provided by the relay node that relays the communication between the device and the core network, and used by the service providing device that provides the service to the recorded device, using to obtain the relevant information of the API required to obtain the relevant information of the communication of the preceding relay node; API-related information, and perform the processing required by the service provider before selecting the service provider.

1: System

10A, 10B, 10C: Honeycomb

40: Core Network

50: Packet data network

60: application server

100A, 100B, 100C: wireless communication device

200A, 200B, 200C: Terminal devices

300A, 300B, 300C: MEC server

Claims (30)

A communication device is provided with: an acquisition unit, which is provided by a relay node that relays the communication between the previous communication device and the core network, and is used by a service providing device that provides services to the previous communication device, for obtaining Obtain the relevant information of the API (Application Programing Interface) required for the communication-related information of the preceding relay nodes; and the selection processing unit performs the processing based on the relevant information of the preceding API that has been acquired by the preceding recording obtaining unit. The processing required by the pre-recording service providing device for selecting the service providing source; the pre-recording selection processing unit is under the management of the pre-recording relay node corresponding to the pre-recording service providing device that has been selected as the pre-recording service providing source. In this case, the communication path change process is performed so that it is included in the management. The communication device according to claim 1, wherein the relevant information of the aforementioned API includes: information indicating whether the aforementioned API is available. The communication device according to claim 2, wherein the information indicating whether the aforementioned API is available or not includes: information indicating whether the aforementioned API is available or not. The communication device according to claim 2, wherein the information indicating whether the aforementioned API is usable includes: information indicating the opening and closing of the aforementioned API. The communication device according to claim 1, wherein the communication-related information of the relay node in the preceding description includes: the relay node in the preceding description and the relay node connected to the preceding The relay node pre-records the relevant information of the wireless communication of the communication device. The communication device according to claim 1, wherein the communication-related information of the preceding relay node includes: the preceding relay node and the communication-related information of the preceding service providing device connected to the preceding relay node. The communication device according to claim 1, wherein the communication-related information of the aforementioned relay node includes: the communication-related information of the aforementioned relay node and other relay nodes connected to the aforementioned relay node. The communication device according to claim 1, wherein the information related to the communication of the relay node mentioned above includes: at least one of physical location information or meaningful location information. The communication device according to claim 1, wherein the prescriptive selection processing unit preferentially selects the prescriptive API as a usable prescriptive service providing device as a service providing source. The communication device according to claim 1, wherein the aforementioned selection processing unit includes the aforementioned relay node whose aforementioned API is unavailable on the communication path to the aforementioned aforementioned service providing device that has been selected as the service providing source. In this case, the communication path change process is performed so that it can communicate with the aforementioned service providing apparatus through the aforementioned API as another available aforementioned relay node. The communication device according to claim 1, wherein the aforementioned acquisition unit obtains information about the aforementioned API provided by one or more aforementioned relay nodes included in the communication path to the aforementioned service providing device. . The communication device as described in claim 1, wherein, The aforesaid acquisition part obtains the relevant information of the antecedent communication that has been acquired using the aforesaid API; the aforesaid selection processing part also selects the service provision source of the antecedent service providing device based on the relevant information of the aforesaid communication. The communication device according to claim 1, wherein the prescriptive selection processing unit selects the prescriptive service providing device from the service providing source based on a user operation. A communication device is provided with: an acquisition unit, which is provided by a relay node relaying the communication between a terminal device and a core network, and is used to acquire the relevant information of the API required for the communication of the relay node. , to obtain it; and the notification department, to notify the aforesaid terminal device of the relevant information of the aforesaid API that has been acquired by the aforesaid obtaining department; the aforesaid terminal device is a service provider that selects a service providing source based on the relevant information of the aforesaid API; In the case where the preceding terminal device is not included under the management of the preceding relay node corresponding to the preceding preceding service providing device that has been selected as the preceding serving providing source, the communication path change process is performed so as to be included under the management. The communication device according to claim 14, wherein the aforementioned acquisition unit repeatedly obtains the relevant information of the aforementioned API; and the aforementioned notification unit notifies the aforementioned API related information that has been repeatedly obtained by the aforementioned API. The communication device as described in claim 14, wherein the aforementioned communication The device system further includes: a search unit for exploring other relay nodes that can be used with the pre-recorded API. The communication device according to claim 16, wherein the aforementioned communication device further comprises: a memory unit that memorizes the information representing the search results by the aforementioned search unit. The communication device as described in claim 17, wherein the information representing the exploration results in the preceding description includes: identification information of other relay nodes in the preceding description, identification information on other devices corresponding to the other relay nodes in the preceding description, and other relays in the preceding description. Information about the preamble API provided by the node. The communication device according to claim 14, wherein the aforementioned communication device further comprises: a service processing unit that performs processing necessary for providing a service to the aforementioned terminal device. The communication device according to claim 19, wherein the aforementioned service processing unit requests the aforementioned relay node to change the communication settings based on the relevant information of the aforementioned communication. The communication device as described in claim 14, wherein the aforesaid obtaining unit obtains relevant information of the preceding communication; and the preceding notifying unit notifies the aforementioned terminal device of the obtained information about the preceding communication. The communication device according to claim 14, wherein the aforementioned acquisition unit acquires the related information of the aforementioned API based on the result of using the aforementioned API. A communication device is provided with: a relay processing unit, which is used to perform communication between a terminal device and a core network. The relay; and the providing section, which uses the API to provide the information related to the communication relayed by the aforementioned relay processing section to the service providing device that provides services to the aforementioned terminal device; and the notification section, which is related to the aforementioned API. Information, notified to the terminal device in the preceding paragraph; the relevant information of the preceding paragraph communication includes: throughput rate, delay time, location information, wireless access method, CQI, at least any one of the SIB (System Information Block) retained by the device; the preceding paragraph The terminal device selects the pre-recorded service providing device based on the relevant information of the pre-recorded API; the relay node corresponding to the pre-recorded service provider device that has been selected as the pre-recorded service provision source does not include the pre-recorded terminal device under the management of the device Under the management, the communication path change processing is performed so that it is included under the management. The communication device according to claim 23, wherein the aforementioned providing unit switches the opening and closing of the aforementioned API. A communication method is a communication method in a communication device, which is carried out by the pre-recorded communication device: it will be provided by a relay node that relays the communication between the pre-recorded communication device and the core network, and is provided by the pre-recorded communication device. The relevant information of the API required by the service provider device to obtain the relevant information of the communication of the relay node mentioned above, and the steps to obtain it; and Based on the relevant information of the pre-recorded API that has been acquired, the steps of processing required for the pre-recording service providing device to select the service providing source are performed; When the aforementioned communication device is not included under the management of the relay node, the communication path change process is performed so that it is included under the management. A communication method is a communication method in a communication system with a communication device, a relay node and a terminal device, which is carried out by the pre-recorded communication device: the pre-recorded relay node that relays the communication between the pre-recorded terminal device and the core network. Provided, the relevant information of the API required to obtain the relevant information of the communication of the preceding relay node, and the steps of obtaining it; and the steps of notifying the preceding terminal device that the relevant information of the preceding API has been obtained; by The aforesaid terminal device performs: the step of selecting a service providing device of a service providing source based on the relevant information of the aforesaid API; and under the management of the preceding record relay node corresponding to the preceding record service providing device that has been selected as the prescriptive service providing source, it does not include In the case of the aforementioned terminal device, the communication path change process is performed so as to be included in the management. A communication method, which is a communication method in a communication system with a communication device, a relay node and a terminal device, which is Performed by the aforementioned relay node: the steps of relaying the communication between the terminal device and the core network; and providing the relevant information of the relayed communication to the service providing device that provides services to the aforementioned terminal device using API and the step of notifying the relevant information of the preceding API to the preceding terminal device; the relevant information of the preceding communication includes: throughput rate, delay time, location information, wireless access method, CQI, SIB held by the preceding relay node At least one of (System Information Block); performed by the aforesaid terminal device: the step of selecting a service providing device of a service providing source based on the relevant information of the aforesaid API; and the preceding service providing device having been selected as the aforesaid service providing source When the preceding terminal device is not included under the management of the corresponding preceding relay node, the communication path change process is performed so as to be included under the management. A communication program is used to make the processor of the communication device function as: an acquisition part, which is provided by a relay node relaying the communication between the terminal device and the core network, and is used to obtain the communication of the relay node mentioned above The relevant information of the API required for the relevant information is obtained; and the notification section is to notify the relevant information of the API that has been acquired by the obtaining section of the preceding note to the terminal device of the preceding note; the terminal device of the preceding note is based on the relevant information of the preceding API. to select the service from which the service is provided The providing device; if the prescriptive terminal device is not included under the management of the prescriptive relay node corresponding to the prescriptive service providing device that has been selected as the prescriptive service providing source, the communication path change process is performed so that it is included under the management. A communication program, which is used to make the processor of the communication device function as: a relay processing part, which relays the communication between the terminal device and the core network; and a providing part, which is to be processed by the aforementioned relay processing part The information related to the relayed communication is provided to the service providing device that provides services to the terminal device of the previous record; and the notification department is to notify the terminal device of the previous record of the relevant information of the API of the previous record; the relevant information of the previous record of communication includes: throughput rate, At least one of delay time, location information, wireless access method, CQI, and SIB (System Information Block) held by the aforementioned communication device; the aforementioned terminal device selects the aforementioned service provider based on the relevant information of the aforementioned API; If the relay node corresponding to the aforesaid service providing device selected as the aforesaid service providing source does not include the aforesaid terminal device under the management of the aforesaid communication device, the communication path change process is performed so as to be included under the management. A communication program used to cause the processor of a communication device to function as: The acquisition part will be provided by the relay node that relays the communication between the aforementioned communication device and the core network, and used by the service provider device that provides services to the aforementioned communication device, and is used to obtain the communication information of the aforementioned relay node. The relevant information of the API required for the relevant information is obtained; and the selection processing unit is based on the relevant information of the previously recorded API that has been acquired by the previous recorded API, and is used to select the source of the service provision. Processing; the prescriptive selection processing unit performs a communication path change process to include the prescriptive communication device under the management of the relay node corresponding to the prescriptive service providing device that has been selected as the prescriptive service providing source. under management.

Images