WO2017098810A1

WO2017098810A1 - Device, method, and program

Info

Publication number: WO2017098810A1
Application number: PCT/JP2016/080849
Authority: WO
Inventors: 齋藤　真
Original assignee: ソニー株式会社
Priority date: 2015-12-07
Filing date: 2016-10-18
Publication date: 2017-06-15
Also published as: DE112016005590T5

Abstract

[Problem] To set a communication path between servers in mobile-edge computing (MEC) in a more appropriate mode. [Solution] A device provided with: an acquisition unit that acquires a connection request with which an access point name (APN) indicating a connection destination is associated; and a control unit that, on the basis of management information in which the APN and a gateway via which the device is connected to a server designated by the APN are associated, sets a bearer between a request source of the connection request and the server designated by the APN associated with the connection request.

Description

Apparatus, method, and program

The present disclosure relates to an apparatus, a method, and a program.

In recent years, mobile edge computing (MEC) technology that performs data processing with a server (hereinafter also referred to as an edge server) that is physically located near a terminal such as a smartphone has been attracting attention. . For example, in the following Non-Patent Document 1, a standard of technology related to MEC is studied.

In the MEC, the edge server is arranged at a position physically close to the terminal, so that communication delay is shortened compared to a general cloud server arranged in a concentrated manner, and applications that require high real-time performance are used. It becomes possible. Also, in MEC, high-speed network application processing can be realized regardless of the performance of the terminal by distributing the functions previously processed on the terminal side to the edge server close to the terminal. The edge server can have various functions including, for example, a function as an application server and a function as a content server, and can provide various services to the terminal.

On the other hand, the technology related to MEC, including the contents of the investigations disclosed in Non-Patent Document 1 and the like, is still short since the examination began, and it is difficult to say that sufficient proposals have been made. . For example, no sufficient proposal has been made for a technique for setting a communication path between servers in the MEC in a more preferable manner.

Therefore, the present disclosure proposes an apparatus, a method, and a program that can set a communication path between servers in the MEC in a more preferable manner.

According to the present disclosure, an acquisition unit that acquires a connection request associated with an APN (Access Point Name) indicating a connection destination, the APN, and a gateway that is connected to connect to a server specified by the APN, An apparatus is provided, comprising: a control unit that sets a bearer between a request source of the connection request and the server specified by the APN associated with the connection request based on associated management information The

Further, according to the present disclosure, a transmission unit that transmits a connection request associated with an APN (Access Point Name) indicating a connection destination to an external device, the APN, and a connection to the server specified by the APN A process of performing communication with the server via a bearer set to connect to the server specified by the APN associated with the connection request based on management information associated with the gateway A device comprising: a device.

Further, according to the present disclosure, a connection request associated with an APN (Access Point Name) indicating a connection destination is acquired, and the processor is connected to connect to the APN and a server specified by the APN. And setting a bearer between the requester of the connection request and the server specified by the APN associated with the connection request based on management information associated with the gateway Is provided.

Further, according to the present disclosure, a connection request associated with an APN (Access Point Name) indicating a connection destination is transmitted to an external device, and the processor connects to the APN and a server specified by the APN. Based on the management information associated with the gateway that passes through, the communication is performed with the server via the bearer set to connect to the server specified by the APN associated with the connection request. And a method is provided.

Further, according to the present disclosure, a connection request in which an APN (Access Point Name) indicating a connection destination is associated with a computer is acquired, and the APN and a server designated by the APN are connected. And setting a bearer between the request source of the connection request and the server specified by the APN associated with the connection request based on management information associated with the gateway, A program is provided.

According to the present disclosure, a connection request in which an APN (Access Point Name) indicating a connection destination is associated with a computer is transmitted to an external device, and the APN and a server specified by the APN are connected. Based on the management information associated with the gateway that passes through, the communication is performed with the server via the bearer set to connect to the server specified by the APN associated with the connection request. And a program for executing the program is provided.

As described above, according to the present disclosure, an apparatus, a method, and a program capable of setting a communication path between servers in an MEC in a more preferable aspect are provided.

Note that the above effects are not necessarily limited, and any of the effects shown in the present specification, or other effects that can be grasped from the present specification, together with or in place of the above effects. May be played.

It is explanatory drawing for demonstrating the outline | summary of MEC. It is explanatory drawing for demonstrating the platform of a MEC server. It is explanatory drawing for demonstrating an example of the basic architecture of EPC. It is explanatory drawing for demonstrating an example of a structure of a bearer. It is explanatory drawing for demonstrating an example of a structure of the bearer in the case of providing a radio relay station. An example of the protocol stack in communication between eNB, DeNB, and RN is shown. It is a sequence diagram which shows an example of the flow of the process of the attach procedure of UE performed in EPS. It is explanatory drawing for demonstrating an example of the network structure of LTE which introduced the MEC server. It is explanatory drawing for demonstrating another example of the network configuration of LTE which introduce | transduced the MEC server. 2 is an explanatory diagram for describing an example of a schematic configuration of a system 1 according to an embodiment of the present disclosure. FIG. It is a block diagram showing an example of composition of MEC server 300 concerning the embodiment. It is a block diagram showing an example of composition of application server 60 concerning the embodiment. 2 is an explanatory diagram for describing an example of a schematic configuration of a system 1 according to a first embodiment of the present disclosure. FIG. It is a sequence diagram which shows an example of the flow of the process which concerns on release of a default bearer. It is a sequence diagram which shows an example of the flow of the process which concerns on release of a default bearer. It is a sequence diagram which shows an example of the flow of the process which concerns on release of a default bearer. It is a sequence diagram which shows an example of the flow of the process which concerns on release of a default bearer. It is explanatory drawing for demonstrating an example of the structure for implement | achieving the connectivity between MEC servers by DPI. It is explanatory drawing for demonstrating an example of the architecture of a MEC server. It is explanatory drawing for demonstrating an example of a structure of the system by which the MEC server was introduced. FIG. 9 is an explanatory diagram for describing an example of a schematic configuration of a system 1 according to a second embodiment of the present disclosure. An example of information recorded in the GW mapping list is shown. The other example of the information recorded on a GW mapping list | wrist is shown. It is explanatory drawing for demonstrating the outline | summary of the bearer set between MEC servers. It is the figure which showed an example of the protocol stack of communication between MEC servers. It is the figure which showed an example of the protocol stack of communication between MEC servers. It is the figure which showed an example of the structure of a MEC bearer. It is the figure which showed an example of the structure of a MEC bearer. It is the figure which showed an example of the structure of a MEC bearer. It is the figure which showed an example of the structure of a MEC bearer. It is the figure which showed an example of the structure of a MEC bearer. It is the figure which showed an example of the structure of a MEC bearer. It is explanatory drawing for demonstrating an example of the bearer structure in the system 1 which concerns on the embodiment. It is the sequence diagram shown about the example of the flow of the bearer setting process performed in the system which concerns on the 1st Example of the embodiment. It is the sequence diagram shown about the example of the flow of the bearer setting process performed in the system which concerns on the 2nd Example of the embodiment. It is the sequence diagram shown about the example of the flow of the bearer setting process performed in the system which concerns on the 3rd Example of the embodiment. It is the figure which showed an example of the protocol stack of communication between MEC servers. It is the figure which showed an example of the protocol stack of communication between MEC servers. It is the figure which showed an example of the protocol stack of communication between MEC servers. It is the figure which showed an example of the protocol stack of communication between MEC servers. It is the figure which showed an example of the protocol stack of communication between MEC servers. It is the figure which showed an example of the protocol stack of communication between MEC servers. It is explanatory drawing for demonstrating the outline | summary of the 4th Example of the embodiment. It is explanatory drawing for demonstrating the outline | summary of the 5th Example of the embodiment. It is explanatory drawing for demonstrating an example of the interface implement | achieved by application of SCEF. It is explanatory drawing for demonstrating another example of the interface implement | achieved by application of SCEF. It is explanatory drawing for demonstrating another example of the interface implement | achieved by application of SCEF. It is explanatory drawing for demonstrating another example of the interface implement | achieved by application of SCEF. It is explanatory drawing for demonstrating another example of the interface implement | achieved by application of SCEF. 2 shows an example of an architecture for applying an ADC to an MEC server. 2 shows an example of an architecture for applying an ADC to an MEC server. It is the figure which showed an example of the protocol stack in communication between MME. It is the figure which showed an example of the EPC network architecture. It is a block diagram which shows an example of a schematic structure of a server. It is a block diagram which shows the 1st example of schematic structure of eNB. It is a block diagram which shows the 2nd example of schematic structure of eNB. It is a block diagram which shows an example of a schematic structure of a smart phone. It is a block diagram which shows an example of a schematic structure of a car navigation apparatus.

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 the substantially same function structure, duplication description is abbreviate | omitted by attaching | subjecting the same code | symbol.

The description will be made in the following order.
1. 1. Introduction 1.1. MEC
1.2. Bearer 1.3. Technical issues Configuration example 2.1. System configuration example 2.2. Configuration example of MEC server 2.3. 2. Configuration example of application server First embodiment 3.1. Technical features 3.2. Evaluation 4. Second Embodiment 4.1. Technical features 4.2. First Example 4.3. Second embodiment 4.4. Third Example 4.5. Fourth Example 4.6. Fifth embodiment 4.7. Evaluation 5. Application example 5.1. Application examples related to servers 5.2. Application examples related to base stations 5.3. 5. Application examples related to terminal devices Conclusion

<< 1. Introduction >>
<1.1. MEC>
(1) Overview First, an overview of MEC will be described with reference to FIG.

FIG. 1 is an explanatory diagram for explaining the outline of the MEC. In FIG. 1, an example of a communication path for a UE (User Equipment) to access an application and content in the current mobile communication (in which MEC is not introduced) represented by LTE (Long Term Evolution) is shown at the top. Is shown. In addition, an example of a communication path for the UE to access the application and the content when the MEC is introduced is shown in the lower part.

As shown in the upper part of FIG. 1, in the current mobile communication, applications and contents are arranged in an IP network that is outside (a side far from the UE) from EPC (Evolved Packet Core). Therefore, the UE can execute an application or obtain content, and a relay network (eg, backbone network), EPC, backhaul link, base station, and access on the way to the data center. Communicating via all links. Therefore, enormous network costs and delays have occurred.

On the other hand, as shown in the lower part of FIG. 1, in the MEC, the application and the content are held inside the EPC (side closer to the UE). For example, in the example shown in FIG. 1, an MEC server (that is, an edge server) formed integrally with the base station functions as an application server and a content server. Therefore, in order to execute an application or acquire content, the UE only performs communication inside the EPC only (because there can be exchange with a server outside the EPC). Good. Therefore, by introducing MEC, not only communication with extremely low delay becomes possible, but also traffic other than the access link (for example, backhaul link, EPC, and relay network) can be reduced. Furthermore, the reduction in communication delay and the reduction of traffic other than the access link can contribute to an improvement in throughput and a reduction in power consumption on the UE and network side. As described above, introduction of the MEC can bring various advantages to users, network providers, and service providers. Since MEC performs distributed processing of data on the local side (that is, the side closer to the UE), application to an application rooted in a region and application to a distributed computer are expected.

Although FIG. 1 shows an example in which the MEC server is formed integrally with the base station, the present technology is not limited to such an example. The MEC server may be formed as a device different from the base station, or may be physically separated from the base station.

(2) Platform Next, the platform of the MEC server will be described with reference to FIG.

FIG. 2 is an explanatory diagram for explaining the platform of the MEC server. The 3GPP radio network element (3GPP Radio Network Element), which is the lowest layer component, is a base station facility such as an antenna and an amplifier. On top of that, the hosting infrastructure is composed of hardware resources such as server equipment and a virtualization layer formed by software that virtualizes them. Server technology can be provided. An application platform (Application Platform) runs on this virtual server. Note that a physical server on which hardware resources such as server equipment operate corresponds to an example of a “physical server”.

The virtualization manager manages the creation and disappearance of VMs (Virtual Machines), which are the devices on which each top-level application (MEC App) operates. Since each application can be executed by different companies, the virtualization manager is required to consider security and separation of allocated resources, but can apply general cloud infrastructure technology.

Application Platform Service (Application Platform Service) is a collection of common services characteristic of MEC. The Traffic Offload Function is a switching control such as routing between when a request from the UE is processed by an application on the MEC server and when an application on the Internet (parent application on the data server) is processed. I do. Radio Network Information Services are radio status information such as the strength of radio waves between a base station and a UE (for example, formed integrally) corresponding to the MEC server by each application on the MEC server. Information is obtained from the underlying wireless network and provided to the application. Communication Services provides a route when each application on the MEC server communicates with a UE or an application on the Internet. When there is a request for generating or operating each application on the MEC server, the service registry authenticates whether the application is legitimate, registers it, and answers inquiries from other entities.

Each VM and each application on the VM operate on the application platform described above, and provide various services to the UE in place of or in cooperation with the application on the Internet.

Since the MEC server is assumed to be installed in a large number of base stations, it is also necessary to examine a mechanism for managing and linking a large number of MEC servers. The hosting infrastructure management system (Hosting Infrastructure Management System), application platform management system (Application Platform Management System), and application management system (Application Management System) manage and coordinate each corresponding entity on the MEC server.

(3) Trends in standardization In Europe, ISG (Industry Specification Groups) was established in ETSI in October 2014, and MEC standardization work was started. The first specification is targeted at the end of 2016, and standardization work is currently underway. More specifically, standardization is proceeding mainly with standardization of API (Application Programming Interface) for MEC implementation under the cooperation of ETSI ISG NFV (Network Function Virtualization) and 3GPP.

<1.2. Bearer>
Next, the bearer will be described with reference to FIGS. First, the architecture of the core network will be described with reference to FIG.

FIG. 3 is an explanatory diagram for explaining an example of the basic architecture of EPC (Evolved Packet Core). UE (User Equipment) is a terminal device and is also referred to as a user. eNB (evolved Node B) is a base station. A P-GW (PDN (Packet Data Network) Gateway) is a connection point between an EPC and a PDN (for example, a concept including the Internet, an external IP network, a cloud, etc.), and exchanges user packets with the PDN. S-GW (Serving Gateway) is a connection point between E-UTRAN (Evolved Universal Terrestrial Radio Access Network) and EPC, and provides user packet routing and forwarding functions. OCS (Online Charging System) is a functional entity that controls billing in real time. OFCS (Offline Charging System) is a functional entity that performs charging control offline. PCRF (Policy and Charging Rule Function) is a functional entity that performs policy and charging control. MME (Mobility Management Entity) is a functional entity that manages mobility. HSS (Home Subscriber Server) is a functional entity that manages subscriber information. The solid line in the figure means the user plane, and the broken line means the control plane.

UE is connected to eNB and connected to EPC via S-GW based on control of MME and HSS. Further, the UE connects to the Internet (ie, PDN) via the P-GW, and connects to a content server on the Internet based on a request from an application on the UE. The connection between the UE and the PDN is established by setting a bearer. A bearer means a series of physical or logical paths for transferring user data. An example of a bearer configuration in an end-to-end service from a UE to a device on the Internet is shown in FIG.

FIG. 4 is an explanatory diagram for explaining an example of the configuration of the bearer. As shown in FIG. 4, the bearer set between UE and eNB is also called a radio bearer. A bearer set between the eNB and the UE is also referred to as an S1 bearer. And the bearer set between UE and S-GW is also named E-RAB (E-UTRAN Radio Access Bearer) generically. A bearer set between the S-GW and the P-GW is also referred to as an S5 / S8 bearer. A bearer set between the UE and the P-GW is also collectively referred to as an EPS (Evolved Packet System) bearer. A bearer set between the P-GW and a device on the Internet is also referred to as an external bearer.

The LTE-A (LTE Advanced) standard also proposes a configuration in which a radio relay station (RN: Relay Node) that relays radio transmission between the UE and the eNB is provided. For example, FIG. 5 is an explanatory diagram for explaining an example of the configuration of a bearer when a radio relay station is provided. In the following description, among eNBs, especially when an eNB to which an RN is connected is explicitly indicated, it may be referred to as “DeNB (Donor eNodeB)”. As illustrated in FIG. 5, the bearer set between the UE and the DeNB is also referred to as an S1 / Un bearer.

FIG. 6 shows an example of a protocol stack in communication between eNB, DeNB, and RN. As shown in FIGS. 5 and 6, each between DeNB and DeNB and between RN and DeNB is equivalent to a bearer used for the X2 interface mapped one-to-one.

Here, the EPS bearer of interest in this technology will be described in more detail. The EPS bearer is set between, for example, a UE and one or more P-GWs specified by an APN (Access Point Name). There are one default bearer (Default Bearer) and one or more settable individual bearers (Dedicated Bearer) in EPS bearers that can be set between one APN. In each bearer, SDF (Service Data Flow) is exchanged. Tables 1 and 2 below show an overview of bearer QoS.

FIG. 7 is a sequence diagram showing an example of the flow of the UE attach procedure executed in the EPS.

First, the UE transmits an attach request signal specifying the APN to the MME (step S11). The APN specified here is also referred to as a default APN. Next, various processes such as identification, authentication, and encryption are performed between the UE and the HSS (step S12). At this time, the MME performs user authentication based on the authentication information acquired from the HSS, and acquires and manages contract information necessary for bearer setting from the HSS. Next, the MME transmits a location registration request (Location Request) signal to the HSS (step S13), and receives a location registration response (Location Request Response) signal from the HSS (step S14).

Then, based on the APN notified from the UE, the MME selects the bearer setting destination S-GW and P-GW, and transmits a bearer request signal to the selected S-GW (step S15). At that time, the MME performs an APN-FQDN (Fully Qualified Domain Name) using, for example, a DNS resolver (Domain Name System resolver) function, and selects a P-GW that can connect to the PDN for which a connection request has been made. Also, the MME selects an S-GW based on a policy such as a collaboration base based on a TAI (Tracking Area Identification) described in the cell ID acquired from the eNB.

Next, the S-GW performs bearer establishment procedures for the P-GW specified in the bearer setting request signal (step S16). In this bearer establishment procedure, the P-GW acquires charging information to be applied in cooperation with the PCRF, and further performs connection processing to the PDN. When the bearer setting with the P-GW is completed, the S-GW transmits a bearer request request response signal to the MME (step S17).

The MME transmits a radio bearer setting request (Radio Bearer) signal including information received from the S-GW, that is, information indicating that the attach request has been accepted, to the eNB (step S18). The eNB transmits a radio bearer setting request (Radio Bearer) signal including information indicating that the attach request has been accepted to the UE, and establishes a radio bearer with the UE (step S19). When the eNB receives a radio bearer response signal from the UE (step S20), the eNB transmits a radio bearer response signal to the MME (step S21). Then, the UE transmits an attach completion signal to the MME. The bearer set in this way is a default bearer.

This enables transmission of uplink user plane traffic data via S-GW and P-GW from UE to PDN (for example, application server on PDN). Also, downlink user plane traffic data can be transmitted from the PDN to the UE via the S-GW and P-GW.

When a bearer update request signal is transmitted from the MME to the S-GW (step S23), the S-GW performs a bearer update procedure (step S24) and a bearer update request response (Bearer). An Update Request Response signal is transmitted to the MME (step S25).

This completes the process. The processing here is “3GPP,“ 3GPP TS24.301 V8.1.0 ”, March 2009, [searched on November 19, 2015], Internet <http: //www.arib.or .jp / IMT-2000 / V730Jul09 / 5_Appendix / Rel8 / 24 / 24301-810.pdf> ”.

<1.3. Technical issues>
Subsequently, a technical problem of an embodiment of the present disclosure will be described.

FIG. 8 is an explanatory diagram for explaining an example of an LTE network configuration in which an MEC server is introduced. As shown in FIG. 8, the LTE network configuration is composed of E-UTRAN in the wireless network and EPC in the core network. Such a configuration may also be referred to as EPS. The UE accesses the Internet via the P-GW specified by the APN. When the UE communicates with a content server on the Internet, typically, user data passes through the eNB, S-GW, and P-GW.

Similarly, in the example shown in FIG. 8, even when the UE accesses the MEC server, the UE accesses the MEC server via the P-GW specified by the APN. That is, when the UE communicates with the MEC server, typically, user data passes through the eNB, S-GW, and P-GW.

Here, the communication path setting procedure will be described in more detail. First, the UE connects to a MEC server that can be specified by a URI (Uniform Resource Identifier) or an IP address by performing an attach procedure. However, user plane traffic from the UE is once carried to the P-GW. The P-GW removes the header (for example, GTP (general packet radio service) Tunnel Protocol) header used in the EPC from the user packet. Then, the P-GW transmits user data to the destination address specified by the URI or IP address specified by the UE.

Here, when a UE specifies a URI and tries to connect, it normally starts a DNS resolver and acquires an IP address that means the URI before trying to connect. Specifically, after the connection with the P-GW is established, the UE acquires an IP address with the DNS server in the PDN or the DNS server in the EPC. In the EPC, the MME may be responsible for the DNS resolver function. Since the acquired IP address of the MEC server is an address in the EPC, a connection from the P-GW to the MEC server via the EPC is established.

As described above, even if the MEC is introduced, a redundant communication path is set according to the structure of the current mobile communication network, and it is difficult to obtain an expected effect.

On the other hand, for example, as in eNB, an MEC server is installed in a place closer to an application user (in other words, UE), and the so-called QoS is provided by grasping the radio wave status and usage status of radio access. Therefore, it is expected to realize a response with a lower delay. For example, FIG. 9 is an explanatory diagram for explaining another example of the LTE network configuration in which the MEC server is introduced, and an example of a method for realizing connectivity from the UE to the MEC server arranged in the eNB. It is shown. That is, as a method for realizing connectivity from the UE to the MEC server arranged in the eNB, for example, it is conceivable to use a switch (SW) function such as a virtualization technique or a packet switching technique.

On the other hand, when an application on the MEC server is used from the UE, it is assumed that the MEC server is used in cooperation with an MEC server located at another location, an application server on the Internet, or the like. obtain. As a specific example, in the case of the example shown in FIG. 9, it can be assumed that the MEC server indicated by the reference symbol MEC-1 establishes communication with an application server operating on the Internet.

On the other hand, at present, the 3GPP rules do not clarify how to establish a communication path between MEC servers that are not entities of the wireless core network. Specifically, in the regulations stipulated by 3GPP, for example, an interface for establishing a communication path between MEC servers via devices such as eNB, RN, and S-GW is not defined. Therefore, the present disclosure proposes a mechanism for setting a communication path between MEC servers in a more preferable manner.

In this specification, the present technology will be described assuming an EPS in LTE as a network architecture. However, the present technology can be applied to UMTS (Universal Mobile Telecommunications System) in 3G, and can also be applied to any other network architecture.

<< 2. Configuration example >>
<2.1. System configuration example>
First, an example of a schematic configuration of the system 1 according to an embodiment of the present disclosure will be described with reference to FIG. FIG. 10 is an explanatory diagram for describing an example of a schematic configuration of the system 1 according to an embodiment of the present disclosure. As illustrated in FIG. 10, the system 1 includes a wireless communication device 100, a terminal device 200, and an MEC server 300. Here, the terminal device 200 is also called a user. The user may also be referred to as a UE. That is, the UE 200 described above may correspond to the terminal device 200 illustrated in FIG. The wireless communication device 100C is also called UE-Relay. The UE here may be a UE defined in LTE or LTE-A, and the UE-Relay may be Prose UE to Network Relay as discussed in 3GPP, and more generally It may mean equipment.

(1) Wireless communication device 100
The wireless communication device 100 is a device that provides a wireless communication service to subordinate devices. For example, the wireless communication device 100A is a base station of a cellular system (or mobile communication system). The base station 100A performs wireless communication with a device (for example, the terminal device 200A) located inside the cell 10A of the base station 100A. For example, the base station 100A transmits 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 and the like. The base station 100A is logically connected to the core network 40 through, for example, an S1 interface, and can transmit and receive control information and the like. Note that communication between these devices can be physically relayed by various devices.

Here, the radio communication device 100A shown in FIG. 10 is a macro cell base station, and the cell 10 is a macro cell. On the other hand, the

wireless communication devices

100B and 100C are master devices that operate the

small cells

10B and 10C, respectively. As an example, the master device 100B is a small cell base station that is fixedly installed. The small cell base station 100B establishes a wireless backhaul link with the macro cell base station 100A and an access link with one or more terminal devices (for example, the terminal device 200B) in the small cell 10B. Note that the wireless communication device 100B may be a relay node defined by 3GPP. The master device 100C is a dynamic AP (access point). The dynamic AP 100C is a mobile device that dynamically operates the small cell 10C. The dynamic AP 100C establishes a radio backhaul link with the macro cell base station 100A and an access link with one or more terminal devices (for example, the terminal device 200C) in the small cell 10C. The dynamic AP 100C may be, for example, a terminal device equipped with hardware or software that can operate as a base station or a wireless access point. The small cell 10C in this case is a locally formed network (Localized Network / Virtual cell).

The cell 10 may be operated according to any wireless communication scheme such as LTE, LTE-A (LTE-Advanced), GSM (registered trademark), UMTS, W-CDMA, CDMA200, WiMAX, WiMAX2, or IEEE 802.16, for example. .

Note that the small cell is a concept that can include various types of cells (for example, femtocells, nanocells, picocells, and microcells) that are smaller than the macrocells and that are arranged so as to overlap or not overlap with the macrocells. In one example, the small cell is operated by a dedicated base station. In another example, the small cell is operated by a terminal serving as a master device temporarily operating as a small cell base station. So-called relay nodes can also be considered as a form of small cell base station. A wireless communication device that functions as a master station of a relay node is also referred to as a donor base station. The donor base station may mean a DeNB in LTE, and more generally may mean a parent station of a relay node.

(2) Terminal device 200
The terminal device 200 can communicate in a cellular system (or mobile communication system). The terminal device 200 performs wireless communication with a wireless communication device (for example, the base station 100A, the

master device

100B, or 100C) of the cellular system. For example, the terminal device 200A receives a downlink signal from the base station 100A and transmits an 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 via a gateway device (P-GW in FIG. 8). For this reason, the wireless communication apparatus 100 provides the service provided by the application server 60 to the MEC server 300 and the user via the packet data network 50, the core network 40, and the wireless communication path.

(4) MEC server 300
The MEC server 300 is a service providing apparatus that provides a service (application, content, or the like) to a user. The MEC server 300 can be provided in the wireless communication device 100. In that case, the wireless communication device 100 provides the service provided by the MEC server 300 to the user via the wireless communication path. The MEC server 300 may be realized as a logical functional entity, and may be formed integrally with the wireless communication device 100 or the like as shown in FIG.

For example, the base station 100A provides the service provided by the MEC server 300A to the terminal device 200A connected to the macro cell 10. Also, the base station 100A provides the service provided by the MEC server 300A to the terminal device 200B connected to the small cell 10B via the master device 100B.

Further, the master device 100B provides the service provided by the MEC server 300B to the terminal device 200B connected to the small cell 10B. Similarly, the master device 100C provides the service provided by the MEC server 300C to the terminal device 200C connected to the small cell 10C.

(5) Supplement Although the schematic configuration of the system 1 has been described above, the present technology is not limited to the example illustrated in FIG. For example, as a configuration of the system 1, a configuration that does not include a master device, an SCE (Small Cell Enhancement), a HetNet (Heterogeneous Network), an MTC (Machine Type Communication) network, or the like may be employed.

<2.2. Configuration example 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. FIG. 11 is a block diagram illustrating an exemplary configuration of the MEC server 300 according to an embodiment of the present disclosure. Referring to FIG. 11, the MEC server 300 includes a communication unit 310, a storage unit 320, and a processing unit 330.

(1) Communication unit 310
The communication unit 310 is an interface for performing communication with other devices. For example, the communication unit 310 communicates with the corresponding wireless communication device 100. When the MEC server 300 is formed as a logical entity and included in the wireless communication device 100, the communication unit 310 performs communication with, for example, the control unit of the wireless communication device 100. The MEC server 300 may have an interface for performing direct communication with a device other than a device formed integrally.

(2) Storage unit 320
The storage unit 320 temporarily or permanently stores a program for operating the MEC server 300 and various data. For example, the MEC server 300 may store 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 MEC platform 331, a VNF (Virtual Network Function) 333, and a service providing unit 335. Note that the processing unit 330 may further include other components other than these components. That is, the processing unit 330 can perform operations other than the operations of these components.

The MEC platform 331 is as described above with reference to FIG.

VNF333 is a software package for realizing a network function. The VNF 333 operates on a virtual machine called NFVI (Network Functions Virtualisation Infrastructure). The specifications of VNF and NFVI are being studied by ETSI's NFV ISG (Network Functions Virtualization Industry Specification Group). For details, refer to “ETSI,“ GS NFV-SWA 001 V1.1.1 (2014-12) ”, December 2014, [November 19, 2015 search], Internet <http: // www. etsi.org/deliver/etsi_gs/NFV-SWA/001_099/001/01.01.01_60/gs_NFV-SWA001v010101p.pdf> ”. The VNF 333 may mean the VNF under consideration of this specification, or may more generally mean a virtualized network function.

The service providing unit 335 has a function of providing various services. Typically, the service providing unit 335 is realized as an MEC application that operates on the MEC platform 331. In this specification, an application that operates on the MEC server 300 is also referred to as an MEC application. For example, the MEC application operating on the MEC server 300 may be an instance of an application copied from the application server 60, or may be an application placed directly on the MEC server 300.

<2.3. Application server configuration example>
Next, an example of the configuration of the application server 60 according to an embodiment of the present disclosure will be described with reference to FIG. FIG. 12 is a block diagram illustrating an exemplary configuration of the application server 60 according to an embodiment of the present disclosure. Referring to FIG. 12, the application server 60 includes a communication unit 61, a storage unit 62, and a processing unit 63.

(1) Communication unit 61
The communication unit 61 is an interface for performing communication with other devices. For example, the communication unit 61 communicates with other devices on the PDN.

(2) Storage unit 62
The storage unit 62 temporarily or permanently stores a program for operating the application server 60 and various data. For example, the application server 60 can store various contents and applications provided to the user.

(3) Processing unit 63
The processing unit 63 provides various functions of the application server 60. The processing unit 63 corresponds to, for example, a CPU (Central Processing Unit). The processing unit 63 includes a service providing unit 64. Note that the processing unit 330 may further include other components other than this component. That is, the processing unit 330 can perform operations other than the operations of the constituent elements.

The service providing unit 64 has a function of providing various services. Typically, the service providing unit 64 is realized as an application.

An application that operates on the application server 60 and has a corresponding relationship with the MEC application that operates on the MEC server 300 is also referred to as an MEC application. Similarly, an application that operates on the terminal device 200 and has a corresponding relationship with the MEC application that operates on the MEC server 300 is also referred to as an MEC application.

The configuration example of each device has been described above. Hereinafter, for convenience of explanation, the radio communication device 100 is also referred to as an eNB 100, and the terminal device 200 is also referred to as a UE 200.

<< 3. First Embodiment >>
As one of the solutions to the above-mentioned problems, the MEC server is arranged at an arbitrary location (for example, RN, eNB, S-GW, etc.), and the packet route is set by a switch function (SW) such as DPI (Deep Packet Inspection). A mechanism for realizing connectivity with the UE by switching is being studied. Therefore, as an embodiment, an example of a mode for switching packet paths by DPI (Deep Packet Inspection) will be described.

<3.1. Technical features>
For example, FIG. 13 is an explanatory diagram for explaining an example of a schematic configuration of the system 1 according to the present embodiment, and a configuration for realizing connectivity between the MEC server 300 and the UE 200 by DPI. An example is shown. As illustrated in FIG. 13, the system 1 includes an eNB 100, a UE 200, an MEC server 300, an S-GW 41, a P-GW 42, an MME 43, an HSS 44, a PDN 50, and an application server 60. In the example shown in FIG. 13, on the MEC server 300, the MEC DPI 333A and the MEC router 333B operate as VNFs. Further, the MEC application 335 operates on the MEC server 300. In addition, the solid line in a figure means a user plane (it is also called a data plane), and a broken line means a control plane.

The MEC DPI 333A has a function of performing a peep (for example, DPI) on the acquired packet. For example, the MEC DPI 333A removes the GTP-U (GTP for User Plane) header of the packet transmitted from the eNB 100 to the S-GW 41, peeks at the IP header, and stores the information stored in the contents (for example, the packet Destination IP address) is acquired.

The MEC router 333B has a function of switching packet paths. For example, when the destination IP address acquired by the MEC DPI 333A indicates the MEC application 335, the MEC router 333B directly transmits the packet to the MEC application 335 instead of the S-GW 41. At that time, the MEC router 333B may transmit the packet after adding a GTP-U header designating the MEC server 300 to the packet. On the other hand, if the destination IP address acquired by the MEC DPI 333A does not indicate the MEC application 335, the MEC router 333B adds the GTP-U header once removed to the packet and transmits the packet to the S-GW 41.

Therefore, the MEC router 333B holds information for identifying the GTP-U header and the S-GW 41 for each UE 200 until the default bearer (that is, tunneling) between the eNB 100 and the S-GW 41 is released. Typically, the MEC router 333B retains this information until it detects the release of the default bearer between the eNB 100 and the S-GW 41. Here, release of the default bearer can be detected in a plurality of ways. For example, FIGS. 14 to 17 are sequence diagrams illustrating an example of a flow of processing relating to release of a default bearer. As a specific example, as shown in FIG. 14, when a UE performs a detach procedure (Detach Procedure), the UE receives a detach accept signal from the MME, and then releases a connection (signaling connection release). The release of the default bearer may be detected by the eNB receiving the signal. When the MME, HSS, or P-GW performs the detach procedure, the release of the default bearer may be detected by the eNB 100 receiving the connection release signal. For example, FIG. 15 shows an example when the MME performs a detach procedure. FIG. 16 shows an example in which the HSS performs a detach procedure. Similarly, FIG. 17 shows an example when the P-GW performs a detach procedure. Note that an example of the flow of processing related to the release of the default bearer shown in FIGS. 14 to 17 is generally known, and detailed description thereof is omitted. Moreover, release of a default bearer may be detected by eNB100 failing in detection of UE200 like the case where the power supply of UE200 is turned off.

Next, attention is paid to the connection method between the MEC servers when the connectivity from the UE to the MEC server is realized by the method based on the DPI. For example, FIG. 18 is an explanatory diagram for describing an example of a configuration for realizing connectivity between MEC servers by DPI. The example illustrated in FIG. 18 illustrates an example of establishing a connection between the first MEC server 300-1 installed in the eNB 100 and the second MEC server 300-2 installed in the S-GW 41. ing. In FIG. 17, a path indicated by a thick line corresponds to a communication path between the MEC application operating on the first MEC server 300-1 and the MEC application operating on the second MEC server 300-2.

Here, an outline of a procedure for establishing a communication path between the first MEC server 300-1 and the second MEC server 300-2, which is indicated by a bold line in FIG. 18, will be described.

First, the first MEC server 300-1 uses the service discovery function provided from the MEC platform to identify another MEC server located in the vicinity (in other words, the aggregation point located at the upper level). Identification information (for example, an IP address for specifying the second MEC server 300-2) is acquired. In the following description, it is assumed that the IP address of the other MEC server is acquired as identification information for specifying the other MEC server.

Next, the first MEC server 300-1 adds a GTP header for identifying the acquired IP address and the S-GW 41 to a packet to be transmitted (for example, a packet from the MEC application 335-1). The packet is sent to the MEC router 333B-1. The MEC router 333B-1 transfers the packet sent from the first MEC server 300-1 to the S-GW 41.

The S-GW 41 replaces the GTP header of the packet transferred from the MEC router 333B-1 with the GTP header for connecting to the P-GW 42, and replaces the packet with the MEC DPI 333A-2 of the second MEC server 300-2. Send to.

The MEC DPI 333A-2 removes the GTP header from the received packet and acquires an IP address indicating the destination of the packet. Next, the MEC router 333B-2 switches the route of the packet according to the destination indicated by the acquired IP address. For example, if the acquired IP address indicates the MEC application 335-2 that operates on the second MEC server 300-2, the MEC router 333B-2 sends the packet to the MEC application instead of the P-GW 42. Send directly to 335-2. If the acquired IP address does not indicate the MEC application 335-2 running on the second MEC server 300-2, the packet is transmitted to the P-GW.

As described above, the packet is transmitted from the first MEC server 300-1 to the second MEC server 300-2. Needless to say, packet transmission from the second MEC server 300-2 to the first MEC server 300-1 is also realized by the same procedure. In the example illustrated in FIG. 18, the description has been given focusing on the case where the connection between the MEC servers installed in the eNB and the S-GW is established. However, the present embodiment is not necessarily limited to the same mode. As a specific example, the connection between the MEC servers may be established by the same procedure for each of the RN and the eNB, the eNB and the eNB, and the RN and the S-GW. Is possible.

<3.2. Evaluation>
According to the present embodiment, the shortest communication path that does not pass through the P-GW 42 is set between the UE 200 and the MEC application 335. In addition, according to the present embodiment, a communication path can be set between MEC servers. On the other hand, as described with reference to FIG. 18, when establishing a connection between MEC servers based on DPI as in the present embodiment, it is considered that there are the following disadvantages.

First, in the system 1 according to the present embodiment, DPI is performed by the MEC DPI 333A on all packets transmitted from the UE 200 or the MEC server 300. Therefore, the processing load for DPI increases and the processing delay time increases. Also, a header group (for example, IP header, UDP header, GTP-U header, etc.) removal function, a removed header group storage function, a management function for managing the UE 200 and MEC server 300 and a list of header groups, and a header Additional functions of the group are required. This also causes scalability issues. Furthermore, a mechanism for avoiding the security and confidentiality problems of user data that may be caused by the DPI function is required.

In addition, when the eNB 100 and the MEC server 300 connected to a relay node that relays user packets wirelessly or a wireless backhaul and the MEC server 300 are integrally formed, the MEC server 300 itself needs to have a wireless communication interface.

Therefore, the second embodiment described below has been developed in order to eliminate the above drawbacks.

<< 4. Second Embodiment >>
The second embodiment of the present disclosure will be described in detail below.

<4.1. Technical features>
(1) Virtualization of Network Function Entity First, an example of the architecture of the MEC server will be described with reference to FIG. FIG. 19 is an explanatory diagram for explaining an example of the architecture of the MEC server. As shown in FIG. 19, the MEC server includes hardware such as a commercial off-the-shelf (COTS), a computer, a memory, and an input / output (I / O) interface. A KVM (Kernel-based Virtual Machine) hypervisor and a container engine operate on these hardware, and an MEC platform and a plurality of VMs, VNFs, and applications operate on the hardware. As a more specific example, a KVM hypervisor may be operated on the host OS, and the MEC platform, VM, VNF, and application may be operated on the KVM hypervisor. As another example, a container engine may be operated on the host OS, and the MEC platform, VM, VNF, and application may be operated on the container engine. As another example, the KVM hypervisor and the container engine may be operated on the host OS, and the MEC platform, the VM, the VNF, and the application may be operated on the KVM hypervisor and the container engine.

For example, vMME (Virtual MME) in which MME is virtualized operates as VNF-1 on VM (Virtual Machine) -1. Further, the vS-GW in which the S-GW is virtualized operates as the VNF-2 on the VM-2. In addition, vP-GW in which P-GW is virtualized operates as VNF-3 on VM-3. In addition, vHSS in which HSS is virtualized operates as VNF-4 on VM-4. Further, the vPCRF in which the PCRF is virtualized operates as the VNF-5 on the VM-5. Also, a vRAN in which a RAN (Radio Access Network) is virtualized operates as the VNF-6 on the VM-6. In addition, as VNF-7 on VM-7, a functional entity that provides an RNIS (Radio Network Information Services) function operates. Further, a functional entity that provides a location function operates as VNF-8 on the VM-8. Further, a functional entity that provides a mobility function operates as VNF-9 on VM-9. Further, as VNF-10 on the VM-10, a functional entity that provides management functions such as instance movement management and state management operates. In addition, a functional entity that provides a service discovery function operates as VNF-11 on VM-11. Here, the service discovery function is information (for example, an IP address, etc.) that is provided by a function providing platform (for example, MEC platform) on the MEC server and that identifies other MEC servers to which applications and the like are connected. And a function that provides search results of available services.

Also, an MEC application may operate as an application on the VM-12. Also, the MEC application may run on the KVM hypervisor. For example, in the example shown in FIG. 19, a first MEC application (Appl-1) and a second MEC application (Appl-2) are operating as applications on the KVM hypervisor.

In addition, it responds to requests such as transmission band (transmission speed), delay request, optimization of transmission speed such as TCP / IP, and correspondence to OSS (Operations System Supports) / BSS (Business system Supports). VNF is considered. When communication with an existing device (for example, a base station, PCRF, HHS, MME, etc.) is required, this VNF operates via the API to exchange communication. Note that a protocol and an interface will be separately described later together with an embodiment of the present disclosure. Further, in the following description, a functional entity virtualized on the MEC server is given a name “v” indicating virtual (Virtual), such as vMME, vP-GW, and vS-GW. It shall be.

Next, an example of a network architecture including an MEC server will be described with reference to FIG. FIG. 20 is an explanatory diagram for explaining an example of the architecture of a network including an MEC server. As shown in FIG. 20, the access from the network management function such as OSS and BSS to the functional entity virtualized on the MEC server is managed by the MEC platform to be the same as the access to the existing functional entity. The

The VNF manager and the MEC manager monitor the operation of the virtual entity such as the functional entity virtualized on the MEC server and the MEC application, and perform the operation of the application according to the monitoring result. Control. Similarly, the virtualization infrastructure manager includes hardware such as COTS (commercial off-the-shelf), computer, memory, and I / O (Input / Output) interface, and a KVM hypervisor and a container operating on the hardware. Monitor engine operation. Then, the virtualization infrastructure manager controls the operation of the hardware, the KVM hypervisor and the container engine that operate on the hardware, according to the monitoring result. In addition, the VNF manager and MEC manager, and the virtualization infrastructure manager may operate in cooperation with each other. The operations of the network management function, the VNF manager, the MEC manager, and the virtualization infrastructure manager may be autonomous based on management by an orchestrator.

(2) Example of System Configuration Next, in order to make the features of the present embodiment easier to understand, an example of a schematic configuration of the system 1 according to the present embodiment will be described.

FIG. 21 is an explanatory diagram for explaining an example of a schematic configuration of the system 1 according to the present embodiment. In the example shown in FIG. 21, the system 1 includes an eNB 100, DeNBs 110-1 and 110-2, RNs 120-1 and 120-2, a UE 200, MEC servers 300-0 to 300-5, and an S-GW 41. , P-GW 42, MME 43, HSS 44, OCS 45, OFCS 46, PCRF 47, PDN 50, and application server 60. In the blocks indicating the nodes of the eNB 100, the DeNBs 110-1 and 110-2, and the RNs 120-1 and 120-2, information described in parentheses indicates identification information of the node.

In the example shown in FIG. 21, the MEC server 300-0 is associated with the base station 100 (for example, formed integrally). Similarly, MEC servers 300-1 and 300-3 are associated with RNs 120-1 and 120-2, respectively. The MEC servers 300-2 and 300-4 are associated with the DeNBs 110-1 and 110-2. The MEC server 300-5 is associated with the S-GW 41.

In each of the MEC servers 300-0 to 300-5, a VNF corresponding to the characteristics of the MEC server is operating on the MEC platform. Specifically, in the MEC server 300-1 associated with the RN 120-1, vDeNB, vS-GW, vP-GW, and MEC Storage-1 are operating on the MEC platform. Note that MEC Storage-1 is a location where an MEC application such as an application server or the like that operates on the MEC server 300-1 is stored. Further, MEC Storage-1 may be a place where VMs and containers are stored. In the following description, when simply described as “MEC application”, unless otherwise specified, it may include an operation base of an MEC application operating on an MEC server such as an application server. In the following description, when the vDeNB, vS-GW, and vP-GW operating on the MEC server 300-1 are explicitly indicated, they may be referred to as vDeNB_1, vS-GW_1, and vP-GW_1. Also,

Similarly, in the MEC server 300-3 associated with the RN 120-2, the vDeNB_3, vS-GW_3, vP-GW_3, and the MEC application are operating on the MEC platform. In the MEC server 300-0 associated with the eNB 100, vS-GW_0, vP-GW_0, and the MEC application are operating on the MEC platform. In the MEC server 300-2 associated with the DeNB 110-1, vS-GW_2, vP-GW_2, and an MEC application are operating on the MEC platform. Similarly, in the MEC server 300-4 associated with the DeNB 110-2, vS-GW_4, vP-GW_4, and the MEC application are operating on the MEC platform. In the MEC server 300-5 associated with the S-GW 41, the vP-GW_5 and the MEC application operate on the MEC platform. Further, in each of the MEC servers 300-0 to 300-5, a VNF that virtualizes other functional entities in the mobile communication network, such as vMME, vHSS, and vPCRF, may operate. In addition, the solid line in a figure means a user plane and a broken line means a control plane. Further, among the solid lines in the figure, the part indicated by a bold line means a communication path (virtual bearer described later) that is virtually set. A virtualized VNF (vDeNB, vS-GW / vP-GW) or the like may operate on the NFV platform or other virtual infrastructure.

(3) Bearer Setting In the system 1 according to the present embodiment, the MME 43 sets (that is, establishes) a bearer between the MEC servers 300.

(3-1) Setting of MEC Bearer Specifically, the MME 43 first generates management information (hereinafter also referred to as “GW mapping list”) for specifying a connection path between the MEC servers 300 in advance. . The GW mapping list includes, for example, an APN for connecting to each MEC server 300 (that is, an APN for specifying the vP-GW of the MEC server 300), and a gateway through which the MEC server 300 is connected. (For example, P-GW, S-GW, vP-GW, and vS-GW) are recorded in association with each other.

For example, FIG. 22 shows an example of information recorded in the GW mapping list. In the example shown in FIG. 22, between the identification information of a wireless network node (for example, RN, eNB, DeNB, etc.), the APN indicating the connection destination, and the server (for example, MEC server) designated by the node and the APN. It is recorded in association with a list of gateways through which a connection is established. The numbers in parentheses indicate the number of physical hops. As a specific example, in the system 1 shown in FIG. 21, when establishing a connection between the RN 120-1 indicated by “RN_1” and the MEC server 300-5 designated by “vAPN # 5”. Pay attention. In this case, in the GW mapping list, an entry indicating a connection relationship between the note indicated by “RN_1” and the server specified by “vAPN # 5” includes a DeNB 110- 1, information indicating each of S-GW 41 and vP-GW_5 in the MEC server 300-5 is recorded.

FIG. 23 shows another example of information recorded in the GW mapping list. In the example shown in FIG. 23, an APN indicating each of a connection source and a connection destination and a list of gateways through which a connection between servers designated by each APN is established are recorded in association with each other. The numbers in parentheses indicate the number of physical hops. As a specific example, attention is paid to a case where a connection is established between the MEC server 300-1 designated by “APN # 1” and the MEC server 300-2 designated by “APN # 2”. In this case, in the GW mapping list, an entry indicating the connection relationship between the servers designated by “APN # 1” and “vAPN # 2” includes an RN 120-1 and a DeNB 110-1 that are routed at the time of connection. VS-GW_2 and vP-GW_2 in the MEC server 300-2
And information indicating each of them is recorded.

Information recorded in the GW mapping list such as identification information (P-GW ID, etc.) indicating each node and identification information (vAPN, PDN ID, etc.) specifying each server is stored in the HSS 44 in advance, for example. Recorded and managed (Provisioning / Commissioning). In other words, the MME 43 may generate a GW mapping list based on information acquired from the HSS 44, for example.

When the MME 43 receives a connection request associated with an APN indicating a connection destination from the MEC server 300, the MME 43 designates the MEC server 300 serving as a request source and the APN associated with the connection request based on the GW mapping list. A bearer is set up with another MEC server 300 that performs the operation. Here, with reference to FIG. 24, the outline of the bearer set by the MME 43 will be described between the MEC server 300-1 (MEC-Server-1) and the MEC server 300-2 (MEC-Server-2) in FIG. A case where a bearer is set between them will be described as an example. FIG. 24 is an explanatory diagram for explaining an outline of a bearer set between MEC servers.

For example, when the MME 43 receives a connection request associated with an APN that specifies the MEC server 300-2 from the MEC server 300-1, the MME 43 determines whether the MEC server 300-1 and 300-2 are based on the GW mapping list. Identify a list of gateways through which to establish a connection. Accordingly, for example, the vP-GW_1 and vS-GW_2 of the MEC server 300-1, the RN 120-1 indicated by “RN_1”, the DeNB 110-1 indicated by “DeNB_1”, and the MEC server 300-2. vS-GW_2 and vP-GW_2 are specified. Of the identified gateways, a physical configuration such as RN, eNB, DeNB, P-GW, and S-GW corresponds to an example of “first gateway”. A virtual configuration such as vP-GW and vS-GW on the MEC server 300 corresponds to an example of “second gateway”.

Next, the MME 43 sets a bearer among the identified vP-GW_1, vS-GW_2, DeNB_1 (ie, RN120-1), DeNB_1 (ie, DeNB110-1), vS-GW_2, and vP-GW_2. To do. Note that details of a series of processing flows related to the setting of each bearer will be separately described later as an example.

The MME 43 then sets a series of bearers set between the vP-GW_1, vS-GW_2, DeNB_1 (ie, RN120-1), DeNB_1 (ie, DeNB110-1), vS-GW_2, and vP-GW_2. Alternatively, it may be set as a virtual bearer. Thus, for example, a series of bearers between the vP-GW_1 of the MEC server 300-1 (MEC-Server-1) and the vP-GW_2 of the MEC server 300-2 (MEC-Server-2) It becomes possible to virtualize as a bearer. In the following description, the above-described virtual bearer is also referred to as “MEC bearer”.

(3-2) Expansion of MEC bearer Further, in the system 1 according to the present embodiment, a path to the vP-GW is virtualized and provided as VNF in the MEC server 300, for example, a plurality of MEC servers 300 It is also possible to extend the MEC bearer between the services operating in each. The service in this description includes, for example, a service provided for each OTT (Over-The-Top) such as a service provider, an application that operates individually, a VM, a container, and the like.

As a specific example, attention is paid to a case where the MME 43 sets a bearer between services operating on the MEC servers 300-1 and 300-2. In this case, the MME 43, in addition to the connection request associated with the APN indicating the connection destination from the MEC server 300-1, information for specifying a service that operates on the MEC server 300-2 that is the connection destination (for example, , URI, IP address, etc.). Information for specifying a service operating on the MEC server 300-2 can be acquired by using, for example, a service discovery function provided by the MEC platform.

Next, the MME 43 specifies a list of gateways through which the connection between the MEC servers 300-1 and 300-2 is established based on the GW mapping list based on the GW mapping list. And MME43 sets a bearer between each specified gateway. As a result, a series of bearers is set between the vP-GW_1 of the MEC server 300-1 (MEC-Server-1) and the vP-GW_2 of the MEC server 300-2 (MEC-Server-2).

Further, based on the information for specifying the acquired service, the MME 43 virtualizes the path from the vP-GW_2 to the service operating in the MEC server 300-2 as VNF in the MEC server 300-2. To set up a bearer. The same applies to the MEC server 300-1 side.

The MME 43 connects a bearer that virtualizes the route from the vP-GW to the service in each of the MEC servers 300-1 and 300-1, and the vP-GW of each of the MEC servers 300-1 and 300-2. Are set as virtual bearers (that is, MEC bearers). In the following description, when the virtual bearer is particularly distinguished from the above-described “MEC bearer”, it may be referred to as an “expanded MEC bearer”. With such a configuration, a bearer obtained by virtualizing a series of bearers between the vP-GW_1 of the MEC server 300-1 and the vP-GW_2 of the MEC server 300-2 is further added to the MEC servers 300-1 and 300-. It is possible to extend the service between the two services.

For example, FIGS. 25 and 26 are diagrams illustrating an example of a protocol stack for communication between MEC servers, and correspond to an example of setting a bearer between the MEC servers 300-1 and 300-2 illustrated in FIG. To do. FIG. 25 shows an example of an architecture when GTP-U is not included in the protocol stack of the MEC server 300. In the example shown in FIG. 25, the GTP and GRE (Generic Routing Encapsulation) protocols are terminated by the vP-GW of the MEC server 300. FIG. 26 shows an example of an architecture in the case where GTP-U is included in the protocol stack of the MEC server 300. In the case of the example shown in FIG. 26, the GTP and GRE protocols are terminated at a point (for example, an IP address) that identifies the MEC server 300 itself.

As described above, in the system 1 according to the present embodiment, the path to the vP-GW is virtualized and provided as VNF in the MEC server 300, so that the bearer can be extended to the MEC server 300. Further, in the system 1 according to the present embodiment, the bearer method defined in 3GPP is extended to the MEC server 300, so that, for example, flow-based QoS is applied to bidirectional communication between the MEC servers 300. It is also possible to do.

(3-3) Configuration Example of Bearer For example, FIGS. 27 and 28 are diagrams illustrating an example of the configuration of the MEC bearer. Specifically, FIG. 27 shows an example of the configuration of the MEC bearer when the GTP and GRE protocols are terminated at a point (for example, an IP address, etc.) that identifies the MEC server 300 itself, as shown in FIG. Is shown. FIG. 28 shows an example of the configuration of the MEC bearer when the GTP and GRE protocols are terminated in the vP-GW of the MEC server 300 as shown in FIG.

Further, the target to which the APN is assigned is not necessarily limited to the MEC server 300 alone. As a specific example, for example, an APN may be assigned for each OTT such as a service provider or for each application. In such a case, for example, even in a situation where a plurality of OTT services (in other words, applications) operate on one MEC server 300, each service provided by the OTT is individually based on the APN. It becomes possible to specify. It is also possible to assign an APN for each VM in which an application is mounted or for each container.

For example, FIG. 29 and FIG. 30A are diagrams showing an example of the configuration of the MEC bearer. In the example illustrated in FIG. 29 and FIG. 30A, an MEC bearer (for example, an extended MEC bearer) is set for each OTT in a situation where a plurality of OTT services operate on the MEC server 300. FIG. 29 shows an example of the configuration of the MEC bearer when the GTP and GRE protocols are terminated at a point (for example, an IP address, etc.) that identifies the MEC server 300 itself, as shown in FIG. Yes. FIG. 30A shows an example of the configuration of the MEC bearer when the GTP and GRE protocols are terminated in the vP-GW of the MEC server 300 as shown in FIG. With such a configuration, for example, it is possible to realize provision of independent QoS for each OTT, each VM, or each container. For example, FIG. 30B is a diagram illustrating an example of the configuration of the MEC bearer, and illustrates an example in which an MEC bearer is set for each container. FIG. 30C is a diagram illustrating an example of the configuration of the MEC bearer, and illustrates an example in which an MEC bearer is set for each VM.

FIG. 31 is an explanatory diagram for explaining an example of a bearer configuration in the system 1 according to the present embodiment, and shows an example when the MEC server 300 provides a service to the UE. For example, in the example shown in the upper part of FIG. 31, the MEC server 300-1 (MEC-Server-1) cooperates with another MEC server 300-2 (MEC-Server-2) to An example in the case of providing a service is shown. In this case, an EPS bearer is set between the UE and the MEC server 300-1, and an MEC bearer is set between the MEC server 300-1 and the MEC server 300-2. Further, the example shown in the lower part of FIG. 31 shows an example in which the MEC server 300-1 (MEC-Server-1) provides a service to the UE in cooperation with the application server 60. . In this case, an EPS bearer is set between the UE and the MEC server 300-1, and an MEC bearer is set between the MEC server 300-1 and the application server 60. With such a configuration, the system 1 according to the present embodiment can provide a bearer that satisfies the QoS requested by the service in a more preferable manner.

<4.2. First Example>
Next, as a first example of the present embodiment, a case where an MEC bearer is set between the MEC servers 300 based on a request from a network management function such as OSS or BSS (hereinafter simply referred to as “OSS”). An example will be described. In this description, based on a request from the OSS, by setting an MEC bearer between the MEC server 300-1 and the MEC server 300-2 in FIG. 21, the MEC server 300-1 to the MEC server 300- Description will be given focusing on the case of moving application information to 2.

For example, FIG. 32 is a sequence diagram illustrating an example of the flow of bearer setting processing executed in the system 1 according to the first example of the present embodiment. As shown in FIG. 32, this sequence includes OSS, HSS 44, MME 43, MEC server 300-1 (MEC-Server-1), RN 120-1 (RN_1), DeNB 110-1 (DeNB_1), and S-GW 41. , And the MEC server 300-2 (MEC-Server-2).

First, based on instructions from the OSS, a list of identification information (such as P-GW ID) indicating each node and identification information (APN, PDN ID, etc.) specifying each server is registered in the HSS 44. (S301). The MME 43 generates a GW mapping list based on the information registered in the HSS 44 (S303). The generation of the GW mapping list only needs to be executed in advance, and the same process need not be executed every time the MEC bearer is set between the MEC servers 300.

Next, a description will be given focusing on processing for setting MEC bearers between the MEC servers 300 based on an instruction from the OSS. For example, when moving application information between the MEC servers 300, a network administrator or the like designates the MEC server 300 that is the destination of application information to the OSS via the UI (for example, GUI). Then, instruct the transfer of the information.

As a specific example, it is assumed that a network administrator or the like instructs the OSS to move application information from the MEC server 300-1 to the MEC server 300-2 via a UI (for example, GUI). . In this case, the OSS requests the MME 43 to set the MEC bearer between the MEC server 300-1 and the MEC server 300-2. As a result, the MEC bearer setting request signal is transmitted from the OSS to the MME 43 (S305). The MEC bearer setting request corresponds to an example of a “connection request”.

In response to the MEC bearer setting request from the OSS, the MME 43 collates the APN for connecting to the MEC servers 300-1 and 300-2 with the GW mapping list, and the MEC server 300-1 to the MEC server 300 -2 specifies a list of gateways through which connection is made (S307). In the case of the example shown in FIG. 32, vP-GW_1, vS-GW_1, vDeNB_1, RN120-1, DeNB110-1, S-GW41, and vS in MEC server 300-1 in MEC server 300-1. -GW_2 and vP-GW_2 are identified.

Note that the identification of the P-GW corresponding to the APN is executed based on, for example, a mechanism such as DNS (FQDN: Fully Qualified Domain Name). Also, the identification of the GW in which each MEC server 300 is installed can be executed based on information registered in advance based on an instruction from an OTT or the like such as a service provider, as in the TAI List allocation policy. Good. In addition, the MEC server 300 uses the function (for example, API) provided by the MEC platform, so that the location information of the connected nodes (for example, Radio Nodes such as eNodeB, NodeB, Relay Node, DeNodeB, etc.) And the acquired position information may be notified to the MME 43.

Next, the MME 43 instructs the vS-GW_1 of the MEC server 300-1 to establish an S5 / S8 bearer with the vP-GW_1. Upon receiving this instruction, vS-GW_1 establishes an S5 / S8 bearer with vP-GW_1. Also, the MME 43 instructs the vDeNB_1 of the MEC server 300-1 to establish an S1-U bearer with the RN 120-1. In response to this instruction, vDeNB_1 sets up an S1-U bearer with RN 120-1 (S309). When the setting of each bearer is completed, a response to the MEC bearer setting request is transmitted from the MEC server 300-1 to the MME 43 (S311).

Similarly, the MME 43 instructs the vS-GW_2 of the MEC server 300-2 to establish an S5 / S8 bearer with the vP-GW_2. Upon receiving this instruction, vS-GW_2 establishes an S5 / S8 bearer with vP-GW_2. Also, the MME 43 instructs the vS-GW_2 of the MEC server 300-2 to establish an S1-U bearer with the DeNB 110-1. Upon receiving this instruction, vS-GW_2 establishes an S1-U bearer with DeNB 110-1 (S313). When the bearer setting is completed, a response to the MEC bearer setting request is transmitted from the MEC server 300-2 to the MME 43 (S315).

Further, the MME 43 instructs the DeNB 110-1 via the S-GW 41 to establish an S1-U / Un bearer between the DeNB 110-1 and the RN 120-1 (S317). In response to this instruction, DeNB-1 sets up an S1-U / Un bearer between DeNB 110-1 and RN 120-1 (S319). When the bearer setting is completed, a response to the MEC bearer setting request is transmitted from the S-GW 41 to the MME 43 (S321).

Note that it can be assumed that at least some of the bearers described above are already set (established). Thus, when there is a bearer that has already been set, it is not always necessary to set a new bearer, and a bearer that has already been set may be used.

As described above, a series of bearers for connecting the MEC server 300-1 and the MEC server 300-2 is set, and data transfer between the MEC server 300-1 and the MEC server 300-2 is performed via the bearer. Communication between applications becomes possible. Next, when identification information (for example, an IP address) of the communication points of the MEC servers 300-1 and 300-2 is specified, between the communication point of the VP-GW_1 and the MEC server 300-1, vP-GW_2. And a new bearer (tunnel) is set as a default bearer between the communication point of the MEC server 300-2. Further, the MME 43 sets the MEC bearer by virtualizing a series of bearers set between the MEC server 300-1 and the MEC server 300-2.

When the MME 43 confirms the completion of the setting of each bearer between the MEC server 300-1 and the MEC server 300-2 (that is, the bearer between the gateways specified based on the GW mapping list), the MME bearer requests for setting the MEC bearer Is sent to the OSS (S323).

Thus, the MEC server 300-1 and the MEC server 300-2 are connected by the MEC bearer (S325). As a result, the MEC server 300-1 can transmit application information to the MEC server 300-2 via the set MEC bearer (S327).

Note that the protocol stack in the communication between the MEC server 300-1 and the MEC server 300-2 in the first embodiment is as described above with reference to FIGS.

<4.3. Second Embodiment>
Next, as a second example of the present embodiment, in a situation where the UE 200 communicates with an application that operates on the MEC server 300, the application cooperates with an application that operates on another MEC server 300. An example of operation will be described. In the present description, in the configuration shown in FIG. 21, based on a request from the application Appl-1 operating on the MEC server 300-1, the MEC server 300-1 and the MEC server 300 on which the application Appl-2 operates. In the following description, attention is paid to the case where an MEC bearer is set between -2.

For example, FIG. 33 is a sequence diagram showing an example of the flow of the bearer setting process executed in the system 1 according to the second example of the present embodiment. As shown in FIG. 33, this sequence includes OSS, HSS 44, MME 43, UE 200, MEC server 300-1 (MEC-Server-1), RN 120-1 (RN_1), DeNB 110-1 (DeNB_1), S -GW 41 and MEC server 300-2 (MEC-Server-2) are involved.

First, based on an instruction from the OSS, a list of identification information indicating each node and identification information specifying each server is registered in the HSS 44 (S401), and a GW mapping list is generated by the MME 43 based on the information. (S403). This processing is the same as the processing indicated by reference numerals S301 and S303 in FIG.

Also, based on the request from the UE 200, the application Appl-1 on the MEC server 300-1 starts to operate (S405).

Here, it is assumed that the application Appl-1 needs to cooperate with the application Appl-2 operating on the MEC server 300-2 in order to provide the service to the UE 200. In this case, the application Appl-1 uses the service discovery function provided from the MEC platform, thereby connecting information (for example, APN) to the MEC server 300-2 in which the application Appl-2 is stored. ) Is acquired (S407).

Next, the application Appl-1 requests the MME 43 to set the MEC bearer between the MEC server 300-1 and the MEC server 300-2 based on the acquired APN. Thereby, a setting request signal for the MEC bearer associated with the APN is transmitted from the MEC server 300-1 to the MME 43 (S409). At this time, the partner to which the application App-1 makes a MEC bearer setting request may be a vMME implemented as VNF in the MEC server 300-1. Further, the interface (in other words, the communication path) between the application Appl-1 and the MME 43 can be established by mounting the vS-GW realized as VNF. As another example of an interface from the application Appl-1 to the MME 43, an interface provided by a function called SCEF (Service Capability Exposure Function) may be used. The details of SCEF will be described later.

Note that the processes indicated by reference numerals S411 to S425 are the same as the processes indicated by reference numerals S307 to S321 in FIG. That is, the MME 43 collates the APN associated with the connection request from the application Appl-1 with the GW mapping list, and obtains a list of gateways through which the MEC server 300-1 connects to the MEC server 300-2. Specify (S411). Then, the MME 43 instructs the vS-GW_1 and vDeNB_1 of the MEC server 300-1 and vS-GW_2 and S-GW 41 of the MEC server 300-2 to establish a bearer. As a result, a series of bearers for connecting the MEC server 300-1 and the MEC server 300-2 is set. Next, when identification information (for example, an IP address) of the communication points of the MEC servers 300-1 and 300-2 is specified, between the communication point of the VP-GW_1 and the MEC server 300-1, vP-GW_2. And a new bearer (tunnel) is set as a default bearer between the communication point of the MEC server 300-2. Further, the MME 43 sets an MEC bearer by virtualizing a series of bearers set between the MEC server 300-1 and the MEC server 300-2 (S413 to S425).

When the MME 43 confirms the completion of the setting of each bearer between the MEC server 300-1 and the MEC server 300-2, the MME 43 sends a response to the setting request of the MEC bearer to the application Appl− operating on the MEC server 300-1. 1 (S427).

Thus, the MEC server 300-1 and the MEC server 300-2 are connected by the MEC bearer (S429). As a result, communication between the application Appl-1 operating on the MEC server 300-1 and the application Appl-2 operating on the MEC server 300-2 is enabled via the set MEC bearer. The That is, the application Appl-1 can cooperate with the application Appl-2 through the set MEC bearer (S431).

The MEC bearer set in this embodiment may be, for example, an MEC bearer set between the MEC servers 300-1 and 300-2, or between the applications Appl-1 and Appl-2 (that is, between VMs or It may be an extended MEC bearer set between containers).

In the above description, the cooperation between the MEC servers 300-1 and 300-2 has been described. However, the present invention is not necessarily limited to the same configuration. As a specific example, three or more MEC servers can be linked. In this case, for example, by setting an MEC bearer between each of three or more MEC servers, the three or more MEC bearers can be linked to each other.

Further, the protocol stack in the communication between the MEC server 300-1 and the MEC server 300-2 in the second embodiment is as described above with reference to FIGS.

<4.4. Third Example>
Next, as a third example of the present embodiment, assuming that the UE 200 moves between cells provided by different nodes (eNB, RN, etc.), the MEC server 300 that provides a service to the UE 200 An example in the case of operating in cooperation with another MEC server 300 will be described. In this description, assuming that the UE 200 moves between cells provided by each of the RNs 120-1 and 120-2 in the configuration shown in FIG. 21, the MEC server 300-1 and the MEC server 300-3 A description will be given focusing on a case where an MEC bearer is set between both parties (that is, between the MEC servers 300-1 and 300-3) in order to cooperate.

For example, FIG. 34 is a sequence diagram showing an example of the flow of bearer setting processing executed in the system 1 according to the third example of the present embodiment. As shown in FIG. 34, this sequence includes OSS, HSS 44, MME 43, UE 200, MEC server 300-1 (MEC-Server-1), RN 120-1 (RN_1), DeNB 110-1 (DeNB_1), S -GW41, DeNB110-2 (DeNB_2), RN120-2 (RN_2), and MEC server 300-3 (MEC-Server-3) are involved.

First, based on an instruction from the OSS, a list of identification information indicating each node and identification information specifying each server is registered in the HSS 44 (S501), and a GW mapping list is generated by the MME 43 based on the information. (S503). This processing is the same as the processing indicated by reference numerals S301 and S303 in FIG.

Also, based on the request from the UE 200, the application Appl-1 on the MEC server 300-1 starts to operate (S505).

Here, the UE 200 moves from the cell provided by the RN 120-1 to the cell provided by the RN 120-2, so that the UE 200 uses the other MEC server 300 to provide the service to the UE 200. Assume that a desired state has been detected. In this case, the application Appl-1 uses a service discovery function provided from the MEC platform to provide a service to the UE 200 in a more suitable environment (for example, maximum delay, minimum guaranteed bandwidth). Etc.) to discover the MEC server 300 that can provide the environment. At this time, in order to discover the MEC server 300 that can provide a more suitable environment, the application App1-1, for example, the location information of the UE 200 that is connected and the currently connected node (for example, RN, Information such as eNB, DeNB, NB) may be used. As a result, the application Appl-1 acquires information (for example, vAPN) for connecting to the MEC server 300-3 (S507). In the following description, it is assumed that the application Appl-1 has acquired the APN as information for connecting to the MEC server 300-3. The type of information to be performed is not particularly limited. As a specific example, the application Appl-1 may acquire a URI and an IP address as information for connecting to the MEC server 300-3.

Next, the application Appl-1 (or another application providing the service) issues a request for setting the MEC bearer between the MEC server 300-1 and the MEC server 300-3 to the MME 43 based on the acquired APN. Do. As a result, a setting request signal for the MEC bearer associated with the APN is transmitted from the MEC server 300-1 to the MME 43 (S509). The interface from the MEC server 300-1 to the MME 43 is realized by, for example, an S1-MME interface via a node such as eNB or RN, or an S11 interface via an S-GW.

As another example of an interface from the MEC server 300-1 to the MME 43, an interface provided by SCEF may be used. In this case, the MEC server 300-1 (or an application operating on the MEC server 300-1) can connect to the MME 43 by using, for example, SCEF and make a bearer setting request. . At this time, the MEC server 300-1 can also monitor the bearer setting status (for example, whether the bearer setting is completed) by using SCEF. The details of SCEF will be described later.

Upon receiving the MEC bearer setting request from the application Appl-1, the MME 43 collates the APN for connecting to each of the MEC servers 300-1 and 300-3 with the GW mapping list, and the MEC server 300-1 A list of gateways through which to connect to the MEC server 300-3 is specified (S511). In the case of the example shown in FIG. 34, vP-GW_1, vS-GW_1, and vDeNB_1, RN120-1, DeNB110-1, S-GW41, DeNB110-2, RN120-, and RN120- in MEC server 300-1. 2 and vDeNB_3, vS-GW_3, and vP-GW_3 in the MEC server 300-3 are specified.

Next, the MME 43 instructs the vS-GW_1 of the MEC server 300-1 to establish an S5 / S8 bearer with the vP-GW_1. Upon receiving this instruction, vS-GW_1 establishes an S5 / S8 bearer with vP-GW_1. Also, the MME 43 instructs the vDeNB_1 of the MEC server 300-1 to establish an S1-U bearer with the RN 120-1. In response to this instruction, vDeNB_1 sets up an S1-U bearer with RN 120-1 (S513). When the setting of each bearer is completed, a response to the MEC bearer setting request is transmitted from the MEC server 300-1 to the MME 43 (S515).

Similarly, the MME 43 instructs the vS-GW_3 of the MEC server 300-3 to establish an S5 / S8 bearer with the vP-GW_2. Upon receiving this instruction, vS-GW_3 establishes an S5 / S8 bearer with vP-GW_3. Also, the MME 43 instructs the vDeNB_3 of the MEC server 300-3 to establish an S1-U bearer with the RN 120-2. In response to this instruction, vDeNB_3 sets up an S1-U bearer with RN 120-2 (S517). When the bearer setting is completed, a response to the MEC bearer setting request is transmitted from the MEC server 300-3 to the MME 43 (S519).

Further, the MME 43 instructs the DeNB 110-1 via the S-GW 41 to establish an S1-U / Un bearer between the DeNB 110-1 and the RN 120-1. Upon receiving this instruction, DeNB-1 sets up an S1-U / Un bearer between DeNB 110-1 and RN 120-1 (S523). Similarly, the MME 43 instructs the DeNB 110-2 via the S-GW 41 to establish an S1-U / Un bearer between the DeNB 110-2 and the RN 120-2. In response to this instruction, DeNB-2 sets up an S1-U / Un bearer between DeNB 110-2 and RN 120-2 (S529). Next, the MME 43 instructs the S-GW 41 to establish S1-U / Un bearers between the DeNB 110-1 and the S-GW 41 and between the DeNB 110-2 and the S-GW 41, respectively. In response to this instruction, the S-GW 41 sets S1-U / Un bearers between the DeNB 110-1 and the S-GW 41 and between the DeNB 110-2 and the S-GW 41 (S525, S527). . When a series of bearer settings is completed, a response to the MEC bearer setting request is transmitted from the S-GW 41 to the MME 43 (S531).

Next, when identification information (for example, an IP address) of the communication points of the MEC servers 300-1 and 300-3 is specified, between the communication point of the vP-GW_1 and the MEC server 300-1, vP-GW_3 And a new bearer (tunnel) is set as a default bearer between the communication point of the MEC server 300-3. Further, the MME 43 sets the MEC bearer by virtualizing a series of bearers set between the MEC server 300-1 and the MEC server 300-3.

Note that it can be assumed that at least some of the bearers described above are already set (established). Thus, when there is a bearer that has already been set, it is not always necessary to set a new bearer, and a bearer that has already been set may be used. Further, the bearers set by the above processing between the DeNB 110-1 and the DeNB 110-2, between the RN 120-1 and the DeNB 110-1, and between the RN 120-2 and the DeNB 110-2 are as follows. It is equivalent to a bearer used for an X2 interface mapped one-to-one.

When the MME 43 confirms the completion of the setting of each bearer between the MEC server 300-1 and the MEC server 300-3, the MME 43 sends a response to the MEC bearer setting request as an application Appl- 1 is transmitted (S533).

Thus, the MEC server 300-1 and the MEC server 300-3 are connected by the MEC bearer (S535). This makes it possible to transfer application information between the MEC server 300-1 and the MEC server 300-3 via the set MEC bearer.

As a more specific example, by transferring the information of the application Appl-1 from the MEC server 300-1 to the MEC server 300-3, the application Appl that takes over the information of the application Appl-1 on the MEC server 300-3. -3 can be operated. As another example, the application Appl-3 may be operated on the MEC server 300-3, and the application Appl-3 and the application Appl-1 operating on the MEC server 300-1 may be linked to each other. .

Note that when the UE 200 starts using the application Appl-3 operating on the new MEC server 300-3 from the application Appl-1 used so far, the bearer from the UE 200 to the application Appl-1 is , May be released based on an instruction from the MME 43. In this case, for example, the MME 43 may receive an instruction from the UE 200 or an application and instruct to release the bearer.

Note that the MEC bearer set in this embodiment may be, for example, an MEC bearer set between the MEC servers 300-1 and 300-3, or between the applications Appl-1 and Appl-3 (between VMs and containers). It may be an extended MEC bearer that is set at the same time.

With the above configuration, for example, even when the UE 200 moves to the cell provided by the RN 120-2, the application Appl-1 is replaced with the application Appl-1 by providing the service received from the application Appl-1. -3 can continue to be received. This also allows the UE 200 to have a more suitable environment (for example, an environment that satisfies the maximum delay, the minimum guaranteed bandwidth, etc.) even in a situation where the UE 200 moves between cells provided by each of the RNs 120-1 and 120-2. It becomes possible to receive service provision.

In addition, FIGS. 35 to 37 and FIGS. 38 to 40 show examples of protocol stacks in communication between the MEC server 300-1 and the MEC server 300-3 in the third embodiment. FIGS. 35 to 37 and FIGS. 38 to 40 are diagrams showing examples of protocol stacks for communication between MEC servers. For example, FIGS. 35 to 37 show an example of the architecture in the case where the protocol stack of the MEC server 300 does not include GTP-U. In the case of the examples shown in FIGS. 35 to 37, the GTP and GRE protocols are terminated by the vP-GW of the MEC server 300. FIG. 38 to FIG. 40 show an example of the architecture when the protocol stack of the MEC server 300 includes GTP-U. In the case of the examples shown in FIGS. 38 to 40, the GTP and GRE protocols are terminated at a point that identifies the MEC server 300 itself, or a point that identifies a VM or a container (for example, an IP address). .

<4.5. Fourth embodiment>
Next, as a fourth example of the present embodiment, an example in which so-called access control is performed when an MEC bearer is set between MEC servers located in different PLMNs (Public Land Mobile Networks) will be described. For example, FIG. 41 is an explanatory diagram for describing an overview of a fourth example of the present embodiment.

For example, FIG. 41 shows an example of a configuration for controlling access from the MEC server 300 located on the Visited PLMN side to the MEC server located on the Home PLMN side. The Visited PLMN indicates a PLMN provided by another operator (for example, a carrier) different from the contracted party of the UE (that is, a PLMN connected by roaming). Further, Home PLMN indicates a PLMN provided by an operator that is a contract destination of the UE.

As shown in FIG. 41, the access from the MEC server located on the Visited PLMN side to the service operating on the Home PLMN side MEC server can be accessed from the vPL-GW on the Home PLMN side from the vS-GW on the Visited PLMN side. Done through. At this time, in the system 1 according to the present embodiment, for example, based on the access policy registered in the HSS on the Home PLMN side, the MME on the Visited PLMN side changes from the MEC server located on the Visited PLMN side to the MEC on the Home PLMN side. Control access to the server 300.

As a specific example, in the access policy at the time of roaming shown as “HSS Provisioning APN List”, for services to which “vAPN-H1” is assigned as APN (that is, services provided by “OTT-1”), Access from the visited PLMN side is allowed (Allowed). Also, access from the Visited PLMN side is prohibited (Not-Allowed) for a service to which “vAPN-H2” is assigned as an APN (ie, a service provided by “OTT-2”). In addition, in this access policy, access between the Visited PLMN side service assigned with “vAPN-V1” as the APN and the Home PLMN side service assigned with “vAPN-H1” is individually permitted. Yes.

That is, the MME on the Visited PLMN side is based on the access policy for roaming registered in the HSS on the Home PLMN side, for example, “OTT-2” to which “vAPN-H2” is assigned from the MEC server on the Visited PLMN side. Access to services provided by is prohibited. Also, the MME on the Visited PLMN side permits access to the service provided by “OTT-1” to which “vAPN-H1” is allocated from the MEC server on the Visited PLMN side based on the access policy.

In the system 1 according to the present embodiment, for example, based on the access policy at the time of roaming, for example, an MEC server (or service) operating on the Visited PLMN side and an MEC server (or service) operating on the Home PLMN side are used. ) Is controlled.

As a specific example, the Visited PLMN side MME is based on the roaming access policy registered in the Home PLMN side HSS, and “VAPN-H1” is allocated from the Visited PLMN side MEC server. The setting of the MEC bearer to the service provided by “1” is permitted. Also, the MME on the Visited PLMN side prohibits the setting of the MEC bearer from the Visited PLMN side MEC server to the service provided by “OTT-2” to which “vAPN-H2” is allocated. .

Note that the above-described access control at the time of roaming includes, for example, access control between MEC servers installed in networks of different carriers, and access control considering an MEC server installed in a relay base station having mobility. It is possible to apply. Further, the access control described above may be applied to so-called local breakout.

<4.6. Fifth embodiment>
Next, as a fifth example of the present embodiment, an example in which a mechanism of PCC (Policy and Charging Control) is introduced to the system 1 according to the present embodiment will be described.

For example, FIG. 42 is an explanatory diagram for explaining the outline of the fourth example of the present embodiment, and shows an example of the architecture of the PCC. As described above, the PCRF is a functional entity that performs policy and charging control. As a more specific example, the PCRF executes QoS switching or the like according to the charging status by linking with an online charging system (OCS: Online Charging System) or an offline charging system (OFCS: Offline Charging System). . The TDF (Traffic Detection Function) is a function for identifying and measuring traffic on the network, applying a policy for securing traffic, and the like.

PCEF (Policy and Charging Enforcement Function) is a functional entity that performs policy control and charges for each IP flow according to information notified from the PCRF. The PCEF can be mounted on, for example, the P-GW described above. Further, BBERF (Bearer Biding and Event Reporting Functions) executes policy control according to information notified from the PCRF, similarly to PCEF. Further, BBERF executes cooperation processing with QoS control unique to the access system, such as identification of a radio access bearer that transfers a packet received from the P-GW to the eNB. BBERF can be implemented in the above-described S-GW, for example. The MEC server described above may correspond to an AF (Application Function) shown in FIG.

In the architecture shown in FIG. 42, only an Rx interface for sharing (notifying) information such as QoS is defined as an interface from the AF (that is, the MEC server) to the PCRF. Therefore, an interface for making a QoS request from the AF to the PCRF is not defined, and the PCRF switches the QoS according to information notified from the AF.

In contrast, the application of a new function called SCEF is currently being studied. SCEF provides an interface that enables the exchange of information by accessing the network function in EPC from SCS (Service Capability Server) or AS (Application Serve).

For example, FIG. 43 is an explanatory diagram for describing an example of an interface realized by application of SCEF. As shown in FIG. 43, by applying SCEF, for example, an interface for making a QoS request to the PCRF from the SCS or AS is provided. Thereby, for example, a policy (for example, QoS) can be set for the PCRF from the MEC server (or an application running on the MEC server).

FIG. 44 is an explanatory diagram for describing another example of an interface realized by application of SCEF. As shown in FIG. 44, application of SCEF provides, for example, an interface between the SCS and AS and the HSS. Thereby, for example, an MEC server (or an application running on the MEC server) sends a connection request to another MEC server (that is, an MEC bearer setting request) to the MME via the SCEF and the HSS. It can also be done directly.

45 to 47 are explanatory diagrams for explaining another example of an interface realized by application of SCEF. For example, as shown in FIG. 45, when SCEF is applied, for example, an MEC server (or an application operating on the MEC server) issues a bearer (for example, MEC bearer) setting request to the MME. Is also possible. Also, when a bearer setting request is made from the MEC server to the MME, the bearer setting status (for example, whether or not the bearer setting is completed) is monitored via the interface provided by the application of SCEF. It is also possible to do. For example, FIG. 46 shows an example of a flow of a series of processes related to the monitoring request. FIG. 47 shows an example of a flow of a series of processes related to the monitoring event report.

Also, a function called ADC (Application Detection and Control Function) may be applied to the MEC server. For example, FIGS. 48 and 49 show an example of an architecture for applying an ADC to an MEC server. For example, the ADC can be included in the TDF as shown in FIG. As another example, the ADC may be included in a vPCEF operating on the vP-GW as shown in FIG.

In this way, by applying the ADC to the MEC server, for example, a report of detection and control (for example, start and stop) of a defined application from the MEC server to the PCRF is not transmitted via the Rx interface. Can be realized. As a result, for example, in a situation where a plurality of MEC servers cooperate to provide a service (for example, cloud gaming), QoS (for example, delay, guaranteed bandwidth, etc.) required between the MEC servers is ensured. For this reason, it is possible to assign a resource such as a bearer from the MEC server to the PCRF.

In addition, when there are a plurality of the MMEs in the network, it is possible to share and refer to the GW mapping list or the like by cooperating with each other through an appropriate authentication procedure as necessary. In this case, it is also possible to use the S10 interface currently defined by 3GPP. For example, FIG. 50A shows an example of a protocol stack in communication between MMEs.

<4.7. Evaluation>
Heretofore, each example according to the present embodiment has been described in detail.

According to the present embodiment, the MEC server is installed in a wireless communication network that has not been defined so far without maximizing the use of the existing network protocol and changing the existing network device. It is possible to realize a communication path between servers (MEC servers).

In addition, according to the present embodiment, a plurality of MEC servers can be linked regardless of inside or outside the wireless communication network. For this reason, for example, even for an application in which service provision is restricted, it is possible to provide a service in a more favorable manner to the user by cooperation between the MEC servers. Furthermore, since a plurality of MEC servers having different computing resources can be linked, so-called distributed processing type services can be provided via a wireless communication network.

In addition, according to the present embodiment, it is possible to move application information between MEC servers using the existing OSS and BSS mechanisms.

Further, according to the present embodiment, it is possible to provide the EBS bearer specified by LTE to the MEC server for connection between the MEC servers. Thereby, for example, the QoS mechanism in LTE can be applied to communication (for example, bidirectional communication) between MEC servers.

Further, according to the present embodiment, it is possible to use both the SDN (Software-Defined Networking) / NFV mechanism and the existing 3GPP mechanism. Therefore, for example, application to an IoT network expected to be developed in the future and a 5G network realized in the future is possible.

In addition, according to the present embodiment, the network function is virtualized by VDN of SDN / NFV, thereby realizing communication between servers (between MEC servers) without performing DPI for all packets. It becomes possible. Therefore, for example, it is possible to reduce the load on the system accompanying the execution of DPI. Further, since it is not necessary to perform DPI, it is not always necessary to install an MEC server between network devices, and it becomes easier to install the MEC server in an existing network.

Further, according to the present embodiment, by assigning an APN to an MEC server and using a mechanism such as HSS, MME, and PCRF, for example, an OTT (for example, a service provided by the MEC server) For each provider), it is possible to authenticate and specify a connectable MEC server.

Also, according to this embodiment, it is possible to use an EPS bearer, which is an existing framework of 3GPP, for each APN. Therefore, for example, it is possible to provide appropriate QoS for each service.

Further, according to the present embodiment, it is possible to acquire information (for example, APN) for specifying the MEC server by using the service discovery function provided by the MEC platform. Therefore, for example, based on an instruction from the OSS, UE, or an application (for example, an application operating on the MEC server), a communication path between the MEC servers is established, and application information is moved between the MEC servers. Is also possible. In addition, with such a mechanism, for example, from a MEC server that can provide a more suitable environment (for example, an environment that satisfies the maximum delay, the minimum guaranteed bandwidth, etc.) even in a situation where the UE moves between cells, A service can be provided to the UE.

Further, according to the present embodiment, by using the 3GPP framework, it becomes possible to perform charging and policy control for each application on the MEC server, for each VM, or for each container.

Further, according to the present embodiment, by registering an access policy for each server (for example, MEC server), for each VM, or for each container (in other words, for each APN) in the HSS, it is possible to perform roaming or local breakout. It becomes possible to realize access control to the server at the time.

In the above-described example, the example in which the MME sets the MEC bearer between the MEC servers operating in the eNB, the DeNB, the RN, and the like has been described for the LTE wireless communication access accommodating network. The application target of the present embodiment is not necessarily limited to the LTE wireless communication access accommodating network. For example, the APN is not limited to the designation of the P-GW but can be applied to, for example, a GGSN (GPRS Support Node). Therefore, this embodiment can be applied to a system in which GGSN is used, for example.

As a more specific example, the present embodiment may be applied to a so-called 3G wireless communication access accommodating network. For example, FIG. 50B is a diagram illustrating an example of an EPC network architecture. As shown in FIG. 50B, in the 3G radio access accommodating network, the SGSN plays the same role as the MME in the LTE radio communication access accommodating network. Therefore, for example, the SGSN may generate a GW mapping list based on information recorded and managed in advance in the HSS, and set an MEC bearer between MEC servers operating on the RNC or NodeB based on the GW mapping list. .

<< 5. Application example >>
The technology according to the present disclosure can be applied to various products. For example, the MEC server 300 or the application server 60 may be realized as any type of server such as a tower server, a rack server, or a blade server. In addition, at least a part of the components of the MEC server 300 or the application server 60 is a module mounted on the server (for example, an integrated circuit module configured by one die, or a card or blade inserted into a slot of the blade server ).

Also, for example, the MEC server 300 may be realized as any kind of eNB (evolved Node B) such as a macro eNB or a small eNB. The small eNB may be an eNB that covers a cell smaller than a macro cell, such as a pico eNB, a micro eNB, or a home (femto) eNB. Instead, the MEC server 300 may be realized as another type of base station such as a NodeB or a BTS (Base Transceiver Station). The MEC server 300 may include a main body (also referred to as a base station device) that controls wireless communication, and one or more RRHs (Remote Radio Heads) that are arranged at a location different from the main body. In addition, various types of terminals described later may operate as the MEC server 300 by temporarily or semi-permanently executing the base station function. Furthermore, at least some components of the MEC server 300 may be realized in a base station device or a module for the base station device.

Further, for example, the MEC server 300 is a smartphone, a tablet PC (Personal Computer), a notebook PC, a portable game terminal, a mobile terminal such as a portable / dongle type mobile router or a digital camera, or an in-vehicle terminal such as a car navigation device. It may be realized as. In addition, the MEC server 300 is a terminal that performs M2M (Machine To Machine) communication (also referred to as MTC (Machine Type Communication) terminal), such as surveillance cameras, gateway terminals of various sensor devices, cars, buses, trains, airplanes, etc. You may implement | achieve in the vehicle etc. which implement | achieve a means. Furthermore, at least a part of the components of the MEC server 300 may be realized in a module (for example, an integrated circuit module configured by one die) mounted on these terminals.

<5.1. Application examples for servers>
FIG. 51 is a block diagram illustrating an example of a schematic configuration of a server 700 to which the technology according to the present disclosure can be applied. The server 700 includes a processor 701, a memory 702, a storage 703, a network interface 704, and a bus 706.

The processor 701 may be a CPU (Central Processing Unit) or a DSP (Digital Signal Processor), for example, and controls various functions of the server 700. The memory 702 includes a RAM (Random Access Memory) and a ROM (Read Only Memory), and stores programs and data executed by the processor 701. The storage 703 may include a storage medium such as a semiconductor memory or a hard disk.

The network interface 704 is a wired communication interface for connecting the server 700 to the wired communication network 705. The wired communication network 705 may be a core network such as EPC (Evolved Packet Core) or a PDN (Packet Data Network) such as the Internet.

The bus 706 connects the processor 701, the memory 702, the storage 703, and the network interface 704 to each other. The bus 706 may include two or more buses with different speeds (eg, a high speed bus and a low speed bus).

In the server 700 shown in FIG. 51, one or more components (MEC platform 331, VNF 333 and / or service providing unit 335) included in the MEC server 300 described with reference to FIG. May be. As an example, a program for causing a processor to function as the one or more components (in other words, a program for causing the processor to execute the operation of the one or more components) is installed in the server 700, and the processor 701 is The program may be executed. As another example, the server 700 may include a module including the processor 701 and the memory 702, and the one or more components may be mounted in the module. In this case, the module may store a program for causing the processor to function as the one or more components in the memory 702 and execute the program by the processor 701. As described above, the server 700 or the module may be provided as an apparatus including the one or more components, and the program for causing a processor to function as the one or more components may be provided. . In addition, a readable recording medium in which the program is recorded may be provided.

51, one or more components (service providing unit 64) included in the application server 60 described with reference to FIG. 12 may be implemented in the processor 701. In the server 700 illustrated in FIG. As an example, a program for causing a processor to function as the one or more components (in other words, a program for causing the processor to execute the operation of the one or more components) is installed in the server 700, and the processor 701 is The program may be executed. As another example, the server 700 may include a module including the processor 701 and the memory 702, and the one or more components may be mounted in the module. In this case, the module may store a program for causing the processor to function as the one or more components in the memory 702 and execute the program by the processor 701. As described above, the server 700 or the module may be provided as an apparatus including the one or more components, and the program for causing a processor to function as the one or more components may be provided. . In addition, a readable recording medium in which the program is recorded may be provided.

<5.2. Application examples for base stations>
(First application example)
FIG. 52 is a block diagram illustrating a first example of a schematic configuration of an eNB to which the technology according to the present disclosure may be applied. The eNB 800 includes one or more antennas 810 and a base station device 820. Each antenna 810 and the base station apparatus 820 can be connected to each other via an RF cable.

Each of the antennas 810 has a single or a plurality of antenna elements (for example, a plurality of antenna elements constituting a MIMO antenna), and is used for transmission and reception of radio signals by the base station apparatus 820. The eNB 800 includes a plurality of antennas 810 as illustrated in FIG. 52, and the plurality of antennas 810 may respectively correspond to a plurality of frequency bands used by the eNB 800, for example. 52 illustrates an example in which the eNB 800 includes a plurality of antennas 810, but the eNB 800 may include a single antenna 810.

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

The controller 821 may be a CPU or a DSP, for example, and operates various functions of the upper layer of the base station apparatus 820. For example, the controller 821 generates a data packet from the data in the signal processed by the wireless communication interface 825, and transfers the generated packet via the network interface 823. The controller 821 may generate a bundled packet by bundling data from a plurality of baseband processors, and may transfer the generated bundled packet. In addition, the controller 821 is a logic that executes control such as radio resource control, radio bearer control, mobility management, inflow control, or scheduling. May have a typical function. Moreover, the said control may be performed in cooperation with a surrounding eNB or a core network node. The memory 822 includes RAM and ROM, and stores programs executed by the controller 821 and various control data (for example, terminal list, transmission power data, scheduling data, and the like).

The network interface 823 is a communication interface for connecting the base station device 820 to the core network 824. The controller 821 may communicate with the core network node or other eNB via the network interface 823. In that case, the eNB 800 and the core network node or another eNB may be connected to each other by a logical interface (for example, an S1 interface or an X2 interface). The network interface 823 may be a wired communication interface or a wireless communication interface for wireless backhaul. When the network interface 823 is a wireless communication interface, the network interface 823 may use a frequency band higher than the frequency band used by the wireless communication interface 825 for wireless communication.

The wireless communication interface 825 supports any cellular communication scheme such as LTE (Long Term Evolution) or LTE-Advanced, and provides a wireless connection to terminals located in the cell of the eNB 800 via the antenna 810. The wireless communication interface 825 may typically include a baseband (BB) processor 826, an RF circuit 827, and the like. The BB processor 826 may perform, for example, encoding / decoding, modulation / demodulation, and multiplexing / demultiplexing, and each layer (for example, L1, MAC (Medium Access Control), RLC (Radio Link Control), and PDCP). Various signal processing of (Packet Data Convergence Protocol) is executed. The BB processor 826 may have some or all of the logical functions described above instead of the controller 821. The BB processor 826 may be a module that includes a memory that stores a communication control program, a processor that executes the program, and related circuits. The function of the BB processor 826 may be changed by updating the program. Good. Further, the module may be a card or a blade inserted into a slot of the base station apparatus 820, or a chip mounted on the card or the blade. On the other hand, the RF circuit 827 may include a mixer, a filter, an amplifier, and the like, and transmits and receives a radio signal via the antenna 810.

The wireless communication interface 825 includes a plurality of BB processors 826 as illustrated in FIG. 52, and the plurality of BB processors 826 may respectively correspond to a plurality of frequency bands used by the eNB 800, for example. Further, the wireless communication interface 825 includes a plurality of RF circuits 827 as shown in FIG. 52, and the plurality of RF circuits 827 may respectively correspond to a plurality of antenna elements, for example. 52 illustrates an example in which the wireless communication interface 825 includes a plurality of BB processors 826 and a plurality of RF circuits 827, the wireless communication interface 825 includes a single BB processor 826 or a single RF circuit 827. But you can.

52, one or more components (MEC platform 331, VNF 333 and / or service providing unit 335) included in the MEC server 300 described with reference to FIG. 11 are implemented in the wireless communication interface 825. May be. Alternatively, at least some of these components may be implemented in the controller 821. As an example, the eNB 800 includes a module including a part (for example, the BB processor 826) or all of the wireless communication interface 825 and / or the controller 821, and the one or more components are mounted in the module. Good. In this case, the module stores a program for causing the processor to function as the one or more components (in other words, a program for causing the processor to execute the operation of the one or more components). The program may be executed. As another example, a program for causing a processor to function as the one or more components is installed in the eNB 800, and the radio communication interface 825 (eg, the BB processor 826) and / or the controller 821 executes the program. Good. As described above, the eNB 800, the base station apparatus 820, or the module may be provided as an apparatus including the one or more components, and a program for causing a processor to function as the one or more components is provided. May be. In addition, a readable recording medium in which the program is recorded may be provided.

(Second application example)
FIG. 53 is a block diagram illustrating a second example of a schematic configuration of an eNB to which the technology according to the present disclosure may be applied. The eNB 830 includes one or more antennas 840, a base station apparatus 850, and an RRH 860. Each antenna 840 and RRH 860 may be connected to each other via an RF cable. Base station apparatus 850 and RRH 860 can be connected to each other via a high-speed line such as an optical fiber cable.

Each of the antennas 840 has a single or a plurality of antenna elements (for example, a plurality of antenna elements constituting a MIMO antenna), and is used for transmission / reception of radio signals by the RRH 860. As illustrated in FIG. 53, the eNB 830 includes a plurality of antennas 840, and the plurality of antennas 840 may correspond to a plurality of frequency bands used by the eNB 830, for example. FIG. 53 illustrates an example in which the eNB 830 includes a plurality of antennas 840, but the eNB 830 may include a single antenna 840.

The base station device 850 includes 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.

The wireless communication interface 855 supports a cellular communication method such as LTE or LTE-Advanced, and provides a wireless connection to a terminal located in a sector corresponding to the RRH 860 via the RRH 860 and the antenna 840. The wireless communication interface 855 may 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. 52 except that the BB processor 856 is connected to the RF circuit 864 of the RRH 860 via the connection interface 857. The wireless communication interface 855 includes a plurality of BB processors 856 as illustrated in FIG. 53, and the plurality of BB processors 856 may respectively correspond to a plurality of frequency bands used by the eNB 830, for example. 53 shows an example in which the wireless communication interface 855 includes a plurality of BB processors 856, the wireless communication interface 855 may include a single BB processor 856.

The connection interface 857 is an interface for connecting the base station device 850 (wireless communication interface 855) to the RRH 860. The connection interface 857 may be a communication module for communication on the high-speed line that connects the base station apparatus 850 (wireless communication interface 855) and the RRH 860.

In addition, the RRH 860 includes a connection interface 861 and a wireless communication interface 863.

The connection interface 861 is an interface for connecting the RRH 860 (wireless communication interface 863) to the base station device 850. The connection interface 861 may be a communication module for communication on the high-speed line.

The wireless communication interface 863 transmits and receives wireless signals via the antenna 840. The wireless communication interface 863 may typically include an RF circuit 864 and the like. The RF circuit 864 may include a mixer, a filter, an amplifier, and the like, and transmits and receives wireless signals via the antenna 840. The wireless communication interface 863 includes a plurality of RF circuits 864 as shown in FIG. 53, and the plurality of RF circuits 864 may correspond to, for example, a plurality of antenna elements, respectively. FIG. 53 shows an example in which the wireless communication interface 863 includes a plurality of RF circuits 864, but the wireless communication interface 863 may include a single RF circuit 864.

53, one or more components (MEC platform 331, VNF 333, and / or service providing unit 335) included in the MEC server 300 described with reference to FIG. 11 include the wireless communication interface 855 and / or Alternatively, the wireless communication interface 863 may be implemented. Alternatively, at least some of these components may be implemented in the controller 851. As an example, the eNB 830 includes a module including a part (for example, the BB processor 856) or the whole of the wireless communication interface 855 and / or the controller 851, and the one or more components are mounted in the module. Good. In this case, the module stores a program for causing the processor to function as the one or more components (in other words, a program for causing the processor to execute the operation of the one or more components). The program may be executed. As another example, a program for causing a processor to function as the one or more components is installed in the eNB 830, and the wireless communication interface 855 (eg, the BB processor 856) and / or the controller 851 executes the program. Good. As described above, the eNB 830, the base station apparatus 850, or the module may be provided as an apparatus including the one or more components, and a program for causing a processor to function as the one or more components is provided. May be. In addition, a readable recording medium in which the program is recorded may be provided.

<5.3. Application examples related to terminal devices>
(First application example)
FIG. 54 is a block diagram illustrating an example of a schematic configuration of a smartphone 900 to which the technology according to the present disclosure can be applied. The smartphone 900 includes a processor 901, a memory 902, a storage 903, an external connection interface 904, a camera 906, a sensor 907, a microphone 908, an input device 909, a display device 910, a speaker 911, a wireless communication interface 912, one or more antenna switches 915. One or more antennas 916, a bus 917, a battery 918 and an auxiliary controller 919 are provided.

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

The camera 906 includes, for example, an image sensor such as a CCD (Charge Coupled Device) or a CMOS (Complementary Metal Oxide Semiconductor), and generates a captured image. The sensor 907 may include a sensor group such as a positioning sensor, a gyro sensor, a geomagnetic sensor, and an acceleration sensor. The microphone 908 converts sound input to the smartphone 900 into an audio signal. The input device 909 includes, for example, a touch sensor that detects a touch on the screen of the display device 910, a keypad, a keyboard, a button, or a switch, and receives an operation or information input from a 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 an output image of the smartphone 900. The speaker 911 converts an audio signal output from the smartphone 900 into audio.

The wireless communication interface 912 supports any cellular communication method such as LTE or LTE-Advanced, and performs wireless communication. The wireless communication interface 912 may typically include a BB processor 913, an RF circuit 914, and the like. The BB processor 913 may perform, for example, encoding / decoding, modulation / demodulation, and multiplexing / demultiplexing, and performs various signal processing for wireless communication. On the other hand, the RF circuit 914 may include a mixer, a filter, an amplifier, and the like, and transmits and receives radio signals via the antenna 916. The wireless communication interface 912 may be a one-chip module in which the BB processor 913 and the RF circuit 914 are integrated. The wireless communication interface 912 may include a plurality of BB processors 913 and a plurality of RF circuits 914 as shown in FIG. 54 shows an example in which the wireless communication interface 912 includes a plurality of BB processors 913 and a plurality of RF circuits 914, the wireless communication interface 912 includes a single BB processor 913 or a single RF circuit 914. But you can.

Furthermore, the wireless communication interface 912 may support other types of wireless communication methods such as a short-range wireless communication method, a proximity wireless communication method, or a wireless LAN (Local Area Network) method in addition to the cellular communication method. In that case, a BB processor 913 and an RF circuit 914 for each wireless communication method may be included.

Each of the antenna switches 915 switches the connection destination of the antenna 916 among a plurality of circuits (for example, circuits for different wireless communication systems) included in the wireless communication interface 912.

Each of the antennas 916 includes a single or a plurality of antenna elements (for example, a plurality of antenna elements constituting a MIMO antenna), and is used for transmission / reception of a radio signal by the radio communication interface 912. The smartphone 900 may include a plurality of antennas 916 as illustrated in FIG. Note that FIG. 54 illustrates an example in which the smartphone 900 includes a plurality of antennas 916, but the smartphone 900 may include a single antenna 916.

Furthermore, the smartphone 900 may include an antenna 916 for each wireless communication method. In that case, the antenna switch 915 may be omitted from the configuration of the smartphone 900.

The bus 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 auxiliary controller 919 to each other. . The battery 918 supplies power to each block of the smartphone 900 shown in FIG. 54 via a power supply line partially shown by a broken line in the drawing. For example, the auxiliary controller 919 operates the minimum necessary functions of the smartphone 900 in the sleep mode.

54, one or more components (MEC platform 331, VNF 333, and / or service providing unit 335) included in the MEC server 300 described with reference to FIG. 11 are included in the wireless communication interface 912. May be implemented. Alternatively, at least some of these components may be implemented in the processor 901 or the auxiliary controller 919. As an example, the smartphone 900 includes a module including a part (for example, the BB processor 913) or the whole of the wireless communication interface 912, the processor 901, and / or the auxiliary controller 919, and the one or more components in the module. May be implemented. In this case, the module stores a program for causing the processor to function as the one or more components (in other words, a program for causing the processor to execute the operation of the one or more components). The program may be executed. As another example, a program for causing a processor to function as the one or more components is installed in the smartphone 900, and the wireless communication interface 912 (eg, the BB processor 913), the processor 901, and / or the auxiliary controller 919 is The program may be executed. As described above, the smartphone 900 or the module may be provided as a device including the one or more components, and a program for causing a processor to function as the one or more components may be provided. In addition, a readable recording medium in which the program is recorded may be provided.

(Second application example)
FIG. 55 is a block diagram illustrating an example of a schematic configuration of a car navigation device 920 to which the technology according to the present disclosure can be applied. The car 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 storage medium interface 928, an input device 929, a display device 930, a speaker 931, and wireless communication. The interface 933 includes one or more antenna switches 936, one or more antennas 937, and a battery 938.

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

The GPS module 924 measures the position (for example, latitude, longitude, and altitude) of the car navigation device 920 using GPS signals received from GPS satellites. The sensor 925 may include a sensor group such as a gyro sensor, a geomagnetic sensor, and an atmospheric pressure sensor. The data interface 926 is connected to the in-vehicle network 941 through a terminal (not shown), for example, and acquires data generated on the vehicle side such as vehicle speed data.

The content player 927 reproduces content stored in a storage medium (for example, 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 a touch on the screen of the display device 930, and receives an operation 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 content to be reproduced. The speaker 931 outputs the navigation function or the audio of the content to be played back.

The wireless communication interface 933 supports any cellular communication method such as LTE or LTE-Advanced, and performs wireless communication. The wireless communication interface 933 may typically include a BB processor 934, an RF circuit 935, and the like. The BB processor 934 may perform, for example, encoding / decoding, modulation / demodulation, and multiplexing / demultiplexing, and performs various signal processing for wireless communication. On the other hand, the RF circuit 935 may include a mixer, a filter, an amplifier, and the like, and transmits and receives a radio signal via the antenna 937. The wireless communication interface 933 may be a one-chip module in which the BB processor 934 and the RF circuit 935 are integrated. The wireless communication interface 933 may include a plurality of BB processors 934 and a plurality of RF circuits 935 as shown in FIG. 55 shows an example in which the wireless communication interface 933 includes a plurality of BB processors 934 and a plurality of RF circuits 935, the wireless communication interface 933 includes a single BB processor 934 or a single RF circuit 935. But you can.

Further, the wireless communication interface 933 may support other types of wireless communication methods such as a short-range wireless communication method, a proximity wireless communication method, or a wireless LAN method in addition to the cellular communication method. A BB processor 934 and an RF circuit 935 may be included for each communication method.

Each of the antenna switches 936 switches the connection destination of the antenna 937 among a plurality of circuits included in the wireless communication interface 933 (for example, circuits for different wireless communication systems).

Each of the antennas 937 has a single or a plurality of antenna elements (for example, a plurality of antenna elements constituting a MIMO antenna), and is used for transmission / reception of a radio signal by the radio communication interface 933. The car navigation device 920 may include a plurality of antennas 937 as shown in FIG. FIG. 55 shows an example in which the car navigation apparatus 920 includes a plurality of antennas 937, but the car navigation apparatus 920 may include a single antenna 937.

Furthermore, the car navigation device 920 may include an antenna 937 for each wireless communication method. In that case, the antenna switch 936 may be omitted from the configuration of the car navigation device 920.

The battery 938 supplies power to each block of the car navigation apparatus 920 shown in FIG. 55 via a power supply line partially shown by a broken line in the figure. Further, the battery 938 stores electric power supplied from the vehicle side.

In the car navigation device 920 shown in FIG. 55, one or more components (MEC platform 331, VNF 333 and / or service providing unit 335) included in the MEC server 300 described with reference to FIG. It may be implemented at 933. Alternatively, at least some of these components may be implemented in the processor 921. As an example, the car navigation apparatus 920 includes a module including a part (for example, the BB processor 934) or the whole of the wireless communication interface 933 and / or the processor 921, and the one or more components are mounted in the module. May be. In this case, the module stores a program for causing the processor to function as the one or more components (in other words, a program for causing the processor to execute the operation of the one or more components). The program may be executed. As another example, a program for causing a processor to function as the one or more components is installed in the car navigation device 920, and the wireless communication interface 933 (eg, the BB processor 934) and / or the processor 921 executes the program. May be. As described above, the car navigation apparatus 920 or the module may be provided as an apparatus including the one or more components, and a program for causing a processor to function as the one or more components may be provided. Good. In addition, a readable recording medium in which the program is recorded may be provided.

Also, the technology according to the present disclosure may be realized as an in-vehicle system (or vehicle) 940 including one or more blocks of the car navigation device 920 described above, an in-vehicle network 941, and a vehicle side module 942. That is, the in-vehicle system (or vehicle) 940 may be provided as a device including the MEC platform 331, the VNF 333, and / or the service providing unit 335. The vehicle-side module 942 generates vehicle-side data such as vehicle speed, engine speed, or failure information, and outputs the generated data to the in-vehicle network 941.

<< 6. Conclusion >>
The embodiment of the present disclosure has been described above in detail with reference to FIGS. As described above, the MME 43 according to the present embodiment acquires a connection request associated with an APN (Access Point Name) indicating a connection destination. Then, the MME 43 specifies the request source of the connection request and the APN associated with the connection request based on the management information in which the APN and the gateway through which to connect to the server designated by the APN are associated. A bearer is set between the server and the server to be executed. With such a configuration, according to the system 1 according to the present embodiment, a communication path between servers in the MEC (that is, between MEC servers) can be set in a more preferable manner.

The preferred embodiments of the present disclosure have been described in detail above with reference to the accompanying drawings, but the technical scope of the present disclosure is not limited to such examples. It is obvious that a person having ordinary knowledge in the technical field of the present disclosure can come up with various changes or modifications within the scope of the technical idea described in the claims. Of course, it is understood that it belongs to the technical scope of the present disclosure.

In addition, the effects described in this specification are merely illustrative or illustrative, and are not limited. That is, the technology according to the present disclosure can exhibit other effects that are apparent to those skilled in the art from the description of the present specification in addition to or instead of the above effects.

The following configurations also belong to the technical scope of the present disclosure.
(1)
An acquisition unit for acquiring a connection request associated with an APN (Access Point Name) indicating a connection destination;
Based on the management information associated with the APN and the gateway through which the APN designates a server to be connected, the connection request request source and the APN associated with the connection request are designated by the APN. A control unit for setting a bearer between the server and
An apparatus comprising:
(2)
The controller is
Identifying at least one gateway through which to connect to the server specified by the APN associated with the connection request based on the management information;
A bearer is set between each of the request source, the server, and the identified at least one gateway;
The apparatus according to (1) above.
(3)
The control unit includes a series of bearers set between the request source, the server specified by the APN, and the gateway that is connected to connect to the server. Is set as a virtual bearer that connects the two.
(4)
The server specified by the APN is a virtual server operating on a physical server of a mobile communication network;
The controller is
Based on the management information, as at least one of the gateways, a first gateway on a mobile communication network that is connected to the physical server on which the virtual server specified by the APN operates, the physical server, A virtual second gateway for connecting to the virtual server,
At least a bearer is set between the identified first gateway, the physical server, the identified second gateway, and the virtual server.
The apparatus according to (2) or (3).
(5)
The APN is associated with the server;
The control unit sets a bearer between the connection request source and the server indicated by the APN associated with the connection request based on the management information. The device according to any one of the above.
(6)
The APN is associated with an application that operates on the server specified by the APN,
The acquisition unit acquires the connection request in which the APN and identification information for specifying the application operating on the server are associated with each other,
The control unit sets a bearer between the server specified by the APN associated with the connection request and the application indicated by the APN based on the identification information.
The apparatus according to any one of (1) to (4).
(7)
The APN is associated with a service provider;
The control unit sets the bearer between the request source and the server for providing the service by the provider indicated by the APN associated with the connection request based on the management information. The apparatus according to any one of (1) to (4).
(9)
The APN is associated with a virtual machine operating on the server specified by the APN,
The acquisition unit acquires the connection request in which the APN is associated with identification information for specifying the virtual machine operating on the server,
The control unit sets a bearer between the server specified by the APN associated with the connection request and the virtual machine indicated by the APN based on the identification information.
The apparatus according to any one of (1) to (4).
(9)
The APN is associated with a container operating on the server designated by the APN,
The acquisition unit acquires the connection request in which the APN and identification information for specifying the container operating on the server are associated with each other,
The control unit sets a bearer between the server specified by the APN associated with the connection request and the container indicated by the APN based on the identification information.
The apparatus according to any one of (1) to (4).
(10)
The apparatus according to any one of (1) to (9), wherein the control unit controls a type of bearer set for each APN.
(11)
The apparatus according to any one of (1) to (10), wherein the control unit selectively restricts connection to the server designated by the APN for each APN.
(12)
A transmission unit that transmits a connection request associated with an APN (Access Point Name) indicating a connection destination to an external device;
Based on the management information in which the APN and the gateway through which to connect to the server designated by the APN are associated, set to connect to the server designated by the APN associated with the connection request A processing unit that performs communication with the server via the bearer;
An apparatus comprising:
(13)
Obtaining a connection request associated with an APN (Access Point Name) indicating a connection destination;
Based on the management information in which the processor associates the APN and the gateway through which to connect to the server designated by the APN, the request source of the connection request and the APN associated with the connection request are Setting up a bearer with the server to be designated;
Including the method.
(14)
Transmitting a connection request associated with an APN (Access Point Name) indicating a connection destination to an external device;
In order for the processor to connect to the server designated by the APN associated with the connection request based on management information associated with the APN and a gateway through which the APN is designated to connect to the server designated by the APN Performing communication with the server via the configured bearer;
Including the method.
(15)
On the computer,
Obtaining a connection request associated with an APN (Access Point Name) indicating a connection destination;
Based on the management information associated with the APN and the gateway through which the APN designates a server to be connected, the connection request request source and the APN associated with the connection request are designated by the APN. Setting up a bearer with the server,
A program that executes
(16)
On the computer,
Transmitting a connection request associated with an APN (Access Point Name) indicating a connection destination to an external device;
Based on the management information in which the APN and the gateway through which to connect to the server designated by the APN are associated, set to connect to the server designated by the APN associated with the connection request Performing communication with the server via the bearer;
A program that executes

1 system 10 cell 40 core network 41 S-GW
42 P-GW
43 MME
44 HSS
50 packet data network 60 application server 61 communication unit 62 storage unit 63 processing unit 64 service providing unit 100 wireless communication device 200 terminal device 300 MEC server 310 communication unit 320 storage unit 330 processing unit

Claims

An acquisition unit for acquiring a connection request associated with an APN (Access Point Name) indicating a connection destination;
Based on the management information associated with the APN and the gateway through which the APN designates a server to be connected, the connection request request source and the APN associated with the connection request are designated by the APN. A control unit for setting a bearer between the server and
An apparatus comprising:
The controller is
Identifying at least one gateway through which to connect to the server specified by the APN associated with the connection request based on the management information;
A bearer is set between each of the request source, the server, and the identified at least one gateway;
The apparatus of claim 1.
The control unit includes a series of bearers set between the request source, the server specified by the APN, and the gateway that is connected to connect to the server. The apparatus according to claim 2, wherein the device is set as a virtual bearer that connects the two.
The server specified by the APN is a virtual server operating on a physical server of a mobile communication network;
The controller is
Based on the management information, as at least one of the gateways, a first gateway on a mobile communication network that is connected to the physical server on which the virtual server specified by the APN operates, the physical server, A virtual second gateway for connecting to the virtual server,
At least a bearer is set between the identified first gateway, the physical server, the identified second gateway, and the virtual server.
The apparatus of claim 2.
The APN is associated with the server;
The apparatus according to claim 1, wherein the control unit sets a bearer between a request source of the connection request and the server indicated by the APN associated with the connection request based on the management information.
The APN is associated with an application that operates on the server specified by the APN,
The acquisition unit acquires the connection request in which the APN and identification information for specifying the application operating on the server are associated with each other,
The control unit sets a bearer between the server specified by the APN associated with the connection request and the application indicated by the APN based on the identification information.
The apparatus of claim 1.
The APN is associated with a service provider;
The control unit sets the bearer between the request source and the server for providing the service by the provider indicated by the APN associated with the connection request based on the management information. The apparatus of claim 1.
The APN is associated with a virtual machine operating on the server specified by the APN,
The acquisition unit acquires the connection request in which the APN is associated with identification information for specifying the virtual machine operating on the server,
The control unit sets a bearer between the server specified by the APN associated with the connection request and the virtual machine indicated by the APN based on the identification information.
The apparatus of claim 1.
The APN is associated with a container operating on the server designated by the APN,
The acquisition unit acquires the connection request in which the APN and identification information for specifying the container operating on the server are associated with each other,
The control unit sets a bearer between the server specified by the APN associated with the connection request and the container indicated by the APN based on the identification information.
The apparatus of claim 1.
The apparatus according to claim 1, wherein the control unit controls the type of bearer set for each APN.
The apparatus according to claim 1, wherein the control unit selectively restricts connection to the server designated by the APN for each APN.
A transmission unit that transmits a connection request associated with an APN (Access Point Name) indicating a connection destination to an external device;
Based on the management information in which the APN and the gateway through which to connect to the server designated by the APN are associated, set to connect to the server designated by the APN associated with the connection request A processing unit that performs communication with the server via the bearer;
An apparatus comprising:
Obtaining a connection request associated with an APN (Access Point Name) indicating a connection destination;
Based on the management information in which the processor associates the APN and the gateway through which to connect to the server designated by the APN, the request source of the connection request and the APN associated with the connection request are Setting up a bearer with the server to be designated;
Including the method.
Transmitting a connection request associated with an APN (Access Point Name) indicating a connection destination to an external device;
In order for the processor to connect to the server designated by the APN associated with the connection request based on management information associated with the APN and a gateway through which the APN is designated to connect to the server designated by the APN Performing communication with the server via the configured bearer;
Including the method.
On the computer,
Obtaining a connection request associated with an APN (Access Point Name) indicating a connection destination;
Based on the management information associated with the APN and the gateway through which the APN designates a server to be connected, the connection request request source and the APN associated with the connection request are designated by the APN. Setting up a bearer with the server,
A program that executes
On the computer,
Transmitting a connection request associated with an APN (Access Point Name) indicating a connection destination to an external device;
Based on the management information in which the APN and the gateway through which to connect to the server designated by the APN are associated, set to connect to the server designated by the APN associated with the connection request Performing communication with the server via the bearer;
A program that executes